[Data converter] Improve the hex parsing & general functionality #2352
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 spent some more time hacking on this instead of spending my time in a more productive way. This does the following:
dat
deserializing from custom matching stuff to a propernom
parser that accounts for comments and leading0x
tags.dat
files can now parse values with leading zeroes truncated (though we continue to generatedat
files with the leading zeroes included)dat
files will be generated by default asMEMNAME.dat
though this can be customized with-e
flag. I.e.-e out
will generateMEMNAME.out
dat
directory, the tool will look forMEMNAME.dat
which can be retargeted via-e
flag.--to json
target when given a directory as input