Path: utzoo!utgpu!watmath!clyde!att!pacbell!ames!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: pointers, tests, casts
Message-ID: <9038@smoke.BRL.MIL>
Date: 2 Dec 88 14:51:54 GMT
References: <11130@dartvax.Dartmouth.EDU> <44100016@hcx3>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <44100016@hcx3> shirono@hcx3.SSD.HARRIS.COM writes:
>Even in the K&R1 days, the only valid definition of NULL has been
>#define NULL 0

True of pre-ANSI C, but an ANSI C implementation can use either that
definition or
#define NULL ((void*)0)
I recommend the former even for ANSI C implementations.  The added
complexity buys just one thing, which is possible type mismatch
checking, but I don't think that is significant enough to justify
the change.