More like all the On Error Resume Next statements. Which wasn’t even the worst thing about Visual Basic! VB also had the On Error Resume statement. On Error Resume Next at least moved on to the next line after an error occurred; On Error Resume just re-executed the error-generating line, I guess on the assumption that something would eventually change there.
I did BASIC on the Apple IIe, then TurboBasic, Visual Basic (3, 4, 5 and 6 with some C in there somewhere), VB.Net, C#, Java, Objective-C and finally QT. Now I drive a school bus.
Interesting to meet another person that went through the “GW-BASIC to Rust” journey. Mine was through FreeBasic and C++ in the middle but we ended up in the same neighbourhood.
This just confirms Twitter is a 1M line BASIC program.
Think of all the GOTOs
More like all the On Error Resume Next statements. Which wasn’t even the worst thing about Visual Basic! VB also had the On Error Resume statement. On Error Resume Next at least moved on to the next line after an error occurred; On Error Resume just re-executed the error-generating line, I guess on the assumption that something would eventually change there.
There would just be one of those, at the top of the 1 file…
On Error was used within a function, so you would have one (or more … or less) per function.
Oof indeed! After 40 years, I forgot it even had fns
I started with VB3, which didn’t have custom classes. I have no idea how I did anything back then, but at least it was better than TurboBasic.
I did years of gw-basic, then ms quickbasic, j++, java, c#, now rust.
I did BASIC on the Apple IIe, then TurboBasic, Visual Basic (3, 4, 5 and 6 with some C in there somewhere), VB.Net, C#, Java, Objective-C and finally QT. Now I drive a school bus.
Interesting to meet another person that went through the “GW-BASIC to Rust” journey. Mine was through FreeBasic and C++ in the middle but we ended up in the same neighbourhood.