From xemacs-m  Sat Jun 21 02:10:26 1997
Received: from iria.mines.u-nancy.fr (galibert@iria.mines.u-nancy.fr [193.49.140.100])
	by xemacs.org (8.8.5/8.8.5) with SMTP id CAA17714
	for <xemacs-beta@xemacs.org>; Sat, 21 Jun 1997 02:10:25 -0500 (CDT)
Received: (from galibert@localhost) by iria.mines.u-nancy.fr (950413.SGI.8.6.12/950213.SGI.AUTOCF) id JAA04331; Sat, 21 Jun 1997 09:09:06 +0200
Message-ID: <19970621090905.50312@iria.mines.u-nancy.fr>
Date: Sat, 21 Jun 1997 09:09:05 +0200
From: Olivier Galibert <Olivier.Galibert@mines.u-nancy.fr>
To: Hrvoje Niksic <hniksic@srce.hr>
Cc: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Re: Yet more 64bits lossage
References: <19970621012424.18989@iria.mines.u-nancy.fr> <199706210604.XAA07502@xemacs.eng.sun.com> <19970621082753.50969@iria.mines.u-nancy.fr> <kiglo445ua5.fsf@jagor.srce.hr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
In-Reply-To: <kiglo445ua5.fsf@jagor.srce.hr>; from Hrvoje Niksic on Sat, Jun 21, 1997 at 08:45:06AM +0200

On Sat, Jun 21, 1997 at 08:45:06AM +0200, Hrvoje Niksic wrote:
> No,
> 
> #define NULL 0
> 
> is sufficient in every ANSI C implementation.
I do not say it is not ANSI, just that it is not reasonable. Most
people expect NULL to fit for a null pointer no matter what the
context is, including varargs.


> The problem with variable-width argument lists is that the compilers
> cannot know whether there is an integer context, or a pointer
> context.  Thus one should always cast the pointers when calling such
> functions:
Actually, this I what I do in my programs. I was trying not to disturb
too much existing code. Removing the XtVa* entirely, like Martin said,
is a much better fix.

  OG.

