|
DNALab ?! Any connection with the research in genetics ?!
|
|
|
|
|
No! It's a name made by Microsoft. Distributed Network Application === DNA...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
|
Option Strict Off. That is enough for me to hate it.
|
|
|
|
|
|
Then you can't like the dynamic keyword in C#.
|
|
|
|
|
Oh I don't like it. Too much typing. And I have seen some use it just because they can with no real purpose. Same treatment that var gets mostly.
|
|
|
|
|
d@nish wrote: Oh I don't like it. Too much No typing.
FTFY
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
Whenever I see var I have trouble dissociating it from the dreaded variant in the subject language, it still makes me shudder.
Some silly bugger used a GoTo in a stored proc the other day, the reaction was not pretty.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Some silly bugger used a GoTo in a stored proc the other day,
Almost forgivable. We have some in our C# code.
|
|
|
|
|
Shirley that's VB.net, VB6 had the wonderful Option Explicit . Where I used to work it was hanging offence to not include that one.
|
|
|
|
|
Don't forget Option Base [^], just to mess with anyone who tries to understand your arrays.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
As I always say Pete a good programmer can write bad code in any language.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Thank God! For a moment I thought you'd lost your mind. Everyone knows MicroFocus Cobol is second to none. Which is why it figures prominently on my resume.
/ravi
|
|
|
|
|
A short while ago (like one or two months ago) there was a TOP article here on CP explaining that VB6 is a great language that should come back. It got quite some upvotes too.
Just looked it up: Visual Basic 6.0: A giant more powerful than ever[^].
It even won VB article of the month.
I'm not saying it's a bad article, the author clearly put time and effort in it, and I refrained from voting. I WAS very surprised by the article and the amount of people agreeing with it though.
Thought you might have read it
|
|
|
|
|
What a bunch of crack smoking dullards!! I had to keep it kid sister safe...
|
|
|
|
|
I agree with you whole heartidly though
|
|
|
|
|
We still have many VB6 code around here (mostly batch and client legacy apps). The main reason behind is that the .NET framework is not installed on standard end user PC images.
The signature is in building process.. Please wait...
|
|
|
|
|
Doesn't .Net framework come with OS these days?
|
|
|
|
|
Depends on each image you create. Our System Admins just uncheck the .NET Framework option during install..
The signature is in building process.. Please wait...
|
|
|
|
|
vonb wrote: Our System Admins just uncheck the .NET Framework option during install.. You should then combat that with ClickOnce's prerequisite installers...
|
|
|
|
|
Like COBOL, VB6 is here to stay. More than 50% of business transactions are processed with COBOL and VB6. Some claim 70% and 80%.
|
|
|
|
|
I realise I may get flamed for this, and I am mentally prepared for it, but VB6 was not as bad as people make it out to be. Sure it was not the best language for much of anything, but it is not as bad as people make it out to be. .NET was far worse, and I would even go as far as to say that C# is more shoddy than VB6 ever was or ever will be.
Now before the flaming starts hear me out. I personally would class VB6 as an intermediary language, sure there was a lot more managed libraries than C++ will ever have, but the amount of managed code in VB6 pales in comparison to the amount of managed code in .NET or C#. As someone who has dabbled briefly into cryptography, managed code is the single largest bane of any language you can name. Unmanaged code also prods the coder to pay a hell of a lot more attention to what they are doing, to make sure they get things right, because getting anything wrong can lead to catastrophic failure, particularly in languages that have even less managed code libraries than VB6.
So is VB6 the best language ever? No, but there are certainly a significant amount of more "modern" languages around that are significantly worse.
Sure you could write some unsafe code in VB6, but if you are any good at it, you can write "unsafe code" that does the job it was written for, does it correctly, and is faster than the "managed code".
In short, before anyone starts ranting about how bad a language is, learn the compiler properly, learn the loop holes, the does and the don't. You'll be happier, more productive code monkeys. When speed and accuracy is of prime importance to your application, unmanaged code is king. Quit with the hand holding that are managed libraries and learn to code properly.
|
|
|
|
|
Seems like you wrote that trying to attract a flame. For most things managed code is 'coding properly', particularly with an intelligent garbage collection algorithm and large memory spaces. C#/.Net applications get very close in speed to a correctly coded C++ equivalent. An environment where "getting anything wrong can lead to catastrophic failure" is not better.
|
|
|
|
|
No it's not better, but it does teach you to be better coders because you are paying a lot more attention to what you are doing as opposed to letting the managed code do it for you. In many instances the managed code is also slower, see my cryptography example. But I do agree with you that managed code does suit most instances. I was being very specific with the example.
|
|
|
|