getopt-long [was: -t output]

[David Relson]

At 10:41 AM 7/30/03, Joerg Over Dexia wrote:

>I'd second that. It probably does affect a lot of users, me for
>example, but if you don't dare to make valuable changes with a
>version 0.13 you'll have a lot of overhead and gunk once you're
>going 1.0. And you'll probably be sorry. So my call'd be:
>Whenever it's making broad sense, topple/build/change it *now*.
>(In that line of thought, I'd rather have an exit value of 0 for
>ham, so that everything <> 0 would be either spam (or unsure) or
>an error. It just feels right (for me). I'm probably alone there,
>so I'll patch it, but what I want to say is: If a majority here
>thought that a wise idea I'd recommend changing it as soon as
>possible although that'd break about every script in production
>out there. That's what 0.x versions are for.)
>
>Greetings, jo
>--

Hi Joerg,

Since bogofilter's purpose is to detect spam, having exit code 0 mean 
"Yes.  It's spam." works well.

Your patch will be simpler with the next release as the exit codes are 
defined with an "enum" in file common.h

David