===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
ninja-build-1.10.1/doc/manual.asciidoc-354-
ninja-build-1.10.1/doc/manual.asciidoc:355:Variables can also be referenced using curly braces like `${in}`.
ninja-build-1.10.1/doc/manual.asciidoc-356-
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-369-command to run.  In the context of a rule, the `command` variable
ninja-build-1.10.1/doc/manual.asciidoc:370:defines the command to run, `$in` expands to the list of
ninja-build-1.10.1/doc/manual.asciidoc:371:input files (`foo.c`), and `$out` to the output files (`foo.o`) for the
ninja-build-1.10.1/doc/manual.asciidoc-372-command.  A full list of special variables is provided in
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-388-In the scope of a `build` block (including in the evaluation of its
ninja-build-1.10.1/doc/manual.asciidoc:389:associated `rule`), the variable `$in` is the list of inputs and the
ninja-build-1.10.1/doc/manual.asciidoc:390:variable `$out` is the list of outputs.
ninja-build-1.10.1/doc/manual.asciidoc-391-
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-717-Implicit outputs _(available since Ninja 1.7)_ may be added before
ninja-build-1.10.1/doc/manual.asciidoc:718:the `:` with +| _output1_ _output2_+ and do not appear in `$out`.
ninja-build-1.10.1/doc/manual.asciidoc-719-(See <<ref_outputs,the reference on output types>>.)
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-753-
ninja-build-1.10.1/doc/manual.asciidoc:754:`${varname}`:: alternate syntax for `$varname`.
ninja-build-1.10.1/doc/manual.asciidoc-755-
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-758-
ninja-build-1.10.1/doc/manual.asciidoc:759:`$:` :: a colon.  (This is only necessary in `build` lines, where a colon
ninja-build-1.10.1/doc/manual.asciidoc-760-would otherwise terminate the list of outputs.)
ninja-build-1.10.1/doc/manual.asciidoc-761-
ninja-build-1.10.1/doc/manual.asciidoc:762:`$$`:: a literal `$`.
ninja-build-1.10.1/doc/manual.asciidoc-763-
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-848-`in`:: the space-separated list of files provided as inputs to the build line
ninja-build-1.10.1/doc/manual.asciidoc:849:  referencing this `rule`, shell-quoted if it appears in commands.  (`$in` is
ninja-build-1.10.1/doc/manual.asciidoc-850-  provided solely for convenience; if you need some subset or variant of this
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-853-
ninja-build-1.10.1/doc/manual.asciidoc:854:`in_newline`:: the same as `$in` except that multiple inputs are
ninja-build-1.10.1/doc/manual.asciidoc-855-  separated by newlines rather than spaces.  (For use with
ninja-build-1.10.1/doc/manual.asciidoc:856:  `$rspfile_content`; this works around a bug in the MSVC linker where
ninja-build-1.10.1/doc/manual.asciidoc-857-  it uses a fixed-size buffer for processing input.)
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-916-1. _Explicit outputs_, as listed in a build line.  These are
ninja-build-1.10.1/doc/manual.asciidoc:917:   available as the `$out` variable in the rule.
ninja-build-1.10.1/doc/manual.asciidoc-918-+
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-925-  the only difference is that implicit outputs don't show up in the
ninja-build-1.10.1/doc/manual.asciidoc:926:  `$out` variable.
ninja-build-1.10.1/doc/manual.asciidoc-927-+
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-937-1. _Explicit dependencies_, as listed in a build line.  These are
ninja-build-1.10.1/doc/manual.asciidoc:938:   available as the `$in` variable in the rule.  Changes in these files
ninja-build-1.10.1/doc/manual.asciidoc-939-   cause the output to be rebuilt; if these files are missing and
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-948-   explicit dependencies, the only difference is that implicit dependencies
ninja-build-1.10.1/doc/manual.asciidoc:949:   don't show up in the `$in` variable.
ninja-build-1.10.1/doc/manual.asciidoc-950-+
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-980-expanded immediately (according to the below scoping rules), and
ninja-build-1.10.1/doc/manual.asciidoc:981:from then on `$name` expands to the static string as the result of the
ninja-build-1.10.1/doc/manual.asciidoc-982-expansion.  It is never the case that you'll need to "double-escape" a
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-1018-
ninja-build-1.10.1/doc/manual.asciidoc:1019:1. Special built-in variables (`$in`, `$out`).
ninja-build-1.10.1/doc/manual.asciidoc-1020-
##############################################
ninja-build-1.10.1/doc/manual.asciidoc-1022-
ninja-build-1.10.1/doc/manual.asciidoc:1023:3. Rule-level variables from the `rule` block (i.e. `$command`).
ninja-build-1.10.1/doc/manual.asciidoc-1024-   (Note from the above discussion on expansion that these are
ninja-build-1.10.1/doc/manual.asciidoc:1025:   expanded "late", and may make use of in-scope bindings like `$in`.)
ninja-build-1.10.1/doc/manual.asciidoc-1026-
##############################################
ninja-build-1.10.1/misc/bash-completion-52-	targets_command="eval ninja -C \"${dir}\" -t targets all 2>/dev/null | cut -d: -f1"
ninja-build-1.10.1/misc/bash-completion:53:	COMPREPLY=($(compgen -W '`${targets_command}`' -- "$cur"))
ninja-build-1.10.1/misc/bash-completion-54-    fi
##############################################
ninja-build-1.10.1/src/ninja.cc-922-" 13 ,3;2!2;\n8 ,;<11!;\n5 `'<10!(2`'2!\n11 ,6;, `\\. `\\9 .,c13$ec,.\n6 "
ninja-build-1.10.1/src/ninja.cc:923:",2;11!>; `. ,;!2> .e8$2\".2 \"?7$e.\n <:<8!'` 2.3,.2` ,3!' ;,(?7\";2!2'<"
ninja-build-1.10.1/src/ninja.cc:924:"; `?6$PF ,;,\n2 `'4!8;<!3'`2 3! ;,`'2`2'3!;4!`2.`!;2 3,2 .<!2'`).\n5 3`5"
ninja-build-1.10.1/src/ninja.cc:925:"'2`9 `!2 `4!><3;5! J2$b,`!>;2!:2!`,d?b`!>\n26 `'-;,(<9!> $F3 )3.:!.2 d\""
ninja-build-1.10.1/src/ninja.cc-926-"2 ) !>\n30 7`2'<3!- \"=-='5 .2 `2-=\",!>\n25 .ze9$er2 .,cd16$bc.'\n22 .e"
ninja-build-1.10.1/src/ninja.cc:927:"14$,26$.\n21 z45$c .\n20 J50$c\n20 14$P\"`?34$b\n20 14$ dbc `2\"?22$?7$c"
ninja-build-1.10.1/src/ninja.cc-928-"\n20 ?18$c.6 4\"8?4\" c8$P\n9 .2,.8 \"20$c.3 ._14 J9$\n .2,2c9$bec,.2 `?"
ninja-build-1.10.1/src/ninja.cc:929:"21$c.3`4%,3%,3 c8$P\"\n22$c2 2\"?21$bc2,.2` .2,c7$P2\",cb\n23$b bc,.2\"2"
ninja-build-1.10.1/src/ninja.cc-930-"?14$2F2\"5?2\",J5$P\" ,zd3$\n24$ ?$3?%3 `2\"2?12$bcucd3$P3\"2 2=7$\n23$P"