Bug #13610 Updated: heredoc: any chars (even white space) after closing ";" causes error
| From: | derick@php.net | Date: | Tue, 09 Oct 2001 10:10:40 +0000 |
| Subject: | Bug #13610 Updated: heredoc: any chars (even white space) after closing ";" causes error | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-67596@lists.php.net to get a copy of this message | ||
ID: 13610
Updated by: derick
Reported By: rprangnell@hotmail.com
Status: Open
Old Bug Type: Scripting Engine problem
Bug Type: Feature/Change Request
Operating System: Windows98
PHP Version: 4.0.6
New Comment:
It is expected behavior. Although I agree it is not very handy that this is not possible. Making
this a feature request.
Derick
Previous Comments:
------------------------------------------------------------------------
[2001-10-09 06:07:02] rprangnell@hotmail.com
Having carefully searching the bugs database and drawn a blank on this( I made sure to include
'closed' and 'bogus' entries in my search!), I would like to point out that the
new 'heredoc' syntax (which is GREAT) has a little bug that could prove troublesome as it
is hard to spot. The bug is that you can't put anything other than the 'return'
character after the semi-colon that closes the statement. Even a single white space character after
the semi-colon forces a parse error. This can be a poser, especially if the user's editor
can't display non-printing characters.
Typically, this kind of thing won't work:
$query = <<< SQL
SELECT parentID
FROM messages
WHERE msgID = $msgID
SQL; // Can't put a comment (or anything else) here!
I encountered the same bug with both the PWS and the Apache ISAPI module version.
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=13610&edit=1