Jakub, what great news!
Congratulations, Kevin!
Bet FrankenPHP will bring the biggest step forward in the modern PHP
projects.
On Tue, May 13, 2025 at 10:45 PM Jakub Zelenka wrote:
> Hello,
>
> The PHP Foundation would like to announce that it has decided to directly
> support the FrankenPHP pr
Hi Larry
On Tue, May 13, 2025 at 3:58 AM Larry Garfield wrote:
>
> I hereby open the vote on the Pipe operator RFC:
>
> https://wiki.php.net/rfc/pipe-operator-v3
It looks like the example under "Rejected Features" is wrong.
// With Elixir style
$foo
|> bar(...)
should be
$foo
|> bar()
Al
Hello,
The PHP Foundation would like to announce that it has decided to directly
support the FrankenPHP project moving forward. The plan is that FrankenPHP
will move to the PHP GitHub organization, which will make it easier for
core contributors and others to be actively involved in the project.
On Tue, May 13, 2025, at 1:41 PM, Levi Morrison wrote:
> On Mon, May 12, 2025 at 8:00 PM Larry Garfield wrote:
>>
>> I hereby open the vote on the Pipe operator RFC:
>>
>> https://wiki.php.net/rfc/pipe-operator-v3
>>
>> The vote will run until 26 May.
>
> Hey, Larry, quick check:
>
>> Supporting p
On Tue, May 13, 2025 at 11:31 AM Deleu wrote:
> Hi!
>
> This would allow public, private and protected classes in a way that I
> believe to be useful for the large ecosystem that surrounds Composer. From
> my extremely limited understanding of the engine, I think the easy/natural
> step would be
On Mon, May 12, 2025 at 8:00 PM Larry Garfield wrote:
>
> I hereby open the vote on the Pipe operator RFC:
>
> https://wiki.php.net/rfc/pipe-operator-v3
>
> The vote will run until 26 May.
Hey, Larry, quick check:
> Supporting pass-by-ref parameters in simple cases is quite easy, and
> a naive i
On Tue, May 13, 2025, 18:35 Deleu wrote:
> Hi!
>
> It's been a few days since I wanted to send this email to internals, but
> real life has been a bit chaotic so I apologize if it comes off as if I
> didn't research the archives enough. I glossed over the Module conversation
> from 10 months ago
Thank you for your work on this.
While I will enjoy this feature if it passes, it irks and saddens me that...
once\again::PHP->has|>added
a.feature.other.languages.only.need.dot.for
That isn't your fault, and any hope of changing that about the language
left the station decades ago.
On Mon, May
Hi!
It's been a few days since I wanted to send this email to internals, but
real life has been a bit chaotic so I apologize if it comes off as if I
didn't research the archives enough. I glossed over the Module conversation
from 10 months ago and the one that recently surfaced and after deeply
th
Hi,
On Tue, May 13, 2025 at 12:56 PM Tim Düsterhus wrote:
> Hi
>
> Am 2025-05-13 12:13, schrieb Jakub Zelenka:
> >> From my experience in maintaining an old PHP application and
> >> upgrading
> >> it to support the latest and greatest PHP every year, I think the
> >> following points would be a
Hi
we just opened the vote for the "Throwable Hierarchy Policy for
Extensions" policy RFC:
RFC: https://wiki.php.net/rfc/extension_exceptions
Discussion: https://externals.io/message/127206
PR: https://github.com/php/policies/pull/17
As with every RFC, a 2/3 majority is required. Voting ends
Hi
Am 2025-05-13 12:13, schrieb Jakub Zelenka:
From my experience in maintaining an old PHP application and
upgrading
it to support the latest and greatest PHP every year, I think the
following points would be a good starting point to discuss:
- For backwards compatibility breaks introduced i
Hi,
On Sun, May 11, 2025 at 10:14 PM Tim Düsterhus wrote:
> Hi
>
> I gave this some additional thoughts.
>
> Am 2025-05-09 13:36, schrieb Jakub Zelenka:
> >> - A minor version MUST NOT break syntax compatibility (i.e. every PHP
> >> program that compiles must continue to compile).
> >>
> >
> > A
13 matches
Mail list logo
