Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.berkeley.edu.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!ucbvax.berkeley.edu!dillon
From: dillon@ucbvax.berkeley.edu.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: Lattice C
Message-ID: <11532@ucbvax.berkeley.edu.BERKELEY.EDU>
Date: Fri, 24-Jan-86 13:00:52 EST
Article-I.D.: ucbvax.11532
Posted: Fri Jan 24 13:00:52 1986
Date-Received: Sat, 25-Jan-86 09:37:48 EST
Organization: University of California at Berkeley
Lines: 23
Keywords: code length


	There are several reasons why your "small" lattice C programs
Take so much room:

	(A) the Xstartup.obj is also included.  This is the startup
module which breaks up the arguments and calls main()... It also
happens to use STDIO, therefore the stdio library routines are also
linked in.

	(B) for those of you who havent guessed yet, printf() and 
associated functions take about 10K of space.

To REALLY test code size, write a C program which doesn't call ANY
library routines, then link it without all the other garbage:

	alink x.o to a

NOW you can use WACK ... notice that the code is rather smaller?  Now
do you understand how it works??? ALL those files you had to link in
are your support routines, etc....

				<sigh>
				-Matt