Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67461
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 188.94.27.5 as permitted sender)
Message-ID: <519E797D.7040405@php.net>
Date: Thu, 23 May 2013 22:18:05 +0200
Reply-To: internals@lists.php.net
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Bug #64910: Line number of $e = new Exception vs. line number of
 throw $e
From: sebastian@php.net (Sebastian Bergmann)

 Hi!

 The error message that is created for an uncaught exception as well
 as the stacktrace of an exception list the number of the line on which
 the exception object was created. I would expect this to be number of
 the line on which the exception is raised using the throw statement.

 Derick agrees with me that this is a bug. We propose to update the file
 and line properties of the exception object in the
 zend_throw_exception_internal() and zend_throw_exception() functions.

 Would such a change be accepted? Does it require an RFC?

 Thanks!
Sebastian