Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124029
Content-Type: multipart/alternative;
 boundary="------------Kqs9x0WbeI4uP62EQVS9UXfJ"
Message-ID: <56f90e18-ed94-4b33-bb23-021e112d1ead@scriptfusion.com>
Date: Sat, 29 Jun 2024 12:52:37 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
To: Stephen Reay <php-lists@koalephant.com>
Cc: internals@lists.php.net
References: <50DEC8FF-FBE1-4B39-AACD-076683499897@koalephant.com>
Content-Language: en-GB
In-Reply-To: <50DEC8FF-FBE1-4B39-AACD-076683499897@koalephant.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------Kqs9x0WbeI4uP62EQVS9UXfJ
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 29/06/2024 10:31, Stephen Reay wrote:
>> On 29 Jun 2024, at 06:03, Bilge<bilge@scriptfusion.com>  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.

No objection. I was only kidding :)

Cheers, Bilge

--------------Kqs9x0WbeI4uP62EQVS9UXfJ
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 29/06/2024 10:31, Stephen Reay
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:50DEC8FF-FBE1-4B39-AACD-076683499897@koalephant.com">
      <pre class="moz-quote-pre" wrap="">
</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">On 29 Jun 2024, at 06:03, Bilge <a class="moz-txt-link-rfc2396E" href="mailto:bilge@scriptfusion.com">&lt;bilge@scriptfusion.com&gt;</a> wrote:

On 28/06/2024 22:35, Niels Dossche wrote:
</pre>
        <blockquote type="cite">
          <pre class="moz-quote-pre" wrap="">- Why did you choose UrlParser to be a "static" class?
</pre>
        </blockquote>
        <pre class="moz-quote-pre" wrap="">
Because "static class" is the hip new cool ;)

Bilge
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
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.</pre>
    </blockquote>
    <p>No objection. I was only kidding :)</p>
    <p><span style="white-space: pre-wrap">Cheers,
Bilge
</span></p>
  </body>
</html>

--------------Kqs9x0WbeI4uP62EQVS9UXfJ--