On Thursday, December 12, 2002, at 02:08 PM, Berin Loritsch wrote:
I'd actually prefer it the other way.. Why?1) We should *never* explicitly throw a NullPointerException. If an argument is required, throw an IllegalArgumentException instead. The meaning of the error is much more clear.
Throw a NullPointerException when an argument that is expected is null.
Use IllegalArgumentException when there is an argument supplied, but it is invalid for other reasons.
-pete
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
