Re: svn: /php/php-src/trunk/ NEWS Zend/tests/array_type_hint_001.phpt Zend/tests/hint/param_type_hint_001.phpt
Zend/tests/hint/param_type_hint_002.phpt Zend/tests/hint/param_type_hint_003.phpt Zend/tests/hint/param_type_hint_004.phpt Zend/t
| From: | Felipe Pena | Date: | Sat, 22 May 2010 15:03:57 +0000 |
| Subject: | Re: svn: /php/php-src/trunk/ NEWS Zend/tests/array_type_hint_001.phpt Zend/tests/hint/param_type_hint_001.phpt Zend/tests/hint/param_type_hint_002.phpt Zend/tests/hint/param_type_hint_003.phpt Zend/tests/hint/param_type_hint_004.phpt Zend/t |
||
| References: | 1 2 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-62686@lists.php.net to get a copy of this message | ||
2010/5/22 Ilia Alshanetsky <ilia@prohost.org>
> Felipe,
>
> Wouldn't the simpler change be to allow use of no spaces between scalar
> hint and a variable? Basically change + to a *?
>
>
>
But it is not just about 0 or more tab/spaces, there is also \r, \n... which
are inclued in the {WHITESPACE}.
And I consider simpler to match just the type name, thus not needing the
yyless() logic. Hence I also suggested in the patch to remove the _HINT
suffix.
--
Regards,
Felipe Pena