Hi Dan Ack,
> Also, I didn't understand why there was a problem with formatting
> traces in userland. I saw a link to some code, but no clear
> description of what the problem was.
I expanded the description of how `getTraceAsString()` might be improperly used
in existing code and moved it to
ht
> >
> > I've created a new RFC
> > https://wiki.php.net/rfc/throwable_string_param_max_len
>
> How come you're proposing an ini setting instead of adding a parameter
> to getTraceAsString() that specifies the length for params?
I don't expect many people to use a parameter for getTraceAsString()
On Sat, 27 Jun 2020 at 16:16, tyson andre wrote:
>
> I've created a new RFC https://wiki.php.net/rfc/throwable_string_param_max_len
How come you're proposing an ini setting instead of adding a parameter
to getTraceAsString() that specifies the length for params?
Also, I didn't understand why the
Hi internals,
I've created a new RFC https://wiki.php.net/rfc/throwable_string_param_max_len
Since 2003, `Throwable->getTraceAsString()` and `Throwable->__toString()`
have limited the length of string function arguments in stringified stack
traces to 15 bytes
(e.g. `#0 /path/to/file.php(line) fu
