Tony Marston wrote on 10/03/2016 10:38:
"Rowan Collins" wrote in message news:56e0025c.5040...@gmail.com...
This leaves us back with a decision about *which* BC breaks are
acceptable, discussion of which includes how many people use the
feature, how it will affect them, and what the benefits are in the
particular case.
No BC breaks are acceptable unless it is for a valid reason, such as a
security issue or a performance issue. Changes in fashion are NOT a
good reason.
OK, so you've listed two reasons that should be accepted, and one that
shouldn't (which is something of a straw man, because I don't think
anyone would directly defend a proposal as "fashionable"). But that's
still not a full definition, as you acknowledge with your "such as".
So, remembering that a lot of this is YOUR opinion, and other people are
perfectly entitled to disagree with you, I would still be interested if
you could come up with a test that you would like applied for what is a
"valid reason" for a BC break. We can't really have a policy of "ask
Tony Marston if it's OK", so the only practical way forward is for us to
come up with such a test.
Scenarios to consider include: creating a new function (someone might
have created a custom function with that name); functionality that
depended on deprecated or unmaintained third-party code; replacing a
scenario that currently generates an error with working code.
Regards,
--
Rowan Collins
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
