On 18 February 2015 at 13:18, Rowan Collins <rowan.coll...@gmail.com> wrote: >> 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.
Of course, and some people may opt to avoid type hints altogether in their own code to avoid this, but they can't avoid changes to internal functions. How do we plan to release these incremental changes? We try and minimise BC as much as possible so a patch release might not be possible. Do we restrict it to minor versions, i.e. the yearly release schedule? >> 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. That's not really what I meant. So a user doesn't have to keep track of which internal functions are now typed and which are not, all functions should be typed at the same time, or none at all. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
