Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118526 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 48219 invoked from network); 26 Aug 2022 23:46:48 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 26 Aug 2022 23:46:48 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7F32F180381 for ; Fri, 26 Aug 2022 16:46:47 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-vs1-f41.google.com (mail-vs1-f41.google.com [209.85.217.41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 26 Aug 2022 16:46:47 -0700 (PDT) Received: by mail-vs1-f41.google.com with SMTP id 190so3078825vsz.7 for ; Fri, 26 Aug 2022 16:46:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc; bh=8MyvFWo2wb5jJFAxZWUPvrnszwpYm37QVxNN4sFuhzw=; b=UimkxuLVbKx1sO2qDstJr8m4Qj3i1DHtU90TIBtyLBiiPiP8V6X6H/k49o6NQzgUEE /+NypV3/3RRnjGXa3WQvhp9k6/QImGSFnprp9KbgEbXDQ3QXfOYpPiPTNPrL4aYawDtX fr8MLpgPpq+4lvP13QrrGl+23Inqxt9aTYEbxTp5mFyArU9+L2XKVNiJoOGhlMh3b/qI bWW40c4TqcODc3b8CWoWlYweEwT9MrF8kJF0cWcOL/NVnKG6bv0J08QziUzAAxRvGhUV FUNjROgvWQVR6O0ijceesNO7gGf8QOlrH43I1uQ02mjQnDk35M2CQMZL9fydQ9o03puq JF9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc; bh=8MyvFWo2wb5jJFAxZWUPvrnszwpYm37QVxNN4sFuhzw=; b=SZW3ySNWYKPVBLEMGqdxU84uYA8Hkl6pFAB3yYlOcALv9aKjxpCXyLnSKBRWvQWQli ZgQpOlmCDwFxefQ71GJKfK2/zHe0YnDQ6rVKngzoypx2A/6D3TgsWS9BnL1Pj/K3LQYK gKzCgyPxcJLikOUfJidTmo7uSXGI8+ArXkDuMHfgMNQlvX1Q+GNjv/T1O23FPpy2H4a6 ouCan6oQl/+HcSgfNBhmHy9Ha6dYof6XHTCRCxV9vRGV7DU86EVnFqgr/UQzji0TzES0 lRrUN3Lms9MMNMghiylcJaq5ioD+YQo0854MxXBgVbUI9f6zz8/lz01alDvTMl/N/RMc oFgw== X-Gm-Message-State: ACgBeo276lFjrDKPT7OLw/mRfL+VNr5BxRYq/R1RLL9SHYobrUQ/NXuS anjKJkfk+jdN/cBHizEtG910Sp8d9MnteiOimzUvGoXkKXo= X-Google-Smtp-Source: AA6agR7MJl67/7wWnLNUImm0n4wc010wk2rUYZj8R70oSDgWm/dJl+pGaYGRQ6Pc8sELjca3z8mMfCSCPGW9l/XwnsQ= X-Received: by 2002:a05:6102:3f55:b0:390:c753:3565 with SMTP id l21-20020a0561023f5500b00390c7533565mr31238vsv.13.1661557606189; Fri, 26 Aug 2022 16:46:46 -0700 (PDT) MIME-Version: 1.0 References: <8D53AD5B-7CFC-4820-9EE4-FEB365D327A8@woofle.net> In-Reply-To: Date: Sat, 27 Aug 2022 01:46:35 +0200 Message-ID: To: PHP Internals List Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] RFC json_validate() - status: Under Discussion From: dev.juan.morales@gmail.com (juan carlos morales) OMG, I need to take a rest, sorry for this, here it goes again; the about JSON_INVALID_UTF8_IGNORE opinion is the same, but previous code was wrong Code: string(5) "dummy" } string(8) "No error" Saying so, now ... yes I support and think is NEEDED the usage of the JSON_INVALID_UTF8_IGNORE , as json_validate() result goes in the same direction with json_decode(). I think we need to have this flag. RFC: https://wiki.php.net/rfc/json_validate Implementation: https://github.com/php/php-src/pull/9399