I think this is a great idea. Perhaps for now we can just use a shared Google doc until something more official is built. Adding it to our todo list now.
Could we build up a knowledge base of code we can apply when making the tests. Eg. how do you turn off certain features, like RegExp? How do you shuffle an array? Stuff like that.
Though I agree to some extent this will severely limit the numbers of submitted katas! I for one, cannot write in ruby and will likely not be able to deliver a working Ruby solution on most of the katas I write.
Coffeescript - in my personal view - shouldn't be a languague as it's "simply" a preprocessor. You can wrait it all in javascript and wrap it in "escape-to-javascript"-coffeescript.
I am dissapointed in the number of solutions I see that are object based.
Disclaimer: I am a Rubyist, and as such I have only been practicing Ruby kata.
The entire point of training with kata is to develop positive habits with practice. If you are developing in an OO language, the positive habits you want to develop are Object Oriented in nature. If the code you produce while training with kata is not Object Oriented, then you are not developing habits that will help your Object Oriented programming!
In my opinion, Ruby is one of the greatest OO languages ever produced. We should be using the power of Objects that it provides!
It's not very idiomatic Ruby to force a regexp match to return a boolean (true/false).
In Ruby, the Regexp class's #=~ and #match methods return nil (false-y in Ruby) if no match was found, or a Fixnum (truth-y in Ruby) which is the first match's index position in the string if a match was detected.
Therefore, in my opinion, the test case should have read:
Test.expect(validPhoneNumber("(123) 456-7890"), 'expected "(123) 456-7890" to be valid' )
Google doc has been added.
:-)
Will be looking forward to it - in any form it may take.
I think this is a great idea. Perhaps for now we can just use a shared Google doc until something more official is built. Adding it to our todo list now.
Could we build up a knowledge base of code we can apply when making the tests. Eg. how do you turn off certain features, like RegExp? How do you shuffle an array? Stuff like that.
Though I agree to some extent this will severely limit the numbers of submitted katas! I for one, cannot write in ruby and will likely not be able to deliver a working Ruby solution on most of the katas I write.
Coffeescript - in my personal view - shouldn't be a languague as it's "simply" a preprocessor. You can wrait it all in javascript and wrap it in "escape-to-javascript"-coffeescript.
I am dissapointed in the number of solutions I see that are object based.
Disclaimer: I am a Rubyist, and as such I have only been practicing Ruby kata.
The entire point of training with kata is to develop positive habits with practice. If you are developing in an OO language, the positive habits you want to develop are Object Oriented in nature. If the code you produce while training with kata is not Object Oriented, then you are not developing habits that will help your Object Oriented programming!
In my opinion, Ruby is one of the greatest OO languages ever produced. We should be using the power of Objects that it provides!
This comment is hidden because it contains spoiler information about the solution
I thought about this, but I decided this kata could be performed without seriously impacting any core Classes.
It's not very idiomatic Ruby to force a regexp match to return a boolean (true/false).
In Ruby, the Regexp class's #=~ and #match methods return nil (false-y in Ruby) if no match was found, or a Fixnum (truth-y in Ruby) which is the first match's index position in the string if a match was detected.
Therefore, in my opinion, the test case should have read:
Test.expect(validPhoneNumber("(123) 456-7890"), 'expected "(123) 456-7890" to be valid' )