From xemacs-m  Sat Jun  7 14:04:48 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 OAA04195
	for <xemacs-beta@xemacs.org>; Sat, 7 Jun 1997 14:04:46 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcsye24769; Sat, 7 Jun 1997 15:04:46 -0400 (EDT)
Date: Sat, 7 Jun 1997 15:04:46 -0400 (EDT)
Message-Id: <QQcsye24769.199706071904@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 Developers <xemacs-beta@xemacs.org>
Subject: A byte-compiler bug?
In-Reply-To: <kig206ep93d.fsf@jagor.srce.hr>
References: <kig206ep93d.fsf@jagor.srce.hr>
X-Mailer: VM 6.33 under 20.3 XEmacs Lucid (beta4)
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

The byte compiler is reusing constants.  ?\0 is the same as 0 as
it knows.  It already has ?\0 in its vector of constants so it
uses it in every place where a 0 would be used.

