base-class-library

If the statement above is correct, then why when I use reflector on .Net BCL I see it is used a lot? EDIT: let me rephrase: are all the GO-TO's I see in reflector written by humans or compilers? The above isn't really correct - it was a polemical device used by Dijkstra at a time when gotos were about the only flow control structure in use. In fact, several people have produced rebuttals, including Knuth's classic "Structured Programming Using Goto" paper (title from memory). And there are some situations (error handling, state machines) where gotos can produce clearer code (IMHO), than the

I am using CodeDOM to create an in-memory assembly at run time like so: public Assembly Compile(CodeCompileUnit targetUnit) { string path = Path.GetDirectoryName(new Uri(Assembly.GetExecutingAssembly().CodeBase).AbsolutePath); var compilerParameters = new CompilerParameters { GenerateInMemory = true, IncludeDebugInformation = true, TreatWarningsAsErrors = true, WarningLevel = 4, CompilerOptions = "/nostdlib", }; //For system.dll compilerParameters.ReferencedAssemblies.Add(typeof(System.Diagnostics.Debug).Assembly.Location); //For system.core.dll compilerParameters.ReferencedAssemblies.Add

An example would be: XNamespace ns = "my namespace" Why not?: XNamespace ns = new XNamespace ( "my namespace" ) What's the idea behind using implicit/explicit convertions instead of constructors? Convenience? Is there a guideline for this? Convenience? More or less, yes. Consider the case for when you’ve got a number-like object (say, a Complex ) on which you do calculations. Clearly, writing code such as: Complex result = c1 * new Complex(2) + new Complex(32); is very annoying and hard to read. Implicit conversions help here (an alternative would be operator overloads in this example, but

There are several places in BCL where one can make use of IEqualityComparer . Like Enumerable.Contains or Dictionary Constructor . I can provide my comparer if I'm not happy with the default one. Sometimes I want to know whether the collection contains that very object that I have reference to. Not the one that is considered "equal" in any other meaning. The question is: whether there exists standard equality comparer in the BCL that relies only on ReferenceEquals method? The one that I wrote myself is this: class ReferenceComparer<T> : IEqualityComparer<T> where T : class { private static