ID:               28140
 Updated by:       [EMAIL PROTECTED]
 Reported By:      php at richardneill dot org
-Status:           Open
+Status:           Bogus
 Bug Type:         CGI related
 Operating System: Linux
 PHP Version:      5.0.0RC1
 New Comment:

For reference the installation behavior for $EPREFIX/php is documented
here:

http://www.php.net/manual/en/features.commandline.php


Previous Comments:
------------------------------------------------------------------------

[2004-04-25 06:10:08] php at richardneill dot org

Quite right - I do apologise. I had simply assumed that
a script which began with
#!/usr/local/bin/php
would be the CLI version. 
(That's how it used to work, with the Mandrake rpms, but 
I had to compile it myself to have --enable-sockets), and the default
wasn't what I expected.

Sorry for wasting your time.

Richard

------------------------------------------------------------------------

[2004-04-25 05:30:22] [EMAIL PROTECTED]

Not reproducable here, double check that you are indeed using the CLI
version of PHP:

/usr/local/bin/php -v

------------------------------------------------------------------------

[2004-04-25 04:06:54] php at richardneill dot org

Description:
------------
Using php from the command line, the error messages include html tags.
The html_errors directive is supposed to be overridden for PHP-CLI:
http://uk.php.net/manual/en/features.commandline.php



Reproduce code:
---------------
#!/usr/local/bin/php -q
<? 
echo "no semicolon"
?>



run this from the command line.

Expected result:
----------------
Parse error: parse error, expecting `','' or `';'' in
/home/rjn/test.php on line 4

(this is what I see using PHP 4.3.3)

Actual result:
--------------
<br />
<b>Parse error</b>:  parse error, unexpected T_VARIABLE, expecting ','
or ';' in <b>/home/rjn/test/php</b> on line <b>4</b><br />

(this is what I see in PHP 5.0.0RC1)


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=28140&edit=1

Reply via email to