Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.UUCP
Newsgroups: comp.lang.c
Subject: Re: Writing readable code
Message-ID: <6041@brl-smoke.ARPA>
Date: Tue, 30-Jun-87 12:17:12 EDT
Article-I.D.: brl-smok.6041
Posted: Tue Jun 30 12:17:12 1987
Date-Received: Fri, 3-Jul-87 07:26:01 EDT
References: <1158@copper.TEK.COM> <6858@auspyr.UUCP> <17171@cca.CCA.COM> <13008@topaz.rutgers.edu> <926@argus.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <926@argus.UUCP> ken@argus.UUCP (Kenneth Ng) writes:
>NULL is ***NOT*** defined as zero on all machines.

I suspect readers of this newsgroup are sick of this by now,
but it is IMPORTANT to understand that:
	(a) NULL is not defined by a machine; it is defined in <stdio.h>
	and perhaps other places for programmer convenience
	(b) #define NULL 0	is ALWAYS a CORRECT definition; this has
	nothing to do with how null pointers are represented in a C
	implementation but is required by the C language definition
	(c) NULL is not appropriate for passing as a function parameter
	unless it is appropriately cast