On 1/22/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > Nowhere is there any mention of generic functions or adding methods or > criteria, but it internally uses a Dispatcher object that does lookups > based on class and attribute names. So, it's not necessary to expose > generic functions' complexity directly, if all you want to do is define > some type of registry of rules based on standardized access patterns. > RuleDispatch was created in part because I got tired of having to write > new kinds of registry classes all the time for PEAK, every time there I > had some new way of looking things up. RuleDispatch lets me focus on > the app and not on the data structures needed to implement it.
I actually did consider identity.require registering rules in a context, but I couldn't see the value of doing that over just putting an expression in the call to require() and eval'ing it. Kevin
