-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Samstag, 27. September 2003 11:11 schrieb Jeroen Frijters:
> > Have you misread Andrew's comment ? I read it exaclty the other > > way around then you. > > I didn't misread it, I just strongly disagree with it. If Andrew's > argument was the reason UnsupportedOperationException was chosen, I > think we need to reconsider. Yes. > Surely there is defensively written code out there that handles > UnsupportedOperationException (for example, when dealing with > collections), this will consume our UnsupportedOperationException > (which really means something quite different) and make diagnosing > the problem extremely hard. When an application depends on missing > functionality I want to see the exception and reduce the chance > that the app accidentally eats the exception. Well, thats my concern too. Summarized inheriting from either UnsupportedOperationException or Error is bad. Just inheriting from Exception might not be. Michael - -- Homepage: http://www.worldforge.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/dVbwWSOgCCdjSDsRAg9eAJ4zJpofhG7tQsSiT4iRbWFX6vFbHACfX/Gz YccHJ9M6jHR/JQ6AlnfxUso= =sdgC -----END PGP SIGNATURE----- _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
