Tool to parse and validate PHP script?

[Gilles Ganault]

Hello

Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?

I just noticed that I copy/pasted some code that had lines longer that
can fit in the SSH terminal window, and that caused a run-time error
as reported in the /var/log/httpd-error.log but not in the browser:

[error] PHP Notice: Undefined index: etablissemen\nt in
/usr/local/www/apache22/data/prospect.php on line 49, referer:
http://server/myscript.php

Thank you.

[Rik Wasmus]

Gilles Ganault wrote:

Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?

I just noticed that I copy/pasted some code that had lines longer that
can fit in the SSH terminal window, and that caused a run-time error
as reported in the /var/log/httpd-error.log but not in the browser:

[error] PHP Notice: Undefined index: etablissemen\nt in
/usr/local/www/apache22/data/prospect.php on line 49, referer:
http://server/myscript.php

You can run 'php -l thescript.php' to do a syntax check, however your
error would not be catched by that: this is a run time error, and only
catchable by actually running the script.

Of course, on live websites error should not be shown, but logged, as is
done her apparently.
--
Rik Wasmus

[ELINTPimp]

On May 8, 9:06 am, Rik Wasmus <[e-mail]:

Gilles Ganault wrote:

Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?

I just noticed that I copy/pasted some code that had lines longer that
can fit in the SSH terminal window, and that caused a run-time error
as reported in the /var/log/httpd-error.log but not in the browser:

[error] PHP Notice: Undefined index: etablissemen\nt in
/usr/local/www/apache22/data/prospect.php on line 49, referer:
http://server/myscript.php

You can run 'php -l thescript.php' to do a syntax check, however your
error would not be catched by that: this is a run time error, and only
catchable by actually running the script.

Of course, on live websites error should not be shown, but logged, as is
done her apparently.
--
Rik Wasmus

Any chance to transfer your file by ftp or sftp?

[Peter H. Coffin]

On Thu, 8 May 2008 06:14:40 -0700 (PDT), ELINTPimp wrote:

>Gilles Ganault wrote:

Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?

I just noticed that I copy/pasted some code that had lines longer that
can fit in the SSH terminal window, and that caused a run-time error
as reported in the /var/log/httpd-error.log but not in the browser:

[error] PHP Notice: Undefined index: etablissemen\nt in
/usr/local/www/apache22/data/prospect.php on line 49, referer:
http://server/myscript.php

Any chance to transfer your file by ftp or sftp?

Or use a better configuration on the editor....

--
This was, apparently, beyond her ken. So far beyond her ken that she was
well into barbie territory.
-- J. D. Baldwin

[Rik Wasmus]

ELINTPimp wrote:

On May 8, 9:06 am, Rik Wasmus <[e-mail]:

>Gilles Ganault wrote:

>> Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?
I just noticed that I copy/pasted some code that had lines longer that
can fit in the SSH terminal window, and that caused a run-time error
as reported in the /var/log/httpd-error.log but not in the browser:
[error] PHP Notice: Undefined index: etablissemen\nt in
/usr/local/www/apache22/data/prospect.php on line 49, referer:
http://server/myscript.php

You can run 'php -l thescript.php' to do a syntax check, however your
error would not be catched by that: this is a run time error, and only
catchable by actually running the script.

Of course, on live websites error should not be shown, but logged, as is
done her apparently.

Any chance to transfer your file by ftp or sftp?

What do you mean? 'my file'?

--
Rik Wasmus

[Gilles Ganault]

On Thu, 8 May 2008 06:14:40 -0700 (PDT), ELINTPimp <sm*****@gmail.com>
wrote:

>Any chance to transfer your file by ftp or sftp?

I could do that instead. I'll just have to remember to convert from
CRLF to CR.

Thanks for the "-l" switch.

[ELINTPimp]

On May 8, 9:59 am, Rik Wasmus <[e-mail]:

ELINTPimp wrote:

On May 8, 9:06 am, Rik Wasmus <[e-mail]:

Gilles Ganault wrote:
Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?
I just noticed that I copy/pasted some code that had lines longer that
can fit in the SSH terminal window, and that caused a run-time error
as reported in the /var/log/httpd-error.log but not in the browser:
[error] PHP Notice: Undefined index: etablissemen\nt in
/usr/local/www/apache22/data/prospect.php on line 49, referer:
http://server/myscript.php
You can run 'php -l thescript.php' to do a syntax check, however your
error would not be catched by that: this is a run time error, and only
catchable by actually running the script.

Of course, on live websites error should not be shown, but logged, as is
done her apparently.

Any chance to transfer your file by ftp or sftp?

What do you mean? 'my file'?

--
Rik Wasmus

Sorry, Rik, I replied to the wrong comment. I was referring to the
posters copy/paste method being the problem and skip the need for
checking this post-transfer altogether by transferring the file they
created (and presumably tested) instead of copy/paste over ssh.

[Rik Wasmus]

Gilles Ganault wrote:

On Thu, 8 May 2008 06:14:40 -0700 (PDT), ELINTPimp <sm*****@gmail.com>
wrote:

>Any chance to transfer your file by ftp or sftp?

I could do that instead. I'll just have to remember to convert from
CRLF to CR.

I often work under Windows, however, even under Windows my editor is set
up to \n instead of \r\n all the time. Saves a lot of headaches.

--
Rik Wasmus

[Jerry Stuckle]

Rik Wasmus wrote:

Gilles Ganault wrote:

>On Thu, 8 May 2008 06:14:40 -0700 (PDT), ELINTPimp <sm*****@gmail.com>
wrote:

>>Any chance to transfer your file by ftp or sftp?

I could do that instead. I'll just have to remember to convert from
CRLF to CR.

I often work under Windows, however, even under Windows my editor is set
up to \n instead of \r\n all the time. Saves a lot of headaches.

A text mode transfer will automatically strip or add \r as necessary.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[sheldonlg]

Gilles Ganault wrote:

Hello

Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?

You will never have a compile-time error with PHP since PHP is a script
and, hence, doesn't compile. Perhaps you mean run-time issues?

[Gilles Ganault]

On Thu, 08 May 2008 17:22:59 -0400, sheldonlg <sheldonlgwrote:

>You will never have a compile-time error with PHP since PHP is a script
and, hence, doesn't compile. Perhaps you mean run-time issues?

No, I meant syntax errors that could be picked by just parsing the
source, so those simple issues are detected before actualling running
the program. "php -l" did the trick (along with "... or die" to detect
faulty SQL commands). Thanks.

[Andrius Dijakas]

Gilles Ganault wrote:

On Thu, 08 May 2008 17:22:59 -0400, sheldonlg <sheldonlgwrote:

>>You will never have a compile-time error with PHP since PHP is a script
and, hence, doesn't compile. Perhaps you mean run-time issues?

No, I meant syntax errors that could be picked by just parsing the
source, so those simple issues are detected before actualling running
the program. "php -l" did the trick (along with "... or die" to detect
faulty SQL commands). Thanks.

some editors have syntax checking, as for example jEdit (www.jedit.org) with
phpparser plugin installed.

--
a.d.

[Jerry Stuckle]

Sir Robin wrote:

On Thu, 08 May 2008 17:22:59 -0400, sheldonlg <sheldonlgwrote:

>Gilles Ganault wrote:

>>Hello

Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?

You will never have a compile-time error with PHP since PHP is a script
and, hence, doesn't compile. Perhaps you mean run-time issues?

As far as I understand PHP does in fact first compile the script to byte-code
and then run it... Surely if the code has syntax errors it would result to
compile time error, right?

No, Gilles is correct. PHP is not compiled. It is interpreted. A big
difference. And no, syntax errors are not considered compile-time errors.

Java, OTOH, is compiled to byte code.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Michael Fesser]

..oO(Jerry Stuckle)

>Sir Robin wrote:

>On Thu, 08 May 2008 17:22:59 -0400, sheldonlg <sheldonlgwrote:

>>Gilles Ganault wrote:
Hello

Is there a tool on Linux/FreeBSD that can parse a PHP script to make
sure there's no compile-time issues?
You will never have a compile-time error with PHP since PHP is a script
and, hence, doesn't compile. Perhaps you mean run-time issues?

As far as I understand PHP does in fact first compile the script to byte-code
and then run it... Surely if the code has syntax errors it would result to
compile time error, right?

No, Gilles is correct. PHP is not compiled. It is interpreted.

It's both (hence some even call PHP an "interpiler"). The source code is
compiled into a byte code, which is then interpreted by the Zend engine.
Two steps, two different things.

Caches like APC for example store the _compiled_ code.

>A big
difference. And no, syntax errors are not considered compile-time errors.

It's the parser which chokes upon them, not the interpreter. So they can
be called compile-time errors.

>Java, OTOH, is compiled to byte code.

Which is then executed/interpreted by the VM. Quite similar to PHP, just
done more independently.

Micha