Closed masatake closed 7 months ago
My idea:
%x COND
...
<COND> {
...
}
The first COND is introduced as a new name that points to a language object. The second COND is not introduced as a new name. Instead, the second COND refers to the language object introduced with the first COND.
Attention: 4 lines
in your changes are missing coverage. Please review.
Comparison is base (
c26e151
) 85.38% compared to head (33d3068
) 85.38%.
Files | Patch % | Lines |
---|---|---|
optlib/lex.c | 0.00% | 4 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
https://sources.debian.org/patche/exuberant-ctags/1:5.9~svn20110310-11/python-disable-imports.patch/
From the comment in the patch, You will know why I am concerned about whether a language object is extracted as a definition or reference tag.
In some lexers, all the rules for a condition are grouped together as:
It is useful to be able to jump to these blocks.
Conditions used for grouping are tagged as reference tags having "grouping" role of "cond" kind. So you must add --extras=+r to your ctags cmdline for enabling this support.
Update the parser version to 1.1.
This is derrived from #3937.