Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116394
MIME-Version: 1.0
References: <CAF+90c_wDsjuMFAoQLehkn5GeoLv5GByczF+o-eDmYe+VVRxTA@mail.gmail.com>
In-Reply-To: <CAF+90c_wDsjuMFAoQLehkn5GeoLv5GByczF+o-eDmYe+VVRxTA@mail.gmail.com>
Date: Mon, 15 Nov 2021 16:40:27 -0500
Message-ID: <CAKuGYLQvCNjBeJToHY_x_u4QD-+n8+9iPXnX6p-caW1_nJ0HXQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e4c50205d0daa84b"
Subject: Re: [PHP-DEV] [VOTE] Deprecate dynamic properties
From: matthewmatthew@gmail.com (Matthew Brown)

--000000000000e4c50205d0daa84b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 12 Nov 2021 at 08:08, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I've opened the vote on
> https://wiki.php.net/rfc/deprecate_dynamic_properties. Voting will close
> 2021-11-26.
>
> Regards,
> Nikita
>

There are two things developers think about when releasing code:

1. does it work for me
2. does it work for everyone else

With its support for runtime type hints and other similar checks, PHP does
a reasonably good job of aligning those two =E2=80=94 what works for me _ge=
nerally_
works for everyone else, too.

Using dynamic properties is one of the areas where "works for me" and
"works for everyone else" can diverge. Some people use static analysis to
keep track of those divergences, but if PHP _can_ warn people they're doing
a probably-dumb thing, I think it should.

I encourage people to vote "yes" on this, if you want PHP to be better at
preventing people from shooting themselves in the foot. I know there are
valid uses for this, but it's nevertheless a surprising feature, and not
one that delights many PHP developers. Making it attribute-only from 9.0
onwards seems incredibly sensible.

Best wishes,

Matt

--000000000000e4c50205d0daa84b--