From owner-freebsd-current@FreeBSD.ORG  Mon Mar  1 21:39:28 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 20A3F16A4CE
	for <current@freebsd.org>; Mon,  1 Mar 2004 21:39:28 -0800 (PST)
Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6A75743D1D
	for <current@freebsd.org>; Mon,  1 Mar 2004 21:39:27 -0800 (PST)
	(envelope-from bde@zeta.org.au)
Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au
	[61.8.0.87])i225dQnX021689;	Tue, 2 Mar 2004 16:39:26 +1100
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	i225dN5c016806;	Tue, 2 Mar 2004 16:39:25 +1100
Date: Tue, 2 Mar 2004 16:39:23 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Mark Murray <mark@grondar.org>
In-Reply-To: <200402291546.i1TFkZ0w070591@grimreaper.grondar.org>
Message-ID: <20040302163419.M8656@gamplex.bde.org>
References: <200402291546.i1TFkZ0w070591@grimreaper.grondar.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: NULL vs 0 vs 0L bikeshed time
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2004 05:39:28 -0000

On Sun, 29 Feb 2004, Mark Murray wrote:

> ...
> I'd like to commit the following patch. It makes sure that for C
> and the kernel, NULL is a ((void *)0), and for C++, NULL is either
> (0L) or 0, with __LP64__ used to define the difference.
>
> The intent is to catch use of NULL where 0 or (0L) should be used.
> It generates extra warnings (I promise to fix these).

This may involve fixing hundreds if not thousands of ports.

Bruce