Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79710
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <54900F01.2080309@beccati.com>
Date: Tue, 16 Dec 2014 11:03:16 +0000
Cc: Xinchen Hui <laruence@php.net>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <24343159-F6CC-4C11-AD8B-CFB608A87339@ajf.me>
References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me> <CABBJUpfLCjWCgOUneN2O2M7qP2WBf8OgbVrdB-jm+Fn_dDJvVA@mail.gmail.com> <548FE4A8.4040909@beccati.com> <6879A58C-458B-459D-97D3-1A73663E1A0E@ajf.me> <54900F01.2080309@beccati.com>
To: Matteo Beccati <php@beccati.com>
Subject: Re: [PHP-DEV] [RFC] PHP 5.7
From: ajf@ajf.me (Andrea Faulds)

Hey Matteo,

> On 16 Dec 2014, at 10:52, Matteo Beccati <php@beccati.com> wrote:
>=20
> On 16/12/2014 08:55, Andrea Faulds wrote:
>> Could you tell me which RFCs targeted 5.7 and didn=E2=80=99t just add =
deprecation notices? I=E2=80=99m unaware of any.
>=20
> I've tried to search the ML for such list of RFCs:
>=20
> https://wiki.php.net/rfc/gc_fn_pointer
> https://wiki.php.net/rfc/secure_unserialize (also 5.6 if RMs agree)
> https://wiki.php.net/rfc/closure_apply
> https://wiki.php.net/rfc/pack_unpack_64bit_formats (targeting 5.6)
> https://wiki.php.net/rfc/intdiv
> https://wiki.php.net/rfc/session.user.return-value
>=20
> maybe others too, but I got bored ;)

I wrote the Closure::call() and intdiv() RFCs. Truth be told, they both =
targeted master, not a specific PHP version. master has become PHP 7, so =
whatever the wording of them said, they really target PHP 7 now. They =
were written back before the whole PHP 7/phpng thing when I didn=E2=80=99t=
 know whether we were going to go straight to PHP 7 or whether there=E2=80=
=99d be another minor and then PHP 7 a year or two after. Now we=E2=80=99r=
e going straight to PHP 7 - the 5.7 proposed wouldn=E2=80=99t be an =
exception to that, as 5.7 would have no new features and be released =
around the same time. It=E2=80=99s not, well, the 5.7 I had in mind when =
I wrote those RFCs.

Filtered unserialize() and 64-bit pack/unpack targeted 5.6 micro =
releases, not 5.7.

I don=E2=80=99t really know about the session handling and GC ones.
--
Andrea Faulds
http://ajf.me/