this post was submitted on 19 May 2024
104 points (97.3% liked)

Programming

17378 readers
509 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

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
[–] stepan@lemmy.cafe 21 points 5 months ago (3 children)

TIL that C# and Java have a goto statement.

[–] leftzero@lemmynsfw.com 19 points 5 months ago (3 children)
[–] NaoPb@eviltoast.org 8 points 5 months ago (1 children)

Please don't link to medium articles. That page is terrible to visit.

[–] leftzero@lemmynsfw.com 2 points 5 months ago (1 children)

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

[–] NaoPb@eviltoast.org 1 points 5 months ago (1 children)

I'm running exactly the same and it doesn't look fine on my end.

[–] leftzero@lemmynsfw.com 1 points 5 months ago (1 children)

Huh. Maybe it's NoScript, then.

[–] NaoPb@eviltoast.org 2 points 5 months ago

Could be. I'm getting forced to make an account and such. That's why I hate medium.

[–] airbreather@lemmy.world 4 points 5 months ago (2 children)

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

[–] asyncrosaurus@programming.dev 3 points 5 months ago

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

[–] BatmanAoD@programming.dev 1 points 5 months ago* (last edited 5 months 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.

[–] BatmanAoD@programming.dev 2 points 5 months ago (1 children)

What...? That is a terrible idea.

[–] leftzero@lemmynsfw.com 1 points 5 months 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.

[–] atzanteol@sh.itjust.works 4 points 5 months ago* (last edited 5 months ago) (1 children)

Java doesn't. Well, it's a reserved keyword but it's not implemented.

[–] Carighan@lemmy.world 1 points 5 months ago (1 children)

Yeah but we got labels with continue and break, so we can pseudo goto.

[–] atzanteol@sh.itjust.works 1 points 5 months ago (1 children)

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".

[–] lmaydev@lemmy.world 1 points 3 months ago

If pretty much gets compiled to a goto statement. Well more a jumpif but same principle

[–] TehPers@beehaw.org 3 points 5 months ago* (last edited 5 months ago) (1 children)

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).

[–] asyncrosaurus@programming.dev 5 points 5 months 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.