Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79725
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <548FFA9A.9080404@gmail.com>
References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me>
	<548FFA9A.9080404@gmail.com>
Date: Tue, 16 Dec 2014 17:10:33 +0100
Message-ID: <CAH-PCH75NvghaPyHct5kZEO=dmac2Vg9cNYUq1qE-fc-cGO2xg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Andrea Faulds <ajf@ajf.me>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013d1a6444a20b050a5799c9
Subject: Re: [PHP-DEV] [RFC] PHP 5.7
From: tyra3l@gmail.com (Ferenc Kovacs)

--089e013d1a6444a20b050a5799c9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 16, 2014 at 10:25 AM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:
>
> Hi!
>
> > There has been some debate about whether to make =E2=80=9CPHP 5.7". I h=
ave
> > made a very simple RFC. It proposes a final minor version of PHP 5,
> > PHP 5.7, to be released at the same time as PHP 7, with no new
> > features whatsoever.
> >
> > The hope is that we can put this to a vote in 2 weeks=E2=80=99 time and
> > settle the matter, just as we did with the PHP 6/7 name vote,
> > although perhaps slightly less messily this time. ;)
>
> It'd be nice to describe what we have now for 5.7 - i.e. which
> deprecation messages and other warnings are on the agenda? Doesn't have
> to be the exclusive list but at least to give the idea what we're
> talking about.
>

Just an initial list, feel free to extend it:

   - we could add an E_DEPRECATED for zpp overflow:
   https://wiki.php.net/rfc/zpp_fail_on_overflow
   - if we could trigger E_DEPRECATED for function foo($x,$x) {} which is
   now a compile error thanks to https://wiki.php.net/phpng that would be
   nice
   - if we could cover some of the BC breaks with E_DEPRECATED from
   https://wiki.php.net/rfc/uniform_variable_syntax#backward_incompatible_c=
hanges
   that would be nice, but not sure if feasible.
   - if we could trigger E_DEPRECATED for list()-ing a string which will be
   removed in 7.0(https://wiki.php.net/rfc/fix_list_behavior_inconsistency)
   that would be nice.
   - E_DEPRECATED for the alternative php tags which will be removed with
   7.0(https://wiki.php.net/rfc/remove_alternative_php_tags).
   - merge https://github.com/php/php-src/pull/807 for adding E_DEPRECATED
   for multiple default labels in switch.
   - maybe we could add an E_DEPRECATED for
   https://wiki.php.net/rfc/session.user.return-value to notify authors of
   custom session handlers(
   https://wiki.php.net/rfc/session.user.return-value)
      - please note that the vote for this change was in favour for
      changing it in 5.7, so if we don't overrule the decision, we
don't add the
      deprecated message, but the BC break instead.


--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--089e013d1a6444a20b050a5799c9--