On Tue, 2009-08-11 at 17:33 -0400, Casey Dahlin wrote: > This makes EventOperators N-ary rather than binary trees. It > auto-optimizes them with a new event_operator_add_child helper that > simply gifts all of the new child's children to the new parent rather > than attaching it when the new parent and child are of the same type. > > This makes it a bit easier to make qualitative statements about trees, > particularly "this tree only contains OR operators," which should become > useful as AND operators become deprecated in future state models. > Thanks Casey. Could you explain a little bit more about the rationale behind these changes? Right now this just looks like a different way of constructing the operator trees, and unless I'm mistaken, it's more expensive to build them this way, they use more memory per node and they're more difficult to iterate than the btrees we currently use. Are you working on something else that requires this? Perhaps it'd help to outline that work as well to the ML. One thing I'd like to ask about - I don't have any plans to deprecate AND operators; could you tell us a little bit about your plans in this regard? > > === modified file 'ChangeLog' > --- ChangeLog 2009-08-04 08:51:25 +0000 > +++ ChangeLog 2009-08-11 05:51:31 +0000 > @@ -1,3 +1,60 @@ > +2009-08-11 Casey Dahlin