Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67365 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21543 invoked from network); 7 May 2013 21:14:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 May 2013 21:14:21 -0000 Authentication-Results: pb1.pair.com smtp.mail=bobwei9@hotmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=bobwei9@hotmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.106 as permitted sender) X-PHP-List-Original-Sender: bobwei9@hotmail.com X-Host-Fingerprint: 65.55.111.106 blu0-omc2-s31.blu0.hotmail.com Windows 2000 SP4, XP SP1 Received: from [65.55.111.106] ([65.55.111.106:4644] helo=blu0-omc2-s31.blu0.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 83/1A-06696-CAE69815 for ; Tue, 07 May 2013 17:14:20 -0400 Received: from BLU0-SMTP101 ([65.55.111.73]) by blu0-omc2-s31.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 7 May 2013 14:14:18 -0700 X-EIP: [EisXtxgUKS9cJETQNBH1HeWFRvI21XY2] X-Originating-Email: [bobwei9@hotmail.com] Message-ID: Received: from [192.168.178.93] ([87.240.218.8]) by BLU0-SMTP101.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 7 May 2013 14:14:16 -0700 Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) In-Reply-To: <51895FF2.3080809@sugarcrm.com> Date: Tue, 7 May 2013 23:14:13 +0200 CC: PHP Mailing List Developers Content-Transfer-Encoding: quoted-printable References: <51895FF2.3080809@sugarcrm.com> To: Stas Malyshev X-Mailer: Apple Mail (2.1499) X-OriginalArrivalTime: 07 May 2013 21:14:16.0772 (UTC) FILETIME=[D5021040:01CE4B67] Subject: Re: [PHP-DEV] idea: letting the line number and file name be set via user_error From: bobwei9@hotmail.com (Bob Weinand) Am 7.5.2013 um 22:11 schrieb Stas Malyshev : > Hi! >=20 >> And today we have the problem that we cannot use in any useful manner >> trigger_error in libraries, when we don't know where the error >> originates from. You debug today trigger_error's in libraries with >> putting a debug_print_backtrace behind the trigger_error. I think you >=20 > Why not use a debugger to debug? Debuggers have backtrace tools. >=20 >> (there you can add a backtrace) too, but you have to catch them, if >> not your script will abort; but I only need a notice...) >=20 > If you need additional information in the notice, you can always add = it > to the text of the notice. >=20 > --=20 > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 >=20 > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php nothing against the debugger, but it'd be something really time saving = to see the entry point instantly instead of having to use the debugger = first... And yes, I can add it to the text (I can even add a function between = which analyses the backtrace first), but I think we need more useful (=3D = more information) error throwing in PHP? Bob