Re: defvars at compile time

[David Kastrup]

Juanma Barranquero <address@hidden> writes:

> On 9/16/05, David Kastrup <address@hidden> wrote:
>
>> Actually, I get "might be undefined at run time" in some similar
>> eval-when-compile wrapped situations.
>
> Maybe with some unusual combination of circumstances.
>
>> And having different semantics
>> during compilation and execution also is not a good idea.
>
> There's almost zero semantics in `(eval-when-compile (defvar xxx))'.
> It doesn't generate code, or assign any value, or affect dynamic
> bindings (on normal situations, which we're discussing now).

Yet.  I believe that itmakes a difference with lexical scope, where it
also serves as a declaration that let-bindings to that variable should
have dynamic scope.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum