Philippe Marschall wrote:
> http://gbracha.blogspot.com/2008/03/monkey-patching.html

I agree with Gilad that extensions and specially overrides (aka monkey 
patching) are dangerous thing to do if you aren't aware of consequences, 
but on the other hand he also concluded that there isn't better and 
established way to solve the problem.

I myself try to follow two rules:

- never override stuff from other,
- do overrides only of my own stuff, in my control and in my images.

That means that I make overrides only in end packages, for instance 
customer specific ones, which are at the end of chain, not overriden 
with any more package.

That way clashes with others overriding the same stuff are more or less 
avoided while advantages of overrides are preserved.

Janko

> 
> 2008/7/13 Janko Mivšek <janko.mivsek at eranova.si>:
>> Dear all,
>>
>> Is there any new Monticello which deals with overrides right? 1.5? 2.0?
>>
>> I just published my packages and again incorrectly because some methods
>> are overridden in extensions of another package. If you do that in
>> current MC, you loose those methods in an original package. Bad!
>>
>> I'm willing to migrate to such MC immediately if available. I think
>> working with overrides is such a powerful feature (not to mention that
>> VisualWorks have that) that Squeak needs the proper support as soon as
>> possible.
>>
>> Best regards
>> Janko
>>
>> --
>> Janko Mivšek
>> AIDA/Web
>> Smalltalk Web Application Server
>> http://www.aidaweb.si
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>

-- 
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si