I would like to receive(json,ini, associative array,xml, whatever) the tree of include files(something
like that).
The problem can be solved in three ways:
- 1. overload of standard designs
- 2. some magic parameters in the debugger(xdebug cake, but the complete information about dependencies between files does not)
- 3. grep-th and the creation of alternatives(like ov_include and fishing source via debug_backtrace)
- 4. by force of will and eyes to go through all the files
The first option requires the intervention of the interpreter and the work on the updated patch as new versions of php.
The second is unknown to me. In any case, Xdebug config:
zend_extension_ts="D:\\PHP\\ext\\php_xdebug.dll"
xdebug.profiler_enable = 1
xdebug.profiler_output_dir = "D:\\server\\profiling\\"
xdebug.trace_output_name = %t.%s.%H
xdebug.collect_params 1
xdebug.collect_return 1
xdebug.collect_vars 1
xdebug.default_enable 1
xdebug.show_mem_delta 1
php_flag xdebug.auto_trace 1
xdebug.trace_format 1
Third cool and probably the easiest, but from the performance point of view, stern(created a static list array inside the function that checks whether we are not trying to get stuck or to include an existing file, process backtrace, record the results) when a lot of files.
Fourth, for larger projects will not work.
Why.Now a Junior recruit, and documentation for the engine is ready for a third. Want the plotter to print a scheme of work every page so that the guys don't have to guess where and what.