Author Albert.Zeyer
Recipients Albert.Zeyer, neologix, pitrou, r.david.murray
Date 2013-02-26.13:01:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361883680.64.0.364878582837.issue17263@psf.upfronthosting.co.za>
In-reply-to
Content
> Wouldn't it be better to expose and re-use the HEAD_LOCK and HEAD_UNLOCK macros from pystate.c?

The macro-names HEAD_LOCK/HEAD_UNLOCK irritates me a bit. Protecting only the head would not be enough. Any tstate object could be invalidated. But actually, it protects any modification on the list (both in tstate_delete_common and in new_threadstate), as far as I see it.

But yes, it would be a good thing to export this locking functionality so other code can use it.
History
Date User Action Args
2013-02-26 13:01:20Albert.Zeyersetrecipients: + Albert.Zeyer, pitrou, r.david.murray, neologix
2013-02-26 13:01:20Albert.Zeyersetmessageid: <1361883680.64.0.364878582837.issue17263@psf.upfronthosting.co.za>
2013-02-26 13:01:20Albert.Zeyerlinkissue17263 messages
2013-02-26 13:01:20Albert.Zeyercreate