Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24345
Return-Path: <andi@zend.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 85760 invoked by uid 1010); 11 Jul 2006 21:37:47 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 85744 invoked from network); 11 Jul 2006 21:37:47 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 11 Jul 2006 21:37:47 -0000
X-PHP-List-Original-Sender: andi@zend.com
X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4)
Received: from ([80.74.107.235:44355] helo=mail.zend.com)
	by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP
	id 23/20-17536-82A14B44 for <internals@lists.php.net>; Tue, 11 Jul 2006 17:37:46 -0400
Received: (qmail 26104 invoked from network); 11 Jul 2006 21:36:51 -0000
Received: from localhost (HELO ANDILENOVO) (127.0.0.1)
  by localhost with SMTP; 11 Jul 2006 21:36:51 -0000
To: "'Michael Wallner'" <mike@php.net>,
	<internals@lists.php.net>
Date: Tue, 11 Jul 2006 14:37:39 -0700
Message-ID: <002501c6a532$3d1a9d20$a610a8c0@zend.2k>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acak1Z5zZAB/mRShRWKzu7keuIFg3wAXIprQ
In-Reply-To: <97.00.12962.7DE73B44@pb1.pair.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Subject: RE: [PHP-DEV] More valuable error message handling
From: andi@zend.com ("Andi Gutmans")
References: <97.00.12962.7DE73B44@pb1.pair.com>

I definitely think that for production apps we should be able to turn this
off. It could significantly slow down apps. 

> -----Original Message-----
> From: Michael Wallner [mailto:mike@php.net] 
> Sent: Tuesday, July 11, 2006 3:35 AM
> To: internals@lists.php.net
> Subject: [PHP-DEV] More valuable error message handling
> 
> 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
>