wrote in message news:56d5dda6.4080...@fleshgrinder.com...
On 3/1/2016 6:34 PM, Rowan Collins wrote:
Rowan Collins wrote on 01/03/2016 11:33:
Secondly, violating visibility may have repercussions outside actual
errors.
Incidentally, PHP itself encountered this a few years ago, where a
release of libxml2 changed internal behaviour that was being relied on
for a hack. The result was that entities like > started silently
disappearing from everyone's parsed XML if they compiled PHP against the
new library. See https://bugs.php.net/bug.php?id=45996 and
http://thread.gmane.org/gmane.comp.gnome.lib.xml.general/14610
Regards,
The misuse of "var" as it was explained is reason alone to take action.
Just because one developer out of millions made a mistake is no reason to
punish those millions.
If "var" can be abused then "public" can be abused in the same way, so
surely the only way to avoid the possibility of ANY abuse whatsoever would
be to remove "public" as well as "var".
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
