Painful Ruby Inheritance Quirk

Let’s say you have a class Foo:

Further, let’s say you have a class Bar, derived from Foo, that redefines a couple of things:

It seems kind of obvious that:

But would you have guessed that:

This caused me no end of headaches during a weekend bout of refactoring. Pushing default constants up to the parent class completely hosed me up in those child classes that tried to override them. Overriding dumb getter methods that just return constants, though, works fine.

I’m sure there’s some computer-sciencey reason for this that Matz could explain to me, but I had really expected the every-call-is-a-message nature of Ruby to handle those two cases more consistently.