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.
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
refactor: use parse_address whenever appropriate #723
Conversation
the only place of them I am actually not a 100% sure if it's a good idea changing EDIT: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woohoo Ctrl+H
FTW
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work :)
I like changes like this, but they are also scary. I hope you're able to at least test each command that would be affected by these changes.
Apart from some usages of |
Don't bother, |
refactor: use parse_address whenever appropriate
Description/Motivation/Screenshots
This small refactoring PR replaces the following occurrences with
parse_address
for consistency and easier maintainability:to_unsigned_long(gdb.parse_and_eval(...))
int(gdb.parse_and_eval(...))
How Has This Been Tested?
make test
Checklist
dev
branch, notmaster
.