[592] in The GTK GIMP ToolKit mailing list archive

home help back first fref pref prev next nref lref last post

[gtk-list] Re: Why g_print ?

daemon@ATHENA.MIT.EDU (Elliot Lee)
Wed Jul 30 21:41:00 1997

Date: Wed, 30 Jul 1997 21:27:39 -0400 (EDT)
From: Elliot Lee <sopwith@redhat.com>
To: gtk-list@redhat.com
In-Reply-To: <Pine.LNX.3.96.970730171909.27493M-100000@slow>
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com

On Wed, 30 Jul 1997, Ian Main wrote:

> This one question still haunts me :)  How come we have g_print, g_malloc,
> g_strdup and fellow glib functions ?

<wild stab>Because they are more portable, more debuggable, and more
featureful than the system ones. For example, I think g_error() will
actually pop up a window if you use it with gtk.

-- Elliot					http://www.redhat.com/
What's nice about GUI is that you see what you manipulate.
What's bad about GUI is that you can only manipulate what you see.

--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null


home help back first fref pref prev next nref lref last post