[PEAK] Method replacement and ambiguity resolution using next_method

[Christoph Zwerschke]

Am 21.08.2010 19:01 schrieb P.J. Eby:
> Therefore, by implying that using next_method to redefine an
> existing rule or resolve an ambiguity is like monkeypatching, it will
> be implied that this is a bad thing vs. defining a more specific
> method (more like subclassing than monkeypatching). ;-)

Nice analogy. It's also similar to hooking which is known to be a 
dangerous technique.

 > I am also thinking of splitting AmbiguousMethods into two
 > differently-named subclasses: DuplicateRules and ConflictingRules.

Good idea. I also like the name change from ...Methods to ...Rules.

-- Christoph