Re: memory allocation/freeing
- From: Owen Taylor <owt1 cornell edu>
- To: Helge Hess <hh mdlink de>
- Cc: gtk-list <gtk-list redhat com>
- Subject: Re: memory allocation/freeing
- Date: 04 Mar 1998 13:38:07 -0500
Helge Hess <firstname.lastname@example.org> writes:
> I wonder who is considered maintaining memory with gtk.
> eg the function
Unfortunately, for returns it depends on the function. It should
be in the documentation, when there is documentation.
For arguments, GTK should never take ownership of the arguments,
although it may add an extra reference count if the argument
is a pointer to a reference counted object.
However, there are may be exceptions to this rule. I.e.,
gtk_tooltips_set_colors() (As pointed out recently)
These should be considered be bugs.
> gchar * gtk_editable_get_chars (GtkEditable *editable,
> gint start_pos,
> gint end_pos);
> returns a (gchar *) pointer. When is it allocated/deallocated ...
> Do I have to deallocate the pointer ?
> The same for setting:
> void gtk_editable_insert_text (GtkEditable *editable,
> const gchar *new_text,
> gint *position);
The text will be copied from Nnew_text.
> Are all pointers given into gtk_* functions considered to be copied ?
] [Thread Prev