API & ABI Versioning...

on YouTube ↗01h 00m

" summary

Defines API vs ABI by concrete effects: symbol mangling changes when argument types change, struct size/alignment and member order change binary layouts, and adding or reordering virtual functions shifts the vtable layout so binaries break. Recommends using explicit export macros, keeping a changelog, bumping major for any API or ABI break, minor for backward-compatible additions, patch for internal fixes, and shipping migration scripts. Explains mangling and advocates embracing semantic versioning that accounts for ABI.

AI-written summary · about

" chapters (28)

1. 0:00Intro
2. 7:42Communication
3. 9:02API
4. 12:57Changes
5. 13:55Change Types
6. 15:01No Change
7. 15:33Define Behavior
8. 16:17Nonbreaking Changes
9. 17:01Relaxed Changes
10. 18:55Breaking Changes
11. 20:27Positive Integers
12. 24:53ABI
13. 25:51Infrastructure
14. 26:58Mangling
15. 28:36Changing type
16. 29:39API symbols
17. 32:17Vtable
18. 33:47Layout
19. 34:58Binary Layout
20. 38:46Semver
21. 40:14Convention
22. 41:13Documentation
23. 42:25How to include API
24. 44:57Dependency changes
25. 46:28Can I do more
26. 47:33Two things might impact
27. 55:37QA
28. 57:50Downgrade