c# case insensitivity - it's fine as it is, it comes from c and c++ , if you have only one way to write a variable name ,you can enfoce coding conventions while compiling.
Automatic creation of "()" braces - that's beacuse you are coming from vb ;) - it makes no sense to write methods calls without braces it looks ugly.
With - it an ugly construct , I hate it it doesn't look readable. and besides if your code calls many properities at the same time maybe you need to design your classes again.
Yosi:
- Insensitivity: Why should I be able to write basically the same variable name with only case differences? That's just giving us enough rope to hang ourselvss with.. and you *know* that its a common practice in a lot of places, although its not a good one.. Hell, even I used it at times, because its more convenient than readable..
braces - Not saying that no braces is good, just saying that saving me the trouble to write them wil save me about 20% of coding time... hows that for a productivity increase?
With - Ugly? now *that's* because you came from a non-VB background ;) its one of the most useful, time saving, readable, productivity enhancing code constructs I've met, and I can't think of how I could totally get rid of the need for it no matter how good I design my copmonents. sometimes you just *have* code that calls or sets multiple properties on a componenet in one method.
I think case sensitivity is a huge strength! It makes your code much cleaner, and naming conventions much cleaner.
For example, in C#
you can declare
MyClass myClass = new MyClass();
while in VB you would have to do something like
Dim [myClass] as New MyClass()
I consider it to be a strength, much more than a weakness.
dave: that's exactly the kind of code that I believe should be avoided. It's much more confusing to readf by a 3rd party, and although easy to create and looks cleaner- but is harder to maintain.
If all those things were in both languages, why would you need to. I think they are great the way they are and PLEASE LEAVE THE CASE-SENSITIVITY in C#.
That was #1, 3, and 4 on "his" list...
I had vs 2003 installed, but the only "edit & continue " like feature was that once you edited, you couldn't continue...
You're telling me that "Tools-> Options-> Edit and Continue-> Changes in VB and C# Code-> Allow me to Edit C# Files While Editing" does not work for you?
hmm... getting rid of case insensitivity in C# may make a lot of sensitive C# programmers insensitive...
sorry had to put that one in 8-)
What does case insensitivity buy you other than less maintainable code? :)
Tim: I would think just the opposite - insensitivity "blocks" the same variable name from appearing twice in the same scope with different casing. Allowing *that* could lead to harder to maintain code...
Chad: I agree. It should have said "Missing IDE enhancements for language 'X'"
As for QuickCode - It's pretty cool, I just wanted to air out the fact that I shhouldn't need to use such a tool to get that sort of functionality from the world's most advanced IDE to date..
Aaron: 'using' not does allow me to write something like this:
using(thins)
{
.MyProperty= "something";
}
Roy, if there ever was a stereotypical VB programmer to be singled out as an example, it would be you. Absolutely no understanding of why things aren't all like VB. This post was enough to put me off reading your blog for good. Unsubscribed.
Oisin: Ouch. Sorry you feel that way.I have lots to say about that , so I'll write a post about it.