Hi. > > Why not in the new "exception" package? > > [The aim being to deprecate the old "MathRuntimeException".] > > Sorry for that. I'm still not used to the new package. > Could you look at the various createXxxException factory methods in and > replace them by dedicated exceptions in the new package ? Obviously this > one is used only from one class but the older ones are more heavily used.
I've created "MathUnsupportedOperationException" (not committed yet). I was going to create "MathNullPointerException" but then looking at the usage in CM, I noticed that most checks for "null" result in throwing an "IllegalArgumentException"; exceptions to that rule appear in class "BigFraction". The usage should be consistent. I think that it is fine to use "MathIllegalArgumentException" everywhere. In which case I think that that we shouldn't have a "MathNullPointerException" at all (and never throw a "NullPointerException" explicitly from CM, so that when it happens, it will mean that some check is missing somewhere). Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
