-
Notifications
You must be signed in to change notification settings - Fork 52
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
Big-endian 'emojis.bin' decoding fix #100
Conversation
looks good just clang-format it (and if it turns |
What? And why? Never used clang-format before, don't even have it installed, and I'm not sure what it's supposed to do or where I am supposed to run it. I'm installing it, but I really don't know why I'm doing this or what the point is. Also, line 93 of what? BTW, when I run it like |
its for formatting but if you dont want to deal with it i think i can add it to the pr myself? ive never done that before though |
See the update.
Trying to add clang 15 to my system now just to see if that changes something for some reason. But I didn't touch line 93 so i don't know why that's something I need to be worrying about/messing with in this PR... shouldn't that be something separate if we're changing other code not related to the endian fixes? Edit:
|
Brain fart. emojis.cpp. not chatinput.cpp. OK, coming up. |
the line 93 thing is because some versions of clang-format will screw up the trailing return type by removing the space even though it should be there |
That code already existed. So why wasn't this done already? Why is that change being introduced by my PR? For the rest of it, the stuff I actually wrote, I understand. And you want me to change
to
rather than
Correct? |
if clang-format doesnt do anything to the line then you can leave it be, and if it does modify it then you can just manually fix it so it remains unmodified. i just preemptively brought it up because clang-format might have incorrectly changed it. |
Which it did. Ok, so I will add the space back in. |
Done. |
See #97
Now synced up with
master
branch instead ofattachments
.It finished compiling at last, and it does work fine on my PowerPC G4 (7447a) and amd64 (nehalem) machines both.
re: long compile times (from the other PR): yeah, it does take a while... but the powerbook is also just a dog performance-wise. It's much more bearable on my other hardware, especially because my other hardware has multiple execution cores.