Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113186
MIME-Version: 1.0
References: <CAKuGYLQJ+xNWv0hvUAObE6U98VYKzc3O9LaBMPggH+S8KNBVKg@mail.gmail.com>
 <CA71F0D2-7620-46E6-A764-4CFBD7CDD349@koalephant.com> <CAKuGYLSkdoPdQxv=YjhZS0Hzez0shCwnojS_UTJcXaSgoMbMJg@mail.gmail.com>
 <d1f5b0d3-16e5-6436-496e-2ca7a0a54e85@gmail.com>
In-Reply-To: <d1f5b0d3-16e5-6436-496e-2ca7a0a54e85@gmail.com>
Date: Mon, 15 Feb 2021 15:25:42 -0500
Message-ID: <CAKuGYLRmHZGYRM4jHfKKoGLV7yiN-DBhXqxMgdDVEcOL=cD_Ww@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e5957c05bb65ca38"
Subject: Re: [PHP-DEV] Whitespace around Paamayim Nekudotayim (double colon)
From: matthewmatthew@gmail.com (Matthew Brown)

--000000000000e5957c05bb65ca38
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks, now I realise I was probably wrong to bring this up.

I had it in my mind that "::" could never appear chained together (thinking
of constants), but it's just that I've never seen code that chains them
together =E2=80=93 i.e. this is valid:

A::b()::c()::$d::$e =3D 5;


On Mon, 15 Feb 2021 at 15:06, Rowan Tommins <rowan.collins@gmail.com> wrote=
:

> On 15/02/2021 14:52, Matthew Brown wrote:
> > The most comparable example is between namespace separators:
> >
> > Ns \ bar();
> > Ns \ SOME_CONST;
> >
> > are both syntax errors.
>
>
> As Sara says, this only became an error in 8.0, and there was a rather
> specific reason for it, but I think there is a philosophical difference,
> too.
>
> "\" is part of a single piece of syntax: a fully-qualified class,
> constant, or function name. You can't write $foo\Bar or Foo\$bar or
> $foo\$bar.
>
> "::" on the other hand is an operator that can be used in a variety of
> ways. You can write $foo::bar(), Foo::$bar, $foo::$bar, {$foo .
> 'Handler'}::handle(), parent::foo(), and so on. It stands to reason that
> it would have the same whitespace rules as any other operator.
>
>
> > I was surprised to learn that PHP treats :: similar to ->
>
> I think it would be rather surprising if it *didn't* treat the two
> operators similarly, since they're so closely related.
>
>
> > I wonder if there's a benefit to removing a small potential footgun fro=
m
> > the language?
>
>
> I'm not really sure what the footgun here is. Adding newlines around
> just about any operator you can think of will lead to code that confuses
> at first glance:
>
> $x =3D [
>      1,
>      2,
>      3,
>      4,
>      5
> ]
>
> // Wait, we're not done yet...
>
> [2];
>
>
> Short of changing the entire language from semicolon-delimited to
> newline-delimited, that's inevitable.
>
>
> Regards,
>
> --
> Rowan Tommins
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--000000000000e5957c05bb65ca38--