Path: utzoo!attcan!uunet!husc6!uwvax!vanvleck!uwmcsd1!bbn!rochester!pt.cs.cmu.edu!speech2.cs.cmu.edu!jgk
From: jgk@speech2.cs.cmu.edu (Joe Keane)
Newsgroups: comp.arch
Subject: Re: null pointers (was: negative addresses)
Keywords: unbelievable
Message-ID: <1998@pt.cs.cmu.edu>
Date: 19 Jun 88 21:53:58 GMT
References: <226@proxftl.UUCP> <3100003@hpmwtla.HP.COM>
Sender: netnews@pt.cs.cmu.edu
Organization: Carnegie Mellon
Lines: 14

In article <3100003@hpmwtla.HP.COM> jeffa@hpmwtla.HP.COM (Jeff Aguilera) writes:
>ANSI C is not C.  Prototypes do not exist in C.  Please show me where in
>K&R that it states that "0" refers to the NULL pointer irrespective of the
>underlying implementation.  Mr. Wells, if "0" does refer to the null
>pointer, why do some systems have #define NULL (-1) in stdio?  My 
>statement regarding casting is correct, since not all pointers need be 
>of the same size.  Prototypes eliminate this annoyance, but I live with
>a compiler void of prototypes :-(

Please, not this again!  Any system with `#define NULL (-1)' is so
broken it's pitiful.  Code in my previous posting must work right.

>Jeff "still wondering when C will be as clean as Algol-68" Aguilera
--Joe "enough about NULL" Keane