Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80509
Return-Path: <cmbecker69@gmx.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 95373 invoked from network); 15 Jan 2015 01:07:38 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 15 Jan 2015 01:07:38 -0000
Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.22 as permitted sender)
X-PHP-List-Original-Sender: cmbecker69@gmx.de
X-Host-Fingerprint: 212.227.17.22 mout.gmx.net  
Received: from [212.227.17.22] ([212.227.17.22:62740] helo=mout.gmx.net)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 6F/85-00659-8D217B45 for <internals@lists.php.net>; Wed, 14 Jan 2015 20:07:37 -0500
Received: from [192.168.0.100] ([91.67.244.80]) by mail.gmx.com (mrgmx103)
 with ESMTPSA (Nemesis) id 0MKHik-1Y9ukM0VAU-001i9C; Thu, 15 Jan 2015 02:07:32
 +0100
Message-ID: <54B712D8.2050809@gmx.de>
Date: Thu, 15 Jan 2015 02:07:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Andrea Faulds <ajf@ajf.me>, Zeev Suraski <zeev@zend.com>
CC: RQuadling@gmail.com, Leigh <leight@gmail.com>, 
 PHP Internals List <internals@lists.php.net>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> <CAPwsocGyv7dp8n=_E1QfrXRSbYZXcHZAPk5F=hDLB070i=SCGA@mail.gmail.com> <4E2073DE-0951-498C-97BB-DDAC094F11FA@ajf.me> <9a033dd1f223f854e760924d118ab812@mail.gmail.com> <CAKUjMCU-57cDpG5ZbDGv10dSqx=Ey40D-WbKxKSnC6oSYOfLWw@mail.gmail.com> <2ae0164cb9b9bf1c974d7a3c60af0466@mail.gmail.com> <F3BC55CD-38CD-42B7-AE0B-A6D34E3D3875@ajf.me>
In-Reply-To: <F3BC55CD-38CD-42B7-AE0B-A6D34E3D3875@ajf.me>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Provags-ID:  V03:K0:k9CG7jTPC/OqHqTK8HB/VFnR6TQsWX1RqoFkRRqr0NBo851buUB
 YRzWjsTk7fajbAkLVljwww/1NjxbxrBXYk/EEajsGSkYslI2xWDfOo7xLC3CuiSegY1r4L6
 5gD5BiU2/eCF3VB01t4E3KaUBNr53F3d9ODVOWegmZ0odN1t7SHPc04Kg3UB8ckPs6toPa2
 sdB+yepoVAOAIHmVQjGKQ==
X-UI-Out-Filterresults: notjunk:1;
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: cmbecker69@gmx.de (Christoph Becker)

Andrea Faulds wrote:

> From what I can see, the larger PHP community is generally in favour
> of strict typing, and among them, the previous RFC revision was
> received quite poorly. Myself, I might have been somewhat happy with
> just weak hints, but it would upset an awful lot of developers who
> would like some measure of strict typing. Developers who would most
> likely not use the new scalar type hints, because they weren’t
> strict. And if nobody uses them, why add them?
> 
> This revision hopes to possibly placate both weak and strict typing
> advocates. Of course, it also will lose some support in that it
> allows a choice. Plus, it gives the user choice, not the API
> designer, which I expect will be somewhat controversial. But I am
> hopeful.

Just a thought: what about having weak scalar type hints which throw
E_STRICT_TYPE if a value of another type is passed?

-- 
Christoph M. Becker