TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Tucker Taft <[log in to unmask]>
Date: Fri, 17 Apr 1998 17:14:40 -0400
Reply-To: Tucker Taft <[log in to unmask]>
Parts/Attachments: text/plain (35 lines)
> Tucker Taft wrote:
> > However, if you are talking about the same set of stuff for a compiled
> > version of Ada, this is a non-trivial task, though one that
> > we agree might be worth doing.  It would be especially good if
> > we could tap into the JDK "DLL" or "shared library" that is
> > used to support these Java classes on a particular target O/S.
>
> How non-trivial is this really?  I have only read enough about Java
> to be dangerous, but I seem to recall that you could use the Java
> Native Interface to fire off a Java interpreter from within a
> compiled version of code from another language.  Could one do this,
> then use the interfaces previously described?

Yes, one option is to call into the Java classes from Ada.
This would not be a particularly big job, though at this point
it might be simpler to just use an Ada95-to-Java-byte-code compiler
such as our AppletMagic, or the one integrated with ObjectAda
(based on AppletMagic), or the forthcoming GNAT-based one.
For academic use, this option is probably the most attractive.
As Just-In-Time compilers improve, this option might compete with
one cobbled together out of native-compiled Ada code, JNI, and
the Java byte-code library.

> --Martin
>
> Martin C. Carlisle, Asst Prof of Comp Sci,
> US Air Force Academy, [log in to unmask]
> http://www.usafa.af.mil/dfcs/bios/carlisle.html
>
> DISCLAIMER: The content of this message does not
> necessarily reflect the opinions of the US Air
> Force Academy, or the US government

-Tucker Taft  [log in to unmask]

ATOM RSS1 RSS2