Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120925
MIME-Version: 1.0
References: <TYWP286MB22515F6CC485136AFF9FA095F21CA@TYWP286MB2251.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <TYWP286MB22515F6CC485136AFF9FA095F21CA@TYWP286MB2251.JPNP286.PROD.OUTLOOK.COM>
Date: Wed, 23 Aug 2023 11:16:25 +0300
Message-ID: <CAAwdEzAKOfdysJtodjMrAOjMBLBMgV+2dD4tGE=Hi2u3hOUSCg@mail.gmail.com>
To: chopins xiao <chopins.xiao@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006936d3060392bb11"
Subject: Re: [PHP-DEV] Replace ugly attribute token #[] to other
From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=)

--0000000000006936d3060392bb11
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 23, 2023 at 9:36=E2=80=AFAM chopins xiao <chopins.xiao@gmail.co=
m> wrote:

> I use @ instead of #[] as attribute token. attribute use whitespace marks
> are closed. Of course you can start with @@ or #, other.
> error control use @@ instead of @, add T_SILENCE token
>
> <snip>

>
> my implemented:
> https://github.com/chopins/php-src/tree/new-syntax/attribute
>
>
> Other new syntax implemented (Verification of feasibility) :
>
> https://github.com/chopins/php-src/blob/php-alternative-syntax/alternativ=
e-syntax.md
>
>
> Regards
> Chopin Xiao
>

Hey Chopin

You can check:
https://wiki.php.net/rfc/attributes_v2, that initially implemented it with
<<Attribute>>
https://wiki.php.net/rfc/shorter_attribute_syntax, that changed the syntax
to @@Attribute
https://wiki.php.net/rfc/shorter_attribute_syntax_change, that finally
changed the syntax to #[Attribute]

In time, the last syntax proved to be good, especially when dealing with
code that must run as well on PHP versions before PHP 8.0, as it's
interpreted there as a comment.

All I can see right now are a lot of backward incompatible changes that are
unlikely to be accepted with no clear gains.
Please consider them, so that there is a clear upgrade path for existing
codebase.

Regards,
Alex

--0000000000006936d3060392bb11--