Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109279 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 40172 invoked from network); 24 Mar 2020 20:35:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Mar 2020 20:35:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 261261804F8 for ; Tue, 24 Mar 2020 12:00:12 -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,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,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-io1-f51.google.com (mail-io1-f51.google.com [209.85.166.51]) (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 12:00:11 -0700 (PDT) Received: by mail-io1-f51.google.com with SMTP id c19so19262581ioo.6 for ; Tue, 24 Mar 2020 12:00:11 -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=QBOv+Tq/a8RyD1ksobfZxYHva+bSUhaLWqgyj1S7PkM=; b=LJYS9kRycKsHx2+weN75ziXA8nxlBw8byBUTNpEMFdCRz/TOrYi8prIQLodRZY6c/M l1htJXtIiIn0ZP/TPj+Awo0PMJl6HlfQV0U7dMqyGxD1aaLKc02CRQGUBEA595b5ovAV Th0mNmYCuJLH9UCpAn7WW194crDsXz8HY/arYF40RVHyknF4qPHOyR9Q/4H26jfzMNRc 9CBgV/ePa7rM65ZrTsCSN7leZ16kCXlryhdtO76CLJISAhz6fzQRPf+MVRdTKdL/jhIS PaXUa2a++OFW8BCbQkh1pkXb6WbNd+LxHvHEFszeRuvyeiAvVtKBcxVmYUMMdj+dCWaL Y/Cg== 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=QBOv+Tq/a8RyD1ksobfZxYHva+bSUhaLWqgyj1S7PkM=; b=nRPDaP16wQIxUVbNK6MnuAciDLDXvZXnNpOlkcT2MT80HKpqT3fP0ff/qPQJJOkrr4 nYFPJ2mYz1bDnL+G7WQQyfedx3XDjyWAJk1/sJrFsGy7OXAYENRfpn1FBPkxQYx6izDt tvLigrcTGNfRwgqHFyl4mydOgWGifV6tIlZG4lLMEZb4fUA6ziTZP5uwQgToIG43HpNb mX3LmVeM36Z0SYoedLjg3OMRgLinllLNbcSEZbfWbbwwxWcrtKpdAI84uC51KGIbTpwn 2npswaSZro9LJfw3gRq1WBax2JNsaqvxZPdMw0U38wyhDORRymMrTjDr5wYNnGLtE28s F1iA== X-Gm-Message-State: ANhLgQ0HF3AYPkNv9tPtrRx1+3ed9NvDNs2SaFpdt5BgxyE4o0FfSCkL 7dNnE0pG+jdeWwOeuZAPd6jD0/No205hfNCapEE= X-Google-Smtp-Source: ADFU+vuCBeS3WMC9b4CRF4e+WsWKcfaMeyQaE4tlZF2gA792lR9jxLhMi7iU1sk77iv5soRq1aI0M3NgI/CBXGCSuKQ= X-Received: by 2002:a02:cbad:: with SMTP id v13mr11400533jap.28.1585076411273; Tue, 24 Mar 2020 12:00:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 24 Mar 2020 19:59:45 +0100 Message-ID: To: "G. P. B." Cc: Nikita Popov , =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= , PHP Internals List Content-Type: multipart/alternative; boundary="0000000000006fa1c905a19e5c41" Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Locale-independent float to string cast From: kjarli@gmail.com (Lynn) --0000000000006fa1c905a19e5c41 Content-Type: text/plain; charset="UTF-8" On Tue, Mar 24, 2020 at 7:41 PM G. P. B. wrote: > On Tue, 24 Mar 2020 at 11:03, Lynn wrote: > >> I would like >> to see a warning of sorts so I can fix this before untested legacy code >> will seriously break data exports. >> >> Regards, >> Lynn >> > > We are not saying that this won't be prevalent,especially in legacy code, > however, IMHO, this is not a serious issue as it is only a matter how one > character is displayed to end users. > It's so much more than a character that's being displayed. There are automated data exports with prices, that will be automatically consumed on the other side. These kind of changes can seriously break if they were expected to be localized currency formats. We're talking massive amounts of data here. I've seen price formats go wrong often and seen them be fixed even up to a week ago. It's hard to track all usages in a 20 year old code base. As much as I love that this can be fixed, I rather not see it fixed at all if there's no upgrade path available. Regards, Lynn --0000000000006fa1c905a19e5c41--