Re: [PHP] "php -l" - does it find *anything*?

2010-07-08 Thread Gary .
On 7/6/10, Per Jessen wrote: > It really is _only_ the syntax. Same goes for e.g. the C lint - Sorry, but that's not what I remember from my C days, nor what wikipedia says "lint was the name originally given to a particular program that flagged some suspicious and non-portable constructs (likely

Re: [PHP] "php -l" - does it find *anything*?

2010-07-06 Thread Per Jessen
Gary . wrote: > Yeah. There are static checkers out there, even some FOSS ones. I > guess I'm just a bit frustrated that (as you say) the man page says > that "-l" checks syntax but doesn't really detail what kind of things > that covers. It really is _only_ the syntax. Same goes for e.g. the C

Re: [PHP] "php -l" - does it find *anything*?

2010-07-06 Thread David Hutto
On Tue, Jul 6, 2010 at 8:22 AM, Gary . wrote: > Ashley Sheridan writes: >> On Tue, 2010-07-06 at 10:54 +0200, Gary . wrote: > >>     If foo3 never happens to be called when I am doing my testing (for >>     example if the call is in some "if" branch that is never exercised) then >>     it only get

Re: [PHP] "php -l" - does it find *anything*?

2010-07-06 Thread Gary .
Ashley Sheridan writes: > On Tue, 2010-07-06 at 10:54 +0200, Gary . wrote: > If foo3 never happens to be called when I am doing my testing (for > example if the call is in some "if" branch that is never exercised) then > it only gets found in production, so I would like to find this ki

Re: [PHP] "php -l" - does it find *anything*?

2010-07-06 Thread Peter Lind
On 6 July 2010 11:30, Ashley Sheridan wrote: > On Tue, 2010-07-06 at 10:54 +0200, Gary . wrote: > >> Or, alternatively put, is there any way to find the kind of problems in >> foo2 & foo3 (below), at "*compile* time"? >> >> ,[ lint-test.php ] >> | > | >> | error_reporting(E_ALL | E_STRICT); >>

Re: [PHP] "php -l" - does it find *anything*?

2010-07-06 Thread Ashley Sheridan
On Tue, 2010-07-06 at 10:54 +0200, Gary . wrote: > Or, alternatively put, is there any way to find the kind of problems in > foo2 & foo3 (below), at "*compile* time"? > > ,[ lint-test.php ] > | | > | error_reporting(E_ALL | E_STRICT); > | > | function foo1() > | { > | $bar = 'cheese'; >

[PHP] "php -l" - does it find *anything*?

2010-07-06 Thread Gary .
Or, alternatively put, is there any way to find the kind of problems in foo2 & foo3 (below), at "*compile* time"? ,[ lint-test.php ] | ` I only get errors displayed when code happens to pass down the code path, i.e. at runtime: , | /home/jg/work $ php -l lint-test.php | No syntax err