Memory Models

[bob larson]

In article <309 at hitech.ht.oz> clyde at hitech.ht.oz (Clyde Smith-Stubbs) writes:
>From article <5653 at ficc.uu.net>, by peter at 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 at basil.usc.edu
Uucp: {uunet,cit-vax}!usc!basil!blarson
Prime mailing list:	info-prime-request%ais1 at usc.edu
			usc!ais1!info-prime-request