Re: Possible defvar bug

[Tassilo Horn]

Alan Mackenzie <address@hidden> writes:

>> ELISP> (let ((foo 3))
>>       (defvar foo 1)
>>       (print foo))
>> 3
>> ELISP> foo
>> *** Eval error ***  Symbol's value as variable is void: foo
>> ELISP> 
>
>> And, no, this is almost never what you want :-) Just like Tassilo
>> noticed by accident.
>
> Why would anybody want to defvar a variable inside a let binding which
> also defines it, anyway?

Yes, these minimal examples look weired.  The real code was a bit more
like

  (let* ((crm-separator ",") ...)
    ...
    (function-that-might-read-multiple-values-using-crm))

and `function-that-might-read-multiple-values-using-crm' dispatches if
one or multiple separated values are to be read, and then delegates to a
read-single-value or read-multiple-values-with-crm function.  The latter
required crm when being called.

The let-binding of `crm-separator' was just meant as a default value in
case crm was going to be used, because all LaTeX keyval-options use ","
to separate key-value pairs.

Bye,
Tassilo