Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83063
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender)
Message-ID: <54E49135.60907@gmail.com>
Date: Wed, 18 Feb 2015 13:18:45 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAESVnVoZYiMWQk1Ydc-9wbkJo7Ru_4mrUtrubW=Rh=QKK9o8TA@mail.gmail.com> <CAPwsocFUF9WcTxc-BjmaCccdPbeYs5VgyDvqYbx=3cR-SwoPkg@mail.gmail.com>
In-Reply-To: <CAPwsocFUF9WcTxc-BjmaCccdPbeYs5VgyDvqYbx=3cR-SwoPkg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Scalar Type Hints v0.4
From: rowan.collins@gmail.com (Rowan Collins)

Leigh wrote on 18/02/2015 13:10:
>> 3b) Internal impact: Again, behavior remains unchanged unless the
>> >ZEND_ARG_INFO struct has been modified to add proper typehints.  If
>> >typehints have been added, then the more aggressive coersion rules
>> >apply during typehint validation.
> This leaves us in a state where some functions will have defined types
> with their aggressive coersion rules and some will not, and we can't
> expect users to remember which set of functions have been updated or
> not.
>

That's precisely the case for every existing user-defined function. 
Switching to PHP 7 won't suddenly add type hints to every function in 
every library and every existing bespoke code base, so there is no way 
to avoid that thought process.

> I think the rules need to apply to everything or nothing.

The rules will apply to everything in the same way - if a function is 
typehinted, it behaves like so; if it's not, it behaves the same way it 
did in PHP 5.

Regards,
-- 
Rowan Collins
[IMSoP]