Re: Freeing gerrors



On Tue, 2010-07-13 at 10:23 +0200, Xabier Rodriguez Calvar wrote:
> The other way around, you force the client to free it, so you change
> the
> possible segfault for a possible leak (I won't enter to discuss if it
> is
> better to have an early segfault than a late leak). With this option
> it
> is easier to propagate the error with g_propagate_error.
> 

For what I've seen so far, seems the common way is the client freeing
the error, not the caller.

Question comes to be sure which way should be used to make sure we are
following it in all framework.

	J.A.




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