From: Per Bothner <per@bothner.com>
To: kawa@sourceware.org
Subject: Re: SRFI 170 (POSIX API) for Kawa
Date: Wed, 15 Jul 2020 21:58:46 -0700 [thread overview]
Message-ID: <5865887e-6b2a-7868-ffa1-c8ea7bdcde6d@bothner.com> (raw)
In-Reply-To: <CA+ghDQ_3KPn3JdJFc3iLhr2d-ruBCESj+fW6qdtXx+f+u7vTCQ@mail.gmail.com>
On 7/15/20 5:02 PM, Jamison Hope wrote:
> I agree [JNR] shouldn't be a required dependency. But it would also be
> handy to be able to use the SRFI in conjunction with a stock binary
> Kawa release, and not have to do a custom configuration.
>
> Per, can the srfi loading in ImportFromLibrary.java cross jar
> boundaries?
IIRC ImportFromLibrary.java doesn't know anything about jar boundaries.
It just searches in the classpath.
If so, one option might be for SRFI97Map to map 170 to
> some other named class that isn't included in kawa.jar, and then
> provide a separately-compiled kawa-srfi170.jar or whatever that did
> rely on JNR-Posix or other such native code. Then if that other jar
> is in the CLASSPATH, then (import (srfi 170)) loads/uses it, and if
> not, then it doesn't work, or maybe we instead fall back on a
> Java-only subset.
Should be possible, as long as we make sure failure modes (error messages etc)
are reasonable.
There may be some interaction with Java 9 modules; it's been a while since I looked into those.
> I've never used JNR. My impression is that it's like JNA but..
> better? Or at least newer?
I believe newer.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2020-07-16 4:58 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
2020-07-15 6:59 ` Arvydas Silanskas
2020-07-16 0:02 ` Jamison Hope
2020-07-16 4:58 ` 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=5865887e-6b2a-7868-ffa1-c8ea7bdcde6d@bothner.com \
--to=per@bothner.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).