Re: patch: g_[s]list_sort_udata, g_tree_new_udata


It seems like most of these objects (GHashTable, GTree, GSList, GList)
don't manage destroy functions for their data, so
that's why I didn't bother; I think it would be inconsistent with
most of the data structures in glib ...
(though admittedly its all a bit different than the attitude adopted
by, say, GClosure)

Thanks for committing that,

On 13 Nov 2000, Jonathan Blandford wrote:

> Also, I was going to add the GTree patch, but was curious what the right
> way to manage the udata memory is?  Should it just be up to the user to
> free, or do we want to do something else?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]