Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118533 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 27873 invoked from network); 29 Aug 2022 08:45:58 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Aug 2022 08:45:58 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7FE9F1801FD for ; Mon, 29 Aug 2022 01:45:57 -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-f53.google.com (mail-vs1-f53.google.com [209.85.217.53]) (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 ; Mon, 29 Aug 2022 01:45:57 -0700 (PDT) Received: by mail-vs1-f53.google.com with SMTP id m66so7582742vsm.12 for ; Mon, 29 Aug 2022 01:45:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc; bh=2LPL8rOouGn8ZlrgsL/LCIedi91ay0IpFtHWvgfc6yg=; b=ZN4xJBhzH90ti1ifKqN0VMy6r0OlReEArMdRPHm8U/IjanC+3ATJKEUCYjeZVNllLR 3zjsUq45jLzEBij/5hE4YCa4rkLLrnqp+55nPqmkQdZJ5b2XB2Eejg9n1Ry+stmEeOIv hCSHyNAkVmGL2fNY3X1Sc6h++OWd6eUYKcgXsd8KcisVZ57XXP77rzbxzbw5/KnbcLmr f+w9mtwUV1go6boIY+o/ZLKMwhJ6mJXbUI5z6GdDki62DpXt4eAhAGl0Bre+DBBRgGO/ 78J7HOgPTJIbHqBvZ2Bz0nylPo/ZOlV1AB9z5sosXt1wArhKHqTtbPdSCSLmSD1JPrO4 oqNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc; bh=2LPL8rOouGn8ZlrgsL/LCIedi91ay0IpFtHWvgfc6yg=; b=z9oqMRuSk+GrDwsDSZS2oz+gPRMf5Qmxfxq4Sqj4c4bTmdvs+49s7w+zlKaf6m5nQE LYwm6kczIT2NSkFXN5e68IozFS2xhLmGYavx8Bqjevig3s+ZmcetUd/wrGPWS+eHNNvk mZMu+NhtJ/FAoSbW0YkUKBZHp9Q9Jvm/z5fIxeU1zZlgkb5JFcz2duRB2xAAHRFMN6vE xZ0KjzL+7YgSLeq6pDZnejySFPm8+z7Z0panDd2jNhmPYDw2khNfK1Jshzbi2FAVlMsW 85vSTiYMShCErpW6I7mn9asn2+sXqM1y/Jh9jMy/2LEhOQ8vraGEjpw3GDO4XHOb4yI9 xhkQ== X-Gm-Message-State: ACgBeo1Ryu17wBqArJ4TM13jWtPLu181aScIEMBu3xyKbYbt6ADCQ/AM IDDtUQMuXBAmB/QdTbGac4HA8ysFy9gZ+L9L3c0= X-Google-Smtp-Source: AA6agR6jU8sojZMb2de2SCC8EeGC//6WFDP0f9NlAJhh/PhKIJvXvILHhXbIefAistDOve+QfTmZZmmhPzIDwXq7rHE= X-Received: by 2002:a05:6102:3123:b0:390:d9f3:2a9f with SMTP id f3-20020a056102312300b00390d9f32a9fmr1158514vsh.6.1661762756325; Mon, 29 Aug 2022 01:45:56 -0700 (PDT) MIME-Version: 1.0 References: <8D53AD5B-7CFC-4820-9EE4-FEB365D327A8@woofle.net> In-Reply-To: Date: Mon, 29 Aug 2022 10:45:45 +0200 Message-ID: To: David Gebler Cc: PHP Internals List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC json_validate() - status: Under Discussion From: dev.juan.morales@gmail.com (juan carlos morales) El s=C3=A1b, 27 ago 2022 a las 2:50, David Gebler ()= escribi=C3=B3: > > You can always offer two votes on the RFC - one for the function itself, = then one for should it return boolean or return an int representing the jso= n_last_error constants and let it be decided that way. Thanks for the advice I did not know that. At the moment this is the only open question for this RFC, and I would like to know what the people thinks about it, otherwise, will go with 2 votings. > I think on the whole, I agree with the sentiment that returning boolean a= nd checking json_last_error() on false is probably the best / least worst o= ption. > So if I could vote, I would vote yes and for the boolean option, with a s= econdary preference for returning int if boolean option is rejected. Thanks for the feedback. > And I was unconvinced about the whole idea originally, so a good example = of where positive, robust discussion can change someone's mind. That is why we have these discussions :) .... thanks a lot for taking your time on this. > Good luck with progressing the RFC, I don't think I have anything else to= add. Thanks a lot!