#27148 [Opn->Bgs]: a keyword (like print) is not allowed as method name
| From: | andrey@php.net | Date: | Fri, 06 Feb 2004 08:43:23 +0000 |
| Subject: | #27148 [Opn->Bgs]: a keyword (like print) is not allowed as method name | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-54501@lists.php.net to get a copy of this message | ||
ID: 27148
User updated by: andrey@php.net
Reported By: andrey@php.net
-Status: Open
+Status: Bogus
Bug Type: Zend Engine 2 problem
Operating System: linux
PHP Version: 5CVS-2004-02-05 (dev)
New Comment:
next time have to double check. The fault was mine (hmm).
Previous Comments:
------------------------------------------------------------------------
[2004-02-05 20:53:38] alan_k@php.net
/home/alan# php -r 'class a { function print(){}}'
Parse error: parse error, expecting `T_STRING' in Command line code on
line 1
faxserver:/home/alan# php -v
PHP 4.3.2 (cli) (built: Jun 3 2003 11:24:43)
Copyright (c) 1997-2003 The PHP Group
I'm not sure how it could have worked with 4.3.5-dev.. - T_PRINT and
the associated grammer havent changed since it was first checked into
CVS....
------------------------------------------------------------------------
[2004-02-05 16:18:41] andrey@php.net
print, echo, die ...
------------------------------------------------------------------------
[2004-02-04 13:07:36] andrey@php.net
Description:
------------
PHP5 (HEAD) complains when a class has a method named print(). Looks
like the yacc grammar have to modified to allow that. The example code
works without problems with 4.3.5-dev
Reproduce code:
---------------
php -r 'class a { function print(){}}'
Expected result:
----------------
no error
Actual result:
--------------
PHP Parse error: parse error, unexpected T_PRINT, expecting T_STRING
in Command line code on line 1
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=27148&edit=1