Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:124414 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 44F181A00B7 for ; Sat, 13 Jul 2024 00:37:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1720831154; bh=7sqpgtsyyYr2fJOv04kgSYCWi78atv5R7e+5X/AsEcI=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=cY6cogTXBTQQTG0T2oU8FbnR7es57aHthEpxgrQfXiV6hZAfjnmqdG6hhEH9Y18EY S4kyC+b2MdAMaHpd483R4b2Rj3dEeeADiJP9Nsnc+YFW9EruSMM/bERUqC2Mu5Imf+ dHbGLKlGLuAjz5W7X9L76qlZU3dpqDsSBYmAAFmvs02gWjFBy38m6COacVZmW0OK8n hdThdxs9vZdIpzeddw3Ax6Aa2R+QiB5e0s39DvCDSePnDqGZcQnYKnpmEzfOVQYDyg CceuV6x68KE0IcM41j2wp/W1YcmrD/elWqnPmCbfEIrl5MXgP0z8b8hyMBNJiYnW2x TGJm7RWYGoSUg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id ECF33180048 for ; Sat, 13 Jul 2024 00:39:12 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail.sakiot.com (mail.sakiot.com [160.16.227.216]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 13 Jul 2024 00:39:12 +0000 (UTC) Received: from smtpclient.apple (74.73.239.49.rev.vmobile.jp [49.239.73.74]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.sakiot.com (Postfix) with ESMTPSA id AE740401E5; Sat, 13 Jul 2024 09:37:41 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com; s=default; t=1720831061; bh=7sqpgtsyyYr2fJOv04kgSYCWi78atv5R7e+5X/AsEcI=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=cjoCBIK+7pvIwFb064LlScmcqNClg/lalfwbFDARakyS8gCknTLEYFBN22LV7BNhH xWQTy0oWR/98CqBRbzlrTy6qUQv1rFmf5uy3sG1O2ClO0TjIvhuD3aqSGNcHeyW1jE +Yor9pILYx42tNpUb+C6UrxDNNEP4vYOaibRn8xc= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net Mime-Version: 1.0 (1.0) Subject: Re: [PHP-DEV] Breaking change of rounding behavior in PHP 8.4 Date: Sat, 13 Jul 2024 09:37:28 +0900 Message-ID: References: Cc: "Christoph M. Becker" , PHP Internals In-Reply-To: To: "Gina P. Banyard" X-Mailer: iPhone Mail (21F90) From: saki@sakiot.com (Saki Takamachi) Hi Gina, > I agree, this situation is extremely suboptimal. >=20 > My understanding as to why people declined the "Change the edge case of ro= und()" RFC [1] was because they were worried about the silent change in beha= viour. > However, most people seem to have missed the fact, myself included, that r= egardless of it being accepted or not there would have been changes to the b= ehaviour. > As such we have the worst of both worlds, continuing to have incorrect flo= ating point semantics for people that rely on proper IEEE 754 floating point= s, > and yet we still have a silent change in behaviour due to the partial bugf= ix. >=20 > Moreover, these fixes made the implementation of round() more complicated,= for marginal benefits IMHO. >=20 > Best regards, >=20 > Gina P. Banyard >=20 > [1] https://wiki.php.net/rfc/change_the_edge_case_of_round Opinion on this seems to be more divided than I expected. I think the fairest approach would be to revert the change that extended the= range of rounding to one more digit and hold a RFC vote. Note that it doesn't take 2/3 to take down this change, it takes 2/3 to keep= this change. How do you think? Regards, Saki=