[Lldb-commits] [lldb] r320769 - [ExpressionParser] Rollback C++98 as the standard for evaluating.

[Davide Italiano via lldb-commits]

Author: davide
Date: Thu Dec 14 16:00:17 2017
New Revision: 320769

URL: http://llvm.org/viewvc/llvm-project?rev=320769&view=rev
Log:
[ExpressionParser] Rollback C++98 as the standard for evaluating.

Some ubuntu bots are failing with this patch in, let me unblock
while I investigate.

Modified:
    lldb/trunk/source/Plugins/ExpressionParser/Clang/ClangExpressionParser.cpp

Modified: lldb/trunk/source/Plugins/ExpressionParser/Clang/ClangExpressionParser.cpp
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/source/Plugins/ExpressionParser/Clang/ClangExpressionParser.cpp?rev=320769&r1=320768&r2=320769&view=diff
==============================================================================
--- lldb/trunk/source/Plugins/ExpressionParser/Clang/ClangExpressionParser.cpp (original)
+++ lldb/trunk/source/Plugins/ExpressionParser/Clang/ClangExpressionParser.cpp Thu Dec 14 16:00:17 2017
@@ -381,15 +381,7 @@ ClangExpressionParser::ClangExpressionPa
     // For now, the expression parser must use C++ anytime the
     // language is a C family language, because the expression parser
     // uses features of C++ to capture values.
-
-    // Clang now sets as default C++14 as the default standard (with
-    // GNU extensions), so we do the same here to avoid mismatches that
-    // cause compiler error when evaluating expressions (e.g. nullptr
-    // not found as it's a C++11 feature). Currently lldb evaluates
-    // C++14 as C++11 (see two lines below) so we decide to be consistent
-    // with that, but this could be re-evaluated in the future.
     m_compiler->getLangOpts().CPlusPlus = true;
-    m_compiler->getLangOpts().CPlusPlus11 = true;
     break;
   case lldb::eLanguageTypeObjC:
     m_compiler->getLangOpts().ObjC1 = true;