Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75584 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88149 invoked from network); 16 Jul 2014 10:27:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jul 2014 10:27:09 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.171 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.171 mail-we0-f171.google.com Received: from [74.125.82.171] ([74.125.82.171:57830] helo=mail-we0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 13/72-07119-B7356C35 for ; Wed, 16 Jul 2014 06:27:08 -0400 Received: by mail-we0-f171.google.com with SMTP id p10so701243wes.2 for ; Wed, 16 Jul 2014 03:27:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=6tmyn+hyVpgubK7dpVuzCkszUtPJabKrGMg3ZO0NKWg=; b=sG51XGvAf1kiTTd51i616LWdvTo32mh6QBnFBywrImX2BUDR5YRzg0egQ/n7DXmZp7 RUKtb7SxlVVuJdJRyODX4yPUBE3nTSEnR7VQNpSCwMIafby3ziXCkTGhLrypOS/I5BR1 hkCUKt2hI+VKwCipr5CxO7Rstx9YnJRdFxu5ulcTz3mhywPdFeDLFmwy+LpVzlwuSRjD 3l0qpPLTr9IaFx4NB0VKjSCM0ao9NbZs4Zt0DNKkJexReIL9dqU3LI4z0VV3WFSZ7wWE L6I87gK1FRacnhmDz9Vbl6GWa3Y9U3mMPFNTJd4OOhF3oZGBKOnqr34U9hwS8mleSSvq /azg== X-Received: by 10.194.236.132 with SMTP id uu4mr33992963wjc.54.1405506424293; Wed, 16 Jul 2014 03:27:04 -0700 (PDT) Received: from [192.168.0.139] ([62.189.198.114]) by mx.google.com with ESMTPSA id v4sm27295469wiz.16.2014.07.16.03.27.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Jul 2014 03:27:03 -0700 (PDT) Message-ID: <53C652FA.6010704@gmail.com> Date: Wed, 16 Jul 2014 11:24:58 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: internals@lists.php.net References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <16D48604-0C0A-4613-91A4-21392E3A2636@ajf.me> <05CE2216-C5D9-4937-9F2E-AA1407284D9F@ajf.me> <53C460DF.5040304@sugarcrm.com> <53C53A96.2040303@gmail.com> <53C55342.1010207@sugarcrm.com> <53C563B3.6060905@gmail.com> <54536191-1B92-4933-973F-0C8289D13A4C@ajf.me> <00d12255efc53466245b21a83ff7d474@mail.gmail.com> In-Reply-To: <00d12255efc53466245b21a83ff7d474@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening) From: rowan.collins@gmail.com (Rowan Collins) Zeev Suraski wrote (on 16/07/2014): > For me the introduction of a new set of rules is a deal breaker. > I'm -1 on the RFC the way it is, and +1 if we implement these 'hints' as > implicit casts, plus change implicit casts to emit E_CAST in case of loss > of data or 'bogus' conversions. Just to be clear, implementing E_CAST would require introducing a set of rules for when to throw it. By a strict reading of your message, that's a deal breaker. In other words, you can't make an omelette without breaking eggs. We can choose not to make the omelette, or we can choose which eggs to break.