> |
> |I want the object to be destroyed regardless of how many
> |references there are to it when the WM_DESTROY message
> |is received by object 'x' (which is the window).
> 
> Hmm, for example, IO objects are NOT destroyed on close(), even though
> any operation on them are useless.  They raise exceptions for
> operations after closing.  I think it's enough for treating
> WM_DESTROYed Window objects as well.
> 

Matz, it sounds like this has potential to be a serious memory leak.
Would that be a correct statement?  If so, can I interact with the
garbage collector to collect these objects? or something like that...???

Thanks.
Bryce