Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100776 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2439 invoked from network); 26 Sep 2017 11:42:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Sep 2017 11:42:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.219 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.219 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.219] ([81.169.146.219:34931] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/81-20795-21D3AC95 for ; Tue, 26 Sep 2017 07:42:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1506426128; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Date:From:References:In-Reply-To: MIME-Version; bh=OUrwBExHEaqPniA51YhT3TzBU8evXGtBuPdwZmUbakY=; b=LoEWBFoNLGAi7zydVCQrTmzM82ndnEYGARS2KAkUnWz7+z0/a2n40pCkr+/NBxNrko ilYvIRVfG7RFExuPAQiipmxee2DUdFz9DOO/Ry2+dLrvOBKTIVljJ47NviFB7X5q3/hb EEKfX3Og43OW9Bx4fRvhmrzmee9qx2/M1LJ0A= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mlsGbEv0XHBzMIJSS+jKTzde5mDb8Db2nURiq+cA== X-RZG-CLASS-ID: mo00 Received: by mail-yw0-f169.google.com with SMTP id p10so6840327ywh.8 for ; Tue, 26 Sep 2017 04:42:08 -0700 (PDT) X-Gm-Message-State: AHPjjUhUqFarlMB1OLi0FeajNZK1WgBa6uKaQfKoCoKLGWGmnD1lv6PH D6Z/PCib63zaTyLDtE4F3LsyD6Q0L0xiT9eaBs4= X-Google-Smtp-Source: AOwi7QA3U/Y9DgPy5S7OwYR4KuO8dJN+t8x3UeRg0xEb10UmCIuqx0pc6ysfEmcchbo7mOMOb3N/t3KQZhgl8jBj1Es= X-Received: by 10.129.40.79 with SMTP id o76mr6427316ywo.376.1506426127598; Tue, 26 Sep 2017 04:42:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.224.146 with HTTP; Tue, 26 Sep 2017 04:42:07 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Sep 2017 13:42:07 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Derick Rethans Cc: Andrea Faulds , PHP Internals Content-Type: multipart/alternative; boundary="001a11428394379170055a162a0a" Subject: Re: [PHP-DEV] [VOTE] JSON_THROW_ON_ERROR From: me@kelunik.com (Niklas Keller) --001a11428394379170055a162a0a Content-Type: text/plain; charset="UTF-8" 2017-09-26 12:01 GMT+02:00 Derick Rethans : > On Mon, 25 Sep 2017, Andrea Faulds wrote: > > > Hi everyone, > > > > https://wiki.php.net/rfc/json_throw_on_error > > > > Voting opens today, 2017-09-25, and ends in 10 days' time, 2017-10-05. > Under > > the terms of the voting RFC this only needs 50%+1 but I'll feel guilty > if it's > > not 2/3 so it's 2/3. > > > > Happy voting, please ask if there's anything needing clarifying. > > I'm going to be in favour, but I was wondering whether the name of the > exception "JsonException" is a good thing? I would still introduce it, > but probably subclass a "JsonCodingException" to signal just an > exceptional code while encoding/decoding. I can see future exceptions > being thrown from the extension, where you then get confusion (or > conflicts with error codes). Which future exceptions can you imagine? Regards, Niklas --001a11428394379170055a162a0a--