On 11/7/07, David Walker <[EMAIL PROTECTED]> wrote:
> style(9) man page (DESCRIPTION section) says:
> Then there's a blank line, followed by the /usr/include files. The
> /usr/include files should be sorted!
>
> I guess this means alphabetically. Can someone confirm or deny please?
mostly. some headers go on top always, like sys/types.h.
> Also, although not explicitly stated, it appears to be suggested that
> single line comments are punctuated.
> (DESCRIPTION section):
> /*
> * Multi-line comments look like this. Make them real sentences.
> * Fill them so they look like real paragraphs.
> */
> and:
> #include <sys/types.h> /* Non-local includes in brackets. */
> and various other places.
> However, when defining structures, the examples:
> struct foo {
> struct foo *next; /* List of active foo */
> struct mumble amumble; /* Comment for mumble */
> int bar;
> };
> struct foo *foohead; /* Head of global foo list */
> (etcetera) suggest ambiguity.
> Clarification appreciated.
i think this doesn't matter. style guidelines are just guidelines.
