Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126114
Message-ID: <6c1b378a-4c93-4747-bb5a-84d133c95d8b@gmx.de>
Date: Fri, 6 Dec 2024 00:16:10 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
Content-Language: de-DE
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>,
 =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: ignace nyamagana butera <nyamsprod@gmail.com>,
 Niels Dossche <dossche.niels@gmail.com>, internals@lists.php.net
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>
 <57d09ef6591a4c70e60569b9de7ce330@bastelstu.be>
 <CAH5C8xXhHk2QjM5+VzKPFkBoLpO+kR-Tqr_o1YoaW=fkURHQFA@mail.gmail.com>
In-Reply-To: <CAH5C8xXhHk2QjM5+VzKPFkBoLpO+kR-Tqr_o1YoaW=fkURHQFA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:GuwUDK8Fii4=;g9H98ILcmwgFodpDN5GO6EPRX48
 duHrQEkvvp8Fipxwr8O7Sfo76cu7b4kAs9BenMI0gPAMOCx3uq03fnyGDrF89KE2gJu32hKIc
 45hZfm4p6V43qhdkVKiQxWb/LxE3VWlfv+sWgSIE9YYBwQ6nvAwNOj+9RfrrIyS4pJMCGqAMu
 FmFNmwJkHHdIZGAzmKeZwMo0yxyDwO5/ElWm7YyKVLoDowvv+lX6OpTyaJcr1puHKT3rKUsG0
 Tb3+45VnuK0gshBy7A5RIGbW0cY1ISQ0OCAegO+soAwBDQrJM5A3ad10qTH9QbWhDlcT36/iI
 358DhkYs+zY3+GYBCBDwLk+h0u2iQVD0xC5CcbbyI4eJyDr+Xr/7YEDCeMHhCy3cwx8d5+i9k
 b0CtDox0WJJ6C98YniRptpTu0gU1+z5lwSEdx5lKfCM+9wycDVKoww8HOF53Ifaoynft4DiTm
 7Y7MxT/rRy2C7AjsF6dETfnTCDuBAJyIWIcTnxbEnsMPjOoZJhk8obYNjrSYmw1lfjMXujuk1
 ikB5gaFQB9skSEgbBzqedVMLeQ1w01eFPBjebirQ1+c8XIlBTlijhcnJpmg01ORE7h1i0/X4H
 n9aTV8xxYpSoD6GEoUFNp4SS4pmiiTqc8m1WDXZGfqKjkB8NGB01am14H39ZVlf4LZRC408kx
 t/OjxvnKShRnzNnxf8ym4Ccc1ugc/fRQH4gpxfnUyyZEBtHw1FyhBoVXgT+EL2CXurZSoNkXk
 3AZaioP/BCU/yQaowHoUl7KUesqICmYK1WZ8eTNJmCaiqnJWV7MhxmDmoaU4kOwaEYUw73Sz9
 eP+aX7xWD3hwH5kfbONoLkvLH+HwTvXj1tCXe0fM6a+A7bGjmsLA9ksDA9EWgQwbNLYhtJaSz
 otgDMSeYnmv3ioTUl0W/hVBFRa8nhDPsSqUAYff9RlYOk1vRyx4Ouic16rm+EwJ6Wyrv6HRmF
 3mvCEXP+CexzYuKi16ZyV3D0ZpNP10AkD0kceQdY+bM2v/An15Munrrc93KAEawXsgepL1nUT
 vkveBhRDMNbY9eQNFsMLewhdsCBfB9BxvypUEK+VQK07pZDn2Gfz5h84Pwvlc8/3AlHIE8kBP
 fDa9e17rP+zmqBmmHtxpPAkfSbRwbf
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 05.12.2024 at 22:49, M=C3=A1t=C3=A9 Kocsis wrote:

>> I'm not sure I like the `Interface` suffix on the `UriInterface`
>> interface. Just `Uri\Uri` would be equally expressive.
>
> Yes, I was expecting this debate :) To be honest, I never liked interfac=
es
> without an "Interface"
> suffix, and my dislike didn't go away when I had to use such an interfac=
e
> somewhere, because it
> was difficult for me to find out what the symbol I was typing actually
> referred to.

By the same argument, you could come up with code like

<?php
class User {
    const defaultGroupNameConstant =3D "users";
    private string $nameVariable;
    public function getNameMethod() {=E2=80=A6}
    =E2=80=A6
}
?>

> But apart from my personal
> experiences, I prefer to stay with "UriInterface" because the 2 most wel=
l
> known internal PHP interfaces
> also have the same suffix (DateTimeInterface, SessionInterface), and thi=
s
> name definitely conveys that
> people should not try to instantiate it.

DateTimeInterface has been introduced after there had already been
DateTime.  Otherwise, we would likely have DateTime, DateTimeMutable and
DateTimeImmutable.  (Or only DateTime as immutable class.)

SessionHandler/SessionHandlerInterface have been bad naming choices, in
my opinion.  The interface could have been SessionHandler, and the class
DefaultSessionHandler (and should have been final).  I dislike these
Interface and Implementation (or abbreviations of these) suffixes.

Christoph