Programming

17408 readers

74 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

104

[History] An editor letter by Edsger Dijkstra, titled: "go to statements considered harmful" (march 1968). (dl.acm.org)

submitted 5 months ago by abbadon420@lemm.ee 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

[–] huginn@feddit.it 2 points 5 months ago (1 children)

There's a solid reason for goto in C.

Bringing goto into Java was (and is) idiotic.

If you're trying to squeeze every ounce of performance out of your code then you'll need those optimizations.

But any higher level language than C the entire point is to write easily maintainable and useful code that any idiot can go, read and update. A goto is antithetical to readability.

[–] ggppjj@lemmy.world 1 points 5 months ago

It can be, sure. But when used in a limited manner where it makes sense it can be the more readable option. I've used it in a try/catch to retry the operation after changing a variable. One label ("reconnect"), one goto, totally easy to understand on a surface level.