http://msdn.microsoft.com/en-us/library/ewwyfdbe%28v=vs.71%29.aspx

Note

An unnamed bit field of width 0 forces alignment of the next bit field to the next type boundary, where type is the type of the member.

The following example declares a structure that contains bit fields:

// bit_fields1.cpp

struct Date

{

   unsigned nWeekDay  : ;    // 0..7   (3 bits)

   unsigned nMonthDay : ;    // 0..31  (6 bits)

   unsigned nMonth    : ;    // 0..12  (5 bits)

   unsigned nYear     : ;    // 0..100 (8 bits)

};

int main()

{

}

The conceptual memory layout of an object of type Date is shown in the following figure.

Memory Layout of Date Object

Note that nYear is 8 bits long and would overflow the word boundary of the declared type, unsigned int. Therefore, it is begun at the beginning of a new unsigned int.

It is not necessary that all bit fields fit in one object of the underlying type; new units of storage are allocated, according to the number of bits requested in the declaration.

Microsoft Specific

The ordering of data declared as bit fields is from low to high bit, as shown in the figure above.

END Microsoft Specific

If the declaration of a structure includes an unnamed field of length 0, as shown in the following example,

// bit_fields2.cpp

struct Date

{

   unsigned nWeekDay  : ;    // 0..7   (3 bits)

   unsigned nMonthDay : ;    // 0..31  (6 bits)
unsigned           : 0;    // Force alignment to next boundary.

   unsigned nMonth    : ;    // 0..12  (5 bits)

   unsigned nYear     : ;    // 0..100 (8 bits)

};

int main()

{

}

the memory layout is as shown in the following figure.

Layout of Date Object with Zero-Length Bit Field

The underlying type of a bit field must be an integral type, as described in Fundamental Types.