Re: About node references

Dimitre Novatchev wrote:

  Hi,

> I realize that until now I have presented this idea only very
> vaguely. Here is a first try at a more consistent presentation.

> A "Ref" is an object that has two parts: a reference (memory
> reference) and an associated string key. So, a Ref can be
> represented by the pair:

> [...]

> Also, when all Refs to an item are destroyed, this item can be
> garbage-collected, thus no "leakage" is to occur due to using Refs

  I must admit I am a bit lost.  If items can be garbage-collected
when there is no more Ref "pointing" to them, what's the point to
have a copy function?  And if the Ref object must be kept to ensure
it is still dereferenceable, what is the string used for?

  I guess I missed something obvious here, but I can't tell what.

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/