Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
With reference counting there's no inherent need for a single pass (or an elaborate way to work around the need for one).
Refcounting is fine...
Posted Aug 21, 2011 8:39 UTC (Sun) by khim (subscriber, #9252)
With refcounting you still must think about objects lifetime. Thus you still will create sane designs because you must make sure you'll not create loops. But full GC encourages "don't know and don't care when this object will be removed" designs - and these can only be fixed with full rewrite.
Posted Aug 31, 2011 14:25 UTC (Wed) by nix (subscriber, #2304)
Java is new Tk
Posted Aug 27, 2011 18:30 UTC (Sat) by BenHutchings (subscriber, #37955)
Reference counting can also result in long pauses due to cascading destruction. In fact, it can be worse than incremental GC in this respect.
Posted Aug 27, 2011 23:47 UTC (Sat) by andresfreund (subscriber, #69562)
Posted Aug 28, 2011 23:03 UTC (Sun) by foom (subscriber, #14868)
There's a reason that Python introduced the "with" statement: to allow for easily-written *actually* predictable resource closing.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds