103
[History] An editor letter by Edsger Dijkstra, titled: "go to statements considered harmful" (march 1968). (dl.acm.org)
submitted 2 years ago by to c/programming@programming.dev
58 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 2 years ago (1 child)

goto does have some uses, such as single exit point, but should be used sparingly.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Single exit point is an assembly rule that was mindlessly ported to C/C++. It doesn't make sense in a structured language.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Maybe for your use-cases, for mine i find it quite useful.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    I'll be very interested to hear more, do you have a blog?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    A common case is a function that uses resources like opening files, sockets, whatever. If there's an error you want to ensure a clean exit, so at different parts of said function you goto the end where you check if said resources are being used and release them before exiting.

    Cleaner than constantly checking at every error.

  • permalink
  • fedilink
  • source
  • parent