|
|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
Patchesreq69654.E_USER_DEBUG.E_DEBUG.patch (last revision 2015-05-19 08:37 UTC by a dot cobest at gmail dot com)Pull RequestsHistoryAllCommentsChangesGit/SVN commits
[2015-05-18 14:19 UTC] a dot cobest at gmail dot com
-Summary: Add E_DEBUG and E_DEBUG constant
+Summary: Add E_DEBUG constant
[2015-05-18 14:19 UTC] a dot cobest at gmail dot com
[2015-05-18 14:21 UTC] a dot cobest at gmail dot com
[2015-05-18 14:39 UTC] a dot cobest at gmail dot com
[2015-05-18 16:54 UTC] stas@php.net
-Package: PHP Language Specification
+Package: Scripting Engine problem
[2015-05-19 08:39 UTC] a dot cobest at gmail dot com
-Summary: Add E_DEBUG constant
+Summary: Add E_DEBUG and E_USER_DEBUG constants
[2015-05-19 08:39 UTC] a dot cobest at gmail dot com
[2015-05-19 08:40 UTC] a dot cobest at gmail dot com
[2017-01-02 08:56 UTC] krakjoe@php.net
-Status: Open
+Status: Closed
-Assigned To:
+Assigned To: krakjoe
[2017-01-02 08:56 UTC] krakjoe@php.net
|
|||||||||||||||||||||||||||
Copyright © 2001-2026 The PHP GroupAll rights reserved. |
Last updated: Wed Oct 07 20:00:02 2026 UTC |
Description: ------------ All loggers and project has [DEBUG] mode. Using E_NOTICE as debug identification is incorrect for dev-messages because in production dev-message must be ignoring and in dev-mode all messages (notices and debugs) mixed in mess. Some extensions can use the constant E_DEBUG in their dev-messages. For example, MongoLog use E_NOTICE for debugging. It is not convenient. Test script: --------------- <?php // ... trigger_error("Connection with DB established", E_DEBUG); // ... Expected result: ---------------- If bit E_DEBUG present in error_reporting: Debug: Connection with DB established in ... Actual result: -------------- The constant E_DEBUG doesn't exists