Re: Cooperating on .defs API specifications

[Murray Cumming <murrayc murrayc com>]

On Tue, 2004-03-30 at 21:52, Andreas Rottmann wrote:
> Owen Taylor <otaylor redhat com> writes:
> 
> > I think we'd actually open to include .defs with the modules themselves;
> > the downside being, of course, that you don't get updated defs until
> > the module releases a new version.
> >
> > The other downside is that it is easy for the GTK+ version to get
> > out of date if people aren't careful about putting back their changes
> > to the canonical version ... 
> >
> I think would be not a good idea, for the reasons you already
> mentioned. The thing is: the GTK+ people, (or other module authors),
> don't actually use the .defs, only the wrapper people do. IMHO, it
> makes much more sense to have them in their own package, maintained by
> the people who need them.

Having GTK+ defs in GTK+ will work if that part of GTK+ has a
maintainer, so that changes can be made instantly. It might not be
possible for all other modules, but it doesn't need to be.

I would expect individual bindings to copy the .defs out of GTK+ at
regular intervals rather than actually using the file directly from
GTK+. Otherwise there is a big risk of breaking 4 bindings projects when
1 binding project makes a change.

-- 
Murray Cumming
www.murrayc.com
murrayc murrayc com