Because in the end that memory also needs to be freed via g_free, does it not? 
That I can only do by defining a custom destructor on it that calls g_free to 
deallocate. And to be sure that nowhere accidentally somebody copies the 
pointer and then the destructors causes a double-free, I also define a custom 
=copy hook.

Reply via email to