Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113184
MIME-Version: 1.0
References: <CAKuGYLQJ+xNWv0hvUAObE6U98VYKzc3O9LaBMPggH+S8KNBVKg@mail.gmail.com>
 <CA71F0D2-7620-46E6-A764-4CFBD7CDD349@koalephant.com> <CAKuGYLSkdoPdQxv=YjhZS0Hzez0shCwnojS_UTJcXaSgoMbMJg@mail.gmail.com>
 <CAESVnVqTTCAU5buGBhxOqAkDFEwbx67MOyqiOGRCTKKmCiG_kQ@mail.gmail.com>
In-Reply-To: <CAESVnVqTTCAU5buGBhxOqAkDFEwbx67MOyqiOGRCTKKmCiG_kQ@mail.gmail.com>
Date: Mon, 15 Feb 2021 14:52:42 -0500
Message-ID: <CAKuGYLRx3X0zM=Ws3Z+SOHnjChTCQuRkpzBW9YxUT3ddgP9DOg@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Stephen Reay <php-lists@koalephant.com>, Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000de059005bb6554b2"
Subject: Re: [PHP-DEV] Whitespace around Paamayim Nekudotayim (double colon)
From: matthewmatthew@gmail.com (Matthew Brown)

--000000000000de059005bb6554b2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 15 Feb 2021 at 11:05, Sara Golemon <pollita@php.net> wrote:

> That change was made very recently (8.0) and was done for technical
> reasons (attributes) not aesthetic ones.
>
> Personally, I agree that adding whitespace around double colon is a
> suspect move, but breaking valid code for the sake of one's own sense of
> aesthetic doesn't progress the language, it regresses it.
>
> -Sara
>
> TL;DR - I vote No to such a change
>

OK, I take your point.

While I'm at it, I would also be happy for PHP to treat this as a parse
error (vs a runtime error, as it does currently):

$a->
list($a, $b) =3D $c;

But requiring zero whitespace after `->` would invalidate quite a bit of
existing code.

My reasons aren't _just_ aesthetic, mind =E2=80=93 this also leads to ambig=
uity
during autocompletion in IDEs. I realise it's not internals' job to make
that easier, though.

--000000000000de059005bb6554b2--