interfaces / implementations separation (was Let's discuss KDevelop4 interfaces and shell)

[Alexander Dymo]

On Saturday 20 January 2007 02:50, Matt Rogers wrote:
> Yes, I agree that it is a neat side effect. However, I don't agree that
> each thing that is useful in a plugin requires an abstract interface.
> Kopete has a PluginController class that isn't an interface and that has
> worked fine since 2003. Just because it's useful in a plugin, doesn't mean
> that it requires an interface.
Right, but it's not possible to have your cake and eat it. We shall
have either interfaces or no interfaces. Having both would indicate design
problems.