From: | kik@zia.cray.com (Krishna Ksheerabdhi) |
Newsgroups: | comp.compilers |
Date: | 8 May 1996 00:27:33 -0400 |
Organization: | Compilers Central |
Keywords: | Java |
> From: Rupert Brauch <brauch@hpp.stanford.edu>
>
> There are a bunch of reasons why you wouldn't want to fly with Java.
> You may have existing code that you don't want to rewrite in Java.
> You may not be able to live with the overhead of interpreted code,
> etc.
Amen to the point about existing code that you want to 'move around',
but regarding 'overhead' - can't that be solved by a
compiler/translator that converts byte code to native code that takes
advantage of the underlying architecture? One could integrate that
several ways - on-the-fly in sync with the bytecode verifier [Franz's
thesis on semantic dictionary encoding (SDE) from ETH comes to mind]
or as a separate pass after the verification. I heard it from the
grapevine that Borland has such a product in the works. Could someone
authenticate that?
This should be possible shouldn't it, or am I missing something?
Curious,
ksh
----
Ksheerabdhi Krishna
Cray Research, Inc. Phone: (505) 988-2468 (x28)
Santa Fe, NM 87505 e-mail: kik@cray.com
[I may be an old grouch, but this is starting to smell like the UNCOL black
hole. Yes, you can turn your intermediate code into native code with some
amount of effort on some number of platforms, but the details always end
up killing you. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.