Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119353
Message-ID: <1b532bf0-7934-e693-ba01-32b9587d54f5@alec.pl>
Date: Thu, 19 Jan 2023 19:23:19 +0100
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAOWwgpnQvKYvx9UhtZDSBhP4Sq9V65ccxdqGUzTfm5-J+6Znsg@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAOWwgpnQvKYvx9UhtZDSBhP4Sq9V65ccxdqGUzTfm5-J+6Znsg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Pass Scope to Magic Accessors
From: alec@alec.pl (Aleksander Machniak)

On 19.01.2023 17:23, Nicolas Grekas wrote:
> Hi internals,
> 
> Ilija and I would like to start a discussion about the following RFC:
> https://wiki.php.net/rfc/pass_scope_to_magic_accessors
> 
> When using magic methods to access actual properties, respecting their
> declared visibility is often desired. Yet, accessing the calling scope to
> emulate the visibility restrictions is unreasonably difficult at the
> moment. This RFC proposes to pass the calling scope to magic accessors to
> make it trivial to get it.

Why not a new function, e.g. func_call_scope()? It could work 
everywhere, not only in magic methods.

I guess it would be tricky with calls to the parent magic method when 
you need the "outer calling scope", but I'd like to see some reasoning 
in the RFC.

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com