Post by zeeshan on Dec 21, 2013 6:56:50 GMT
I'm not trying to start an argument here, but for whatever reason it's typically stated that Visual Basic is case insensitive and C languages aren't (and somehow that is a good thing).
But here's my question: Where exactly is Visual Basic case insensitive? When I type...
...into the Visual Studio 2008 or Visual Studio 2010 IDE, the second one has a warning of "Local variable SS is already declared in the current block". In the VBA VBE, it doesn't immediately kick an error, but rather just auto-corrects the case.
Am I missing something here with this argument that Visual Basic is not case sensitive? (Also, if you know or care to answer, why would that be a bad thing?)
Why am I even asking this question?
I've used Visual Basic in many of its dialects for years now, sometimes as a hobbyist, sometimes for small business-related programs in a workgroup. As of the last six months, I've been working on a big project, much bigger than I anticipated. Much of the sample source code out there is in C#. I don't have any burning desire to learn C#, but if there are things I'm missing out on that C# offers that Visual Basic doesn't (an opposite would be VB.NET offers XML Literals), then I'd like to know more about that feature. So in this case, it's often argued that C languages are case sensitive and that's good and Visual Basic is case insensitive and that is bad. I'd like to know...
how exactly is Visual Basic case insensitive because every single example in the code editor becomes case sensititive (meaning case gets corrected) whether I want it or not and
is this compelling enough for me to consider moving to C# if VB.NET case is somehow limiting what I could do with code?
But here's my question: Where exactly is Visual Basic case insensitive? When I type...
Dim ss As String
Dim SS As String
...into the Visual Studio 2008 or Visual Studio 2010 IDE, the second one has a warning of "Local variable SS is already declared in the current block". In the VBA VBE, it doesn't immediately kick an error, but rather just auto-corrects the case.
Am I missing something here with this argument that Visual Basic is not case sensitive? (Also, if you know or care to answer, why would that be a bad thing?)
Why am I even asking this question?
I've used Visual Basic in many of its dialects for years now, sometimes as a hobbyist, sometimes for small business-related programs in a workgroup. As of the last six months, I've been working on a big project, much bigger than I anticipated. Much of the sample source code out there is in C#. I don't have any burning desire to learn C#, but if there are things I'm missing out on that C# offers that Visual Basic doesn't (an opposite would be VB.NET offers XML Literals), then I'd like to know more about that feature. So in this case, it's often argued that C languages are case sensitive and that's good and Visual Basic is case insensitive and that is bad. I'd like to know...
how exactly is Visual Basic case insensitive because every single example in the code editor becomes case sensititive (meaning case gets corrected) whether I want it or not and
is this compelling enough for me to consider moving to C# if VB.NET case is somehow limiting what I could do with code?