Re: gerror.c revisited

[<dom recoil org>]

Quoting Darin Adler <darin@eazel.com>:

> > (We should really add g_fatal() that prints a message and does exit(1)
> > without the abort).
> 
> I wholeheartedly agree. I think many uses of g_error are actually candidates
> for g_fatal. The latter would be for errors with a runtime cause rather than
> programmer errors.
> 
> Of course the names still don't make clear which is appropriate to use when.
> 

I disagree.  Runtime errors should be handled (and there's no excuse for not
handling them with the GError methods).  If it is a program ending problem,
a dialog should appear instead of a message to stderr.

Dom.