Re: Possible defvar bug

[Thierry Volpiatto <thierry.volpiatto@gmail.com>]

"Drew Adams" <drew.adams@oracle.com> writes:

>> See also documentation of `require' which should not be used inside
>> `let' bindings for same reasons.
>
> Hm.  What doc of `require' mentions this?

,----
| The expression `(require 'comint)' loads the file `comint.el' if it has
| not yet been loaded, ensuring that `comint-dynamic-complete-filename'
| is defined.  Features are normally named after the files that provide
| them, so that `require' need not be given the file name.  (Note that it
| is important that the `require' statement be outside the body of the
| `let'.  Loading a library while its variables are let-bound can have
| unintended consequences, namely the variables becoming unbound after
| the let exits.)
`----


> I looked at the doc string and (elisp) `Named Features', but I didn't
> notice anything about this.
>
> I hope that the doc for this, wherever it might be, is more specific than what
> you said, because I cannot imagine that such a blanket statement is correct.
> Presumably, any potential problem would depend on what variables the `let'
> binds?
Of course.

-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997