> btw, i just gave abi a compile last night i was a bit miffed to see the
> spew of errors from mswordview (a bit shamed really). And i wondered about
> the errors from constructs like
>
> unsigned char test:3;
>
> I think that this results only in a warning with gcc's -traditional option, but
> id like to be reassured that bitfields are an actual part of ansi c, and that
> there no hidden compiler dependancy in using them ?, anyone know ?
To me it looked like it was dissatisfied with the "char" part of it, not
the ":3" part of it. "unsigned int test:3;" ought to work beautifully?