I'm just wondering if there's now a more accepted way to define a set of values than #define.
Say I have the following:
#define C_CMD1 1
#define C_CMD2 2
#define C_CMD3 3
etc...
Is there a more accepted way of doing this now that doesn't require #defines, and preferably is restricted in scope so the same name can be used in different classes with different values associated with them? I thought of CONST Variables but it seems like a waste of ram.
Last edited by _Elixia_; 06-29-2003 at 04:39 PM.
Using consts would be the only other way to do it, AFAIK.
Naturally I didn't feel inspired enough to read all the links for you, since I already slaved away for long hours under a blistering sun pressing the search button after typing four whole words! - Quzah
You. Fetch me my copy of the Wall Street Journal. You two, fight to the death - Stewie
I wouldn't say using const variables is a waste of RAM. Think about how much sapce an int takes (usually 4 bytes, sometimes 2 or 8) compared to the amount of memory you have access to (several megabytes).
The type safety, and additional ease of debugging actual variables as opposed to #defines is well worth a few bytes per variable.
The word rap as it applies to music is the result of a peculiar phonological rule which has stripped the word of its initial voiceless velar stop.
And there's the fact that most modern compilers automatically substitute const non-user-defined variables with literals. So there's no wasted memory.
I know this doesn't cover user-defined classes; but then again, neither does #define.
The prefered way to define constants in C++ is using the keyword const.
Mr. C: Author and Instructor
Thank you, Mr Obvious.
Naturally I didn't feel inspired enough to read all the links for you, since I already slaved away for long hours under a blistering sun pressing the search button after typing four whole words! - Quzah
You. Fetch me my copy of the Wall Street Journal. You two, fight to the death - Stewie
