-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Theo Van Dinter writes:
> 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.
yeah. plus keeping backwards compat APIs around, when it won't have an
effect on performance, is not a big problem anyway. (e.g. calling into
parse_config() can still take place if a line is unhandled, because that
should never happen in the non-error case anyway.)
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFBYd1fQTcbUG5Y7woRArOvAKDgNsfwMJE4pgfLdovdFsVOUZzqBgCfaY/X
r/rVludMQwLVK0LMbmO0RSY=
=IAsT
-----END PGP SIGNATURE-----
