When you make a change in your code, it’s important to consider the potential impacts on your clients. At CppCon, I gave a talk about those impacts, both on API & ABI, and how to advertise them.
As I said in my trip report, I had two talks at CppCon this year. The first one was about using CMake for Modular Design. The second one is about changes in your library will impact your clients through API & ABI and how to tell them about it through versioning:
Do you think about your libraries in CMake in term of compiler flags or architecture modules? In this talk, I show you how to do the latter.
For those who couldn’t make it to CppCon 2017, the video of my first talk “Using Modern CMake Patterns to Enforce a Good Modular Design” is now online: