Improve headers consistency - #386
Conversation
|
Do we have the stubs for sceImpose? |
|
For usermode, here: https://github.com/pspdev/pspsdk/blob/master/src/user/sceImpose.S |
|
this looks like gratuitous changes that could break stuff for questionable gain. |
I agree here. This change could impact on homebrew apps downstream , and it seems mostly cosmetic. If you want to define new types it's okay, but current methods should remain unchanged. |
|
That is a fair concern. As far as I know from C standard (and for what I know about C++), as long as the type name remains together with the typedef alias, both I don't know about non-standard C, but they usually only expand what is allowed. Basically, this struct MyStruct { /**/ };To typedef struct MyStruct { /**/ } MyStructAlias;Using But this struct MyStruct { /**/ };To typedef struct { /**/ } MyStructAlias;Is a breaking change, as |
|
I get the feedback, it's not adding much except for the |
|
I tested on real HW in user mode, with |
Hello!
I ran this cleanup pass so that the external python parser that I use doesn't choke on some of the unusual patterns present in the headers. The build passes, I only did simple modifications.
See also: https://github.com/zPSP-Dev/Zig-PSP/blob/trunk/tools/generate_bindings.py#L101
Thanks