For Programmers, Not Users 53/lib/cpp
/lib/
/usr/local/lib/
/cpp
next%Hmm... Excuse us for one second:
% ls /lib
cpp* gcrt0.o libsys_s.a
cpp-precomp* i386/ m68k/
crt0.o libsys_p.a posixcrt0.o
next% strings /lib/cpp-precomp | grep /
/*%s*/
//%s
/usr/local/include
/NextDeveloper/Headers
/NextDeveloper/Headers/ansi
/NextDeveloper/Headers/bsd
/LocalDeveloper/Headers
/LocalDeveloper/Headers/ansi
/LocalDeveloper/Headers/bsd
/NextDeveloper/2.0CompatibleHeaders
%s/%s
/lib/%s/specs
next%Silly us. NEXTSTEP’s /lib/cpp calls /lib/cpp-precomp. You won’t find
that documented on the man page either:
next% man cpp-precomp
No manual entry for cpp-precomp.For Programmers, Not Users
Don’t blame Ken and Dennis for the sorry state of Unix documentation
today. When the documentation framework was laid down, standards for
documentation that were prevalent in the rest of the computer industry
didn’t apply. Traps, bugs, and potential pitfalls were documented more fre-
quently than features because the people who read the documents were, for
the most part, the people who were developing the system. For many of
these developers, the real function of Unix’s “man” pages was as a place to
collect bug reports. The notion that Unix documentation is for naive, or
merely inexpert users, programmers, and system administrators is a recent