theo
theo
I'll look into getting this working with the GitHub workflow soon
More important than compatibility with other documentation is compatibility with existing header files, sdks, etc. like tonc and dkp. It might be frustrating for people if that is strayed from.
> Yes, I think it's *entirely reasonable* that if we provide alternate names that we'd require of ourselves to also provide a matching alternate header file to go with it....
This should have been fixed
Oops, thats my bad. I just pushed a fix that specifies char signedness in that spot, it should build now!