Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85515
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.181 as permitted sender)
Message-ID: <5515D57F.9070505@gmail.com>
Date: Fri, 27 Mar 2015 15:11:11 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Nikita Popov <nikita.ppv@gmail.com>, 
 PHP internals <internals@lists.php.net>
References: <CAF+90c-CbGZ1d3DJSbzPmCbpjm6Pw3qPXQ=CG4XvbaM+528+jQ@mail.gmail.com>
In-Reply-To: <CAF+90c-CbGZ1d3DJSbzPmCbpjm6Pw3qPXQ=CG4XvbaM+528+jQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Deprecate or remove mbstring function overloads in
 PHP 7
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

I was never happy about this particular hack but that said, unless we
*know* it is not used widely (and I suspect it is in Japan etc. where we
don't have a lot of visibility due to language barrier) we can't really
remove it.

Also, I'm not sure why should we remove it. Yes, it's a PITA for the
code, but looking at it in another direction, it is only a PITA if
people actually turn it on, which means they're using it (otherwise why
turn it on?). Deprecating it may be ok provided we actually have some
proposal as to what people should do instead.

If we have consensus on deprecating it, I don't think it's a problem
have it done in 7.0 since it's not a substantial code/feature change and
beta period provides ample time for people to scream if it's
unacceptable. If there's no consensus yet, I'd go for 7.1.

-- 
Stas Malyshev
smalyshev@gmail.com