Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121968
MIME-Version: 1.0
References: <8f4e3274-6489-4378-82db-fb4829770196@gmail.com>
 <CA+XhMqz3Or4+XPWUJne0uS8gS6=GcsY+HNbCPBDTuCpGjx8+Bw@mail.gmail.com> <a5ddd5fa-ab5f-4e77-802e-8cab54387dd0@gmail.com>
In-Reply-To: <a5ddd5fa-ab5f-4e77-802e-8cab54387dd0@gmail.com>
Date: Sat, 9 Dec 2023 09:40:10 +0000
Message-ID: <CA+XhMqwq449MQUKVs2AJWi1zPSU_T9-qVnp_Y1SNFO8t5iuddA@mail.gmail.com>
To: Niels Dossche <dossche.niels@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005a4161060c107d8f"
Subject: Re: [PHP-DEV] Filesystem path APIs
From: devnexen@gmail.com (David CARLIER)

--0000000000005a4161060c107d8f
Content-Type: text/plain; charset="UTF-8"

On Fri, 8 Dec 2023 at 16:10, Niels Dossche <dossche.niels@gmail.com> wrote:

> Hi David
>
> On 08/12/2023 10:08, David CARLIER wrote:
> >     I think these would be great additions to PHP as working with paths
> and files is a core part of any programming language.
> >
> >
> > Seems like it, is there an argument to be made to, let's say, in the
> performance side ?
>
> A native implementation is going to be faster than an implementation in
> userspace.
> However, I don't think that matters because the performance is likely
> dominated by the I/O you do after constructing a path.
> You'd need to construct a large number of paths before you notice anything
> I guess.
>
> Cheers
> Niels
>

Very true, so what would be the argument beside having those as "builtins"
as opposed to external components ?

--0000000000005a4161060c107d8f--