Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67476
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <519E7A88.5070208@sugarcrm.com>
References: <519E797D.7040405@php.net>
	<519E7A88.5070208@sugarcrm.com>
Date: Fri, 24 May 2013 04:36:06 +0200
Message-ID: <CABFWAEqT_hfiSqP9wyNmuDMQfatzZMBygYZLbQXykECgce-0Eg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>, Sebastian Bergmann <sebastian@php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Bug #64910: Line number of $e = new Exception vs. line
 number of throw $e
From: phpwnd@gmail.com (Josh Davis)

On 23 May 2013 22:22, Stas Malyshev <smalyshev@sugarcrm.com> wrote:

> If we update file/line here, we lose original exception information and
> file/line in the exception becomes useless. Right now, since 99.99% of
> the code does "throw new", it is always useful. So how you would propose
> to solve this?

As a PHP programmer, I would always expect the file/line to refer to
the throw statement that has thrown it last. If I wanted to keep track
of an exception being rethrown, I'd use nested exceptions (Exception's
constructor's third parameter.)

Hope that helps.