Hi Michael, On Friday 26 September 2003 17:56, Michael Koch wrote: > I'm for UnsupportedOperationException too because it exists already > and dont have to invent something new. > > A reason against using it is that some methods return UOE by design in > some situations. That means that i may not be clear in any case if > the method throwns an exception because its unimplementd or because > of other reasons.
How about NotYetImplementedException extends UnsupportedOperationException then to distinguish between the above cases? IMHO, it would be quite useful for the project being able to say "we are able to run any JDK 1.2 programme". A script that has to know about which method might throw UnsupportedOperationException and which shouldn't could never be really reliable. Cheers, Andy. -- aicas GmbH Haid-und-Neu-Straße 18 * 76131 Karlsruhe http://www.aicas.com Tel: +49-721-663 968-24; Fax: +49-721-663 968-94 _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath