glib dependancy in KDE3.x
lypanov at kde.org
Fri Mar 7 17:58:41 GMT 2003
On Fri, Mar 07, 2003 at 06:46:22PM +0100, Guillaume Laurent wrote:
> No, it's not. If KDE is so much ahead in terms of integration, it's because
> it's C++ all throughout. That is not a necessary condition, but it helps
Wrong, its because we have naturally defined c++ bindings
to everything that is important. This doesn't need to be
an exception for arts.
> I don't really care. Ressources-wise, glib is a rounding error on most current
> machines. Avoiding to duplicate it is certainly a good thing. However, using
> it because "some things must be implemented in C", is not a good reason.
Very much agreed. If its in C it should be in C. If C++, then C++.
Not half half unless its for some bridging requirements. Which I
thought it was for.
> I've been told that arts is in C so that Gnome can use it. It then makes sense
> to use glib. If it's in C for any other reason, then it should be moved to
Unfortunately, AFAIK, Gnome doesn't reuse it...
More information about the kde-core-devel