Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111351
MIME-Version: 1.0
References: <alpine.DEB.2.23.453.2008041440380.7489@singlemalt.home.derickrethans.nl>
 <BYAPR05MB6535AE9831221566469C4503DE4A0@BYAPR05MB6535.namprd05.prod.outlook.com>
 <alpine.DEB.2.23.453.2008060741110.7489@singlemalt.home.derickrethans.nl> <20200806091749.64675445@mcmic-probook.opensides.be>
In-Reply-To: <20200806091749.64675445@mcmic-probook.opensides.be>
Date: Thu, 6 Aug 2020 08:42:15 +0100
Message-ID: <CAJvSBVMMpP1=jrMX1vB5SsLWdXsS5N6M1o9dFCZhFv-bJr-W1g@mail.gmail.com>
To: =?UTF-8?Q?C=C3=B4me_Chilliet?= <come.chilliet@fusiondirectory.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b5bad605ac30a24c"
Subject: Re: [PHP-DEV] [RFC] Shorter Attribute Syntax Change RFC 0.2
From: phpmailinglists@gmail.com (Peter Bowyer)

--000000000000b5bad605ac30a24c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 6 Aug 2020 at 08:18, C=C3=B4me Chilliet <
come.chilliet@fusiondirectory.org> wrote:

> As said before, it does have an ending delimiter when they are arguments
> since
>  there is the parenthesis around them. When there are no arguments I don=
=E2=80=99t
> see
>  the benefit of an ending delimiter, it=E2=80=99s easy to spot the end of=
 the word.
>

And if needed, make the parenthesis required. So @@Foo is illegal,
but @@Foo() is allowed.

Required parenthesis is familiar to most PHP programmers (functions,
classes following common coding conventions) - what's not to like?

Using "^" in the code demonstrations below as no one has proposed it and my
point isn't about #, << or @@ we get:

^Foo(
  ^Bar(43, "raa")
)

vs

^[Foo(
  ^[Bar(43, "raa")]
)]

To me the former is significantly more pleasant to read.

Is it difficult to parse?

Peter

--000000000000b5bad605ac30a24c--