Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124017
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
Message-ID: <50DEC8FF-FBE1-4B39-AACD-076683499897@koalephant.com>
Date: Sat, 29 Jun 2024 16:31:41 +0700
Cc: internals@lists.php.net
To: Bilge <bilge@scriptfusion.com>
From: php-lists@koalephant.com (Stephen Reay)


> On 29 Jun 2024, at 06:03, Bilge <bilge@scriptfusion.com> wrote:
>=20
> =EF=BB=BFOn 28/06/2024 22:35, Niels Dossche wrote:
>> - Why did you choose UrlParser to be a "static" class?
>=20
> Because "static class" is the hip new cool ;)
>=20
> Bilge

I would argue that for 90%+ of cases, static *userland* classes are used bec=
ause of (a) autoloading and (b) the ability to use private/protected methods=
.

Neither of those apply to a php extension.

I agree with the others, the static parser class is weird. Either put the st=
atic methods on the url class, or make the parser an instance with options.

Cheers

Stephen