Req #75459 [Opn->Fbk]: debug_backtrace() should include the Closure object

From: Date: Mon, 30 Oct 2017 09:07:58 +0000
Subject: Req #75459 [Opn->Fbk]: debug_backtrace() should include the Closure object
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-212366@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=75459&edit=1 ID: 75459 Updated by: daverandom@php.net Reported by: hegostasla at 2emea dot com Summary: debug_backtrace() should include the Closure object -Status: Open +Status: Feedback Type: Feature/Change Request Package: *General Issues PHP Version: Irrelevant Block user comment: N Private report: N New Comment: Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PHP. Please provide some sample code demonstrating how you expect this to look. Note also that: - it is already possible to get the defining file and line via reflection http://php.net/manual/en/reflectionfunctionabstract.getfilename.php http://php.net/manual/en/reflectionfunctionabstract.getstartline.php - for closures, the defining line and file doesn't always have an unambiguously useful meaning, e.g. for closures created with ReflectionFunction::getClosure(), should the defining file and line be the location of the method call that created the closure, or the location of the definition of the underlying function? Previous Comments: ------------------------------------------------------------------------ [2017-10-30 08:54:10] hegostasla at 2emea dot com Description: ------------ Precisely like it does with the object, it should include the closure object. Currently it is very hard to figure out what is what. The closure objects should also embed the file and line they were defined in, also for debugging purposes. Thank you. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=75459&edit=1

« previous php.bugs (#212366) next »