Re: Comments on PHP security
| From: | Ilia Alshanetsky | Date: | Thu, 11 Jan 2007 18:01:21 +0000 |
| Subject: | Re: Comments on PHP security | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-27376@lists.php.net to get a copy of this message | ||
On 11-Jan-07, at 12:53 PM, Alain Williams wrote:
On Thu, Jan 11, 2007 at 06:44:35PM +0100, Derick Rethans wrote:Uhm those are PHP tools for PHP code, what do they have to do with internals. Rather then whining about "if I only had tool XYZ" use what's already widely available. Ilia AlshanetskyThat is why there is a concept called "testing" [1] and code coverage [2]. [1]. http://phpunit.de/ [2]. http://sebastian-bergmann.de/archives/578-Code-Coverage-Reports-with-PHPUnit-3.htmlYou are an experienced and careful programmer, that is why you understand the value of doing this sort of thing. The trouble is that most PHP programers are not experienced and/or careful ... that is *why* many PHP scripts have nasty bugs in them. As I said: we are looking at ways of helping the sort of person who would not come near this mail list.