Jesus Climent wrote: > On Sat, May 11, 2002 at 06:23:19PM +0200, Arpi wrote: > >>Hi, >> >> >>>I will add the code to the CVS and put a mark that is still beta >> > code. > >>where should i send the updates later? >>i mean i see no sense of having it in your cvs, while the developed > > version > >>is here... > > Usually patches, so far, go to the mailing list. > >>>BTW, what is the license of the code? GPL? >> >>same as spamassassin - dunno what :) >>i don't care of the liceses > > OK. > > Anyone's comments about the upload of the c code in the cvs?
I have a suggestion... If it's really that much faster, we should use a better approach. 1. Create a libspamassassin in C. 2. Create an XS interface to libspamassassin. The C code should do all the loading and parsing of config files, and all the regexp work, and probably the parsing of emails. 3. Leave the eval tests in Perl. 4. Create a small C program that can call libspamassassin on its own, but not do the eval tests. Ultimately I think this is a better solution for everyone, and means we all work together rather than confuse people with separate projects (and Arpi you should know all about that ;-) Matt. _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
