From xemacs-m  Mon Jun 30 14:30:50 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 OAA28180
	for <xemacs-beta@xemacs.org>; Mon, 30 Jun 1997 14:30:27 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcwfe22524; Mon, 30 Jun 1997 15:30:18 -0400 (EDT)
Date: Mon, 30 Jun 1997 15:30:18 -0400 (EDT)
Message-Id: <QQcwfe22524.199706301930@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@xemacs.org
Subject: Re: XEmacs 20.3-beta10 "Athens" is released
In-Reply-To: <m2g1tzoqyk.fsf@altair.xemacs.org>
References: <m290zsj0z4.fsf@altair.xemacs.org>
	<kig90zsz2lg.fsf@jagor.srce.hr>
	<m2g1tzoqyk.fsf@altair.xemacs.org>
X-Mailer: VM 6.33 under 20.3 "Athens" XEmacs  Lucid (beta10)
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

Steven L Baur writes:
 > Hrvoje Niksic <hniksic@srce.hr> writes:
 > 
 > > Steven L Baur <steve@xemacs.org> writes:
 > >> At Ben Wing's direction, I was going to remove the LOSING_BYTECODE code
 > >> which apparently allows some strange feature where compiled bytecode
 > >> objects can be referenced as a vector.  *A lot* of code breaks (at a
 > >> minimum EFS, AUCTeX, W3, Ilisp, Hyperbole, Edebug, CC-mode, strokes and
 > >> VM), so I backed it out at the last minute, and now have no intention
 > >> of ever taking it out.
 > 
 > > Have you investigated why they break?  LOSING_BYTECODE looks like a
 > > horrible kludge to me.
 > 
 > There wasn't any time to go into it in great depth.  I poked around a
 > bit and didn't see anything obvious.  I was hoping one of the package
 > authors could shed some light on what exactly is going.  This is a
 > feature I'm totally unfamiliar with.

I don't have the faintest idea what in VM would care about whether
byte-compiled functions have vecotrs in them or not.  I will try a
build with LOSING_BYTECODE turned off and see what goes boom, but
if I had to put money down. I would wager on something in XEmacs
being broken related to this rather than something in VM and all
those other packages.  I can't imagine all those authors (and
myself) doing something this filthy.

