On 2/4/07, Zeev Suraski <[EMAIL PROTECTED]> wrote:
One of the key guidelines of the language definition process of PHP was that we don't want multiple ways of doing the same thing, and we don't buy the argument of 'why do you care? you can still do it the other way'.
We already have many ways to do the same tasks. It is getting even worst as even some bugs require to use the other way to solve the problem (like with arrays and __get/__set, it sometimes requires to use ArrayObect and we even introduce a kind of breakage in 5.2.x...).
Only if the new way is significantly better than the old way of doing things (i.e. much faster / much simpler, etc.) we consider it. I think it's been a very good guideline and helped us a lot in keeping PHP relatively clean for a very long time.
It should have yes. And for most situations it did. But here we are talking about something asked since years and always rejected with the same arguments, despite a clear support from the community. We should organize a poll somewhere, I will be surprised to see a negative result.
I think we can live w/o it like we did in the last decade, but I feel strongly about not introducing it unless we also support [] as a replacement for list(). If [] works for arrays people would expect it to work for lists too. I guess my more accurate vote for that option would be +0 (and -1 in case it's only a replacement for array()).
It is impossible (holy BC) to replace array(), no question here :) --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
