program code [was: [cvs] bogofilter/src ...]

[Tom Anderson]

----- Original Message ----- 
From: "David Relson" <relson at osagesoftware.com>
>
> Yes these things are spread out.  We also build 4 major programs --
> bogofilter, bogoutil,  bogolexer, and bogotune.  They share many
> options, but each has some of its own.  The result is 4 sets of option
> definitions, parsing routines, and help routines.
>
> So be it.

Why not put these routines into a common library?

> to C code which was then compiled.  Consequently anything doable in C++
> can be done in C, if one cares to make the effort.  AFAICT, we're

True of any Turing complete language ;-)

> The fact that it _can_ support 4 distinct database systems (BerkeleyDB,
> tdb, qdbm, and sqlite) indicates that _something_ in the datastore
> architecture is done right.  Of course it could also be argued that
> supporting more than 1 database backend is going off on a tangent.

Can individual database code be split into seperate libraries?  Then instead 
of tangents, they will be seperate projects.  Just make sure they all 
support the same basic API.

> We live in a complicated world where 1 size doesn't fit all -- unless
> you do some customizing.

Or use an interpreter ;-P

Tom


_______________________________________________
Bogofilter-dev mailing list
Bogofilter-dev at bogofilter.org
http://www.bogofilter.org/mailman/listinfo/bogofilter-dev