gEDA-dev: libgeda error reporting

[Steve Meier]

2.4 supports GLog and GError

2.6 added g_log_set_default_handler

Steve M.


On Mon, 2007-07-02 at 16:49 -0400, Stuart Brorson wrote:
> Ummm, GError, GLog, or what have you.... what dependencies do they
> introduce?  Are they part of the stock GTK-2.4?
> 
> Stuart
> 
> 
> On Mon, 2 Jul 2007, Steve Meier wrote:
> 
> > I would suggest looking into GLog for logging.
> >
> > Steve M.
> >
> >
> > On Mon, 2007-07-02 at 21:34 +0200, Ivan Stankovic wrote:
> >> 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.
> >>
> >
> >
> >
> > _______________________________________________
> > geda-dev mailing list
> > geda-dev at moria.seul.org
> > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
> >
> 
> 
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev