Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82411
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CABBJUpf=wKvGY9+xORRv6WVhCb5+LfRZXGYNasHFS=fz_mwaZQ@mail.gmail.com>
References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> <CABBJUpf=wKvGY9+xORRv6WVhCb5+LfRZXGYNasHFS=fz_mwaZQ@mail.gmail.com>
Date: Wed, 11 Feb 2015 11:45:18 +0800
Message-ID: <CABBJUpeceN1uDK870eV2=znC9f3eaxqYCmaEk0ErH2cbFxTNEw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
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 Wed, Feb 11, 2015 at 11:36 AM, Xinchen Hui <laruence@php.net> wrote:
> Hey:
>
>
> On Fri, Feb 6, 2015 at 4:14 AM, Andrea Faulds <ajf@ajf.me> wrote:
>> Good evening,
>>
>> At long last, I=E2=80=99m going to put the RFC to a vote. It=E2=80=99s b=
een 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 f=
ully. Please read the RFC in full: the details are important. And if  anyon=
e has any questions or uncertainties, please ask them before voting. I am v=
ery happy to answer them.
>>
>> I would urge everyone who wants type hints to vote for this RFC. It is n=
ot 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 typ=
ing, nor weak typing, on anyone who does not want it. It would allow the ad=
dition of type hints to existing codebases. It would not create a situation=
 where userland functions are strict yet internal functions are not, becaus=
e the strict mode affects both. I=E2=80=99ve tested the implementation myse=
lf on my own code, and it worked well, providing benefits other proposals w=
ould 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 (20=
15-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 RF=
Cs=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...

<?php

   include_one "lib/xxxx.php" // it use strict type

   declare(strict_types=3D0); //damned , restore it.


   $a =3D new B; // autoload, target file use strict type,

   declare(strict_types =3D 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/



--=20
Xinchen Hui
@Laruence
http://www.laruence.com/