[Xcb] OK, maybe API isn't *quite* stable... :-(

[Jeremy A. Kolb]

On Mon, 12 Dec 2005, Vincent Torri wrote:

> 
> 
> > The other issue is the awful naming convention. Getting names to have
> > sensible case is a matter of a little bit of XSLT work and a little
> > fixing of the protocol descriptions -- but porting existing code is
> > going to be a pain. Still, I think this is something we should do. I
> > know exactly what I was thinking when I picked the name
> > "XCBConnSetupSuccessRep", and it was really dumb.
> 
> I've read that xml will be replaced by python. If so, we should be clear
> on what the naming convention is. For my part, I like the usual c-style
> (downcase, _ separated)
> 
> There is a draft about the naming convention (the xcb site is down for
> me, I can't check) ?
> 
> Vincent
> _______________________________________________
> Xcb mailing list
> Xcb at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xcb
> 

The xml should stay, it would just be python instead of xslt that would 
generate the code.  I do like the idea of using xslt since that just seems 
more portable to me, but I don't know what I'm talking about ;)

As for the naming conventions I agree with you Vincent, at least for 
function falls.  One thing that's REALLY bugged me are the enum names, 
they all end up really long.

Jeremy