1. Nov 26, 2018
  2. Nov 25, 2018
  3. Nov 09, 2018
  4. Nov 06, 2018
    • Corey Farrell's avatar
      Remove inappropriate jsonp_free which caused segmentation fault. · e262ea5f
      Corey Farrell authored
      pack_string should never free str on error.  This wouldn't be a problem
      except the check for `ours` was inverted.  Just remove the check for
      ours since the true condition is unreachable.
      
      json_vpack_ex also had an error check for s.has_error.  This can never
      be true unless value is NULL.
      
      Expand pack_unpack testing to cover empty format string, NULL object
      value with non-null concatenated key, array containing a non-null object
      after a NULL (error) string.
      
      Fixes #444
      e262ea5f
  5. Oct 17, 2018
  6. Oct 15, 2018
  7. Sep 30, 2018
  8. Sep 29, 2018
  9. Sep 26, 2018
    • Corey Farrell's avatar
      More work on json_pack error reporting. · 8d659113
      Corey Farrell authored
      * Remove errant line-feed from pack_object error message.
      * Correct error message in pack_object_inter.
      * Create pack_integer / pack_real to get the correct error messages on
        failure when packing numeric values.
      * Add tests for packing NAN and infinity directly, in an array and as
        an object value.
      8d659113
    • Corey Farrell's avatar
      json_pack: Improve handling of formats with '?' and '*'. · 5df5fc5b
      Corey Farrell authored
      When NULL is received for an optional argument we should not set an
      error message as this would block later error messages. If NULL is
      received for a non-optional string we should set has_error. Set
      has_error for UTF-8 errors to ensure optional strings with UTF-8
      errors are not replaced with json_null(). Use 'purpose' argument in
      NULL error messages of read_string.
      
      Add error handling and tests for invalid formats where '+', '#', or '%'
      is used on an optional string 's?' or 's*'.
      
      Fix NULL string error messages to use 'purpose'.
      
      Refactor skipping of '*' token, this is now handled by read_string and
      pack_object_inter. This allows invalid format strings such as 's*#' and
      's*+' to produce error messages.
      
      Fixes #437
      5df5fc5b
  10. Sep 04, 2018
  11. Aug 31, 2018
  12. Aug 30, 2018
  13. Aug 12, 2018
  14. Aug 09, 2018
  15. Aug 02, 2018
  16. Jul 30, 2018
  17. Jul 25, 2018
  18. Jul 15, 2018
    • Crayon's avatar
      Update copyright for 2018 · 3e13f514
      Crayon authored
      3e13f514
    • Corey Farrell's avatar
      Deal with warnings under gcc 8. · 81fe13ee
      Corey Farrell authored
      Recent versions of gcc have introduced compiler warnings for string
      operations that could be truncated.  This caused problems with -Werror.
      src/error.c used strncpy to write "..." to a string, but skipped writing
      the NUL terminator.  Switch this to use memcpy.  src/load.c produced
      warnings from snprintf writing error strings that could be truncated.
      Added code to autotools build to detect `-Wno-format-truncation', add it
      to AM_CFLAGS if supported.
      81fe13ee
  19. Jul 10, 2018
  20. May 22, 2018
  21. May 18, 2018
  22. May 07, 2018
  23. Mar 22, 2018
  24. Mar 20, 2018
  25. Mar 11, 2018