From: Duncan Mak <duncanmak@gmail.com>
To: kawa mailing list <kawa@sourceware.org>
Subject: Notations for calling Java methods
Date: Fri, 04 May 2018 18:34:00 -0000 [thread overview]
Message-ID: <CABgWrqrO=WizKba4RH_ncs6wwPg23mPB9Jp1WDhCVGDiFL0RDg@mail.gmail.com> (raw)
Hello Per,
I was doing some reading on the various Scheme implementations on the JVM
and saw that both JScheme and SISC and of course Kawa have their own way to
reference Java fields/methods.
Kawa - https://www.gnu.org/software/kawa/Method-operations.html
JScheme - http://jscheme.sourceforge.net/jscheme/doc/javaprimitives.html
SISC - http://sisc-scheme.org/manual/html/ch08.html#SchemeToJava
I was wondering if you could say more about the variously notations, and
their pros and cons - is there a reason why Kawa did not adopt the Javadot
notation?
Also, I saw that Silk has another technique (
http://www.cs.brandeis.edu/~tim/Papers/Reflection99/Old/paper2.html), and
what do you think about that?
Thanks!
--
Duncan.
next reply other threads:[~2018-05-04 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 18:34 Duncan Mak [this message]
2018-05-05 0:52 ` 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='CABgWrqrO=WizKba4RH_ncs6wwPg23mPB9Jp1WDhCVGDiFL0RDg@mail.gmail.com' \
--to=duncanmak@gmail.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).