Diving Into OOP (Day 6) : Understanding Enums in C# (A Practical Approach)

Akhil Mittal

Introduction

This article of the series “Diving into OOP” will explain the enum datatype in C#. We'll learn by doing a hands-on lab, not just by theory. We'll explore the power of enum and will cover almost every scenario in which we can use an enum. We'll follow a practical approach of learning to understand this concept. We may come across complex examples to understand the concept more deeply.

Enums (The definition)

Let's start with the definition taken from the MSDN

“The enum keyword is used to declare an enumeration, a distinct type that consists of a set of named constants called the enumerator list.

Usually it is best to define an enum directly within a namespace so that all classes in the namespace can access it with equal convenience. However, an enum can also be nested within a class or struct.

By default, the first enumerator has the value 0 and the value of each successive enumerator is increased by 1. For example, in the following enumeration, Sat is 0, Sun is 1, Mon is 2 and so forth.”

Image credit: http://pixabay.com/en/job-interview-career-conference-156130/

Pre-requisites:

I expect that my readers of this article should have a very basic knowledge of C# and I always wish that my readers should enjoy reading this article. Also keep writing programs by yourself that are given as examples in this article, to get the hands-on and understand the concept more deeply.

Let's recall our road map as in the following:

Image credit: http://borgefagerli.com/at-a-crossroads/cross-roads/

A Practical Approach

Enum plays almost the same responsibility as the class does, in other words creating a new data type and it exists at the same level as class, interfaces or structs.

Just open your Visual Studio and add a console application named Enums. You'll get a Program class.

Note: Each and every code snippet in this article is tried and tested.

Declare an enum at the same level as of the Program class, call it Color.

Program.cs

namespace Enums
{
class Program
{
static void Main(string[] args)
{
}
}
enum Color
{
Yellow,
Blue,
Brown,
Green
}
}

In the preceding example, we created a new datatype using an enum. The datatype is Color having four distinct values Yellow, Blue, Brown and Green. The text that we write inside the declared enum could be anything of your wish; it just provides a custom enumerated list to you.

Modify your main program as shown below.

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine(Color.Yellow);
Console.ReadLine();
}
}
enum Color
{
Yellow,
Blue,
Brown,
Green
}
}

Run the program.

Output: Yellow

Now if we just typecast Color.Yellow to int, what do we get?

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine((int)Color.Yellow);
Console.ReadLine();
}
}
enum Color
{
Yellow,
Blue,
Brown,
Green
}
}

Output: 0

We see that enums are called static variables, so an enum can be considered here as static objects. Therefore other enums in the preceding example can be declared in the same way as Yellow, like Blue can be declared as Color.Blue. The output in the above two examples we see is 0 when we type cast and Yellow without typecasting, hence we see here that its behaviour is very similar to an array where Yellow has a value 0, similarly Blue has a value 1, Brown: 2, Green:3.

Therefore when we do Color.Yellow, it's like displaying a number 0, so from this we can infer that an enum represents a constant number, therefore an enum type is a distinct type having named constants.

A point to remember: An enum represents a constant number and an enum type is known as a distinct type having named constants.

Underlying data type

Program.cs

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine((byte)Color.Yellow);
Console.WriteLine((byte)Color.Blue);
Console.ReadLine();
}
}
enum Color:byte
{
Yellow,
Blue,
Brown,
Green
}
}

Output

0
1

Note: Each and every code snippet in this article is tried and tested.

The only change we did here is that we specified the type to the underlying enum that we declared. The default datatype for the enum is int, here we have specified the data type as byte and we get the result.

There are more data types that can be specified for enum like long, ulong, short, ushort, int, uint, byte and sbyte.

Point to remember: We can't declare char as an underlying data type for enum objects because char stores Unicode characters, but enum objects data type can only be a number.

Inheritance in enum

Program.cs

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine((byte)Color.Yellow);
Console.WriteLine((byte)Color.Blue);
Console.ReadLine();
}
}
enum Color:byte
{
Yellow,
Blue,
Brown,
Green
}
enum Shades:Color
{
}
}

Output:

Compile time error: Type byte, sbyte, short, ushort, int, uint, long, or ulong expected

We clearly see here enums can't be derived from any other type except that specified in the error.

Point to remember: an enum can't be derived from any other type except that of type byte, sbyte, short, ushort, int, uint, long, or ulong

Let's derive a class from an enum, call it class Derived, so our code is as in the following.

Program.cs:

class Program
{
static void Main(string[] args)
{
Console.WriteLine((byte)Color.Yellow);
Console.WriteLine((byte)Color.Blue);
Console.ReadLine();
}
}

Enum:

enum Color:byte
{
Yellow,
Blue,
Brown,
Green
}

Derived.cs:

class Derived:Color
{
}

Compile the code.

Output:

Compile time error: 'Enums.Derived': cannot derive from sealed type 'Enums.Color'

Image credit: https://www.flickr.com/photos/lwr/931211869/

So, the point to remember is: By default an enum is a sealed class and therefore conforms to all the rules that a sealed class follows, so no class can derive from an enum, in other words a sealed type.

Can System.Enum be a base class to enum?

Program.cs:

using System;
namespace Enums
{
internal enum Color: System.Enum
{
Yellow,
Blue
}
internal class Program
{
private static void Main(string[] args)
{
}
}
}

Output:

Compile time error: Type byte, sbyte, short, ushort, int, uint, long, or ulong expected

Point to remember: The enum type is implicitly derived from System.Enum and so we cannot explicitly derive it from System.Enum.

To add more, an enum is also derived from the three interfaces IComparable, IFormattable and IConvertible.

A. IComparable

Let's check.

Program.cs:

using System;
namespace Enums
{
internal enum Color
{
Yellow,
Blue,
Green
}
internal class Program
{
private static void Main(string[] args)
{
Console.WriteLine(Color.Yellow.CompareTo(Color.Blue));
Console.WriteLine(Color.Blue.CompareTo(Color.Green));
Console.WriteLine(Color.Blue.CompareTo(Color.Yellow));
Console.WriteLine(Color.Green.CompareTo(Color.Green));
Console.ReadLine();
}
}
}

Output:

-1
-1
1
0

Sometimes we may get into situations where we have a large number of enums defined and we want to compare the values of the enum to each other to check if they are smaller, larger or an equal value to one another.

Since all enums implicitly derive from an Enum class that implements the interface IComparable, so they all have a method CompareTo(), that we just use in the above example. The method being non-static must be used through a member. Yellow has the value 0, Blue has 1 and Green has 2. In the first statement, when Color.Yellow is comared to Color.Blue, the value of Yellow is less than Blue hence -1 is returned. The same applies for the second statement when Color.Blue is compared to Color.Green. Green has a larger value, in other words 2 than that of Color.Blue having value 1 only. In the third statement, in other words the revers of the first statement, we get the result of comparison as 1, because Blue is greater than Yellow. In the last statement where Color.Green compares to itself, we undoubtedly get the value 0.

So the value -1 means the value is smaller, 1 means the value is larger and 0 means equal values for both the enum members.

The following is another comparison example.

Program.cs:

using System;
namespace Enums
{
enum Color
{
Yellow,
Blue,
Green
}
internal class Program
{
private static void Main(string[] args)
{
int myColor = 2;
if(myColor== Color.Green)
{
Console.WriteLine("my color");
}
Console.ReadLine();
}
}
}

Output:

Compile time error : Operator '==' cannot be applied to operands of type 'int' and 'Enums.Color'

In the above example we tried to compare an int type to a Enum type and that resulted in a compile time error. Since an enum acts as an individual data type so it cannot be directly compared to an int, however, we can typecast the enum type to an int to do the comparison, like in the following example.

Program.cs:

using System;
namespace Enums
{
enum Color
{
Yellow,
Blue,
Green
}
internal class Program
{
private static void Main(string[] args)
{
int myColor = 2;
if(myColor== (int)Color.Green)
{
Console.WriteLine("my color");
}
Console.ReadLine();
}
}
}

Output: my color

B. IFormattable

Program.cs:

using System;
namespace Enums
{
internal enum Color
{
Yellow,
Blue,
Green
}
internal class Program
{
private static void Main(string[] args)
{
System.Console.WriteLine(Color.Format(typeof(Color), Color.Green, "X"));
System.Console.WriteLine(Color.Format(typeof(Color), Color.Green, "d"));
Console.ReadLine();
}
}
}

Output:

00000002
2

Format is the method derived from the IFormatter interface. It's a static method so can be used directly with the enum class defined as Color. It's first parameter is the type of the enum class, the second is the member that must be formatted and the third is the format, in other words hexadecimal or decimal, like we used in the above example and we got a positive result output too.

C. IConvertible

using System;
namespace Enums
{
enum Color
{
Yellow,
Blue,
Green
}
internal class Program
{
private static void Main(string[] args)
{
string[] names;
names = Color.GetNames(typeof (Color));
foreach (var name in names)
{
Console.WriteLine(name);
}
Console.ReadLine();
}
}
}

Output:

Yellow
Blue
Green

Note: Each and every code snippet in this article is tried and tested.

GetNames is a static method that accepts Type, in other words an instance of type as a parameter and in return gives an array of strings. Like in the above example, we had an array of 3 members in our enum, therefore thier names are displayed one by one.

The following is another example.

Program.cs

using System;
namespace Enums
{
enum Color
{
Yellow,
Blue,
Green
}
internal class Program
{
private static void Main(string[] args)
{
Console.WriteLine(Color.Blue.ToString());
Console.WriteLine(Color.Green.ToString());
Console.ReadLine();
}
}
}

Output:

Blue
Green

As we see in the above example, we converted an enum type to a starting type and got an output too, so, numerous predefined conversion methods can be used to convert an enum from one data type to another.

Point to remember: numerous predefined conversion methods can be used to convert an enum from one data type to another.

Duplicity, default values and initialization

Program.cs:

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine((byte)Color.Yellow);
Console.WriteLine((byte)Color.Blue);
Console.ReadLine();
}
}
enum Color
{
Yellow,
Blue,
Brown,
Green,
Blue
}
}

Output:

Compile time error: The type 'Enums.Color' already contains a definition for 'Blue'

In the preceding example we just repeated the enum member Blue of Color and we got a compile time error, hence we now know that an enum cannot contain two members having the same name. By default if the first value is not specified then the first member takes the value 0 and increments it by one for succeeding members.

Let's use one more example.

Program.cs:

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine((int)Color.Yellow);
Console.WriteLine((int)Color.Blue);
Console.WriteLine((int)Color.Brown);
Console.WriteLine((int)Color.Green);
Console.ReadLine();
}
}
enum Color
{
Yellow =2,
Blue,
Brown=9,
Green,
}
}

Output:

2
3
9
10

Surprise! We can always specify the default constant value to any enum member, here we see, we specified the value 2 for yellow, so as per the law of enum, the value of blue will be incremented by one and gets the value 3. We again specified 9 as a default value to Brown and so its successor Green gets incremented by one and gets that value 10.

Moving on to another example.

Program.cs:

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
}
}
enum Color:byte
{
Yellow =300 ,
Blue,
Brown=9,
Green,
}
}

Output:

Compile time error: Constant value '300' cannot be converted to a 'byte'

We just derived our enum from byte, we know we can do that . We then change the value of Yellow from 2 to 300 and we resulted in a compile time error. Since here our underlying data type was byte, it is as simple as that, that we cannot specify the value to enum members that exceeds the range of underlying data types. The value 300 is beyond the range of byte. It is similar to assigning the beyond range value to a byte data type variable.

The following is another example.

Program.cs:

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine((int)Color.Yellow);
Console.WriteLine((int)Color.Blue);
Console.WriteLine((int)Color.Brown);
Console.WriteLine((int)Color.Green);
Console.ReadLine();
}
}
enum Color
{
Yellow = 2,
Blue,
Brown = 9,
Green = Yellow
}
}

Output:

2
3
9
2

Here we initialized Green to Yellow and we did not get an error, so we see, more than one enum members can be initialized with the same constant value.

Point to remember: More than one enum members can be initialized with the same constant value.

Program.cs:

using System;
namespace Enums
{
class Program
{
static void Main(string[] args)
{
Color.Yellow = 3;
}
}
enum Color
{
Yellow = 2,
Blue,
Brown = 9,
Green = Yellow
}
}

Output:

Compile time error: The left-hand side of an assignment must be a variable, property or indexer

In the preceding example, we tried to initialize the enum member out of the scope of the defined enum, in other words in another class and got a compile time error. We must not forget that an enum acts as a constant, that cannot change its value.

Point to remember: An enum acts as a constant, so its value cannot be changed once initialized.

Readability

Program.cs:

using System;
namespace Enums
{
internal enum Color
{
Yellow,
Blue,
Brown,
Green
}
internal class Program
{
private static void Main(string[] args)
{
Console.WriteLine(CheckColor(Color.Yellow));
Console.WriteLine(CheckColor(Color.Brown));
Console.WriteLine(CheckColor(Color.Green));
Console.ReadLine();
}
public static string CheckColor(Color color)
{
switch (color)
{
case Color.Yellow:
return "Yellow";
case Color.Blue:
return "Blue";
case Color.Brown:
return "Brown";
case Color.Green:
return "Green";
default:
return "no color";
}
}
}
}

Output:

Yellow
Brown
Green

Here, in the above example we declared an enum Color containing various color members.There is a class named program that contains a static method named CheckColor, that has a switch statement checking the color on the basis of the ed parameter to the method, in other words an Enum Color. In the Main method we try to access that CheckColor method, ing various parameters. We see that the the switch statement in the CheckColor method can use any of the datatypes ed and in return the case statements use the name of that type and not the plain int number to compare the result. We see that this made our program more readable. So an enum plays an important role in making the program more readable, structured and easy to grasp.

Circular dependency

Program.cs:

using System;
namespace Enums
{
internal enum Color
{
Yellow=Blue,
Blue
}
internal class Program
{
private static void Main(string[] args)
{
}
}
}

Output:

Compile time error: The evaluation of the constant value for 'Enums.Color.Yellow' involves a circular definition

Like constants we also cannot have circular dependency in enums. We assigned the value Blue to Yellow and Blue in turn is incremented by one as a next enum member, this results in a circular dependency of Blue to yellow and resulted in an error, C# is smart enough to catch these kinds of tricks.

Diving Deep

Let's take some complex scenarios.

Lab 1

Program.cs:

using System;
namespace Enums
{
enum Color
{
}
internal class Program
{
private static void Main(string[] args)
{
Color color = (Color) -1;
Console.ReadLine();
}
}
}

Note: Each and every code snippet in this article is tried and tested.

Output:

Compile time error:
To cast a negative value, you must enclose the value in parentheses
'Enums.Color' is a 'type' but is used like a 'variable'

In the preceding example, we are casting a negative value to enum, but the compiler says that while casting a negative value, we must keep that in parenthesis. It's not strange, since C# knows that “-” is also a unary operator, that use of the code above may create confusion for the compiler of whether we are using subtraction or we are typecasting a negative value. So always use parenthesis while typecasting negative values.

Lab 2

Program.cs:

using System;
namespace Enums
{
enum Color
{
value__
}
internal class Program
{
private static void Main(string[] args)
{
}
}
}

Output:

Compile time error: The enumerator name 'value__' is reserved and cannot be used

We clearly see here that we have value__ as a reserved member for the enumerator. The C# compiler like this keyword has a large number of reserved builtin keywords.

Image credit: www.vector.rs

It may keep this reserved keyword to keep track of the enum members internally but not sure.

Summary:

Let's recall all the points that we need to remember.

An enum represents for a constant number and an enum type is known as a distinct type having named constants.
We can't declare char as an underlying data type for enum objects because char stores Unicode characters, but enum objects data type can only be number.
An enum can't be derived from any other type except that of type byte, sbyte, short, ushort, int, uint, long, or ulong.
By default an enum is a sealed class and therefore conforms to all the rules that a sealed class follows, so no class can derive from an enum, in other words a sealed type.
The enum type is implicitly derived from System.Enum and so we cannot explicitly derive it from System.Enum.
An enum is also derived from the three interfaces IComparable, IFormattable and IConvertible.
A numerous predefined conversion methods can be used to convert an enum from one data type to another.
More than one enum member can be initialized a same constant value.
An enum acts as a constant, so its value cannot be changed once initialized.
The enumerator name "value__" is reserved and cannot be used.

Conclusion

With this article we completed nearly all the scenarios related to enum. We did many of hands-on labs to clarify our concepts. I hope my readers now know by heart these basic concepts and will never forget them.

These may also help you in cracking C# interviews.

Keep coding and enjoy reading.

Also do not forget to rate/comment/like my article if it helped you by any means, this helps me to get motivated 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 !

Enums Data TypeEnums in C#Diving in OOPInheritance in enum

15 Comments

Join the conversation! Your thoughts help the community grow.

Vipin Tyagi10y ago
Finally I completed Enum ,Now move to next.....
- Akhil Mittal10y ago
  Great. Thanks for reading.
Upendra Pratap Shahi11y ago
nice sir
- Akhil Mittal11y ago
  Thanks
Gowtham Rajamanickam11y ago
good
- Akhil Mittal11y ago
  Thank you :-)
Karen Tonoyan12y ago
And ofcourse you can convert strings to enum constants by this way Colors mycolorValue = (Colors) Enum.Parse(typeof(Colors),"Green");
Nilesh Avhad12y ago
This is most understandable OOP series I ever read on internet. I request you to keep posting such a article with very basic language with such a real world example. egarly Waiting for your next articles... Thanks again.............:)
- Akhil Mittal12y ago
  The pleasure is all mine Sir.Thanks a lot for following the articles :-)
Santosh Yadav12y ago
Nice article.. Thanks
- Akhil Mittal12y ago
  Thanks
udeep kansal12y ago
Very good article..keep showing your skills to explain technology concepts in much easier way..Thank you !!
- Akhil Mittal12y ago
  Thanks Udeep for reading the post.:-) :-)
Manju lata Yadav12y ago
Nice Arictle... Post more Articles...
- Akhil Mittal12y ago
  Thanks a lot.Lines like this motivates me a lot.