From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-5632-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 20748 invoked from network); 4 Mar 1999 08:34:04 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 4 Mar 1999 08:34:04 -0000
Received: (qmail 7520 invoked by alias); 4 Mar 1999 08:33:44 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 5632
Received: (qmail 7513 invoked from network); 4 Mar 1999 08:33:42 -0000
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
        <zsh-workers@sunsite.auc.dk>
Subject: 0 vs. NULL (RE: Worrisome warnings after recent patches)
Date: Thu, 4 Mar 1999 11:31:44 +0300
Message-ID: <000901be6619$6f8a6930$21c9ca95@mowp.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <199903040750.IAA01987@beta.informatik.hu-berlin.de>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2013.2901

> +	    Cline to, tn = NULL;

What is the point of using NULL to initialize null pointer. The only
portable and official way is to use `0'(zero), that is garanteed to be
converted to whatever representation null pointer has on a given system.

I mention it, because I just recently have seen quite a number of bug
reports, that rsulted exactly from using something like NULL for this.

Just a reminder ...

/andrej