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 kristjan.jonsson
Recipients benjamin.peterson, brett.cannon, georg.brandl, kristjan.jonsson, larry, loewis, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner
Date 2014-02-07.10:50:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391770256.95.0.791952840917.issue20440@psf.upfronthosting.co.za>
In-reply-to
Content
These macros work as assignment with builtin decref, 
i.e. a smart replacement for =
We could resolve this by calling them Py_ASSIGN Py_XASSIGN
and having complementary macros Py_STORE/Py_XSTORE that will incref the new value.

However, with an added incref, does the X apply to the source or the target?
I wonder if we need the X variants in these macros.  Once you are doing things like this, why not just use X implicitly?  An extra pointer test or two is unlikely to be a performance problem in the places you might use them.

Anyway, I'll be adding this to the internal api of stackless because it is tremendously useful.
History
Date User Action Args
2014-02-07 10:50:57kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, brett.cannon, georg.brandl, rhettinger, pitrou, vstinner, larry, benjamin.peterson, skrah, serhiy.storchaka
2014-02-07 10:50:56kristjan.jonssonsetmessageid: <1391770256.95.0.791952840917.issue20440@psf.upfronthosting.co.za>
2014-02-07 10:50:56kristjan.jonssonlinkissue20440 messages
2014-02-07 10:50:56kristjan.jonssoncreate