• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 1878 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Use of C's enum command with C166 compiler

Richard Roebuck

I'm currently attempting to modify an automatic code generation
package (designed to run with MSVC/C++, WATCOM C/C++ and
Borland C) to autogenerate software compilable with the Keil
CA166 package. Of the standard files which have to be included
into the code, one of them contains the lines...

enum {
COMPLEX_INHERITED = -1,
COMPLEX_NO,
COMPLEX_YES
};

...but the C166 compiler 'seems' to be objecting to the fact that
I'm using a negative number within the enum command.

According to K & R the enum command should be declaring the
contents of the enum commands to be of type 'int' - so I can't
see what the problem is.

Can anyone shed any light on this? Where am I going wrong?


Yours (grateful in advance),


Richard Roebuck.

Parents
  • 0

    Be very careful - here be cross-platform compatibility dragons!
    It's one thing to get it to compile; possibly as much again to get the compiled code to work!

    Byte ordering and data sizes are two of the fiercest dragons.

    Anyway, back at your question, does the C166 compiler have an option which forces int to default to unsigned?

    My Borland manual specifically includes an example like yours, and the Keil C51 manual specifically mentions negative values in enums.
    Your example gives no error in C51 v6.03, but the Keil compilers are not all equal!

Reply
  • 0

    Be very careful - here be cross-platform compatibility dragons!
    It's one thing to get it to compile; possibly as much again to get the compiled code to work!

    Byte ordering and data sizes are two of the fiercest dragons.

    Anyway, back at your question, does the C166 compiler have an option which forces int to default to unsigned?

    My Borland manual specifically includes an example like yours, and the Keil C51 manual specifically mentions negative values in enums.
    Your example gives no error in C51 v6.03, but the Keil compilers are not all equal!

Children
No data