Thread: Switch Problem

Originally Posted by JVene

Thus:

#pragma warning( disable: nnnn );

where nnnn is the warning number


For portable code, this should be wrapped in a conditional block for the ms compiler

This disables the warning from there onward, which will silence any such warnings in the following code. Thus you need to do something like this:

Code:

#ifdef _MSC_VER // Detect if it's Microsoft's compilers
#pragma warning(push)
#pragma warning(disable: nnnn)
#endif
// Code
#ifdef _MSC_VER
#pragma warning(pop)
#endif

Originally Posted by whiteflags

"A lot of other problems"? Microsoft's warning doesn't even mention why x was deprecated in favor of x_s, so there is no silencing of any issues regardless, it's merely an authoritative tenet. The macro doesn't remove any other warning, either, according to their docs.

It's clearly outlined in the documentation why to use the *_s versions.
Warnings aren't always so informative.
The macro removes ALL warnings about deprecated functions.

That would be the point since Microsoft is deciding what is deprecated and what is not, clearly, but there isn't "a lot of other problems". There's no reason why warning can't be made informative either.

Originally Posted by whiteflags

That would be the point since Microsoft is deciding what is deprecated and what is not, clearly, but there isn't "a lot of other problems".

I don't think so.
They made a point about deprecating non *_s functions because clearly they're dangerous and Microsoft is the company of security. That's basically the only functions in the C library they've deprecated.
They have full right to deprecate their own API, too, of course, so there's no problem there.

There's no reason why warning can't be made informative either.

Warnings usually need to be short enough or we'd full length explanations about every error we get. The term deprecated usually tells a developer "this function might go away soon, so I should avoid it if I can." So it's fitting for a warning, but if it's the best for this kind of warnings is debatable.

Perhaps there are better ways. What way would you choose?
And I agree the warning isn't the best one - at first I thought those functions would be removed.