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] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
