Comments

According to Windows Phone API reference there are 11,000 Windows Runtime API members supported on Windows 8. The phone supports a subset of 2,800. The Phone also has 600 members not supported on Windows 8.

Search for "Windows Store Apps" "Windows Phone 8" "API is not implemented" to see some examples.

Windows Phone 8 and Windows 8 platform comparison shows the libraries supported in the Common native API: DirectX 11.1, XAudio2, MediaEngine, STL, CRT, and WinSock.

XAML controls comparison between Windows Phone 8 and Windows 8 might help.

Really a great session.  I especially like:

• isocpp.org as a unifying website.
• String literals 
• Initializer lists
• "await" for C++   
• Bjarne's book is coming soon.

Something things I don't like:

• "Windows Store Apps" documentation that omits how to achieve a goal in C++.
• The documentation assumption that you are individually familiar with C# and XAML when explaining how to combine C++ and XAML. 
• Sridhar Poduri's book "Programming Windows 8 Apps using Microsoft Visual C++" is not available yet. 
• Key "Windows Store Apps:" functionality implemented in .NET rather than in language independent that C++ can use.

Some questions I have:

• I'm not sure how to search JUST the Microsoft documentation that pertains to C++ and "Windows Store App" development for a keyword.  (I could in a PDF or windows help file).
• I am not sure yet if you really can take ANY C++/CX and XAML  program from Win8 to Win Phone 8.  There usually is some fine print.

Perhaps this demo should be redone to avoid the "out of disk space" errors that kept disrupting the presentation.

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.