# Frequently-Asked Questions About MySQL++

## What version of MySQL++ should I use?

If you’re writing new code, you should use the [latest stable version](/#stable).

If you have existing code currently using an older version of MySQL++, you may not want to upgrade all the way to the current version in a single step. You might upgrade to an [intermediate version](/#oldver) first to get bug fixes and maybe some minor features, then once that step is working and tested, you can think about jumping to the latest stable version.

MySQL++ uses the [standard](https://semver.org/) major.minor.bug-fix version number scheme. A change in the library’s major version number denotes changes that will almost certainly require source code changes in your program. See the “[Incompatible Library Changes](doc/html/userman/breakages.html)” chapter of the user manual for details. A change in the minor version number indicates added features that don’t change existing library interfaces. If you don’t want to use those features, you should be able to install the new library without rebuilding your program. A change in the bug-fix number indicates internal bug fixes, which don’t affect the library interface at all, so such versions are always safe to install.
MySQL++ uses the [standard](https://semver.org/) major.minor.bug-fix version number scheme. A change in the library’s major version number denotes changes that will almost certainly require source code changes in your program. A change in the minor version number indicates added features that don’t change existing library interfaces. If you don’t want to use those features, you should be able to install the new library without rebuilding your program. A change in the bug-fix number indicates internal bug fixes, which don’t affect the library interface at all, so such versions are always safe to install.

We haven’t followed this discipline perfectly, but we do [document](doc/html/userman/breakages.html) the cases where it occurs.
We haven’t followed this discipline perfectly, but we do document the cases where it occurs in the “[Incompatible Library Changes](/doc/html/userman/breakages.html)” chapter of the user manual.


## What platforms does it work on?

MySQL++ should work on any platform that has a C++98 or newer compiler and the MySQL C API development files. MySQL++ does optionally use some C++11 and C++14 features, but their presence is either autodetected at build time, or you have to go out of your way to enable them.

In practice, MySQL++ works best on the platforms that get the most attention. This means mass-market operating systems on common hardware, and the default tool chain for the platform.