Hi! > I've looked into it and I'm not sure whether an option for getTrace > method is the best way to solve this. I mean the trace is created > along with the exception so it would have to be generated with the > object fields regardless and then filtered if the option is not set. > I think it would be better to add new PHP directive for this > (disabled by default for back compatibility).
No, I don't think it is a good idea. We have too many config directives already, and behavior-modifying directives is really not a good idea, since it is a global state with all its problems. > Also what do you mean by DEBUG_BACKTRACE_*? Constants used for trace parameters. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
