Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118807 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 88171 invoked from network); 12 Oct 2022 17:30:30 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Oct 2022 17:30:30 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B950B180545 for ; Wed, 12 Oct 2022 10:30:29 -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 ; Wed, 12 Oct 2022 10:30:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1665595827; bh=vaHlkMeB4dePTVHldgJKH5DyuV/H1d+XVUxHlWBNOfo=; h=Date:Subject:From:To:References:In-Reply-To:From; b=Jy25aY324UB/VPdIjfBwmJx0r25Nwmqybo0ViQcYRJiZzxcOCfmjjOWLAH3WtqjVu UtKgM25zt8qpmfOX/US75ohqLwGmw0KjflHTuLr/YuQ5GW0uXSD5WbLEG/SZYA1Erf 2izE4RP8FL6yQbmJWkdQamqAVDfVyb46Lv6nnJkbv+v5QjyhrMAbpOYqiXSzvRLggu fX0pJ815jXn5dPGmx3vKAikS6BvTZs7p4RRjkFR5P4cRMlX7bZCUj4F4rp5wtrN1Rv mvsGnP2zagO+zu3yMiYqiA3h+/J7/+L2SUaqR048fiWDmwAI9/SadF1nrJCYadbgQL LJt76gZdWzepg== Message-ID: Date: Wed, 12 Oct 2022 19:30:26 +0200 MIME-Version: 1.0 Content-Language: en-US To: "Christoph M. Becker" , 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> <76b3ab60-8865-a0aa-3949-f9276cd35149@bastelstu.be> <720bc406-78f1-4f4f-b0fa-00c6eb541523@app.fastmail.com> <5c02132b-59b7-81dc-bd9f-a9d9210f7721@gmx.de> 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/28/22 17:42, Tim Düsterhus wrote: >>> If you want to go that route, I'd go all the way to an RCV vote and be done with it. Or else just make an executive decision as the RFC author and let the chips fall where they may. >> >> I'm generally not too happy with secondary votes. Sometimes you only >> support the primary vote for certain secondary options; to "be sure" >> that another secondary option won't "win", you'd need to vote "no" on >> the primary choice. >> >> I'd prefer a single vote with pre-selected details. I don't have any >> particular preference in this case, though. >> > > Would the increase of E_NOTICE to E_WARNING for the two cases that > currently emit E_NOTICE be something that even requires a vote or is > this something that can simply be decided by merging a PR? [1] In that > case the second and third vote could be simplified to "Convert E_* to > Exception" with the regular 2/3 majority required. As I've been told that the E_NOTICE to E_WARNING also requires a vote, I've thought about this whole matter a little more, because I agree with Christoph that secondary votes are "not great". In the end I've decided to make this all primary votes that more or less build on each other, each requiring a 2/3 majority. The vote to change E_NOTICE/E_WARNING to Exception in 8.3 was dropped to keep thing simpler and to not have conflicting votes. Instead there is only "Unify to E_WARNING in 8.x" and "Upgrade to Exception in 9.0" (which may happen independently of whether the E_NOTICE will remain in 8.x). That said: Discussion has come to a halt and I don't plan any more changes to the proposal. As such I plan to open voting on Friday with the voting widgets as they are currently within the RFC: https://wiki.php.net/rfc/improve_unserialize_error_handling#proposed_voting_choices Best regards Tim Düsterhus