Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124528
Feedback-ID: ifab94697:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-568-g843fbadbe-fm-20240701.003-g843fbadb
Precedence: bulk
MIME-Version: 1.0
Message-ID: <66c4ac1c-b3d7-4b20-b986-1fe1a464f485@app.fastmail.com>
In-Reply-To: <a3154cde-73ca-4b8e-bf90-b9aeabd5fbce@app.fastmail.com>
References: <0a6a61cd-f203-4dea-a7f8-97e6b885c52d@app.fastmail.com>
 <b5c0be62-ea39-47fb-a8f8-ab6cd5ee3dab@app.fastmail.com>
 <CP8P284MB2148CB72E1A6A7AB5F29E8F093AE2@CP8P284MB2148.BRAP284.PROD.OUTLOOK.COM>
 <a3154cde-73ca-4b8e-bf90-b9aeabd5fbce@app.fastmail.com>
Date: Sun, 21 Jul 2024 11:21:24 +0200
To: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Asymmetric Visibility, v2
Content-Type: multipart/alternative;
 boundary=a884214e4e5443dea42fbcb96580507f
From: rob@bottled.codes ("Rob Landers")

--a884214e4e5443dea42fbcb96580507f
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Sat, Jul 20, 2024, at 23:51, Larry Garfield wrote:
> On Sat, Jul 20, 2024, at 7:22 AM, Rodrigo Vieira wrote:
> > Will the alternative syntax on hook not even be put to a vote?
>=20
> It was, a year and a half ago when Aviz was first proposed.  The prefe=
rence was split, but leaned toward the prefix-style syntax.  So we went =
with that.  I don't think we'll ever get everyone to want the same synta=
x, but we're using the one that was both somewhat more popular, and (as =
discussed in the RFC) arguably superior.
>=20
> As the "comments in yield from" thread has shown, *any* even slight ch=
ange to PHP's syntax will require work from static analysis tools.  That=
's the nature of the problem space, regardless of the syntax specifics.
>=20
> --Larry Garfield
>=20

Just to play devil=E2=80=99s advocate, it was also before we had propert=
y hooks who advertised itself as a way to =E2=80=9Cwrap and guard access=
 to object properties=E2=80=9D but we are simply ignoring their existenc=
e here.

=E2=80=94 Rob
--a884214e4e5443dea42fbcb96580507f
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div>=
<br></div><div>On Sat, Jul 20, 2024, at 23:51, Larry Garfield wrote:<br>=
</div><blockquote type=3D"cite" id=3D"qt" style=3D""><div>On Sat, Jul 20=
, 2024, at 7:22 AM, Rodrigo Vieira wrote:<br></div><div>&gt; Will the al=
ternative syntax on hook not even be put to a vote?<br></div><div><br></=
div><div>It was, a year and a half ago when Aviz was first proposed.&nbs=
p; The preference was split, but leaned toward the prefix-style syntax.&=
nbsp; So we went with that.&nbsp; I don't think we'll ever get everyone =
to want the same syntax, but we're using the one that was both somewhat =
more popular, and (as discussed in the RFC) arguably superior.<br></div>=
<div><br></div><div>As the "comments in yield from" thread has shown, *a=
ny* even slight change to PHP's syntax will require work from static ana=
lysis tools.&nbsp; That's the nature of the problem space, regardless of=
 the syntax specifics.<br></div><div><br></div><div>--Larry Garfield<br>=
</div><div><br></div></blockquote><div><br></div><div>Just to play devil=
=E2=80=99s advocate, it was also before we had property hooks who advert=
ised itself as a way to =E2=80=9Cwrap and guard access to object propert=
ies=E2=80=9D but we are simply ignoring their existence here.<br></div><=
div><br></div><div id=3D"sig121229152">=E2=80=94 Rob<br></div></body></h=
tml>
--a884214e4e5443dea42fbcb96580507f--