On Sun, Jul 24, 2011 at 00:36, Gwynne Raskind <gwy...@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 secur...@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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
