Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83462
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAB6YZuyr4QTMBoOQe5Q3xHpS1wSndpOqKvX_Czh2rZVzSKFPhw@mail.gmail.com>
References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com>
 <CAEPJduk3VgWYgpuJ4G0JvUXYaMoO7430Q0k7v5ifwWF_dzh9rA@mail.gmail.com>
 <9aec85c81b49009c6238ff6d8be27cd4@mail.gmail.com> <CAB6YZuyr4QTMBoOQe5Q3xHpS1wSndpOqKvX_Czh2rZVzSKFPhw@mail.gmail.com>
Date: Sun, 22 Feb 2015 01:30:10 -0800
Message-ID: <CAFr9Zqti473HR70G0uKC2be0ow30pzD3J-1fmHKFh35fB0+Dkg@mail.gmail.com>
To: =?UTF-8?Q?Pavel_Kou=C5=99il?= <pajousek@gmail.com>
Cc: Zeev Suraski <zeev@zend.com>, Benjamin Eberlei <kontakt@beberlei.de>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0115ebf4dbc36b050fa9efb3
Subject: Re: [PHP-DEV] Coercive Scalar Type Hints RFC
From: shashankkumar.me@gmail.com (Shashank Kumar)

--089e0115ebf4dbc36b050fa9efb3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 21, 2015 at 2:39 PM, Pavel Kou=C5=99il <pajousek@gmail.com> wro=
te:

> On Sat, Feb 21, 2015 at 11:25 PM, Zeev Suraski <zeev@zend.com> wrote:
> > There=E2=80=99s a fundamental difference between the two RFCs that goes=
 beyond
> > whether using a global INI setting and the other per-file setting.  The
> > fundamental difference is that the endgame of the Dual Mode RFC is havi=
ng
> > two modes =E2=80=93 and whatever syntax we=E2=80=99ll add, will be with=
 us forever;  and
> in
> > the Coercive STH RFC =E2=80=93 the endgame is a single mode with no INI=
 entries,
> > and opening the door to changing the rest of PHP to be consistent with
> the
> > same rule-set as well (implicit casts).   The challenge with the Coerci=
ve
> > STH RFC is figuring out the best transition strategy, but the endgame i=
s
> > superior IMHO.
>
> Hello,
>
> the two modes was something that I didn't like, at all, as a userland
> developer. It seems really scary that decision to add 2 modes would
> mean that every PHP code could have been written in any of these 2
> ways and it would stick forever with PHP, because removing it again if
> it proved to be a bad feature would be IMHO really painful.
>
> So a single mode is infinitely better than 2 modes.
>
> Also, personally, I would prefer #1 or #2 version for internal
> functions, but definitely without an INI switch. Not being able to
> change it on some hostings could make development for the transition
> period kinda painful.
>
> Regards
> Pavel Kouril
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
> As a userland developer I will chime in and say that I love this rfc
better than the dual mode. In my opinion, having dual mode will
put unnecessary cognitive burden on me especially when reading other
people's code and libraries. While current rfc conversion rules are also
different than what exists in PHP but I can get used to them and they are
more
in line with what should ideally be there (except contentious ones like
bool).

I will certainly love to see the type coercion rules being unified and
slightly tightened up
over time and this is a good first step for that.
I am not a lang expert but of the languages I have learnt
and developed in, I can't think of any that allow dual mode type coercion
rules in such an explicit manner as the one proposed by Andrea/Anthony.

Thanks
Shashank

--089e0115ebf4dbc36b050fa9efb3--