In all honesty, I hadn't used the make-input-port procedure before. It
didn't occur to me to use that to make a nonblocking input port. Your code
snippet seems to solve the problem quite a bit better than my egg does.
Is open-input-file*/nonblock in a currently released egg?
On Thu, Jul 7, 2016
Hello everyone. Quite an interesting discussion started in response to my
announcement of the async-io egg the other day. I've been following along
and Chris Vine had made some mention of busy waiting being a flaw with the
library itself. He mentioned that this could be dealt with using
Hi guys. I'm not very familiar with the low level details, but the
documentation for srfi-18 found here.
https://wiki.call-cc.org/man/4/Unit%20srfi-18
Contains this quote
"Blocking I/O will block all threads, except for some socket operations
(see the section about the tcp unit). An exception
Hello Chicken Users!
I have created an asynchronous I/O egg for chicken. Would it be possible to
have it added to the egg-locations file in subversion?
Here is the repository
https://github.com/yarnoiser/async-io
And here is the url for the release-info file specifically.
for the feedback.
On Wed, Jun 15, 2016 at 12:46 PM, Mario Domenech Goulart <
mario.goul...@gmail.com> wrote:
> Hello Robert,
>
> On Wed, 15 Jun 2016 12:33:35 -0600 Robert Smiley <yarnoiser...@gmail.com>
> wrote:
>
> > Oh. I read a tutorial a while
Hello everyone,
My name is Robert and I'm new around here.
I've recently created an egg out of some code I have written. The library's
focus is cooperative multitasking using coroutines and finite state
machines.
I understand this approach has drawbacks compared to srfi-18 (having to
explicitly
