Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API

From: Date: Sat, 29 Jun 2024 09:31:41 +0000
Subject: Re: [RFC] [Discussion] Add WHATWG compliant URL parsing API
Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message

> On 29 Jun 2024, at 06:03, Bilge <[email protected]> wrote:
> 
> On 28/06/2024 22:35, Niels Dossche wrote:
>> - Why did you choose UrlParser to be a "static" class?
> 
> Because "static class" is the hip new cool ;)
> 
> Bilge

I would argue that for 90%+ of cases, static *userland* classes are used because 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 static methods on the url
class, or make the parser an instance with options.

Cheers

Stephen


Thread (152 messages)

« previous php.internals (#124017) next »