[PATH] fix broken mac build on old clangs.

Thiago Macieira thiago at macieira.org
Mon Nov 9 13:47:39 PST 2015


On Monday 09 November 2015 19:33:55 Tomaz Canabrava wrote:
> http://lists.qt-project.org/pipermail/development/2015-July/022219.html

> > thiago's
> > 
> > > answers made me stick with Qt side.
> > 
> > links? is it in that same thread?

That's a link to an email from Simon. I can't find my own answer, but it's in 
the same thread.

My argument was that there's a difference in philosophy. CopperSpice is trying 
to push the envelope of what can be done with C++11, at the cost of leaving a 
lot of compilers and users behind. In fact, their source code cannot be 
compiled even with Microsoft Visual Studio 2015, the latest version. And it's 
entirely source-incompatible with the existing codebase, so it's a pain for 
people to migrate.

Qt is a lot more conservative. Even the C++11 change I've been talking about 
here isn't wholesale. We will require a subset of the C++11 core language 
features and almost none of the C++11 Standard Library features, corresponding 
to the intersection of the GCC 4.7, Clang 3.3 and Microsoft Visual Studio 2012 
support.

Which is equivalent to the VS2012 support. Thanks Microsoft.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358



More information about the subsurface mailing list