Showing posts with label C# Bloopers. Show all posts
Showing posts with label C# Bloopers. Show all posts
2013-02-21

C# Blooper №14: Weird / annoying interface method visibility rules.

›
Before reading any further, please read the disclaimer . As it turns out, an explicit interface method implementation in C# must be tied ...
2013-02-05

C# Blooper №13: Stack and Queue do not implement ICollection

›
Before reading any further, please read the disclaimer . This is a blooper of the Common Language Runtime (CLR), not of the language itse...
2013-01-25

C# Blooper №12: 'Where' constraints not included in method signatures

›
Before reading any further, please read the disclaimer . When writing generic methods in C#, it is possible to use the 'where' ke...
2013-01-14

C# Blooper №11: Zero to Enum conversion weirdness

›
Before reading any further, please read the disclaimer . When you assign an enum to int, you have to cast it. That's good. When you a...
2013-01-08

C# Blooper №10: Switch statements are not properly formatted.

›
Before reading any further, please read the disclaimer . This is rather a Microsoft Visual Studio blooper than a Microsoft C# blooper: Wh...
2013-01-07

C# Blooper №9: Annoying case statement fall-through rules.

›
Before reading any further, please read the disclaimer . Overall, C# takes an approach which is far more friendly to novice programmers t...
2013-01-04

C# Blooper №8: No warnings for conditions that are always true/false

›
Before reading any further, please read the disclaimer . The Microsoft C# compiler does not issue 'condition is always true' and ...

C# Blooper №7: No warnings about unused private methods.

›
Before reading any further, please read the disclaimer . If you have a private method which is never used, you will not be given a warnin...
2012-11-29

C# Blooper №6: No warnings about unused parameters.

›
Before reading any further, please read the disclaimer . One common mistake that programmers make is to forget to make use of a parameter...
3 comments:
2012-11-13

Why the Microsoft C# compiler lacks many useful warnings

›
As my C# Bloopers series of articles shows, the Microsoft C# compiler fails to issue many useful warnings which one would reasonably expec...
2012-11-12

C# Blooper №5: Lame/annoying variable scoping rules, Part 2

›
Before reading any further, please read the disclaimer . In light of the previous blooper , this one is more of a confusing error message...
1 comment:
2012-11-08

C# Blooper №4: Lame/annoying variable scoping rules, Part 1

›
Before reading any further, please read the disclaimer . A variable identifier is, of course, only visible within the scope in which it i...
2012-01-06

C# Blooper №3: No warnings about fields having already been initialized.

›
Before reading any further, please read the disclaimer . When you declare a member variable and you pre-initialize it at the same time, a...

C# Blooper №2: No warnings about accessing uninitialized members.

›
Before reading any further, please read the disclaimer . When you declare a member variable, and then you try to read it from within the ...
2011-12-31

C# Blooper №1: No warnings about uninitialized readonly members when the class is public and the member is public, protected or protected internal.

›
Before reading any further, please read the disclaimer . The C# compiler is kind enough to give you a "field is never assigned to...

C# Bloopers

›
Please do not get me wrong; C# is awesome. It is the language of my choice, even though I am pretty well versed in C++ and Java. That havin...