Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108905
MIME-Version: 1.0
References: <1845472b-08ab-bb31-dc77-23c620b8d217@mabe.berlin>
 <4D79715B-D9F8-42F8-B0DB-4EA7B6DBFB6A@gmail.com> <58110de6-9d68-869c-9381-d50c1ea46616@mabe.berlin>
In-Reply-To: <58110de6-9d68-869c-9381-d50c1ea46616@mabe.berlin>
Date: Mon, 9 Mar 2020 09:27:34 +0000
Message-ID: <CALKiJKqGvt0aeg5mqix+jpHko3GeqPMZWytN97BagAbg7goTTA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000aa314e05a0689dc0"
Subject: Re: [PHP-DEV] Bug Wrong resolution of "Late Static Binding" after self::method()
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000aa314e05a0689dc0
Content-Type: text/plain; charset="UTF-8"

On Mon, 9 Mar 2020 at 05:38, Marc <marc@mabe.berlin> wrote:

>
> 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?
>



A reasonably intuitive parallel that occurred to me is that $this is also
maintained through self:: calls (as long as they're not to a method
declared static).

So if you replace the static:: call in my previous example with a $this->
call, you get the same result:


# https://3v4l.org/deRcD
class A {
    function call() {
        self::method1();
    }
    function method1() {
        $this->method2();
    }
    function method2() {
        echo 'Base definition';
    }
}
class B extends A {
    function method2() {
        echo 'Override';
    }
}
(new B)->call(); # echoes 'Override'


Regards,
-- 
Rowan Tommins
[IMSoP]

--000000000000aa314e05a0689dc0--