1. 18 8月, 2018 1 次提交
    • W
      Fix destructuring alternation · 0673dee1
      William Langford 提交于
      Attempting to use the existing FORK_OPT opcode resulted in difficulty
      knowing when to pop an error message off the stack and when not to. This
      commit makes DESTRUCTURE_ALT a real opcode that is identical to
      FORK_OPT, except for never pushing the error message onto the stack when
      continuing from an error backtrack.
      
      Some small changes were necessary to the DUP/POP behavior surrounding
      destructuring to accomodate this.
      0673dee1
  2. 17 8月, 2018 1 次提交
  3. 12 5月, 2018 1 次提交
  4. 07 3月, 2018 2 次提交
  5. 02 3月, 2018 1 次提交
  6. 24 2月, 2018 1 次提交
  7. 21 2月, 2018 4 次提交
  8. 05 1月, 2018 1 次提交
  9. 13 12月, 2017 1 次提交
  10. 12 12月, 2017 3 次提交
    • N
      Update AUTHORS · 8eff744e
      Nicolas Williams 提交于
      8eff744e
    • D
      Added rawfile · b4742c12
      David Fetter 提交于
      In passing, clean remnants of argfile from slurpfile docs.
      b4742c12
    • N
      Revert "reduce: handle empty updates (fix #1313)" · 9a4576e7
      Nicolas Williams 提交于
      This reverts commit e24af3c7.
      
      While the semantics are desirable, there is no way to implement them
      efficiently.  The reason is that in order to handle backtracking (empty)
      from the state update expression, we have to retain a reference to the
      reduction state value in order to restore it upon backtracking.
      Retaining a reference to the reduction state kills performance by
      causing lots of additional memory allocations and garbage because the
      input to the update expression will always have at least two references,
      thus no changes to it can be done in-place, and all changes end up being
      CoW changes.
      
      Avoiding this is the very reason for the LOADVN instruction (leaving
      `null` in the variable loaded from).
      9a4576e7
  11. 11 12月, 2017 1 次提交
  12. 05 12月, 2017 2 次提交
  13. 30 11月, 2017 2 次提交
    • W
      Actually fix the strptime tests · 0c9eaced
      William Langford 提交于
      This has been a complicated issue to fix for a number of reasons.
      The core of it is that the behavior is different between different
      versions of macOS, some of which set possible-but-incorrect values.
      
      This commit addresses the issue by always using our computation for
      tm_wday and tm_yday on macOS. As a side-effect, strptime format
      strings that specify %u and %j will no longer work on macOS.
      0c9eaced
    • E
      Keep object keys in parsing order in `tostream` output · 476b3677
      Eric Bréchemier 提交于
      As noted by @nicowilliams, `tostream` used `keys`,
      which sorts the keys in alphabetical order, instead
      of `keys_unsorted`, which preserves the parsing order.
      
      Fixes #1541.
      476b3677
  14. 28 11月, 2017 3 次提交
  15. 23 11月, 2017 2 次提交
  16. 19 6月, 2017 1 次提交
  17. 22 5月, 2017 1 次提交
    • N
      Deal with strptime() on OS X and *BSD (fix #1415) · c538237f
      Nicolas Williams 提交于
      strptime() on OS X and *BSDs (reputedly) does not set tm_wday and
      tm_yday unless corresponding %U and %j format specifiers were used.
      That can be... surprising when one parsed year, month, and day anyways.
      Glibc's strptime() conveniently sets tm_wday and tm_yday in those cases,
      but OS X's does not, ignoring them completely.
      
      This commit makes jq compute those where possible, though the day of
      week computation may be wrong for dates before 1900-03-01 or after
      2099-12-31.
      c538237f
  18. 21 5月, 2017 5 次提交
  19. 11 5月, 2017 1 次提交
  20. 04 5月, 2017 1 次提交
    • J
      Use unsorted keys in walk · ca12bd9b
      Jonathan Word 提交于
      Preserve key sorting order when executing in walk, if sorted keys is desired `--sort-keys` should be used to explicitly obtain sorted keys.
      ca12bd9b
  21. 30 4月, 2017 1 次提交
  22. 27 4月, 2017 1 次提交
  23. 22 4月, 2017 1 次提交
  24. 16 4月, 2017 1 次提交
  25. 03 4月, 2017 1 次提交