Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site wlbr.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!qantel!hplabs!nsc!voder!wlbr!steve
From: steve@wlbr.UUCP (Steve Childress)
Newsgroups: net.micro.pc
Subject: Pointers in MS-C, large model
Message-ID: <346@wlbr.UUCP>
Date: Fri, 6-Sep-85 02:12:52 EDT
Article-I.D.: wlbr.346
Posted: Fri Sep  6 02:12:52 1985
Date-Received: Mon, 9-Sep-85 00:52:15 EDT
Organization: Eaton IMS, Westlake Village, CA
Lines: 30

...
...

Relative to the Microsoft C compiler ( != Lattice) ...

When using the large (data space) model, I understand that MS just
ignores the problem of pointers in the 808x CPUs, ie, 

MS just compares the low 16 bits, as I understand. To detect a pointer
operation which yields a value in excess of 2^16, the burden falls upon
the programmer (!).

Lattice C, despite the lousy library, does handle 20 bit pointers, though with
speed penalties arising from normalization.


How is one to write C code to handle:
   char  *p, x[200000]
   p++ = &x[65535];

Where am I wrong here? Did Microsoft REALLY throw us a curve?

		Regards,
			Steve Childress
			Eaton IMS    R&D Group MS 43 
			31717 La Tienda Drive
			Westlake Village,  CA    91360
			(818) 889-2211 X2148
			{trwrb, scgvaxd, ihnp4, voder, vortex} !wlbr!steve
		        or	 		        ...wlbr!wlbreng1!steve