Skip to main content

C# Tutorial - Optional and Named Arguments [Beginner]


When C# 4.0 was released, developers got their hands on some syntactic sugar that helps in the readability and maintainability of code - optional arguments and named arguments.

Optional Arguments

The first concept we'll be looking at today is optional arguments. Let's use optional arguments to help a common maintainability issue - adding another argument to a function. Here's a really basic method that we'll be extending.
public void MyFunction(int a)
{
  Console.WriteLine("Parameter a is: {0}", a);
}

...

MyFunction(3);
// Output: Parameter a is: 3
 
At some point in the future, as often happens, a developer decides MyFunction needs to do a little more and needs another argument.
public void MyFunction(int a, int b)
{
  Console.WriteLine(a);
  Console.WriteLine(b);
}
 
This introduces a maintainability problem - everywhere that MyFunction is called now needs to supply another argument. What the developer can do instead is assign argument "b" a default value.
public void MyFunction(int a, int b = 4)
{
  Console.WriteLine("Parameter a is: {0}", a);
  Console.WriteLine("Parameter b is: {0}", b);
}

...

MyFunction(3);
// Output: Parameter a is: 3
// Output: Parameter b is: 4
 
With the use of optional parameters none of the calling code needs to change, and the developer can be at least a little more confident that she didn't break existing code.

There's no limit to the types that can be used in optional parameters. Let's extend our method again by adding an optional string parameter.
public void MyFunction(int a, int b = 4, string c = "foo")
{
  Console.WriteLine("Parameter a is: {0}", a);
  Console.WriteLine("Parameter b is: {0}", b);
  Console.WriteLine("Parameter c is: {0}", c);
}
 
This function can now be called three different ways.
MyFunction(3);
// Output: Parameter a is: 3
// Output: Parameter b is: 4
// Output: Parameter c is: foo

MyFunction(3, 5);
// Output: Parameter a is: 3
// Output: Parameter b is: 5
// Output: Parameter c is: foo

MyFunction(3, 5, "bar");
// Output: Parameter a is: 3
// Output: Parameter b is: 5
// Output: Parameter c is: bar
 
So now what happens if a caller wants to use MyFunction and only supply values for "a" and "c". This is now possible with the use of named arguments.

Named Arguments

Using named parameters, let's call the previous function and supply values for "a" and "c".
MyFunction(3, c: "bar");
// Output: Parameter a is: 3
// Output: Parameter b is: 4
// Output: Parameter c is: bar
 
As you can see, named arguments are used by supplying the name of the argument, a colon, and then the value you'd like to supply for that argument. If you don't supply a name, like I did in this case, they will be assigned in the order they appear in the method signature.

We could also reorder the arguments, if we wanted.
MyFunction(c: "bar", a: 3);
// Output: Parameter a is: 3
// Output: Parameter b is: 4
// Output: Parameter c is: bar
 
One of the best uses I've seen so far for named arguments is to improve readability. Here's an example of code that has poor readability.
Update(
  0.1, 
  2.4, 
  1.7, 
  0.0, 
  10.3, 
  2.3, 
  1.0, 
  0.0, 
  0.0);
I'm sure we've all seen something similar to this. What the heck are those values supposed to mean. Using comments for every value would help, but another solution is to name each argument.
Update(
  positionX: 0.1, 
  positionY: 2.4, 
  positionZ: 1.7, 
  velocityX: 0.0, 
  velocityY: 10.3, 
  velocityZ: 2.3, 
  accelerationX: 1.0, 
  accelerationY: 0.0, 
  accelerationZ: 0.0);
 
This is much more readable. We can see clearly that this Update function is used for some physical properties of an object and we can clearly see where each value is being applied.

That does it for this tutorial on optional and named arguments. Hopefully you can see where this syntax would be useful in your own systems and you begin using them to create higher quality code.
Labels:

Comments

Post a Comment

Popular posts from this blog

C# Snippet - Shuffling a Dictionary [Beginner]

Randomizing something can be a daunting task, especially with all the algorithms out there. However, sometimes you just need to shuffle things up, in a simple, yet effective manner. Today we are going to take a quick look at an easy and simple way to randomize a dictionary, which is most likely something that you may be using in a complex application. The tricky thing about ordering dictionaries is that...well they are not ordered to begin with. Typically they are a chaotic collection of key/value pairs. There is no first element or last element, just elements. This is why it is a little tricky to randomize them. Before we get started, we need to build a quick dictionary. For this tutorial, we will be doing an extremely simple string/int dictionary, but rest assured the steps we take can be used for any kind of dictionary you can come up with, no matter what object types you use. Dictionary < String , int > origin = new Dictionary < string , int >();
1 comment
Read more

C# Snippet - The Many Uses Of The Using Keyword [Beginner]

What is the first thing that pops into your mind when you think of the using keyword for C#? Probably those lines that always appear at the top of C# code files - the lines that import types from other namespaces into your code. But while that is the most common use of the using keyword, it is not the only one. Today we are going to take a look at the different uses of the using keyword and what they are useful for. The Using Directive There are two main categories of use for the using keyword - as a "Using Directive" and as a "Using Statement". The lines at the top of a C# file are directives, but that is not the only place they can go. They can also go inside of a namespace block, but they have to be before any other elements declared in the namespace (i.e., you can't add a using statement after a class declaration). Namespace Importing This is by far the most common use of the keyword - it is rare that you see a C# file that does not h
Post a Comment
Read more

C# WPF Printing Part 2 - Pagination [Intermediate]

About two weeks ago, we had a tutorial here at SOTC on the basics of printing in WPF . It covered the standard stuff, like popping the print dialog, and what you needed to do to print visuals (both created in XAML and on the fly). But really, that's barely scratching the surface - any decent printing system in pretty much any application needs to be able to do a lot more than that. So today, we are going to take one more baby step forward into the world of printing - we are going to take a look at pagination. The main class that we will need to do pagination is the DocumentPaginator . I mentioned this class very briefly in the previous tutorial, but only in the context of the printing methods on PrintDialog , PrintVisual (which we focused on last time) and PrintDocument (which we will be focusing on today). This PrintDocument function takes a DocumentPaginator to print - and this is why we need to create one. Unfortunately, making a DocumentPaginator is not as easy as
Post a Comment
Read more