Yes, please open a JIRA. This is an error in the parser that needs to be fixed or it may bite our foot later.
Michael Neale < michael.neale <at> gmail.com> writes:
> could you paste an example of this as a new bug in JIRA? if it did work with
previous, it should work with trunk.Michael .
I think this is OK and I presume it is just a warning - I've been doing some
other work with ANTLR and I had the debugger catching this exception. I got
it down to eval(3 == 3) causing the exception but the rule still worked.
Interestingly eval(3 >= 2) did not cause a problem. Do you want me to raise a
JIRA for this?
rules-users mailing list