From xemacs-m  Sat Jun 21 01:28:36 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id BAA17464
	for <xemacs-beta@xemacs.org>; Sat, 21 Jun 1997 01:28:35 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcuvx10888; Sat, 21 Jun 1997 02:28:34 -0400 (EDT)
Date: Sat, 21 Jun 1997 02:28:34 -0400 (EDT)
Message-Id: <QQcuvx10888.199706210628@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: XEmacs Beta Test <xemacs-beta@xemacs.org>
Subject: Yet more 64bits lossage
In-Reply-To: <199706210604.XAA07502@xemacs.eng.sun.com>
References: <19970621012424.18989@iria.mines.u-nancy.fr>
	<199706210604.XAA07502@xemacs.eng.sun.com>
X-Mailer: VM 6.33 under Emacs 19.34.1
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Does compiling with 64-bit pointers buy the user anything but
trouble?  I'm sure it will give us a warm fuzzy feeling to have it
work, but there are icebergs ahead.  If the cause of these crashes
is 32-bit ints and 64-bit pointers, then there is the problem that
Lisp_Objects are ints.  Any pointer to an object that needs the
topmost 64 bits isn't going to fit in a Lisp_Object.  XEmacs is
going to go boom if something tries to cram a 64-bit wide pointer
in there.  So if XEmacs can't use 64-bit pointers why compile with
them?  (I'm assuming the person doing the build has a choice.)

