[608] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Why g_print ?
daemon@ATHENA.MIT.EDU (Werner Koch)
Thu Jul 31 06:01:57 1997
Date: Thu, 31 Jul 1997 11:18:46 +0200
From: Werner Koch <wk@isil.d.shuttle.de>
To: gtk-list@redhat.com
In-Reply-To: <199707310238.EAA12062%timj@psynet.net>; from Tim Janik on Thu, Jul 31, 1997 at 04:38:13AM +0200
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
On Thu, Jul 31, 1997 at 04:38:13AM +0200, Tim Janik wrote:
> regarding g_malloc(), g_free() and siblings, these functions are much safer
> than thier libc equivalences. e.g. g_free() just returns if called with
> NULL, i even rely on that behaviour in my apps.
^^^^^
That's required by Standard C, see also free(3).
Werner
--
Werner Koch, Duesseldorf - werner.koch@guug.de - PGP keyID: 0C9857A5
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
