Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67627
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <CAH-PCH7_wHUsttwQWY4YUADjPUhJcv24NDPtxMvdhkDfa2=HAg@mail.gmail.com>
References:
	 <CAH-PCH7_wHUsttwQWY4YUADjPUhJcv24NDPtxMvdhkDfa2=HAg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 04 Jun 2013 14:55:34 +0200
Message-ID: <1370350534.2630.117.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] bring Exception::getTrace/getTraceAsString
 consistent with debug_backtrace
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Tue, 2013-06-04 at 14:32 +0200, Ferenc Kovacs wrote:
> What do you think about adding the $options and $limit arguments to those
> two Exception methods?

With debug_backtrace() adding those reduces the work the engine has to
do while collecting the data, getTrace() is simply passing a
pre-existing zval array to the user, so adding the logic their makes the
implementation more complex and usage of these options slows down the
operation (not that performance of those should really matter ;-) )

I'd prefer to keep it clean and simple :)

johannes