On Mon, Oct 04, 2004 at 03:34:12PM -0700, Justin Mason wrote:
> BTW, note that plugins *should* be able to push their own entries
> onto the $conf->{registered_commands} list. That is, in my opinion,
> much cleaner than the current parse_config() API, and may be worthwhile
> as a way for future plugins to do configuration.
Hey, that was my idea! ;)
Yeah, I was thinking that's the best way to do it. Since you don't unload a
plugin once its loaded, there's no reason not to push the config bits on the
array and let our standard code deal with the options.
The only issue is if the internal API changes, the plugins will stop
working... But the goal is to use the standard functions anyway, so evertying
will break no matter what if the API significantly changes.
--
Randomly Generated Tagline:
OK, enough hype.
-- Larry Wall in the perl man page
pgp858QQ2FU1n.pgp
Description: PGP signature
