Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126976
Message-ID: <b218076d-b686-476f-9bb4-af185f309f1b@bastelstu.be>
Date: Sun, 30 Mar 2025 13:12:09 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: "Gina P. Banyard" <internals@gpb.moe>,
 PHP Internals List <internals@lists.php.net>
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
 <RYUX5rSGApW8lPGs1yovM2fIXXBHd_UcqEKAKgj8-dRrpThS4tC195Jb3kPTT5up96r7SZ2WunauAblAIEkZe41BwZxLeSE2SaKQLAYSmZo=@gpb.moe>
 <17bdbfa35c920a86a19690e356e05f99@bastelstu.be>
 <CAH5C8xWCR9tcTS_g+7hc7kR8r4W3DCLeGoQv6cgm3sm6kv=Kvw@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAH5C8xWCR9tcTS_g+7hc7kR8r4W3DCLeGoQv6cgm3sm6kv=Kvw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 3/12/25 23:00, Máté Kocsis wrote:
> I'm not sure if I'm entirely correct, but it's possible that a 3rd party
> URI implementation
> won't (or cannot) use PHP's memory manager, and it relies on the regular
> malloc:
> in this case, even memory errors could lead to failures.

We already discussed this in private and the UriOperationException was 
removed from the RFC, but for public record:

Something like a memory allocation error is not actionable by the user. 
Thus it should be an `Error` (rather than an exception) or a bail out. 
Perhaps the engine will one day support gracefully handling the memory 
limit being exceeded with an OutOfMemoryError being thrown in that 
situation. Then it would also fit nicely for any URI implementation.

Best regards
Tim Düsterhus