[armedbear-devel] Question about calling Java
axel at rauschma.de
Thu Feb 4 14:39:48 UTC 2010
Quick comment: The latest incarnation of the Java FFI API allows one to use strings whenever a class object or a method object is required:
(jnew "my.package.MyClass" arg) for new my.package.MyClass(arg)
(jcall "methodName" obj arg) for obj.methodName(arg)
This is certainly good enough for me. I don't know how efficient the produced code is, but this is currently not an issue for me.
On Feb 4, 2010, at 14:50 , Alessio Stalla wrote:
> On Thu, Feb 4, 2010 at 12:24 PM, Nitralime <nitralime at googlemail.com> wrote:
>> On 02/03/2010 08:05 PM, Mark Evenson wrote:
>> On 2/3/10 8:00 PM, Alessio Stalla wrote:
>> On Wed, Feb 3, 2010 at 6:46 PM, nitralime<nitralime at googlemail.com> wrote:
>> IMHO, the ablity of using Java libraries easily should be an integral
>> part of
>> every language targeting JVM! I find it very unfortunate that the Java
>> of ABCL is practically (i.e. out of the box) absent.
>> Why do you say that? ABCL's Java FFI is somewhat verbose, but apart
>> from this limitation that Mark found, and maybe some things that could
>> be polished and made more uniform, you can do anything you want.
>> We would probably be using SBCL if we didn't want integration with the
>> My description of the situation was intentionally provocative :-(
>> I just wanted to draw your attention to the fact that the current
>> JVM integration could be more user friendly than what it is now!
> Do you have ideas on how to make it more user-friendly?
>> A more systematic tutorial would also be very nice for inexperienced users
>> like me :-)
> I agree, something like "how to use <insert java library here> with
> abcl" would be useful as a starting point for new users. Would you
> volunteer to write it? ;) More seriously, like Ville said, it would be
> nice if you identified what is hard for you and what is lacking in
> documentation, and write a report about it; someone else, or yourself
> when you'll have more experience, will eventually be able to use that
> information to make our documentation better.
> armedbear-devel mailing list
> armedbear-devel at common-lisp.net
Axel.Rauschmayer at ifi.lmu.de
More information about the armedbear-devel