Open elliottcstr opened 5 years ago
Hi @elliottcstr
Thanks for this. I'm painfully aware about the number of parser warnings generated.
I built this thing years ago so my memory is not especially fresh. However, many of the warnings stem from how I wrote the grammar. I wrote it to be almost identical to how the grammar is specified in BNF in the IEEE specification document. The aim of the project being to make it as clear as possible how the bison code related to the specification.
A warning from bison about things like useless rules implies some redundency in how the IEEE BNF grammar is specified. I didn't / still dont' have enough confidence about parser engineering to refactor that amount of stuff away. As you say, there are many warnings, some of which are no doubt solely my own fault.
In terms of fixing this:
@ben-marshall
Roger that. I too, am building a flex/bison parser from the IEEE spec and was looking for any projects to get started. Just wanted to document for onlookers.
Issue Description
Many rule warnings (errors) that need addressing
What should happen:
No/Less Warnings
What actually happens:
Warnings
...only first terminal screen pasted here
Steps to re-create:
bison==3.0.4
flex==2.6.4
(ubuntu-bionic packages)People to Notify:
Related Issues: