Navigating C++ 3103
Well, there happens traditionally to be a chapter of the man pages devoted to C library calls. Hey, two chapters. Maybe more. Unix is written in C, after all, and extending it (writting applications and system softare) required some documentation and it came with the system as the man pages.
But ... there is no chapter for pascal library calls (are there any?). Nor java calls. Nor ML library calls, nor ... well, I don't know if APL could ever have a library :).
So I don't see why you think that an "arbitrary" language should come with a chapter of the manpages all writetn out, one page per standard language library call. Perhaps you don't. Perhaps yu think C++ is anything but arbitrary, and that it deserves its place at the center of the pantheon of languages!
As it happens, some languages do have manpages per call (perl springs to mind, as does tk-tcl, but I always jetison that mess. They have to be joking).
It does. You are confused by language. % man -k perl Bundle::LWP (3pm) - A bundle to install all libwww-perl related modules Digest::MD2 (3pm) - Perl interface to the MD2 Algorithm Digest::MD5 (3pm...
Hi, I'm using Slackware 10.1, kernel 2.6.7 on a DELL Inspiron 8600 with a winmodem, chipset Intel 82801DB ICH4, manufacturer...
But C++ has nothing intrinsically to do with unix in the way that C does. It runs fine on VMS, and even msdos. Ditto pascal. Ditto java. That unix is written in C explains why the C library calls came initially documented with the unix system. Nothing more should be expected.
Peter
Linux groups from Newsgroups