2008.05.26 16:34 "Re: [Tiff] beta2 release - lfind() problem on Win64", by Bob Friesenhahn
It seems that the only cure is to add Windows specific code to handle this specific case.
We have such a code (see port/ directory) and it was used on Windows platform until I discovered that lfind is hidden under _lfind name there. So we can just continue using our implementation.
This sounds like the right approach to me. Of course, care needs to be taken that a wrong prototype from the Windows headers is not applied.
OFF: do they seriously thinking that their "safe" functions really help people?
I think that they are really quite helpful to programmers since they remind that Microsoft Windows has no intention to adhere to ANSI and other internationaly-recognized specifications so some other OS should be used if at all possible. This is just another nail in the coffin for Microsoft in the Enterprise market. Stack and heap exploits are surely a relatively minor concern when trying to achieve security in the Windows environment.
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/