Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85455
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.174 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <55119F4E.6010503@gmail.com>
References: <CAF+90c-CbGZ1d3DJSbzPmCbpjm6Pw3qPXQ=CG4XvbaM+528+jQ@mail.gmail.com>
	<006301d06637$ebbb4ee0$c331eca0$@php.net>
	<BLU436-SMTP34001F28C093D64F89F882E20A0@phx.gbl>
	<007901d0664f$dee34430$9ca9cc90$@php.net>
	<55119F4E.6010503@gmail.com>
Date: Tue, 24 Mar 2015 14:35:36 -0600
Message-ID: <CAFMT4Nos6Hm3pGf-av5zfun_GBMSX+y5f14B6d=c9U-8YvybbQ@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Deprecate or remove mbstring function overloads in PHP 7
From: levim@php.net (Levi Morrison)

On Tue, Mar 24, 2015 at 11:30 AM, Rowan Collins <rowan.collins@gmail.com> w=
rote:
> Fran=C3=A7ois Laupretre wrote on 24/03/2015 16:30:
>>>
>>> De : Bob Weinand [mailto:bobwei9@hotmail.com]
>>>
>>> No, he isn't asking for delaying the timeline. He's asking if we can do
>>> this
>>> without RFC. Minimal self-contained changes don't need a RFC and can go
>>> as
>>> well into alpha/beta phase without issues.
>>
>> Sorry, I don't understand when a change is supposed to require an RFC or
>> not, and when it can come after feature freeze or not. Is it written
>> somewhere ? What is the definition of a 'minimal self-contained' change =
?
>> Why is it different if it belongs to an extension ?
>>
>> I may be wrong but the proposed change is not what I call a 'minimal
>> self-contained' change and there's a clear BC break. I'd love it to be p=
art
>> of 7.0 but I would first appreciate to be sure the rules are the same fo=
r
>> everyone.
>
>
> Agreed, this is quite a major feature, and pretty much everything in PHP =
is
> an "extension" as far as the architecture is concerned.
>
> While I agree it would be great to phase this functionality out, I don't =
see
> how that can be done without an RFC.

If we deprecate it I am fine with doing this without an RFC. Removing
it would need an RFC in my opinion.