If we require an object parameter to be non-null our methods test for this and throw an IllegalArgumentException (note that we don't throw a NullPointerException). Perhaps the same could apply in Ant?
-----Original Message----- From: Kev Jackson [mailto:[EMAIL PROTECTED] Sent: Tue 28/12/2004 10:25 To: Ant Developers List Cc: Subject: [Patch] StringInputStream - removed unused imports - changed <CODE> to <code> On a related note: Parameter x must not be <code>null</code> Wouldn't it make sense to throw some kind of exception if parameter x was null? At the beginning of the method, not later on when some other method tries something and gets hit with a NullPointerException. Some thoughts Kev --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]