Inline evals should no longer be necessary, but backward compatibles (i.e., the engine will just ignore them). There should be no change on eval() CEs.

   It seems we still have a bug. I will investigate.

   Edson


2011/6/9 jkrupka <jkrupka@gmail.com>
Should evals be supported in 5.2 with the same syntax that was used in 5.1?
I commented on https://issues.jboss.org/browse/JBRULES-3055, but I'm
wondering if this is a bug or just an undocumented change due to the parser
work in 5.2...?

I haven't tested to see what usage of evals break in 5.2 that worked in 5.1,
I just know that I had multiple compile errors using 5.2.0CR1 on rules that
worked in 5.1 (and even in 5.2.0M2) that had a standalone eval pattern.  The
jira mentions the usage of && in the eval as the thing that causes it to
break, but I haven't confirmed that.

--
View this message in context: http://drools.46999.n3.nabble.com/Evals-in-5-2-tp3043452p3043452.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



--
  Edson Tirelli
  JBoss Drools Core Development
  JBoss by Red Hat @ www.jboss.com