The cleanest way i can think of would be to set the references to nil,
and call GC.start. This will not in every case collect the object
(because there may be something looking like a reference in some
register).
That's what we try, but with problems atm.
As an insane idea maybe you could use something like weakref to
channel all pointers through one object if you're program logic may
hold some unused references somewhere. (Though getting rid of the
unused references may make more sense).
At least realy interesting 
and yes we try to figure out where the
references might be.
[... code sniped ...]
Simon
Then maybe this is even a usable way, because if you proxy the objects
like this and after "destruction" someone accesses the proxied object
you'll get an exception with a usefull backtrace.
regards,
Brian
···
On 11/08/05, Kroeger Simon (ext) <simon.kroeger.ext@siemens.com> wrote:
> The cleanest way i can think of would be to set the references to nil,
> and call GC.start. This will not in every case collect the object
> (because there may be something looking like a reference in some
> register).
That's what we try, but with problems atm.
> As an insane idea maybe you could use something like weakref to
> channel all pointers through one object if you're program logic may
> hold some unused references somewhere. (Though getting rid of the
> unused references may make more sense).
At least realy interesting and yes we try to figure out where the
references might be.
> [... code sniped ...]
Simon
--
http://ruby.brian-schroeder.de/
Stringed instrument chords: http://chordlist.brian-schroeder.de/