Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zephyr.ens.tek.com!tektronix!reed!intelhf!ichips!inews!pima!bhoughto
From: bhoughto@pima.intel.com (Blair P. Houghton)
Newsgroups: comp.std.c
Subject: Re: gcc and NULL function pointers.
Message-ID: <4641@inews.intel.com>
Date: 9 Jun 91 22:06:33 GMT
References: <16386@ganymede.inmos.co.uk> <1991Jun4.012914.25418@tkou02.enet.dec.com>
Sender: news@inews.intel.com
Organization: Intel Corp, Chandler, AZ
Lines: 14

Old chesnuts crack hard...

In article <1991Jun4.012914.25418@tkou02.enet.dec.com> diamond@jit533.enet@tkou02.enet.dec.com (Norman Diamond) writes:
>>On our system, NULL is #defined in a header file to be ((void *)0),
>So, be careful casting your uses of the NULL macro!!

Better, su to root and erase the `(void *)' part.  The most
general, and therefore most valuable, way to define NULL is
to simply map it to the digit 0.  Anything else only complicates
the situation unnecessarily (although it might illuminate the
occasional compiler bug.)

				--Blair
				  "Blink-blink."