php.net |  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
 [2007-11-28 05:47 UTC] smp_info at yahoo dot com
Description:
------------
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:
---------------
<?php

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

?>

and

<?php

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

$test = new test();
$test->hello();

?>

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.

Patches

Pull Requests

History

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

?> marks the end of a PHP block, even when prepended with //
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Mon Nov 04 06:01:28 2024 UTC