commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <>
Subject Re: Potential bugs in commons 3.2 with JUnit tests
Date Tue, 17 Aug 2010 21:23:48 GMT
But it looks to me like you have null values embedded in the inputs.

I think the same would happen if you called Arrays.sort and some of the
objects in the array being sorted were null.

Why do you think that non-nullity of the top level arguments is all that

On Tue, Aug 17, 2010 at 1:30 PM, Ted Dunning <> wrote:

> The 10 tests presented in the attachments violates one of the common Java
> code practices (at least in my viewpoint):
> if all the inputs are not null, there should not be null pointer exception
> thrown.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message