Hello! Virtuous Code is using DISQUS, a powerful comment system, to manage its comments. Learn more.
Community Page
- avdi.org/devblog Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- FKING WESTERN UNION!!!!!!!!!!!!!!!!!!!!!!!!!! I HATE IT!!!!!!!!!!!!!!!!!!!!!!!!!!! IM HAVING THE SAME DARN PROBLEM!! CAN'T LOG IN!!!
- I'm very sad I missed Barcamp (and it would have been great to catch up with you, as well). Hopefully I'll be at the next one. At any rate, I did have a great day-before-father's-day...
- Good insight. A lot of social gatherings like Green Drinks seem to be a majority female. Cross pollination between Greens and Geeks might be a good thing.
- Wow, the hackerspace thing is so rad. I wish there was one in the Harrisburg area.
- Yeah, I overstated, as is my wont. I guess the real issue I have is that the practices are already starting to read a tiny bit like a "Java list". Java was all about taking away all the...
Jump to original thread »
In Ruby, the typical way to define a class is using the class keyword:
class Foo
# ...
end
The class keyword, however, is effectively just syntax sugar for the Class constructor:
Foo = Class.new
# ...
end
Using Class.new is occasio ... Continue reading »
class Foo
# ...
end
The class keyword, however, is effectively just syntax sugar for the Class constructor:
Foo = Class.new
# ...
end
Using Class.new is occasio ... Continue reading »
7 months ago
4 months ago
Thanks for sharing. I ran into this todo when refactoring some examples. It seems so odd that the order in which .inherited is called changes depending on how you construct the class.