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 pitrou
Recipients asvetlov, christian.heimes, daniel.urban, eltoder, jcea, pitrou, python-dev
Date 2012-12-08.20:46:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354999569.54.0.936869538068.issue16602@psf.upfronthosting.co.za>
In-reply-to
Content
> I don't think there's a way to write PyWeakref_GET_OBJECT() in standard 
> C90 without double evaluation.

Agreed. We generally don't document whether our macros are compatible with side effects in parameters, and I think we'd like to keep it that way. People should simply avoid doing this kind of thing, as it's knowingly fragile, and trivial to avoid anyway.
History
Date User Action Args
2012-12-08 20:46:09pitrousetrecipients: + pitrou, jcea, christian.heimes, asvetlov, daniel.urban, python-dev, eltoder
2012-12-08 20:46:09pitrousetmessageid: <1354999569.54.0.936869538068.issue16602@psf.upfronthosting.co.za>
2012-12-08 20:46:09pitroulinkissue16602 messages
2012-12-08 20:46:09pitroucreate