deprecated C functions

When I compile my project in Visual Studio 2005 Express Edition (Beta 2), I get warnings about functions being deprecated. I added STRSAFE_NO_DEPRECATE and _CRT_SECURE_NO_DEPRECATE to the preprocessor, but I still get all the warnings. We don't have any one header file that I could use to disable the warning with a pragma, so is there another way to turn off the warnings?

Thanks,

Cari

[393 byte] By [CariBegle] at [2007-12-16]
# 1
What are the other warnings that you are still seeing?

Thanks,
Ayman.

AymanShoukry at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...
# 2
Not all functions, that are declared deprecated, were deprecated while adding Secure CRT. You may seen some functions deprecated because their name conflicts with C Standard, for example, itoa(). For those you need to add leading underscore(_itoa). In the latest builds of VS2005, deprecation warning tells exactly what was the reason for deprecation of a specific function.

As for now, as Ayman said, please post link of errors or check corresponding MSDN topics for deprecated functions.

Thanks,
Nikola

NikolaDudar at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...
# 3

If you go the Property Page where you can enter in new preprocessor definitions, and then you go down to see the actual Command Line, you will see that quotes have been put around _CRT_SECURE_NO_DEPRECATE. The /D option is supposed to strip the quotes (according to documentation), but that doesn't seem to work right.

I added /D_CRT_SECURE_NO_DEPRECATE in the Additional Options box, and that fixed the problem.

(I also had trouble with my defined symbol not even appearing on the command line. Can someone confirm that the Preprocessor Definitions input box has trouble translating its input into proper commandline options)

-Aner

Aner at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...
# 4
i don't see how the deprecated string function prototypes can be "left alone" given that wchar.h includes the following:

#ifndef _CRT_INSECURE_DEPRECATE

#define _CRT_INSECURE_DEPRECATE

#endif

i have a lot of code that has been very thoroughly tested in production environments for many years, and i don't really want to go off on some tangent changing everything just to protect me from myself. what am i missing?

tmike at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...