Thread: MS is back with more deprecations...

MSVC 2005 Beta 2 has just introduced a whole set of additional nonstandard deprecations, on top of the 'deprecations' made to the C standard library in Beta 1 due to perceived security risks, except to the STL this time.

In particular, I got hammered by a pile of warnings about std::remove(), and I can't find my real errors anymore. Anyway, does anyone know of any security vulnerabilities associated with std::remove(), that don't involve misuse? Because I'm just a little sceptical about MS's recent pushes for changes to the C/C++ standards, and it's more than a little annoying when perfectly healthy code generates an entire output-window full of crazy un-disableable 3-warning deprecation combos, which also happen to list all the template arguments in an obscenely un-compact manner and obscure any useful information.
[end rant]

You can either disable the warning with a pragma or use define _CRT_SECURE_NO_DEPRECATE in your project settings.

I don't know anything specifically in remove but I would not be suprised if something was wrong in there. Maybe I'll take a look later. If you google you can get to some MSDN pages that give you lots of exploit examples.

Here is a good link to start at:

http://msdn2.microsoft.com/library/8ef0s5kh.aspx

OK thanks, I'll take a look (the define worked too, was looking for that some time ago - except for the STL ones, it's _SCL_SECURE_NO_DEPRECATE, not sure exactly why it's SCL rather than STL, but the deprecation code used SCL and that's what worked).

**EDIT**
As far as I can see, most if not all of the 'problems' with the CRT functions can be prevented with minimal effort on the part of the programmer (i.e. eliminating typos and logic errors, as should be done anyway). Not sure about the filesystem stuff though, don't know much about it.