On Wednesday 12 August 2009 07:26:18 Sergei Golubchik wrote:
> [...]
> There are certain warnings and classes of warnings that I don't want to
> see in the code, right. But there are many others - fixing them only
> obfuscates the code, adds ugly hacks (and long comments /* we have to do
> it this
Hi, Henrik!
On Aug 11, Henrik Ingo wrote:
> On Tue, Aug 11, 2009 at 7:27 PM, Sergei Golubchik wrote:
> >> Would be great to get us to compile without any warnings. The
> >> Drizzle people already compile with -pedantic -Werror, so we are
> >> trailing behind there!
> >
> > Just to make a statement
On Tue, Aug 11, 2009 at 7:27 PM, Sergei Golubchik wrote:
>> Would be great to get us to compile without any warnings. The Drizzle
>> people already compile with -pedantic -Werror, so we are trailing
>> behind there!
>
> Just to make a statement (and not to start a flame war:) -
> I strongly believe
Hi, Kristian!
On Aug 11, Kristian Nielsen wrote:
> I have now implemented and installed in our Buildbot enhanced
> facilities for dealing with compiler warnings.
>
> We already have a file support-files/compiler_warnings.supp, which I
> think is used by PushBuild @ MySQL. The new facilities in ou
I have now implemented and installed in our Buildbot enhanced facilities for
dealing with compiler warnings.
We already have a file support-files/compiler_warnings.supp, which I think is
used by PushBuild @ MySQL. The new facilities in our Buildbot uses the same
file to suppress certain warnings t
5 matches
Mail list logo
