"the upcoming 3.0 and its breaking changes." -- what does this mean ?

[jamesL]

the quote is from https://github.com/SFML/SFML/pull/1235

so what does it mean that 3.0 has breaking changes ?

code samples in existing books will now need "minor" / "major" changes ?

the tutorials and wiki will need significant changes ?

sfml will no longer work on OpenGL < 3.1 ? 

or something inconsequential like "existing programs will need to be recompiled due to changes in sfml dependencies"

[Hapax]

Software written using SFML 2 would need its SFML parts to be modified to match the version 3 interface.

Breaking, in this context, basically means that existing version 2 programs won't run as is without modification.

Note that this is identical to the 'breaking' interface of SFML version 2 from version 1.

It allows major updates to SFML without requiring direct backwards-compatibility. For example, SFML 3 will use C++11 (or later) whereas SFML 2 does not so C++11 (or later) compiler will be required for SFML 3.

All this helps us to understand that it might be some time before SFML 3 appears.


I'd like to know the current design for 3's interface is shaping up (if it's begun) so we can be prepared for it.

[Mario]

Also keep in mind this doesn't necessarily mean your code will break. Depending on how you've written your program, what you're using, etc. it's certainly possible you wouldn't need any change at all.

[MetalCoder]

Is there a roadmap for 3.0? I'm pretty curious to learn what will be coming in the new version of SFML.

[lukaius]

Cant wait but i just a learned sfml 2.4