[711] in java-interest
Re: java-interest-digest V1 #83
daemon@ATHENA.MIT.EDU (Roland Giersig)
Mon Jul 17 14:04:19 1995
Date: Mon, 17 Jul 95 10:15:11 +0200
From: Roland.Giersig@aut.alcatel.at (Roland Giersig)
To: java-interest@java.Eng.Sun.COM
> From: csw@scndprsn.Eng.Sun.COM (Chris Warth)
> Date: Thu, 13 Jul 1995 15:15:46 -0700
> Subject: Re: java-interest-digest V1 #82
>
> > 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?
> >
>
> 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.
>
How about giving a tag or attribute to a class that hints the interpreter
"this class should be machine compiled as it is cpu-intensive"?
for example: class Foo is_a_cpu_hog { ... } ;^)
Security-wise it's an absolute no-no to execute machine code loaded over
the net.
Roland
--
Roland.Giersig@aut.alcatel.at (speaking only to, err, for myself)
ALCATEL Austria, Scheydgasse 41, A-1210 WIEN. Phone: +43-1-27722-3755
GS/AT d++(--) H s+:+ g+ p? au a- w v- C++$ US++>+++ P+ L E(+) N++(*) W+
V- -po+ Y+ t++(+++) !5 G? tv b++ D++ B? e+++>* u h--- f r+++ n+(----) y?
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
