""François Laupretre"" wrote in message
news:018d01d03501$c0a877d0$41f96770$@tekwire.net...
De : a...@adamharvey.name [mailto:a...@adamharvey.name] De la part
I'm happy to update the manual, but I think I'd want more of a
consensus (not necessarily a formal RFC, but at least a straw poll)
for "soft deprecation" (to reuse the term we used for mysql_* before
it started generating E_DEPRECATED messages but was deprecated in the
manual) before making the change.
+1 to deprecate feature. I am generally favorable to BC but developers had
10 years to adapt to the new syntax and the change is trivial.
Why should we have to change our code to adapt to new syntax when the old
syntax has NEVER been marked as deprecated? Using this logic must we also
change our code to replace all occurrences of the old "long" syntax for
arrays with the new "short" syntax?
If we plan changes like this for php 7, we'll have to reconsider our
position on 5.7.
Users will never upgrade to any new version of PHP which does not contain
either bug fixes or new features. The proposal for 5.7 was for it to contain
nothing but a new set of deprecated notices.
François
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
