>From what I understand, if I use this setting I need to add it to the OpenEXR >as well. I'll try that.
----- Original Message ----- From: Bob Friesenhahn <[EMAIL PROTECTED]> Date: Friday, October 24, 2008 10:04 pm Subject: Re: [Openexr-devel] Pulling my hair out: switching projecttoVS2008breaks OpenEXR :( To: [EMAIL PROTECTED] Cc: openexr-devel@nongnu.org > On Sat, 25 Oct 2008, [EMAIL PROTECTED] wrote: > > > It turns out that having _SECURE_SCL=0 defined in my project > (not even in the OpenEXR project) is what OpenEXR couldn't > handle--for whatever reason I cannot imagine. What's going on > here? I need this setting as otherwise the slowdown from the > bounds checking the Visual Studio nanny does on STL vectors in > opposition to the standard is unacceptable. > > Google says: > > http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=352481 > > "Specifing a project with #define SECURE_SCL 0 which uses > std::vector<..> may result into a case in which the > application > overwrites memory." > > Bob > ====================================== > Bob Friesenhahn > [EMAIL PROTECTED], > http://www.simplesystems.org/users/bfriesen/GraphicsMagick > Maintainer, http://www.GraphicsMagick.org/ > >
_______________________________________________ Openexr-devel mailing list Openexr-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/openexr-devel
