On Jun 6, 2006, at 8:38 AM, dblack / wobblini.net wrote:

> 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.

I think Codeblogger was trying to say that when someone does write  
that function your test will either fail because your code no longer  
does what the test intends, or it will pass, in which case the code  
will respond accurately even with the new core method.  So there's no  
problem.

Of course, this hinges on comprehensive tests.
-Mat