[signals] rationale for signals::connection::disconnect() const

14 Feb
2007
14 Feb
'07
4:40 p.m.
I just noticed that boost.signals declares signals::connection::disconnect() as a const member function. Can anyone explain to me why that was done? It seems like a non-const operation to me. That's how I declared it in thread_safe_signals, and it doesn't seem to cause any problems there. -- Frank
6623
Age (days ago)
6623
Last active (days ago)
0 comments
1 participants
participants (1)
-
Frank Mori Hess