Re: svn commit: rev 5671 - in trunk/subversion: libsvn_diff tests/libsvn_fs tests/libsvn_subr

On Fri, 2003-04-18 at 12:31, Karl Fogel wrote:
> Should issue #1031 be invalid, then? Is there reason to suspect that
> the warnings generated by whatever-you-want-to-call-unreleased-gcc are
> bogus? (I mean, whether or not the warnings eventually go away
> because the compiler's policy changes, they may still reveal problems
> right now.)

If the warning reveals some problem with our code, like "int" being used
with "apr_size_t" should be, then sure, we should fix it. But the issue
is that we're using the type, not that unreleased-gcc spits out a
warning.

If the warning is bogus, then we certainly shouldn't make our code any
less elegant in order to silence warnings from an unreleased compiler.
(Warnings from a released compiler are a trickier issue.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 18 19:33:03 2003