From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>,
kawa mailing list <kawa@sourceware.org>
Subject: Re: Support for SRFI 18 / 21 (multithreading)
Date: Thu, 17 Jan 2019 07:42:00 -0000 [thread overview]
Message-ID: <8c0ac236-4d12-f59b-fce5-9573f7bea0c4@bothner.com> (raw)
In-Reply-To: <CABgWrqqFk2dSFr2zm4to=EMbbiKMsQr3Viw1sUrAd7mQahCCFA@mail.gmail.com>
On 1/16/19 8:33 PM, Duncan Mak wrote:
> Hello Per,
>
> I came across SRFI 18 / 21 (I don't really know concretely how the two
> differ), I see that neither is supported in Kawa.
>
> From a quick look at the API, I'm guessing that the SRFI API can be
> implemented using the Java threading APIs. Am I missing something?
>
> Is there a reason that the SRFI is not supported? is it only because no one
> has looked into it, or are there deeper reasons?
>
> If it is indeed feasible, would an implementation be welcome?
I haven't really looked into those SRFIs.
An implementation would be welcome - especially if it can be done as
a relatively light wrapper on top of Java facilities.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2019-01-17 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 4:34 Duncan Mak
2019-01-17 7:42 ` Per Bothner [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c0ac236-4d12-f59b-fce5-9573f7bea0c4@bothner.com \
--to=per@bothner.com \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.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).