public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>
Cc: kawa mailing list <kawa@sourceware.org>, srfi-170@srfi.schemers.org
Subject: Re: SRFI 170 (POSIX API) for Kawa
Date: Tue, 14 Jul 2020 21:16:25 -0700	[thread overview]
Message-ID: <e8cc682f-2298-94c6-2e31-c88bc9e842eb@bothner.com> (raw)
In-Reply-To: <CABgWrqpf7aUCNBof38oKKyudkgda1HG00uHH+YRhv6g+sf1B6Q@mail.gmail.com>

On 7/14/20 2:10 PM, Duncan Mak wrote:
> it's pretty clear that we won't be able to support the entirety of the SRFI 170 API using just Java classes. If we want to achieve that, we'll probably have to use JNR-Posix.
> 
> With JNR-Posix, Per's comments about shipping native code will become a thing.

I don't mind an optional (configurable) dependency on jnr or jnr-posix, but I don't think
it should be a required or default dependency.

I don't have much feel for how popular or common JNR is - it seems to be
a project that is in semi-maintenance mode, and not on any kind of "standards track".
I haven't done anything with it.

That doesn't seem we can't make use of it, of course.

Please us and Duncan know (here) whether SRFI-170 or other Posix bindings would be
useful to you.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2020-07-15  4:16 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
2020-07-14 21:10     ` Duncan Mak
2020-07-15  4:16       ` Per Bothner [this message]
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=e8cc682f-2298-94c6-2e31-c88bc9e842eb@bothner.com \
    --to=per@bothner.com \
    --cc=duncanmak@gmail.com \
    --cc=kawa@sourceware.org \
    --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).