🚀 go-pugleaf

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

>In article <danpop.824303108@rscernix>, danpop@mail.cern.ch (Dan Pop) writes:
>|> In <4fqdta$rhh@meaddata.lexis-nexis.com> christw@meaddata.com (Christopher C. Wood) writes:
>
>|> >In article <9602121654.AA02634@ues5.cern.ch>, Dan Pop <Dan.Pop@cern.ch> writes:
>
>|> >What is the non-trivial method to convert an integer into an ASCII
>|> >representation of its value?  All I need is code that will run on
>|> >Solaris (2.3) and HPUX 9. 
>
>|> Why do you want to do it in a non-trivial way?  What's wrong with the
>|> trivial method: sprintf(buff, "%d", intval)?
>
>Linking in a 15K library when all I need is a 50-byte subroutine.
>
>Laziness like you suggest leads to code bloat.

The most ludicrous comment I ever read in this thread.

1. sprintf shares its code with printf and you'll have some difficulties
   finding a non-trivial C program which doesn't calls printf.

2. In Unix (all modern flavours) the libraries are shared.  You won't
   need to link the 15K library module to your code.  By the time you
   start your program, it will be already in memory, because other 
   processes using printf are already running.

3. The #1 source of code bloat is putting a GUI to programs that don't
   actually need one.

How about keeping your mouth shut on topics you have not the slightest
clue about?

Dan
--
Dan Pop
CERN, CN Division
Email: danpop@mail.cern.ch 
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland