Boris Kolpackov wrote:
Hi Alexey,
To answer all your questions at once, what you are trying to do is
not possible. It might work for some versions but that is not
guaranteed by the Xerces-C++ project.
Xerces-C++ has the following release numbering policy:
1. Releases with different major versions (e.g., 2.8.0 and 3.0.0)
are interface (and thus binary) incompatible.
2. Releases with the same major versions but different minor
versions (e.g., 2.7.0 and 2.8.0) are interface-compatible
but binary-incompatible. This means that an application
should be able to migrate from one version to the other
without any source code changes but will require a
recompilation. Common changes that are interface-compatible
but binary-incompatible are adding and reordering virtual
functions, changing function signatures in a compatible
way, and changing sizes of objects (e.g., adding or removing
a private member variable).
3. Releases with the same major and minor versions but different
revisions (e.g., 2.8.0 and 2.8.1) are binary (and thus
interface) compatible.
Boris
Hello Boris,
Thank you for fast answer and for clarification. :)
