This protection concept sounds perfectly rational, until you think of
other obvious things that do similar things to protect the coder.
myLong.equals(myString) doesn't throw an exception for instance, it just
return false.
but then you never know that you have a problem in your code and just
On Sat, May 19, 2018 at 4:47 AM, sebb wrote:
> On 18 May 2018 at 20:34, Gary Gregory wrote:
> > Hi All:
> >
> > A lot of methods in CollectionUtils are not null-safe and are documented
> as
> > such in Javadoc with throwing NPEs.
> >
> > I'd like to
On 18 May 2018 at 20:34, Gary Gregory wrote:
> Hi All:
>
> A lot of methods in CollectionUtils are not null-safe and are documented as
> such in Javadoc with throwing NPEs.
>
> I'd like to change that.
To what?
> The change is behavioral and BC would be preserved.
>
>
+1
Sent from Yahoo Mail on Android
On Sat, 19 May 2018 at 7:35, Gary Gregory wrote: Hi
All:
A lot of methods in CollectionUtils are not null-safe and are documented as
such in Javadoc with throwing NPEs.
I'd like to change that.
The change is behavioral and BC
Hi All:
A lot of methods in CollectionUtils are not null-safe and are documented as
such in Javadoc with throwing NPEs.
I'd like to change that.
The change is behavioral and BC would be preserved.
Thoughts?
Gary