[PEAK] Method replacement and ambiguity resolution using next_method

Christoph Zwerschke cito at online.de
Sat Aug 21 08:23:05 EDT 2010


Am 20.08.2010 20:49 schrieb P.J. Eby:
> However, at least currently, it seems like use of "next_method" is
> rare, so these cases are unlikely to be hidden.
>
> Your thoughts?

Hm, I already disliked the next_method parameter for it's original 
purpose, and I also fear that people will add it now just for indicating 
the relaxed behavior. On the other hand, this approach sounds logically 
consistent. I know I'm not a big help here ;-)

-- Christoph


More information about the PEAK mailing list