style revision 1.28 1 /* $NetBSD: style,v 1.28 2005/01/03 13:59:40 wiz Exp $ */
2
3 /*
4 * The revision control tag appears first, with a blank line after it.
5 * Copyright text appears after the revision control tag.
6 */
7
8 /*
9 * The NetBSD source code style guide.
10 * (Previously known as KNF - Kernel Normal Form).
11 *
12 * from: @(#)style 1.12 (Berkeley) 3/18/94
13 */
14 /*
15 * An indent(1) profile approximating the style outlined in
16 * this document lives in /usr/share/misc/indent.pro. It is a
17 * useful tool to assist in converting code to KNF, but indent(1)
18 * output generated using this profile must not be considered to
19 * be an authoritative reference.
20 */
21
22 /*
23 * Source code revision control identifiers appear after any copyright
24 * text. Use the appropriate macros from <sys/cdefs.h>. Usually only one
25 * source file per program contains a __COPYRIGHT() section.
26 * Historic Berkeley code may also have an __SCCSID() section.
27 * Only one instance of each of these macros can occur in each file.
28 */
29 #include <sys/cdefs.h>
30 __COPYRIGHT("@(#) Copyright (c) 2000\n\
31 The NetBSD Foundation, inc. All rights reserved.\n");
32 __RCSID("$NetBSD: style,v 1.28 2005/01/03 13:59:40 wiz Exp $");
33
34 /*
35 * VERY important single-line comments look like this.
36 */
37
38 /* Most single-line comments look like this. */
39
40 /*
41 * Multi-line comments look like this. Make them real sentences. Fill
42 * them so they look like real paragraphs.
43 */
44
45 /*
46 * Attempt to wrap lines longer than 80 characters appropriately.
47 * Refer to the examples below for more information.
48 */
49
50 /*
51 * EXAMPLE HEADER FILE:
52 *
53 * A header file should protect itself against multiple inclusion.
54 * E.g, <sys/socket.h> would contain something like:
55 */
56 #ifndef _SYS_SOCKET_H_
57 #define _SYS_SOCKET_H_
58 /*
59 * Contents of #include file go between the #ifndef and the #endif at the end.
60 */
61 #endif /* !_SYS_SOCKET_H_ */
62 /*
63 * END OF EXAMPLE HEADER FILE.
64 */
65
66 /*
67 * Kernel include files come first.
68 */
69 #include <sys/types.h> /* Non-local includes in brackets. */
70
71 /*
72 * If it's a network program, put the network include files next.
73 * Group the includes files by subdirectory.
74 */
75 #include <net/if.h>
76 #include <net/if_dl.h>
77 #include <net/route.h>
78 #include <netinet/in.h>
79 #include <protocols/rwhod.h>
80
81 /*
82 * Then there's a blank line, followed by the /usr include files.
83 * The /usr include files should be sorted!
84 */
85 #include <assert.h>
86 #include <errno.h>
87 #include <stdio.h>
88 #include <stdlib.h>
89
90 /*
91 * Global pathnames are defined in /usr/include/paths.h. Pathnames local
92 * to the program go in pathnames.h in the local directory.
93 */
94 #include <paths.h>
95
96 /* Then, there's a blank line, and the user include files. */
97 #include "pathnames.h" /* Local includes in double quotes. */
98
99 /*
100 * ANSI function declarations for private functions (i.e. functions not used
101 * elsewhere) and the main() function go at the top of the source module.
102 * Don't associate a name with the types. I.e. use:
103 * void function(int);
104 * Use your discretion on indenting between the return type and the name, and
105 * how to wrap a prototype too long for a single line. In the latter case,
106 * lining up under the initial left parenthesis may be more readable.
107 * In any case, consistency is important!
108 */
109 static char *function(int, int, float, int);
110 static int dirinfo(const char *, struct stat *, struct dirent *,
111 struct statfs *, int *, char **[]);
112 static void usage(void);
113 int main(int, char *[]);
114
115 /*
116 * Macros are capitalized, parenthesized, and should avoid side-effects.
117 * Spacing before and after the macro name may be any whitespace, though
118 * use of TABs should be consistent through a file.
119 * If they are an inline expansion of a function, the function is defined
120 * all in lowercase, the macro has the same name all in uppercase.
121 * If the macro is an expression, wrap the expression in parenthesis.
122 * If the macro is more than a single statement, use ``do { ... } while (0)'',
123 * so that a trailing semicolon works. Right-justify the backslashes; it
124 * makes it easier to read. The CONSTCOND comment is to satisfy lint(1).
125 */
126 #define MACRO(v, w, x, y) \
127 do { \
128 v = (x) + (y); \
129 w = (y) + 2; \
130 } while (/* CONSTCOND */ 0)
131
132 #define DOUBLE(x) ((x) * 2)
133
134 /* Enum types are capitalized. No comma on the last element. */
135 enum enumtype {
136 ONE,
137 TWO
138 } et;
139
140 /*
141 * When declaring variables in structures, declare them organized by use in
142 * a manner to attempt to minimize memory wastage because of compiler alignment
143 * issues, then by size, and then by alphabetical order. E.g, don't use
144 * ``int a; char *b; int c; char *d''; use ``int a; int b; char *c; char *d''.
145 * Each variable gets its own type and line, although an exception can be made
146 * when declaring bitfields (to clarify that it's part of the one bitfield).
147 * Note that the use of bitfields in general is discouraged.
148 *
149 * Major structures should be declared at the top of the file in which they
150 * are used, or in separate header files, if they are used in multiple
151 * source files. Use of the structures should be by separate declarations
152 * and should be "extern" if they are declared in a header file.
153 *
154 * It may be useful to use a meaningful prefix for each member name.
155 * E.g, for ``struct softc'' the prefix could be ``sc_''.
156 */
157 struct foo {
158 struct foo *next; /* List of active foo */
159 struct mumble amumble; /* Comment for mumble */
160 int bar;
161 unsigned int baz:1, /* Bitfield; line up entries if desired */
162 fuz:5,
163 zap:2;
164 uint8_t flag;
165 };
166 struct foo *foohead; /* Head of global foo list */
167
168 /* Make the structure name match the typedef. */
169 typedef struct BAR {
170 int level;
171 } BAR;
172
173 /*
174 * All major routines should have a comment briefly describing what
175 * they do. The comment before the "main" routine should describe
176 * what the program does.
177 */
178 int
179 main(int argc, char *argv[])
180 {
181 long num;
182 int ch;
183 char *ep;
184
185 /*
186 * At the start of main(), call setprogname() to set the program
187 * name. This does nothing on NetBSD, but increases portability
188 * to other systems.
189 */
190 setprogname(argv[0]);
191
192 /*
193 * For consistency, getopt should be used to parse options. Options
194 * should be sorted in the getopt call and the switch statement, unless
195 * parts of the switch cascade. Elements in a switch statement that
196 * cascade should have a FALLTHROUGH comment. Numerical arguments
197 * should be checked for accuracy. Code that cannot be reached should
198 * have a NOTREACHED comment.
199 */
200 while ((ch = getopt(argc, argv, "abn")) != -1) {
201 switch (ch) { /* Indent the switch. */
202 case 'a': /* Don't indent the case. */
203 aflag = 1;
204 /* FALLTHROUGH */
205 case 'b':
206 bflag = 1;
207 break;
208 case 'n':
209 errno = 0;
210 num = strtol(optarg, &ep, 10);
211 if (num <= 0 || *ep != '\0' || (errno == ERANGE &&
212 (num == LONG_MAX || num == LONG_MIN)) )
213 errx(1, "illegal number -- %s", optarg);
214 break;
215 case '?':
216 default:
217 usage();
218 /* NOTREACHED */
219 }
220 }
221 argc -= optind;
222 argv += optind;
223
224 /*
225 * Space after keywords (while, for, return, switch). No braces are
226 * used for control statements with zero or only a single statement,
227 * unless it's a long statement.
228 *
229 * Forever loops are done with for's, not while's.
230 */
231 for (p = buf; *p != '\0'; ++p)
232 continue; /* Explicit no-op */
233 for (;;)
234 stmt;
235
236 /*
237 * Parts of a for loop may be left empty. Don't put declarations
238 * inside blocks unless the routine is unusually complicated.
239 */
240 for (; cnt < 15; cnt++) {
241 stmt1;
242 stmt2;
243 }
244
245 /* Second level indents are four spaces. */
246 while (cnt < 20)
247 z = a + really + long + statement + that + needs + two lines +
248 gets + indented + four + spaces + on + the + second +
249 and + subsequent + lines;
250
251 /*
252 * Closing and opening braces go on the same line as the else.
253 * Don't add braces that aren't necessary except in cases where
254 * there are ambiguity or readability issues.
255 */
256 if (test) {
257 /*
258 * I have a long comment here.
259 */
260 #ifdef zorro
261 z = 1;
262 #else
263 b = 3;
264 #endif
265 } else if (bar) {
266 stmt;
267 stmt;
268 } else
269 stmt;
270
271 /* No spaces after function names. */
272 if ((result = function(a1, a2, a3, a4)) == NULL)
273 exit(1);
274
275 /*
276 * Unary operators don't require spaces, binary operators do.
277 * Don't excessively use parenthesis, but they should be used if
278 * statement is really confusing without them, such as:
279 * a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
280 */
281 a = ((b->c[0] + ~d == (e || f)) || (g && h)) ? i : (j >> 1);
282 k = !(l & FLAGS);
283
284 /*
285 * Exits should be EXIT_SUCCESS on success, and EXIT_FAILURE on
286 * failure. Don't denote all the possible exit points, using the
287 * integers 1 through 300. Avoid obvious comments such as "Exit
288 * 0 on success."
289 */
290 exit(EXIT_SUCCESS);
291 }
292
293 /*
294 * The function type must be declared on a line by itself
295 * preceding the function.
296 */
297 static char *
298 function(int a1, int a2, float fl, int a4)
299 {
300 /*
301 * When declaring variables in functions declare them sorted by size,
302 * then in alphabetical order; multiple ones per line are okay.
303 * Function prototypes should go in the include file "extern.h".
304 * If a line overflows reuse the type keyword.
305 *
306 * DO NOT initialize variables in the declarations.
307 */
308 extern uint32_t zero;
309 extern u_char one;
310 extern char two;
311 struct foo three, *four;
312 double five;
313 int *six, seven;
314 char *eight, *nine, ten, eleven, twelve, thirteen;
315 char fourteen, fifteen, sixteen;
316
317 /*
318 * Casts and sizeof's are not followed by a space. NULL is any
319 * pointer type, and doesn't need to be cast, so use NULL instead
320 * of (struct foo *)0 or (struct foo *)NULL. Also, test pointers
321 * against NULL. I.e. use:
322 *
323 * (p = f()) == NULL
324 * not:
325 * !(p = f())
326 *
327 * Don't use `!' for tests unless it's a boolean.
328 * E.g. use "if (*p == '\0')", not "if (!*p)".
329 *
330 * Routines returning void * should not have their return values cast
331 * to any pointer type.
332 *
333 * Use err/warn(3), don't roll your own!
334 */
335 if ((four = malloc(sizeof(struct foo))) == NULL)
336 err(1, NULL);
337 if ((six = (int *)overflow()) == NULL)
338 errx(1, "Number overflowed.");
339
340 /* No parentheses are needed around the return value. */
341 return eight;
342 }
343
344 /*
345 * Use ANSI function declarations. ANSI function braces look like
346 * old-style (K&R) function braces.
347 * As per the wrapped prototypes, use your discretion on how to format
348 * the subsequent lines.
349 */
350 static int
351 dirinfo(const char *p, struct stat *sb, struct dirent *de, struct statfs *sf,
352 int *rargc, char **rargv[])
353 { /* Insert an empty line if the function has no local variables. */
354
355 /*
356 * In system libraries, catch obviously invalid function arguments
357 * using _DIAGASSERT(3).
358 */
359 _DIAGASSERT(p != NULL);
360 _DIAGASSERT(filedesc != -1);
361
362 if (stat(p, sb) < 0)
363 err(1, "Unable to stat %s", p);
364
365 /*
366 * To printf 64 bit quantities, use %ll and cast to (long long).
367 */
368 printf("The size of %s is %lld\n", p, (long long)sb->st_size);
369 }
370
371 /*
372 * Functions that support variable numbers of arguments should look like this.
373 * (With the #include <stdarg.h> appearing at the top of the file with the
374 * other include files).
375 */
376 #include <stdarg.h>
377
378 void
379 vaf(const char *fmt, ...)
380 {
381 va_list ap;
382
383 va_start(ap, fmt);
384 STUFF;
385 va_end(ap);
386 /* No return needed for void functions. */
387 }
388
389 static void
390 usage(void)
391 {
392
393 /*
394 * Use printf(3), not fputs/puts/putchar/whatever, it's faster and
395 * usually cleaner, not to mention avoiding stupid bugs.
396 * Use snprintf(3) or strlcpy(3)/strlcat(3) instead of sprintf(3);
397 * again to avoid stupid bugs.
398 *
399 * Usage statements should look like the manual pages. Options w/o
400 * operands come first, in alphabetical order inside a single set of
401 * braces. Followed by options with operands, in alphabetical order,
402 * each in braces. Followed by required arguments in the order they
403 * are specified, followed by optional arguments in the order they
404 * are specified. A bar (`|') separates either/or options/arguments,
405 * and multiple options/arguments which are specified together are
406 * placed in a single set of braces.
407 *
408 * Use getprogname() instead of hardcoding the program name.
409 *
410 * "usage: f [-ade] [-b b_arg] [-m m_arg] req1 req2 [opt1 [opt2]]\n"
411 * "usage: f [-a | -b] [-c [-de] [-n number]]\n"
412 */
413 (void)fprintf(stderr, "usage: %s [-ab]\n", getprogname());
414 exit(1);
415 }
416