You do have unit tests, don't you? ;-)
Of course not! Real Men don't use unit testing! Just like Fortran is for quiche eaters! ;)
Btw, what sort of "callbacks" are you using? This strickes me a C type thing, rather than a C++ one. Are you using the WIndows API or something?
No the callbacks I'm talking about are libsigc++ callbacks. I'm not sure if you can still really qualify them as normal callbacks, maybe you know libsigc++ but it's a C++ signal/slot implementation for typesafe callbacks. I use it a lot to separate logic from GUI elements and the gtkmm library (a C++ wrapper around GTK) uses it exclusively for that purpose. For example when some custom control that I wrote emits a signal like 'changed' and I'd like to update the preferences object, I'd have to pass in the preference object from the control, which is ofcourse not desired since it would couple the UI element with the program. The solution in this specific case is to store the preferences object (at least a pointer or reference) in the object where the callback function is, but I've run across situations where this isn't as obvious as it would seem. (don't ask me to describe them in detail, it was usually when trying to decouple old code while maintaining backwards compatible with the way things worked before).
cheers,
roel
