Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100061
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain duncanc.co.uk from 209.85.220.171 cause and error)
MIME-Version: 1.0
Date: Thu, 27 Jul 2017 16:41:22 +0100
Message-ID: <CAHE1Eds0eiCy2F-W9CUK_wRACOEsikjLeWc1JczW4+kXuRW0Fw@mail.gmail.com>
To: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a113f417685eac905554e651f"
Subject: json_encode() / json_decode() warnings
From: php@duncanc.co.uk (Craig Duncan)

--001a113f417685eac905554e651f
Content-Type: text/plain; charset="UTF-8"

Hi internals,

When using `json_encode()` and `json_decode()` it is required that you
manually check for errors after every call, eg:

```php
$data = json_decode("false");
if (json_last_error() !== JSON_ERROR_NONE) {
    throw new UnexpectedValueException(json_last_error_msg());
}
```

This isn't _that_ unusual in PHP, however normally in these situations a
warning would be raised. But the JSON functions only raise warnings in a
couple of scenarios, most issues are completely silent.

I wanted to begin a discussion around changing this, so that warnings are
raised for any issues during `json_encode()` and `json_decode()`.

I have an implementation ready and I'm happy to draft an RFC if this
suggestion doesn't receive universal hatred.

Thanks for your time,
Craig

--001a113f417685eac905554e651f--