public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrea 'Fyre Wyzard' Bocci" <fwyzard@inwind.it>
To: danny <danny@3rdplanetsoftware.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: directories for newbies
Date: Mon, 22 Jul 2002 02:39:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20020722105924.00b23ff0@popmail.inwind.it> (raw)
In-Reply-To: <3D3BBB6D.7BE2639E@3rdplanetsoftware.com>

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

Hi Danny,

>Thanks for the stat function. U referred to section 1 & 2. What book is
>this?

It's not a book, it's the man(ual) pages you get on most Unix system.

To get the documentation for a program or library function, if the people 
who provided those also provided the man pages, you can usually simply type 
from the prompt

man name_of_the_function

The man pages are divided in sections, one for user programs, one for 
system programs, one for C library routines, one for games, etc...
If a keyword is used in more than one section, you can chose which section 
to search specifying te number on the command line, like

man 2 name_of_the_function

Hope this helps,
fwyzard

[-- Attachment #2: Type: application/pgp-signature, Size: 222 bytes --]

  reply	other threads:[~2002-07-22  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <616BE6A276E3714788D2AC35C40CD18D71B3A6@whale.softwire.co.uk>
2002-07-22  0:57 ` Rupert Wood
2002-07-22  1:20   ` danny
2002-07-22  2:39     ` Andrea 'Fyre Wyzard' Bocci [this message]
2002-07-21  4:11 danny
     [not found] ` <20020721164957.GA16367@satyr.sylvan.com>
2002-07-21 13:00   ` danny
     [not found]     ` <20020721203537.GA20277@satyr.sylvan.com>
2002-07-21 18:41       ` danny
2002-07-21 20:15         ` H.S.Rai
2002-07-21 20:41           ` danny
2002-07-22  6:32         ` Ish Rattan
2002-07-22  6:37           ` Nelson Guedes Paulo Junior
2002-08-10  5:02         ` Nix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.2.20020722105924.00b23ff0@popmail.inwind.it \
    --to=fwyzard@inwind.it \
    --cc=danny@3rdplanetsoftware.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).