2015-03-12 11:23 GMT+02:00 Zeev Suraski <z...@zend.com>:
> > -----Original Message----- > > From: Bob Weinand [mailto:bobw...@hotmail.com] > > Sent: Thursday, March 12, 2015 12:46 AM > > To: Pierre Joye > > Cc: PHP internals > > Subject: Re: [PHP-DEV] [RFC] Basic Scalar Types > > > > Correct. It's just for the case where the other two fail. > > We still can add strict mode in a later version if people need it. > > All the RFC does is the most basic scalar type hinting you can build > everything > > on. (for example adding the declare(strict_types=1); would work without > any > > BC break on top of it) > > The issue is that it's only possible to open the voting on this one until > tomorrow. > > As I said, I do think we need *something* for 7.0. I went as far as > saying that I'd change my vote on the quite-bad-IMHO dual mode RFC to yes > if it seems both present proposals aren't going to succeed. But I would > much rather see this one pass over the dual mode if it was available for a > vote. > > So really, the options we have are: > > 1. Put this one for a vote before the end of tomorrow. Here too, on a > personal level, if I see that this proposal isn't gaining enough votes, > I'd support the dual mode one. > 2. Don't put it up for a vote, and then we may or may not have something > for 7.0. > > Zeev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > At this point I think the best way is to reserve the keywords for typehints, and not the only 4, but also for resource and null. And work towards making typehints in 7.1. Rushing things like it's now never lead to any good results. And that dual-mode RFC is re-incarnation of the register_globals, just in a different way. But essentially will make the same mess.
