RE: [Freetype] FreeType 2 changes required for XFree86

[Mark Storer]

>> Why doesn't XFree86 follow common C protocol and use uppercase?
>Perhaps because this is not *that* common, except of course for
>the C code produced by a small company in far north-west USA,
>named something like yocto$oft.  ;-)

It's not all that common for Them either... they have #def's for "min" and
"max".

The STL implementation They ship required a nasty workaround for STL's min &
max.  Not Pretty.

My two bits (01):
#defines for common names are bad.  Period.

--Mark Storer
  Software Engineer
  Cardiff Software

#include <disclaimer>
typedef std::disclaimer<Cardiff> Discard;