Req #12512 [Opn->Wfx]: E_INFO/E_USER_INFO
| From: | jani@php.net | Date: | Fri, 17 Dec 2010 11:28:53 +0000 |
| Subject: | Req #12512 [Opn->Wfx]: E_INFO/E_USER_INFO | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-157037@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=12512&edit=1
ID: 12512
Updated by: jani@php.net
Reported by: yohgaki at hotmail dot com
Summary: E_INFO/E_USER_INFO
-Status: Open
+Status: Wont fix
Type: Feature/Change Request
-Package: Feature/Change Request
+Package: *General Issues
PHP Version: 4.0.6
Block user comment: N
Private report: N
New Comment:
How about not.
Previous Comments:
------------------------------------------------------------------------
[2001-08-01 08:27:26] yohgaki at hotmail dot com
I would like to treat all E_NOTICE/E_USER_NOTICE as fatal error for my
applications. However, newer pgsql extension raise E_NOTICE when
transaction cannot be finished. (There is notice errors for resetting
cache also) I like it, but I need to parse E_NOTICE message to check if
it is fatal or not.
How about to have a E_INFO/E_USER_INFO for infomational errors?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=12512&edit=1