Am Montag, 10. Mai 2010, um 21:28:54 schrieb
[hidden email]:
> You must keep the signatures as they are currently (default argument or
> not does not matter). But you can add methods, you can also add methods
> with the same name but different signature.
>
> For if there is
> void foo(A a, B b, C c=C())
> you can keep it and add
> void foo(A a, B b, D d=D(), C c=C())
>
> In the implementation, of course, you implement the first one by calling
> the second one.
Thanks Marcel for helping me out here, but in the meantime I also read this:
http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++saying "In the KDE project, we will provide binary compatibility within the
life-span of a major release for the core libraries (kdelibs kdepimlibs)."
This means to me within 4.4.x there have to be ABI compatibility and for 4.x
there should be at least API compability where function signatures can change.
I made some changes to libkdcraw for 4.5. For ABI compability I have to revert
them and add duplicates with new signatures. Is this really needed?
Regards, Jens
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
