Letters to the editor: go to statement considered harmful | Communications of the ACM
dl.acm.org

In this letter, Dijkstra talks about readability and maintainability in a time where those topics were rarely talked about (1968). This letter was one of the main causes why modern programmers don’t have to trouble themselves with goto statements. Older languages like Java and C# still have a (discouraged) goto statement, because they (mindlessly) copied it from C, which (mindlessly) copied it from Assembly, but more modern languages like Swift and Kotlin don’t even have a goto statement anymore.

        • @leftzero
          2•1 month ago

          Looks fine on Firefox on Android with uBlock Origin. 🤷‍♂️

      • AirBreather
        4•1 month ago

        To be fair, await is a bit more like comefrom, and it’s been around for a few releases now.

        • @[email protected]
          2•1 month ago

          async/await was introduced in version 4.5, released 2012. More than a few releases at this point!

        • @[email protected]
          1•1 month ago

          How is await like comefrom, any more than threading is like comefrom? The variable context is preserved and you have no control over what is executed before the await returns.

        • @leftzero
          1•1 month ago

          It’s scary as fuck, yeah, but, to be fair, it’s only intended to be used by code generators, and it’s quite awkward to use outside of them.

        • @[email protected]English
          1•1 month ago

          Following that logic if, else and while are also “pseudo goto” statements.

          There’s nothing wrong with conditional jumps - we couldn’t program without them. The problem with goto specifically is that you can goto “anywhere”.

    • TehPersEnglish
      3•1 month ago

      In C# at least, goto can take you between case labels in a switch statement (rather than using fallthrough), which I don’t view as being nearly as bad. For example, you can do goto case 1 or goto default to jump to another case.

      The only other use of goto I find remotely tolerable is when paired with a labelled loop statement (like putting a label right before a for loop), but honestly Rust handles that far better with labelled loops (and labelled block expressions).

      • @[email protected]
        5•1 month ago

        I’ve programmed C# for nearly 15 years, and have used goto twice . Once to simplify an early break from a nested loop, essentially a nested continue. The second was to refactor a giant switch statement in a parser, essentially removing convoluted while loops, and just did a goto the start.

        It’s one of those things that almost should never be used, but the times it’s been needed, it removed a lot of silliness.