Yeah, for sure "On Error Resume Next" is terrible. I did a conversion to C# of classic VB with COM Interop code. It's hard to convert into something current because of so many unhandled errors due to "On Error Resume Next". Sadly even the application's API interfacing examples in their documentation used it, so I can't blame the VB programmer.
VB was the first programming language I had seriously gotten into back in ~1996. In that respect, I see it fondly and wouldn't mind having a open source version of the language and IDE I could use to poke around some of my oldest projects. Though from every other aspect, I feel that the language is antiquated and there are much better options out there. Winforms.NET is just fine for graphical business applications, which I do a lot of in contacting situations. Just recently I was asked to convert around 20 classic VB projects into.NET. That was a quick reminder that the language could be easily abused and used to produce garbage code. The jewel of that project was a 5000 line program that was basically a single sub program loaded with goto statements, classic VB specific functions, and COM interop code.
Slashdot Mirror
Yeah, for sure "On Error Resume Next" is terrible. I did a conversion to C# of classic VB with COM Interop code. It's hard to convert into something current because of so many unhandled errors due to "On Error Resume Next". Sadly even the application's API interfacing examples in their documentation used it, so I can't blame the VB programmer.
VB was the first programming language I had seriously gotten into back in ~1996. In that respect, I see it fondly and wouldn't mind having a open source version of the language and IDE I could use to poke around some of my oldest projects. Though from every other aspect, I feel that the language is antiquated and there are much better options out there. Winforms .NET is just fine for graphical business applications, which I do a lot of in contacting situations. Just recently I was asked to convert around 20 classic VB projects into .NET. That was a quick reminder that the language could be easily abused and used to produce garbage code. The jewel of that project was a 5000 line program that was basically a single sub program loaded with goto statements, classic VB specific functions, and COM interop code.