Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75583 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84870 invoked from network); 16 Jul 2014 09:34:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jul 2014 09:34:21 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.53 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.53 mail-qa0-f53.google.com Received: from [209.85.216.53] ([209.85.216.53:34374] helo=mail-qa0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 40/02-07119-C1746C35 for ; Wed, 16 Jul 2014 05:34:21 -0400 Received: by mail-qa0-f53.google.com with SMTP id v10so473195qac.40 for ; Wed, 16 Jul 2014 02:34:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JIkAHPCGh3VhKA8kuViiFQNTiNAwcNxgue8K6t1qcJ4=; b=lqBIfLWqcybkjhbJMrBJ+1CjygR8sVSxpbX7e7xMoIUhw3KOia/ZI5u3QWWyWBBTiQ xbAAVZgj5uyGmuaai06leU6YoD+4JAn9TS+UbH44jcLyyIBrjCbut/2amo5ZGwJ6gnqs 53tiI8AX7XKmJXCy0Y59QyeiJaCdEuvWg1qV3vamJiduF1bqFnitH5rd9MVcA57FN9zE i7ArdVQRARdAZG76uVk1i3BX2xYZLPTqc+vL+fonYz8C6HtGOZHQPFGH30SY3JIiC3Pz acgXz8z1fqBXuIYb70ff4LOqR2N+2tKgbSRTu8w0TO3gHZz3V6hLqSQUFg2DTUYnngPq fDaA== MIME-Version: 1.0 X-Received: by 10.140.49.76 with SMTP id p70mr41998195qga.86.1405503257610; Wed, 16 Jul 2014 02:34:17 -0700 (PDT) Received: by 10.140.28.183 with HTTP; Wed, 16 Jul 2014 02:34:17 -0700 (PDT) Received: by 10.140.28.183 with HTTP; Wed, 16 Jul 2014 02:34:17 -0700 (PDT) In-Reply-To: <00d12255efc53466245b21a83ff7d474@mail.gmail.com> 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> Date: Wed, 16 Jul 2014 11:34:17 +0200 Message-ID: To: Zeev Suraski Cc: Stas Malyshev , PHP internals , Andrey Andreev , Andrea Faulds , Rowan Collins Content-Type: multipart/alternative; boundary=001a11370a3466abf304fe4c3a18 Subject: RE: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening) From: pierre.php@gmail.com (Pierre Joye) --001a11370a3466abf304fe4c3a18 Content-Type: text/plain; charset=UTF-8 On Jul 16, 2014 4:29 PM, "Zeev Suraski" wrote: > 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. I am -1 in yet another error (as in E_*), which will be just as painful to deal with than any other. --001a11370a3466abf304fe4c3a18--