On Wed, 9 Jan 2008 11:19:46 +0800 "Michael Yang" <[EMAIL PROTECTED]> wrote:
> OS's API is what I would need mainly. > > manpages are good, but it would be better if there is a well organized > documents. > > For example, when I want to investigate some issues on regular expression, > in Perl, I can use "perldoc -q reg", in Java, I can search the class name > with the keyword, in Qt, I can check the classes related to regular > expression within "assistant" doc. > > With manual pages, it seems that I have to know the exact name which exists > in manuals, like "man std::iostream", to get the related manuals, but will > not if the name is wrong. > There is apropos which helps, and google of course. > -M. > > On Jan 8, 2008 11:17 PM, Magnus Therning <[EMAIL PROTECTED]> wrote: > > > On 1/8/08, Michael Yang <[EMAIL PROTECTED]> wrote: > > > > > Hi all: > > > > > > I'm starting the C++ Developer work on linux, no GUI app involved. > > > > > > Could you tell me what the tools you are working with? > > > > > > I'm trying with g++ and vim. Is there a package containing the help doc > > > for the library API, like the MSDN on Windows. > > > > > > Well, it all depends on what libraries/APIs you are programming against. > > The OS's API is generally documented in manpages (manpages-dev). Many > > libraries are accompanied by *-doc packages letting you isntall the > > documentation you need locally. Some things (mostly tools in my experience) > > is documented in info format (IIRC it's the official documentation format > > for GNU packages) and if you search online you can usually find most of that > > for perusing in a web browser too. > > > > So, you might say it's a bit less organised in than in the Windows world, > > but bear in mind that if you use non-Microsoft APIs you end up with a > > similarly unstructured set of documentation. > > > > /M > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
