Todo List

Class dcouple::signal::GenericSignal

access specifiers

Member dcouple::signal::Signal ()

We would like to only allow emit() to be called by the owner. Should we require a this pointer to be passed which we can check? A bit hackish, and Signals that are not owned can not be protected this way. We could just assume that the user does not call emit from strange places, but it may cause a security risk in some application.

Member dcouple::slot::Slot ()

Free slots have a problem. When they receive a signal during a garbage collection run, e.g., from an object that is configured to emit a "destroyed" signal, at a time when they themselves have become garbage (or more importantly, their call back function) they can cause a segmentation fault when calling the collected function. This situation is likely to occur at program termination (when "almost" verything is collected). This is supposedly not a problem for owned slots that refer to member functions of the owner, because the destructor of the owner is called before its members are invalidated (right?). Solution: have all free slots register with a global static SlotManager. Before letting the program terminate, this owner must be instructed to disconnect all slots.

---