make IStatus pure virtual?

[Andreas Pakulat]

Hi,

just fixed a minor nuisance in IStatus and while porting the places
implementing an IStatus I was wondering wether it makes sense to make all
those "signals" on the interface pure virtuals.

The benefit of that would be compile errors if any IStatus subclass has an
error in its own declaration of those signals (IStatus is not a QObject
hence they're no signals on that class yet).

The downside would be that each IStatus subclass would have to provide all
of the signals, even if it doesn't use them. This is already the case for
some instances, which declare all signals but use only one or two...

So basically the question is: Is there a good reason why an IStatus
subclass would declare only some of the signals from the interface?

Andreas

-- 
You'll wish that you had done some of the hard things when they were easier
to do.