-1 This would call for the handling of a lot of special cases, e.g. a subclass declaring fewer exceptions than the superclass. Also, adding an additional parameter allows automatically changing client code to provide a default for it. Adding an exception really not only may but almost certainly will cause uncompilable client code. I do not see how this change can be handled even remotely automatically, and the manual effort exceeds what can be done automatically anyway.
- Arno Calum Maclean schrieb: > > Change Signature currently does not allow you to add/remove exceptions from > the throws clause. > In certain circumstances, this could be a very useful feature. > For example, at the moment I have a superclass method declared to throw an > IOException. If I want to add another Exception to the throws clause, I've > got to do it individually for the superclass and each subclass. > I should note that adding an exception may cause a problem to client code - > i.e. it may not currently handle this exception, while removing an exception > may cause a problem to the method implementation - i.e. it may currently > throw an exception of this type. > However, this happens to some degree anyway when adding/removing parameters. > Thanks, > Calum > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
