Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87105 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30378 invoked from network); 11 Jul 2015 00:38:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jul 2015 00:38:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=kris.craig@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kris.craig@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.182 as permitted sender) X-PHP-List-Original-Sender: kris.craig@gmail.com X-Host-Fingerprint: 209.85.160.182 mail-yk0-f182.google.com Received: from [209.85.160.182] ([209.85.160.182:34213] helo=mail-yk0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 93/3C-48996-76560A55 for ; Fri, 10 Jul 2015 20:38:00 -0400 Received: by ykax123 with SMTP id x123so28534758yka.1 for ; Fri, 10 Jul 2015 17:37:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4Qcoixz9Nft9n3LodFs4LE41GkoeEtreyvOV8+DT6p8=; b=myk59e75/mPwIwBf3L7xO7aV4aSEQ/Rj1IOMbrn54LRk4/htjpL01kaPHo+Ywiry67 /ocHVN11Fq7RrHIdQhAB3abRVR1tkCyS8s+UaEewKuDWUbD/oXXTaTEFkQOZBCa4Pqct Ov5NgkJm6uqqsZRUZDx3gAzxq/6sgrep60SROqIebcP4kXXSlUmaaM8Yx3BSnu/vga18 Xpk8ebqWpobsOKOYh5+bLh3bZJCH1kw3Y4OlukbDKgi62xjEwPCBU4VAD8ERaZ9w4HGm VmoMBNMhaCngmz+Frwir2S6tbug2hLAePfyYO89zxk3/8UAaroScvi5OZgmBR6evocXr b02g== MIME-Version: 1.0 X-Received: by 10.129.104.194 with SMTP id d185mr25387749ywc.6.1436575076601; Fri, 10 Jul 2015 17:37:56 -0700 (PDT) Received: by 10.37.110.132 with HTTP; Fri, 10 Jul 2015 17:37:56 -0700 (PDT) In-Reply-To: <55A03B7D.1040907@garfieldtech.com> References: <87ad99ac-6647-4e40-a9c2-d652a46cfaae@me.com> <55A03B7D.1040907@garfieldtech.com> Date: Fri, 10 Jul 2015 17:37:56 -0700 Message-ID: To: Larry Garfield Cc: PHP internals list Content-Type: multipart/alternative; boundary=001a114904862254d1051a8eb344 Subject: Re: [PHP-DEV] Concept for Json_decode From: kris.craig@gmail.com (Kris Craig) --001a114904862254d1051a8eb344 Content-Type: text/plain; charset=UTF-8 On Fri, Jul 10, 2015 at 2:39 PM, Larry Garfield 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 --001a114904862254d1051a8eb344--