Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!astroatc!prairie!dan
From: dan@prairie.UUCP
Newsgroups: news.software.b
Subject: Re: News for Xenix on PC AT ?
Message-ID: <452@prairie.UUCP>
Date: Fri, 8-May-87 08:23:02 EDT
Article-I.D.: prairie.452
Posted: Fri May  8 08:23:02 1987
Date-Received: Sat, 9-May-87 08:32:15 EDT
References: <18346@ucbvax.BERKELEY.EDU> <145@sds.UUCP>
Reply-To: dan@prairie.UUCP (Daniel M. Frank)
Organization: Prairie Computing, Madison, Wisconsin
Lines: 20

In article <655@cognos.UUCP> jimp@cognos.UUCP (Jim Patterson) writes:
>>As quoted from <442@prairie.UUCP> by dan@prairie.UUCP (Daniel M. Frank):
>>| The VAX compiler and linker appear to arrange that (char *)0
>>| ALWAYS points to a null string.
>
>This can't be the VAX/VMS C compiler. 

   Ok.  I meant the VAX BSD Unix compiler.  My apologies for ignoring a
large segment (no pun intended) of the VAX-using public.

   By the way, there is a linker option in SVR2 that forces a 0-value
pointer to point to a null string.  It's only available in small model
on the 286 (for obvious reasons), but I wonder how much it's used by
VAX System V programmers.

-- 
      Dan Frank (w9nk)
	ARPA: dan@db.wisc.edu			ATT: (608) 255-0002 (home)
	UUCP: ... uwvax!prairie!dan		     (608) 262-4196 (office)
	SNAILMAIL: 1802 Keyes Ave. Madison, WI 53711-2006