Question

Recently I asked a question about how to clean up what I considered ugly code. One recommendation was to create an Extension Method that would perform the desired function and return back what I wanted. My first thought was ‘Great! How cool are Extensions…’ but after a little more thinking I am starting to have second thoughts about using Extensions…

My main concern is that it seems like Extensions are a custom ‘shortcut’ that can make it hard for other developers to follow. I understand using an Extension can help make the code syntax easier to read, but what about following the voice behind the curtain?

Take for example my previous questions code snippet:

if (entry.Properties['something'].Value != null)   attribs.something = entry.Properties['something'].Value.ToString(); 

Now replace it with an Extension:

public static class ObjectExtensions {     public static string NullSafeToString(this object obj)     {         return obj != null ? obj.ToString() : String.Empty;     } } 

and call using the syntax:

attribs.something = entry.Properties['something'].Value.NullSafeToString(); 

Definetely a handy way to go, but is it really worth the overhead of another class object? And what happens if someone wants to reuse my code snippet but doesn’t understand Extension? I could have just as easily used the syntax with the same result:

attribs.something = (entry.Properties['something'].Value ?? string.Empty).ToString() 

So I did a little digging and found a couple of articles that talked about the pros/cons of using Extensions. For those inclined have a look at the following links:

MSDN: Extension Methods

Extension Methods Best Practice

Extension Methods

I can’t really decide which is the better way to go. Custom Extensions that do what I want them to do or more displayed code to accomplish the same task? I would be really interested in learning what ‘real’ developers think about this topic…

Answer 1

Personally I think the ‘problems’ of extension method readability are vastly overstated. If you concentrate on making your code easy to read in terms of what it’s doing, that’s more important most of the time than how it’s doing it. If the developer wants to trace through and find out what’s actually happening behind the scenes, they can always click through to the implementation.

My main problem with extension methods is their discovery method – i.e. via a specified namespace instead of a specified class. That’s a different matter though 🙂

I’m not suggesting that you put in extension methods arbitrarily, but I would seriously consider how often you need to know how every expression in a method works vs skimming through it to see what it does in broader terms.

EDIT: Your use of terminology may be misleading you slightly. There’s no such thing as an ‘extension object’ – there are only ‘extension methods’ and they have to exist in static types. So you may need to introduce a new type but you’re not creating any more objects.