Debugging via Google

I just had a funny debugging experience. I had added a new Ant target with a Java task, but when I tried to execute it Ant complained with the following error message:

The <java> type doesn’t support the “classame” attribute

As I didn’t see anything obvious, I did what I often do in those cases: I copied and pasted the error message into Google. This time there were no search results, but Google responded with a helpful message nonetheless:

Did you mean: The <java> type doesn’t support this “classname” attribute

I struggled to see the difference between what I had typed in and what Google suggested and finally realized that I had accidentally omitted an “n” in the “classname” attribute.

Go Google! :)

3 Responses to “Debugging via Google”

  1. Chad R West Says:

    That’s too funny. I’ve found that Google has about the best spell checker around. No matter how badly you munge a word it comes up with what I was looking for. Thunderbird and Outlook don’t even come close.

  2. DigitalHobbit Says:

    Yes, I found Google’s spell checker to be very reliable. Do you know if they use a smart, context sensitive algorithm to come up with alternative suggestions?

  3. Marius Says:

    Nope! They are using what they calls ‘Lexicon’ For more info check http://www-db.stanford.edu/~backrub/google.html. MRG

Leave a Reply