Re: Allow (...)->foo() expressions not only for `new`
| From: | Bob Weinand | Date: | Mon, 25 Feb 2013 23:16:33 +0000 |
| Subject: | Re: Allow (...)->foo() expressions not only for `new` | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-66226@lists.php.net to get a copy of this message | ||
Am 26.02.2013 um 00:08 schrieb "Stas Malyshev" <smalyshev@sugarcrm.com>:
> Hi!
>
>> Don't consider it as a syntax change, only as a bugfix. It must have been a
>> bug, that this degree of conformity was not yet reached. :-P
>
> If it changes syntax, it's by definition a syntax change. It does not
> matter if you think it should be changed and if you think it's a bug, it
> still should be properly reviewed and approved.
>
>> It's only stupid to vote about such microscopic changes as long as there are
>> no real arguments against it in the discussion preceding the implementation.
>
> It's not stupid to have RFC for all syntax changes. This allows us to
> keep track of it and gives us venue that all involved (including tool
> makers, etc.) can follow and be reasonably sure they didn't miss syntax
> change because somebody considered it microscopic.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
Ok, you are right. Even if I am not a fan of this bureaucracy, I see that this is
useful and nescessary. I'll appreciate this in future.
Bob