Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.Sun.COM (Guy Harris)
Newsgroups: comp.lang.c
Subject: Re: Let's define our own NULL II
Message-ID: <58240@sun.uucp>
Date: 28 Jun 88 17:37:25 GMT
References: <162@navtech.uucp>
Sender: news@sun.uucp
Lines: 14

> A personal message to Guy Harris at Sun: I'd love to see your analysis of
> this -- I encountered this idea first at a company I will not name -- the
> one we both worked at as of the beginning of 1984 (though I was at their main
> facility).

Oh, you mean CCI?

If I'm writing code that includes some include file that defines NULL, I use
it; otherwise, I use 0.  I don't pull in e.g.  just to define NULL;
however, most of the code I write is either 1) in the kernel, in which case it
usually includes  for other reasons and gets NULL predefined or 2)
not in the kernel, but uses standard I/O, in which case it includes 
and gets NULL predefined.

Had I an ANSI C environment I'd include  and get it defined that way.