Re: [RFC] Deprecations for PHP 8.5
| From: | Gina P. Banyard | Date: | Mon, 07 Jul 2025 15:51:10 +0000 |
| Subject: | Re: [RFC] Deprecations for PHP 8.5 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-127937@lists.php.net to get a copy of this message | ||
On Monday, 7 July 2025 at 16:46, Eric Norris <eric.t.norris@gmail.com> wrote:
> > ** Deprecate the error_prepend_string and error_append_string INI directives
> > Why is that of questionable use? Why is "this is a development and debugging
> > feature" considered a valid reason to get rid of something? It allows prominently displaying
> > issues in development when they would be hidden behind other HTML otherwise.
>
>
> I recently made a change to the php_error_cb function for the Error
> Backtraces v2 RFC (https://wiki.php.net/rfc/error_backtraces_v2), and
> I recall that working inside that function was quite difficult. The
> error_prepend_string and error_append_string directives are a tiny
> part of the complexity there, but nonetheless removing them would
> maybe start to move us in a direction of greatly simplifying the
> implementation of php_error_cb, which I would support. I don't have
> strong feelings here, however.
I removed it as it seems my justification was not enough,
if you still think it would be worthwhile by expanding on this complexity, that would be great!
I do know aswell that any call to zend_error() doesn't use the docref IIRC, which leads to very
inconsistent styling.
Best regards,
Gina P. Banyard