Re: [avr-libc-dev] vfprintf warnings

[E. Weddington]

On 11 Nov 2002 at 9:42, Theodore A. Roth wrote:

> 
> 
> On Mon, 11 Nov 2002, E. Weddington wrote:
> 
> :) On 11 Nov 2002 at 16:09, Joerg Wunsch wrote:
> :)
> :) > As E. Weddington wrote:
> :) >
> :) > > Since I've been giving it a shot at building avrlibc with the
> latest :) > > snapshots, I've noticed that there are 4 warnings for
> vfprintf.c :) > > stating that 4 variables are possibly uninitialized
> before use: :) > > base, pb, width, and prec. :) > :) > That's OK. :)
> > :) > There's no way to tell gcc to shut up about them. :) :)
> -Wno-uninitialized
> 
> I'd rather not see this used. In most cases, you should get a warning.
> What we have here are special cases which have been given proper
> scrutiny and are justified. We need something like a lint comment in
> the code to disable the warning, not globally turning off the warning.
> In any event, there should be a comment in the code stating that it
> may generate a warning, but it can safely be ignored and why.
> Otherwise, someone in the future will see the warning and "fix" (like
> I almost did on friday).
> 

I was thinking on just using the flag for the module, not project-
wide. Yeah it would be great to have something in the code to bookend 
it and turn off the warning.

Eric