[rules-users] Overriding default evaluators

[Barry Kaplan]

I should point out that this is only a problem when overriding operators. 

But I won't, at least here, go into the other nasty hacks I have to do to
get around the non-polymorphic ValueType systems. I'm assuming that that
design is there for performance reasons (ie, to eliminate the need for
instanceOf checks) but it really creates serious smells all over the code
base. Ok, I guess I'm going into it ;-)

Consider SetEvaluatorDefintion. It has to define duplicate evaluators for
all the ValueTypes -- even though they all do the same thing. This
duplication is seems to exists only to support the lookup of evaluators by
ValueType. Of course I did not follow this pattern in the scala evaluators
since I'm way too lazy for that ;-)

Anyway, I've worked around all my issues for now. Once I get mostly done
with scala extensions to the DRL syntax I'll compile my issues and maybe we
can discuss modifications to drools internals. 
-- 
View this message in context: http://n3.nabble.com/Overriding-default-evaluators-tp441342p442366.html
Sent from the Drools - User mailing list archive at Nabble.com.