public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.demon.co.uk>
To: danny <danny@3rdplanetsoftware.com>
Cc: gcc gnu <gcc-help@gcc.gnu.org>
Subject: Re: directories for newbies
Date: Sat, 10 Aug 2002 05:02:00 -0000	[thread overview]
Message-ID: <87n0ruly9x.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <3D3B5B72.B0CCF29B@3rdplanetsoftware.com>

On Mon, 22 Jul 2002, danny@3rdplanetsoftware.com moaned:
> Also what I'd really like is some online manual that grouped all the standard lib
> functions into different categories. Such as file management, networking, disk
> management, strings, etc. Anything like that around?

There's a manual/info book on the C library:

info libc

(which can also be typeset):

and at <http://www.opengroup.org/onlinepubs/007904975/nfindex.html> is
the Base Definitions for POSIX, which is the standard that you should
actually be following when writing portable code :)

By no means everything is in there (e.g. you won't find JPEG readers or
graphical stuff in there), but the core stuff is.

-- 
`There's something satisfying about killing JWZ over and over again.'
                                        -- 1i, personal communication

  parent reply	other threads:[~2002-08-10 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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

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=87n0ruly9x.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.demon.co.uk \
    --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).