Re: try..catch

Andi Gutmans wrote: > 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. > Andi Is it an entirely impossible idea to imagine that the errors and exceptions that are caught would be either [1] thrown explicitly with a throw() clause [2] and/or caught according to an explicit level defined in php.ini [3] caught according to an explicit level defined in the catch() call My preferences would be from 1 to 3, highest first. Did I see a mention of combining try .. catch with the error-reporting operator '@'? Would this be close to the semantics of throw()? -- | Heikki Korpela | heikki.korpela@wapit.com | tel. +358 50 3838 609 | | Software Developer, Wapit Finland | http://www.wapit.com | -- "Ain't working? Umm.. has the operating system been updated?"