A simple kdevplatform design question ...

[Sandro Andrade]

On 6/22/07, Alexander Dymo <dymo at ukrpost.ua> wrote:
>
> On 6/21/07, Sandro Andrade <sandro.andrade at gmail.com> wrote:
> > Why there is a need for separating ICore from Core ?
> As Andreas said, the plugins don't need to link to the application,
> they need to link only to the small library with well-defined set of
> interfaces (with BC guarantees).


Hi Andreas and Alexander,

As stated in http://accu.org/index.php/journals/269, the three main reasons
for separating interface from implementation are:

1) Reducing implementation detail exposed to the user
2) Reducing physical coupling
3) Allowing customised implementations

I guess the reason 3) does not apply to the kdevplatform, right ?
So, in conclusion, the reason for this programming style is just to reduce
compilation time and dependencies ? In despite of these reasons, BC issues
could be handled by a d-pointer, leading us to forget about separating ICore
from Core ?

Thanks in advance,
Sandro

_______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20070622/7511f4f4/attachment.html>