Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site lsuc.UUCP
Path: utzoo!lsuc!jimomura
From: jimomura@lsuc.UUCP (Jim Omura)
Newsgroups: net.micro.6809
Subject: Re: code size vs. module size
Message-ID: <1002@lsuc.UUCP>
Date: Sun, 29-Dec-85 22:20:03 EST
Article-I.D.: lsuc.1002
Posted: Sun Dec 29 22:20:03 1985
Date-Received: Sun, 29-Dec-85 22:42:53 EST
References: <74200016@ea.UUCP>
Reply-To: jimomura@lsuc.UUCP (Jim Omura)
Organization: Barrister & Solicitor, Toronto
Lines: 25
Summary: 10K is typical stdio overhead


     While working with CP/M Small-C I noticed that 10K was about the smallest
program size I generally encountered.  I think that this is the 'stdio'
overhead and probably typical of most C compilers.  the 6K source to 16K
object code isn't really unusual.

     Interestingly, while we're discussing text editors, I put the source-
code for the "microEMACS" editor which was posted for the Amiga.  On the
Amiga, using Lattice C, it created a source code for about 40K.  I didn't
think we'd see a substantially smaller code size, but on the Color Computer
running OS-9 and using the Microware C compiler, one of our people compiled
it to an object code size of about 24K.  He has it running on the CoCo,
but only through a remote terminal (a Radio Shack DT100, probably running
as a VT-52 emulator--I didn't ask).  He had to break down the modules
to a lot of smaller modules and make a few minor changes, but he got it
to run in a few days.  I'm impressed.  I thought it was out of reach for
the Color Computer completely.

                                             Cheers! -- Jim O.

-- 
James Omura, Barrister & Solicitor, Toronto
ihnp4!utzoo!lsuc!jimomura
Byte Information eXchange: jimomura
(416) 652-3880