|
I even make use of it! In switch statements where two or more alternatives have the same (final) handling, it can be really useful, and far safer than the silent fallthrough of classical C (which is not allowed in C#).
It lacks a builtin ComeFrom, though; I had to implement that myself. It really is a must when you do more than the elementary exception handling.If you leave the stack dump to the standard library exception handling, you won't be able to pick up the output and process it in a reasonable way.
Of course you can't make a ComeFrom without support from the runtime libary. Given the StackTrace / StackFrame classes, it is trivial.
|
|
|
|
|
And so you see - everything has it use 
|
|
|
|
|
Richard Deeming wrote: IMO, there shouldn't even be an option to turn them off.)
All of this is presuming that VB should be allowed to exist in the first place.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Then stop financing its makers - oh wait, they build C# too ....
Oh wait again - its even the same compiler and toolset ....
|
|
|
|
|
I did stop funding them. The last thing I bought from Microsoft was a MSDN subscription a number of years ago. That got me Windows 7 and VS2013. Recently, I migrated almost completely away from Microsoft at home. I still have a VM running Win7 so I can write Windows code with VS2017 community), but that's it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Then there is only one thing left to do: find a job where you don't have to work with Microsoft either. If I see your rant, it would be really better for your heart.
|
|
|
|
|
VB pile of crap? Really? Funny how we see things. When I look at all the {{{{{}}}}} and ;;;;;;;;; in other languages, I feel sorry for all that syntax crap they have been born with. A lot of people like that sh*t though, so it must be some sweet crap..
Functionality wise, VB and C# for example visite the same barbershop to get their new identical look, ready to be swallowed up by the machine. So if you are not talking about syntax, then C# is in this case a pile of crap too. I doubt that.
|
|
|
|
|
When converting stringly typed data from a flat file into strongly typed data for database storage, nothing beats the built in conversion functions found in VB. In addition, VB.net's verboseness means I can look at the header of a function and know exactly what events and what objects those events tie to. In C# this wire-up is frequently hidden in another source file. Having keyword based blocking vs. {} for block controls also helps when working out the logical structure of code. Is that } going to the "if" or the "while" statement 30 lines up? In VB you'll see an End If or Loop so you don't have to guess when looking at the code on paper. Granted, VS's indent lines make this less of an issue now but prior to those indent lines it was an issue.
Where C#'s syntax is better is in the implementation of Lambda (anonymous) functions and LINQ syntax. VB.Net's syntax is just awkward here. I also prefer C#'s <> for type declarations for Dictionaries and Lists as it highlights the actual typing without making the New parameters confusing.
|
|
|
|
|
After using VB.Net for around 8 years, I have been using C#.Net exclusively for the past 5. There are two things I very much still miss about VB.Net - the first of which are those oh-so-hated-by-everyone-else verbose blocking keywords. ESPECIALLY when working at the end of a function or class...
[ Next / End If / End Select / End With / End Function ] is instantly easier to understand which blocks you are leaving, than [ }}}}} ] - even when on separate lines.
The second is the [ My. ] class - so much exposure to the underlying environment, user profile, settings, and resources... all in one API.
At the end of the day, I use C# just to keep fluent in what is arguably the more-widely-used language of the two, but I very much miss the good ol' days.
|
|
|
|
|
It takes manure to make things grow. Have you ever worked in VB? If not How can you criticize something you don't use? 
tired of the VB bashers …..
|
|
|
|
|
In point of fact, I've worked in every evil incarnation of it, but more importantly, I've worked with better languages, so I know from where I speak.
Even if I hadn't, I'm old, so I'm entitled to criticize anything I want.
Oh, and you can use your cute little disappointment emoji till the cows come home. I don't give two sh|ts about it. (I can say that because I'm old, too.)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
You are not the only "Old Guy". I am 70 in a few months. I have been working in Basic (GW-Basic) since 1978. I have made a very good living with it, and have happy clients running their businesses all over the Southeast and Central U.S. with my programs.
Being "Old" does not entitle you to anything, except the knowledge you will die soon. The emoji was for you, because you sound like a fan-boy millennial in your post.
BTW, I am converting my programs to C#, and have found it is more verbose,and does not handle Dates worth a cr@p. I'm doing that so when I finally drop dead at the keyboard, my clients will be able to find one of the younger guys around that know C# to support them. I notice you failed to mention any of the so-called "better" languages you work in. I'd be interested to know what language/framework du-jour you currently like.
Get over it, it's all just syntax, in the final analysis. The tool you use is not important, only the product you create
Oy! Haters gonna hate.
|
|
|
|
|
why do you think it's crap? is this from personal experience or is from from what others say it is?
from my personal experience (and i do have quite a few languages that i use from day to day) it's on par but not equal to C#, VB.net does somethings better than C# and vice versa. and at the end of the day they both compile down to the same IL.
i could say javascript is crap because it's an interpenetrated language and other reasons, but it does serve a purpose and does it well, so i wont.
|
|
|
|
|
Matt McGuire wrote: why do you think it's crap?
Because of the first two letters in its name. I thought I' made that clear.
Matt McGuire wrote: i could say javascript is crap
And I don't personally know a single person that would argue with you on that point.
Matt McGuire wrote: but it does serve a purpose
Only because we let it serve a purpose.
Y'all really need to stop arguing the point. It's crap, and I absolutely won't change my mind.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I used to be like you years ago, but after a couple decades of coding, i have learned to be more flexible in what i use to get the job done.
John Simmons / outlaw programmer wrote: Because of the first two letters in its name. I thought I' made that clear.
by the sound of it, you haven't used it, or at least not enough to see some of the benefits that VB.net offers that differentiates it from C#.
C# and VB.net are both good languages, and they both have their strengths and weaknesses. I use them both, and ADA, javascript, c, c++, D, Rust,HTML and a few others i dabble in; they all have their own uses.
if you want to bash on VB6 go for it, that should have died over 10 years ago. but VB.net is not VB6
|
|
|
|
|
Matt McGuire wrote: by the sound of it, you haven't used it, or at least not enough to see some of the benefits that VB.net offers that differentiates it from C#.
Once again, and for the last time, I *HAVE* used VB.Net, and it is still crap, just like it's predecessor, VB6.
Matt McGuire wrote: if you want to bash on VB6 go for it,
I suppose I could equate that with "divine dispensation", but I didn't need it to start with.
VB apologists make me laugh out-f*ckin-loud...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Look I'm not here to convince you otherwise, you have your standpoint and i will respect that, even if i don't agree with it.
My only request is to not bash on others for their personal preferences. if there was constructive criticism over a language feature, I have no issue with, but to say something is just "crap" is not helpful and will lead to angering others for no purpose what so ever.
|
|
|
|
|
VB is used in-house, making the software carrying the company forward.
C-ish languages used by experts, for boxed software, and for contractor work, carrying their company forward.
|
|
|
|
|
I would debate that, this stems from the old long debate of VB6 vs. C++.
I use to develop industrial control systems that controlled directly to the IO with VB.Net and had several hundred installations. the difference between c# and vb.net is not a lot. both are good languages, and both had good features, both have their own benefits, what it actually comes down to is do you prefer "{}" or "if, end if"; it still compiles down to the same IL.
|
|
|
|
|
13 is the age when one should be moving from VB to a programming language. No later than puberty.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Boom tish!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
VB is OK as long as you still work in your parents' basement.
|
|
|
|
|
This thread is about VB.NET, which can express virtually everything that C# can express, albeit with a wordier syntax.
Do you mean that C# is not a real programming language?
Or do you mean that VB6 / VBA is not a real programming language (which I could get behind, if not entirely agree with)?
|
|
|
|
|
I'd have to argue that VBA is a real programming language, but that it's limited by the host application. VBA in Excel is extremely powerful. VBA in Word has been lobotomized.
VB6 was good for what it was intended to do and represents a completely different era of Windows programming.
|
|
|
|
|
You mean the Excel and Word object models, respectively. You can easily access the Word object model from Excel, and the Excel object model from Word. You can also access both object models from an external program/script -- .NET languages, Python, VBScript, JScript and others. I think the limitations of these object models are independent of the language.
VBA (and VB6) is limited in that it doesn't have a first-class-function mechanism (AddressOf doesn't count, as AFAICT there is no way to call such a function pointer from VBA), nor does it have a lambda function syntax. This means that LINQ/FP-style data processing is impossible in VBA/VB6, and filtering / sorting / projecting any collection of data involves nested For Each and conditional blocks.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
