I believe re-organizing the exception hierarchy is a great feature for a major release. For minor releases, avoid refactoring that would break current code.
Paul On Fri, Feb 11, 2011 at 1:23 PM, Phil Steitz <phil.ste...@gmail.com> wrote: > So from the user perspective, the compatibility issue is that code > that catches MathException will in some cases propagate runtime > exceptions instead. This sounds ridiculous, but what would be the > implications of just reverting the hierarchy so catching > MathException would work as before, but make MathException itself > unchecked? > > Sorry if this seems to be walking into the kind of discussion you > did not want to reopen at this point; but I am just trying to see > what we might be able to do to prevent users having to make code > changes to have their apps that use 2.1 work safely in 2.2. > > I will add at this point that if we just s/2.2/3.0 and s/3.0/4.0, I > am fine releasing as is. > > Phil >
