xcb-proto 1.0 RC2

The X protocol C-language Binding (XCB) is a replacement for Xlib featuring a small footprint, latency hiding, direct access to the protocol, improved threading support, and extensibility.
xcb-proto project contains descriptions of the X Window System core protocol and selected extensions in an XML-based data format.
They are used by the X C Binding (XCB) library to generate much of its code, but you can also use these descriptions for other purposes, such as decoding the X protocol or building X Window System bindings for other languages.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type sh ./configure instead to prevent `csh from trying to execute configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- < import >xproto< /import > was explicitly added to extensions that use xproto. "union" was changed to "xidunion" for XID unions like DRAWABLE and FONTABLE, so that the code generator can more easily declare these XID unions as integer typedefs rather than unions.
- Structures attempting to provide C type safety were replaced with CARD32 typedefs.
- render.xml now describes CompositeGlyphs* as taking lists of BYTE, rather than lists of unions of structures of lists.
- The caller must construct an appropriate sequence of glyph elements.
- XCB didnt properly handle the previous definition.