Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!usc!basil.usc.edu!blarson
From: blarson@basil.usc.edu (bob larson)
Newsgroups: comp.lang.c
Subject: Re: Memory Models
Message-ID: <19158@usc.edu>
Date: 13 Aug 89 15:56:06 GMT
References: <5653@ficc.uu.net> <309@hitech.ht.oz>
Sender: news@usc.edu
Reply-To: blarson@basil.usc.edu (bob larson)
Organization: USC AIS, Los Angeles
Lines: 18

In article <309@hitech.ht.oz> clyde@hitech.ht.oz (Clyde Smith-Stubbs) writes:
>From article <5653@ficc.uu.net>, by peter@ficc.uu.net (Peter da Silva):
>>> That is not a C language issue.  It's kludgery introduced specifically
>>> in the IBM PC environment.
>It IS a language issue - you could argue that near and far address spaces
>are not part of the Standard C, therefore it is not a C issue, however
>there are sufficient architectures that REQUIRE a useful language  to

Just because your address space is segmented dosn't mean you have to
kludge your language around.  Prime C does quite nicely without memory
models.  (Actually, it does have one compiler switch to enable parinoia
about pointers possibly pointing in arrays larger than 128k bytes, PC
compilers would call this huge.)  (Additional instructions were added
for C to handle the concept of an efficent pointer to a byte.)
Bob Larson	Arpa:	blarson@basil.usc.edu
Uucp: {uunet,cit-vax}!usc!basil!blarson
Prime mailing list:	info-prime-request%ais1@usc.edu
			usc!ais1!info-prime-request