[Python-3000] patch: bytes object PyBUF_LOCKDATA read-only and immutable support (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Wed Sep 12 01:12:14 CEST 2007
- Previous message: [Python-3000] patch: bytes object PyBUF_LOCKDATA read-only and immutable support
- Next message: [Python-3000] patch: bytes object PyBUF_LOCKDATA read-only and immutable support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Travis E. Oliphant wrote:
I'm not sure I understand the difference between a classic read lock and the exclusive write lock concept.
A read lock means that others can obtain read locks, and nobody can obtain a write lock.
A write lock means that nobody else can obtain a lock of any kind.
I think strictly the 'e' should only be inserted if the preceding letter is one whose sound changes depending on whether it's followed by an 'e', such as 'c' or 'g'. "Writeable" does seem to be commonly used, though.
In any case, it would be good to adopt a convention for these kinds of word used in source, to minimise confusion.
-- Greg
- Previous message: [Python-3000] patch: bytes object PyBUF_LOCKDATA read-only and immutable support
- Next message: [Python-3000] patch: bytes object PyBUF_LOCKDATA read-only and immutable support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]