Bug #52515 [Opn->Bgs]: php -l (lint) documentation incorrect/confusing
| From: | markskilbeck@php.net | Date: | Tue, 21 Sep 2010 16:01:02 +0000 |
| Subject: | Bug #52515 [Opn->Bgs]: php -l (lint) documentation incorrect/confusing | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-5103@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=52515&edit=1
ID: 52515
Updated by: markskilbeck@php.net
Reported by: exaxngxums at mailinator dot com
Summary: php -l (lint) documentation incorrect/confusing
-Status: Open
+Status: Bogus
Type: Bug
Package: Documentation problem
PHP Version: 5.3.3
Block user comment: N
New Comment:
Why doesn't it make sense? -l just runs a syntax check. If you want to
know about
errors, other than the syntax, you need to execute the file properly,
which is
exactly what the documentation says.
Previous Comments:
------------------------------------------------------------------------
[2010-08-02 15:13:17] exaxngxums at mailinator dot com
Description:
------------
Under the -l option at
http://php.net/manual/en/features.commandline.options.php
it says
"This option won't find fatal errors (like undefined functions). Use -f
if you would like to test for fatal errors too."
"-f"? Really? That doesn't make any sense, given what -f is for
(actually running the script).
I asked on the users mailing list and Peter Lnid said
"Sounds like a roundabout way of saying "You can only find run-time
errors (such as undefined functions) by actually running the script".
Could definitely need some clarification"
I agree with him, on both points. Please make it explicitly clear what
you mean.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=52515&edit=1