Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84965 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38769 invoked from network); 16 Mar 2015 01:49:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2015 01:49:04 -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.192.42 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.42 mail-qg0-f42.google.com Received: from [209.85.192.42] ([209.85.192.42:35656] helo=mail-qg0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 81/1C-06614-D8636055 for ; Sun, 15 Mar 2015 20:49:01 -0500 Received: by qgez64 with SMTP id z64so29175133qge.2 for ; Sun, 15 Mar 2015 18:48:58 -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=bRJZSfA6okALO6m4/wEmKTOwePE6PUx/IUO5X9tiLOY=; b=B8jxxKsbWvR1JXMWAGaFVnae2IAtEpluFhD2CqOxY0qYTiePDHdPk4PB4B8FKSibtv DhRaXTru4OVXQW8dRkjxL7IZ4/39uGQSWEr7/y0PzPhdyrEiigxDL0whJgh8ozRRQqYu fJYchvil3eTv2joZBIoWzevvafoekR1gHGyFaVO+Iyq+FkHHdaSCTdZW5YI+HHI/b8FX 9adosDhZ/Nj4Ab04RWNrHYkie7LU7xpmM3ajgBxUcCAIzBANGc8R55TEEfxEkUZRGvi6 3vTahpDb5h+xmZvp2RFHfp09EDOXJOOqfRIsGgI9QkGYT61lQI0GIf19yA7iEk1g9Q1T k8jg== MIME-Version: 1.0 X-Received: by 10.229.68.136 with SMTP id v8mr72279165qci.16.1426470537973; Sun, 15 Mar 2015 18:48:57 -0700 (PDT) Received: by 10.96.39.195 with HTTP; Sun, 15 Mar 2015 18:48:57 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Mar 2015 12:48:57 +1100 Message-ID: To: Yasuo Ohgaki Cc: Anthony Ferrara , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC][Status] Scalar Type Declarations Voting Date Change From: pierre.php@gmail.com (Pierre Joye) On Mon, Mar 16, 2015 at 12:40 PM, Yasuo Ohgaki wrote: > Hi Anthony, > > On Mon, Mar 16, 2015 at 6:33 AM, Anthony Ferrara > wrote: > >> I have decided to close the vote on my Scalar type declarations RFC. >> >> When I added the wording "or the date that voting closes on a >> competing RFC." to the voting timeline of the RFC, it was in the >> understanding that it was a good faith effort on the part of Zeev and >> the competing RFC for the best of the project. I was advised against >> doing so by several people. I still chose to show the good faith and >> attempt to work with people rather than against them. >> >> However, it has become exceedingly clear to me that this good faith >> has not been reciprocated. The understanding that we had when both >> proposals opened has now been violated. Rules have been broken and >> politics are ensuing in an attempt to sabotage this proposal. Rather >> than working together, "unofficial polls", backdoor politics and poor >> behavior have created yet more toxicity. >> >> For this reason, I consider the good-faith clause violated. >> >> Rather than drag this vote on end, and rather than be accused of >> closing "when convenient", I am choosing to move up the ending day to >> put an end to the drama. >> >> Therefore, I am closing votes on this RFC effective tomorrow, March 16th. >> >> https://wiki.php.net/rfc/scalar_type_hints_v5#vote >> > > The most serious issue of this RFC is > > - It hides bugs that should be fixed in both weak and strict hint mode. I disagree, and I won't discuss why again. You misunderstood how it works or did not test it. Not sure which :( > Coercive type for general developers and strict type for library developers > will > eliminate more type related bugs, more natural to average PHP users. IMHO. And change casting rules, open a pandora box. And even worst, it is a zero compromise RFC. Same as before, no need to discuss that any longer. > It's natural that we have different point of views, but we can easily > understand/guess > the consequence of the RFC. Weak mode is simply too weak to be useful. > Strict mode will hide type bugs by errorless casts. Show me examples when something not in strict mode behave differently and it will be fixed. But saying that is per se wrong and double standard in regard of voting. Or why did you vote in favor of other RFCs which obviously had or still have bugs? > I hope both you and Zeev work together to satisfy most needs because > hiding bugs are not good thing to do. It does but I do not claim that there are no bug, every code has bugs and they should be fixed. -- Pierre @pierrejoye | http://www.libgd.org