Fwd: [PHP-DEV] Oniguruma maintenance was ended on 2025-04-24

2025-04-29 Thread David CARLIER
-- Forwarded message - From: David CARLIER Date: Wed, 30 Apr 2025 at 06:20 Subject: Re: [PHP-DEV] Oniguruma maintenance was ended on 2025-04-24 To: youkidearitai Hi youkidearitai. I would be in favor on moving to *whatever *viable solution in the long run appears (e.g. being at

[PHP-DEV] Oniguruma maintenance was ended on 2025-04-24

2025-04-29 Thread youkidearitai
Hi, Internals Oniguruma(鬼車) maintenance was ended on April 24, 2025. https://github.com/kkos/oniguruma This library uses mbregex in php-src. There is forked library in Onigumo(鬼雲). https://github.com/k-takata/Onigmo How do we do that? - Move to Onigumo - Stay in Oniguruma - Deprecate mbregex fun

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-04-29 Thread ignace nyamagana butera
Hi Paul, I will try to address your concerns. Keep in mind that I am not the author of the RFC but I do like how it is currently shaped with some caveats but those can be put under future improvements. > So, one value added by splitting the classes is to resolve that asymmetry. First, I agree wi

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-04-29 Thread Tim Düsterhus
Hi On 4/29/25 10:54, ignace nyamagana butera wrote: I have one last question while reviewing my polyfill implementation. Is it worth it adding a SensitiveParameter attribute on the argument of the following methods ? - Uri\Rfc3986\Uri::withUserInfo - Uri\WhatWg\Url::withPassword I'm fine with

Re: [PHP-DEV] Re: RFC: Nested Classes

2025-04-29 Thread Tim Düsterhus
Hi On 4/24/25 21:26, Rob Landers wrote: This was very deliberate after much feedback and careful design. People were quite clear (including yourself, if I recall) that they didn't want a new syntax. Since there is no new syntax, there is no way to tell (from the outside) whether A\B\C refers

Re: [PHP-DEV] Concept: Lightweight error channels

2025-04-29 Thread Paul M. Jones
> On Apr 27, 2025, at 07:26, Niels Dossche wrote: > > Regarding performance however, rather than introducing yet another completely > new concept to do almost the same thing, why not try to improve exception > performance instead? > > I just opened a PR that makes instantiating exceptions m

Re: [PHP-DEV] Concept: Lightweight error channels

2025-04-29 Thread Matthew Weier O'Phinney
On Tue, Apr 29, 2025 at 9:09 AM Hammed Ajao wrote: > On Mon, Apr 28, 2025, 1:22 p.m. Larry Garfield > wrote: > >> On Mon, Apr 28, 2025, at 11:28 AM, Edmond Dantes wrote: >> >> I have already demonstrated how it can be solved without generics. >> Multiple response channels from a function alread

Re: [PHP-DEV] Concept: Lightweight error channels

2025-04-29 Thread Hammed Ajao
On Mon, Apr 28, 2025, 1:22 p.m. Larry Garfield wrote: > On Mon, Apr 28, 2025, at 11:28 AM, Edmond Dantes wrote: > >> I have already demonstrated how it can be solved without generics. > Multiple response channels from a function already exist: Normal returns > and exceptions. Exceptions as curr

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-04-29 Thread Paul M. Jones
Hi Ignace & Maté and all, tl;dr: I argue against Ignace's objections to splitting the URI class into two classes (one that retains raw URI values and another that normalizes values as-it-goes). Jump to the very end for a discussion regarding the with() methods (search for the word "asymmetry" h

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-04-29 Thread ignace nyamagana butera
Hi Maté and Time, I have one last question while reviewing my polyfill implementation. Is it worth it adding a SensitiveParameter attribute on the argument of the following methods ? - Uri\Rfc3986\Uri::withUserInfo - Uri\WhatWg\Url::withPassword I'm fine with any answer ? Does it warrant a parag