summaryrefslogtreecommitdiffstats
path: root/share/man/man9/style.9
Commit message (Collapse)AuthorAgeFilesLines
* Boot out <sysexits.h> once and for all.des2008-12-171-7/+4
| | | | MFC after: 1 week
* Revert r184509: don't encourage the use of sysexits.h with err() andrwatson2008-11-271-2/+2
| | | | | | | errx(),, as there seems to be a general preference against this practice. Suggested by: bde, des, jhb
* In style(9) examples of err() and errx(), use sysexits(3) errors ratherrwatson2008-10-311-2/+2
| | | | | | | than returning 1. Submitted by: Bruce Cran <bruce at cran dot org dot uk> MFC after: 3 days
* Back-out my previous change. See the thread atdanger2008-07-101-3/+6
| | | | http://lists.freebsd.org/pipermail/cvs-all/2008-July/263779.html
* - nested functions are a GCC extensions and should not be useddanger2008-07-091-6/+3
| | | | | Submitted by: gahr MFC after: 3 days
* Add to the history section.obrien2008-01-271-0/+4
|
* "redacted" replaced for clarity.grog2008-01-051-1/+1
|
* Line break before "All rights reserved" in the license example.joel2007-01-281-1/+2
| | | | Reveiwed by: bde, rwatson
* Clarify case body indention.obrien2006-11-261-1/+1
|
* Use 'manual page' instead of 'man page' for consistency.hmp2005-06-281-1/+1
| | | | Approved by: re (hrs)
* Clarify the header.obrien2005-05-171-1/+1
|
* Recover the original Berkeley RCS id, and fix the description ofru2005-05-171-2/+3
| | | | format for source files when it comes to $FreeBSD$.
* Remove a duplicate 'comment' to fix the syntax of a sentence.keramida2005-05-171-1/+1
|
* Fixed the misplaced $FreeBSD$.ru2005-02-091-0/+2
|
* Add a few colons.ru2005-01-261-3/+3
| | | | Submitted by: Joel Dahl
* Nits.ru2005-01-131-1/+1
|
* Fix typos and add .Pp after the end of a display to separate thekeramida2005-01-091-2/+3
| | | | displayed text from the paragraph right after it.
* Clarify /*- convention.imp2005-01-051-3/+13
|
* A large majority of the source files in the tree start their licenseimp2005-01-051-0/+10
| | | | | | | | and copyright statements in a comment that begins with /*-. Document this tradition. A strict adherence to this rule will help resellers that wish to publish all copyright notices, generated automatically from the tree. There are too many variant licenses to do it purely by more complicated pattern matching.
* Clarify the structure element size ordering.dds2004-12-021-1/+1
| | | | Obtained from: OpenBSD style.9 1.38
* Mechanically kill hard sentence breaks and double whitespaces.ru2004-07-031-2/+2
|
* Fixed a style bug in the previous commit.bde2004-06-261-0/+1
|
* Embellish the getopt(3) example with mixed case.obrien2004-06-261-2/+4
| | | | Reviewed by: bde
* Assorted markup, spelling, and grammar fixes.ru2004-06-161-8/+11
|
* What world have we come to when even style(9) isn't unfailable:le2004-06-131-1/+1
| | | | correct style nit in an example.
* Better English usage.fanf2003-11-121-1/+1
| | | | Submitted by: wollman
* Clarify the rule about structure typedefs being discouraged, followingfanf2003-11-101-3/+12
| | | | a discussion on src-committers.
* Two minor fixes:imp2003-09-271-2/+15
| | | | | | | | | | 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.
* mdoc(7): Use the new feature of the .In macro.ru2003-09-081-5/+5
|
* Xref sytle.Makefile(5).trhodes2003-04-261-1/+2
| | | | PR: 51183
* Revert previous commit which accidentally snuck in with some unrelatedjhb2003-03-251-1/+1
| | | | | | changes. Reported by: bde
* Remove obsolete at_fork() and at_exit() manpages. Curiously, at_exec()jhb2003-03-251-1/+1
| | | | | | didn't have a manpage. Reminded by: ru
* english(4) police.schweikh2002-12-271-1/+1
|
* mdoc(7) police: scheduled sweep.ru2002-11-291-3/+8
| | | | Approved by: re
* mdoc(7) police:ru2002-11-261-1/+2
| | | | | | | | Revert to using the .Tn POSIX and .Tn ANSI instead of \*[Px] and \*[Ai] strings; using these strings is unsafe in troff mode, as they include a change in a font size. Approved by: re
* Further clarifications of the #ifdef/#if/#elif/#endif style information,rwatson2002-11-011-13/+16
| | | | | | | | | | largely submitted by bde. Return our exemption of the #ifdef lint comments since the exemption is intended to handle a particularly common current case without mandating change. Improve language and spelling, and slightly clarify the notions associated specifically with #elif. Obtained from: bde
* Clarify style(9) WRT comments following #endif, #else.rwatson2002-10-281-1/+63
| | | | | | | | | | | The closing comment is required only for long conditionally defined code sections, with the exception of lint cases. Attempt to document also the logic for using '!' before the SOMETIMESSOMETHGINGHERE. The goal of these comments is to make complex cases more comprehensible, not to require them in all cases. The rules here are derived from behavior used in 90+% of the kernel source code. Reviewed by and discussed with: jhb, bde, mike
* Add a paragraph which should clarify the separation of asterisksrobert2002-09-101-0/+6
| | | | | | | | | | | | | | | | | | and adjacent tokens in declarations. The added text was originally a single sentence I wrote and which was heavily modified and extended by Bruce Evans. This clarification attempt originates from differing usage of the 'restrict' type-qualifier. Although various documents documents dicussing the C Programming Language put a space between an asterisk and the 'restrict' keyword, including the C99 standard (at least the n869.txt draft) and other ISO/IEC JTC1/SC22/WG14 documents, the IEEE Std 1003.1-2001 document does not separate them. Discussed with: bde Requested by: tjr Separation using a single space also liked by: mike
* Remove a sentence about wrapping macro definitions in bare braces,fanf2002-09-101-6/+5
| | | | | | | which became wrong after using do { } while (0) became recommended. Move the definition of what braces are to their new first occurrence. Reviewed by: bde
* Expand a contraction in the text of style(9) for consistency.robert2002-09-061-1/+1
| | | | | Do not touch contractions in comments of code examples because their usage seems to be justified by space contraints.
* Suggest that function prototypes in kernel headers be alphabetical,imp2002-08-211-0/+3
| | | | | | | unless there's a compelling reason to deviate. Submitted by: Don Lewis Suggestion not objected to by: developers@
* mdoc(7) police: nit.ru2002-08-131-1/+1
|
* Clarify the sizeof(var) rule. This is the result of the consensus inimp2002-07-251-0/+5
| | | | | | arch@ between myself, bde and markm. I kept the parts that all of us agreed to, and omitted some more extensive text that I'd originally wanted.
* Clarify version 1.68 to more accurately describe the intent of the change toimp2002-07-021-1/+2
| | | | | | | try to avoid ambiguous cases in the future. Wording approved by: julian (early draft), grog, rwatson, wes and maybe other members of core I'm forgetting.
* Correct two syntax mistakes.asmodai2002-04-141-3/+3
| | | | Fix overflowing right side, so that the && operator fits on the same line.
* Remove extraneous newline.asmodai2002-04-141-1/+0
|
* 'char *' can be a large entity now (on 64-bit platforms). Thus move it upobrien2002-03-241-1/+1
| | | | to make the example match the text requirements.
* mdoc(7) police: markup nit.ru2002-03-181-1/+2
|
* The do { } while (0) macro example was missing a space after the 'e'.imp2002-02-271-1/+1
|
* Note new status of __P. Don't use it.imp2002-02-011-9/+2
| | | | Reviewed by: arch@, mckusick (in principle)
OpenPOWER on IntegriCloud