Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

jdavidb
  (email not shown publicly)
http://voiceofjohn.blogspot.com/

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Monday October 13, 2008
03:53 PM

Java gravel of the day: poor API design

[ #37655 ]

What a piece of work is NodeList. Nobody seemed to think of making NodeList implement List, and that's somewhat bizarre, and worse, inconvenient.

Crying for XML::TreeBuilder over here, today...

As I always say, why reuse fundamental classes and interfaces when you can reinvent the wheel, and make it square in the process!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I think the NodeList problems come from an implementation that follows the W3C API too strictly. The win, of course, is that you can swap out back-end implementations on a whim, but given how infrequently that happens, the painful API is a net loss.

    I gotta say, though, the ubiquity of the standard XML APIs is really appealing in Java though. Just knowing that I don't have to think twice about firing up the XSL transformer is nice.