Comment by lou1306

2 years ago

Well, a language that allows something like "On Error Resume Next" is not that great by any definition of the word...

Having said that, I must also say that I started coding on VB6 and if I had to show some elemetary programming to a ~10-yo, I'd give them something like QB64 in a heartbeat. There's something good in grappling with a "bad" language, educationally speaking.

5 comments

lou1306

Reply
Shorel  2 years ago

"On Error Resume Next" never died, it just became serverless!

  • rbanffy  2 years ago

    “On Error Resume Next” is how C has always behaved.

    • lou1306  2 years ago

      What do you mean? I thought runtime errors in C were almost always catastrophic; the real issue is UB (first example that comes to mind is out-of-bound array access; sometimes you segfault sometimes you just get random data) or, in general, stuff that should be an error but isn't

      EDIT: Ah I guess you were referring to arbitrary code injection after, say, a stack overflow? But I think that's a runtime issue rather than a language one (hard to draw a line in a systems PL, but still)

      1 reply →