Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain duncanc.co.uk from 209.85.192.173 cause and error)
MIME-Version: 1.0
In-Reply-To: <A6.ED.40376.EA89C795@pb1.pair.com>
References: <CAHE1Eds0eiCy2F-W9CUK_wRACOEsikjLeWc1JczW4+kXuRW0Fw@mail.gmail.com>
 <CANUQDCinNh5z4n_6WTJ2Ms_V9VEUiovD8-6dae_Y6Om9jj3wjA@mail.gmail.com>
 <CAHE1Eds4zvho47-yc2xfTCanQ_D8ZDVAfybR+9n0UjygoyEAgw@mail.gmail.com> <A6.ED.40376.EA89C795@pb1.pair.com>
Date: Sat, 29 Jul 2017 17:08:41 +0100
Message-ID: <CAHE1Edscjm037w80rv=aSNkYNJkbdWJBBeBDnEY+EG58=NuuJw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c11ba5ae5ee920555770290"
Subject: Re: [PHP-DEV] json_encode() / json_decode() warnings
From: php@duncanc.co.uk (Craig Duncan)

--94eb2c11ba5ae5ee920555770290
Content-Type: text/plain; charset="UTF-8"

On 29 July 2017 at 15:16, Andrea Faulds <ajf@ajf.me> wrote:

> Could we not simply make it a flag? e.g.
>
>     $bar = json_encode($foo, JSON_THROW_EXCEPTIONS);
>     $baz = json_decode($bar, false, 512, JSON_THROW_EXCEPTIONS);
>
> That wouldn't break backwards-compatibility, but would still provide the
> desired functionality. :)


Hi Andrea, although that wouldn't break compatibility, it doesn't protect
new developers from using them dangerously.
That desired functionality is available in many userland libraries, I don't
think we gain much from adding it to core.
My aim is to make the core functions easier/safer to use out of the box.

--94eb2c11ba5ae5ee920555770290--