this post was submitted on 18 May 2025
0 points (50.0% liked)
Programming
20211 readers
191 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So you’re telling me
0xDEADBEEF
does not contain the physical address of the thing it points to?It's a technicality about the pointer type. You can cast the type away which typically doesn't change the actual value (but I'm pretty sure that causes undefined behavior)
For your example,
int x = 0xDEADBEEF;
signifies the integer -559038737 (at least on x86.)char *p = (char*)0xDEADBEEF;
on the other hand may or may not point to the real memory address 0xDEADBEEF, depending on factors like if the processor is using virtual or real addressing, etcYes and no, according to the analogy. Just as a word contains the idea of an object, but not the object itself.