TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: Peter Fitzsimmons
from: David Muir
date: 1995-08-24 19:06:08
subject: Communication/Thread problems

-=> Quoting Peter Fitzsimmons to David Muir <=-

 PF> Right;  use Wait-for-something in it's own thread.
 
    Okay, but to avoid any confusion what do you define as
"wait-for-something"? In my particular implementation the call to
"dosread" 
was only made if at least a single character was waiting. The 
dosread(buf,4000,return) took considerably longer than
dosread(buf,num_waiting,return). If this is due to my not having the port open 
in "wait-for-something" mode, then how do you define that so I can correct 
that oversight.

 PF> You're right about your being wrong .  DosSleep() is proably one of
 PF> the WORST ways to "release control";  it is much better
to block in a
 PF> device driver (for example,  in a DosRead() call) that will only wake
 PF> you up when you have some real work to do. 
 PF> For example,  I have seen this in an os/2 program:

    So then initaiting a thread dos not interfere with other operationsof the 
program? (I'll give this a shot, like I said I have almost no documentation).

Dave...


~~~ TGWave v1.00 Beta-05g [NR]
--- GEcho 1.11+
* Origin: Forbidden Knights Systems * (905)820-7273 * Dual * (1:259/423)
SEEN-BY: 105/42 620/243 711/401 409 410 413 430 807 808 809 934 955 712/407
SEEN-BY: 712/515 628 704 713/888 800/1 7877/2809
@PATH: 259/423 400 99 250/99 3615/50 396/1 270/101 105/103 42 712/515
@PATH: 711/808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.