Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115874
MIME-Version: 1.0
References: <CAF+90c9_qu=PiTS81J2mesPfJdz7n5nSi3qoLNLjhEGN-aTytA@mail.gmail.com>
 <CAESVnVqMfxSZxG1+k+_o+HZ1B7QbH=wDeMTQm8R-Ok_bEyqSRA@mail.gmail.com>
 <CAF+90c-J7skECnr7TE5f5twBNRArhAh3xuKVjdGqq3HsOZrnog@mail.gmail.com> <c4db0e87-e673-03b8-66c8-87da0552c13c@gmail.com>
In-Reply-To: <c4db0e87-e673-03b8-66c8-87da0552c13c@gmail.com>
Date: Fri, 27 Aug 2021 10:02:24 +0700
Message-ID: <CAEZPtU6yMvkAEdhopUm2o8+0U=iBOm9N5+wmYL6zeNq1e2xMRQ@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Deprecate dynamic properties
From: pierre.php@gmail.com (Pierre Joye)

Hi Stan,

On Fri, Aug 27, 2021 at 5:10 AM Stanislav Malyshev <smalyshev@gmail.com> wrote:
>
> Hi!
>
> > The crux of the issue is what our end goal is:
> >
> > 1. Require users to explicitly annotate classes that use dynamic
> > properties, but otherwise keep dynamic properties as a fully supported part
> > of the core language.
> > 2. Remove support for dynamic properties entirely. The core language only
> > has declared properties and __get/__set, and nothing else. stdClass is just
> > a very efficient implementation of __get/__set.
>
> I think goal (1) is reasonable for the long run, and goal (2) is taking
> it a bit too far for PHP.

I feel the same way. However my gut feeling tells me that we will end
up with (2) sooner or later. Having StdClass behaving differently
(even if it is technically not, I don't think the "it is a more
efficient get/set implementation" will make it through our users base)
looks inconsistent.

I don't know how others feel about it, I think most want to go the
path to (2) and a more strict, if not almost fully strict PHP. Core
devs to simplify the engine, users to allow them easier checks and
safety in their frameworks or libs. End user don't really bother as
far as I can see. We may have to decide once the long term vision for
PHP and then do the changes accordingly, and more importantly, with
consistency.

Best,
-- 
Pierre

@pierrejoye | http://www.libgd.org