Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129543
Precedence: list
MIME-Version: 1.0
Date: Thu, 04 Dec 2025 10:55:00 +0100
To: Henrik Skov <henry.wood.dk@gmail.com>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] My wish for PHP 9
In-Reply-To: <b536c6ee-2553-4c2e-a80d-2d7015356008@gmail.com>
References: <b536c6ee-2553-4c2e-a80d-2d7015356008@gmail.com>
Message-ID: <4618f8efefdd9e075ca729395fcac201@bastelstu.be>
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 Henrik

Am 2025-12-02 14:51, schrieb Henrik Skov:
> As mostly just a bystander, I just wanted to say that all your work 
> makes me very excited for the future of PHP !
> 
> What I hope will make it into PHP 9:
> 
> - Pattern matching
> - Poll API
> - TrueSync
> - ext/uri
> 
> Keep up all the good work !

Thank you for your friendly message. Most of the features that you 
listed don't need to wait for PHP 9, since they can be integrated into a 
backwards compatible way, for example by adding new functions rather 
than modifying them (such as ext/uri, which already shipped with PHP 
8.5) did.

The biggest and most complicated part of doing RFCs is figuring out all 
the details and edge cases to make sure a new feature integrates nicely 
into PHP. For more complex topics there often is more than one possible 
way of doing things, with different folks having different preferences, 
requirements or example use cases that can help understand the problem 
better to find the best possible solution.

This - very important - part of the process is open to anyone, so if you 
have anything useful to add to the discussion, even if it's just some 
anecdote based on your experience that explains why the RFC is important 
or helpful to you, you are welcome to participate in the discussion. 
There is only one important rule on this list that many newcomers often 
are not familiar with and that is “please don't top post”. This means 
that you should reply to the email you want to reply to and then add 
your message *below* (or inline with) the quoted text you are replying 
to, ideally cutting the quoted text to the minimal bits that still 
provide the necessary context. Just like I did in this reply to you.

Best regards
Tim Düsterhus