Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120332
MIME-Version: 1.0
References: <4ECF6970-2A01-4C47-9B41-87D534F54CB8@shyim.de>
 <CAMjSS5Nsq6uo=yagS+XmstqU3a4Tah-_Bc6G1KwZbzMuO8z3hw@mail.gmail.com> <CAPKYkKyvyGP7ybPbzuc4M=PyawBR5QxQ_YiNObWO7stn1ehbyg@mail.gmail.com>
In-Reply-To: <CAPKYkKyvyGP7ybPbzuc4M=PyawBR5QxQ_YiNObWO7stn1ehbyg@mail.gmail.com>
Date: Wed, 17 May 2023 22:52:38 +0100
Message-ID: <CA+p1Fab6fC5Q3_=evnc5KX31n=97cGgF8VpN7dnQ+t2O_Tuxmg@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000007ebcd805fbeab53f"
Subject: Re: [PHP-DEV] [RFC] path_join function
From: davidgebler@gmail.com (David Gebler)

--0000000000007ebcd805fbeab53f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, May 17, 2023 at 4:31=E2=80=AFPM Chase Peeler <chasepeeler@gmail.com=
> wrote:

> Definitely a useful feature, but not sure it needs to be a core function.
>
>
I feel the same. There are countless useful utility functions which could
exist in core, many of which are even widely used and commonly reinvented
as userland functions, Many would also seem at least prima facie to be
complementary to existing functions which are in core. But my understanding
of the usual convention is that "lots of people would have a use for it"
isn't enough where no significant further justification or benefit can be
provided for introducing a new core function.

On a wider philosophy on the future of the language, I'd be more inclined
to support changes like this which went the extra mile and introduced new,
complete object classes to group related core functionality and slowly
deprecate the enormous stock library of the global function namespace,
which feels random enough as it is.

-Dave

--0000000000007ebcd805fbeab53f--