From: Per Bothner <per@bothner.com>
To: Sudarshan S Chawathe <chaw@eip10.org>, kawa <kawa@sourceware.org>
Subject: Re: gnu.expr.ModuleMethod no more? (+ Emacs SLIME)
Date: Mon, 05 Jun 2017 00:29:00 -0000 [thread overview]
Message-ID: <2e3756cf-2c75-2dec-d3a0-d2300df97448@bothner.com> (raw)
In-Reply-To: <22244.1496609440@vereq.eip10.org>
On 06/04/2017 01:50 PM, Sudarshan S Chawathe wrote:
> The source and binary packages for kawa-2.4 (from ftp.gnu.org) both
> include the class gnu.expr.ModuleMethod but the Gitlab repository
> doesn't seem to have it. Is that indicative of a change in future
> Kawa releases? If so, what is the recommended replacement?
The replacement is gnu.expr.CompiledProc.
> Sorry if I'm missing something obvious here. I did a quick grep and
> skimming on the Changelogs
Yes, that is what you should have done - except I got a bit sloppy
maintaining the ChangeLog in the invoke branch ...
> and couldn't figure much out except that
> ModuleMethod.java did exist in the repository a while back. I suspect
> this may be somehow related to recent changes related to the merged
> invoke branch, but have only vague ideas.
CompiledProc is a very direct replacement for ModuleMethod. However, the
former uses a MethodHandle (or a java.lang.reflect.Method) that points
to a procedure's check method; the old way used an index that was used is
a compiler-generated switch.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2017-06-05 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 20:50 Sudarshan S Chawathe
2017-06-05 0:29 ` Per Bothner [this message]
2017-06-05 13:34 ` Per Bothner
2017-06-05 15:01 ` Duncan Mak
2017-06-05 22:53 ` Per Bothner
2017-06-08 21:59 ` 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=2e3756cf-2c75-2dec-d3a0-d2300df97448@bothner.com \
--to=per@bothner.com \
--cc=chaw@eip10.org \
--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).