We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
typedef enum { SCREEN_STARTUP, SCREEN_SHUTDWN, } ScreenType; void main( void ) { while(1); }
Can you be more specific, I always like to learn something new, you may see something I don't know about. It's quite simple: according to ANSI/ISO C Standards, the last name in an enum definition is notallowed to be followed by a comma. This is exactly opposite to struct and union definitions, where you're required to terminate the last field definition with a semicolon. Your code had such a formally forbidden comma after the second field of your enum, which means it's incorrect. In the meantime, a lot of C compilers out there have been extended to not enforce this restriction. From what you showed, Keil detected this error up to version 7.09, but this was changed with 7.10. So, to sum it up: even though the behaviour of versions 7.09 and 7.10 differs, in this particular case that doesn't mean either of them must have a bug. The actual bug is in your code, but 7.10 chose to ignore it, because it's harmless.
Thanks Hans I appreciate the input. I just want to add that I posted the code with the extra comma intentionally, just incase somebody wanted to copy and run it for themselves. If I left it out then it would not generate any error on both V709 or V710. EOM.