1. 05 Oct, 2019 1 commit
  2. 02 Oct, 2019 4 commits
  3. 17 Apr, 2019 1 commit
  4. 24 Mar, 2019 1 commit
  5. 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
  6. 12 Mar, 2019 1 commit
  7. 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
  8. 23 Nov, 2018 1 commit
  9. 25 Sep, 2018 1 commit
  10. 23 Sep, 2018 1 commit
  11. 04 Sep, 2018 1 commit
  12. 03 Sep, 2018 2 commits
  13. 03 Jul, 2018 1 commit
  14. 30 Jun, 2018 1 commit
  15. 14 May, 2018 1 commit
  16. 24 Mar, 2018 1 commit
  17. 28 Jan, 2018 1 commit
  18. 25 Jul, 2017 1 commit
  19. 13 Dec, 2016 1 commit
  20. 03 Dec, 2016 3 commits
  21. 02 Dec, 2016 1 commit
  22. 12 Oct, 2016 2 commits
  23. 18 Aug, 2016 1 commit
  24. 18 Jul, 2016 1 commit
    • c0nk's avatar
      Change node_map type from map<ptr,ptr> to vector<pair<ptr,ptr>> (#386) · f0b15cd6
      c0nk authored
      * Change node_map type from map<ptr,ptr> to vector<pair<ptr,ptr>>
      
      Map nodes are now iterated over in document order.
      
      * Change insert_map_pair to always append
      
      Always append in insert_map_pair even if the key is already present.
      This breaks the behavior of force_insert which now always inserts KVs
      even if the key is already present. The first insert for duplicated keys
      now takes precedence for lookups.
      f0b15cd6
  25. 13 May, 2016 5 commits
  26. 02 Apr, 2016 1 commit
  27. 01 Apr, 2016 1 commit
  28. 31 Jan, 2016 2 commits
    • Scott Wolchok's avatar
      Avoid copying cached RegExes for scalars · 005a6a19
      Scott Wolchok authored
      This improves performance on the test.yaml attached to #158 by about
      25% on my machine as compared to the previous commit (0.25s -> 0.20s),
      as measured by `time build/util/parse < test.yaml > /dev/null`.
      005a6a19
    • Scott Wolchok's avatar
      Cache scalar regexes · 8c35a8ff
      Scott Wolchok authored
      This improves performance on the test.yaml attached to #158 by about
      35% on my machine (0.39s -> 0.25s), as measured by
      `time build/util/parse < test.yaml > /dev/null`.
      8c35a8ff