Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85447 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29260 invoked from network); 24 Mar 2015 13:39:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Mar 2015 13:39:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:38736] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D4/42-12194-01961155 for ; Tue, 24 Mar 2015 08:39:30 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 1C9BA4B0218; Tue, 24 Mar 2015 14:37:52 +0100 (CET) Reply-To: To: "'Nikita Popov'" , "'PHP internals'" References: In-Reply-To: Date: Tue, 24 Mar 2015 14:39:15 +0100 Message-ID: <006301d06637$ebbb4ee0$c331eca0$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQINGwJxyuYhIX37R6FSHjGdA0ViXZyyOIqA Content-Language: fr X-Antivirus: avast! (VPS 150324-0, 24/03/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Deprecate or remove mbstring function overloads in PHP 7 From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : Nikita Popov [mailto:nikita.ppv@gmail.com] > > The mbstring extension supports replacing PHP string functions with > multibyte variants through the mbstring.func_overload ini option. >=20 > This ini setting is a real PITA for code compatibility, as it makes it > impossible to rely on the output of even the most basic PHP functions, = like > strlen(). Security-critical code in libraries and frameworks typically > handles this issue by conditionally using either strlen() or 8bit > mb_strlen(). Apart from that, the issue is generally ignored. >=20 > If we do not wish to drop support for this option in PHP 7, I would at > least suggest to deprecate it. Probably fine, but how does your suggestion fit in the PHP 7 timeline ? = The BC break requires it is introduced in 7.0. And it is too late for = this. As everyone seems to be against delaying the timeline, I hope we = won't accept exceptions. Regards Fran=C3=A7ois