Re: Deprecate or remove mbstring function overloads in PHP 7

On Tue, Mar 24, 2015 at 11:30 AM, Rowan Collins <rowan.collins@gmail.com> wrote: > François 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 part >> of 7.0 but I would first appreciate to be sure the rules are the same for >> 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.