From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 58011 invoked by alias); 17 Jan 2019 04:34:37 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 57244 invoked by uid 89); 17 Jan 2019 04:34:37 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=java, Java, H*c:alternative X-HELO: mail-io1-f51.google.com Received: from mail-io1-f51.google.com (HELO mail-io1-f51.google.com) (209.85.166.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 17 Jan 2019 04:34:35 +0000 Received: by mail-io1-f51.google.com with SMTP id k2so6764646iog.7 for ; Wed, 16 Jan 2019 20:34:35 -0800 (PST) MIME-Version: 1.0 From: Duncan Mak Date: Thu, 17 Jan 2019 04:34:00 -0000 Message-ID: Subject: Support for SRFI 18 / 21 (multithreading) To: kawa mailing list Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-q1/txt/msg00021.txt.bz2 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? Thanks! -- Duncan.