RFC: Custom callback to dump results in php -a
#5962
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RFC: https://wiki.php.net/rfc/readline_interactive_shell_result_function
readline_interactive_shell_result_function()
that can be used to configure a custom callback to dump results of standalone expressions.
(For interactive shells)
cli.enable_interactive_shell_result_function=0
See ext/readline/tests/readline_interactive_result.phpt for an example of how a
customized callback could be set.
Those hooks can use projects such as php-parser or php-ast to customize
the logic of whether the value of assignments or print() expressions
should not be printed.
Example usage:
The system ini setting
cli.enable_interactive_shell_result_function
can be used to disable this functionality to debug applications that load
buggy handlers. It is enabled by default.
Currently, this only attempts to support single expressions terminated by
;
,if the ini setting is enabled, a handler is configured, and parsing the code doesn't throw a ParseError/CompileError.
See ext/readline/tests/libedit_interactive_result.phpt for an example session.
Related to https://externals.io/message/111073