Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126947
Date: Tue, 25 Mar 2025 16:06:03 -0700 (PDT)
To: =?UTF-8?Q?M=C3=A1t=C3=A9_Kocsis?= <kocsismate90@gmail.com>
Cc: Internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
Message-ID: <A0229B50-4238-4C1F-8339-D0552813FF69@automattic.com>
In-Reply-To: <CAH5C8xXeJf96ETaphZvKoX19Ssd_Uc=8jMbc4J-HuciCUF=XzA@mail.gmail.com>
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
	<dd61999c-1ebd-4765-9add-cd8065968965@gmail.com>
	<CAOV5rgYZ_s1of-igLFEK7oqqh6=3HeYv0=JvvKvvjkcp0F6Q9Q@mail.gmail.com>
	<CAH5C8xV67frqOBCvLt73RM7QO86_pu40sHP5h71_kDRbKPtA8Q@mail.gmail.com>
	<1BCB4144-231D-45EA-A914-98EE8F0F503A@automattic.com>
	<8E614C9C-BA85-45D8-9A4E-A30D69981C5D@automattic.com>
	<CAH5C8xV69pHnSKWJrVB8EQab7vPhcaXAwYezoG6z3Oj7ZkXBaQ@mail.gmail.com>
	<044E7A8E-B79D-44DB-B572-102A80CDFC3C@automattic.com>
	<CAH5C8xWpquzmvtbSk6=mL4U0z=Tupv2zD+FXag+zenF7q04HUQ@mail.gmail.com>
	<CAH5C8xXeJf96ETaphZvKoX19Ssd_Uc=8jMbc4J-HuciCUF=XzA@mail.gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_64F249A4-8E09-4112-8058-911B957A49B8"
From: dennis.snell@automattic.com (Dennis Snell)


--=_64F249A4-8E09-4112-8058-911B957A49B8
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

> On Mar 25, 2025, at 3:23 PM, M=C3=A1t=C3=A9 Kocsis <kocsismate90@gmail.co=
m> wrote:
>=20
>=20
> Hi Dennis,
>=20
>=20
>> I am myself also a bit lost on the countless names that I tried out in t=
he implementation, but I think I had toHumanFriendlyString() and toDisplayF=
riendlyString() methods at some point. These then ended up being toString()=
 and toDisplayString() after some iterations. I would be ok with renaming g=
etHost() and toString() so=C2=A0that their names suggest they don't use IDN=
A,=C2=A0but I'd clearly need a good enough=C2=A0suggestion, since neither "=
MachineFriendly", nor "NonDisplayable" sound like the best alternative for =
me. I was also considering using getIdnaHost() and toIdnaString(), but I re=
alized these are the worst looking names I have come up with so=C2=A0far.
>>=20
>>=20
>>=20
>=20
> What about getPunycodeHost(), getUnicodeHost(), toPunycodeString(), toUni=
codeString()? Or getAsciiHost() and toAsciiString() may also work. These ar=
e the best names I managed to come up with so far.
>=20
>=20
> In the=C2=A0meantime, I renamed RFC 3986's toString() methods too accordi=
ng to another suggestion:
> - toString() became toRawString()
> - toNormalizedString() became toString()
>=20
>=20
> The new names mirror exactly what their getter counterparts do.
>=20
>=20
> M=C3=A1t=C3=A9=C2=A0
>=20
>=20

Hi M=C3=A1t=C3=A9,


I=E2=80=99ve been pondering these names for the past week and a half and I =
couldn=E2=80=99t think of anything, but at first glance I like getUnicodeHo=
st() and getAsciiHost(). These communicate=C2=A0a little bit the nuance, th=
ough they aren=E2=80=99t totally in-your-face (which in this case I wish th=
ere were a more obvious pair that is).


Other pairs I was toying with but don=E2=80=99t like are:
=C2=A0- getPrintHost() / getDataHost()
=C2=A0- getDisplayHost() / getAPIHost()
=C2=A0- getDisplayHost() / getEncodedHost()
=C2=A0- getDisplayHost() / getEscapedHost()


(the same pairs would apply to the other methods, like toDisplayString() / =
toEncodedString())


This seems to be taking a lot of effort and time, but thank you still for e=
ngaging with it =E2=80=94 naming is hard! But it=E2=80=99s worth it.


--=_64F249A4-8E09-4112-8058-911B957A49B8
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w=
3.org/TR/REC-html40/loose.dtd">
<html>
<head>
<meta charset=3D"utf-8">
<style>body{font-family:-apple-system,Helvetica,Arial,sans-serif;}blockquot=
e{margin:0;padding:0 0 0 12px;border-left:1px solid #aaa;color:#aaa;}hr.uni=
box-forward{border:0;color:#888;background-color:#888;height:1px;}</style>
</head>
<body>
<blockquote type=3D"cite">
<div>On Mar 25, 2025, at 3:23 PM, M=C3=A1t=C3=A9 Kocsis &lt;kocsismate90@gm=
ail.com&gt; wrote:</div>
<div><br></div>
<div dir=3D"ltr" style=3D"caret-color: rgb(0, 0, 0); font-family: -webkit-s=
tandard; font-variant-caps: normal; font-weight: 400; text-decoration: none=
;">Hi Dennis,</div>
<div dir=3D"ltr" style=3D"caret-color: rgb(0, 0, 0); font-family: -webkit-s=
tandard; font-variant-caps: normal; font-weight: 400; text-decoration: none=
;"><br></div>
<div class=3D"gmail_quote gmail_quote_container" style=3D"caret-color: rgb(=
0, 0, 0); font-family: -webkit-standard; font-variant-caps: normal; font-we=
ight: 400; text-decoration: none;">
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; borde=
r-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 20=
4, 204); padding-left: 1ex;"><div dir=3D"ltr"><div class=3D"gmail_quote"><d=
iv>I am myself also a bit lost on the countless names that I tried out in t=
he implementation, but I think I had toHumanFriendlyString() and toDisplayF=
riendlyString() methods at some point. These then ended up being toString()=
 and toDisplayString() after some iterations. I would be ok with renaming g=
etHost() and toString() so=C2=A0that their names suggest they don't use IDN=
A,=C2=A0but I'd clearly need a good enough=C2=A0suggestion, since neither "=
MachineFriendly", nor "NonDisplayable" sound like the best alternative for =
me. I was also considering using getIdnaHost() and toIdnaString(), but I re=
alized these are the worst looking names I have come up with so=C2=A0far.</=
div></div></div></blockquote>
<div><br></div>
<div>What about getPunycodeHost(), getUnicodeHost(), toPunycodeString(), to=
UnicodeString()? Or getAsciiHost() and toAsciiString() may also work. These=
 are the best names I managed to come up with so far.</div>
<div><br></div>
<div>In the=C2=A0meantime, I renamed RFC 3986's toString() methods too acco=
rding to another suggestion:</div>
<div>- toString() became toRawString()</div>
<div>- toNormalizedString() became toString()</div>
<div><br></div>
<div>The new names mirror exactly what their getter counterparts do.</div>
<div><br></div>
<div>M=C3=A1t=C3=A9=C2=A0</div>
</div>
</blockquote>
<div><br></div>
<div>Hi M=C3=A1t=C3=A9,</div>
<div><br></div>
<div>I=E2=80=99ve been pondering these names for the past week and a half a=
nd I couldn=E2=80=99t think of anything, but at first glance I like getUnic=
odeHost() and getAsciiHost(). These communicate<i>=C2=A0</i>a little bit th=
e nuance, though they aren=E2=80=99t totally in-your-face (which in this ca=
se I wish there were a more obvious pair that is).</div>
<div><br></div>
<div>Other pairs I was toying with but don=E2=80=99t like are:</div>
<div>=C2=A0- getPrintHost() / getDataHost()</div>
<div>=C2=A0- getDisplayHost() / getAPIHost()</div>
<div>=C2=A0- getDisplayHost() / getEncodedHost()</div>
<div>=C2=A0- getDisplayHost() / getEscapedHost()</div>
<div><br></div>
<div>(the same pairs would apply to the other methods, like toDisplayString=
() / toEncodedString())</div>
<div><br></div>
<div>This seems to be taking a lot of effort and time, but thank you still =
for engaging with it =E2=80=94 naming is hard! But it=E2=80=99s worth it.</=
div>
</body>
</html>
--=_64F249A4-8E09-4112-8058-911B957A49B8--