"Error in blah.inc, line 13
included from foo.inc line 15
included from bar.inc line 623"
as well as beeing able to "get_include_history()" which returns
the status of this stack would help php developpers _a lot_ I
think. :)
My intention was not
1) extended error messages (you mentioned) or
2) per owner configuration (Michel mentioned)
I aimed at developers too, like you did, to be able to
print a tree-like thing, which would simplify understanding
of foreign scripts, very complex script und scripts you have
not touched for a time and all scripts at all.
Imageine you´ve got an app with 10 included files, you can check then
with ease which files are used in which way by which files like this
(in chronological order
1)mainapp.php
2)sub.1.php
3) sub.sub.1.php
2)sub.2.php
2)sub.3.php
3) sub.sub.3.php
1)process.php
1)footer.php
Thus you can figure out how thinks act in apps with a few and the more the better
include()s.
For development and debugging purposes it would be great to have such a tool.
We have three uses of this function, I think it could convince somebody :)