On Fri, 4 Nov 2005, Malcolm Rowe wrote:
> On Fri, Nov 04, 2005 at 01:13:24PM -0800, Garrett Rooney wrote:
> > then, there are systems that produce warnings through no fault of our
> > code, which would make this problematic.
> >
>
> Well, that was actually something I wondered about: are there GCC versions
> that produce warnings with -Wall for our codebase? (gcc 3.3.6 doesn't,
> but I wouldn't be too surprised if later versions did).
>
I get lots of "could be used before initialized" for variables tha aren't
initialized and then passed by reference to a function that is supposed to
fill out the variable. This is with 4.0.2. I haven't wanted to silence all
these because that has other problems.
> What I'd quite like is to be able to 'lock in' the '-Wall
-Werror' > choice at configure time, so that I don't have to remember it.
> "./configure CFLAGS='-Wall -Werror'" almost works, except that something
> in APR's configure test can't deal with that (and, thinking about it,
> that probably means it's a Bad Idea to even try).
>
We have EXTRA_FLAGS that you can put in your shell's init script. We could
point that out in hacking and propose a set of good warning options, so
new committers notice.
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 5 13:33:39 2005