#1 make autoload idempotent

open
nobody
None
5
2006-04-29
2006-04-29
Thibaut
No

Hello,

currently, issuing
autoload, ifile, vari
where VARI has already been defined as an autoload
variable yields an error:
ERROR (*main*) autoload variable must be nil initially

This makes it harder for e.g. a user to install a more
recent or modified version of a plugin that is already
installed system-wide.

I think the right behavior would be for the second
definition to override the first one, perhaps with a
warning when the new autoload does not refer to the
same IFILE.

This occured to me as I was trying to design a
reasonable framework for installing plugins through
mixed systems, i.e. the OS-level package manager and
yorick's pkg_mngr, and into several trees (e.g. OS
level and user level). I won't detail here, but it
looks like this issue with the autoload mechanism is
the last remaining difficulty towards a robust and
user-friendly system.

Regards, Thibaut.

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks