Re: [Openexr-devel] Visual Studio 2k5 beta 2 generates 1000 warnings compiling OpenEXR...

[Florian Kainz]

Bob Friesenhahn wrote:
> On Tue, 30 Aug 2005, Florian Kainz wrote:
>
> > Don't panic.  We have known for a while that Visual Studio likes
> > to complain about our code, we have looked at the warnings, and we
> > will eventually fix them.  We have tested the code extensively, and
> > it does run fine in 32-bit and 64-bit environments.  Most of the
> > warnings flag either problems that are of a more theoretical nature
> > or things that are not actually problems.
>
> I am glad to hear that the OpenEXR code works well at 64-bits on an 
> Itanium CPU running Windows and 64-bit 'x86 Windows.  If so, then 
> OpenEXR must be much better prepared than the vast majority of existing 
> software packages.  I have not yet tried my own code in those 
> environments, but although it works great at 64-bits on other systems 
> (SGI, Compaq Alpha, AMD Opteron with Linux, UltraSPARC) I expect it to 
> go "kersplat" as a 64-bit Windows program.
>
> Some Microsoft compiler warnings are simply annoying.  It seems that
>
>   pragma warning( disable: 4800 )
>
> should eliminate the silly warning about bool conversions.

Let me qualify this... we've tested OpenEXR on 32-bit and 64-bit
Linux (on X86-64, not Itanium), and on 32-bit Windows.  As far
as we know, we don't rely on "long" being the same size as a
pointer.  In a few places, where we really need 64-bit integers,
we use Int64, which is defined as "unsigned __int64" on Windows.