Skip to content
This repository has been archived by the owner on Jan 31, 2018. It is now read-only.

Naming conflicts #1

Closed
jcelerier opened this issue Jul 29, 2015 · 1 comment
Closed

Naming conflicts #1

jcelerier opened this issue Jul 29, 2015 · 1 comment

Comments

@jcelerier
Copy link

Seriously, everybody on earth and maybe up to the international space station uses the terms "Modern C++" for C++11 / C++14.

e.g. Effective Modern C++, etc... http://shop.oreilly.com/product/0636920033707.do

There is also "Modern C++ and Windows Store" that already has a foot hold in the Windows-specific world : http://www.amazon.fr/Modern-C-Windows-Store-Apps/dp/0989020800/ref=sr_1_5?s=english-books&ie=UTF8&qid=1438185205&sr=1-5&keywords=modern+c%2B%2B

@kennykerr
Copy link
Owner

That’s why it’s called "Modern C++ for the Windows Runtime". There's only one standard C++ language projection for the Windows Runtime and this is it.

Plus naming is hard. 😊

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants