Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104866 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41958 invoked from network); 22 Mar 2019 03:13:46 -0000 Received: from unknown (HELO mail-it1-f194.google.com) (209.85.166.194) by pb1.pair.com with SMTP; 22 Mar 2019 03:13:46 -0000 Received: by mail-it1-f194.google.com with SMTP id y63so1014545itb.5 for ; Thu, 21 Mar 2019 17:06:01 -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=BbTdcXzYLM0BGnbRxi+S4wKdSL/dchc6dPOlU/COmFw=; b=coVxu67ykz4G4tp1dFqA+eiTwNaT0P3z2UOdtgKmVtRtZVeDv2zBR1t4ktxWH5avhy 3/GNrccBpjTZJWGYU5HDzSYXx4i5agNhJn0iF/fBVTHfl1X7iOpSISd+PYCymftod2T7 23LssX4hwnwh6yTnBXD7Dz7mxA19QwYq7JWS6+0SJAlIZZqd3MHIXX1r1HpMl9+2fJ7p T+mxraoK+TVqq4MtFJRMORwh/BgJxCDv2ct1zO+nM2FxjqOSxhmTeo+QCCELVe4H22oQ N50ocLfWQv/sxxs27xqbxfEKrUxZs5/0RbZKHMIBi2JOoAG/H10kvSCX0GzRuLh8D+eD kD0w== 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=BbTdcXzYLM0BGnbRxi+S4wKdSL/dchc6dPOlU/COmFw=; b=Fdq/ZMa0GVrIoK2z2Uz0wp6McR4WbpzHvwN8gxs+4Uqligo2MXTZdkjewlUgx02ciC 2So5T8FEBzRatY3Pn8hnwLSaTM5macQ7Xj3OeOCVMEMdzNo4CS1ynanD9pqyRWUBCfPG Pr2E7eGVnMzENoqz7VDGIG+IIZ5f/mczH25YeK5pt45LCBfvFBQoUCtF3CrzhDe00TM9 4xjpf1+41YANm/OftKxelDGVDRk/kiz00Y1KWLdwSf/pqfy1Zb6WvbXYfQuMq6yym1CZ zq8M4tnpbgMNKrBfuTmKr+VbbpllmCnD3SSWopM2UE4uAoNo00H7FyjP/FH2lfZ2Sg3P Y4pQ== X-Gm-Message-State: APjAAAVZnkAgcOEDx/jxM8dGod941gOIHViDwQfmvBF3vwfBQp6wfWba KeAVyJJX+nRDNZU4WZu7/Jd1WfVH6ank00dlpKM= X-Google-Smtp-Source: APXvYqz510aIoc/IjHsCVeRxFA84G6NMnjrJ/dIK4quWjs9jDotEGeonogMMr/U6maP5Beo9HWac5ZZoV0ysiCp1wbM= X-Received: by 2002:a24:2149:: with SMTP id e70mr1170681ita.23.1553213161314; Thu, 21 Mar 2019 17:06:01 -0700 (PDT) MIME-Version: 1.0 References: <5c941f4a.1c69fb81.dfc90.faa9SMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: <5c941f4a.1c69fb81.dfc90.faa9SMTPIN_ADDED_MISSING@mx.google.com> Date: Fri, 22 Mar 2019 01:05:50 +0100 Message-ID: To: Andrea Faulds Cc: PHP Internals Content-Type: multipart/alternative; boundary="000000000000bd9f950584a39ee8" Subject: Re: [PHP-DEV] Re: [RFC] Permit trailing whitespace in numeric strings From: benjamin.morel@gmail.com (Benjamin Morel) --000000000000bd9f950584a39ee8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable FWIW, I'd lean towards rejecting leading whitespace. That could be a good BC break candidate for PHP 8! Ben On Fri, 22 Mar 2019 at 00:33, Andrea Faulds wrote: > Hi again, > > I would proceed to a vote with this (and do intend to still), but the > response from internals has been very quiet. Has it gotten lost among > all the other things happening? :) > > I realise it's not a very exciting change of course, and there isn't > much to discuss about it. It's pretty much a like it or hate it RFC with > no particular nuance beyond that. > > One thing I do wonder about (given reaction on reddit and my personal > general doubt) is how internals feels about whether we should take the > opposite approach, that is, to break backwards-compatibility by > rejecting *leading* whitespace in numeric strings instead. All the > arguments in favour of this RFC's approach can also apply to that > approach if you flip them around. The main reason to go for what I did > so far is, well, it's harder to justify backwards-compatibility > breakages. But I also initially came up with this when PHP 8 wasn't on > the horizon. > > Andrea > > Andrea Faulds wrote: > > Hej allihopa, > > > > Here's an RFC that's been lying in my drafts for uh=E2=80=A6 26 months: > > > > https://wiki.php.net/rfc/trailing_whitespace_numerics > > > > I expect this should be an uncontroversial proposal, but maybe I'm > > jinxing it there. I hope you all like it. :) > > > > Thanks to Nikita for reminding me it existed and thus motivating me to > > pick it up again. Also thanks to Nikita for suggesting a potential > > follow-up RFC, and also making the =E2=80=9CSaner string to number comp= arisons=E2=80=9D > > RFC, both providing additional impetus for me to finally clean this up > > and put it to discussion. > > > > Thanks! > > Andrea > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --000000000000bd9f950584a39ee8--