Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version nyu B notes v1.5 12/10/84; site acf4.UUCP
Path: utzoo!linus!philabs!cmcl2!acf4!tsc2597
From: tsc2597@acf4.UUCP (Sam Chin)
Newsgroups: net.micro.pc
Subject: Re: Need 286 "C" benchmark (FLAME!)
Message-ID: <1050041@acf4.UUCP>
Date: Wed, 29-May-85 09:30:00 EDT
Article-I.D.: acf4.1050041
Posted: Wed May 29 09:30:00 1985
Date-Received: Fri, 31-May-85 04:26:32 EDT
References: <152@megad.UUCP>
Organization: New York University
Lines: 18

<>

Someone was looking for a compiler where you could declare more than 64K of
local static data. Well, both Microsoft C and Metaware have models where
they dynamically change the DS and ES register as the program executes and
thus allow for multiple data segments. This enables static data do be more
than 64K. The limit on Microsoft C is that each object is no larger than
64K. This may be a problem in that malloc() returns an unsigned int and not
a long or that they simply ran out of registers to manage the heap (since
they were handling multiple data segments). To me though these are *never*
problems because it is so so simple to write an assembly language kludge to
handle any amount of data you want or use the low level routines like
movedata or poke/peek in Lattice. Do they no longer teach Assembler Language
in schools? Come on!

Sam Chin
allegra!cmcl2!acf4!tsc2597
tsc2597.acf4@nyu