lint: to -p or not to -p

[Henry Spencer]

Users of V7 lint(1) should know that the -p option is a mixed blessing.
While it adds much more stringent portability checking, it also does
less checking in one important respect than lint used without -p.  The
problem is that lint -p uses its own lint-library file, but does not
complain if it runs across functions not mentioned in said library.
The Unix read() call, for example, is not in the -p library.  This is
reasonable enough, since said call is portable only to other Unixes,
but its absence means that botches in (say) the types of its parameters
do not get reported.  The best procedure is to lint both with and without
-p for maximum checking.