>>>>> "Dave" == Dave Thomas <Dave / PragmaticProgrammer.com> writes:

Dave> OK, but in your example someone wrote code explicitly to bypass the
Dave> fact that it was private.

That's true: it was only an example i've wrote to test the private
thing in Ruby...

I don't want to speak about explicit hacking of well designed classes
 anymore, but only about the fact that we can _accidentally_ overload
 a private method by extending the class or call it from a subclass as
 i've done in my example. At least, in such cases, Ruby should issue a
 warning message (dunno if it's possible to disable such a thing).
 
-- 
Éòic Jacoboni, nil y a 1292459471 secondes