Re: autoloads for safe-local-variables (was: allout patch - moresafe-local-variables, plus autoloads)

["Stuart D. Herring" <herring@lanl.gov>]

>> +;;;###autoload
>> +(put 'allout-show-bodies 'safe-local-variable t)
>
> In my commits, I've put in the same line...
>
> ;;;###autoload(put 'page-delimiter 'safe-local-variable t)
>
> ... like it is done e.g. in `code-pages.el':
>
> ;;;###autoload(autoload-coding-system 'cp437 '(require 'code-pages))
>
> Which style is preferable?

The first style leaves the code as active code, executed when the file is
loaded.  The second style generates no code in file.elc but only in
loaddefs.el.  So if it's logically part of the library, you want the first
form; if it's some sort of reference to the library, but not really part
of it, like the code-pages example, you want the second one.  For a simple
(put ...) it probably doesn't matter too much, but it probably would
interact better with, say, unload-feature to use the first one.

This gets me thinking, though -- does unload-feature remove plists from
symbols it's dumping?  If so, shouldn't it not remove the
`risky-local-variable' property if any?  Apologies if this is just
confusion.

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.