Comments

I would be interested in comments from Mr Stroustrup on these C++ compiler extensions by Microsoft:

Using Windows Runtime Components in Visual C++

Specifically,

1) The use of "Ref" classes

          Person^ p = ref new Person("Clark Kent");

and their declaration.

2) The use of Platform Strings at the library interface

using namespace Platform;

std::wstring wstr1( L"Test" );

String^ str10 = ref new String(  wstr1.c_str(),   wstr1.length()  );

Will there will be an compiler that produces ARM code that supports these extensions?

My adoption decision depends on:

1) Better documentation on how to use the combination of XAML, WinRT and C++/CX. 

2) Platform targets. My current belief is that the Windows phones will never allow C++, tablets will be Win 8, and WinRT won't apply to the installed base of Windows 7 computers.

I found a way that should help me with the /VMG problem.

#pragma detect_mismatch( "name", "value"))

http://msdn.microsoft.com/en-us/library/ee956429.aspx

Using /vmg  in a static library, but not using it in the application also creates a nasty runtime crash.

See http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/be4af7c2-db82-4976-9faf-df924b4d7339  for details.

So if you are already in the area of preventing incomprehensible runtime crashes by detecting problems due to mismatched compiler options in the linker, perhaps that error might be detected too.

I value the intent of the Windows runtime and the C++ extensions more than some yet to be implemented C++ standard features. 

If VS11 did not support the WinRT reasonably for C++ by Build, that would have been a minor disaster. 

One of the reasons why C took over was the crystal quality of the K&R's "The C programming Language".  VS11's release needs a single document of that quality for C++ and WinRT.

Absolutely topnotch !

Please do another sesion for the other topics in   "Using Windows Runtime Components in Visual C++"  at   http://msdn.microsoft.com/en-us/library/windows/apps/hh454076(v=VS.85).aspx">http://msdn.microsoft.com/en-us/library/windows/apps/hh454076(v=VS.85).aspx

• Value structs  -- Why do we need these? Any chance that the types and data members could be inspectable at runtime?  Are these serializable?
• Properties --  How do you specify whether the property is read-only? Just by not providing a set() ?
• Ref classes --  When should you use them? What C++ class techniques are not allowed in ref classes?
• Interfaces and Parameterized Interfaces -- Please explain parameterized interfaces.
• Delegates -- Looks like delegates can be constructed from plain and member functions.  How about from member functions from classes that are not "ref" ?
• Events -- How to add Events is covered, but how do you fire them?  Where are the methods for "event ReminderEventHandler^ Reminder;" documented?  Can non ref classes declare and use Events?
• Inheritance -- Is is correct to says that ref classes consumed by Javascript must be sealed?  What is "sealed" anyhow?  Is it possible to inherit the metro GUI classes?  There is no documentation present currently.

1) The C++ specific   "Using Windows Runtime Components in Visual C++" needs to be beefed up, and sample code showing how to use std::wstring with the runtime components added.

http://msdn.microsoft.com/en-us/library/windows/apps/hh454076(v=VS.85).aspx">http://msdn.microsoft.com/en-us/library/windows/apps/hh454076(v=VS.85).aspx

2) The C++ team should not let "Building your first Windows Metro style app using C#, C++, or Visual Basic"  at  http://msdn.microsoft.com/en-us/library/windows/apps/br211380(v=VS.85).aspx#getting_data_into_an_app">http://msdn.microsoft.com/en-us/library/windows/apps/br211380(v=VS.85).aspx#getting_data_into_an_app

show that a C++ taking twenty times the source code as C# or VB.   Although I'm sure that was not intentional, an introductory METRO sample should be focused on clarity, not the use of language specific features.

Thanks for an informative low key lecture which helped me understand better how things work in WinRT.   One typo is that your title should be Principal Architect. 

Two concrete suggestions:

1) Improve http://msdn.microsoft.com/en-us/library/windows/apps/hh454076(v=VS.85).aspx">http://msdn.microsoft.com/en-us/library/windows/apps/hh454076(v=VS.85).aspx

with an example that shows mostly standard c++11 code, and then only a few lines of code that interface with the WinRT interface.

WHY: People like to feel comfortable by understanding most of what a program does, and then add to their understanding with something new.  

2) Bundle all the explanations together and send a comprehensive document to everyone who uses Visual C++.   It should have a FAQ that addresses the various concerns present in comments.