Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109281 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 9367 invoked from network); 25 Mar 2020 00:50:07 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 Mar 2020 00:50:07 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B0CBB1804B8 for ; Tue, 24 Mar 2020 16:14:36 -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=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS 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-ua1-f54.google.com (mail-ua1-f54.google.com [209.85.222.54]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 24 Mar 2020 16:14:36 -0700 (PDT) Received: by mail-ua1-f54.google.com with SMTP id 9so71969uav.12 for ; Tue, 24 Mar 2020 16:14:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PE+GjM+6OApyZgWNYmLmB115s0SgdaxU+1+naviqerM=; b=Ke4NefXbG+9/pSGX7k2XHlsIRpuCSa8oBbFFIS5SkcydgOrA/9MWFEQk4X3J9+Ymj6 FoTv4tAq+axLKAhF80pCl9IKDptB4BvJAsjDNUh/mDViQA1BS0tXmpA9Py6ErY/2xCv1 hHX8wSaQ4Nip5666LppzSmg4mPZvSOZc+0SE2mFp1YOkWgALVTVsaa2t8gps4UlyivF2 yJ0yNGJT8lLwhlA/SEmv2+rne7mlRbw7g2cyCHm3dw8L8HyANVew6rCvQ2t9DxWV6yZ+ V84GM1Bvfb9le4dtwZ/732/2LHJwFQJKcGEMq8r8fFbFkeeMgcLvKSxtVzrArbU+Coe8 15OA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PE+GjM+6OApyZgWNYmLmB115s0SgdaxU+1+naviqerM=; b=aI+NN5c7XXgGO3za5ijD/jz689hC9G+yjITrmtJP8w+gi+8bTDt+7L+2BQP23qUTOd YR6LF/9YXLp9V0u/zsxUDJRv44rRqtrHjo5JFJn+JDin2JA1+RUhAPIFApZKYa9l7GzZ UD4mrjy2Tqpwo8JUODFhwSFh54R4BKlGJAFlrM1DKurvV5iYLeCqQzyccTvF8P5yOtEy 0WT7h9HLjbQnLGr/ue4Rc1QX7ZM0lBCXIaGsBgSCatKYa2WMRLq3lAnIsflspVaUZk9h P445LH5Zp9JYtWxX58gKYGRhODMTgnMCaA6kUMrJCxnjRRy1AoGsu/U1EC7/3b2hWVU5 3zZw== X-Gm-Message-State: ANhLgQ0r8dAdpffizdBqdYi6IDYgTjeAbWc6nT9ZcrEl0NdMetnyd1Se PBwWxbBGx3CuYn3MWvq9aoGRXlztHsp8YdC3+KI= X-Google-Smtp-Source: ADFU+vtesbV04ZTfokEMOADGbryFdvjwVSPQnElMFpDfYylaj7p9cmgW2f9v/gU9f+Esc5XSP5hC8fo8iT4AlQSwx/M= X-Received: by 2002:ab0:192:: with SMTP id 18mr483514ual.3.1585091673032; Tue, 24 Mar 2020 16:14:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 25 Mar 2020 00:14:21 +0100 Message-ID: To: Lynn Cc: "G. P. B." , Nikita Popov , PHP Internals List Content-Type: multipart/alternative; boundary="0000000000001b8c2505a1a1ea7c" Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Locale-independent float to string cast From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=) --0000000000001b8c2505a1a1ea7c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Lynn, > There are automated data exports with prices, that will be automatically consumed on the other side. I agree that these cases can go horribly wrong. However, my reasoning is the following: - if a piece of code currently relies on locale-independence (e.g. automated data exports) then this change wouldn't cause any breakage since a workaround has already been in place there (e.g. the programmers use var_export() instead of casting) - if a piece of code relies on the locale-dependent string representation of floats then there will be a BC break, sure, however I believe that code isn't very sensitive to the change in the vast majority of the cases since that data is for presentation purposes only. Or do you have other locale-dependent use-cases in mind? I am sure there are some but I think the number of the situations where the change is problematic is less than what it first seems. Regards, M=C3=A1t=C3=A9 --0000000000001b8c2505a1a1ea7c--