5 ms·
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
by lou1306 3y 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.
- Shorel 3y ago"On Error Resume Next" never died, it just became serverless!
- rbanffy 3y ago“On Error Resume Next” is how C has always behaved.
- lou1306 3y agoWhat 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)
- rbanffy 3y agoI was more in the line of not checking whether you got a valid fd when you open a file and trying to use it nevertheless. In BASIC, when you try to open a file that’s not there, by default you get a runtime error and the program exits. If you do an “On Error Resume Next” the program will happily proceed with invalid data.
- Shorel 3y agosegmentation fault (core dumped)