🚀 go-pugleaf

In article <kevinbDMyx3u.5C0@netcom.com>, kevin@frobozz.sccsi.com (Kevin Brown) writes:
|> In article <4g2i5q$dj7@meaddata.lexis-nexis.com>,
|> Christopher C. Wood <christw@meaddata.com> wrote:
|> >In article <stephenkDMuGux.Iot@netcom.com>, stephenk@netcom.com (Stephen Knilans) writes:

|> >|> The libraries are there for a REASON!  There are possibly HUNDREDS
|> >|> of number formats, and it is very difficult to provide for all.

|> >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().  

|> That's because itoa() is not a standard library call.  

It's what the quotes around "standard" were meant to convey.  Lots of
developers treat this as something that is always there; as did I,
until I used non-bsd systems...

|> > As _assumed_ in Stroustrup, 2nd ed.

|> I don't see it in there at all.  What's the page number, and are you
|> sure they haven't actually implemented it as an example in that book?

I was a tad hasty.  Stroustrup uses atoi() on pg. 158 of "The C++
Programming Language, 2nd Ed, rather than itoa() as I claim.  It is
used, with no reference to header files, or discussion in the text.

|> >Guess what?  This "standard" library call, in actual practice, isn't
|> >standard.

|> That's because it's not *in* the standard.  

Is there a standard way to get a string representation of an integer
in C or C++?

Chris
-- 
Speaking only for myself, of course.
Chris Wood    christw@lexis-nexis.com   ChrisCWood@eworld.com