On Fri, 14 Aug 2009, Pedro Lopez-Cabanillas wrote:
>> gtkmm is signal/slot based too, but because of its closer integration
moc is processing source code by scanning it and then generating code that
will be fed to the compiler. This is a preprocessor.
I love Qt, really... but having to use moc is annoying. I'm not alone in
this. Plus, syntax highlighters sometimes choke on Qt's syntax.
>> signals & slots are a callback mechanism too. they just hide it from
Not exactly. You can manipulate run-time connections with either library.
libsigc++ requires that the types of the connections being made at runtime
are already known at compile time.
Qt allows you to make connections between signals and slots whose types
are not known until runtime.
This difference is generally not significant to an application designer.
The only place I know that this ability is being utilized is in KDE where
the UI's are being created at run-time from an XML file specification.
And with a little planning, you could probably do something similar with
Linux-audio-dev mailing list