NAWK(1) | User Commands | NAWK(1) |
nawk - pattern scanning and processing language
nawk [-f progfile | 'prog']
[-Ffieldsep] [-v var=value] [file . . .]
Nawk scans each input file for lines that match any of a set of patterns specified literally in prog or in one or more files specified as -f progfile. With each pattern there can be an associated action that will be performed when a line of a file matches the pattern. Each line is matched against the pattern portion of every pattern-action statement; the associated action is performed for each matched pattern. The file name - means the standard input. Any file of the form var=value is treated as an assignment, not a filename, and is executed at the time it would have been opened if it were a filename (/usr/5bin/s42/awk, /usr/5bin/posix/awk, and /usr/5bin/posix2001/awk only). The option -v followed by var=value is an assignment to be done before prog is executed; any number of -v options may be present. The -F fs option defines the input field separator to be the regular expression fs.
An input line is normally made up of fields separated by white space, or by regular expression FS. The fields are denoted $1, $2, ..., while $0 refers to the entire line.
A pattern-action statement has the form
A missing { action } means print the line; a missing pattern always matches. Pattern-action statements are separated by newlines or semicolons.
An action is a sequence of statements. A statement can be one of the following:
if ( expression ) statement [ else statement ] while ( expression ) statement for ( expression ; expression ; expression ) statement for ( var in array ) statement do statement while ( expression ) break continue { [statement ...] } expression # commonly var = expression print [expression-list] [> expression] printf format [, expression-list] [> expression] next # skip remaining patterns on this input line delete array[subscript] # delete an array element exit [expr] # exit immediately; status is expr return [expr]
Statements are terminated by semicolons, newlines or right braces. An empty expression-list stands for $0. String constants are quoted " ", with the usual C escapes recognized within. Expressions take on string or numeric values as appropriate, and are built using the operators + - * / % ^ (exponentiation), and concatenation (indicated by white space). The operators ! ++ -- += -= *= /= %= ^= > >= < <= == != ?: are also available in expressions. Variables may be scalars, array elements (denoted x[i]) or fields. Variables are initialized to the null string. Array subscripts may be any string, not necessarily numeric; this allows for a form of associative memory. Multiple subscripts such as [i,j,k] are permitted; the constituents are concatenated, separated by the value of SUBSEP.
The print statement prints its arguments on the standard output (or on a file if >file or >>file is present or on a pipe if |cmd is present), separated by the current output field separator, and terminated by the output record separator. file and cmd may be literal names or parenthesized expressions; identical string values in different statements denote the same open file. The printf statement formats its expression list according to the format (see printf(3)). The built-in function close(expr) closes the file or pipe expr.
The mathematical functions exp, log, sqrt, sin, cos, and atan2 are built in. Other built-in functions:
The ``function'' getline sets $0 to the next input record from the current input file; getline <file sets $0 to the next record from file. getline x sets variable x instead. Finally, cmd |getline pipes the output of cmd into getline; each call of getline returns the next line of output from cmd. In all cases, getline returns 1 for a successful input, 0 for end of file, and -1 for an error.
Additional functions may be defined (at the position of a pattern-action statement) thus:
or:
Parameters are passed by value if scalar and by reference if array name; functions may be called recursively. Parameters are local to the function; all other variables are global. Thus local variables may be created by providing excess parameters in the function definition.
Patterns are arbitrary Boolean combinations (with ! || &&) of regular expressions and relational expressions. Regular expressions are full regular expressions with /usr/5bin/nawk and extended regular expressions with /usr/5bin/s42/awk, /usr/5bin/posix/awk, and /usr/5bin/posix2001/awk; both are as described in egrep(1). Isolated regular expressions in a pattern apply to the entire line. Regular expressions may also occur in relational expressions, using the operators ~ and !~. /re/ is a constant regular expression; any string (constant or variable) may be used as a regular expression, except in the position of an isolated regular expression in a pattern. For /usr/5bin/posix2001/awk, regular expressions may be part of arithmetic expressions.
A pattern may consist of two patterns separated by a comma; in this case, the action is performed for all lines from an occurrence of the first pattern though an occurrence of the second.
A relational expression is one of the following:
where a relop is any of the six relational operators in C, and a matchop is either ~ (matches) or !~ (does not match). A conditional is an arithmetic expression, a relational expression, or a Boolean combination of these.
The special patterns BEGIN and END may be used to capture control before the first input line is read and after the last. BEGIN and END do not combine with other patterns.
Variable names with special meanings:
Print lines longer than 72 characters.
Print first two fields in opposite order.
BEGIN { FS = ",[ \t]*|[ \t]+" }
{ print $2, $1 }
{ s += $1 } END { print "sum is", s, " average is", s/NR }
Print all lines between start/stop pairs.
BEGIN { # Simulate echo(1) for (i = 1; i < ARGC; i++) printf "%s ", ARGV[i] printf "\n" exit }
egrep(1), lex(1), oawk(1), sed(1), printf(3), locale(7)
A. V. Aho, B. W. Kernighan, P. J. Weinberger, The AWK Programming
Language, Addison-Wesley, 1988. ISBN 0-201-07981-X
There are no explicit conversions between numbers and strings. To force an expression to be treated as a number add 0 to it; to force it to be treated as a string concatenate "" to it.
The LC_COLLATE variable has currently no effect in regular expressions. Ranges in bracket expressions are ordered as byte values in single-byte locales and as wide character values in multibyte locales; equivalence classes match the given character only, and multi-character collating elements are not available.
2/6/05 | Heirloom Toolchest |