GNU bug report logs - #51695
29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Emanuel Berg <moasenwood <at> zoho.eu>
Cc: 51695 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
Subject: Re: bug#51695: 29.0.50; lexical scope closure, interactive spec
 byte compiler warnings/usage issue
Date: Wed, 10 Nov 2021 15:20:08 +0200

> From: Emanuel Berg <moasenwood <at> zoho.eu>
> Cc: 51695 <at> debbugs.gnu.org,  monnier <at> iro.umontreal.ca
> Date: Wed, 10 Nov 2021 02:39:05 +0100
> 
> > How can the interactive spec use lexically-bound variables
> > outside its scope, when the interactive spec runs not at
> > function definition time, but at function invocation time,
> > when those variables will be long gone?
> 
> But it does work if you evaluate the code, isn't this
> discrepancy a problem?

Not for me, it isn't.  But what do I know?

> "Function definition time", is that the time of Elisp
> evaluation, byte compilation, or the loading of byte-compiled
> source BTW?

Whenever the function definition is evaluated, yes.

Previous Next

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