I think Classpath should also declare RuntimeExceptions if JDK does so.
If you do a getExceptionTypes() on java.lang.reflect.Method you will get all declared Throwables. This includes RuntimeExceptions and Errors that are declared to be thrown by a method (also for constructors).
So, to keep the runtime-behavoir of such objects consistent we need to declare such Exceptions even if the compiler does require it.
--ingo
Sascha Brawer wrote:
Hi all,
if the signature of a JDK method declares to throw some RuntimeException, should the Classpath do so, too?
For example, java.awt.Toolkit.createButton declares to throw java.awt.HeadlessException in the JDK, but not in Classpath. HeadlessException extends java.lang.RuntimeException.
-- Sascha
Sascha Brawer, [EMAIL PROTECTED], http://www.dandelis.ch/people/brawer/
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
