[699] in java-interest
Re: java-interest-digest V1 #82
daemon@ATHENA.MIT.EDU (John Mitchell)
Thu Jul 13 21:10:52 1995
From: johnm@medicus.com (John Mitchell)
To: csw@scndprsn.Eng.Sun.COM (Chris Warth)
Date: Thu, 13 Jul 95 16:23:30 PDT
Cc: ekim@nyquist.bellcore.com, java-interest@java.Eng.Sun.COM
In-Reply-To: <9507132215.AA16357@builder.Eng.Sun.COM>; from "Chris Warth" at Jul 13, 95 3:15 pm
> > Is this what is called a "fat binary". Multiple versions of a class
> > or a method which have the right binary version picked at runtime?
We need both, me thinks.
> In principle, yes, this would be a fat binary, but I doubt that we will
> ship around class files with a bunch of different machine code versions
> in them. All I intended to point out is that the class file format can
> *potentially* handle multiple architectures. We intend to do on the
> fly compilation to machine code at runtime as the white paper said.
Right but only doing just-in-time-compiling from the bytecode precludes
the easy integration of platform specific native code when it's
available.
John
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
