On Sat 14 Jan 2012 16:16, David Kastrup <d...@gnu.org> writes: > Andy Wingo <wi...@pobox.com> writes: > >> On Sat 14 Jan 2012 09:59, David Kastrup <d...@gnu.org> writes: >> >>> so that (define x 5) inside of local-eval would _not_ be equivalent to >>> (module-define! (current-module) 'x 5) as the first one would take the >>> current module at the-environment time, and the second one would take >>> it at local-eval time. >> >> This would be a lexical definition, and probably not allowed by the >> current code. > > Two half-sentences, and each one makes me go WHAT!?!?!?!
The drama is unnecessary, thanks. > I assume that "this" means "the second one". Why would a module-define! > call be a lexical definition? And why would it not be allowed by "the > current code" and what does "the current code" mean in that context? I mean that currently, with Mark's current patches, the only ones which allow local-eval in 2.0, definitions are not allowed. A call to module-define! is a procedure call, not a definition. Andy -- http://wingolog.org/
