From xemacs-m  Mon Jun 30 14:36:28 1997
Received: from newman.aventail.com (root@newman.aventail.com [199.238.236.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id OAA28238
	for <xemacs-beta@xemacs.org>; Mon, 30 Jun 1997 14:36:28 -0500 (CDT)
Received: from kramer.in.aventail.com (wmperry@kramer.in.aventail.com [192.168.1.12])
	by newman.aventail.com (8.8.5/8.8.5) with ESMTP id MAA17294;
	Mon, 30 Jun 1997 12:36:28 -0700 (PDT)
Received: (from wmperry@localhost) by kramer.in.aventail.com (8.7.6/8.7.3) id MAA22381; Mon, 30 Jun 1997 12:36:28 -0700
To: Kyle Jones <kyle_jones@wonderworks.com>
Cc: xemacs-beta@xemacs.org
Subject: Re: XEmacs 20.3-beta10 "Athens" is released
References: <m290zsj0z4.fsf@altair.xemacs.org> 	<kig90zsz2lg.fsf@jagor.srce.hr> 	<m2g1tzoqyk.fsf@altair.xemacs.org> <QQcwfe22524.199706301930@crystal.WonderWorks.COM>
Errors-to: wmperry@aventail.com
Reply-to: wmperry@aventail.com
X-Face: O~Rn;(l][/-o1sALg4A@xpE:9-"'IR[%;,,!m7</SYF`{vYQ(&RI1&EiH[FvT;J}@f!4kfz
 x_!Y#=y{Uuj9GvUi=cPuajQ(Z42R[wE@{G,sn$qGr5g/wnb*"*ktI+,CD}1Z'wxrM2ag-r0p5I6\nA
 [WJopW_J.WY;
From: wmperry@aventail.com (William M. Perry)
Date: 30 Jun 1997 12:36:27 -0700
In-Reply-To: Kyle Jones's message of "Mon, 30 Jun 1997 15:30:18 -0400 (EDT)"
Message-ID: <86205j3mtg.fsf@kramer.in.aventail.com>
Lines: 32
X-Mailer: Gnus v5.4.60/XEmacs 20.3(beta10) - "Athens"

Kyle Jones <kyle_jones@wonderworks.com> writes:

> 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.

  I sure as hell don't reference any byte-code directly.

-Bill P.

