Am 10.03.2016 um 16:44 schrieb Andrew Brown <browne...@gmail.com>: > as @Arvids said, var is missing functionality that public has, so they are > not exact aliases of each other. i think this is valid enough reason to > remove it.
To me this is reason enough to keep it. If your codebase does not care about visibility (and yes, I'm against forcing people to always use it) then I don't think it makes sense to enforce the 'bigger' public keyword instead of var. > even if it weren't the case, I would say let the language maintainers > decide if this cleanup would be worth it to them and make their lives > easier and their code more consistent, and userland developers (including > myself) be damned in 5+ years with this minor inconvenience. I think 5 > years is plenty of lead time to make this fix. How minor that BC break really is should be evaluated based on public PHP applications, e.g. a quick glance at Wordpress showed some usage of var. But if the majority of core people think that the benefit outweighs the cost then so be it. - Chris -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
