Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83434
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.176 cause and error)
MIME-Version: 1.0
In-Reply-To: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com>
References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com>
Date: Sat, 21 Feb 2015 22:38:33 +0100
Message-ID: <CAEPJduk3VgWYgpuJ4G0JvUXYaMoO7430Q0k7v5ifwWF_dzh9rA@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c26958b07cb3050f9ffd7c
Subject: Re: [PHP-DEV] Coercive Scalar Type Hints RFC
From: kontakt@beberlei.de (Benjamin Eberlei)

--001a11c26958b07cb3050f9ffd7c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Zeev,

On Sat, Feb 21, 2015 at 6:22 PM, Zeev Suraski <zeev@zend.com> wrote:

> All,
>
>
>
> I=E2=80=99ve been working with Fran=C3=A7ois and several other people fro=
m internals@
> and the PHP community to create a single-mode Scalar Type Hints proposal.
>
>
>
> I think it=E2=80=99s the RFC is a bit premature and could benefit from a =
bit more
> time, but given the time pressure, as well as the fact that a not fully
> compatible subset of that RFC was published and has people already
> discussing it, it made the most sense to publish it sooner rather than
> later.
>
>
>
> The RFC is available here:
>
>
>
> wiki.php.net/rfc/coercive_sth
>
>
>
> Comments welcome!
>

I was really looking forward to the RFC. However the dependence on an INI
setting and the question of massive internal BC break are a bit too much I
think.

They are necessary as you explain to allow internal functions/ZPP to have
the same conversion rules as userland functions. This INI setting is quite
similar to introducing two modes as well, but on the server configuration
level instead in a much more fine granular way in scalar type hints v0.5.

I see much more compatibility problems for third party libraries here.

Now if I had to decide between having two modes on a granular file level or
an INI setting (option 2/3) or massive BC breaks (option 1) to get scalar
type hints in PHP, then two modes with declare() doens't look, because I
can pick the mode I want, and no-one can force it on me.


>
> Zeev
>

--001a11c26958b07cb3050f9ffd7c--