Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82114
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.41 as permitted sender)
Message-ID: <54D6F23F.1060405@gmail.com>
Date: Sat, 07 Feb 2015 21:21:03 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Andrea Faulds <ajf@ajf.me>, =?UTF-8?B?UGF2ZWwgS291xZlpbA==?=
 <pajousek@gmail.com>
CC: PHP Internals <internals@lists.php.net>
References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> <CAB6YZuy-FFERAqcOjtyiizzwUZb6qrnMw8FCf8zur1wsL37Opg@mail.gmail.com> <9E1C2427-0295-4F3E-BD29-04DA84321067@ajf.me>
In-Reply-To: <9E1C2427-0295-4F3E-BD29-04DA84321067@ajf.me>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I don’t think it’s unfair. There’s a limited set of permitted
> conversions in some strictly-typed languages, but it’s still
> strictly-typed.

The main problem with strict typing as it is being proposed by
strictness proponents is exactly that - there's no limited set
permitted. It leads to absurd limitations like 1 not accepted where a
float value is required, or where a boolean value is required. That's
the essential problem with this proposal - it sacrifices the frequent
use cases that make sense to nearly everybody for abstract
bondage-and-discipline notion under misguided assumption that it would
be a service to the users. In fact, if forced to use this API, people
would probably just learn to do (float) each time they call such
function, which makes them just do more work for something they could
have - and already do have, in internal functions - for free.
-- 
Stas Malyshev
smalyshev@gmail.com