GNU bug report logs - #62317
28.2; This byte-compiled file behaves wrongly.

Previous Next

Full log

Message #70 received at 62317 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: 62317 <at> debbugs.gnu.org, teika <at> gmx.com, monnier <at> iro.umontreal.ca
Subject: Re: bug#62317: 28.2; This byte-compiled file behaves wrongly.
Date: Wed, 13 Sep 2023 17:45:08 +0300

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Wed, 13 Sep 2023 07:02:38 -0700
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 62317 <at> debbugs.gnu.org, teika <at> gmx.com
> 
> Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> 
> >> It seems like this patch was never installed.
> >
> > To be honest, I'm not sure it's worth the trouble.
> >
> > I'd argue that the bug is in having side-effects like that inside
> > `eval-and/when-compile` (or at the top-level of a `require`d file).
> > The patch only caters to changes to the `current_buffer` but there can
> > be many other ways to cause similar troubles and I can't think of a good
> > way to confine them all.
> 
> Good point.  It seems rather unusual to call `set-buffer' from the
> top-level of a required file, to say the least.  And if we accept that,
> users can start calling all kinds of weird and wonderful things.
> 
> On the other hand, the fix seems innocuous enough.
> 
> Eli, what do you think?  Should we close this as wontfix?

Given that Stefan Monnier himself is not sure, yes, I think we should
close this as wontfix.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.