| Age | Commit message (Collapse) | Author |
|---|
|
|
|
I updated some of these gems for a different project, and
suddenly `rake build` was giving very different output
compared to the current gh-pages. This commit makes sure
everyone updating gh-pages is using reasonably similar
versions, so we avoid spurious diffs.
|
|
Conflicts:
docs/content/2.download/default.yml
docs/content/index/index.yml
docs/default_manpage.md
docs/templates/index.liquid
docs/templates/shared/_header.liquid
|
|
|
|
|
|
Conflicts:
docs/content/3.manual/manual.yml
|
|
|
|
|
|
This is part 2 of the fix to #817. Part 1 is the previous commit.
|
|
This is part 1 of the fix for #817. The next commit is part 2.
|
|
|
|
|
|
|
|
|
|
|
|
This lets us use uint16_t for the program counter. JVM
languages have the same limit on method size so it is a
reasonable limit.
|
|
See https://github.com/stedolan/jq/issues/488#issuecomment-124998113
|
|
|
|
|
|
|
|
Adjust what gets cleaned up now that ChangeLog and
config/.gitignore are checked into the repo, and skip
install and distcheck steps.
|
|
The .com redirects to .io, but might as well have the
correct one to begin with.
|
|
This affects where `make check` tells you to report failures.
|
|
|
|
|
|
|
|
|
|
|
|
The jq 1.3 filenames for Windows are jq-1.3.exe instead of jq.exe. Updated these so they no longer return a 404.
|
|
This includes the following commits from the gh-pages branch:
- 63e80b8
- d24a397
- 9796cd6
- ee21707
- ccb0f1d
- 200e6b3
- 64134c0
- 57152d2
- 8ffbfa3
|
|
By lowering the precedence of rules that should never use
the generic Exp '?' rule.
|
|
This was an important conflict. In the following expression:
def a: 0; . | a
Bison needs to decide between these two equally valid
parses:
(def a: 0; .) | a
def a: 0; (. | a)
For jq we want the second one, because the first results in
"a/0 is not defined". In the current parser the first parse
is a reduce and the second parse is a shift. Since Bison
prefers to shift in shift/reduce conflicts, we accidentally
got the correct behavior.
This commit adds a precedence level FUNCDEF which is lower
precedence than '|', meaning we explicitly choose the
correct parse.
Of course many unit tests already cover this case, but I
added one specifically for it.
|
|
|
|
|
|
https://github.com/travis-ci/travis-ci/issues/4123
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Remove excess layer creation
This is an antipattern in Docker.
* Remove build tools once build is complete
Leaving them around is not necessary and expands the image size 5x
* Make check works with libonig installed
* Compiles statically (needs libonig to be built rather than installed)
* Valgrind doesn't work with the use of TLS in jq so it's disabled -- this
might be a FIXME situation; I'm not familiar enough with valgrind to
say whether this is expected
* Make entrypoint be the jq binary so that the image can also be used
to run jq in environments where you don't want to or can't install
jq (such as CoreOS).
|
|
|
|
Previously, with clang++:
jq.h:46:37: error: typedef redefinition with different
types ('struct jq_util_input_state *' vs 'jq_util_input_state')
With g++:
jq.h:46:37: error: conflicting declaration
‘typedef struct jq_util_input_state* jq_util_input_state’
This typedef was added to libjq by commit 0d41447 which was
after the 1.4 release, so although it is a public API, this
is not a backcompat break because it has never been in a
release.
Specifying the "*" at all uses of jq_util_input_state is
slightly tedious, but jq_state already works that way, so at
least it will be consistent.
|
|
|
|
|
|
The CHECK_MATH_FUNC() m4 macro needs work. It should use
AC_RUN_IFELSE(), not just AC_LINK_IFELSE(), and it should #define
_GNU_SOURCE and/or other such feature macros in the prologue to get
non-standard math functions (alternatvely jq should only support
standard math functions).
|
|
|
|
|
