This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients Mark.Shannon, amaury.forgeotdarc, benjamin.peterson, brett.cannon, dmalcolm, ilblackdragon, jcea, larry, lemburg, mark.dickinson, vstinner
Date 2013-03-31.22:30:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5158B91F.6040306@egenix.com>
In-reply-to <1364758189.59.0.0992026014456.issue17206@psf.upfronthosting.co.za>
Content
On 31.03.2013 21:29, Larry Hastings wrote:
> 
> Larry Hastings added the comment:
> 
> For the record: I care.  Generally speaking CPython is a lovingly
> crafted source tree, and the choices its architects made are nearly
> always sensible and well-reasoned.  When I see things like this, things
> that seem kind of dumb on first glance, I worry that we're missing
> something.

Did someone test the patch on a use case where the performance of
this macro matters a lot ? E.g. deallocating large lists or
dictionaries.

Todays CPUs have plenty of registers available, so it's possible
that the patch actually speeds up things, since the decref'ed
variable may well be an indirect reference. At the time Py_DECREF
was written, registers were precious golden flasks, only to be
filled with the most valuable of things ;-)

Just want to be sure we're not missing something...
History
Date User Action Args
2013-03-31 22:30:58lemburgsetrecipients: + lemburg, brett.cannon, jcea, amaury.forgeotdarc, mark.dickinson, vstinner, larry, benjamin.peterson, dmalcolm, Mark.Shannon, ilblackdragon
2013-03-31 22:30:58lemburglinkissue17206 messages
2013-03-31 22:30:57lemburgcreate