3 ms·
I'm going to be honest here, whenever I read things like this more I'm convinced C belongs in the trash can I would accept that pointer overflow is implementat
by raverbashing 10y ago
I'm going to be honest here, whenever I read things like this more I'm convinced C belongs in the trash can
I would accept that pointer overflow is implementation dependent. Allowing it to be "undefined behaviour" is sincerely BS.
Every processor has a "pointer register". Increment it until it overflows. What happens then? Most of the time it will roll over. I suspect this happens in even early RISC architectures that faint if you look at it too hard. There's your answer
It's right, it's not a compiler bug. C tries to solve all problems and cops out on the real issues. The language is broken.
- banachtarski 10y agoNo, it's definitely a compiler bug here.