commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Crum <>
Subject Re: [Math - 403] Never propagate a "NullPointerException" resulting from bad usage of the API
Date Wed, 02 Mar 2011 16:36:32 GMT
I agree with this view. It would help the developer who uses CM if the 
library told him/her what they did wrong ("argument 'foo' cannot be 
null") instead of a simple exception thrown message 
("NullPointerException thrown at line nnn of class Xyz").


On 3/2/2011 3:37 AM, Gilles Sadowski wrote:
> In my view, the
> exceptions are good if they allow to easily track down bugs (be they in CM
> or in user code). Accordingly they must precisely point to the source of the
> problem (in the code) and not try to outguess the user (as to what it
> should mean for him).

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message