[Xcb] XML description of GLX conditional reply lists
jamey at minilop.net
Tue Nov 28 21:37:35 PST 2006
I was just looking again at our GLX protocol description. Several GLX
requests currently aren't expressed well. A simple change to the C code
lets XCB be more natural, while still backward compatible with XCB 1.0.
But what description should go in the XML?
Here's the challenge. If GetBooleanv, for example, has only one BOOL to
return, then it returns it in a fixed spot in the reply. Otherwise, it
treats that fixed spot as padding and uses a list instead. Currently, a
caller needs code like this to read the reply: 
if(xcb_glx_get_booleanv_data_length(reply) != 1)
result = xcb_glx_get_booleanv_data(reply);
result = &reply->datum;
This pattern should move into xcb_glx_get_booleanv_data and friends.
Such a change doesn't break ABI or API, because the behavior of
xcb_glx_get_booleanv_data only changes when length is 1, and in that
case the current implementation returns a pointer to unallocated memory.
So I know where I want to get to in the generated code, but I'm not sure
how to get there in the XML descriptions or the XSLT. Ideas?
 Jeremy, I think the Mesa XCB port is buggy in these requests. If
data_length is 0, then Mesa/XCB looks at datum; but if there was one
item, my reading of server source says data_length would be 1. I think
you were confused because on Xlib Mesa checks that reply.length is
non-zero, but that's not the same as the field that XCB calls "n".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/xcb/attachments/20061128/cba1c636/attachment.pgp
More information about the Xcb