Very, very fast event library
Since the connectionSet::Clear() function merely calls a std::vector::clear(), would it not be safe to iterate, copying all but erased connection?
By reseting your connections I meant if you had a Connection d just doing d = Connection(). If you had two connections that refer to the same signal/slot combo, then do it to both of them. This obviously won't work if you're using a ConnetionSet (but I'm not a big fan of the ConnectionSet class if you couldn't tell from the rest of this thread).
Yeh, either keep the Connection around by itself and set it to an empty connection, or remove it from whatever container you're keeping it around in. ConnectionSet is primarily used as a detail class right now; there's no reason to use it if you need functionality it doesn't offer.
Quote:Original post by Promit
I'd like to take this time to suggest a promotion for SiCrane from Staff to Total Badass Developer.
I support the motion.
Thank you for the interesting article and great library!
I think Don Clugston's library could be made a little bit more portable (across gcc compilers) if he had used the gcc extension 6.6 to extract the function address from the member function pointer without any nasty structure and algorithm.
But his way is cooler [smile]
I think Don Clugston's library could be made a little bit more portable (across gcc compilers) if he had used the gcc extension 6.6 to extract the function address from the member function pointer without any nasty structure and algorithm.
But his way is cooler [smile]
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement