Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Sorry to bring up this thread again.
Here's a warning I got:
I tried:Code:warning C4996: 'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
but that didn't work.Code:#define _CRT_SECURE_NO_WARNINGS
I used the online(vc++ 2008) help, and it says to "simply define _CRT_SECURE_NO_WARNINGS", with no instructions of how to go about it.
I did some research on the internet, and it appears I need to edit property sheets, but the VC++ 2008 Express instructions for property sheets don't match what I see on the screen(and don't match the options that are available). Perhaps it is for another version of VC++.
Last edited by happyclown; 01-24-2009 at 07:25 PM. Reason: edited compiler warning
OS: Linux Mint 13(Maya) LTS 64 bit.
You may also want to consider using the more secure functions, as well.
True, not as portable, but they are safer. Well, that can be debatable, but at least they help find bugs.
Mostly, simple wrappers can be built for these functions for compilers that do not support these.