Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124289
Precedence: bulk
MIME-Version: 1.0
References: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
 <f3e738cd-dd9b-490e-a1f1-a1227cb696d2@scriptfusion.com> <D76AE2E1-E75F-41DF-844E-963613F4EC0D@newclarity.net>
 <743774dd-2281-458d-b0fa-d3e8806a3516@scriptfusion.com> <3B6AF286-642C-4850-9577-B10049CE4C1E@koalephant.com>
 <CAAwdEzBVEqtMxbinycBHp5Hg-spywHGzPcRpttBnDyV-sy+SuQ@mail.gmail.com> <30320e4c-aa99-4fb6-b475-d21f5fe85a26@scriptfusion.com>
In-Reply-To: <30320e4c-aa99-4fb6-b475-d21f5fe85a26@scriptfusion.com>
Date: Mon, 8 Jul 2024 17:13:29 +0300
Message-ID: <CAAwdEzDTFJg9ruqKmnU9Y2MNfxgq3G07k_pUpaJa1Brm8D2fuQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Static class
To: Bilge <bilge@scriptfusion.com>
Cc: Stephen Reay <php-lists@koalephant.com>, Mike Schinkel <mike@newclarity.net>, 
	php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000887de6061cbd0555"
From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=)

--000000000000887de6061cbd0555
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 8, 2024 at 3:22=E2=80=AFPM Bilge <bilge@scriptfusion.com> wrote=
:

> On 08/07/2024 12:48, Alexandru P=C4=83tr=C4=83nescu wrote:
>
>
> If we support inheritance for static classes, we should allow static on
> both interface and abstract classes.
>
> What do you mean by *allow static on [...] interface*? Are you saying you
> also expect to see `static interface` support? (This is something I am
> absolutely not considering at this time, without a very good argument in
> favour of).
>
>
> For completeness, if we think that the static keyword on a class-level
entity means that it will allow only static members on that entity, all
class-level entities should be able to be marked as "static".:
Yes, it might not be really required, but I can see how it would help
define a static interface that can only be implemented by a static class.

Reading on :
> A static class only permits extending a parent class that is also marked
static. A non-static class cannot extend a static class.

The wording is a bit confusing for me.
But I understand that once a class is static, all the chain of inheritance
should be made of static classes, going up or down (and I would also think
we can add interfaces and traits.).
If interfaces are not included, do we allow implementing an interface? If
we allow implementing an interface, should that interface contain only
static members? Same for traits.

Alex

--000000000000887de6061cbd0555
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 8, 2024 at 3:22=E2=80=AFPM Bi=
lge &lt;<a href=3D"mailto:bilge@scriptfusion.com">bilge@scriptfusion.com</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u>=
</u>

 =20
   =20
 =20
  <div>
    <div>On 08/07/2024 12:48, Alexandru
      P=C4=83tr=C4=83nescu wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr"><br></div></div></blockquote><blockquote type=3D"c=
ite"><div dir=3D"ltr"><div class=3D"gmail_quote">
          <div>If we support inheritance for static classes, we should
            allow static on both interface and abstract classes.<br>
          </div>
          <div><br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>What do you mean by <i>allow static on [...] interface</i>? Are
      you saying you also expect to see `static interface` support?
      (This is something I am absolutely not considering at this time,
      without a very good argument in favour of).</p>
    <p><br></p></div></blockquote><div>For completeness, if we think that t=
he static keyword on a class-level entity means that it will allow only sta=
tic members on that entity, all class-level entities should be able to be m=
arked as &quot;static&quot;.:</div><div>Yes, it might not be really require=
d, but I can see how it would help define a static interface that can only =
be implemented by a static class.<br></div><div><br></div><div>Reading on :=
</div><div>&gt;=C2=A0A static class only permits extending a parent class t=
hat is also marked static. A non-static class cannot extend a static class.=
</div><div><br></div><div>The wording is a bit confusing for me.</div><div>=
But I understand that once a class is static, all the chain of inheritance =
should be made of static classes, going up or down (and I would also think =
we can add interfaces=C2=A0and traits.).</div><div>If interfaces are not in=
cluded, do we allow implementing an interface? If we allow implementing an =
interface, should that interface contain only static members? Same for trai=
ts.</div><div><br></div><div>Alex</div></div></div>

--000000000000887de6061cbd0555--