>> Ok, but I picked 0 means error and 1 means ok as is standard in most >> perl modules and the rest of our code. Lets this type of thing work:
I agree 0 generally means error, although Michael is correct in pointing out it really means false. There are cases where you want to use a negative number or undef to indicate an error, though. The related return code issue I wanted to discuss, but I didn't get to in my earlier email is that it would be nice if we had a way to indicate that a rule did not run (which is different than saying it didn't match). We could use that information to potentially get rid of score sets. Each rule could then only have two potential scores: "hit" and "not run" (the third state of "not hit" always has a score of zero for simplicity). Daniel -- Daniel Quinlan anti-spam (SpamAssassin), Linux, http://www.pathname.com/~quinlan/ and open source consulting
