I have been going through NumberUtils code and tests to make sure that handling of nulls is documented (and tested) correctly. I notice that createNumber returns null for null (need to add a javadoc comment for this); whereas createFloat, et al will throw NPEs on null. Shouldn't these behave the same? In any case, the behavior should be documented.
Should I submit a patch to
1. Make createFloat et al return null for null as createNumber does
2. Make no changes to NumberUtils methods, just add javadoc and tests documenting current behavior.
3. Go back to sleep...;-)
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
