-
Notifications
You must be signed in to change notification settings - Fork 23
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
Migrated code base to use cstdint #48
Migrated code base to use cstdint #48
Conversation
da88b66
to
cead6ba
Compare
I've been both dreading and looking forward to this change. I actually have a very similar looking branch parked ready to rebase after PR #43 but this looks great so far. I've only done a quick scan so far, but I'm happy with the approach. Keen to make sure we don't cause any drams with doco etc for a couple changes (for example) from %lu to %u. But in principle, I like the more modern types and it can only help with portability. It's going to take a few days to pour through and highlight any discussion points so please bear with me. Keen to get your input too @jtxa. It's moments like these I'm grateful for a regression test suite! |
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.
Firstly, my apologies for taking so long to get through this. It is a huge boost for maintainability and modernisation of the codebase. Thank you Sean!
Some minor comments.
a959e37
to
f25f2fd
Compare
First pass at using standard types. Looking for feedback if this is something we want to pursue and how far to go.
Addressed comments in #25 and #26