Posted on September 28, 2009
In Ruby, one easy way to check for palindromes would be to write a method such as this:
class String
def palindrome?
self == self.reverse
end
end
But the C++ part of my brain screams that this is likely to be very inefficient. So, today’s kata: test-drive a palindrome? method for String, ensuring (with tests) that it is much faster than the above.
[...] today’s kata « silk and spinach silkandspinach.net/2009/09/28/todays-kata – view page – cached In Ruby, one easy way to check for palindromes would be to write a method such as this: class String def palindrome? self == self.reverse — From the page [...]
I'm Kevin Rutherford, from Macclesfield in the UK. I'm an independent agile software coach and mentor, specialising in test-driven development, agile, lean and the theory of constraints.
Joe Wright
November 25, 2009
It’s interesting to perform the same Kata with different design goals. If you are looking for readability and expressing intent then your example is perfect already.
Optimized version would be: First check length. Then match first and last going inwards.