|
Lines 470-485
Link Here
|
| 470 |
not fputs/puts/putchar/whatever; it's faster and usually cleaner, not |
470 |
not fputs/puts/putchar/whatever; it's faster and usually cleaner, not |
| 471 |
to mention avoiding stupid bugs. |
471 |
to mention avoiding stupid bugs. |
| 472 |
.Pp |
472 |
.Pp |
| 473 |
Usage statements should look like the manual pages synopsis. Options w/o |
473 |
Usage statements should look like the manual pages synopsis. Options |
| 474 |
operands come first, in alphabetical order inside a single set of |
474 |
without operands come first, in alphabetical order inside a single set of |
| 475 |
braces, followed by options with operands, in alphabetical order, |
475 |
square brackets, followed by options with operands, in alphabetical |
| 476 |
each in braces, followed by required arguments in the order they |
476 |
order, each in square brackets, followed by required arguments in the |
| 477 |
are specified, followed by optional arguments in the order they |
477 |
order they are specified, not in brackets, followed by optional |
| 478 |
are specified. A bar |
478 |
arguments in the order they are specified, in square brackets. A bar |
| 479 |
.Pq Sq \&| |
479 |
.Pq Sq \&| |
| 480 |
separates either-or options/arguments, |
480 |
separates either-or options/arguments, |
| 481 |
and multiple options/arguments which are specified together are |
481 |
and multiple options/arguments which are specified together are |
| 482 |
placed in a single set of braces. |
482 |
placed in a single set of square brackets. |
| 483 |
.Pp |
483 |
.Pp |
| 484 |
.Bd -ragged -offset 0.3i |
484 |
.Bd -ragged -offset 0.3i |
| 485 |
"usage: f [-aDde] [-b b_arg] [-m m_arg] req1 req2 [opt1 [opt2]]\en" |
485 |
"usage: f [-aDde] [-b b_arg] [-m m_arg] req1 req2 [opt1 [opt2]]\en" |