Re: coding standards

Luke Kenneth Casson Leighton (lkcl@switchboard.net)
Sat, 9 May 1998 14:14:44 +0100 (BST)

Date:	Sat, 9 May 1998 14:14:44 +0100 (BST)
From:	Luke Kenneth Casson Leighton <lkcl@switchboard.net>
To:	"Christopher R. Hertel" <crh@NTS.Umn.EDU>
Subject: Re: coding standards
In-Reply-To: <199805090240.VAA06671@unet.unet.umn.edu>

> As Andrew pointed out to me, the C standard does define NULL as a pointer
> with a value of zero. void *ptr = 0 isn't wrong, per se., it's just that
> it's much clearer to use NULL.

> #define NULL ((void*)0)

the atari lattice c compiler used to crash because of this (quite normal)
#define. i vaguely recall assigning an int (which defaulted to 16 bit on
a 68000 processor) to NULL which caused the compiler-crash: i was used to
decent compilers that define int to be 32 bit :-) :-)