Modularity

[Matthias Andree]

Adriano Nagelschmidt Rodrigues <anr at estadao.com.br> writes:

> Matthias Andree writes:
>> Not quite. While -f and -r (Fisher-Robinson) and (Robinson) share their
>> registration, -g (Graham) uses a different registration procedure, and
>> the filter algorithm is queried for parameters.
>
> Can they be made common (eg a superset of the information is stored in the
> dbs)?

A useful suggestion, I had also thought about storing information WHAT
is in the DB in WHAT format in the DB itself. It would require a special
"initialize data base mode" though, and it might get in the way of the
user when there is no /compelling/ reason to do so.

>> OTOH, these programs share a lot of common code (like the tokenizer,
>> data base, and recently, MIME stuff), so that we'd exchange like 10
>> percent of these programs with the other 90% being linked in unchanged.
>
> What about a libbogo.{so,a}?

.so won't happen before libtool is fixed for MacOS X 10.1 and newer.

.a is what we do now - at build time.

> Yes, for example, when I decided to add the '-f' switch last night, it wasn't
> clear to me if I would have compatibility problems with the existent ham/spam
> databases and if I needed to use it with [nNsS].

Whether these are real problems, is a moot point, -g allows a token to
be registered up to four times per mail, while -f and -r allow a token
to be registered only once per mail.

-- 
Matthias Andree