I've been building the mesa CVS stuff every couple days (mesa-for-cpu
rendering, mesa-for-3dfx, glu, glut, and all the samples/demos/book programs)
with MSVC 6 SP3. Now, I've only got MSVC set for Warning Level 3, not 4,
because the code base does generate a large amount of warnings under WL4
(compilng mesa alone generates over 1000 warnings, I don't know exactly how
much because 1000 is the limit for my shell's rollback buffer...).
The bulk of the warnings are in these categories:
- function 'foo' selected for automatic inline expansion
- unreferenced formal parameter
- conditional expression is constant
- many conversions from 'int' to 'unsigned int' on either assignment
on initialization
- local variable 'foo' may be used without having been initialized
Personally, I would REALLY like to see all of these gone, BUT I don't know how
other people (Brian?) feel on the issue. The first on the list I can take care
of with a msvc-specific #pragma (it IS an msvs-specific warning after all), but
the others require code-motion.
Additionally, the following warnings are currently turned off for Windblows
builds:
'=' : conversion from 'const double ' to 'float ', possible loss of data
'<' : signed/unsigned mismatch
'=' : truncation from 'const double ' to 'float '
'function' undefined; assuming extern returning int
integral size mismatch in argument; conversion supplied
-Ted
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
