Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103728
MIME-Version: 1.0
References: <CAHE1EdtMNi=V=TRRnFyNGkMTjUOUC+2q8EFQs3h3xVHZPnFNNw@mail.gmail.com>
 <CAF+90c8PpA5_DDM4En+iTqESH15S0cgqWd-qekM0XQG1jXJ_qw@mail.gmail.com>
In-Reply-To: <CAF+90c8PpA5_DDM4En+iTqESH15S0cgqWd-qekM0XQG1jXJ_qw@mail.gmail.com>
Date: Mon, 14 Jan 2019 13:18:49 +0000
Message-ID: <CAHE1Edt_s0d_aDT7oKsx8SrP9impUFVqQt5axLQE3OPq5gGbSg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004af192057f6ae314"
Subject: Re: [PHP-DEV] Making stdClass iterable
From: php@duncanc.co.uk (Craig Duncan)

--0000000000004af192057f6ae314
Content-Type: text/plain; charset="UTF-8"

On Mon, 14 Jan 2019 at 11:57, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Rather than implementing Traversable, I think it would be much better to
> implement IteratorAggregate and provide a proper getIterator()
> implementation. Objects that only implement Traversable are a PITA to work
> with and lots of code assumes that anything Traversable will either be
> Iterator or IteratorAggregate. For userland code this is strictly enforced,
> but internal code can avoid this. However, the current exceptions to this
> are rather niche, while stdClass is somewhat commonly used.
>

That makes sense, if the RFC passes I'll pick up these implementation
points before proceeding, thanks

--0000000000004af192057f6ae314--