gabriele renzi wrote:

>il Tue, 20 Jul 2004 02:49:00 +0900, Mark Sparshatt
><msparshatt / yahoo.co.uk> ha scritto::
>
>  
>
>>I think changing to a reference counting GC system would change the 
>>behaviour of the program, since it would change when an object is collected.
>>
>>I know that this subtlety has caused problems for people moving from 
>>CPython (Which uses reference counting) to Jython (which uses mark and 
>>sweep)
>>    
>>
>
>CPython does reference count, while JPython should use the jvm's GC.
>
>This problem may appear when going from refcount to gc, cause you may
>expect that an object gets gc'ed at the end of a code block (in ref
>count)while it does not (gc).
>OTOH, when you're expecting a general GC behaviour you don't make
>assumptions about the automatic deletion of an object, so this problem
>does not arise. At least, I think. 
>
>
>
>  
>
The problem would come if someone did release an alternate 
implementation of Ruby with reference counting GC. Then if people who 
were used to alternate Ruby moved to standard ruby they might expect the 
same behaviour, and assume it's a bug when standard ruby behaves 
differently.

--
Mark Sparshatt