Xref: utzoo comp.lang.modula2:801 comp.lang.misc:1473 comp.lang.c:9509 comp.lang.pascal:825
Path: utzoo!mnetor!uunet!husc6!purdue!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.modula2,comp.lang.misc,comp.lang.c,comp.lang.pascal
Subject: Re: Modula2's godawful IO.
Message-ID: <11154@mimsy.UUCP>
Date: 21 Apr 88 10:25:42 GMT
References: <764@ndsuvax.UUCP> <535@m10ux.UUCP> <730@mhuxm.UUCP> <230@jupiter.olyis.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 25

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

In article <230@jupiter.olyis.UUCP> ecb@pluto.uucp (Eric Brown) writes:
>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.
[stuff deleted]
>Not all the world is a vax, you know.

Conversely, not all the world is an IBM PC with a Microsoft compiler.
It is not difficult[*] to arrange for the linker to pull in a simple
printf() if the rest of the program does not use floating point, and a
full-blown floating point printf if it does.  Just because Microsoft's
implementation is poor (in terms of space, at any rate) is no reason to
castigate printf itself.

-----
[*]What, never?  Well, hardly ever.  The trick is to have the linker
examine the undefined externals for floating-point library references,
and if present, link with `bigprintf.obj'; otherwise it should use
`littleprintf.obj'.  It is just a Small Matter of Programming.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris