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.

  • realharo
    arrow-up
    14
    arrow-down
    0
    ·
    5 months ago
    link
    fedilink

    C is one of the few languages where using goto makes sense as a poor man’s local error/cleanup handler.

    • 42yeah
      arrow-up
      1
      arrow-down
      0
      ·
      5 months ago
      link
      fedilink

      Yeah. Without a proper error handling mechanism, goto is actually useful for once.

      • anti-idpol action
        arrow-up
        1
        arrow-down
        0
        ·
        5 months ago
        link
        fedilink

        Still don’t get why Go simultaneously picked this and introduced defer