style revision 1.38
1/* $NetBSD: style,v 1.38 2006/11/02 22:44:41 christos 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.38 2006/11/02 22:44:41 christos 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 <inttypes.h> 88#include <stdio.h> 89#include <stdlib.h> 90 91/* 92 * Global pathnames are defined in /usr/include/paths.h. Pathnames local 93 * to the program go in pathnames.h in the local directory. 94 */ 95#include <paths.h> 96 97/* Then, there's a blank line, and the user include files. */ 98#include "pathnames.h" /* Local includes in double quotes. */ 99 100/* 101 * ANSI function declarations for private functions (i.e. functions not used 102 * elsewhere) and the main() function go at the top of the source module. 103 * Don't associate a name with the types. I.e. use: 104 * void function(int); 105 * Use your discretion on indenting between the return type and the name, and 106 * how to wrap a prototype too long for a single line. In the latter case, 107 * lining up under the initial left parenthesis may be more readable. 108 * In any case, consistency is important! 109 */ 110static char *function(int, int, float, int); 111static int dirinfo(const char *, struct stat *, struct dirent *, 112 struct statfs *, int *, char **[]); 113static void usage(void); 114int main(int, char *[]); 115 116/* 117 * Macros are capitalized, parenthesized, and should avoid side-effects. 118 * Spacing before and after the macro name may be any whitespace, though 119 * use of TABs should be consistent through a file. 120 * If they are an inline expansion of a function, the function is defined 121 * all in lowercase, the macro has the same name all in uppercase. 122 * If the macro is an expression, wrap the expression in parenthesis. 123 * If the macro is more than a single statement, use ``do { ... } while (0)'', 124 * so that a trailing semicolon works. Right-justify the backslashes; it 125 * makes it easier to read. The CONSTCOND comment is to satisfy lint(1). 126 */ 127#define MACRO(v, w, x, y) \ 128do { \ 129 v = (x) + (y); \ 130 w = (y) + 2; \ 131} while (/* CONSTCOND */ 0) 132 133#define DOUBLE(x) ((x) * 2) 134 135/* Enum types are capitalized. No comma on the last element. */ 136enum enumtype { 137 ONE, 138 TWO 139} et; 140 141/* 142 * When declaring variables in structures, declare them organized by use in 143 * a manner to attempt to minimize memory wastage because of compiler alignment 144 * issues, then by size, and then by alphabetical order. E.g, don't use 145 * ``int a; char *b; int c; char *d''; use ``int a; int b; char *c; char *d''. 146 * Each variable gets its own type and line, although an exception can be made 147 * when declaring bitfields (to clarify that it's part of the one bitfield). 148 * Note that the use of bitfields in general is discouraged. 149 * 150 * Major structures should be declared at the top of the file in which they 151 * are used, or in separate header files, if they are used in multiple 152 * source files. Use of the structures should be by separate declarations 153 * and should be "extern" if they are declared in a header file. 154 * 155 * It may be useful to use a meaningful prefix for each member name. 156 * E.g, for ``struct softc'' the prefix could be ``sc_''. 157 */ 158struct foo { 159 struct foo *next; /* List of active foo */ 160 struct mumble amumble; /* Comment for mumble */ 161 int bar; 162 unsigned int baz:1, /* Bitfield; line up entries if desired */ 163 fuz:5, 164 zap:2; 165 uint8_t flag; 166}; 167struct foo *foohead; /* Head of global foo list */ 168 169/* Make the structure name match the typedef. */ 170typedef struct BAR { 171 int level; 172} BAR; 173 174/* C99 uintN_t is preferred over u_intN_t. */ 175uint32_t zero; 176 177/* 178 * All major routines should have a comment briefly describing what 179 * they do. The comment before the "main" routine should describe 180 * what the program does. 181 */ 182int 183main(int argc, char *argv[]) 184{ 185 long num; 186 int ch; 187 char *ep; 188 189 /* 190 * At the start of main(), call setprogname() to set the program 191 * name. This does nothing on NetBSD, but increases portability 192 * to other systems. 193 */ 194 setprogname(argv[0]); 195 196 /* 197 * For consistency, getopt should be used to parse options. 198 * Options should be sorted in the getopt call and the switch 199 * statement, unless parts of the switch cascade. For the 200 * sorting order, see the usage() example below. Don't forget 201 * to add option descriptions to the usage and the manpage. 202 * Elements in a switch statement that cascade should have a 203 * FALLTHROUGH comment. Numerical arguments should be checked 204 * for accuracy. Code that cannot be reached should have a 205 * NOTREACHED comment. 206 */ 207 while ((ch = getopt(argc, argv, "abn")) != -1) { 208 switch (ch) { /* Indent the switch. */ 209 case 'a': /* Don't indent the case. */ 210 aflag = 1; 211 /* FALLTHROUGH */ 212 case 'b': 213 bflag = 1; 214 break; 215 case 'n': 216 errno = 0; 217 num = strtol(optarg, &ep, 10); 218 if (num <= 0 || *ep != '\0' || (errno == ERANGE && 219 (num == LONG_MAX || num == LONG_MIN)) ) 220 errx(1, "illegal number -- %s", optarg); 221 break; 222 case '?': 223 default: 224 usage(); 225 /* NOTREACHED */ 226 } 227 } 228 argc -= optind; 229 argv += optind; 230 231 /* 232 * Space after keywords (while, for, return, switch). No braces are 233 * required for control statements with only a single statement, 234 * unless it's a long statement. 235 * 236 * Forever loops are done with for's, not while's. 237 */ 238 for (p = buf; *p != '\0'; ++p) 239 continue; /* Explicit no-op */ 240 for (;;) 241 stmt; 242 243 /* 244 * Braces are required for control statements with a single statement 245 * that may expand to nothing. 246 */ 247#ifdef DEBUG_FOO 248#define DPRINTF(a) 249#else 250#define DPRINTF(a) printf a 251#endif 252 if (broken) { 253 DPRINTF(("broken is %d\n", broken)); 254 } 255 256 /* 257 * Parts of a for loop may be left empty. Don't put declarations 258 * inside blocks unless the routine is unusually complicated. 259 */ 260 for (; cnt < 15; cnt++) { 261 stmt1; 262 stmt2; 263 } 264 265 /* Second level indents are four spaces. */ 266 while (cnt < 20) 267 z = a + really + long + statement + that + needs + two lines + 268 gets + indented + four + spaces + on + the + second + 269 and + subsequent + lines; 270 271 /* 272 * Closing and opening braces go on the same line as the else. 273 * Don't add braces that aren't necessary except in cases where 274 * there are ambiguity or readability issues. 275 */ 276 if (test) { 277 /* 278 * I have a long comment here. 279 */ 280#ifdef zorro 281 z = 1; 282#else 283 b = 3; 284#endif 285 } else if (bar) { 286 stmt; 287 stmt; 288 } else 289 stmt; 290 291 /* No spaces after function names. */ 292 if ((result = function(a1, a2, a3, a4)) == NULL) 293 exit(1); 294 295 /* 296 * Unary operators don't require spaces, binary operators do. 297 * Don't excessively use parenthesis, but they should be used if 298 * statement is really confusing without them, such as: 299 * a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1; 300 */ 301 a = ((b->c[0] + ~d == (e || f)) || (g && h)) ? i : (j >> 1); 302 k = !(l & FLAGS); 303 304 /* 305 * Exits should be EXIT_SUCCESS on success, and EXIT_FAILURE on 306 * failure. Don't denote all the possible exit points, using the 307 * integers 1 through 127. Avoid obvious comments such as "Exit 308 * 0 on success.". Since main is a function that returns an int, 309 * prefer returning from it, than calling exit. 310 */ 311 return EXIT_SUCCESS; 312} 313 314/* 315 * The function type must be declared on a line by itself 316 * preceding the function. 317 */ 318static char * 319function(int a1, int a2, float fl, int a4) 320{ 321 /* 322 * When declaring variables in functions declare them sorted by size, 323 * then in alphabetical order; multiple ones per line are okay. 324 * Function prototypes should go in the include file "extern.h". 325 * If a line overflows reuse the type keyword. 326 * 327 * DO NOT initialize variables in the declarations. 328 */ 329 extern u_char one; 330 extern char two; 331 struct foo three, *four; 332 double five; 333 int *six, seven; 334 char *eight, *nine, ten, eleven, twelve, thirteen; 335 char fourteen, fifteen, sixteen; 336 337 /* 338 * Casts and sizeof's are not followed by a space. NULL is any 339 * pointer type, and doesn't need to be cast, so use NULL instead 340 * of (struct foo *)0 or (struct foo *)NULL. Also, test pointers 341 * against NULL. I.e. use: 342 * 343 * (p = f()) == NULL 344 * not: 345 * !(p = f()) 346 * 347 * Don't use `!' for tests unless it's a boolean. 348 * E.g. use "if (*p == '\0')", not "if (!*p)". 349 * 350 * Routines returning ``void *'' should not have their return 351 * values cast to more specific pointer types. 352 * 353 * Use err/warn(3), don't roll your own! 354 */ 355 if ((four = malloc(sizeof(struct foo))) == NULL) 356 err(1, NULL); 357 if ((six = (int *)overflow()) == NULL) 358 errx(1, "Number overflowed."); 359 360 /* No parentheses are needed around the return value. */ 361 return eight; 362} 363 364/* 365 * Use ANSI function declarations. ANSI function braces look like 366 * old-style (K&R) function braces. 367 * As per the wrapped prototypes, use your discretion on how to format 368 * the subsequent lines. 369 */ 370static int 371dirinfo(const char *p, struct stat *sb, struct dirent *de, struct statfs *sf, 372 int *rargc, char **rargv[]) 373{ /* Insert an empty line if the function has no local variables. */ 374 375 /* 376 * In system libraries, catch obviously invalid function arguments 377 * using _DIAGASSERT(3). 378 */ 379 _DIAGASSERT(p != NULL); 380 _DIAGASSERT(filedesc != -1); 381 382 if (stat(p, sb) < 0) 383 err(1, "Unable to stat %s", p); 384 385 /* 386 * To printf quantities that might be larger that "long", include 387 * <inttypes.h>, cast quantities to intmax_t or uintmax_t and use 388 * PRI?MAX constants, which may be found in <machine/int_fmtio.h>. 389 */ 390 (void)printf("The size of %s is %" PRIdMAX " (%#" PRIxMAX ")\n", p, 391 (intmax_t)sb->st_size, (uintmax_t)sb->st_size); 392 393 /* 394 * To printf quantities of known bit-width, use the corresponding 395 * defines (generally only done within NetBSD for quantities that 396 * exceed 32-bits). 397 */ 398 (void)printf("%s uses %" PRId64 " blocks and has flags %#" PRIx32 "\n", 399 p, sb->st_blocks, sb->st_flags); 400 401 /* 402 * There are similar constants that should be used with the *scanf(3) 403 * family of functions: SCN?MAX, SCN?64, etc. 404 */ 405} 406 407/* 408 * Functions that support variable numbers of arguments should look like this. 409 * (With the #include <stdarg.h> appearing at the top of the file with the 410 * other include files). 411 */ 412#include <stdarg.h> 413 414void 415vaf(const char *fmt, ...) 416{ 417 va_list ap; 418 419 va_start(ap, fmt); 420 STUFF; 421 va_end(ap); 422 /* No return needed for void functions. */ 423} 424 425static void 426usage(void) 427{ 428 429 /* 430 * Use printf(3), not fputs/puts/putchar/whatever, it's faster and 431 * usually cleaner, not to mention avoiding stupid bugs. 432 * Use snprintf(3) or strlcpy(3)/strlcat(3) instead of sprintf(3); 433 * again to avoid stupid bugs. 434 * 435 * Usage statements should look like the manual pages. 436 * Options w/o operands come first, in alphabetical order 437 * inside a single set of braces, upper case before lower case 438 * (AaBbCc...). Next are options with operands, in the same 439 * order, each in braces. Then required arguments in the 440 * order they are specified, followed by optional arguments in 441 * the order they are specified. A bar (`|') separates 442 * either/or options/arguments, and multiple options/arguments 443 * which are specified together are placed in a single set of 444 * braces. 445 * 446 * Use getprogname() instead of hardcoding the program name. 447 * 448 * "usage: f [-aDde] [-b b_arg] [-m m_arg] req1 req2 [opt1 [opt2]]\n" 449 * "usage: f [-a | -b] [-c [-de] [-n number]]\n" 450 */ 451 (void)fprintf(stderr, "usage: %s [-ab]\n", getprogname()); 452 exit(EXIT_FAILURE); 453} 454