Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77488
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.107 as permitted sender)
Message-ID: <54208F5C.4080603@sugarcrm.com>
Date: Mon, 22 Sep 2014 14:06:36 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: Pierre Joye <pierre.php@gmail.com>
CC: PHP internals <internals@lists.php.net>
References: <6893A97A-EC4C-4124-B804-96E2A26B953F@ajf.me>	<B84F8A67-CE7E-4716-A211-7BB52421534F@ajf.me>	<EAB826F3-959E-4DD2-9474-6EADDA12EF4D@ajf.me> <CAEZPtU532FXAOiKNWkVFpcvEK=44LLZ-SLgO4WFc3G0KL4=17Q@mail.gmail.com>
In-Reply-To: <CAEZPtU532FXAOiKNWkVFpcvEK=44LLZ-SLgO4WFc3G0KL4=17Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with Cast
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> - One about having scalar typed arguements, hinted or not, simple
> yes/no, so we at least agree on having the feature

I'm not sure how that would work. We agree on having what feature?
Having coercive typing and having strict typing are two different
options, working in different way and implying different coding
approaches. And then there's also a third option which is a "compromise"
approach where it is sometimes strict and sometimes not depending on a
matrix of choices, and different matrices would work in different way.
If I agree, for example, that coercive model is helpful - that doesn't
mean I want complete strict typing, and I certainly would prefer none
for now - in hope I would succeed convincing the majority in the future
in the merits of coercive typing approach - than having strict model
implemented now and closing the door for the coercive one forever. So I
don't see how "at least agree" without specifying what we agreeing on
works out.

> 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

Is there any data to support this conviction that this is not merely
requested now and then, but it is a *top* requested feature since very
long? Note that none of the languages most close to PHP have it.
Also, I did a poll one on stackoverflow:

http://programmers.stackexchange.com/questions/27564/what-features-would-you-like-to-have-in-php

and it's not on top at all, though it is among the requested ones.
However, having no consensus on it, saying "let's get together and make
something" does not look like a good idea to me, because there are
opportunity costs to prematurely having "something" that is not
satisfactory.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/