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 tim.peters
Recipients amaury.forgeotdarc, mbandy, pitrou, tim.peters
Date 2010-02-25.22:25:15
SpamBayes Score 8.113924e-05
Marked as misclassified No
Message-id <1267136718.08.0.751533908567.issue8020@psf.upfronthosting.co.za>
In-reply-to
Content
Amaury, I have no real idea what your "No, the description above says it: ..." is a response to, but if it's to my point that obmalloc is not intended to be thread-safe, it's not addressing that point.  Any case in which another thread can affect a thread currently running in obmalloc is forbidden:  forbidden, not allowed, begging for undefined behavior, etc etc.

> Could we use an "inline" function instead of a macro?

If every C compiler on every platform Python runs on supports such a thing with exactly the same spelling, sure ;-)
History
Date User Action Args
2010-02-25 22:25:18tim.peterssetrecipients: + tim.peters, amaury.forgeotdarc, pitrou, mbandy
2010-02-25 22:25:18tim.peterssetmessageid: <1267136718.08.0.751533908567.issue8020@psf.upfronthosting.co.za>
2010-02-25 22:25:16tim.peterslinkissue8020 messages
2010-02-25 22:25:16tim.peterscreate