This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Option to automatically generate missing exceptions and methods
- From: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- To: <java at gcc dot gnu dot org>
- Date: Tue, 11 Mar 2003 22:22:06 +0100
- Subject: Option to automatically generate missing exceptions and methods
Part of the problem of getting GCJ to work can sometimes
be that various classes and methods are not supported
in Classpath.
I've seen that Classpath contains empty methods/classes,
which allow programs to compile and link with GCJ, but
simply throw a runtime exception if they are ever invoked.
It seems to me that instead of manually writing these stubs,
GCJ could automatically generate the empty classes/methods.
Is there such an option?
The benefits of such an option would be several:
- No need to add stubs to libgcj/Classpath, unless they
do something more than the compiler generated
- For some programs, the missing stubs are all that are missing
to get things up and running
- Although most programs would not work with the generated stubs,
it might still have some value for testing/debugging/prototyping
of GCJ and the app in question
Øyvind