Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use uintptr_t instead of u32 when dealing with pointer manipulation #205

Open
roeming opened this issue Apr 30, 2024 · 1 comment
Open

Use uintptr_t instead of u32 when dealing with pointer manipulation #205

roeming opened this issue Apr 30, 2024 · 1 comment

Comments

@roeming
Copy link
Collaborator

roeming commented Apr 30, 2024

Right now, they are equivalent. Looking ahead to future proofing, it'd be nice to have pointers be implementation-agnostic. Which means pointer manipulation being implementation-agnostic.
@roeming roeming changed the title Use size_t instead of u32 when dealing with pointer manipulation Use uintptr_t instead of u32 when dealing with pointer manipulation Jun 4, 2024
@EpochFlame
Copy link
Member

I don't think this was added to C++ until C++11 (which copied it from C99).
If it helps resolve issues for people trying to port Pikmin 2 to a 64-bit architecture, sounds good to me, I suppose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roeming @EpochFlame