Sam Lantinga
Sam Lantinga
This is one of those cases where depending on where we move the setrendertargets call, we get different warnings. I'm bumping this out of the 2.24.0 milestone for more investigation....
Here are my thoughts... # Stricter coding, naming style. Generally agreed. We'll need to create an sdl2-compat library similar to sdl12-compat that preserves the old ABI for older programs while...
> # Make SDL_main a header-only lib I like this idea. @icculus, what do you think? Is this something we can implement in 2.0.22?
Another idea for SDL3: * Remove all the complexity around removing API entry points. You can disable subsystems, but the API entry points will remain, with dummy implementations.
IMPORTANT: We will also need sdl20-compat from the very beginning.
SDL3 is the next major ABI breaking revision - what we previously were calling SDL 2.1.
> Please keep the existing way available. Any change will be really disruptive. I haven't yet been able to switch out from 2.0.12 due to the regressions and am just...
Is this ready for review and testing in 2.26.0?
@wooosh, can you review this and update it for the latest main code?