If less code improves readability, then it's good.jackpf wrote:But surely you could do this instead:
Goto would use less code...but still, it's not necessary.Code: Select all
$break = false; while ($something && $break !== true) while($someother && $break !== true) if ($somecondition) $break = true;
I don't see what the big deal is... On the back-end, all if statements and loops are essentially goto statements anyway. Just cleaner. If goto statements were to be used for an entire project, then it would certainly make things look less organized. But, all of the examples that you guys have given mesh goto with current standards. If the existence of goto causes programmers to go back to our prehistoric roots of assembly, then it'd be negative.
However, open source is like democracy. If a policy helps some people and doesn't affect the opposition, there's no reason to deny the policy. This can be seen in desegregation, women's rights, and eventually gay marriage.
See that? GOTO statements = gay marriage. Who'da thought?