Years ago, I took some childish pleasure in naming the class that does whitespace-stripping in Saxon "Stripper.java".
Guess what? The second-most popular entry point to the Saxonica web site from Google is .../javadoc/net/sf/saxon/event/stripper.html
The punters must be very disappointed. I wonder how much I'm paying for the wasted bandwidth?
It's one way to boost my google rankings, I suppose.
|
|
||||||||
Choosing Java class names
Comments
Re: Choosing Java class names
by
Bob DuCharme
on Fri 06 Oct 2006 13:29 BST | Permanent Link
Perhaps it partially makes up for it that people trying to learn more about the Document Information Typing Architecture may end up learning about a stripper instead: http://www.snee.com/bobdc.blog/2006/02/googling_dita.html
Re: Choosing Java class names
by
bryan rasmussen
on Fri 06 Oct 2006 14:21 BST | Permanent Link
you should do a blog post about the stripper, that will really get those ratings up.
Re: Choosing Java class names
by
wolfgang
on Fri 06 Oct 2006 19:15 BST | Permanent Link
By the way, for some more spare time pleasure, see the (open source) projects using saxon, as an RSS feed: http://www.google.com/codesearch/feeds/search?q=saxon
Re: Choosing Java class names
by
Bart Schuller
on Fri 06 Oct 2006 21:12 BST | Permanent Link
In my current (non-Open Source) project, I decided to talk about document Hunks where I could have chosen Chunks.
Creative naming adds a little spice to life. Of course, the creativity is in choosing something that still makes sense, not words like Frobnicator. |
Search
Recent Comments
Recent Articles
Month Archive
|
|||||||