Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92955
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.49 as permitted sender)
MIME-Version: 1.0
Reply-To: bishop@php.net
Sender: bishop.bettini@gmail.com
In-Reply-To: <CAF+90c_Hg2OsPG6QBjkttqGzP4d413VAWcamDYaAsB1u4uGnVQ@mail.gmail.com>
References: <CAF+90c_Hg2OsPG6QBjkttqGzP4d413VAWcamDYaAsB1u4uGnVQ@mail.gmail.com>
Date: Fri, 29 Apr 2016 13:42:58 -0400
Message-ID: <CAEYWF=4Lmdh7zsXocw=mRXDt5DcU7K_xkr7Q7oFgDcVGqu3qMg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113524002fe9180531a32e93
Subject: Re: [PHP-DEV] [RFC] Forbid $this being null in instance methods
From: bishop@php.net (Bishop Bettini)

--001a113524002fe9180531a32e93
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 29, 2016 at 1:12 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals!
>
> I'd like to submit a small RFC for your consideration, which ensures
> something that really ought to be a given already: If you use $this in an
> instance method, you should actually get a $this (and not NULL).
>
>     https://wiki.php.net/rfc/forbid_null_this_in_methods
>
> As this is targeting PHP 7.1, the RFC is careful to retain compatibility
> with certain legacy PHP 4 code patterns.
>

What is the performance cost of inspecting the method for $this, and is
that inspection impervious to tricks that shield $this?

Example:

A::method();
class A {
    public function method() {
        $foo = function () {
            $this->something();
        }
    }
}

Does that throw an \Error?  Would it throw an \Error if $foo() were called?

--001a113524002fe9180531a32e93--