Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123992
Message-ID: <4148946E-7D16-46F8-8B88-9C7C5D61D129@koalephant.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_B115DD9C-B5F6-42CD-ABA4-A9F56AF56900"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: [PHP-DEV] [RFC] Static class
Date: Sat, 29 Jun 2024 01:04:12 +0700
In-Reply-To: <CANS-=pd2+aJbNiLBb9pS-m5JHATGOJKsAMN05nUDkbrPdDwYyQ@mail.gmail.com>
Cc: Mike Schinkel <mike@newclarity.net>,
 =?utf-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>,
 Bilge <bilge@scriptfusion.com>,
 php internals <internals@lists.php.net>,
 lnearwaju@gmail.com
To: Lynn <kjarli@gmail.com>
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>
 <CANS-=pd2+aJbNiLBb9pS-m5JHATGOJKsAMN05nUDkbrPdDwYyQ@mail.gmail.com>
From: php-lists@koalephant.com (Stephen Reay)


--Apple-Mail=_B115DD9C-B5F6-42CD-ABA4-A9F56AF56900
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 28 Jun 2024, at 14:05, Lynn <kjarli@gmail.com> wrote:
>=20
>=20
>=20
> On Fri, Jun 28, 2024 at 2:48=E2=80=AFAM Mike Schinkel =
<mike@newclarity.net <mailto:mike@newclarity.net>> wrote:
>> >> and inheritance is not meant for code reuse.
>>=20
>> 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 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 =
with complexity.
>=20
> 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?

Hi Lynn,

I understand it's frustrating when there are bugs/unexpected behaviour, =
but wouldn't the (existing) *ability* to add the `final` keyword to a =
class solve those issues for you, without preventing others from using =
the capabilities of parent/child class relationships?


Cheers


Stephen=20=

--Apple-Mail=_B115DD9C-B5F6-42CD-ABA4-A9F56AF56900
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><br =
id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>On 28 Jun 2024, at 14:05, Lynn =
&lt;kjarli@gmail.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><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=AFAM 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 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 =
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'm not against =
having static classes open by default for the&nbsp;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&nbsp;problem of =
horizontal&nbsp;reuse?</div></div></div>
</div></blockquote></div><br><div>Hi Lynn,</div><div><br></div><div>I =
understand it's frustrating when there are bugs/unexpected behaviour, =
but wouldn't the (existing) *ability* to add the `final` keyword to a =
class solve those issues for you, without preventing others from using =
the capabilities of parent/child class =
relationships?</div><div><br></div><div><br></div><div>Cheers</div><div><b=
r></div><div><br></div><div>Stephen&nbsp;</div></body></html>=

--Apple-Mail=_B115DD9C-B5F6-42CD-ABA4-A9F56AF56900--