[Xcb] about api changes

[Christoph Pfister]

2007/6/7, Christoph Pfister <christophpfister at gmail.com>:
> Am Mittwoch, 6. Juni 2007 20:17 schrieb Barton C Massey:
> > Excellent suggestion!  If you wanted to create this Wiki
> > page for us and put the stuff you list on it, that would be
> > awesome :-).
> >
> >       Bart
>
> Okay - I'm playing around a bit with this - the "1 bit" version is already
> available at http://xcb.freedesktop.org/StableAPI/ ...
>
> Christoph

Okay, the page is up now (though not linked to from any other page
yet). Feel free to add your items or to start thinking about the
existing ones :-)

Christoph


> > In message <19a3b7a80706060748k4b3e14bbxb464b67e131c5ff5 at mail.gmail.com> you
> wrote:
> > > Hi,
> > >
> > > There were some suggestions for api-incompatilbe improvements recently
> > > especially with regards to the new python generator. I'd suggest that
> > > you put them on a wiki page / create an experimental tree showing
> > > stuff / etc as it seems more and more likely that such an api breakage
> > > will happen at some point in future.
> > >
> > > Therefore I think it would be a good idea to have a process for that
> > > stabilization consisting of stuff like a) keep track of proposals (as
> > > you don't want to break the api again & again it's crucial if you
> > > forget certain points), b) review / discussion / show it concretly
> > > somewhere, c) freeze for a certain time and d) change it in one go and
> > > be happy :-)
> > >
> > > Christoph
> > >
> > >
> > > PS: some items I remember off the cuff:
> > >
> > > - iterator "mess" (e.g. quite some duplication of code for those
> > > iterators which just point to an entry in an array; maybe only having
> > > iterator_t *xcb_...s() and int xcb_..._length() for that type of
> > > iterator), ".rem" is named +/- well
> > > - some points about naming normalization
> > > - should the _request stuff be part of the public api? (e.g. compile
> > > time speedup if the headers are smaller)