Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118694 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 21956 invoked from network); 27 Sep 2022 20:01:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 27 Sep 2022 20:01:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D87DA180210 for ; Tue, 27 Sep 2022 13:01:38 -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,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24940 176.9.0.0/16 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 27 Sep 2022 13:01:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1664308896; bh=5bX8pql8t0QvSeMDrSn/NXhpgjK5WdcurAEHqB4xRdo=; h=Date:Subject:To:References:From:In-Reply-To:From; b=D1beFU36MG7Uw4GA3+n7iQyDLN1grP2RW+R+0ccCNvAYRq9FzMjMFBmCukCDJSMf3 4k2PVh3D3V12TyJKwn9AGIAKO5pWHJDvKLkvkYTTGn2/BMCIutjwn6aZBOze1OMAKN kJql67DdZ8VaAPejGxDcfXVSglxi7fb8HoKn5OpLkjiGOxYcrrkcwFq86eEfDivWgo Iei01sX+ADBnmAY2R2tFx0+2SU8CCMLIJTxIbwgLdTfIH1QzyYBWDwuuCFibO2wT6F TJRR2wAbqtx8USF8OrT+BMminaYT+PQOrLM0pVnwmvP8Cat54JsycXUnCg/P9lmTWz 9aZZHL+ugpVXg== Message-ID: <76b3ab60-8865-a0aa-3949-f9276cd35149@bastelstu.be> Date: Tue, 27 Sep 2022 22:01:35 +0200 MIME-Version: 1.0 Content-Language: en-US To: Larry Garfield , php internals References: <530b3a9d-0ee4-6061-8c69-df672d238032@bastelstu.be> <628f27cd-d7f0-4a75-bf5b-f4812ff459a5@www.fastmail.com> <2474d6fc-a61d-19e8-b903-ff389dbb9ff6@bastelstu.be> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] RFC [Discussion]: Improve unserialize() error handling From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=) Hi On 9/8/22 18:36, Larry Garfield wrote: >>> Either I guess? Honestly we should decide that in advance on the list. :-) E_WARNING+Exception in 9 is what I'd probably favor, with "Exception now" as a second choice. >>> > We've done this kind of two-step thing before; a lot of PHP 8 changes were voted on well in advance of 8.0's release. A "Warning now, Exception in 9" vote would not be unprecedented. > Thank you, I thought about what to do here and I've adjusted the options in the "increase to what" vote to make this a 3-way vote: https://wiki.php.net/rfc/improve_unserialize_error_handling#increasing_the_severity_of_existing_warningsnotices Do you believe that my reasoning with regard to the interpretation of the vote's results is sound? A ranked choice vote should not necessary here, because the three options follow a natural order with regard to severity/possible breakage. Best regards Tim Düsterhus