The PHP development team announces the immediate availability of PHP
8.1.28. This is a security release that addresses CVE-2024-1874,
CVE-2024-2756 and CVE-2024-3096.
All PHP 8.1 users are encouraged to upgrade to this version.
For source downloads of PHP 8.1.28 please visit our downloads page.
On Fri, Apr 12, 2024, at 2:55 AM, Juliette Reinders Folmer wrote:
> The first part of my email (up to the "Furthermore") was mostly me
> trying to summarize the complexity of the proposal and to compare it to
> existing syntaxes and list those things which - to me - appeared
> inconsistent
Hi Gina,
> This isn't a BC Break in theory as class names are, for the time being,
> case-insensitive.
Strictly speaking, this can be considered a BC Break because the string
returned by `::class` changes.
However, I'm not sure how much of an impact it will have.
Regards,
Saki
On 10 April 2024 04:40:13 BST, Juliette Reinders Folmer
wrote:
* Whether a type can be specified on the parameter on `set` depends on whether
the property is typed. You cannot declare `set(mixed $value)` for an untyped
property, even though it would effectively be compatible. This is
On Friday, 5 April 2024 at 18:00, Tim Düsterhus wrote:
> Hi
>
> I've just written up the follow-up RFC to my previous “Casing of
> acronyms in class and method names” thread and I'm officially opening up
> the discussion period for it.
>
> Please find the following links for your convenience:
Hi
Le jeu. 4 avr. 2024 à 07:41, youkidearitai a
écrit :
> 2024年4月4日(木) 6:30 Tim Düsterhus :
> >
> > Hi
> >
> > On 4/3/24 10:02, youkidearitai wrote:
> > > Therefore, I think require an RFC, I have written a draft an RFC that
> > > fixes these issues.
> > >
Hi,
On 12.04.24 04:55, Juliette Reinders Folmer wrote:
Hi Ilija,
On 12-4-2024 1:00, Ilija Tovilo wrote:
Oh, and hang on, they *can* be read from a method in the same class as long as
that method is called from within the set hook, so now the method will need to
either do a backtrace or
