wrote in message news:56d86c00.6000...@fleshgrinder.com...
On 3/3/2016 10:34 AM, Tony Marston wrote:
If you want to avoid such confusion over alias names then surely that
would be an argument against introducing aliases in the first place. In
this case the short array syntax would never have been introduced as the
(only slightly longer) long array syntax had already existed since day
#1.
No, that is not what one should conclude from it. Short array syntax was
added by popular demand
Really? Exactly how many of the millions of PHP developers out there voted
for this change?
and hence for a very good reason. The fact that
there are no plans regarding the old syntax and thus keeping the
duplication indefinitely is the actual problem.
Is it actually a "problem"? How many books and articles on PHP programming
are out there which use the "old" syntax? How much confusion would it cause
if the "old" and well known syntax were to be dropped? How many applications
would suddenly stop working? How much effort would be required in userland
to fix this state of affairs? How many swear words would these userland
developers have for the language developers? There are NO sideeffects of
leaving aliases in the language. It would take NO effort to leave them in,
but it would take effort to take them out which includes updating immense
volumes of documentation. The only "problem" is that it offends the delicate
sensibilities of a few "purist" developers who cannot understand the
difference between improving the language and breaking it.
Change for the sake of change is bad, no argument there. Change for the
sake of progress is not and totally normal.
Only if it results in an actual and measurable improvement. Changes for
"purity" or "consistency" do NOT fall into this category.
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
