🚀 go-pugleaf

In article <stephenkDMuGux.Iot@netcom.com>, stephenk@netcom.com (Stephen Knilans) writes:

|> If you write code to directly convert a binary number to a human
|> readable version, and find that it won't work the same on all
|> processors, this is NOT the fault of C!!!!!!!!!!!  It is because
|> MANY processors are different!

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

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