Dan Sugalski wrote:
We aren't doing refcounting. We are continuing with the current scheme as implemented. We're not looking to do anything to change that scheme except perhaps implementing a generational or continuous garbage collection system.
Last I checked Python used refcounting... How can we claim to support Python without refcounting?
Easily--Python does *not* claim timely destruction. I've asked Guido, and he's been pretty adamant about that.
> Unless Larry mandates dead-on timely destruction for Perl 6, and he's > told me end of block or end of sub is fine so far, refcounting isn'tan option.
I wandered across some C# docs that describe a method to both work with exception handling and insure timely destruction... Its nothing new. And it only garauntees the timely destruction at the end-of-block, not when last reference is released. But it is interesting to see how others do it.
Couldn't parrot divorce itself from the timely destruction issue and punt that to the higher level languages? Require the HLL or programmer to call an explicit destructor, and have parrot's idea of timely destruction be limited to the HLL forcing garbage collection...
That's what the lazysweep support does. -- Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
