Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99435
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain pmmaga.net designates 149.210.149.69 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50D8C5E2-DCD3-455C-9FF6-FEDD5723FBE6@gmail.com>
References: <CAJd4=YaMDkocahDE0muQNPYW=vgR_nffJD-CBKic7CnbFPwyyw@mail.gmail.com>
 <eadc5bea-3412-9c9b-faa9-e74b442a6b84@gmx.de> <7028fcfd-d47f-c983-510d-eefe4a36cd4a@tekwire.net>
 <CA+kxMuQ7LtWgpOnXGQf5rMw09TE3+DatkTYwM70PgGEkk4hc_Q@mail.gmail.com>
 <B8A7972A-093E-4D45-8796-8D1D276F7981@gmail.com> <CAJd4=YbBeaYWC2aUtXHA0r5TprmjKLy7-TB3C7g-fPCgvo4S4Q@mail.gmail.com>
 <50D8C5E2-DCD3-455C-9FF6-FEDD5723FBE6@gmail.com>
Date: Wed, 7 Jun 2017 18:36:01 +0200
Message-ID: <CAJd4=YYW4NZsmBgFsrG7Ux8YJ138dYNk769Y_iYKANQ_CiKExw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a11471eb21caed9055161566e"
Subject: Re: [PHP-DEV] Re: [RFC] [VOTE] Arrays starting with a negative index
From: mail@pmmaga.net (=?UTF-8?Q?Pedro_Magalh=C3=A3es?=)

--001a11471eb21caed9055161566e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 7, 2017 at 5:38 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 7 June 2017 15:23:13 BST, "Pedro Magalh=C3=A3es" <mail@pmmaga.net> wro=
te:
> >On Wed, Jun 7, 2017 at 4:07 PM, Rowan Collins <rowan.collins@gmail.com>
> >wrote:
> >
> >> you can't simply pass something that *incidentally* changes a
> >> pre-established rule
> >
> >
> >Hi Rowan,
> >
> >Would you consider that that is not the case for your own RFC?
> >https://wiki.php.net/rfc/deprecate-bareword-strings
>
>
> I'm sorry, I don't follow. What rule is broken, incidentally or
> explicitly, by that RFC?
>
>
> --
> Rowan Collins
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

The page that was already mentioned on this thread:
https://wiki.php.net/rfc/releaseprocess#releases_cycle explicitly states
the following:

x.y.z to x.y+1.z
> Backward compatibility must be kept


However, a number of already implemented RFCs for 7.2 do not follow that
rule strictly:

   - https://wiki.php.net/rfc/number_format_negative_zero
   - https://wiki.php.net/rfc/convert_numeric_keys_in_object_array_casts
   - https://wiki.php.net/rfc/deprecate-bareword-strings
   - https://wiki.php.net/rfc/get_class_disallow_null_parameter
   - https://wiki.php.net/rfc/counting_non_countables
   - https://wiki.php.net/rfc/deprecate-png-jpeg-2wbmp
   - https://wiki.php.net/rfc/hash-context.as-resource
   - https://wiki.php.net/rfc/deprecate-and-remove-intl_idna_variant_2003
   - As well as some of the RFCs still pending implementation

I don't mean at all that these should not have been accepted. Especially
the ones that initiate a deprecation phase. But it is seems to me that this
RFC does not break any rule that has been upheld strictly up to this point.

Regards,
Pedro

--001a11471eb21caed9055161566e--