Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70580
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGfRu7NgxewY7rxm7zCY8VMxM8=hkBfLbvceG6Xzgc3mnEvU8A@mail.gmail.com>
References: <CAGfRu7NgxewY7rxm7zCY8VMxM8=hkBfLbvceG6Xzgc3mnEvU8A@mail.gmail.com>
Date: Wed, 11 Dec 2013 02:36:55 +0100
Message-ID: <CADyq6sLbXQmLDE3kJ2VXzJKqi90-uXKuQFHKvDUjaGOvDs6Avw@mail.gmail.com>
To: chobie <chobieee@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113397cecc9caf04ed3844b5
Subject: Re: [PHP-DEV] Proposal: ArraySerializable interface
From: ocramius@gmail.com (Marco Pivetta)

--001a113397cecc9caf04ed3844b5
Content-Type: text/plain; charset=UTF-8

I am personally (currently) relying on the approach where array conversion
gives me the values of the various properties as objects (when they are
objects), so I wouldn't like another magic operator in there (to deal
with/workaround).
Wondering why this approach would be better than doing a recursive array
map iteration.

Pardon my naive and inelegant way of dealing with maps (see the running
example at http://3v4l.org/ZOodL ):

class ObjectToArrayConverter
{
    /**
     * @param mixed $value
     *
     * @raturn array
     */
    public static function toArray($value)
    {
        if (! (is_object($value) || is_array($value))) {
            return $value;
        }

        if (is_object($value) && method_exists($value, '__toArray')) {
            return $value->__toArray();
        }

        return array_map(__METHOD__, (array) $value);
    }
}


Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On 11 December 2013 02:23, chobie <chobieee@gmail.com> wrote:

> Hi,
>
> I've got an idea for adding common way to convert array from object:
> ArraySerializable interface and to allow the changing of existing
> array conversion mechanism.
> As an example of this change, consider the following code-snippet:
>
>     $person = new StdClass();
>     $person->name = "John";
>     $phone = new StdClass();
>     $phone->number = "12345";
>     $person->phone = $phone;
>
>     var_dump((array)$person);
>     #array(2) {
>     #  ["name"]=>
>     #  string(4) "John"
>     #  ["phone"]=>
>     #  object(stdClass)#2 (1) {
>     #    ["number"]=>
>     #    string(5) "12345"
>     #  }
>     #}
>
> Currently, the implicit object to array conversion does not work
> recursively. This propose changes object to array conversion behaviour
> which implements ArraySerializable interface. specifically
> ArraySerializable::__toArray method overrides current (array) cast.
>
>     interface ArraySerializable
>     {
>         /** @return array */
>         public function __toArray();
>     }
>
>
> ArraySerializable interface provides common way to convert to array
> from object. also impose conversion rule.
>
> * __toArray() returning value excepts an array and It values only
> accepts primitive type. (long, double, string and array)
>    * do cast to array operation when the value contains object which
> implements ArraySerializable interface
>   * otherwise, raise RuntimeException.
> * __toArray() method calls implicitly when cast to array from object.
>
> This feature improves object to portable format (like json) conversion
> mechanism.
>
> rough propose document and patch are here:
> https://gist.github.com/chobie/7890899
>
> I want to get feedback about this propose. If I get a good response
> I'll investigate potential issues and improve rfc and patch.
>
> Thanks,
> Shuhei
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a113397cecc9caf04ed3844b5--