| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | wait-for-something |
Regarding my question "how do you define
"wait-for-something" mode".
Forget I asked. (Please ). Knowing I'm a novice is one thing, showing the
whole world is another.
I'll letcha know how it turns out.
Okay.. I took your advice. Moved my reads to a thread to check it out.
Your suggestion to use a "wait-for-something" approach showed no noticable
improvement, however it did also "not" exhibit the
"delay" which I had
previously mentioned.
Notably, I no longer have to check for "waiting" characters. While it
doesn't work "as I want" that is more due to the
"oddity" I mentioned in my
earlier message which I will look after later.
Also as you suggest, the dossleep appears to be a waste inside the thread,
although I still use it in the main program to lower the system demand (one
dosleep through the loop, which I "suppose" I could probably alleviate by
moving my loop into a thread as well).
Thanks for your advice in this manner. And where the heck were you when I
first started trying to figure out my communications routines? It's nice
to know I got the basics right, even if my implementation was less than
perfect.
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™.