Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54172
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain darkrainfall.org from 209.85.161.46 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAKUjMCU6sUqmmH21AFhZcZr+09b9iMxJgjRCEhKqLLWOkM3CKQ@mail.gmail.com>
References: <EEC7B72B6296471D876EE88FC4A85623@pc07654>
	<4E2AF3D4.9070704@daylessday.org>
	<CAKUjMCU6sUqmmH21AFhZcZr+09b9iMxJgjRCEhKqLLWOkM3CKQ@mail.gmail.com>
Date: Sat, 23 Jul 2011 18:36:35 -0400
Message-ID: <CAMWw8k9A0t62wvZRwp+XAL2pUsvhTWHGExYDwxBhQchbvohUcw@mail.gmail.com>
To: RQuadling@gmail.com
Cc: Antony Dovgal <tony@daylessday.org>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] new gcov.php.net machine is up
From: gwynne@darkrainfall.org (Gwynne Raskind)

In my experience, 100% warnings free is only practical in two cases:

1) When the project is built with that policy from day one.
2) When someone takes the (I'd estimate) two weeks solid work
necessary to eliminate every existing warning from the current trunk,
AND a strict policy of maintaining zero warnings is put in place.
(Believe me, the policy doesn't work if there are any warnings in the
build; people inevitably get lazy.)

Given the variety of warnings that pop up in a PHP build (and don't
even start me on the list thrown up by Clang's static analyzer!), it's
a major undertaking to eliminate all the warnings, and it'll get ugly.

-- Gwynne

On Sat, Jul 23, 2011 at 16:06, Richard Quadling <rquadling@gmail.com> wrote:
> On 23 July 2011 17:16, Antony Dovgal <tony@daylessday.org> wrote:
>> Thanks Nuno, great job!
>>
>> On 07/23/2011 08:03 PM, Nuno Lopes wrote:
>>>
>>> Hi,
>>>
>>> Thanks to Nexcess, we have a new wonderful machine for http://gcov.php.net
>>> up and running.
>>> This new machine is running linux 64 bits, so expect a few differences in
>>> the test results.
>>>
>>> I believe most things are ported from the old machine, including all
>>> daemon's configurations.
>>> I fired an experimental run of the cron job. Please help me by reporting
>>> extensions that are not enabled, daemons that are misconfigured and why
>>> (and
>>> therefore some tests are failing or skiping), missing valgrind
>>> suppressions,
>>> and so on.
>>>
>>> Thanks to Nexcess for offering a new machine to replace the old one.
>>>
>>> Nuno
>
> Excellent work.
>
> I see from the recent report that there are a LOT of similar warnings.
> I'm guessing that those warnings, whilst they are generated on a linux
> x64 box, would be the same for win32 (and anything else).
>
> What sort of policy is needed in addressing casting warnings like
> this. I get a LOT of warnings about casting of doubles/floats to
> ints/longs, along with the potential for potential data loss.
>
> How feasible is it to aim for a 100% warning free build? I'm not
> meaning that we should suppress the warnings.
>
> --
> Richard Quadling
> Twitter : EE : Zend : PHPDoc
> @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>