Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54175
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMWw8k9A0t62wvZRwp+XAL2pUsvhTWHGExYDwxBhQchbvohUcw@mail.gmail.com>
References: <EEC7B72B6296471D876EE88FC4A85623@pc07654>
	<4E2AF3D4.9070704@daylessday.org>
	<CAKUjMCU6sUqmmH21AFhZcZr+09b9iMxJgjRCEhKqLLWOkM3CKQ@mail.gmail.com>
	<CAMWw8k9A0t62wvZRwp+XAL2pUsvhTWHGExYDwxBhQchbvohUcw@mail.gmail.com>
Date: Sun, 24 Jul 2011 00:47:47 +0200
Message-ID: <CADNQb0WiD4WSHeONb9CNfP2zGyH1wVySUYchyn=3ToFaUTrmdg@mail.gmail.com>
To: Gwynne Raskind <gwynne@darkrainfall.org>, PHP Security <security@php.net>
Cc: RQuadling@gmail.com, 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: hannes.magnusson@gmail.com (Hannes Magnusson)

On Sun, Jul 24, 2011 at 00:36, Gwynne Raskind <gwynne@darkrainfall.org> wrote:
> 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.

Exactly.
And given the nature of PHP, using several dozen bucketloads of
external libraries... it is isn't realistic to eliminate all random
[irrelevant] compiler warnings.

Couple of years ago I have vague memories of "homeland security" [usa]
project, and several projects after that, offering various analyzes of
php-src.
I believe security@php.net receives such reports automatically (they
had login credentials at least).

Removing compiler warnings is (in a project like PHP) generally not a
high priority, but again, if a trusted person commits such a patch.. I
highly doubt it would get reverted.


-Hannes