[Xcb] Hello xcblist.

Thomas Heller thom.heller at googlemail.com
Wed Feb 3 23:00:14 PST 2010

Hi all,

This is my first post too. For the last couple of month i tried to
develop C++ bindings for xcb from scratch.
Some basic stuff works for now, I initially decided to not write a
generator for the xml files.
However this approach led to nothing.
This is the reason i wrote a parser using boos.spirit. The parsing
works, but i couldn't find any
spare time to finisch the generator.
The reason i am posting is that in the presence of a new binding you
guys might be interested in the stuff
i did so far.
You can find the source at: http://github.com/sithhell/xcppb

Any suggestions and comments are very welcome,

On Thu, Feb 4, 2010 at 6:58 AM, Barton C Massey <bart at cs.pdx.edu> wrote:
> In message <20100204012124.9ed00b6c.Highjinks at gmx.com> you wrote:
>> Recently I've picked up Modula-3, and decided to do an XCB
>> binding for it.
> Cool.  I hadn't even thought about M3 in years.
>> Looks like the best course of action would be to
>> autogenerate the binding using the XML schema in the
>> repository.
> Indeed.
>> Should I write my own parser? Extend the ones in the
>> repository?  Any tips on where I should get started?
> I'd look at hacking up the Python-based C code generator to
> emit M3.  I think this will be the lowest-energy route.  The
> modularity of that looks to me good enough that you should
> be able to replace only a couple of files.
> There are two general approaches to writing language
> bindings for XCB.  One is to write a from-scratch binding
> including a runtime entirely in the target language,
> ignoring the existing XCB C library altogether.  The other
> is to write just an XCB "stub generator" for the target
> language, and use the target language's FFI to interface
> with the "bottom half" XCB C library, much the way that Xlib
> does.
> The second approach is generally preferred; it allows
> target-language applications to freely mix FFI calls to
> libraries that indirectly talk to XCB with direct XCB calls.
> It also leverages the extensive work that has gone into the
> XCB bottom half.
>> Would the XCB team welcome an M3 binding?
> We welcome bindings for any language!  If you're asking
> about eventually moving it upstream, yes we would be
> amenable to that once it's solidly working.
> Good to meet you!
>    Bart
> _______________________________________________
> Xcb mailing list
> Xcb at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xcb

More information about the Xcb mailing list