Hello Mike

Replying to a message of Mike Bilow to Alan Clifford:

 MB> As I read my own words again, I realize that I forgot to mention an
 MB> additional concern.  If you do not post the event semaphore after
 MB> every byte, you must set up a handler for the special case where you
 MB> get an otherwise unhandled residue in the buffer.  For example, if
 MB> you trigger the event semaphore every 10 bytes, and you physically
 MB> receive 5 bytes, then those 5 bytes will sit in the buffer forever
 MB> unless you either receive 5 more bytes or do something special to get
 MB> them out of there.

I thought about putting a "timerout" on the event semaphore to
cover this but that would mean the thread would run even if there were no
characters waiting.  Rather defeats the object of using an event semaphore.

 MB> This may sound like a really obvious observation, but it is a common

Nothing is obvious at the moment.  All help gratefully received.

 MB> One common approach is to use a timer to post the event semaphore. 
 MB> Then, when a byte is inserted into the buffer and the timer is not

Aha, I'd better read the chapter on timers.

I've got "OS/2 Warp Control Program API" by Marc Stock (well, the
local library bought it for me).  It doesn't cover IOCTLs.  Here I am with
the money in my hot little hands but the local bookshops don't carry more
than "The idiot child's guide to OS/2 programming - vital bits missed
out edition" for me to look at before I buy.  A trip to the London
bookshops is required I think.  Is any of this stuff is available online?


Alan

--- FleetStreet 1.14 NR