It fucking does. Y'all don't give @davejmurphy enough credit, as far as I can tell devkitppc is the last maintained open source ppc toolchain left and it was for console hacking memes.https://twitter.com/hedgeberg/status/1012226738267545600 …
-
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.
-
I don't believe I "yanked a core typedef" though. I fixed a problem that threw up warnings which showed up a lot of places where daft assumptions were made. Ultimately it improved a lot of code. It also brought devkitPPC in to line with other newlib based toolchains.
- Show replies
New conversation -
-
-
Being honest I think that s32 return type was a mistake as well, but of course hindsight is 20/20.
-
Thanks for being honest. FWIW I appreciate devkitPPC and the work you've done; I'm just saying there's a pattern of breakage and decisions I disagree with (and devkitPPC is not unique; it has its niches though).
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.