[Xcb] Whatever happened to the XCloseDisplay() hooks?

Barton C Massey bart at cs.pdx.edu
Wed Oct 14 14:19:47 PDT 2009

In message <e2ed954f0910141320l88bb36fr28cd0b8b21fec603 at mail.gmail.com> you wrote:
> If the only choices are adding a magic xcb_aux_disconnect
> that applications have to know to call, or adding
> callbacks to xcb_disconnect directly, I think I'd rather
> put them in libxcb.

I'm really strongly opposed to putting callbacks in XCB
core, actually.

Mainly, I don't know where it stops: I can imagine that if
xcb_disconnect() wants them, xcb_connect() may want them for
similar reasons, and folks have long wanted them for
xcb_wait_for_event() and by the time you're done the whole
notion that XCB is a thin wrapper over the protocol is lost.
This is how it started with Xlib, too, so I think I'm sane
to worry about this.

(For another thing, callbacks are evil.  I could try to
explain, but it would take me half an hour and I have things
I need to get done right now and you can probably figure out
for yourself why I would think this.  Suffice it to say that
I don't want callbacks anyplace near me, so why would I want
them in XCB?)

Cairo is built with a really simple model: if you opened it,
you close it.  I don't think I get why having both XCB and
xcb_render_util be built on this same model is somehow a
design defect.

But probably I'm just confused as usual.


More information about the Xcb mailing list