Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80508 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87933 invoked from network); 15 Jan 2015 00:02:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jan 2015 00:02:34 -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.48 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.48 mail-qa0-f48.google.com Received: from [209.85.216.48] ([209.85.216.48:42988] helo=mail-qa0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 29/44-00659-99307B45 for ; Wed, 14 Jan 2015 19:02:34 -0500 Received: by mail-qa0-f48.google.com with SMTP id v8so9018318qal.7 for ; Wed, 14 Jan 2015 16:02:31 -0800 (PST) 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:content-transfer-encoding; bh=KUfoN5ZJVBcVCAlz7kp71OXIDnKMURjDGRSfpZROfHM=; b=knvLxFP1UXy34jf65jkBBEI2491xMuPJC7aG80uwMu3KyK9/CyAnGOIIkO1mbty0Qg BAyHYUmp4LveMyZ9C542Ix/XFTQ0aFGxMbcnapSv2/ZnI5BtxntuxYwpjt8usMB8TvF9 7r+yd152u2F2kY9nbDT5QwccZCkzSyC5rAA+yjX91dX2CQ0a1OuHX7Y/tH9rMAs4esc/ 1qUbiP95kSDyqIDLKjGszpFtE+ZB3GPRPxyq86g/Ba/hZhpgHTV6Pg1KBiLmnOyiFnMw Wtt6DIcEQdtkP7o+iBVV8Qh/fjIerc+Jrzw4ggfAxnPtQaqb63nKhcVppQ5LoxF728Ni 4nIQ== MIME-Version: 1.0 X-Received: by 10.140.43.52 with SMTP id d49mr457080qga.94.1421280151544; Wed, 14 Jan 2015 16:02:31 -0800 (PST) Received: by 10.140.22.106 with HTTP; Wed, 14 Jan 2015 16:02:31 -0800 (PST) In-Reply-To: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> Date: Thu, 15 Jan 2015 01:02:31 +0100 Message-ID: To: Andrea Faulds Cc: PHP Internals List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2 From: pierre.php@gmail.com (Pierre Joye) hi Andrea, On Wed, Jan 14, 2015 at 1:16 AM, Andrea Faulds wrote: > Good evening, > > I=E2=80=99ve made some quite significant changes to my Scalar Type Hints = RFC, and bumped its version to 0.2. > > Here: https://wiki.php.net/rfc/scalar_type_hints > > This is a new thread because I=E2=80=99ve made a significant revision to = the RFC, so it=E2=80=99d be sensible to separate discussion of the updated = RFC from the v0.1 RFC. > > Please tell me your thoughts. As much as I like the concept, it adds a bit too much confusions and options for my taste. My feeling (as you and other said already many many times), a relatively large part of the users would prefer strict type hinting over something that relies on the current conversion behaviors, for clarity. There are still some people opposed to strict hinting or opposed to hinting but that was pretty much the same when we discussed the additions of OO related features. Instead of having one option full of compromises, I would suggest to go with the 0.1 version with two options, strict and matching the current conversions behaviors and move on. No matter how we look at it, there is no way we can find compromises between one or the other solution. It is only about strict or current conversions, everything else is going to be an endless discussion about the exact same arguments, pros, cons, etc. Cheers, --=20 Pierre @pierrejoye | http://www.libgd.org