|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #43434 // style comments ending in ?> cause parsing errors
Submitted: 2007-11-28 05:47 UTC Modified: 2007-11-28 08:24 UTC
From: smp_info at yahoo dot com Assigned:
Status: Not a bug Package: *Programming Data Structures
PHP Version: 5.2.5 OS: Windows Vista
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
29 - 27 = ?
Subscribe to this entry?

 [2007-11-28 05:47 UTC] smp_info at yahoo dot com
Any slash style comment (//) that ends with ?> will produce a parse error.

With /* */ style comments, this does not happen.  Have not tested with # style comments.

Reproduce code:

//this line ends with ?>
echo 'hello';




class test
	//this comment ends with ?>
	public function hello()
		echo 'hello';

$test = new test();


Expected result:
I expect both examples to echo the word "hello".

Actual result:
First example: "echo 'hello'; ?>" is printed to the screen.

Second example: Parse error: syntax error, unexpected ';', expecting T_FUNCTION in C:\Apache2\Apache2\htdocs\crap\bug.php on line 5

On a real-world example where I encounted the problem, I got a Parse error: unexpected $end

So the errors vary.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2007-11-28 08:24 UTC]
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at and the instructions on how to report
a bug at

?> marks the end of a PHP block, even when prepended with //
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Jul 21 20:01:30 2024 UTC