>>> "Nascif Abousalh-Neto"<[EMAIL PROTECTED]> seems to think that:
[ ... ]
>> This doesn't really help the elisp illiterate plugin tool developer,
>> but it would make it easy to create and maintain a plugin
>> interface for the JDEE.
>
>What about doing it in the other direction: creating eieio classes
>from existing Java classes? The generated eieio classes could extend basic
>classes designed for easy integration into the JDEE plug-in framework.
>
>Generating Lisp from Java seems to be more appropriate in this particular
>problem, since typically the Java code will already exist (in the form of a
>library or tool that we want to add to JDEE).
[ ... ]
>From my perspective (as a non-java programmer) a better idea might be
defining classes in a language agnostic form, such as XML. This is
the same notion CORBA developers used when they created the C like
IDL (Interface Description Language, not the other IDL). I don't
recommend IDL for this task, however. ;)
My intention for discussing such an interface with Paul was so I
could hack Emacs Lisp code, and have it display UML, or other types
of graphics via a slave Java process.
Eric
--
Eric Ludlam: [EMAIL PROTECTED], [EMAIL PROTECTED]
Home: www.ultranet.com/~zappo Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
