News for hackers. Stuff that matters.
Re:IDEs we had 30 years ago by lou1306 on Tuesday January 02, 2024 @09:40AM (#38842061)
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)

Re:IDEs we had 30 years ago by rbanffy on Wednesday January 03, 2024 @01:17AM (#38851298)
I 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.