This article will introduce you to some usage analysis of debug_backtrace, debug_print_backtrace and anonymous functions. Students who need to know more can refer to them.
debug_print_backtrace, the difference is that it will directly print the backtrace information.
debug_print_backtrace() is a very low-key function, few people pay attention to it.
But when I call one object to another object and then call other objects and a function in the file and an error occurs, it is laughing.
debug_print_backtrace() can print out the calling process of a page, making it clear where it came from and where it went.
However, this is a proprietary function of PHP5. Fortunately, it has been implemented in pear,
1. debug_backtrace It can backtrace the calling information of the function, which can be said to be a debugging tool
The code is as follows | Copy code | ||||||||
function one() { two(); } function two() { three(); }function three() { print_r( debug_backtrace() ); } /*Output:Array( [0] => Array ([file] => [line] => 10 [function] => three
|
The code is as follows | Copy code |
echo preg_replace_callback('~-([a-z])~', function ($match) { Return strtoupper($match[1]); }, 'hello-world' ); // Output helloWorld ?> |
Keyword connecting closure and external variables: USE
Closures can save some variables and values in the context of the code block. By default in PHP, anonymous functions cannot call the context variables of the code block in which they are located, but need to use the use keyword
The code is as follows | Copy code | ||||
function test(){ $num = 2; $array = array(1,2,3,4,5,6,7,8); |