#46084 [Opn->Bgs]: PHP needs a source code analyzer

From: Date: Mon, 15 Sep 2008 23:50:16 +0000
Subject: #46084 [Opn->Bgs]: PHP needs a source code analyzer
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-129006@lists.php.net to get a copy of this message
ID: 46084 Updated by: johannes@php.net Reported By: kevin dot benton at beatport dot com -Status: Open +Status: Bogus Bug Type: Feature/Change Request Operating System: All PHP Version: 5.2.6 New Comment: Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Due to the volume of reports we can not explain in detail here why your report is not a bug. The support channels will be able to provide an explanation for you. Thank you for your interest in PHP. This is no feature to be done by the "core" group of developers, it's better to be done in userland PHP, there are projects like php under control or zend code analyzer as part of zend ide or soem other solutions .... or feel free to implement your own (and become famous) Previous Comments: ------------------------------------------------------------------------ [2008-09-15 17:23:18] kevin dot benton at beatport dot com Description: ------------ PHP needs a really good source code analyzer to report common problems in PHP code (i.e. defaulted parameters before required parameters). Having such a feature makes it easier for new PHP developers to see where problematic code may lie, as well as providing some good best-practices guidelines. I really like the way perltidy does this for Perl code. What's really neat about perltidy is it allows you to help it understand what best practices you want to enforce and what best practices you want to ignore or modify. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=46084&edit=1

« previous php.bugs (#129006) next »