11 Feb
2007
11 Feb
'07
11:13 p.m.
Timmo Stange wrote:
As for your solution: If I understand it correctly, your signal does not support the full ordering of the original version. You can establish an order (through at_back/at_front) within the groups and for the ungrouped slots in one signal. The standard containers don't support that notion. You'd need a (meta-)key with an infinite value range to support at_back/at_front in a std::map.
Sorry, I only looked at your group_key_less comparison here. I saw now that you use a list as container and a linear search in signalN::connect, which ensures the correct order. That works as expected, of course, but significantly changes the complexity of connect() to the worse compared to what the current docs say. Regards Timmo Stange