"John Myers" <[EMAIL PROTECTED]> writes: > SpamAssassin is in serious danger of contracting "plugin disease." > The fact that people are seriously talking about making > PerMsgStatus::check() a plugin is Exhibit A. The idea is itself a > reduction to absurdity.
No, moving most of check() to where the check function can be placed in different plugins is a very good move. This allows us to provide options for how check() works. For example, trying out Bayesian decision-making, decision tree for faster operation, etc. I think you might have some good points about plugin-izing eval-tests. I think something needs to be done to improve the maintainability and cross-version-compatibility of the EvalTests.pm module, but I'm not sure what it is yet. Theo is doing a valuable experiment and I think he has a very good shot of ending up somewhere that makes sense. Let's give him some time to work it out before rejecting it. Daniel -- Daniel Quinlan http://www.pathname.com/~quinlan/
