TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Hi! It's me again! ;-) (I hope my questions are providing at least
some entertainment....) If you're not a C programmer, you can probably
skip this message.
The bulk of my document is the Function Reference for a C API. At the
beginning of each function is a Syntax section with a C function
prototype. We're now arguing over the precise format for the syntax.
Following are three choices at least a couple of us like; if you have
any wildly better ideas, let me know.
Send e-mail, and I'll summarize:
K&R style
int foo ( bar, baz );
long bar; /* This does something */
int baz; /* This does something else */
"standard" ANSI style
int foo
long bar, /* This does something */
int baz /* This does something else */
);
"compact" ANSI style
int foo(
long bar, /* This does something */
int baz); /* This does something else */
(It's nice working at a place where I can hack my own path, but I wish
the stones weren't so hard ...)
--
--- Aahz (@netcom.com)
Hugs and backrubs -- I break Rule 6
Androgynous kinky vanilla queer het
The best way to get information on Usenet is not to ask a question,
but to post the wrong information.
