Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87104
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.27 cause and error)
To: internals@lists.php.net
References: <87ad99ac-6647-4e40-a9c2-d652a46cfaae@me.com>
Message-ID: <55A03B7D.1040907@garfieldtech.com>
Date: Fri, 10 Jul 2015 16:39:09 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0)
 Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <87ad99ac-6647-4e40-a9c2-d652a46cfaae@me.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Concept for Json_decode
From: larry@garfieldtech.com (Larry Garfield)

On 7/10/15 3:27 PM, Dean Eigenmann wrote:
> Hello,
>
> I have a proposal for PHP. The proposed interface would allow 
> developers to decode json into a custom object directly. If given the 
> approval I would possibly be able to implement it.
>
> Here is my github link with further details: 
> https://github.com/decanus/JSON-Aware/tree/master
>
> Regards,
> Dean

I'll ask before someone else does...

Why does this need to be in PHP core?  Why can't it be done purely in 
user-space PHP code?  The syntax would be different, fine, but how is it 
functionally better in C?

-- 
--Larry Garfield