| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Serial I/O {4 of 10} |
* Reply to msg originally in Personal Mail - David Muir
-=> Quoting Peter Fitzsimmons to David Muir <=-
DM> The Basic functions included in that unit were originally made to
DM> duplicate an existing "DOS" unit (for easy porting).
PF> There is no reason why your class (unit) can't have a "write
one byte"
PF> routine; what I am saying is that under the covers, this should not
PF> translate to a DosWrite() for 1 byte (calling the device driver, in
PF> ring 0, is what is expensive).
Now I understand what you're saying (I have my slow years ).
While "my"
implementation of the unit would rarely ever need to consider this, I am
certain that any implementation which used "more" output than me
typing on my
keyboard could certainly benefit from a buffered state (perhaps buffering the
byte for a "period of time" and sending via thread using a blockwrite of
however many characters managed to make it into the "waiting to go" buffer
after perhaps 200ms (or some reasonable time for this type of thread)).
Thanks for the suggestion. I think this particular implementation
basically just answers the common question "How do I do it" ,
where you are
quite correctly answering "How do I do it `well'".
Thanks again..
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: 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™.