First of all… HAPPY NEW YEAR ALL !!
I felt I had to do some research… and I did for couple days till yesterday morning I felt ill as hell. Now, I’m getting better, and it seems the “virus” that hit spain got me too… Anyway, I’m winning the battle to my flu.
So, before getting ill, I had a look at Qt’s signals and slots, and wondered if I could do something similar myself. Well, I called this tiny library “Ideal”, and till now it only has signals/”slots” (there are no slots, we’ll see later) and a small timer for testing purposes…
I don’t mean this thing to be huge, but I guess I will be working on it from time to time. However, it was a great thing for me seeing it working. The “bad” thing: it uses c++0x stuff to work.
Let’s see a small usage example:
using namespace Ideal;
using namespace Ideal::Core;
using namespace std;
: public Object
MyObject(Object *object = 0);
IDEAL_SIGNAL(mySignal); // signal with no parameters
IDEAL_SIGNAL(pushed, bool); // signal with a bool parameter
, IDEAL_SIGNAL_INIT(pushed, bool)
: public Object
OtherObject(Object *object = 0);
void receivedSignal(Object *sender);
void buttonPushed(Object *sender, bool param);
void OtherObject::receivedSignal(Object *sender)
cout << "received a signal ! (from object: " << sender << ")" << endl;
void OtherObject::buttonPushed(Object *sender, bool param)
cout << "button pushed ! (from object: " << sender << " and param " << param << ")" << endl;
int main(int argc, char **argv)
// simulate that something happened, and see how slots become called
object.pushed.emit(true); // this two calls won't have any effect (no "slots" called)
This is the general look of this stuff… the pros:
- Signal/Slot type safe at compile time, not runtime.
- No external tool like ‘moc’ needed for signals to work (also a weak point, see later)
- You know in which order “slots” will become called. Planned also a way to “reorder” the way they will. At this very moment, they are called in the exact order they are connected.
- Slightly faster than Qt’s signal/slot callings (based on a test that was doing 1.000.000 calls).
- Don’t know if a strong point: there is no slot concept. They are callbacks, you can call the method you want using signals without mattering if it was declared as a slot or not. I can see the use case where you would have expect something to have been a slot but it isn’t, so you can’t call it easily with Qt’s signals/slots.
- Tiny tool. At this very moment, this library only contains a timer and the signal/”slot” thingy.
- Because no tool like ‘moc’ is needed, I haven’t got that cool meta object information that Qt has.
- It uses a new feature from c++0x.
- Won’t be public until I have something more to show.
- One-way-of-doing-it principle. Will try to KISS by letting the library user doing a certain thing in a certain way.
- Correction. As everything… on the real paper this is much more difficult than in the theory
- There is no interest in having this library built with old compilers and other systems than GNU/Linux (or better said, POSIX compliant). I mean, we all can get a free operating system which builds this library, so I don’t find the reason for making this library build for, say Solaris 2. However, the way it is going to be written allows it to be also expandable for other operating systems. Based on conditional d pointers where there is a d pointer for system doing the nasty job behind the cool scenes of the nice API.
- C++ on steroids usage.
- Obviously, this will be free software. At this very moment I have licensed the very small work as (LGPLv3), but well, I need to really study better all the licenses and decide.