From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>, Lassi Kortela <lassi@lassi.io>
Cc: kawa mailing list <kawa@sourceware.org>, srfi-170@srfi.schemers.org
Subject: Re: SRFI 170 (POSIX API) for Kawa
Date: Sat, 22 Feb 2020 16:40:00 -0000 [thread overview]
Message-ID: <db57ec24-ffed-c71d-eac5-82caa989c56d@bothner.com> (raw)
In-Reply-To: <CABgWrqrybka5p8K9xMhb5tNFA_JRCYKq_ysxjcrm2C13gPzTvg@mail.gmail.com>
On Sat, Feb 22, 2020 at 4:46 AM Lassi Kortela <lassi@lassi.io> wrote:
> Is anyone working on implementing SRFI 170 for Kawa yet? Since Kawa is
> Java-based instead of C-based, and uses pathname objects as well as a
> per-thread parameter object to store the current directory, it would
> make for a good test case.
It might be interesting to see how much could be implemented in portable Java,
without digging into native (C/C++) code. Kawa currently does not contain
native code, which means we can make a single cross-platform "binary release".
That doesn't mean I'll rule out having optional features that depend
on native code, but I would prefer to stick to no native code in the
default build.
There are no doubt large parts of SRFI-170 that could be implemented
without native code, but I haven't done the effort to see what the issues are.
If someone wants to look into to what extent SRFI-170 can be mapped into
Java APIs that would be interesting, but I'm not planning to do that
study myself.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2020-02-22 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 9:46 Lassi Kortela
2020-02-22 16:08 ` Duncan Mak
2020-02-22 16:40 ` Per Bothner [this message]
2020-07-14 21:10 ` Duncan Mak
2020-07-15 4:16 ` Per Bothner
2020-07-15 6:59 ` Arvydas Silanskas
2020-07-16 0:02 ` Jamison Hope
2020-07-16 4:58 ` Per Bothner
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=db57ec24-ffed-c71d-eac5-82caa989c56d@bothner.com \
--to=per@bothner.com \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=lassi@lassi.io \
--cc=srfi-170@srfi.schemers.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).