Re: GCC warnings for unused global variables

[Laurent Guerby <guerby at acm dot org>]

On Fri, 2003-05-02 at 18:34, David O'Brien wrote:
> On Fri, May 02, 2003 at 01:42:30PM +0200, Bonzini wrote:
> > mankind is warned with at least a year of advance, and let's face that
> > the fix is (more or less) as simple as
> > grep -rl "^static.*const.*rcsid" | perl -i -pe '!$replaced_yet && s/^static.*const(.*rcsid)/volatile$1/ && ($replaced_yet = 1)'.
> 
> You've never worked on a large corporate source base have you?  Just
> making the source change is only 1/2 the battle.  Getting the review
> board (or release engineer, or what ever) approval for wide sweeping
> changes can be quite difficult.

I assume such a body will also disallow compiler change, 
so you won't be hit by the new warning :).

Seriously, someone in your organisation made the decision
to be -Wall warning free, such a decision imply that new
warnings related changes are an accepted maintenance cost
when upgrading compilers.

-- 
Laurent Guerby <guerby@acm.org>