[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#51695: 29.0.50; lexical scope closure, interactive spec byte compile
From: |
Eli Zaretskii |
Subject: |
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@zoho.eu>
> Cc: 51695@debbugs.gnu.org, monnier@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.
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Emanuel Berg, 2021/11/08
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Eli Zaretskii, 2021/11/09
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Stefan Monnier, 2021/11/09
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Michael Heerdegen, 2021/11/09
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Emanuel Berg, 2021/11/09
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Emanuel Berg, 2021/11/09
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Michael Heerdegen, 2021/11/10
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Emanuel Berg, 2021/11/10
- bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue, Michael Heerdegen, 2021/11/10