Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100495
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain legalweb.org.uk designates 188.39.106.5 as permitted sender)
To: internals@lists.php.net
References: <82.9A.10715.73494B95@pb1.pair.com>
Message-ID: <5d882203-b31c-f006-db93-60d23ae2c6b1@legalweb.org.uk>
Date: Sun, 10 Sep 2017 08:42:40 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <82.9A.10715.73494B95@pb1.pair.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Subject: Re: [PHP-DEV] [RFC] [Discussion] JSON_THROW_ON_ERROR
From: brad@legalweb.org.uk (Bradley Weston)

I definitely hate having to test the return value and then getting the 
error message via a function call. +1 for ability to throw exceptions 
instead.


On 10/09/17 02:24, Andrea Faulds wrote:
> Hi everyone,
>
> Craig Duncan previously sparked discussion here about JSON's 
> error-handling behaviour. Unfortunately, his attempt to change it 
> seems not to have gone anywhere, but I have his blessing to try this 
> other approach instead.
>
> So here's an RFC: https://wiki.php.net/rfc/json_throw_on_error
>
> The feature can be described in a single paragraph (in fact, the title 
> is pretty much enough, the patch is just detail) but it's better to go 
> through the proper RFC process.
>
> Please tell me what you think.
>
> Thanks!
>