The one problem that I have with C...

[Daniel Rudy]

....is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

 

[Al Bowers]

...is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

There is no problem.
Your reference should primarily be the International Standard,
ISO/IEC 9899. It is this Standard, and not a Unix manpage, that
defines the language. The Standard gives description to all its
library functions.

 

[dandelion]

"Daniel Rudy"
<5n6o7.8d9c0r1u2d3y4.5s6p7a8m9@0e1m2a3i4l5.6p7a8c9b0e1l2l3.4i5n6v7a8l9i0d1.2
n3e4t5> wrote in message

...is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

Then write one. Should not be *that* difficult. Merely a lot of work.

 

[Trent Buck]

Quoth Daniel Rudy on or about 2004-11-23:

The one problem that I have with C is that there is no single man page
that lists the stdlib functions that I can reference. I'm working in
a Unix environment.

Under Debian, the manpages-posix-dev package
http://packages.debian.org/unstable/doc/manpages-posix-dev

provides /usr/share/man/man7/stdlib.h.7posix.gz, which in the `SEE ALSO'
section lists (presumably) all the stdlib.h functions:

<limits.h> , <math.h> , <stddef.h> , <sys/types.h> ,
<sys/wait.h> , the System Interfaces volume of
IEEE Std 1003.1-2001, _Exit(), a64l(), abort(),
abs(), atexit(), atof(), atoi(), atol(), atoll(),
bsearch(), calloc(), div(), drand48(), erand48(),
exit(), free(), getenv(), getsubopt(), grantpt(),
initstate(), jrand48(), l64a(), labs(), lcong48(),
ldiv(), llabs(), lldiv(), lrand48(), malloc(),
mblen(), mbstowcs(), mbtowc(), mkstemp(), mrand48(),
nrand48(), posix_memalign(), ptsname(), putenv(),
qsort(), rand(), realloc(), realpath(), setstate(),
srand(), srand48(), srandom(), strtod(), strtof(),
strtol(), strtold(), strtoll(), strtoul(), str-
toull(), unlockpt(), wcstombs(), wctomb()

-trent

 

[Michael Mair]

...is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

This is not really a C problem. It is a problem of your not
having a good reference.
For the C99 stdlib:
http://www.dinkumware.com/refxc.html
or google for "N869" in order to find the last public draft
of the C99 standard.
POSIX or GNU extensions: OT here, but similarly easy to find/RTFM.

Apart from that: Get a good C Book.


-Michael

 

[Merrill & Michele]

"Michael Mair":

This is not really a C problem. It is a problem of your not
having a good reference.
For the C99 stdlib:
http://www.dinkumware.com/refxc.html
or google for "N869" in order to find the last public draft
of the C99 standard.
POSIX or GNU extensions: OT here, but similarly easy to find/RTFM.

Apart from that: Get a good C Book.

K&R2 admits that its list of functions is not complete but begins the
appendices with the proviso that the others are of limited utility or easily
derived from the others. MPJ

 

[Michael Mair]

K&R2 admits that its list of functions is not complete but begins the
appendices with the proviso that the others are of limited utility or easily
derived from the others. MPJ

And many other books do similarly; I really do not need to know
about wcstomb() if I am not dealing with wide or multibyte characters.
What pi..es most people is inventing useful new string or I/O functions
when they actually already exist ;-)
Happens mostly with library extensions, though, which are documented
somewhere.
However, as N869 is available, you can have a look at all of the
standard C library if you truly need it.
If you need the complete library reference regularly, have a look at
reference books.


Cheers
Michael

 

[Wolfgang Riedel]

...is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

lookup
http://petef.port5.com/c/portability.txt

for keywords, identifiers, macros and functions
defined in various standards.

Wolfgang

 

[Jack Klein]

Quoth Daniel Rudy on or about 2004-11-23:

Under Debian, the manpages-posix-dev package
http://packages.debian.org/unstable/doc/manpages-posix-dev

provides /usr/share/man/man7/stdlib.h.7posix.gz, which in the `SEE ALSO'
section lists (presumably) all the stdlib.h functions:

<limits.h> , <math.h> , <stddef.h> , <sys/types.h> ,
<sys/wait.h> , the System Interfaces volume of
IEEE Std 1003.1-2001, _Exit(), a64l(), abort(),
abs(), atexit(), atof(), atoi(), atol(), atoll(),
bsearch(), calloc(), div(), drand48(), erand48(),
exit(), free(), getenv(), getsubopt(), grantpt(),
initstate(), jrand48(), l64a(), labs(), lcong48(),
ldiv(), llabs(), lldiv(), lrand48(), malloc(),
mblen(), mbstowcs(), mbtowc(), mkstemp(), mrand48(),
nrand48(), posix_memalign(), ptsname(), putenv(),
qsort(), rand(), realloc(), realpath(), setstate(),
srand(), srand48(), srandom(), strtod(), strtof(),
strtol(), strtold(), strtoll(), strtoul(), str-
toull(), unlockpt(), wcstombs(), wctomb()

The problem here is that what you posted contains two non-standard
headers, a standard that is irrelevant here (only ANSI/ISO/IEC 9899
defines the C language), and a whole lot of functions that are not
part of the C standard library and that cannot be prototyped in a
standard conforming <stdlib.h>.

 

[Mark A. Odell]

Daniel Rudy
<5n6o7.8d9c0r1u2d3y4.5s6p7a8m9@0e1m2a3i4l5.6p7a8c9b0e1l2l3.4i5n6v7a8l9i0d1.
2n3e4t5> wrote in

...is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

Unix is platform, the C language is platform independent so why not look
for a platform independent summary of the C language? One like Eric Huss':

http://www.acm.uiuc.edu/webmonkeys/book/c_guide/

 

[Keith Thompson]

This is not really a C problem. It is a problem of your not
having a good reference.
For the C99 stdlib:
http://www.dinkumware.com/refxc.html
or google for "N869" in order to find the last public draft
of the C99 standard.

[...]

If you're serious enough about this to want a copy of N869, you should
seriously consider getting a copy of the actual C99 standard. ANSI
sells them in PDF format for $18 (but watch out for the license
agreement). Other national bodies probably also have PDF copies
available for more or less reasonable prices.

 

[William Ahern]

...is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

There is string(3) in my Linux environment. There may be similar ones I
haven't stumbled across. Of course, string(3) includes many GNU/glibc'isms.

 

[Randy Howard]

5n6o7.8d9c0r1u2d3y4.5s6p7a8m9@
0e1m2a3i4l5.6p7a8c9b0e1l2l3.4i5n6v7a8l9i0d1.2n3e4t5 says...

...is that there is no single man page that lists the stdlib functions
that I can reference. I'm working in a Unix environment.

How about something like this:
http://refcards.com/refcards/c/c-refcard-a4.pdf

 

[Daniel Rudy]

At about the time of 11/23/2004 7:39 AM, Michael Mair stated the following:

This is not really a C problem. It is a problem of your not
having a good reference.
For the C99 stdlib:
http://www.dinkumware.com/refxc.html
or google for "N869" in order to find the last public draft
of the C99 standard.
POSIX or GNU extensions: OT here, but similarly easy to find/RTFM.

Apart from that: Get a good C Book.

I have a couple of good C books, but they are geared to teaching the
language, not being used as a reference. Infact, I haven't seen any C
book that is not geared to learning the language, and I've seen a few.
The closest that I have found that has a library reference is C by
Discovery by L.S. Foster.

 

[Michael Mair]

At about the time of 11/23/2004 7:39 AM, Michael Mair stated the following:




I have a couple of good C books, but they are geared to teaching the
language, not being used as a reference. Infact, I haven't seen any C
book that is not geared to learning the language, and I've seen a few.
The closest that I have found that has a library reference is C by
Discovery by L.S. Foster.

Umh, that leaves me puzzled. I sometimes have a look into H. Herold's
"C Kompaktreferenz" which is a good book but unfortunately only
available in German.
I silently assumed that there is something comparable on the English
book market and would have thought that "Harbison & Steele, C: A
Reference Manual" does the job (I do not possess it so I cannot say
for sure).


Cheers
Michael

 

[Alan Balmer]

At about the time of 11/23/2004 7:39 AM, Michael Mair stated the following:


I have a couple of good C books, but they are geared to teaching the
language, not being used as a reference. Infact, I haven't seen any C
book that is not geared to learning the language, and I've seen a few.
The closest that I have found that has a library reference is C by
Discovery by L.S. Foster.

One of the usual recommendations is "C, A Reference Manual", by
Harbison and Steele. It covers C99 as well as previous versions.

 

[Dan Pop]

At about the time of 11/23/2004 7:39 AM, Michael Mair stated the following:


I have a couple of good C books, but they are geared to teaching the
language, not being used as a reference. Infact, I haven't seen any C
book that is not geared to learning the language, and I've seen a few.

Get K&R2. Appendix A contains a reference description of the language
and Appendix B a reference description of the standard library (with
insignificant omissions).

If interested in C99, you can get the standard itself in either electronic
or printed format for decent prices or the last public draft (which is
good enough for most intents and purposes) for free (google for n869).

Dan