Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112112
Date: Fri, 23 Oct 2020 21:53:23 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <2A808AB8-7179-41F6-88F4-A19C8F7FA171@newclarity.net>
References: <DM6PR07MB661879DD06F467899D1883B7F91F0@DM6PR07MB6618.namprd07.prod.outlook.com> <5f92f1e0.1c69fb81.a800f.cbe1SMTPIN_ADDED_MISSING@mx.google.com> <bee5937e-b166-bc92-5767-a4144146d1c4@gmail.com> <2A808AB8-7179-41F6-88F4-A19C8F7FA171@newclarity.net>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
CC: internals@lists.php.net
Message-ID: <02DD5C20-522B-46C7-B5EE-BC61E2EC4C6F@gmail.com>
Subject: Re: [PHP-DEV] Is there any interest for object constructor shorthand *just forstdClass*
From: rowan.collins@gmail.com (Rowan Tommins)

On 23 October 2020 21:14:49 BST, Mike Schinkel <mike@newclarity=2Enet> wrot=
e:
>> On Oct 23, 2020, at 2:33 PM, Rowan Tommins <rowan=2Ecollins@gmail=2Ecom=
>
>wrote:
>>=20
>> I don't follow; is the resulting JSON different if you cast to
>object, or is there some other reason you prefer an object over using
>an associative array directly?
>
>The by-reference semantics of objects vs arrays in PHP=2E


*shrug* If you want things to be mutable between functions, stick an & in =
front of them; if you want copy-on-write performance, leave it to the engin=
e=2E That doesn't seem to have anything to do with JSON or API as a use cas=
e=2E



>That pattern can have a non-insignificant performance penalty when
>dealing with a large number of objects, a use-case that is not
>infrequent when processing JSON, especially responses returned via an
>HTTP API=2E


That gives us all the more reason to look for efficient ways of populating=
 anonymous class instances, then=2E (And, indeed, populating actual named c=
lasses, if such a penalty applies to them too=2E)

My point was that if we didn't already have it, making (object)$array crea=
te an instance of an anonymous class would feel natural and not lose anythi=
ng that we have now=2E

I see stdClass as a badly named and no longer necessary kludge, and would =
rather see features that help replace it than features that rely on it=2E

Regards,

--=20
Rowan Tommins
[IMSoP]