Re: svn commit: r151753 - spamassassin/trunk/lib/Mail/SpamAssassin/Plugin.pm

[Justin Mason <jm...@jmason.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


quinlan@apache.org writes:
> +Note: there are no guarantees that the internal data structures of
> +SpamAssassin will not change from release to release.  In particular to
> +this plugin hook, if you modify the rules data structures in a
> +third-party plugin, all bets are off until such time that an API is
> +present for modifying that configuration data.

... that makes the new plugin API sound quite a bit less useful ;)
what's it being added for?

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFCB+ApMJF5cimLx9ARAi4UAJoCiPFUCnirR+kOSXdqQbfZubEwrgCgnn+H
Sp6mR0k4rM/hIm8DEIToeVw=
=5wek
-----END PGP SIGNATURE-----

Re: svn commit: r151753 - spamassassin/trunk/lib/Mail/SpamAssassin/Plugin.pm

[Daniel Quinlan <qu...@pathname.com>]

jm@jmason.org (Justin Mason) writes:

> ... that makes the new plugin API sound quite a bit less useful ;)
> what's it being added for?

ReplaceTags.

I hope to eventually clean up the internals and make it okay after 3.1,
but it's just a bit too hairy right now to feel okay about making the
API usable for random third-party plugins (it's fine as long as the
integrator checks compatibility).

The API is still generally useful if you have *anything* to do at end of
parsing (for example, tying a DB as in accessdb), stuff that doesn't
involve internal APIs.

Daniel

-- 
Daniel Quinlan
http://www.pathname.com/~quinlan/