Re: RFC: Making T_FUNCTION optional in method declarations
| From: | James Butler | Date: | Sun, 28 Nov 2010 14:29:08 +0000 |
| Subject: | Re: RFC: Making T_FUNCTION optional in method declarations | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-50653@lists.php.net to get a copy of this message | ||
Is this going to make it harder for newbies to pick up OOP from a code readability point of view
when they look at other people's and framework's code? Also my IDE autocompletes it for me
(maybe I'm being lazy here) so I don't see the overhead as being too onerous ( my personal
view though)
--
James Butler
Sent from my iPhone
On 28 Nov 2010, at 14:02, "Daniel Convissor" <danielc@analysisandsolutions.com>
wrote:
> Hi Again:
>
> On Sat, Nov 27, 2010 at 08:43:40PM -0500, Daniel Convissor wrote:
>>
>> Not that my vote really counts, but -1. Doing so would eliminate the
>> helpful ability to grep source code for 'function bar'.
>
> It also will trip up the multitude of PHP IDE's and editors. Plus it
> reduces code portability. All for saving us making a typo and having to
> write "function"?
>
> --Dan
>
> --
> T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
> data intensive web and database programming
> http://www.AnalysisAndSolutions.com/
> 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>