Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123984
Precedence: bulk
MIME-Version: 1.0
References: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
 <CANLbj-qvn-BFfN8hEQRciUuT_qCiiPfyqc=YiL1Pw5+Oy-Ad4Q@mail.gmail.com>
 <554ffb9e-35c5-466e-aace-0501eee3d0bd@bastelstu.be> <6452BECC-BB20-48DC-9595-324EA70E6A67@newclarity.net>
In-Reply-To: <6452BECC-BB20-48DC-9595-324EA70E6A67@newclarity.net>
Date: Fri, 28 Jun 2024 09:05:28 +0200
Message-ID: <CANS-=pd2+aJbNiLBb9pS-m5JHATGOJKsAMN05nUDkbrPdDwYyQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Static class
To: Mike Schinkel <mike@newclarity.net>
Cc: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>, 
	Bilge <bilge@scriptfusion.com>, php internals <internals@lists.php.net>, lnearwaju@gmail.com
Content-Type: multipart/alternative; boundary="000000000000f12658061bede0d0"
From: kjarli@gmail.com (Lynn)

--000000000000f12658061bede0d0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 28, 2024 at 2:48=E2=80=AFAM Mike Schinkel <mike@newclarity.net>=
 wrote:

> >> and inheritance is not meant for code reuse.
>
> Just because code reuse in inheritance can be problematic it does not hav=
e
> to be in all-cases. Moderation in all things. I used that approach for 10=
+
> years and never once had any of the problems people claim about using
> inheritance for code reuse. This was likely because my needs were
> constrained by the use-case and by nature did not grow out of control wit=
h
> complexity.
>

My experience is the opposite. There are subtle bugs I keep running into
with static function and properties causing unexpected behavior. I'm not
against having static classes open by default for the sake of consistency,
though my preference would be to avoid the headache altogether and just
make them final by default so I won't ever have to deal with it. Would
traits not solve the problem of horizontal reuse?

--000000000000f12658061bede0d0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jun 28, 2024 at 2:48=E2=80=AF=
AM Mike Schinkel &lt;<a href=3D"mailto:mike@newclarity.net">mike@newclarity=
.net</a>&gt; wrote:</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">
&gt;&gt; and inheritance is not meant for code reuse.<br>
<br>
Just because code reuse in inheritance can be problematic it does not have =
to be in all-cases. Moderation in all things. I used that approach for 10+ =
years and never once had any of the problems people claim about using inher=
itance for code reuse. This was likely because my needs were constrained by=
 the use-case and by nature did not grow out of control with complexity.<br=
></blockquote><div><br></div><div>My experience is the opposite. There are =
subtle bugs I keep running into with static function and properties causing=
 unexpected behavior. I&#39;m not against having static classes open by def=
ault for the=C2=A0sake of consistency, though my preference would be to avo=
id the headache altogether and just make them final by default so I won&#39=
;t ever have to deal with it. Would traits not solve the=C2=A0problem of ho=
rizontal=C2=A0reuse?</div></div></div>

--000000000000f12658061bede0d0--