Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85797
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
In-Reply-To: <C2187224-4574-4E56-BFF5-CCE2E01E6968@gmail.com>
Date: Tue, 14 Apr 2015 09:33:38 +0300
Cc: PHP internals list <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <4D090060-127D-4BA8-8C98-6E315EF077C0@gmail.com>
References: <CAEKnhAHjM2RY+Z2iB7D5wAb=FA43vMkKb1+34O-rTsuV222YUg@mail.gmail.com> <C2187224-4574-4E56-BFF5-CCE2E01E6968@gmail.com>
To: Jakub Zelenka <bukka@php.net>
Subject: Re: [PHP-DEV] JSON float number as string
From: indeyets@gmail.com (Alexey Zakhlestin)


> On 14 Apr 2015, at 07:31, Alexey Zakhlestin <indeyets@gmail.com> =
wrote:
>=20
> Feels a bit hackish
> I think it is possible to introduce an overall better solution
>=20
> We can expose result of json-tokenizing as a tree of objects:
>=20
> JSON\Object
> JSON\Array
> JSON\String
> JSON\Number
> JSON\False
> JSON\True
> JSON\Null
>=20
> then, it would be possible to introduce any number of experimental =
userland implementations like the one proposed here

I decided to elaborate

    <?php
    namespace JSON;

    abstract class Value
    {
        public function toJson();
        public function toNative();  // this would do, whatever =
json_decode does
    }


    class Object extends Value implements \ArrayAccess, =
\IteratorAggregate
    {
    }

    class Array extends Value implements \ArrayAccess, =
\IteratorAggregate
    {
    }

    abstract class Literal extends Value
    {
        public function toString();
        public function __toString()
        {
            return $this->toString();
        }
    }

    class String extends Literal
    {
    }

    class Number extends Literal
    {
        public function toInt();
        public function toFloat();
    }

    class False extends Literal
    {
    }

    class True extends Literal
    {
    }

    class Null extends Literal
    {
    }


So, in case of Number, there would be a way to get the value the way it =
was stored in document using toString(), use toInt() or toFloat() to get =
a value with possible precision loss or use toNative(), which would be =
=E2=80=9Csmart=E2=80=9D and return int or float using the same logic, =
which json_decode() uses now.

It would work the other way round too. Object::toJson() would return =
json-representation of the tree.