Conditional C++11 Support

[eXpl0it3r]

I thought we already agreed on not introducing conditional C++11 support, since it would alone create a lot of work for nearly no gain.

And I agree about the tracker. As long as we still have basic bugs lying around or simple features, we shouldn't start creating one of the bigger construction sites.

[binary1248]

I thought we already agreed on not introducing conditional C++11 support, since it would alone create a lot of work for nearly no gain.

Why is #129 still open?

[eXpl0it3r]

Because it turned into "Full C++11 support", but I guess you can also close it and open a dedicated issue.

[binary1248]

I think contrary to #129, taking C++11 into account when writing SFML 3 isn't really an "issue" that you can tackle on its own. It's something like a coding/design/implementation guideline that should be taken into consideration.

I'll close #129 and won't make a new issue regarding full C++11 support in SFML 3, it just doesn't make sense.

[Laurent]

SFML 3 won't be a full rewrite from scratch, we'll have to convert existing code to C++11 so in my opinion it is a task.

[binary1248]

I agree that it is a task, but I don't think it fits with the rest of the issues on the tracker, which are either bug reports or requests for new features. It is something we will do while working on SFML 3. We also don't have issues for "Correct whitespace errors" or "Correct spelling mistakes" do we?

[Laurent]

Maybe we should create tasks such as "add move construction / assignment", "replace sf::Thread with std::thread", etc. because if we just adapt the code when we see something that can be changed, we'll leave SFML in an inconsistent/messy state.

[Hiura]

The page Roadmap 3.0 could be used to keep such tasks.

[binary1248]

I'll leave formulating the task list to you then.

[Jesper Juhl]

Migrating a C++98 codebase to C++11 (or C++14) can be a big task. But I've personally found that using Clang Modernizer can be a nice first step in the right direction.
It is not perfect and only supports a limited number of transformations, but I've found it to be a great starting point for legacy codebases.
Maybe check it out when you start work on SFML 3 ? :-)