Cool guys,<br>Thanks for the answers they made everything clear for me ^_^. By the way I'm really considering on getting close to XCB developing after GSoC ends, I"m really impressed with X. After learning a little more about X I feel that it's architecture design was really well-done and probably years ahead of it's time.<br>
<br>Regards =],<br>Marcos <br><br><div class="gmail_quote">2010/5/27 Barton C Massey <span dir="ltr"><<a href="mailto:bart@cs.pdx.edu">bart@cs.pdx.edu</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">In message <<a href="mailto:87mxvnyria.fsf@keller.adm.naquadah.org">87mxvnyria.fsf@keller.adm.naquadah.org</a>> you wrote:<br>
> On Wed, May 26 2010, Marcos Roriz wrote:<br>
> > One of the thing that I didn't understand is why does<br>
> > XCB/Xlib needs to generate Xml for the protocol isn't<br>
> > the protocol fixed (at least at core), i.e., "imutable",<br>
> > ins't better/easier to just create a implementation or<br>
> > does it really needs the power of dynamic generation the<br>
> > C bindings?<br>
><br>
> The protocol, and its extension, are fixed. The XML files are<br>
> hand-written to describe this protocol. Then this XML files are used to<br>
> generate various bindings for various languages.<br>
><br>
> This mean you do not have to write a full implementation for each<br>
> language, just a binding generator.<br>
<br>
</div>Originally, we took this approach to get rid of a lot of<br>
repetitive, error-prone hand-generated boilerplate C code.<br>
The ability to automatically produce X11 bindings for other<br>
languages, and to easily add understanding of X11 to tools<br>
such as Wireshark, has been a nice bonus. The XML also<br>
serves as reasonably nice documentation of the protocol; at<br>
some point we may consider canonicalizing it as the<br>
definition of some X11 extension protocols.<br>
<br>
If nothing else, it has been good to test the X server<br>
against a client library that was developed independently of<br>
Xlib: we've found a few server bugs that were masked by<br>
corresponding Xlib bugs that way.<br>
<br>
Bart<br>
</blockquote></div><br><br clear="all"><br>-- <br>Marcos Roriz<br>Bacharelando em Ciência da Computação<br>Universidade Federal de Goiás<br><br>E-mail: <a href="mailto:marcosrorizinf@gmail.com">marcosrorizinf@gmail.com</a><br>
Home Page:<a href="http://marcosroriz.wordpress.com">http://marcosroriz.wordpress.com</a><br>