Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!olivea!orc!inews!iwarp.intel.com!gargoyle!ddsw1!zane
From: zane@ddsw1.MCS.COM (Sameer Parekh)
Newsgroups: comp.sys.apple2
Subject: Re: Computer capabilities (Re: Stellar 7 re-release)
Keywords: Do not meddle in the affairs of wizards: it makes them soggy and hard
Message-ID: <1991Jan02.224634.21366@ddsw1.MCS.COM>
Date: 2 Jan 91 22:46:34 GMT
References: <325@generic.UUCP> <1990Dec31.233636.24004@dartvax.dartmouth.edu>
Reply-To: zane@ddsw1.MCS.COM (Sameer Parekh)
Organization: ddsw1.MCS.COM Contributor, Wheeling, IL
Lines: 13

In article <1990Dec31.233636.24004@dartvax.dartmouth.edu> anarch@eleazar.dartmouth.edu (The Anarch) writes:
>compile to an executable.  How big a file do you end up with?  Now fire up
>the mini-assembler and put together a program that accomplishes the same
>thing.  I would be shocked if it took you more than two dozen bytes, data
>included.  printf(), though, is a *big* function!
	Don't USE printf() use puts()! Printf is huge because of all the
formatting routines, puts is VERY simple.  (Maybe even a while loop
of putchar()s would be more efficient, but that is what I think puts()
does anyway.)


-- 
zane@ddsw1.MCS.COM