I did not have a look at the implementation of the include functions, but this feature would make sense to me.
More than that, we could also use the history for error messages (quite useful!) as well as detecting infinite loops
('a.php' includes 'b.php' which includes 'a.php'...) that cause
crashes at the moment...
I would be interested on working on this if you think this is desirable.
I already thought at. I first thought it would be good to allow a parameter included_by() which tells the paraent level you want to get,
this feature/change request would have nothing to do with the former one.
Such a feature would be a great point, debugging scripts (escpecially large scripts you´re not working alone on).
If you´d the possibility to access the parent include()er files, you would be able with a simple task to figure out which files are involved currently in the scripts and who includes who. I don´t think it´s possible with the current design and I have no time at the moment, to explain, why it would be that great, cos I´m in rush. I´ll write sth. later on this topic.
regards
--
· André Langhorst · t: +49 571 3201801 ·
· waldschrott@php.net · m: +49 173 9558736 ·
· PHP Quality Assurance · http://qa.php.net ·