You can register a shutdown function that gets called even in the case of a
fatal error. We use something like this:
public function init() {
register_shutdown_function(array('Bootstrap', 'fatalErrorCatcher'));
...
}
public function fatalErrorCatcher() {
On 14 May 2011 at 15:05, Peter Lind peter.e.l...@gmail.com wrote:
On 14 May 2011 12:33, Tim Streater t...@clothears.org.uk wrote:
I would like, in my app, to recover from as many run-time errors as possible,
so that I can tidy up. And unsolicited output generated by the standard error
system
On 16 May 2011 22:14, Tim Streater t...@clothears.org.uk wrote:
On 14 May 2011 at 15:05, Peter Lind peter.e.l...@gmail.com wrote:
On 14 May 2011 12:33, Tim Streater t...@clothears.org.uk wrote:
I would like, in my app, to recover from as many run-time errors as
possible,
so that I can tidy
On 16 May 2011 at 21:34, Peter Lind peter.e.l...@gmail.com wrote:
You were trying to call a method on a non-object - how do you expect
PHP to handle that if not with a fatal error?
Anyway, good to hear you solved the issue - I misunderstood what you
wanted to do (shut down in a proper
I would like, in my app, to recover from as many run-time errors as possible,
so that I can tidy up. And unsolicited output generated by the standard error
system is really unhelpful as it becomes part of the ajax reply to the browser.
So I've added my own error handler, but it seems that I
On 14 May 2011 12:33, Tim Streater t...@clothears.org.uk wrote:
I would like, in my app, to recover from as many run-time errors as possible,
so that I can tidy up. And unsolicited output generated by the standard error
system is really unhelpful as it becomes part of the ajax reply to the
6 matches
Mail list logo
