Okay, but it seems that MSVC will not fully implement C++11 and instead is targeting C++14. So our hands are tied. Either we have to say "only the C++11 they managed to implement" or "wait for C++14".
http://blogs.msdn.com/b/somasegar/archive/2013/06/28/cpp-conformance-roadmap.aspx Best Regards, Chris Beck On Wed, Nov 26, 2014 at 5:37 PM, <anonymissi...@arcor.de> wrote: > > I would guess that either we should say "only MSVC supported stuff > please" > > or drop support. > > Not only do windows builds profit from the Linux ones, but also the other > way round. There are sometimes bugs, wrong memory handling in particular, > that valgrind & Co just do not find, but the MSVC debugger does. Dropping > support - bad idea. > "Only MSVC supported" is bad idea too, considering the build issues on > windows even without C++ 11, in combination with the low number and/or > activity of windows devs. > > cheers, > anonymissimus > > _______________________________________________ > Wesnoth-dev mailing list > Wesnoth-dev@gna.org > https://mail.gna.org/listinfo/wesnoth-dev >
_______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
