Path: utzoo!attcan!uunet!ginosko!aplcen!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.lang.c Subject: Re: Memory Models Keywords: Memory models,C Message-ID: <10744@smoke.BRL.MIL> Date: 16 Aug 89 04:01:11 GMT References: <562@dcscg1.UUCP> <10703@smoke.BRL.MIL> <888@fiasco.sco.COM> Reply-To: gwyn@brl.arpa (Doug Gwyn) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 13 In article <888@fiasco.sco.COM> md@sco.COM (Michael Davidson) writes: >>In article <562@dcscg1.UUCP> drezac@dcscg1.UUCP (Duane L. Rezac) writes: >>>I am just getting into C and have a question on Memory Models. >Sorry, but it is an evil necessity brought about by the segmented >architecture of the INTEL 8086 and 80286 ... 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. The Apple IIGS architecture (65816) has a similar trade-off, and the available C compilers for it do not have "near" and "far" foolishness. And yes, it is possible for am Apple IIGS C programmer to select which model is to be used for his application, at least with Orca/C.