no we are not going to stop calling it so, for the sole purpose of irritating those people who doesnt like it, any problem with that ?
OK its a good confession post, but, not so encouraging because, well, I myself is a half-c#-half-native-C++ coder and C++/CLI is my glue, now I am frustrated.
and, I am also worrying in another way, cause I dont think C++/CLI is part of the grand new plan for native 'reinanssance', its just some dirty work that have to be done, and if its the case, then it is occupying too much resources of the team, potentially affecting the real exciting new stuff, I can feel the pressure, bad for the health.
actually this is NOT so cool ...... we used to have it in previous versions.
and C++/CLI is NOT about native coding ...... ok sort of but not primarily.
and that post is actually an apology:
We realize this wasn’t what you wanted to happen and an explanation doesn’t help you get your work done if you are affected by this, but we want you to know the truth.
@felix9 Thank you for doing some research but I think you will find the only piece of literature worth quoting about C++ is the standard itself. I did acknowledge the origins of the name "STL" in my second post and queried if we were talking about the same dead implementation and it seems we are.
if read carefully you can see that all of my quotes are talking about the part of the actual standard library, the 'dead implementation' is only mentioned when people want to explain 'why' they are using this term this way.
I dont think the standard itself is 'the only piece of literature worth quoting', surely you are getting way too formal here. this term is so widely used in the industry and academia, everybody understand it and take it naturally, if you want to talk that way then good for you, but we are living people and we dont need to always speak the 'iso standard' language.
WHAH! This means I will suffer THE PAIN so much longer, arrggghhh.
Actually I just want native c++ Intelisense to work inside a C++/CLI project, and inside a ref class, then it will be so much better for me, sigh.
VisualAssist X is my friend but still ...
But there is still hope, since you should release Win8 really fast, and AppStore is important for Win8, especially the Tablet/ARM edtion, so the dev tool for AppStore need to be released even soooner, then I can get my v.Next.
usually the 'non-commercial' license is applied on free (as in beer) software, it will be uncommon if you add this limitation on a nonfree product, while other free editions exists and without the limitation, kinda strange to me. (obviously WinPhone tools are free and can build commercial apps, if you add native sdk to WinPhone, then it'll get weird.)
GTK/Qt, good idea. GTK+ is not ready for Windows yet, but Qt has an existing official vs addin, and ms can please the Nokia guys, so why not. (ps, not conspiracy but actually I do remember some ms guys said their are considering options to support Nokia's other ecosystems, )
you can compile the code but you can't get the designer/wizards/debug extensions/etc working.
and in the book C++ Cookbook, it says (p213) :
The part of the library that comprises the containers is often referred to as the Standard Template Library, or STL, becauses this is what it was called before it was included in the C++ Standard.
I think its a very widely used name to refer this part of C++ Standard Library that incorporated or 'absorbed' from the original STL library.
one more example: in the book "The C++ Standard Library: a Tutorial and Reference" by Nicolai M. Josuttis, there is a chapter called "The Standard Template Library", it starts with:
The heart of the C++ standard library, the part that influenced it overall architecture, is the Standard Template Library (STL).
one more: the C++ Reference site: http://www.cplusplus.com/reference/
(It) can be divided into::
C++ Standard Library: Miscellaneous libraries
C++ Standard Library: Standard Template Library (STL)
C++ Standard Library: Input/Output Stream Library
according to MSDN: http://msdn.microsoft.com/en-us/library/f1dtts6s.aspx
...... Standard Template Library, a subset of the Standard C++ Library.
The C++ library headers have two broader subdivisions:
Standard Template Library conventions.
and STL is a sub-topic under C++ Standard Library in the documentation tree: http://msdn.microsoft.com/en-us/library/c191tb28.aspx
and, according to Dinkumware: http://www.dinkumware.com/manuals/default.aspx#Standard%20C++%20Library
The Standard C++ library consists of 51 headers. Of these, 16 constitute the Standard Template Library, or STL.
wow, live debugging of VC11 !