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

Greg Hudson <ghudson@MIT.EDU> writes:
> > I don't know. Do you get the listed warnings if you try to compile
> > with gcc3.3? :-)
>
> According to ftp.gnu.org and <http://gcc.gnu.org/>, the current release
> of gcc is 3.2.2. Please do not call things gcc 3.3 and gcc 3.4 when
> they haven't been released yet; for all we know, the warning policies
> will change before then.

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.)

I don't know the answers to these questions. It just strikes me that
the issue here isn't whether we should refer to the next GCC as "3.3",
but whether we should be treating its warnings as useful information
:-).

---------------------------------------------------------------------
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:16:21 2003