Skip to main content

Clashing for enumerations.

When we use enumerations, by default the values assigned to enumerations start from zero. Suppose you have two classes with classA and classB with enumeraions defined as below.

For classA: enum { santro,zen } cars;

For classB: enum { Kinetic,sunny} bikes;

Now in a function you get some integer which should indicate the type of car or type bike.

void findType(int nType)

{

if( nType == classA::santro )

{

cout<

}

if( nType == classA::zen)

{

cout<

}

if( nType == classB::kinetic)

{

cout<

}

if( nType == classB::sunny)

{

cout<

}

}

Now with such a code you will always find out put as

santro

kinetic

OR

zen

sunny

This is because though while coding we use classA::santro and classB::kinetic, both the variables have the same value i.e. zero. Thus for any value of nType (0 or 1 ), always two if conditions are satisfied, giving the wrong result . So if you are using two enumeraions in a single function you should always make sure to avoid the clash between them.

For this we can use the following code to add the offset to one of the enumeraions.

enum { kinetic = 100, sunny } bikes;

Thus values of the enums bikes and cars, will differ in value and the clashing between the two will be avoided.( You also have to adjust the values of the variable nType passed to the function accordingly.)

If two enumeraions are being used in same function, then care should be taken to avoid the clashing between the two.

Labels:

Comments

Post a Comment

Popular posts from this blog

Explain Polymorphism and Flavors of Polymorphism...

Polymorphism is the ability of different objects to react in an individual manner to the same message. This notion was imported from natural languages. For example, the verb "to close" means different things when applied to different objects. Closing a door, closing a bank account, or closing a program's window are all different actions; their exact meaning is determined by the object on which the action is performed. Most object-oriented languages implement polymorphism only in the form of virtual functions. But C++ has two more mechanisms of static (meaning: compile-time) polymorphism: Operator overloading. Applying the += operator to integers or string objects, for example, is interpreted by each of these objects in an individual manner. Obviously, the underlying implementation of += differs in every type. Yet, intuitively, we can predict what results are. Templates. A vector of integers, for example, reacts differently from a vector of string objects when it receives
17 comments
Read more

Explain using static class member ..

A class member declared static is a single instance of that member shared by all instances of this class (that's why it is sometimes termed a class variable, as opposed to object variable). This feature has many uses: for instance, in order to create a file lock, one can use a static bool class member. An object trying to access this file has to check first whether the static (i.e., shared) flag is false. If it is, the object turns the flag on and processes the file safely, since other objects will now find that the flag is now on, and hence -- they cannot access the file. When the object processing the file is done, it has to turn off the flag, enabling another object to access it. How is a static member created? class fileProc { FILE *p; static bool isLocked; //only a declaration; see definition below... public: bool isLocked () const {return isLocked; } }; //somewhere outside the class definition: bool fileProc::isLocked; //definition; initialized to 'false' by defau
9 comments
Read more

the Differences Between static_cast and reinterpret_cast

The operators static_cast and reinterpret_cast are similar: they both convert an object to an object of a different type. However, they aren't interchangeable. Static_cast uses the type information available at compile time to perform the conversion, making the necessary adjustments between the source and target types. Thus, its operation is relatively safe. On the other hand, reinterpret_cast simply reinterprets the bit pattern of a given object without changing its binary representation. To show the difference between the two, let's look at the following example: int n = 9; double d = static_cast < double > (n); In this example, we convert an int to a double. The binary representation of these types is very different. In order to convert the int 9 to a double, static_cast needs to properly pad the additional bytes of d. As expected, the result of the conversion is 9.0. Now let's see how reinterpret_cast behaves in this context: int n = 9; double d = reinterp
2 comments
Read more