Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108903
To: Matthew Brown <matthewmatthew@gmail.com>
Cc: internals@lists.php.net
References: <1845472b-08ab-bb31-dc77-23c620b8d217@mabe.berlin>
 <4D79715B-D9F8-42F8-B0DB-4EA7B6DBFB6A@gmail.com>
Message-ID: <58110de6-9d68-869c-9381-d50c1ea46616@mabe.berlin>
Date: Mon, 9 Mar 2020 06:38:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <4D79715B-D9F8-42F8-B0DB-4EA7B6DBFB6A@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: [PHP-DEV] Bug Wrong resolution of "Late Static Binding" after
 self::method()
From: marc@mabe.berlin (Marc)

Hi,


On 08.03.20 17:54, Matthew Brown wrote:
> This is expected behaviour given my understanding of how late static binding works:
>
> If there is a chain of “self::” calls that ultimately ends in “static::someMethod”, then PHP behaves as if every preceding call was a call to “static::”, not “self::”. In your second call you’re explicitly overriding that resolution by changing using (self::class)::someMethod, which PHP always treats as A::someMethod, thus producing the expected output.

Thanks for explaining.

I couldn't find any information for this behavior in the documentation - 
Is that documented anywhere?

Does it make sense? -> I have read "self::" all time as a shortcut for 
"MyClass::" until I noticed this is not the case and I expect most PHP 
devs would explain it this way.

Is there a reason why self:: doesn't reset the internal "static" reference?


Sorry for all these questions.

Sometimes the world could be so simple until it turns out it isn't for 
no reason.


Thanks,

Marc