php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #10348 php -l (lint) disabled?
Submitted: 2001-04-16 14:43 UTC Modified: 2001-06-18 19:58 UTC
From: colin at easydns dot com Assigned:
Status: Not a bug Package: PHP options/info functions
PHP Version: 4.0 Latest CVS (16/04/2001) OS: RH/Debian
Private report: No CVE-ID: None
View Add Comment Developer Edit
 [2001-04-16 14:43 UTC] colin at easydns dot com 
"php -l script.php" doesn't seem to do anything.

If it's been removed, then we should remove it from the list of "php -h" options.

- Colin

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-06-01 17:04 UTC] sniper@php.net 
Works just fine for me.
(it's syntax check only, ie. try putting some error in you script..)

--Jani
 [2001-06-18 17:57 UTC] colin at easydns dot com 
Sorry to open it again, but I don't think it is working, even with 4.0.6rc2.  Take this script with the missing semi-colon:

x.php
--------------------
    <?php
    $a = array(1,2,3,4)
    print_r($a);
    ?>

Then, "php -l x.php" outputs nothing, but "php x.php" returns the expected:
    X-Powered-By: PHP/4.0.6RC2
    Content-type: text/html

    <br>
    <b>Parse error</b>:  parse error in <b>x.php</b> on line <b>4</b><br>


- Colin
 [2001-06-18 19:58 UTC] sniper@php.net 
With PHP 4.0.6RC3 I get parse error when run php -l.

Are you compiling from the tar.gz package Andi made 
or are you getting PHP/Zend from CVS with the tag?
If so, I'd say you should get clean checkouts of all PHP/Zend/TSRM to be sure. 

As this is definately fixed, I'm closing this. Further
discussion by private email / on php-dev@lists.php.net

We don't need to pollute bugdb with bogus bug reports
by ourselves, do we? :)
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue Apr 16 14:01:29 2024 UTC