semaphores and Rlocks
Aahz
aahz at pythoncraft.com
Fri Dec 20 20:12:35 EST 2002
More information about the Python-list mailing list
Fri Dec 20 20:12:35 EST 2002
- Previous message (by thread): semaphores and Rlocks
- Next message (by thread): semaphores and Rlocks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <3E03A3F7.2AD7A028 at sdfasdfasdfa.invalid>, Jive Dadson <sdfadfsa at sdfasdfasdfa.invalid> wrote: > >Yeah. Win32 CRITICAL_SECTION is implemented the same way, with >an interlocked increment wrapped around a win32 Mutex. But >CRITICAL_SECTION allows a thread to acquire the a lock repeatedly. > >By the way, I noticed some comments about not having >InterlockedIncrement or something like that available on Win98. I can >furnish an assembly language version in a C "__asm" thingy if anyone is >interested. It would be just about as "portable" as the win32 API. Someone in the past year on either c.l.py or python-dev was talking about writing some improvements to thread_nt.h, but I can't find it in a few minutes of Googling. If you can find that person and talk with him, that might be a good first step. -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ "To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it." --reddy at lion.austin.ibm.com
- Previous message (by thread): semaphores and Rlocks
- Next message (by thread): semaphores and Rlocks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list