[Development] Binary Compatibility question (KDE)
Thiago Macieira
thiago.macieira at intel.com
Fri Feb 28 17:26:20 CET 2014
Em sex 28 fev 2014, às 11:10:41, André Somers escreveu:
> To me, it doesn't sound reasonable to expect an unqualified &func to
> stay source compatible. If you want your code to be source compatible
> with future vesions and you use function pointers, I'd suggest to always
> use the longer, ugly cast version. I don't think it is unreasonable that
> in the future overloads are introduced for existing functions,
> especially for non-slots.
>
> BC is IMHO a big enough constraint. Lets not bind our hands even further...
For most functions, I agree.
However, we need to be careful about signals. Since they are very, very often
used in:
connect(obj, &Klass::somethingChanged, ...)
We need to ensure that we aren't adding overloads to signals.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list