Binary Compatibility Workarounds: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(Adapt to page move)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
[[Category:Developing_Qt]]
[[Category:Developing_Qt::Guidelines]]


This page describes some workarounds for keeping binary compatibility in patch releases. You should read the KDE reference: [http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++ Binary Compatibility Issues with C++].
This page describes some workarounds for keeping binary compatibility in patch releases. You should read the KDE reference: [https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B Binary Compatibility Issues with C++].


Specifically, the d-pointer technique is explained in much detail in [[D-Pointer|D-Pointer: What Private Implementation is and how it works]].
Specifically, the d-pointer technique is explained in much detail in [[D-Pointer|D-Pointer: What Private Implementation is and how it works]].

Latest revision as of 13:43, 25 August 2017


This page describes some workarounds for keeping binary compatibility in patch releases. You should read the KDE reference: Binary Compatibility Issues with C++.

Specifically, the d-pointer technique is explained in much detail in D-Pointer: What Private Implementation is and how it works.

Declaring a slot for private classes (d-pointer)

Use a Q_PRIVATE_SLOT:

 class A: public QObject
 {
 Q_OBJECT
 
 private:
 Q_PRIVATE_SLOT(d_func(), void myPrivateSlot())
 };

/* in .cpp file */

 void APrivate::myPrivateSlot() {}

 #include "moc_a.cpp"

Pitfalls to avoid:

  • Don't include `a.moc`, but `moc_a.cpp` in your .cpp file
  • Q_PRIVATE_SLOT takes the complete signature of the private slot, not just its name