Reposting the issue from the sourceforge https://sourceforge.net/p/flex/bugs/162
The attached test case has one exclusive state COMMENT. Some COMMENT rules there (obviously) can't be matched.
The problem is that addition of some rule for INITIAL state causes the warnings to disappear.
When the XXX rule is commented out, flex (correctly) prints these warnings:
testcase.l:17: warning, rule cannot be matched
testcase.l:18: warning, rule cannot be matched
When the XXX rule is present, flex (incorrectly) doesn't print these warnings.
Any rules in any other states shouldn't affect exclusive states. Each exclusive state should behave exactly as if it was the only state in the lex source.
flex-2.5.38_2 on FreeBSD-9.2
https://sourceforge.net/p/flex/bugs/162/attachment/testcase.l
Reposting the issue from the sourceforge https://sourceforge.net/p/flex/bugs/162
The attached test case has one exclusive state COMMENT. Some COMMENT rules there (obviously) can't be matched.
The problem is that addition of some rule for INITIAL state causes the warnings to disappear.
When the XXX rule is commented out, flex (correctly) prints these warnings:
testcase.l:17: warning, rule cannot be matched
testcase.l:18: warning, rule cannot be matched
When the XXX rule is present, flex (incorrectly) doesn't print these warnings.
Any rules in any other states shouldn't affect exclusive states. Each exclusive state should behave exactly as if it was the only state in the lex source.
flex-2.5.38_2 on FreeBSD-9.2
https://sourceforge.net/p/flex/bugs/162/attachment/testcase.l