Re: try..catch

Quoting Andi Gutmans <andi@zend.com>: > I think one thing I would like to add to what Zeev said, there are a lot of > E_WARNINGS out there. I'm not sure we'd want each one to trigger an > exeception. We might want to pick the functions which would trigger an > exception and add a bitwise or of E_EXCEPTION to their error code. My understanding is that normal php errors would not cause an exception unless they were inside a try {} block? In which case most E_WARNINGS would behave as they do now - subject to the level of error_reporting - and only start raising exceptions when the user explicitly asks to start catching them. If you're going to keep things simple by not letting the user say what kinds of exceptions to catch, I think all exceptions should be available to the user. -chuck -- Charles Hagenbuch, <chuck@horde.org> -- We are not just cogs in a collective happiness machine.