From: Christopher Allan Webber <cwebber@dustycloud.org>
To: guile-devel@gnu.org
Subject: Re: Asynchronous event loop brainstorm at FSF 30
Date: Sun, 04 Oct 2015 10:24:36 -0500 [thread overview]
Message-ID: <87bncetz3f.fsf@dustycloud.org> (raw)
In-Reply-To: <87k2r3tvzh.fsf@dustycloud.org>
BTW, someone (I got the message privately, feel free to identify
yourself, person!) pointed me to http://wehu.github.io/mo/
which might be interesting to look at... it's the start of a node-style
event loop thing written in Guile, it looks like?
- Chris
next prev parent reply other threads:[~2015-10-04 15:24 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 [this message]
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
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=87bncetz3f.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--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).