Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102946
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.167.44 as permitted sender)
MIME-Version: 1.0
Date: Sat, 21 Jul 2018 18:05:22 -0600
Message-ID: <CAFMT4NpLq4Ox8Bt2eyJqa35BoCfqNOfg0x5sy_iByARzXkrq_g@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Implementation ideas for adding early warning for mis-use of "parent"?
From: levim@php.net (Levi Morrison)

This code the illustrates the issue; it has no errors or warnings:

```php
class A {
  function m(): parent {
    return $this;
  }
}
```

However, if you run the method you will get an error. I want to add a
light warning such as E_STRICT or E_DEPRECATED at compile time.

Using CG(active_class_entry)->parent will not work at compile time, so
that strategy is out.

Given that `zend_compile_func_decl` is not called directly from
`zend_compile_class_decl` it would be difficult to pass the parent's
name in any way other than a compiler global. Is there anything in
particular I need to do if I add another compiler global? I intend to
set and unset it in `zend_compile_class_decl`.

Anyone have a better way to pass around the parent's name at compile time?