Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!comp.vuw.ac.nz!actrix!templar!jbickers From: jbickers@templar.actrix.gen.nz (John Bickers) Newsgroups: comp.sys.amiga.programmer Subject: Re: How are some programs SO DAMN SMALL! Message-ID: <11295.tnews@templar.actrix.gen.nz> Date: 19 Feb 91 00:44:40 GMT References: <1991Jan20.210328.18087@hoss.unl.edu> <28077.279c3c3f@kuhub.cc.ukans.edu> <91042.125712UH2@psuvm.psu.edu> <91042.134209J56QC@CUNYVM.BITNET> by dave@cs.arizona.edu (Dave P. Schaumann): > Really, to be strictly accurate, you should include all the AmigaOS support > code in your code size, too. The characters "echo hello world" aren't some Note that a C program to do the same thing includes: - The code for AmigaDOS, because of Write() and Output(). - The code for graphics.library, because of the text and layers stuff required. - The code for the CON: device. - The code for the Shell used to load the program. Etc. Regardless of the pedantic aspects of all this, the only reasonable solution to the problem of what to guage program size by is the size of the file that gets executed. The user can then watch out for themselves with respect to what other overhead may be involved. > Dave Schaumann | DANGER: Access holes may tear easily. Use of the access -- *** John Bickers, TAP, NZAmigaUG. jbickers@templar.actrix.gen.nz *** *** "Patterns multiplying, re-direct our view" - Devo. ***