Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!hplabs!tektronix!tekcrl!tekgvs!toma From: toma@tekgvs.UUCP (Thomas Almy) Newsgroups: net.emacs,net.micro.pc,net.micro Subject: Re: MicroEMACS and MS C Message-ID: <1675@tekgvs.UUCP> Date: Mon, 11-Aug-86 11:20:21 EDT Article-I.D.: tekgvs.1675 Posted: Mon Aug 11 11:20:21 1986 Date-Received: Tue, 12-Aug-86 23:21:36 EDT References: <243@killer.UUCP> Reply-To: toma@tekgvs.UUCP (Thomas Almy) Organization: Tektronix, Inc., Beaverton, OR. Lines: 34 Keywords: Obscure MS C feature (?) Xref: mnetor net.emacs:1385 net.micro.pc:6114 net.micro:5816 In article <243@killer.UUCP> tad@killer.UUCP writes: > >A while back, there was a discussion about the standard memory >models offered by Microsoft C, and how none of them were really >right (ie. no small code, large data model). Well, quite >accidentally, I stumbled across section 7.11.2 of the MSC User's >Guide, and found the section called "Creating Customized >Memory Models", and said, "Hey, I bet this could be what we all >need!". > >I'm not an expert at diddling with these type of things (yet), >but I think the following switch is appropriate: > >-Asfd > >the s is for short code pointers, the f for far data pointers, and >the d I'm not real sure about. The manual says that all the >memory models use d as a default which is stack segment equal >to data segment. The other options are u, for separate DS and SS, >which I think is inappropriate, and w, for a separate SS, but no >fixed DS, which I'm *sure* is not appropriate. But how do you recompile the C library for the mixed model when Microsoft doesn't supply the library sources? There is no library with short code pointers and far data pointers. I was thinking of just using the small model but declaring the line structures to be far. The trouble with this is that I would have to write malloc. At any rate, the new version 4.0 C supports a model with small code and large data, so the problem is moot. Tom Almy Tektronix, Inc.