The lcl_fullversion constant contains all of the component version number values, formatted with 2 digits and concatenated (leading zeros are omitted).

For example, if the LCL version is 2.2.4.1, lcl_fullversion will be 2020401.

Given a complete version string like 2.2.4, the lcl_major constant contains the first number (2).

Given a version string like 2.2.4, the lcl_minor constant contains the second number (2).

Please note: Starting with LCL version 3.0, lcl_minor is incremented by 1 for each new release or fixes branch. For example: 3.0, 3.1, 3.2, etc. An even minor version number, like 3.0 or 3.2, represents a general availability release. An odd minor version number no longer indicates that it is a development (or trunk) version. Instead, an odd minor version number like 3.1 or 3.3 represents a fixes branch. For example: 3.1 would contain bug fixes for the 3.0 release and would be used as the basis for the 3.2 release. Development (or trunk) versions are always represented as minor version number 99; i.e. 3.99 is the development branch for the future 4.0 release. Also, selected commits from this branch are cherry picked to the 3.X family.

Given a version string like 2.2.4, the lcl_release constant contains the third number (4).

Please note: Starting with LCL 3.0, the release number is no longer maintained and will always contain 0 (zero). Releases are represented using the major and minor version numbers: 3.0, 3.1, 3.2, etc.

Given a complete version string like 2.2.4.1, the lcl_patch constant contains the last number (1). If there is no fourth number, for example when the version string is 2.2.4, then lcl_patch is 0.