Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123887
Content-Type: multipart/alternative;
 boundary="------------6pDdC0v0FZtLlH1IP27MBC0s"
Message-ID: <d41cad0a-99fc-461d-84ae-4ba627f70599@scriptfusion.com>
Date: Wed, 26 Jun 2024 21:18:39 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Static class
To: internals@lists.php.net
References: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
 <ef0c3617-6757-45a1-a485-3f7c197fd599@app.fastmail.com>
 <4596aa73-cfd4-2292-7191-2839a5bab695@php.net>
Content-Language: en-GB
In-Reply-To: <4596aa73-cfd4-2292-7191-2839a5bab695@php.net>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------6pDdC0v0FZtLlH1IP27MBC0s
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 25/06/2024 16:17, Derick Rethans wrote:
> we shouldn't be encouraging static classes as
> a bag of static functions, that ought to be just namespaced functions.

I understand this is the prevailing preference of a certain few, 
including (but not limited to) yourself and Larry. Nevertheless, classes 
as a bag of static functions is a phenomenon that exists and will 
continue to exist in PHP until such a time as `static` is completely 
removed from the language, so I don't really understand the avoidance of 
adding, in the interim, what seems like just a missing part of an 
existing feature.

However, I still want to understand why a file of functions is strictly 
better than a class of functions. What are the benefits of a file over a 
class?

For me, I dislike importing individual functions. It is often the case 
that, when such logic is so grouped in a static class, where we use one 
we may use several such functions. In such a case, we only need a single 
import statement instead of one for each function. This seems like a 
clear benefit. Even in the case that I only use one, I still prefer to 
import a class over a function, because it has better support in my 
editor and doesn't stick out like a sore thumb in the list of imports 
(why should it?).

Cheers, Bilge

--------------6pDdC0v0FZtLlH1IP27MBC0s
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 25/06/2024 16:17, Derick Rethans
      wrote:<span style="white-space: pre-wrap">
</span><span style="white-space: pre-wrap">
</span></div>
    <blockquote type="cite"
      cite="mid:4596aa73-cfd4-2292-7191-2839a5bab695@php.net">
      <pre class="moz-quote-pre" wrap="">we shouldn't be encouraging static classes as 
a bag of static functions, that ought to be just namespaced functions.</pre>
    </blockquote>
    <p><span style="white-space: pre-wrap">I understand this is the prevailing preference of a certain few, including (but not limited to) yourself and Larry. Nevertheless, classes as a bag of static functions is a phenomenon that exists and will continue to exist in PHP until such a time as `static` is completely removed from the language, so I don't really understand the avoidance of adding, in the interim, what seems like just a missing part of an existing feature.</span></p>
    <p><span style="white-space: pre-wrap">However, I still want to understand why a file of functions is strictly better than a class of functions. What are the benefits of a file over a class?</span></p>
    <p><span style="white-space: pre-wrap">For me, I dislike importing individual functions. It is often the case that, when such logic is so grouped in a static class, where we use one we may use several such functions. In such a case, we only need a single import statement instead of one for each function. This seems like a clear benefit. Even in the case that I only use one, I still prefer to import a class over a function, because it has better support in my editor and doesn't stick out like a sore thumb in the list of imports (why should it?).</span></p>
    <p><span style="white-space: pre-wrap">Cheers,
Bilge
</span></p>
    <p><span style="white-space: pre-wrap">
</span></p>
  </body>
</html>

--------------6pDdC0v0FZtLlH1IP27MBC0s--