[cfe-dev] RFC: Default language standard mode policy

David Chisnall via cfe-commits cfe-commits at lists.llvm.org
Thu Jun 30 02:02:06 PDT 2016

On 29 Jun 2016, at 23:07, Richard Smith via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> Yes, those are real problems, but it's not reasonable for us to keep the default at C++98/03 forever. GCC has already taken the plunge here, so a lot of open-source code that doesn't work in C++11 onwards already explicitly specifies an appropriate -std= flag.

Could you clarify exactly what the issue is?  Currently, if I have some legacy C++98 code, the odds are that it just compiles with ${CXX}.  If I have new C++11 or C++14 code, then its build system likely sticks on the required -std= flag and it builds independent of what the compiler default is.

What code would be broken by keeping the default at the language version accepted by code that didn’t know about newer standards?  As long as we’re keeping support for C++98 in the front end, keeping the default there doesn’t seem particularly arduous for us and will avoid breaking third-party code.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3719 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20160630/21c8a927/attachment-0001.bin>

More information about the cfe-commits mailing list