🚀 go-pugleaf

In article <4gl74s$sga@meaddata.lexis-nexis.com> christw@meaddata.com
(Christopher C. Wood) writes:

> In article <9lspg3xn54.fsf@marks.jyacc.com>, jtrigg@marks.jyacc.com
> (Jim Trigg) writes:
> |> In article <4g2i5q$dj7@meaddata.lexis-nexis.com> christw@meaddata.com
> |> (Christopher C. Wood) writes:

> |> > Look, I've shown a bunch of things with this thread.  _none_ of the
> |> > respondants pointed out that there is a "standard" library call to do
> |> > this: itoa().  As documented in K&R (I'd cite page numbers, but I
> |> > don't have it at this desk.)  As _assumed_ in Stroustrup, 2nd ed.
> |> > Guess what?  This "standard" library call, in actual practice, isn't
> |> > standard.  Each platform has its own version.  One version is even
> |> > wrong in the manufacturers on-line documentation.  Is this a fault
> |> > with the "Standard" for C or C++ libraries?  Or just the
> |> > implementations.  You tell me.

> |> The "documentation" in K&R is on page 64 (2nd ed.), where they show
> |> how to write it.  They never claim it is part of any library.  The
> |> code that they provide is system-independent.  (It does depend on one
> |> function that they wrote earlier in the book, reverse() which reverses
> |> a string in place.)  It is not even library-dependent.

> Right.

> |> Also, in regard to your claim that linking in sprintf links in the
> |> full stdio library, well, atoi (and relatives) links in the full
> |> stdlib library.  Unless, of course, you have an intelligent linker
> |> which only brings in symbols that are actually referenced.

> stdlib is almost always needed, for geteuid(), exit(), getenv(), and
> getopt().  Most unix programs use accept command line arguments or
> environment variables, and really ought to use standardized functions
> to access them.

First, geteuid() and getenv() are not part of stdlib (according to
ANSI/ISO).  They may be part of POSIX, I'm not sure.

Second, stdio is almost always needed as well.  A program which does no 
input and no output is practically useless.  Note that stdio handles ALL
i/o requests including both console (stdin/stdout) and file i/o.

Just a Thought,
Jim Trigg