Re: [Fonts]Re: [Freetype] FreeType 2 changes required for XFree86

[Juliusz Chroboczek]

BS> Defining common names like ''read'' always leads to problems 
BS> when using multiple packages. 

BS> Why doesn't XFree86 follow common C protocol and use uppercase? 

BS> Better yet, why not use a name like XF86_READ to avoid conflicts
BS> on such common names? 

The goal being to use common source code both in the X server (when
using the wrappers) and outside it, it would be rather pointless to
use ``common C protocol'', wouldn't it?

The symbol name is xf86_read; it is the choice of the module author
whether to include xf86_libc and use xf86_read directly, or whether to
include xf86_ansic and have a nice define from read to xf86_read.

                                        Juliusz