Comment on C# to take a breaking change in version 5parentComments−solutionyogi14yWell, they are human after all.Overall, I feel that C# team has definitely achieved their goal of being a 'Pit of Success'. http://www.codinghorror.com/blog/2007/08/falling-into-the-pi...E.g. Order of evaluation is strictly defined as left to right in C#.http://blogs.msdn.com/b/ericlippert/archive/2008/05/23/prece...Disallowing use of uninitialized local variable.http://stackoverflow.com/questions/7797424/why-arent-unassig...C# warns you if you doif (i = 1) //notice the '=' instead of '==' {}warning CS0665: Assignment in conditional expression is always constant; did you mean to use == instead of = ?Obviously, they failed in the case of 'foreach' but I feel great knowing that they will be fixing it in the next release.
Comments
Well, they are human after all.
Overall, I feel that C# team has definitely achieved their goal of being a 'Pit of Success'. http://www.codinghorror.com/blog/2007/08/falling-into-the-pi...
E.g. Order of evaluation is strictly defined as left to right in C#.
http://blogs.msdn.com/b/ericlippert/archive/2008/05/23/prece...
Disallowing use of uninitialized local variable.
http://stackoverflow.com/questions/7797424/why-arent-unassig...
C# warns you if you do
if (i = 1) //notice the '=' instead of '==' {
}
warning CS0665: Assignment in conditional expression is always constant; did you mean to use == instead of = ?
Obviously, they failed in the case of 'foreach' but I feel great knowing that they will be fixing it in the next release.