Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: Justus Winter <4winter@informatik.uni-hamburg.de>
User-Agent: alot/0.2-372-g8f06
To: notmuch mailing list      <notmuch@notmuchmail.org>, 
Date: Sun, 29 Jan 2012 18:01:24 -0000
Message-ID: <20120129180124.23430.33656@thinkbox.jade-hamburg.de>
Subject: error handling and stderr
Date: Sun, 29 Jan 2012 19:01:24 +0100
Precedence: list

Hi notmuch developers,

currently there is no way to determine why opening a database using
notmuch_database_open fails. I suppose that this is a problem for all
functions returning a pointer, but it is especially problematic for
this function since one cannot distinguish between a temporary failure
(someone else opened the db read/write) and a configuration problem
(wrong path).

This is a real problem for providing sensible feedback to the user.

And writing an error message to stderr is a sensible thing to do if it
is done in a command line utility but doing so within a library is a
severe problem for any curses frontends and is generally considered a
bad practice.

For the record, libabcs README[0] agrees with me on both aspects.

Since fixing this means breaking the api we need to discuss this
thoroughly and identify all the functions involved.

Users of the python bindings won't be affected by an api change like
this since we're converting any error code to exceptions anyway.

Cheers,
Justus

0: https://git.kernel.org/?p=3Dlinux/kernel/git/kay/libabc.git;a=3Dblob_pla=
in;f=3DREADME