| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Semaphore |
DAB> Well, I have used DosEnterCritSec when I had to call a time-critical
DAB> communications routine in order to prevent timeouts
DAB> (Communicating with weird PLC's).
DAB> I needed to be sure that when I went into that
DAB> routine, everything else
DAB> stopped until it was completed. It WAS designed to
DAB> be as quick as possible.
DAB> I don't think I'm being lazy... I just wanted to
DAB> point out that I think
DAB> that there are legitimate uses for DosEnterCritSec.
I don't think that is a legitimate use, because it is working around a
design flaw in the program (you have free-running polling loops in the
other threads).
I have written a lot of real time communication code under OS/2. I have
never had to use a critsec, or even the "time critical" priority
class.
Pete's first thread axiom: A thread's most important job is to do
nothing very well.
--- Maximus/2 3.00
* Origin: Sol 3 * Toronto * V.32 * (905)858-8488 (1:259/414)SEEN-BY: 50/99 270/101 620/243 625/100 711/401 409 410 413 430 808 809 934 SEEN-BY: 711/955 712/407 515 624 628 713/888 800/1 @PATH: 259/414 400 99 250/99 3615/50 396/1 270/101 712/515 711/808 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™.