===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
jq-1.6/scripts/update-website-10-# build website
jq-1.6/scripts/update-website:11:scriptdir=`dirname "$0"`
jq-1.6/scripts/update-website-12-cd "$scriptdir"/../docs
##############################################
jq-1.6/scripts/crosscompile-13-set -e
jq-1.6/scripts/crosscompile:14:cd `dirname "$0"`/../build
jq-1.6/scripts/crosscompile-15-
##############################################
jq-1.6/ChangeLog-52-
jq-1.6/ChangeLog:53:	Add `{$var}` `. as {$var}` syntax (fix #831)
jq-1.6/ChangeLog-54-
##############################################
jq-1.6/ChangeLog-206-
jq-1.6/ChangeLog:207:	Add `$__loc__` (fix #740)
jq-1.6/ChangeLog-208-
##############################################
jq-1.6/ChangeLog-324-
jq-1.6/ChangeLog:325:	Add `label $name | EXP`; fix `break`
jq-1.6/ChangeLog-326-
##############################################
jq-1.6/ChangeLog-516-
jq-1.6/ChangeLog:517:	Use `def f($a): ...;` syntax for builtins
jq-1.6/ChangeLog-518-
jq-1.6/ChangeLog:519:	Add `def f($arg):` syntax (fix #524)
jq-1.6/ChangeLog-520-
##############################################
jq-1.6/ChangeLog-582-
jq-1.6/ChangeLog:583:	Add `foreach EXP as $var (INIT; UPDATE)` form
jq-1.6/ChangeLog-584-
##############################################
jq-1.6/tests/shtest-31-# String constant folding (addition only)
jq-1.6/tests/shtest:32:nref=$($VALGRIND $Q $JQ -n --debug-dump-disasm '"foo"' | wc -l)
jq-1.6/tests/shtest-33-
jq-1.6/tests/shtest-34-# Numeric constant folding (not all ops yet)
jq-1.6/tests/shtest:35:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '1+1' | wc -l)
jq-1.6/tests/shtest-36-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-39-fi
jq-1.6/tests/shtest:40:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '1-1' | wc -l)
jq-1.6/tests/shtest-41-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-44-fi
jq-1.6/tests/shtest:45:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '2*3' | wc -l)
jq-1.6/tests/shtest-46-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-49-fi
jq-1.6/tests/shtest:50:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '9/3' | wc -l)
jq-1.6/tests/shtest-51-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-54-fi
jq-1.6/tests/shtest:55:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '9==3' | wc -l)
jq-1.6/tests/shtest-56-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-59-fi
jq-1.6/tests/shtest:60:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '9!=3' | wc -l)
jq-1.6/tests/shtest-61-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-64-fi
jq-1.6/tests/shtest:65:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '9<=3' | wc -l)
jq-1.6/tests/shtest-66-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-69-fi
jq-1.6/tests/shtest:70:n=$($VALGRIND $Q $JQ -n --debug-dump-disasm '9>=3' | wc -l)
jq-1.6/tests/shtest-71-if [ $n -ne $nref ]; then
##############################################
jq-1.6/tests/shtest-134-
jq-1.6/tests/shtest:135:## If we add an option to stream to the `import ... as $symbol;` directive
jq-1.6/tests/shtest-136-## then we can move these tests into tests/all.test.
##############################################
jq-1.6/tests/shtest-204-
jq-1.6/tests/shtest:205:if [ $(HOME="$mods" $VALGRIND $Q $JQ --debug-dump-disasm -n fg | grep '^[a-z]' | wc -l) -gt 3 ]; then
jq-1.6/tests/shtest-206-    echo "Binding too many defs into program" 1>&2
##############################################
jq-1.6/m4/ax_compare_version.m4-134-      # Determine the number of characters in A and B.
jq-1.6/m4/ax_compare_version.m4:135:      ax_compare_version_len_A=`echo "$A" | $AWK '{print(length)}'`
jq-1.6/m4/ax_compare_version.m4:136:      ax_compare_version_len_B=`echo "$B" | $AWK '{print(length)}'`
jq-1.6/m4/ax_compare_version.m4-137-
jq-1.6/m4/ax_compare_version.m4-138-      # Set A to no more than B's length and B to no more than A's length.
jq-1.6/m4/ax_compare_version.m4:139:      A=`echo "$A" | sed "s/\(.\{$ax_compare_version_len_B\}\).*/\1/"`
jq-1.6/m4/ax_compare_version.m4:140:      B=`echo "$B" | sed "s/\(.\{$ax_compare_version_len_A\}\).*/\1/"`
jq-1.6/m4/ax_compare_version.m4-141-    ],
##############################################
jq-1.6/m4/ax_compare_version.m4-143-      # A count greater than zero means use only that many subversions
jq-1.6/m4/ax_compare_version.m4:144:      A=`echo "$A" | sed "s/\(\([[0-9]]\{4\}\)\{m4_substr($2,2)\}\).*/\1/"`
jq-1.6/m4/ax_compare_version.m4:145:      B=`echo "$B" | sed "s/\(\([[0-9]]\{4\}\)\{m4_substr($2,2)\}\).*/\1/"`
jq-1.6/m4/ax_compare_version.m4-146-    ],
##############################################
jq-1.6/m4/ax_compare_version.m4-152-    # Pad zeros at end of numbers to make same length.
jq-1.6/m4/ax_compare_version.m4:153:    ax_compare_version_tmp_A="$A`echo $B | sed 's/./0/g'`"
jq-1.6/m4/ax_compare_version.m4:154:    B="$B`echo $A | sed 's/./0/g'`"
jq-1.6/m4/ax_compare_version.m4-155-    A="$ax_compare_version_tmp_A"
##############################################
jq-1.6/src/main.c-144-  /* debugging only */
jq-1.6/src/main.c:145:  DUMP_DISASM           = 65536,
jq-1.6/src/main.c-146-};
##############################################
jq-1.6/config/m4/misc.m4-2-dnl Shamelessly stolen from Heimdal
jq-1.6/config/m4/misc.m4:3:AC_DEFUN([upcase],[`echo $1 | tr abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ`])dnl
##############################################
jq-1.6/config/m4/find-func-no-libs2.m4-54-	eval "ac_cv_func_$1=yes"
jq-1.6/config/m4/find-func-no-libs2.m4:55:	eval "ac_cv_lib_`echo "$ac_res" | sed 's/-l//'`=yes"
jq-1.6/config/m4/find-func-no-libs2.m4-56-	AC_DEFINE_UNQUOTED($ac_tr_func)
##############################################
jq-1.6/docs/content/3.manual/manual.yml-221-        This option passes a value to the jq program as a predefined
jq-1.6/docs/content/3.manual/manual.yml:222:        variable. If you run jq with `--arg foo bar`, then `$foo` is
jq-1.6/docs/content/3.manual/manual.yml-223-        available in the program and has the value `"bar"`. Note that
jq-1.6/docs/content/3.manual/manual.yml-224-        `value` will be treated as a string, so `--arg foo 123` will
jq-1.6/docs/content/3.manual/manual.yml:225:        bind `$foo` to `"123"`.
jq-1.6/docs/content/3.manual/manual.yml-226-
jq-1.6/docs/content/3.manual/manual.yml-227-        Named arguments are also available to the jq program as
jq-1.6/docs/content/3.manual/manual.yml:228:        `$ARGS.named`.
jq-1.6/docs/content/3.manual/manual.yml-229-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-233-        predefined variable. If you run jq with `--argjson foo 123`, then
jq-1.6/docs/content/3.manual/manual.yml:234:        `$foo` is available in the program and has the value `123`.
jq-1.6/docs/content/3.manual/manual.yml-235-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-239-        an array of the parsed JSON values to the given global variable.
jq-1.6/docs/content/3.manual/manual.yml:240:        If you run jq with `--slurpfile foo bar`, then `$foo` is available
jq-1.6/docs/content/3.manual/manual.yml-241-        in the program and has an array whose elements correspond to the
##############################################
jq-1.6/docs/content/3.manual/manual.yml-246-        This option reads in the named file and binds its contents to the given
jq-1.6/docs/content/3.manual/manual.yml:247:        global variable.  If you run jq with `--rawfile foo bar`, then `$foo` is
jq-1.6/docs/content/3.manual/manual.yml-248-        available in the program and has a string whose contents are to the texs
##############################################
jq-1.6/docs/content/3.manual/manual.yml-261-        Remaining arguments are positional string arguments.  These are
jq-1.6/docs/content/3.manual/manual.yml:262:        available to the jq program as `$ARGS.positional[]`.
jq-1.6/docs/content/3.manual/manual.yml-263-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-266-        Remaining arguments are positional JSON text arguments.  These
jq-1.6/docs/content/3.manual/manual.yml:267:        are available to the jq program as `$ARGS.positional[]`.
jq-1.6/docs/content/3.manual/manual.yml-268-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-314-          If the key contains special characters, you need to surround
jq-1.6/docs/content/3.manual/manual.yml:315:          it with double quotes like this: `."foo$"`, or else `.["foo$"]`.
jq-1.6/docs/content/3.manual/manual.yml-316-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-786-
jq-1.6/docs/content/3.manual/manual.yml:787:          `has($key)` has the same effect as checking whether `$key`
jq-1.6/docs/content/3.manual/manual.yml-788-          is a member of the array returned by `keys`, although `has`
##############################################
jq-1.6/docs/content/3.manual/manual.yml-1022-
jq-1.6/docs/content/3.manual/manual.yml:1023:      - title: "`$__loc__`"
jq-1.6/docs/content/3.manual/manual.yml-1024-        body: |
##############################################
jq-1.6/docs/content/3.manual/manual.yml-1026-          Produces an object with a "file" key and a "line" key, with
jq-1.6/docs/content/3.manual/manual.yml:1027:          the filename and line number where `$__loc__` occurs, as
jq-1.6/docs/content/3.manual/manual.yml-1028-          values.
##############################################
jq-1.6/docs/content/3.manual/manual.yml-1704-
jq-1.6/docs/content/3.manual/manual.yml:1705:      - title: "`$ENV`, `env`"
jq-1.6/docs/content/3.manual/manual.yml-1706-        body: |
jq-1.6/docs/content/3.manual/manual.yml-1707-
jq-1.6/docs/content/3.manual/manual.yml:1708:          `$ENV` is an object representing the environment variables as
jq-1.6/docs/content/3.manual/manual.yml-1709-          set when the jq program started.
##############################################
jq-1.6/docs/content/3.manual/manual.yml-1981-
jq-1.6/docs/content/3.manual/manual.yml:1982:             Same as `JOIN($idx; stream; idx_expr; .)`.
jq-1.6/docs/content/3.manual/manual.yml-1983-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2173-
jq-1.6/docs/content/3.manual/manual.yml:2174:          The `break $label_name` expression will cause the program to
jq-1.6/docs/content/3.manual/manual.yml:2175:          to act as though the nearest (to the left) `label $label_name`
jq-1.6/docs/content/3.manual/manual.yml-2176-          produced `empty`.
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2188-
jq-1.6/docs/content/3.manual/manual.yml:2189:          because no label `$out` is visible.
jq-1.6/docs/content/3.manual/manual.yml-2190-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2413-    entries:
jq-1.6/docs/content/3.manual/manual.yml:2414:      - title: "Variable / Symbolic Binding Operator: `... as $identifier | ...`"
jq-1.6/docs/content/3.manual/manual.yml-2415-        body: |
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2432-          defining variables. Still, sometimes they do make things easier, so jq
jq-1.6/docs/content/3.manual/manual.yml:2433:          lets you define variables using `expression as $variable`. All
jq-1.6/docs/content/3.manual/manual.yml-2434-          variable names start with `$`. Here's a slightly uglier version of the
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2462-
jq-1.6/docs/content/3.manual/manual.yml:2463:          The expression `exp as $x | ...` means: for each value of expression
jq-1.6/docs/content/3.manual/manual.yml-2464-          `exp`, run the rest of the pipeline with the entire original input, and
jq-1.6/docs/content/3.manual/manual.yml:2465:          with `$x` set to that value.  Thus `as` functions as something of a
jq-1.6/docs/content/3.manual/manual.yml-2466-          foreach loop.
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2468-          Just as `{foo}` is a handy way of writing `{foo: .foo}`, so
jq-1.6/docs/content/3.manual/manual.yml:2469:          `{$foo}` is a handy way of writing `{foo:$foo}`.
jq-1.6/docs/content/3.manual/manual.yml-2470-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2599-          input's `.foo` field to each element of the array.  Do note
jq-1.6/docs/content/3.manual/manual.yml:2600:          that calling `addvalue(.[])` will cause the `map(. + $f)` part
jq-1.6/docs/content/3.manual/manual.yml-2601-          to be evaluated once per value in the value of `.` at the call
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2632-          $times_three | [.+ $times_three]) | ...`: here the binding
jq-1.6/docs/content/3.manual/manual.yml:2633:          `$times_three` is _not_ visible past the closing parenthesis.
jq-1.6/docs/content/3.manual/manual.yml-2634-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2643-
jq-1.6/docs/content/3.manual/manual.yml:2644:          For each result that `.[]` produces, `. + $item` is run to
jq-1.6/docs/content/3.manual/manual.yml-2645-          accumulate a running total, starting from 0. In this
##############################################
jq-1.6/docs/content/3.manual/manual.yml-2713-
jq-1.6/docs/content/3.manual/manual.yml:2714:          The form is `foreach EXP as $var (INIT; UPDATE; EXTRACT)`.
jq-1.6/docs/content/3.manual/manual.yml-2715-          Like `reduce`, `INIT` is evaluated once to produce a state
jq-1.6/docs/content/3.manual/manual.yml:2716:          value, then each output of `EXP` is bound to `$var`, `UPDATE`
jq-1.6/docs/content/3.manual/manual.yml-2717-          is evaluated for each output of `EXP` with the current state
jq-1.6/docs/content/3.manual/manual.yml:2718:          and with `$var` visible.  Each value output by `UPDATE`
jq-1.6/docs/content/3.manual/manual.yml-2719-          replaces the previous state.  Finally, `EXTRACT` is evaluated
##############################################
jq-1.6/docs/content/3.manual/manual.yml-3000-      Note that the LHS of assignment operators refers to a value in
jq-1.6/docs/content/3.manual/manual.yml:3001:      `.`.  Thus `$var.foo = 1` won't work as expected (`$var.foo` is
jq-1.6/docs/content/3.manual/manual.yml-3002-      not a valid or useful path expression in `.`); use `$var | .foo =
##############################################
jq-1.6/docs/content/3.manual/manual.yml-3020-          Note that the left-hand side of '|=' refers to a value in `.`.
jq-1.6/docs/content/3.manual/manual.yml:3021:          Thus `$var.foo |= . + 1` won't work as expected (`$var.foo` is
jq-1.6/docs/content/3.manual/manual.yml-3022-          not a valid or useful path expression in `.`); use `$var |
##############################################
jq-1.6/docs/content/3.manual/manual.yml-3169-
jq-1.6/docs/content/3.manual/manual.yml:3170:      For example, with `-L$HOME/.jq` a module `foo` can be found in
jq-1.6/docs/content/3.manual/manual.yml:3171:      `$HOME/.jq/foo.jq` and `$HOME/.jq/foo/foo.jq`.
jq-1.6/docs/content/3.manual/manual.yml-3172-
##############################################
jq-1.6/docs/content/3.manual/manual.yml-3208-
jq-1.6/docs/content/3.manual/manual.yml:3209:      - title: "`import RelativePathString as $NAME [<metadata>];`"
jq-1.6/docs/content/3.manual/manual.yml-3210-        body: |
##############################################
jq-1.6/docs/content/3.manual/manual.yml-3214-          the relative path string.  The file's data will be available
jq-1.6/docs/content/3.manual/manual.yml:3215:          as `$NAME::NAME`.
jq-1.6/docs/content/3.manual/manual.yml-3216-
##############################################
jq-1.6/docs/content/3.manual/v1.3/manual.yml-133-        This option passes a value to the jq program as a predefined
jq-1.6/docs/content/3.manual/v1.3/manual.yml:134:        variable. If you run jq with `--arg foo bar`, then `$foo` is
jq-1.6/docs/content/3.manual/v1.3/manual.yml-135-        available in the program and has the value `"bar"`.
##############################################
jq-1.6/docs/content/3.manual/v1.3/manual.yml-494-
jq-1.6/docs/content/3.manual/v1.3/manual.yml:495:          `has($key)` has the same effect as checking whether `$key`
jq-1.6/docs/content/3.manual/v1.3/manual.yml-496-          is a member of the array returned by `keys`, although `has`
##############################################
jq-1.6/docs/content/3.manual/v1.3/manual.yml-1049-          defining variables. Still, sometimes they do make things easier, so jq
jq-1.6/docs/content/3.manual/v1.3/manual.yml:1050:          lets you define variables using `expression as $variable`. All
jq-1.6/docs/content/3.manual/v1.3/manual.yml-1051-          variable names start with `$`. Here's a slightly uglier version of the
##############################################
jq-1.6/docs/content/3.manual/v1.3/manual.yml-1079-
jq-1.6/docs/content/3.manual/v1.3/manual.yml:1080:          The expression `exp as $x | ...` means: for each value of expression
jq-1.6/docs/content/3.manual/v1.3/manual.yml-1081-          `exp`, run the rest of the pipeline with the entire original input, and
jq-1.6/docs/content/3.manual/v1.3/manual.yml:1082:          with `$x` set to that value.  Thus `as` functions as something of a
jq-1.6/docs/content/3.manual/v1.3/manual.yml-1083-          foreach loop.
##############################################
jq-1.6/docs/content/3.manual/v1.3/manual.yml-1144-
jq-1.6/docs/content/3.manual/v1.3/manual.yml:1145:          For each result that `.[]` produces, `. + $item` is run to
jq-1.6/docs/content/3.manual/v1.3/manual.yml-1146-          accumulate a running total, starting from 0. In this
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-220-        This option passes a value to the jq program as a predefined
jq-1.6/docs/content/3.manual/v1.6/manual.yml:221:        variable. If you run jq with `--arg foo bar`, then `$foo` is
jq-1.6/docs/content/3.manual/v1.6/manual.yml-222-        available in the program and has the value `"bar"`. Note that
jq-1.6/docs/content/3.manual/v1.6/manual.yml-223-        `value` will be treated as a string, so `--arg foo 123` will
jq-1.6/docs/content/3.manual/v1.6/manual.yml:224:        bind `$foo` to `"123"`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-225-
jq-1.6/docs/content/3.manual/v1.6/manual.yml-226-        Named arguments are also available to the jq program as
jq-1.6/docs/content/3.manual/v1.6/manual.yml:227:        `$ARGS.named`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-228-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-232-        predefined variable. If you run jq with `--argjson foo 123`, then
jq-1.6/docs/content/3.manual/v1.6/manual.yml:233:        `$foo` is available in the program and has the value `123`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-234-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-238-        an array of the parsed JSON values to the given global variable.
jq-1.6/docs/content/3.manual/v1.6/manual.yml:239:        If you run jq with `--slurpfile foo bar`, then `$foo` is available
jq-1.6/docs/content/3.manual/v1.6/manual.yml-240-        in the program and has an array whose elements correspond to the
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-245-        This option reads in the named file and binds its contents to the given
jq-1.6/docs/content/3.manual/v1.6/manual.yml:246:        global variable.  If you run jq with `--rawfile foo bar`, then `$foo` is
jq-1.6/docs/content/3.manual/v1.6/manual.yml-247-        available in the program and has a string whose contents are to the texs
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-260-        Remaining arguments are positional string arguments.  These are
jq-1.6/docs/content/3.manual/v1.6/manual.yml:261:        available to the jq program as `$ARGS.positional[]`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-262-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-265-        Remaining arguments are positional JSON text arguments.  These
jq-1.6/docs/content/3.manual/v1.6/manual.yml:266:        are available to the jq program as `$ARGS.positional[]`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-267-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-313-          If the key contains special characters, you need to surround
jq-1.6/docs/content/3.manual/v1.6/manual.yml:314:          it with double quotes like this: `."foo$"`, or else `.["foo$"]`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-315-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-785-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:786:          `has($key)` has the same effect as checking whether `$key`
jq-1.6/docs/content/3.manual/v1.6/manual.yml-787-          is a member of the array returned by `keys`, although `has`
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1021-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:1022:      - title: "`$__loc__`"
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1023-        body: |
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1025-          Produces an object with a "file" key and a "line" key, with
jq-1.6/docs/content/3.manual/v1.6/manual.yml:1026:          the filename and line number where `$__loc__` occurs, as
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1027-          values.
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1703-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:1704:      - title: "`$ENV`, `env`"
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1705-        body: |
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1706-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:1707:          `$ENV` is an object representing the environment variables as
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1708-          set when the jq program started.
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1980-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:1981:             Same as `JOIN($idx; stream; idx_expr; .)`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-1982-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2172-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2173:          The `break $label_name` expression will cause the program to
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2174:          to act as though the nearest (to the left) `label $label_name`
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2175-          produced `empty`.
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2187-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2188:          because no label `$out` is visible.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2189-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2412-    entries:
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2413:      - title: "Variable / Symbolic Binding Operator: `... as $identifier | ...`"
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2414-        body: |
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2431-          defining variables. Still, sometimes they do make things easier, so jq
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2432:          lets you define variables using `expression as $variable`. All
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2433-          variable names start with `$`. Here's a slightly uglier version of the
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2461-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2462:          The expression `exp as $x | ...` means: for each value of expression
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2463-          `exp`, run the rest of the pipeline with the entire original input, and
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2464:          with `$x` set to that value.  Thus `as` functions as something of a
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2465-          foreach loop.
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2467-          Just as `{foo}` is a handy way of writing `{foo: .foo}`, so
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2468:          `{$foo}` is a handy way of writing `{foo:$foo}`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2469-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2598-          input's `.foo` field to each element of the array.  Do note
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2599:          that calling `addvalue(.[])` will cause the `map(. + $f)` part
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2600-          to be evaluated once per value in the value of `.` at the call
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2631-          $times_three | [.+ $times_three]) | ...`: here the binding
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2632:          `$times_three` is _not_ visible past the closing parenthesis.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2633-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2642-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2643:          For each result that `.[]` produces, `. + $item` is run to
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2644-          accumulate a running total, starting from 0. In this
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2712-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2713:          The form is `foreach EXP as $var (INIT; UPDATE; EXTRACT)`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2714-          Like `reduce`, `INIT` is evaluated once to produce a state
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2715:          value, then each output of `EXP` is bound to `$var`, `UPDATE`
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2716-          is evaluated for each output of `EXP` with the current state
jq-1.6/docs/content/3.manual/v1.6/manual.yml:2717:          and with `$var` visible.  Each value output by `UPDATE`
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2718-          replaces the previous state.  Finally, `EXTRACT` is evaluated
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-2999-      Note that the LHS of assignment operators refers to a value in
jq-1.6/docs/content/3.manual/v1.6/manual.yml:3000:      `.`.  Thus `$var.foo = 1` won't work as expected (`$var.foo` is
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3001-      not a valid or useful path expression in `.`); use `$var | .foo =
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3019-          Note that the left-hand side of '|=' refers to a value in `.`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml:3020:          Thus `$var.foo |= . + 1` won't work as expected (`$var.foo` is
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3021-          not a valid or useful path expression in `.`); use `$var |
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3168-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:3169:      For example, with `-L$HOME/.jq` a module `foo` can be found in
jq-1.6/docs/content/3.manual/v1.6/manual.yml:3170:      `$HOME/.jq/foo.jq` and `$HOME/.jq/foo/foo.jq`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3171-
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3207-
jq-1.6/docs/content/3.manual/v1.6/manual.yml:3208:      - title: "`import RelativePathString as $NAME [<metadata>];`"
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3209-        body: |
##############################################
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3213-          the relative path string.  The file's data will be available
jq-1.6/docs/content/3.manual/v1.6/manual.yml:3214:          as `$NAME::NAME`.
jq-1.6/docs/content/3.manual/v1.6/manual.yml-3215-
##############################################
jq-1.6/docs/content/3.manual/v1.4/manual.yml-178-        This option passes a value to the jq program as a predefined
jq-1.6/docs/content/3.manual/v1.4/manual.yml:179:        variable. If you run jq with `--arg foo bar`, then `$foo` is
jq-1.6/docs/content/3.manual/v1.4/manual.yml-180-        available in the program and has the value `"bar"`.
##############################################
jq-1.6/docs/content/3.manual/v1.4/manual.yml-185-        value to the jq program as a predefined variable. If you run jq
jq-1.6/docs/content/3.manual/v1.4/manual.yml:186:        with `--argfile foo bar`, then `$foo` is available in the
jq-1.6/docs/content/3.manual/v1.4/manual.yml-187-        program and has the value resulting from parsing the content of
##############################################
jq-1.6/docs/content/3.manual/v1.4/manual.yml-215-          If the key contains special characters, you need to surround
jq-1.6/docs/content/3.manual/v1.4/manual.yml:216:          it with double quotes like this: `."foo$"`.
jq-1.6/docs/content/3.manual/v1.4/manual.yml-217-
##############################################
jq-1.6/docs/content/3.manual/v1.4/manual.yml-608-
jq-1.6/docs/content/3.manual/v1.4/manual.yml:609:          `has($key)` has the same effect as checking whether `$key`
jq-1.6/docs/content/3.manual/v1.4/manual.yml-610-          is a member of the array returned by `keys`, although `has`
##############################################
jq-1.6/docs/content/3.manual/v1.4/manual.yml-1451-          defining variables. Still, sometimes they do make things easier, so jq
jq-1.6/docs/content/3.manual/v1.4/manual.yml:1452:          lets you define variables using `expression as $variable`. All
jq-1.6/docs/content/3.manual/v1.4/manual.yml-1453-          variable names start with `$`. Here's a slightly uglier version of the
##############################################
jq-1.6/docs/content/3.manual/v1.4/manual.yml-1481-
jq-1.6/docs/content/3.manual/v1.4/manual.yml:1482:          The expression `exp as $x | ...` means: for each value of expression
jq-1.6/docs/content/3.manual/v1.4/manual.yml-1483-          `exp`, run the rest of the pipeline with the entire original input, and
jq-1.6/docs/content/3.manual/v1.4/manual.yml:1484:          with `$x` set to that value.  Thus `as` functions as something of a
jq-1.6/docs/content/3.manual/v1.4/manual.yml-1485-          foreach loop.
##############################################
jq-1.6/docs/content/3.manual/v1.4/manual.yml-1546-
jq-1.6/docs/content/3.manual/v1.4/manual.yml:1547:          For each result that `.[]` produces, `. + $item` is run to
jq-1.6/docs/content/3.manual/v1.4/manual.yml-1548-          accumulate a running total, starting from 0. In this
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-214-        This option passes a value to the jq program as a predefined
jq-1.6/docs/content/3.manual/v1.5/manual.yml:215:        variable. If you run jq with `--arg foo bar`, then `$foo` is
jq-1.6/docs/content/3.manual/v1.5/manual.yml-216-        available in the program and has the value `"bar"`. Note that
jq-1.6/docs/content/3.manual/v1.5/manual.yml-217-        `value` will be treated as a string, so `--arg foo 123` will
jq-1.6/docs/content/3.manual/v1.5/manual.yml:218:        bind `$foo` to `"123"`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-219-
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-223-        predefined variable. If you run jq with `--argjson foo 123`, then
jq-1.6/docs/content/3.manual/v1.5/manual.yml:224:        `$foo` is available in the program and has the value `123`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-225-
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-229-        an array of the parsed JSON values to the given global variable.
jq-1.6/docs/content/3.manual/v1.5/manual.yml:230:        If you run jq with `--argfile foo bar`, then `$foo` is available
jq-1.6/docs/content/3.manual/v1.5/manual.yml-231-        in the program and has an array whose elements correspond to the
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-281-          If the key contains special characters, you need to surround
jq-1.6/docs/content/3.manual/v1.5/manual.yml:282:          it with double quotes like this: `."foo$"`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-283-
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-698-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:699:          `has($key)` has the same effect as checking whether `$key`
jq-1.6/docs/content/3.manual/v1.5/manual.yml-700-          is a member of the array returned by `keys`, although `has`
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-852-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:853:      - title: "`$__loc__`"
jq-1.6/docs/content/3.manual/v1.5/manual.yml-854-        body: |
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-856-          Produces an object with a "file" key and a "line" key, with
jq-1.6/docs/content/3.manual/v1.5/manual.yml:857:          the filename and line number where `$__loc__` occurs, as
jq-1.6/docs/content/3.manual/v1.5/manual.yml-858-          values.
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-1928-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:1929:          The `break $label_name` expression will cause the program to
jq-1.6/docs/content/3.manual/v1.5/manual.yml:1930:          to act as though the nearest (to the left) `label $label_name`
jq-1.6/docs/content/3.manual/v1.5/manual.yml-1931-          produced `empty`.
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-1943-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:1944:          because no label `$out` is visible.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-1945-
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2187-          defining variables. Still, sometimes they do make things easier, so jq
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2188:          lets you define variables using `expression as $variable`. All
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2189-          variable names start with `$`. Here's a slightly uglier version of the
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2217-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2218:          The expression `exp as $x | ...` means: for each value of expression
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2219-          `exp`, run the rest of the pipeline with the entire original input, and
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2220:          with `$x` set to that value.  Thus `as` functions as something of a
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2221-          foreach loop.
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2223-          Just as `{foo}` is a handy way of writing `{foo: .foo}`, so
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2224:          `{$foo}` is a handy way of writing `{foo:$foo}`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2225-
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2331-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2332:          For each result that `.[]` produces, `. + $item` is run to
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2333-          accumulate a running total, starting from 0. In this
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2391-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2392:          The form is `foreach EXP as $var (INIT; UPDATE; EXTRACT)`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2393-          Like `reduce`, `INIT` is evaluated once to produce a state
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2394:          value, then each output of `EXP` is bound to `$var`, `UPDATE`
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2395-          is evaluated for each output of `EXP` with the current state
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2396:          and with `$var` visible.  Each value output by `UPDATE`
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2397-          replaces the previous state.  Finally, `EXTRACT` is evaluated
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2656-          Note that the left-hand side of '=' refers to a value in `.`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2657:          Thus `$var.foo = 1` won't work as expected (`$var.foo` is not
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2658-          a valid or useful path expression in `.`); use `$var | .foo =
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2693-          Note that the left-hand side of '|=' refers to a value in `.`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2694:          Thus `$var.foo |= . + 1` won't work as expected (`$var.foo` is
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2695-          not a valid or useful path expression in `.`); use `$var |
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2798-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2799:      For example, with `-L$HOME/.jq` a module `foo` can be found in
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2800:      `$HOME/.jq/foo.jq` and `$HOME/.jq/foo/foo.jq`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2801-
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2837-
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2838:      - title: "`import RelativePathString as $NAME [<metadata>];`"
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2839-        body: |
##############################################
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2843-          the relative path string.  The file's data will be available
jq-1.6/docs/content/3.manual/v1.5/manual.yml:2844:          as `$NAME::NAME`.
jq-1.6/docs/content/3.manual/v1.5/manual.yml-2845-
##############################################
jq-1.6/docs/README.md-14-After that finishes installing, you'll need to make sure RVM is on
jq-1.6/docs/README.md:15:your path by doing `source $HOME/.rvm/scripts/rvm`, or just opening a
jq-1.6/docs/README.md-16-new shell. See <https://rvm.io> for more info on RVM.
##############################################
jq-1.6/NEWS-26-
jq-1.6/NEWS:27:    - destructuring (`. as [$first, $second] | ...`)
jq-1.6/NEWS-28-    - try/catch, generalized `?` operator, and label/break
##############################################
jq-1.6/debian/patches/0009-Hardcode-version-to-1.6.patch-16--set -e
jq-1.6/debian/patches/0009-Hardcode-version-to-1.6.patch:17:-cd `dirname "$0"`
jq-1.6/debian/patches/0009-Hardcode-version-to-1.6.patch-18--if git rev-parse --verify -q jq-1.0 > /dev/null 2>&1; then
##############################################
jq-1.6/.pc/enable-manpages.patch/Makefile.am-95-.FORCE:
jq-1.6/.pc/enable-manpages.patch/Makefile.am:96:generate_ver = ver="`{ $(srcdir)/scripts/version || echo '$(VERSION)' ; } | sed 's/.*/\#define JQ_VERSION \"&\"/'`"
jq-1.6/.pc/enable-manpages.patch/Makefile.am-97-.remake-version-h: .FORCE
##############################################
jq-1.6/.pc/patch-version-into-build.patch/configure.ac-94-        AS_IF([test "x$bundle_cmd" = "x" || \
jq-1.6/.pc/patch-version-into-build.patch/configure.ac:95:        ! bmsg="`cd ${srcdir}/docs; "$bundle_cmd" check 2>/dev/null`"],[
jq-1.6/.pc/patch-version-into-build.patch/configure.ac-96-           AC_MSG_WARN([$bmsg])
##############################################
jq-1.6/.pc/dont-distribute-duplicate-docs.patch/Makefile.am-95-.FORCE:
jq-1.6/.pc/dont-distribute-duplicate-docs.patch/Makefile.am:96:generate_ver = ver="`{ $(srcdir)/scripts/version || echo '$(VERSION)' ; } | sed 's/.*/\#define JQ_VERSION \"&\"/'`"
jq-1.6/.pc/dont-distribute-duplicate-docs.patch/Makefile.am-97-.remake-version-h: .FORCE
##############################################
jq-1.6/.pc/disable-static-libtool.patch/Makefile.am-95-.FORCE:
jq-1.6/.pc/disable-static-libtool.patch/Makefile.am:96:generate_ver = ver="`{ $(srcdir)/scripts/version || echo '$(VERSION)' ; } | sed 's/.*/\#define JQ_VERSION \"&\"/'`"
jq-1.6/.pc/disable-static-libtool.patch/Makefile.am-97-.remake-version-h: .FORCE
##############################################
jq-1.6/.pc/0007-stop-using-libtool-bin.patch/Makefile.am-95-.FORCE:
jq-1.6/.pc/0007-stop-using-libtool-bin.patch/Makefile.am:96:generate_ver = ver="`{ $(srcdir)/scripts/version || echo '$(VERSION)' ; } | sed 's/.*/\#define JQ_VERSION \"&\"/'`"
jq-1.6/.pc/0007-stop-using-libtool-bin.patch/Makefile.am-97-.remake-version-h: .FORCE
##############################################
jq-1.6/.pc/0008-Do-not-use-venderized-oniguruma.patch/Makefile.am-95-.FORCE:
jq-1.6/.pc/0008-Do-not-use-venderized-oniguruma.patch/Makefile.am:96:generate_ver = ver="`{ $(srcdir)/scripts/version || echo '$(VERSION)' ; } | sed 's/.*/\#define JQ_VERSION \"&\"/'`"
jq-1.6/.pc/0008-Do-not-use-venderized-oniguruma.patch/Makefile.am-97-.remake-version-h: .FORCE
##############################################
jq-1.6/.pc/0009-Hardcode-version-to-1.6.patch/scripts/version-2-set -e
jq-1.6/.pc/0009-Hardcode-version-to-1.6.patch/scripts/version:3:cd `dirname "$0"`
jq-1.6/.pc/0009-Hardcode-version-to-1.6.patch/scripts/version-4-if git rev-parse --verify -q jq-1.0 > /dev/null 2>&1; then
##############################################
jq-1.6/configure.ac-91-        AS_IF([test "x$bundle_cmd" = "x" || \
jq-1.6/configure.ac:92:        ! bmsg="`cd ${srcdir}/docs; "$bundle_cmd" check 2>/dev/null`"],[
jq-1.6/configure.ac-93-           AC_MSG_WARN([$bmsg])
##############################################
jq-1.6/Makefile.am-95-.FORCE:
jq-1.6/Makefile.am:96:generate_ver = ver="`{ $(srcdir)/scripts/version || echo '$(VERSION)' ; } | sed 's/.*/\#define JQ_VERSION \"&\"/'`"
jq-1.6/Makefile.am-97-.remake-version-h: .FORCE