Hey:
On Wed, Feb 11, 2015 at 11:36 AM, Xinchen Hui <[email protected]> wrote:
> Hey:
>
>
> On Fri, Feb 6, 2015 at 4:14 AM, Andrea Faulds <[email protected]> wrote:
>> Good evening,
>>
>> At long last, I’m going to put the RFC to a vote. It’s been long enough - I don’t
>> think there needs to be, or will be, much further discussion.
>>
>> I’d like to make sure that everyone voting understands the RFC fully. 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 very happy to answer them.
>>
>> I would urge everyone who wants type hints to vote for this RFC. It is not a perfect
>> solution, but there can be no perfect solution to this issue. However, I think it is better than
>> most of the alternatives suggested thus far - see the rationale section, and previous discussions.
>> Crucially, this RFC would keep PHP a weakly-typed language, and not force either strict typing, nor
>> weak typing, on anyone who does not want it. It would allow the addition 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’ve tested the implementation myself on
>> my own code, and it worked well, providing benefits other proposals would not have given (see my
>> previous post about my experiences).
>>
>> Voting starts today (2015-02-05) and ends in two weeks’ time (2015-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 RFCs’ 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...
<?php
include_one "lib/xxxx.php" // it use strict type
declare(strict_types=0); //damned , restore it.
$a = new B; // autoload, target file use strict type,
declare(strict_types = 0); //damned, restore it.
?>
am I wrong?!
thanks
>
> thanks
>> --
>> Andrea Faulds
>> http://ajf.me/
>>
>>
>>
>>
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
>
>
> --
> Xinchen Hui
> @Laruence
> http://www.laruence.com/
--
Xinchen Hui
@Laruence
http://www.laruence.com/