Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!wisdom.BITNET!simsong
From: simsong@wisdom.BITNET (Simson L. Garfinkel)
Newsgroups: net.micro.pc
Subject: Microemacs and MS C
Message-ID: <8608130841.AA20449@ucbjade.Berkeley.Edu>
Date: Wed, 13-Aug-86 04:41:42 EDT
Article-I.D.: ucbjade.8608130841.AA20449
Posted: Wed Aug 13 04:41:42 1986
Date-Received: Wed, 13-Aug-86 19:18:36 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 34

Newsgroups: net.emacs,net.micro.pc,net.micro
Subject: Re: MicroEMACS and MS C
Summary: Memory Modeles exploited
Expires:
References: <>
Sender: Simson L. Garfinkel
Reply-To: simsong%H@wiscvm.arpa (Simson L. Garfinkel)
Followup-To:
Distribution: net
Organization: Weizmann Inst. of Science, Dept. Of Math, Rehovot, Israel
Keywords: MS C


In article <> 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've been using MS C for a long time now. Yes, it does offer these
various memory model options. Unfortunately, MicroSoft does not provide
a library for use with the small code, large data model until you get to
MS C version 4.0. So, you're welcome to use this Customized Memory Model
but you have to write your own library routine, or do harry things to
call their library rotines (basically, you can declare all of their library
routines as "far", but this doesn't always work).

MS 4.0 comes with a new memory model (the name of which escapes me at the
moment) which is large data, small code.

--simson