The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: qt license

Jason Gunthorpe <jgg@gpu.srv.ualberta.ca> writes:

> Now, my point is simple, GTK is nice, but it's not perfect. Compare the
> GTK code with my code and you well see what I mean. GTK uses a large
> number of macros to implement their OO ontop of C which makes the client
> code harder to read and harder to write. The C++ Deity widgets have
> no such problems.

> I -really- like how GTK is designed (Deitys widget's follow an almost
> identical path, even though I had no knowledge of how GTK worked till very
> recently) but I highly dislike the use of a contrived OO mechanism ontop
> of plain C.

I think that the right way to do it (if you want your widget set to be
likely to get wide distribution) is to write it in C and then provide
a C++ wrapper for those who prefer that.  Note that that's already
been done for Gtk.  Go to www.gimp.org and follow the pointers to the
Gtk page.  You'll see there's a gtk-- which provides C++ wrappers for
Gtk.

I'm sure the fact that Gtk was written in C has had a lot to do with
the fact that there are already python, perl, SCM, guile, and C++
implementations/interfaces in the works.

Personally, though I use C++ for a decent chunk of my work, I was
really surprised at how much easier the Gtk source is to read and
debug than most C++ code I've come across.  Also, and I don't really
want to get into a big language war here, but without using RTTI, the
method that the Gtk authors chose for implementing a class system
allows them to do dynamic stuff more easily than you can with the
default C++ class heirarchy, and their signal mechanism (if I
understand it right) gives more runtime flexibility than the default
C++ virtual function setup.

Now I know that you *can* do the same thing in C++, but my experience
has been that because C++ already has mechanisms in place to do
something approximating what you want in these areas, many people
don't bother to go the extra mile.

-- 
Rob Browning <rlb@cs.utexas.edu>
PGP fingerprint = E8 0E 0D 04 F5 21 A0 94  53 2B 97 F5 D6 4E 39 30


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .