Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site omen.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!think!mit-eddie!genrad!decvax!tektronix!reed!omen!caf
From: caf@omen.UUCP (Chuck Forsberg WA7KGX)
Newsgroups: net.micro.pc
Subject: Re: A New Compiler Model
Message-ID: <195@omen.UUCP>
Date: Fri, 19-Jul-85 06:30:26 EDT
Article-I.D.: omen.195
Posted: Fri Jul 19 06:30:26 1985
Date-Received: Sun, 21-Jul-85 22:27:10 EDT
References: <368@kontron.UUCP> <716@dataio.UUCP>
Reply-To: caf@.UUCP (Chuck Forsberg WA7KGX)
Organization: Omen Technology, Portland
Lines: 24

In article <716@dataio.UUCP> bright@dataio.UUCP (Walter Bright) writes:
>In article <368@kontron.UUCP> cramer@kontron.UUCP (Clayton Cramer) writes:
>>One of the nice things about writing code in assembler for the PC is that
>>you run the resulting .EXE file through EXE2BIN and get a .COM file.  
>>Wouldn't it be nice if Microsoft (and everyone else) supported a new
>>memory segmentation module with code and data in the same segment, so
>>we could create .COM programs written in C?
>
>The Datalight C compiler explicitly supports this memory model.

The requirement for a .COM file is that the loaded "stuff" not exceed
some size (64k?) and there be no relocation or segment fixups.

Obviously, an 8080 model (DS=SS=ES=CS) program would fit into a .COM
file.  Many small model programs can fit also, provided the text+data
is less than 64k and the program itself sets up the data segment.  You
could even get away with a large or huge model program provided the
text+data fit within the 64k (i.e. memory allocated dynamically).

-- 
  Chuck Forsberg WA7KGX   ...!tektronix!reed!omen!caf   CIS:70715,131
Omen Technology Inc     17505-V NW Sauvie Island Road Portland OR 97231
Voice: 503-621-3406     Modem: 503-621-3746 (Hit CR's for speed detect)
Home of Professional-YAM, the most powerful COMM program for the IBM PC