-
Notifications
You must be signed in to change notification settings - Fork 616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iQue] Match z_message #2435
[iQue] Match z_message #2435
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused as to why the new PRINTF
s aren't fenced in a version ifdef.
They don't mess up the debug rom?
The new PRINTFs are in NTSC-only code, so they wouldn't show up in the debug ROM. When matching NTSC we didn't bother to guess what they were (and some of them ended up being subtly different from PAL anyway) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the macros as array accesses look goofy THING(p)[i]
, but dont think theres anything that can really be done about it
we could also write |
Here's how that would look: cadmic@2d9686d |
I like it alot more, but would understand if others are hesitant |
I think I like it better too so I made the change |
@AngheloAlf pinging incase you want to re-review with the new change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I slightly prefer the old syntax but it is fine either way
The big clue was that the debug string
was changed to
so I think they did a find-and-replace everywhere to workaround the EGCS bug. I made macros for
msgCtx->msgBufDecoded
,msgCtx->msgBufDecodedWide
,font->msgBuf
, andfont->msgBufWide
which are kind of annoying to read but maybe not terrible