From owner-freebsd-ports@FreeBSD.ORG Thu Mar 10 19:25:29 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D02FF16A4CE for ; Thu, 10 Mar 2005 19:25:29 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9561A43D5C for ; Thu, 10 Mar 2005 19:25:28 +0000 (GMT) (envelope-from barner@gmx.de) Received: (qmail invoked by alias); 10 Mar 2005 19:25:27 -0000 Received: from unknown (EHLO zi025.glhnet.mhn.de) (129.187.19.157) by mail.gmx.net (mp004) with SMTP; 10 Mar 2005 20:25:27 +0100 X-Authenticated: #147403 Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id A2366C386; Thu, 10 Mar 2005 20:25:27 +0100 (CET) Date: Thu, 10 Mar 2005 20:25:27 +0100 From: Simon Barner To: Volker Stolz Message-ID: <20050310192527.GC1911@zi025.glhnet.mhn.de> References: <20050310120140.GD80397@i2.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WK3l2KTTmXPVedZ6" Content-Disposition: inline In-Reply-To: <20050310120140.GD80397@i2.informatik.rwth-aachen.de> User-Agent: Mutt/1.5.8i X-Y-GMX-Trusted: 0 cc: ports@FreeBSD.org cc: kde@FreeBSD.org Subject: Re: C++ issue on 4.11: kpopupmenu.h [Please review] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 19:25:29 -0000 --WK3l2KTTmXPVedZ6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Volker Stolz wrote: [...] > As far as I know, all systems with NULL !=3D 0L have either been molten d= own > or are otherwise not in a position to run KDE :) Volker, AFAIK, null pointers in C++ are supposed to be written as 0 (or OL for (some?) 64 bit platforms). NULL is a construct that has been introduced with K&R C, where it was defined as follows: #define NULL ((void*) 0) Today's C compilers also accept 0 instead of NULL. So, in your case, using 0 should be just fine. Btw.: I just grepped /usr/include on both FreeBSD 4.11 and 5.3, and in the latter case there seems to have some substantial cleanup regarding NULL: FreeBSD 5 has include/sys/_null.h (which is #included by stdio.h), whereas 4.x has several places where #ifndef NULL #define ... is used.=20 Perhaps some _really_ NULL-savant could step in here and clarify things ;-) Simon --WK3l2KTTmXPVedZ6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCMJ8nCkn+/eutqCoRAvSlAKCEQ8Xc4rd0j89IXOYq6qVxM6TkAACferPu Pn4Kkdb/aVbWz6p6tmJMEL8= =z4vM -----END PGP SIGNATURE----- --WK3l2KTTmXPVedZ6--