summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2007-12-09 19:42:57 +0000
committerroot <root>2007-12-09 19:42:57 +0000
commit9df49634f11f561ad9b5669124a4f2bd7179a559 (patch)
treee9b29494d8bc1b1b82b86908a7e2e1b2dede78fd /ev.pod
parent5466167e0504f6fd929074dda89e770d4abfd3c3 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod7
1 files changed, 5 insertions, 2 deletions
diff --git a/ev.pod b/ev.pod
index 3ad52c0..0657b7f 100644
--- a/ev.pod
+++ b/ev.pod
@@ -119,14 +119,17 @@ you actually want to know.
=item int ev_version_minor ()
-You can find out the major and minor version numbers of the library
+You can find out the major and minor API/ABI version numbers of the library
you linked against by calling the functions C<ev_version_major> and
C<ev_version_minor>. If you want, you can compare against the global
symbols C<EV_VERSION_MAJOR> and C<EV_VERSION_MINOR>, which specify the
version of the library your program was compiled against.
+These version numbers refer to the API and ABI version of the library, not
+the release version.
+
Usually, it's a good idea to terminate if the major versions mismatch,
-as this indicates an incompatible change. Minor versions are usually
+as this indicates an incompatible change. Minor versions are usually
compatible to older versions, so a larger minor version alone is usually
not a problem.