You might have had the anti boxing and unboxing rhetoric pounded into your head.
In the .NET world they’re often mentioned as an unfortunate side-effect of backwards compatibility. A reminder of life before generics…
…before Linq. *shudder*
Let’s take a look at 7 of the reasons why programmers beat up on boxing. [Read more…]
There used to have a wonderful series of “What If?” comics that pondered a few of the important hypothetical questions in the Marvel universe.
We talked about a few of the limitations of interfaces in C# on episode 1, and I wanted to provide a few examples of what we were on about with this fun little twist.
Let’s see what it could look if interfaces, static classes, and anonymous classes supported constructors and some theoretical workarounds for these limitations. [Read more…]
During Episode 1, we discussed the pitfalls of using explicit interface method implementations. I’ve put this article together to illustrate some of the confusing scenarios. The intent of this article isn’t to illustrate all of the pitfalls, but instead to illustrate enough to help explain why explicit interface method implementations should be carefully considered before use. [Read more…]
We programmers tend to have a few OCD qualities and there are a few things about C# interface naming conventions that we talked during episode 1 of the podcast about I’d like to whine about discuss.
Interfaces are a powerful piece of object oriented programming that is often overlooked. In this, the very first episode of Coding Blocks the Podcast, we discuss many of the things you should know about interfaces.
To help follow along with the podcast, here are some code snippets to explain some of the conversation. In regards to Joe’s statement about interfaces being like guard rails on a highway, putting some code snippets in here should give some context and greater understanding. [Read more…]
