Re: Purpose of jde-autoloads

Przemysław Wojnowski <[email protected]> writes:

> Hello everybody,
>
> I was thinking about purpose of autoloads and IIUC its sole purpose is to lazy 
> load parts of JDEE. But what for? Maybe 10-15 years ago it was speeding up 
> loading of JDEE, but now the difference is marginal.

No, it's purpose is to speed the lazy loading of *all* of JDEE. IIRC,
there may have been some aim to disconnect the different bits of JDEE
(so, yes, debugger and so forth), but that's a byproduct.

> The only function I would see in autoloads would be something like
> this: (defun jde-start () "Start JDEE." (require 'jde))

The jde-autoloads file should only contain autoload statements

(autoload jde-mode "jde.el" "I do Java" t)



> Rationale: If someone would install JDEE (e.g. from elpa) it wouldn't slow down 
> Emacs startup. But user could load it anytime using M-x jde-start when s/he 
> would like to open a Java project.
>
> What do you think about it? I nobody mind or answer by the end of the
> week I'll reduce jde-autoload to the one method.

jde-autoloads.el should be autogen anyway, from the ###autoload magic
cookies. Generally, every entry point to JDEE should be covered. As it's
a major mode, that is essentially just the major mode itself, and the
(add-to-list 'auto-mode-alist) line. I don't think that JDEE has any
other entry points.

If jdee becomes ELPA packaged (when it needs to be), jde-autoloads.el is
generated client side at install side anyway.

Phil

------------------------------------------------------------------------------
_______________________________________________
jdee-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jdee-devel