gEDA-dev: libgeda error reporting
Ivan Stankovic
ivan.stankovic at fer.hr
Mon Jul 2 15:34:49 EDT 2007
On Mon, Jul 02, 2007 at 12:35:12PM -0400, Ales Hvezda wrote:
> > While working on gattrib, I noticed that libgeda
> > prints errors and uses calls like fprintf(stderr, ...).
> >
> > So when you try to open up a nonexistant file in
> > a program using libgeda (gattrib in this case), you
> > get errors both from libgeda and from the program.
> > Is this intended?
>
> Originally intended, but should be removed or fixed now.
> libgeda calls should return error status and if necessary
> write something to the log.
Actually, I would rather avoid writing anything to
log files (or stdout/stderr) from libgeda, as this
seems better handled by programs using libgeda
functions.
I'll investigate GError, as suggested by Peter, and
see if I can come up with a reasonable patch.
--
Ivan Stankovic, ivan.stankovic at fer.hr
"Protect your digital freedom and privacy, eliminate DRM,
learn more at http://www.defectivebydesign.org/what_is_drm"
More information about the geda-dev
mailing list