Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think!snorkelwacker!mit-eddie!uw-beaver!uw-entropy!dataio!bright
From: bright@Data-IO.COM (Walter Bright)
Newsgroups: comp.lang.c
Subject: Re: Expanded/Extended memory use in MSC 5.1
Keywords: expanded extended memory microsoft
Message-ID: <2303@dataio.Data-IO.COM>
Date: 24 Jan 90 21:19:08 GMT
References: <8559@stiatl.UUCP> <2581@jato.Jpl.Nasa.Gov>
Reply-To: bright@Data-IO.COM (Walter Bright)
Organization: Data I/O Corporation; Redmond, WA
Lines: 14

In article <8559@stiatl.UUCP> arw@stiatl.UUCP (Allan Watkins) writes:
<   4) WHEN IS SOMEONE GONNA MAKE IT EASY TO USE EXPANDED AND EXTENDED MEMORY
<       IN NORMAL MSC C LANGUAGE? (no violins please).

In Zortech C, there is direct compiler and library support for allocating
space in and having pointers into expanded memory. This is done with a
special pointer type, called a __handle pointer, that the compiler supports.
Accessing memory through a __handle pointer causes the appropriate EMS
page to be swapped in, etc., all transparently.

The current implementation does not support extended memory, though this is
a limitation of the library support for it, not the compiler.

This, of course, doesn't help you if you wish to use MSC! :-)