Starting with version 1.0.0 libuv follows the semantic versioning scheme. This means that new APIs can be introduced throughout the lifetime of a major release. In this section you’ll find all macros and functions that will allow you to write or compile code conditionally, in order to work with multiple libuv versions.

Version-checking macros and functions <libuv 1.10.3-dev API documentation>

Vars

VERSION_MAJOR: cuint: libuv version’s major number. Source Edit
VERSION_MINOR: cuint: libuv version’s minor number. Source Edit
VERSION_PATCH: cuint: libuv version’s patch number. Source Edit
VERSION_IS_RELEASE: cint: Set to 1 to indicate a release version of libuv, 0 for a development snapshot. Source Edit
VERSION_SUFFIX: cstring: libuv version suffix. Certain development releases such as Release Candidates might have a suffix such as “rc”. Source Edit
VERSION_HEX: cuint: Returns the libuv version packed into a single integer. 8 bits are used for each component, with the patch number stored in the 8 least significant bits. E.g. for libuv 1.2.3 this would be 0x010203. Source Edit

Procs

proc version(): cuint {. importc: "uv_version", header: "uv.h" .}: Returns VERSION_HEX. Source Edit
proc versionString(): cstring {. importc: "uv_version_string", header: "uv.h" .}: Returns the libuv version number as a string. For non-release versions the version suffix is included. Source Edit

Module uv_version

Vars

Procs