Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118366
MIME-Version: 1.0
References: <C622EC5A-F2DA-4638-B93A-46A8D6407F60@automattic.com> <a72a14ca-97a5-4738-8c43-2259f9dedf66@www.fastmail.com>
In-Reply-To: <a72a14ca-97a5-4738-8c43-2259f9dedf66@www.fastmail.com>
Date: Sun, 7 Aug 2022 19:11:01 +0200
Message-ID: <CANMwmbPT0m2M-jvGkPtOVDLMxRJ2wSv1U+yOEYeobADd4=Jstw@mail.gmail.com>
To: Ollie Read <php@ollie.codes>
Cc: =?UTF-8?Q?Bj=C3=B6rn_Larsson?= <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000482b9b05e5a9c97a"
Subject: Re: [PHP-DEV] Re: RFC Idea - is_json - looking for feedback
From: dev.juan.morales@gmail.com (juan carlos morales)

--000000000000482b9b05e5a9c97a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Ollie.

Dont be sorry. Actually I appreciate every feedback I got.

I promise I Will not dissapoint anyone.


I Will prepare de RFC next week.

Regards.

Juan

El dom., 7 de agosto de 2022 14:03, Ollie Read <php@ollie.codes> escribi=C3=
=B3:

> Hey,
>
> While I'm not opposed to the idea, I'm struggling to think of a way to
> accurately determine whether a string is true JSON that doesn't involve
> some sort of parsing.
>
> Sure some regexes can be run on it, but I'm not sure that will ever be
> 100% accurate. Any parsing of the JSON to determine whether or not it's
> valid JSON would, in most situations, lead down a code path that then
> parsed the JSON again, essentially repeating the same function for little
> benefit.
>
> I personally like to use the *`JSON_THROW_ON_ERROR`* flag on json_decode.
>
> Not trying to rain on your parade, so sorry if it comes across that way,
> I'm just not sure of a way to do it where the benefit outweighs the cons,
> but then again, there are people a lot smarter than me on this list.
>
> ---
> Best Regards,
> *Ollie Read*
>

--000000000000482b9b05e5a9c97a--