On Friday, 10 January 2014 at 12:24:18 UTC, Robert M. Münch wrote:
Hi, not really a comment regarding the actual implementation
but I think that good debug support for signales & slots helps
a lot in using it. What do I mean with this:
- a way to dump in a human readable form the run-time
connections. Which function / class / etc. is currently
attached to which signal?
- automatic logging like a call-stack in a debugger to get an
idea when which signal is acted on
- a way to get the order of activation for debugging to
identify unwanted side-effects
- etc.
Big signal & slot implementaitons can be hard to debug, this
should be as simple as possible.
Please move discussion to matching thread linked in first post.
This one is for voting.
