Re: g_*printf() (Was: gtk+-1.1.6 report)

[Aaron Digulla <digulla wi-pc44 fh-konstanz de>]

Quoting Sebastian Wilhelmi (wilhelmi@ira.uka.de):

> > Along these lines, I'd suggest a "out-of-memory" hook. The standard hook
> > should abort the program. The reason behind this is that the program
> > should print a meaningful error when it runs out of memory but most people
> > don't want to add a check after every invokation of g_printf_new().
> > (and that should be g_sprintf_new() :-)
> As mentioned earlier, g_strdup_printf does, what is wanted, as for the
> hook, glib never returns on memory errors, but simply aborts. As I tried
> to explain earlier, this is a good thing (i.e. to simply abort and not
> provide a callback in case of memory shortage; see thread "[gtk-list]
> 1.1.5 g_timer_new bug!")

Does that mean one can't write reliable applications with GLib/Gtk ?

--
Aaron "Optimizer" Digulla             Team AMIGA     AROS Head of Development
Author of XDME, ResTrackLib, CInt.		       <http://www.aros.org/>
"(to) optimize: Make a program faster by improving the algorithms rather than
by buying a faster machine."