[Xcb] EWMH API for XCB

[Arnaud Fontaine]

>>>>> Josh Triplett <josh at joshtriplett.org> writes:

Hi,

    >> Well,  I think it  would be  better to not  make it static  as it
    >>  could  be  useful  to  any program  implementing  extensions  to
    >> EWMH. Therefore,  I have just added an  assert()[0]. I think it's
    >> ok this way, isn't it?

    >  In XCB,  we've  had  some bad  experiences  with asserts,  simply
    >  because end-users  notice them  and blame  XCB rather  than buggy
    >  applications. :) Detecting  problems at  compile time  seem ideal
    > when you can.  This  case seems somewhat less problematic since an
    >  application  would  have  to  explicitly use  your  new  library;
    > however, I'd still suggest  doing as much checking as you possibly
    > can at compile time.

Yes, it makes sense, I didn't  think about that point. Could you suggest
a patch as I don't really know how to do it properly? Thanks much.

Cheers,
Arnaud