Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80533
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <7B5C883B-E8FE-489A-B1E2-EAD6722544C8@ajf.me>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> <CA+9eiLsOgM4qTTG9VfeWZm1wki9D7a-4Y4TiiqQJZE2Ym8sXcg@mail.gmail.com>
 <7B5C883B-E8FE-489A-B1E2-EAD6722544C8@ajf.me>
Date: Thu, 15 Jan 2015 19:36:29 +0800
Message-ID: <CABBJUpdbOX7SXsiso=GFJ-+08isPG9ZnzKUGcpiQhF1xN57eFw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Dmitry Stogov <dmitry@zend.com>, PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: laruence@php.net (Xinchen Hui)

Hey:

On Thu, Jan 15, 2015 at 6:42 AM, Andrea Faulds <ajf@ajf.me> wrote:
> Hey Dmitry,
>
>> On 14 Jan 2015, at 20:40, Dmitry Stogov <dmitry@zend.com> wrote:
>>
>> In my opinion, version 0.1 was consistent enough.
>>
>> handling two different approaches just makes mess...
>>
>> We have internal function strlen(string $s), and it may be called with i=
nteger argument e.g. strlen(123) -> 3
>> I think user functions should follow the same rules.
>
> This RFC does that. In the =E2=80=9Cweak=E2=80=9D mode that would continu=
e work, and it would also for userland functions with scalar type hints. In=
 the =E2=80=9Cstrict=E2=80=9D mode that would break, and it would also brea=
k for a similar userland function with a scalar type hint.
sounds like a hell to me.....

sorry for saying that, but I don't like the whole "declare" thing...

could we please strict to v0.1, only make it first ?

thanks
>
>>
>> If some rules are "bad", lets change that rules for both internal and us=
er functions.
>> But it's better to do it in a separate RFC (after scalar type hinting 0.=
1 accepted), or we will stick forever.
>
> I=E2=80=99m not sure the weak typing approach to function parameters is b=
ad per se, but a lot of developers would certainly prefer the strict typing=
 approach. That=E2=80=99s why the RFC allows choice: for all the people tha=
t weak typing works for, good, you can keep using that. The people who want=
 strict typing get strict typing without forcing the people who want weak t=
yping to use it.
>
> 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/