1. 29 Nov, 2019 1 commit
  2. 23 Nov, 2019 1 commit
  3. 04 Nov, 2019 1 commit
  4. 31 Oct, 2019 1 commit
  5. 23 Oct, 2019 1 commit
    • Romain Geissler @ Amadeus's avatar
      Fix -Wmisleading-indentation warning when using gcc >= 6. (#779) · 14c87258
      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);
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      14c87258
  6. 16 Oct, 2019 1 commit
  7. 13 Oct, 2019 1 commit
  8. 11 Oct, 2019 1 commit
  9. 05 Oct, 2019 1 commit
  10. 04 Oct, 2019 1 commit
  11. 02 Oct, 2019 6 commits
  12. 27 Sep, 2019 4 commits
    • Andy Maloney's avatar
    • Isabella Muerte's avatar
      Fix `DEBUG_POSTFIX` property (#746) · 9d7e556e
      Isabella Muerte authored
      The generator expressions here are actually unnecessary, now that I think about it.
      
      This should fix #745
      9d7e556e
    • Ezekiel Warren's avatar
      Add bazel Support (#724) · 62ff3514
      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"],
      )
      62ff3514
    • Isabella Muerte's avatar
      Refactor CMake to use more modern paradigms (#741) · 5e9cb012
      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
      5e9cb012
  13. 25 Sep, 2019 1 commit
  14. 15 Sep, 2019 3 commits
  15. 10 Sep, 2019 3 commits
  16. 04 Aug, 2019 1 commit
  17. 17 Apr, 2019 1 commit
  18. 24 Mar, 2019 2 commits
  19. 13 Mar, 2019 1 commit
    • Ted Lyngmo's avatar
      Apply formatting/style tweaks to comply with compile time diagnostics for g++ and clang++ (#686) · 0d5c5715
      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".
      0d5c5715
  20. 12 Mar, 2019 1 commit
  21. 27 Feb, 2019 1 commit
  22. 13 Feb, 2019 1 commit
  23. 06 Jan, 2019 1 commit
  24. 21 Dec, 2018 1 commit
    • Simon Gene Gottlieb's avatar
      Fix float precision (#649) · abf941b2
      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.
      abf941b2
  25. 23 Nov, 2018 1 commit
  26. 19 Nov, 2018 1 commit
    • Joel Frederico's avatar
      Don't stomp on build flags (#635) · 2443da52
      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.
      2443da52
  27. 18 Nov, 2018 1 commit