php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #52515 php -l (lint) documentation incorrect/confusing
Submitted: 2010-08-02 15:13 UTC Modified: 2010-09-21 18:01 UTC
From: exaxngxums at mailinator dot com Assigned:
Status: Not a bug Package: Documentation problem
PHP Version: 5.3.3 OS:
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: exaxngxums at mailinator dot com
New email:
PHP Version: OS:

 

 [2010-08-02 15:13 UTC] 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.


Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-09-21 18:01 UTC] markskilbeck@php.net
-Status: Open +Status: Bogus
 [2010-09-21 18:01 UTC] markskilbeck@php.net
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.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved.
Last updated: Wed Jul 09 11:01:34 2025 UTC