Linked by Eugenia Loli on Fri 11th Nov 2005 00:44 UTC, submitted by esther schindler
General Development As part of a larger article about C++'s evolution, DevSource reports on a minor war in the C++ standards community. Don't get excited: the fighting is already over. At issue is whether Microsoft's compiler can say that std::copy is "deprecated" (which usually means "this feature will not be in the next version of the language") when they really mean "our compiler suggests you do not use it." Is this a silly semantic dispute or another sign that Microsoft is trying to hijaack the language?
Permalink for comment 59173
To read all comments associated with this story, please click here.
What I wonder
by japh on Fri 11th Nov 2005 08:01 UTC
Member since:

If std::copy is deprecated, what are they suggesting you use instead? Copying thing isn't something you can take away from the language, obviously.

So what is the Microsoft way of copying?

Reply Score: 1