Hector Martin

That's not what happened Marcan. Please stop telling lies. I know you don't like me but this crap is beneath you.

Dude, when I released the open source HBC (and made a point of trying to build it with the latest devkitPPC/libogc) I had to spend an hour changing a metric fuckload of of types/printf stuff that had changed. Worked on Dolphin but others said not on real HW.

Like, sorry, but there is *no* excuse for changing the size of core types on an established platform. That's a fucking massive ABI-breaking change. You just don't do that.

And yes I know both are 32 bits on this platform, but that doesn't mean they're freely interchangeable. And this isn't the only issue; basically every HBC release we've had where we updated libogc/devkitPro at the same time, we had to fix *some* breakage.

Well *exactly* Marcan. It doesn't mean they're freely interchangeable and the warnings you refer to are because of somebody's code being written as if they are.

You mean "everybody's". This is platform-specific code. The convention for the libogc APIs is to return s32. There's no printf specifier for s32. There is one for int32_t (if you assume *that* mapping never changes), but who uses PRId32 for every single return code?

The point is you don't just up and yank and change a core typedef out from under people without changing the platform specifier. You can argue the code makes non-portable assumptions all you want, but once a platform is defined, it's defined.