Why is it inexperienced programmers go through a phase where they think goto is evil incarnate? I wish Dijkstra had never written that damn paper.
They can be described with if, while, for, case, pattern matching, recursion, etc. There is almost always a better alternative.
>Why is it inexperienced programmers go through a phase where they think goto is evil incarnate?
It seems to me that most people who support general usage of GOTO are inexperienced and don't necessarily realize it. They lack knowledge of better control structures. See the blub paradox.
Besides, the justification here is performance, not readability. I'm saying that performance in particular is a bad justification for using GOTO.
>> "Why is it inexperienced programmers go through a phase where they think goto is evil incarnate? I wish Dijkstra had never written that damn paper."
You seem to be referencing my comments. I'm not inexperienced, and I don't think goto is evil incarnate. I do believe that optimizing for individual CPU cycles in PHP is generally pointless.