Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116004
To: internals@lists.php.net
References: <CAF+90c-Xze=9A66hfDggan-JrebJDNvS1LdU45_Lreg+LXGhuw@mail.gmail.com>
 <a25a1cfd-b699-f6b3-34cb-593e59acdabd@mabe.berlin>
Message-ID: <3dfa71bf-b600-bb03-d69d-1c6e3ef90609@gmail.com>
Date: Wed, 8 Sep 2021 09:33:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <a25a1cfd-b699-f6b3-34cb-593e59acdabd@mabe.berlin>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Alias stdClass to DynamicObject?
From: rowan.collins@gmail.com (Rowan Tommins)

On 07/09/2021 17:15, Marc Bennewitz wrote:
>
> * It's a class -> Why do we suffix it with "Object"?


Classes are generally named to make sense when you have an instance: a 
class called "HttpRequest" is not saying that the *class* is a request, 
but that every *instance* is one, as in "$myRequest = new HttpRequest;" 
Similarly, "DynamicObject" is not saying that the *class* is an object 
(or dynamic, for that matter), but that every instance is: "$myObject = 
new DynamicObject;"


> * Yes it's about dynamic properties - but is this the user goal to 
> have dynamic properties or is it an implementation detail to get 
> something else (map/dict)? 


I think a lot of uses of stdClass are precisely where people feel a map 
or dictionary *isn't* appropriate, and that's why they don't want to use 
an array: for instance, decoding a JSON string, or a database result 
row. The values aren't all of the same type, and you would never want to 
apply the same operation to all of them; you will probably initialise 
them once, and then access them by name, but don't have the facility to 
declare them up front.


Regards,

-- 
Rowan Tommins
[IMSoP]