I'm no one important, but I just want to say for the sake of the
public image of PHP I hope this does not pass, or at least not in the
foreseeable future.
There are NO substantial gains to speak of here and the BC break is
real and it's super annoying when they pile up and up.
Besides, this is
On Friday, 14 June, 2024 г. at 00:04, Timo Tijhof
wrote:
> Would this affect unserialize()?
>
> I ask because MediaWiki's main "text" database table is an
> immutable/append-only store where we store the text of each page revision
> since ~2004. It is stored as serialised blobs of a value class.
Hi internals
I'm placing my RFC "Add stream open functions to XML{Reader,Writer}" under
voting.
This RFC was previously called "Add openStream() to XML{Reader,Writer}" but
that name became inaccurate during the discussion phase due to changes in the
RFC proposal.
Discussion:
Would this affect unserialize()?
I ask because MediaWiki's main "text" database table is an
immutable/append-only store where we store the text of each page revision
since ~2004. It is stored as serialised blobs of a value class. There have
been a number of different implementations over the past
Hello devs,
is here anyone who has access to https://github.com/Imagick/imagick repo or
direct contact to the maintainer?
We use Imagick in our projects and I would be happy if the latest master can be
released for PHP 8.3 and master adjusted for PHP-8.4/dev.
If there is an interest, I can
Hi Gina
On Thu, Jun 13, 2024 at 3:24 AM Gina P. Banyard wrote:
>
> On Wednesday, 12 June 2024 at 16:06, Ilija Tovilo
> wrote:
>
> > Hi everyone
> >
> > [...]
> >
> > I hope that these semantics are acceptable for everyone.
> >
> > Ilija
>
> Hello Ilija,
>
> I might know what sort of technical
Hi,
There was an RFC about more appropriate date exceptions
https://wiki.php.net/rfc/datetime-exceptions
implemented in
https://github.com/php/php-src/commit/66a1a911f1d6cd4b89c0bb5577fa77f1d6a2cb96
Looking at PHP example, it updated method return types like
- Datetime::modify
-
