Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105795 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 27560 invoked from network); 29 May 2019 15:34:11 -0000 Received: from unknown (HELO NAM02-SN1-obe.outbound.protection.outlook.com) (40.92.5.84) by pb1.pair.com with SMTP; 29 May 2019 15:34:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PlVA4thAjv00XItlMAJRiuD3Iqr7RAq82e8Y0XwwsbU=; b=PAvZCM9TGUGduNguFayZT63dPf6wWS6pQ43o1zAlsMnMc4MFes0Jzokb3dlITYzqXu5aDoL9Wq8pQqkevy+7Xgp2xAu4N9ifKzdNA3G0ioeXhxfgn1OfdPW4NFQujnIu+8c9rAQQ6+2R4SRdgh1DmPWtYEaS2JTm8tjftEKOc5Ru5YEeNc3KBmXyWvchDB3CDgs5cjriTxSl3vb93jU0SlPb2ZyVnvGAYD5ZCDc0xd1nXnc6l/YYFo9v5NbBFQqqedSNwsqRAfAOOwIqXIukHXDvB9/PqYdxgIYmzPjPpLQuQq6mx8vHZ83iq6oFvSPqAM8CTtrn5x/yVCEMNcafGA== Received: from SN1NAM02FT027.eop-nam02.prod.protection.outlook.com (10.152.72.59) by SN1NAM02HT105.eop-nam02.prod.protection.outlook.com (10.152.72.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1922.16; Wed, 29 May 2019 12:43:33 +0000 Received: from MWHPR06MB2861.namprd06.prod.outlook.com (10.152.72.60) by SN1NAM02FT027.mail.protection.outlook.com (10.152.72.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1922.16 via Frontend Transport; Wed, 29 May 2019 12:43:33 +0000 Received: from MWHPR06MB2861.namprd06.prod.outlook.com ([fe80::bc99:7f29:71ac:9104]) by MWHPR06MB2861.namprd06.prod.outlook.com ([fe80::bc99:7f29:71ac:9104%4]) with mapi id 15.20.1922.021; Wed, 29 May 2019 12:43:33 +0000 To: =?Windows-1252?Q?C=F4me_Chilliet?= , "internals@lists.php.net" Thread-Topic: [PHP-DEV] Re: [RFC] Numeric Literal Separator Thread-Index: AQHVCzD4Zg3fV6zubk+OJkqTtyX3naaAoYJugABd7YCAAB+7gIAAsIkAgABOz8Y= Date: Wed, 29 May 2019 12:43:33 +0000 Message-ID: References: ,<1858501.VmE1D5L3rF@mcmic-probook> In-Reply-To: <1858501.VmE1D5L3rF@mcmic-probook> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:CC1A589801FE76AAEBCA277B031EFC9C6BAAEFE6715757C742AC0FD8AE3DAC78;UpperCasedChecksum:37140ADB248891EFEA4704248068A1588175D2F35E1F6DE286792B8B05613D75;SizeAsReceived:6961;Count:43 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [bptf9qjFWq3jK+cbiJj5ZCi8rYpZxj0g] x-ms-publictraffictype: Email x-incomingheadercount: 43 x-eopattributedmessage: 0 x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(5050001)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322404)(2017031323274)(2017031324274)(1601125500)(1603101475)(1701031045);SRVR:SN1NAM02HT105; x-ms-traffictypediagnostic: SN1NAM02HT105: x-microsoft-antispam-message-info: gsXmJ+WLDY60rvu0a6wRtbiEh6f5L6H0r5elEFSB2gL7rp6BeSqvKdRhlP9k7jloGUdhpOnJTupsbWLlSZUQwQIT9WRimiUah9T9LP282JvJJE8ZsNO1k/LjyNyTBxEizBYXTcqnKK8CUxAFLSGw/y8HiwI53bRwRt6wOY0ODC87fSGfEIsXTY91GFgrMOfI Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 3c33fce4-2c8c-43e2-6851-08d6e43342fd X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2019 12:43:33.6651 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM02HT105 Subject: Re: [PHP-DEV] Re: [RFC] Numeric Literal Separator From: theodorejb@outlook.com (Theodore Brown) On Wed, May 29, 2019 at 2:49 AM C=F4me Chilliet wrote:= =0A= =0A= > What bugs me with this RFC is that it seems to be mainly intended=0A= > for grouping digits by 3, which from what I understand is cultural.=0A= =0A= While it is expected that grouping decimal literals by 3 will be a=0A= frequent use case, the RFC does not enforce an arbitrary group size.=0A= Not only would doing so add complexity, but it would also prevent=0A= some of the use cases mentioned in the RFC. For example, if you're=0A= working with financial quantities stored as cents, it can be useful=0A= to group the dollar amount by 3 and the cents by 2:=0A= =0A= ```php=0A= $amount =3D 100_500_00; // represents $100,500.00=0A= ```=0A= =0A= The RFC also contains examples of grouping hex and binary literals by=0A= 2, 4, or 8 digits.=0A= =0A= Not placing restrictions on the size of digit groups enables=0A= programmers to choose the grouping that best reflects their intent.=0A= It's also consistent with the other languages that support this=0A= feature.=0A= =0A= > I will not vote no on the RFC, most likely I won=92t vote. But I=0A= > think I will not use this in my code.=0A= =0A= That's fine. Not everyone has a use case for this feature, but it can=0A= be very helpful for those that do.=0A= =0A= Best regards,=0A= Theodore=