http://www.vim.org/scripts/script.php?script_id=1464

Enjoy!

I wrote a little bit about my earliest steps in Ruby on Rails in June. Today, I will start a series of posts that describe what I’ve done with it lately. Also, I’ll slowly be introducing Adobe Flex development into my setup and I’m hoping these two…

For me, a weak-reference is really usefull for Events.

Imagine you have a longliving objects, which has severeal interessting events for you.

Imagine a class/object that ist not that long living. So if you registerd a event from the “long-living” object, your short living object would not be garbagecollectet because it holds a “strong” ref. You have to unregister the event, for making your short-living object ready to be G-collected.

If there were only weak references, the G-Collector could say, fine your “short-living” class has only weakers so i G-Collect it.

That is my big advantage of Weakreferences. (I dont see the point from translating weakers to strongers, because i have to decide in my implemenation if my short-living object would “keep” alive or not.)

(Im just learning and try to unterstand your listened advantages).

RealWorld example;

Your “Car” Object listens to a global “GPS-Satellite” object and wants to now when he bypasses the border of the country. (the Country_Changed event

So if nobody uses this car, the car has not to listen to the satellite (becuase its useless).

If the car would “weakly” listen to this event, and there is nobody who is using this car (using this car would mean there is a strong ref to it), he could be G-Collected (whatever this means in this sample).

If he does “strongly” listen to the satelite, he makes it self “unCollectable”. –> Untill the GPS-Satellite would be destroyed itself which should not happen that often.

(You cant bash, destroy stomp the car) which will cause memory-leaks.

Hm

Greets

Anonmyous

Hmm i think a weak reference would not prevent you to recreate a G-collected object.

From the other post you describe.

“If the user were to open that screen up again, you could check the Target property of the WeakReference to see if the large object has been garbage collected yet. If the Target property is not null, you can create a new “strong reference” by setting a normal”.

If the target property is not null, there was an existing strong ref, and the weak-ref was useless because the object would not be garbage collected anyway. If the target property is null, your object has been collected and you have to recreate your object.

“You might keep a WeakReference around after you set the “strong reference” to the object to null when the user cancel’s out of the screen.”

If you set the strong reference to null, and you have a weakreference to it, the object is garbage collected.

So wheres the advantage in your example?

Thanks for the great keyboard tips, though!