From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Passing objects between threads
Date: Sat, 10 Sep 2016 11:37:55 +0200 [thread overview]
Message-ID: <CAMFYt2YKuh0O_bNULu7UwdJE1SU6TGcNkPvkxrw049Yc2sJtTQ@mail.gmail.com> (raw)
Hi,
is there any easy way to create a channel (queue) that could be used to
communicate between threads? In particular, if the queue is empty, I would
like the consumer to wait until something appears in it (pretty much like
the channels in Clojure)
regs,
Panicz
next reply other threads:[~2016-09-10 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 9:37 Panicz Maciej Godek [this message]
2016-09-10 10:35 ` Passing objects between threads Diogo F. S. Ramos
2016-09-10 11:18 ` Chaos Eternal
2016-09-10 19:30 ` Panicz Maciej Godek
2016-09-10 19:29 ` Panicz Maciej Godek
2016-09-10 14:30 ` Chris Vine
2016-09-10 20:16 ` Panicz Maciej Godek
2016-09-10 21:36 ` Chris Vine
2016-09-11 18:34 ` Andy Wingo
2016-09-12 19:58 ` Panicz Maciej Godek
2016-09-12 23:10 ` Chris Vine
2016-09-15 19:37 ` Panicz Maciej Godek
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=CAMFYt2YKuh0O_bNULu7UwdJE1SU6TGcNkPvkxrw049Yc2sJtTQ@mail.gmail.com \
--to=godek.maciek@gmail.com \
--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).