From: Vasantha Ganesh <vasanthaganesh.k@gmail.com>
To: kawa@sourceware.org
Cc: Per Bothner <per@bothner.com>
Subject: Question, GSoC Idea `Easier Access to Native Libraries using JNA/JNR"
Date: Sun, 02 Apr 2017 11:07:00 -0000 [thread overview]
Message-ID: <CAL0TjKrATQ=DTwrJd2Xydca-dGZ6f-uTPg6ee_KaKELv2kQnag@mail.gmail.com> (raw)
Hello all,
I have been trying to write a proposal for ``Easier Access to Native
Libraries using JNA/JNR" idea for my GSoC project.
The access to native libraries is available through popular libraries
such as JNA and JNR. Access to native libraries in Kawa is just like
any other Java library in a very consistent way (strengths of Kawa?).
I tried looking into the Ruby wrappers. JRuby is trying to make their
FFI API compliant with other implementations. So that Code on JRuby
can run in the same way as other Ruby implementations.
Common lisp is trying to do something similar with CFFI. Common lisp
implementations are trying to make their code that can run on other
implementations in the same way. This calls for a common API (CFFI).
But in scheme we are not trying to be compliant with any other Scheme
implementations. Take Guile and Kawa for example. Guile code does not
necessarily run on Kawa. Also, Guile has its own FFI.
These are just my views. I would like to know the motivation of this
project because I'm fuzzy about the usefulness of this project.
It might be a little late to write proposal for other ideas.
Thank you.
Vasantha Ganesh K.
next reply other threads:[~2017-04-02 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 11:07 Vasantha Ganesh [this message]
2017-04-02 15:12 ` Per Bothner
2017-04-02 21:08 ` Jamison Hope
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='CAL0TjKrATQ=DTwrJd2Xydca-dGZ6f-uTPg6ee_KaKELv2kQnag@mail.gmail.com' \
--to=vasanthaganesh.k@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/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).