Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124401
Precedence: bulk
MIME-Version: 1.0
References: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
 <ef0c3617-6757-45a1-a485-3f7c197fd599@app.fastmail.com> <4596aa73-cfd4-2292-7191-2839a5bab695@php.net>
 <132b86de-f571-4611-8b9b-35ae107901f0@scriptfusion.com>
In-Reply-To: <132b86de-f571-4611-8b9b-35ae107901f0@scriptfusion.com>
Date: Thu, 11 Jul 2024 21:13:53 -0600
Message-ID: <CAM7F2-_KZEEQhhq2hkB_XyN8stpJBA6DyeiEjBzNtZ6E3E3gKw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Static class
To: Bilge <bilge@scriptfusion.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000090bb3b061d04459d"
From: lnearwaju@gmail.com (Lanre)

--00000000000090bb3b061d04459d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 11, 2024 at 6:16=E2=80=AFPM Bilge <bilge@scriptfusion.com> wrot=
e:

> 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.
>
> cheers,
> Derick
>
> Can someone clue me in as to why grouping related functions in a file wit=
h
> nothing but a namespace is strictly better than those same related
> functions grouped as members of a class? It doesn't have to be Larry or
> Derick, because even though they have expressed this view, I am aware the=
y
> are not the only ones whom hold it. Anyone who can shed some light on thi=
s
> perspective is welcome to comment.
>
> Cheers,
> Bilge
>

It isn't implicitly better, but if PHP had proper support for autoloading
functions, I would at least consider them equivalent when all the
functions/methods are public.

My primary language is C++, where the distinction is even blurrier since
both static class members and namespace members are accessed with '::'. For
example, X::Y() could be a namespaced function or a static method, and it
doesn't actually matter which it is under the hood since they are
functionally identical.

In PHP, however, putting all your functions in a namespace is less
performant than using static classes. For instance, if you have ten
functions.php files each for a separate namespace, Composer will load all
ten for every single request, regardless of whether they are used.
Additionally, if you install a Composer package that registers some
functions, those will also be loaded for every request.

Cheers,

Lanre

--00000000000090bb3b061d04459d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 11, 2024 at 6:16=E2=80=AFPM B=
ilge &lt;<a href=3D"mailto:bilge@scriptfusion.com">bilge@scriptfusion.com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u=
></u>

 =20
   =20
 =20
  <div>
    <div>On 25/06/2024 16:17, Derick Rethans
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <pre><span style=3D"white-space:pre-wrap">we shouldn&#39;t be encoura=
ging static classes as </span>a bag of static functions, that ought to be j=
ust namespaced functions.

cheers,
Derick
</pre>
    </blockquote>
    <p>Can someone clue me in as to why grouping related functions in a
      file with nothing but a namespace is strictly better than those
      same related functions grouped as members of a class? It doesn&#39;t
      have to be Larry or Derick, because even though they have
      expressed this view, I am aware they are not the only ones whom
      hold it. Anyone who can shed some light on this perspective is
      welcome to comment.</p>
    <p>Cheers,<br>
      Bilge<br></p></div></blockquote><div><br></div><div><p>It isn&#39;t i=
mplicitly better, but if PHP had proper support for autoloading functions, =
I would at least consider them equivalent when all the functions/methods ar=
e public.</p><p>My primary language is C++, where the distinction is even b=
lurrier since both static class members and namespace members are accessed =
with &#39;::&#39;. For example, <code>X::Y()</code> could be a namespaced f=
unction or a static method, and it doesn&#39;t actually matter which it is =
under the hood since they are functionally identical.</p><p>In PHP, however=
, putting all your functions in a namespace is less performant than using s=
tatic classes. For instance, if you have ten <code>functions.php</code> fil=
es each for a separate namespace, Composer will load all ten for every sing=
le request, regardless of whether they are used. Additionally, if you insta=
ll a Composer package that registers some functions, those will also be loa=
ded for every request.</p><p>Cheers,</p><p>Lanre</p></div></div></div>

--00000000000090bb3b061d04459d--