Browse by Tags

• Breaking Changes
• COM Programming
• Puzzles

• Chained user-defined explicit conversions in C#, Part Three

  Jeroen Frijters knew the answer to my challenge of last time: how is it that Foo foo = new Foo(); can cause a runtime conversion failure? And how is it that Bar bar = (Bar)(new Baz()); can succeed even if there is no user-defined conversion or built-in Read More... Posted Friday, April 20, 2007 7:00 AM by Eric Lippert | 2 Comments Filed under: COM Programming, C#, Puzzles, Conversions

• Chained user-defined explicit conversions in C#, Part Two

  Reader Larry Lard asks a follow-up question regarding the subject of Monday’s blog entry . Why is it that the compiler knows that (int)(new Base()) will always fail, and therefore makes the conversion illegal, but does not know that (Derived)(new Base()) Read More... Posted Wednesday, April 18, 2007 7:00 AM by Eric Lippert | 9 Comments Filed under: C#, Puzzles, Conversions

• Chained user-defined explicit conversions in C#

  Reader Niall asked me why the following code compiles but produces an exception at runtime: class Base {} class Derived : Base {} class Castable { public static explicit operator Base() { return new Base(); } } // ... Derived d = (Derived)(new Castable()); Read More... Posted Monday, April 16, 2007 7:00 AM by Eric Lippert | 8 Comments Filed under: C#, Breaking Changes, Conversions