2 title: JSON library for modern C++
7 There are myriads of [JSON](http://json.org) libraries out there, and each may even have its reason to exist. Our class had these design goals:
9 - **Intuitive syntax**. In languages such as Python, JSON feels like a first class data type. We used all the operator magic of modern C++ to achieve the same feeling in your code. Check out the [examples below](#examples) and you'll know what I mean.
11 - **Trivial integration**. Our whole code consists of a single header file [`json.hpp`](https://github.com/nlohmann/json/blob/develop/src/json.hpp). That's it. No library, no subproject, no dependencies, no complex build system. The class is written in vanilla C++11. All in all, everything should require no adjustment of your compiler flags or project settings.
13 - **Serious testing**. Our class is heavily [unit-tested](https://github.com/nlohmann/json/blob/master/test/src/unit.cpp) and covers [100%](https://coveralls.io/r/nlohmann/json) of the code, including all exceptional behavior. Furthermore, we checked with [Valgrind](http://valgrind.org) that there are no memory leaks. To maintain high quality, the project is following the [Core Infrastructure Initiative (CII) best practices](https://bestpractices.coreinfrastructure.org/projects/289).
15 Other aspects were not so important to us:
17 - **Memory efficiency**. Each JSON object has an overhead of one pointer (the maximal size of a union) and one enumeration element (1 byte). The default generalization uses the following C++ data types: `std::string` for strings, `int64_t`, `uint64_t` or `double` for numbers, `std::map` for objects, `std::vector` for arrays, and `bool` for Booleans. However, you can template the generalized class `basic_json` to your needs.
19 - **Speed**. There are certainly [faster JSON libraries](https://github.com/miloyip/nativejson-benchmark#parsing-time) out there. However, if your goal is to speed up your development by adding JSON support with a single header, then this library is the way to go. If you know how to use a `std::vector` or `std::map`, you are already set.
21 See the [contribution guidelines](https://github.com/nlohmann/json/blob/master/.github/CONTRIBUTING.md#please-dont) for more information.
25 The single required source, file `json.hpp` is in the `src` directory or [released here](https://github.com/nlohmann/json/releases). All you need to do is add
31 using json = nlohmann::json;
34 to the files you want to use JSON objects. That's it. Do not forget to set the necessary switches to enable C++11 (e.g., `-std=c++11` for GCC and Clang).
36 :beer: If you are using OS X and [Homebrew](http://brew.sh), just type `brew tap nlohmann/json` and `brew install nlohmann_json` and you're set. If you want the bleeding edge rather than the latest release, use `brew install nlohmann_json --HEAD`.
38 If you are using the [Meson Build System](http://mesonbuild.com), then you can wrap this repo as a subproject.
40 If you are using [Conan](https://www.conan.io/) to manage your dependencies, merely add `jsonformoderncpp/x.y.z@vthiery/stable` to your `conanfile.py`'s requires, where `x.y.z` is the release version you want to use. Please file issues [here](https://github.com/vthiery/conan-jsonformoderncpp/issues) if you experience problems with the packages.
42 If you are using [hunter](https://github.com/ruslo/hunter/) on your project for external dependencies, then you can use the [nlohman_json package](https://github.com/ruslo/hunter/wiki/pkg.nlohmann_json). Please see the hunter project for any issues regarding the packaging.
44 :warning: [Version 3.0.0](https://github.com/nlohmann/json/wiki/Road-toward-3.0.0) is currently under development. Branch `develop` is used for the ongoing work and is probably **unstable**. Please use the `master` branch for the last stable version 2.1.1.
48 Beside the examples below, you may want to check the [documentation](https://nlohmann.github.io/json/) where each function contains a separate code example (e.g., check out [`emplace()`](https://nlohmann.github.io/json/classnlohmann_1_1basic__json_a602f275f0359ab181221384989810604.html#a602f275f0359ab181221384989810604)). All [example files](https://github.com/nlohmann/json/tree/develop/doc/examples) can be compiled and executed on their own (e.g., file [emplace.cpp](https://github.com/nlohmann/json/blob/develop/doc/examples/emplace.cpp)).
50 ### JSON as first-class data type
52 Here are some examples to give you an idea how to use the class.
54 Assume you want to create the JSON object
73 With the JSON class, you could write:
76 // create an empty structure (null)
79 // add a number that is stored as double (note the implicit conversion of j to an object)
82 // add a Boolean that is stored as bool
85 // add a string that is stored as std::string
88 // add another null object by passing nullptr
89 j["nothing"] = nullptr;
91 // add an object inside the object
92 j["answer"]["everything"] = 42;
94 // add an array that is stored as std::vector (using an initializer list)
95 j["list"] = { 1, 0, 2 };
97 // add another object (using an initializer list of pairs)
98 j["object"] = { {"currency", "USD"}, {"value", 42.99} };
100 // instead, you could also write (which looks very similar to the JSON above)
105 {"nothing", nullptr},
117 Note that in all these cases, you never need to "tell" the compiler which JSON value you want to use. If you want to be explicit or express some edge cases, the functions `json::array` and `json::object` will help:
120 // a way to express the empty array []
121 json empty_array_explicit = json::array();
123 // ways to express the empty object {}
124 json empty_object_implicit = json({});
125 json empty_object_explicit = json::object();
127 // a way to express an _array_ of key/value pairs [["currency", "USD"], ["value", 42.99]]
128 json array_not_object = { json::array({"currency", "USD"}), json::array({"value", 42.99}) };
131 ### Serialization / Deserialization
135 You can create an object (deserialization) by appending `_json` to a string literal:
138 // create object from string literal
139 json j = "{ \"happy\": true, \"pi\": 3.141 }"_json;
141 // or even nicer with a raw string literal
150 Note that without appending the `_json` suffix, the passed string literal is not parsed, but just used as JSON string value. That is, `json j = "{ \"happy\": true, \"pi\": 3.141 }"` would just store the string `"{ "happy": true, "pi": 3.141 }"` rather than parsing the actual object.
152 The above example can also be expressed explicitly using `json::parse()`:
156 auto j3 = json::parse("{ \"happy\": true, \"pi\": 3.141 }");
159 You can also get a string representation (serialize):
162 // explicit conversion to string
163 std::string s = j.dump(); // {\"happy\":true,\"pi\":3.141}
165 // serialization with pretty printing
166 // pass in the amount of spaces to indent
167 std::cout << j.dump(4) << std::endl;
174 #### To/from streams (e.g. files, string streams)
176 You can also use streams to serialize and deserialize:
179 // deserialize from standard input
183 // serialize to standard output
186 // the setw manipulator was overloaded to set the indentation for pretty printing
187 std::cout << std::setw(4) << j << std::endl;
190 These operators work for any subclasses of `std::istream` or `std::ostream`. Here is the same example with files:
194 std::ifstream i("file.json");
198 // write prettified JSON to another file
199 std::ofstream o("pretty.json");
200 o << std::setw(4) << j << std::endl;
203 Please note that setting the exception bit for `failbit` is inappropriate for this use case. It will result in program termination due to the `noexcept` specifier in use.
205 #### Read from iterator range
207 You can also read JSON from an iterator range; that is, from any container accessible by iterators whose content is stored as contiguous byte sequence, for instance a `std::vector<std::uint8_t>`:
210 std::vector<std::uint8_t> v = {'t', 'r', 'u', 'e'};
211 json j = json::parse(v.begin(), v.end());
214 You may leave the iterators for the range [begin, end):
217 std::vector<std::uint8_t> v = {'t', 'r', 'u', 'e'};
218 json j = json::parse(v);
223 We designed the JSON class to behave just like an STL container. In fact, it satisfies the [**ReversibleContainer**](http://en.cppreference.com/w/cpp/concept/ReversibleContainer) requirement.
226 // create an array using push_back
232 // also use emplace_back
233 j.emplace_back(1.78);
236 for (json::iterator it = j.begin(); it != j.end(); ++it) {
237 std::cout << *it << '\n';
241 for (auto& element : j) {
242 std::cout << element << '\n';
246 const std::string tmp = j[0];
251 j == "[\"foo\", 1, true]"_json; // true
254 j.size(); // 3 entries
256 j.type(); // json::value_t::array
257 j.clear(); // the array is empty again
259 // convenience type checkers
274 o.emplace("weather", "sunny");
276 // special iterator member functions for objects
277 for (json::iterator it = o.begin(); it != o.end(); ++it) {
278 std::cout << it.key() << " : " << it.value() << "\n";
282 if (o.find("foo") != o.end()) {
283 // there is an entry with key "foo"
286 // or simpler using count()
287 int foo_present = o.count("foo"); // 1
288 int fob_present = o.count("fob"); // 0
294 ### Conversion from STL containers
296 Any sequence container (`std::array`, `std::vector`, `std::deque`, `std::forward_list`, `std::list`) whose values can be used to construct JSON types (e.g., integers, floating point numbers, Booleans, string types, or again STL containers described in this section) can be used to create a JSON array. The same holds for similar associative containers (`std::set`, `std::multiset`, `std::unordered_set`, `std::unordered_multiset`), but in these cases the order of the elements of the array depends how the elements are ordered in the respective STL container.
299 std::vector<int> c_vector {1, 2, 3, 4};
300 json j_vec(c_vector);
303 std::deque<double> c_deque {1.2, 2.3, 3.4, 5.6};
304 json j_deque(c_deque);
305 // [1.2, 2.3, 3.4, 5.6]
307 std::list<bool> c_list {true, true, false, true};
309 // [true, true, false, true]
311 std::forward_list<int64_t> c_flist {12345678909876, 23456789098765, 34567890987654, 45678909876543};
312 json j_flist(c_flist);
313 // [12345678909876, 23456789098765, 34567890987654, 45678909876543]
315 std::array<unsigned long, 4> c_array {{1, 2, 3, 4}};
316 json j_array(c_array);
319 std::set<std::string> c_set {"one", "two", "three", "four", "one"};
320 json j_set(c_set); // only one entry for "one" is used
321 // ["four", "one", "three", "two"]
323 std::unordered_set<std::string> c_uset {"one", "two", "three", "four", "one"};
324 json j_uset(c_uset); // only one entry for "one" is used
325 // maybe ["two", "three", "four", "one"]
327 std::multiset<std::string> c_mset {"one", "two", "one", "four"};
328 json j_mset(c_mset); // both entries for "one" are used
329 // maybe ["one", "two", "one", "four"]
331 std::unordered_multiset<std::string> c_umset {"one", "two", "one", "four"};
332 json j_umset(c_umset); // both entries for "one" are used
333 // maybe ["one", "two", "one", "four"]
336 Likewise, any associative key-value containers (`std::map`, `std::multimap`, `std::unordered_map`, `std::unordered_multimap`) whose keys can construct an `std::string` and whose values can be used to construct JSON types (see examples above) can be used to create a JSON object. Note that in case of multimaps only one key is used in the JSON object and the value depends on the internal order of the STL container.
339 std::map<std::string, int> c_map { {"one", 1}, {"two", 2}, {"three", 3} };
341 // {"one": 1, "three": 3, "two": 2 }
343 std::unordered_map<const char*, double> c_umap { {"one", 1.2}, {"two", 2.3}, {"three", 3.4} };
345 // {"one": 1.2, "two": 2.3, "three": 3.4}
347 std::multimap<std::string, bool> c_mmap { {"one", true}, {"two", true}, {"three", false}, {"three", true} };
348 json j_mmap(c_mmap); // only one entry for key "three" is used
349 // maybe {"one": true, "two": true, "three": true}
351 std::unordered_multimap<std::string, bool> c_ummap { {"one", true}, {"two", true}, {"three", false}, {"three", true} };
352 json j_ummap(c_ummap); // only one entry for key "three" is used
353 // maybe {"one": true, "two": true, "three": true}
356 ### JSON Pointer and JSON Patch
358 The library supports **JSON Pointer** ([RFC 6901](https://tools.ietf.org/html/rfc6901)) as alternative means to address structured values. On top of this, **JSON Patch** ([RFC 6902](https://tools.ietf.org/html/rfc6902)) allows to describe differences between two JSON values - effectively allowing patch and diff operations known from Unix.
362 json j_original = R"({
363 "baz": ["one", "two", "three"],
367 // access members with a JSON pointer (RFC 6901)
368 j_original["/baz/1"_json_pointer];
371 // a JSON patch (RFC 6902)
373 { "op": "replace", "path": "/baz", "value": "boo" },
374 { "op": "add", "path": "/hello", "value": ["world"] },
375 { "op": "remove", "path": "/foo"}
379 json j_result = j_original.patch(j_patch);
382 // "hello": ["world"]
385 // calculate a JSON patch from two JSON values
386 json::diff(j_result, j_original);
388 // { "op":" replace", "path": "/baz", "value": ["one", "two", "three"] },
389 // { "op": "remove","path": "/hello" },
390 // { "op": "add", "path": "/foo", "value": "bar" }
394 ### Implicit conversions
396 The type of the JSON object is determined automatically by the expression to store. Likewise, the stored value is implicitly converted.
400 std::string s1 = "Hello, world!";
417 You can also explicitly ask for the value:
420 std::string vs = js.get<std::string>();
421 bool vb = jb.get<bool>();
422 int vi = jn.get<int>();
427 ### Arbitrary types conversions
429 Every type can be serialized in JSON, not just STL-containers and scalar types. Usually, you would do something along those lines:
433 // a simple struct to model a person
441 ns::person p = {"Ned Flanders", "744 Evergreen Terrace", 60};
443 // convert to JSON: copy each value into the JSON object
446 j["address"] = p.address;
451 // convert from JSON: copy each value from the JSON object
453 j["name"].get<std::string>(),
454 j["address"].get<std::string>(),
459 It works, but that's quite a lot of boilerplate... Fortunately, there's a better way:
463 ns::person p {"Ned Flanders", "744 Evergreen Terrace", 60};
465 // conversion: person -> json
468 std::cout << j << std::endl;
469 // {"address":"744 Evergreen Terrace","age":60,"name":"Ned Flanders"}
471 // conversion: json -> person
480 To make this work with one of your types, you only need to provide two functions:
483 using nlohmann::json;
486 void to_json(json& j, const person& p) {
487 j = json{ {"name", p.name}, {"address", p.address}, {"age", p.age} };
490 void from_json(const json& j, person& p) {
491 p.name = j.at("name").get<std::string>();
492 p.address = j.at("address").get<std::string>();
493 p.age = j.at("age").get<int>();
498 That's all! When calling the `json` constructor with your type, your custom `to_json` method will be automatically called.
499 Likewise, when calling `get<your_type>()`, the `from_json` method will be called.
501 Some important things:
503 - Those methods **MUST** be in your type's namespace (which can be the global namespace), or the library will not be able to locate them (in this example, they are in namespace `ns`, where `person` is defined).
504 - When using `get<your_type>()`, `your_type` **MUST** be [DefaultConstructible](http://en.cppreference.com/w/cpp/concept/DefaultConstructible). (There is a way to bypass this requirement described later.)
505 - In function `from_json`, use function [`at()`](https://nlohmann.github.io/json/classnlohmann_1_1basic__json_a93403e803947b86f4da2d1fb3345cf2c.html#a93403e803947b86f4da2d1fb3345cf2c) to access the object values rather than `operator[]`. In case a key does not exists, `at` throws an exception that you can handle, whereas `operator[]` exhibits undefined behavior.
506 - In case your type contains several `operator=` definitions, code like `your_variable = your_json;` [may not compile](https://github.com/nlohmann/json/issues/667). You need to write `your_variable = your_json.get<decltype your_variable>();` instead.
507 - You do not need to add serializers or deserializers for STL types like `std::vector`: the library already implements these.
509 #### How do I convert third-party types?
511 This requires a bit more advanced technique. But first, let's see how this conversion mechanism works:
513 The library uses **JSON Serializers** to convert types to json.
514 The default serializer for `nlohmann::json` is `nlohmann::adl_serializer` (ADL means [Argument-Dependent Lookup](http://en.cppreference.com/w/cpp/language/adl)).
516 It is implemented like this (simplified):
519 template <typename T>
520 struct adl_serializer {
521 static void to_json(json& j, const T& value) {
522 // calls the "to_json" method in T's namespace
525 static void from_json(const json& j, T& value) {
526 // same thing, but with the "from_json" method
531 This serializer works fine when you have control over the type's namespace. However, what about `boost::optional`, or `std::filesystem::path` (C++17)? Hijacking the `boost` namespace is pretty bad, and it's illegal to add something other than template specializations to `std`...
533 To solve this, you need to add a specialization of `adl_serializer` to the `nlohmann` namespace, here's an example:
536 // partial specialization (full specialization works too)
538 template <typename T>
539 struct adl_serializer<boost::optional<T>> {
540 static void to_json(json& j, const boost::optional<T>& opt) {
541 if (opt == boost::none) {
544 j = *opt; // this will call adl_serializer<T>::to_json which will
545 // find the free function to_json in T's namespace!
549 static void from_json(const json& j, boost::optional<T>& opt) {
553 opt = j.get<T>(); // same as above, but with
554 // adl_serializer<T>::from_json
561 #### How can I use `get()` for non-default constructible/non-copyable types?
563 There is a way, if your type is [MoveConstructible](http://en.cppreference.com/w/cpp/concept/MoveConstructible). You will need to specialize the `adl_serializer` as well, but with a special `from_json` overload:
566 struct move_only_type {
567 move_only_type() = delete;
568 move_only_type(int ii): i(ii) {}
569 move_only_type(const move_only_type&) = delete;
570 move_only_type(move_only_type&&) = default;
577 struct adl_serializer<move_only_type> {
578 // note: the return type is no longer 'void', and the method only takes
580 static move_only_type from_json(const json& j) {
581 return {j.get<int>()};
584 // Here's the catch! You must provide a to_json method! Otherwise you
585 // will not be able to convert move_only_type to json, since you fully
586 // specialized adl_serializer on that type
587 static void to_json(json& j, move_only_type t) {
594 #### Can I write my own serializer? (Advanced use)
596 Yes. You might want to take a look at [`unit-udt.cpp`](https://github.com/nlohmann/json/blob/develop/test/src/unit-udt.cpp) in the test suite, to see a few examples.
598 If you write your own serializer, you'll need to do a few things:
600 - use a different `basic_json` alias than `nlohmann::json` (the last template parameter of `basic_json` is the `JSONSerializer`)
601 - use your `basic_json` alias (or a template parameter) in all your `to_json`/`from_json` methods
602 - use `nlohmann::to_json` and `nlohmann::from_json` when you need ADL
604 Here is an example, without simplifications, that only accepts types with a size <= 32, and uses ADL.
607 // You should use void as a second template argument
608 // if you don't need compile-time checks on T
609 template<typename T, typename SFINAE = typename std::enable_if<sizeof(T) <= 32>::type>
610 struct less_than_32_serializer {
611 template <typename BasicJsonType>
612 static void to_json(BasicJsonType& j, T value) {
613 // we want to use ADL, and call the correct to_json overload
614 using nlohmann::to_json; // this method is called by adl_serializer,
615 // this is where the magic happens
619 template <typename BasicJsonType>
620 static void from_json(const BasicJsonType& j, T& value) {
622 using nlohmann::from_json;
628 Be **very** careful when reimplementing your serializer, you can stack overflow if you don't pay attention:
631 template <typename T, void>
632 struct bad_serializer
634 template <typename BasicJsonType>
635 static void to_json(BasicJsonType& j, const T& value) {
636 // this calls BasicJsonType::json_serializer<T>::to_json(j, value);
637 // if BasicJsonType::json_serializer == bad_serializer ... oops!
641 template <typename BasicJsonType>
642 static void to_json(const BasicJsonType& j, T& value) {
643 // this calls BasicJsonType::json_serializer<T>::from_json(j, value);
644 // if BasicJsonType::json_serializer == bad_serializer ... oops!
645 value = j.template get<T>(); // oops!
650 ### Binary formats (CBOR and MessagePack)
652 Though JSON is a ubiquitous data format, it is not a very compact format suitable for data exchange, for instance over a network. Hence, the library supports [CBOR](http://cbor.io) (Concise Binary Object Representation) and [MessagePack](http://msgpack.org) to efficiently encode JSON values to byte vectors and to decode such vectors.
655 // create a JSON value
656 json j = R"({"compact": true, "schema": 0})"_json;
659 std::vector<std::uint8_t> v_cbor = json::to_cbor(j);
661 // 0xa2, 0x67, 0x63, 0x6f, 0x6d, 0x70, 0x61, 0x63, 0x74, 0xf5, 0x66, 0x73, 0x63, 0x68, 0x65, 0x6d, 0x61, 0x00
664 json j_from_cbor = json::from_cbor(v_cbor);
666 // serialize to MessagePack
667 std::vector<std::uint8_t> v_msgpack = json::to_msgpack(j);
669 // 0x82, 0xa7, 0x63, 0x6f, 0x6d, 0x70, 0x61, 0x63, 0x74, 0xc3, 0xa6, 0x73, 0x63, 0x68, 0x65, 0x6d, 0x61, 0x00
672 json j_from_msgpack = json::from_msgpack(v_msgpack);
675 ## Supported compilers
677 Though it's 2016 already, the support for C++11 is still a bit sparse. Currently, the following compilers are known to work:
679 - GCC 4.9 - 7.1 (and possibly later)
680 - Clang 3.4 - 5.0 (and possibly later)
681 - Microsoft Visual C++ 2015 / Build Tools 14.0.25123.0 (and possibly later)
682 - Microsoft Visual C++ 2017 / Build Tools 15.1.548.43366 (and possibly later)
684 I would be happy to learn about other compilers/versions.
688 - GCC 4.8 does not work because of two bugs ([55817](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55817) and [57824](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57824)) in the C++11 support. Note there is a [pull request](https://github.com/nlohmann/json/pull/212) to fix some of the issues.
689 - Android defaults to using very old compilers and C++ libraries. To fix this, add the following to your `Application.mk`. This will switch to the LLVM C++ library, the Clang compiler, and enable C++11 and other features disabled by default.
692 APP_STL := c++_shared
693 NDK_TOOLCHAIN_VERSION := clang3.6
694 APP_CPPFLAGS += -frtti -fexceptions
697 The code compiles successfully with [Android NDK](https://developer.android.com/ndk/index.html?hl=ml), Revision 9 - 11 (and possibly later) and [CrystaX's Android NDK](https://www.crystax.net/en/android/ndk) version 10.
699 - For GCC running on MinGW or Android SDK, the error `'to_string' is not a member of 'std'` (or similarly, for `strtod`) may occur. Note this is not an issue with the code, but rather with the compiler itself. On Android, see above to build with a newer environment. For MinGW, please refer to [this site](http://tehsausage.com/mingw-to-string) and [this discussion](https://github.com/nlohmann/json/issues/136) for information on how to fix this bug. For Android NDK using `APP_STL := gnustl_static`, please refer to [this discussion](https://github.com/nlohmann/json/issues/219).
701 The following compilers are currently used in continuous integration at [Travis](https://travis-ci.org/nlohmann/json) and [AppVeyor](https://ci.appveyor.com/project/nlohmann/json):
703 | Compiler | Operating System | Version String |
704 |-----------------|------------------------------|----------------|
705 | GCC 4.9.4 | Ubuntu 14.04.5 LTS | g++-4.9 (Ubuntu 4.9.4-2ubuntu1~14.04.1) 4.9.4 |
706 | GCC 5.4.1 | Ubuntu 14.04.5 LTS | g++-5 (Ubuntu 5.4.1-2ubuntu1~14.04) 5.4.1 20160904 |
707 | GCC 6.3.0 | Ubuntu 14.04.5 LTS | g++-6 (Ubuntu/Linaro 6.3.0-18ubuntu2~14.04) 6.3.0 20170519 |
708 | GCC 7.1.0 | Ubuntu 14.04.5 LTS | g++-7 (Ubuntu 7.1.0-5ubuntu2~14.04) 7.1.0
709 | Clang 3.5.0 | Ubuntu 14.04.5 LTS | clang version 3.5.0-4ubuntu2~trusty2 (tags/RELEASE_350/final) |
710 | Clang 3.6.2 | Ubuntu 14.04.5 LTS | clang version 3.6.2-svn240577-1~exp1 (branches/release_36) |
711 | Clang 3.7.1 | Ubuntu 14.04.5 LTS | clang version 3.7.1-svn253571-1~exp1 (branches/release_37) |
712 | Clang 3.8.0 | Ubuntu 14.04.5 LTS | clang version 3.8.0-2ubuntu3~trusty5 (tags/RELEASE_380/final) |
713 | Clang 3.9.1 | Ubuntu 14.04.5 LTS | clang version 3.9.1-4ubuntu3~14.04.2 (tags/RELEASE_391/rc2) |
714 | Clang 4.0.1 | Ubuntu 14.04.5 LTS | clang version 4.0.1-svn305264-1~exp1 (branches/release_40) |
715 | Clang 5.0.0 | Ubuntu 14.04.5 LTS | clang version 5.0.0-svn310902-1~exp1 (branches/release_50) |
716 | Clang Xcode 6.4 | Darwin Kernel Version 14.3.0 (OSX 10.10.3) | Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) |
717 | Clang Xcode 7.3 | Darwin Kernel Version 15.0.0 (OSX 10.10.5) | Apple LLVM version 7.3.0 (clang-703.0.29) |
718 | Clang Xcode 8.0 | Darwin Kernel Version 15.6.0 | Apple LLVM version 8.0.0 (clang-800.0.38) |
719 | Clang Xcode 8.1 | Darwin Kernel Version 16.1.0 (macOS 10.12.1) | Apple LLVM version 8.0.0 (clang-800.0.42.1) |
720 | Clang Xcode 8.2 | Darwin Kernel Version 16.1.0 (macOS 10.12.1) | Apple LLVM version 8.0.0 (clang-800.0.42.1) |
721 | Clang Xcode 8.3 | Darwin Kernel Version 16.5.0 (macOS 10.12.4) | Apple LLVM version 8.1.0 (clang-802.0.38) |
722 | Clang Xcode 9 beta | Darwin Kernel Version 16.6.0 (macOS 10.12.5) | Apple LLVM version 9.0.0 (clang-900.0.26) |
723 | Visual Studio 14 2015 | Windows Server 2012 R2 (x64) | Microsoft (R) Build Engine version 14.0.25420.1 |
724 | Visual Studio 2017 | Windows Server 2016 | Microsoft (R) Build Engine version 15.1.1012.6693 |
728 The class is licensed under the [MIT License](http://opensource.org/licenses/MIT):
730 Copyright © 2013-2017 [Niels Lohmann](http://nlohmann.me)
732 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
734 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
736 THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
740 I deeply appreciate the help of the following people.
742 - [Teemperor](https://github.com/Teemperor) implemented CMake support and lcov integration, realized escape and Unicode handling in the string parser, and fixed the JSON serialization.
743 - [elliotgoodrich](https://github.com/elliotgoodrich) fixed an issue with double deletion in the iterator classes.
744 - [kirkshoop](https://github.com/kirkshoop) made the iterators of the class composable to other libraries.
745 - [wancw](https://github.com/wanwc) fixed a bug that hindered the class to compile with Clang.
746 - Tomas Åblad found a bug in the iterator implementation.
747 - [Joshua C. Randall](https://github.com/jrandall) fixed a bug in the floating-point serialization.
748 - [Aaron Burghardt](https://github.com/aburgh) implemented code to parse streams incrementally. Furthermore, he greatly improved the parser class by allowing the definition of a filter function to discard undesired elements while parsing.
749 - [Daniel Kopeček](https://github.com/dkopecek) fixed a bug in the compilation with GCC 5.0.
750 - [Florian Weber](https://github.com/Florianjw) fixed a bug in and improved the performance of the comparison operators.
751 - [Eric Cornelius](https://github.com/EricMCornelius) pointed out a bug in the handling with NaN and infinity values. He also improved the performance of the string escaping.
752 - [易思龙](https://github.com/likebeta) implemented a conversion from anonymous enums.
753 - [kepkin](https://github.com/kepkin) patiently pushed forward the support for Microsoft Visual studio.
754 - [gregmarr](https://github.com/gregmarr) simplified the implementation of reverse iterators and helped with numerous hints and improvements. In particular, he pushed forward the implementation of user-defined types.
755 - [Caio Luppi](https://github.com/caiovlp) fixed a bug in the Unicode handling.
756 - [dariomt](https://github.com/dariomt) fixed some typos in the examples.
757 - [Daniel Frey](https://github.com/d-frey) cleaned up some pointers and implemented exception-safe memory allocation.
758 - [Colin Hirsch](https://github.com/ColinH) took care of a small namespace issue.
759 - [Huu Nguyen](https://github.com/whoshuu) correct a variable name in the documentation.
760 - [Silverweed](https://github.com/silverweed) overloaded `parse()` to accept an rvalue reference.
761 - [dariomt](https://github.com/dariomt) fixed a subtlety in MSVC type support and implemented the `get_ref()` function to get a reference to stored values.
762 - [ZahlGraf](https://github.com/ZahlGraf) added a workaround that allows compilation using Android NDK.
763 - [whackashoe](https://github.com/whackashoe) replaced a function that was marked as unsafe by Visual Studio.
764 - [406345](https://github.com/406345) fixed two small warnings.
765 - [Glen Fernandes](https://github.com/glenfe) noted a potential portability problem in the `has_mapped_type` function.
766 - [Corbin Hughes](https://github.com/nibroc) fixed some typos in the contribution guidelines.
767 - [twelsby](https://github.com/twelsby) fixed the array subscript operator, an issue that failed the MSVC build, and floating-point parsing/dumping. He further added support for unsigned integer numbers and implemented better roundtrip support for parsed numbers.
768 - [Volker Diels-Grabsch](https://github.com/vog) fixed a link in the README file.
769 - [msm-](https://github.com/msm-) added support for american fuzzy lop.
770 - [Annihil](https://github.com/Annihil) fixed an example in the README file.
771 - [Themercee](https://github.com/Themercee) noted a wrong URL in the README file.
772 - [Lv Zheng](https://github.com/lv-zheng) fixed a namespace issue with `int64_t` and `uint64_t`.
773 - [abc100m](https://github.com/abc100m) analyzed the issues with GCC 4.8 and proposed a [partial solution](https://github.com/nlohmann/json/pull/212).
774 - [zewt](https://github.com/zewt) added useful notes to the README file about Android.
775 - [Róbert Márki](https://github.com/robertmrk) added a fix to use move iterators and improved the integration via CMake.
776 - [Chris Kitching](https://github.com/ChrisKitching) cleaned up the CMake files.
777 - [Tom Needham](https://github.com/06needhamt) fixed a subtle bug with MSVC 2015 which was also proposed by [Michael K.](https://github.com/Epidal).
778 - [Mário Feroldi](https://github.com/thelostt) fixed a small typo.
779 - [duncanwerner](https://github.com/duncanwerner) found a really embarrassing performance regression in the 2.0.0 release.
780 - [Damien](https://github.com/dtoma) fixed one of the last conversion warnings.
781 - [Thomas Braun](https://github.com/t-b) fixed a warning in a test case.
782 - [Théo DELRIEU](https://github.com/theodelrieu) patiently and constructively oversaw the long way toward [iterator-range parsing](https://github.com/nlohmann/json/issues/290). He also implemented the magic behind the serialization/deserialization of user-defined types.
783 - [Stefan](https://github.com/5tefan) fixed a minor issue in the documentation.
784 - [Vasil Dimov](https://github.com/vasild) fixed the documentation regarding conversions from `std::multiset`.
785 - [ChristophJud](https://github.com/ChristophJud) overworked the CMake files to ease project inclusion.
786 - [Vladimir Petrigo](https://github.com/vpetrigo) made a SFINAE hack more readable and added Visual Studio 17 to the build matrix.
787 - [Denis Andrejew](https://github.com/seeekr) fixed a grammar issue in the README file.
788 - [Pierre-Antoine Lacaze](https://github.com/palacaze) found a subtle bug in the `dump()` function.
789 - [TurpentineDistillery](https://github.com/TurpentineDistillery) pointed to [`std::locale::classic()`](http://en.cppreference.com/w/cpp/locale/locale/classic) to avoid too much locale joggling, found some nice performance improvements in the parser, improved the benchmarking code, and realized locale-independent number parsing and printing.
790 - [cgzones](https://github.com/cgzones) had an idea how to fix the Coverity scan.
791 - [Jared Grubb](https://github.com/jaredgrubb) silenced a nasty documentation warning.
792 - [Yixin Zhang](https://github.com/qwename) fixed an integer overflow check.
793 - [Bosswestfalen](https://github.com/Bosswestfalen) merged two iterator classes into a smaller one.
794 - [Daniel599](https://github.com/Daniel599) helped to get Travis execute the tests with Clang's sanitizers.
795 - [Jonathan Lee](https://github.com/vjon) fixed an example in the README file.
796 - [gnzlbg](https://github.com/gnzlbg) supported the implementation of user-defined types.
797 - [Alexej Harm](https://github.com/qis) helped to get the user-defined types working with Visual Studio.
798 - [Jared Grubb](https://github.com/jaredgrubb) supported the implementation of user-defined types.
799 - [EnricoBilla](https://github.com/EnricoBilla) noted a typo in an example.
800 - [Martin Hořeňovský](https://github.com/horenmar) found a way for a 2x speedup for the compilation time of the test suite.
801 - [ukhegg](https://github.com/ukhegg) found proposed an improvement for the examples section.
802 - [rswanson-ihi](https://github.com/rswanson-ihi) noted a typo in the README.
803 - [Mihai Stan](https://github.com/stanmihai4) fixed a bug in the comparison with `nullptr`s.
804 - [Tushar Maheshwari](https://github.com/tusharpm) added [cotire](https://github.com/sakra/cotire) support to speed up the compilation.
805 - [TedLyngmo](https://github.com/TedLyngmo) noted a typo in the README, removed unnecessary bit arithmetic, and fixed some `-Weffc++` warnings.
806 - [Krzysztof Woś](https://github.com/krzysztofwos) made exceptions more visible.
807 - [ftillier](https://github.com/ftillier) fixed a compiler warning.
808 - [tinloaf](https://github.com/tinloaf) made sure all pushed warnings are properly popped.
809 - [Fytch](https://github.com/Fytch) found a bug in the documentation.
810 - [Jay Sistar](https://github.com/Type1J) implemented a Meson build description.
811 - [Henry Lee](https://github.com/HenryRLee) fixed a warning in ICC and improved the iterator implementation.
812 - [Vincent Thiery](https://github.com/vthiery) maintains a package for the Conan package manager.
813 - [Steffen](https://github.com/koemeet) fixed a potential issue with MSVC and `std::min`.
814 - [Mike Tzou](https://github.com/Chocobo1) fixed some typos.
815 - [amrcode](https://github.com/amrcode) noted a missleading documentation about comparison of floats.
816 - [Oleg Endo](https://github.com/olegendo) reduced the memory consumption by replacing `<iostream>` with `<iosfwd>`.
817 - [dan-42](https://github.com/dan-42) cleaned up the CMake files to simplify including/reusing of the library.
818 - [Nikita Ofitserov](https://github.com/himikof) allowed for moving values from initializer lists.
819 - [Greg Hurrell](https://github.com/wincent) fixed a typo.
820 - [Dmitry Kukovinets](https://github.com/DmitryKuk) fixed a typo.
821 - [kbthomp1](https://github.com/kbthomp1) fixed an issue related to the Intel OSX compiler.
822 - [Markus Werle](https://github.com/daixtrose) fixed a typo.
823 - [WebProdPP](https://github.com/WebProdPP) fixed a subtle error in a precondition check.
825 Thanks a lot for helping out! Please [let me know](mailto:mail@nlohmann.me) if I forgot someone.
827 ## Used third-party tools
829 The library itself contains of a single header file licensed under the MIT license. However, it is built, tested, documented, and whatnot using a lot of third-party tools and services. Thanks a lot!
831 - [**American fuzzy lop**](http://lcamtuf.coredump.cx/afl/) for fuzz testing
832 - [**AppVeyor**](https://www.appveyor.com) for [continuous integration](https://ci.appveyor.com/project/nlohmann/json) on Windows
833 - [**Artistic Style**](http://astyle.sourceforge.net) for automatic source code identation
834 - [**benchpress**](https://github.com/sbs-ableton/benchpress) to benchmark the code
835 - [**Catch**](https://github.com/philsquared/Catch) for the unit tests
836 - [**Clang**](http://clang.llvm.org) for compilation with code sanitizers
837 - [**Cmake**](https://cmake.org) for build automation
838 - [**Codacity**](https://www.codacy.com) for further [code analysis](https://www.codacy.com/app/nlohmann/json)
839 - [**cotire**](https://github.com/sakra/cotire) to speed of compilation
840 - [**Coveralls**](https://coveralls.io) to measure [code coverage](https://coveralls.io/github/nlohmann/json)
841 - [**Coverity Scan**](https://scan.coverity.com) for [static analysis](https://scan.coverity.com/projects/nlohmann-json)
842 - [**cppcheck**](http://cppcheck.sourceforge.net) for static analysis
843 - [**cxxopts**](https://github.com/jarro2783/cxxopts) to let benchpress parse command-line parameters
844 - [**Doxygen**](http://www.stack.nl/~dimitri/doxygen/) to generate [documentation](https://nlohmann.github.io/json/)
845 - [**git-update-ghpages**](https://github.com/rstacruz/git-update-ghpages) to upload the documentation to gh-pages
846 - [**Github Changelog Generator**](https://github.com/skywinder/github-changelog-generator) to generate the [ChangeLog](https://github.com/nlohmann/json/blob/develop/ChangeLog.md)
847 - [**libFuzzer**](http://llvm.org/docs/LibFuzzer.html) to implement fuzz testing for OSS-Fuzz
848 - [**OSS-Fuzz**](https://github.com/google/oss-fuzz) for continuous fuzz testing of the library
849 - [**send_to_wandbox**](https://github.com/nlohmann/json/blob/develop/doc/scripts/send_to_wandbox.py) to send code examples to [Wandbox](http://melpon.org/wandbox)
850 - [**Travis**](https://travis-ci.org) for [continuous integration](https://travis-ci.org/nlohmann/json) on Linux and macOS
851 - [**Valgrind**](http://valgrind.org) to check for correct memory management
852 - [**Wandbox**](http://melpon.org/wandbox) for [online examples](http://melpon.org/wandbox/permlink/4NEU6ZZMoM9lpIex)
854 ## Projects using JSON for Modern C++
856 The library is currently used in Apple macOS Sierra and iOS 10. I am not sure what they are using the library for, but I am happy that it runs on so many devices.
860 - The code contains numerous debug **assertions** which can be switched off by defining the preprocessor macro `NDEBUG`, see the [documentation of `assert`](http://en.cppreference.com/w/cpp/error/assert). In particular, note [`operator[]`](https://nlohmann.github.io/json/classnlohmann_1_1basic__json_a2e26bd0b0168abb61f67ad5bcd5b9fa1.html#a2e26bd0b0168abb61f67ad5bcd5b9fa1) implements **unchecked access** for const objects: If the given key is not present, the behavior is undefined (think of a dereferenced null pointer) and yields an [assertion failure](https://github.com/nlohmann/json/issues/289) if assertions are switched on. If you are not sure whether an element in an object exists, use checked access with the [`at()` function](https://nlohmann.github.io/json/classnlohmann_1_1basic__json_a674de1ee73e6bf4843fc5dc1351fb726.html#a674de1ee73e6bf4843fc5dc1351fb726).
861 - As the exact type of a number is not defined in the [JSON specification](http://rfc7159.net/rfc7159), this library tries to choose the best fitting C++ number type automatically. As a result, the type `double` may be used to store numbers which may yield [**floating-point exceptions**](https://github.com/nlohmann/json/issues/181) in certain rare situations if floating-point exceptions have been unmasked in the calling code. These exceptions are not caused by the library and need to be fixed in the calling code, such as by re-masking the exceptions prior to calling library functions.
862 - The library supports **Unicode input** as follows:
863 - Only **UTF-8** encoded input is supported which is the default encoding for JSON according to [RFC 7159](http://rfc7159.net/rfc7159#rfc.section.8.1).
864 - Other encodings such as Latin-1, UTF-16, or UTF-32 are not supported and will yield parse errors.
865 - [Unicode noncharacters](http://www.unicode.org/faq/private_use.html#nonchar1) will not be replaced by the library.
866 - Invalid surrogates (e.g., incomplete pairs such as `\uDEAD`) will yield parse errors.
867 - The strings stored in the library are UTF-8 encoded. When using the default string type (`std::string`), note that its length/size functions return the number of stored bytes rather than the number of characters or glyphs.
868 - The code can be compiled without C++ **runtime type identification** features; that is, you can use the `-fno-rtti` compiler flag.
869 - **Exceptions** are used widely within the library. They can, however, be switched off with either using the compiler flag `-fno-exceptions` or by defining the symbol `JSON_NOEXCEPTION`. In this case, exceptions are replaced by an `abort()` call.
870 - By default, the library does not preserve the **insertion order of object elements**. This is standards-compliant, as the [JSON standard](https://tools.ietf.org/html/rfc7159.html) defines objects as "an unordered collection of zero or more name/value pairs". If you do want to preserve the insertion order, you can specialize the object type with containers like [`tsl::ordered_map`](https://github.com/Tessil/ordered-map) or [`nlohmann::fifo_map`](https://github.com/nlohmann/fifo_map).
872 ## Execute unit tests
874 To compile and run the tests, you need to execute
877 $ make json_unit -Ctest
878 $ ./test/json_unit "*"
880 ===============================================================================
881 All tests passed (14504461 assertions in 48 test cases)
884 Alternatively, you can use [CMake](https://cmake.org) and run
894 For more information, have a look at the file [.travis.yml](https://github.com/nlohmann/json/blob/master/.travis.yml).