Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77234
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <EAB826F3-959E-4DD2-9474-6EADDA12EF4D@ajf.me>
References: <6893A97A-EC4C-4124-B804-96E2A26B953F@ajf.me>
	<B84F8A67-CE7E-4716-A211-7BB52421534F@ajf.me>
	<EAB826F3-959E-4DD2-9474-6EADDA12EF4D@ajf.me>
Date: Tue, 16 Sep 2014 07:08:24 +0200
Message-ID: <CAEZPtU532FXAOiKNWkVFpcvEK=44LLZ-SLgO4WFc3G0KL4=17Q@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with Cast
From: pierre.php@gmail.com (Pierre Joye)

hi Andrea,

On Mon, Sep 15, 2014 at 3:07 PM, Andrea Faulds <ajf@ajf.me> wrote:
>
> On 14 Sep 2014, at 00:35, Andrea Faulds <ajf@ajf.me> wrote:
>
>> I have postponed the vote after further thought. It=E2=80=99s been a whi=
le since this was discussed on the list.
>>
>> However, it is my intent to open voting properly at some point soon, if =
all goes to plan.
>
> I have withdrawn the RFC. I do not feel anymore that it is the way forwar=
d with scalar type hints in PHP.

Sigh. Here we go again.

I do not think we will ever reach an agreement on the list before the
RFC goes to the voting phase. That's why I think the RFC should
contain the most requested options and go with them. Any further
discussions will simply create more confusions and yet again move to a
dead end, we all lose.

It would be great if there are two sets of options:
- One about having scalar typed arguements, hinted or not, simple
yes/no, so we at least agree on having the feature
- a set of options about how should it work
  . strict
  . what the rfc describes in its last state
  . matching, if possible at all, current casting, following what
(int)$foo and co or whatever is considered as "the common casting php
way"

I am not saying these are the only options or only the correct ones,
there may be other. I only would like to get this sorted out sooner
rather than later.

If we agree on the feature itself and we do not see a clear majority
on one point or another, let take the top two options and try to
figure what has to be changed to get a majority (2nd phase vote).

To be more clear: We must get a decision here. I am convinced that
this is a top requested feature, since very long. Delay it forever
only because we are unable to find a concensus sounds pretty bad. Let
get us together to finally have this feature implemented, in the best
possible way.

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org