>> 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
