| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
termination with '\0') vs. null termination.
Input from krw@, jaredy@, jmc@. OK deraadt@
|
| |
|
|
| |
rescinded 22 July 1999. Proofed by myself and Theo.
|
| |
|
|
|
| |
- section reorder
- merge COMPATIBILITY
|
| | |
|
| | |
|
| |
|
|
| |
getpass(3) is now implemented in terms of readpasasphrase(3).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- only use the .Dv NULL form when referring explicitly to a function
argument or return value
- otherwise, use these forms:
o non-null
o null-terminated (hyphenated form for predicate adjective)
o else, null terminated, or null terminate, whichever the case
o null pointer, null byte, null string, etc.
- may use NUL to refer to an ASCII NUL, but it doesn't need a .Tn macro
In general, capitalizing the word "null" everywhere is unnecessary and makes
the man pages harder to read. The above is consistent with popular programming
texts (i.e., K&R, Stevens).
|
| |
|
|
|
| |
between NUL and NULL, i.e., don't use the .Dv (defined variable) macro when
referring to an ASCII NUL
|
| | |
|
| | |
|
| |
|
|
| |
Make sure everything uses {SYS,}LIBC_SCCS properly
|
| |
|
jmc
cloder
millert
aaron
deraadt
tholo