Adding %define parse.trace
in lrparser.y
#7
durwasa-chakraborty
started this conversation in
Ideas
Replies: 1 comment
-
YACC and POSIX portability.Initially, I thought it could be the issue with POSIX / YACC portability, a specified requirement in the bison documentation. However, that does not seem to be the case. The generated codes, y.tab.h and y.tab.cc should compile and run. Possible issue with Makefile.As the error occurs when the Makefile is linking, it could be an issue with either the Makefile or make itself (for macOS). Some checklists :
Additionally, snapshots of the error would be helpful. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello
I am starting this thread regarding including the
%define parse.trace {}
construct in ourlrparser.y
file. @Barenya255 originally proposed this idea, and you can refer to the related PR here.Overview
The
%define parse.trace {}
is a Bison construct that aims to enhance the parser by providing detailed trace information during parsing. This can be highly beneficial for debugging and understanding the parser's behavior in more complex scenarios.Observations and Current Challenges
While attempting to integrate this feature, we encountered several challenges that caused regressions in our current codebase. We experienced issues when trying to run this on different operating system variants, including macOS and Pop!_OS. Despite multiple attempts, the feature did not work as expected across these systems.
Argument for Inclusion
Despite the regressions, I believe that the inclusion of
%define parse.trace {}
in our codebase would primarily benefit our project in the following ways:Proposed Changes
To ensure that this feature can be successfully integrated without causing disruptions, I propose the following steps:
%define parse.trace {}
feature in stages, starting with a dedicated branch. This will allow us to monitor its impact and make necessary adjustments before merging it into the main codebase.cc: @Barenya255 , could you expand on how we should go about adding the changes? I look forward to hearing your thoughts and feedback on this proposal.
Beta Was this translation helpful? Give feedback.
All reactions