Tru64 and 2.2 problems - cast-to-union

[Nikola Milutinovic]

> Just to add an oppinion.
>
>> I do not and cannot accept the point "GCC is standard - yield to it". GCC
>> is "yet another C language standard" and should be treated that way. So
>> far we have K&R C, ANSI C, ISO C and GNU C. I would welcome emerging of
>> ONE C standard, but then we should all push for it.
>>
>> Why would GCC be more "expressive" that ANSI C (which is mostly supported
>> as a standard, I believe)? Is ANSI C unportable to GNU C?
>
>I 100% agree with you here!  I love GCC, but I like to use other compilers
>too, and as it turns out, I prefer to program in such a way that my code
>will compile on *any* C compiler if at all possible.  I don't understand
>the reasoning behind the "just use gcc" group when there are many better
>reasons to use a native compiler designed for the platform to be used.

It is not just whether native compiler is better that Global GNU CC. It is
(for me) a point of expressiveness. What is it that you can express with GCC
constructs, that cannot be expressed elegantly with ANSI C? If there is
something like that, then propose it as a change in standard, rather than
being autistic and saying "it's either GNU way or the highway" (deliberate
exageration in this case).

>By the way, you are sending your responses directly to me... why not CC
>the mailing list too?  I think it is worthy of discussion!

Sorry. Corrected.

Nix.