So the project file for the Jucer is for Visual Studio 2005. That’s fine; I’d been meaning to upgrade anyhow.
However, building JUCE with VS 2005 yields 15 compiler warnings about deprecated functions in the run-time library. The deprecated functions are all ones that could potentially cause buffer overflows and there are replacement functions that don’t have that problem.
The problem is that the replacement functions aren’t cross-platform. Some of them are inside JUCE_WIN32 blocks anyhow, so that’s no big deal. Other ones aren’t.
There is a preprocessor macro that can be set to not show the warnings about deprecated functions. I could just turn that on.
However, it does seem to me that the code is better with the new functions. It makes the code less clean 'cos you have to litter it with more #ifdef JUCE_WIN32 lines, but that’s not too bad.
The other snag is that I don’t think the newer, more secure functions are available in the older Microsoft libraries. I guess we’d have to check and see if they’re in the new Platform SDK.
Unless someone’s got a better solution to all this?