> People do get obsessed with optimisation, yes. But, anyway, we couldn't > change this now, without breaking ABI.
All very true. > I suggest that you > a) Store a second piece of information alongside each signal, > identifying the signal type. > b) Use static_cast<>, after you've discovered what the type is. Since the types provided as template parameters to class template sigc::signal#<> is a compile-time notion, this can only work if some predefined set of signal instantiations is used and hence not a very flexible solution. But hopefully I am wrong. _______________________________________________ libsigc-list mailing list libsigc-list@gnome.org http://mail.gnome.org/mailman/listinfo/libsigc-list
