PHP debug_backtrace in production code?
<p>Is there a compelling reason to not use <a href="http://us2.php.net/debug_backtrace">debug_backtrace</a> for the sole purpose of determining the calling method's class, name, and parameter list? Not for debugging purposes.  It has the word "debug" in the function name, which makes me feel a little dirty to be using it in this way, but it fit the bill for what I needed to do (a single function that can be called from many places and needs to call the calling method from another system).  It works, but is this still a bad idea? If so, why?</p>
