• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 22 subscribers
  • Views 1491 views
  • Users 0 members are here
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

EC++ and priority keyword incompatibility

Georget Stephane

Hello,

Is it normal that EC++ won't compile properly if a variable is called "priority" or "_priority"?

Example:

unsigned int priority = 1;
unsigned int _priority = 1;

Won't compile. I don't think that these words are either defined nor EC++ tokens.


In AR166_Config.h also, there is a line that goes like:
extern void  os_init_context (P_TCB p_TCB, U8 priority,
                             FUNCP task_body, U8 full_contxt);

EC++ always throws an error on it. (note the declaration of U8 priority, valid in C but not with EC++).

So this header cannot be included in a .cpp file, even though it has a few #ifdef __cplusplus at the beginning, showing that this file should compile with EC++, no?

Thx,

-Stephane

Parents
  • 0 in reply to Gp F

    Not quite.

    - priority, _priority and __priority are EC++ keywords.

    - _priority_ is a C keyword, not EC++

    - priority and _priority should not be EC++ tokens, for they are used elsewhere in Keil AR166 headers, and not documented in the EC++ manual.

    Let me get to the point then: it would be really cool if the next version of AR166 headers could compile successfully with EC++!

    Rgds,

    Steph-

Reply
  • 0 in reply to Gp F

    Not quite.

    - priority, _priority and __priority are EC++ keywords.

    - _priority_ is a C keyword, not EC++

    - priority and _priority should not be EC++ tokens, for they are used elsewhere in Keil AR166 headers, and not documented in the EC++ manual.

    Let me get to the point then: it would be really cool if the next version of AR166 headers could compile successfully with EC++!

    Rgds,

    Steph-

Children
No data