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?