Bug #8858 Updated: Mac line endings cause error message with '?'
| From: | elixer@php.net | Date: | Sat, 28 Apr 2001 01:57:16 +0000 |
| Subject: | Bug #8858 Updated: Mac line endings cause error message with '?' | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-52681@lists.php.net to get a copy of this message | ||
ID: 8858
Updated by: elixer
Reported By: davidv@angliaed.co.uk
Old-Status: Open
Status: Bogus
Bug Type: Reproduceable crash
PHP Version: 4.0.4pl1
Assigned To:
Comments:
This is not a bug in PHP. If you are running your scripts on a Unix platform they must be
terminated by a '\n' (0x0A).
Previous Comments:
---------------------------------------------------------------------------
[2001-01-23 13:21:55] davidv@angliaed.co.uk
If a PHP source file is saved with Mac line endings (each line ends with character 13 (0x0D) only)
then any comment that starts with // and ends with a question mark such as:
// Comment?
will cause an error message to be output to the browser:
Parse error: parse error in /home/www/php/admin/syncdb.php on line 1
Note that the ? is NOT at the end of line 1 but can be anywhere in the script.
With either Unix line endings (0x0A) or PC line endings (0x0D + 0x0A) the problem does not occur.
The system is running apache 1.3.14 on a Linux (RedHat 6.0) i586 server.
---------------------------------------------------------------------------
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=8858&edit=2