Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110379
To: Marcio Almada <marcio.web2@gmail.com>
CC: internals <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] Shorter attribute syntax
Thread-Index: AQHWOgIv0rCwDWp4oECJgOMrWx9MxKjI6UuAgAABI/Q=
Date: Thu, 4 Jun 2020 20:40:07 +0000
Message-ID:
 <BYAPR05MB6535CF9EA64DC8AD629634D2DE890@BYAPR05MB6535.namprd05.prod.outlook.com>
References:
 <BYAPR05MB6535959E5CB99B9BE918E561DE880@BYAPR05MB6535.namprd05.prod.outlook.com>,<CAOsHV+tduL15fGA2Q6E07vfM5e46DWwNpgE3nnya-bWvq9BQRw@mail.gmail.com>
In-Reply-To:
 <CAOsHV+tduL15fGA2Q6E07vfM5e46DWwNpgE3nnya-bWvq9BQRw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [e8zy9Gp1w//MGm4CGXHHpT+RIbuG2Oec]
x-ms-publictraffictype: Email
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 76aaa35a-d3e7-4f73-377b-08d808c777f4
x-ms-traffictypediagnostic: MW2NAM12HT153:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 hKBIjfqoG2vXgZe7FmXth1uVzlYq7oKfI5L75lROMPdsr/P1hMMM1aAzicHDNQ/lUtBkTwaCyHkEbzRBSQwE0RRPW8Fi+pd0SMdC/nRmZQSWLweDbgffU33/4xPGzeP9sdaY+InygmnXFPyXApH7KVtPO6XyMzeij7lhG8VTBHuZbakXl+eJ3JlFGZ4zniNKu+NZ8Tb0bWXBZCogfv5+pA==
x-forefront-antispam-report:
 CIP:255.255.255.255;CTRY:;LANG:en;SCL:0;SRV:;IPV:NLI;SFV:NSPM;H:BYAPR05MB6535.namprd05.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:;DIR:OUT;SFP:1901;
x-ms-exchange-antispam-messagedata:
 YSZ41K7Dc/DAWSPUCGIEWL4HpYk0wZBYoE409pcWckWC4j1JSKQRGGg03gYd9Mqh0irUGpMu8UtK1tIXQMyzbxiDzhB8fnYM80dmaZbIusgShn/GPDbiZa7Dr7FSAG0QoEMaIoRdH6m5Vpg2KJgnDQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 76aaa35a-d3e7-4f73-377b-08d808c777f4
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2020 20:40:07.5713
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2NAM12HT153
Subject: Re: [PHP-DEV] [RFC] Shorter attribute syntax
From: theodorejb@outlook.com (Theodore Brown)

On Thu, June 4, 2020 at 3:28 PM Marcio Almada <marcio.web2@gmail.com> wrote=
:=0A=
=0A=
> I'd also prefer any attribute syntax without the bracket-like pair=0A=
> of tokens. I'm just a bit confused about the RFC itself and the PR=0A=
> content at this point. =0A=
>=0A=
> The RFC is currently proposing `@@MyAttribute()` and the PR=0A=
> is currently implementing `@:MyAttribute()` as the sigil. The first=0A=
> brings a BC break and the second doesn't, being the important=0A=
> difference.=0A=
>=0A=
> I'm inclined to `@:` instead of `@@`. Which one will actually be=0A=
> on the ballot? :D=0A=
=0A=
Hi Marcio,=0A=
=0A=
`@@` is the syntax that will be voted on. The linked PR is for the=0A=
original `@:` implementation, but as the RFC notes switching this=0A=
to `@@` just requires a single character to be changed in the lexer=0A=
and a small grammar adjustment. If the proposal is accepted we'll=0A=
submit a new PR with the updated implementation.=0A=
=0A=
Apologies for the confusion!=0A=
=0A=
Theodore=0A=