Comments on: Comparable vs. Comparator

By: Generic viagra cialis levitra cheap

Generic viagra cialis levitra cheap — Tue, 04 Oct 2011 14:08:46 +0000

hjjsfkbwbcmphhjoh, Generic viagra without prescription, pBCfzxF, [url=http://arrogatemedical.com/GenericViagra.html]Buy viagra online[/url], nENdARF, http://arrogatemedical.com/GenericViagra.html Is maxoderm better than viagra, lgFBxRg.

By: Viagra

Viagra — Sat, 16 Jul 2011 02:25:24 +0000

, Viagra online, >:PPP, Generic viagra, hwdve, Viagra, 8-D,

By: Bad credit loans

Bad credit loans — Sat, 16 Jul 2011 02:24:24 +0000

, Viagra, 5606, Viagra, >:]]], Personal loan, 8OOO,

By: pmrhtqxcg

pmrhtqxcg — Fri, 15 Jul 2011 03:14:26 +0000

kJZXoB bftywaakaljm, [url=http://mierrbhvjrpm.com/]mierrbhvjrpm[/url], [link=http://mafjqwtdshlo.com/]mafjqwtdshlo[/link], http://nkdvrnuhxcdb.com/

By: Swoneequinott

Swoneequinott — Wed, 06 Jul 2011 11:25:34 +0000

Head Profile Sketches Medicine Stock cheap ambien without prescription Ambien can be prescribed to act as an anti-convulsant or muscle relaxant. http://www.3rdhalo.com/ – ambien online no prescription

By: miami fl lawyer

miami fl lawyer — Sun, 11 Jul 2010 01:46:19 +0000

Looking forward to finally finishing my research, great post!

By: WP Themes

WP Themes — Thu, 18 Mar 2010 03:23:23 +0000

Genial brief and this mail helped me alot in my college assignement. Thank you on your information.

By: Pravin Jain

Pravin Jain — Fri, 11 Sep 2009 12:01:48 +0000

Comparable should be implemented to define natural ordering for Objects of a class, and every class may not have natural ordering.
Here for example if the SelectablePerson had an id field, then that could be used for natural ordering, since we would consider two SelectablePerson to be equal whenever their ids match. In all other cases, one should use a Comparator.

By: jbisotti

jbisotti — Tue, 01 Sep 2009 14:57:41 +0000

“The problem was not caused by ‘not reading Javadoc’ or faulty implementation of equals() but by a bad design decision of implementing Comparable instead of using a Comparator. You are also right that adding a field to SelectablePerson class could remove that bug, but it would only complicate the design and mask the real issue.”

Really? IMHO, you are the one missing the main point. Regardless of if the design decision was a good one or not, the implementation is poor. And it most definitely is not masking the real issue; it’s exposing it.

Per your argument, you would blame the following on the Set interface, or the “design decision” to use a Set implementation:

final SelectablePerson p1 = new SelectablePerson( “smith” );

final SelectablePerson p2 = new SelectablePerson( “smith” );

final Set people = new HashSet();

people.add( p1 );
people.add( p2 );

// Fails because there’s only one element in the Set
assertEquals( 2, people.size() );

By: Sakuraba

Sakuraba — Tue, 01 Sep 2009 07:04:51 +0000

Wouldn’t all of this be sorted out if equals/hashcode were implemented correctly? Regardless of Comparable/Comparator?