Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82410 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2222 invoked from network); 11 Feb 2015 03:37:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Feb 2015 03:37:10 -0000 Authentication-Results: pb1.pair.com header.from=laruence@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=xinchen.h@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.215.45 as permitted sender) X-PHP-List-Original-Sender: xinchen.h@zend.com X-Host-Fingerprint: 209.85.215.45 mail-la0-f45.google.com Received: from [209.85.215.45] ([209.85.215.45:46881] helo=mail-la0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/60-33902-06ECAD45 for ; Tue, 10 Feb 2015 22:37:06 -0500 Received: by lams18 with SMTP id s18so837512lam.13 for ; Tue, 10 Feb 2015 19:37:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=GCrTMWDI1gYyYEZMLJu2+RbGldLZS2FrKz5p7ZV+v0A=; b=aZp5z7K5PPHChDh+7HfXyAQxKnmjeSkQpkKMJ0NjW76Id8JF9ZjXGRNcKRBb9xrmgV zdNyrOmiabw9sjDZKsbH/mgKnIV26eQZ4njJl8WRbC4kp2GbuGT6kpRlTJdDGbLY/ARy Jpb5GOqvtpFga5gh4+zKrTHG/8z7uXG4bmqfDM2hSSVCDSomW5mmWp1kPXWYEMXohr/E PCtC7DvCgw5ir7wAyPg2hCKg9w56TUAVLJBxiJSjaUJuPc1B0/g7Ifmw3xDOLTdMf63F w+gZQSy1xulRHjEurKKbRiY1nD76RxL8uDX3VKuOQ3fEqYEHSFEFykYBUhbIgVjRDSMs Pk1Q== X-Gm-Message-State: ALoCoQkeQsQxrEvNfegNCzNL7NKcXO6cRvhKzFsuZiLyLghQfKDacBPqSD/QJQAUnuandnkAkOGfABDoiJ/CMboPfpHs3aKU+NmqPMK/8E1qkOvmPLd5U6s+JZJZ6JjgAW3VwDyq6kLsgNuTVXaXzKvgxPc5TgxZrg== X-Received: by 10.112.26.110 with SMTP id k14mr25744972lbg.29.1423625821232; Tue, 10 Feb 2015 19:37:01 -0800 (PST) Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com. [209.85.217.175]) by mx.google.com with ESMTPSA id b6sm3045373laa.14.2015.02.10.19.36.59 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Feb 2015 19:37:00 -0800 (PST) Received: by mail-lb0-f175.google.com with SMTP id n10so848132lbv.6 for ; Tue, 10 Feb 2015 19:36:59 -0800 (PST) X-Received: by 10.152.206.2 with SMTP id lk2mr26372752lac.13.1423625819387; Tue, 10 Feb 2015 19:36:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.28.193 with HTTP; Tue, 10 Feb 2015 19:36:38 -0800 (PST) In-Reply-To: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> Date: Wed, 11 Feb 2015 11:36:38 +0800 Message-ID: To: Andrea Faulds Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints From: laruence@php.net (Xinchen Hui) Hey: On Fri, Feb 6, 2015 at 4:14 AM, Andrea Faulds wrote: > Good evening, > > At long last, I=E2=80=99m going to put the RFC to a vote. It=E2=80=99s be= en long enough - I don=E2=80=99t think there needs to be, or will be, much = further discussion. > > I=E2=80=99d like to make sure that everyone voting understands the RFC fu= lly. Please read the RFC in full: the details are important. And if anyone= has any questions or uncertainties, please ask them before voting. I am ve= ry happy to answer them. > > I would urge everyone who wants type hints to vote for this RFC. It is no= t a perfect solution, but there can be no perfect solution to this issue. H= owever, I think it is better than most of the alternatives suggested thus f= ar - see the rationale section, and previous discussions. Crucially, this R= FC would keep PHP a weakly-typed language, and not force either strict typi= ng, nor weak typing, on anyone who does not want it. It would allow the add= ition of type hints to existing codebases. It would not create a situation = where userland functions are strict yet internal functions are not, because= the strict mode affects both. I=E2=80=99ve tested the implementation mysel= f on my own code, and it worked well, providing benefits other proposals wo= uld not have given (see my previous post about my experiences). > > Voting starts today (2015-02-05) and ends in two weeks=E2=80=99 time (201= 5-02-19). In addition to the vote on the main RFC, there is also a vote on = the type aliases issue, and a vote to reserve the type names for future RFC= s=E2=80=99 sake if this RFC fails. > > The RFC can be found here, and it contains a voting widget: https://wiki.= php.net/rfc/scalar_type_hints > > Thank you for your time. > Actually, I was surprised by the progress of voting now... Seems never have so many users to vote... and bulk of active core developers are vote against on it. As a PHP user, I actually don't care about scalar type hinting much.. but I am strongly objecting declare thing... image of, one line setting care make a project doesn't work... image of, a larger project, some devers user strict_type, some for safe doesn't use.. then they have to add declare to every files's head... it's a nightmare.... I , here, acking you please reconsidering your vote... thanks > -- > Andrea Faulds > http://ajf.me/ > > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > --=20 Xinchen Hui @Laruence http://www.laruence.com/