Re: RFC: Making T_FUNCTION optional in method declarations
| From: | Adam Harvey | Date: | Mon, 29 Nov 2010 03:32:29 +0000 |
| Subject: | Re: RFC: Making T_FUNCTION optional in method declarations | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50679@lists.php.net to get a copy of this message | ||
2010/11/28 Johannes Schlüter <johannes@schlueters.de>:
> Without T_FUNCTION token. In my opinion an access modifier /public,
> private protected, static, final) should still be required for keeping
> readability.
I'd be -1 at the moment. The patch is certainly fine, but I think this
has the potential to generate a lot of head-scratchers for neophyte
coders trying to support code across multiple versions, and would
increase our support burden for the benefit of removing a few
keystrokes that every remotely experienced PHP developer already has
committed to muscle memory.
Adam