Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123797
Precedence: bulk
MIME-Version: 1.0
References: <eb3f59cc-3ed8-461a-a3a4-f6ba10ed31e1@scriptfusion.com>
 <CABigaAWB=X7id9HO+0YcxYy2GH_=N0NfzJyjv+ThuNG=sNUq0w@mail.gmail.com> <942bd631-a7c7-4705-af90-b00a9acf7231@scriptfusion.com>
In-Reply-To: <942bd631-a7c7-4705-af90-b00a9acf7231@scriptfusion.com>
Reply-To: autaut03@gmail.com
Date: Tue, 25 Jun 2024 02:34:07 +0300
Message-ID: <CABigaAU4MKxH4k=C7mGV=Bd3wM1yBApMajkBu0Vftna5Mc=s0Q@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Static class
To: Bilge <bilge@scriptfusion.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005d7c68061bab383b"
From: autaut03@gmail.com (Alex Wells)

--0000000000005d7c68061bab383b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 25, 2024 at 1:56=E2=80=AFAM Bilge <bilge@scriptfusion.com> wrot=
e:

> Hi Alex,
>
> If you wish to implement data objects, what part of the current proposal
> precludes you from doing so?
>
>
 None, but they both try to solve the same problem, so it's highly unlikely
that data objects would ever be considered if this RFC is accepted. And
while static classes fit better with lots of existing PHP code, data
classes (or a similar proposal) would bring more benefit to the table in
the long run, which is why I was hoping for an alternative solution to be
considered and/or discussed. I'm not planning to pursue the data objects
proposal further, but it was still worth mentioning so the internals are
aware of the alternatives to this RFC.

--0000000000005d7c68061bab383b
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 Tue, Jun 25, 2024 at 1:56=E2=80=AF=
AM Bilge &lt;<a href=3D"mailto:bilge@scriptfusion.com">bilge@scriptfusion.c=
om</a>&gt; wrote:</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">
Hi Alex,<br>
<br>
If you wish to implement data objects, what part of the current proposal <b=
r>
precludes you from doing so?<br>
<br></blockquote><div><br></div><div>=C2=A0None, but they both try to solve=
 the same problem, so it&#39;s highly unlikely that data objects would ever=
 be considered if this RFC is accepted. And while static classes fit better=
 with lots of existing PHP code, data classes (or a similar proposal) would=
 bring more benefit to the table in the long run, which is why I was hoping=
 for an alternative solution to be considered and/or discussed. I&#39;m not=
 planning to pursue the data objects proposal further, but it was still wor=
th mentioning so the internals are aware of the alternatives to this RFC.</=
div></div></div>

--0000000000005d7c68061bab383b--