Hi,
>> Binary incompatible and breaking would be silently data corruption or
>> no longer starting due to missing symbols etc.
>
> pseudocode:
>
> ret = sane_start()
> if(ret){
> die("bad status");
> }
>
> that works in sane 1.0, and fails in sane 1.1, both with the original
> binary, and with a new binary compiled against 1.1 headers. Thus, it
> is both a source and a binary incompatibility, which calls for a
> soversion bump. We knew this going in, yet some folks were very much
> against the bump, so we split hairs, and tried to say it was not big
> enough to matter. That was a foolish choice, which drove some
> developers away. I take a great measure of personal responsibility for
> that.
I know. But still "lamp not warm" is in the area of "paper jammed",
"cover open" - try again later.
Nothing too incompatible here, just before it stalled the whole program
infinitely and now the user gets a notification.
From my point of few it is not too much of a deal. So bump or name it
SANE 2.0
I could not care less ...
Yours,
--
Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
