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: Elmar Haneke <elmar at haneke dot de>
- Subject: Re: Why interpret dynamically loaded classes?
- From: Andrew Haley <aph at cygnus dot co dot uk>
- Date: Wed, 23 Aug 2000 11:57:57 +0100 (BST)
- Cc: Jack Andrews <jack dot andrews at str dot com dot au>, java-discuss at sourceware dot cygnus dot com
- References: <91831350CC59D3118C88005004754C4624B93E@MELB_XMAIL><39A37E2E.722EEB5C@haneke.de>
Elmar Haneke writes:
> Jack Andrews 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?
>
> This might be done!
>
> But, I would expect it to be rather slow
Perhaps, but I really like this idea. I've been thinking of doing
this for a while but I've never found the spare time to try it. I
don't think it would be very difficult.
It might even be possible to keep a copy of gcj running in the
background and just feed it with new classfiles when required. That's
more of a research project, though!
Andrew.