2 ms·
Few people asked for, or even wanted GOTO, yet that seemed to make it through with flying colors. When people would argue against it, the rationale was "well,
by mgkimsal 15y ago
Few people asked for, or even wanted GOTO, yet that seemed to make it through with flying colors. When people would argue against it, the rationale was "well, you don't have to use it!"
Why does the same criteria not apply to short array syntax? If you don't want to use it, don't use it, but hundreds of thousands of other people likely do want it.
FWIW, I first remember hearing about this in 2003/2004, and at that time I was against it for most of the same reasons I've read in opposition to adding it. Working outside of PHP for some time, I've come to realize the shortsightedness I labored under, and would fully love to have this.
I'm not 100% sure the votes on that page are from May 2011 - it's hard to tell for sure.
- jasonlotito 15y agoThe votes are old. The discussion has been raised again for 5.4 ( http://markmail.org/message/fx3brcm4ekh645se http://markmail.org/message/fx3brcm4ekh645se ) goto is a limited goto, and the reasoning for it's inclusion makes sense when you consider the other forms of limited goto already in place (breaks, cases, try/catches). It's not an unlimited goto.
- mgkimsal 15y agoThe wiki page would have diffused this entire post if it had the dates of the votes on it :) I understand GOTO, but the reaction to people who thought it was a bad idea was "don't use it!", ignoring the fact that whether we use it or not, we have to deal with other peoples' code that do use it.
- jasonlotito 15y agoYeah, but even the few people who do use it, it's implementation is limited, solving problems that would otherwise require excess code. The people shouting "don't use it!" are thinking of a limitless goto. It's a shame, but not surprising really.