Re: Deprecate or remove mbstring function overloads in PHP 7
| From: | Rowan Collins | Date: | Tue, 24 Mar 2015 17:30:54 +0000 |
| Subject: | Re: Deprecate or remove mbstring function overloads in PHP 7 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85452@lists.php.net to get a copy of this message | ||
François Laupretre wrote on 24/03/2015 16:30:
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. Regards, -- Rowan Collins [IMSoP]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.