Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104200
MIME-Version: 1.0
References: <CAHE1Edvdo3qhOvJopP5fxsWZCuDAw8PZ5AXNy4=--bWK7_6T=w@mail.gmail.com>
 <CAFMT4NrMexgvB-g7GoFECRjU-tyEh81J5y5YfnbM-KuTDzZ6aw@mail.gmail.com>
In-Reply-To: <CAFMT4NrMexgvB-g7GoFECRjU-tyEh81J5y5YfnbM-KuTDzZ6aw@mail.gmail.com>
Date: Tue, 5 Feb 2019 17:25:29 +0000
Message-ID: <CAHE1Eduu32+p=OfLXDqFg5SPkYLKhXpoJW+udLzHq+d_5FZW0w@mail.gmail.com>
To: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000970b0058128e6e9"
Subject: Re: [PHP-DEV] [VOTE] Making stdClass iterable
From: php@duncanc.co.uk (Craig Duncan)

--0000000000000970b0058128e6e9
Content-Type: text/plain; charset="UTF-8"

On Tue, 5 Feb 2019 at 16:39, Levi Morrison <levim@php.net> wrote:

> I just wanted to pipe in to suggest an alternative approach to
> accomplish some of the same goals: an external PropertyIterator.
>

I believe Nikita suggested something similar, and while it would certainly
be useful it doesn't accomplish the same goals as this proposal.
The goal of this proposal is to make the language more consistent and less
surprising.
The *iterable* type accepts a plain array, but not an object that is used
to represent a plain array, that's surprising to me.

*stdClass* is "promoted" as part of the language, it's use is not advised
against anywhere in the manual, and it's the default response format for
*json_decode()*
To me, this class is presented as a first class citizen, but it works like
a second class one.

As it looks like my first approach to resolving this inconsistency is
likely to fail the vote, I'm considering a second approach now to update
the docs and "officially" deprecate/discourage usage of *stdClass*

--0000000000000970b0058128e6e9--