On Dec 3, 2010, at 6:04 PM, Terry Reedy wrote:
> gc is implementation specific. CPython uses ref counting + cycle gc. A 
> constraint on all implementations is that objects have a fixed, unique id 
> during their lifetime. CPython uses the address as the id, so it cannot move 
> objects. Other implementations do differently. Compacting gc requires an id 
> to current address table or something.

It's somewhat unfortuante that python has this constraint, instead of the 
looser: "objects have a fixed id during their lifetime", which is much easier 
to implement, and practically as useful.

James

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to