From: dblack@...
Date: 2006-06-06T21:38:53+09:00
Subject: Re: Ruby and the Open-Closed Principle

Hi --

On Tue, 6 Jun 2006, Codeblogger wrote:

>> The problem is that once you add behavior, it is existing, and someone
>> else might therefore change it.  In other words, you might end up with
>> two versions of a method with the same name.
>
>
> That's why you want to write tests.

Yes, but that's not necessarily enough.  You can't test in advance
every scenario where someone might, later on, have written a new core
method with the same name as yours.


David

-- 
David A. Black (dblack@wobblini.net)
* Ruby Power and Light, LLC (http://www.rubypowerandlight.com)
   > Ruby and Rails consultancy and training
* Author of "Ruby for Rails" from Manning Publications!
   > http://www.manning.com/black