|
From: | Lars Hansen |
Subject: | Re: void variable |
Date: | Mon, 26 Jul 2004 17:12:57 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 |
I agree that the manual should direct people to autoload variables used by autoloaded functions if programs might want to bind them. But I also think it should be carefully explained what can happen if a non-autoloaded variable is bound. We cannot be sure all relevant variables are autoloaded.Actually, on second thought I am not that sure anymore. Several variables, that are important enough for people to want to bind them, are not autoloaded. The situation is potentially dangerous, as we saw with wdired. So we should warn about it _somewhere_. Either the manual or the docstrings or both. The manual should direct people to autoload variables used by autoloaded functions, if programs might want to bind them.
What about:1. Docstrings of defvar, defcustom and let briefly explain what happens if a local binding exist when defvar or defcustom is evaluated _and_ mention the autoloading pitfall. 2. Manual explain the same a bit more elaborate and direct people to autoload relevant variables to avoid the pitfall.
[Prev in Thread] | Current Thread | [Next in Thread] |