vvd, just out of interest, why add the _Q suffix to the endian ifdefs? gcc3/4 automatically define __BIG_ENDIAN__ on BE architectures and __LITTLE_ENDIAN__ ON LE architectures - I don't see the point in us requiring it to be manually defined on all platforms by using this non-standard naming? if platform-specific compiler doesn't specify endian then add a define for that platform but stick to the standard names without the _Q suffix

this is important for universal binary on mac using xcode < 2.3 (i _believe_ 2.4 allows architecture specific CFLAGS - i am downloading as we speak to test) as endian detection is expected to check the standard convention of __BIG_ENDIAN__ / __LITTLE_ENDIAN__

note from this grep that we currently have the following unique ifdefs involving endian defines in ezquake src (the one missing the _q_ suffix is in gl_texture.c)

#elif defined(__LITTLE_ENDIAN__Q__)
#elif defined(__PDP_ENDIAN__Q__)
#ifdef __BIG_ENDIAN__
#ifdef __BIG_ENDIAN__Q__
#ifdef __PDP_ENDIAN__Q__

i also don't see the point in adding 'toy' support for PDP-11 endian but i guess that is just russian eccentricity :-)

i just went ahead and fixed this in CVS as nobody replied with any acceptable reason why the __Q suffix had been added

Because this was ported from MVDSV.
Where "gcc3/4 automatically define __BIG_ENDIAN__ on BE architectures and __LITTLE_ENDIAN__ ON LE architectures" don't work, for example, on some SunOS 5.8/9 UltraSparc64.
MVDSV on PDP-11 - who know... :-)
And I made endian support same in MVDSV and in ezQauke.


Don't work. :-\

P.S. In Russia days from Dec 31 to Jan 8 are holidays.
I only today "open" qw.nu forum - too many work after holydays and have no internet at home. :-(

but this is not an answer

OK some gcc on some architectures don't automatically define the endianness, but why choose a non-standard naming convention? Just make all architectures define/redefine __BIG_ENDIAN__ or __LITTLE_ENDIAN__

Can u to guarantee what no arhitectures with "#define __LITTLE_ENDIAN__ 1234" and etc. ?
Or u propose to do:
#ifdef __LITTLE_ENDIAN__
#undef __LITTLE_ENDIAN__
#ednif
#ifdef __LITTLE_ENDIAN__Q__
#define __LITTLE_ENDIAN__
#endif
...
Or? Ur variant?

http://mvdsv.cvs.sourceforge.net/mvdsv/mvdsv/configure?revision=1.13&view=markup&sortby=date

Let project managers choose "correct" way.
In MVDSV I don't want to change this.

Let's stay with non-Q variant. There's a good point for MVDSV to have his own Q-ed version in there, ezQuake doesn't have as many target platforms as MVDSV though.