Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #14424
| From | mhx@iae.nl (Marcel Hendrix) |
|---|---|
| Subject | Re: Non-blocking asynchronous execution |
| Newsgroups | comp.lang.forth |
| Message-ID | <98641909968435@frunobulax.edu> (permalink) |
| Date | 2012-07-26 16:39 +0200 |
| References | <m7rwhx.3ll@spenarnc.xs4all.nl> |
| Organization | Wanadoo |
Albert van der Horst <albert@spenarnc.xs4all.nl> writes Re: Non-blocking asynchronous execution [..] > In this and probably Marcels example, during 5 seconds an > extra process shows up on the system. The point is apparently > to accomplish this without the extra process. Hmmm. No, iForth's FORTH-PROCESS is the classical PAUSE loop with the USER areas etc.. It works because *all* iForth I/O is non-blocking. As, for accuracy reasons, MS blocks, I had to cheat with the non-standard ~MS. As such, I met Arnold's challenge. You know, I had to look up how FORTH-PROCESS works in the sources. How quickly I forget ... -marcel
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Non-blocking asynchronous execution mhx@iae.nl (Marcel Hendrix) - 2012-07-25 20:08 +0200
Re: Non-blocking asynchronous execution Albert van der Horst <albert@spenarnc.xs4all.nl> - 2012-07-26 15:03 +0000
Re: Non-blocking asynchronous execution mhx@iae.nl (Marcel Hendrix) - 2012-07-26 16:39 +0200
Re: Non-blocking asynchronous execution Arnold Doray <invalid@invalid.com> - 2012-07-27 04:55 +0000
csiph-web