Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57812
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain easen.co.uk from 74.125.82.54 cause and error)
Message-ID: <4F3802D1.3090103@easen.co.uk>
Date: Sun, 12 Feb 2012 18:20:01 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Stefan Marr <php@stefan-marr.de>
CC: internals PHP <internals@lists.php.net>
References: <4F343C47.1020304@easen.co.uk> <4A078642-29BC-41F0-B900-92E476830675@stefan-marr.de>
In-Reply-To: <4A078642-29BC-41F0-B900-92E476830675@stefan-marr.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Bug #61033 __FUNCTION__ doesn't report correctly in
 alias trait methods
From: marc@easen.co.uk (Marc Easen)

On Fri 10 Feb 2012 09:49:54 GMT, Stefan Marr wrote:
> Hi Marc:
>
> On 09 Feb 2012, at 22:36, Marc Easen wrote:
>
>> The reason why I feel this should be changes to reflect the actual called function name is that one of main uses of the __FUNCTION__ constant it to refer back to the function that is currently running, for the use recursive functions:
>
> I still maintain the position that __FUNCTION__, as __LINE__ and __FILE__, is supposed to be a lexical constant. (In retro-spective, adapting __CLASS__ to do even more magic might have been a mistake, from a conceptual point of view.)
>

As with PHP 5.4 you are able change the function name and the class you 
are running in thanks to traits, so makes sense to update these magic 
constants to represent the the value at run time as apposed to compile 
time.  __LINE__ and __FILE__ will always be relating to values at 
compile time.

Cheers,
Marc