On Sat, Feb 21, 2015 at 2:39 PM, Pavel Kouřil <pajou...@gmail.com> wrote:
> On Sat, Feb 21, 2015 at 11:25 PM, Zeev Suraski <z...@zend.com> wrote: > > There’s a fundamental difference between the two RFCs that goes beyond > > whether using a global INI setting and the other per-file setting. The > > fundamental difference is that the endgame of the Dual Mode RFC is having > > two modes – and whatever syntax we’ll add, will be with us forever; and > in > > the Coercive STH RFC – the endgame is a single mode with no INI entries, > > and opening the door to changing the rest of PHP to be consistent with > the > > same rule-set as well (implicit casts). The challenge with the Coercive > > STH RFC is figuring out the best transition strategy, but the endgame is > > superior IMHO. > > Hello, > > the two modes was something that I didn't like, at all, as a userland > developer. It seems really scary that decision to add 2 modes would > mean that every PHP code could have been written in any of these 2 > ways and it would stick forever with PHP, because removing it again if > it proved to be a bad feature would be IMHO really painful. > > So a single mode is infinitely better than 2 modes. > > Also, personally, I would prefer #1 or #2 version for internal > functions, but definitely without an INI switch. Not being able to > change it on some hostings could make development for the transition > period kinda painful. > > Regards > Pavel Kouril > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > As a userland developer I will chime in and say that I love this rfc better than the dual mode. In my opinion, having dual mode will put unnecessary cognitive burden on me especially when reading other people's code and libraries. While current rfc conversion rules are also different than what exists in PHP but I can get used to them and they are more in line with what should ideally be there (except contentious ones like bool). I will certainly love to see the type coercion rules being unified and slightly tightened up over time and this is a good first step for that. I am not a lang expert but of the languages I have learnt and developed in, I can't think of any that allow dual mode type coercion rules in such an explicit manner as the one proposed by Andrea/Anthony. Thanks Shashank
