[PEAK] PEAK Roadmap Update

[Phillip J. Eby]

At 12:26 AM 5/25/2006 +0300, Niki wrote:
>Phillip J. Eby wrote:
>>After that, I'll be starting on a new PEAK-Rules project, whose purpose 
>>will ultimately be to replace both RuleDispatch and PyProtocols, although 
>>it won't do so immediately.
>Any chance for PEAK-Rules to support unregistering of overloads?

Yes, this is one of the requirements driving the desire for pluggable 
engines, as some engines will be optimized for dynamic adds/removes, and 
others will not be.   RuleDispatch's monolithic engine is definitely not 
optimized for unregistering things.