Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24350
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7.0.1.0.2.20060712181246.05f91d40@zend.com>
Date: Wed, 12 Jul 2006 18:13:52 +0300
To: Michael Wallner <mike@php.net>
Cc: internals@lists.php.net
In-Reply-To: <97.00.12962.7DE73B44@pb1.pair.com>
References: <97.00.12962.7DE73B44@pb1.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] More valuable error message handling
From: zeev@zend.com (Zeev Suraski)

I think that error_get_last() makes sense, but not the other 
two.  You can fairly easily implement that using an error handler if 
you'd like, and as Andi said, keeping track of all of the errors that 
happened on a production server doesn't make sense from a performance 
(and possibly even memory) perspective(s).

Zeev

At 13:35 11/07/2006, Michael Wallner wrote:
>Hi,
>
>I think many people agree that PHPs means for a developer to
>get the last error message(s) are way suboptimal.
>
>INI(track_errors) and $php_errormsg or hacking some error
>handler magic are--despite sep. extension facilities--the
>only one that come to mind, both cumbersome and unintuitive.
>
>
>I therefore propose some new functionality with possibly
>this 3 new functions:
>
>- error_get_last()
>Get the last error message.
>
>- error_get_all()
>Get an array of all occurred errors.
>
>- error_clear_all()
>Reset error stack.
>
>Return values and parameters are subject to discussion, as well as
>when PHP puts errors into this stack, eventually if track_errors is
>enabled?
>
>
>Thoughts, objections, flames?
>
>
>
>PS: Sorry, if that comes through twice.
>
>Regards,
>--
>Michael
>
>--
>PHP Internals - PHP Runtime Development Mailing List
>To unsubscribe, visit: http://www.php.net/unsub.php