Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83437
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.223.175 as permitted sender)
References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com> <CAOsHV+uVXPuxY0Zy_pOwb1G=EdX4tJyJ7jEkWQ7DM-yXcg2u=w@mail.gmail.com>
In-Reply-To: <CAOsHV+uVXPuxY0Zy_pOwb1G=EdX4tJyJ7jEkWQ7DM-yXcg2u=w@mail.gmail.com>
MIME-Version: 1.0
Thread-Index: AQKcPg+jpyYspJS11b5G1A7RBHpKTgKHEpygm0+PyrA=
Date: Sun, 22 Feb 2015 00:12:11 +0200
Message-ID: <e5de9ed3420c0448adc82ca2fc1cfc2f@mail.gmail.com>
To: marcio3w@gmail.com
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113f998afc2abd050fa07592
Subject: RE: [PHP-DEV] Coercive Scalar Type Hints RFC
From: zeev@zend.com (Zeev Suraski)

--001a113f998afc2abd050fa07592
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

M=C3=A1rcio,



I hope to be able to work on an actual implementation and have something by
the end of the upcoming week, allowing us all to experiment.

Other than tweaking the conversion table, which based on the feedbacks I *
*believe** can be done in a way everyone can live with =E2=80=93 I agree th=
at the
biggest open question is how we deal with internal functions.



Also note that the, the 2nd proposed option in the RFC (=E2=80=9CEmit E_DEP=
RECATED
in 7.0, move to E_RECOVERABLE_ERROR in v7.1 or v8.0=E2=80=9D) =E2=80=93 of =
marking
newly-rejected-conversions as E_DEPRECATED is not considered as a BC break
IMHO.  The code would still work, and the likelihood that something bad was
legitimately found is pretty high.



Given the compressed timeline, I wanted to gauge the general response as
soon as possible, and also start the RFC discussion process as soon as
possible, which meant we couldn=E2=80=99t include the implementation to go =
along
with it.



Two more things regarding the competing RFC =E2=80=93 it=E2=80=99s still al=
ive, and being
promoted for PHP 7.0;  And while it doesn=E2=80=99t create a huge BC break,=
 it
allows developers to selectively create localized BC breaks, on a per file
basis.



Thanks for the feedback!


Zeev



Thanks for your effort and for proposing the RFC so quick. But indeed, as
you said, this is really premature.

According to my interpretation the RFC proposes a potentially huge bc break
on internal functions usage while the competing (recently withdraw) RFC was
BC compatible regarding this. Having this proposal without a working patch,
so we can try the real impact it could have before form opinions, frankly,
doesn't sound like a good idea.

I know it's still a draft but, considering the RFC is aimed to v7.0, I hope
to see a working implementation before the feature freeze just like what
was exemplary made with the other previous withdraw proposals.

Thanks,

M=C3=A1rcio

--001a113f998afc2abd050fa07592--