This is the mail archive of the
java-discuss@sources.redhat.com
mailing list for the Java project.
RE: Why interpret dynamically loaded classes?
- To: "'Jack Andrews'" <jack dot andrews at str dot com dot au>, "java-discuss at sourceware dot cygnus dot com" <java-discuss at sourceware dot cygnus dot com>
- Subject: RE: Why interpret dynamically loaded classes?
- From: Anthony Green <green at cygnus dot com>
- Date: Tue, 22 Aug 2000 23:47:20 -0700
- Organization: Red Hat
- Reply-To: "green at cygnus dot com" <green at cygnus dot com>
Jack wrote:
> I note that both GCJ and TowerJ use a bytecode interpreter to handle
dynamic
> class loading. But why not just compile the dynamically loaded class to a
> native shared object at *runtime*, then link at runtime, too?
Yes, this is possible. If someone were to implement this I'm sure we'd find
a way to fit it in.
> You'd just need to deploy the bytecode to native compiler with the
> executable rather than the bytecode interpreter.
Well, that's one problem, because our compiler doesn't run on all of the
target devices.
AG