ID: 13938
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Old Status: Feedback
Status: Open
Bug Type: Scripting Engine problem
Operating System: WinNT 4.0
PHP Version: 4.0.6
New Comment:
There are absolutely no newlines. In fact, at this very moment I am making changes to
a web application, and am getting a parse error on line 1837 of a script which has
only 1148 lines.
Previous Comments:
------------------------------------------------------------------------
[2001-11-05 21:43:29] [EMAIL PROTECTED]
Can you check your file for newlines after the %>. I can reproduce the error by
putting 3 or 4 newlines at the end of the file after the closing tag. Because you are
in a string, it errors when it reaches EOF.
------------------------------------------------------------------------
[2001-11-05 16:56:41] [EMAIL PROTECTED]
I saw some previous reports of this bug in earlier versions of PHP 4. It's back in
4.0.6, at least on WinNT 4.0.
Here's an extremely simple sample script:
<%
$test = "This is an improperly terminated string;
%>
This script has a total of 5 lines. The error generated to the browser when this
script is accessed is:
Parse error: parse error in d:\users\tleaver\leaver.com\htdocs\bad.php on line 9
Line 9 does not exist. Unlike previous reports of this bug which I've seen, this bug
does not depend on includes.
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=13938&edit=1
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
