From owner-freebsd-bugs  Mon Feb 17 23:50:08 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA02778
          for bugs-outgoing; Mon, 17 Feb 1997 23:50:08 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA02761;
          Mon, 17 Feb 1997 23:50:03 -0800 (PST)
Date: Mon, 17 Feb 1997 23:50:03 -0800 (PST)
Message-Id: <199702180750.XAA02761@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Peter Mutsaers <plm@xs4all.nl>
Subject: Re: bin/2752: NULL is used instead of 0 many places
Reply-To: Peter Mutsaers <plm@xs4all.nl>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/2752; it has been noted by GNATS.

From: Peter Mutsaers <plm@xs4all.nl>
To: arnej@imf.unit.no
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/2752: NULL is used instead of 0 many places
Date: 17 Feb 1997 20:24:09 +0100

 >> On Mon, 17 Feb 1997 10:10:59 +0100 (CET), Arne Henrik Juul
 >> <arnej@imf.unit.no> said:
 
     AHJ> 	Appy following patch.  This changes NULL to 0 most places
     AHJ> 	but to '\0' in character context, to be more stylistically
     AHJ> 	correct.
 
 Why is using '\0' more stylistically correct? A pointer is a pointer,
 and one can always assign 0 to it.
 
 One does not assign 0L to an long* either, but simply 0.