Re: Question/comment about the Array to String conversion RFC
| From: | Sara Golemon | Date: | Thu, 19 Mar 2015 17:53:35 +0000 |
| Subject: | Re: Question/comment about the Array to String conversion RFC | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85227@lists.php.net to get a copy of this message | ||
On Thu, Mar 19, 2015 at 1:40 PM, Dan Ackroyd <danack@basereality.com> wrote:
> On 19 March 2015 at 17:14, François Laupretre <francois@php.net> wrote:
>
>> As you may have noticed if you had a look at the RFC or twitter, I have decided to follow
>> people's suggestion.
>> Please note that the switch from E_DEPRECATED to fatal error won't require any new
>> RFC/discussion/vote
>> as the fatal error is considered as approved. I just introduce an E_DEPRECATED phase for
>> 7.0.
>
> You edited the RFC after the voting had closed? You are not allowed to
> edit an RFC after the voting has occurred.
>
Agreed. I hereby change my vote from 'Yes' to 'No' in protest of this action.
> For now, please revert the changes your made to the RFC after it had
> been closed.
>
Please. If we need to change the schedule, let that be a separate RFC.
> And whoever has the power to remove karma, please take
> the power to edit RFCs away from Francois once that has been done.
>
Now that's a bit heavy-handed. Let's call this a slap on the wrist and move on.
-Sara