#161 Check diagnostics: rule cannot be matched

2.6.0
open
nobody
None
5
2015-11-18
2013-10-04
No

I get the message "lexer.l:36: warning, rule cannot be matched" during a build process on my openSUSE system. I find this strange because the "dot" rule on the line 36 should pick up every character which will not be matched by previous rules. The documentation contains the following description.

... If it finds more than one match, it takes the one matching the most text [...]. If it finds two or more matches of the same length, the rule listed first in the flex input file is chosen.
...

Are any improvements needed for the matching of different single characters here?

1 Attachments

Discussion

  • Markus Elfring

    Markus Elfring - 2013-10-08

    Now I understand a bit better why my last dot rule can be wrong in the shown example.

    By the way: Why can't I close this issue myself?

     
  • Will Estes

    Will Estes - 2015-11-18
    • Group: 2.5.37 --> 2.6.0
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks