From: Chris Vine <chris@cvine.freeserve.co.uk>
To: guile-user@gnu.org
Subject: Re: Potluck - thread safe event loop with await semantics
Date: Tue, 23 Feb 2016 04:58:41 +0000 [thread overview]
Message-ID: <20160223045841.7051f9cc@dell.homenet> (raw)
In-Reply-To: <20160222174056.2091d806@dell.homenet>
On Mon, 22 Feb 2016 17:40:56 +0000
Chris Vine <chris@cvine.freeserve.co.uk> wrote:
[snip]
> I have gone a little further with this and have added more convenience
> wrapper procedures which makes a-sync rather easy to use. I am
> preparing a guile-a-sync package which I will put on github. I have
> everything going except that I am finishing off adding a wrapper for
> clock_gettime() so that a monotonic clock is available for timeouts.
> It also has some bug fixes for the code I posted.
I have put up the code at https://github.com/ChrisVine/guile-a-sync.git
It is still something of a work in progress, particularly as regards
the documentation. In particular it is in need of a good set of
examples of how to use the helper procedures, and also some proper unit
tests. These will be forthcoming in the course of a few days or so.
Chris
next prev parent reply other threads:[~2016-02-23 4:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 21:45 Potluck - thread safe event loop with await semantics Chris Vine
2016-02-22 12:01 ` Ludovic Courtès
2016-02-22 16:36 ` Marko Rauhamaa
2016-02-22 17:40 ` Chris Vine
2016-02-22 17:53 ` Thompson, David
2016-02-22 18:12 ` Chris Vine
2016-02-22 19:54 ` Christopher Allan Webber
2016-02-22 20:28 ` David Pirotte
2016-02-23 0:31 ` Chris Vine
2016-02-23 1:30 ` Chris Vine
2016-02-23 19:55 ` David Pirotte
2016-02-23 6:25 ` David Pirotte
2016-02-23 12:09 ` Chris Vine
2016-02-23 16:49 ` Chris Vine
2016-02-25 23:22 ` David Pirotte
2016-02-23 4:58 ` Chris Vine [this message]
2016-03-01 20:39 ` Amirouche Boubekki
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=20160223045841.7051f9cc@dell.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=guile-user@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).