Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!vaxine!wjh12!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!sri-unix!Bicer.ES@Xerox.ARPA
From: Bicer.ES@Xerox.ARPA
Newsgroups: net.micro.cpm
Subject: Aztec C Users
Message-ID: <12271@sri-arpa.UUCP>
Date: Fri, 13-Apr-84 22:30:39 EDT
Article-I.D.: sri-arpa.12271
Posted: Fri Apr 13 22:30:39 1984
Date-Received: Sat, 12-May-84 02:18:15 EDT
Lines: 36


Someone complained that Aztec C creates a large COM file (compared to what???).
Keep the code below in seperate file, and include it when linking your modules
(order doesn't matter, but before libc.lib). I call this file minroot.c and
minroot.o for source and relocatible versions respectively.
-----------------------------------------------------------------------
Croot()
{
    exit(main());
}

exit(code)
{
    boot@();  /* @ sdands for underline character. These keyboards!!! */ 
}

badfd()
{
    return -1;
}

noper()
{
    return 0;
}
----------------------------------------------------------------------
The result of the program  "main() { }" (which shows size of the runtime
package) is:
  with minroot.o = 7 sectors --> 896 bytes
  without        =36 sectors -->4608 bytes
  
  But if you use the buffered I/O library (printf does!), then the necesseary
  code gets linked in and the size of the COM file is the same as before.
  
  	Jack Bicer