Visual c ++ 8.0 hijacking C ++ standards?

Danny Kalev is the host of the C ++ section of informit.com, a slightly nervous and sensitive blogger that I admire and loyal to C ++. Today, he published an article on informit titled "Visual C ++ 8.0 hijacking C ++ standards ". I rushed to see that it turned out to be about a compilation warning. In general, VC ++ 8.0 provides the warning "this function has been deprecated" for some usage of the STD: Copy algorithm ". This is enough. I annoyed Danny, who had always been pure-hearted, and wrote an article to discuss it. According to his article, this is currently in the maillist of the c ++ Standards Committee.

In my opinion, C ++ has the honor to have a group of pure people like Danny Kalev who have never become a plaything in the hands of giants. C ++ also has the honor to have some big players like Microsoft, so that they can continue to develop new tricks and will not suffocate and die. Why does Microsoft warn against this STD: Copy? The reason is simple: security. The STD: Copy behavior is similar to the strcpy and memcpy in C language. It is not a consequence. As long as your mind is short for one second, this algorithm will split your application.

Should I support VC ++? It is also not supported. As I said in my speech at the upcoming C ++ Technology Conference, all improvements that help increase C ++ productivity are commendable. If VC compiler only provides warm suggestions and prompts in good faith, I think there is no dispute here. This prompt may help you avoid the painful debugging of a few weeks. The productivity improvement effect is self-evident. However, Microsoft's warning language is arrogant and beyond the boundary. "Abandon ?", Does Microsoft think it has the right to discard an algorithm in the ISO standard? Just because I developed a compiler? It is as ridiculous as saying that a company that produces a leather ruler can change the measurement of one meter. This is what Danny criticized throughout the article.

But the problem is, look at this title, "hijacking", Danny, and whether your terms have crossed the line? In any case, I don't think vc8 is opposite to Standard C ++. No, I think vc8 is not a tool that evil forces attempt to bring C ++ astray, but an important step to guide C ++ towards the future. However, even if Microsoft wants to attach C ++, the action should be gentle. After all, this is not your own VB and C #. If you want to stick to it, you can stick to it.