Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82995 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21289 invoked from network); 17 Feb 2015 18:30:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2015 18:30:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.223.174 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.223.174 mail-ie0-f174.google.com Received: from [209.85.223.174] ([209.85.223.174:45148] helo=mail-ie0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E4/F9-19463-8D883E45 for ; Tue, 17 Feb 2015 13:30:49 -0500 Received: by iecat20 with SMTP id at20so42944002iec.12 for ; Tue, 17 Feb 2015 10:30:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=d+FL5V6QNaD+K7mj5KsxZusPJMIw8F+VCApYbW58C6o=; b=VlIjCcIiCnwHsBNjZ+6WZpiXQIR97IT/gGNXSW/FLTXJVJ7Rwl9pJMY9t1rICrT59E GM3CNWZkt/Zn5mJ1mpAIsJa5RsPu29HN70qxBw+bmVzwePRA5wRs9XCi3xO+U4NyI8pn 994Nc/NmiHQE+uZBy8KluJWH5bznK4sksPADPHmAAMNt0tGkwJKf8ssMDz1CUu7/3uqf BnTX4+sKIppdRVvFOdSUepXZQFrYtgLbKlu2a9MzOCBzVQB6fQ7A8TugqXQ97Hz7+IDa 1UDS7k3lP+y2klIgfbh9Hj0hx0/85ToM8QPcuuQ5VMxoVgZfdEDly3EMZXaQd5uMctuq IRkg== X-Gm-Message-State: ALoCoQlST9W3zJCSulDARmCT0vGf+AwKGPD6+2qULBzJggEKr088vJu75/9H1aDlT2+FESeGbbHq8xgWAYkVU2AeapaG4FHcHAqsVc4qXX6Lhm4oOqIULlY0DPOmWk786AUlRCycH/t01K7CzRkiq1dfcFFTglJglg== X-Received: by 10.50.78.131 with SMTP id b3mr29576573igx.0.1424197845846; Tue, 17 Feb 2015 10:30:45 -0800 (PST) References: <011801d04a07$83ab1c00$8b015400$@php.net> <016f01d04a3a$e9183220$bb489660$@php.net> <022801d04ab1$4a0c47d0$de24d770$@php.net> <1913e09d7f52541901d8574d2080a63f@mail.gmail.com> <7a5d96b34b98ec1f3ee17be7fa6a1e81@mail.gmail.com> <2CBDEB67-3DE3-437D-9AF3-0E6A92027244@zend.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGD0sLDaA+/0NIeBlQhQC5OtPA/xwHih9+6AanvcsEBj7eMCwEU0CpMAs0H7+gBDwGZjwJNu28fAX8sxVQAox2RWwKtsa6+Ap7Ai84CNkZj6pzeFDMg Date: Tue, 17 Feb 2015 20:30:44 +0200 Message-ID: <4cc0c81c7199a452534bb8edcdb19914@mail.gmail.com> To: Andrey Andreev Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] Reviving scalar type hints From: zeev@zend.com (Zeev Suraski) > Yes, I already know that. > The difference, and why I keep pointing that out, is that me and many > others > want strict typing for our own reasons (but still in its entirety instead > of as a > limited mode) and most of us don't even care if you getting weak typing > for > your own usage. You can't work towards consensus if your target is to > prevent the opposing group of getting what they want. I see both as > valuable > tools for different jobs and I want to have more tools at my disposal, > while > you're trying to tell me that I should use only one tool for everything. First, it's very important to understand that my target is to prevent the opposing group from getting what they want. I'm really not sadistic :) My reasons were obviously different and worked towards a different goal. Much in the same way that people who vote against an RFC - one of the countless that were voted against - don't do that to hurt the ones who support it. They do it because they think adding it would bring negative consequences. I never believed the 'You don't have to use it' as a silver bullet explanation for why it's OK to add features with potentially negative implications. The good news is that I think that in many ways the ideas we're toying with right now are better for the strict-type camp, especially if we end up going for just one mode, and meet roughly mid-way in terms of strict and weak - which I think is doable. The biggest gripes strict campers had with weak mode are gone in this proposal, and unlike v0.3 - that would actually be the default (and only) behavior, which is a big gain for the strict campers. And the most prominent features of weak typing are kept (dynamic type conversion where it makes sense), hopefully making the weak campers happy too. > But you implied that most objections were from people who don't want > strict > typing in PHP at all. And I disagree with that because it's a speculation, > which > in turn you are using to favor your weak-hints-only case (hence, twisting > it in > another direction). I didn't imply it now (at least I certainly didn't intend to). I did outright say it a week or two ago, and still believe that's the case but reached the conclusion that none of us would gain anything from further discussing it. We won't know unless we start actually polling the people who voted and ask, which we're not going to do, and we're obviously not going to convince each other. Much more importantly, it at least *seems* as if we have a direction for something that a very wide audience may rally behind. Let's focus on that! Zeev