Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125391
Message-ID: <B1CE9C9A-8906-46D7-8DE7-83CFBD1B5473@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_508AA5DB-0BD5-41D6-AE29-440A4F1B7951"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\))
Subject: Re: [PHP-DEV] Pre-RFC Discussion: Support for String Literals as
 Object Properties and Named Parameters in PHP
Date: Mon, 2 Sep 2024 13:35:48 -0400
In-Reply-To: <480c0005-f495-4b0d-bd5d-5322077e466d@gmx.de>
Cc: Hammed Ajao <hamiegold@gmail.com>,
 internals@lists.php.net
To: "Christoph M. Becker" <cmbecker69@gmx.de>
References: <CA+Jpajmb6vp+yLG8Z78TafrCu3ZyYFrw5PL5JFSsAeA_ZX_Jjw@mail.gmail.com>
 <1C1BB102-EE71-49A6-A057-C727A39FC38F@newclarity.net>
 <480c0005-f495-4b0d-bd5d-5322077e466d@gmx.de>
From: mike@newclarity.net (Mike Schinkel)


--Apple-Mail=_508AA5DB-0BD5-41D6-AE29-440A4F1B7951
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On Sep 2, 2024, at 12:42 PM, Christoph M. Becker <cmbecker69@gmx.de> =
wrote:
>=20
> On 02.09.2024 at 16:51, Mike Schinkel wrote:
>=20
>> Generally I am one who welcomes new feature ideas, but I fear that =
string literals as object properties would break a valuable assumption =
that all properties must be a valid identifier. Without that assumption =
I fear many things that would become more complex.
>=20
> Is that so?  See <https://3v4l.org/bZTFi>.

Consider me corrected.

I seem to now remember once knowing this was possible since you point it =
out. I think my subconscious must have caused me to repress that memory =
given the tragedy of it when I read Hammad's proposal. =C2=AF\_(=E3=83=84)=
_/=C2=AF

>> So I am sympathetic to the desire to improve the language. However I =
fear this specific change would create more pain than pleasure. Better =
IMO to look for less disruptive solutions to achieve the same goals. For =
example, if the Enum+Attributes approach meets your needs aside from =
having too much boilerplate, maybe we could enhance PHP to have less of =
that boilerplate?
>=20
> ACK

Can you elaborate on what 'ACK' means in this context?

-Mike


--Apple-Mail=_508AA5DB-0BD5-41D6-AE29-440A4F1B7951
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Sep 2, 2024, at 12:42 PM, Christoph M. Becker &lt;<a =
href=3D"mailto:cmbecker69@gmx.de" class=3D"">cmbecker69@gmx.de</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">On 02.09.2024 at 16:51, Mike Schinkel wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Generally I am one who =
welcomes new feature ideas, but I fear that string literals as object =
properties would break a valuable assumption that all properties must be =
a valid identifier. Without that assumption I fear many things that =
would become more complex.<br class=3D""></blockquote><br class=3D"">Is =
that so? &nbsp;See &lt;<a href=3D"https://3v4l.org/bZTFi" =
class=3D"">https://3v4l.org/bZTFi</a>&gt;.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Consider me corrected.</div><div><br =
class=3D""></div><div>I seem to now remember once knowing this was =
possible since you point it out. I think my subconscious must have =
caused me to repress that memory given the tragedy of it when I read =
Hammad's proposal.&nbsp;<span style=3D"color: rgb(29, 28, 29); =
font-family: Slack-Lato, Slack-Fractions, appleLogo, sans-serif; =
font-size: 15px; orphans: 2; widows: 2; background-color: rgb(248, 248, =
248);" class=3D"">=C2=AF\_(=E3=83=84)_/=C2=AF</span></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D"">So I am sympathetic to =
the desire to improve the language. However I fear this specific change =
would create more pain than pleasure. Better IMO to look for less =
disruptive solutions to achieve the same goals. For example, if the =
Enum+Attributes approach meets your needs aside from having too much =
boilerplate, maybe we could enhance PHP to have less of that =
boilerplate?<br class=3D""></blockquote><br class=3D"">ACK<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Can =
you elaborate on what 'ACK' means in this context?</div><div><br =
class=3D""></div><div>-Mike</div></div><br class=3D""></body></html>=

--Apple-Mail=_508AA5DB-0BD5-41D6-AE29-440A4F1B7951--