[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764
From: |
Maxim Cournoyer |
Subject: |
Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764 |
Date: |
Fri, 31 Mar 2023 10:02:58 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Hi Josselin,
Josselin Poiret <dev@jpoiret.xyz> writes:
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> I've seen this too, but it disappears if you byte-compile the project.
>> I'm not sure what that means, although it does seems sub-optimal that we
>> rely on byte-compilation for the code to evaluate correctly.
>
> The problem actually comes from stale byte-compiled files. If you were
> to interpret everything, it would work properly. The issue is when a
> variable becomes a syntax-transformer, ie. a macro: then it should get
> expanded at compile-time, but guile doesn't recompile dependents
> (because it doesn't know about them). Hence, in dependent .go files,
> the variable didn't get expanded, and is then used at runtime, hence the
> error.
I thought I had cleared all .go files, but your explanation suggests I
didn't. I probably got confused in my multiple sessions on various
machines :-).
Thanks for the explanation.
--
Thanks,
Maxim