[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: translators and scoping rules (was: Re: language translator help)
From: |
Neil Jerram |
Subject: |
Re: translators and scoping rules (was: Re: language translator help) |
Date: |
28 Apr 2002 19:21:52 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 |
>>>>> "John" == John W Eaton <address@hidden> writes:
John> The eval() function can introduce new local variables. How would you
John> do that with Guile? [...]
Currently impossible, I believe.
Parts of the solution are there, namely `local-eval' and
`the-environment', and it's easy to see how we could extend `define'
so that it could add a new binding to a `the-environment'-type
environment. However, `local-eval' and `the-environment' are already
considered a bit tricksy and perhaps-ought-not-to-be-there by some
people.
Can you explain in more application-specific terms what kind of usage
you are aiming to support by this mechanism? Then we could perhaps
think of a more natural (in Guile terms) way of achieving it.
Neil
- Re: loop translations (was: Re: language translator help), (continued)
- translators and scoping rules (was: Re: language translator help), John W. Eaton, 2002/04/27
- Re: translators and scoping rules (was: Re: language translator help), Per Bothner, 2002/04/28
- Re: translators and scoping rules (was: Re: language translator help), John W. Eaton, 2002/04/28
- Re: translators and scoping rules (was: Re: language translator help), Per Bothner, 2002/04/29
- Re: translators and scoping rules (was: Re: language translator help), John W. Eaton, 2002/04/29
- Re: translators and scoping rules (was: Re: language translator help),
Neil Jerram <=