Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85465
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender)
Message-ID: <5512C718.2020008@gmail.com>
Date: Wed, 25 Mar 2015 14:32:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c-CbGZ1d3DJSbzPmCbpjm6Pw3qPXQ=CG4XvbaM+528+jQ@mail.gmail.com>	<66c0cca2453de53bed0328af2732c7bd@mail.gmail.com>	<50.00.26446.A7E72155@pb1.pair.com> <CAGAGxbbpDoanY3Y=jLuij+gfQOOqjncsruKR8k4jEc6UKr9eTQ@mail.gmail.com>
In-Reply-To: <CAGAGxbbpDoanY3Y=jLuij+gfQOOqjncsruKR8k4jEc6UKr9eTQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Deprecate or remove mbstring function overloads in
 PHP 7
From: rowan.collins@gmail.com (Rowan Collins)

Chris Wright wrote on 25/03/2015 13:44:
> That said, in the interests of not causing people using this functionality
> issues with logs full of errors and/or error-related performance issues, I
> would support having this deprecation set up in such a way that an error is
> only issued at most once per request - there's no need to issue a
> deprecation warning at every function call.

I guess the advantage of doing it on each function call is that you see 
which areas of code are relying on the feature, rather than just that 
it's enabled.

Maybe we need a smarter way of signalling deprecation in general, 
because it's very all-or-nothing at the moment. But that could possibly 
be implemented as a userland error handler which de-duped errors before 
outputting them.

Regards,
-- 
Rowan Collins
[IMSoP]