Way2js4 - Fix VarDataSize computation for ENUM and add trace file #212
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Same as in src/
Preparation for tracing differences in VarDataSize computation
For easier tracing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I finally found the last part where ENUM handling was not correct in src. It was in GenerateProcFuncAsmLabels.
For finding it, I have added the compile-time option USRTRACEFILE, which can now be used to create a "...log" file of the details of the compilation steps in their sequence and with their parameters. If the compile time option is off, no overheader is created.
I also centralized the size computations, so they can be logged more easily if required for an anaylsis.
Future: It may also make sense to collect the messages in memory first and write them into the diag file instead.