From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,99bdf14f233488c4 X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,99bdf14f233488c4 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,12f4d07c572005e3 X-Google-Attributes: gid103376,public From: stt@henning.camb.inmet.com (Tucker Taft) Subject: Re: Java Risks (should be Java mis-speak) Date: 1996/06/03 Message-ID: #1/1 X-Deja-AN: 158303192 sender: news@inmet.camb.inmet.com (USENET news) x-nntp-posting-host: henning.camb.inmet.com references: followup-to: comp.lang.ada,comp.lang.c++,comp.lang.eiffel organization: Intermetrics, Inc. newsgroups: comp.lang.ada,comp.lang.c++,comp.lang.eiffel Date: 1996-06-03T00:00:00+00:00 List-Id: Richard Riehle (rriehle@nunic.nu.edu) wrote: : On Fri, 31 May 1996, The Right Reverend Colin James III wrote: : Colin, : I appreciate your taking the time to post a reply to my comments. : > Richard Riehle posted with deletions: : > : > Apparently Riehle does not understand that bytecode produced by Java is : > exactly what FORTH produces. The Java bytecode and the FORTH representation are not "exactly" the same. In fact, FORTH generally uses a "word" code rather than a byte code. The Java byte code and the FORTH word-code have some common goals, but the details are all quite different. : > Therefore for Ada or Eiffel to produce bytecode is silly. : If I implied that Ada or Eiffel should produce bytecode, I apologize. : That was never my intention. However, there are already Ada products, : and, I believe, Eiffel products in development, that will generate : either Java code or some intermediate Java representation that will : ultimately be translated into bytecode. Our Ada/Java product ("AppletMagic(r)") generates Java-compatible byte codes directly, with no intermediate steps. Java byte-codes are stored in ".class" files. The output of AppletMagic, just like the output of Sun's Java compiler, is one or more ".class" files, containing byte-codes to represent methods, and other information to provide the symbol table information necessary to support dynamic linking. The Java byte-code/".class"-file format, although designed to support Java, is not inherently dependent on the "surface syntax" used to write a program. The semantics of languages like Modula-3, Ada 95, Oberon-2, etc., are all quite directly representable in Java byte codes. Eiffel would be a bit more of a challenge, given its heavy dependence on multiple inheritance of implementation, though it could probably be done with some appropriate mapping. In any case, by generating a Java-compatible ".class" file, AppletMagic allows the Ada 95 programmer to create the same kind of platform independent, browser-executable applets as one can create using a Java compiler, and to call back and forth between Ada95 and Java code. There is a lot of information available on Java (see www.javasoft.com), as well as on our Ada => Java-byte-code compiler (see www.inmet.com/javadir/download). There is no need to speculate... : ... : Richard Riehle -Tucker Taft stt@inmet.com http://www.inmet.com/~stt/ Intermetrics, Inc. Cambridge, MA USA