enum problem
In the attached zip file there are 2 enums: TInstruction and TRegister. My compiler doesn't like TInstruction enum. Attached error.png shows the errors being complained about. I cannot see any difference between the 2 enums except their lists! I'm at a loss on this problem. I sure hope this is something simple here that I am missing.
maxcy/wt1v
I did some experimenting in the TInstruction enum: changed and, or, xor to tand, tor, txor since that was where most of the compiler complaints came from. Enum is no longer a problem, but the rest of the code that relied on and, or, xor are now giving complaints as expected!! So these 3 words are reserved by the compiler and no one gets to use them in enums! How do I get around this quagmire?Originally Posted by maxcy
maxcy/wt1v
maxcy/wt1v
> and, or, xor
These are actual keywords in C++.
You need to make a different name.
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.
That doesn't make any sense! A compiler needs to make tokens for all reserved words not just these 3! I can't imagine writing a compiler and not being able to write tokens for any reserved word! I think that while writing a C++ compiler, one would need to include these keywords. I always thought that what I put into an enum list has nothing to do with reserved words. It's just a list that equates to ints. The code in this zip file is right out of Ron Maks C++ compiler design book. He was a teaching professor at some prestigious university (now probably retired), wrote several books (2 on compilers). Do you really believe that the code from his book was never any good? Have compilers changed this much over time?
maxcy/wt1v
Really?
And what is a compiler supposed to do with an expression like this containing your 'enum' values.
if ( and and or )
> Have compilers changed this much over time?
It seems far more likely that someone is taking really old C code (where those words would indeed be valid enum members) and shoe-horning it into C++ without knowing what they're doing.
'and', 'or' have always been part of C++, so that enum was never valid C++ in any version of the language.
C++ keywords - cppreference.com
Compare with the list of C keywords
C keywords - cppreference.com
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.
I've been focusing on this project too long. All the enums are passed as function parameters so the compiler could see the difference between a reserved word and an enum, but your example blows that out of the water!!! I did get the last chapter of this book fixed up and running. Now it compiles a simple Pascal program into assembly code. I would now consider this thread no longer needed, so I would mark it as completed as I do in other forums. But, alas, I can find no way to do so in this forum!
Thanks for all the help!!! maxcy/wt1v
