Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111133
To: Derick Rethans <derick@php.net>, PHP Developers Mailing List
	<internals@lists.php.net>
Thread-Topic: [PHP-DEV] The @@ is terrible, are we sure we're OK with it?
Thread-Index: AQHWYB+xuk8gBb/CD0iZOS7S/V0L06kT0uLa
Date: Wed, 22 Jul 2020 17:09:42 +0000
Message-ID:
 <DM6PR07MB661873706B57603ECBDE9D7EF9790@DM6PR07MB6618.namprd07.prod.outlook.com>
References:
 <alpine.DEB.2.23.453.2007221247530.7489@singlemalt.home.derickrethans.nl>
In-Reply-To:
 <alpine.DEB.2.23.453.2007221247530.7489@singlemalt.home.derickrethans.nl>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [ltMKpQw/FN1WG3p6gfejttIKhsTUqcds]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: bd9f3e67-d10b-4baa-3aa8-08d82e6206ee
x-ms-traffictypediagnostic: DM6NAM11HT065:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 ZgjrEvGORW7W9ot+flEMzG6RXB1SzkjuQ7bzerL+K3KR7tEA2rcDT3Ot/z+ARK3obQ0athavvX61JnfuEC1BcfDhV71dNjHZz8wGwJaZuiufREu841cIObVPqPxaQg4txPkS6yakIoQvFK6tY41tSw3v/tCRY6Hzy4ZnNPtxcbqu8S4MqZRmu+DMxmXa5FtDOX4GSBdZ0OnPTMn7m2KpjQ==
x-forefront-antispam-report:
 CIP:255.255.255.255;CTRY:;LANG:en;SCL:0;SRV:;IPV:NLI;SFV:NSPM;H:DM6PR07MB6618.namprd07.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:;DIR:OUT;SFP:1901;
x-ms-exchange-antispam-messagedata:
 YU3Uz6b3PZEiumy7bLpY93RlWMUTXRdeZ6o1P/ZNfm3R7uXKefox03WFVTzH9o6x9ZXAFapzgQS1xtKxNGMePdXqeDRf5zklTMncpLlpZSfTDXeYrhzurmcIvWk+LC2p0PK6CYAOO621uPw2m0Q+oA==
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: hotmail.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM11FT012.eop-nam11.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: bd9f3e67-d10b-4baa-3aa8-08d82e6206ee
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2020 17:09:43.0024
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6NAM11HT065
Subject: Re: [PHP-DEV] The @@ is terrible, are we sure we're OK with it?
From: tysonandre775@hotmail.com (tyson andre)

Hi Derick,=0A=
=0A=
> Please, let's do the sensible and use the Rusty #[...] syntax.=0A=
=0A=
I'd probably re-vote for `<<Attribute>>` given the fact that `@@` may intro=
duce similar parsing ambiguities in the future=0A=
that may interfere with future language changes. (but those issues are not =
a certainty)=0A=
=0A=
I think that `#[` has its own issues, but am open to re-voting on it.=0A=
For example, the following snippet would get parsed differently in PHP 7.4 =
and PHP 8.0, given a hypothetical JIT annotation for Opcache.=0A=
With <<Opcache\Jit>>, it would give people a clear indication that the file=
 required PHP 8.0,=0A=
but a one-line annotation might be silently treated differently in many sub=
tle ways in 7.4.=0A=
It's probably possible to amend the parser make it an error to put the func=
tion declaration on the same line or to have other `#` comments=0A=
within a multi-line #[ annotation,=0A=
but I really dislike the special casing it would add.=0A=
=0A=
```=0A=
$function =3D array_filter(=0A=
=A0 =A0 $values,=0A=
=A0 =A0 #[Opcache\Jit] function(int $x) { return $x % 2 > 0; }=0A=
);=0A=
```=0A=
=0A=
Cheers,=0A=
- Tyson=