Hi! > And today we have the problem that we cannot use in any useful manner > trigger_error in libraries, when we don't know where the error > originates from. You debug today trigger_error's in libraries with > putting a debug_print_backtrace behind the trigger_error. I think you
Why not use a debugger to debug? Debuggers have backtrace tools. > (there you can add a backtrace) too, but you have to catch them, if > not your script will abort; but I only need a notice...) If you need additional information in the notice, you can always add it to the text of the notice. -- 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
