Age | Commit message (Collapse) | Author |
|
Instead, just document what POSIX requires.
Reminded of the problem by joachimschipper dot nl,
Feedback from matthew@, krw@, deraadt@, and ok deraadt@.
|
|
|
|
termination with '\0') vs. null termination.
Input from krw@, jaredy@, jmc@. OK deraadt@
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
not "Month, ##, ####"
|
|
|
|
- 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).
|
|
pjanzen@
|
|
between NUL and NULL, i.e., don't use the .Dv (defined variable) macro when
referring to an ASCII NUL
|
|
|
|
grep '"' | cut -d':' -f1`; do
sed -e '/^.Dd /s/"//g' -e '/^.Dd /s/\(^.Dd [A-Za-z]*\) \(.*\)$/\1, \2/' <$i >x
cat x > $i
done
|
|
Make sure everything uses {SYS,}LIBC_SCCS properly
|
|
|