Moveing KDevelop from python

[Bernd Gehrmann]

On Monday 06 May 2002 22:05, you wrote:
> On Monday 06 May 2002 3:43 pm, Bernd Gehrmann wrote:
> > No, you always pay. Wrappers of any kind that are not automatic suffer
> > from bit rod over time. See also the java bindings for an excellent
> > example.
>
> I agree the java bindings are difficult to keep up to date. But the only
> solution that has been suggested is to make the static bindings generation
> more complete and less error prone, so that less skill is involved in
> maintaining them. C++ is a static language, apart from Trolltech's
> extensions (RTTI is no use for dynamic programming). Even Apple's Cocoa
> Objective-C <--> Java bindings need some static hints, although it can do a
> whole lot more at runtime.

I'm not sure what exactly you mean by "static hints", but one way to
influence the code generation would be to add certain kdoc-like
tags to the header files instead of modifying the code by hand after
the code has been generated. Don't know if that's possible in the
cases you are talking about.

> Ashley Winters has done some *very* interesting stuff in wrapping the Qt
> api (and soon the KDE one) in a language independent manner.

Looking at xdata.cpp, I wasn't aware that C++'s multiple inheritance makes
so many problems...

Anyway, sharing as much as possible between different languages
certainly seems like a good way to reduce maintainance costs.

Bernd.