=========================================================== .___ __ __ _________________ __ __ __| _/|__|/ |_ / ___\_` __ \__ \ | | \/ __ | | \\_ __\ / /_/ > | \// __ \| | / /_/ | | || | \___ /|__| (____ /____/\____ | |__||__| /_____/ \/ \/ grep rough audit - static analysis tool v2.8 written by @Wireghoul =================================[justanotherhacker.com]=== lua-penlight-1.3.2/doc/manual/03-strings.md-59-'$ variables' can optionally have curly braces; this form is useful if you are lua-penlight-1.3.2/doc/manual/03-strings.md:60:glueing text together to make variables, e.g `${prefix}_name_${postfix}`. The lua-penlight-1.3.2/doc/manual/03-strings.md-61-`substitute` method will throw an error if a $ variable is not found in the ############################################## lua-penlight-1.3.2/doc/manual/03-strings.md-95-`indent_substitute` can substitute templates, and in which case they themselves lua-penlight-1.3.2/doc/manual/03-strings.md:96:will be substituted using the given table. So in this case, `$t` was substituted lua-penlight-1.3.2/doc/manual/03-strings.md-97-twice. ############################################## lua-penlight-1.3.2/doc/manual/03-strings.md-129- - Lines begining with `#` are Lua lua-penlight-1.3.2/doc/manual/03-strings.md:130: - Otherwise, anything inside `$()` is a Lua expression. lua-penlight-1.3.2/doc/manual/03-strings.md-131- ############################################## lua-penlight-1.3.2/doc/manual/03-strings.md-157-usually '#' but it's sometimes necessary to redefine these if the defaults lua-penlight-1.3.2/doc/manual/03-strings.md:158:interfere with the target language - for instance, `$(V)` has another meaning in lua-penlight-1.3.2/doc/manual/03-strings.md-159-Make, and `#` means a preprocessor line in C/C++. ############################################## lua-penlight-1.3.2/doc/manual/06-data.md-1160-However, xml matches can shape the structure of the output. By replacing the `day_of_week` lua-penlight-1.3.2/doc/manual/06-data.md:1161:line of the template with `<day_of_week data='$_'/>` we get the same effect; `$_` is lua-penlight-1.3.2/doc/manual/06-data.md-1162-a special symbol that means that this captured value (or simply _capture_) becomes the key. lua-penlight-1.3.2/doc/manual/06-data.md-1163- lua-penlight-1.3.2/doc/manual/06-data.md:1164:Note that `$NUMBER` means a numerical index, so lua-penlight-1.3.2/doc/manual/06-data.md:1165:that `$1` is the first element of the resulting array, and so forth. You can mix lua-penlight-1.3.2/doc/manual/06-data.md-1166-numbered and named captures, but it's strongly advised to make the numbered captures lua-penlight-1.3.2/doc/manual/06-data.md:1167:form a proper array sequence (everything from `1` to `n` inclusive). `$0` has a lua-penlight-1.3.2/doc/manual/06-data.md-1168-special meaning; if it is the only capture (`{[0]='foo'}`) then the table is ############################################## lua-penlight-1.3.2/doc/manual/06-data.md-1220-You will then get `{{alpha='1.3'},...}`. The most convenient format would be lua-penlight-1.3.2/doc/manual/06-data.md:1221:returned by this (note that `_-` behaves just like `$_`): lua-penlight-1.3.2/doc/manual/06-data.md-1222- ############################################## lua-penlight-1.3.2/doc/manual/08-additional.md-119- lua-penlight-1.3.2/doc/manual/08-additional.md:120:SIP captures (like `$v{mon}`) do not have to be named. You can use just `$v`, but lua-penlight-1.3.2/doc/manual/08-additional.md-121-you have to be consistent; if a pattern contains unnamed captures, then all ############################################## lua-penlight-1.3.2/lua/pl/template.lua-6--- * lines starting with # are Lua lua-penlight-1.3.2/lua/pl/template.lua:7:-- * otherwise, `$(expr)` is the result of evaluating `expr` lua-penlight-1.3.2/lua/pl/template.lua-8---