Doc #61723 [Asn->Csd]: <?php issues a parse error

Edit report at https://bugs.php.net/bug.php?id=61723&edit=1 ID: 61723 Updated by: aharvey@php.net Reported by: lgandras at gmail dot com Summary: <?php issues a parse error -Status: Assigned +Status: Closed Type: Documentation Problem Package: Documentation problem Operating System: Centos 6.2 PHP Version: 5.3.10 Assigned To: aharvey Block user comment: N Private report: N New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2012-04-14 07:04:05] aharvey@php.net Automatic comment from SVN on behalf of aharvey Revision: http://svn.php.net/viewvc/?view=revision&amp;revision=325166 Log: Fix doc bug #61723 (&lt;?php issues a parse error). ------------------------------------------------------------------------ [2012-04-14 04:59:11] aharvey@php.net Reopening as a doc bug and assigning to myself -- we could be a little clearer about this on the escaping from HTML manual page. ------------------------------------------------------------------------ [2012-04-14 04:45:42] rasmus@php.net <?php is an XML PI tag. The full grammar for the tag as defined by the spec is: PI ::= '<?' PITarget (S (Char* - (Char* '?>' Char*)))? '?>' The PITarget in this case is 'php'. The 'S' in the grammar there means whitespace. The first whitespace character signifies the end of the PITarget. If you have no whitespace you do not have a valid PI tag. ------------------------------------------------------------------------ [2012-04-14 04:21:51] laruence@php.net @aharvey ah, thanks, in that case, I would say, this is a rare usage, and a doc will be okey. ------------------------------------------------------------------------ [2012-04-14 04:05:38] aharvey@php.net I was able to. You have to be very careful not to have any whitespace after the <? php — if your editor adds a newline (like vi), then that will cause it to be OK. What I'm not so sure about is whether this is really a bug: the whitespace at the end of the opening tag is really part of the opening tag, so it may just need a documentation update to be clearer. Parser people? What's our expectation here? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=61723 -- Edit this bug report at https://bugs.php.net/bug.php?id=61723&edit=1