Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uunet!steinmetz!philabs!pwa-b!mmintl!johnt
From: johnt@mmintl.UUCP (John Tangney)
Newsgroups: comp.lang.c,comp.sys.ibm.pc,comp.sys.intel
Subject: Re: C compilers that can access more memory
Message-ID: <2163@mmintl.UUCP>
Date: Mon, 8-Jun-87 20:11:28 EDT
Article-I.D.: mmintl.2163
Posted: Mon Jun  8 20:11:28 1987
Date-Received: Fri, 12-Jun-87 01:04:59 EDT
References: <496@tahoe.UUCP>
Reply-To: johnt@mmintl.UUCP (John Tangney)
Organization: Multimate International, E. Hartford, CT.
Lines: 18
Keywords: More C Memory
Xref: mnetor comp.lang.c:2408 comp.sys.ibm.pc:4722 comp.sys.intel:262

In article <496@tahoe.UUCP> malc@tahoe.UUCP (Malcolm L. Carlock) writes:
>Microsoft C and
>MIX C both seem to be unable to access more than 64K of either.  (This
>seems to be based on some difficulty implementing pointers using these
>machines' segmented memory setup).

Sorry, Microsoft C 4.00 certainly *does* allow access beyond 64K.  It does
this via different memory "models", whereby code, data or neither is limited
to 64K.  Allowing the limitations provides for the speed/space advantages if
it is known that (eg) code will not go beyond 64K.  Also supported is a
"mixed model", which allows you to specify explicitly which structs or
functions you want to be near or far.

I have been using MS-C 4.00 since it became available.

I don't know anything about MIX C.

johnt