Binary number representation in array initialization doesn't compile

I don't believe binary notation is a standard feature of the C language. Hex notation, however, is a standard feature.

Some compilers implement an extension of the language to allow certain features and increase usability. 

So are you saying that Code Composer has binary notation as a C extension? That would be pretty cool. I'm not a user of Code Composer, but out of curiosity I downloaded the latest compiler manual MSP430 Optimizing C/C++ Compiler v 3.1 User's Guide (Rev. C) and looked at the compiler extensions. I don't see it in the list. Perhaps CCS doesn't support that feature.

The "0b" syntax for binary numbers is NOT part of standard C.

One workaround is a "binary.h" containing 256 lines worth of "#define B10000000 0x80" and etc :-(

Hi,

since you did not mention what you intend to do with your array I will give you my thoughts on how to deal with bit variables (since (standard) C has no 0xb support for binary variables)!

I'm defining my own data type BITFIELD which looks like (has to be a int according to C; but char (BIT0 to BIT7) will also work!)
/* ============================================================================
// structure which stores information used for program flow or debugging purposes
// ==========================================================================*/
  struct BITFIELD
  {
    unsigned char FLAG0  :1;
    unsigned char FLAG1  :1;
    unsigned char FLAG2  :1;
    unsigned char FLAG3  :1;
    unsigned char FLAG4  :1;
    unsigned char FLAG5  :1;
    unsigned char FLAG6  :1;
    unsigned char FLAG7  :1;
    unsigned char FLAG8  :1;
    unsigned char FLAG9  :1;
    unsigned char FLAG10 :1;
    unsigned char FLAG11 :1;
    unsigned char FLAG12 :1;
    unsigned char FLAG13 :1;
    unsigned char FLAG14 :1;
    unsigned char FLAG15 :1;
  };

Now, you define an initialize your variable(s) like:

volatile struct BITFIELD STATUS = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0};
                                          // defines/initializes a structure of
                                          // type BITFIELD, variable name -STATUS-

// access them from your application like i.e.
STATUS.FLAG0 = 1;  // set FLAG0 = BIT0 to 1

I'm usually defining symbolic name for the bitfield to ease my life. This could look like
/*-----------------------------------------------------------------------------
// Symbolic names for STATUS flags
//---------------------------------------------------------------------------*/
#define bADC10FLAG  STATUS.FLAG0         // ADC10 conversion finished
#define bWDTFLAG  STATUS.FLAG2  // status flag for WATCHDOG timer

Now you can do thinks like i.e.
while (!bADC10FLAG)
  __no_operation(); // wait for bADC10FLAG to be set

You can group your variables into an array or union if you want to.
Rgds
aBUGSworstnightmare