Path: utzoo!attcan!uunet!munnari.oz.au!mel.dit.csiro.au!yarra!pta!teti!teslab!charles
From: charles@teslab.lab.OZ (Charles Widepy)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: How are some programs SO DAMN SMALL!
Message-ID: <1209@teslab.lab.OZ>
Date: 28 Feb 91 05:11:51 GMT
References: <1991Jan20.210328.18087@hoss.unl.edu> <28077.279c3c3f@kuhub.cc.ukans.edu> <11295.tnews@templar.actrix.gen.nz>
Reply-To: charles@teslab.lab.oz.au (Charles Widepy)
Organization: Technology Evaluation Section, L.A.B., Sydney
Lines: 19

In article <11295.tnews@templar.actrix.gen.nz> jbickers@templar.actrix.gen.nz (John Bickers) writes:
>    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.

I think that any reasonable person who has even considered this will
conclude that there is NO solution to the problem of how to gauge
program size. (eg. A program could be written as a very small executable
and a large shareable .library.)

This is all just an incredibly long winded and pointless discussion,
wasting lots of time and money, sparked by someone just trying to
prove what a smart arse he is. And lots of followups by people trying
to do the same (including this one :).

I say we give it a rest.
-- 
/      \  CWW           charles@teslab.lab.oz.au
\_.--._/  ..!uunet!munnari!teslab.lab.oz!charles