BEGINFILE and ENDFILE Special Patterns ¶This section describes a gawk-specific feature.
Two special kinds of rule, BEGINFILE and ENDFILE, give
you “hooks” into gawk’s command-line file processing loop.
As with the BEGIN and END rules
(see The BEGIN and END Special Patterns),
BEGINFILE and ENDFILE rules in a program execute in the order they are
read by gawk.
The bodies of the BEGINFILE rules execute just before
gawk reads the first record from a file. FILENAME
is set to the name of the current file, and FNR is set to zero.
Before executing a BEGINFILE rule, gawk clears
$0 and the fields, since no record has been
read yet from the file that is about to be processed.
The BEGINFILE rule provides you the opportunity to accomplish two tasks
that would otherwise be difficult or impossible to perform:
You do this by checking if the ERRNO variable is not the empty
string; if so, then gawk was not able to open the file.
This makes it possible to catch and process I/O errors at the
level of the awk program.
In this case, your program can execute the nextfile statement
(see The nextfile Statement). This causes gawk to skip
the file entirely. Otherwise, gawk exits with the usual
fatal error.
gawk has started processing the file.
(This is a very advanced feature, currently used only by the
gawkextlib project.)
The ENDFILE rule is called when gawk has finished processing
the last record in an input file. For the last input file,
it will be called before any END rules.
The ENDFILE rule is executed even for empty input files.
The next statement (see The next Statement) is not allowed inside
either a BEGINFILE or an ENDFILE rule. The nextfile
statement is allowed only inside a
BEGINFILE rule, not inside an ENDFILE rule.
The getline function (see Explicit Input with getline) is restricted inside
both BEGINFILE and ENDFILE: only redirected
forms of getline are allowed.
BEGINFILE and ENDFILE are gawk extensions.
In most other awk implementations, or if gawk is in
compatibility mode (see Command-Line Options), they are not special.