Home

The "stable" branch can be a bit outdated, but is only pushed to after performing extensive testing on different hardware and operating systems. Breaking changes in History.txt are documented from one stable release to another, because sometimes the master branch can undo breaking backward compatibility before another stable release. Use the stable branch if you rarely upgrade the library and just want something well tested with a number for the version.

The "master" branch is the main target for pull requests during active development, so it needs to release bug fixes quickly without breaking too much in the process. Pulling into master is done after manual testing on one operating system, and running automatic tests on Linux, Windows and MacOS servers with Intel and ARM instruction sets. Use master if you want to continuously adapt to changes as they come with the latest bugfixes.

Do not use the "experimental" branch, because it may have untested code pushed from an Android tablet during code inspection, and is often force pushed to erase failed prototypes. Only used to synchronize code between test computers and have a cloud backup.

See the "DFPSR/Doc" documentation folder in the repository for information about using the library.