bug#10982: documentation bug eval-after-load

bug#10982: documentation bug eval-after-load

[Le Wang]

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

Hi on this page:

http://www.gnu.org/software/emacs/manual/html_node/elisp/Hooks-for-Loading.html#Hooks-for-Loading

> library can also be a feature (i.e. a symbol), in which case form is
evaluated when (provide library) is called.

Then on this page
http://www.gnu.org/software/emacs/manual/html_node/elisp/Named-Features.html

> This function announces that feature is now loaded, or being loaded, into
the current Emacs session. This means that the facilities associated with
feature are or will be available for other Lisp programs.

So two issue come up:  should symbol even be supported by `eval-after-load`
if the feature might not be finished loading?  If it has to be kept for
backward compatibility, documentation should explicitly say don't use
symbol because the feature might not be finished loading.

-- 
Le

[-- Attachment #2: Type: text/html, Size: 1205 bytes --]

bug#10982: documentation bug eval-after-load

[Glenn Morris]

Le Wang wrote:

> So two issue come up:  should symbol even be supported by `eval-after-load`
> if the feature might not be finished loading?  If it has to be kept for
> backward compatibility, documentation should explicitly say don't use
> symbol because the feature might not be finished loading.

The version of eval-after-load in the trunk handles this better, so that
even if provide is not at the end of the file, the eval-after-load forms
do not run until the file has finished loading.

What is the second issue?

bug#10982: documentation bug eval-after-load

[Le Wang]

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

On Sat, Mar 10, 2012 at 1:40 AM, Glenn Morris <rgm@gnu.org> wrote:

> Le Wang wrote:
>
> > So two issue come up:  should symbol even be supported by
> `eval-after-load`
> > if the feature might not be finished loading?  If it has to be kept for
> > backward compatibility, documentation should explicitly say don't use
> > symbol because the feature might not be finished loading.
>
> The version of eval-after-load in the trunk handles this better, so that
> even if provide is not at the end of the file, the eval-after-load forms
> do not run until the file has finished loading.
>
> What is the second issue?
>

Sorry, the two issues are documentation and implementation. Clearly the
implementation has been fixed, I just checked that the documentation is
also correct.  Please close this bug.

-- 
Le

[-- Attachment #2: Type: text/html, Size: 1118 bytes --]