开发者

Setting Visual C++ Studio/Express to strict ANSI mode

开发者 https://www.devze.com 2023-02-18 04:41 出处:网络
I generally program & compile under Linux with gcc and -ansi flag; but I\'ve been forced with doing a job in Visual C++ and whenever I compile my C code I get all the Microsoft warnings like

I generally program & compile under Linux with gcc and -ansi flag; but I've been forced with doing a job in Visual C++ and whenever I compile my C code I get all the Microsoft warnings like

开发者_如何学JAVA

'fscanf': This function or variable may be unsafe. Consider using fscanf_s instead.

I get these despite following some steps on MSDN Developer's site for setting up an ANSI C project, but all the _s ("secure") calls are not ANSI C!

Any suggestions on putting Visual C++ Studio in a strict ANSI-only mode?

Thanks.


As mentioned in another answer, #define'ing _CRT_SECURE_NO_WARNING will address the specific warnings you mentioned in your question.

If you're really looking for an ANSI-only mode, the closest thing is the /Za compiler switch. Inside the Visual Studio IDE, you can find it in the project's Properties dialog (under Configuration Properties | C/C++ | Language | Disable Language Extensions).

Note that virtually all Windows apps build with Microsoft's compiler extensions enabled; e.g., I don't think you'd even be able to consume Windows SDK headers with /Za set. If your code truly is strict ANSI, you should be OK. If you have a few Windows-specific pieces in a project that is mostly strict ANSI, you could probably isolate those sources and only build those indivudal source files with /Za unset.


These warnings can be suppressed by defining _CRT_SECURE_NO_WARNING

Go to Procect Settings -> Preprocessor and add _CRT_SECURE_NO_WARNING

This isn't forcing compiler to comply with ANSI. Just suppresses use ..._s warnings


One way to suppress specific warnings is to add something like the following to the source.

#if defined( _WIN32 )
#pragma warning(disable:4996)
#endif
0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号