Boost C++ Libraries Home Libraries People FAQ More

PrevUpHomeNext

Overview

Boost.JSON is a portable C++ library which provides containers and algorithms that implement JavaScript Object Notation, or simply "JSON", a lightweight data-interchange format. This format is easy for humans to read and write, and easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language (Standard ECMA-262). JSON is a text format that is language-independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

This library focuses on a common and popular use-case: parsing and serializing to and from a container called value which holds JSON types. Any value which you build can be serialized and then deserialized, guaranteeing that the result will be equal to the original value. Whatever JSON output you produce with this library will be readable by most common JSON implementations in any language.

The value container is designed to be well suited as a vocabulary type appropriate for use in public interfaces and libraries, allowing them to be composed. The library restricts the representable data types to the ranges which are almost universally accepted by most JSON implementations, especially JavaScript. The parser and serializer are both highly performant, meeting or exceeding the benchmark performance of the best comparable libraries. Allocators are very well supported. Code which uses these types will be easy to understand, flexible, and performant.

Boost.JSON offers these features:

The library relies heavily on these well known C++ types in its interfaces (henceforth termed standard types):

The requirements for Boost.JSON depend on whether the library is used as part of Boost, or in the standalone flavor (without Boost):

Using Boost
  • Requires only C++11
  • The default configuration
  • Aliases for standard types use their Boost equivalents
  • Link to a built static or dynamic Boost library, or use header-only (see below)
  • Supports -fno-exceptions, detected automatically
Without Boost
  • Requires C++17
  • Aliases for standard types use their std equivalents
  • Obtained when defining the macro BOOST_JSON_STANDALONE
  • Link to a built static or dynamic standalone library, or use header-only (see below)
  • Supports -fno-exceptions: define BOOST_NO_EXCEPTIONS and boost::throw_exception manually

When using without Boost, support for <memory_resource> is required. In particular, if using libstdc++ then version 8.3 or later is needed.

Header-Only

To use as header-only; that is, to eliminate the requirement to link a program to a static or dynamic Boost.JSON library, simply place the following line in exactly one new or existing source file in your project.

#include <boost/json/src.hpp>
Embedded

Boost.JSON works great on embedded devices. The library uses local stack buffers to increase the performance of some operations. On Intel platforms these buffers are large (4KB), while on non-Intel platforms they are small (256 bytes). To adjust the size of the stack buffers for embedded applications define this macro when building the library or including the function definitions:

#define BOOST_JSON_STACK_BUFFER_SIZE 1024
#include <boost/json/src.hpp>
[Note] Note

This library uses separate inline namespacing for the standalone mode to allow libraries which use different modes to compose without causing link errors. Linking to both modes of Boost.JSON (Boost and standalone) is possible, but not recommended.

Boost.JSON has been tested with the following compilers:

  • clang-3.8
  • clang-4.0
  • clang-5.0
  • clang-6.0
  • clang-6
  • clang-7
  • clang-8
  • clang-9
  • gcc-4.8
  • gcc-4.9
  • gcc-5
  • gcc-6
  • gcc-7
  • gcc-8
  • gcc-9
  • msvc-14.1+

Quality Assurance

The development infrastructure for the library includes these per-commit analyses:

  • coverage reports
  • benchmark performance comparisons
  • compilation and tests on Travis, Azure Pipelines, Appveyor
  • fuzzing using clang-llvm and machine learning

Credits

This library wouldn't be where it is today without the help of Peter Dimov for design advice and optimization assistance.


PrevUpHomeNext