Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.csd.uwm.edu!mailrus!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Memory Models - Thanks for the info
Message-ID: <10811@smoke.BRL.MIL>
Date: 24 Aug 89 18:05:53 GMT
References: <564@dcscg1.UUCP> <225800209@uxe.cso.uiuc.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <225800209@uxe.cso.uiuc.edu> mcdonald@uxe.cso.uiuc.edu writes:
-From article <10744@smoke.BRL.MIL>, by gwyn@smoke.BRL.MIL (Doug Gwyn):
> People who aren't "wedded" to the *86 architecture generally don't
> seem to think it was necessary to cause memory models to be visible
> in higher-level programming languages.
-Nobody, even those like the '86, would claim that memory models
-need to be visible. They didn't. The compilers could have made
-everything large model. BUT ...

No, that's a misinterpretation of what I said.  Multiple memory models
can be supported without forcing them to be visible to the programmer.
ORCA/C for the Apple IIGS provides an example of one way to do this.