On Thu, 21 Sep 2000, John Levon wrote:
> I have seen this myself. It is to do with Qt breaking by trying to use xor
> which is a keyword in standard c++. In my opinion this is a broken header
> used in Qt. For the benefit of the list the relevant section is :
>
> #if !(defined(__STRICT_ANSI__) && defined(_CC_GNU_)) && !defined(_CC_EDG_)
> && !defined(_CC_HP_) && !defined(_CC_HP_ACC_) && !defined(_CC_USLC_) &&
> !defined(_CC_MWERKS_) && !defined(xor)
> QRegion xor( const QRegion & ) const;
> #endif
> QRegion eor( const QRegion & ) const;
>
>
> Does someone want to suggest how this might be worked around ? In my
> opinion this is Qt being wrong, again.
>
This seems in fact to be a gcc funniness. We have -ansi option used, but
it is not defining __STRICT_ANSI__ (as verified via gcc ... -E -dM).
Anyone any ideas ? Or should I just #define __STRICT_ANSI__ (yuck)
john
