Re: IsSubclass test reordering [WAS: Patch to clear RuleSet]

> BTW, any tips on how to trace which functions are being called under what
> rules? I hacked something for RuleDispatch some time ago [1] (the
> _make_func_logger) but felt kind of dirty. Is there any way to implement
> similar functionality, more elegantly, in peak.rules? I've though of an
> around() method that logged every next_method's func_name or something but
> then I realized that will be called just once for each call to the "base"
> gf, not on every "around", "before", "after" and chained "when"s that
> might be executed for a single call to the "base" gf (I'm sure there's a
> formal name for "base gf"... but unknown to me, sorry). Please note that
> this is not a feature request, I know you're a busy man, but a request for
> a small bump in the right direction so I can implement it myself.

Forgot to add the URL:
[1]
http://toscawidgets.org/trac/tw/browser/tw/core/genericfunctions.py?rev=200%3A23ab23f98f43#L144

Alberto