Greg Young [MVP]

One of the annoying syntax thing for me in C# is the class / ctor syntax.

Public class MyClass

{

  public MyClass(){}

}

Why do I need to type "MyClass" twice? (or 3 times, or 10 times).

(Prior to C# 3, the most annoying syntax for me was Property Accessors. Talk about excessive typing for no good reason!)

Molasses eh... Let's see. I dislike inline anonymous delegates in method calls. Seeing "})" just looks strange.

I also dislike full syntax for lambdas (no type inference).

I absolutely hate that  {} is required for single line try/catch.

And, finally, why the heck do I have to break out of the last block in a switch.

How about:

TypeOfEnum enumValue = (TypeOfEnum) Enum.Parse(typeof(TypeOfEnum), someValue);

and I really want hashtables to be prettier:

Dictionary<string, string> d = new Dictionary<string, string>();javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("ctl00$ctl00$ctl00$bcr$bcr$bcr$ctl14$ctl02$ctl02$ctl02$btnSubmit", "", true, "CreateCommentForm", "", false, true))

Add

d.Add("blah", blah");

d.Add("blah2", blah2");

CallSomeMethod(d);

... as opposed to something more boo-like:

CallSomeMethod({"blah": "blah", "blah2" : "blah2"});

I see 'syntactical molasses' every day, but it's not the language's fault. No matter what they tell you, it's a people problem, right ?

Sure, some languages are more verbose than others (in my personal experience, Java was the most verbose I ever encountered), but it's up to the developers to make good or bad use of the language. No ?

Indeed, WRT "break".  If the language will give me an error that the break is missing, it knows exactly where it should be; so I don't need it.  It's not like C++ where you can fall through to the next case...

Similar to "Error: missilng semicolon".  Well, then put the damn semicolon in then!

Generics can get pretty sticky when you have anything that might be nested. Like if you find yourself in this situation:

Dictionary<string, IList<IItem>> itemDict = new Dictionary<string,IList<IItem>>();

My favorite was the "toArray" method of ArrayList.

www.lazycoder.com/.../arraylisttoarray

"That’s ok, but now you have an ArrayList, not an array of type “Group”. Luckily you can use the ToArray() method of the ArrayList class to convert it to a Group array. There is a catch though. Even though you pass in a type (”Group”) it returns an array of objects. You need to explicitly cast it as the type you want the array to be of.

arGroups = (Group[]) listGroups.ToArray(typeof(Group));

"

Generics killed this little bit of heaven.

I found myself doing this one day:

List<ITrans> list = new List<ITrans>();

double sum = 0;

list.ForEach(delegate(ITran t) { sum += t.Amount; });

Then slapped myself and changed it to use a real for loop.