Kendall Bennett wrote:
> 
> [EMAIL PROTECTED] (Theodore Jump) wrote:
> 
> > 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
> 
> We also get tons of 'unreachable code' warnings in the Watcom C++
> compilers.
> 
> > 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.
> 
> I would also like to see all of these warnings gone. However I do not
> advocate using #pragma's and compiler options to turn these off, but
> rather to fix the code so that the warnings no longer show up.
> 
> I would like to try and take a stab at that, if that is OK with the
> rest of the developers.


Please do so.  The sooner the better.  Keep us posted on your check-ins.

-Brian


_______________________________________________
Mesa-dev maillist  -  [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev

Reply via email to