according to the book i am referring.
y=2 should give warning.. but it is not giving any warning or anything. jst displaying the no. i put with y.Code:enum color{ red,blue,green,white}; int x; enum color y; x= blue; //valid. x contains y y=2 // compiler warning
and
what is the us of enummerated data types??
> y=2 should give warning
It will, IF you compile it as C++ code. enums in C++ are distinct from int, and distinct from each other.
In C, enums are just named integers, so you use them just as you would use an integer.
Some lint-like tools will however complain when you (ab)use enums in certain ways.
> what is the us of enummerated data types??
Readability is one thing, automatically assigned values is another.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
But when i put y=9, it is again not showing any error. 9 is not in the defined set. it shouldn't display it. And if enums are jus named integers in C, the casting integers as enums explicitly has no meaning.
#define red 0
#define blue 1
#define green 2
#define white 3
What you basically get is a symbol which is known to the compiler, as opposed to known to the pre-processor.
Like I said, enums in C are not much better than this.
They are not as strongly typed as they are in C++.
> But when i put y=9, it is again not showing any error.
All enums are ints in C.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
