From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10225 invoked by alias); 8 Aug 2004 04:52:48 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 10217 invoked from network); 8 Aug 2004 04:52:46 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sourceware.org with SMTP; 8 Aug 2004 04:52:46 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 1C23447D91; Sat, 7 Aug 2004 21:52:46 -0700 (PDT) Date: Sun, 08 Aug 2004 04:52:00 -0000 From: Joel Brobecker To: gdb-patches@sources.redhat.com Cc: Andrew Cagney , Peter Schauer , Kevin Buettner Subject: [RFC/AIX] xm-aix4.h - Can we remove NULL re-define? Message-ID: <20040808045246.GE24160@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-SW-Source: 2004-08/txt/msg00235.txt.bz2 config/xm-aix4.h contains the following definition: | /* Brain death inherited from PC's pervades. */ | #undef NULL | #define NULL 0 Is this still needed? Where does this come from? It looks pretty scary that a compiler would actually defined NULL as being non-zero. I have always heard that NULL is not garantied to be zero, but I've seen so much code kind of confusing NULL and zero that I thought nobody in their right mind would actually do otherwise... If still necessary, can this be replaced by something like this in defs.h? #if (NULL != 0) #undef NULL #define NULL 0 #endif -- Joel