Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!unisoft!mtxinu!rtech!llama!jas
From: jas@llama.rtech.UUCP (Jim Shankland)
Newsgroups: comp.lang.c
Subject: Re: Header problems
Message-ID: <1797@rtech.UUCP>
Date: 10 Mar 88 18:34:58 GMT
References: <2550049@hpisod2.HP.COM> <7412@brl-smoke.ARPA> <3351@chinet.UUCP>
Sender: news@rtech.UUCP
Reply-To: jas@llama.UUCP (Jim Shankland)
Organization: Relational Technology, Inc. Alameda, CA
Lines: 16
Summary: comp.lang.c into summer reruns already?

In article <3351@chinet.UUCP> dag@chinet.UUCP (Daniel A. Glasser) writes:
>Your use of NULL === 0 promotes unportable code, and is considered to be
>bad programming style in a world where portability across multiple machine
>architectures ... is required....  On machines were sizeof int !=
>sizeof(void *), the above definition will
>not work....  A better way to do it, in each place you want to define NULL,
>is:
>
>	#ifndef	NULL
>	#define	NULL	((void *)0)
>	#endif

Ack!  Here it comes again!  Warm up the ``kill'' file.
Jim Shankland
  ..!ihnp4!cpsc6a!\
               sun!rtech!jas
 ..!ucbvax!mtxinu!/