Xref: utzoo comp.lang.modula2:798 comp.lang.misc:1470 comp.lang.c:9491 comp.lang.pascal:822
Path: utzoo!mnetor!uunet!iconsys!caeco!olyis!pluto!ecb
From: ecb@pluto.uucp (Eric Brown)
Newsgroups: comp.lang.modula2,comp.lang.misc,comp.lang.c,comp.lang.pascal
Subject: Re: Modula2's godawful IO.
Message-ID: <230@jupiter.olyis.UUCP>
Date: 16 Apr 88 16:38:26 GMT
References: <764@ndsuvax.UUCP> <535@m10ux.UUCP> <730@mhuxm.UUCP> <942@unmvax.unm.edu>
Sender: news@olyisjupiter.UUCP
Reply-To: ecb@pluto.UUCP (Eric Brown)
Organization: Olympus Software, Inc.   Sandy, UT
Lines: 13

In article <942@unmvax.unm.edu> mike@turing.UNM.EDU.UUCP (Michael I. Bushnell) writes:
>To use printf, it ups your text segment by a whole 2236 bytes.  Wow.
>Puts is about 10% of that (200 bytes)
>but isn't really any faster.  But CERTAINLY NOT a "20K" overhead.  Go
>ahead and use printf.  It doesn't really cost you that much.

Now include the size of the floating point libraries.  On Microsoft 5.0 C,
calling printf links the floating point emulator, which is about 30K of code.
Is this significant?  I think so.  I once hacked out 300K out of a suite of
programs by transforming printf's to puts'es and also by using an integer-only
printf.  Sometimes, every byte counts.  Not all the world is a vax, you know.

	-Eric, Called Ultrahacker