[Seaside] Object Destruction (or how to destroy instance)
boris at deepcovelabs.com
Wed Sep 12 08:53:54 UTC 2007
Inspect those instances and lookup refrences to them via the menu bar. They will be collected only if no one has a hard reference to them.
(Sent from a BlackBerry)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: seaside at lists.squeakfoundation.org <seaside at lists.squeakfoundation.org>
Sent: Wed Sep 12 01:43:01 2007
Subject: [Seaside] Object Destruction (or how to destroy instance)
Maybe this question is more about smalltalk than about seaside, so
In my reporting application i have following problem:
Some components of my seaside application working with Business Model
I do it to have ability to revert changes. If user wants to save
changes, database collection
just replaces old business objects with their updated copies. So
everything works just fine.
But there is a question: If i ask VisualWorks to show all instances
of Business Model, i can also
see old models, which were replaced by newer ones in DB collections.
So some instances "just flying
in the air". How can i destroy them (something like calling
destructor in C++). Or thats a not a problem and
they will be killed by garbage collector sometime? If so, when they
will be killed?
Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside