- 29 Nov, 2019 1 commit
-
-
Carlos Gomes Martinho authored
Change the namespace from yaml::yaml to yaml-cpp::yaml-cpp.
-
- 23 Nov, 2019 1 commit
-
-
Igor [hyperxor] authored
Also add a test for a parser with no data
-
- 04 Nov, 2019 1 commit
-
-
Igor [hyperxor] authored
-
- 31 Oct, 2019 1 commit
-
-
Mike Egger authored
-
- 23 Oct, 2019 1 commit
-
-
Romain Geissler @ Amadeus authored
This happens whenever in a macro you use some "if" block, and don't use curly braces {}, as the macro is expanded on a single line, not on several lines. So just add the missing curly braces to please gcc. In file included from /remote/users/mlamesch/CloneFromPlatinum/yamlcpp/osp/Yamlcpp/18-0-0-5/include/yaml-cpp/yaml.h:18, from src/TestYaml.cpp:2: /remote/users/mlamesch/CloneFromPlatinum/yamlcpp/osp/Yamlcpp/18-0-0-5/include/yaml-cpp/node/convert.h: In static member function static bool YAML::convert<int>::decode(const YAML::Node&, int&): /remote/users/mlamesch/CloneFromPlatinum/yamlcpp/osp/Yamlcpp/18-0-0-5/include/yaml-cpp/node/convert.h:139:1: error: this if clause does not guard... [-Werror=misleading-indentation] YAML_DEFINE_CONVERT_STREAMABLE_SIGNED(int); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
- 16 Oct, 2019 1 commit
-
-
carmeli-tamir authored
* Showing test output only on failure * Test commit to see the failed test * Now making sure that the tests pass with no output
-
- 13 Oct, 2019 1 commit
-
-
Isabella Muerte authored
🐛 Fixes #748 (#770)
-
- 11 Oct, 2019 1 commit
-
-
Rasmus authored
-
- 05 Oct, 2019 1 commit
-
-
Andy Maloney authored
Also run clang-format on these files as requested
-
- 04 Oct, 2019 1 commit
-
-
Fatih YAZICI authored
Add empty list of sources to add_library and add_executable.
-
- 02 Oct, 2019 6 commits
-
-
Andy Maloney authored
-
Andy Maloney authored
-
Andy Maloney authored
-
Andy Maloney authored
-
Andy Maloney authored
-
Andy Maloney authored
-
- 27 Sep, 2019 4 commits
-
-
Andy Maloney authored
-
Isabella Muerte authored
The generator expressions here are actually unnecessary, now that I think about it. This should fix #745
-
Ezekiel Warren authored
Example of how someone might consume yaml-cpp with bazel: cc_binary( name = "example", srcs = ["example.cc"], deps = ["@com_github_jbeder_yaml_cpp//:yaml-cpp"], ) -
Isabella Muerte authored
Remove 2.6-isms Remove 2.8-isms Bump CMake minimum version to 3.4 Disable some options when used as a subdirectory Use `CONFIGURE_DEPENDS` with `file(GLOB)` when possible Backport CMake 3.15's MSVC_RUNTIME_LIBRARY setting. Set all compile options as generator expressions. Set all find-package files to be installed to the correct file. Remove `export(PACKAGE)`, as this has been deprecated. Remove fat binary support Remove manual setting of iPhone settings. These should be set by parent projects. Remove use of ExternalProject for a local use Conditionally remove format target unless clang-format is found
-
- 25 Sep, 2019 1 commit
-
-
Jesse Beder authored
-
- 15 Sep, 2019 3 commits
-
-
Andy Maloney authored
-
Andy Maloney authored
-
Andy Maloney authored
-
- 10 Sep, 2019 3 commits
-
-
Andy Maloney authored
* CMake: Prefix options with "YAML" and hide platform-specific options When including yaml-cpp as a subproject, some option names can conflict with other projects. (1) Make sure the yaml-cpp options are prefixed with YAML (2) Hide platform-specific options when possible to avoid cluttering the cmake option list * Update docs for change from BUILD_SHARED_LIBS to YAML_BUILD_SHARED_LIBS
-
Andy Maloney authored
Setting CMAKE_CXX_STANDARD and CMAKE_CXX_STANDARD_REQUIRED directly is problematic when including yaml-cpp as a subproject. The proper way is to set these per-target.
-
Andy Maloney authored
This sets the other variables: https://cmake.org/cmake/help/latest/command/project.html
-
- 04 Aug, 2019 1 commit
-
-
Jeppe Blicher Tarp authored
Specifically, printing `.nan`, `.inf`, and `-.inf`, respectively, as per the spec section 10.2.1.4.
-
- 17 Apr, 2019 1 commit
-
-
bedapisl authored
Invalid access via operator[] or as<> will now print the offending key, if possible. For example: a: x: 1 y: 2 node["a"]["z"].as<int>() will say that the key "z" was invalid.
-
- 24 Mar, 2019 2 commits
-
-
Jesse Beder authored
It wouldn't have compiled anyways, since the Scanner and Directive objects inside it are incomplete types at the time of the move definitions.
-
peterchen-cp authored
-
- 13 Mar, 2019 1 commit
-
-
Ted Lyngmo authored
* Add compilation flags: -Wshadow -Weffc++ -pedantic -pedantic-errors * Delete implicit copy & move constructors & assignment operators in classes with pointer data members. * An exception to the above: Add default copy & move constructors & assignment operators for the Binary class. * Convert boolean RegEx operators to binary operators. * Initialize all members in all classes in ctors. * Let default ctor delegate to the converting ctor in Binary and RegEx * Don't change any tests except regex_test (as a result of the change to binary operators). Note: https://bugzilla.redhat.com/show_bug.cgi?id=1544675 makes -Weffc++ report a false positive in "include/yaml-cpp/node/impl.h".
-
- 12 Mar, 2019 1 commit
-
-
caryoscelus authored
ref #110
-
- 27 Feb, 2019 1 commit
-
-
Olli Wang authored
NDK now uses ninja for building but yaml-cpp would emit the “ninja: error: build.ninja:326: bad $-escape (literal $ must be written as $$)” error due to syntax error in the generated build.ninja file. Related issue: https://github.com/jbeder/yaml-cpp/issues/630
-
- 13 Feb, 2019 1 commit
-
-
tt4g authored
Splitting the condition of the if statement containing `constant expression` eliminates warnings in Visual Studio with /W4.
-
- 06 Jan, 2019 1 commit
-
-
pent0 authored
-
- 21 Dec, 2018 1 commit
-
-
Simon Gene Gottlieb authored
The issue is that numbers like 2.01 or 3.01 can not be precisely represented with binary floating point numbers. This replaces all occurrences of 'std::numeric_limits<T>::digits10 + 1' with 'std::numeric_limits<T>::max_digits10'. Background: Using 'std::numeric_limits<T>::digits10 + 1' is not precise enough. Converting a 'float' into a 'string' and back to a 'float' will not always produce the original 'float' value. To guarantee that the 'string' representation has sufficient precision the value 'std::numeric_limits<T>::max_digits10' has to be used.
-
- 23 Nov, 2018 1 commit
-
-
Alexander Anokhin authored
* Removed an expression which is always true * The second expression (ch is space) is removed because the first one contains space 0x20 * nextEmptyLine is always false so it is removed from the expression
-
- 19 Nov, 2018 1 commit
-
-
Joel Frederico authored
Let CMake handle the default optimizations for various configurations. We don't need to override them. In fact, overriding them makes it impossible for users to override them themselves.
-
- 18 Nov, 2018 1 commit
-
-
Lassi Hämäläinen authored
- Option defaults to ON and setting it to OFF, disables install target generation
-