Search:

That's true.

I'm just trying to justify the use of moc in Qt (because I'm a big fan of it).

This library also claims to make programming more intuitive and OO by not using macros, etc. But Qt...

The biggest difference between that and Qt's signals and slots system is that in S&S, the object generating the event doesn't need to explicitly call callbacks. The meta objects system does that for...

What if it has multiple functions?

Classic OOP theory says objects should represent "things" with state (properties), and actions (methods).

If something only does one thing, isn't it a...

Or we can also think of them as a function that is defined like an object. I think from places I have seen functors used, that's a more conceptually accurate description. It's not an object that...

It is an object, but it doesn't represent a function in the world. It represents an action, a function. It's not REALLY conceptually an object.

I don't think it's just the type system. The callback system assumes that the "interested party" is a function (or functor, which is conceptually a function), instead of an object, which is not OO.
...

The reason Qt went with their own syntax (signals and slots) was because they thought, the way everyone else was doing it, with event callbacks (I haven't looked into your library, so I don't know if...

Ah! Like a not-ugly version of FLTK. That would be great actually. Qt has a fairly steep learning curve.

What does it do better than Qt?