Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116007
MIME-Version: 1.0
References: <CAF+90c-Xze=9A66hfDggan-JrebJDNvS1LdU45_Lreg+LXGhuw@mail.gmail.com>
In-Reply-To: <CAF+90c-Xze=9A66hfDggan-JrebJDNvS1LdU45_Lreg+LXGhuw@mail.gmail.com>
Date: Wed, 8 Sep 2021 12:08:06 +0200
Message-ID: <CAOWwgpkkSHf_oLzR01hNn=DPQZtJi4oFG2zgzbdsqnqhwWrA+A@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>, Rowan Collins <rowan.collins@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000c5169f05cb790ff2"
Subject: Re: [PHP-DEV] Alias stdClass to DynamicObject?
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000c5169f05cb790ff2
Content-Type: text/plain; charset="UTF-8"

> In the thread for deprecation of dynamic properties, Rowan suggested that
> we alias "stdClass" to "DynamicObject" in
> https://externals.io/message/115800#115802. I wanted to split this
> discussion off into a separate thread, as this can be decided
> independently.
>
> The rationale for this is that "stdClass" is something of a misnomer: The
> name makes it sound like this is a common base class, as used in a number
> of other languages. However, PHP does not have a common base class. The
> only way in which "stdClass" is "standard" is that it is the return type of
> casting an array to (object).
>
> The actual role of stdClass is to serve as a container for dynamic
> properties, thus the suggested DynamicObject name.
>
> What do people think about adding such an alias? Is this worthwhile?
>

Hi Nikita, Rowan,

I'm reading the discussion about the side of the alias. Can't we solve
these concerns by making DynamicObject extend stdClass instead of aliasing?
That wouldn't allow an stdClass object to get through the DynamicObject
typehint, but that shouldn't be an issue since no such code has yet been
written, isn't it?

Nicolas

--000000000000c5169f05cb790ff2--