Re: C standard question?

On 11 May, 13:47, Chris H <ch...@[EMAIL PROTECTED]
> wrote:
> In message
> <f4d865b0-d912-4a2c-8cf5-1ed5b8f97...@[EMAIL PROTECTED]
>,
> Spiros Bousbouras <spi...@[EMAIL PROTECTED]
> writes
>
> >Anyway I believe that "char unsigned" is harmless
> >and does not warrant an inflammatory and potentially
> >offensive comment as "ridiculous". Especially if it's
> >the only comment in the post.
>
> I would agree however it depends on the reaction of the person being
> told that they are in a minority of 2 in a sample size of several
> 100,000.

But he wasn't told that , he was told that it's
ridiculous. Such a statistic is interesting although
I would imagine you're just guessing.

> Do compilers still accept char unsigned?

I just tried compiling
int main(void) {

char unsigned c ;
return 0 ;
}
with 2 different versions of gcc, 2 different versions
of Sun Studio 12 C compiler and splint. I got some
warnings about the unused variable but that's all.

> Some used to but I bet many
> don't now and Tomas does say he is trying to write fully ****table code.

Why would a compiler not compile something which
exists in both C standards ? If anything I would imagine
it makes the implementation more complex if one tries
to enforce a specific order between char and unsigned.