Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118595 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 61905 invoked from network); 10 Sep 2022 11:46:14 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Sep 2022 11:46:14 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 52F9D1804AB for ; Sat, 10 Sep 2022 04:46:11 -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 ; Sat, 10 Sep 2022 04:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1662810368; bh=awFFJfAGUA5ii7NBIIwUzAidDTOeCtryyR6QmjlwTdo=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=VvsMl+XP1mPwNjV+QQ18u2GL7rVwNm7Nh0sTtKgQVASJgWUIasRsbEMpUz3ebqwkt Qj0OINHFrbgAa0URebAuCfrNsZj7zW59FyPAXV5FObNnO+GXV0mQTXbUrSzuczQh2B oZmv/5bJwCloDmiSaEUGct3llBFKwY60p3IFQsKxWlag8ISIKl1ZWGJ+axKT6YpFE6 Pleu2lq4OksbLCxxxrc7S+zhpVCsA8O9FbwIR3Vq8iFrtgrxSNNxKXF2+Xt/G7FNhg Kjt34K9Q5NHGfe7oqgA3YqLyb7/1FC5OlYa5FK7smXvFWewD2M38H0W2d96+8wMKiN Fhl0inJfBVX0g== Message-ID: <1315d105-7ab7-74da-888a-b7b023cd0c27@bastelstu.be> Date: Sat, 10 Sep 2022 13:46:05 +0200 MIME-Version: 1.0 Content-Language: en-US To: Paul Dragoonis Cc: PHP Internals List 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/10/22 13:03, Paul Dragoonis wrote: > Do give it more thought regarding the callbacks what Nikolas said, sleep on > it. Are you referring to 'unserialize_callback_func' or to the unserialize handlers (i.e. __wakeup, __unserialize, Serializable::unserialize)? If the former, I am currently waiting for an explanation of the use cases from someone who uses it, to be able to make an educated decision. > Not saying it matters, but also double check how error handling MAY differ > when in a Class::_unserialize() context. Maybe it doesn't diff, I haven't > checked in a while, but food for thought. I'm afraid, this is a little vague. What possible difference (and difference to *what*) do you have in mind? > In any case, good cleanup initiative. > Best regards Tim Düsterhus