#28155 [Bgs]: clone reserved word? T_CLONE parse error
| From: | helly@php.net | Date: | Tue, 14 Sep 2004 21:22:00 +0000 |
| Subject: | #28155 [Bgs]: clone reserved word? T_CLONE parse error | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-66183@lists.php.net to get a copy of this message | ||
ID: 28155
Updated by: helly@php.net
Reported By: fbn79 at libero dot it
Status: Bogus
Bug Type: Zend Engine 2 problem
-Operating System: winxp pro
+Operating System: *
-PHP Version: 5CVS-2004-04-26 (dev)
+PHP Version: 5*
New Comment:
impossible
Previous Comments:
------------------------------------------------------------------------
[2004-09-14 21:41:51] nospam0 at malkusch dot de
How about turning the keyword off, when
zend.ze1_compatibility_mode is used? There might be some
PHP4 classes (and I had one of them) which have a clone
method and are broken since PHP5.
------------------------------------------------------------------------
[2004-06-03 11:05:12] ben at jazzyphones dot com
Hi
I am getting the same behaviour but am not sure how to fix this based
on the above comments. You say you have updated the summary, can you
link to this summary?
Regards
------------------------------------------------------------------------
[2004-04-26 16:46:03] derick@php.net
Updated summary to make it easier to find for other people running into
this new behavior.
------------------------------------------------------------------------
[2004-04-26 16:45:09] derick@php.net
It's a keyword now, and not a bug (As it's expected behavior)
------------------------------------------------------------------------
[2004-04-26 14:02:38] fbn79 at libero dot it
Description:
------------
I'm not sure if it's a buf or if the function name "clone" was reserved
in php5. The parse errore exist in RC1 and RC2 whith or without
Compatibility Mode OFF or ON
Reproduce code:
---------------
class myclass{
function &clone()
{
....
}
}
Actual result:
--------------
Parse error: parse error, unexpected T_CLONE, expecting T_STRING in ...
on line ...
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=28155&edit=1