I agree that it we should minimize the amount of INI directives. Let's
try and use our brains after 4.0.2 and see what is really needed.
I know it´s not yet after 4.0.2 but I can´t keep it in my brain.
It´s related to debugging too, but not to get_include_history().
Is it possible to get the __FILE__ and the __LINE__ constants in a far function to know from which file and line a function has been called.
That would be extremely handy dealing with custom error handlers for example.
Currently I have to do call my custom error handler with these __FILE__ and __LINE__ constants to make them available to that method.
$this->error->throw(__FILE__,__LINE__);
to display from within throw() "error in file x line y"
It would be very handy to do
$this->error->throw();
and then in the calling method throw()
function throw() {
echo "error in file ".__CALLING_FILE__." line ".__CALLING_LINE__; }
I could imagine that it´s somehow possible, the parser has to know where he has to continue returning from that method.
I don´t think this could be a security threat in any way.
Well maybe all these debug improvements can be done with get_include_history() together.
andré