+1, In my sorts, having to deal with nulls is causing me difficulties as well.. Although I could see something like any nulls being ignored as a type of behavior.. Sort everything, and drop the nulls!
Eric -----Original Message----- From: Jonathan Carlson [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 3:38 PM To: [EMAIL PROTECTED] Subject: [Collections] ComparableComparator - nulls OK I'd like to make the case for a ComparableComparator that allows the sorting of nulls to the bottom. This could be a flag to set on the existing class or another Comparator called something like NullableComparableComparator (or ComparableNullComparator?). This becomes a big issue when sorting a collection of things based on one of their getter methods with generic components like the TransformingComparator I just submitted. Too often the returned value can be a null. It's not too hard to write my own (I already have), but I prefer having things like this standardized in one library rather than written differently for each project. My two cents. I'd appreciate feedback, even negative feedback if it's appropriate. Jonathan ===== Jonathan Carlson [EMAIL PROTECTED] Minneapolis, Minnesota __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
