From: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: guile-devel@gnu.org
Subject: Re: Asynchronous event loop brainstorm at FSF 30
Date: Thu, 19 Nov 2015 13:27:38 +0000 [thread overview]
Message-ID: <20151119132738.31a19e46@bother.homenet> (raw)
In-Reply-To: <20151118102625.6b5d6d2e@bother.homenet>
On Wed, 18 Nov 2015 10:26:25 +0000
Chris Vine <chris@cvine.freeserve.co.uk> wrote:
> On Tue, 17 Nov 2015 11:46:24 -0600
> Christopher Allan Webber <cwebber@dustycloud.org> wrote:
> [snip]
> > This sounds very interesting... is the source available? Could you
> > point to it?
> >
> > Thanks!
> > - Chris
>
> No it's not. I'll email you something.
In case it's of use to others in looking at the options, I have now put
the code here:
http://www.cvine.plus.com/event-loop/event-loop.scm
I have no problem with any parts of it going into guile if thought
useful. I was inclined to apply the MIT license to it but that seems
fairly pointless give that guile is covered by the LGPL. The
interesting part is not so much the event loop but the use of
coroutines to give "await" type semantics. This particular
implementation does allow tasks to run in their own threads in a safe
way.
It works for my limited purposes but I imagine it could be much
improved.
Chris
next prev parent reply other threads:[~2015-11-19 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 22:29 Asynchronous event loop brainstorm at FSF 30 Christopher Allan Webber
2015-10-04 13:24 ` Amirouche Boubekki
2015-10-04 15:19 ` Christopher Allan Webber
2015-10-04 15:24 ` Christopher Allan Webber
2015-10-04 15:58 ` Nala Ginrut
2015-10-04 16:15 ` Chris Vine
2015-11-17 17:46 ` Christopher Allan Webber
2015-11-18 10:26 ` Chris Vine
2015-11-18 14:37 ` Christopher Allan Webber
2015-11-19 13:27 ` Chris Vine [this message]
2015-11-18 12:44 ` Mikael Djurfeldt
2015-11-18 14:16 ` Christopher Allan Webber
2015-11-18 16:36 ` Mikael Djurfeldt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151119132738.31a19e46@bother.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).