Hi,
In the Mantis, the select_condition rule is modified to:
select_expression ::=
select_condition
| ! select_condition
| select_expression &&
select_expression
| select_expression ||
select_expression
| ( select_expression )
| select_expression with (
with_covergroup_expression ) [ matches integer_covergroup_expression ]
| cross_identifier
| cross_set_expression [ matches
integer_expression ]
Now if someone writes (maybe semantically not correct)
bins apple = X matches 127 && B;
Will it solve to:
(X matches 127) && B
due to presence of && in the select_expression rule or
X matches (127 && B)
due to presence of && in the expression rule itself.
This is clear conflict.
I think we can fix it by adding () around the 'interger_expression'
rule present after 'matches' keyword. Another way is to make
'cross_set_expression [ matches integer_expression ]' as separate
rule parallel to 'select_expression', so that && operator
will not be applied on it. Please let me know.
--
Regards
Surya
--
This message has been scanned for viruses and
dangerous content by
MailScanner, and is
believed to be clean.
Received on Tue Feb 14 06:20:55 2012