Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85050 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17243 invoked from network); 16 Mar 2015 13:32:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2015 13:32:45 -0000 X-Host-Fingerprint: 78.192.130.122 jav75-2-78-192-130-122.fbxo.proxad.net Received: from [78.192.130.122] ([78.192.130.122:4143] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 35/09-03331-B7BD6055 for ; Mon, 16 Mar 2015 08:32:44 -0500 Message-ID: <35.09.03331.B7BD6055@pb1.pair.com> To: internals@lists.php.net Date: Mon, 16 Mar 2015 14:32:39 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Posted-By: 78.192.130.122 Subject: Re: [PHP-DEV] About declare(strict_types = 1) From: pascal.chevrel@free.fr (Pascal Chevrel) Le 16/03/2015 12:39, Xinchen Hui a écrit : > Hey: > > And last comment, if there no such declare thing, I will definitely > vote yes to this RFC. Hi Xinchen, You can also not vote at all, that's a very valid option. By voting yes, you say that you want PHP developers to have access to STH in PHP 7, by voting No, you say that you don't want PHP developers to be able to use STH in PHP 7. By not voting, you let the rest of the PHP community that cares about STH (both for and against) decide if the feature gets in the language. As a person with voting rights, you should study the RFCs in details, understand them fully and vote on what you think you have understanding and expertise on. There is no obligation to vote on all RFCs. It seems that you won't use STH yourself so you will probably never use declare in your code and won't be impacted by the existence or not of the feature. I also don't like how the declare syntax looks, and similarily I personnally dislike even more how ugly the namespace syntax is in PHP with the backslashes (Foo\Bar\Baz), yet, I am happy that we do have the possibility to namespace our code, because PHP 5 *needed* that feature. And I think PHP 7 needs something like that, I also think it's a very clever solution as we can keep on using PHP as a weakly typed language as usual but also strenghten some of our code that needs strong typing. > > that's why I want vote no for this, and wait for Bob's Basic STH. > > thanks It's too late, Bob's Basic STH missed the schedule for PHP 7, it was proposed way too late and the coercive STH RFC has just zero chance to pass, it's too much of a BC break for everybody. The dual mode STH is the only chance to have something for PHP 7 and remain competitive with HHVM, Node.js… that we see people switch to. Baidu switched to HHVM, Wikipedia too, in my country big names switched from PHP to node.js and that was not just for performance reasons, it was also for the features. Zeev himself admitted that we need something for PHP 7. Personnally, I think the dual mode is a very clever way to please all PHP developpers, those that want to use weak typing, those that want to use stronger typing and those like me that would continue to use weak typing because it's convenient but would be happy to use STH on very specific parts of his code that would benefit from it. Cheers, Pascal