| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now that #1313 is fixed, |= no longer outputs null when the RHS update
expression outputs empty.
When a user wants to keep the current value of the LHS they would have
the RHS update expression output `.`, so having `empty` achieve the same
thing would be redundant. The obvious thing to do is to delete the LHS
when the RHS update outputs `empty` (i.e., doesn't output any values).
It's reasonable to think that existing programs won't be broken by this
change, because reduce and |= not handling empty well is clearly a bug.
(Though it's possible that some programs were using empty to quickly
terminate reduce or |=, it's not likely. They should use label/break
instead.)
Prior to this change |= would use the _last_ value output by the RHS
update expression. With this change |= will use the _first_ value
instead. This change _is_ a minor backwards-incompatible change. It
may or may not be acceptable; we'll see. It is a useful change in that
it makes |= faster when the update expression produces multiple values.
|
|
|
|
|
|
first(g) was extracting two values, which, if g is slow, made first(g)
slow. And if the second extraction were to throw an error, then
first(g) would throw that error, which is clearly not the right thing to
do. Besides that, first(g) was allocating garbage, which it no longer
does.
|
|
|
|
|
|
Handle cut-off UTF-8 sequences when reading files
|
|
Read additional bytes from the file to complete the UTF-8 sequence so the bytes
in it don't get converted to U+FFFD replacement characters.
|
|
while true; do printf '{"deeper": '; done | jq .
|
|
This addresses #1136, and mitigates a stack exhaustion when printing
a very deeply nested term.
|
|
|
|
This reverts commit 0b8218515eabf1a967eba0dbcc7a0e5ae031a509.
There is a new oniguruma package which previously trashed the build.
|
|
simply -> simple
|
|
|
|
jq has been in the community repo for [just over a year now][0].
[0]: https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/jq&id=8d5e06065bc92bf56ea651970c9bda07fb545554
|
|
|
|
|
|
- cd out of the tmp dir before attempting to remove it.
|
|
|
|
|
|
|
|
|
|
|
|
Thanks @JanSchulz, @nicowilliams!
|
|
|
|
|
|
One can now run:
make TRACE_TESTS=1 check
to get detailed output
|
|
Use %%FAIL IGNORE MSG for error messages that differ on Windows, and
move the sort_by/group_by tests that fail qhen qsort() is not stable.
Now only tests/sorttest and tests/shtest are disabled on Windows.
|
|
|
|
Signed-off-by: Nicolas Williams <nico@cryptonector.com>
|
|
Signed-off-by: Nicolas Williams <nico@cryptonector.com>
|
|
Signed-off-by: Nicolas Williams <nico@cryptonector.com>
|
|
Signed-off-by: Nicolas Williams <nico@cryptonector.com>
|
|
For this to work, one of the core commiter should do:
* enable appveyor in the github project (grant access)
* Make an appveyor account and add the github jq repo as a new project
inspirations from:
appveyor, msys2, use bash environment to build...
* https://github.com/ariscop/elemental-ircd/blob/appveyor/appveyor.yml
* https://github.com/khaledhosny/ots/pull/67/files
* https://github.com/universal-ctags/ctags/blob/master/appveyor.yml
* https://github.com/universal-ctags/ctags/blob/master/win32/appveyor.bat
and with mvsc
* https://github.com/khaledhosny/ots/blob/master/.appveyor.yml
Signed-off-by: Nicolas Williams <nico@cryptonector.com>
|
|
|
|
|
|
|
|
|
|
|
|
Allow a continuation on a comment immediately after a shebang to make
this traditional hack possible:
#!/bin/sh
# this next line is ignored by jq \
exec jq -f "$0" "$@"
# jq code follows
But continue only on the first line following a shebang, and only if
it's a comment.
|
|
|
|
|
|
|
