Diving Into OOP (Day 8) - Indexers in C# (A Practical Approach)

Table of Contents

Introduction
Indexers in C# (The definition)
Roadmap
Indexers (The explanation)
- Lab 1
- Lab 2
- Lab 3
Data-Types in Indexers
- Lab 1
Indexers in interfaces
Indexers in Abstract class
Indexer Overloading
- Point to remember
Static Indexers?
- Point to remember

Inheritance/Polymorphism in Indexers
.NET Framework and Indexers
- Point to remember
Properties vs Indexers
Conclusion

Introduction

In my last article of this series we learned about properties in C#. This article of the series “Diving into OOP” will explain all about indexers in C#, their uses and practical implementation. We'll follow the same way of learning, in other words less theory and more practice. I'll try to explain the concept in-depth.

Indexers in C# (The definition)

Let's use the definition from: MSDN.

“Indexers allow instances of a class or struct to be indexed just like arrays. Indexers resemble properties except that their accessors take parameters.”

Roadmap

Let's recall our road map.

Roadmap

Indexers (The explanation)

As the definition says, indexers allow us to leverage the capability of accessing the class objects as an array. For a better understanding, create a console application named Indexers and add a class to it named Indexer. We'll use this class and project to learn Indexers. Make the class public, do not add any code for now and in Program.cs add following code.

Lab 1

namespace Indexers
{
class Program
{
static void Main(string[] args)
{
Indexer indexer=new Indexer();
indexer[1] = 50;
}
}
}

Compile the code. We get:

Error Cannot apply indexing with [] to an expression of type 'Indexers.Indexer'

I just created an object of the Indexer class and tried to use that object as an array. Since it was not actually an array, it produced a compile time error.

Lab 2

Indexer.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace Indexers
{
public class Indexer
{
public int this[int indexValue]
{
set
{
Console.WriteLine("I am in set : Value is " + value + " and indexValue is " + indexValue);
Console.ReadLine();
}
}
}
}

Program.cs

namespace Indexers
{
class Program
{
static void Main(string[] args)
{
Indexer indexer=new Indexer();
indexer[1] = 50;
}
}
}

Output

console

Here we just used an indexer to index my object of the class Indexer. Now my object can be used as an array to access various object values.

Implementation of indexers is derived from a property known as “this”. It takes an integer parameter indexValue. Indexers are different from properties. In properties, when we want to initialize or assign a value, the “set” accessor, if defined, is automatically called. And the keyword “value” in the “set” accessor was used to hold or keep track of the assigned value to our property. In the preceding example, indexer[1] = 50; calls the “set” accessor of the “this” property, in other words the indexer 50 becomes the value and 1 becomes the index of that value.

Lab 3

Indexer.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace Indexers
{
public class Indexer
{
public int this[int indexValue]
{
set
{
Console.WriteLine("I am in set : Value is " + value + " and indexValue is " + indexValue);
}
get
{
Console.WriteLine("I am in get and indexValue is " + indexValue);
return 30;
}
}
}
}

Program.cs

using System;
namespace Indexers
{
class Program
{
static void Main(string[] args)
{
Indexer indexer=new Indexer();
Console.WriteLine(indexer[1]);
Console.ReadKey();
}
}
}

Output

see output

In the preceding code snippet, I used get as well, to access the value of the indexer. Properties and Indexers work on the same set of rules. There is a bit of a difference on how we use them. When we do indexer[1] then that means the “get” accessor is called and when we assign some value to indexer[1] then the “set” accessor is called. When implementing indexer code we need to take care that when we access an indexer it is accessed in the form of a variable and that too is an array parameter.

Data-Types in Indexers

Lab 1

Indexer.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace Indexers
{
public class Indexer
{
public int Index;
public int this[string indexValue]
{
set
{
Console.WriteLine("I am in set : Value is " + value + " and indexValue is " + indexValue);
Index = value;
}
get
{
Console.WriteLine("I am in get and indexValue is " + indexValue);
return Index;
}
}
}
}

Program.cs

using System;
namespace Indexers
{
class Program
{
static void Main(string[] args)
{
Indexer indexer=new Indexer();
indexer["name"]=20;
Console.WriteLine(indexer["name"]);
Console.ReadKey();
}
}
}

Output

show output

The “this” property, in other words indexers, have a return value. In our example the return value was an integer. The square brackets along with “this” can also hold other data types and not only an integer. In the preceding example I tried to explain this using a string parameter type for “this” : public int this [string indexValue].

The string parameter “indexValue” has a value “name”, like we ed in the Main method of Program.cs. So one can have more than one indexer in a class deciding what should be the data type of the parameter value of an array. An indexer, like properties, follow the same rules of inheritance and polymorphism.

Indexers in interfaces

Like Properties and Methods, Indexers can also be declared in interfaces.

For practical implementation, just create an interface named IIndexers with the following code.

namespace Indexers
{
interface IIndexers
{
string this[int indexerValue] { get; set; }
}
}

Here, an indexer is declared with an empty get and set accessor, that returns string values.

Now we need a class that implements this interface. You can define a class of your choice and implement that using the IIndexers interface.

Indexer.cs

using System;
namespace Indexers
{
public class IndexerClass:IIndexers
{
readonly string[] _nameList = { "AKhil","Bob","Shawn","Sandra" };
public string this[int indexerValue]
{
get
{
return _nameList[indexerValue];
}
set
{
_nameList[indexerValue] = value;
}
}
}
}

The class has a default array of strings that holds names. Now we can implement an interface defined indexer in this class to write our custom logic to fetch names on the base of indexerValue. Let's call this in our main method.

Program.cs

using System;
namespace Indexers
{
class Program
{
static void Main(string[] args)
{
IIndexers iIndexer=new IndexerClass();
Console.WriteLine(iIndexer[0]);
Console.WriteLine(iIndexer[1]);
Console.WriteLine(iIndexer[2]);
Console.WriteLine(iIndexer[3]);
Console.ReadLine();
}
}
}

Run the application.

Output

In the main method, we took an interface reference to create an object of the Indexer class and we accessed that object array using indexer values like an array. It gives the names one by one.

Now if I want to access a “set” accessor as well, I can easily do that. To check this, just add two more lines where you set the value in the indexer.

iIndexer[2] = "t;Akhil Mittal";
Console.WriteLine(iIndexer[2]);

I set the value of the second element as a new name. Let's see the output.

Indexers in Abstract class

Like we used indexers in interfaces, we can also use indexers in abstract classes. I'll use the same logic of source code that we used in interfaces, so that you can relate how it works in abstract class as well. Just define a new class that should be abstract and should contain an abstract indexer with empty get and set.

AbstractBaseClass

namespace Indexers
{
public abstract class AbstractBaseClass
{
public abstract string this[int indexerValue] { get; set; }
}
}

Define the derived class, inheriting from the abstract class.

IndexerClass

We here use an override in the indexer to override the abstract indexer declared in the abstract class.

using System;
namespace Indexers
{
public class IndexerClass:AbstractBaseClass
{
readonly string[] _nameList = { "AKhil","Bob","Shawn","Sandra" };
public override string this[int indexerValue]
{
get
{
return _nameList[indexerValue];
}
set
{
_nameList[indexerValue] = value;
}
}
}
}

Program.cs

We'll use a reference of an abstract class to create an object of the Indexer class.

using System;
namespace Indexers
{
class Program
{
static void Main(string[] args)
{
AbstractBaseClass absIndexer=new IndexerClass();
Console.WriteLine(absIndexer[0]);
Console.WriteLine(absIndexer[1]);
Console.WriteLine(absIndexer[2]);
Console.WriteLine(absIndexer[3]);
absIndexer[2] = "Akhil Mittal";
Console.WriteLine(absIndexer[2]);
Console.ReadLine();
}
}
}

Output

run program

All of the preceding code is self-explanatory. You can explore more scenarios by yourself for a better understanding.

Indexer Overloading

Indexer.cs

using System;
namespace Indexers
{
public class Indexer
{
public int this[int indexerValue]
{
set
{
Console.WriteLine("Integer value " + indexerValue + " " + value);
}
}
public int this[string indexerValue]
{
set
{
Console.WriteLine("String value " + indexerValue + " " + value);
}
}
public int this[string indexerValue, int indexerintValue]
{
set
{
Console.WriteLine("String and integer value " + indexerValue + " " + indexerintValue + " " + value);
}
}
}
}

Program.cs

using System;
namespace Indexers
{
class Program
{
static void Main(string[] args)
{
Indexer indexer=new Indexer();
indexer[1] = 30;
indexer["name"]=20;
indexer["address",2] = 40;
Console.ReadLine();
}
}
}

Output

run

In the preceding example, we see the indexer's signature is in the actual count of the actual parameters and data types irresepective of the names of the arguments/parameters or return value of the indexers. This allows us to overload indexers as we do in method overloading. You can read more about method over loading. Here now we have overloaded indexers that take integer, string integer and string combined as actual parameters. Like methods cannot be overloaded on the base of return types, so are indexers. Indexers follow the same methodology of overload like methods do.

Point to remember

Like indexers, we cannot overload properties. Properties are more like knowing by name and indexers on the other hand is more like knowing by signature.

Static Indexers

In the example that we discussed in the last section, just add a static keyword to the indexer signature.

public static int this[int indexerValue]
{
set
{
Console.WriteLine("Integer value " + indexerValue + " " + value);
}
}

Compile the program. We get a compile time error.

Error The modifier 'static' is not valid for this item

The error clearly indicates that an indexer cannot be marked static. An indexer can only be a class instance member but not static, on the other hand a property can be static too.

Point to remember

Properties can be static but indexers cannot be.

Inheritance/Polymorphism in Indexers

Indexer.cs

using System;
namespace Indexers
{
public class IndexerBaseClass
{
public virtual int this[int indexerValue]
{
get
{
Console.WriteLine("Get of IndexerBaseClass; indexer value: " + indexerValue);
return 100;
}
set
{
Console.WriteLine("Set of IndexerBaseClass; indexer value: " + indexerValue + " set value " + value);
}
}
}
public class IndexerDerivedClass:IndexerBaseClass
{
public override int this[int indexerValue]
{
get
{
int dValue = base[indexerValue];
Console.WriteLine("Get of IndexerDerivedClass; indexer value: " + indexerValue + " dValue from base class indexer: " + dValue);
return 500;
}
set
{
Console.WriteLine("Set of IndexerDerivedClass; indexer value: " + indexerValue + " set value " + value);
base[indexerValue] = value;
}
}
}
}

Program.cs

using System;
namespace Indexers
{
class Program
{
static void Main(string[] args)
{
IndexerDerivedClass indexDerived=new IndexerDerivedClass();
indexDerived[2] = 300;
Console.WriteLine(indexDerived[2]);
Console.ReadLine();
}
}
}

Output

Output

The example code taken above explains run time polymorphism and inheritance in indexers. I created a base class named IndexerBaseClass having an indexer with its own get and set as was explained in prior examples. Thereafter a derived class is created named IndexerDerivedClass, this derives from IndexerBaseClass and overrides the “this” indexer from the base class. Note that the base class indexer is marked virtual, so we can override it in a derived class by marking it “override” in the derived class. The example makes a call to the indexer of the base class. Sometimes when we need to override code in a derived class in the derived class, we may require the base class indexer to be called first. This is just a situation. The same rule of run time polymorphism applies here, we declare the base class indexer and virtual and derived class one as override. In the “set” accessor of the derived class, we can call the base class indexer as base[indexerValue]. Also this value is used to initialize the derived class indexer as well. So the value is stored in the “value” keyword too. So, indexDerived[2] in the Main() method of Program.cs is replaced to base[2] in the “set” accessor. Whereas in the “get” accessor it is the reverse, we must put base[indexerValue] on the right hand side of the equal sign. The “get” accessor in the base class returns the value 100 that we get in the dValue variable.

.NET Framework and Indexers

Indexers play a crucial role in the .NET Framework. Indexers are widely used in the .NET Framework builtin classes, libraries such as collections and enumerable. Indexers are used in collections that are searchable like Dictionary, Hashtable, List, Arraylist and so on.

Point to remember

Dictionary in C# largely uses indexers to have a staring parameter as an indexer argument.

Classes like ArrayList and List use indexers internally to provide functionality of arrays for fetching and using the elements.

Properties vs Indexers

I have already explained a lot about properties and indexers, to summarize, let me point to an MSDN link for a better explanation.

table

Table taken from MSDN.

Conclusion

With this article we completed nearly all the scenarios related to an indexer. We did many hands-on labs to clarify our concepts. I hope my readers now know by heart about these basic concepts and will never forget them. These may also help you in cracking C# interviews.

smile

Keep coding and enjoy reading.

Also do not forget to rate/comment/like my article if it helped you by any means, this motivates and encourages me to write more and more.

Read more:

For more technical articles you can reach out to CodeTeddy

My other series of articles:

Happy coding !

12 Comments

Join the conversation! Your thoughts help the community grow.

Vipin Tyagi10y ago
Finally ,I completed the Series.Thanks Sir
Santhakumar Munuswamy11y ago
Good show
Debasis Saha11y ago
Good One..
- Akhil Mittal11y ago
  Thanks
Rakesh11y ago
Nicely explain
- Akhil Mittal11y ago
  Thanks
Gopi Chand11y ago
Great
- Akhil Mittal11y ago
  Thanks
Sibeesh Venu11y ago
Good one.
- Akhil Mittal11y ago
  Sibeesh Venu Thanks
Pankaj Kumar Choudhary11y ago
Really Impressive Work Sir..........
- Akhil Mittal11y ago
  Thanks