David Muir wrote in a message to Mike Bilow:

 DM>     I did manage to figure out how to assign a 32bit
 DM> semaphore (although I  haven't figured out how to use 'em
 DM> ). I don't suppose the above file is  publically
 DM> available (GUIREF20.INF)? I'm using VP and don't have the
 DM> benefit  of the docs supplied with commercial compilers.

It is part of the OS/2 2.11 and OS/2 Warp Toolkit, which either comes with
a commercial compiler or on DevCon.  It is a licensed product, so IBM does
expect someone -- you or the compiler vendor -- to pay for it.  DevCon is a
very good value, however.

 DM>     okay.. now that that is settled, is it possible to run
 DM> such a thread which  is blocked by a semaphore rather than
 DM> using dossleep? Call it curiousity. 

You could really start a timer and all that, but why?  I think I explained
how to do this in a later message.  A thread that is blocked is equally
blocked whether it is waiting for a sleep to expire or for a semaphore to
be posted.  I am not actually sure if there is any difference in processing
overhead, but I suspect that sleep requires less processing than semaphore
checking.  It stands to reason that the scheduler would have to recheck all
pending semaphore requests on each transition from one thread to the next.
 
-- Mike


---