This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Option to automatically generate missing exceptions and methods
- From: Tom Tromey <tromey at redhat dot com>
- To: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: <java at gcc dot gnu dot org>
- Date: 11 Mar 2003 14:42:21 -0700
- Subject: Re: Option to automatically generate missing exceptions and methods
- References: <41D1051F31A2674C99E41CA28EE734980464C9@isp-ex2k.intellimade.net>
- Reply-to: tromey at redhat dot com
>>>>> "Øyvind" == Øyvind Harboe <oyvind dot harboe at zylin dot com> writes:
Øyvind> It seems to me that instead of manually writing these stubs,
Øyvind> GCJ could automatically generate the empty classes/methods.
Øyvind> Is there such an option?
Nope. I don't think gcj has enough information to generate stubs
automatically. For instance, what is the superclass of an unknown
class? Likewise for argument and return types. How would you
distinguish a missing-and-to-be-stubbed class from a typo?
Someone wrote a tool to generate the stub classes from javadoc. I
think it would be better to just generate the ones we find we need.
Or, hack the upstream code not to require things we don't have.
That's the rhug approach. This has the benefit of keeping the API
compatibility page more closely aligned with what we really implement.
Tom