KWIG Qt->Gtk porting layer and merging main loops.

[Christian Neumair]

Am Freitag, den 29.10.2004, 18:30 +0200 schrieb Alexander Neundorf:
> On Friday 29 October 2004 16:33, nf wrote:
> > I think - one day - you will have to make a decision on the hierarchy of
> > technologies: Choose one technology for the tiny common back-end bits
> > and others for the layer above that.
> >
> > Agreeing on a common back-end "technology" (fd_glib i would suggest)
> 
> AFAIK glib contains e.g. container classes and stuff.
> Why should a C++ developer use C container functions ?

No, it doesn't. Glib is written in pure C (optionally, ISO-C99 extension
are used) and covers exclusively helper/abstraction/higher-level code
for many routine tasks, like string parsing, file handling, i18n and
friends. It's very much a convenient collection of helpers.
The fundamental object/class implementation is inside gobject. Most
distros ship it as one package, though. You may want to cp.
$PKG_CONFIG_PATH/(glib|gobject)-2.0.pc and
$PREFIX/include/glib-2.0/(glib|gobject)/.

> There is the STL and there is Qt and soon QtCore.

What's your point? I admit that C++ has very nice standard libraries,
and might have advantages (simula-style oop) for high-level classes, but
for low-level UNIX taks/apps C/glib\{gobject} IMHO is still the way to
go.

regs,
 Chris