Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!mips!daver!tscs!tct!chip
From: chip@tct.com (Chip Salzenberg)
Newsgroups: comp.os.minix
Subject: Re: NULL
Message-ID: <286B307B.1CA7@tct.com>
Date: 28 Jun 91 12:50:03 GMT
References: <33822@usc.edu> <1991Jun27.095611.26562@syd.dit.CSIRO.AU>
Organization: TC Telemanagement, Clearwater, FL
Lines: 15

According to evans@syd.dit.CSIRO.AU (Bruce.Evans):
>In article <33822@usc.edu> kjh@pollux.usc.edu (Kenneth J. Hendrickson) writes:
>>In /usr/include/stdio.h, #define NULL 0
>
>The redefinition of NULL in stdio.h is to avoid about 1000 incorrect warnings
>from the standard compiler. The standard compiler does not really understand
>void *.

Then the other headers should be changed to match.

There's no reason for inconsistency among /usr/include/*.h.
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.com>, <uunet!pdn!tct!chip>
 "I want to mention that my opinions whether real or not are MY opinions."
             -- the inevitable William "Billy" Steinmetz