if someString != null and someString.length() > 0
Another similar experience occurred later this afternoon, when I found myself wondering, "Where is the java List.find() method and how do I give it a closure to execute?" Oh silly me, I was doing it again. Closures in java? What was I thinking? I went to the bathroom and splashed some cold water on my face to wake up from this ambiguous land of juby or rava or wherever my brain was.
The interesting part of this story is that when I went home and started playing with ruby, I didn't start thinking, "How can I add more parentheses? How can I turn this closure into an annoying class that implements a few obscure interfaces?" To me, it was a good real-life example of how the good ideas behind good tools stay with you because they're good ideas. In other words, a closure is really handy, and so is simple and expressive syntax, so my brain didn't want to let go of those ideas. It wasn't just a difference in dialect.
June 17th, 2005 at 08:11 AM yet another reason that I am a dentist.Although I like the idea of good tools sticking with you because they are good tools. I understood that much.