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

go to bug id or search bugs for

Bug #6037 unexpected result - parse error ?
Submitted: 2000-08-09 00:45 UTC Modified: 2000-08-10 15:36 UTC
From: elkner at linofee dot org Assigned:
Status: Closed Package: Scripting Engine problem
PHP Version: 4.0.1pl2 OS: Linux (Slackware 7.0)
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: elkner at linofee dot org
New email:
PHP Version: OS:

 

 [2000-08-09 00:45 UTC] elkner at linofee dot org 
Parse error: parse error in test.php on line9.

test.php
<?
        $qid=0;
        if ( $qid ) {
                print <<<EOF
                <p>
EOF;           
        }
?>

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-08-09 00:49 UTC] rasmus@php.net 
Yes, this is a bug.  Workaround: Remove any whitespace after EOF;
 [2000-08-09 23:46 UTC] stas@php.net 
Well, I don't see why it is a bug. Text marker should be strict to not be mixed with the text. Language statements rarely need spaces after them, while texts do. That means, you can do text containing EOF; on the start of the line, just by adding space to it. Are you sure it's a bug?
 [2000-08-10 13:56 UTC] elkner at linofee dot org 
OK. That, so it is not a bug, but a feature ;-)
Sorry, for stealing your time :(
 [2000-08-10 15:36 UTC] stas@php.net 
close it
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved. 		Last updated: Fri Jul 03 13:00:01 2026 UTC