[usocket-devel] [usocket-cvs] r553 - in usocket/trunk: . backend vendor

[Chun Tian (binghe)]

done.

I think ABCL's Java interface is still quite trivial. Maybe some days in the future, people can directly export any Java class into CLOS class and operate them the same way as CLOS. (This requires lots of MOP work, but ABCL's current MOP support is quite limited)

--binghe

在 2010-7-20，19:48， Chun Tian (binghe) 写道：

> Ah ... I saw a sample from http://common-lisp.net/project/armedbear/doc/abcl-user.html
> 
> OK, will try to use the new interface.
> 
> --binghe
> 
> 在 2010-7-20，19:44， Chun Tian (binghe) 写道：
> 
>> Hi, Erik
>> 
>> If I remove JDI stuff, where can I find those JDI functions (do-jmethod-call, ...)? ABCL supply them now?
>> 
>> Regards,
>> 
>> Chun Tian (binghe)
>> 
>> 在 2010-7-20，18:49， Erik Huelsmann 写道：
>> 
>>> Hi Chun,
>>> 
>>> I think the JDI stuff I added way back when, isn't needed anymore. You
>>> could try removing it. Before, it wasn't always possible to
>>> dynamically determine retrieve a method from a JavaObject. Now, since
>>> it has an IntendedClass slot, the information that JDI was trying to
>>> capture, has been added to the base JavaObject class.
>>> 
>>> If you want, I can help to phase out JDI.
>>> 
>>> With kind regards,
>>> 
>>> 
>>> Erik.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2603 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/usocket-devel/attachments/20100915/670b1c94/attachment.bin>