> We can't require any c++11 feature until we drop support for gcc 4.4. > [...] there are problems in the gcc 4.4 system headers that make using c++11 > mode impossible (except on b2g/android).
Is there any reason to support gcc 4.4 outside of B2G/Android? If we dropped support for gcc 4.4 on desktop, would we get auto (and potentially other C++11 niceties)? That seems like a pretty easy win... On Sat, Jul 13, 2013 at 5:00 PM, Mike Hommey <[email protected]> wrote: > On Sat, Jul 13, 2013 at 01:15:31PM -0700, Kyle Huey wrote: >> We've dropped support for versions of MSVC prior to 2010, and we're >> requiring at least GCC 4.4. According to [0] that means we should be able >> to use *auto*. Anybody know any reasons why we can't start using it? > > We can't require any c++11 feature until we drop support for gcc 4.4. Or > remove support for non c++11. Because there are problems in the gcc 4.4 > system headers that make using c++11 mode impossible (except on > b2g/android). I'm happy with removing support for non-c++11 mode now > that m-c is past next esr. > But starting to use C++11 features can be dangerous, as it will make > backporting harder. > > Mike > _______________________________________________ > dev-platform mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
