Programming

17504 readers

19 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 [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

104

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

submitted 6 months ago by [email protected] to c/programming

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

[–] [email protected] 4 points 6 months ago (2 children)

Java does not support goto.

[–] [email protected] 3 points 6 months ago

Well it has labeled breaks but that's the closest it gets to it.

[–] mrkite 3 points 6 months ago (3 children)

And yet it's still easy to write spaghetti code in Java. Just abuse inheritance. Where is this function implemented? No one knows but the compiler!

[–] 0x0 4 points 6 months ago

You mean SpaghettiFactory()

[–] [email protected] 3 points 6 months ago

And don't forget to use miracle sort for any sorting needs you have. Why do the work yourself when you can just hope it gets solved for you?!

[–] [email protected] 0 points 6 months ago

That doesn't make it spaghetti code though. In well-written OOP code you shouldn't care where a function is implemented. The problem is a much too high level of abstraction. If your high level code is so abstract that it is only running tasks and handling messages there's no way to write it in a way that prevents mistakes because you couldn't possibly know what the actual implementations do.