Antoine Pitrou <pit...@free.fr> added the comment: > In this case, "acquire" isn't ambiguous. All the other lock types > actually acquire a write lock, so it makes sense to have the operation > with the same name they use also acquire a write lock on this object.
Well, it looks like a strange kind of "consistency" to me, since other lock types are not dual. Both posix and Java APIs don't seem to imply that the write lock is the "default" lock in a RW lock. However, I'm not a synchronization specialist. > I realized that read/write locks are actually shared/exclusive locks, > which might form the basis for a name that doesn't collide with RLock. > Boost > (http://www.boost.org/doc/libs/1_43_0/doc/html/thread/synchronization.html#thread.synchronization.mutex_types.shared_mutex) > uses shared_mutex for the concept, so SLock or SELock? SELock looks ok, but I have to say that RWLock is more obvious (I don't need to do a search to guess that RW means "read/write"). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8800> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
