Author sbt
Recipients Sebastian.Noack, asvetlov, christian.heimes, jyasskin, kristjan.jonsson, mklauber, neologix, pitrou, sbt
Date 2012-10-02.10:59:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349175595.63.0.761929152847.issue8800@psf.upfronthosting.co.za>
In-reply-to
Content
> The unlock operation is the same, so now you have to arbitrarily pick one 
> of the "lockd" and chose release().

That depends on the implementation.  In the three implementations on

    http://en.wikipedia.org/wiki/Readers-writers_problem

the unlock operateration is different for readers and writers.

> Why take a construct which is essentially a lock that can be acquired in two 
> different ways and force people to view it as separate objects?

I don't see why writing

    lock.exclusive.acquire()

really requires a different way of thinking compared to writing

    lock.exclusive_acquire()

or

    lock.acquire_exclusive()
History
Date User Action Args
2012-10-02 10:59:55sbtsetrecipients: + sbt, pitrou, kristjan.jonsson, christian.heimes, jyasskin, asvetlov, neologix, mklauber, Sebastian.Noack
2012-10-02 10:59:55sbtsetmessageid: <1349175595.63.0.761929152847.issue8800@psf.upfronthosting.co.za>
2012-10-02 10:59:55sbtlinkissue8800 messages
2012-10-02 10:59:55sbtcreate