On Tue, 11 Jan 2022 at 09:11, Tim Düsterhus, WoltLab GmbH <duester...@woltlab.com> wrote: > > So basically all the other languages I researched do not provide > arguments within back traces.
Uh, that kind of suggests that providing arguments at all is a mistake, and that removing could be the way to go. I mean other than everyone complaining about the BC break. An awkward question; why is this hard-coding of the behaviour dependent on a new attribute the correct thing to do? PHP allows people to set_error_handler() to process errors how they like. Conceiveably, allowing users to set a custom function to redact data from stack traces would allow users to inspect and redact the parameters however they like. Why is adding a special attribute that is recognised by the PHP engine itself the right thing to do? To be clear, I can think of at least two reasons. But also, I think every attribute that is proposed to be added to PHP core, needs to have the reasons why it's the right thing to do listed. If nothing else, it will help to reject attributes in the future if they don't have the same strong justifications. cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
