Ruby: Defining Class Methods

Jay Fields' Thoughts: Ruby: Defining Class Methods:

"This [, Class.method,] is the version that recent Java/C# converts seem to prefer. I'm not a big fan of this version because it requires me to change all the class method definitions if I change the name of the class." I think it's all a matter of perspective. Class.method seems less magical and makes more sense to me. Especially since Self changes so readily. Since many Ruby purists frown on this I avoid doing it but I dislike Self.method as it is less clear to me. ESPECIALLY when refactoring; contrary to your complaint. If I were to use Class.method I would instantly know what class I'm refactoring and wouldn't have to worry about some recursive reference to Self that might or might not be in play. Using the class name is more precise while using self muddies the waters. Also when you say, "...it requires me to change all the class method definitions if I change the nam...

Full article: http://blog.jayfields.com/2007/10/ruby-defining-class-met...