Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119931
MIME-Version: 1.0
References: <aa9f0f66-f772-3fc4-4f66-2245930ab089@helionweb.de>
 <CAPyj-LAughwkC=nQjU=K56rMmCjPdmq42DPPr7Q0v0dtkieLzA@mail.gmail.com>
 <CADK1yXKWbwiUAmWpoOdCF459fzq3w47SpwBvJ_6-nXTnfzkjhQ@mail.gmail.com>
 <8abbed60-5569-4eca-ad12-957877feed9b@app.fastmail.com> <CADK1yXJj1=gfNLgUX69yED_pa5zJLJomyQ9M0K57zavu1fTikw@mail.gmail.com>
 <efa92c34-7296-44f0-b120-635a3590f8cb@app.fastmail.com> <CADK1yXKrxuBpScE7oWNo-dVPGi1p7wHCKRe28JhknBZxQy_B5g@mail.gmail.com>
 <SN1PR12MB25735728AB4A39DB4846FA9BDB9A9@SN1PR12MB2573.namprd12.prod.outlook.com>
 <CANS-=pc8Lr9izR3Jpz7hTTAgLQFFjQwScFS0Gv5w96fnE3eLng@mail.gmail.com> <SN1PR12MB2573C1BA6AC5F7909632DB42DB9A9@SN1PR12MB2573.namprd12.prod.outlook.com>
In-Reply-To: <SN1PR12MB2573C1BA6AC5F7909632DB42DB9A9@SN1PR12MB2573.namprd12.prod.outlook.com>
Date: Tue, 11 Apr 2023 09:48:06 -0500
Message-ID: <CAESVnVpJUm0K313PezQpW55KrZu5wdTsM7AsrEOEhxY0XHHmMQ@mail.gmail.com>
To: Jeffrey Dafoe <JDafoe@fsx.com>
Cc: Lynn <kjarli@gmail.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f2cd6805f91094a9"
Subject: Re: [PHP-DEV] Future stability of PHP?
From: pollita@php.net (Sara Golemon)

--000000000000f2cd6805f91094a9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 11, 2023 at 9:29=E2=80=AFAM Jeffrey Dafoe <JDafoe@fsx.com> wrot=
e:

> Essentially the same thing here. Removal of dynamic properties will be th=
e
> next big one for my team. It's the deprecations that hit huge swaths of
> code without really offering much benefit that are annoying.
>
> Yes, we have a _lot_ of classes. Also multiple versions of Zend framework
> that we backport to. However, I see in a subsequent email that this is in
> preparation for improvements, which makes it more tolerable.
>
>
To clarify; Are you saying that you have a _lot_ of classes _which make use
of dynamic properties_?  A class where properties are predefined is
unimpacted by this.  stdClass is also unimpacted (as it implicitly has
allowdynamicproperties).  The only classes you should need to add the
attribute to are ones where you're using them, essentially, as typed
associative arrays.

I'm surprised if that's what you have, because it seems like a lot of extra
effort to give names to what are essentially anonymous structures.  The
advantage of providing a name should be that you get to know what
properties will be present (and perhaps that the values therein are
validated or typed themselves).

Can you expand a bit more on your use-case?

-Sara

--000000000000f2cd6805f91094a9--