Re: Removing unloaded functions from auto-mode-alist.

[Lute Kamstra]

David Kastrup <address@hidden> writes:

> Lute Kamstra <address@hidden> writes:
>
>> David Kastrup <address@hidden> writes:
>>
>> [...]
>>
>>> Well, the idea explored a bit later later was that "load" will
>>> record autoloads, but not do anything with them by itself, instead
>>> letting "provide" handle it.
>>
>> Ah, now I understand your post.  I think letting provide record
>> autoloads is a bad idea.  provide can occur anywhere in a file.  So
>> when provide records autoloads it won't record the autoloads that
>> get replaced after that position.
>
> No, the idea was that load initiates the recording of autoload data
> alright, but will throw the recorded data away at the end of the load
> unless a `provide' occured at its top level.  If the provide occured
> at the top level of the load, then the end of the load will tag all
> the functions with the autoload data, like do_autoload does now at the
> end of its load sequence.
>
> So the "provide" merely sets a flag, and this flag causes the
> encompassing load not to throw the collected previous autoload data
> away at the end of the load sequence, but use it for marking the
> changed functions with the old autoloads in their properties.
>
> Clearer now?

Yup.  (I hope so.  ;-))

But you want that autoloads are recorded in Fload, after loading the
file is complete, right?  That would be a complicated change, best
done after the release.

Lute.