Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15810 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19268 invoked by uid 1010); 5 Apr 2005 09:43:15 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19253 invoked from network); 5 Apr 2005 09:43:15 -0000 Received: from unknown (HELO marcus-boerger.de) (127.0.0.1) by localhost with SMTP; 5 Apr 2005 09:43:15 -0000 X-Host-Fingerprint: 81.169.182.136 h59705.serverkompetenz.net Linux 2.4/2.6 Received: from ([81.169.182.136:54689] helo=strato.aixcept.de) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id FE/75-19272-2BD52524 for ; Tue, 05 Apr 2005 05:43:14 -0400 Received: from zarniwoop-1g.mbo (dsl-082-083-246-048.arcor-ip.net [82.83.246.48]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 95EDA35C270; Tue, 5 Apr 2005 11:49:11 +0200 (CEST) Date: Tue, 5 Apr 2005 05:43:11 -0400 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1325222760.20050405054311@marcus-boerger.de> To: Greg Beaver Cc: Andrey Hristov , Stanislav Malyshev , internals@lists.php.net In-Reply-To: <425181BF.4090403@php.net> References: <5.1.0.14.2.20050403125628.03f83de0@localhost> <425002D8.50004@php.net> <42515CFC.2050108@php.net> <42516F85.10803@hristov.com> <425181BF.4090403@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: __autoload() enhancement From: mail@marcus-boerger.de (Marcus Boerger) Hello Greg, Monday, April 4, 2005, 2:04:47 PM, you wrote: > Andrey Hristov wrote: >> Stanislav, >> Greg probable means something like a stack trace of the autload callbacks >> that were called. This will be a nice addition just like Exception >> stacktraces >> are (I wish there were stacktraces for Fatal errors). > yes, a stack trace would be ideal - I knew there was a name for that > thing I was describing :) A stack trace is only some additional information that has no real added information. Also it is not a real stack trace since what you asked is just a list of functions called at one level and not the trace up to that part where a class was missing (which would be a stack trace). After my last commit you can get a stack trace by throwing an exception in the last called function. To get a list of all functions being called just check spl_autoload_functions(). A combination of both would require the engine to be changed to be capable of handling multiple exceptions - which hopefully we do not want. Right now a second exception while an exception is already pending results in a fatal error. -- Best regards, Marcus mailto:mail@marcus-boerger.de