On Wednesday, March 11, 2015, Bob Weinand <bobw...@hotmail.com> wrote: >> Am 11.03.2015 um 23:29 schrieb Pavel Kouřil <pajou...@gmail.com>: >> >>>> It shouldn't prevent any future improvements and still give use all the >>> advantages of scalar types. >>> >>> Besides what I think of proposing yet another RFC, -1 because it is >>> basically what the initial idea from the opponents of optional strict mode >>> wanted before they go with the latest one. It also totally ignore what the >>> Anthony's proposes. >>> >> >> Hello, >> >> I'd say that this is definitely better than the dual mode RFC, but >> worse than the coercive one - I can't find a single reason why some >> modes switch should be good. I can only see negative outcomes from >> this, and a painful experience when developing with PHP in the long >> run as a userland developer. >> >> Basically goes with what I've been saying from the beggining of the >> introduction of the "dual mode" - I don't care if strong or weak >> typing wins, but I want only on in the language. PHP is inconsistent, >> there's no need to make even more inconsistencies and stuff. >> >> Regards >> Pavel Kouril > > It's not worse than the coercive one. It's just doing less. It doesn't change ZPP. > We always still can change ZPP later in future. > > If you like the coercive one, you also should like this one. > > Bob
Yeah, I like this one - but I slightly prefer the coercive one. I feel like this one is just too weak (yes, because it doesn't change the ZPP), but it is still better than no hints at all - and infinitely better than introducing two modes. Hopefully you understand my POV now. :) Regards Pavel Kouřil
