Re: [Swarm-Support] Time efficiency of at$createActionTo$message

[Jason Alexander]

> > The thing is as the model progresses the argument day becomes 
> > progressively
> > larger.
> If this scheduling happens again and again, you'll be leaking 
> Selectors like crazy.
> Java/Swarm objects are live until dropped (they have objects on the C 
> side that are pinned-down, and the garbage collector can't touch > them).

Just out of curiosity...

Why doesn't Swarm use a retain count mechanism for preserving objects 
(like in OS X) instead of an explicit drop mechanism?  Is it just an 
artifact of design, or was their a principled reason for it?

Jason