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 59184
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: What I wonder
by japh on Fri 11th Nov 2005 09:00 UTC 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[3]: What I wonder
by sappyvcv on Fri 11th Nov 2005 09:11 in reply to "RE[2]: What I wonder"
sappyvcv Member since:
2005-07-06

They do? It's not a warning in final, so you don't know that.

Reply Parent Score: 1

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

Of course I don't know that, but there has to be some reason they put the message in there.

From the article:
Author Kate Gregory explained that the code construct presents a security weakness in a programmer's code. "You can turn off that error checking," Gregory said, "but you probably don't want to."

So then there should be a better way to do things, I'm just wondering what way that is. There's not much point in warning you about something if you can't change it to something better.

Reply Parent Score: 2