Apple Event: May 7th at 7 am PT
clang shipped with Xcode 4.3.2 crushed when compile c++11 lambda code.
Code is very simple:
int main() {
auto f=[](){};
f();
}
Compile with:
clang++ -std=c++11 ll.cc
clang crushed at clang::Sema::AddInitializerToDecl with a long stack dump.
Same code compiles with GCC 4.6.1 on Ubuntu.
So?
The latest, bleeding edge of C++ has all sorts of similarly pointless examples that won't compile on this compiler or that one. If this one fails it doesn't mean there is anything wrong with Clang. By the same token, the similar GCC failures don't mean there is anything wrong with GCC.
C++ was so monstrously complex in 1998 that nobody ever managed to write a compiler for it. It sure isn't any better now. That is why people who actually want to get something done use C#, Objective-C, or C.
It is true that C++ is complex; however, that is besides the point. LLVM 3.1 claims that it supports lambdas, initializer lists but fails on both (unlike many other compilers such as GCC or VC++)
Hence my use of the term "bleeding edge". It may be in clang 3.1, but that doesn't mean it is in Apple's branch of Clang that ships with Xcode 4.3.2.
Etresoft is quite correct, lambdas aren't in the Apple branch of Clang that underlies Xcode 4.3. All indications are that you will have to wait for Xcode 4.4 (given that Apple doesn't generally change the compiler version for minor releases of Xcode) or later.
Thanks for your inputs. I suppose the disparity arises from the xcode 4.3.2 project's build setting that allows the following selections:
- Compiler for C/C++/... Apple LLVM 3.1
- C++ Language Dailect C++11[-std=c++11]
- C++ Standard Library libC++ (LLVM C++ standard library with C++11 support)
clang shipped with Xcode 4.3.2 crushed when compile c++11 lambda
