Skip to main content

[C++] enum class

Traditional C++ enum had several issues. To solve these problems, C++11 introduced a new feature called enum class. In this article, I will examine the problems with the traditional enum and how they are solved with enum class.

First, traditional enum could not be forward-declared. The reason was that if the values in the enumerator were unknown, it was impossible to determine their size. However, enum class is treated as int if an underlying type is not specified, assigning values outside the range of an int will raise a compilation error. If you want to use values outside the range of an int, you need to specify the underlying type.

Another problem with traditional enum was that the scope of enumerator names was not limited. Let's see the following example.

Here, we try to represent the results of IO and Parse functions with enums. However, this code will not compile because the Error and Ok of IOResult conflict with those of ParseResult. To resolve this issue, you can change the enumerator names, or use namespaces.

However, with enum class, the names of enumerators are limited to the scope of the enum class, so there is no need for such verbose code.

Most importantly, the biggest problem with traditional enum was that they were weakly typed and could be implicitly converted to integer types. However, enum class do not allow implicit conversion to integer types. If you try to use an enum class as an int, you will encounter a compilation error. You need to use static_cast to explicitly cast it.

As explained above, traditional enum cannot be forward-declared, their enumerator names are not limited in scope, and they can be implicitly converted to integer types. For now, enum class are the correct approach in most case.

Note: This article is a translation of a Korean post written in 2015. If you want to read the original, please refer to this link.

Labels:

Comments

Post a Comment

Popular posts from this blog

[C++] Handling Exceptions in Constructors

When you use RAII idiom, there are often situations where constructors have to do complex tasks. These complex tasks can sometimes fail, resulting in throwing exceptions. This raises a concern: Is it okay to throw exceptions in constructors? The first concern is memory leaks. Fortunately, memory leaks do not occur. Variables created on the stack are released through stack unwinding, and if an exception occurs during heap allocation with the new operator, the new operator automatically deallocates the memory and returns nullptr . The next concern is whether the destructor of the member variables will be called correctly. However, this is also not a problem. When an exception occurs, member variables can be divided into three categories: fully initialized member variables, member variables being initialized, and uninitialized member variables. Fully initialized member variables have had their constructors called and memory allocations completed successfully. In the example code, t
Post a Comment
Read more

Iterator Adapters in Rust

An Iterator that takes another iterator and returns a new one is called an iterator adapter . The name "adapter" comes from one of the GoF's design patterns, the adapter pattern . However, in reality, it corresponds more to the decorator pattern , so if you pay too much attention to the name, you might get confused about its purpose. So it's better not to worry too much about the name. Enough complaining about the name, what does an iterator adapter do? An iterator adapter adds a task to be performed when the iterator iterates. This will be easier to understand when you see an example. The map function is one of the famous adapters. The iterator returned by the map function for those who have used functional languages iterates over new values transformed from the original values. Besides, various adapters are already implemented in the standard library. Among them, the most frequently used are those that are convenient to use with loops. Examples include the
Post a Comment
Read more

Difference Between the clear Command in Linux and Mac

I've been writing a series of posts about CSI Sequences, but we rarely use CSI Sequences directly. However, there is a CSI Sequence that we use unknowingly. It's the clear command that clears the screen. The clear command basically uses two types of CSI sequences. One is CSI H ( Cu rsor P osition, a.k.a CUP); it moves the cursor to the beginning of the screen. The cursor is at the top-left corner after the command ends, thanks to CUP. The second CSI Sequence is CSI 2 J ( E rase in D isplay, a.k.a. ED), which is used to clear the entire screen. Linux and Mac use these two sequences; they behave the same way up to this point. However, Linux's clear and Mac's differ in their subsequent actions. In a nutshell, Linux's clear clears the scrollback buffer, while Mac's does not. Linux's one prints CSI 3 J after the two sequences. CSI 3 J is an extension of the Escape Sequence introduced by xterm that removes lines stored in the scrollback buffer. Since be
Post a Comment
Read more