it'd also be kick-ass if this plugin could auto-upgrade when the BerkeleyDB module is upgraded: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4416 ;)
re coding style: http://wiki.apache.org/spamassassin/CodingStyle --j. On Tue, Dec 16, 2008 at 16:36, Michael Alan Dorman <[email protected]> wrote: > On Tue, 16 Dec 2008 09:56:04 -0600 > Michael Parker <[email protected]> wrote: > >> Copying the t-tests for your particular implementation is a good >> start. You may need to adjust them a bit and feel free to expand >> them to test even more functionality. > > Sure. Is there any need for me to bother with SVN, at least initially? > It seems to me that working against 3.2.5 should be adequate, but I > don't pretend to know for certain. > >> Then you have the masses/bayes-testing directory that will give you >> some help. Inside that directory is the benchmark tool that you can >> use to test the speed of your implementation against others. > > Ah, this I probably wouldn't have noticed right away, which would have > been a shame since what I really want is for this to be screamingly > absurdly fast. > >> Looking forward to seeing what you've come up with. > > I've got everything done except restore_database at this point, but > it's been about six hours of coding and visual inspection of same; > hence the need for some good test code. :) > > I suspect that there will have to be some discussion of some particular > choices I made--for instance, if they're tieing in R/O mode, I will > just return 0 if _any_ tables are missing, stuff like that. So it's > maybe stricter in some ways. > > Also, is there a particular style guide that SA follows? Maybe with a > perltidy profile I can use to reformat to it? > > Mike. > >
