On Fri, Feb 6, 2015 at 6:22 AM, Andi Gutmans <[email protected]> wrote:
> I have to say I’m pretty disappointed at the opening of the vote.
> We had a pretty good RFC (thank you) for weak type hinting which was aligned with the spirit of
> PHP and everyone was able to rally around it.
> This has now been morphed into something very hard to swallow and IMO having such a
> declare(…) syntax will be ridiculed by the broader app dev community until the end of time… But
> even that syntax aside (it’s only syntax after all), I think we lost the ability to reach
> consensus on something so important to everyone which we haven’t been able to come to agreement on
> for over 10 years. Finally it was there, in reach and you made a 180 degree turn.
> I think it’d be so much easier for us to implement weak type hinting. Have everyone rally
> around it. Be happy and then learn and see whether an additional mechanism is really necessary. We
> could even add an E_STRICT_TYPES error_reporting flag to help folks “debug” their code if they
> so wish to see if there are any hotspots in their code they may want to take a look at - again not
> necessarily an error but maybe a debugging tool.
>
> But net, net - why not just implement the thing everyone can agree on. Have something really
> good in the spirit of the PHP Language for PHP 7 and learn how people leverage that… The reality
> is that for the majority of the Web community “1” coming in from HTTP should be accepted as a 1.
> Period.
>
> I voted “no” but I will vote “yes” for the competing RFC which is 80% of your RFC. Why
> are we not given that option??????
I have to agree here while I like the declare option, it should have
been an option as we clearly do not have a consensus during the
discussions (and will never have). Jeopardize the whole because of
that sounds dangerous to me.