Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.25 cause and error)
Message-ID: <55A07A7F.8040409@garfieldtech.com>
Date: Fri, 10 Jul 2015 21:07:59 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <87ad99ac-6647-4e40-a9c2-d652a46cfaae@me.com>	<55A03B7D.1040907@garfieldtech.com> <CAKOpQSw9f90NdB-qt5e+hJJiPrmzSaoVPAsZZsiB0E=su7Z6OA@mail.gmail.com>
In-Reply-To: <CAKOpQSw9f90NdB-qt5e+hJJiPrmzSaoVPAsZZsiB0E=su7Z6OA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Concept for Json_decode
From: larry@garfieldtech.com (Larry Garfield)

On 07/10/2015 07:37 PM, Kris Craig wrote:
> On Fri, Jul 10, 2015 at 2:39 PM, Larry Garfield <larry@garfieldtech.com>
> wrote:
>
>> 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
>>
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
> PHP already has tons of abstractions designed to provide convenience.
> We've never followed the "if it can be done in userland, don't do it in
> core" standard.  If we did, we would have far fewer array_* functions, for
> example.
>
> The question is whether or not this would be useful enough to warrant
> putting it in core, not whether or not someone could write a ton of code to
> do it in userland.
>
> Dean, could you write an RFC for this proposal?  That would make it easier
> to evaluate, plus give us something we can vote on.
>
> --Kris

Except that "this is simple enough to do in PHP, why does it need to be 
in core" has been the reason to reject plenty of proposals, too. It's an 
entirely fair question to ask, and one that an RFC will need to address.

--Larry Garfield