GLib/GObject+C as the lingua franca?
Aaron J. Seigo
aseigo at kde.org
Sun Jul 27 03:40:50 BST 2008
On Saturday 26 July 2008, nf2 wrote:
> Aaron J. Seigo wrote:
> > On Saturday 26 July 2008, nf2 wrote:
> >> Aaron J. Seigo wrote:
> >>> On Friday 25 July 2008, nf2 wrote:
> >>>> I wonder if a kind of mixed style would work: libraries with public
> >>>> GObject/C APIs, but internally stdc++.
> >>> the phrase "disgustingly ugly" comes to mind.
> >> Why? I think a lot of things that are tiring with plain C - like
> >> strings, containers and garbage collection might be a bit easier with a
> >> bit of C++.
> > so write in C++ but hobble it with an API designed to make up for C's
> > shortcomings? that's what i meant by "disgustingly ugly"
> I think you are a bit undervaluing GObject. I think it does a lot more
> than reinventing C++... things which are quite difficult with plain C++
> as well.
... and that's where Qt comes in. it has a very clean, consistent and powerful
API that makes up for things that are quite difficult with plain C++.
the GObject stuff is understandable when dealing with C. but when dealing with
C++, it really isn't the API the to mimic / use. there's much better Free
Software alternatives that exist right now.
the Qt world has become quite comfortable with using glib when it comes to C
related stuff out of pragmatism. the rest of the world ought to learn simiar
pragmatism; it's nonsense to uglify code when the only reason is to molify a
bunch who lack similar pragmatism.
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 194 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel