-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Daniel Quinlan writes: > [EMAIL PROTECTED] (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). yeah, I was hoping for the "pass rule code for rules with certain tflags into the plugin for substitution" approach as I mentioned before -- that doesn't require the plugin to delve into the Conf structure to do it. > 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. ah, that's a good point. that hadn't occurred to me... - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFCB/i5MJF5cimLx9ARAjZFAKC1PlK/1jLhtdESD4TQq8QL3TnKtQCfSubV gA6QHfieBiwF7SYuUoNuu+k= =PWDL -----END PGP SIGNATURE-----
