Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Having "Type" as a non-terminal in a Yacc-parser botches c-xref analysis #58

Open
thoni56 opened this issue Apr 25, 2020 · 0 comments
Open

Having "Type" as a non-terminal in a Yacc-parser botches c-xref analysis #58

thoni56 opened this issue Apr 25, 2020 · 0 comments
Labels
bug

Comments

@thoni56
Copy link
Owner

thoni56 commented Apr 25, 2020 •
edited
Loading

For some reason having "Type" as a non-terminal in a Yacc grammar makes the rest of the grammar in-visible to c-xref.

It seems that it has to be capitilized to have this effect.

The issue was found in the java_parser.y in commits prior to 82f0ab6, in which the non-terminal was renamed.
@thoni56 thoni56 added the bug label Apr 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thoni56