diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2021-03-24 13:56:48 +0100 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2021-03-24 23:45:29 +0100 |
| commit | 8593b15c77f7f2a73512261a0b0b97a64e5e93c8 (patch) | |
| tree | 3d63ed505051917847ac569d2276fcfb82b9d39b | |
| parent | a5eee22e594c2460f7d8d0a95316244abf8f9f27 (diff) | |
| download | curl-8593b15c77f7f2a73512261a0b0b97a64e5e93c8.tar.gz | |
docs/ABI: tighten up the language
Make the promises more firm
Closes #6786
| -rw-r--r-- | docs/libcurl/ABI.md | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/docs/libcurl/ABI.md b/docs/libcurl/ABI.md index 39134a1ae..be5ce2da2 100644 --- a/docs/libcurl/ABI.md +++ b/docs/libcurl/ABI.md @@ -9,17 +9,16 @@ ABI - Application Binary Interface ## Upgrades - In the vast majority of all cases, a typical libcurl upgrade does not break - the ABI at all. Your application can remain using libcurl just as before, - only with less bugs and possibly with added new features. You need to read - the release notes, and if they mention an ABI break/soname bump, you may have - to verify that your application still builds fine and uses libcurl as it now - is defined to work. + A libcurl upgrade does not break the ABI or change established and documented + behavior. Your application can remain using libcurl just as before, only with + less bugs and possibly with added new features. ## Version Numbers - In libcurl land, you really can't tell by the libcurl version number if that - libcurl is binary compatible or not with another libcurl version. + In libcurl land, you cannot tell by the libcurl version number if that + libcurl is binary compatible or not with another libcurl version. As a rule, + we don't break the ABI so you can *always* upgrade to a later version without + any loss or change in functionality. ## Soname Bumps @@ -50,7 +49,7 @@ ABI - Application Binary Interface ## History The previous major library soname number bumps (breaking backwards - compatibility) have happened the following times: + compatibility) happened the following times: 0 - libcurl 7.1, August 2000 |