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?
Thread beginning with 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
japh
Member since:
2005-11-11

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

RE: What I wonder
by sappyvcv on Fri 11th Nov 2005 08:54 in reply to "What I wonder"
sappyvcv Member since:
2005-07-06

It's not deprecated, so it's a moot point.

AFAIK, std::copy is just a memory copy routine for a list.

Reply Parent Score: 1

RE[2]: What I wonder
by japh on Fri 11th Nov 2005 09:00 in reply to "RE: What I wonder"
japh Member since:
2005-11-11

Well, it might not be deprecated, but they obviously wants you to use something else.

std::copy is used to copy from/to all stl containers. It's really quite common, and doesn't just do memory copy.

Reply Parent Score: 1

RE: What I wonder
by gdanko on Fri 11th Nov 2005 18:18 in reply to "What I wonder"
gdanko Member since:
2005-07-15

So what is the Microsoft way of copying?

The world needs to switch to xcopy and UNC paths because Bill said so.

Reply Parent Score: 1