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

Matt Rogers mattr at kde.org
Sat Jan 20 00:50:13 UTC 2007


On Friday 19 January 2007 4:39 pm, Alexander Dymo wrote:
> On Friday 19 January 2007 20:41, Matt Rogers wrote:
> > You didn't need to do that in general, but specifically for the three
> > classes that you singled out in your proposal. It wasn't until Jens
> > mentioned the link time advantages that it became apparent to me what
> > having a
> > PluginController interface gives us.
>
> I still think link time is a neat side-effect of plugins vs shell
> independence. For each thing that is useful in plugins there has to
> be an interface. And plugin controller happens to be one of such things.
>

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.
-- 
Matt




More information about the KDevelop-devel mailing list