[
https://jira.jboss.org/jira/browse/JBRULES-2051?page=com.atlassian.jira.p...
]
Edson Tirelli closed JBRULES-2051.
----------------------------------
Fix Version/s: 5.0.0.GA
Resolution: Rejected
Hey Wolfgang,
Complain about this to Mark. :) I do it every time this syntax comes up. It is a
non-orthogonal special case where the variable is bound to multiple OR'd patterns at
once:
$cheese : ( Cheese( type == "stilton" ) or Cheese( type == "brie" ) )
So the variable will be bound to the corresponding pattern in each logical branch.
I have a campaign going on to drop support for that syntax. You are welcome to enlist into
my side of the fight! ;)
Cheers,
Edson
Odd rule in DRL.g: lhs_not_binding
----------------------------------
Key: JBRULES-2051
URL:
https://jira.jboss.org/jira/browse/JBRULES-2051
Project: JBoss Drools
Issue Type: Quality Risk
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.0.0.CR1
Environment: any
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Priority: Minor
Fix For: 5.0.0.GA
This NT expands into
not_key fact_binding =>
'not' label ( fact | '(' fact_binding_expression ')' )
Now, fact_binding_expression is just fact { ('or'|'||') fact }
And the NT fact derives into fact_type '(' [ constraints ] ')'
So, what would the binding variable in NT label ever be bound to?
I think that the syntax shouldn't contain the lhs_not_binding rule at all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira