generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ABI: remove the ascii logo

Browse Source 
and made the indent level to 1
This commit is contained in:
Daniel Stenberg
2015-07-30 12:16:14 +02:00
parent fc69e2f7ec
commit 5b9a006b8f
1 changed files with 31 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/libcurl/ABI
View File

@@ -1,13 +1,5 @@
_ _ ____ _
___| | | | _ \| |
/ __| | | | |_) | |
| (__| |_| | _ <| |___
\___|\___/|_| \_\_____|
libcurl's binary interface
ABI - Application Binary Interface ABI - Application Binary Interface
---------------------------------- ==================================
"ABI" describes the low-level interface between an application program and a "ABI" describes the low-level interface between an application program and a
library. Calling conventions, function arguments, return values, struct library. Calling conventions, function arguments, return values, struct
@@ -21,9 +13,9 @@ Upgrades
In the vast majority of all cases, a typical libcurl upgrade does not break 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, 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 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 the release notes, and if they mention an ABI break/soname bump, you may have
have to verify that your application still builds fine and uses libcurl as to verify that your application still builds fine and uses libcurl as it now
it now is defined to work. is defined to work.
Version Numbers Version Numbers
--------------- ---------------
@@ -54,9 +46,9 @@ Downgrades
Going to an older libcurl version from one you're currently using can be a Going to an older libcurl version from one you're currently using can be a
tricky thing. Mostly we add features and options to newer libcurls as that tricky thing. Mostly we add features and options to newer libcurls as that
won't break ABI or hamper existing applications. This has the implication won't break ABI or hamper existing applications. This has the implication
that going backwards may get you in a situation where you pick a libcurl that going backwards may get you in a situation where you pick a libcurl that
that doesn't support the options your application needs. Or possibly you doesn't support the options your application needs. Or possibly you even
even downgrade so far so you cross an ABI break border and thus a different downgrade so far so you cross an ABI break border and thus a different
soname, and then your application may need to adapt to the modified ABI. soname, and then your application may need to adapt to the modified ABI.
History History