Hokie dokie.

Day Job hasn't bought into the rules-engine idea Just Yet, so I'm going
to proceed down the drools path as 100% new development.

Due to .Net considerations and such, I *will* make the rule parser a
modular component.  As long as something implements Parser, and builds
expression trees correctly, any language may be used.

Initially, I'm going to take a step back, and just implement the first
language to be roughly Java, similar to JEOPS.

Once we have a developer-friendly language, we can asses the situation,
and work on creating an idiot^H^H^H^H^H^H management-friendly language.

Regarding compilation of rules, I think we can handle that as well,
for allowing an unmodifiable, static rules base.  Maybe.

        -bob


_______________________________________________
drools-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/drools-interest

Reply via email to