> It makes no sense IMO to subclass Throwable directly as you would be > implying that you had a new category of problem that wasn't an > application issue and wasn't a system issue.
Excellent. I agree completely. > Application code should not be throwing or catching Errors Not necessarily true, but I get your point. > Nestable should be a subclass of Exception. Because you likely don't > want it to be checked, it would more specifically be a subclass of > RuntimeException. I agree with almost everything you've said. I'm just wondering now if we shouldn't have CheckedNestableException and UncheckedNestableException or something like that, where both implement a Nestable interface. Jeff __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
