Why does the '$' character generate a warning?

Follow

Todd Martin

• October 23, 2009 04:39

Using the '$' character with CrossWorks for MSP430 (2.0.8) causes the following error: "literal contains non-portable characters".

Sure, I could ignore or work around the error. But this has me curious: why is this perfectly-good ASCII character considered non-portable? Is it because it can be interpreted as currency symbol? Non-portable between what?

Puzzled.

~Todd

0

• 

  Steve

  • November 05, 2009 11:23

  I get the same error with #s and other symbols. I can get rid of all warnings apart from these!

  0

  Comment actions Permalink
• 

  Jon Elliott

  • November 05, 2009 12:59

  Could you provide an example of the code causing the error?

  0

  Comment actions Permalink
• 

  Steve

  • November 05, 2009 13:09

  case '$':   keyBuf=K_SECRET;      

  case '@':   keyBuf=K_PC;

  "médico:",

  "ÈEŠTINA",

  "FRANÇAIS",

  #s were OK after all - I just assumed that they cause an error because of their association with the $s!

  0

  Comment actions Permalink
• 

  Paul Curtis

  • November 05, 2009 14:06

  See section 5.2.1 "Character Sets" of the C90 standard.  '$' and '@' are not members of the basic character set and, hence, are not portable characters.  This is because the '$' in the ASCII code page can be substituted in other code pages.  '#' is in the basic character set and does not generate a warning in strings.

   

  0

  Comment actions Permalink

Please sign in to leave a comment.