Comments on: D’oh! http://blog.xcski.com/2008/05/31/doh-2 Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place. Tue, 02 Dec 2008 06:27:30 +0000 http://wordpress.org/?v=2.6.5 By: Paul Tomblin http://blog.xcski.com/2008/05/31/doh-2#comment-92631 Paul Tomblin Sun, 01 Jun 2008 00:55:54 +0000 http://blog.xcski.com/?p=1363#comment-92631 Well, "data.size()" isn't the normal way of getting how many rows. To be strictly OO-ish, I'd make a TableModel and call the method getRowCount(). But I didn't need all the capability of a TableModel so I just have a simple ArrayList called "data". Well, “data.size()” isn’t the normal way of getting how many rows. To be strictly OO-ish, I’d make a TableModel and call the method getRowCount(). But I didn’t need all the capability of a TableModel so I just have a simple ArrayList called “data”.

]]> By: David Parsons http://blog.xcski.com/2008/05/31/doh-2#comment-92610 David Parsons Sat, 31 May 2008 20:53:15 +0000 http://blog.xcski.com/?p=1363#comment-92610 I'm impressed at the intuitiveness in the name of the data.size() whatevertheycallamethodinjava. Seeing a wetcamij called size() and realizing it's a rowcount is not the sort of thing that would leap out at me as an obvious bug, except in the original naming of the wetcamij. I’m impressed at the intuitiveness in the name of the data.size() whatevertheycallamethodinjava. Seeing a wetcamij called size() and realizing it’s a rowcount is not the sort of thing that would leap out at me as an obvious bug, except in the original naming of the wetcamij.

]]> By: Paul Tomblin http://blog.xcski.com/2008/05/31/doh-2#comment-92602 Paul Tomblin Sat, 31 May 2008 17:12:39 +0000 http://blog.xcski.com/?p=1363#comment-92602 Talk to the Swing designers. rowAtPoint and columnAtPoint are methods in JTable, not in my code. Talk to the Swing designers. rowAtPoint and columnAtPoint are methods in JTable, not in my code.

]]> By: Seth http://blog.xcski.com/2008/05/31/doh-2#comment-92600 Seth Sat, 31 May 2008 16:16:34 +0000 http://blog.xcski.com/?p=1363#comment-92600 Shouldn't rows and columns (indices, counts) be different types to prevent just that sort of error? "Strong typing is for programmers with weak memories." Shouldn’t rows and columns (indices, counts) be different types to prevent just that sort of error?

“Strong typing is for programmers with weak memories.”

]]>