Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70613
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGfRu7NC3WTg38831zafjcfhskm2XfVUc2-je4m+k0PwPyvfmQ@mail.gmail.com>
References: <CAGfRu7NgxewY7rxm7zCY8VMxM8=hkBfLbvceG6Xzgc3mnEvU8A@mail.gmail.com>
 <CADyq6sLbXQmLDE3kJ2VXzJKqi90-uXKuQFHKvDUjaGOvDs6Avw@mail.gmail.com> <CAGfRu7NC3WTg38831zafjcfhskm2XfVUc2-je4m+k0PwPyvfmQ@mail.gmail.com>
Date: Fri, 13 Dec 2013 00:19:55 +0100
Message-ID: <CADyq6sJK4818X+tgK6mEr-6WYQK6GXjTfvvcfJDLzbR3pwC4DQ@mail.gmail.com>
To: chobie <chobieee@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bdc94ca883f7c04ed5e96c2
Subject: Re: [PHP-DEV] Proposal: ArraySerializable interface
From: ocramius@gmail.com (Marco Pivetta)

--047d7bdc94ca883f7c04ed5e96c2
Content-Type: text/plain; charset=UTF-8

On 11 December 2013 16:29, chobie <chobieee@gmail.com> wrote:

> 2013/12/11 Marco Pivetta <ocramius@gmail.com>:
>
>
> > I'm actually wondering about the opposite case.
> > What would I have to do to have the previous behavior working on an
> `ArraySerializable` instance (basically ignore `__toArray()` for one
> particular cast)?
> > I don't want to go the reflection way :-)
>
> I'm curious about your story. What king of work do you do?
>

There are quite a lot of cases where array cast behavior is currently
something we rely on (to avoid reflection). Here's two that come into my
mind:

 - Using `__sleep()` and returning array keys for parent classes'
properties:

    public function __sleep()
    {
        return array_keys((array) $this); // handles the "\0*\0" or
"\0ClassName\0" properties
    }

 - Relying on `(array)` casting returning all property names all the time
 - Some stuff I've been working about converting objects to arrays to
objects (GeneratedHydrator)

Those are some of the bc breaks that I have on top of my mind.

I'd rather prefer having userland implementations as I mentioned before
(since it's possible). Casting to `(array)` actually solves more complex
problems, while solving the problem of extracting data is fairly simple


Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--047d7bdc94ca883f7c04ed5e96c2--