Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104208
MIME-Version: 1.0
References: <CAHE1Edvdo3qhOvJopP5fxsWZCuDAw8PZ5AXNy4=--bWK7_6T=w@mail.gmail.com>
 <CAFMT4NrMexgvB-g7GoFECRjU-tyEh81J5y5YfnbM-KuTDzZ6aw@mail.gmail.com> <CAHE1Eduu32+p=OfLXDqFg5SPkYLKhXpoJW+udLzHq+d_5FZW0w@mail.gmail.com>
In-Reply-To: <CAHE1Eduu32+p=OfLXDqFg5SPkYLKhXpoJW+udLzHq+d_5FZW0w@mail.gmail.com>
Date: Tue, 5 Feb 2019 18:46:37 +0000
Message-ID: <CALKiJKoYySw+K0NfYqUtwg8SU57c=-QhUDkTKqWViXOUL2HZPw@mail.gmail.com>
To: Craig Duncan <php@duncanc.co.uk>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001b9a5a05812a083e"
Subject: Re: [PHP-DEV] [VOTE] Making stdClass iterable
From: rowan.collins@gmail.com (Rowan Collins)

--0000000000001b9a5a05812a083e
Content-Type: text/plain; charset="UTF-8"

On Tue, 5 Feb 2019 at 17:25, Craig Duncan <php@duncanc.co.uk> wrote:

> The *iterable* type accepts a plain array, but not an object that is used
> to represent a plain array, that's surprising to me.
>


I think this notion of stdClass as "an object used to represent a plain
array" is a peculiar one. The only reason I can think of for using stdClass
is to specifically *not* be like an array in some way.

As I mentioned in the discussion thread, the closer comparison would be to
an anonymous class: $foo = new stdClass; and $foo = new class {}; both
produce objects with no behaviour, no pre-defined methods, and the ability
to define properties dynamically.

On that definition, there's no surprise at all: it's an object that has no
defined behaviour, so is not defined as having the "iterable" behaviour.



> To me, this class is presented as a first class citizen, but it works like
> a second class one.
>


While I agree that it's an anomaly in many ways, I think the fact that it's
not marked iterable is a peculiar detail to get stuck on.

Regards,
-- 
Rowan Collins
[IMSoP]

--0000000000001b9a5a05812a083e--