@Charles: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/cxx_status.html#rev130953
As of revision 130953 committed on May 5, 2011, clang definitely claims to. I haven't tried writing code against it though.
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
@Charles: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/cxx_status.html#rev130953
As of revision 130953 committed on May 5, 2011, clang definitely claims to. I haven't tried writing code against it though.
What is up with that range-for snippet? The snippet should read:
for (object var : collection_to_loop) { }
instead of
for each (object var in collection_to_loop) { }
see http://en.wikipedia.org/wiki/C%2B%2B0x#Range-based_for-loop
Also, the one C&B attendees comment about lack of support for template aliasing in compilers.... Clang (at least top-of-tree) had it before the conference started.
@Alex C:See theGoingDeep::Advanced_STL_1, its about shared_ptr, also the videos from introductory series are worth to be seen
I think that "Alex C" was reading "MyType ^ ptr0" instead of "MyType * ptr0". The first is potentially valid if MyType was a CLR type and we were compiling with the C++/CLI switch (/clr). Thus his use of the term "handle" and "plain C++ pointer".
On the code example at 7min 22s, why are you using a handle to object instead of a plain C++ pointer?
The screen resolution makes the asterisk look like a caret.