Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125820
Precedence: bulk
MIME-Version: 1.0
References: <ZydAaayECTRNG8Ackhb0tDgYjmdFKnkW4p0ISWlLFP5My4CsJBR1KKTylrD14Ags2GUyBLoJPf68N6Z6LoVzjG-tru8YAbmi74W5xzSkJ8I=@gpb.moe>
 <20340e0e-ddd0-44cd-b555-1402857eb20f@app.fastmail.com> <CANNiG7i1mOpXnZGuh6GZBobKnABQYCvzBd1++EOyA8=JRNR6Mw@mail.gmail.com>
 <CAPyj-LBCYXjwcWv8tRwfN+zCM=hwABdiqhRzMcppubASjaM_eA@mail.gmail.com>
 <AM8P250MB01702D66B6FCC3300902654DE2422@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <352272ef-55f4-41a5-a083-5ab933adf4e5@app.fastmail.com>
In-Reply-To: <352272ef-55f4-41a5-a083-5ab933adf4e5@app.fastmail.com>
Date: Mon, 21 Oct 2024 18:04:23 +1000
Message-ID: <CAKVXxD_z1PGmgtSLkdXmau+BPEmHLtGQoMm0uF0pWgV+pe-TjQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Change behaviour of array sort functions to
 return a copy of the sorted array
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000080a8940624f81a91"
From: mickmackusa@gmail.com (mickmackusa)

--00000000000080a8940624f81a91
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 21, 2024 at 3:24=E2=80=AFPM Larry Garfield <larry@garfieldtech.=
com>
wrote:

> I am confused by this statement.  How is "adding more functions that do
> exactly what they say on the tin and act in a predictable fashion" bad?
> It's not like we're running out of space for functions.  Small,
> purpose-built, highly-predictable APIs that fully address a problem space
> are the ideal goal; the number of them is largely irrelevant.
>
> I wouldn't mind array_sorted() instead of sorted(), since it wouldn't wor=
k
> on iterables.  But array_sort() vs sort() is just horribly confusing for =
no
> good reason, and the API itself does nothing to tell you which is which.
>
> --Larry Garfield
>

Couldn't it be said that prefixing native array functions with "array_" and
not adding "ed"  to the middle (e.g. array_walked_recursive) or end of
native functions is moving toward naming convention normalcy?
Does PHP have any "ed" functions?
Having separate array_*() and *() functions offers a path to the possible
future decision to cull the *() functions and/or remove the
modify-by-reference behaviour of array_*() functions ...if that is ever
desirable.
I see this naming distinction as a stepping stone to a more consistent
naming convention rather than the final solution.
(Just like defining the function alias preg_escape() as a pathway to
removing preg_quote() -- which is a function that doesn't do what it says
on the tin.)

Mick

--00000000000080a8940624f81a91
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 Mon, Oct 21, 2024 at 3:24=E2=80=AF=
PM Larry Garfield &lt;<a href=3D"mailto:larry@garfieldtech.com" target=3D"_=
blank">larry@garfieldtech.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">I am confused by this statement.=C2=A0 How is =
&quot;adding more functions that do exactly what they say on the tin and ac=
t in a predictable fashion&quot; bad?=C2=A0 It&#39;s not like we&#39;re run=
ning out of space for functions.=C2=A0 Small, purpose-built, highly-predict=
able APIs that fully address a problem space are the ideal goal; the number=
 of them is largely irrelevant.<br>
<br>
I wouldn&#39;t mind array_sorted() instead of sorted(), since it wouldn&#39=
;t work on iterables.=C2=A0 But array_sort() vs sort() is just horribly con=
fusing for no good reason, and the API itself does nothing to tell you whic=
h is which.<br>
<br>
--Larry Garfield<br></blockquote><div><br>Couldn&#39;t it be said that pref=
ixing native array functions with &quot;array_&quot; and not adding &quot;e=
d&quot;=C2=A0 to the middle (e.g. array_walked_recursive) or end of native =
functions is moving toward naming convention normalcy?</div><div>Does PHP h=
ave any &quot;ed&quot; functions?</div><div>Having separate array_*() and *=
() functions offers a path to the possible future decision to cull the *() =
functions and/or remove the modify-by-reference behaviour of array_*() func=
tions ...if that is ever desirable.</div><div>I see this naming distinction=
 as a stepping stone to a more consistent naming convention rather than the=
 final solution.</div><div>(Just like defining the function alias preg_esca=
pe() as a pathway to removing preg_quote() -- which is a function that does=
n&#39;t do what it says on the tin.)</div><div><br></div><div>Mick</div></d=
iv></div>

--00000000000080a8940624f81a91--