Re: gobject destructor


I am always impressed by the prompt and helpful response to questions
on this list.  Thank you very much for this.

On Tue, May 11, 2004 at 11:00:50AM +0800, James Henstridge wrote:
> This is not unexpected behaviour.  The "destroy" signal is not the 
> equivalent of a deconstructor (for that, you want "finalize"). ...
Ok, I see.

> So if your widget can't handle destroy being called multiple times, then 
> it is a bug in your widget.  You probably want to move some of the code 
> you currently have in the "destroy" handler to a "finalize" handler.
Is it guaranteed, that after the first call to destroy only destroy
and finalise calls will happen?

Thank you,

Attachment: signature.asc
Description: Digital signature

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