|
I didn't read the post, but from the title, I understand your pain.
|
|
|
|
|
I assume that if it was Delphi your title would be "I hate Delphi, I hate Delphi & I HATE Delphi". If it was C++, C# or Java?
It looks like you are facing what I call "legacy mess" that does not necessarily translated to a specific language (OK, in your case is VB). Believe me, I feel the "pain", but on the other hand there are still a lot of companies (of any kind) that operate with legacy software (even VB) without a problem erroneous code.
I would say that the real tragedy is to see nowadays projects mimic "legacy styles" (including code and people) like the ones you try to deal with.
I wish you the best, in other words not to deal again with mess.
Cheers
|
|
|
|
|
It's just that if I was given the go ahead I could have written a scalable, neater version in C# quicker than this elephanting mess is taking...
|
|
|
|
|
I would rather sort out some bad VB than bad assembler.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
|
Yes On Error Resume Next and my favourite
On Error GoTo ErrorHandle
ErrorHandle:
'**** this (stars to make KSS safe)
Application.DoEvents
to quote Dave Borman 'My God It's Full of Stars'
|
|
|
|
|
Don't blame VB - it has it's rights...
The problem - IMHO - is that the developers(?) before you made wrong decisions and left you with a pile of sh...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
|
|
|
|
|
True, very true, but as I said above they have access to weaponry and VB (as far as I know) can't kill me!
|
|
|
|
|
Truly - the worst developer work is to renovate others code...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
|
|
|
|
|
I 'dunno, I kind of like VB. My career really got it's boost with VB6. Interestingly enough I still get projects where they want VB.NET or for VB6 application maintenance and I don't mind it.
But I admit with all of my new projects starts, I've been using C# for PC side development and have grown more comfortable with it.
It was broke, so I fixed it.
|
|
|
|
|
Point, when you were learning it was great. When you want something quick to try an idea it has a place. A production environment running a test rig, no, just no! VB like everything has its place...
|
|
|
|
|
glennPattonWork wrote: A production environment running a test rig, no, just no!
Why not? By the time the code is run, it is exactly the same CLR as a C# application (that is what puts the "common" in Common Language Runtime) executing exactly the same code in the .NET Framework.
Sloppy coding is sloppy coding, and C# can be as bad as, even worse than, VB.
|
|
|
|
|
Most my production VB code is still in use and have had little or no issues.
What issues do crop up they are generally having to do with adding features for new product, updating the UI of the applicationor changing test parameters. I've offered to rewrite them into C# code, but the answer is always, Why? If they still work, lets keep using them.
VB if coded well is a very viable platform to use, it's not just a "Starter" language although it does serve well in that capacity. The problem with VB is the ability to abuse some of the features, things like resume next and goto. But those features are great tools when debugging or running code that you know is incomplete. These have their place.
I've have seen some truly awfull code in C++, C#, assembly you name it. Any language can be abused it's not specific to VB.
It was broke, so I fixed it.
|
|
|
|
|
for the honesty. My career has followed a similar path. The 'legacy' VB6 applications still install and work fine on Windows 8, but most importantly, they continue to generate revenue in sales and support contracts. Like you, new projects are either C# or VB.NET.
"Go forth into the source" - Neal Morse
|
|
|
|
|
I use VB, and my code is as structured as C#. Any coder who is still relying on GOTO and other antiquated keywords deserves to be slapped down hard.
|
|
|
|
|
There is my point!
|
|
|
|
|
And yet, GOTO DOES have some valid uses.
In college, when learning COBOL, we were told there was only one valid use for GOTO.
Forget the details, but suffice to say that to avoid the use of GOTO for a particular type of COBOL application, the code size tripled.
Tim
|
|
|
|
|
Umm try coding any loop or call with out using a GOTO or JMP in assembly you can't...
|
|
|
|
|
Some languages need it. VB is not one of those languages. I've been coding in VB since VB4, and have never found a use for GOTO .
|
|
|
|
|
I've been writing VB code for more than 15 years, and I have never needed to use GOTO . Some languages, like COBOL, Fortran, Assembly, and older flavors of BASIC, needed the syntax. VB does not and never has.
|
|
|
|
|
I was raging against my coding problem more than the Language!
|
|
|
|
|
We already have ran a poll for it as well.
glennPattonWork wrote: being the last programmer to touch it all the blame will fall at my door even though the famous "well it was working when it was left with you", And yeah we all hate VB and my condolence with you.
Believe Yourself™
|
|
|
|
|
Speaking of Ini-Files. Make sure the INI-File IS NOT written in UTF-8. Windows can't handle UTF-8 ini files!!
|
|
|
|
|
No the elephant is plain ASCII text file so far...
|
|
|
|
|
Blame the programmer, not the language. That said, it is obvious, over and over again, that VB attracts the worst programmers. However, I've also perused the VB articles on CP here and am equally impressed with the code there as I am in say, the C# and C++ forums. And I also have the equal amount of rolling eyes as well.
Marc
|
|
|
|