d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Two minor fixes:

Browse Source 
o It is the /usr/include files, not the /usr include files.
o Document the practice of converting to the c99 standard uintXX_t
  form from the older, but non-standard, BSD-style u_intXX_t.  This
  has been going on in the tree for a while now, and I've heard other
  developers also state that this conversion is happening.  Note also
  that this is a slow process and should be treated like whitespace
  changes.
This commit is contained in:
Warner Losh 2003-09-27 22:17:37 +00:00
parent 98c469d484
commit 3c29b8c1c8
1 changed files with 15 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
share/man/man9/style.9
View File

@ -120,8 +120,8 @@ Do not use files in
for files in the kernel. for files in the kernel.
.Pp .Pp
Leave a blank line before the next group, the Leave a blank line before the next group, the
.Pa /usr .Pa /usr/include
include files, files,
which should be sorted alphabetically by name. which should be sorted alphabetically by name.
.Bd -literal .Bd -literal
#include <stdio.h> #include <stdio.h>
@ -247,6 +247,19 @@ is treated as
#endif /* !COMPAT_43*/ #endif /* !COMPAT_43*/
.Ed .Ed
.Pp .Pp
The project is slowly moving to use the
.St -isoC-99
unsigned integer identifiers of the form
.Ic uintXX_t
in preference to the older BSD-style integer identifiers of the form
.Ic u_intXX_t .
New code should use the former, and old code should be converted to
the new form if other major work is being done in that area and
there's no overriding reason to prefer the older BSD-style.
Like white-space commits, care should be taken in making
.Ic uintXX_t
only commits.
.Pp
Enumeration values are all uppercase. Enumeration values are all uppercase.
.Bd -literal .Bd -literal
enum enumtype { ONE, TWO } et; enum enumtype { ONE, TWO } et;