aboutsummaryrefslogtreecommitdiff
path: root/nx-X11/lib/X11/lcUniConv
diff options
context:
space:
mode:
authorJeremy Huddleston <jeremy@tifa.local>2008-02-10 19:04:40 -0800
committerMike Gabriel <mike.gabriel@das-netzwerkteam.de>2016-11-02 19:46:36 +0100
commitf686bc3ebed90b7fb8bbbf8cce3d894971e42ca5 (patch)
tree941929eff16ad18fe7c0a6f8c1a4463649f86976 /nx-X11/lib/X11/lcUniConv
parent64d51869fcc6ae4dd4c8d3e1d924fa2e4ccc75af (diff)
downloadnx-libs-f686bc3ebed90b7fb8bbbf8cce3d894971e42ca5.tar.gz
nx-libs-f686bc3ebed90b7fb8bbbf8cce3d894971e42ca5.tar.bz2
nx-libs-f686bc3ebed90b7fb8bbbf8cce3d894971e42ca5.zip
Fixed #ifdef checks that were using i386 to use __i386__
""" It's simply obsolete, sloppy, compiler namespace pollution. The compiler is not allowed to predefine symbols that might conflict with ordinary identifiers. For backwards compatibility gcc currently predefines i386 when compiling for x86 32-bit (but not 64-bit), but that will go away. It is also not defined if you specify -ansi when invoking the compiler, because then it is seriously standards compliant. Other compilers shouldn't define it either. Correct code shouldn't rely on it being defined. However __i386__ is safe and proper. """ Backported-to-NX-by: Ulrich Sibiller <uli42@gmx.de>
Diffstat (limited to 'nx-X11/lib/X11/lcUniConv')
0 files changed, 0 insertions, 0 deletions