[llvm-bugs] [Bug 35853] New: Clang 4.0 still uses C++98 by default

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=35853

            Bug ID: 35853
           Summary: Clang 4.0 still uses C++98 by default
           Product: clang
           Version: 4.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: noloader at gmail.com
                CC: dgregor at apple.com, llvm-bugs at lists.llvm.org

Well, this was a surprising result. I noticed it while troubleshooting an issue
where a lambda was not invoked. The lambda was guarded with a macro because the
code is both C++03 and C++11.

Testing on Fedora 27 with LLVM's Clang 4.0:

$ clang++ -x c++ -dM -E - < /dev/null | egrep '(clang|__cplusplus)'
#define __clang__ 1
#define __clang_major__ 4
#define __clang_minor__ 0
#define __clang_patchlevel__ 1
#define __clang_version__ "4.0.1 (tags/RELEASE_401/final)"
#define __cplusplus 199711L

Maybe it would be prudent to change to C++03 or C++11 by default in 2018.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180108/677a5101/attachment.html>