Merge remote-tracking branch 'origin/master' into cmake

author: Juergen Kahrs <Juergen.Kahrs@googlemail.com> 2014-06-24 13:18:33 +0200
committer: Juergen Kahrs <Juergen.Kahrs@googlemail.com> 2014-06-24 13:18:33 +0200
commit: f1245d04a9f076773c60499b468f44ed9c91b59b (patch)
tree: 2b49234400150bfaac7ebf8c017562300edc7471
parent: ee9707cc44eea3ca64cb71666ac3e8ed26a3bb7f (diff)
parent: 78ded8ee8f11a321c96417e7d02dac2f5723a221 (diff)
download: egawk-f1245d04a9f076773c60499b468f44ed9c91b59b.tar.gz
egawk-f1245d04a9f076773c60499b468f44ed9c91b59b.tar.bz2
egawk-f1245d04a9f076773c60499b468f44ed9c91b59b.zip
228 files changed, 43376 insertions, 26691 deletions
diff --git a/.gitignore b/.gitignore
index 1d665c4d..72445191 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,16 +5,14 @@
 # Directories
 autom4te.cache
 .deps
+*.dSYM
 
 # Single files.
 Makefile
 config.h
 config.log
 config.status
-dgawk
 gawk
-pgawk
 stamp-h1
-libtool
 
 test/fmtspcl.ok
diff --git a/ChangeLog b/ChangeLog
index 6058eefa..14202f52 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,375 @@
+2014-06-22         Paul Eggert          <eggert@penguin.cs.ucla.edu>
+
+	Bring in from GNULIB:
+
+	regex: fix memory leak in compiler
+	Fix by Andreas Schwab in:
+	https://sourceware.org/ml/libc-alpha/2014-06/msg00462.html
+	* lib/regcomp.c (parse_expression): Deallocate partially
+	constructed tree before returning error.
+
+2014-06-19         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* builtin.c (do_sub): Add more info to leading comment.
+	Add some whitespace in the code.
+
+2014-06-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c: Sync with GNU grep.
+
+2014-06-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c (mbs_to_wchar): Define a macro if not MBS.
+
+2014-05-29         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c: Sync with GNU grep.
+
+2014-05-26         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* io.c (inetfile): Change return type to bool.  Wrap code
+	with ifdef HAVE_SOCKETS so that it'll compile on DJGPP.
+
+2014-05-22         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	Allow any redirected getline inside BEGINFILE/ENDFILE.
+
+	* awkgram.y (LEX_GETLINE): Only require a redirection and not also
+	a variable if getline is in a BEGINFILE or ENDFILE rule.
+	* interpret.h (Op_K_getline_redir): Remove check and fatal error.
+
+2014-05-20         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c (dfaexec): Minor sync with GNU grep.
+
+2014-05-14         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* custom.h (_GL_PURE): Move definition to here. Sigh.
+	* dfa.h, dfa.c: Sync with GNU grep. Sigh.
+
+	Unrelated:
+
+	* custom.h: Remove stuff for Ultrix 4.3. No one has such
+	systems anymore; this just got missed earlier.
+
+2014-05-11         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* debug.c (do_eval): Repair fix of 2014-05-09 and use
+	assoc_remove to take @eval out of the function table.
+	* symbol.c: Fix a comment.  This file needs some work.
+
+2014-05-10         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* io.c (get_a_record): Finish TERMNEAREND handling in case
+	we don't have a regular file but aren't going to get more data.
+	Added some additional comments.
+
+2014-05-09         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* debug.c (do_eval): Don't free `f' which points into the context
+	that was previously freed. Bug reported by Jan Chaloupka
+	<jchaloup@redhat.com>.  Apparently introduced with move to
+	SYMTAB and FUNCTAB, but only showed up on Fedora 20 and Ubuntu 14.04,
+	which have a newer glibc.
+	(do_eval): Fix a memory leak seen by valgrind on Fedora 20 and
+	Ubuntu 14.04: the new SRCFILE that is added wasn't released.
+
+	Unrelated:
+
+	* io.c (get_a_record): Handle return of TERMNEAREND when the
+	entire file has been read into the buffer and we're using a
+	regex for RS. Bug report by Grail Dane <grail69@hotmail.com>.
+
+2014-05-04         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* debug.c (debug_prog): Change check for GAWK_RESTART so that it
+	actually works. Bug fix: run command in debugger would start
+	over again but not actually start running the program.
+
+2014-04-25         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* io.c (two_way_open): In forked child, reset SIGPIPE to SIG_DFL.
+	Fixes problems with "broken pipe" errors from child processes,
+	restoring 4.1.0 and earlier behavior. Thanks to Daryl F
+	<wyatt@prairieturtle.ca> for the report.
+	(gawk_popen): Ditto.
+
+2014-04-25         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.h, dfa.c: Merge with GNU grep; lots of forward motion.
+
+2014-04-24         Arnold D. Robbins     <arnold@skeeve.com>
+
+	Update xalloc.h for pending merge with dfa.
+
+	* xalloc.h (xstrdup): Implement this.
+	(x2nrealloc): Incorporate changed logic from GNULIB.
+
+2014-04-20         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* io.c (struct inet_socket_info): Define new structure
+	for use in parsing special socket filenames.
+	(inetfile): Parse all components of the special socket filename
+	into the struct inet_socket_info.  Returns true only if it is a
+	valid socket fliename, unlike the previous version which checked
+	for the '/inet[46]?/' prefix only.
+	(redirect): Patch to use updated inetfile() function.
+	(devopen): Remove logic to parse socket filenames, since this has
+	been moved into the inetfile() function.
+	(two_way_open): Update args to inetfile().
+
+2014-04-20         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* builtin.c (do_rand): Make calls to random() in predictable
+	order to avoid order of evaluation differences amongst compilers.
+	Thanks to Anders Magnusson <ragge@ludd.ltu.se> (of the PCC team)
+	for the suggestion.
+
+2014-04-18         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac: Change adding of -export-dynamic for GCC to be
+	-Wl,-export-dynamic, which then works for PCC also.
+
+2014-04-11         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* io.c (closemabyesocket): Define if not defined, e.g. building
+	without socket code. Thanks to dave.gma@googlemail.com (Dave Sines)
+	for the report.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* README: Update.
+	* configure.ac: Bump version.
+
+2014-04-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* regcomp.c (parse_bracket_exp): Move a call to `re_free' inside
+	an ifdef. Makes the code marginally cleaner.
+
+2014-03-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c: Sync with GNU grep.
+
+2014-03-28         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac: Remove duplicate AC_HEADER_TIME and rearrange
+	order of macros some. May help on older systems.
+
+2014-03-23         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c: Move include of dfa.h around for correct building
+	on Irix. Thanks to Nelson H.F. Beebe for the report.
+
+	Unrelated:
+
+	* .gitignore: Simplify .dSYM pattern for Mac OS X.
+
+2014-03-21         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c (using_simple_locale): Add ifdefs in case there is no
+	locale support at all. Thanks to Scott Deifik for the report.
+
+	Unrelated:
+
+	* main.c (UPDATE_YEAR): Set to 2014.
+
+2014-03-17         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* .gitignore: Add .dSYM directories for Mac OS X.
+	Thanks to Hermann Peifer for the suggestion.
+
+2014-03-10         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.h, dfa.c: Sync with grep. Yet again.
+	* regex_internal.c (built_wcs_upper_buffer, build_upper_buffer):
+	Fixes from GNULIB for mixed case matching on Mac OS X.
+
+	Unrelated:
+
+	* builtin.c (format_tree): Smarten handling of %' flag. Always
+	pass it in for floating point formats. Then only add the
+	thousands_sep if there is one. Also, allow for thousands_sep
+	to be a string, not just one character.  Thanks to Michal Jaegermann
+	for the report.
+
+2014-03-08         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* gawkapi.c (api_impl): Add memory allocation function pointers.
+	* gawkapi.h (GAWK_API_MINOR_VERSION): Bump.
+	(gawk_api_t): Add memory allocation function pointers api_malloc,
+	api_calloc, api_realloc, and api_free.
+	(gawk_malloc, gawk_calloc, gawk_realloc, gawk_free): New macros.
+	(emalloc): Replace malloc with gawk_malloc.
+	(erealloc): Replace erealloc with gawk_erealloc.
+
+2014-03-05         Arnold D. Robbins     <arnold@skeeve.com>
+
+	Straighten out enumerated types some more.
+
+	* awk.h (add_srcfile): Fix type of first parameter.
+	* awkgram.y (add_srcfile, do_add_srcfile): Ditto.
+	* cmd.h (A_NONE): New enum nametypeval.
+	* command.y (argtab): Use it in final value.
+	* ext.c (make_builtin): Use awk_false, awk_true.
+	* io.c (init_output_wrapper): Use awk_false.
+
+	Unrelated:
+
+	* debug.c (do_commands): Initialize num to silence warnings.
+	Thanks to Michal Jaegermann.
+
+	Unrelated:
+
+	* builtin.c (do_mktime): Change lint warning for minutes to
+	check against 59, not 60.  Thanks to Hermann Peifer for the report.
+
+2014-03-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c: Sync with grep. Yet again.
+
+2014-02-28         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c: Sync with grep. Looks like good improvement with
+	respect to bracket expressions.
+
+2014-02-27         Arnold D. Robbins     <arnold@skeeve.com>
+
+	Fixes for enum/int mismatches as warned by some compilers.
+
+	* awk.h (ANONE): New enum for array sorting.
+	* array.c (assoc_list): Use it.
+	* builtin.c (format_tree): New MP_NONE value.
+	* gawkapi.c: Use awk_false and awk_true everywhere instead of
+	false and true.
+
+2014-02-26         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac: Set up do-nothing extension/Makefile on
+	MirBSD also.
+
+2014-02-21         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.h, dfa.c (parse_bracket_exp): Sync with grep.
+
+2014-02-20         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* regex.h, regex.c, regex_internal.c, regex_internal.h: Sync
+	with GLIBC. Mainly copyright updates.
+	* getopt.c, getopt.h, getopt1.c, getopt_int.h: Ditto.
+	* dfa.c (parse_bracket_exp): Sync with grep, where they restored
+	the buggy code.  Sigh.
+
+	Unrelated:
+
+	* NEWS: Typo fix.
+	* interpret.h (r_interpret): Init a variable for BEGINFILE to avoid
+	compiler warnings. Thanks to Michal Jaegermann.
+
+2014-02-15         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* awkgram.c, command.c: Regenerated - Bison 3.0.2.
+
+2014-02-04         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c (to_uchar): Make use of this. Syncs with GNU grep.
+
+2014-02-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* awkgram.y (negate_num): Bracket `tval' in #ifdef MPFR since it's
+	only used in that code.
+
+2014-01-31         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (dist-hook): Improve creation of pc/config.h. We
+	have to jump through a lot of hoops for 'make distcheck' to
+	actually work.
+
+2014-01-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (dist-hook): Improve creation of pc/config.h to copy
+	the new file into the distribution directory being created.
+	Also, put the temporary files into /tmp.
+
+2014-01-28         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* awkgram.y (negate_num): If just a double, return. Fixes a bug
+	that showed up on 32-bit systems with MPFR. Thanks to Eli Zaretskii
+	and Corinna Vinschen for the report.  Also, free the MPZ integer.
+	Thanks to valgrind for the report.
+
+	Unrelated:
+
+	* dfa.c: Sync with GNU grep - removed some special cased code
+	for grep.
+
+2014-01-24         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac, field.c: Update copyright year.
+
+2014-01-19         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* awkgram.y (negate_num): Handle the case of -0 for MPFR; the sign
+	was getting lost. Thanks to Hermann Peifer for the report.
+
+2014-01-18         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dfa.c (parse_bracket_exp): Sync with GNU grep, which now uses
+	gawk's code for RRI in single-byte locales!  Hurray.
+
+2014-01-16         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac: For z/OS, restore creation of do-nothing
+	Makefile in extension directory.
+
+2014-01-14         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* field.c (do_split): Make sure split() gets FS value if no
+	third arg even after FPAT was set. Thanks to Janis Papanagnou
+	for the report.
+
+2014-01-13         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* README: Fix John Malmberg's email address.
+
+2014-01-12         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* awkgram.y:  Update copyright year.
+	(func_use): Simplify code.
+	* command.y:  Update copyright year.
+	* ext.c:  Update copyright year.
+	(make_builtin): Small simplification.
+	(make_old_builtin): Make code consistent with make_builtin(), add
+	call to track_ext_func().
+	* bootstrap.sh: Update copyright year. Remove touch of version.c
+	since that file is no longer autogenerated.
+
+2014-01-07         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* command.y (next_word): Move into ifdef for HAVE_LIBREADLINE,
+	since it's only used by that code.
+	* ext.c (load_old_ext): Minor improvements.
+
+2014-01-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* config.guess, config.rpath, config.sub, depcomp,
+	install-sh: Updated.
+	* dfa.h, dfa.c: Sync with GNU grep; comment fix and copyright year.
+	* NEWS: Updated some, including copyright year.
+
+2013-12-26         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* README: Add John Malmberg for VMS.
+
+2013-12-24         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* getopt.h: Add `defined(__sun)' to list of system that do get to
+	include stdlib.h.  Needed for Illumos. Thanks to
+	Richard Palo <richard.palo@free.fr> for the report.
+
 2013-12-21         Mike Frysinger        <vapier@gentoo.org>
 
 	* configure.ac: Add --disable-extensions flag to control
@@ -22,6 +394,11 @@
 	systems.
 	* awk.h (HAVE_VPRINTF): Remove check.
 
+2013-12-12         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* io.c (redirect): Add additional VMS error codes.
+	(nextfile): Retry open after closing some files.
+
 2013-12-10         Scott Deifik          <scottd.mail@sbcglobal.net>
 
 	* io.c (closemaybesocket): Add definition for DJGPP.
diff --git a/Checklist b/Checklist
index 98faf6cb..e0e1ffec 100644
--- a/Checklist
+++ b/Checklist
@@ -1,4 +1,4 @@
-Sun Apr 21 23:14:21 IDT 2013
+Fri Apr  4 11:43:29 IDT 2014
 ============================
 
 A checklist for making releases
@@ -12,20 +12,18 @@ README_d/* edited
 VMS/* version stuff up to date
 	vms/vmsbuild.com
 	vms/descrip.mms
-	vms/vms-conf.h: update VERSION and PACKAGE_VERSION
 NEWS is up to date
 Any new options have been added to usage function
 All paper work signed and sent in
 All files checked in
 Version information is correct in
-	version.c
 	doc/gawk.1
 	doc/awkcard.in
-	doc/gawk.texi
+	doc/gawktexi.in
 	doc/gawkinet.texi
 	extension/configure.ac
 doc/texinfo.tex is up to date
-doc/gawk.texi is up to date
+doc/gawktexi.in is up to date
 doc/gawkinet.texi is up to date
 doc/gawk.1 is up to date
 doc/awkcard.in is up to date
@@ -43,6 +41,8 @@ Testing on
 	compile with tcc
 	compile with clang
 
+	compile 32 bit tests - clang and gcc
+
 	configure --disable-lint
 	configure --disable-nls
 	configure --with-whiny-user-strftime
diff --git a/Makefile.am b/Makefile.am
index efb3711f..6e5715d7 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -1,7 +1,7 @@
 #
 # Makefile.am --- automake input file for gawk
 #
-# Copyright (C) 2000-2013 the Free Software Foundation, Inc.
+# Copyright (C) 2000-2014 the Free Software Foundation, Inc.
 #
 # This file is part of GAWK, the GNU implementation of the
 # AWK Programming Language.
@@ -172,10 +172,14 @@ check-local: gawk$(EXEEXT)
 dist-hook:
 	cd $(distdir)/extension ; rm -f *.o *.so
 	cd $(srcdir)/pc ; \
-	sed -n -f configpk.sed < ../configure.ac > tmp.sed ; \
-	sed -f config.sed < ../configh.in > config.tmp ; \
-	sed -f tmp.sed < config.tmp > config.h ; \
-	$(RM) tmp.sed config.tmp
+	chmod u+w config.h ; \
+	sed -n -f configpk.sed < ../configure.ac > /tmp/tmp.sed ; \
+	sed -f config.sed < ../configh.in > /tmp/config.tmp ; \
+	sed -f /tmp/tmp.sed < /tmp/config.tmp > config.h ; \
+	$(RM) /tmp/tmp.sed /tmp/config.tmp
+	pwd
+	chmod u+w $(distdir)/pc/config.h
+	cp $(srcdir)/pc/config.h $(distdir)/pc/config.h
 
 # Special rules for individual files
 # Use of awk instead of $(AWK) is deliberate, in case gawk doesn't build
diff --git a/Makefile.in b/Makefile.in
index 25ee0da5..2abf5b46 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -17,7 +17,7 @@
 #
 # Makefile.am --- automake input file for gawk
 #
-# Copyright (C) 2000-2013 the Free Software Foundation, Inc.
+# Copyright (C) 2000-2014 the Free Software Foundation, Inc.
 #
 # This file is part of GAWK, the GNU implementation of the
 # AWK Programming Language.
@@ -1171,10 +1171,14 @@ check-local: gawk$(EXEEXT)
 dist-hook:
 	cd $(distdir)/extension ; rm -f *.o *.so
 	cd $(srcdir)/pc ; \
-	sed -n -f configpk.sed < ../configure.ac > tmp.sed ; \
-	sed -f config.sed < ../configh.in > config.tmp ; \
-	sed -f tmp.sed < config.tmp > config.h ; \
-	$(RM) tmp.sed config.tmp
+	chmod u+w config.h ; \
+	sed -n -f configpk.sed < ../configure.ac > /tmp/tmp.sed ; \
+	sed -f config.sed < ../configh.in > /tmp/config.tmp ; \
+	sed -f /tmp/tmp.sed < /tmp/config.tmp > config.h ; \
+	$(RM) /tmp/tmp.sed /tmp/config.tmp
+	pwd
+	chmod u+w $(distdir)/pc/config.h
+	cp $(srcdir)/pc/config.h $(distdir)/pc/config.h
 
 # Special rules for individual files
 # Use of awk instead of $(AWK) is deliberate, in case gawk doesn't build
diff --git a/NEWS b/NEWS
index d444526e..8984e856 100644
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,10 @@
-   Copyright (C) 2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+   Copyright (C) 2010, 2011, 2012, 2013, 2014 Free Software Foundation, Inc.
    
    Copying and distribution of this file, with or without modification,
    are permitted in any medium without royalty provided the copyright
    notice and this notice are preserved.
 
-Changes from 4.1.1 to 4.2.0
+Changes from 4.1.x to 4.2.0
 ---------------------------
 
 1. If not in POSIX mode, changes to ENVIRON are reflected into
@@ -16,13 +16,23 @@ Changes from 4.1.1 to 4.2.0
    get the same series of numbers each time you call rand() repeatedly,
    but this will be a different series than previously.
 
+Changes from 4.1.1 to 4.1.2
+---------------------------
+
+1. The manual has been considerably improved.
+	- Thoroughly reviewed and updated.
+	- Out-of-date examples replaced.
+	- Chapter 15 on MPFR reworked.
+	- Summary sections added to all chapters.
+	- Exercises added in several chapters.
+
 Changes from 4.1.0 to 4.1.1
 ---------------------------
 
 1. The "stat" extension now includes a "devbsize" element which indicates
-   the units for the "nblocks" element
+   the units for the "nblocks" element.
 
-2. The extension facility works on MinGW. Many of the extensions can be
+2. The extension facility now works on MinGW. Many of the extensions can be
    built and used directly.
 
 3. A number of bugs in the pretty-printing / profiling code have been fixed.
@@ -31,18 +41,36 @@ Changes from 4.1.0 to 4.1.1
 
 5. The debugger now lists source code correctly under Cygwin.
 
-6. Configuration and building Mac OS X libreadline should work now.
+6. Configuration and building with the Mac OS X libreadline should work now.
 
 7. The -O option now works again.
 
 8. The --include option, documented since 4.0, now actually works.
 
-9. Infrastructure updated to automake 1.13.4 and libtool 2.4.2.418.
+9. Infrastructure updated to automake 1.13.4, bison 3.0.2, and
+   libtool 2.4.2.418.
 
 10. The configure script now accepts a --disable-extensions option,
-which disables checking for and building the extensions.
+    which disables checking for and building the extensions.
+
+11. The VMS port has been considerably improved. In particular config.h
+    is now generated by a DCL script. Also, the extension facility works
+    and several of the extensions can be built and used. Currently, the
+    extension facility only works on Alpha and Itanium.
+
+12. The API now provides functions pointers for malloc(), calloc(),
+    realloc() and free(), to insure that the same memory allocation
+    functions are always used. This bumps the minor version by one.
+
+13. The printf quote flag now works correctly in locales with a different
+    decimal point character but without a thousands separator character.
+    If the thousands separator is a string, it will be correctly added
+    to decimal numbers.
+
+14. The readfile extension now has an input parser that will read whole
+    files as a single record.
 
-XXX. A number of bugs have been fixed. See the ChangeLog.
+15. A number of bugs have been fixed. See the ChangeLog.
 
 Changes from 4.0.2 to 4.1.0
 ---------------------------
diff --git a/README b/README
index eaf11a44..028637ec 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-  Copyright (C) 2005, 2006, 2007, 2009, 2010, 2011, 2012, 2013
+  Copyright (C) 2005, 2006, 2007, 2009, 2010, 2011, 2012, 2013, 2014
   Free Software Foundation, Inc.
   
   Copying and distribution of this file, with or without modification,
@@ -7,19 +7,21 @@
 
 README:
 
-This is GNU Awk 4.1.0. It is upwardly compatible with Brian Kernighan's
+This is GNU Awk 4.1.1. It is upwardly compatible with Brian Kernighan's
 version of Unix awk.  It is almost completely compliant with the
 2008 POSIX 1003.1 standard for awk. (See the note below about POSIX.)
 
-This is a major new release. See NEWS and ChangeLog for details.
+This is a bug-fix release. See NEWS and ChangeLog for details.
 
-Work to be done is described briefly in the TODO file.  Changes in this
-version are summarized in the NEWS file.
+Work to be done is described briefly in the TODO file, which is available
+only in the 'master' branch in the Git repo.
+
+Changes in this version are summarized in the NEWS file.
 
 Read the file POSIX.STD for a discussion of issues where the standard
 says one thing but gawk does something different.
 
-To format the documentation with TeX, use at least version 2013-03-19.11
+To format the documentation with TeX, use at least version 2014-03-18.17
 of texinfo.tex. There is a usable copy of texinfo.tex in the doc directory.
 
 INSTALLATION:
@@ -45,9 +47,12 @@ Automake.
 After successful compilation, do `make check' to run the test suite.
 There should be no output from the `cmp' invocations except in the
 cases where there are small differences in floating point values, and
-possibly in the case of strftime. Several of the tests ignore errors
-on purpose; those are not a problem.  If there are other differences,
-please investigate and report the problem.
+possibly in the case of strftime.  There may be differences based on
+installed (or not installed) locales and the quality of multibyte
+character support on your system.
+
+Several of the tests ignore errors on purpose; those are not a problem.
+If there are other differences, please investigate and report the problem.
 
 PRINTING THE MANUAL
 
@@ -65,7 +70,7 @@ the section in the manual on reporting bugs. Note that comp.lang.awk
 is about the worst place to post a gawk bug report. Please, use the
 mechanisms outlined in the manual.
 
-Email should be sent to bug-gawk@gnu.org.  This is now a separate mailing
+Email should be sent to bug-gawk@gnu.org.  This is a separate mailing
 list at GNU Central.  The advantage to using this address is that bug
 reports are archived at GNU Central.
 
@@ -89,6 +94,9 @@ VMS:
 	Pat Rankin
 	r.pat.rankin@gmail.com
 
+	John Malmberg
+	wb8tyw@qsl.net
+
 z/OS (OS/390):
 	Dave Pitts
 	dpitts@cozx.com
diff --git a/README.git b/README.git
index 7d0d260c..c947cc24 100644
--- a/README.git
+++ b/README.git
@@ -1,4 +1,4 @@
-Sat Dec  1 21:53:02 IST 2012
+Thu Apr 17 16:54:26 IDT 2014
 ============================
 
 If you are reading this, you have retrieved the gawk code base via
@@ -350,3 +350,16 @@ has been pushed up to the Savannah repo or not.
 
 If your branch is completely local to your machine, use `git rebase'.
 Otherwise, use `git merge'.
+
+- How do I remove branches in my local repo that are no longer in the
+  remote repo?
+
+  Either
+  	git fetch --prune
+  or
+  	git remote prune origin
+
+  These remove the remote branches (i.e., origin/something)
+  that no longer exist on the remote.
+
+  (Thanks to Stepan Kasal for this answer.)
diff --git a/README_d/ChangeLog b/README_d/ChangeLog
index 49c30f13..6bc828d9 100644
--- a/README_d/ChangeLog
+++ b/README_d/ChangeLog
@@ -1,3 +1,36 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-04-02         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* README.gcc-3: New file.
+
+2014-01-22         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* README.solaris: Updated.
+
+2014-01-12         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* README.VMS: document that the gawk.cld needs a fix.
+
+2013-12-23         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* README.VMS: Add documentation about building dynamic
+	extensions.
+
+2013-12-23         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* README.VMS: Document decoding Gawk VMS exit codes.
+
+2013-12-16         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* README.VMS: Further updates.
+
+2013-12-05         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* README.VMS: updated with current build information.
+
 2013-07-02         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* README.pc: Update that |& also now works on MinGW.
diff --git a/README_d/README.VMS b/README_d/README.VMS
index b47cb0f7..0faabbc2 100644
--- a/README_d/README.VMS
+++ b/README_d/README.VMS
@@ -6,21 +6,112 @@ CC and LINK commands, and there's also a Makefile for use with the MMS
 utility.  From the source directory, use either
  |$ @[.VMS]VMSBUILD.COM
 or
- |$ MMS/DECRIPTION=[.VMS]DECSRIP.MMS GAWK
+ |$ MMS/DESCRIPTION=[.VMS]DESCRIP.MMS gawk
+or
+ |$ MMK/DESCRIPTION=[.VMS]DESCRIP.MMS gawk
+
+Note that on IA64 and Alpha the case of the target may be important.
+MMS has had problems on ODS-5 volumes.  MMK does not have these issues.
+MMK is available free from https://github.com/endlesssoftware/mmk.
+The most recent builds of gawk on VMS used MMK.
+
+Support of the vmsbuild.com may get dropped in a future release.
 
 DEC C  -- use either vmsbuild.com or descrip.mms as is.
+       DEC C is also known as Compaq C and HP C.
+
 VAX C  -- use `@vmsbuild VAXC' or `MMS/MACRO=("VAXC")'.  On a system
         with both VAX C and DEC C installed where DEC C is the default,
         use `MMS/MACRO=("VAXC","CC=CC/VAXC")' for the MMS variant; for
         the vmsbuild.com variant, any need for `/VAXC' will be detected
         automatically.
+        * IMPORTANT NOTE * VAX C should not be used on VAX/VMS 5.5-2 and
+        later.  Use DEC C instead.
+
 GNU C  -- use `@vmsbuild GNUC' or `MMS/MACRO=("GNUC")'.  On a system
         where the GCC command is not already defined, use either
         `@vmsbuild GNUC DO_GNUC_SETUP' or
         `MMS/MACRO=("GNUC","DO_GNUC_SETUP")'.
 
-     Tested under Alpha/VMS V7.1 using DEC C V6.4.  GAWK should work
-without modifications for VMS V4.6 and up.
+Most recent builds are using:
+    OpenVMS VAX 7.3 using DEC C 6.4
+    OpenVMS Alpha 8.3 using HP C V 7.3
+    OpenVMS Alpha 8.4 using HP C V 7.3
+    OpenVMS IA64 8.4 using HP C V 7.3
+
+GAWK was originally ported for VMS V4.6 and up.  It has not been tested
+with a release that old for some time.
+
+Compiling dynamic extensions on VMS:
+
+GAWK comes with some dynamic extensions.  The extensions that have been
+ported to VMS can be built using one of the following commands.
+
+ |$ MMS/DESCRIPTION=[.VMS]DESCRIP.MMS extensions
+or
+ |$ MMK/DESCRIPTION=[.VMS]DESCRIP.MMS extensions
+
+GAWK uses AWKLIBPATH as either an environment variable or a logical name
+to find the dynamic extensions.
+
+Dynamic extensions need to be compiled with the same compiler options for
+floating point, pointer size, and symbol name handling as gawk.
+Alpha and Itanium should use IEEE floating point.  The pointer size is 32 bits,
+and the symbol name handling is to be exact case with CRC shortening for
+symbols longer than 32 bits.
+
+Currently dynamic extensions have only been tested to work on VMS 8.3 and later
+on both Alpha and Itanium.  Dynamic extensions are not currently working on
+VAX/VMS 7.3.
+
+Compile time are macros needed to be defined before the first VMS supplied
+header file is included.  Usually this will be done with a config.h file.
+
+#if (__CRTL_VER >= 70200000) && !defined (__VAX)
+#define _LARGEFILE 1
+#endif
+
+#ifndef __VAX
+#ifdef __CRTL_VER
+#if __CRTL_VER >= 80200000
+#define _USE_STD_STAT 1
+#endif
+#endif
+#endif
+
+Alpha and Itanium:
+
+/name=(as_is,short)
+/float=ieee/ieee_mode=denorm_results
+
+VAX:
+
+/name=(as_is,short)
+
+The linker option files are [.vms]gawk_plugin.opt for Alpha and Itanium.
+
+As the VAX dynamic plug-in feature is not yet working, the files potentially
+needed for a future VAX plugin are in [.vms.vax] directory of the source.
+
+
+Testing GAWK on VMS:
+
+After you build gawk, you can test it with the [.vms]vmstest.com procedure.
+The procedure takes a parameter that is either for a list of tests or
+a specific test.  The parameter clean cleans up files left over from running
+the tests.
+
+  $ set def [.test]
+  $ @[-.vms]vmstest.com bigtest
+  $ @[-.vms]vmstest.com clean
+  $ set def [-]
+
+To test the dynamic extensions on VMS 8.3 and later, use:
+
+  $ set def [.test]
+  $ @[-.vms]vmstest.com extension
+  $ @[-.vms]vmstest.com clean
+  $ set def [-]
 
 
 Installing GAWK on VMS:
@@ -33,6 +124,11 @@ That symbol should be placed in the user's login.com or in the system-
 wide sylogin.com procedure so that it will be defined every time the
 user logs on.
 
+If your gawk was installed by a PCSI kit into the GNV$GNU: directory tree,
+the program will be known as GNV$GNU:[bin]gnv$gawk.exe and the help file
+will be GNV$GNU:[vms_help]gawk.hlp.  The GNV$GNU:[vms_bin]gawk_verb.cld can be
+used to add GAWK and the alias AWK to a DCL command table.
+
      Optionally, the help entry can be loaded into a VMS help library.
  |$ LIBRARY/HELP SYS$HELP:HELPLIB [.VMS]GAWK.HLP
 (You may want to substitute a site-specific help library rather than
@@ -79,9 +175,52 @@ separated list of directory specifications.  When defining it, the
 value should be quoted so that it retains a single translation, not a
 multi-translation RMS searchlist.
 
-------------------------------
-Thu Jun 18 05:22:10 IDT 2009
-============================
+     The exit status from Gawk is encoded in the the VMS $status exit
+value so that the severity bits are set as expected and the original
+Gawk exit value can be extracted.
+
+To extract the actual gawk exit code from the VMS status use:
+     unix_status = (vms_status .and. &x7f8) / 8
+
+The exit value is encoded to comply with VMS coding standards and
+will have the C_FACILITY_NO of 0x350000 with the constant 0xA000
+added to the number shifted over by 3 bits to make room for the
+severity codes.
+
+The Gawk exit value of 1 will result in the VMS status having the
+ERROR severity status set.  The Gawk exit value of 2 will result in
+the FATAL severity status set.  All other Gawk exit values will have
+the Success severity status set.
+
+This change was needed to provide all Gawk exit values to VMS programs and
+for compatibilty with programs written in C and the GNV environment.
+
+Older versions of Gawk incorrectly mostly passed through the Gawk
+status values instead of encoding them.  DCL scripts that were checking
+the severity values will probably not need changing.  DCL scripts that
+were checking the exact exit status will need an update.
+
+VAX/VMS floating point uses unbiased rounding.  This is generaly incompatible
+with the expected behavior.  The ofmta test in the test directory will
+fail on VAX.
+
+Gawk needs the SYS$TIMEZONE_RULE or TZ logical name to be defined or it
+will output times in GMT.
+
+The vmstest.com script needs SYS$TIMEZONE_NAME to be defined to match
+the SYS$TIMEZONE_RULE.  Older versions of VMS do not define these logical
+names.
+
+TO DO Items (not in order of priority)
+
+1. Implement dynamic plug-ins on VAX.
+
+2. With the system() function, the status for DCL commands are not being
+   returned.
+
+3. Need gawk to accept logical names GNV$AWKPATH, GNV$AWKLIB, and
+   GNV$AWK_LIBARARY in addtion to the unprefixed names.  This will allow
+   system wide default values to be set by an installation kit.
 
-On OpenVMS V7.3 (Alpha) the "manyfiles" test is known to fail. The reason
-is not (yet) known.
+4. Need to fix the gawk.cld file to not require a parameter for the options
+   that do not use the parameter.
diff --git a/README_d/README.gcc-3 b/README_d/README.gcc-3
new file mode 100644
index 00000000..c76a9af7
--- /dev/null
+++ b/README_d/README.gcc-3
@@ -0,0 +1,11 @@
+Wed Apr  2 21:29:17 IDT 2014
+============================
+
+I have had a report that on a GNU/Linux system using gcc 3.3.6 (32 bit)
+that the aasort test fails.  Compiling without -O builds a gawk that
+does pass all tests.
+
+Caveat Emptor.
+
+Arnold Robbins
+arnold@skeeve.com
diff --git a/README_d/README.pc b/README_d/README.pc
index 32a81fc1..63ba473e 100644
--- a/README_d/README.pc
+++ b/README_d/README.pc
@@ -18,7 +18,7 @@ The `configure' step takes a long time, but works otherwise.
 
 ******************************** N O T E *******************************
 * The `|&' operator only works when gawk is compiled for Cygwin or for *
-* MinGW.  Neither * socket support nor two-way pipes work in any other *
+* MinGW.  Neither socket support nor two-way pipes work in any other   *
 * Windows environment!                                                 *
 ************************************************************************
 
diff --git a/README_d/README.solaris b/README_d/README.solaris
index 7aa44eeb..91e0c701 100644
--- a/README_d/README.solaris
+++ b/README_d/README.solaris
@@ -1,7 +1,8 @@
-Thu Nov  7 22:42:46 IST 2013
+Wed Jan 22 21:51:59 IST 2014
 ============================
 
-On Solaris 11 x86 with the Sun compiler you need to use
+On Solaris 10 x86, Solaris 11 x86, Solaris 10 sparc and Solaris 11 sparc,
+with the Sun compiler (Solaris Studio 12.3) you need to use
 
 	c99 -Xc -D_XPG6
 
@@ -9,23 +10,5 @@ to correctly compile gawk and the extensions.
 
 Various tests can fail if the necessary locales aren't installed.
 
-Fri Jul 15 14:24:00 IDT 2011
-============================
-It looks like you need to use
-
-	-Xc -D_XPG4_2
-
-on Solaris 10 with the Sun C compiler when compiling gawk in order for
-libsigsegv to be found correctly, and
-
-	-Xc -D_XPG4_2 -Duint64_t=upad64_t
-
-on Solaris 9.
-
-Tue Apr 20 11:33:20 IDT 2010
-============================
-The lc_num1 test fails on Solaris 10 systems. This is a bug with Solaris,
-not gawk.
-
 Arnold Robbins
 arnold@skeeve.com
diff --git a/TODO b/TODO
index f7a10ba3..a4764946 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-Thu Oct 24 22:11:44 IDT 2013
+Thu Apr 17 11:31:24 IDT 2014
 ============================
 
 There were too many files tracking different thoughts and ideas for
@@ -19,6 +19,9 @@ TODO
 Minor Cleanups and Code Improvements
 ------------------------------------
 
+	Nuke installing the igawk script and the igawk.1 man page. Just
+	remove them from the dist.
+
 	Review the bash source script for working with shared libraries in
 	order to nuke the use of libtool. [ Partially started in the
 	nolibtool branch. ]
diff --git a/array.c b/array.c
index 37894da5..682b8ddb 100644
--- a/array.c
+++ b/array.c
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -1279,7 +1279,7 @@ assoc_list(NODE *symbol, const char *sort_str, sort_context_t sort_ctxt)
 	INSTRUCTION *code = NULL;
 	extern int currule;
 	int save_rule = 0;
-	assoc_kind_t assoc_kind = 0;
+	assoc_kind_t assoc_kind = ANONE;
 	
 	elem_size = 1;
 
diff --git a/awk.h b/awk.h
index e0964b94..9255b45b 100644
--- a/awk.h
+++ b/awk.h
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -1327,6 +1327,7 @@ if (--val) \
 /* array.c */
 typedef enum { SORTED_IN = 1, ASORT, ASORTI } sort_context_t;
 typedef enum {
+	ANONE   = 0x00,		/* "unused" value */
 	AINDEX	= 0x001,	/* list of indices */ 
 	AVALUE	= 0x002,	/* list of values */
 	AINUM	= 0x004,	/* numeric index */
@@ -1371,7 +1372,8 @@ extern const char *getfname(NODE *(*)(int));
 extern NODE *stopme(int nargs);
 extern void shadow_funcs(void);
 extern int check_special(const char *name);
-extern SRCFILE *add_srcfile(int stype, char *src, SRCFILE *curr, bool *already_included, int *errcode);
+extern SRCFILE *add_srcfile(enum srctype stype, char *src, SRCFILE *curr, bool *already_included, int *errcode);
+extern void free_srcfile(SRCFILE *thisfile);
 extern void register_deferred_variable(const char *name, NODE *(*load_func)(void));
 extern int files_are_same(char *path, SRCFILE *src);
 extern void valinfo(NODE *n, Func_print print_func, FILE *fp);
diff --git a/awkgram.c b/awkgram.c
index 74913840..b36816c9 100644
--- a/awkgram.c
+++ b/awkgram.c
@@ -1,19 +1,19 @@
-/* A Bison parser, made by GNU Bison 2.7.12-4996.  */
+/* A Bison parser, made by GNU Bison 3.0.2.  */
 
 /* Bison implementation for Yacc-like parsers in C
-   
-      Copyright (C) 1984, 1989-1990, 2000-2013 Free Software Foundation, Inc.
-   
+
+   Copyright (C) 1984, 1989-1990, 2000-2013 Free Software Foundation, Inc.
+
    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.
-   
+
    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.
-   
+
    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
 
@@ -26,7 +26,7 @@
    special exception, which will cause the skeleton and the resulting
    Bison output files to be licensed under the GNU General Public
    License without this special exception.
-   
+
    This special exception was added by the Free Software Foundation in
    version 2.2 of Bison.  */
 
@@ -44,7 +44,7 @@
 #define YYBISON 1
 
 /* Bison version.  */
-#define YYBISON_VERSION "2.7.12-4996"
+#define YYBISON_VERSION "3.0.2"
 
 /* Skeleton name.  */
 #define YYSKELETON_NAME "yacc.c"
@@ -62,8 +62,7 @@
 
 
 /* Copy the first part of user declarations.  */
-/* Line 371 of yacc.c  */
-#line 26 "awkgram.y"
+#line 26 "awkgram.y" /* yacc.c:339  */
 
 #ifdef GAWKDEBUG
 #define YYDEBUG 12
@@ -198,14 +197,13 @@ extern double fmod(double x, double y);
 
 #define is_identchar(c)		(isalnum(c) || (c) == '_')
 
-/* Line 371 of yacc.c  */
-#line 203 "awkgram.c"
+#line 201 "awkgram.c" /* yacc.c:339  */
 
-# ifndef YY_NULL
+# ifndef YY_NULLPTR
 #  if defined __cplusplus && 201103L <= __cplusplus
-#   define YY_NULL nullptr
+#   define YY_NULLPTR nullptr
 #  else
-#   define YY_NULL 0
+#   define YY_NULLPTR 0
 #  endif
 # endif
 
@@ -218,7 +216,7 @@ extern double fmod(double x, double y);
 #endif
 
 
-/* Enabling traces.  */
+/* Debug traces.  */
 #ifndef YYDEBUG
 # define YYDEBUG 0
 #endif
@@ -226,64 +224,63 @@ extern double fmod(double x, double y);
 extern int yydebug;
 #endif
 
-/* Tokens.  */
+/* Token type.  */
 #ifndef YYTOKENTYPE
 # define YYTOKENTYPE
-   /* Put the tokens into the symbol table, so that GDB and other debuggers
-      know about them.  */
-   enum yytokentype {
-     FUNC_CALL = 258,
-     NAME = 259,
-     REGEXP = 260,
-     FILENAME = 261,
-     YNUMBER = 262,
-     YSTRING = 263,
-     RELOP = 264,
-     IO_OUT = 265,
-     IO_IN = 266,
-     ASSIGNOP = 267,
-     ASSIGN = 268,
-     MATCHOP = 269,
-     CONCAT_OP = 270,
-     SUBSCRIPT = 271,
-     LEX_BEGIN = 272,
-     LEX_END = 273,
-     LEX_IF = 274,
-     LEX_ELSE = 275,
-     LEX_RETURN = 276,
-     LEX_DELETE = 277,
-     LEX_SWITCH = 278,
-     LEX_CASE = 279,
-     LEX_DEFAULT = 280,
-     LEX_WHILE = 281,
-     LEX_DO = 282,
-     LEX_FOR = 283,
-     LEX_BREAK = 284,
-     LEX_CONTINUE = 285,
-     LEX_PRINT = 286,
-     LEX_PRINTF = 287,
-     LEX_NEXT = 288,
-     LEX_EXIT = 289,
-     LEX_FUNCTION = 290,
-     LEX_BEGINFILE = 291,
-     LEX_ENDFILE = 292,
-     LEX_GETLINE = 293,
-     LEX_NEXTFILE = 294,
-     LEX_IN = 295,
-     LEX_AND = 296,
-     LEX_OR = 297,
-     INCREMENT = 298,
-     DECREMENT = 299,
-     LEX_BUILTIN = 300,
-     LEX_LENGTH = 301,
-     LEX_EOF = 302,
-     LEX_INCLUDE = 303,
-     LEX_EVAL = 304,
-     LEX_LOAD = 305,
-     NEWLINE = 306,
-     SLASH_BEFORE_EQUAL = 307,
-     UNARY = 308
-   };
+  enum yytokentype
+  {
+    FUNC_CALL = 258,
+    NAME = 259,
+    REGEXP = 260,
+    FILENAME = 261,
+    YNUMBER = 262,
+    YSTRING = 263,
+    RELOP = 264,
+    IO_OUT = 265,
+    IO_IN = 266,
+    ASSIGNOP = 267,
+    ASSIGN = 268,
+    MATCHOP = 269,
+    CONCAT_OP = 270,
+    SUBSCRIPT = 271,
+    LEX_BEGIN = 272,
+    LEX_END = 273,
+    LEX_IF = 274,
+    LEX_ELSE = 275,
+    LEX_RETURN = 276,
+    LEX_DELETE = 277,
+    LEX_SWITCH = 278,
+    LEX_CASE = 279,
+    LEX_DEFAULT = 280,
+    LEX_WHILE = 281,
+    LEX_DO = 282,
+    LEX_FOR = 283,
+    LEX_BREAK = 284,
+    LEX_CONTINUE = 285,
+    LEX_PRINT = 286,
+    LEX_PRINTF = 287,
+    LEX_NEXT = 288,
+    LEX_EXIT = 289,
+    LEX_FUNCTION = 290,
+    LEX_BEGINFILE = 291,
+    LEX_ENDFILE = 292,
+    LEX_GETLINE = 293,
+    LEX_NEXTFILE = 294,
+    LEX_IN = 295,
+    LEX_AND = 296,
+    LEX_OR = 297,
+    INCREMENT = 298,
+    DECREMENT = 299,
+    LEX_BUILTIN = 300,
+    LEX_LENGTH = 301,
+    LEX_EOF = 302,
+    LEX_INCLUDE = 303,
+    LEX_EVAL = 304,
+    LEX_LOAD = 305,
+    NEWLINE = 306,
+    SLASH_BEFORE_EQUAL = 307,
+    UNARY = 308
+  };
 #endif
 /* Tokens.  */
 #define FUNC_CALL 258
@@ -338,37 +335,23 @@ extern int yydebug;
 #define SLASH_BEFORE_EQUAL 307
 #define UNARY 308
 
-
-
+/* Value type.  */
 #if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED
 typedef int YYSTYPE;
 # define YYSTYPE_IS_TRIVIAL 1
-# define yystype YYSTYPE /* obsolescent; will be withdrawn */
 # define YYSTYPE_IS_DECLARED 1
 #endif
 
+
 extern YYSTYPE yylval;
 
-#ifdef YYPARSE_PARAM
-#if defined __STDC__ || defined __cplusplus
-int yyparse (void *YYPARSE_PARAM);
-#else
-int yyparse ();
-#endif
-#else /* ! YYPARSE_PARAM */
-#if defined __STDC__ || defined __cplusplus
 int yyparse (void);
-#else
-int yyparse ();
-#endif
-#endif /* ! YYPARSE_PARAM */
 
 
 
 /* Copy the second part of user declarations.  */
 
-/* Line 390 of yacc.c  */
-#line 372 "awkgram.c"
+#line 355 "awkgram.c" /* yacc.c:358  */
 
 #ifdef short
 # undef short
@@ -382,11 +365,8 @@ typedef unsigned char yytype_uint8;
 
 #ifdef YYTYPE_INT8
 typedef YYTYPE_INT8 yytype_int8;
-#elif (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-typedef signed char yytype_int8;
 #else
-typedef short int yytype_int8;
+typedef signed char yytype_int8;
 #endif
 
 #ifdef YYTYPE_UINT16
@@ -406,8 +386,7 @@ typedef short int yytype_int16;
 #  define YYSIZE_T __SIZE_TYPE__
 # elif defined size_t
 #  define YYSIZE_T size_t
-# elif ! defined YYSIZE_T && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+# elif ! defined YYSIZE_T
 #  include <stddef.h> /* INFRINGES ON USER NAME SPACE */
 #  define YYSIZE_T size_t
 # else
@@ -429,11 +408,30 @@ typedef short int yytype_int16;
 # endif
 #endif
 
-#ifndef __attribute__
-/* This feature is available in gcc versions 2.5 and later.  */
-# if (! defined __GNUC__ || __GNUC__ < 2 \
-      || (__GNUC__ == 2 && __GNUC_MINOR__ < 5))
-#  define __attribute__(Spec) /* empty */
+#ifndef YY_ATTRIBUTE
+# if (defined __GNUC__                                               \
+      && (2 < __GNUC__ || (__GNUC__ == 2 && 96 <= __GNUC_MINOR__)))  \
+     || defined __SUNPRO_C && 0x5110 <= __SUNPRO_C
+#  define YY_ATTRIBUTE(Spec) __attribute__(Spec)
+# else
+#  define YY_ATTRIBUTE(Spec) /* empty */
+# endif
+#endif
+
+#ifndef YY_ATTRIBUTE_PURE
+# define YY_ATTRIBUTE_PURE   YY_ATTRIBUTE ((__pure__))
+#endif
+
+#ifndef YY_ATTRIBUTE_UNUSED
+# define YY_ATTRIBUTE_UNUSED YY_ATTRIBUTE ((__unused__))
+#endif
+
+#if !defined _Noreturn \
+     && (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112)
+# if defined _MSC_VER && 1200 <= _MSC_VER
+#  define _Noreturn __declspec (noreturn)
+# else
+#  define _Noreturn YY_ATTRIBUTE ((__noreturn__))
 # endif
 #endif
 
@@ -444,24 +442,25 @@ typedef short int yytype_int16;
 # define YYUSE(E) /* empty */
 #endif
 
-
-/* Identity function, used to suppress warnings about constant conditions.  */
-#ifndef lint
-# define YYID(N) (N)
-#else
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-static int
-YYID (int yyi)
+#if defined __GNUC__ && 407 <= __GNUC__ * 100 + __GNUC_MINOR__
+/* Suppress an incorrect diagnostic about yylval being uninitialized.  */
+# define YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN \
+    _Pragma ("GCC diagnostic push") \
+    _Pragma ("GCC diagnostic ignored \"-Wuninitialized\"")\
+    _Pragma ("GCC diagnostic ignored \"-Wmaybe-uninitialized\"")
+# define YY_IGNORE_MAYBE_UNINITIALIZED_END \
+    _Pragma ("GCC diagnostic pop")
 #else
-static int
-YYID (yyi)
-    int yyi;
+# define YY_INITIAL_VALUE(Value) Value
 #endif
-{
-  return yyi;
-}
+#ifndef YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
+# define YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
+# define YY_IGNORE_MAYBE_UNINITIALIZED_END
 #endif
+#ifndef YY_INITIAL_VALUE
+# define YY_INITIAL_VALUE(Value) /* Nothing. */
+#endif
+
 
 #if ! defined yyoverflow || YYERROR_VERBOSE
 
@@ -480,8 +479,7 @@ YYID (yyi)
 #    define alloca _alloca
 #   else
 #    define YYSTACK_ALLOC alloca
-#    if ! defined _ALLOCA_H && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+#    if ! defined _ALLOCA_H && ! defined EXIT_SUCCESS
 #     include <stdlib.h> /* INFRINGES ON USER NAME SPACE */
       /* Use EXIT_SUCCESS as a witness for stdlib.h.  */
 #     ifndef EXIT_SUCCESS
@@ -493,8 +491,8 @@ YYID (yyi)
 # endif
 
 # ifdef YYSTACK_ALLOC
-   /* Pacify GCC's `empty if-body' warning.  */
-#  define YYSTACK_FREE(Ptr) do { /* empty */; } while (YYID (0))
+   /* Pacify GCC's 'empty if-body' warning.  */
+#  define YYSTACK_FREE(Ptr) do { /* empty */; } while (0)
 #  ifndef YYSTACK_ALLOC_MAXIMUM
     /* The OS might guarantee only one guard page at the bottom of the stack,
        and a page size can be as small as 4096 bytes.  So we cannot safely
@@ -510,7 +508,7 @@ YYID (yyi)
 #  endif
 #  if (defined __cplusplus && ! defined EXIT_SUCCESS \
        && ! ((defined YYMALLOC || defined malloc) \
-	     && (defined YYFREE || defined free)))
+             && (defined YYFREE || defined free)))
 #   include <stdlib.h> /* INFRINGES ON USER NAME SPACE */
 #   ifndef EXIT_SUCCESS
 #    define EXIT_SUCCESS 0
@@ -518,15 +516,13 @@ YYID (yyi)
 #  endif
 #  ifndef YYMALLOC
 #   define YYMALLOC malloc
-#   if ! defined malloc && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+#   if ! defined malloc && ! defined EXIT_SUCCESS
 void *malloc (YYSIZE_T); /* INFRINGES ON USER NAME SPACE */
 #   endif
 #  endif
 #  ifndef YYFREE
 #   define YYFREE free
-#   if ! defined free && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+#   if ! defined free && ! defined EXIT_SUCCESS
 void free (void *); /* INFRINGES ON USER NAME SPACE */
 #   endif
 #  endif
@@ -536,7 +532,7 @@ void free (void *); /* INFRINGES ON USER NAME SPACE */
 
 #if (! defined yyoverflow \
      && (! defined __cplusplus \
-	 || (defined YYSTYPE_IS_TRIVIAL && YYSTYPE_IS_TRIVIAL)))
+         || (defined YYSTYPE_IS_TRIVIAL && YYSTYPE_IS_TRIVIAL)))
 
 /* A type that is properly aligned for any stack member.  */
 union yyalloc
@@ -561,16 +557,16 @@ union yyalloc
    elements in the stack, and YYPTR gives the new location of the
    stack.  Advance YYPTR to a properly aligned location for the next
    stack.  */
-# define YYSTACK_RELOCATE(Stack_alloc, Stack)				\
-    do									\
-      {									\
-	YYSIZE_T yynewbytes;						\
-	YYCOPY (&yyptr->Stack_alloc, Stack, yysize);			\
-	Stack = &yyptr->Stack_alloc;					\
-	yynewbytes = yystacksize * sizeof (*Stack) + YYSTACK_GAP_MAXIMUM; \
-	yyptr += yynewbytes / sizeof (*yyptr);				\
-      }									\
-    while (YYID (0))
+# define YYSTACK_RELOCATE(Stack_alloc, Stack)                           \
+    do                                                                  \
+      {                                                                 \
+        YYSIZE_T yynewbytes;                                            \
+        YYCOPY (&yyptr->Stack_alloc, Stack, yysize);                    \
+        Stack = &yyptr->Stack_alloc;                                    \
+        yynewbytes = yystacksize * sizeof (*Stack) + YYSTACK_GAP_MAXIMUM; \
+        yyptr += yynewbytes / sizeof (*yyptr);                          \
+      }                                                                 \
+    while (0)
 
 #endif
 
@@ -589,7 +585,7 @@ union yyalloc
           for (yyi = 0; yyi < (Count); yyi++)   \
             (Dst)[yyi] = (Src)[yyi];            \
         }                                       \
-      while (YYID (0))
+      while (0)
 #  endif
 # endif
 #endif /* !YYCOPY_NEEDED */
@@ -605,17 +601,19 @@ union yyalloc
 #define YYNNTS  65
 /* YYNRULES -- Number of rules.  */
 #define YYNRULES  188
-/* YYNRULES -- Number of states.  */
+/* YYNSTATES -- Number of states.  */
 #define YYNSTATES  335
 
-/* YYTRANSLATE(YYLEX) -- Bison symbol number corresponding to YYLEX.  */
+/* YYTRANSLATE[YYX] -- Symbol number corresponding to YYX as returned
+   by yylex, with out-of-bounds checking.  */
 #define YYUNDEFTOK  2
 #define YYMAXUTOK   308
 
-#define YYTRANSLATE(YYX)						\
+#define YYTRANSLATE(YYX)                                                \
   ((unsigned int) (YYX) <= YYMAXUTOK ? yytranslate[YYX] : YYUNDEFTOK)
 
-/* YYTRANSLATE[YYLEX] -- Bison symbol number corresponding to YYLEX.  */
+/* YYTRANSLATE[TOKEN-NUM] -- Symbol number corresponding to TOKEN-NUM
+   as returned by yylex, without out-of-bounds checking.  */
 static const yytype_uint8 yytranslate[] =
 {
        0,     2,     2,     2,     2,     2,     2,     2,     2,     2,
@@ -652,96 +650,7 @@ static const yytype_uint8 yytranslate[] =
 };
 
 #if YYDEBUG
-/* YYPRHS[YYN] -- Index of the first RHS symbol of rule number YYN in
-   YYRHS.  */
-static const yytype_uint16 yyprhs[] =
-{
-       0,     0,     3,     4,     7,    10,    13,    16,    19,    22,
-      25,    30,    35,    37,    40,    42,    44,    47,    49,    50,
-      52,    57,    59,    61,    63,    65,    71,    73,    75,    77,
-      80,    82,    84,    91,    92,    96,    98,   100,   101,   104,
-     107,   109,   112,   115,   119,   121,   131,   138,   147,   156,
-     169,   181,   183,   186,   189,   192,   195,   199,   200,   205,
-     208,   209,   214,   215,   220,   225,   227,   228,   230,   231,
-     234,   237,   243,   248,   250,   253,   256,   258,   260,   262,
-     264,   266,   270,   271,   272,   276,   283,   293,   295,   298,
-     299,   301,   302,   305,   306,   308,   310,   314,   316,   319,
-     323,   324,   326,   327,   329,   331,   335,   337,   340,   344,
-     348,   352,   356,   360,   364,   368,   372,   378,   380,   382,
-     384,   387,   389,   391,   393,   395,   397,   399,   402,   404,
-     408,   412,   416,   420,   424,   428,   432,   435,   438,   444,
-     449,   453,   457,   461,   465,   469,   473,   475,   478,   482,
-     487,   492,   494,   496,   498,   501,   504,   506,   508,   511,
-     514,   516,   519,   524,   525,   527,   528,   531,   533,   536,
-     538,   542,   544,   547,   550,   552,   555,   557,   561,   563,
-     565,   566,   569,   572,   574,   575,   577,   579,   581
-};
-
-/* YYRHS -- A `-1'-separated list of the rules' RHS.  */
-static const yytype_int16 yyrhs[] =
-{
-      76,     0,    -1,    -1,    76,    77,    -1,    76,   105,    -1,
-      76,    47,    -1,    76,     1,    -1,    80,    81,    -1,    80,
-      89,    -1,    84,    81,    -1,    69,    48,    78,    89,    -1,
-      69,    50,    79,    89,    -1,     6,    -1,     6,     1,    -1,
-       1,    -1,     6,    -1,     6,     1,    -1,     1,    -1,    -1,
-     113,    -1,   113,    55,   106,   113,    -1,    17,    -1,    18,
-      -1,    36,    -1,    37,    -1,   133,    88,   134,   136,   106,
-      -1,     4,    -1,     3,    -1,    83,    -1,    69,    49,    -1,
-      45,    -1,    46,    -1,    35,    82,    67,   108,   135,   106,
-      -1,    -1,    87,    86,     5,    -1,    61,    -1,    52,    -1,
-      -1,    88,    90,    -1,    88,     1,    -1,   105,    -1,   137,
-     106,    -1,   137,   106,    -1,   133,    88,   134,    -1,   104,
-      -1,    23,    67,   113,   135,   106,   133,    97,   106,   134,
-      -1,    26,    67,   113,   135,   106,    90,    -1,    27,   106,
-      90,    26,    67,   113,   135,   106,    -1,    28,    67,     4,
-      40,   130,   135,   106,    90,    -1,    28,    67,    96,   137,
-     106,   113,   137,   106,    96,   135,   106,    90,    -1,    28,
-      67,    96,   137,   106,   137,   106,    96,   135,   106,    90,
-      -1,    91,    -1,    29,    89,    -1,    30,    89,    -1,    33,
-      89,    -1,    39,    89,    -1,    34,   110,    89,    -1,    -1,
-      21,    92,   110,    89,    -1,    93,    89,    -1,    -1,   100,
-      94,   101,   102,    -1,    -1,    22,     4,    95,   124,    -1,
-      22,    67,     4,    68,    -1,   113,    -1,    -1,    93,    -1,
-      -1,    97,    98,    -1,    97,     1,    -1,    24,    99,   138,
-     106,    88,    -1,    25,   138,   106,    88,    -1,     7,    -1,
-      59,     7,    -1,    58,     7,    -1,     8,    -1,    85,    -1,
-      31,    -1,    32,    -1,   111,    -1,    67,   112,   135,    -1,
-      -1,    -1,    10,   103,   117,    -1,    19,    67,   113,   135,
-     106,    90,    -1,    19,    67,   113,   135,   106,    90,    20,
-     106,    90,    -1,    51,    -1,   105,    51,    -1,    -1,   105,
-      -1,    -1,    56,   118,    -1,    -1,   109,    -1,     4,    -1,
-     109,   139,     4,    -1,     1,    -1,   109,     1,    -1,   109,
-     139,     1,    -1,    -1,   113,    -1,    -1,   112,    -1,   113,
-      -1,   112,   139,   113,    -1,     1,    -1,   112,     1,    -1,
-     112,     1,   113,    -1,   112,   139,     1,    -1,   131,   114,
-     113,    -1,   113,    41,   113,    -1,   113,    42,   113,    -1,
-     113,    14,   113,    -1,   113,    40,   130,    -1,   113,   116,
-     113,    -1,   113,    53,   113,    54,   113,    -1,   117,    -1,
-      13,    -1,    12,    -1,    52,    13,    -1,     9,    -1,    56,
-      -1,   115,    -1,    57,    -1,   118,    -1,   119,    -1,   117,
-     118,    -1,   120,    -1,   118,    65,   118,    -1,   118,    60,
-     118,    -1,   118,    61,   118,    -1,   118,    62,   118,    -1,
-     118,    58,   118,    -1,   118,    59,   118,    -1,    38,   123,
-     107,    -1,   131,    43,    -1,   131,    44,    -1,    67,   112,
-     135,    40,   130,    -1,   117,    11,    38,   123,    -1,   119,
-      65,   118,    -1,   119,    60,   118,    -1,   119,    61,   118,
-      -1,   119,    62,   118,    -1,   119,    58,   118,    -1,   119,
-      59,   118,    -1,    85,    -1,    63,   118,    -1,    67,   113,
-     135,    -1,    45,    67,   111,   135,    -1,    46,    67,   111,
-     135,    -1,    46,    -1,   121,    -1,   131,    -1,    43,   131,
-      -1,    44,   131,    -1,     7,    -1,     8,    -1,    59,   118,
-      -1,    58,   118,    -1,   122,    -1,    69,   122,    -1,     3,
-      67,   111,   135,    -1,    -1,   131,    -1,    -1,   125,    16,
-      -1,   126,    -1,   125,   126,    -1,   127,    -1,    70,   112,
-      71,    -1,   127,    -1,   128,   127,    -1,   128,    16,    -1,
-       4,    -1,     4,   129,    -1,   130,    -1,    66,   120,   132,
-      -1,    43,    -1,    44,    -1,    -1,    72,   106,    -1,    73,
-     106,    -1,    68,    -1,    -1,   137,    -1,    74,    -1,    54,
-      -1,    55,   106,    -1
-};
-
-/* YYRLINE[YYN] -- source line where rule number YYN was defined.  */
+  /* YYRLINE[YYN] -- Source line where rule number YYN was defined.  */
 static const yytype_uint16 yyrline[] =
 {
        0,   200,   200,   202,   207,   208,   214,   226,   230,   241,
@@ -757,12 +666,12 @@ static const yytype_uint16 yyrline[] =
     1216,  1217,  1223,  1224,  1229,  1231,  1236,  1238,  1246,  1251,
     1260,  1267,  1269,  1271,  1287,  1297,  1304,  1306,  1311,  1313,
     1315,  1323,  1325,  1330,  1332,  1337,  1339,  1341,  1391,  1393,
-    1395,  1397,  1399,  1401,  1403,  1405,  1428,  1433,  1438,  1463,
-    1469,  1471,  1473,  1475,  1477,  1479,  1484,  1488,  1520,  1522,
-    1528,  1534,  1547,  1548,  1549,  1554,  1559,  1563,  1567,  1582,
-    1595,  1600,  1636,  1654,  1655,  1661,  1662,  1667,  1669,  1676,
-    1693,  1710,  1712,  1719,  1724,  1732,  1742,  1754,  1763,  1767,
-    1771,  1775,  1779,  1783,  1786,  1788,  1792,  1796,  1800
+    1395,  1397,  1399,  1401,  1403,  1405,  1419,  1424,  1429,  1454,
+    1460,  1462,  1464,  1466,  1468,  1470,  1475,  1479,  1511,  1513,
+    1519,  1525,  1538,  1539,  1540,  1545,  1550,  1554,  1558,  1573,
+    1586,  1591,  1627,  1645,  1646,  1652,  1653,  1658,  1660,  1667,
+    1684,  1701,  1703,  1710,  1715,  1723,  1733,  1745,  1754,  1758,
+    1762,  1766,  1770,  1774,  1777,  1779,  1783,  1787,  1791
 };
 #endif
 
@@ -795,13 +704,13 @@ static const char *const yytname[] =
   "func_call", "direct_func_call", "opt_variable", "delete_subscript_list",
   "delete_subscript", "delete_exp_list", "bracketed_exp_list", "subscript",
   "subscript_list", "simple_variable", "variable", "opt_incdec", "l_brace",
-  "r_brace", "r_paren", "opt_semi", "semi", "colon", "comma", YY_NULL
+  "r_brace", "r_paren", "opt_semi", "semi", "colon", "comma", YY_NULLPTR
 };
 #endif
 
 # ifdef YYPRINT
-/* YYTOKNUM[YYLEX-NUM] -- Internal token number corresponding to
-   token YYLEX-NUM.  */
+/* YYTOKNUM[NUM] -- (External) token number corresponding to the
+   (internal) symbol number NUM (which must be that of a token).  */
 static const yytype_uint16 yytoknum[] =
 {
        0,   256,   257,   258,   259,   260,   261,   262,   263,   264,
@@ -815,110 +724,18 @@ static const yytype_uint16 yytoknum[] =
 };
 # endif
 
-/* YYR1[YYN] -- Symbol number of symbol that rule YYN derives.  */
-static const yytype_uint8 yyr1[] =
-{
-       0,    75,    76,    76,    76,    76,    76,    77,    77,    77,
-      77,    77,    78,    78,    78,    79,    79,    79,    80,    80,
-      80,    80,    80,    80,    80,    81,    82,    82,    82,    82,
-      83,    83,    84,    86,    85,    87,    87,    88,    88,    88,
-      89,    89,    90,    90,    90,    90,    90,    90,    90,    90,
-      90,    90,    91,    91,    91,    91,    91,    92,    91,    91,
-      94,    93,    95,    93,    93,    93,    96,    96,    97,    97,
-      97,    98,    98,    99,    99,    99,    99,    99,   100,   100,
-     101,   101,   102,   103,   102,   104,   104,   105,   105,   106,
-     106,   107,   107,   108,   108,   109,   109,   109,   109,   109,
-     110,   110,   111,   111,   112,   112,   112,   112,   112,   112,
-     113,   113,   113,   113,   113,   113,   113,   113,   114,   114,
-     114,   115,   115,   116,   116,   117,   117,   117,   118,   118,
-     118,   118,   118,   118,   118,   118,   118,   118,   118,   119,
-     119,   119,   119,   119,   119,   119,   120,   120,   120,   120,
-     120,   120,   120,   120,   120,   120,   120,   120,   120,   120,
-     121,   121,   122,   123,   123,   124,   124,   125,   125,   126,
-     127,   128,   128,   129,   130,   130,   131,   131,   132,   132,
-     132,   133,   134,   135,   136,   136,   137,   138,   139
-};
+#define YYPACT_NINF -273
 
-/* YYR2[YYN] -- Number of symbols composing right hand side of rule YYN.  */
-static const yytype_uint8 yyr2[] =
-{
-       0,     2,     0,     2,     2,     2,     2,     2,     2,     2,
-       4,     4,     1,     2,     1,     1,     2,     1,     0,     1,
-       4,     1,     1,     1,     1,     5,     1,     1,     1,     2,
-       1,     1,     6,     0,     3,     1,     1,     0,     2,     2,
-       1,     2,     2,     3,     1,     9,     6,     8,     8,    12,
-      11,     1,     2,     2,     2,     2,     3,     0,     4,     2,
-       0,     4,     0,     4,     4,     1,     0,     1,     0,     2,
-       2,     5,     4,     1,     2,     2,     1,     1,     1,     1,
-       1,     3,     0,     0,     3,     6,     9,     1,     2,     0,
-       1,     0,     2,     0,     1,     1,     3,     1,     2,     3,
-       0,     1,     0,     1,     1,     3,     1,     2,     3,     3,
-       3,     3,     3,     3,     3,     3,     5,     1,     1,     1,
-       2,     1,     1,     1,     1,     1,     1,     2,     1,     3,
-       3,     3,     3,     3,     3,     3,     2,     2,     5,     4,
-       3,     3,     3,     3,     3,     3,     1,     2,     3,     4,
-       4,     1,     1,     1,     2,     2,     1,     1,     2,     2,
-       1,     2,     4,     0,     1,     0,     2,     1,     2,     1,
-       3,     1,     2,     2,     1,     2,     1,     3,     1,     1,
-       0,     2,     2,     1,     0,     1,     1,     1,     2
-};
+#define yypact_value_is_default(Yystate) \
+  (!!((Yystate) == (-273)))
 
-/* YYDEFACT[STATE-NAME] -- Default reduction number in state STATE-NUM.
-   Performed when YYTABLE doesn't specify something else to do.  Zero
-   means the default is an error.  */
-static const yytype_uint8 yydefact[] =
-{
-       2,     0,     1,     6,     0,   174,   156,   157,    21,    22,
-       0,    23,    24,   163,     0,     0,     0,   151,     5,    87,
-      36,     0,     0,    35,     0,     0,     0,     0,     3,     0,
-       0,   146,    33,     4,    19,   117,   125,   126,   128,   152,
-     160,   176,   153,     0,     0,   171,     0,   175,    27,    26,
-      30,    31,     0,     0,    28,    91,   164,   154,   155,     0,
-       0,     0,   159,   153,   158,   147,     0,   180,   153,   106,
-       0,   104,     0,     0,   161,    89,   186,     7,     8,    40,
-      37,    89,     9,     0,    88,   121,     0,     0,     0,     0,
-       0,    89,   122,   124,   123,     0,     0,   127,     0,     0,
-       0,     0,     0,     0,     0,     0,     0,     0,     0,     0,
-     119,   118,   136,   137,     0,     0,     0,     0,   104,     0,
-     173,   172,    29,     0,     0,   135,     0,     0,     0,   178,
-     179,   177,   107,    89,   183,     0,     0,   148,    14,     0,
-       0,    17,     0,     0,    90,   181,     0,    41,    34,   113,
-     114,   111,   112,     0,     0,   115,   163,   133,   134,   130,
-     131,   132,   129,   144,   145,   141,   142,   143,   140,   120,
-     110,   162,   170,    97,    95,     0,     0,    92,   149,   150,
-     108,   188,     0,   109,   105,    13,    10,    16,    11,    39,
-       0,    57,     0,     0,     0,    89,     0,     0,     0,    78,
-      79,     0,   100,     0,    89,    38,    51,     0,    60,    44,
-      65,    37,   184,    89,     0,    20,   139,    89,    98,     0,
-     138,     0,   100,    62,     0,     0,     0,     0,    66,    52,
-      53,    54,     0,   101,    55,   182,    59,     0,     0,    89,
-     185,    42,   116,    32,    99,    96,     0,     0,   165,     0,
-       0,     0,     0,   174,    67,     0,    56,     0,    82,    80,
-      43,    25,    89,    58,    63,     0,   167,   169,    64,    89,
-      89,     0,     0,    89,     0,    83,    61,     0,   166,   168,
-       0,     0,     0,     0,     0,    81,     0,    85,    68,    46,
-       0,    89,     0,    89,    84,    89,     0,    89,     0,    89,
-      66,     0,    70,     0,     0,    69,     0,    47,    48,    66,
-       0,    86,    73,    76,     0,     0,    77,     0,   187,    89,
-      45,     0,    89,    75,    74,    89,    37,    89,     0,    37,
-       0,     0,    50,     0,    49
-};
+#define YYTABLE_NINF -104
 
-/* YYDEFGOTO[NTERM-NUM].  */
-static const yytype_int16 yydefgoto[] =
-{
-      -1,     1,    28,   140,   143,    29,    77,    53,    54,    30,
-      31,    83,    32,   146,    78,   205,   206,   222,   207,   237,
-     248,   255,   296,   305,   317,   208,   258,   276,   286,   209,
-     144,   145,   125,   175,   176,   232,   116,   117,   210,   115,
-      94,    95,    35,    36,    37,    38,    39,    40,    55,   264,
-     265,   266,    45,    46,    47,    41,    42,   131,   211,   212,
-     137,   239,   213,   319,   136
-};
+#define yytable_value_is_error(Yytable_value) \
+  (!!((Yytable_value) == (-104)))
 
-/* YYPACT[STATE-NUM] -- Index in YYTABLE of the portion describing
-   STATE-NUM.  */
-#define YYPACT_NINF -273
+  /* YYPACT[STATE-NUM] -- Index in YYTABLE of the portion describing
+     STATE-NUM.  */
 static const yytype_int16 yypact[] =
 {
     -273,   376,  -273,  -273,   -27,   -21,  -273,  -273,  -273,  -273,
@@ -957,7 +774,48 @@ static const yytype_int16 yypact[] =
      448,   710,  -273,   522,  -273
 };
 
-/* YYPGOTO[NTERM-NUM].  */
+  /* YYDEFACT[STATE-NUM] -- Default reduction number in state STATE-NUM.
+     Performed when YYTABLE does not specify something else to do.  Zero
+     means the default is an error.  */
+static const yytype_uint8 yydefact[] =
+{
+       2,     0,     1,     6,     0,   174,   156,   157,    21,    22,
+       0,    23,    24,   163,     0,     0,     0,   151,     5,    87,
+      36,     0,     0,    35,     0,     0,     0,     0,     3,     0,
+       0,   146,    33,     4,    19,   117,   125,   126,   128,   152,
+     160,   176,   153,     0,     0,   171,     0,   175,    27,    26,
+      30,    31,     0,     0,    28,    91,   164,   154,   155,     0,
+       0,     0,   159,   153,   158,   147,     0,   180,   153,   106,
+       0,   104,     0,     0,   161,    89,   186,     7,     8,    40,
+      37,    89,     9,     0,    88,   121,     0,     0,     0,     0,
+       0,    89,   122,   124,   123,     0,     0,   127,     0,     0,
+       0,     0,     0,     0,     0,     0,     0,     0,     0,     0,
+     119,   118,   136,   137,     0,     0,     0,     0,   104,     0,
+     173,   172,    29,     0,     0,   135,     0,     0,     0,   178,
+     179,   177,   107,    89,   183,     0,     0,   148,    14,     0,
+       0,    17,     0,     0,    90,   181,     0,    41,    34,   113,
+     114,   111,   112,     0,     0,   115,   163,   133,   134,   130,
+     131,   132,   129,   144,   145,   141,   142,   143,   140,   120,
+     110,   162,   170,    97,    95,     0,     0,    92,   149,   150,
+     108,   188,     0,   109,   105,    13,    10,    16,    11,    39,
+       0,    57,     0,     0,     0,    89,     0,     0,     0,    78,
+      79,     0,   100,     0,    89,    38,    51,     0,    60,    44,
+      65,    37,   184,    89,     0,    20,   139,    89,    98,     0,
+     138,     0,   100,    62,     0,     0,     0,     0,    66,    52,
+      53,    54,     0,   101,    55,   182,    59,     0,     0,    89,
+     185,    42,   116,    32,    99,    96,     0,     0,   165,     0,
+       0,     0,     0,   174,    67,     0,    56,     0,    82,    80,
+      43,    25,    89,    58,    63,     0,   167,   169,    64,    89,
+      89,     0,     0,    89,     0,    83,    61,     0,   166,   168,
+       0,     0,     0,     0,     0,    81,     0,    85,    68,    46,
+       0,    89,     0,    89,    84,    89,     0,    89,     0,    89,
+      66,     0,    70,     0,     0,    69,     0,    47,    48,    66,
+       0,    86,    73,    76,     0,     0,    77,     0,   187,    89,
+      45,     0,    89,    75,    74,    89,    37,    89,     0,    37,
+       0,     0,    50,     0,    49
+};
+
+  /* YYPGOTO[NTERM-NUM].  */
 static const yytype_int16 yypgoto[] =
 {
     -273,  -273,  -273,  -273,  -273,  -273,   208,  -273,  -273,  -273,
@@ -969,10 +827,21 @@ static const yytype_int16 yypgoto[] =
      -46,  -273,   -25,   -57,    85
 };
 
-/* YYTABLE[YYPACT[STATE-NUM]].  What to do in state STATE-NUM.  If
-   positive, shift that token.  If negative, reduce the rule which
-   number is the opposite.  If YYTABLE_NINF, syntax error.  */
-#define YYTABLE_NINF -104
+  /* YYDEFGOTO[NTERM-NUM].  */
+static const yytype_int16 yydefgoto[] =
+{
+      -1,     1,    28,   140,   143,    29,    77,    53,    54,    30,
+      31,    83,    32,   146,    78,   205,   206,   222,   207,   237,
+     248,   255,   296,   305,   317,   208,   258,   276,   286,   209,
+     144,   145,   125,   175,   176,   232,   116,   117,   210,   115,
+      94,    95,    35,    36,    37,    38,    39,    40,    55,   264,
+     265,   266,    45,    46,    47,    41,    42,   131,   211,   212,
+     137,   239,   213,   319,   136
+};
+
+  /* YYTABLE[YYPACT[STATE-NUM]] -- What to do in state STATE-NUM.  If
+     positive, shift that token.  If negative, reduce the rule whose
+     number is the opposite.  If YYTABLE_NINF, syntax error.  */
 static const yytype_int16 yytable[] =
 {
       34,    80,    80,    70,    81,   126,   127,   260,   121,   238,
@@ -1093,12 +962,6 @@ static const yytype_int16 yytable[] =
        0,    90,   214,     0,    92,    93
 };
 
-#define yypact_value_is_default(Yystate) \
-  (!!((Yystate) == (-273)))
-
-#define yytable_value_is_error(Yytable_value) \
-  (!!((Yytable_value) == (-104)))
-
 static const yytype_int16 yycheck[] =
 {
        1,    29,    30,    26,    29,    59,    60,   238,    46,   211,
@@ -1219,8 +1082,8 @@ static const yytype_int16 yycheck[] =
       -1,    53,    54,    -1,    56,    57
 };
 
-/* YYSTOS[STATE-NUM] -- The (internal number of the) accessing
-   symbol of state STATE-NUM.  */
+  /* YYSTOS[STATE-NUM] -- The (internal number of the) accessing
+     symbol of state STATE-NUM.  */
 static const yytype_uint8 yystos[] =
 {
        0,    76,     0,     1,     3,     4,     7,     8,    17,    18,
@@ -1259,30 +1122,64 @@ static const yytype_uint8 yystos[] =
       88,   106,    90,    88,    90
 };
 
-#define yyerrok		(yyerrstatus = 0)
-#define yyclearin	(yychar = YYEMPTY)
-#define YYEMPTY		(-2)
-#define YYEOF		0
-
-#define YYACCEPT	goto yyacceptlab
-#define YYABORT		goto yyabortlab
-#define YYERROR		goto yyerrorlab
-
-
-/* Like YYERROR except do call yyerror.  This remains here temporarily
-   to ease the transition to the new meaning of YYERROR, for GCC.
-   Once GCC version 2 has supplanted version 1, this can go.  However,
-   YYFAIL appears to be in use.  Nevertheless, it is formally deprecated
-   in Bison 2.4.2's NEWS entry, where a plan to phase it out is
-   discussed.  */
-
-#define YYFAIL		goto yyerrlab
-#if defined YYFAIL
-  /* This is here to suppress warnings from the GCC cpp's
-     -Wunused-macros.  Normally we don't worry about that warning, but
-     some users do, and we want to make it easy for users to remove
-     YYFAIL uses, which will produce warnings from Bison 2.5.  */
-#endif
+  /* YYR1[YYN] -- Symbol number of symbol that rule YYN derives.  */
+static const yytype_uint8 yyr1[] =
+{
+       0,    75,    76,    76,    76,    76,    76,    77,    77,    77,
+      77,    77,    78,    78,    78,    79,    79,    79,    80,    80,
+      80,    80,    80,    80,    80,    81,    82,    82,    82,    82,
+      83,    83,    84,    86,    85,    87,    87,    88,    88,    88,
+      89,    89,    90,    90,    90,    90,    90,    90,    90,    90,
+      90,    90,    91,    91,    91,    91,    91,    92,    91,    91,
+      94,    93,    95,    93,    93,    93,    96,    96,    97,    97,
+      97,    98,    98,    99,    99,    99,    99,    99,   100,   100,
+     101,   101,   102,   103,   102,   104,   104,   105,   105,   106,
+     106,   107,   107,   108,   108,   109,   109,   109,   109,   109,
+     110,   110,   111,   111,   112,   112,   112,   112,   112,   112,
+     113,   113,   113,   113,   113,   113,   113,   113,   114,   114,
+     114,   115,   115,   116,   116,   117,   117,   117,   118,   118,
+     118,   118,   118,   118,   118,   118,   118,   118,   118,   119,
+     119,   119,   119,   119,   119,   119,   120,   120,   120,   120,
+     120,   120,   120,   120,   120,   120,   120,   120,   120,   120,
+     121,   121,   122,   123,   123,   124,   124,   125,   125,   126,
+     127,   128,   128,   129,   130,   130,   131,   131,   132,   132,
+     132,   133,   134,   135,   136,   136,   137,   138,   139
+};
+
+  /* YYR2[YYN] -- Number of symbols on the right hand side of rule YYN.  */
+static const yytype_uint8 yyr2[] =
+{
+       0,     2,     0,     2,     2,     2,     2,     2,     2,     2,
+       4,     4,     1,     2,     1,     1,     2,     1,     0,     1,
+       4,     1,     1,     1,     1,     5,     1,     1,     1,     2,
+       1,     1,     6,     0,     3,     1,     1,     0,     2,     2,
+       1,     2,     2,     3,     1,     9,     6,     8,     8,    12,
+      11,     1,     2,     2,     2,     2,     3,     0,     4,     2,
+       0,     4,     0,     4,     4,     1,     0,     1,     0,     2,
+       2,     5,     4,     1,     2,     2,     1,     1,     1,     1,
+       1,     3,     0,     0,     3,     6,     9,     1,     2,     0,
+       1,     0,     2,     0,     1,     1,     3,     1,     2,     3,
+       0,     1,     0,     1,     1,     3,     1,     2,     3,     3,
+       3,     3,     3,     3,     3,     3,     5,     1,     1,     1,
+       2,     1,     1,     1,     1,     1,     1,     2,     1,     3,
+       3,     3,     3,     3,     3,     3,     2,     2,     5,     4,
+       3,     3,     3,     3,     3,     3,     1,     2,     3,     4,
+       4,     1,     1,     1,     2,     2,     1,     1,     2,     2,
+       1,     2,     4,     0,     1,     0,     2,     1,     2,     1,
+       3,     1,     2,     2,     1,     2,     1,     3,     1,     1,
+       0,     2,     2,     1,     0,     1,     1,     1,     2
+};
+
+
+#define yyerrok         (yyerrstatus = 0)
+#define yyclearin       (yychar = YYEMPTY)
+#define YYEMPTY         (-2)
+#define YYEOF           0
+
+#define YYACCEPT        goto yyacceptlab
+#define YYABORT         goto yyabortlab
+#define YYERROR         goto yyerrorlab
+
 
 #define YYRECOVERING()  (!!yyerrstatus)
 
@@ -1299,27 +1196,15 @@ do                                                              \
   else                                                          \
     {                                                           \
       yyerror (YY_("syntax error: cannot back up")); \
-      YYERROR;							\
-    }								\
-while (YYID (0))
+      YYERROR;                                                  \
+    }                                                           \
+while (0)
 
 /* Error token number */
-#define YYTERROR	1
-#define YYERRCODE	256
-
-
-/* This macro is provided for backward compatibility. */
-#ifndef YY_LOCATION_PRINT
-# define YY_LOCATION_PRINT(File, Loc) ((void) 0)
-#endif
+#define YYTERROR        1
+#define YYERRCODE       256
 
 
-/* YYLEX -- calling `yylex' with the right arguments.  */
-#ifdef YYLEX_PARAM
-# define YYLEX yylex (YYLEX_PARAM)
-#else
-# define YYLEX yylex ()
-#endif
 
 /* Enable debugging if requested.  */
 #if YYDEBUG
@@ -1329,40 +1214,36 @@ while (YYID (0))
 #  define YYFPRINTF fprintf
 # endif
 
-# define YYDPRINTF(Args)			\
-do {						\
-  if (yydebug)					\
-    YYFPRINTF Args;				\
-} while (YYID (0))
+# define YYDPRINTF(Args)                        \
+do {                                            \
+  if (yydebug)                                  \
+    YYFPRINTF Args;                             \
+} while (0)
+
+/* This macro is provided for backward compatibility. */
+#ifndef YY_LOCATION_PRINT
+# define YY_LOCATION_PRINT(File, Loc) ((void) 0)
+#endif
+
 
-# define YY_SYMBOL_PRINT(Title, Type, Value, Location)			  \
-do {									  \
-  if (yydebug)								  \
-    {									  \
-      YYFPRINTF (stderr, "%s ", Title);					  \
-      yy_symbol_print (stderr,						  \
-		  Type, Value); \
-      YYFPRINTF (stderr, "\n");						  \
-    }									  \
-} while (YYID (0))
+# define YY_SYMBOL_PRINT(Title, Type, Value, Location)                    \
+do {                                                                      \
+  if (yydebug)                                                            \
+    {                                                                     \
+      YYFPRINTF (stderr, "%s ", Title);                                   \
+      yy_symbol_print (stderr,                                            \
+                  Type, Value); \
+      YYFPRINTF (stderr, "\n");                                           \
+    }                                                                     \
+} while (0)
 
 
-/*--------------------------------.
-| Print this symbol on YYOUTPUT.  |
-`--------------------------------*/
+/*----------------------------------------.
+| Print this symbol's value on YYOUTPUT.  |
+`----------------------------------------*/
 
-/*ARGSUSED*/
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static void
 yy_symbol_value_print (FILE *yyoutput, int yytype, YYSTYPE const * const yyvaluep)
-#else
-static void
-yy_symbol_value_print (yyoutput, yytype, yyvaluep)
-    FILE *yyoutput;
-    int yytype;
-    YYSTYPE const * const yyvaluep;
-#endif
 {
   FILE *yyo = yyoutput;
   YYUSE (yyo);
@@ -1371,8 +1252,6 @@ yy_symbol_value_print (yyoutput, yytype, yyvaluep)
 # ifdef YYPRINT
   if (yytype < YYNTOKENS)
     YYPRINT (yyoutput, yytoknum[yytype], *yyvaluep);
-# else
-  YYUSE (yyoutput);
 # endif
   YYUSE (yytype);
 }
@@ -1382,22 +1261,11 @@ yy_symbol_value_print (yyoutput, yytype, yyvaluep)
 | Print this symbol on YYOUTPUT.  |
 `--------------------------------*/
 
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static void
 yy_symbol_print (FILE *yyoutput, int yytype, YYSTYPE const * const yyvaluep)
-#else
-static void
-yy_symbol_print (yyoutput, yytype, yyvaluep)
-    FILE *yyoutput;
-    int yytype;
-    YYSTYPE const * const yyvaluep;
-#endif
 {
-  if (yytype < YYNTOKENS)
-    YYFPRINTF (yyoutput, "token %s (", yytname[yytype]);
-  else
-    YYFPRINTF (yyoutput, "nterm %s (", yytname[yytype]);
+  YYFPRINTF (yyoutput, "%s %s (",
+             yytype < YYNTOKENS ? "token" : "nterm", yytname[yytype]);
 
   yy_symbol_value_print (yyoutput, yytype, yyvaluep);
   YYFPRINTF (yyoutput, ")");
@@ -1408,16 +1276,8 @@ yy_symbol_print (yyoutput, yytype, yyvaluep)
 | TOP (included).                                                   |
 `------------------------------------------------------------------*/
 
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static void
 yy_stack_print (yytype_int16 *yybottom, yytype_int16 *yytop)
-#else
-static void
-yy_stack_print (yybottom, yytop)
-    yytype_int16 *yybottom;
-    yytype_int16 *yytop;
-#endif
 {
   YYFPRINTF (stderr, "Stack now");
   for (; yybottom <= yytop; yybottom++)
@@ -1428,49 +1288,42 @@ yy_stack_print (yybottom, yytop)
   YYFPRINTF (stderr, "\n");
 }
 
-# define YY_STACK_PRINT(Bottom, Top)				\
-do {								\
-  if (yydebug)							\
-    yy_stack_print ((Bottom), (Top));				\
-} while (YYID (0))
+# define YY_STACK_PRINT(Bottom, Top)                            \
+do {                                                            \
+  if (yydebug)                                                  \
+    yy_stack_print ((Bottom), (Top));                           \
+} while (0)
 
 
 /*------------------------------------------------.
 | Report that the YYRULE is going to be reduced.  |
 `------------------------------------------------*/
 
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-static void
-yy_reduce_print (YYSTYPE *yyvsp, int yyrule)
-#else
 static void
-yy_reduce_print (yyvsp, yyrule)
-    YYSTYPE *yyvsp;
-    int yyrule;
-#endif
+yy_reduce_print (yytype_int16 *yyssp, YYSTYPE *yyvsp, int yyrule)
 {
+  unsigned long int yylno = yyrline[yyrule];
   int yynrhs = yyr2[yyrule];
   int yyi;
-  unsigned long int yylno = yyrline[yyrule];
   YYFPRINTF (stderr, "Reducing stack by rule %d (line %lu):\n",
-	     yyrule - 1, yylno);
+             yyrule - 1, yylno);
   /* The symbols being reduced.  */
   for (yyi = 0; yyi < yynrhs; yyi++)
     {
       YYFPRINTF (stderr, "   $%d = ", yyi + 1);
-      yy_symbol_print (stderr, yyrhs[yyprhs[yyrule] + yyi],
-		       &(yyvsp[(yyi + 1) - (yynrhs)])
-		       		       );
+      yy_symbol_print (stderr,
+                       yystos[yyssp[yyi + 1 - yynrhs]],
+                       &(yyvsp[(yyi + 1) - (yynrhs)])
+                                              );
       YYFPRINTF (stderr, "\n");
     }
 }
 
-# define YY_REDUCE_PRINT(Rule)		\
-do {					\
-  if (yydebug)				\
-    yy_reduce_print (yyvsp, Rule); \
-} while (YYID (0))
+# define YY_REDUCE_PRINT(Rule)          \
+do {                                    \
+  if (yydebug)                          \
+    yy_reduce_print (yyssp, yyvsp, Rule); \
+} while (0)
 
 /* Nonzero means print parse trace.  It is left uninitialized so that
    multiple parsers can coexist.  */
@@ -1484,7 +1337,7 @@ int yydebug;
 
 
 /* YYINITDEPTH -- initial size of the parser's stacks.  */
-#ifndef	YYINITDEPTH
+#ifndef YYINITDEPTH
 # define YYINITDEPTH 200
 #endif
 
@@ -1507,15 +1360,8 @@ int yydebug;
 #   define yystrlen strlen
 #  else
 /* Return the length of YYSTR.  */
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static YYSIZE_T
 yystrlen (const char *yystr)
-#else
-static YYSIZE_T
-yystrlen (yystr)
-    const char *yystr;
-#endif
 {
   YYSIZE_T yylen;
   for (yylen = 0; yystr[yylen]; yylen++)
@@ -1531,16 +1377,8 @@ yystrlen (yystr)
 #  else
 /* Copy YYSRC to YYDEST, returning the address of the terminating '\0' in
    YYDEST.  */
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static char *
 yystpcpy (char *yydest, const char *yysrc)
-#else
-static char *
-yystpcpy (yydest, yysrc)
-    char *yydest;
-    const char *yysrc;
-#endif
 {
   char *yyd = yydest;
   const char *yys = yysrc;
@@ -1570,27 +1408,27 @@ yytnamerr (char *yyres, const char *yystr)
       char const *yyp = yystr;
 
       for (;;)
-	switch (*++yyp)
-	  {
-	  case '\'':
-	  case ',':
-	    goto do_not_strip_quotes;
-
-	  case '\\':
-	    if (*++yyp != '\\')
-	      goto do_not_strip_quotes;
-	    /* Fall through.  */
-	  default:
-	    if (yyres)
-	      yyres[yyn] = *yyp;
-	    yyn++;
-	    break;
-
-	  case '"':
-	    if (yyres)
-	      yyres[yyn] = '\0';
-	    return yyn;
-	  }
+        switch (*++yyp)
+          {
+          case '\'':
+          case ',':
+            goto do_not_strip_quotes;
+
+          case '\\':
+            if (*++yyp != '\\')
+              goto do_not_strip_quotes;
+            /* Fall through.  */
+          default:
+            if (yyres)
+              yyres[yyn] = *yyp;
+            yyn++;
+            break;
+
+          case '"':
+            if (yyres)
+              yyres[yyn] = '\0';
+            return yyn;
+          }
     do_not_strip_quotes: ;
     }
 
@@ -1613,11 +1451,11 @@ static int
 yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
                 yytype_int16 *yyssp, int yytoken)
 {
-  YYSIZE_T yysize0 = yytnamerr (YY_NULL, yytname[yytoken]);
+  YYSIZE_T yysize0 = yytnamerr (YY_NULLPTR, yytname[yytoken]);
   YYSIZE_T yysize = yysize0;
   enum { YYERROR_VERBOSE_ARGS_MAXIMUM = 5 };
   /* Internationalized format string. */
-  const char *yyformat = YY_NULL;
+  const char *yyformat = YY_NULLPTR;
   /* Arguments of yyformat. */
   char const *yyarg[YYERROR_VERBOSE_ARGS_MAXIMUM];
   /* Number of reported tokens (one for the "unexpected", one per
@@ -1625,10 +1463,6 @@ yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
   int yycount = 0;
 
   /* There are many possibilities here to consider:
-     - Assume YYFAIL is not used.  It's too flawed to consider.  See
-       <http://lists.gnu.org/archive/html/bison-patches/2009-12/msg00024.html>
-       for details.  YYERROR is fine as it does not invoke this
-       function.
      - If this state is a consistent state with a default action, then
        the only way this function was invoked is if the default action
        is an error action.  In that case, don't check for expected
@@ -1678,7 +1512,7 @@ yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
                   }
                 yyarg[yycount++] = yytname[yyx];
                 {
-                  YYSIZE_T yysize1 = yysize + yytnamerr (YY_NULL, yytname[yyx]);
+                  YYSIZE_T yysize1 = yysize + yytnamerr (YY_NULLPTR, yytname[yyx]);
                   if (! (yysize <= yysize1
                          && yysize1 <= YYSTACK_ALLOC_MAXIMUM))
                     return 2;
@@ -1745,26 +1579,17 @@ yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
 | Release the memory associated to this symbol.  |
 `-----------------------------------------------*/
 
-/*ARGSUSED*/
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static void
 yydestruct (const char *yymsg, int yytype, YYSTYPE *yyvaluep)
-#else
-static void
-yydestruct (yymsg, yytype, yyvaluep)
-    const char *yymsg;
-    int yytype;
-    YYSTYPE *yyvaluep;
-#endif
 {
   YYUSE (yyvaluep);
-
   if (!yymsg)
     yymsg = "Deleting";
   YY_SYMBOL_PRINT (yymsg, yytype, yyvaluep, yylocationp);
 
+  YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
   YYUSE (yytype);
+  YY_IGNORE_MAYBE_UNINITIALIZED_END
 }
 
 
@@ -1773,18 +1598,8 @@ yydestruct (yymsg, yytype, yyvaluep)
 /* The lookahead symbol.  */
 int yychar;
 
-
-#ifndef YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
-# define YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
-# define YY_IGNORE_MAYBE_UNINITIALIZED_END
-#endif
-#ifndef YY_INITIAL_VALUE
-# define YY_INITIAL_VALUE(Value) /* Nothing. */
-#endif
-
 /* The semantic value of the lookahead symbol.  */
-YYSTYPE yylval YY_INITIAL_VALUE(yyval_default);
-
+YYSTYPE yylval;
 /* Number of syntax errors so far.  */
 int yynerrs;
 
@@ -1793,35 +1608,16 @@ int yynerrs;
 | yyparse.  |
 `----------*/
 
-#ifdef YYPARSE_PARAM
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-int
-yyparse (void *YYPARSE_PARAM)
-#else
-int
-yyparse (YYPARSE_PARAM)
-    void *YYPARSE_PARAM;
-#endif
-#else /* ! YYPARSE_PARAM */
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 int
 yyparse (void)
-#else
-int
-yyparse ()
-
-#endif
-#endif
 {
     int yystate;
     /* Number of tokens to shift before error messages enabled.  */
     int yyerrstatus;
 
     /* The stacks and their tools:
-       `yyss': related to states.
-       `yyvs': related to semantic values.
+       'yyss': related to states.
+       'yyvs': related to semantic values.
 
        Refer to the stacks through separate pointers, to allow yyoverflow
        to reallocate them elsewhere.  */
@@ -1889,23 +1685,23 @@ yyparse ()
 
 #ifdef yyoverflow
       {
-	/* Give user a chance to reallocate the stack.  Use copies of
-	   these so that the &'s don't force the real ones into
-	   memory.  */
-	YYSTYPE *yyvs1 = yyvs;
-	yytype_int16 *yyss1 = yyss;
-
-	/* Each stack pointer address is followed by the size of the
-	   data in use in that stack, in bytes.  This used to be a
-	   conditional around just the two extra args, but that might
-	   be undefined if yyoverflow is a macro.  */
-	yyoverflow (YY_("memory exhausted"),
-		    &yyss1, yysize * sizeof (*yyssp),
-		    &yyvs1, yysize * sizeof (*yyvsp),
-		    &yystacksize);
-
-	yyss = yyss1;
-	yyvs = yyvs1;
+        /* Give user a chance to reallocate the stack.  Use copies of
+           these so that the &'s don't force the real ones into
+           memory.  */
+        YYSTYPE *yyvs1 = yyvs;
+        yytype_int16 *yyss1 = yyss;
+
+        /* Each stack pointer address is followed by the size of the
+           data in use in that stack, in bytes.  This used to be a
+           conditional around just the two extra args, but that might
+           be undefined if yyoverflow is a macro.  */
+        yyoverflow (YY_("memory exhausted"),
+                    &yyss1, yysize * sizeof (*yyssp),
+                    &yyvs1, yysize * sizeof (*yyvsp),
+                    &yystacksize);
+
+        yyss = yyss1;
+        yyvs = yyvs1;
       }
 #else /* no yyoverflow */
 # ifndef YYSTACK_RELOCATE
@@ -1913,22 +1709,22 @@ yyparse ()
 # else
       /* Extend the stack our own way.  */
       if (YYMAXDEPTH <= yystacksize)
-	goto yyexhaustedlab;
+        goto yyexhaustedlab;
       yystacksize *= 2;
       if (YYMAXDEPTH < yystacksize)
-	yystacksize = YYMAXDEPTH;
+        yystacksize = YYMAXDEPTH;
 
       {
-	yytype_int16 *yyss1 = yyss;
-	union yyalloc *yyptr =
-	  (union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize));
-	if (! yyptr)
-	  goto yyexhaustedlab;
-	YYSTACK_RELOCATE (yyss_alloc, yyss);
-	YYSTACK_RELOCATE (yyvs_alloc, yyvs);
+        yytype_int16 *yyss1 = yyss;
+        union yyalloc *yyptr =
+          (union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize));
+        if (! yyptr)
+          goto yyexhaustedlab;
+        YYSTACK_RELOCATE (yyss_alloc, yyss);
+        YYSTACK_RELOCATE (yyvs_alloc, yyvs);
 #  undef YYSTACK_RELOCATE
-	if (yyss1 != yyssa)
-	  YYSTACK_FREE (yyss1);
+        if (yyss1 != yyssa)
+          YYSTACK_FREE (yyss1);
       }
 # endif
 #endif /* no yyoverflow */
@@ -1937,10 +1733,10 @@ yyparse ()
       yyvsp = yyvs + yysize - 1;
 
       YYDPRINTF ((stderr, "Stack size increased to %lu\n",
-		  (unsigned long int) yystacksize));
+                  (unsigned long int) yystacksize));
 
       if (yyss + yystacksize - 1 <= yyssp)
-	YYABORT;
+        YYABORT;
     }
 
   YYDPRINTF ((stderr, "Entering state %d\n", yystate));
@@ -1969,7 +1765,7 @@ yybackup:
   if (yychar == YYEMPTY)
     {
       YYDPRINTF ((stderr, "Reading a token: "));
-      yychar = YYLEX;
+      yychar = yylex ();
     }
 
   if (yychar <= YYEOF)
@@ -2034,7 +1830,7 @@ yyreduce:
   yylen = yyr2[yyn];
 
   /* If YYLEN is nonzero, implement the default value of the action:
-     `$$ = $1'.
+     '$$ = $1'.
 
      Otherwise, the following line sets YYVAL to garbage.
      This behavior is undocumented and Bison
@@ -2048,27 +1844,26 @@ yyreduce:
   switch (yyn)
     {
         case 3:
-/* Line 1787 of yacc.c  */
-#line 203 "awkgram.y"
+#line 203 "awkgram.y" /* yacc.c:1646  */
     {
 		rule = 0;
 		yyerrok;
 	  }
+#line 1853 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 5:
-/* Line 1787 of yacc.c  */
-#line 209 "awkgram.y"
+#line 209 "awkgram.y" /* yacc.c:1646  */
     {
 		next_sourcefile();
 		if (sourcefile == srcfiles)
 			process_deferred();
 	  }
+#line 1863 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 6:
-/* Line 1787 of yacc.c  */
-#line 215 "awkgram.y"
+#line 215 "awkgram.y" /* yacc.c:1646  */
     {
 		rule = 0;
 		/*
@@ -2077,277 +1872,277 @@ yyreduce:
 		 */
   		/* yyerrok; */
 	  }
+#line 1876 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 7:
-/* Line 1787 of yacc.c  */
-#line 227 "awkgram.y"
+#line 227 "awkgram.y" /* yacc.c:1646  */
     {
-		(void) append_rule((yyvsp[(1) - (2)]), (yyvsp[(2) - (2)]));
+		(void) append_rule((yyvsp[-1]), (yyvsp[0]));
 	  }
+#line 1884 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 8:
-/* Line 1787 of yacc.c  */
-#line 231 "awkgram.y"
+#line 231 "awkgram.y" /* yacc.c:1646  */
     {
 		if (rule != Rule) {
 			msg(_("%s blocks must have an action part"), ruletab[rule]);
 			errcount++;
-		} else if ((yyvsp[(1) - (2)]) == NULL) {
+		} else if ((yyvsp[-1]) == NULL) {
 			msg(_("each rule must have a pattern or an action part"));
 			errcount++;
 		} else		/* pattern rule with non-empty pattern */
-			(void) append_rule((yyvsp[(1) - (2)]), NULL);
+			(void) append_rule((yyvsp[-1]), NULL);
 	  }
+#line 1899 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 9:
-/* Line 1787 of yacc.c  */
-#line 242 "awkgram.y"
+#line 242 "awkgram.y" /* yacc.c:1646  */
     {
 		in_function = NULL;
-		(void) mk_function((yyvsp[(1) - (2)]), (yyvsp[(2) - (2)]));
+		(void) mk_function((yyvsp[-1]), (yyvsp[0]));
 		yyerrok;
 	  }
+#line 1909 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 10:
-/* Line 1787 of yacc.c  */
-#line 248 "awkgram.y"
+#line 248 "awkgram.y" /* yacc.c:1646  */
     {
 		want_source = false;
 		yyerrok;
 	  }
+#line 1918 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 11:
-/* Line 1787 of yacc.c  */
-#line 253 "awkgram.y"
+#line 253 "awkgram.y" /* yacc.c:1646  */
     {
 		want_source = false;
 		yyerrok;
 	  }
+#line 1927 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 12:
-/* Line 1787 of yacc.c  */
-#line 261 "awkgram.y"
+#line 261 "awkgram.y" /* yacc.c:1646  */
     {
-		if (include_source((yyvsp[(1) - (1)])) < 0)
+		if (include_source((yyvsp[0])) < 0)
 			YYABORT;
-		efree((yyvsp[(1) - (1)])->lextok);
-		bcfree((yyvsp[(1) - (1)]));
+		efree((yyvsp[0])->lextok);
+		bcfree((yyvsp[0]));
 		(yyval) = NULL;
 	  }
+#line 1939 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 13:
-/* Line 1787 of yacc.c  */
-#line 269 "awkgram.y"
+#line 269 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1945 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 14:
-/* Line 1787 of yacc.c  */
-#line 271 "awkgram.y"
+#line 271 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1951 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 15:
-/* Line 1787 of yacc.c  */
-#line 276 "awkgram.y"
+#line 276 "awkgram.y" /* yacc.c:1646  */
     {
-		if (load_library((yyvsp[(1) - (1)])) < 0)
+		if (load_library((yyvsp[0])) < 0)
 			YYABORT;
-		efree((yyvsp[(1) - (1)])->lextok);
-		bcfree((yyvsp[(1) - (1)]));
+		efree((yyvsp[0])->lextok);
+		bcfree((yyvsp[0]));
 		(yyval) = NULL;
 	  }
+#line 1963 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 16:
-/* Line 1787 of yacc.c  */
-#line 284 "awkgram.y"
+#line 284 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1969 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 17:
-/* Line 1787 of yacc.c  */
-#line 286 "awkgram.y"
+#line 286 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1975 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 18:
-/* Line 1787 of yacc.c  */
-#line 291 "awkgram.y"
+#line 291 "awkgram.y" /* yacc.c:1646  */
     {	(yyval) = NULL; rule = Rule; }
+#line 1981 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 19:
-/* Line 1787 of yacc.c  */
-#line 293 "awkgram.y"
-    {	(yyval) = (yyvsp[(1) - (1)]); rule = Rule; }
+#line 293 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = (yyvsp[0]); rule = Rule; }
+#line 1987 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 20:
-/* Line 1787 of yacc.c  */
-#line 295 "awkgram.y"
+#line 295 "awkgram.y" /* yacc.c:1646  */
     {
 		INSTRUCTION *tp;
 
-		add_lint((yyvsp[(1) - (4)]), LINT_assign_in_cond);
-		add_lint((yyvsp[(4) - (4)]), LINT_assign_in_cond);
+		add_lint((yyvsp[-3]), LINT_assign_in_cond);
+		add_lint((yyvsp[0]), LINT_assign_in_cond);
 
 		tp = instruction(Op_no_op);
-		list_prepend((yyvsp[(1) - (4)]), bcalloc(Op_line_range, !!do_pretty_print + 1, 0));
-		(yyvsp[(1) - (4)])->nexti->triggered = false;
-		(yyvsp[(1) - (4)])->nexti->target_jmp = (yyvsp[(4) - (4)])->nexti;
+		list_prepend((yyvsp[-3]), bcalloc(Op_line_range, !!do_pretty_print + 1, 0));
+		(yyvsp[-3])->nexti->triggered = false;
+		(yyvsp[-3])->nexti->target_jmp = (yyvsp[0])->nexti;
 
-		list_append((yyvsp[(1) - (4)]), instruction(Op_cond_pair));
-		(yyvsp[(1) - (4)])->lasti->line_range = (yyvsp[(1) - (4)])->nexti;
-		(yyvsp[(1) - (4)])->lasti->target_jmp = tp;
+		list_append((yyvsp[-3]), instruction(Op_cond_pair));
+		(yyvsp[-3])->lasti->line_range = (yyvsp[-3])->nexti;
+		(yyvsp[-3])->lasti->target_jmp = tp;
 
-		list_append((yyvsp[(4) - (4)]), instruction(Op_cond_pair));
-		(yyvsp[(4) - (4)])->lasti->line_range = (yyvsp[(1) - (4)])->nexti;
-		(yyvsp[(4) - (4)])->lasti->target_jmp = tp;
+		list_append((yyvsp[0]), instruction(Op_cond_pair));
+		(yyvsp[0])->lasti->line_range = (yyvsp[-3])->nexti;
+		(yyvsp[0])->lasti->target_jmp = tp;
 		if (do_pretty_print) {
-			((yyvsp[(1) - (4)])->nexti + 1)->condpair_left = (yyvsp[(1) - (4)])->lasti;
-			((yyvsp[(1) - (4)])->nexti + 1)->condpair_right = (yyvsp[(4) - (4)])->lasti;
+			((yyvsp[-3])->nexti + 1)->condpair_left = (yyvsp[-3])->lasti;
+			((yyvsp[-3])->nexti + 1)->condpair_right = (yyvsp[0])->lasti;
 		}
-		(yyval) = list_append(list_merge((yyvsp[(1) - (4)]), (yyvsp[(4) - (4)])), tp);
+		(yyval) = list_append(list_merge((yyvsp[-3]), (yyvsp[0])), tp);
 		rule = Rule;
 	  }
+#line 2017 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 21:
-/* Line 1787 of yacc.c  */
-#line 321 "awkgram.y"
+#line 321 "awkgram.y" /* yacc.c:1646  */
     {
 		static int begin_seen = 0;
 		if (do_lint_old && ++begin_seen == 2)
-			warning_ln((yyvsp[(1) - (1)])->source_line,
+			warning_ln((yyvsp[0])->source_line,
 				_("old awk does not support multiple `BEGIN' or `END' rules"));
 
-		(yyvsp[(1) - (1)])->in_rule = rule = BEGIN;
-		(yyvsp[(1) - (1)])->source_file = source;
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyvsp[0])->in_rule = rule = BEGIN;
+		(yyvsp[0])->source_file = source;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2032 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 22:
-/* Line 1787 of yacc.c  */
-#line 332 "awkgram.y"
+#line 332 "awkgram.y" /* yacc.c:1646  */
     {
 		static int end_seen = 0;
 		if (do_lint_old && ++end_seen == 2)
-			warning_ln((yyvsp[(1) - (1)])->source_line,
+			warning_ln((yyvsp[0])->source_line,
 				_("old awk does not support multiple `BEGIN' or `END' rules"));
 
-		(yyvsp[(1) - (1)])->in_rule = rule = END;
-		(yyvsp[(1) - (1)])->source_file = source;
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyvsp[0])->in_rule = rule = END;
+		(yyvsp[0])->source_file = source;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2047 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 23:
-/* Line 1787 of yacc.c  */
-#line 343 "awkgram.y"
+#line 343 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (1)])->in_rule = rule = BEGINFILE;
-		(yyvsp[(1) - (1)])->source_file = source;
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyvsp[0])->in_rule = rule = BEGINFILE;
+		(yyvsp[0])->source_file = source;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2057 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 24:
-/* Line 1787 of yacc.c  */
-#line 349 "awkgram.y"
+#line 349 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (1)])->in_rule = rule = ENDFILE;
-		(yyvsp[(1) - (1)])->source_file = source;
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyvsp[0])->in_rule = rule = ENDFILE;
+		(yyvsp[0])->source_file = source;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2067 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 25:
-/* Line 1787 of yacc.c  */
-#line 358 "awkgram.y"
+#line 358 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(2) - (5)]) == NULL)
+		if ((yyvsp[-3]) == NULL)
 			(yyval) = list_create(instruction(Op_no_op));
 		else
-			(yyval) = (yyvsp[(2) - (5)]);
+			(yyval) = (yyvsp[-3]);
 	  }
+#line 2078 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 26:
-/* Line 1787 of yacc.c  */
-#line 368 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 368 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2084 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 27:
-/* Line 1787 of yacc.c  */
-#line 370 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 370 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2090 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 28:
-/* Line 1787 of yacc.c  */
-#line 372 "awkgram.y"
+#line 372 "awkgram.y" /* yacc.c:1646  */
     {
 		yyerror(_("`%s' is a built-in function, it cannot be redefined"),
 					tokstart);
 		YYABORT;
 	  }
+#line 2100 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 29:
-/* Line 1787 of yacc.c  */
-#line 378 "awkgram.y"
-    { (yyval) = (yyvsp[(2) - (2)]); }
+#line 378 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2106 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 32:
-/* Line 1787 of yacc.c  */
-#line 388 "awkgram.y"
+#line 388 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (6)])->source_file = source;
-		if (install_function((yyvsp[(2) - (6)])->lextok, (yyvsp[(1) - (6)]), (yyvsp[(4) - (6)])) < 0)
+		(yyvsp[-5])->source_file = source;
+		if (install_function((yyvsp[-4])->lextok, (yyvsp[-5]), (yyvsp[-2])) < 0)
 			YYABORT;
-		in_function = (yyvsp[(2) - (6)])->lextok;
-		(yyvsp[(2) - (6)])->lextok = NULL;
-		bcfree((yyvsp[(2) - (6)]));
+		in_function = (yyvsp[-4])->lextok;
+		(yyvsp[-4])->lextok = NULL;
+		bcfree((yyvsp[-4]));
 		/* $4 already free'd in install_function */
-		(yyval) = (yyvsp[(1) - (6)]);
+		(yyval) = (yyvsp[-5]);
 	  }
+#line 2121 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 33:
-/* Line 1787 of yacc.c  */
-#line 406 "awkgram.y"
+#line 406 "awkgram.y" /* yacc.c:1646  */
     { want_regexp = true; }
+#line 2127 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 34:
-/* Line 1787 of yacc.c  */
-#line 408 "awkgram.y"
+#line 408 "awkgram.y" /* yacc.c:1646  */
     {
 		  NODE *n, *exp;
 		  char *re;
 		  size_t len;
 
-		  re = (yyvsp[(3) - (3)])->lextok;
-		  (yyvsp[(3) - (3)])->lextok = NULL;
+		  re = (yyvsp[0])->lextok;
+		  (yyvsp[0])->lextok = NULL;
 		  len = strlen(re);
 		  if (do_lint) {
 			if (len == 0)
-				lintwarn_ln((yyvsp[(3) - (3)])->source_line,
+				lintwarn_ln((yyvsp[0])->source_line,
 					_("regexp constant `//' looks like a C++ comment, but is not"));
 			else if (re[0] == '*' && re[len-1] == '*')
 				/* possible C comment */
-				lintwarn_ln((yyvsp[(3) - (3)])->source_line,
+				lintwarn_ln((yyvsp[0])->source_line,
 					_("regexp constant `/%s/' looks like a C comment, but is not"), re);
 		  }
 
@@ -2357,73 +2152,73 @@ yyreduce:
 			unref(exp);
 			YYABORT;
 		  }
-		  (yyval) = (yyvsp[(3) - (3)]);
+		  (yyval) = (yyvsp[0]);
 		  (yyval)->opcode = Op_match_rec;
 		  (yyval)->memory = n;
 		}
+#line 2160 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 35:
-/* Line 1787 of yacc.c  */
-#line 440 "awkgram.y"
-    { bcfree((yyvsp[(1) - (1)])); }
+#line 440 "awkgram.y" /* yacc.c:1646  */
+    { bcfree((yyvsp[0])); }
+#line 2166 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 37:
-/* Line 1787 of yacc.c  */
-#line 446 "awkgram.y"
+#line 446 "awkgram.y" /* yacc.c:1646  */
     {	(yyval) = NULL; }
+#line 2172 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 38:
-/* Line 1787 of yacc.c  */
-#line 448 "awkgram.y"
+#line 448 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(2) - (2)]) == NULL)
-			(yyval) = (yyvsp[(1) - (2)]);
+		if ((yyvsp[0]) == NULL)
+			(yyval) = (yyvsp[-1]);
 		else {
-			add_lint((yyvsp[(2) - (2)]), LINT_no_effect);
-			if ((yyvsp[(1) - (2)]) == NULL)
-				(yyval) = (yyvsp[(2) - (2)]);
+			add_lint((yyvsp[0]), LINT_no_effect);
+			if ((yyvsp[-1]) == NULL)
+				(yyval) = (yyvsp[0]);
 			else
-				(yyval) = list_merge((yyvsp[(1) - (2)]), (yyvsp[(2) - (2)]));
+				(yyval) = list_merge((yyvsp[-1]), (yyvsp[0]));
 		}
 	    yyerrok;
 	  }
+#line 2189 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 39:
-/* Line 1787 of yacc.c  */
-#line 461 "awkgram.y"
+#line 461 "awkgram.y" /* yacc.c:1646  */
     {	(yyval) = NULL; }
+#line 2195 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 42:
-/* Line 1787 of yacc.c  */
-#line 471 "awkgram.y"
+#line 471 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2201 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 43:
-/* Line 1787 of yacc.c  */
-#line 473 "awkgram.y"
-    { (yyval) = (yyvsp[(2) - (3)]); }
+#line 473 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[-1]); }
+#line 2207 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 44:
-/* Line 1787 of yacc.c  */
-#line 475 "awkgram.y"
+#line 475 "awkgram.y" /* yacc.c:1646  */
     {
 		if (do_pretty_print)
-			(yyval) = list_prepend((yyvsp[(1) - (1)]), instruction(Op_exec_count));
+			(yyval) = list_prepend((yyvsp[0]), instruction(Op_exec_count));
 		else
-			(yyval) = (yyvsp[(1) - (1)]);
+			(yyval) = (yyvsp[0]);
  	  }
+#line 2218 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 45:
-/* Line 1787 of yacc.c  */
-#line 482 "awkgram.y"
+#line 482 "awkgram.y" /* yacc.c:1646  */
     {
 		INSTRUCTION *dflt, *curr = NULL, *cexp, *cstmt;
 		INSTRUCTION *ip, *nextc, *tbreak;
@@ -2438,9 +2233,9 @@ yyreduce:
 		dflt = instruction(Op_jmp);
 		dflt->target_jmp = tbreak;	/* if no case match and no explicit default */
 
-		if ((yyvsp[(7) - (9)]) != NULL) {
-			curr = (yyvsp[(7) - (9)])->nexti;
-			bcfree((yyvsp[(7) - (9)]));	/* Op_list */
+		if ((yyvsp[-2]) != NULL) {
+			curr = (yyvsp[-2])->nexti;
+			bcfree((yyvsp[-2]));	/* Op_list */
 		} /*  else
 				curr = NULL; */
 
@@ -2496,13 +2291,13 @@ yyreduce:
 		if (case_values != NULL)
 			efree(case_values);
 
-		ip = (yyvsp[(3) - (9)]);
+		ip = (yyvsp[-6]);
 		if (do_pretty_print) {
-			(void) list_prepend(ip, (yyvsp[(1) - (9)]));
+			(void) list_prepend(ip, (yyvsp[-8]));
 			(void) list_prepend(ip, instruction(Op_exec_count));
-			(yyvsp[(1) - (9)])->target_break = tbreak;
-			((yyvsp[(1) - (9)]) + 1)->switch_start = cexp->nexti;
-			((yyvsp[(1) - (9)]) + 1)->switch_end = cexp->lasti;
+			(yyvsp[-8])->target_break = tbreak;
+			((yyvsp[-8]) + 1)->switch_start = cexp->nexti;
+			((yyvsp[-8]) + 1)->switch_end = cexp->lasti;
 		}/* else
 				$1 is NULL */
 
@@ -2513,11 +2308,11 @@ yyreduce:
 		break_allowed--;			
 		fix_break_continue(ip, tbreak, NULL);
 	  }
+#line 2312 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 46:
-/* Line 1787 of yacc.c  */
-#line 572 "awkgram.y"
+#line 572 "awkgram.y" /* yacc.c:1646  */
     { 
 		/*
 		 *    -----------------
@@ -2535,22 +2330,22 @@ yyreduce:
 		INSTRUCTION *ip, *tbreak, *tcont;
 
 		tbreak = instruction(Op_no_op);
-		add_lint((yyvsp[(3) - (6)]), LINT_assign_in_cond);
-		tcont = (yyvsp[(3) - (6)])->nexti;
-		ip = list_append((yyvsp[(3) - (6)]), instruction(Op_jmp_false));
+		add_lint((yyvsp[-3]), LINT_assign_in_cond);
+		tcont = (yyvsp[-3])->nexti;
+		ip = list_append((yyvsp[-3]), instruction(Op_jmp_false));
 		ip->lasti->target_jmp = tbreak;
 
 		if (do_pretty_print) {
 			(void) list_append(ip, instruction(Op_exec_count));
-			(yyvsp[(1) - (6)])->target_break = tbreak;
-			(yyvsp[(1) - (6)])->target_continue = tcont;
-			((yyvsp[(1) - (6)]) + 1)->while_body = ip->lasti;
-			(void) list_prepend(ip, (yyvsp[(1) - (6)]));
+			(yyvsp[-5])->target_break = tbreak;
+			(yyvsp[-5])->target_continue = tcont;
+			((yyvsp[-5]) + 1)->while_body = ip->lasti;
+			(void) list_prepend(ip, (yyvsp[-5]));
 		}/* else
 				$1 is NULL */
 
-		if ((yyvsp[(6) - (6)]) != NULL)
-			(void) list_merge(ip, (yyvsp[(6) - (6)]));
+		if ((yyvsp[0]) != NULL)
+			(void) list_merge(ip, (yyvsp[0]));
 		(void) list_append(ip, instruction(Op_jmp));
 		ip->lasti->target_jmp = tcont;
 		(yyval) = list_append(ip, tbreak);
@@ -2559,11 +2354,11 @@ yyreduce:
 		continue_allowed--;
 		fix_break_continue(ip, tbreak, tcont);
 	  }
+#line 2358 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 47:
-/* Line 1787 of yacc.c  */
-#line 614 "awkgram.y"
+#line 614 "awkgram.y" /* yacc.c:1646  */
     {
 		/*
 		 *    -----------------
@@ -2580,12 +2375,12 @@ yyreduce:
 		INSTRUCTION *ip, *tbreak, *tcont;
 
 		tbreak = instruction(Op_no_op);
-		tcont = (yyvsp[(6) - (8)])->nexti;
-		add_lint((yyvsp[(6) - (8)]), LINT_assign_in_cond);
-		if ((yyvsp[(3) - (8)]) != NULL)
-			ip = list_merge((yyvsp[(3) - (8)]), (yyvsp[(6) - (8)]));
+		tcont = (yyvsp[-2])->nexti;
+		add_lint((yyvsp[-2]), LINT_assign_in_cond);
+		if ((yyvsp[-5]) != NULL)
+			ip = list_merge((yyvsp[-5]), (yyvsp[-2]));
 		else
-			ip = list_prepend((yyvsp[(6) - (8)]), instruction(Op_no_op));
+			ip = list_prepend((yyvsp[-2]), instruction(Op_no_op));
 		if (do_pretty_print)
 			(void) list_prepend(ip, instruction(Op_exec_count));
 		(void) list_append(ip, instruction(Op_jmp_true));
@@ -2597,29 +2392,29 @@ yyreduce:
 		fix_break_continue(ip, tbreak, tcont);
 
 		if (do_pretty_print) {
-			(yyvsp[(1) - (8)])->target_break = tbreak;
-			(yyvsp[(1) - (8)])->target_continue = tcont;
-			((yyvsp[(1) - (8)]) + 1)->doloop_cond = tcont;
-			(yyval) = list_prepend(ip, (yyvsp[(1) - (8)]));
-			bcfree((yyvsp[(4) - (8)]));
+			(yyvsp[-7])->target_break = tbreak;
+			(yyvsp[-7])->target_continue = tcont;
+			((yyvsp[-7]) + 1)->doloop_cond = tcont;
+			(yyval) = list_prepend(ip, (yyvsp[-7]));
+			bcfree((yyvsp[-4]));
 		} /* else
 			$1 and $4 are NULLs */
 	  }
+#line 2404 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 48:
-/* Line 1787 of yacc.c  */
-#line 656 "awkgram.y"
+#line 656 "awkgram.y" /* yacc.c:1646  */
     {
 		INSTRUCTION *ip;
-		char *var_name = (yyvsp[(3) - (8)])->lextok;
-
-		if ((yyvsp[(8) - (8)]) != NULL
-				&& (yyvsp[(8) - (8)])->lasti->opcode == Op_K_delete
-				&& (yyvsp[(8) - (8)])->lasti->expr_count == 1
-				&& (yyvsp[(8) - (8)])->nexti->opcode == Op_push
-				&& ((yyvsp[(8) - (8)])->nexti->memory->type != Node_var || !((yyvsp[(8) - (8)])->nexti->memory->var_update))
-				&& strcmp((yyvsp[(8) - (8)])->nexti->memory->vname, var_name) == 0
+		char *var_name = (yyvsp[-5])->lextok;
+
+		if ((yyvsp[0]) != NULL
+				&& (yyvsp[0])->lasti->opcode == Op_K_delete
+				&& (yyvsp[0])->lasti->expr_count == 1
+				&& (yyvsp[0])->nexti->opcode == Op_push
+				&& ((yyvsp[0])->nexti->memory->type != Node_var || !((yyvsp[0])->nexti->memory->var_update))
+				&& strcmp((yyvsp[0])->nexti->memory->vname, var_name) == 0
 		) {
 		
 		/* Efficiency hack.  Recognize the special case of
@@ -2636,25 +2431,25 @@ yyreduce:
 		 */		 
 			NODE *arr = NULL;
 
-			ip = (yyvsp[(8) - (8)])->nexti->nexti; 
-			if ((yyvsp[(5) - (8)])->nexti->opcode == Op_push && (yyvsp[(5) - (8)])->lasti == (yyvsp[(5) - (8)])->nexti)
-				arr = (yyvsp[(5) - (8)])->nexti->memory;
+			ip = (yyvsp[0])->nexti->nexti; 
+			if ((yyvsp[-3])->nexti->opcode == Op_push && (yyvsp[-3])->lasti == (yyvsp[-3])->nexti)
+				arr = (yyvsp[-3])->nexti->memory;
 			if (arr != NULL
 					&& ip->opcode == Op_no_op
 					&& ip->nexti->opcode == Op_push_array
 					&& strcmp(ip->nexti->memory->vname, arr->vname) == 0
-					&& ip->nexti->nexti == (yyvsp[(8) - (8)])->lasti
+					&& ip->nexti->nexti == (yyvsp[0])->lasti
 			) {
-				(void) make_assignable((yyvsp[(8) - (8)])->nexti);
-				(yyvsp[(8) - (8)])->lasti->opcode = Op_K_delete_loop;
-				(yyvsp[(8) - (8)])->lasti->expr_count = 0;
-				if ((yyvsp[(1) - (8)]) != NULL)
-					bcfree((yyvsp[(1) - (8)]));
+				(void) make_assignable((yyvsp[0])->nexti);
+				(yyvsp[0])->lasti->opcode = Op_K_delete_loop;
+				(yyvsp[0])->lasti->expr_count = 0;
+				if ((yyvsp[-7]) != NULL)
+					bcfree((yyvsp[-7]));
 				efree(var_name);
-				bcfree((yyvsp[(3) - (8)]));
-				bcfree((yyvsp[(4) - (8)]));
-				bcfree((yyvsp[(5) - (8)]));
-				(yyval) = (yyvsp[(8) - (8)]);
+				bcfree((yyvsp[-5]));
+				bcfree((yyvsp[-4]));
+				bcfree((yyvsp[-3]));
+				(yyval) = (yyvsp[0]);
 			} else
 				goto regular_loop;
 		} else {
@@ -2671,50 +2466,50 @@ yyreduce:
 			 * ib:[Op_arrayfor_final      ]
 			 */
 regular_loop:
-			ip = (yyvsp[(5) - (8)]);
+			ip = (yyvsp[-3]);
 			ip->nexti->opcode = Op_push_array;
 
 			tbreak = instruction(Op_arrayfor_final);
-			(yyvsp[(4) - (8)])->opcode = Op_arrayfor_incr;
-			(yyvsp[(4) - (8)])->array_var = variable((yyvsp[(3) - (8)])->source_line, var_name, Node_var);
-			(yyvsp[(4) - (8)])->target_jmp = tbreak;
-			tcont = (yyvsp[(4) - (8)]);
-			(yyvsp[(3) - (8)])->opcode = Op_arrayfor_init;
-			(yyvsp[(3) - (8)])->target_jmp = tbreak;
-			(void) list_append(ip, (yyvsp[(3) - (8)]));
+			(yyvsp[-4])->opcode = Op_arrayfor_incr;
+			(yyvsp[-4])->array_var = variable((yyvsp[-5])->source_line, var_name, Node_var);
+			(yyvsp[-4])->target_jmp = tbreak;
+			tcont = (yyvsp[-4]);
+			(yyvsp[-5])->opcode = Op_arrayfor_init;
+			(yyvsp[-5])->target_jmp = tbreak;
+			(void) list_append(ip, (yyvsp[-5]));
 
 			if (do_pretty_print) {
-				(yyvsp[(1) - (8)])->opcode = Op_K_arrayfor;
-				(yyvsp[(1) - (8)])->target_continue = tcont;
-				(yyvsp[(1) - (8)])->target_break = tbreak;
-				(void) list_append(ip, (yyvsp[(1) - (8)]));
+				(yyvsp[-7])->opcode = Op_K_arrayfor;
+				(yyvsp[-7])->target_continue = tcont;
+				(yyvsp[-7])->target_break = tbreak;
+				(void) list_append(ip, (yyvsp[-7]));
 			} /* else
 					$1 is NULL */
 
 			/* add update_FOO instruction if necessary */ 
-			if ((yyvsp[(4) - (8)])->array_var->type == Node_var && (yyvsp[(4) - (8)])->array_var->var_update) {
+			if ((yyvsp[-4])->array_var->type == Node_var && (yyvsp[-4])->array_var->var_update) {
 				(void) list_append(ip, instruction(Op_var_update));
-				ip->lasti->update_var = (yyvsp[(4) - (8)])->array_var->var_update;
+				ip->lasti->update_var = (yyvsp[-4])->array_var->var_update;
 			}
-			(void) list_append(ip, (yyvsp[(4) - (8)]));
+			(void) list_append(ip, (yyvsp[-4]));
 
 			/* add set_FOO instruction if necessary */
-			if ((yyvsp[(4) - (8)])->array_var->type == Node_var && (yyvsp[(4) - (8)])->array_var->var_assign) {
+			if ((yyvsp[-4])->array_var->type == Node_var && (yyvsp[-4])->array_var->var_assign) {
 				(void) list_append(ip, instruction(Op_var_assign));
-				ip->lasti->assign_var = (yyvsp[(4) - (8)])->array_var->var_assign;
+				ip->lasti->assign_var = (yyvsp[-4])->array_var->var_assign;
 			}
 
 			if (do_pretty_print) {
 				(void) list_append(ip, instruction(Op_exec_count));
-				((yyvsp[(1) - (8)]) + 1)->forloop_cond = (yyvsp[(4) - (8)]);
-				((yyvsp[(1) - (8)]) + 1)->forloop_body = ip->lasti; 
+				((yyvsp[-7]) + 1)->forloop_cond = (yyvsp[-4]);
+				((yyvsp[-7]) + 1)->forloop_body = ip->lasti; 
 			}
 
-			if ((yyvsp[(8) - (8)]) != NULL)
-				(void) list_merge(ip, (yyvsp[(8) - (8)]));
+			if ((yyvsp[0]) != NULL)
+				(void) list_merge(ip, (yyvsp[0]));
 
 			(void) list_append(ip, instruction(Op_jmp));
-			ip->lasti->target_jmp = (yyvsp[(4) - (8)]);
+			ip->lasti->target_jmp = (yyvsp[-4]);
 			(yyval) = list_append(ip, tbreak);
 			fix_break_continue(ip, tbreak, tcont);
 		} 
@@ -2722,157 +2517,157 @@ regular_loop:
 		break_allowed--;
 		continue_allowed--;
 	  }
+#line 2521 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 49:
-/* Line 1787 of yacc.c  */
-#line 769 "awkgram.y"
+#line 769 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = mk_for_loop((yyvsp[(1) - (12)]), (yyvsp[(3) - (12)]), (yyvsp[(6) - (12)]), (yyvsp[(9) - (12)]), (yyvsp[(12) - (12)]));
+		(yyval) = mk_for_loop((yyvsp[-11]), (yyvsp[-9]), (yyvsp[-6]), (yyvsp[-3]), (yyvsp[0]));
 
 		break_allowed--;
 		continue_allowed--;
 	  }
+#line 2532 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 50:
-/* Line 1787 of yacc.c  */
-#line 776 "awkgram.y"
+#line 776 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = mk_for_loop((yyvsp[(1) - (11)]), (yyvsp[(3) - (11)]), (INSTRUCTION *) NULL, (yyvsp[(8) - (11)]), (yyvsp[(11) - (11)]));
+		(yyval) = mk_for_loop((yyvsp[-10]), (yyvsp[-8]), (INSTRUCTION *) NULL, (yyvsp[-3]), (yyvsp[0]));
 
 		break_allowed--;
 		continue_allowed--;
 	  }
+#line 2543 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 51:
-/* Line 1787 of yacc.c  */
-#line 783 "awkgram.y"
+#line 783 "awkgram.y" /* yacc.c:1646  */
     {
 		if (do_pretty_print)
-			(yyval) = list_prepend((yyvsp[(1) - (1)]), instruction(Op_exec_count));
+			(yyval) = list_prepend((yyvsp[0]), instruction(Op_exec_count));
 		else
-			(yyval) = (yyvsp[(1) - (1)]);
+			(yyval) = (yyvsp[0]);
 	  }
+#line 2554 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 52:
-/* Line 1787 of yacc.c  */
-#line 793 "awkgram.y"
+#line 793 "awkgram.y" /* yacc.c:1646  */
     { 
 		if (! break_allowed)
-			error_ln((yyvsp[(1) - (2)])->source_line,
+			error_ln((yyvsp[-1])->source_line,
 				_("`break' is not allowed outside a loop or switch"));
-		(yyvsp[(1) - (2)])->target_jmp = NULL;
-		(yyval) = list_create((yyvsp[(1) - (2)]));
+		(yyvsp[-1])->target_jmp = NULL;
+		(yyval) = list_create((yyvsp[-1]));
 
 	  }
+#line 2567 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 53:
-/* Line 1787 of yacc.c  */
-#line 802 "awkgram.y"
+#line 802 "awkgram.y" /* yacc.c:1646  */
     {
 		if (! continue_allowed)
-			error_ln((yyvsp[(1) - (2)])->source_line,
+			error_ln((yyvsp[-1])->source_line,
 				_("`continue' is not allowed outside a loop"));
-		(yyvsp[(1) - (2)])->target_jmp = NULL;
-		(yyval) = list_create((yyvsp[(1) - (2)]));
+		(yyvsp[-1])->target_jmp = NULL;
+		(yyval) = list_create((yyvsp[-1]));
 
 	  }
+#line 2580 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 54:
-/* Line 1787 of yacc.c  */
-#line 811 "awkgram.y"
+#line 811 "awkgram.y" /* yacc.c:1646  */
     {
 		/* if inside function (rule = 0), resolve context at run-time */
 		if (rule && rule != Rule)
-			error_ln((yyvsp[(1) - (2)])->source_line,
+			error_ln((yyvsp[-1])->source_line,
 				_("`next' used in %s action"), ruletab[rule]);
-		(yyvsp[(1) - (2)])->target_jmp = ip_rec;
-		(yyval) = list_create((yyvsp[(1) - (2)]));
+		(yyvsp[-1])->target_jmp = ip_rec;
+		(yyval) = list_create((yyvsp[-1]));
 	  }
+#line 2593 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 55:
-/* Line 1787 of yacc.c  */
-#line 820 "awkgram.y"
+#line 820 "awkgram.y" /* yacc.c:1646  */
     {
 		/* if inside function (rule = 0), resolve context at run-time */
 		if (rule == BEGIN || rule == END || rule == ENDFILE)
-			error_ln((yyvsp[(1) - (2)])->source_line,
+			error_ln((yyvsp[-1])->source_line,
 				_("`nextfile' used in %s action"), ruletab[rule]);
 
-		(yyvsp[(1) - (2)])->target_newfile = ip_newfile;
-		(yyvsp[(1) - (2)])->target_endfile = ip_endfile;
-		(yyval) = list_create((yyvsp[(1) - (2)]));
+		(yyvsp[-1])->target_newfile = ip_newfile;
+		(yyvsp[-1])->target_endfile = ip_endfile;
+		(yyval) = list_create((yyvsp[-1]));
 	  }
+#line 2608 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 56:
-/* Line 1787 of yacc.c  */
-#line 831 "awkgram.y"
+#line 831 "awkgram.y" /* yacc.c:1646  */
     {
 		/* Initialize the two possible jump targets, the actual target
 		 * is resolved at run-time. 
 		 */
-		(yyvsp[(1) - (3)])->target_end = ip_end;	/* first instruction in end_block */
-		(yyvsp[(1) - (3)])->target_atexit = ip_atexit;	/* cleanup and go home */
+		(yyvsp[-2])->target_end = ip_end;	/* first instruction in end_block */
+		(yyvsp[-2])->target_atexit = ip_atexit;	/* cleanup and go home */
 
-		if ((yyvsp[(2) - (3)]) == NULL) {
-			(yyval) = list_create((yyvsp[(1) - (3)]));
+		if ((yyvsp[-1]) == NULL) {
+			(yyval) = list_create((yyvsp[-2]));
 			(void) list_prepend((yyval), instruction(Op_push_i));
 			(yyval)->nexti->memory = dupnode(Nnull_string);
 		} else
-			(yyval) = list_append((yyvsp[(2) - (3)]), (yyvsp[(1) - (3)]));
+			(yyval) = list_append((yyvsp[-1]), (yyvsp[-2]));
 	  }
+#line 2627 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 57:
-/* Line 1787 of yacc.c  */
-#line 846 "awkgram.y"
+#line 846 "awkgram.y" /* yacc.c:1646  */
     {
 		if (! in_function)
 			yyerror(_("`return' used outside function context"));
 	  }
+#line 2636 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 58:
-/* Line 1787 of yacc.c  */
-#line 849 "awkgram.y"
+#line 849 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(3) - (4)]) == NULL) {
-			(yyval) = list_create((yyvsp[(1) - (4)]));
+		if ((yyvsp[-1]) == NULL) {
+			(yyval) = list_create((yyvsp[-3]));
 			(void) list_prepend((yyval), instruction(Op_push_i));
 			(yyval)->nexti->memory = dupnode(Nnull_string);
 		} else {
 			if (do_optimize
-				&& (yyvsp[(3) - (4)])->lasti->opcode == Op_func_call
-				&& strcmp((yyvsp[(3) - (4)])->lasti->func_name, in_function) == 0
+				&& (yyvsp[-1])->lasti->opcode == Op_func_call
+				&& strcmp((yyvsp[-1])->lasti->func_name, in_function) == 0
 			) {
 				/* Do tail recursion optimization. Tail
 				 * call without a return value is recognized
 				 * in mk_function().
 				 */
-				((yyvsp[(3) - (4)])->lasti + 1)->tail_call = true;
+				((yyvsp[-1])->lasti + 1)->tail_call = true;
 			}
 
-			(yyval) = list_append((yyvsp[(3) - (4)]), (yyvsp[(1) - (4)]));
+			(yyval) = list_append((yyvsp[-1]), (yyvsp[-3]));
 		}
 	  }
+#line 2661 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 60:
-/* Line 1787 of yacc.c  */
-#line 881 "awkgram.y"
+#line 881 "awkgram.y" /* yacc.c:1646  */
     { in_print = true; in_parens = 0; }
+#line 2667 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 61:
-/* Line 1787 of yacc.c  */
-#line 882 "awkgram.y"
+#line 882 "awkgram.y" /* yacc.c:1646  */
     {
 		/*
 		 * Optimization: plain `print' has no expression list, so $3 is null.
@@ -2880,12 +2675,12 @@ regular_loop:
 		 * which is faster for these two cases.
 		 */
 
-		if ((yyvsp[(1) - (4)])->opcode == Op_K_print &&
-			((yyvsp[(3) - (4)]) == NULL
-				|| ((yyvsp[(3) - (4)])->lasti->opcode == Op_field_spec
-					&& (yyvsp[(3) - (4)])->nexti->nexti->nexti == (yyvsp[(3) - (4)])->lasti
-					&& (yyvsp[(3) - (4)])->nexti->nexti->opcode == Op_push_i
-					&& (yyvsp[(3) - (4)])->nexti->nexti->memory->type == Node_val)
+		if ((yyvsp[-3])->opcode == Op_K_print &&
+			((yyvsp[-1]) == NULL
+				|| ((yyvsp[-1])->lasti->opcode == Op_field_spec
+					&& (yyvsp[-1])->nexti->nexti->nexti == (yyvsp[-1])->lasti
+					&& (yyvsp[-1])->nexti->nexti->opcode == Op_push_i
+					&& (yyvsp[-1])->nexti->nexti->memory->type == Node_val)
 			)
 		) {
 			static bool warned = false;
@@ -2898,37 +2693,37 @@ regular_loop:
 			 *    [Op_K_print_rec | NULL | redir_type | expr_count]
 			 */
 
-			if ((yyvsp[(3) - (4)]) != NULL) {
-				NODE *n = (yyvsp[(3) - (4)])->nexti->nexti->memory;
+			if ((yyvsp[-1]) != NULL) {
+				NODE *n = (yyvsp[-1])->nexti->nexti->memory;
 
 				if (! iszero(n))
 					goto regular_print;
 
-				bcfree((yyvsp[(3) - (4)])->lasti);			/* Op_field_spec */
+				bcfree((yyvsp[-1])->lasti);			/* Op_field_spec */
 				unref(n);				/* Node_val */
-				bcfree((yyvsp[(3) - (4)])->nexti->nexti);		/* Op_push_i */
-				bcfree((yyvsp[(3) - (4)])->nexti);			/* Op_list */
-				bcfree((yyvsp[(3) - (4)]));				/* Op_list */
+				bcfree((yyvsp[-1])->nexti->nexti);		/* Op_push_i */
+				bcfree((yyvsp[-1])->nexti);			/* Op_list */
+				bcfree((yyvsp[-1]));				/* Op_list */
 			} else {
 				if (do_lint && (rule == BEGIN || rule == END) && ! warned) {
 					warned = true;
-					lintwarn_ln((yyvsp[(1) - (4)])->source_line,
+					lintwarn_ln((yyvsp[-3])->source_line,
 		_("plain `print' in BEGIN or END rule should probably be `print \"\"'"));
 				}
 			}
 
-			(yyvsp[(1) - (4)])->expr_count = 0;
-			(yyvsp[(1) - (4)])->opcode = Op_K_print_rec;
-			if ((yyvsp[(4) - (4)]) == NULL) {    /* no redircetion */
-				(yyvsp[(1) - (4)])->redir_type = redirect_none;
-				(yyval) = list_create((yyvsp[(1) - (4)]));
+			(yyvsp[-3])->expr_count = 0;
+			(yyvsp[-3])->opcode = Op_K_print_rec;
+			if ((yyvsp[0]) == NULL) {    /* no redircetion */
+				(yyvsp[-3])->redir_type = redirect_none;
+				(yyval) = list_create((yyvsp[-3]));
 			} else {
 				INSTRUCTION *ip;
-				ip = (yyvsp[(4) - (4)])->nexti;
-				(yyvsp[(1) - (4)])->redir_type = ip->redir_type;
-				(yyvsp[(4) - (4)])->nexti = ip->nexti;
+				ip = (yyvsp[0])->nexti;
+				(yyvsp[-3])->redir_type = ip->redir_type;
+				(yyvsp[0])->nexti = ip->nexti;
 				bcfree(ip);
-				(yyval) = list_append((yyvsp[(4) - (4)]), (yyvsp[(1) - (4)]));
+				(yyval) = list_append((yyvsp[0]), (yyvsp[-3]));
 			}
 		} else {
 			/*   -----------------
@@ -2941,59 +2736,59 @@ regular_loop:
 			 *
 			 */
 regular_print:	 
-			if ((yyvsp[(4) - (4)]) == NULL) {		/* no redirection */
-				if ((yyvsp[(3) - (4)]) == NULL)	{	/* printf without arg */
-					(yyvsp[(1) - (4)])->expr_count = 0;
-					(yyvsp[(1) - (4)])->redir_type = redirect_none;
-					(yyval) = list_create((yyvsp[(1) - (4)]));
+			if ((yyvsp[0]) == NULL) {		/* no redirection */
+				if ((yyvsp[-1]) == NULL)	{	/* printf without arg */
+					(yyvsp[-3])->expr_count = 0;
+					(yyvsp[-3])->redir_type = redirect_none;
+					(yyval) = list_create((yyvsp[-3]));
 				} else {
-					INSTRUCTION *t = (yyvsp[(3) - (4)]);
-					(yyvsp[(1) - (4)])->expr_count = count_expressions(&t, false);
-					(yyvsp[(1) - (4)])->redir_type = redirect_none;
-					(yyval) = list_append(t, (yyvsp[(1) - (4)]));
+					INSTRUCTION *t = (yyvsp[-1]);
+					(yyvsp[-3])->expr_count = count_expressions(&t, false);
+					(yyvsp[-3])->redir_type = redirect_none;
+					(yyval) = list_append(t, (yyvsp[-3]));
 				}
 			} else {
 				INSTRUCTION *ip;
-				ip = (yyvsp[(4) - (4)])->nexti;
-				(yyvsp[(1) - (4)])->redir_type = ip->redir_type;
-				(yyvsp[(4) - (4)])->nexti = ip->nexti;
+				ip = (yyvsp[0])->nexti;
+				(yyvsp[-3])->redir_type = ip->redir_type;
+				(yyvsp[0])->nexti = ip->nexti;
 				bcfree(ip);
-				if ((yyvsp[(3) - (4)]) == NULL) {
-					(yyvsp[(1) - (4)])->expr_count = 0;
-					(yyval) = list_append((yyvsp[(4) - (4)]), (yyvsp[(1) - (4)]));
+				if ((yyvsp[-1]) == NULL) {
+					(yyvsp[-3])->expr_count = 0;
+					(yyval) = list_append((yyvsp[0]), (yyvsp[-3]));
 				} else {
-					INSTRUCTION *t = (yyvsp[(3) - (4)]);
-					(yyvsp[(1) - (4)])->expr_count = count_expressions(&t, false);
-					(yyval) = list_append(list_merge((yyvsp[(4) - (4)]), t), (yyvsp[(1) - (4)]));
+					INSTRUCTION *t = (yyvsp[-1]);
+					(yyvsp[-3])->expr_count = count_expressions(&t, false);
+					(yyval) = list_append(list_merge((yyvsp[0]), t), (yyvsp[-3]));
 				}
 			}
 		}
 	  }
+#line 2768 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 62:
-/* Line 1787 of yacc.c  */
-#line 979 "awkgram.y"
+#line 979 "awkgram.y" /* yacc.c:1646  */
     { sub_counter = 0; }
+#line 2774 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 63:
-/* Line 1787 of yacc.c  */
-#line 980 "awkgram.y"
+#line 980 "awkgram.y" /* yacc.c:1646  */
     {
-		char *arr = (yyvsp[(2) - (4)])->lextok;
+		char *arr = (yyvsp[-2])->lextok;
 
-		(yyvsp[(2) - (4)])->opcode = Op_push_array;
-		(yyvsp[(2) - (4)])->memory = variable((yyvsp[(2) - (4)])->source_line, arr, Node_var_new);
+		(yyvsp[-2])->opcode = Op_push_array;
+		(yyvsp[-2])->memory = variable((yyvsp[-2])->source_line, arr, Node_var_new);
 
 		if (! do_posix && ! do_traditional) {
-			if ((yyvsp[(2) - (4)])->memory == symbol_table)
+			if ((yyvsp[-2])->memory == symbol_table)
 				fatal(_("`delete' is not allowed with SYMTAB"));
-			else if ((yyvsp[(2) - (4)])->memory == func_table)
+			else if ((yyvsp[-2])->memory == func_table)
 				fatal(_("`delete' is not allowed with FUNCTAB"));
 		}
 
-		if ((yyvsp[(4) - (4)]) == NULL) {
+		if ((yyvsp[0]) == NULL) {
 			/*
 			 * As of September 2012, POSIX has added support
 			 * for `delete array'. See:
@@ -3005,525 +2800,525 @@ regular_print:
 			 * Also, since BWK awk supports it, we don't have to
 			 * check do_traditional either.
 			 */
-			(yyvsp[(1) - (4)])->expr_count = 0;
-			(yyval) = list_append(list_create((yyvsp[(2) - (4)])), (yyvsp[(1) - (4)]));
+			(yyvsp[-3])->expr_count = 0;
+			(yyval) = list_append(list_create((yyvsp[-2])), (yyvsp[-3]));
 		} else {
-			(yyvsp[(1) - (4)])->expr_count = sub_counter;
-			(yyval) = list_append(list_append((yyvsp[(4) - (4)]), (yyvsp[(2) - (4)])), (yyvsp[(1) - (4)]));
+			(yyvsp[-3])->expr_count = sub_counter;
+			(yyval) = list_append(list_append((yyvsp[0]), (yyvsp[-2])), (yyvsp[-3]));
 		}
 	  }
+#line 2811 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 64:
-/* Line 1787 of yacc.c  */
-#line 1017 "awkgram.y"
+#line 1017 "awkgram.y" /* yacc.c:1646  */
     {
 		static bool warned = false;
-		char *arr = (yyvsp[(3) - (4)])->lextok;
+		char *arr = (yyvsp[-1])->lextok;
 
 		if (do_lint && ! warned) {
 			warned = true;
-			lintwarn_ln((yyvsp[(1) - (4)])->source_line,
+			lintwarn_ln((yyvsp[-3])->source_line,
 				_("`delete(array)' is a non-portable tawk extension"));
 		}
 		if (do_traditional) {
-			error_ln((yyvsp[(1) - (4)])->source_line,
+			error_ln((yyvsp[-3])->source_line,
 				_("`delete(array)' is a non-portable tawk extension"));
 		}
-		(yyvsp[(3) - (4)])->memory = variable((yyvsp[(3) - (4)])->source_line, arr, Node_var_new);
-		(yyvsp[(3) - (4)])->opcode = Op_push_array;
-		(yyvsp[(1) - (4)])->expr_count = 0;
-		(yyval) = list_append(list_create((yyvsp[(3) - (4)])), (yyvsp[(1) - (4)]));
+		(yyvsp[-1])->memory = variable((yyvsp[-1])->source_line, arr, Node_var_new);
+		(yyvsp[-1])->opcode = Op_push_array;
+		(yyvsp[-3])->expr_count = 0;
+		(yyval) = list_append(list_create((yyvsp[-1])), (yyvsp[-3]));
 
 		if (! do_posix && ! do_traditional) {
-			if ((yyvsp[(3) - (4)])->memory == symbol_table)
+			if ((yyvsp[-1])->memory == symbol_table)
 				fatal(_("`delete' is not allowed with SYMTAB"));
-			else if ((yyvsp[(3) - (4)])->memory == func_table)
+			else if ((yyvsp[-1])->memory == func_table)
 				fatal(_("`delete' is not allowed with FUNCTAB"));
 		}
 	  }
+#line 2841 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 65:
-/* Line 1787 of yacc.c  */
-#line 1043 "awkgram.y"
-    {	(yyval) = optimize_assignment((yyvsp[(1) - (1)])); }
+#line 1043 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = optimize_assignment((yyvsp[0])); }
+#line 2847 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 66:
-/* Line 1787 of yacc.c  */
-#line 1048 "awkgram.y"
+#line 1048 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2853 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 67:
-/* Line 1787 of yacc.c  */
-#line 1050 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1050 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2859 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 68:
-/* Line 1787 of yacc.c  */
-#line 1055 "awkgram.y"
+#line 1055 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2865 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 69:
-/* Line 1787 of yacc.c  */
-#line 1057 "awkgram.y"
+#line 1057 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(1) - (2)]) == NULL)
-			(yyval) = list_create((yyvsp[(2) - (2)]));
+		if ((yyvsp[-1]) == NULL)
+			(yyval) = list_create((yyvsp[0]));
 		else
-			(yyval) = list_prepend((yyvsp[(1) - (2)]), (yyvsp[(2) - (2)]));
+			(yyval) = list_prepend((yyvsp[-1]), (yyvsp[0]));
 	  }
+#line 2876 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 70:
-/* Line 1787 of yacc.c  */
-#line 1064 "awkgram.y"
+#line 1064 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2882 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 71:
-/* Line 1787 of yacc.c  */
-#line 1069 "awkgram.y"
+#line 1069 "awkgram.y" /* yacc.c:1646  */
     {
-		INSTRUCTION *casestmt = (yyvsp[(5) - (5)]);
-		if ((yyvsp[(5) - (5)]) == NULL)
+		INSTRUCTION *casestmt = (yyvsp[0]);
+		if ((yyvsp[0]) == NULL)
 			casestmt = list_create(instruction(Op_no_op));	
 		if (do_pretty_print)
 			(void) list_prepend(casestmt, instruction(Op_exec_count));
-		(yyvsp[(1) - (5)])->case_exp = (yyvsp[(2) - (5)]);
-		(yyvsp[(1) - (5)])->case_stmt = casestmt;
-		bcfree((yyvsp[(3) - (5)]));
-		(yyval) = (yyvsp[(1) - (5)]);
+		(yyvsp[-4])->case_exp = (yyvsp[-3]);
+		(yyvsp[-4])->case_stmt = casestmt;
+		bcfree((yyvsp[-2]));
+		(yyval) = (yyvsp[-4]);
 	  }
+#line 2898 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 72:
-/* Line 1787 of yacc.c  */
-#line 1081 "awkgram.y"
+#line 1081 "awkgram.y" /* yacc.c:1646  */
     {
-		INSTRUCTION *casestmt = (yyvsp[(4) - (4)]);
-		if ((yyvsp[(4) - (4)]) == NULL)
+		INSTRUCTION *casestmt = (yyvsp[0]);
+		if ((yyvsp[0]) == NULL)
 			casestmt = list_create(instruction(Op_no_op));
 		if (do_pretty_print)
 			(void) list_prepend(casestmt, instruction(Op_exec_count));
-		bcfree((yyvsp[(2) - (4)]));
-		(yyvsp[(1) - (4)])->case_stmt = casestmt;
-		(yyval) = (yyvsp[(1) - (4)]);
+		bcfree((yyvsp[-2]));
+		(yyvsp[-3])->case_stmt = casestmt;
+		(yyval) = (yyvsp[-3]);
 	  }
+#line 2913 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 73:
-/* Line 1787 of yacc.c  */
-#line 1095 "awkgram.y"
-    {	(yyval) = (yyvsp[(1) - (1)]); }
+#line 1095 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = (yyvsp[0]); }
+#line 2919 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 74:
-/* Line 1787 of yacc.c  */
-#line 1097 "awkgram.y"
+#line 1097 "awkgram.y" /* yacc.c:1646  */
     { 
-		NODE *n = (yyvsp[(2) - (2)])->memory;
+		NODE *n = (yyvsp[0])->memory;
 		(void) force_number(n);
 		negate_num(n);
-		bcfree((yyvsp[(1) - (2)]));
-		(yyval) = (yyvsp[(2) - (2)]);
+		bcfree((yyvsp[-1]));
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2931 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 75:
-/* Line 1787 of yacc.c  */
-#line 1105 "awkgram.y"
+#line 1105 "awkgram.y" /* yacc.c:1646  */
     {
-		bcfree((yyvsp[(1) - (2)]));
-		(yyval) = (yyvsp[(2) - (2)]);
+		bcfree((yyvsp[-1]));
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2940 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 76:
-/* Line 1787 of yacc.c  */
-#line 1110 "awkgram.y"
-    {	(yyval) = (yyvsp[(1) - (1)]); }
+#line 1110 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = (yyvsp[0]); }
+#line 2946 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 77:
-/* Line 1787 of yacc.c  */
-#line 1112 "awkgram.y"
+#line 1112 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (1)])->opcode = Op_push_re;
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyvsp[0])->opcode = Op_push_re;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2955 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 78:
-/* Line 1787 of yacc.c  */
-#line 1120 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1120 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2961 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 79:
-/* Line 1787 of yacc.c  */
-#line 1122 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1122 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2967 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 81:
-/* Line 1787 of yacc.c  */
-#line 1132 "awkgram.y"
+#line 1132 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = (yyvsp[(2) - (3)]);
+		(yyval) = (yyvsp[-1]);
 	  }
+#line 2975 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 82:
-/* Line 1787 of yacc.c  */
-#line 1139 "awkgram.y"
+#line 1139 "awkgram.y" /* yacc.c:1646  */
     {
 		in_print = false;
 		in_parens = 0;
 		(yyval) = NULL;
 	  }
+#line 2985 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 83:
-/* Line 1787 of yacc.c  */
-#line 1144 "awkgram.y"
+#line 1144 "awkgram.y" /* yacc.c:1646  */
     { in_print = false; in_parens = 0; }
+#line 2991 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 84:
-/* Line 1787 of yacc.c  */
-#line 1145 "awkgram.y"
+#line 1145 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(1) - (3)])->redir_type == redirect_twoway
-		    	&& (yyvsp[(3) - (3)])->lasti->opcode == Op_K_getline_redir
-		   	 	&& (yyvsp[(3) - (3)])->lasti->redir_type == redirect_twoway)
+		if ((yyvsp[-2])->redir_type == redirect_twoway
+		    	&& (yyvsp[0])->lasti->opcode == Op_K_getline_redir
+		   	 	&& (yyvsp[0])->lasti->redir_type == redirect_twoway)
 			yyerror(_("multistage two-way pipelines don't work"));
-		(yyval) = list_prepend((yyvsp[(3) - (3)]), (yyvsp[(1) - (3)]));
+		(yyval) = list_prepend((yyvsp[0]), (yyvsp[-2]));
 	  }
+#line 3003 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 85:
-/* Line 1787 of yacc.c  */
-#line 1156 "awkgram.y"
+#line 1156 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = mk_condition((yyvsp[(3) - (6)]), (yyvsp[(1) - (6)]), (yyvsp[(6) - (6)]), NULL, NULL);
+		(yyval) = mk_condition((yyvsp[-3]), (yyvsp[-5]), (yyvsp[0]), NULL, NULL);
 	  }
+#line 3011 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 86:
-/* Line 1787 of yacc.c  */
-#line 1161 "awkgram.y"
+#line 1161 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = mk_condition((yyvsp[(3) - (9)]), (yyvsp[(1) - (9)]), (yyvsp[(6) - (9)]), (yyvsp[(7) - (9)]), (yyvsp[(9) - (9)]));
+		(yyval) = mk_condition((yyvsp[-6]), (yyvsp[-8]), (yyvsp[-3]), (yyvsp[-2]), (yyvsp[0]));
 	  }
+#line 3019 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 91:
-/* Line 1787 of yacc.c  */
-#line 1178 "awkgram.y"
+#line 1178 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3025 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 92:
-/* Line 1787 of yacc.c  */
-#line 1180 "awkgram.y"
+#line 1180 "awkgram.y" /* yacc.c:1646  */
     {
-		bcfree((yyvsp[(1) - (2)]));
-		(yyval) = (yyvsp[(2) - (2)]);
+		bcfree((yyvsp[-1]));
+		(yyval) = (yyvsp[0]);
 	  }
+#line 3034 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 93:
-/* Line 1787 of yacc.c  */
-#line 1188 "awkgram.y"
+#line 1188 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3040 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 94:
-/* Line 1787 of yacc.c  */
-#line 1190 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]) ; }
+#line 1190 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]) ; }
+#line 3046 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 95:
-/* Line 1787 of yacc.c  */
-#line 1195 "awkgram.y"
+#line 1195 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (1)])->param_count = 0;
-		(yyval) = list_create((yyvsp[(1) - (1)]));
+		(yyvsp[0])->param_count = 0;
+		(yyval) = list_create((yyvsp[0]));
 	  }
+#line 3055 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 96:
-/* Line 1787 of yacc.c  */
-#line 1200 "awkgram.y"
+#line 1200 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(3) - (3)])->param_count =  (yyvsp[(1) - (3)])->lasti->param_count + 1;
-		(yyval) = list_append((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]));
+		(yyvsp[0])->param_count =  (yyvsp[-2])->lasti->param_count + 1;
+		(yyval) = list_append((yyvsp[-2]), (yyvsp[0]));
 		yyerrok;
 	  }
+#line 3065 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 97:
-/* Line 1787 of yacc.c  */
-#line 1206 "awkgram.y"
+#line 1206 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3071 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 98:
-/* Line 1787 of yacc.c  */
-#line 1208 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (2)]); }
+#line 1208 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[-1]); }
+#line 3077 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 99:
-/* Line 1787 of yacc.c  */
-#line 1210 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (3)]); }
+#line 1210 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[-2]); }
+#line 3083 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 100:
-/* Line 1787 of yacc.c  */
-#line 1216 "awkgram.y"
+#line 1216 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3089 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 101:
-/* Line 1787 of yacc.c  */
-#line 1218 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1218 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3095 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 102:
-/* Line 1787 of yacc.c  */
-#line 1223 "awkgram.y"
+#line 1223 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3101 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 103:
-/* Line 1787 of yacc.c  */
-#line 1225 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1225 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3107 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 104:
-/* Line 1787 of yacc.c  */
-#line 1230 "awkgram.y"
-    {	(yyval) = mk_expression_list(NULL, (yyvsp[(1) - (1)])); }
+#line 1230 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = mk_expression_list(NULL, (yyvsp[0])); }
+#line 3113 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 105:
-/* Line 1787 of yacc.c  */
-#line 1232 "awkgram.y"
+#line 1232 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = mk_expression_list((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]));
+		(yyval) = mk_expression_list((yyvsp[-2]), (yyvsp[0]));
 		yyerrok;
 	  }
+#line 3122 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 106:
-/* Line 1787 of yacc.c  */
-#line 1237 "awkgram.y"
+#line 1237 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3128 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 107:
-/* Line 1787 of yacc.c  */
-#line 1239 "awkgram.y"
+#line 1239 "awkgram.y" /* yacc.c:1646  */
     {
 		/*
 		 * Returning the expression list instead of NULL lets
 		 * snode get a list of arguments that it can count.
 		 */
-		(yyval) = (yyvsp[(1) - (2)]);
+		(yyval) = (yyvsp[-1]);
 	  }
+#line 3140 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 108:
-/* Line 1787 of yacc.c  */
-#line 1247 "awkgram.y"
+#line 1247 "awkgram.y" /* yacc.c:1646  */
     {
 		/* Ditto */
-		(yyval) = mk_expression_list((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]));
+		(yyval) = mk_expression_list((yyvsp[-2]), (yyvsp[0]));
 	  }
+#line 3149 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 109:
-/* Line 1787 of yacc.c  */
-#line 1252 "awkgram.y"
+#line 1252 "awkgram.y" /* yacc.c:1646  */
     {
 		/* Ditto */
-		(yyval) = (yyvsp[(1) - (3)]);
+		(yyval) = (yyvsp[-2]);
 	  }
+#line 3158 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 110:
-/* Line 1787 of yacc.c  */
-#line 1261 "awkgram.y"
+#line 1261 "awkgram.y" /* yacc.c:1646  */
     {
-		if (do_lint && (yyvsp[(3) - (3)])->lasti->opcode == Op_match_rec)
-			lintwarn_ln((yyvsp[(2) - (3)])->source_line,
+		if (do_lint && (yyvsp[0])->lasti->opcode == Op_match_rec)
+			lintwarn_ln((yyvsp[-1])->source_line,
 				_("regular expression on right of assignment"));
-		(yyval) = mk_assignment((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)]));
+		(yyval) = mk_assignment((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1]));
 	  }
+#line 3169 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 111:
-/* Line 1787 of yacc.c  */
-#line 1268 "awkgram.y"
-    {	(yyval) = mk_boolean((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1268 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = mk_boolean((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3175 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 112:
-/* Line 1787 of yacc.c  */
-#line 1270 "awkgram.y"
-    {	(yyval) = mk_boolean((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1270 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = mk_boolean((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3181 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 113:
-/* Line 1787 of yacc.c  */
-#line 1272 "awkgram.y"
+#line 1272 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(1) - (3)])->lasti->opcode == Op_match_rec)
-			warning_ln((yyvsp[(2) - (3)])->source_line,
+		if ((yyvsp[-2])->lasti->opcode == Op_match_rec)
+			warning_ln((yyvsp[-1])->source_line,
 				_("regular expression on left of `~' or `!~' operator"));
 
-		if ((yyvsp[(3) - (3)])->lasti == (yyvsp[(3) - (3)])->nexti && (yyvsp[(3) - (3)])->nexti->opcode == Op_match_rec) {
-			(yyvsp[(2) - (3)])->memory = (yyvsp[(3) - (3)])->nexti->memory;
-			bcfree((yyvsp[(3) - (3)])->nexti);	/* Op_match_rec */
-			bcfree((yyvsp[(3) - (3)]));			/* Op_list */
-			(yyval) = list_append((yyvsp[(1) - (3)]), (yyvsp[(2) - (3)]));
+		if ((yyvsp[0])->lasti == (yyvsp[0])->nexti && (yyvsp[0])->nexti->opcode == Op_match_rec) {
+			(yyvsp[-1])->memory = (yyvsp[0])->nexti->memory;
+			bcfree((yyvsp[0])->nexti);	/* Op_match_rec */
+			bcfree((yyvsp[0]));			/* Op_list */
+			(yyval) = list_append((yyvsp[-2]), (yyvsp[-1]));
 		} else {
-			(yyvsp[(2) - (3)])->memory = make_regnode(Node_dynregex, NULL);
-			(yyval) = list_append(list_merge((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)])), (yyvsp[(2) - (3)]));
+			(yyvsp[-1])->memory = make_regnode(Node_dynregex, NULL);
+			(yyval) = list_append(list_merge((yyvsp[-2]), (yyvsp[0])), (yyvsp[-1]));
 		}
 	  }
+#line 3201 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 114:
-/* Line 1787 of yacc.c  */
-#line 1288 "awkgram.y"
+#line 1288 "awkgram.y" /* yacc.c:1646  */
     {
 		if (do_lint_old)
-			warning_ln((yyvsp[(2) - (3)])->source_line,
+			warning_ln((yyvsp[-1])->source_line,
 				_("old awk does not support the keyword `in' except after `for'"));
-		(yyvsp[(3) - (3)])->nexti->opcode = Op_push_array;
-		(yyvsp[(2) - (3)])->opcode = Op_in_array;
-		(yyvsp[(2) - (3)])->expr_count = 1;
-		(yyval) = list_append(list_merge((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)])), (yyvsp[(2) - (3)]));
+		(yyvsp[0])->nexti->opcode = Op_push_array;
+		(yyvsp[-1])->opcode = Op_in_array;
+		(yyvsp[-1])->expr_count = 1;
+		(yyval) = list_append(list_merge((yyvsp[-2]), (yyvsp[0])), (yyvsp[-1]));
 	  }
+#line 3215 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 115:
-/* Line 1787 of yacc.c  */
-#line 1298 "awkgram.y"
+#line 1298 "awkgram.y" /* yacc.c:1646  */
     {
-		if (do_lint && (yyvsp[(3) - (3)])->lasti->opcode == Op_match_rec)
-			lintwarn_ln((yyvsp[(2) - (3)])->source_line,
+		if (do_lint && (yyvsp[0])->lasti->opcode == Op_match_rec)
+			lintwarn_ln((yyvsp[-1])->source_line,
 				_("regular expression on right of comparison"));
-		(yyval) = list_append(list_merge((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)])), (yyvsp[(2) - (3)]));
+		(yyval) = list_append(list_merge((yyvsp[-2]), (yyvsp[0])), (yyvsp[-1]));
 	  }
+#line 3226 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 116:
-/* Line 1787 of yacc.c  */
-#line 1305 "awkgram.y"
-    { (yyval) = mk_condition((yyvsp[(1) - (5)]), (yyvsp[(2) - (5)]), (yyvsp[(3) - (5)]), (yyvsp[(4) - (5)]), (yyvsp[(5) - (5)])); }
+#line 1305 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_condition((yyvsp[-4]), (yyvsp[-3]), (yyvsp[-2]), (yyvsp[-1]), (yyvsp[0])); }
+#line 3232 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 117:
-/* Line 1787 of yacc.c  */
-#line 1307 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1307 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3238 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 118:
-/* Line 1787 of yacc.c  */
-#line 1312 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1312 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3244 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 119:
-/* Line 1787 of yacc.c  */
-#line 1314 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1314 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3250 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 120:
-/* Line 1787 of yacc.c  */
-#line 1316 "awkgram.y"
+#line 1316 "awkgram.y" /* yacc.c:1646  */
     {	
-		(yyvsp[(2) - (2)])->opcode = Op_assign_quotient;
-		(yyval) = (yyvsp[(2) - (2)]);
+		(yyvsp[0])->opcode = Op_assign_quotient;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 3259 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 121:
-/* Line 1787 of yacc.c  */
-#line 1324 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1324 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3265 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 122:
-/* Line 1787 of yacc.c  */
-#line 1326 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1326 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3271 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 123:
-/* Line 1787 of yacc.c  */
-#line 1331 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1331 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3277 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 124:
-/* Line 1787 of yacc.c  */
-#line 1333 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1333 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3283 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 125:
-/* Line 1787 of yacc.c  */
-#line 1338 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1338 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3289 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 126:
-/* Line 1787 of yacc.c  */
-#line 1340 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1340 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3295 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 127:
-/* Line 1787 of yacc.c  */
-#line 1342 "awkgram.y"
+#line 1342 "awkgram.y" /* yacc.c:1646  */
     {
 		int count = 2;
 		bool is_simple_var = false;
 
-		if ((yyvsp[(1) - (2)])->lasti->opcode == Op_concat) {
+		if ((yyvsp[-1])->lasti->opcode == Op_concat) {
 			/* multiple (> 2) adjacent strings optimization */
-			is_simple_var = ((yyvsp[(1) - (2)])->lasti->concat_flag & CSVAR);
-			count = (yyvsp[(1) - (2)])->lasti->expr_count + 1;
-			(yyvsp[(1) - (2)])->lasti->opcode = Op_no_op;
+			is_simple_var = ((yyvsp[-1])->lasti->concat_flag & CSVAR);
+			count = (yyvsp[-1])->lasti->expr_count + 1;
+			(yyvsp[-1])->lasti->opcode = Op_no_op;
 		} else {
-			is_simple_var = ((yyvsp[(1) - (2)])->nexti->opcode == Op_push
-					&& (yyvsp[(1) - (2)])->lasti == (yyvsp[(1) - (2)])->nexti); /* first exp. is a simple
+			is_simple_var = ((yyvsp[-1])->nexti->opcode == Op_push
+					&& (yyvsp[-1])->lasti == (yyvsp[-1])->nexti); /* first exp. is a simple
 					                             * variable?; kludge for use
 					                             * in Op_assign_concat.
 		 			                             */
 		}
 
 		if (do_optimize
-			&& (yyvsp[(1) - (2)])->nexti == (yyvsp[(1) - (2)])->lasti && (yyvsp[(1) - (2)])->nexti->opcode == Op_push_i
-			&& (yyvsp[(2) - (2)])->nexti == (yyvsp[(2) - (2)])->lasti && (yyvsp[(2) - (2)])->nexti->opcode == Op_push_i
+			&& (yyvsp[-1])->nexti == (yyvsp[-1])->lasti && (yyvsp[-1])->nexti->opcode == Op_push_i
+			&& (yyvsp[0])->nexti == (yyvsp[0])->lasti && (yyvsp[0])->nexti->opcode == Op_push_i
 		) {
-			NODE *n1 = (yyvsp[(1) - (2)])->nexti->memory;
-			NODE *n2 = (yyvsp[(2) - (2)])->nexti->memory;
+			NODE *n1 = (yyvsp[-1])->nexti->memory;
+			NODE *n2 = (yyvsp[0])->nexti->memory;
 			size_t nlen;
 
 			n1 = force_string(n1);
@@ -3536,193 +3331,184 @@ regular_print:
 			n1->flags &= ~(NUMCUR|NUMBER|NUMINT);
 			n1->flags |= (STRING|STRCUR);
 			unref(n2);
-			bcfree((yyvsp[(2) - (2)])->nexti);
-			bcfree((yyvsp[(2) - (2)]));
-			(yyval) = (yyvsp[(1) - (2)]);
+			bcfree((yyvsp[0])->nexti);
+			bcfree((yyvsp[0]));
+			(yyval) = (yyvsp[-1]);
 		} else {
-			(yyval) = list_append(list_merge((yyvsp[(1) - (2)]), (yyvsp[(2) - (2)])), instruction(Op_concat));
+			(yyval) = list_append(list_merge((yyvsp[-1]), (yyvsp[0])), instruction(Op_concat));
 			(yyval)->lasti->concat_flag = (is_simple_var ? CSVAR : 0);
 			(yyval)->lasti->expr_count = count;
 			if (count > max_args)
 				max_args = count;
 		}
 	  }
+#line 3346 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 129:
-/* Line 1787 of yacc.c  */
-#line 1394 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1394 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3352 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 130:
-/* Line 1787 of yacc.c  */
-#line 1396 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1396 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3358 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 131:
-/* Line 1787 of yacc.c  */
-#line 1398 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1398 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3364 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 132:
-/* Line 1787 of yacc.c  */
-#line 1400 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1400 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3370 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 133:
-/* Line 1787 of yacc.c  */
-#line 1402 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1402 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3376 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 134:
-/* Line 1787 of yacc.c  */
-#line 1404 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1404 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3382 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 135:
-/* Line 1787 of yacc.c  */
-#line 1406 "awkgram.y"
+#line 1406 "awkgram.y" /* yacc.c:1646  */
     {
 		/*
-		 * In BEGINFILE/ENDFILE, allow `getline var < file'
+		 * In BEGINFILE/ENDFILE, allow `getline [var] < file'
 		 */
 
-		if (rule == BEGINFILE || rule == ENDFILE) {
-			if ((yyvsp[(2) - (3)]) != NULL && (yyvsp[(3) - (3)]) != NULL)
-				;	 /* all  ok */
-			else {
-				if ((yyvsp[(2) - (3)]) != NULL)
-					error_ln((yyvsp[(1) - (3)])->source_line,
-						_("`getline var' invalid inside `%s' rule"), ruletab[rule]);
-				else
-					error_ln((yyvsp[(1) - (3)])->source_line,
-						_("`getline' invalid inside `%s' rule"), ruletab[rule]);
-			}
-		}
-		if (do_lint && rule == END && (yyvsp[(3) - (3)]) == NULL)
-			lintwarn_ln((yyvsp[(1) - (3)])->source_line,
+		if ((rule == BEGINFILE || rule == ENDFILE) && (yyvsp[0]) == NULL)
+			error_ln((yyvsp[-2])->source_line,
+				 _("non-redirected `getline' invalid inside `%s' rule"), ruletab[rule]);
+		if (do_lint && rule == END && (yyvsp[0]) == NULL)
+			lintwarn_ln((yyvsp[-2])->source_line,
 				_("non-redirected `getline' undefined inside END action"));
-		(yyval) = mk_getline((yyvsp[(1) - (3)]), (yyvsp[(2) - (3)]), (yyvsp[(3) - (3)]), redirect_input);
+		(yyval) = mk_getline((yyvsp[-2]), (yyvsp[-1]), (yyvsp[0]), redirect_input);
 	  }
+#line 3400 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 136:
-/* Line 1787 of yacc.c  */
-#line 1429 "awkgram.y"
+#line 1420 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(2) - (2)])->opcode = Op_postincrement;
-		(yyval) = mk_assignment((yyvsp[(1) - (2)]), NULL, (yyvsp[(2) - (2)]));
+		(yyvsp[0])->opcode = Op_postincrement;
+		(yyval) = mk_assignment((yyvsp[-1]), NULL, (yyvsp[0]));
 	  }
+#line 3409 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 137:
-/* Line 1787 of yacc.c  */
-#line 1434 "awkgram.y"
+#line 1425 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(2) - (2)])->opcode = Op_postdecrement;
-		(yyval) = mk_assignment((yyvsp[(1) - (2)]), NULL, (yyvsp[(2) - (2)]));
+		(yyvsp[0])->opcode = Op_postdecrement;
+		(yyval) = mk_assignment((yyvsp[-1]), NULL, (yyvsp[0]));
 	  }
+#line 3418 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 138:
-/* Line 1787 of yacc.c  */
-#line 1439 "awkgram.y"
+#line 1430 "awkgram.y" /* yacc.c:1646  */
     {
 		if (do_lint_old) {
-		    warning_ln((yyvsp[(4) - (5)])->source_line,
+		    warning_ln((yyvsp[-1])->source_line,
 				_("old awk does not support the keyword `in' except after `for'"));
-		    warning_ln((yyvsp[(4) - (5)])->source_line,
+		    warning_ln((yyvsp[-1])->source_line,
 				_("old awk does not support multidimensional arrays"));
 		}
-		(yyvsp[(5) - (5)])->nexti->opcode = Op_push_array;
-		(yyvsp[(4) - (5)])->opcode = Op_in_array;
-		if ((yyvsp[(2) - (5)]) == NULL) {	/* error */
+		(yyvsp[0])->nexti->opcode = Op_push_array;
+		(yyvsp[-1])->opcode = Op_in_array;
+		if ((yyvsp[-3]) == NULL) {	/* error */
 			errcount++;
-			(yyvsp[(4) - (5)])->expr_count = 0;
-			(yyval) = list_merge((yyvsp[(5) - (5)]), (yyvsp[(4) - (5)]));
+			(yyvsp[-1])->expr_count = 0;
+			(yyval) = list_merge((yyvsp[0]), (yyvsp[-1]));
 		} else {
-			INSTRUCTION *t = (yyvsp[(2) - (5)]);
-			(yyvsp[(4) - (5)])->expr_count = count_expressions(&t, false);
-			(yyval) = list_append(list_merge(t, (yyvsp[(5) - (5)])), (yyvsp[(4) - (5)]));
+			INSTRUCTION *t = (yyvsp[-3]);
+			(yyvsp[-1])->expr_count = count_expressions(&t, false);
+			(yyval) = list_append(list_merge(t, (yyvsp[0])), (yyvsp[-1]));
 		}
 	  }
+#line 3442 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 139:
-/* Line 1787 of yacc.c  */
-#line 1464 "awkgram.y"
+#line 1455 "awkgram.y" /* yacc.c:1646  */
     {
-		  (yyval) = mk_getline((yyvsp[(3) - (4)]), (yyvsp[(4) - (4)]), (yyvsp[(1) - (4)]), (yyvsp[(2) - (4)])->redir_type);
-		  bcfree((yyvsp[(2) - (4)]));
+		  (yyval) = mk_getline((yyvsp[-1]), (yyvsp[0]), (yyvsp[-3]), (yyvsp[-2])->redir_type);
+		  bcfree((yyvsp[-2]));
 		}
+#line 3451 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 140:
-/* Line 1787 of yacc.c  */
-#line 1470 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1461 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3457 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 141:
-/* Line 1787 of yacc.c  */
-#line 1472 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1463 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3463 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 142:
-/* Line 1787 of yacc.c  */
-#line 1474 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1465 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3469 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 143:
-/* Line 1787 of yacc.c  */
-#line 1476 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1467 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3475 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 144:
-/* Line 1787 of yacc.c  */
-#line 1478 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1469 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3481 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 145:
-/* Line 1787 of yacc.c  */
-#line 1480 "awkgram.y"
-    { (yyval) = mk_binary((yyvsp[(1) - (3)]), (yyvsp[(3) - (3)]), (yyvsp[(2) - (3)])); }
+#line 1471 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = mk_binary((yyvsp[-2]), (yyvsp[0]), (yyvsp[-1])); }
+#line 3487 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 146:
-/* Line 1787 of yacc.c  */
-#line 1485 "awkgram.y"
+#line 1476 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = list_create((yyvsp[(1) - (1)]));
+		(yyval) = list_create((yyvsp[0]));
 	  }
+#line 3495 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 147:
-/* Line 1787 of yacc.c  */
-#line 1489 "awkgram.y"
+#line 1480 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(2) - (2)])->opcode == Op_match_rec) {
-			(yyvsp[(2) - (2)])->opcode = Op_nomatch;
-			(yyvsp[(1) - (2)])->opcode = Op_push_i;
-			(yyvsp[(1) - (2)])->memory = make_number(0.0);	
-			(yyval) = list_append(list_append(list_create((yyvsp[(1) - (2)])),
-						instruction(Op_field_spec)), (yyvsp[(2) - (2)]));
+		if ((yyvsp[0])->opcode == Op_match_rec) {
+			(yyvsp[0])->opcode = Op_nomatch;
+			(yyvsp[-1])->opcode = Op_push_i;
+			(yyvsp[-1])->memory = make_number(0.0);	
+			(yyval) = list_append(list_append(list_create((yyvsp[-1])),
+						instruction(Op_field_spec)), (yyvsp[0]));
 		} else {
-			if (do_optimize && (yyvsp[(2) - (2)])->nexti == (yyvsp[(2) - (2)])->lasti
-					&& (yyvsp[(2) - (2)])->nexti->opcode == Op_push_i
-					&& ((yyvsp[(2) - (2)])->nexti->memory->flags & (MPFN|MPZN)) == 0
+			if (do_optimize && (yyvsp[0])->nexti == (yyvsp[0])->lasti
+					&& (yyvsp[0])->nexti->opcode == Op_push_i
+					&& ((yyvsp[0])->nexti->memory->flags & (MPFN|MPZN)) == 0
 			) {
-				NODE *n = (yyvsp[(2) - (2)])->nexti->memory;
+				NODE *n = (yyvsp[0])->nexti->memory;
 				if ((n->flags & (STRCUR|STRING)) != 0) {
 					n->numbr = (AWKNUM) (n->stlen == 0);
 					n->flags &= ~(STRCUR|STRING);
@@ -3732,139 +3518,139 @@ regular_print:
 					n->stlen = 0;
 				} else
 					n->numbr = (AWKNUM) (n->numbr == 0.0);
-				bcfree((yyvsp[(1) - (2)]));
-				(yyval) = (yyvsp[(2) - (2)]);
+				bcfree((yyvsp[-1]));
+				(yyval) = (yyvsp[0]);
 			} else {
-				(yyvsp[(1) - (2)])->opcode = Op_not;
-				add_lint((yyvsp[(2) - (2)]), LINT_assign_in_cond);
-				(yyval) = list_append((yyvsp[(2) - (2)]), (yyvsp[(1) - (2)]));
+				(yyvsp[-1])->opcode = Op_not;
+				add_lint((yyvsp[0]), LINT_assign_in_cond);
+				(yyval) = list_append((yyvsp[0]), (yyvsp[-1]));
 			}
 		}
 	   }
+#line 3531 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 148:
-/* Line 1787 of yacc.c  */
-#line 1521 "awkgram.y"
-    { (yyval) = (yyvsp[(2) - (3)]); }
+#line 1512 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[-1]); }
+#line 3537 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 149:
-/* Line 1787 of yacc.c  */
-#line 1523 "awkgram.y"
+#line 1514 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = snode((yyvsp[(3) - (4)]), (yyvsp[(1) - (4)]));
+		(yyval) = snode((yyvsp[-1]), (yyvsp[-3]));
 		if ((yyval) == NULL)
 			YYABORT;
 	  }
+#line 3547 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 150:
-/* Line 1787 of yacc.c  */
-#line 1529 "awkgram.y"
+#line 1520 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = snode((yyvsp[(3) - (4)]), (yyvsp[(1) - (4)]));
+		(yyval) = snode((yyvsp[-1]), (yyvsp[-3]));
 		if ((yyval) == NULL)
 			YYABORT;
 	  }
+#line 3557 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 151:
-/* Line 1787 of yacc.c  */
-#line 1535 "awkgram.y"
+#line 1526 "awkgram.y" /* yacc.c:1646  */
     {
 		static bool warned = false;
 
 		if (do_lint && ! warned) {
 			warned = true;
-			lintwarn_ln((yyvsp[(1) - (1)])->source_line,
+			lintwarn_ln((yyvsp[0])->source_line,
 				_("call of `length' without parentheses is not portable"));
 		}
-		(yyval) = snode(NULL, (yyvsp[(1) - (1)]));
+		(yyval) = snode(NULL, (yyvsp[0]));
 		if ((yyval) == NULL)
 			YYABORT;
 	  }
+#line 3574 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 154:
-/* Line 1787 of yacc.c  */
-#line 1550 "awkgram.y"
+#line 1541 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (2)])->opcode = Op_preincrement;
-		(yyval) = mk_assignment((yyvsp[(2) - (2)]), NULL, (yyvsp[(1) - (2)]));
+		(yyvsp[-1])->opcode = Op_preincrement;
+		(yyval) = mk_assignment((yyvsp[0]), NULL, (yyvsp[-1]));
 	  }
+#line 3583 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 155:
-/* Line 1787 of yacc.c  */
-#line 1555 "awkgram.y"
+#line 1546 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (2)])->opcode = Op_predecrement;
-		(yyval) = mk_assignment((yyvsp[(2) - (2)]), NULL, (yyvsp[(1) - (2)]));
+		(yyvsp[-1])->opcode = Op_predecrement;
+		(yyval) = mk_assignment((yyvsp[0]), NULL, (yyvsp[-1]));
 	  }
+#line 3592 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 156:
-/* Line 1787 of yacc.c  */
-#line 1560 "awkgram.y"
+#line 1551 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = list_create((yyvsp[(1) - (1)]));
+		(yyval) = list_create((yyvsp[0]));
 	  }
+#line 3600 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 157:
-/* Line 1787 of yacc.c  */
-#line 1564 "awkgram.y"
+#line 1555 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = list_create((yyvsp[(1) - (1)]));
+		(yyval) = list_create((yyvsp[0]));
 	  }
+#line 3608 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 158:
-/* Line 1787 of yacc.c  */
-#line 1568 "awkgram.y"
+#line 1559 "awkgram.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(2) - (2)])->lasti->opcode == Op_push_i
-			&& ((yyvsp[(2) - (2)])->lasti->memory->flags & (STRCUR|STRING)) == 0
+		if ((yyvsp[0])->lasti->opcode == Op_push_i
+			&& ((yyvsp[0])->lasti->memory->flags & (STRCUR|STRING)) == 0
 		) {
-			NODE *n = (yyvsp[(2) - (2)])->lasti->memory;
+			NODE *n = (yyvsp[0])->lasti->memory;
 			(void) force_number(n);
 			negate_num(n);			
-			(yyval) = (yyvsp[(2) - (2)]);
-			bcfree((yyvsp[(1) - (2)]));
+			(yyval) = (yyvsp[0]);
+			bcfree((yyvsp[-1]));
 		} else {
-			(yyvsp[(1) - (2)])->opcode = Op_unary_minus;
-			(yyval) = list_append((yyvsp[(2) - (2)]), (yyvsp[(1) - (2)]));
+			(yyvsp[-1])->opcode = Op_unary_minus;
+			(yyval) = list_append((yyvsp[0]), (yyvsp[-1]));
 		}
 	  }
+#line 3627 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 159:
-/* Line 1787 of yacc.c  */
-#line 1583 "awkgram.y"
+#line 1574 "awkgram.y" /* yacc.c:1646  */
     {
 	    /*
 	     * was: $$ = $2
 	     * POSIX semantics: force a conversion to numeric type
 	     */
-		(yyvsp[(1) - (2)])->opcode = Op_plus_i;
-		(yyvsp[(1) - (2)])->memory = make_number(0.0);
-		(yyval) = list_append((yyvsp[(2) - (2)]), (yyvsp[(1) - (2)]));
+		(yyvsp[-1])->opcode = Op_plus_i;
+		(yyvsp[-1])->memory = make_number(0.0);
+		(yyval) = list_append((yyvsp[0]), (yyvsp[-1]));
 	  }
+#line 3641 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 160:
-/* Line 1787 of yacc.c  */
-#line 1596 "awkgram.y"
+#line 1587 "awkgram.y" /* yacc.c:1646  */
     {
-		func_use((yyvsp[(1) - (1)])->lasti->func_name, FUNC_USE);
-		(yyval) = (yyvsp[(1) - (1)]);
+		func_use((yyvsp[0])->lasti->func_name, FUNC_USE);
+		(yyval) = (yyvsp[0]);
 	  }
+#line 3650 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 161:
-/* Line 1787 of yacc.c  */
-#line 1601 "awkgram.y"
+#line 1592 "awkgram.y" /* yacc.c:1646  */
     {
 		/* indirect function call */
 		INSTRUCTION *f, *t;
@@ -3880,7 +3666,7 @@ regular_print:
 			lintwarn("%s", msg);
 		}
 		
-		f = (yyvsp[(2) - (2)])->lasti;
+		f = (yyvsp[0])->lasti;
 		f->opcode = Op_indirect_func_call;
 		name = estrdup(f->func_name, strlen(f->func_name));
 		if (is_std_var(name))
@@ -3895,71 +3681,71 @@ regular_print:
 		 *		@f(f="real_fun")
 		 */
 
-		(yyval) = list_prepend((yyvsp[(2) - (2)]), t);
+		(yyval) = list_prepend((yyvsp[0]), t);
 	  }
+#line 3687 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 162:
-/* Line 1787 of yacc.c  */
-#line 1637 "awkgram.y"
+#line 1628 "awkgram.y" /* yacc.c:1646  */
     {
-		param_sanity((yyvsp[(3) - (4)]));
-		(yyvsp[(1) - (4)])->opcode = Op_func_call;
-		(yyvsp[(1) - (4)])->func_body = NULL;
-		if ((yyvsp[(3) - (4)]) == NULL) {	/* no argument or error */
-			((yyvsp[(1) - (4)]) + 1)->expr_count = 0;
-			(yyval) = list_create((yyvsp[(1) - (4)]));
+		param_sanity((yyvsp[-1]));
+		(yyvsp[-3])->opcode = Op_func_call;
+		(yyvsp[-3])->func_body = NULL;
+		if ((yyvsp[-1]) == NULL) {	/* no argument or error */
+			((yyvsp[-3]) + 1)->expr_count = 0;
+			(yyval) = list_create((yyvsp[-3]));
 		} else {
-			INSTRUCTION *t = (yyvsp[(3) - (4)]);
-			((yyvsp[(1) - (4)]) + 1)->expr_count = count_expressions(&t, true); 
-			(yyval) = list_append(t, (yyvsp[(1) - (4)]));
+			INSTRUCTION *t = (yyvsp[-1]);
+			((yyvsp[-3]) + 1)->expr_count = count_expressions(&t, true); 
+			(yyval) = list_append(t, (yyvsp[-3]));
 		}
 	  }
+#line 3705 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 163:
-/* Line 1787 of yacc.c  */
-#line 1654 "awkgram.y"
+#line 1645 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3711 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 164:
-/* Line 1787 of yacc.c  */
-#line 1656 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 1647 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 3717 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 165:
-/* Line 1787 of yacc.c  */
-#line 1661 "awkgram.y"
+#line 1652 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3723 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 166:
-/* Line 1787 of yacc.c  */
-#line 1663 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (2)]); }
+#line 1654 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[-1]); }
+#line 3729 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 167:
-/* Line 1787 of yacc.c  */
-#line 1668 "awkgram.y"
-    {	(yyval) = (yyvsp[(1) - (1)]); }
+#line 1659 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = (yyvsp[0]); }
+#line 3735 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 168:
-/* Line 1787 of yacc.c  */
-#line 1670 "awkgram.y"
+#line 1661 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = list_merge((yyvsp[(1) - (2)]), (yyvsp[(2) - (2)]));
+		(yyval) = list_merge((yyvsp[-1]), (yyvsp[0]));
 	  }
+#line 3743 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 169:
-/* Line 1787 of yacc.c  */
-#line 1677 "awkgram.y"
+#line 1668 "awkgram.y" /* yacc.c:1646  */
     {
-		INSTRUCTION *ip = (yyvsp[(1) - (1)])->lasti; 
+		INSTRUCTION *ip = (yyvsp[0])->lasti; 
 		int count = ip->sub_count;	/* # of SUBSEP-seperated expressions */
 		if (count > 1) {
 			/* change Op_subscript or Op_sub_array to Op_concat */
@@ -3969,152 +3755,152 @@ regular_print:
 		} else
 			ip->opcode = Op_no_op;
 		sub_counter++;	/* count # of dimensions */
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyval) = (yyvsp[0]);
 	  }
+#line 3761 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 170:
-/* Line 1787 of yacc.c  */
-#line 1694 "awkgram.y"
+#line 1685 "awkgram.y" /* yacc.c:1646  */
     {
-		INSTRUCTION *t = (yyvsp[(2) - (3)]);
-		if ((yyvsp[(2) - (3)]) == NULL) {
-			error_ln((yyvsp[(3) - (3)])->source_line,
+		INSTRUCTION *t = (yyvsp[-1]);
+		if ((yyvsp[-1]) == NULL) {
+			error_ln((yyvsp[0])->source_line,
 				_("invalid subscript expression"));
 			/* install Null string as subscript. */
 			t = list_create(instruction(Op_push_i));
 			t->nexti->memory = dupnode(Nnull_string);
-			(yyvsp[(3) - (3)])->sub_count = 1;			
+			(yyvsp[0])->sub_count = 1;			
 		} else
-			(yyvsp[(3) - (3)])->sub_count = count_expressions(&t, false);
-		(yyval) = list_append(t, (yyvsp[(3) - (3)]));
+			(yyvsp[0])->sub_count = count_expressions(&t, false);
+		(yyval) = list_append(t, (yyvsp[0]));
 	  }
+#line 3779 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 171:
-/* Line 1787 of yacc.c  */
-#line 1711 "awkgram.y"
-    {	(yyval) = (yyvsp[(1) - (1)]); }
+#line 1702 "awkgram.y" /* yacc.c:1646  */
+    {	(yyval) = (yyvsp[0]); }
+#line 3785 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 172:
-/* Line 1787 of yacc.c  */
-#line 1713 "awkgram.y"
+#line 1704 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = list_merge((yyvsp[(1) - (2)]), (yyvsp[(2) - (2)]));
+		(yyval) = list_merge((yyvsp[-1]), (yyvsp[0]));
 	  }
+#line 3793 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 173:
-/* Line 1787 of yacc.c  */
-#line 1720 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (2)]); }
+#line 1711 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[-1]); }
+#line 3799 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 174:
-/* Line 1787 of yacc.c  */
-#line 1725 "awkgram.y"
+#line 1716 "awkgram.y" /* yacc.c:1646  */
     {
-		char *var_name = (yyvsp[(1) - (1)])->lextok;
+		char *var_name = (yyvsp[0])->lextok;
 
-		(yyvsp[(1) - (1)])->opcode = Op_push;
-		(yyvsp[(1) - (1)])->memory = variable((yyvsp[(1) - (1)])->source_line, var_name, Node_var_new);
-		(yyval) = list_create((yyvsp[(1) - (1)]));
+		(yyvsp[0])->opcode = Op_push;
+		(yyvsp[0])->memory = variable((yyvsp[0])->source_line, var_name, Node_var_new);
+		(yyval) = list_create((yyvsp[0]));
 	  }
+#line 3811 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 175:
-/* Line 1787 of yacc.c  */
-#line 1733 "awkgram.y"
+#line 1724 "awkgram.y" /* yacc.c:1646  */
     {
-		char *arr = (yyvsp[(1) - (2)])->lextok;
-		(yyvsp[(1) - (2)])->memory = variable((yyvsp[(1) - (2)])->source_line, arr, Node_var_new);
-		(yyvsp[(1) - (2)])->opcode = Op_push_array;
-		(yyval) = list_prepend((yyvsp[(2) - (2)]), (yyvsp[(1) - (2)]));
+		char *arr = (yyvsp[-1])->lextok;
+		(yyvsp[-1])->memory = variable((yyvsp[-1])->source_line, arr, Node_var_new);
+		(yyvsp[-1])->opcode = Op_push_array;
+		(yyval) = list_prepend((yyvsp[0]), (yyvsp[-1]));
 	  }
+#line 3822 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 176:
-/* Line 1787 of yacc.c  */
-#line 1743 "awkgram.y"
+#line 1734 "awkgram.y" /* yacc.c:1646  */
     {
-		INSTRUCTION *ip = (yyvsp[(1) - (1)])->nexti;
+		INSTRUCTION *ip = (yyvsp[0])->nexti;
 		if (ip->opcode == Op_push
 			&& ip->memory->type == Node_var
 			&& ip->memory->var_update
 		) {
-			(yyval) = list_prepend((yyvsp[(1) - (1)]), instruction(Op_var_update));
+			(yyval) = list_prepend((yyvsp[0]), instruction(Op_var_update));
 			(yyval)->nexti->update_var = ip->memory->var_update;
 		} else
-			(yyval) = (yyvsp[(1) - (1)]);
+			(yyval) = (yyvsp[0]);
 	  }
+#line 3838 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 177:
-/* Line 1787 of yacc.c  */
-#line 1755 "awkgram.y"
+#line 1746 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyval) = list_append((yyvsp[(2) - (3)]), (yyvsp[(1) - (3)]));
-		if ((yyvsp[(3) - (3)]) != NULL)
-			mk_assignment((yyvsp[(2) - (3)]), NULL, (yyvsp[(3) - (3)]));
+		(yyval) = list_append((yyvsp[-1]), (yyvsp[-2]));
+		if ((yyvsp[0]) != NULL)
+			mk_assignment((yyvsp[-1]), NULL, (yyvsp[0]));
 	  }
+#line 3848 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 178:
-/* Line 1787 of yacc.c  */
-#line 1764 "awkgram.y"
+#line 1755 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (1)])->opcode = Op_postincrement;
+		(yyvsp[0])->opcode = Op_postincrement;
 	  }
+#line 3856 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 179:
-/* Line 1787 of yacc.c  */
-#line 1768 "awkgram.y"
+#line 1759 "awkgram.y" /* yacc.c:1646  */
     {
-		(yyvsp[(1) - (1)])->opcode = Op_postdecrement;
+		(yyvsp[0])->opcode = Op_postdecrement;
 	  }
+#line 3864 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 180:
-/* Line 1787 of yacc.c  */
-#line 1771 "awkgram.y"
+#line 1762 "awkgram.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 3870 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 182:
-/* Line 1787 of yacc.c  */
-#line 1779 "awkgram.y"
+#line 1770 "awkgram.y" /* yacc.c:1646  */
     { yyerrok; }
+#line 3876 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 183:
-/* Line 1787 of yacc.c  */
-#line 1783 "awkgram.y"
+#line 1774 "awkgram.y" /* yacc.c:1646  */
     { yyerrok; }
+#line 3882 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 186:
-/* Line 1787 of yacc.c  */
-#line 1792 "awkgram.y"
+#line 1783 "awkgram.y" /* yacc.c:1646  */
     { yyerrok; }
+#line 3888 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 187:
-/* Line 1787 of yacc.c  */
-#line 1796 "awkgram.y"
-    { (yyval) = (yyvsp[(1) - (1)]); yyerrok; }
+#line 1787 "awkgram.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); yyerrok; }
+#line 3894 "awkgram.c" /* yacc.c:1646  */
     break;
 
   case 188:
-/* Line 1787 of yacc.c  */
-#line 1800 "awkgram.y"
+#line 1791 "awkgram.y" /* yacc.c:1646  */
     { yyerrok; }
+#line 3900 "awkgram.c" /* yacc.c:1646  */
     break;
 
 
-/* Line 1787 of yacc.c  */
-#line 4118 "awkgram.c"
+#line 3904 "awkgram.c" /* yacc.c:1646  */
       default: break;
     }
   /* User semantic actions sometimes alter yychar, and that requires
@@ -4136,7 +3922,7 @@ regular_print:
 
   *++yyvsp = yyval;
 
-  /* Now `shift' the result of the reduction.  Determine what state
+  /* Now 'shift' the result of the reduction.  Determine what state
      that goes to, based on the state we popped back to and the rule
      number reduced by.  */
 
@@ -4151,9 +3937,9 @@ regular_print:
   goto yynewstate;
 
 
-/*------------------------------------.
-| yyerrlab -- here on detecting error |
-`------------------------------------*/
+/*--------------------------------------.
+| yyerrlab -- here on detecting error.  |
+`--------------------------------------*/
 yyerrlab:
   /* Make sure we have latest lookahead translation.  See comments at
      user semantic actions for why this is necessary.  */
@@ -4204,20 +3990,20 @@ yyerrlab:
   if (yyerrstatus == 3)
     {
       /* If just tried and failed to reuse lookahead token after an
-	 error, discard it.  */
+         error, discard it.  */
 
       if (yychar <= YYEOF)
-	{
-	  /* Return failure if at end of input.  */
-	  if (yychar == YYEOF)
-	    YYABORT;
-	}
+        {
+          /* Return failure if at end of input.  */
+          if (yychar == YYEOF)
+            YYABORT;
+        }
       else
-	{
-	  yydestruct ("Error: discarding",
-		      yytoken, &yylval);
-	  yychar = YYEMPTY;
-	}
+        {
+          yydestruct ("Error: discarding",
+                      yytoken, &yylval);
+          yychar = YYEMPTY;
+        }
     }
 
   /* Else will try to reuse lookahead token after shifting the error
@@ -4236,7 +4022,7 @@ yyerrorlab:
   if (/*CONSTCOND*/ 0)
      goto yyerrorlab;
 
-  /* Do not reclaim the symbols of the rule which action triggered
+  /* Do not reclaim the symbols of the rule whose action triggered
      this YYERROR.  */
   YYPOPSTACK (yylen);
   yylen = 0;
@@ -4249,29 +4035,29 @@ yyerrorlab:
 | yyerrlab1 -- common code for both syntax error and YYERROR.  |
 `-------------------------------------------------------------*/
 yyerrlab1:
-  yyerrstatus = 3;	/* Each real token shifted decrements this.  */
+  yyerrstatus = 3;      /* Each real token shifted decrements this.  */
 
   for (;;)
     {
       yyn = yypact[yystate];
       if (!yypact_value_is_default (yyn))
-	{
-	  yyn += YYTERROR;
-	  if (0 <= yyn && yyn <= YYLAST && yycheck[yyn] == YYTERROR)
-	    {
-	      yyn = yytable[yyn];
-	      if (0 < yyn)
-		break;
-	    }
-	}
+        {
+          yyn += YYTERROR;
+          if (0 <= yyn && yyn <= YYLAST && yycheck[yyn] == YYTERROR)
+            {
+              yyn = yytable[yyn];
+              if (0 < yyn)
+                break;
+            }
+        }
 
       /* Pop the current state because it cannot handle the error token.  */
       if (yyssp == yyss)
-	YYABORT;
+        YYABORT;
 
 
       yydestruct ("Error: popping",
-		  yystos[yystate], yyvsp);
+                  yystos[yystate], yyvsp);
       YYPOPSTACK (1);
       yystate = *yyssp;
       YY_STACK_PRINT (yyss, yyssp);
@@ -4322,14 +4108,14 @@ yyreturn:
       yydestruct ("Cleanup: discarding lookahead",
                   yytoken, &yylval);
     }
-  /* Do not reclaim the symbols of the rule which action triggered
+  /* Do not reclaim the symbols of the rule whose action triggered
      this YYABORT or YYACCEPT.  */
   YYPOPSTACK (yylen);
   YY_STACK_PRINT (yyss, yyssp);
   while (yyssp != yyss)
     {
       yydestruct ("Cleanup: popping",
-		  yystos[*yyssp], yyvsp);
+                  yystos[*yyssp], yyvsp);
       YYPOPSTACK (1);
     }
 #ifndef yyoverflow
@@ -4340,13 +4126,9 @@ yyreturn:
   if (yymsg != yymsgbuf)
     YYSTACK_FREE (yymsg);
 #endif
-  /* Make sure YYID is used.  */
-  return YYID (yyresult);
+  return yyresult;
 }
-
-
-/* Line 2050 of yacc.c  */
-#line 1802 "awkgram.y"
+#line 1793 "awkgram.y" /* yacc.c:1906  */
 
 
 struct token {
@@ -4513,15 +4295,39 @@ void
 negate_num(NODE *n)
 {
 #ifdef HAVE_MPFR
-	if (is_mpg_float(n)) {
-		int tval;
-		tval = mpfr_neg(n->mpg_numbr, n->mpg_numbr, ROUND_MODE);
-		IEEE_FMT(n->mpg_numbr, tval);
-	} else if (is_mpg_integer(n)) {
-		mpz_neg(n->mpg_i, n->mpg_i);
-	} else
+	int tval = 0;
 #endif
+
+	if (! is_mpg_number(n)) {
 		n->numbr = -n->numbr;
+		return;
+	}
+
+#ifdef HAVE_MPFR
+	if (is_mpg_integer(n)) {
+		if (! iszero(n)) {
+			mpz_neg(n->mpg_i, n->mpg_i);
+			return;
+		}
+
+		/*
+		 * 0 --> -0 conversion. Requires turning the MPG integer
+		 * into an MPFR float.
+		 */
+
+		mpz_clear(n->mpg_i);	/* release the integer storage */
+
+		/* Convert and fall through. */
+		tval = mpfr_set_d(n->mpg_numbr, 0.0, ROUND_MODE);
+		IEEE_FMT(n->mpg_numbr, tval);
+		n->flags &= ~MPZN;
+		n->flags |= MPFN;
+	}
+
+	/* mpfr float case */
+	tval = mpfr_neg(n->mpg_numbr, n->mpg_numbr, ROUND_MODE);
+	IEEE_FMT(n->mpg_numbr, tval);
+#endif
 }
 
 /* print_included_from --- print `Included from ..' file names and locations */
@@ -4857,10 +4663,19 @@ parse_program(INSTRUCTION **pcode)
 	return (ret || errcount);
 }
 
+/* free_srcfile --- free a SRCFILE struct */
+
+void
+free_srcfile(SRCFILE *thisfile)
+{
+	efree(thisfile->src);
+	efree(thisfile);
+}
+
 /* do_add_srcfile --- add one item to srcfiles */
 
 static SRCFILE *
-do_add_srcfile(int stype, char *src, char *path, SRCFILE *thisfile)
+do_add_srcfile(enum srctype stype, char *src, char *path, SRCFILE *thisfile)
 {
 	SRCFILE *s;
 
@@ -4882,7 +4697,7 @@ do_add_srcfile(int stype, char *src, char *path, SRCFILE *thisfile)
  */
 
 SRCFILE *
-add_srcfile(int stype, char *src, SRCFILE *thisfile, bool *already_included, int *errcode)
+add_srcfile(enum srctype stype, char *src, SRCFILE *thisfile, bool *already_included, int *errcode)
 {
 	SRCFILE *s;
 	struct stat sbuf;
@@ -6856,18 +6671,9 @@ func_use(const char *name, enum defref how)
 	len = strlen(name);
 	ind = hash(name, len, HASHSIZE, NULL);
 
-	for (fp = ftable[ind]; fp != NULL; fp = fp->next) {
-		if (strcmp(fp->name, name) == 0) {
-			if (how == FUNC_DEFINE)
-				fp->defined++;
-			else if (how == FUNC_EXT) {
-				fp->defined++;
-				fp->extension++;
-			} else
-				fp->used++;
-			return;
-		}
-	}
+	for (fp = ftable[ind]; fp != NULL; fp = fp->next)
+		if (strcmp(fp->name, name) == 0)
+			goto update_value;
 
 	/* not in the table, fall through to allocate a new one */
 
@@ -6875,6 +6681,10 @@ func_use(const char *name, enum defref how)
 	memset(fp, '\0', sizeof(struct fdesc));
 	emalloc(fp->name, char *, len + 1, "func_use");
 	strcpy(fp->name, name);
+	fp->next = ftable[ind];
+	ftable[ind] = fp;
+
+update_value:
 	if (how == FUNC_DEFINE)
 		fp->defined++;
 	else if (how == FUNC_EXT) {
@@ -6882,8 +6692,6 @@ func_use(const char *name, enum defref how)
 		fp->extension++;
 	} else
 		fp->used++;
-	fp->next = ftable[ind];
-	ftable[ind] = fp;
 }
 
 /* track_ext_func --- add an extension function to the table */
diff --git a/awkgram.y b/awkgram.y
index 9786ca7a..906e6c8b 100644
--- a/awkgram.y
+++ b/awkgram.y
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -1405,21 +1405,12 @@ simp_exp
 	| LEX_GETLINE opt_variable input_redir
 	  {
 		/*
-		 * In BEGINFILE/ENDFILE, allow `getline var < file'
+		 * In BEGINFILE/ENDFILE, allow `getline [var] < file'
 		 */
 
-		if (rule == BEGINFILE || rule == ENDFILE) {
-			if ($2 != NULL && $3 != NULL)
-				;	 /* all  ok */
-			else {
-				if ($2 != NULL)
-					error_ln($1->source_line,
-						_("`getline var' invalid inside `%s' rule"), ruletab[rule]);
-				else
-					error_ln($1->source_line,
-						_("`getline' invalid inside `%s' rule"), ruletab[rule]);
-			}
-		}
+		if ((rule == BEGINFILE || rule == ENDFILE) && $3 == NULL)
+			error_ln($1->source_line,
+				 _("non-redirected `getline' invalid inside `%s' rule"), ruletab[rule]);
 		if (do_lint && rule == END && $3 == NULL)
 			lintwarn_ln($1->source_line,
 				_("non-redirected `getline' undefined inside END action"));
@@ -1965,15 +1956,39 @@ void
 negate_num(NODE *n)
 {
 #ifdef HAVE_MPFR
-	if (is_mpg_float(n)) {
-		int tval;
-		tval = mpfr_neg(n->mpg_numbr, n->mpg_numbr, ROUND_MODE);
-		IEEE_FMT(n->mpg_numbr, tval);
-	} else if (is_mpg_integer(n)) {
-		mpz_neg(n->mpg_i, n->mpg_i);
-	} else
+	int tval = 0;
 #endif
+
+	if (! is_mpg_number(n)) {
 		n->numbr = -n->numbr;
+		return;
+	}
+
+#ifdef HAVE_MPFR
+	if (is_mpg_integer(n)) {
+		if (! iszero(n)) {
+			mpz_neg(n->mpg_i, n->mpg_i);
+			return;
+		}
+
+		/*
+		 * 0 --> -0 conversion. Requires turning the MPG integer
+		 * into an MPFR float.
+		 */
+
+		mpz_clear(n->mpg_i);	/* release the integer storage */
+
+		/* Convert and fall through. */
+		tval = mpfr_set_d(n->mpg_numbr, 0.0, ROUND_MODE);
+		IEEE_FMT(n->mpg_numbr, tval);
+		n->flags &= ~MPZN;
+		n->flags |= MPFN;
+	}
+
+	/* mpfr float case */
+	tval = mpfr_neg(n->mpg_numbr, n->mpg_numbr, ROUND_MODE);
+	IEEE_FMT(n->mpg_numbr, tval);
+#endif
 }
 
 /* print_included_from --- print `Included from ..' file names and locations */
@@ -2309,10 +2324,19 @@ parse_program(INSTRUCTION **pcode)
 	return (ret || errcount);
 }
 
+/* free_srcfile --- free a SRCFILE struct */
+
+void
+free_srcfile(SRCFILE *thisfile)
+{
+	efree(thisfile->src);
+	efree(thisfile);
+}
+
 /* do_add_srcfile --- add one item to srcfiles */
 
 static SRCFILE *
-do_add_srcfile(int stype, char *src, char *path, SRCFILE *thisfile)
+do_add_srcfile(enum srctype stype, char *src, char *path, SRCFILE *thisfile)
 {
 	SRCFILE *s;
 
@@ -2334,7 +2358,7 @@ do_add_srcfile(int stype, char *src, char *path, SRCFILE *thisfile)
  */
 
 SRCFILE *
-add_srcfile(int stype, char *src, SRCFILE *thisfile, bool *already_included, int *errcode)
+add_srcfile(enum srctype stype, char *src, SRCFILE *thisfile, bool *already_included, int *errcode)
 {
 	SRCFILE *s;
 	struct stat sbuf;
@@ -4308,18 +4332,9 @@ func_use(const char *name, enum defref how)
 	len = strlen(name);
 	ind = hash(name, len, HASHSIZE, NULL);
 
-	for (fp = ftable[ind]; fp != NULL; fp = fp->next) {
-		if (strcmp(fp->name, name) == 0) {
-			if (how == FUNC_DEFINE)
-				fp->defined++;
-			else if (how == FUNC_EXT) {
-				fp->defined++;
-				fp->extension++;
-			} else
-				fp->used++;
-			return;
-		}
-	}
+	for (fp = ftable[ind]; fp != NULL; fp = fp->next)
+		if (strcmp(fp->name, name) == 0)
+			goto update_value;
 
 	/* not in the table, fall through to allocate a new one */
 
@@ -4327,6 +4342,10 @@ func_use(const char *name, enum defref how)
 	memset(fp, '\0', sizeof(struct fdesc));
 	emalloc(fp->name, char *, len + 1, "func_use");
 	strcpy(fp->name, name);
+	fp->next = ftable[ind];
+	ftable[ind] = fp;
+
+update_value:
 	if (how == FUNC_DEFINE)
 		fp->defined++;
 	else if (how == FUNC_EXT) {
@@ -4334,8 +4353,6 @@ func_use(const char *name, enum defref how)
 		fp->extension++;
 	} else
 		fp->used++;
-	fp->next = ftable[ind];
-	ftable[ind] = fp;
 }
 
 /* track_ext_func --- add an extension function to the table */
diff --git a/awklib/ChangeLog b/awklib/ChangeLog
index e47d37b2..6ef0bbde 100644
--- a/awklib/ChangeLog
+++ b/awklib/ChangeLog
@@ -1,3 +1,12 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-03-17         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (clean-local): Clean up .dSYM directories for Mac OS X.
+	Thanks to Hermann Piefer for the suggestion.
+
 2013-05-09         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* 4.1.0: Release tar ball made.
diff --git a/awklib/Makefile.am b/awklib/Makefile.am
index b10fa644..6ffbea81 100644
--- a/awklib/Makefile.am
+++ b/awklib/Makefile.am
@@ -62,6 +62,7 @@ uninstall-local:
 clean-local:
 	rm -f $(AUXAWK) igawk *.exe
 	rm -fr eg.old
+	rm -fr grcat.dSYM pwcat.dSYM
 
 $(srcdir)/stamp-eg: $(srcdir)/../doc/gawk.texi $(srcdir)/../doc/gawkinet.texi
 	cd $(srcdir) && \
diff --git a/awklib/Makefile.in b/awklib/Makefile.in
index 15e6c24d..d32ae04a 100644
--- a/awklib/Makefile.in
+++ b/awklib/Makefile.in
@@ -715,6 +715,7 @@ uninstall-local:
 clean-local:
 	rm -f $(AUXAWK) igawk *.exe
 	rm -fr eg.old
+	rm -fr grcat.dSYM pwcat.dSYM
 
 $(srcdir)/stamp-eg: $(srcdir)/../doc/gawk.texi $(srcdir)/../doc/gawkinet.texi
 	cd $(srcdir) && \
diff --git a/awklib/eg/data/BBS-list b/awklib/eg/data/BBS-list
deleted file mode 100644
index 1007417f..00000000
--- a/awklib/eg/data/BBS-list
+++ /dev/null
@@ -1,11 +0,0 @@
-aardvark     555-5553     1200/300          B
-alpo-net     555-3412     2400/1200/300     A
-barfly       555-7685     1200/300          A
-bites        555-1675     2400/1200/300     A
-camelot      555-0542     300               C
-core         555-2912     1200/300          C
-fooey        555-1234     2400/1200/300     B
-foot         555-6699     1200/300          B
-macfoo       555-6480     1200/300          A
-sdace        555-3430     2400/1200/300     A
-sabafoo      555-2127     1200/300          C
diff --git a/awklib/eg/data/mail-list b/awklib/eg/data/mail-list
new file mode 100644
index 00000000..37ff350a
--- /dev/null
+++ b/awklib/eg/data/mail-list
@@ -0,0 +1,11 @@
+Amelia       555-5553     amelia.zodiacusque@gmail.com    F
+Anthony      555-3412     anthony.asserturo@hotmail.com   A
+Becky        555-7685     becky.algebrarum@gmail.com      A
+Bill         555-1675     bill.drowning@hotmail.com       A
+Broderick    555-0542     broderick.aliquotiens@yahoo.com R
+Camilla      555-2912     camilla.infusarum@skynet.be     R
+Fabius       555-1234     fabius.undevicesimus@ucb.edu    F
+Julie        555-6699     julie.perscrutabor@skeeve.com   F
+Martin       555-6480     martin.codicibus@hotmail.com    A
+Samuel       555-3430     samuel.lanceolis@shu.edu        A
+Jean-Paul    555-2127     jeanpaul.campanorum@nyu.edu     R
diff --git a/awklib/eg/lib/ctime.awk b/awklib/eg/lib/ctime.awk
index f37856c6..ca750370 100644
--- a/awklib/eg/lib/ctime.awk
+++ b/awklib/eg/lib/ctime.awk
@@ -4,7 +4,7 @@
 
 function ctime(ts,    format)
 {
-    format = "%a %b %e %H:%M:%S %Z %Y"
+    format = PROCINFO["strftime"]
     if (ts == 0)
         ts = systime()       # use current time as default
     return strftime(format, ts)
diff --git a/awklib/eg/lib/getopt.awk b/awklib/eg/lib/getopt.awk
index 4283a7e1..db957ceb 100644
--- a/awklib/eg/lib/getopt.awk
+++ b/awklib/eg/lib/getopt.awk
@@ -70,7 +70,7 @@ BEGIN {
     # test program
     if (_getopt_test) {
         while ((_go_c = getopt(ARGC, ARGV, "ab:cd")) != -1)
-            printf("c = <%c>, optarg = <%s>\n",
+            printf("c = <%c>, Optarg = <%s>\n",
                                        _go_c, Optarg)
         printf("non-option arguments:\n")
         for (; Optind < ARGC; Optind++)
diff --git a/awklib/eg/lib/gettime.awk b/awklib/eg/lib/gettime.awk
index 4cb56330..3da9c8ab 100644
--- a/awklib/eg/lib/gettime.awk
+++ b/awklib/eg/lib/gettime.awk
@@ -31,7 +31,7 @@ function getlocaltime(time,    ret, now, i)
     now = systime()
 
     # return date(1)-style output
-    ret = strftime("%a %b %e %H:%M:%S %Z %Y", now)
+    ret = strftime(PROCINFO["strftime"], now)
 
     # clear out target array
     delete time
diff --git a/awklib/eg/lib/grcat.c b/awklib/eg/lib/grcat.c
index ff2913a1..7d6b6a74 100644
--- a/awklib/eg/lib/grcat.c
+++ b/awklib/eg/lib/grcat.c
@@ -1,7 +1,7 @@
 /*
  * grcat.c
  *
- * Generate a printable version of the group database
+ * Generate a printable version of the group database.
  */
 /*
  * Arnold Robbins, arnold@skeeve.com, May 1993
diff --git a/awklib/eg/lib/pwcat.c b/awklib/eg/lib/pwcat.c
index 910e0329..934ef34e 100644
--- a/awklib/eg/lib/pwcat.c
+++ b/awklib/eg/lib/pwcat.c
@@ -1,7 +1,7 @@
 /*
  * pwcat.c
  *
- * Generate a printable version of the password database
+ * Generate a printable version of the password database.
  */
 /*
  * Arnold Robbins, arnold@skeeve.com, May 1993
diff --git a/awklib/eg/lib/quicksort.awk b/awklib/eg/lib/quicksort.awk
index 7a635d6f..43357ac6 100644
--- a/awklib/eg/lib/quicksort.awk
+++ b/awklib/eg/lib/quicksort.awk
@@ -1,8 +1,9 @@
 # quicksort.awk --- Quicksort algorithm, with user-supplied
 #                   comparison function
 #
-# Arnold Robbins, arnoldskeeve.com, Public Domain
+# Arnold Robbins, arnold@skeeve.com, Public Domain
 # January 2009
+
 # quicksort --- C.A.R. Hoare's quick sort algorithm. See Wikipedia
 #               or almost any algorithms or computer science text
 #
diff --git a/awklib/eg/lib/strtonum.awk b/awklib/eg/lib/strtonum.awk
index a56ab50c..9342e789 100644
--- a/awklib/eg/lib/strtonum.awk
+++ b/awklib/eg/lib/strtonum.awk
@@ -3,8 +3,9 @@
 #
 # Arnold Robbins, arnold@skeeve.com, Public Domain
 # February, 2004
+# Revised June, 2014
 
-function mystrtonum(str,        ret, chars, n, i, k, c)
+function mystrtonum(str,        ret, n, i, k, c)
 {
     if (str ~ /^0[0-7]*$/) {
         # octal
@@ -17,7 +18,7 @@ function mystrtonum(str,        ret, chars, n, i, k, c)
 
             ret = ret * 8 + k
         }
-    } else if (str ~ /^0[xX][[:xdigit:]]+/) {
+    } else if (str ~ /^0[xX][[:xdigit:]]+$/) {
         # hexadecimal
         str = substr(str, 3)    # lop off leading 0x
         n = length(str)
@@ -25,10 +26,7 @@ function mystrtonum(str,        ret, chars, n, i, k, c)
         for (i = 1; i <= n; i++) {
             c = substr(str, i, 1)
             c = tolower(c)
-            if ((k = index("0123456789", c)) > 0)
-                k-- # adjust for 1-basing in awk
-            else if ((k = index("abcdef", c)) > 0)
-                k += 9
+            k = index("123456789abcdef", c)
 
             ret = ret * 16 + k
         }
diff --git a/awklib/eg/prog/alarm.awk b/awklib/eg/prog/alarm.awk
index 9bb1633c..63cf64a4 100644
--- a/awklib/eg/prog/alarm.awk
+++ b/awklib/eg/prog/alarm.awk
@@ -71,7 +71,7 @@ BEGIN    \
     # how long to sleep for
     naptime = target - current
     if (naptime <= 0) {
-        print "time is in the past!" > "/dev/stderr"
+        print "alarm: time is in the past!" > "/dev/stderr"
         exit 1
     }
     # zzzzzz..... go away if interrupted
diff --git a/awklib/eg/prog/cut.awk b/awklib/eg/prog/cut.awk
index 16b4bdaa..04d9bc11 100644
--- a/awklib/eg/prog/cut.awk
+++ b/awklib/eg/prog/cut.awk
@@ -34,7 +34,7 @@ BEGIN    \
             OFS = ""
         } else if (c == "d") {
             if (length(Optarg) > 1) {
-                printf("Using first character of %s" \
+                printf("cut: using first character of %s" \
                        " for delimiter\n", Optarg) > "/dev/stderr"
                 Optarg = substr(Optarg, 1, 1)
             }
@@ -43,7 +43,7 @@ BEGIN    \
             if (FS == " ")    # defeat awk semantics
                 FS = "[ ]"
         } else if (c == "s")
-            suppress++
+            suppress = 1
         else
             usage()
     }
@@ -75,7 +75,7 @@ function set_fieldlist(        n, m, i, j, k, f, g)
         if (index(f[i], "-") != 0) { # a range
             m = split(f[i], g, "-")
             if (m != 2 || g[1] >= g[2]) {
-                printf("bad field list: %s\n",
+                printf("cut: bad field list: %s\n",
                                   f[i]) > "/dev/stderr"
                 exit 1
             }
@@ -86,7 +86,7 @@ function set_fieldlist(        n, m, i, j, k, f, g)
     }
     nfields = j - 1
 }
-function set_charlist(    field, i, j, f, g, t,
+function set_charlist(    field, i, j, f, g, n, m, t,
                           filler, last, len)
 {
     field = 1   # count total fields
@@ -96,7 +96,7 @@ function set_charlist(    field, i, j, f, g, t,
         if (index(f[i], "-") != 0) { # range
             m = split(f[i], g, "-")
             if (m != 2 || g[1] >= g[2]) {
-                printf("bad character list: %s\n",
+                printf("cut: bad character list: %s\n",
                                f[i]) > "/dev/stderr"
                 exit 1
             }
diff --git a/awklib/eg/prog/egrep.awk b/awklib/eg/prog/egrep.awk
index 56d199c8..86b3cfda 100644
--- a/awklib/eg/prog/egrep.awk
+++ b/awklib/eg/prog/egrep.awk
@@ -90,9 +90,7 @@ function endfile(file)
 }
 END    \
 {
-    if (total == 0)
-        exit 1
-    exit 0
+    exit (total == 0)
 }
 function usage(    e)
 {
diff --git a/awklib/eg/prog/extract.awk b/awklib/eg/prog/extract.awk
index dc105728..12e30b54 100644
--- a/awklib/eg/prog/extract.awk
+++ b/awklib/eg/prog/extract.awk
@@ -10,7 +10,7 @@ BEGIN    { IGNORECASE = 1 }
 /^@c(omment)?[ \t]+system/    \
 {
     if (NF < 3) {
-        e = (FILENAME ":" FNR)
+        e = ("extract: " FILENAME ":" FNR)
         e = (e  ": badly formed `system' line")
         print e > "/dev/stderr"
         next
@@ -19,7 +19,7 @@ BEGIN    { IGNORECASE = 1 }
     $2 = ""
     stat = system($0)
     if (stat != 0) {
-        e = (FILENAME ":" FNR)
+        e = ("extract: " FILENAME ":" FNR)
         e = (e ": warning: system returned " stat)
         print e > "/dev/stderr"
     }
@@ -27,7 +27,7 @@ BEGIN    { IGNORECASE = 1 }
 /^@c(omment)?[ \t]+file/    \
 {
     if (NF != 3) {
-        e = (FILENAME ":" FNR ": badly formed `file' line")
+        e = ("extract: " FILENAME ":" FNR ": badly formed `file' line")
         print e > "/dev/stderr"
         next
     }
@@ -65,7 +65,7 @@ BEGIN    { IGNORECASE = 1 }
 }
 function unexpected_eof()
 {
-    printf("%s:%d: unexpected EOF or error\n",
+    printf("extract: %s:%d: unexpected EOF or error\n",
         FILENAME, FNR) > "/dev/stderr"
     exit 1
 }
diff --git a/awklib/eg/prog/id.awk b/awklib/eg/prog/id.awk
index 8b60a245..cf744447 100644
--- a/awklib/eg/prog/id.awk
+++ b/awklib/eg/prog/id.awk
@@ -5,6 +5,7 @@
 # Arnold Robbins, arnold@skeeve.com, Public Domain
 # May 1993
 # Revised February 1996
+# Revised May 2014
 
 # output is:
 # uid=12(foo) euid=34(bar) gid=3(baz) \
@@ -19,34 +20,26 @@ BEGIN    \
 
     printf("uid=%d", uid)
     pw = getpwuid(uid)
-    if (pw != "") {
-        split(pw, a, ":")
-        printf("(%s)", a[1])
-    }
+    if (pw != "")
+        pr_first_field(pw)
 
     if (euid != uid) {
         printf(" euid=%d", euid)
         pw = getpwuid(euid)
-        if (pw != "") {
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        }
+        if (pw != "")
+            pr_first_field(pw)
     }
 
     printf(" gid=%d", gid)
     pw = getgrgid(gid)
-    if (pw != "") {
-        split(pw, a, ":")
-        printf("(%s)", a[1])
-    }
+    if (pw != "")
+        pr_first_field(pw)
 
     if (egid != gid) {
         printf(" egid=%d", egid)
         pw = getgrgid(egid)
-        if (pw != "") {
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        }
+        if (pw != "")
+            pr_first_field(pw)
     }
 
     for (i = 1; ("group" i) in PROCINFO; i++) {
@@ -55,13 +48,17 @@ BEGIN    \
         group = PROCINFO["group" i]
         printf("%d", group)
         pw = getgrgid(group)
-        if (pw != "") {
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        }
+        if (pw != "")
+            pr_first_field(pw)
         if (("group" (i+1)) in PROCINFO)
             printf(",")
     }
 
     print ""
 }
+
+function pr_first_field(str,  a)
+{
+    split(str, a, ":")
+    printf("(%s)", a[1])
+}
diff --git a/awklib/eg/prog/igawk.sh b/awklib/eg/prog/igawk.sh
index 03d1c996..70edf606 100644
--- a/awklib/eg/prog/igawk.sh
+++ b/awklib/eg/prog/igawk.sh
@@ -115,7 +115,7 @@ BEGIN {
             }
             fpath = pathto($2)
             if (fpath == "") {
-                printf("igawk:%s:%d: cannot find %s\n",
+                printf("igawk: %s:%d: cannot find %s\n",
                     input[stackptr], FNR, $2) > "/dev/stderr"
                 continue
             }
diff --git a/awklib/eg/prog/split.awk b/awklib/eg/prog/split.awk
index c907530b..bcc73ae6 100644
--- a/awklib/eg/prog/split.awk
+++ b/awklib/eg/prog/split.awk
@@ -4,8 +4,9 @@
 #
 # Arnold Robbins, arnold@skeeve.com, Public Domain
 # May 1993
+# Revised slightly, May 2014
 
-# usage: split [-num] [file] [outname]
+# usage: split [-count] [file] [outname]
 
 BEGIN {
     outfile = "x"    # default
@@ -14,7 +15,7 @@ BEGIN {
         usage()
 
     i = 1
-    if (ARGV[i] ~ /^-[[:digit:]]+$/) {
+    if (i in ARGV && ARGV[i] ~ /^-[[:digit:]]+$/) {
         count = -ARGV[i]
         ARGV[i] = ""
         i++
diff --git a/bootstrap.sh b/bootstrap.sh
index 496d8a03..85cdd196 100755
--- a/bootstrap.sh
+++ b/bootstrap.sh
@@ -3,7 +3,7 @@
 # bootstrap.sh --- touch relevant files to avoid out-of-date issues in
 #		   Git sandboxes
 
-# Copyright (C) 2007, 2009-2013 the Free Software Foundation, Inc.
+# Copyright (C) 2007, 2009-2014 the Free Software Foundation, Inc.
 # 
 # This file is part of GAWK, the GNU implementation of the
 # AWK Programming Language.
@@ -41,4 +41,3 @@ touch po/*.gmo
 touch po/stamp-po
 touch awkgram.c
 touch command.c
-touch version.c
diff --git a/builtin.c b/builtin.c
index b3e2962b..54f52350 100644
--- a/builtin.c
+++ b/builtin.c
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -719,7 +719,7 @@ format_tree(
 	mpz_ptr zi;
 	mpfr_ptr mf;
 #endif
-	enum { MP_INT_WITH_PREC = 1, MP_INT_WITHOUT_PREC, MP_FLOAT } fmt_type;
+	enum { MP_NONE = 0, MP_INT_WITH_PREC = 1, MP_INT_WITHOUT_PREC, MP_FLOAT } fmt_type;
 
 	static const char sp[] = " ";
 	static const char zero_string[] = "0";
@@ -817,7 +817,7 @@ format_tree(
 		mf = NULL;
 		zi = NULL;
 #endif
-		fmt_type = 0;
+		fmt_type = MP_NONE;
 
 		lj = alt = big_flag = bigbig_flag = small_flag = false;
 		fill = sp;
@@ -994,9 +994,7 @@ check_pos:
 			goto check_pos;
 		case '\'':
 #if defined(HAVE_LOCALE_H)       
-			/* allow quote_flag if there is a thousands separator. */
-			if (loc.thousands_sep[0] != '\0')
-				quote_flag = true;
+			quote_flag = true;
 			goto check_pos;
 #else
 			goto retry;  
@@ -1196,6 +1194,9 @@ out0:
 			}
 			if (i < 1)
 				goto out_of_range;
+#if defined(HAVE_LOCALE_H)
+			quote_flag = (quote_flag && loc.thousands_sep[0] != 0);
+#endif
 			chp = &cpbufs[1].buf[i-1];
 			ii = jj = 0;
 			do {
@@ -1203,8 +1204,14 @@ out0:
 				chp--; i--;
 #if defined(HAVE_LOCALE_H)
 				if (quote_flag && loc.grouping[ii] && ++jj == loc.grouping[ii]) {
-					if (i)	/* only add if more digits coming */
-						PREPEND(loc.thousands_sep[0]);	/* XXX - assumption it's one char */
+					if (i) {	/* only add if more digits coming */
+						int k;
+						const char *ts = loc.thousands_sep;
+
+						for (k = strlen(ts) - 1; k >= 0; k--) {
+							PREPEND(ts[k]);
+						}
+					}
 					if (loc.grouping[ii+1] == 0)
 						jj = 0;		/* keep using current val in loc.grouping[ii] */
 					else if (loc.grouping[ii+1] == CHAR_MAX)
@@ -1360,6 +1367,9 @@ mpf1:
 #ifdef HAVE_MPFR
 	int0:
 #endif
+#if defined(HAVE_LOCALE_H)
+			quote_flag = (quote_flag && loc.thousands_sep[0] != 0);
+#endif
 			/*
 			 * When to fill with zeroes is of course not simple.
 			 * First: No zero fill if left-justifying.
@@ -1378,8 +1388,14 @@ mpf1:
 				uval /= base;
 #if defined(HAVE_LOCALE_H)
 				if (base == 10 && quote_flag && loc.grouping[ii] && ++jj == loc.grouping[ii]) {
-					if (uval)	/* only add if more digits coming */
-						PREPEND(loc.thousands_sep[0]);	/* XXX --- assumption it's one char */
+					if (uval) {	/* only add if more digits coming */
+						int k;
+						const char *ts = loc.thousands_sep;
+
+						for (k = strlen(ts) - 1; k >= 0; k--) {
+							PREPEND(ts[k]);
+						}
+					}
 					if (loc.grouping[ii+1] == 0)                                          
 						jj = 0;     /* keep using current val in loc.grouping[ii] */
 					else if (loc.grouping[ii+1] == CHAR_MAX)                        
@@ -1999,10 +2015,10 @@ do_mktime(int nargs)
 			& hour, & minute, & second,
 		        & dst);
 
-	if (do_lint /* Ready? Set! Go: */
-		&& (    (second < 0 || second > 60)
-		|| (minute < 0 || minute > 60)
-		|| (hour < 0 || hour > 23)
+	if (   do_lint /* Ready? Set! Go: */
+	    && (   (second < 0 || second > 60)
+		|| (minute < 0 || minute > 59)
+		|| (hour < 0 || hour > 23) /* FIXME ISO 8601 allows 24 ? */
 		|| (day < 1 || day > 31)
 		|| (month < 1 || month > 12) ))
 			lintwarn(_("mktime: at least one of the values is out of the default range"));
@@ -2438,8 +2454,14 @@ do_rand(int nargs ATTRIBUTE_UNUSED)
  	 */
  
 	do {
-	 	tmprand = 0.5 + ( (random()/RAND_DIVISOR + random())
-					/ RAND_DIVISOR);
+		long d1, d2;
+		/*
+		 * Do the calls in predictable order to avoid
+		 * compiler differences in order of evaluation.
+		 */
+		d1 = random();
+		d2 = random();
+	 	tmprand = 0.5 + ( (d1/RAND_DIVISOR + d2) / RAND_DIVISOR );
 		tmprand -= 0.5;
 	} while (tmprand == 1.0);
 
@@ -2686,23 +2708,28 @@ do_match(int nargs)
  * 2001 standard:
  * 
  * sub(ere, repl[, in ])
- *  Substitute the string repl in place of the first instance of the extended regular
- *  expression ERE in string in and return the number of substitutions. An ampersand
- *  ('&') appearing in the string repl shall be replaced by the string from in that
- *  matches the ERE. An ampersand preceded with a backslash ('\') shall be
- *  interpreted as the literal ampersand character. An occurrence of two consecutive
- *  backslashes shall be interpreted as just a single literal backslash character. Any
- *  other occurrence of a backslash (for example, preceding any other character) shall
- *  be treated as a literal backslash character. Note that if repl is a string literal (the
- *  lexical token STRING; see Grammar (on page 170)), the handling of the
- *  ampersand character occurs after any lexical processing, including any lexical
- *  backslash escape sequence processing. If in is specified and it is not an lvalue (see
- *  Expressions in awk (on page 156)), the behavior is undefined. If in is omitted, awk
- *  shall use the current record ($0) in its place.
+ *  Substitute the string repl in place of the first instance of the
+ *  extended regular expression ERE in string in and return the number of
+ *  substitutions. An ampersand ('&') appearing in the string repl shall
+ *  be replaced by the string from in that matches the ERE. An ampersand
+ *  preceded with a backslash ('\') shall be interpreted as the literal
+ *  ampersand character. An occurrence of two consecutive backslashes shall
+ *  be interpreted as just a single literal backslash character. Any other
+ *  occurrence of a backslash (for example, preceding any other character)
+ *  shall be treated as a literal backslash character. Note that if repl is a
+ *  string literal (the lexical token STRING; see Grammar (on page 170)), the
+ *  handling of the ampersand character occurs after any lexical processing,
+ *  including any lexical backslash escape sequence processing. If in is
+ *  specified and it is not an lvalue (see Expressions in awk (on page 156)),
+ *  the behavior is undefined. If in is omitted, awk shall use the current
+ *  record ($0) in its place.
  *
- * 11/2010: The text in the 2008 standard is the same as just quoted.  However, POSIX behavior
- * is now the default.  This can change the behavior of awk programs.  The old behavior
- * is not available.
+ * 11/2010: The text in the 2008 standard is the same as just quoted.
+ * However, POSIX behavior is now the default.  This can change the behavior
+ * of awk programs.  The old behavior is not available.
+ *
+ * 7/2011: Reverted backslash handling to what it used to be. It was in
+ * gawk for too long. Should have known better.
  */
 
 /*
@@ -2813,9 +2840,11 @@ set_how_many:
 	repl = s->stptr;
 	replend = repl + s->stlen;
 	repllen = replend - repl;
+
 	emalloc(buf, char *, buflen + 2, "do_sub");
 	buf[buflen] = '\0';
 	buf[buflen + 1] = '\0';
+
 	ampersands = 0;
 
 	/*
diff --git a/cmd.h b/cmd.h
index 5a5fd294..6fca6d0a 100644
--- a/cmd.h
+++ b/cmd.h
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 2004, 2010, 2011, 2013 the Free Software Foundation, Inc.
+ * Copyright (C) 2004, 2010, 2011, 2013, 2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -109,7 +109,8 @@ enum argtype {
 /* non-number arguments to commands */ 
 
 enum nametypeval {
-	A_ARGS = 1,
+	A_NONE = 0,
+	A_ARGS,
 	A_BREAK,
 	A_DEL,
 	A_DISPLAY,
diff --git a/command.c b/command.c
index d170e4c1..2d4ccf8c 100644
--- a/command.c
+++ b/command.c
@@ -1,19 +1,19 @@
-/* A Bison parser, made by GNU Bison 2.7.12-4996.  */
+/* A Bison parser, made by GNU Bison 3.0.2.  */
 
 /* Bison implementation for Yacc-like parsers in C
-   
-      Copyright (C) 1984, 1989-1990, 2000-2013 Free Software Foundation, Inc.
-   
+
+   Copyright (C) 1984, 1989-1990, 2000-2013 Free Software Foundation, Inc.
+
    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.
-   
+
    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.
-   
+
    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
 
@@ -26,7 +26,7 @@
    special exception, which will cause the skeleton and the resulting
    Bison output files to be licensed under the GNU General Public
    License without this special exception.
-   
+
    This special exception was added by the Free Software Foundation in
    version 2.2 of Bison.  */
 
@@ -44,7 +44,7 @@
 #define YYBISON 1
 
 /* Bison version.  */
-#define YYBISON_VERSION "2.7.12-4996"
+#define YYBISON_VERSION "3.0.2"
 
 /* Skeleton name.  */
 #define YYSKELETON_NAME "yacc.c"
@@ -63,14 +63,14 @@
 #define yyparse         zzparse
 #define yylex           zzlex
 #define yyerror         zzerror
-#define yylval          zzlval
-#define yychar          zzchar
 #define yydebug         zzdebug
 #define yynerrs         zznerrs
 
+#define yylval          zzlval
+#define yychar          zzchar
+
 /* Copy the first part of user declarations.  */
-/* Line 371 of yacc.c  */
-#line 26 "command.y"
+#line 26 "command.y" /* yacc.c:339  */
 
 #include "awk.h"
 #include "cmd.h"
@@ -99,10 +99,10 @@ static bool in_eval = false;
 static const char start_EVAL[] = "function @eval(){";
 static const char end_EVAL[] = "}";	
 static CMDARG *append_statement(CMDARG *stmt_list, char *stmt);
-static char *next_word(char *p, int len, char **endp);
 static NODE *concat_args(CMDARG *a, int count);
 
 #ifdef HAVE_LIBREADLINE
+static char *next_word(char *p, int len, char **endp);
 static void history_expand_line(char **line);
 static char *command_generator(const char *text, int state);
 static char *srcfile_generator(const char *text, int state);
@@ -137,14 +137,13 @@ static void append_cmdarg(CMDARG *arg);
 static int find_argument(CMDARG *arg);
 #define YYSTYPE CMDARG *
 
-/* Line 371 of yacc.c  */
-#line 142 "command.c"
+#line 141 "command.c" /* yacc.c:339  */
 
-# ifndef YY_NULL
+# ifndef YY_NULLPTR
 #  if defined __cplusplus && 201103L <= __cplusplus
-#   define YY_NULL nullptr
+#   define YY_NULLPTR nullptr
 #  else
-#   define YY_NULL 0
+#   define YY_NULLPTR 0
 #  endif
 # endif
 
@@ -157,7 +156,7 @@ static int find_argument(CMDARG *arg);
 #endif
 
 
-/* Enabling traces.  */
+/* Debug traces.  */
 #ifndef YYDEBUG
 # define YYDEBUG 0
 #endif
@@ -165,59 +164,58 @@ static int find_argument(CMDARG *arg);
 extern int zzdebug;
 #endif
 
-/* Tokens.  */
+/* Token type.  */
 #ifndef YYTOKENTYPE
 # define YYTOKENTYPE
-   /* Put the tokens into the symbol table, so that GDB and other debuggers
-      know about them.  */
-   enum yytokentype {
-     D_BACKTRACE = 258,
-     D_BREAK = 259,
-     D_CLEAR = 260,
-     D_CONTINUE = 261,
-     D_DELETE = 262,
-     D_DISABLE = 263,
-     D_DOWN = 264,
-     D_ENABLE = 265,
-     D_FINISH = 266,
-     D_FRAME = 267,
-     D_HELP = 268,
-     D_IGNORE = 269,
-     D_INFO = 270,
-     D_LIST = 271,
-     D_NEXT = 272,
-     D_NEXTI = 273,
-     D_PRINT = 274,
-     D_PRINTF = 275,
-     D_QUIT = 276,
-     D_RETURN = 277,
-     D_RUN = 278,
-     D_SET = 279,
-     D_STEP = 280,
-     D_STEPI = 281,
-     D_TBREAK = 282,
-     D_UP = 283,
-     D_UNTIL = 284,
-     D_DISPLAY = 285,
-     D_UNDISPLAY = 286,
-     D_WATCH = 287,
-     D_UNWATCH = 288,
-     D_DUMP = 289,
-     D_TRACE = 290,
-     D_INT = 291,
-     D_STRING = 292,
-     D_NODE = 293,
-     D_VARIABLE = 294,
-     D_OPTION = 295,
-     D_COMMANDS = 296,
-     D_END = 297,
-     D_SILENT = 298,
-     D_SOURCE = 299,
-     D_SAVE = 300,
-     D_EVAL = 301,
-     D_CONDITION = 302,
-     D_STATEMENT = 303
-   };
+  enum yytokentype
+  {
+    D_BACKTRACE = 258,
+    D_BREAK = 259,
+    D_CLEAR = 260,
+    D_CONTINUE = 261,
+    D_DELETE = 262,
+    D_DISABLE = 263,
+    D_DOWN = 264,
+    D_ENABLE = 265,
+    D_FINISH = 266,
+    D_FRAME = 267,
+    D_HELP = 268,
+    D_IGNORE = 269,
+    D_INFO = 270,
+    D_LIST = 271,
+    D_NEXT = 272,
+    D_NEXTI = 273,
+    D_PRINT = 274,
+    D_PRINTF = 275,
+    D_QUIT = 276,
+    D_RETURN = 277,
+    D_RUN = 278,
+    D_SET = 279,
+    D_STEP = 280,
+    D_STEPI = 281,
+    D_TBREAK = 282,
+    D_UP = 283,
+    D_UNTIL = 284,
+    D_DISPLAY = 285,
+    D_UNDISPLAY = 286,
+    D_WATCH = 287,
+    D_UNWATCH = 288,
+    D_DUMP = 289,
+    D_TRACE = 290,
+    D_INT = 291,
+    D_STRING = 292,
+    D_NODE = 293,
+    D_VARIABLE = 294,
+    D_OPTION = 295,
+    D_COMMANDS = 296,
+    D_END = 297,
+    D_SILENT = 298,
+    D_SOURCE = 299,
+    D_SAVE = 300,
+    D_EVAL = 301,
+    D_CONDITION = 302,
+    D_STATEMENT = 303
+  };
 #endif
 /* Tokens.  */
 #define D_BACKTRACE 258
@@ -267,37 +265,23 @@ extern int zzdebug;
 #define D_CONDITION 302
 #define D_STATEMENT 303
 
-
-
+/* Value type.  */
 #if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED
 typedef int YYSTYPE;
 # define YYSTYPE_IS_TRIVIAL 1
-# define yystype YYSTYPE /* obsolescent; will be withdrawn */
 # define YYSTYPE_IS_DECLARED 1
 #endif
 
+
 extern YYSTYPE zzlval;
 
-#ifdef YYPARSE_PARAM
-#if defined __STDC__ || defined __cplusplus
-int zzparse (void *YYPARSE_PARAM);
-#else
-int zzparse ();
-#endif
-#else /* ! YYPARSE_PARAM */
-#if defined __STDC__ || defined __cplusplus
 int zzparse (void);
-#else
-int zzparse ();
-#endif
-#endif /* ! YYPARSE_PARAM */
 
 
 
 /* Copy the second part of user declarations.  */
 
-/* Line 390 of yacc.c  */
-#line 301 "command.c"
+#line 285 "command.c" /* yacc.c:358  */
 
 #ifdef short
 # undef short
@@ -311,11 +295,8 @@ typedef unsigned char yytype_uint8;
 
 #ifdef YYTYPE_INT8
 typedef YYTYPE_INT8 yytype_int8;
-#elif (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-typedef signed char yytype_int8;
 #else
-typedef short int yytype_int8;
+typedef signed char yytype_int8;
 #endif
 
 #ifdef YYTYPE_UINT16
@@ -335,8 +316,7 @@ typedef short int yytype_int16;
 #  define YYSIZE_T __SIZE_TYPE__
 # elif defined size_t
 #  define YYSIZE_T size_t
-# elif ! defined YYSIZE_T && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+# elif ! defined YYSIZE_T
 #  include <stddef.h> /* INFRINGES ON USER NAME SPACE */
 #  define YYSIZE_T size_t
 # else
@@ -358,11 +338,30 @@ typedef short int yytype_int16;
 # endif
 #endif
 
-#ifndef __attribute__
-/* This feature is available in gcc versions 2.5 and later.  */
-# if (! defined __GNUC__ || __GNUC__ < 2 \
-      || (__GNUC__ == 2 && __GNUC_MINOR__ < 5))
-#  define __attribute__(Spec) /* empty */
+#ifndef YY_ATTRIBUTE
+# if (defined __GNUC__                                               \
+      && (2 < __GNUC__ || (__GNUC__ == 2 && 96 <= __GNUC_MINOR__)))  \
+     || defined __SUNPRO_C && 0x5110 <= __SUNPRO_C
+#  define YY_ATTRIBUTE(Spec) __attribute__(Spec)
+# else
+#  define YY_ATTRIBUTE(Spec) /* empty */
+# endif
+#endif
+
+#ifndef YY_ATTRIBUTE_PURE
+# define YY_ATTRIBUTE_PURE   YY_ATTRIBUTE ((__pure__))
+#endif
+
+#ifndef YY_ATTRIBUTE_UNUSED
+# define YY_ATTRIBUTE_UNUSED YY_ATTRIBUTE ((__unused__))
+#endif
+
+#if !defined _Noreturn \
+     && (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112)
+# if defined _MSC_VER && 1200 <= _MSC_VER
+#  define _Noreturn __declspec (noreturn)
+# else
+#  define _Noreturn YY_ATTRIBUTE ((__noreturn__))
 # endif
 #endif
 
@@ -373,24 +372,25 @@ typedef short int yytype_int16;
 # define YYUSE(E) /* empty */
 #endif
 
-
-/* Identity function, used to suppress warnings about constant conditions.  */
-#ifndef lint
-# define YYID(N) (N)
+#if defined __GNUC__ && 407 <= __GNUC__ * 100 + __GNUC_MINOR__
+/* Suppress an incorrect diagnostic about yylval being uninitialized.  */
+# define YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN \
+    _Pragma ("GCC diagnostic push") \
+    _Pragma ("GCC diagnostic ignored \"-Wuninitialized\"")\
+    _Pragma ("GCC diagnostic ignored \"-Wmaybe-uninitialized\"")
+# define YY_IGNORE_MAYBE_UNINITIALIZED_END \
+    _Pragma ("GCC diagnostic pop")
 #else
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-static int
-YYID (int yyi)
-#else
-static int
-YYID (yyi)
-    int yyi;
+# define YY_INITIAL_VALUE(Value) Value
 #endif
-{
-  return yyi;
-}
+#ifndef YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
+# define YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
+# define YY_IGNORE_MAYBE_UNINITIALIZED_END
 #endif
+#ifndef YY_INITIAL_VALUE
+# define YY_INITIAL_VALUE(Value) /* Nothing. */
+#endif
+
 
 #if ! defined yyoverflow || YYERROR_VERBOSE
 
@@ -409,8 +409,7 @@ YYID (yyi)
 #    define alloca _alloca
 #   else
 #    define YYSTACK_ALLOC alloca
-#    if ! defined _ALLOCA_H && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+#    if ! defined _ALLOCA_H && ! defined EXIT_SUCCESS
 #     include <stdlib.h> /* INFRINGES ON USER NAME SPACE */
       /* Use EXIT_SUCCESS as a witness for stdlib.h.  */
 #     ifndef EXIT_SUCCESS
@@ -422,8 +421,8 @@ YYID (yyi)
 # endif
 
 # ifdef YYSTACK_ALLOC
-   /* Pacify GCC's `empty if-body' warning.  */
-#  define YYSTACK_FREE(Ptr) do { /* empty */; } while (YYID (0))
+   /* Pacify GCC's 'empty if-body' warning.  */
+#  define YYSTACK_FREE(Ptr) do { /* empty */; } while (0)
 #  ifndef YYSTACK_ALLOC_MAXIMUM
     /* The OS might guarantee only one guard page at the bottom of the stack,
        and a page size can be as small as 4096 bytes.  So we cannot safely
@@ -439,7 +438,7 @@ YYID (yyi)
 #  endif
 #  if (defined __cplusplus && ! defined EXIT_SUCCESS \
        && ! ((defined YYMALLOC || defined malloc) \
-	     && (defined YYFREE || defined free)))
+             && (defined YYFREE || defined free)))
 #   include <stdlib.h> /* INFRINGES ON USER NAME SPACE */
 #   ifndef EXIT_SUCCESS
 #    define EXIT_SUCCESS 0
@@ -447,15 +446,13 @@ YYID (yyi)
 #  endif
 #  ifndef YYMALLOC
 #   define YYMALLOC malloc
-#   if ! defined malloc && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+#   if ! defined malloc && ! defined EXIT_SUCCESS
 void *malloc (YYSIZE_T); /* INFRINGES ON USER NAME SPACE */
 #   endif
 #  endif
 #  ifndef YYFREE
 #   define YYFREE free
-#   if ! defined free && ! defined EXIT_SUCCESS && (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+#   if ! defined free && ! defined EXIT_SUCCESS
 void free (void *); /* INFRINGES ON USER NAME SPACE */
 #   endif
 #  endif
@@ -465,7 +462,7 @@ void free (void *); /* INFRINGES ON USER NAME SPACE */
 
 #if (! defined yyoverflow \
      && (! defined __cplusplus \
-	 || (defined YYSTYPE_IS_TRIVIAL && YYSTYPE_IS_TRIVIAL)))
+         || (defined YYSTYPE_IS_TRIVIAL && YYSTYPE_IS_TRIVIAL)))
 
 /* A type that is properly aligned for any stack member.  */
 union yyalloc
@@ -490,16 +487,16 @@ union yyalloc
    elements in the stack, and YYPTR gives the new location of the
    stack.  Advance YYPTR to a properly aligned location for the next
    stack.  */
-# define YYSTACK_RELOCATE(Stack_alloc, Stack)				\
-    do									\
-      {									\
-	YYSIZE_T yynewbytes;						\
-	YYCOPY (&yyptr->Stack_alloc, Stack, yysize);			\
-	Stack = &yyptr->Stack_alloc;					\
-	yynewbytes = yystacksize * sizeof (*Stack) + YYSTACK_GAP_MAXIMUM; \
-	yyptr += yynewbytes / sizeof (*yyptr);				\
-      }									\
-    while (YYID (0))
+# define YYSTACK_RELOCATE(Stack_alloc, Stack)                           \
+    do                                                                  \
+      {                                                                 \
+        YYSIZE_T yynewbytes;                                            \
+        YYCOPY (&yyptr->Stack_alloc, Stack, yysize);                    \
+        Stack = &yyptr->Stack_alloc;                                    \
+        yynewbytes = yystacksize * sizeof (*Stack) + YYSTACK_GAP_MAXIMUM; \
+        yyptr += yynewbytes / sizeof (*yyptr);                          \
+      }                                                                 \
+    while (0)
 
 #endif
 
@@ -518,7 +515,7 @@ union yyalloc
           for (yyi = 0; yyi < (Count); yyi++)   \
             (Dst)[yyi] = (Src)[yyi];            \
         }                                       \
-      while (YYID (0))
+      while (0)
 #  endif
 # endif
 #endif /* !YYCOPY_NEEDED */
@@ -534,17 +531,19 @@ union yyalloc
 #define YYNNTS  55
 /* YYNRULES -- Number of rules.  */
 #define YYNRULES  156
-/* YYNRULES -- Number of states.  */
+/* YYNSTATES -- Number of states.  */
 #define YYNSTATES  203
 
-/* YYTRANSLATE(YYLEX) -- Bison symbol number corresponding to YYLEX.  */
+/* YYTRANSLATE[YYX] -- Symbol number corresponding to YYX as returned
+   by yylex, with out-of-bounds checking.  */
 #define YYUNDEFTOK  2
 #define YYMAXUTOK   303
 
-#define YYTRANSLATE(YYX)						\
+#define YYTRANSLATE(YYX)                                                \
   ((unsigned int) (YYX) <= YYMAXUTOK ? yytranslate[YYX] : YYUNDEFTOK)
 
-/* YYTRANSLATE[YYLEX] -- Bison symbol number corresponding to YYLEX.  */
+/* YYTRANSLATE[TOKEN-NUM] -- Symbol number corresponding to TOKEN-NUM
+   as returned by yylex, without out-of-bounds checking.  */
 static const yytype_uint8 yytranslate[] =
 {
        0,     2,     2,     2,     2,     2,     2,     2,     2,     2,
@@ -581,73 +580,7 @@ static const yytype_uint8 yytranslate[] =
 };
 
 #if YYDEBUG
-/* YYPRHS[YYN] -- Index of the first RHS symbol of rule number YYN in
-   YYRHS.  */
-static const yytype_uint16 yyprhs[] =
-{
-       0,     0,     3,     4,     7,     9,    12,    15,    17,    19,
-      21,    23,    25,    27,    29,    31,    33,    35,    37,    39,
-      41,    43,    45,    46,    51,    52,    53,    58,    62,    66,
-      69,    71,    73,    75,    78,    81,    84,    88,    91,    92,
-      96,    97,   101,   104,   107,   110,   113,   114,   120,   123,
-     124,   128,   129,   133,   134,   139,   142,   145,   148,   151,
-     154,   156,   158,   161,   162,   167,   169,   171,   173,   175,
-     176,   178,   180,   183,   187,   189,   190,   192,   194,   196,
-     197,   199,   203,   205,   206,   208,   210,   214,   218,   219,
-     220,   224,   226,   227,   233,   237,   238,   240,   241,   243,
-     244,   246,   247,   249,   251,   254,   256,   259,   263,   265,
-     268,   272,   274,   276,   278,   280,   284,   286,   287,   289,
-     291,   293,   295,   297,   301,   305,   309,   313,   314,   316,
-     318,   320,   322,   325,   328,   330,   334,   336,   340,   344,
-     346,   349,   351,   354,   357,   359,   362,   365,   366,   368,
-     369,   371,   373,   376,   378,   381,   384
-};
-
-/* YYRHS -- A `-1'-separated list of the rules' RHS.  */
-static const yytype_int8 yyrhs[] =
-{
-      60,     0,    -1,    -1,    60,    61,    -1,   113,    -1,    71,
-     113,    -1,     1,   113,    -1,     6,    -1,    17,    -1,    18,
-      -1,    25,    -1,    26,    -1,    31,    -1,    33,    -1,     8,
-      -1,     7,    -1,    28,    -1,     9,    -1,     3,    -1,    12,
-      -1,     4,    -1,    27,    -1,    -1,    46,    66,    81,   113,
-      -1,    -1,    -1,    68,    48,    69,   113,    -1,    67,    68,
-      42,    -1,    46,    66,    84,    -1,    13,    94,    -1,    21,
-      -1,    23,    -1,    11,    -1,    62,   109,    -1,    64,   110,
-      -1,    15,    37,    -1,    14,   111,    36,    -1,    10,    95,
-      -1,    -1,    19,    72,    97,    -1,    -1,    20,    73,    99,
-      -1,    16,   100,    -1,    29,    87,    -1,     5,    87,    -1,
-      65,    88,    -1,    -1,    24,    74,   107,    49,   108,    -1,
-      40,    85,    -1,    -1,    22,    75,    93,    -1,    -1,    30,
-      76,    91,    -1,    -1,    32,    77,   107,    79,    -1,    63,
-     102,    -1,    34,    92,    -1,    44,    37,    -1,    45,    37,
-      -1,    41,    80,    -1,    42,    -1,    43,    -1,    35,    37,
-      -1,    -1,    47,   111,    78,    79,    -1,    70,    -1,    83,
-      -1,   109,    -1,     1,    -1,    -1,    82,    -1,    39,    -1,
-      82,    39,    -1,    82,    50,    39,    -1,     1,    -1,    -1,
-      84,    -1,     1,    -1,    38,    -1,    -1,    37,    -1,    37,
-      49,    37,    -1,    37,    -1,    -1,   111,    -1,    86,    -1,
-      37,    51,   111,    -1,    37,    51,    86,    -1,    -1,    -1,
-     111,    89,    79,    -1,    86,    -1,    -1,    37,    51,   111,
-      90,    79,    -1,    37,    51,    86,    -1,    -1,   107,    -1,
-      -1,    37,    -1,    -1,   108,    -1,    -1,    37,    -1,   102,
-      -1,    37,   102,    -1,   107,    -1,    52,    39,    -1,    52,
-      39,   106,    -1,    96,    -1,    97,    96,    -1,    97,    50,
-      96,    -1,     1,    -1,    38,    -1,   107,    -1,    98,    -1,
-      99,    50,    98,    -1,     1,    -1,    -1,    53,    -1,    54,
-      -1,   111,    -1,    86,    -1,   101,    -1,    37,    51,   111,
-      -1,    37,    51,    86,    -1,    37,    51,   101,    -1,   111,
-      54,   111,    -1,    -1,   103,    -1,     1,    -1,   111,    -1,
-     101,    -1,   103,   111,    -1,   103,   101,    -1,   108,    -1,
-     104,    50,   108,    -1,     1,    -1,    55,   104,    56,    -1,
-      55,   104,     1,    -1,   105,    -1,   106,   105,    -1,    39,
-      -1,    57,    38,    -1,    39,   106,    -1,    38,    -1,    53,
-      38,    -1,    54,    38,    -1,    -1,   111,    -1,    -1,   112,
-      -1,    36,    -1,    53,    36,    -1,    36,    -1,    53,    36,
-      -1,    54,    36,    -1,    58,    -1
-};
-
-/* YYRLINE[YYN] -- source line where rule number YYN was defined.  */
+  /* YYRLINE[YYN] -- Source line where rule number YYN was defined.  */
 static const yytype_uint16 yyrline[] =
 {
        0,   106,   106,   108,   126,   127,   177,   184,   185,   186,
@@ -693,13 +626,13 @@ static const char *const yytname[] =
   "printf_args", "list_args", "integer_range", "opt_integer_list",
   "integer_list", "exp_list", "subscript", "subscript_list", "variable",
   "node", "opt_plus_integer", "opt_integer", "plus_integer", "integer",
-  "nls", YY_NULL
+  "nls", YY_NULLPTR
 };
 #endif
 
 # ifdef YYPRINT
-/* YYTOKNUM[YYLEX-NUM] -- Internal token number corresponding to
-   token YYLEX-NUM.  */
+/* YYTOKNUM[NUM] -- (External) token number corresponding to the
+   (internal) symbol number NUM (which must be that of a token).  */
 static const yytype_uint16 yytoknum[] =
 {
        0,   256,   257,   258,   259,   260,   261,   262,   263,   264,
@@ -711,90 +644,18 @@ static const yytype_uint16 yytoknum[] =
 };
 # endif
 
-/* YYR1[YYN] -- Symbol number of symbol that rule YYN derives.  */
-static const yytype_uint8 yyr1[] =
-{
-       0,    59,    60,    60,    61,    61,    61,    62,    62,    62,
-      62,    62,    63,    63,    63,    63,    64,    64,    64,    64,
-      65,    65,    66,    67,    68,    69,    68,    70,    70,    71,
-      71,    71,    71,    71,    71,    71,    71,    71,    72,    71,
-      73,    71,    71,    71,    71,    71,    74,    71,    71,    75,
-      71,    76,    71,    77,    71,    71,    71,    71,    71,    71,
-      71,    71,    71,    78,    71,    71,    79,    80,    80,    81,
-      81,    82,    82,    82,    82,    83,    83,    83,    84,    85,
-      85,    85,    86,    87,    87,    87,    87,    87,    88,    89,
-      88,    88,    90,    88,    88,    91,    91,    92,    92,    93,
-      93,    94,    94,    95,    95,    96,    96,    96,    97,    97,
-      97,    97,    98,    98,    99,    99,    99,   100,   100,   100,
-     100,   100,   100,   100,   100,   100,   101,   102,   102,   102,
-     103,   103,   103,   103,   104,   104,   104,   105,   105,   106,
-     106,   107,   107,   107,   108,   108,   108,   109,   109,   110,
-     110,   111,   111,   112,   112,   112,   113
-};
+#define YYPACT_NINF -151
 
-/* YYR2[YYN] -- Number of symbols composing right hand side of rule YYN.  */
-static const yytype_uint8 yyr2[] =
-{
-       0,     2,     0,     2,     1,     2,     2,     1,     1,     1,
-       1,     1,     1,     1,     1,     1,     1,     1,     1,     1,
-       1,     1,     0,     4,     0,     0,     4,     3,     3,     2,
-       1,     1,     1,     2,     2,     2,     3,     2,     0,     3,
-       0,     3,     2,     2,     2,     2,     0,     5,     2,     0,
-       3,     0,     3,     0,     4,     2,     2,     2,     2,     2,
-       1,     1,     2,     0,     4,     1,     1,     1,     1,     0,
-       1,     1,     2,     3,     1,     0,     1,     1,     1,     0,
-       1,     3,     1,     0,     1,     1,     3,     3,     0,     0,
-       3,     1,     0,     5,     3,     0,     1,     0,     1,     0,
-       1,     0,     1,     1,     2,     1,     2,     3,     1,     2,
-       3,     1,     1,     1,     1,     3,     1,     0,     1,     1,
-       1,     1,     1,     3,     3,     3,     3,     0,     1,     1,
-       1,     1,     2,     2,     1,     3,     1,     3,     3,     1,
-       2,     1,     2,     2,     1,     2,     2,     0,     1,     0,
-       1,     1,     2,     1,     2,     2,     1
-};
+#define yypact_value_is_default(Yystate) \
+  (!!((Yystate) == (-151)))
 
-/* YYDEFACT[STATE-NAME] -- Default reduction number in state STATE-NUM.
-   Performed when YYTABLE doesn't specify something else to do.  Zero
-   means the default is an error.  */
-static const yytype_uint8 yydefact[] =
-{
-       2,     0,     1,     0,    18,    20,    83,     7,    15,    14,
-      17,     0,    32,    19,   101,     0,     0,   117,     8,     9,
-      38,    40,    30,    49,    31,    46,    10,    11,    21,    16,
-      83,    51,    12,    53,    13,    97,     0,    79,     0,    60,
-      61,     0,     0,    22,     0,   156,     3,   147,     0,   149,
-      88,    24,    65,     0,     4,     6,   151,    82,     0,    85,
-      44,    84,   129,     0,    37,   131,   103,   128,   130,   102,
-      29,     0,    35,    82,   118,   119,   121,    42,   122,   120,
-       0,     0,    99,     0,    43,    95,     0,    98,    56,    62,
-      80,    48,    68,    59,    67,   148,    57,    58,     0,    63,
-      33,    55,   153,     0,     0,    34,   150,    82,    91,    45,
-      89,     0,     5,     0,   152,   104,   133,   132,     0,    36,
-       0,   111,   141,     0,     0,   108,    39,   105,   116,   112,
-     114,    41,   113,   144,     0,     0,    50,   100,     0,    52,
-      96,     0,     0,    74,    78,    71,     0,    70,    28,     0,
-     154,   155,     0,     0,    27,    25,    82,    87,    86,   126,
-     124,   125,   123,     0,   139,   143,   106,   142,     0,   109,
-       0,   145,   146,     0,    77,    54,    66,    76,    81,    23,
-      72,     0,    64,    94,    92,    90,     0,   136,     0,   134,
-     140,   107,   110,   115,    47,    73,     0,    26,   138,     0,
-     137,    93,   135
-};
+#define YYTABLE_NINF -148
 
-/* YYDEFGOTO[NTERM-NUM].  */
-static const yytype_int16 yydefgoto[] =
-{
-      -1,     1,    46,    47,    48,    49,    50,    98,    51,   111,
-     186,    52,    53,    80,    81,    83,    82,    85,    86,   149,
-     175,    93,   146,   147,   176,   177,    91,    59,    60,   109,
-     153,   196,   139,    88,   136,    70,    64,   125,   126,   130,
-     131,    77,    65,    66,    67,   188,   164,   165,   127,   137,
-      94,   105,    68,   106,    54
-};
+#define yytable_value_is_error(Yytable_value) \
+  0
 
-/* YYPACT[STATE-NUM] -- Index in YYTABLE of the portion describing
-   STATE-NUM.  */
-#define YYPACT_NINF -151
+  /* YYPACT[STATE-NUM] -- Index in YYTABLE of the portion describing
+     STATE-NUM.  */
 static const yytype_int16 yypact[] =
 {
     -151,   145,  -151,   -34,  -151,  -151,    50,  -151,  -151,  -151,
@@ -820,7 +681,35 @@ static const yytype_int16 yypact[] =
     -151,  -151,  -151
 };
 
-/* YYPGOTO[NTERM-NUM].  */
+  /* YYDEFACT[STATE-NUM] -- Default reduction number in state STATE-NUM.
+     Performed when YYTABLE does not specify something else to do.  Zero
+     means the default is an error.  */
+static const yytype_uint8 yydefact[] =
+{
+       2,     0,     1,     0,    18,    20,    83,     7,    15,    14,
+      17,     0,    32,    19,   101,     0,     0,   117,     8,     9,
+      38,    40,    30,    49,    31,    46,    10,    11,    21,    16,
+      83,    51,    12,    53,    13,    97,     0,    79,     0,    60,
+      61,     0,     0,    22,     0,   156,     3,   147,     0,   149,
+      88,    24,    65,     0,     4,     6,   151,    82,     0,    85,
+      44,    84,   129,     0,    37,   131,   103,   128,   130,   102,
+      29,     0,    35,    82,   118,   119,   121,    42,   122,   120,
+       0,     0,    99,     0,    43,    95,     0,    98,    56,    62,
+      80,    48,    68,    59,    67,   148,    57,    58,     0,    63,
+      33,    55,   153,     0,     0,    34,   150,    82,    91,    45,
+      89,     0,     5,     0,   152,   104,   133,   132,     0,    36,
+       0,   111,   141,     0,     0,   108,    39,   105,   116,   112,
+     114,    41,   113,   144,     0,     0,    50,   100,     0,    52,
+      96,     0,     0,    74,    78,    71,     0,    70,    28,     0,
+     154,   155,     0,     0,    27,    25,    82,    87,    86,   126,
+     124,   125,   123,     0,   139,   143,   106,   142,     0,   109,
+       0,   145,   146,     0,    77,    54,    66,    76,    81,    23,
+      72,     0,    64,    94,    92,    90,     0,   136,     0,   134,
+     140,   107,   110,   115,    47,    73,     0,    26,   138,     0,
+     137,    93,   135
+};
+
+  /* YYPGOTO[NTERM-NUM].  */
 static const yytype_int16 yypgoto[] =
 {
     -151,  -151,  -151,  -151,  -151,  -151,  -151,  -151,  -151,  -151,
@@ -831,10 +720,20 @@ static const yytype_int16 yypgoto[] =
       97,  -151,    -5,  -151,    -3
 };
 
-/* YYTABLE[YYPACT[STATE-NUM]].  What to do in state STATE-NUM.  If
-   positive, shift that token.  If negative, reduce the rule which
-   number is the opposite.  If YYTABLE_NINF, syntax error.  */
-#define YYTABLE_NINF -148
+  /* YYDEFGOTO[NTERM-NUM].  */
+static const yytype_int16 yydefgoto[] =
+{
+      -1,     1,    46,    47,    48,    49,    50,    98,    51,   111,
+     186,    52,    53,    80,    81,    83,    82,    85,    86,   149,
+     175,    93,   146,   147,   176,   177,    91,    59,    60,   109,
+     153,   196,   139,    88,   136,    70,    64,   125,   126,   130,
+     131,    77,    65,    66,    67,   188,   164,   165,   127,   137,
+      94,   105,    68,   106,    54
+};
+
+  /* YYTABLE[YYPACT[STATE-NUM]] -- What to do in state STATE-NUM.  If
+     positive, shift that token.  If negative, reduce the rule whose
+     number is the opposite.  If YYTABLE_NINF, syntax error.  */
 static const yytype_int16 yytable[] =
 {
       55,    61,    76,    78,   132,   121,   138,   174,   140,   141,
@@ -860,12 +759,6 @@ static const yytype_int16 yytable[] =
        0,     0,     0,    45
 };
 
-#define yypact_value_is_default(Yystate) \
-  (!!((Yystate) == (-151)))
-
-#define yytable_value_is_error(Yytable_value) \
-  YYID (0)
-
 static const yytype_int16 yycheck[] =
 {
        3,     6,    17,    17,    81,     1,    83,     1,    85,    86,
@@ -891,8 +784,8 @@ static const yytype_int16 yycheck[] =
       -1,    -1,    -1,    58
 };
 
-/* YYSTOS[STATE-NUM] -- The (internal number of the) accessing
-   symbol of state STATE-NUM.  */
+  /* YYSTOS[STATE-NUM] -- The (internal number of the) accessing
+     symbol of state STATE-NUM.  */
 static const yytype_uint8 yystos[] =
 {
        0,    60,     0,     1,     3,     4,     5,     6,     7,     8,
@@ -918,30 +811,58 @@ static const yytype_uint8 yystos[] =
       56,    79,   108
 };
 
-#define yyerrok		(yyerrstatus = 0)
-#define yyclearin	(yychar = YYEMPTY)
-#define YYEMPTY		(-2)
-#define YYEOF		0
-
-#define YYACCEPT	goto yyacceptlab
-#define YYABORT		goto yyabortlab
-#define YYERROR		goto yyerrorlab
-
-
-/* Like YYERROR except do call yyerror.  This remains here temporarily
-   to ease the transition to the new meaning of YYERROR, for GCC.
-   Once GCC version 2 has supplanted version 1, this can go.  However,
-   YYFAIL appears to be in use.  Nevertheless, it is formally deprecated
-   in Bison 2.4.2's NEWS entry, where a plan to phase it out is
-   discussed.  */
-
-#define YYFAIL		goto yyerrlab
-#if defined YYFAIL
-  /* This is here to suppress warnings from the GCC cpp's
-     -Wunused-macros.  Normally we don't worry about that warning, but
-     some users do, and we want to make it easy for users to remove
-     YYFAIL uses, which will produce warnings from Bison 2.5.  */
-#endif
+  /* YYR1[YYN] -- Symbol number of symbol that rule YYN derives.  */
+static const yytype_uint8 yyr1[] =
+{
+       0,    59,    60,    60,    61,    61,    61,    62,    62,    62,
+      62,    62,    63,    63,    63,    63,    64,    64,    64,    64,
+      65,    65,    66,    67,    68,    69,    68,    70,    70,    71,
+      71,    71,    71,    71,    71,    71,    71,    71,    72,    71,
+      73,    71,    71,    71,    71,    71,    74,    71,    71,    75,
+      71,    76,    71,    77,    71,    71,    71,    71,    71,    71,
+      71,    71,    71,    78,    71,    71,    79,    80,    80,    81,
+      81,    82,    82,    82,    82,    83,    83,    83,    84,    85,
+      85,    85,    86,    87,    87,    87,    87,    87,    88,    89,
+      88,    88,    90,    88,    88,    91,    91,    92,    92,    93,
+      93,    94,    94,    95,    95,    96,    96,    96,    97,    97,
+      97,    97,    98,    98,    99,    99,    99,   100,   100,   100,
+     100,   100,   100,   100,   100,   100,   101,   102,   102,   102,
+     103,   103,   103,   103,   104,   104,   104,   105,   105,   106,
+     106,   107,   107,   107,   108,   108,   108,   109,   109,   110,
+     110,   111,   111,   112,   112,   112,   113
+};
+
+  /* YYR2[YYN] -- Number of symbols on the right hand side of rule YYN.  */
+static const yytype_uint8 yyr2[] =
+{
+       0,     2,     0,     2,     1,     2,     2,     1,     1,     1,
+       1,     1,     1,     1,     1,     1,     1,     1,     1,     1,
+       1,     1,     0,     4,     0,     0,     4,     3,     3,     2,
+       1,     1,     1,     2,     2,     2,     3,     2,     0,     3,
+       0,     3,     2,     2,     2,     2,     0,     5,     2,     0,
+       3,     0,     3,     0,     4,     2,     2,     2,     2,     2,
+       1,     1,     2,     0,     4,     1,     1,     1,     1,     0,
+       1,     1,     2,     3,     1,     0,     1,     1,     1,     0,
+       1,     3,     1,     0,     1,     1,     3,     3,     0,     0,
+       3,     1,     0,     5,     3,     0,     1,     0,     1,     0,
+       1,     0,     1,     1,     2,     1,     2,     3,     1,     2,
+       3,     1,     1,     1,     1,     3,     1,     0,     1,     1,
+       1,     1,     1,     3,     3,     3,     3,     0,     1,     1,
+       1,     1,     2,     2,     1,     3,     1,     3,     3,     1,
+       2,     1,     2,     2,     1,     2,     2,     0,     1,     0,
+       1,     1,     2,     1,     2,     2,     1
+};
+
+
+#define yyerrok         (yyerrstatus = 0)
+#define yyclearin       (yychar = YYEMPTY)
+#define YYEMPTY         (-2)
+#define YYEOF           0
+
+#define YYACCEPT        goto yyacceptlab
+#define YYABORT         goto yyabortlab
+#define YYERROR         goto yyerrorlab
+
 
 #define YYRECOVERING()  (!!yyerrstatus)
 
@@ -958,27 +879,15 @@ do                                                              \
   else                                                          \
     {                                                           \
       yyerror (YY_("syntax error: cannot back up")); \
-      YYERROR;							\
-    }								\
-while (YYID (0))
+      YYERROR;                                                  \
+    }                                                           \
+while (0)
 
 /* Error token number */
-#define YYTERROR	1
-#define YYERRCODE	256
+#define YYTERROR        1
+#define YYERRCODE       256
 
 
-/* This macro is provided for backward compatibility. */
-#ifndef YY_LOCATION_PRINT
-# define YY_LOCATION_PRINT(File, Loc) ((void) 0)
-#endif
-
-
-/* YYLEX -- calling `yylex' with the right arguments.  */
-#ifdef YYLEX_PARAM
-# define YYLEX yylex (YYLEX_PARAM)
-#else
-# define YYLEX yylex ()
-#endif
 
 /* Enable debugging if requested.  */
 #if YYDEBUG
@@ -988,40 +897,36 @@ while (YYID (0))
 #  define YYFPRINTF fprintf
 # endif
 
-# define YYDPRINTF(Args)			\
-do {						\
-  if (yydebug)					\
-    YYFPRINTF Args;				\
-} while (YYID (0))
+# define YYDPRINTF(Args)                        \
+do {                                            \
+  if (yydebug)                                  \
+    YYFPRINTF Args;                             \
+} while (0)
+
+/* This macro is provided for backward compatibility. */
+#ifndef YY_LOCATION_PRINT
+# define YY_LOCATION_PRINT(File, Loc) ((void) 0)
+#endif
 
-# define YY_SYMBOL_PRINT(Title, Type, Value, Location)			  \
-do {									  \
-  if (yydebug)								  \
-    {									  \
-      YYFPRINTF (stderr, "%s ", Title);					  \
-      yy_symbol_print (stderr,						  \
-		  Type, Value); \
-      YYFPRINTF (stderr, "\n");						  \
-    }									  \
-} while (YYID (0))
 
+# define YY_SYMBOL_PRINT(Title, Type, Value, Location)                    \
+do {                                                                      \
+  if (yydebug)                                                            \
+    {                                                                     \
+      YYFPRINTF (stderr, "%s ", Title);                                   \
+      yy_symbol_print (stderr,                                            \
+                  Type, Value); \
+      YYFPRINTF (stderr, "\n");                                           \
+    }                                                                     \
+} while (0)
 
-/*--------------------------------.
-| Print this symbol on YYOUTPUT.  |
-`--------------------------------*/
 
-/*ARGSUSED*/
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
+/*----------------------------------------.
+| Print this symbol's value on YYOUTPUT.  |
+`----------------------------------------*/
+
 static void
 yy_symbol_value_print (FILE *yyoutput, int yytype, YYSTYPE const * const yyvaluep)
-#else
-static void
-yy_symbol_value_print (yyoutput, yytype, yyvaluep)
-    FILE *yyoutput;
-    int yytype;
-    YYSTYPE const * const yyvaluep;
-#endif
 {
   FILE *yyo = yyoutput;
   YYUSE (yyo);
@@ -1030,8 +935,6 @@ yy_symbol_value_print (yyoutput, yytype, yyvaluep)
 # ifdef YYPRINT
   if (yytype < YYNTOKENS)
     YYPRINT (yyoutput, yytoknum[yytype], *yyvaluep);
-# else
-  YYUSE (yyoutput);
 # endif
   YYUSE (yytype);
 }
@@ -1041,22 +944,11 @@ yy_symbol_value_print (yyoutput, yytype, yyvaluep)
 | Print this symbol on YYOUTPUT.  |
 `--------------------------------*/
 
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static void
 yy_symbol_print (FILE *yyoutput, int yytype, YYSTYPE const * const yyvaluep)
-#else
-static void
-yy_symbol_print (yyoutput, yytype, yyvaluep)
-    FILE *yyoutput;
-    int yytype;
-    YYSTYPE const * const yyvaluep;
-#endif
 {
-  if (yytype < YYNTOKENS)
-    YYFPRINTF (yyoutput, "token %s (", yytname[yytype]);
-  else
-    YYFPRINTF (yyoutput, "nterm %s (", yytname[yytype]);
+  YYFPRINTF (yyoutput, "%s %s (",
+             yytype < YYNTOKENS ? "token" : "nterm", yytname[yytype]);
 
   yy_symbol_value_print (yyoutput, yytype, yyvaluep);
   YYFPRINTF (yyoutput, ")");
@@ -1067,16 +959,8 @@ yy_symbol_print (yyoutput, yytype, yyvaluep)
 | TOP (included).                                                   |
 `------------------------------------------------------------------*/
 
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static void
 yy_stack_print (yytype_int16 *yybottom, yytype_int16 *yytop)
-#else
-static void
-yy_stack_print (yybottom, yytop)
-    yytype_int16 *yybottom;
-    yytype_int16 *yytop;
-#endif
 {
   YYFPRINTF (stderr, "Stack now");
   for (; yybottom <= yytop; yybottom++)
@@ -1087,49 +971,42 @@ yy_stack_print (yybottom, yytop)
   YYFPRINTF (stderr, "\n");
 }
 
-# define YY_STACK_PRINT(Bottom, Top)				\
-do {								\
-  if (yydebug)							\
-    yy_stack_print ((Bottom), (Top));				\
-} while (YYID (0))
+# define YY_STACK_PRINT(Bottom, Top)                            \
+do {                                                            \
+  if (yydebug)                                                  \
+    yy_stack_print ((Bottom), (Top));                           \
+} while (0)
 
 
 /*------------------------------------------------.
 | Report that the YYRULE is going to be reduced.  |
 `------------------------------------------------*/
 
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-static void
-yy_reduce_print (YYSTYPE *yyvsp, int yyrule)
-#else
 static void
-yy_reduce_print (yyvsp, yyrule)
-    YYSTYPE *yyvsp;
-    int yyrule;
-#endif
+yy_reduce_print (yytype_int16 *yyssp, YYSTYPE *yyvsp, int yyrule)
 {
+  unsigned long int yylno = yyrline[yyrule];
   int yynrhs = yyr2[yyrule];
   int yyi;
-  unsigned long int yylno = yyrline[yyrule];
   YYFPRINTF (stderr, "Reducing stack by rule %d (line %lu):\n",
-	     yyrule - 1, yylno);
+             yyrule - 1, yylno);
   /* The symbols being reduced.  */
   for (yyi = 0; yyi < yynrhs; yyi++)
     {
       YYFPRINTF (stderr, "   $%d = ", yyi + 1);
-      yy_symbol_print (stderr, yyrhs[yyprhs[yyrule] + yyi],
-		       &(yyvsp[(yyi + 1) - (yynrhs)])
-		       		       );
+      yy_symbol_print (stderr,
+                       yystos[yyssp[yyi + 1 - yynrhs]],
+                       &(yyvsp[(yyi + 1) - (yynrhs)])
+                                              );
       YYFPRINTF (stderr, "\n");
     }
 }
 
-# define YY_REDUCE_PRINT(Rule)		\
-do {					\
-  if (yydebug)				\
-    yy_reduce_print (yyvsp, Rule); \
-} while (YYID (0))
+# define YY_REDUCE_PRINT(Rule)          \
+do {                                    \
+  if (yydebug)                          \
+    yy_reduce_print (yyssp, yyvsp, Rule); \
+} while (0)
 
 /* Nonzero means print parse trace.  It is left uninitialized so that
    multiple parsers can coexist.  */
@@ -1143,7 +1020,7 @@ int yydebug;
 
 
 /* YYINITDEPTH -- initial size of the parser's stacks.  */
-#ifndef	YYINITDEPTH
+#ifndef YYINITDEPTH
 # define YYINITDEPTH 200
 #endif
 
@@ -1166,15 +1043,8 @@ int yydebug;
 #   define yystrlen strlen
 #  else
 /* Return the length of YYSTR.  */
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static YYSIZE_T
 yystrlen (const char *yystr)
-#else
-static YYSIZE_T
-yystrlen (yystr)
-    const char *yystr;
-#endif
 {
   YYSIZE_T yylen;
   for (yylen = 0; yystr[yylen]; yylen++)
@@ -1190,16 +1060,8 @@ yystrlen (yystr)
 #  else
 /* Copy YYSRC to YYDEST, returning the address of the terminating '\0' in
    YYDEST.  */
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static char *
 yystpcpy (char *yydest, const char *yysrc)
-#else
-static char *
-yystpcpy (yydest, yysrc)
-    char *yydest;
-    const char *yysrc;
-#endif
 {
   char *yyd = yydest;
   const char *yys = yysrc;
@@ -1229,27 +1091,27 @@ yytnamerr (char *yyres, const char *yystr)
       char const *yyp = yystr;
 
       for (;;)
-	switch (*++yyp)
-	  {
-	  case '\'':
-	  case ',':
-	    goto do_not_strip_quotes;
-
-	  case '\\':
-	    if (*++yyp != '\\')
-	      goto do_not_strip_quotes;
-	    /* Fall through.  */
-	  default:
-	    if (yyres)
-	      yyres[yyn] = *yyp;
-	    yyn++;
-	    break;
-
-	  case '"':
-	    if (yyres)
-	      yyres[yyn] = '\0';
-	    return yyn;
-	  }
+        switch (*++yyp)
+          {
+          case '\'':
+          case ',':
+            goto do_not_strip_quotes;
+
+          case '\\':
+            if (*++yyp != '\\')
+              goto do_not_strip_quotes;
+            /* Fall through.  */
+          default:
+            if (yyres)
+              yyres[yyn] = *yyp;
+            yyn++;
+            break;
+
+          case '"':
+            if (yyres)
+              yyres[yyn] = '\0';
+            return yyn;
+          }
     do_not_strip_quotes: ;
     }
 
@@ -1272,11 +1134,11 @@ static int
 yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
                 yytype_int16 *yyssp, int yytoken)
 {
-  YYSIZE_T yysize0 = yytnamerr (YY_NULL, yytname[yytoken]);
+  YYSIZE_T yysize0 = yytnamerr (YY_NULLPTR, yytname[yytoken]);
   YYSIZE_T yysize = yysize0;
   enum { YYERROR_VERBOSE_ARGS_MAXIMUM = 5 };
   /* Internationalized format string. */
-  const char *yyformat = YY_NULL;
+  const char *yyformat = YY_NULLPTR;
   /* Arguments of yyformat. */
   char const *yyarg[YYERROR_VERBOSE_ARGS_MAXIMUM];
   /* Number of reported tokens (one for the "unexpected", one per
@@ -1284,10 +1146,6 @@ yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
   int yycount = 0;
 
   /* There are many possibilities here to consider:
-     - Assume YYFAIL is not used.  It's too flawed to consider.  See
-       <http://lists.gnu.org/archive/html/bison-patches/2009-12/msg00024.html>
-       for details.  YYERROR is fine as it does not invoke this
-       function.
      - If this state is a consistent state with a default action, then
        the only way this function was invoked is if the default action
        is an error action.  In that case, don't check for expected
@@ -1337,7 +1195,7 @@ yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
                   }
                 yyarg[yycount++] = yytname[yyx];
                 {
-                  YYSIZE_T yysize1 = yysize + yytnamerr (YY_NULL, yytname[yyx]);
+                  YYSIZE_T yysize1 = yysize + yytnamerr (YY_NULLPTR, yytname[yyx]);
                   if (! (yysize <= yysize1
                          && yysize1 <= YYSTACK_ALLOC_MAXIMUM))
                     return 2;
@@ -1404,26 +1262,17 @@ yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
 | Release the memory associated to this symbol.  |
 `-----------------------------------------------*/
 
-/*ARGSUSED*/
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 static void
 yydestruct (const char *yymsg, int yytype, YYSTYPE *yyvaluep)
-#else
-static void
-yydestruct (yymsg, yytype, yyvaluep)
-    const char *yymsg;
-    int yytype;
-    YYSTYPE *yyvaluep;
-#endif
 {
   YYUSE (yyvaluep);
-
   if (!yymsg)
     yymsg = "Deleting";
   YY_SYMBOL_PRINT (yymsg, yytype, yyvaluep, yylocationp);
 
+  YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
   YYUSE (yytype);
+  YY_IGNORE_MAYBE_UNINITIALIZED_END
 }
 
 
@@ -1432,18 +1281,8 @@ yydestruct (yymsg, yytype, yyvaluep)
 /* The lookahead symbol.  */
 int yychar;
 
-
-#ifndef YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
-# define YY_IGNORE_MAYBE_UNINITIALIZED_BEGIN
-# define YY_IGNORE_MAYBE_UNINITIALIZED_END
-#endif
-#ifndef YY_INITIAL_VALUE
-# define YY_INITIAL_VALUE(Value) /* Nothing. */
-#endif
-
 /* The semantic value of the lookahead symbol.  */
-YYSTYPE yylval YY_INITIAL_VALUE(yyval_default);
-
+YYSTYPE yylval;
 /* Number of syntax errors so far.  */
 int yynerrs;
 
@@ -1452,35 +1291,16 @@ int yynerrs;
 | yyparse.  |
 `----------*/
 
-#ifdef YYPARSE_PARAM
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
-int
-yyparse (void *YYPARSE_PARAM)
-#else
-int
-yyparse (YYPARSE_PARAM)
-    void *YYPARSE_PARAM;
-#endif
-#else /* ! YYPARSE_PARAM */
-#if (defined __STDC__ || defined __C99__FUNC__ \
-     || defined __cplusplus || defined _MSC_VER)
 int
 yyparse (void)
-#else
-int
-yyparse ()
-
-#endif
-#endif
 {
     int yystate;
     /* Number of tokens to shift before error messages enabled.  */
     int yyerrstatus;
 
     /* The stacks and their tools:
-       `yyss': related to states.
-       `yyvs': related to semantic values.
+       'yyss': related to states.
+       'yyvs': related to semantic values.
 
        Refer to the stacks through separate pointers, to allow yyoverflow
        to reallocate them elsewhere.  */
@@ -1548,23 +1368,23 @@ yyparse ()
 
 #ifdef yyoverflow
       {
-	/* Give user a chance to reallocate the stack.  Use copies of
-	   these so that the &'s don't force the real ones into
-	   memory.  */
-	YYSTYPE *yyvs1 = yyvs;
-	yytype_int16 *yyss1 = yyss;
-
-	/* Each stack pointer address is followed by the size of the
-	   data in use in that stack, in bytes.  This used to be a
-	   conditional around just the two extra args, but that might
-	   be undefined if yyoverflow is a macro.  */
-	yyoverflow (YY_("memory exhausted"),
-		    &yyss1, yysize * sizeof (*yyssp),
-		    &yyvs1, yysize * sizeof (*yyvsp),
-		    &yystacksize);
-
-	yyss = yyss1;
-	yyvs = yyvs1;
+        /* Give user a chance to reallocate the stack.  Use copies of
+           these so that the &'s don't force the real ones into
+           memory.  */
+        YYSTYPE *yyvs1 = yyvs;
+        yytype_int16 *yyss1 = yyss;
+
+        /* Each stack pointer address is followed by the size of the
+           data in use in that stack, in bytes.  This used to be a
+           conditional around just the two extra args, but that might
+           be undefined if yyoverflow is a macro.  */
+        yyoverflow (YY_("memory exhausted"),
+                    &yyss1, yysize * sizeof (*yyssp),
+                    &yyvs1, yysize * sizeof (*yyvsp),
+                    &yystacksize);
+
+        yyss = yyss1;
+        yyvs = yyvs1;
       }
 #else /* no yyoverflow */
 # ifndef YYSTACK_RELOCATE
@@ -1572,22 +1392,22 @@ yyparse ()
 # else
       /* Extend the stack our own way.  */
       if (YYMAXDEPTH <= yystacksize)
-	goto yyexhaustedlab;
+        goto yyexhaustedlab;
       yystacksize *= 2;
       if (YYMAXDEPTH < yystacksize)
-	yystacksize = YYMAXDEPTH;
+        yystacksize = YYMAXDEPTH;
 
       {
-	yytype_int16 *yyss1 = yyss;
-	union yyalloc *yyptr =
-	  (union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize));
-	if (! yyptr)
-	  goto yyexhaustedlab;
-	YYSTACK_RELOCATE (yyss_alloc, yyss);
-	YYSTACK_RELOCATE (yyvs_alloc, yyvs);
+        yytype_int16 *yyss1 = yyss;
+        union yyalloc *yyptr =
+          (union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize));
+        if (! yyptr)
+          goto yyexhaustedlab;
+        YYSTACK_RELOCATE (yyss_alloc, yyss);
+        YYSTACK_RELOCATE (yyvs_alloc, yyvs);
 #  undef YYSTACK_RELOCATE
-	if (yyss1 != yyssa)
-	  YYSTACK_FREE (yyss1);
+        if (yyss1 != yyssa)
+          YYSTACK_FREE (yyss1);
       }
 # endif
 #endif /* no yyoverflow */
@@ -1596,10 +1416,10 @@ yyparse ()
       yyvsp = yyvs + yysize - 1;
 
       YYDPRINTF ((stderr, "Stack size increased to %lu\n",
-		  (unsigned long int) yystacksize));
+                  (unsigned long int) yystacksize));
 
       if (yyss + yystacksize - 1 <= yyssp)
-	YYABORT;
+        YYABORT;
     }
 
   YYDPRINTF ((stderr, "Entering state %d\n", yystate));
@@ -1628,7 +1448,7 @@ yybackup:
   if (yychar == YYEMPTY)
     {
       YYDPRINTF ((stderr, "Reading a token: "));
-      yychar = YYLEX;
+      yychar = yylex ();
     }
 
   if (yychar <= YYEOF)
@@ -1693,7 +1513,7 @@ yyreduce:
   yylen = yyr2[yyn];
 
   /* If YYLEN is nonzero, implement the default value of the action:
-     `$$ = $1'.
+     '$$ = $1'.
 
      Otherwise, the following line sets YYVAL to garbage.
      This behavior is undocumented and Bison
@@ -1707,8 +1527,7 @@ yyreduce:
   switch (yyn)
     {
         case 3:
-/* Line 1787 of yacc.c  */
-#line 109 "command.y"
+#line 109 "command.y" /* yacc.c:1646  */
     {
 		cmd_idx = -1;
 		want_nodeval = false;
@@ -1723,11 +1542,11 @@ yyreduce:
 			arg_list = NULL;
 		}
 	  }
+#line 1546 "command.c" /* yacc.c:1646  */
     break;
 
   case 5:
-/* Line 1787 of yacc.c  */
-#line 128 "command.y"
+#line 128 "command.y" /* yacc.c:1646  */
     {
 		if (errcount == 0 && cmd_idx >= 0) {
 			Func_cmd cmdfunc;
@@ -1777,25 +1596,25 @@ yyreduce:
 				YYACCEPT;
 		}
 	  }
+#line 1600 "command.c" /* yacc.c:1646  */
     break;
 
   case 6:
-/* Line 1787 of yacc.c  */
-#line 178 "command.y"
+#line 178 "command.y" /* yacc.c:1646  */
     {
 		yyerrok;
 	  }
+#line 1608 "command.c" /* yacc.c:1646  */
     break;
 
   case 22:
-/* Line 1787 of yacc.c  */
-#line 212 "command.y"
+#line 212 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1614 "command.c" /* yacc.c:1646  */
     break;
 
   case 23:
-/* Line 1787 of yacc.c  */
-#line 217 "command.y"
+#line 217 "command.y" /* yacc.c:1646  */
     {
 		if (errcount == 0) {
 			/* don't free arg_list;	passed on to statement_list
@@ -1811,11 +1630,11 @@ yyreduce:
 			in_eval = true;
 		}
 	  }
+#line 1634 "command.c" /* yacc.c:1646  */
     break;
 
   case 24:
-/* Line 1787 of yacc.c  */
-#line 236 "command.y"
+#line 236 "command.y" /* yacc.c:1646  */
     {
 		(yyval) = append_statement(arg_list, (char *) start_EVAL);
 		if (read_a_line == read_commands_string)	/* unserializing 'eval' in 'commands' */
@@ -1823,27 +1642,27 @@ yyreduce:
 		free_cmdarg(arg_list);
 		arg_list = NULL;
 	  }
+#line 1646 "command.c" /* yacc.c:1646  */
     break;
 
   case 25:
-/* Line 1787 of yacc.c  */
-#line 243 "command.y"
-    { (yyval) = append_statement((yyvsp[(1) - (2)]), lexptr_begin); }
+#line 243 "command.y" /* yacc.c:1646  */
+    { (yyval) = append_statement((yyvsp[-1]), lexptr_begin); }
+#line 1652 "command.c" /* yacc.c:1646  */
     break;
 
   case 26:
-/* Line 1787 of yacc.c  */
-#line 244 "command.y"
+#line 244 "command.y" /* yacc.c:1646  */
     {
-		(yyval) = (yyvsp[(3) - (4)]);
+		(yyval) = (yyvsp[-1]);
 	  }
+#line 1660 "command.c" /* yacc.c:1646  */
     break;
 
   case 27:
-/* Line 1787 of yacc.c  */
-#line 251 "command.y"
+#line 251 "command.y" /* yacc.c:1646  */
     {
-		arg_list = append_statement((yyvsp[(2) - (3)]), (char *) end_EVAL);
+		arg_list = append_statement((yyvsp[-1]), (char *) end_EVAL);
 		if (read_a_line == read_commands_string) {	/* unserializing 'eval' in 'commands' */
 			char *str = arg_list->a_string;
 			size_t len = strlen(str);
@@ -1857,120 +1676,120 @@ yyreduce:
 		cmd_idx = find_command("eval", 4);
 		in_eval = false;
 	  }
+#line 1680 "command.c" /* yacc.c:1646  */
     break;
 
   case 28:
-/* Line 1787 of yacc.c  */
-#line 267 "command.y"
+#line 267 "command.y" /* yacc.c:1646  */
     {
 		NODE *n;
 		CMDARG *arg;
-		n = (yyvsp[(3) - (3)])->a_node;
+		n = (yyvsp[0])->a_node;
 		arg = append_statement(NULL, (char *) start_EVAL);
 		(void) append_statement(arg, n->stptr);
 		(void) append_statement(arg, (char *) end_EVAL);
 		free_cmdarg(arg_list);
 		arg_list = arg;
 	  }
+#line 1695 "command.c" /* yacc.c:1646  */
     break;
 
   case 34:
-/* Line 1787 of yacc.c  */
-#line 286 "command.y"
+#line 286 "command.y" /* yacc.c:1646  */
     {
 		if (cmdtab[cmd_idx].class == D_FRAME
-				&& (yyvsp[(2) - (2)]) != NULL && (yyvsp[(2) - (2)])->a_int < 0)
-			yyerror(_("invalid frame number: %d"), (yyvsp[(2) - (2)])->a_int);
+				&& (yyvsp[0]) != NULL && (yyvsp[0])->a_int < 0)
+			yyerror(_("invalid frame number: %d"), (yyvsp[0])->a_int);
 	  }
+#line 1705 "command.c" /* yacc.c:1646  */
     break;
 
   case 35:
-/* Line 1787 of yacc.c  */
-#line 292 "command.y"
+#line 292 "command.y" /* yacc.c:1646  */
     {
-		int idx = find_argument((yyvsp[(2) - (2)]));
+		int idx = find_argument((yyvsp[0]));
 		if (idx < 0)
-			yyerror(_("info: invalid option - \"%s\""), (yyvsp[(2) - (2)])->a_string);
+			yyerror(_("info: invalid option - \"%s\""), (yyvsp[0])->a_string);
 		else {
-			efree((yyvsp[(2) - (2)])->a_string);
-			(yyvsp[(2) - (2)])->a_string = NULL;
-			(yyvsp[(2) - (2)])->type = D_argument;
-			(yyvsp[(2) - (2)])->a_argument = argtab[idx].value;
+			efree((yyvsp[0])->a_string);
+			(yyvsp[0])->a_string = NULL;
+			(yyvsp[0])->type = D_argument;
+			(yyvsp[0])->a_argument = argtab[idx].value;
 		}
 	  }
+#line 1721 "command.c" /* yacc.c:1646  */
     break;
 
   case 38:
-/* Line 1787 of yacc.c  */
-#line 305 "command.y"
+#line 305 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1727 "command.c" /* yacc.c:1646  */
     break;
 
   case 40:
-/* Line 1787 of yacc.c  */
-#line 306 "command.y"
+#line 306 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1733 "command.c" /* yacc.c:1646  */
     break;
 
   case 46:
-/* Line 1787 of yacc.c  */
-#line 311 "command.y"
+#line 311 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1739 "command.c" /* yacc.c:1646  */
     break;
 
   case 49:
-/* Line 1787 of yacc.c  */
-#line 313 "command.y"
+#line 313 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1745 "command.c" /* yacc.c:1646  */
     break;
 
   case 51:
-/* Line 1787 of yacc.c  */
-#line 314 "command.y"
+#line 314 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1751 "command.c" /* yacc.c:1646  */
     break;
 
   case 53:
-/* Line 1787 of yacc.c  */
-#line 315 "command.y"
+#line 315 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1757 "command.c" /* yacc.c:1646  */
     break;
 
   case 57:
-/* Line 1787 of yacc.c  */
-#line 319 "command.y"
+#line 319 "command.y" /* yacc.c:1646  */
     {
-		if (in_cmd_src((yyvsp[(2) - (2)])->a_string))
-			yyerror(_("source \"%s\": already sourced."), (yyvsp[(2) - (2)])->a_string);
+		if (in_cmd_src((yyvsp[0])->a_string))
+			yyerror(_("source \"%s\": already sourced."), (yyvsp[0])->a_string);
 	  }
+#line 1766 "command.c" /* yacc.c:1646  */
     break;
 
   case 58:
-/* Line 1787 of yacc.c  */
-#line 324 "command.y"
+#line 324 "command.y" /* yacc.c:1646  */
     {
 		if (! input_from_tty)
-			yyerror(_("save \"%s\": command not permitted."), (yyvsp[(2) - (2)])->a_string);
+			yyerror(_("save \"%s\": command not permitted."), (yyvsp[0])->a_string);
 	  }
+#line 1775 "command.c" /* yacc.c:1646  */
     break;
 
   case 59:
-/* Line 1787 of yacc.c  */
-#line 329 "command.y"
+#line 329 "command.y" /* yacc.c:1646  */
     {
 		int type = 0;
 		int num;
 
-		if ((yyvsp[(2) - (2)]) != NULL)
-			num = (yyvsp[(2) - (2)])->a_int;
+		if ((yyvsp[0]) != NULL)
+			num = (yyvsp[0])->a_int;
 
 		if (errcount != 0)
 			;
 		else if (in_commands)
 			yyerror(_("Can't use command `commands' for breakpoint/watchpoint commands"));
-		else if ((yyvsp[(2) - (2)]) == NULL &&  ! (type = has_break_or_watch_point(&num, true)))
+		else if ((yyvsp[0]) == NULL &&  ! (type = has_break_or_watch_point(&num, true)))
 			yyerror(_("no breakpoint/watchpoint has been set yet"));
-		else if ((yyvsp[(2) - (2)]) != NULL && ! (type = has_break_or_watch_point(&num, false)))
+		else if ((yyvsp[0]) != NULL && ! (type = has_break_or_watch_point(&num, false)))
 			yyerror(_("invalid breakpoint/watchpoint number"));
 		if (type) {
 			in_commands = true;
@@ -1982,11 +1801,11 @@ yyreduce:
 			}
 		}
 	  }
+#line 1805 "command.c" /* yacc.c:1646  */
     break;
 
   case 60:
-/* Line 1787 of yacc.c  */
-#line 355 "command.y"
+#line 355 "command.y" /* yacc.c:1646  */
     {
 		if (! in_commands)
 			yyerror(_("`end' valid only in command `commands' or `eval'"));
@@ -1996,54 +1815,54 @@ yyreduce:
 			in_commands = false;
 		}
 	  }
+#line 1819 "command.c" /* yacc.c:1646  */
     break;
 
   case 61:
-/* Line 1787 of yacc.c  */
-#line 365 "command.y"
+#line 365 "command.y" /* yacc.c:1646  */
     {
 		if (! in_commands)
 			yyerror(_("`silent' valid only in command `commands'"));
 	  }
+#line 1828 "command.c" /* yacc.c:1646  */
     break;
 
   case 62:
-/* Line 1787 of yacc.c  */
-#line 370 "command.y"
+#line 370 "command.y" /* yacc.c:1646  */
     {
-		int idx = find_argument((yyvsp[(2) - (2)]));
+		int idx = find_argument((yyvsp[0]));
 		if (idx < 0)
-			yyerror(_("trace: invalid option - \"%s\""), (yyvsp[(2) - (2)])->a_string);
+			yyerror(_("trace: invalid option - \"%s\""), (yyvsp[0])->a_string);
 		else {
-			efree((yyvsp[(2) - (2)])->a_string);
-			(yyvsp[(2) - (2)])->a_string = NULL;
-			(yyvsp[(2) - (2)])->type = D_argument;
-			(yyvsp[(2) - (2)])->a_argument = argtab[idx].value;
+			efree((yyvsp[0])->a_string);
+			(yyvsp[0])->a_string = NULL;
+			(yyvsp[0])->type = D_argument;
+			(yyvsp[0])->a_argument = argtab[idx].value;
 		}
 	  }
+#line 1844 "command.c" /* yacc.c:1646  */
     break;
 
   case 63:
-/* Line 1787 of yacc.c  */
-#line 381 "command.y"
+#line 381 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1850 "command.c" /* yacc.c:1646  */
     break;
 
   case 64:
-/* Line 1787 of yacc.c  */
-#line 382 "command.y"
+#line 382 "command.y" /* yacc.c:1646  */
     {
 		int type;
-		int num = (yyvsp[(2) - (4)])->a_int;
+		int num = (yyvsp[-2])->a_int;
 		type = has_break_or_watch_point(&num, false);
 		if (! type)
 			yyerror(_("condition: invalid breakpoint/watchpoint number"));
 	  }
+#line 1862 "command.c" /* yacc.c:1646  */
     break;
 
   case 65:
-/* Line 1787 of yacc.c  */
-#line 390 "command.y"
+#line 390 "command.y" /* yacc.c:1646  */
     {
 		if (in_commands) {
 			/* Prepend command 'eval' to argument list */
@@ -2054,387 +1873,387 @@ yyreduce:
 			arg_list = arg;
 		}
 	  }
+#line 1877 "command.c" /* yacc.c:1646  */
     break;
 
   case 66:
-/* Line 1787 of yacc.c  */
-#line 404 "command.y"
+#line 404 "command.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(1) - (1)]) != NULL) {
-			NODE *n = (yyvsp[(1) - (1)])->a_node;
-			(yyvsp[(1) - (1)])->type = D_string;
-			(yyvsp[(1) - (1)])->a_string = n->stptr;
+		if ((yyvsp[0]) != NULL) {
+			NODE *n = (yyvsp[0])->a_node;
+			(yyvsp[0])->type = D_string;
+			(yyvsp[0])->a_string = n->stptr;
 			freenode(n);
 		}
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyval) = (yyvsp[0]);
 	  }
+#line 1891 "command.c" /* yacc.c:1646  */
     break;
 
   case 68:
-/* Line 1787 of yacc.c  */
-#line 418 "command.y"
+#line 418 "command.y" /* yacc.c:1646  */
     {	(yyval) = NULL; }
+#line 1897 "command.c" /* yacc.c:1646  */
     break;
 
   case 69:
-/* Line 1787 of yacc.c  */
-#line 423 "command.y"
+#line 423 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1903 "command.c" /* yacc.c:1646  */
     break;
 
   case 74:
-/* Line 1787 of yacc.c  */
-#line 432 "command.y"
+#line 432 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1909 "command.c" /* yacc.c:1646  */
     break;
 
   case 75:
-/* Line 1787 of yacc.c  */
-#line 437 "command.y"
+#line 437 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1915 "command.c" /* yacc.c:1646  */
     break;
 
   case 77:
-/* Line 1787 of yacc.c  */
-#line 440 "command.y"
+#line 440 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1921 "command.c" /* yacc.c:1646  */
     break;
 
   case 78:
-/* Line 1787 of yacc.c  */
-#line 445 "command.y"
+#line 445 "command.y" /* yacc.c:1646  */
     {
 		NODE *n;
-		n = (yyvsp[(1) - (1)])->a_node;
+		n = (yyvsp[0])->a_node;
 		if ((n->flags & STRING) == 0)
 			yyerror(_("argument not a string"));
 	  }
+#line 1932 "command.c" /* yacc.c:1646  */
     break;
 
   case 79:
-/* Line 1787 of yacc.c  */
-#line 455 "command.y"
+#line 455 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1938 "command.c" /* yacc.c:1646  */
     break;
 
   case 80:
-/* Line 1787 of yacc.c  */
-#line 457 "command.y"
+#line 457 "command.y" /* yacc.c:1646  */
     {
-		if (find_option((yyvsp[(1) - (1)])->a_string) < 0)
-			yyerror(_("option: invalid parameter - \"%s\""), (yyvsp[(1) - (1)])->a_string);
+		if (find_option((yyvsp[0])->a_string) < 0)
+			yyerror(_("option: invalid parameter - \"%s\""), (yyvsp[0])->a_string);
  	  }
+#line 1947 "command.c" /* yacc.c:1646  */
     break;
 
   case 81:
-/* Line 1787 of yacc.c  */
-#line 462 "command.y"
+#line 462 "command.y" /* yacc.c:1646  */
     {
-		if (find_option((yyvsp[(1) - (3)])->a_string) < 0)
-			yyerror(_("option: invalid parameter - \"%s\""), (yyvsp[(1) - (3)])->a_string);
+		if (find_option((yyvsp[-2])->a_string) < 0)
+			yyerror(_("option: invalid parameter - \"%s\""), (yyvsp[-2])->a_string);
  	  }
+#line 1956 "command.c" /* yacc.c:1646  */
     break;
 
   case 82:
-/* Line 1787 of yacc.c  */
-#line 470 "command.y"
+#line 470 "command.y" /* yacc.c:1646  */
     {
 		NODE *n;
-		n = lookup((yyvsp[(1) - (1)])->a_string);
+		n = lookup((yyvsp[0])->a_string);
 		if (n == NULL || n->type != Node_func)
-			yyerror(_("no such function - \"%s\""), (yyvsp[(1) - (1)])->a_string);
+			yyerror(_("no such function - \"%s\""), (yyvsp[0])->a_string);
 		else {
-			(yyvsp[(1) - (1)])->type = D_func;
-			efree((yyvsp[(1) - (1)])->a_string);
-			(yyvsp[(1) - (1)])->a_string = NULL;
-			(yyvsp[(1) - (1)])->a_node = n;
+			(yyvsp[0])->type = D_func;
+			efree((yyvsp[0])->a_string);
+			(yyvsp[0])->a_string = NULL;
+			(yyvsp[0])->a_node = n;
 		}
 	  }
+#line 1973 "command.c" /* yacc.c:1646  */
     break;
 
   case 83:
-/* Line 1787 of yacc.c  */
-#line 486 "command.y"
+#line 486 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1979 "command.c" /* yacc.c:1646  */
     break;
 
   case 88:
-/* Line 1787 of yacc.c  */
-#line 495 "command.y"
+#line 495 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 1985 "command.c" /* yacc.c:1646  */
     break;
 
   case 89:
-/* Line 1787 of yacc.c  */
-#line 496 "command.y"
+#line 496 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1991 "command.c" /* yacc.c:1646  */
     break;
 
   case 92:
-/* Line 1787 of yacc.c  */
-#line 498 "command.y"
+#line 498 "command.y" /* yacc.c:1646  */
     { want_nodeval = true; }
+#line 1997 "command.c" /* yacc.c:1646  */
     break;
 
   case 95:
-/* Line 1787 of yacc.c  */
-#line 504 "command.y"
+#line 504 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2003 "command.c" /* yacc.c:1646  */
     break;
 
   case 97:
-/* Line 1787 of yacc.c  */
-#line 510 "command.y"
+#line 510 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2009 "command.c" /* yacc.c:1646  */
     break;
 
   case 99:
-/* Line 1787 of yacc.c  */
-#line 516 "command.y"
+#line 516 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2015 "command.c" /* yacc.c:1646  */
     break;
 
   case 104:
-/* Line 1787 of yacc.c  */
-#line 528 "command.y"
+#line 528 "command.y" /* yacc.c:1646  */
     {
-		int idx = find_argument((yyvsp[(1) - (2)]));
+		int idx = find_argument((yyvsp[-1]));
 		if (idx < 0)
-			yyerror(_("enable: invalid option - \"%s\""), (yyvsp[(1) - (2)])->a_string);
+			yyerror(_("enable: invalid option - \"%s\""), (yyvsp[-1])->a_string);
 		else {
-			efree((yyvsp[(1) - (2)])->a_string);
-			(yyvsp[(1) - (2)])->a_string = NULL;
-			(yyvsp[(1) - (2)])->type = D_argument;
-			(yyvsp[(1) - (2)])->a_argument = argtab[idx].value;
+			efree((yyvsp[-1])->a_string);
+			(yyvsp[-1])->a_string = NULL;
+			(yyvsp[-1])->type = D_argument;
+			(yyvsp[-1])->a_argument = argtab[idx].value;
 		}
 	  }
+#line 2031 "command.c" /* yacc.c:1646  */
     break;
 
   case 106:
-/* Line 1787 of yacc.c  */
-#line 544 "command.y"
+#line 544 "command.y" /* yacc.c:1646  */
     {
-		(yyvsp[(2) - (2)])->type = D_array;	/* dump all items */
-		(yyvsp[(2) - (2)])->a_count = 0;
+		(yyvsp[0])->type = D_array;	/* dump all items */
+		(yyvsp[0])->a_count = 0;
 	  }
+#line 2040 "command.c" /* yacc.c:1646  */
     break;
 
   case 107:
-/* Line 1787 of yacc.c  */
-#line 549 "command.y"
+#line 549 "command.y" /* yacc.c:1646  */
     {
-		(yyvsp[(2) - (3)])->type = D_array;
-		(yyvsp[(2) - (3)])->a_count = num_dim;
+		(yyvsp[-1])->type = D_array;
+		(yyvsp[-1])->a_count = num_dim;
 	  }
+#line 2049 "command.c" /* yacc.c:1646  */
     break;
 
   case 117:
-/* Line 1787 of yacc.c  */
-#line 575 "command.y"
+#line 575 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2055 "command.c" /* yacc.c:1646  */
     break;
 
   case 118:
-/* Line 1787 of yacc.c  */
-#line 577 "command.y"
+#line 577 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2061 "command.c" /* yacc.c:1646  */
     break;
 
   case 119:
-/* Line 1787 of yacc.c  */
-#line 579 "command.y"
+#line 579 "command.y" /* yacc.c:1646  */
     {
 		CMDARG *a;
 		a = mk_cmdarg(D_int);
 		a->a_int = -1;
 		append_cmdarg(a);
 	  }
+#line 2072 "command.c" /* yacc.c:1646  */
     break;
 
   case 126:
-/* Line 1787 of yacc.c  */
-#line 595 "command.y"
+#line 595 "command.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(1) - (3)])->a_int > (yyvsp[(3) - (3)])->a_int)
+		if ((yyvsp[-2])->a_int > (yyvsp[0])->a_int)
 			yyerror(_("invalid range specification: %d - %d"),
-				(yyvsp[(1) - (3)])->a_int, (yyvsp[(3) - (3)])->a_int);
+				(yyvsp[-2])->a_int, (yyvsp[0])->a_int);
 		else
-			(yyvsp[(1) - (3)])->type = D_range;
-		(yyval) = (yyvsp[(1) - (3)]);
+			(yyvsp[-2])->type = D_range;
+		(yyval) = (yyvsp[-2]);
 	  }
+#line 2085 "command.c" /* yacc.c:1646  */
     break;
 
   case 127:
-/* Line 1787 of yacc.c  */
-#line 607 "command.y"
+#line 607 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2091 "command.c" /* yacc.c:1646  */
     break;
 
   case 134:
-/* Line 1787 of yacc.c  */
-#line 621 "command.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 621 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2097 "command.c" /* yacc.c:1646  */
     break;
 
   case 135:
-/* Line 1787 of yacc.c  */
-#line 623 "command.y"
-    { (yyval) = (yyvsp[(1) - (3)]); }
+#line 623 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[-2]); }
+#line 2103 "command.c" /* yacc.c:1646  */
     break;
 
   case 137:
-/* Line 1787 of yacc.c  */
-#line 629 "command.y"
+#line 629 "command.y" /* yacc.c:1646  */
     {
 		CMDARG *a;
 		NODE *subs;
 		int count = 0;
 		
-		for (a = (yyvsp[(2) - (3)]); a != NULL; a = a->next)
+		for (a = (yyvsp[-1]); a != NULL; a = a->next)
 			count++;
-		subs = concat_args((yyvsp[(2) - (3)]), count);
-		free_cmdarg((yyvsp[(2) - (3)])->next);
-		(yyvsp[(2) - (3)])->next = NULL;
-		(yyvsp[(2) - (3)])->type = D_node;
-		(yyvsp[(2) - (3)])->a_node = subs;
-		(yyval) = (yyvsp[(2) - (3)]);
+		subs = concat_args((yyvsp[-1]), count);
+		free_cmdarg((yyvsp[-1])->next);
+		(yyvsp[-1])->next = NULL;
+		(yyvsp[-1])->type = D_node;
+		(yyvsp[-1])->a_node = subs;
+		(yyval) = (yyvsp[-1]);
 	  }
+#line 2122 "command.c" /* yacc.c:1646  */
     break;
 
   case 139:
-/* Line 1787 of yacc.c  */
-#line 648 "command.y"
-    { (yyval) = (yyvsp[(1) - (1)]); num_dim = 1; }
+#line 648 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); num_dim = 1; }
+#line 2128 "command.c" /* yacc.c:1646  */
     break;
 
   case 140:
-/* Line 1787 of yacc.c  */
-#line 650 "command.y"
-    {	(yyval) = (yyvsp[(1) - (2)]); num_dim++; }
+#line 650 "command.y" /* yacc.c:1646  */
+    {	(yyval) = (yyvsp[-1]); num_dim++; }
+#line 2134 "command.c" /* yacc.c:1646  */
     break;
 
   case 142:
-/* Line 1787 of yacc.c  */
-#line 656 "command.y"
+#line 656 "command.y" /* yacc.c:1646  */
     {
-		NODE *n = (yyvsp[(2) - (2)])->a_node;
+		NODE *n = (yyvsp[0])->a_node;
 		if ((n->flags & NUMBER) == 0)
 			yyerror(_("non-numeric value for field number"));
 		else
-			(yyvsp[(2) - (2)])->type = D_field;
-		(yyval) = (yyvsp[(2) - (2)]);
+			(yyvsp[0])->type = D_field;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2147 "command.c" /* yacc.c:1646  */
     break;
 
   case 143:
-/* Line 1787 of yacc.c  */
-#line 665 "command.y"
+#line 665 "command.y" /* yacc.c:1646  */
     {
 		/* a_string is array name, a_count is dimension count */
-		(yyvsp[(1) - (2)])->type = D_subscript;
-		(yyvsp[(1) - (2)])->a_count = num_dim;
-		(yyval) = (yyvsp[(1) - (2)]);
+		(yyvsp[-1])->type = D_subscript;
+		(yyvsp[-1])->a_count = num_dim;
+		(yyval) = (yyvsp[-1]);
 	  }
+#line 2158 "command.c" /* yacc.c:1646  */
     break;
 
   case 144:
-/* Line 1787 of yacc.c  */
-#line 675 "command.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 675 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2164 "command.c" /* yacc.c:1646  */
     break;
 
   case 145:
-/* Line 1787 of yacc.c  */
-#line 677 "command.y"
+#line 677 "command.y" /* yacc.c:1646  */
     { 
-		NODE *n = (yyvsp[(2) - (2)])->a_node;
+		NODE *n = (yyvsp[0])->a_node;
 		if ((n->flags & NUMBER) == 0)
 			yyerror(_("non-numeric value found, numeric expected"));
-		(yyval) = (yyvsp[(2) - (2)]);
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2175 "command.c" /* yacc.c:1646  */
     break;
 
   case 146:
-/* Line 1787 of yacc.c  */
-#line 684 "command.y"
+#line 684 "command.y" /* yacc.c:1646  */
     { 
-		NODE *n = (yyvsp[(2) - (2)])->a_node;
+		NODE *n = (yyvsp[0])->a_node;
 		if ((n->flags & NUMBER) == 0)
 			yyerror(_("non-numeric value found, numeric expected"));
 		else
 			negate_num(n);
-		(yyval) = (yyvsp[(2) - (2)]);
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2188 "command.c" /* yacc.c:1646  */
     break;
 
   case 147:
-/* Line 1787 of yacc.c  */
-#line 696 "command.y"
+#line 696 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2194 "command.c" /* yacc.c:1646  */
     break;
 
   case 148:
-/* Line 1787 of yacc.c  */
-#line 698 "command.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 698 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2200 "command.c" /* yacc.c:1646  */
     break;
 
   case 149:
-/* Line 1787 of yacc.c  */
-#line 703 "command.y"
+#line 703 "command.y" /* yacc.c:1646  */
     { (yyval) = NULL; }
+#line 2206 "command.c" /* yacc.c:1646  */
     break;
 
   case 150:
-/* Line 1787 of yacc.c  */
-#line 705 "command.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 705 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2212 "command.c" /* yacc.c:1646  */
     break;
 
   case 151:
-/* Line 1787 of yacc.c  */
-#line 710 "command.y"
+#line 710 "command.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(1) - (1)])->a_int == 0)
+		if ((yyvsp[0])->a_int == 0)
 			yyerror(_("non-zero integer value"));
-		(yyval) = (yyvsp[(1) - (1)]);
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2222 "command.c" /* yacc.c:1646  */
     break;
 
   case 152:
-/* Line 1787 of yacc.c  */
-#line 716 "command.y"
+#line 716 "command.y" /* yacc.c:1646  */
     {
-		if ((yyvsp[(2) - (2)])->a_int == 0)
+		if ((yyvsp[0])->a_int == 0)
 			yyerror(_("non-zero integer value"));
-		(yyval) = (yyvsp[(2) - (2)]);
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2232 "command.c" /* yacc.c:1646  */
     break;
 
   case 153:
-/* Line 1787 of yacc.c  */
-#line 725 "command.y"
-    { (yyval) = (yyvsp[(1) - (1)]); }
+#line 725 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2238 "command.c" /* yacc.c:1646  */
     break;
 
   case 154:
-/* Line 1787 of yacc.c  */
-#line 727 "command.y"
-    { (yyval) = (yyvsp[(2) - (2)]); }
+#line 727 "command.y" /* yacc.c:1646  */
+    { (yyval) = (yyvsp[0]); }
+#line 2244 "command.c" /* yacc.c:1646  */
     break;
 
   case 155:
-/* Line 1787 of yacc.c  */
-#line 729 "command.y"
+#line 729 "command.y" /* yacc.c:1646  */
     {
-		(yyvsp[(2) - (2)])->a_int = - (yyvsp[(2) - (2)])->a_int;
-		(yyval) = (yyvsp[(2) - (2)]);
+		(yyvsp[0])->a_int = - (yyvsp[0])->a_int;
+		(yyval) = (yyvsp[0]);
 	  }
+#line 2253 "command.c" /* yacc.c:1646  */
     break;
 
   case 156:
-/* Line 1787 of yacc.c  */
-#line 737 "command.y"
+#line 737 "command.y" /* yacc.c:1646  */
     {
 		if (lexptr_begin != NULL) {
 			if (input_from_tty && lexptr_begin[0] != '\0')
@@ -2443,11 +2262,11 @@ yyreduce:
 			lexptr_begin = NULL;
 		}
 	  }
+#line 2266 "command.c" /* yacc.c:1646  */
     break;
 
 
-/* Line 1787 of yacc.c  */
-#line 2451 "command.c"
+#line 2270 "command.c" /* yacc.c:1646  */
       default: break;
     }
   /* User semantic actions sometimes alter yychar, and that requires
@@ -2469,7 +2288,7 @@ yyreduce:
 
   *++yyvsp = yyval;
 
-  /* Now `shift' the result of the reduction.  Determine what state
+  /* Now 'shift' the result of the reduction.  Determine what state
      that goes to, based on the state we popped back to and the rule
      number reduced by.  */
 
@@ -2484,9 +2303,9 @@ yyreduce:
   goto yynewstate;
 
 
-/*------------------------------------.
-| yyerrlab -- here on detecting error |
-`------------------------------------*/
+/*--------------------------------------.
+| yyerrlab -- here on detecting error.  |
+`--------------------------------------*/
 yyerrlab:
   /* Make sure we have latest lookahead translation.  See comments at
      user semantic actions for why this is necessary.  */
@@ -2537,20 +2356,20 @@ yyerrlab:
   if (yyerrstatus == 3)
     {
       /* If just tried and failed to reuse lookahead token after an
-	 error, discard it.  */
+         error, discard it.  */
 
       if (yychar <= YYEOF)
-	{
-	  /* Return failure if at end of input.  */
-	  if (yychar == YYEOF)
-	    YYABORT;
-	}
+        {
+          /* Return failure if at end of input.  */
+          if (yychar == YYEOF)
+            YYABORT;
+        }
       else
-	{
-	  yydestruct ("Error: discarding",
-		      yytoken, &yylval);
-	  yychar = YYEMPTY;
-	}
+        {
+          yydestruct ("Error: discarding",
+                      yytoken, &yylval);
+          yychar = YYEMPTY;
+        }
     }
 
   /* Else will try to reuse lookahead token after shifting the error
@@ -2569,7 +2388,7 @@ yyerrorlab:
   if (/*CONSTCOND*/ 0)
      goto yyerrorlab;
 
-  /* Do not reclaim the symbols of the rule which action triggered
+  /* Do not reclaim the symbols of the rule whose action triggered
      this YYERROR.  */
   YYPOPSTACK (yylen);
   yylen = 0;
@@ -2582,29 +2401,29 @@ yyerrorlab:
 | yyerrlab1 -- common code for both syntax error and YYERROR.  |
 `-------------------------------------------------------------*/
 yyerrlab1:
-  yyerrstatus = 3;	/* Each real token shifted decrements this.  */
+  yyerrstatus = 3;      /* Each real token shifted decrements this.  */
 
   for (;;)
     {
       yyn = yypact[yystate];
       if (!yypact_value_is_default (yyn))
-	{
-	  yyn += YYTERROR;
-	  if (0 <= yyn && yyn <= YYLAST && yycheck[yyn] == YYTERROR)
-	    {
-	      yyn = yytable[yyn];
-	      if (0 < yyn)
-		break;
-	    }
-	}
+        {
+          yyn += YYTERROR;
+          if (0 <= yyn && yyn <= YYLAST && yycheck[yyn] == YYTERROR)
+            {
+              yyn = yytable[yyn];
+              if (0 < yyn)
+                break;
+            }
+        }
 
       /* Pop the current state because it cannot handle the error token.  */
       if (yyssp == yyss)
-	YYABORT;
+        YYABORT;
 
 
       yydestruct ("Error: popping",
-		  yystos[yystate], yyvsp);
+                  yystos[yystate], yyvsp);
       YYPOPSTACK (1);
       yystate = *yyssp;
       YY_STACK_PRINT (yyss, yyssp);
@@ -2655,14 +2474,14 @@ yyreturn:
       yydestruct ("Cleanup: discarding lookahead",
                   yytoken, &yylval);
     }
-  /* Do not reclaim the symbols of the rule which action triggered
+  /* Do not reclaim the symbols of the rule whose action triggered
      this YYABORT or YYACCEPT.  */
   YYPOPSTACK (yylen);
   YY_STACK_PRINT (yyss, yyssp);
   while (yyssp != yyss)
     {
       yydestruct ("Cleanup: popping",
-		  yystos[*yyssp], yyvsp);
+                  yystos[*yyssp], yyvsp);
       YYPOPSTACK (1);
     }
 #ifndef yyoverflow
@@ -2673,13 +2492,9 @@ yyreturn:
   if (yymsg != yymsgbuf)
     YYSTACK_FREE (yymsg);
 #endif
-  /* Make sure YYID is used.  */
-  return YYID (yyresult);
+  return yyresult;
 }
-
-
-/* Line 2050 of yacc.c  */
-#line 747 "command.y"
+#line 747 "command.y" /* yacc.c:1906  */
 
 
 
@@ -2852,7 +2667,7 @@ struct argtoken argtab[] = {
 	{ "sources", D_info, A_SOURCES },
 	{ "variables", D_info, A_VARIABLES },
 	{ "watch", D_info, A_WATCH },
-	{ NULL, D_illegal, 0 },
+	{ NULL, D_illegal, A_NONE },
 };
 
 
@@ -3395,6 +3210,8 @@ do_help(CMDARG *arg, int cmd)
 }
 
 
+#ifdef HAVE_LIBREADLINE
+
 /* next_word --- find the next word in a line to complete 
  *               (word seperation characters are space and tab).
  */
@@ -3421,8 +3238,6 @@ next_word(char *p, int len, char **endp)
 	return p;
 }
 
-#ifdef HAVE_LIBREADLINE
-
 /* command_completion --- attempt to complete based on the word number in line;
  *    try to complete on command names if this is the first word; for the next
  *    word(s), the type of completion depends on the command name (first word).
diff --git a/command.y b/command.y
index f6c79812..576af159 100644
--- a/command.y
+++ b/command.y
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 2004, 2010, 2011 the Free Software Foundation, Inc.
+ * Copyright (C) 2004, 2010, 2011, 2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -51,10 +51,10 @@ static bool in_eval = false;
 static const char start_EVAL[] = "function @eval(){";
 static const char end_EVAL[] = "}";	
 static CMDARG *append_statement(CMDARG *stmt_list, char *stmt);
-static char *next_word(char *p, int len, char **endp);
 static NODE *concat_args(CMDARG *a, int count);
 
 #ifdef HAVE_LIBREADLINE
+static char *next_word(char *p, int len, char **endp);
 static void history_expand_line(char **line);
 static char *command_generator(const char *text, int state);
 static char *srcfile_generator(const char *text, int state);
@@ -916,7 +916,7 @@ struct argtoken argtab[] = {
 	{ "sources", D_info, A_SOURCES },
 	{ "variables", D_info, A_VARIABLES },
 	{ "watch", D_info, A_WATCH },
-	{ NULL, D_illegal, 0 },
+	{ NULL, D_illegal, A_NONE },
 };
 
 
@@ -1459,6 +1459,8 @@ do_help(CMDARG *arg, int cmd)
 }
 
 
+#ifdef HAVE_LIBREADLINE
+
 /* next_word --- find the next word in a line to complete 
  *               (word seperation characters are space and tab).
  */
@@ -1485,8 +1487,6 @@ next_word(char *p, int len, char **endp)
 	return p;
 }
 
-#ifdef HAVE_LIBREADLINE
-
 /* command_completion --- attempt to complete based on the word number in line;
  *    try to complete on command names if this is the first word; for the next
  *    word(s), the type of completion depends on the command name (first word).
diff --git a/config.guess b/config.guess
index 9afd6762..4438cd70 100755
--- a/config.guess
+++ b/config.guess
@@ -1,8 +1,8 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
-#   Copyright 1992-2013 Free Software Foundation, Inc.
+#   Copyright 1992-2014 Free Software Foundation, Inc.
 
-timestamp='2013-11-29'
+timestamp='2014-01-01'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
@@ -50,7 +50,7 @@ version="\
 GNU config.guess ($timestamp)
 
 Originally written by Per Bothner.
-Copyright 1992-2013 Free Software Foundation, Inc.
+Copyright 1992-2014 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
diff --git a/config.rpath b/config.rpath
index 17298f23..ab6fd995 100755
--- a/config.rpath
+++ b/config.rpath
@@ -2,7 +2,7 @@
 # Output a system dependent set of variables, describing how to set the
 # run time search path of shared libraries in an executable.
 #
-#   Copyright 1996-2010 Free Software Foundation, Inc.
+#   Copyright 1996-2014 Free Software Foundation, Inc.
 #   Taken from GNU libtool, 2001
 #   Originally by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
 #
@@ -25,7 +25,7 @@
 #   known workaround is to choose shorter directory names for the build
 #   directory and/or the installation directory.
 
-# All known linkers require a `.a' archive for static linking (except MSVC,
+# All known linkers require a '.a' archive for static linking (except MSVC,
 # which needs '.lib').
 libext=a
 shrext=.so
@@ -57,13 +57,6 @@ else
     aix*)
       wl='-Wl,'
       ;;
-    darwin*)
-      case $cc_basename in
-        xlc*)
-          wl='-Wl,'
-          ;;
-      esac
-      ;;
     mingw* | cygwin* | pw32* | os2* | cegcc*)
       ;;
     hpux9* | hpux10* | hpux11*)
@@ -72,9 +65,7 @@ else
     irix5* | irix6* | nonstopux*)
       wl='-Wl,'
       ;;
-    newsos6)
-      ;;
-    linux* | k*bsd*-gnu)
+    linux* | k*bsd*-gnu | kopensolaris*-gnu)
       case $cc_basename in
         ecc*)
           wl='-Wl,'
@@ -85,17 +76,26 @@ else
         lf95*)
           wl='-Wl,'
           ;;
-        pgcc | pgf77 | pgf90)
+        nagfor*)
+          wl='-Wl,-Wl,,'
+          ;;
+        pgcc* | pgf77* | pgf90* | pgf95* | pgfortran*)
           wl='-Wl,'
           ;;
         ccc*)
           wl='-Wl,'
           ;;
+        xl* | bgxl* | bgf* | mpixl*)
+          wl='-Wl,'
+          ;;
         como)
           wl='-lopt='
           ;;
         *)
           case `$CC -V 2>&1 | sed 5q` in
+            *Sun\ F* | *Sun*Fortran*)
+              wl=
+              ;;
             *Sun\ C*)
               wl='-Wl,'
               ;;
@@ -103,13 +103,24 @@ else
           ;;
       esac
       ;;
+    newsos6)
+      ;;
+    *nto* | *qnx*)
+      ;;
     osf3* | osf4* | osf5*)
       wl='-Wl,'
       ;;
     rdos*)
       ;;
     solaris*)
-      wl='-Wl,'
+      case $cc_basename in
+        f77* | f90* | f95* | sunf77* | sunf90* | sunf95*)
+          wl='-Qoption ld '
+          ;;
+        *)
+          wl='-Wl,'
+          ;;
+      esac
       ;;
     sunos4*)
       wl='-Qoption ld '
@@ -171,15 +182,14 @@ if test "$with_gnu_ld" = yes; then
       fi
       ;;
     amigaos*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_minus_L=yes
-      # Samuel A. Falvo II <kc5tja@dolphin.openprojects.net> reports
-      # that the semantics of dynamic libraries on AmigaOS, at least up
-      # to version 4, is to share data among multiple programs linked
-      # with the same dynamic library.  Since this doesn't match the
-      # behavior of shared libraries on other platforms, we cannot use
-      # them.
-      ld_shlibs=no
+      case "$host_cpu" in
+        powerpc)
+          ;;
+        m68k)
+          hardcode_libdir_flag_spec='-L$libdir'
+          hardcode_minus_L=yes
+          ;;
+      esac
       ;;
     beos*)
       if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
@@ -198,11 +208,13 @@ if test "$with_gnu_ld" = yes; then
         ld_shlibs=no
       fi
       ;;
+    haiku*)
+      ;;
     interix[3-9]*)
       hardcode_direct=no
       hardcode_libdir_flag_spec='${wl}-rpath,$libdir'
       ;;
-    gnu* | linux* | k*bsd*-gnu)
+    gnu* | linux* | tpf* | k*bsd*-gnu | kopensolaris*-gnu)
       if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
         :
       else
@@ -325,10 +337,14 @@ else
       fi
       ;;
     amigaos*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_minus_L=yes
-      # see comment about different semantics on the GNU ld section
-      ld_shlibs=no
+      case "$host_cpu" in
+        powerpc)
+          ;;
+        m68k)
+          hardcode_libdir_flag_spec='-L$libdir'
+          hardcode_minus_L=yes
+          ;;
+      esac
       ;;
     bsdi[45]*)
       ;;
@@ -342,24 +358,15 @@ else
       ;;
     darwin* | rhapsody*)
       hardcode_direct=no
-      if test "$GCC" = yes ; then
+      if { case $cc_basename in ifort*) true;; *) test "$GCC" = yes;; esac; }; then
         :
       else
-        case $cc_basename in
-          xlc*)
-            ;;
-          *)
-            ld_shlibs=no
-            ;;
-        esac
+        ld_shlibs=no
       fi
       ;;
     dgux*)
       hardcode_libdir_flag_spec='-L$libdir'
       ;;
-    freebsd1*)
-      ld_shlibs=no
-      ;;
     freebsd2.2*)
       hardcode_libdir_flag_spec='-R$libdir'
       hardcode_direct=yes
@@ -420,6 +427,8 @@ else
       hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir'
       hardcode_libdir_separator=:
       ;;
+    *nto* | *qnx*)
+      ;;
     openbsd*)
       if test -f /usr/libexec/ld.so; then
         hardcode_direct=yes
@@ -515,7 +524,12 @@ case "$host_os" in
     library_names_spec='$libname$shrext'
     ;;
   amigaos*)
-    library_names_spec='$libname.a'
+    case "$host_cpu" in
+      powerpc*)
+        library_names_spec='$libname$shrext' ;;
+      m68k)
+        library_names_spec='$libname.a' ;;
+    esac
     ;;
   beos*)
     library_names_spec='$libname$shrext'
@@ -534,8 +548,6 @@ case "$host_os" in
   dgux*)
     library_names_spec='$libname$shrext'
     ;;
-  freebsd1*)
-    ;;
   freebsd* | dragonfly*)
     case "$host_os" in
       freebsd[123]*)
@@ -547,6 +559,9 @@ case "$host_os" in
   gnu*)
     library_names_spec='$libname$shrext'
     ;;
+  haiku*)
+    library_names_spec='$libname$shrext'
+    ;;
   hpux9* | hpux10* | hpux11*)
     case $host_cpu in
       ia64*)
@@ -582,7 +597,7 @@ case "$host_os" in
     ;;
   linux*oldld* | linux*aout* | linux*coff*)
     ;;
-  linux* | k*bsd*-gnu)
+  linux* | k*bsd*-gnu | kopensolaris*-gnu)
     library_names_spec='$libname$shrext'
     ;;
   knetbsd*-gnu)
@@ -594,7 +609,7 @@ case "$host_os" in
   newsos6)
     library_names_spec='$libname$shrext'
     ;;
-  nto-qnx*)
+  *nto* | *qnx*)
     library_names_spec='$libname$shrext'
     ;;
   openbsd*)
@@ -625,6 +640,9 @@ case "$host_os" in
   sysv5* | sco3.2v5* | sco5v6* | unixware* | OpenUNIX* | sysv4*uw2*)
     library_names_spec='$libname$shrext'
     ;;
+  tpf*)
+    library_names_spec='$libname$shrext'
+    ;;
   uts4*)
     library_names_spec='$libname$shrext'
     ;;
diff --git a/config.sub b/config.sub
index 8df55110..092cff00 100755
--- a/config.sub
+++ b/config.sub
@@ -1,24 +1,18 @@
 #! /bin/sh
 # Configuration validation subroutine script.
-#   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-#   2011, 2012 Free Software Foundation, Inc.
+#   Copyright 1992-2014 Free Software Foundation, Inc.
 
-timestamp='2012-12-06'
+timestamp='2014-01-01'
 
-# This file is (in principle) common to ALL GNU software.
-# The presence of a machine in this file suggests that SOME GNU software
-# can handle that machine.  It does not imply ALL GNU software can.
-#
-# This file is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
+# This file is free software; you can redistribute it and/or modify it
+# under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
 # (at your option) any later version.
 #
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, see <http://www.gnu.org/licenses/>.
@@ -26,11 +20,12 @@ timestamp='2012-12-06'
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
+# the same distribution terms that you use for the rest of that
+# program.  This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
 
 
-# Please send patches to <config-patches@gnu.org>.  Submit a context
-# diff and a properly formatted GNU ChangeLog entry.
+# Please send patches with a ChangeLog entry to config-patches@gnu.org.
 #
 # Configuration subroutine to validate and canonicalize a configuration type.
 # Supply the specified configuration type as an argument.
@@ -73,9 +68,7 @@ Report bugs and patches to <config-patches@gnu.org>."
 version="\
 GNU config.sub ($timestamp)
 
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012
-Free Software Foundation, Inc.
+Copyright 1992-2014 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -259,12 +252,12 @@ case $basic_machine in
 	| alpha | alphaev[4-8] | alphaev56 | alphaev6[78] | alphapca5[67] \
 	| alpha64 | alpha64ev[4-8] | alpha64ev56 | alpha64ev6[78] | alpha64pca5[67] \
 	| am33_2.0 \
-	| arc \
+	| arc | arceb \
 	| arm | arm[bl]e | arme[lb] | armv[2-8] | armv[3-8][lb] | armv7[arm] \
 	| avr | avr32 \
 	| be32 | be64 \
 	| bfin \
-	| c4x | clipper \
+	| c4x | c8051 | clipper \
 	| d10v | d30v | dlx | dsp16xx \
 	| epiphany \
 	| fido | fr30 | frv \
@@ -272,6 +265,7 @@ case $basic_machine in
 	| hexagon \
 	| i370 | i860 | i960 | ia64 \
 	| ip2k | iq2000 \
+	| k1om \
 	| le32 | le64 \
 	| lm32 \
 	| m32c | m32r | m32rle | m68000 | m68k | m88k \
@@ -293,16 +287,17 @@ case $basic_machine in
 	| mipsisa64r2 | mipsisa64r2el \
 	| mipsisa64sb1 | mipsisa64sb1el \
 	| mipsisa64sr71k | mipsisa64sr71kel \
+	| mipsr5900 | mipsr5900el \
 	| mipstx39 | mipstx39el \
 	| mn10200 | mn10300 \
 	| moxie \
 	| mt \
 	| msp430 \
 	| nds32 | nds32le | nds32be \
-	| nios | nios2 \
+	| nios | nios2 | nios2eb | nios2el \
 	| ns16k | ns32k \
 	| open8 \
-	| or32 \
+	| or1k | or32 \
 	| pdp10 | pdp11 | pj | pjl \
 	| powerpc | powerpc64 | powerpc64le | powerpcle \
 	| pyramid \
@@ -330,7 +325,7 @@ case $basic_machine in
 	c6x)
 		basic_machine=tic6x-unknown
 		;;
-	m6811 | m68hc11 | m6812 | m68hc12 | m68hcs12x | picochip)
+	m6811 | m68hc11 | m6812 | m68hc12 | m68hcs12x | nvptx | picochip)
 		basic_machine=$basic_machine-unknown
 		os=-none
 		;;
@@ -372,13 +367,13 @@ case $basic_machine in
 	| aarch64-* | aarch64_be-* \
 	| alpha-* | alphaev[4-8]-* | alphaev56-* | alphaev6[78]-* \
 	| alpha64-* | alpha64ev[4-8]-* | alpha64ev56-* | alpha64ev6[78]-* \
-	| alphapca5[67]-* | alpha64pca5[67]-* | arc-* \
+	| alphapca5[67]-* | alpha64pca5[67]-* | arc-* | arceb-* \
 	| arm-*  | armbe-* | armle-* | armeb-* | armv*-* \
 	| avr-* | avr32-* \
 	| be32-* | be64-* \
 	| bfin-* | bs2000-* \
 	| c[123]* | c30-* | [cjt]90-* | c4x-* \
-	| clipper-* | craynv-* | cydra-* \
+	| c8051-* | clipper-* | craynv-* | cydra-* \
 	| d10v-* | d30v-* | dlx-* \
 	| elxsi-* \
 	| f30[01]-* | f700-* | fido-* | fr30-* | frv-* | fx80-* \
@@ -387,6 +382,7 @@ case $basic_machine in
 	| hexagon-* \
 	| i*86-* | i860-* | i960-* | ia64-* \
 	| ip2k-* | iq2000-* \
+	| k1om-* \
 	| le32-* | le64-* \
 	| lm32-* \
 	| m32c-* | m32r-* | m32rle-* \
@@ -410,12 +406,13 @@ case $basic_machine in
 	| mipsisa64r2-* | mipsisa64r2el-* \
 	| mipsisa64sb1-* | mipsisa64sb1el-* \
 	| mipsisa64sr71k-* | mipsisa64sr71kel-* \
+	| mipsr5900-* | mipsr5900el-* \
 	| mipstx39-* | mipstx39el-* \
 	| mmix-* \
 	| mt-* \
 	| msp430-* \
 	| nds32-* | nds32le-* | nds32be-* \
-	| nios-* | nios2-* \
+	| nios-* | nios2-* | nios2eb-* | nios2el-* \
 	| none-* | np1-* | ns16k-* | ns32k-* \
 	| open8-* \
 	| orion-* \
@@ -799,7 +796,7 @@ case $basic_machine in
 		os=-mingw64
 		;;
 	mingw32)
-		basic_machine=i386-pc
+		basic_machine=i686-pc
 		os=-mingw32
 		;;
 	mingw32ce)
@@ -835,7 +832,7 @@ case $basic_machine in
 		basic_machine=`echo $basic_machine | sed -e 's/ms1-/mt-/'`
 		;;
 	msys)
-		basic_machine=i386-pc
+		basic_machine=i686-pc
 		os=-msys
 		;;
 	mvs)
@@ -1357,7 +1354,7 @@ case $os in
 	-gnu* | -bsd* | -mach* | -minix* | -genix* | -ultrix* | -irix* \
 	      | -*vms* | -sco* | -esix* | -isc* | -aix* | -cnk* | -sunos | -sunos[34]*\
 	      | -hpux* | -unos* | -osf* | -luna* | -dgux* | -auroraux* | -solaris* \
-	      | -sym* | -kopensolaris* \
+	      | -sym* | -kopensolaris* | -plan9* \
 	      | -amigaos* | -amigados* | -msdos* | -newsos* | -unicos* | -aof* \
 	      | -aos* | -aros* \
 	      | -nindy* | -vxsim* | -vxworks* | -ebmon* | -hms* | -mvs* \
@@ -1503,9 +1500,6 @@ case $os in
 	-aros*)
 		os=-aros
 		;;
-	-kaos*)
-		os=-kaos
-		;;
 	-zvmoe)
 		os=-zvmoe
 		;;
@@ -1554,6 +1548,9 @@ case $basic_machine in
 	c4x-* | tic4x-*)
 		os=-coff
 		;;
+	c8051-*)
+		os=-elf
+		;;
 	hexagon-*)
 		os=-elf
 		;;
@@ -1597,6 +1594,9 @@ case $basic_machine in
 	mips*-*)
 		os=-elf
 		;;
+	or1k-*)
+		os=-elf
+		;;
 	or32-*)
 		os=-coff
 		;;
diff --git a/configure b/configure
index 9cac99cb..4dc9ce8d 100755
--- a/configure
+++ b/configure
@@ -8102,6 +8102,22 @@ $as_echo "#define HAVE_LC_MESSAGES 1" >>confdefs.h
   fi
 
 
+for ac_header in arpa/inet.h fcntl.h limits.h locale.h libintl.h mcheck.h \
+	netdb.h netinet/in.h stdarg.h stddef.h string.h \
+	sys/ioctl.h sys/param.h sys/socket.h sys/time.h unistd.h \
+	termios.h stropts.h wchar.h wctype.h
+do :
+  as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
+ac_fn_c_check_header_mongrel "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default"
+if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
+  cat >>confdefs.h <<_ACEOF
+#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
+_ACEOF
+
+fi
+
+done
+
 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5
 $as_echo_n "checking for ANSI C header files... " >&6; }
 if ${ac_cv_header_stdc+:} false; then :
@@ -8383,22 +8399,6 @@ $as_echo "#define TIME_WITH_SYS_TIME 1" >>confdefs.h
 
 fi
 
-for ac_header in arpa/inet.h fcntl.h limits.h locale.h libintl.h mcheck.h \
-	netdb.h netinet/in.h stdarg.h stddef.h string.h \
-	sys/ioctl.h sys/param.h sys/socket.h sys/time.h unistd.h \
-	termios.h stropts.h wchar.h wctype.h
-do :
-  as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
-ac_fn_c_check_header_mongrel "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default"
-if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
-  cat >>confdefs.h <<_ACEOF
-#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
-_ACEOF
-
-fi
-
-done
-
 
 if test "$ac_cv_header_string_h" = yes
 then
@@ -10068,8 +10068,12 @@ if test "x$enable_extensions" != "xno"; then
 	extensions_supported=no
 
 		case $host_os in
-	mirbsd*)
-		: ;;
+	mirbsd* | openedition*)	# OS/390 z/OS POSIX layer
+		cat << \EOF > extension/Makefile
+all dist check clean distclean install uninstall distcheck:
+	@exit 0
+EOF
+		;;
 	*)
 	ac_fn_c_check_header_mongrel "$LINENO" "dlfcn.h" "ac_cv_header_dlfcn_h" "$ac_includes_default"
 if test "x$ac_cv_header_dlfcn_h" = xyes; then :
@@ -10147,7 +10151,7 @@ $as_echo "#define DYNAMIC 1" >>confdefs.h
 			if test "$GCC" = yes; then
 				case $host_os in
 				linux*|freebsd*)
-					LDFLAGS="$LDFLAGS -export-dynamic"
+					LDFLAGS="$LDFLAGS -Wl,-export-dynamic"
 					;;
 				esac
 			fi
@@ -10463,6 +10467,10 @@ $as_echo "$_found_readline" >&6; }
         LIBS=$_readline_save_libs
 
         if test $_found_readline = yes ; then
+	   case $host_os in
+	   *bsd* )	_combo="$_combo -ltermcap"
+	  	 ;;
+	   esac
 
 $as_echo "#define HAVE_LIBREADLINE 1" >>confdefs.h
 
@@ -10608,41 +10616,6 @@ _ACEOF
 
 fi
 
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether time.h and sys/time.h may both be included" >&5
-$as_echo_n "checking whether time.h and sys/time.h may both be included... " >&6; }
-if ${ac_cv_header_time+:} false; then :
-  $as_echo_n "(cached) " >&6
-else
-  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h.  */
-#include <sys/types.h>
-#include <sys/time.h>
-#include <time.h>
-
-int
-main ()
-{
-if ((struct tm *) 0)
-return 0;
-  ;
-  return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
-  ac_cv_header_time=yes
-else
-  ac_cv_header_time=no
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-fi
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_time" >&5
-$as_echo "$ac_cv_header_time" >&6; }
-if test $ac_cv_header_time = yes; then
-
-$as_echo "#define TIME_WITH_SYS_TIME 1" >>confdefs.h
-
-fi
-
 { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether struct tm is in sys/time.h or time.h" >&5
 $as_echo_n "checking whether struct tm is in sys/time.h or time.h... " >&6; }
 if ${ac_cv_struct_tm+:} false; then :
diff --git a/configure.ac b/configure.ac
index 8db997a6..e7e2d5f6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,7 +1,7 @@
 dnl
 dnl configure.ac --- autoconf input file for gawk
 dnl
-dnl Copyright (C) 1995-2013 the Free Software Foundation, Inc.
+dnl Copyright (C) 1995-2014 the Free Software Foundation, Inc.
 dnl
 dnl This file is part of GAWK, the GNU implementation of the
 dnl AWK Programming Language.
@@ -137,14 +137,14 @@ AM_LANGINFO_CODESET
 gt_LC_MESSAGES
 
 dnl checks for header files
-AC_HEADER_STDC
-AC_HEADER_STDBOOL
-AC_HEADER_SYS_WAIT
-AC_HEADER_TIME
 AC_CHECK_HEADERS(arpa/inet.h fcntl.h limits.h locale.h libintl.h mcheck.h \
 	netdb.h netinet/in.h stdarg.h stddef.h string.h \
 	sys/ioctl.h sys/param.h sys/socket.h sys/time.h unistd.h \
 	termios.h stropts.h wchar.h wctype.h)
+AC_HEADER_STDC
+AC_HEADER_STDBOOL
+AC_HEADER_SYS_WAIT
+AC_HEADER_TIME
 
 if test "$ac_cv_header_string_h" = yes
 then
@@ -290,8 +290,12 @@ if test "x$enable_extensions" != "xno"; then
 
 	dnl On MirBSD (and probably other systems), don't even try.
 	case $host_os in
-	mirbsd*)
-		: ;;
+	mirbsd* | openedition*)	# OS/390 z/OS POSIX layer
+		cat << \EOF > extension/Makefile
+all dist check clean distclean install uninstall distcheck:
+	@exit 0
+EOF
+		;;
 	*)
 	AC_CHECK_HEADER(dlfcn.h,
 		[
@@ -309,7 +313,7 @@ if test "x$enable_extensions" != "xno"; then
 			if test "$GCC" = yes; then
 				case $host_os in
 				linux*|freebsd*)
-					LDFLAGS="$LDFLAGS -export-dynamic"
+					LDFLAGS="$LDFLAGS -Wl,-export-dynamic"
 					;;
 				esac
 			fi
@@ -374,7 +378,6 @@ GNUPG_CHECK_MPFR
 
 dnl checks for structure members
 AC_CHECK_MEMBERS([struct stat.st_blksize])
-AC_HEADER_TIME
 AC_STRUCT_TM
 AC_STRUCT_TIMEZONE
 
diff --git a/custom.h b/custom.h
index 36b4aa0b..efaa0f27 100644
--- a/custom.h
+++ b/custom.h
@@ -47,12 +47,6 @@
 #define HAVE_MKTIME	1
 #endif
 
-/* For ULTRIX 4.3 */
-#ifdef ultrix
-#define HAVE_MKTIME     1
-#define GETGROUPS_NOT_STANDARD	1
-#endif
-
 /* For whiny users */
 #ifdef USE_INCLUDED_STRFTIME
 #undef HAVE_STRFTIME
@@ -76,3 +70,11 @@
 extern int setenv(const char *name, const char *value, int rewrite);
 extern int unsetenv(const char *name);
 #endif
+
+/* Junk for dfa.[ch] */
+/* The __pure__ attribute was added in gcc 2.96.  */
+#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 96)
+# define _GL_ATTRIBUTE_PURE __attribute__ ((__pure__))
+#else
+# define _GL_ATTRIBUTE_PURE /* empty */
+#endif
diff --git a/debug.c b/debug.c
index 8df9ed0d..5d7db01b 100644
--- a/debug.c
+++ b/debug.c
@@ -2801,7 +2801,7 @@ debug_prog(INSTRUCTION *pc)
 		unserialize(OPTION);
 		unsetenv("DGAWK_RESTART");
 		fprintf(out_fp, "Restarting ...\n");	
-		if (run[0] == 'T') 
+		if (strcasecmp(run, "true") == 0)
 			(void) do_run(NULL, 0);
 
 	} else if (command_file != NULL) {
@@ -4851,7 +4851,7 @@ do_commands(CMDARG *arg, int cmd)
 	struct commands_item *c;
 	
 	if (cmd == D_commands) {
-		int num, type;
+		int num = -1, type;
 		if (arg == NULL)
 			type = has_break_or_watch_point(&num, true);
 		else {
@@ -5448,6 +5448,7 @@ do_eval(CMDARG *arg, int cmd ATTRIBUTE_UNUSED)
 	int ecount = 0, pcount = 0;
 	int ret;
 	int save_flags = do_flags;
+	SRCFILE *the_source;
 	
 	if (prog_running) {
 		this_frame = find_frame(0);
@@ -5458,7 +5459,7 @@ do_eval(CMDARG *arg, int cmd ATTRIBUTE_UNUSED)
 	ctxt = new_context();
 	ctxt->install_func = append_symbol;	/* keep track of newly installed globals */
 	push_context(ctxt);
-	(void) add_srcfile(SRC_CMDLINE, arg->a_string, srcfiles, NULL, NULL);
+	the_source = add_srcfile(SRC_CMDLINE, arg->a_string, srcfiles, NULL, NULL);
 	do_flags = false;
 	ret = parse_program(&code);
 	do_flags = save_flags;
@@ -5559,14 +5560,27 @@ do_eval(CMDARG *arg, int cmd ATTRIBUTE_UNUSED)
 		this_func->param_cnt -= ecount;
 	}
 
-	/* always destroy symbol "@eval", however destroy all newly installed
+	/*
+	 * Always destroy symbol "@eval", however destroy all newly installed
 	 * globals only if fatal error (execute_code() returing NULL).
 	 */
 
 	pop_context();	/* switch to prev context */
 	free_context(ctxt, (ret_val != NULL));   /* free all instructions and optionally symbols */
-	if (ret_val != NULL)
-		destroy_symbol(f);	/* destroy "@eval" */
+
+	if (ret_val != NULL) {
+		/*
+		 * Remove @eval from FUNCTAB, so that above code
+		 * will work the next time around.
+		 */
+		NODE *s = make_string("@eval", 5);
+
+		(void) assoc_remove(func_table, s);
+		unref(s);
+	}
+
+	free_srcfile(the_source);
+
 	return false;
 }
 
diff --git a/depcomp b/depcomp
index e1f51f48..31788017 100755
--- a/depcomp
+++ b/depcomp
@@ -1,9 +1,9 @@
 #! /bin/sh
 # depcomp - compile a program generating dependencies as side-effects
 
-scriptversion=2012-07-12.20; # UTC
+scriptversion=2013-05-30.07; # UTC
 
-# Copyright (C) 1999-2012 Free Software Foundation, Inc.
+# Copyright (C) 1999-2013 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -27,9 +27,9 @@ scriptversion=2012-07-12.20; # UTC
 
 case $1 in
   '')
-     echo "$0: No command.  Try '$0 --help' for more information." 1>&2
-     exit 1;
-     ;;
+    echo "$0: No command.  Try '$0 --help' for more information." 1>&2
+    exit 1;
+    ;;
   -h | --h*)
     cat <<\EOF
 Usage: depcomp [--help] [--version] PROGRAM [ARGS]
@@ -56,11 +56,65 @@ EOF
     ;;
 esac
 
+# Get the directory component of the given path, and save it in the
+# global variables '$dir'.  Note that this directory component will
+# be either empty or ending with a '/' character.  This is deliberate.
+set_dir_from ()
+{
+  case $1 in
+    */*) dir=`echo "$1" | sed -e 's|/[^/]*$|/|'`;;
+      *) dir=;;
+  esac
+}
+
+# Get the suffix-stripped basename of the given path, and save it the
+# global variable '$base'.
+set_base_from ()
+{
+  base=`echo "$1" | sed -e 's|^.*/||' -e 's/\.[^.]*$//'`
+}
+
+# If no dependency file was actually created by the compiler invocation,
+# we still have to create a dummy depfile, to avoid errors with the
+# Makefile "include basename.Plo" scheme.
+make_dummy_depfile ()
+{
+  echo "#dummy" > "$depfile"
+}
+
+# Factor out some common post-processing of the generated depfile.
+# Requires the auxiliary global variable '$tmpdepfile' to be set.
+aix_post_process_depfile ()
+{
+  # If the compiler actually managed to produce a dependency file,
+  # post-process it.
+  if test -f "$tmpdepfile"; then
+    # Each line is of the form 'foo.o: dependency.h'.
+    # Do two passes, one to just change these to
+    #   $object: dependency.h
+    # and one to simply output
+    #   dependency.h:
+    # which is needed to avoid the deleted-header problem.
+    { sed -e "s,^.*\.[$lower]*:,$object:," < "$tmpdepfile"
+      sed -e "s,^.*\.[$lower]*:[$tab ]*,," -e 's,$,:,' < "$tmpdepfile"
+    } > "$depfile"
+    rm -f "$tmpdepfile"
+  else
+    make_dummy_depfile
+  fi
+}
+
 # A tabulation character.
 tab='	'
 # A newline character.
 nl='
 '
+# Character ranges might be problematic outside the C locale.
+# These definitions help.
+upper=ABCDEFGHIJKLMNOPQRSTUVWXYZ
+lower=abcdefghijklmnopqrstuvwxyz
+digits=0123456789
+alpha=${upper}${lower}
 
 if test -z "$depmode" || test -z "$source" || test -z "$object"; then
   echo "depcomp: Variables source, object and depmode must be set" 1>&2
@@ -88,32 +142,32 @@ if test "$depmode" = hp; then
 fi
 
 if test "$depmode" = dashXmstdout; then
-   # This is just like dashmstdout with a different argument.
-   dashmflag=-xM
-   depmode=dashmstdout
+  # This is just like dashmstdout with a different argument.
+  dashmflag=-xM
+  depmode=dashmstdout
 fi
 
 cygpath_u="cygpath -u -f -"
 if test "$depmode" = msvcmsys; then
-   # This is just like msvisualcpp but w/o cygpath translation.
-   # Just convert the backslash-escaped backslashes to single forward
-   # slashes to satisfy depend.m4
-   cygpath_u='sed s,\\\\,/,g'
-   depmode=msvisualcpp
+  # This is just like msvisualcpp but w/o cygpath translation.
+  # Just convert the backslash-escaped backslashes to single forward
+  # slashes to satisfy depend.m4
+  cygpath_u='sed s,\\\\,/,g'
+  depmode=msvisualcpp
 fi
 
 if test "$depmode" = msvc7msys; then
-   # This is just like msvc7 but w/o cygpath translation.
-   # Just convert the backslash-escaped backslashes to single forward
-   # slashes to satisfy depend.m4
-   cygpath_u='sed s,\\\\,/,g'
-   depmode=msvc7
+  # This is just like msvc7 but w/o cygpath translation.
+  # Just convert the backslash-escaped backslashes to single forward
+  # slashes to satisfy depend.m4
+  cygpath_u='sed s,\\\\,/,g'
+  depmode=msvc7
 fi
 
 if test "$depmode" = xlc; then
-   # IBM C/C++ Compilers xlc/xlC can output gcc-like dependency information.
-   gccflag=-qmakedep=gcc,-MF
-   depmode=gcc
+  # IBM C/C++ Compilers xlc/xlC can output gcc-like dependency information.
+  gccflag=-qmakedep=gcc,-MF
+  depmode=gcc
 fi
 
 case "$depmode" in
@@ -136,8 +190,7 @@ gcc3)
   done
   "$@"
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
@@ -163,15 +216,14 @@ gcc)
   fi
   "$@" -Wp,"$gccflag$tmpdepfile"
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
   rm -f "$depfile"
   echo "$object : \\" > "$depfile"
-  alpha=ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
-## The second -e expression handles DOS-style file names with drive letters.
+  # The second -e expression handles DOS-style file names with drive
+  # letters.
   sed -e 's/^[^:]*: / /' \
       -e 's/^['$alpha']:\/[^:]*: / /' < "$tmpdepfile" >> "$depfile"
 ## This next piece of magic avoids the "deleted header file" problem.
@@ -180,15 +232,15 @@ gcc)
 ## typically no way to rebuild the header).  We avoid this by adding
 ## dummy dependencies for each header file.  Too bad gcc doesn't do
 ## this for us directly.
-  tr ' ' "$nl" < "$tmpdepfile" |
 ## Some versions of gcc put a space before the ':'.  On the theory
 ## that the space means something, we add a space to the output as
 ## well.  hp depmode also adds that space, but also prefixes the VPATH
 ## to the object.  Take care to not repeat it in the output.
 ## Some versions of the HPUX 10.20 sed can't process this invocation
 ## correctly.  Breaking it into two sed invocations is a workaround.
-    sed -e 's/^\\$//' -e '/^$/d' -e "s|.*$object$||" -e '/:$/d' \
-      | sed -e 's/$/ :/' >> "$depfile"
+  tr ' ' "$nl" < "$tmpdepfile" \
+    | sed -e 's/^\\$//' -e '/^$/d' -e "s|.*$object$||" -e '/:$/d' \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -199,47 +251,6 @@ hp)
   exit 1
   ;;
 
-sgi)
-  if test "$libtool" = yes; then
-    "$@" "-Wp,-MDupdate,$tmpdepfile"
-  else
-    "$@" -MDupdate "$tmpdepfile"
-  fi
-  stat=$?
-  if test $stat -eq 0; then :
-  else
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  rm -f "$depfile"
-
-  if test -f "$tmpdepfile"; then  # yes, the sourcefile depend on other files
-    echo "$object : \\" > "$depfile"
-
-    # Clip off the initial element (the dependent).  Don't try to be
-    # clever and replace this with sed code, as IRIX sed won't handle
-    # lines with more than a fixed number of characters (4096 in
-    # IRIX 6.2 sed, 8192 in IRIX 6.5).  We also remove comment lines;
-    # the IRIX cc adds comments like '#:fec' to the end of the
-    # dependency line.
-    tr ' ' "$nl" < "$tmpdepfile" \
-    | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' | \
-    tr "$nl" ' ' >> "$depfile"
-    echo >> "$depfile"
-
-    # The second pass generates a dummy entry for each header file.
-    tr ' ' "$nl" < "$tmpdepfile" \
-   | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' -e 's/$/:/' \
-   >> "$depfile"
-  else
-    # The sourcefile does not contain any dependencies, so just
-    # store a dummy comment line, to avoid errors with the Makefile
-    # "include basename.Plo" scheme.
-    echo "#dummy" > "$depfile"
-  fi
-  rm -f "$tmpdepfile"
-  ;;
-
 xlc)
   # This case exists only to let depend.m4 do its work.  It works by
   # looking at the text of this script.  This case will never be run,
@@ -253,9 +264,8 @@ aix)
   # current directory.  Also, the AIX compiler puts '$object:' at the
   # start of each line; $object doesn't have directory information.
   # Version 6 uses the directory in both cases.
-  dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-  test "x$dir" = "x$object" && dir=
-  base=`echo "$object" | sed -e 's|^.*/||' -e 's/\.o$//' -e 's/\.lo$//'`
+  set_dir_from "$object"
+  set_base_from "$object"
   if test "$libtool" = yes; then
     tmpdepfile1=$dir$base.u
     tmpdepfile2=$base.u
@@ -268,9 +278,7 @@ aix)
     "$@" -M
   fi
   stat=$?
-
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
     exit $stat
   fi
@@ -279,65 +287,37 @@ aix)
   do
     test -f "$tmpdepfile" && break
   done
-  if test -f "$tmpdepfile"; then
-    # Each line is of the form 'foo.o: dependent.h'.
-    # Do two passes, one to just change these to
-    # '$object: dependent.h' and one to simply 'dependent.h:'.
-    sed -e "s,^.*\.[a-z]*:,$object:," < "$tmpdepfile" > "$depfile"
-    sed -e 's,^.*\.[a-z]*:['"$tab"' ]*,,' -e 's,$,:,' < "$tmpdepfile" >> "$depfile"
-  else
-    # The sourcefile does not contain any dependencies, so just
-    # store a dummy comment line, to avoid errors with the Makefile
-    # "include basename.Plo" scheme.
-    echo "#dummy" > "$depfile"
-  fi
-  rm -f "$tmpdepfile"
+  aix_post_process_depfile
   ;;
 
-icc)
-  # Intel's C compiler anf tcc (Tiny C Compiler) understand '-MD -MF file'.
-  # However on
-  #    $CC -MD -MF foo.d -c -o sub/foo.o sub/foo.c
-  # ICC 7.0 will fill foo.d with something like
-  #    foo.o: sub/foo.c
-  #    foo.o: sub/foo.h
-  # which is wrong.  We want
-  #    sub/foo.o: sub/foo.c
-  #    sub/foo.o: sub/foo.h
-  #    sub/foo.c:
-  #    sub/foo.h:
-  # ICC 7.1 will output
-  #    foo.o: sub/foo.c sub/foo.h
-  # and will wrap long lines using '\':
-  #    foo.o: sub/foo.c ... \
-  #     sub/foo.h ... \
-  #     ...
-  # tcc 0.9.26 (FIXME still under development at the moment of writing)
-  # will emit a similar output, but also prepend the continuation lines
-  # with horizontal tabulation characters.
+tcc)
+  # tcc (Tiny C Compiler) understand '-MD -MF file' since version 0.9.26
+  # FIXME: That version still under development at the moment of writing.
+  #        Make that this statement remains true also for stable, released
+  #        versions.
+  # It will wrap lines (doesn't matter whether long or short) with a
+  # trailing '\', as in:
+  #
+  #   foo.o : \
+  #    foo.c \
+  #    foo.h \
+  #
+  # It will put a trailing '\' even on the last line, and will use leading
+  # spaces rather than leading tabs (at least since its commit 0394caf7
+  # "Emit spaces for -MD").
   "$@" -MD -MF "$tmpdepfile"
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
   rm -f "$depfile"
-  # Each line is of the form 'foo.o: dependent.h',
-  # or 'foo.o: dep1.h dep2.h \', or ' dep3.h dep4.h \'.
-  # Do two passes, one to just change these to
-  # '$object: dependent.h' and one to simply 'dependent.h:'.
-  sed -e "s/^[ $tab][ $tab]*/  /" -e "s,^[^:]*:,$object :," \
-    < "$tmpdepfile" > "$depfile"
-  sed '
-    s/[ '"$tab"'][ '"$tab"']*/ /g
-    s/^ *//
-    s/ *\\*$//
-    s/^[^:]*: *//
-    /^$/d
-    /:$/d
-    s/$/ :/
-  ' < "$tmpdepfile" >> "$depfile"
+  # Each non-empty line is of the form 'foo.o : \' or ' dep.h \'.
+  # We have to change lines of the first kind to '$object: \'.
+  sed -e "s|.*:|$object :|" < "$tmpdepfile" > "$depfile"
+  # And for each line of the second kind, we have to emit a 'dep.h:'
+  # dummy dependency, to avoid the deleted-header problem.
+  sed -n -e 's|^  *\(.*\) *\\$|\1:|p' < "$tmpdepfile" >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -356,34 +336,37 @@ pgcc)
   #    foo.o: sub/foo.c ... \
   #     sub/foo.h ... \
   #     ...
-  dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-  test "x$dir" = "x$object" && dir=
+  set_dir_from "$object"
   # Use the source, not the object, to determine the base name, since
   # that's sadly what pgcc will do too.
-  base=`echo "$source" | sed -e 's|^.*/||' -e 's/\.[-_a-zA-Z0-9]*$//'`
-  tmpdepfile="$base.d"
+  set_base_from "$source"
+  tmpdepfile=$base.d
 
   # For projects that build the same source file twice into different object
   # files, the pgcc approach of using the *source* file root name can cause
   # problems in parallel builds.  Use a locking strategy to avoid stomping on
   # the same $tmpdepfile.
-  lockdir="$base.d-lock"
-  trap "echo '$0: caught signal, cleaning up...' >&2; rm -rf $lockdir" 1 2 13 15
+  lockdir=$base.d-lock
+  trap "
+    echo '$0: caught signal, cleaning up...' >&2
+    rmdir '$lockdir'
+    exit 1
+  " 1 2 13 15
   numtries=100
   i=$numtries
-  while test $i -gt 0 ; do
+  while test $i -gt 0; do
     # mkdir is a portable test-and-set.
-    if mkdir $lockdir 2>/dev/null; then
+    if mkdir "$lockdir" 2>/dev/null; then
       # This process acquired the lock.
       "$@" -MD
       stat=$?
       # Release the lock.
-      rm -rf $lockdir
+      rmdir "$lockdir"
       break
     else
-      ## the lock is being held by a different process,
-      ## wait until the winning process is done or we timeout
-      while test -d $lockdir && test $i -gt 0; do
+      # If the lock is being held by a different process, wait
+      # until the winning process is done or we timeout.
+      while test -d "$lockdir" && test $i -gt 0; do
         sleep 1
         i=`expr $i - 1`
       done
@@ -409,8 +392,8 @@ pgcc)
   sed "s,^[^:]*:,$object :," < "$tmpdepfile" > "$depfile"
   # Some versions of the HPUX 10.20 sed can't process this invocation
   # correctly.  Breaking it into two sed invocations is a workaround.
-  sed 's,^[^:]*: \(.*\)$,\1,;s/^\\$//;/^$/d;/:$/d' < "$tmpdepfile" |
-    sed -e 's/$/ :/' >> "$depfile"
+  sed 's,^[^:]*: \(.*\)$,\1,;s/^\\$//;/^$/d;/:$/d' < "$tmpdepfile" \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -421,9 +404,8 @@ hp2)
   # 'foo.d', which lands next to the object file, wherever that
   # happens to be.
   # Much of this is similar to the tru64 case; see comments there.
-  dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-  test "x$dir" = "x$object" && dir=
-  base=`echo "$object" | sed -e 's|^.*/||' -e 's/\.o$//' -e 's/\.lo$//'`
+  set_dir_from  "$object"
+  set_base_from "$object"
   if test "$libtool" = yes; then
     tmpdepfile1=$dir$base.d
     tmpdepfile2=$dir.libs/$base.d
@@ -434,8 +416,7 @@ hp2)
     "$@" +Maked
   fi
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
      rm -f "$tmpdepfile1" "$tmpdepfile2"
      exit $stat
   fi
@@ -445,76 +426,61 @@ hp2)
     test -f "$tmpdepfile" && break
   done
   if test -f "$tmpdepfile"; then
-    sed -e "s,^.*\.[a-z]*:,$object:," "$tmpdepfile" > "$depfile"
+    sed -e "s,^.*\.[$lower]*:,$object:," "$tmpdepfile" > "$depfile"
     # Add 'dependent.h:' lines.
     sed -ne '2,${
-	       s/^ *//
-	       s/ \\*$//
-	       s/$/:/
-	       p
-	     }' "$tmpdepfile" >> "$depfile"
+               s/^ *//
+               s/ \\*$//
+               s/$/:/
+               p
+             }' "$tmpdepfile" >> "$depfile"
   else
-    echo "#dummy" > "$depfile"
+    make_dummy_depfile
   fi
   rm -f "$tmpdepfile" "$tmpdepfile2"
   ;;
 
 tru64)
-   # The Tru64 compiler uses -MD to generate dependencies as a side
-   # effect.  'cc -MD -o foo.o ...' puts the dependencies into 'foo.o.d'.
-   # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put
-   # dependencies in 'foo.d' instead, so we check for that too.
-   # Subdirectories are respected.
-   dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-   test "x$dir" = "x$object" && dir=
-   base=`echo "$object" | sed -e 's|^.*/||' -e 's/\.o$//' -e 's/\.lo$//'`
-
-   if test "$libtool" = yes; then
-      # With Tru64 cc, shared objects can also be used to make a
-      # static library.  This mechanism is used in libtool 1.4 series to
-      # handle both shared and static libraries in a single compilation.
-      # With libtool 1.4, dependencies were output in $dir.libs/$base.lo.d.
-      #
-      # With libtool 1.5 this exception was removed, and libtool now
-      # generates 2 separate objects for the 2 libraries.  These two
-      # compilations output dependencies in $dir.libs/$base.o.d and
-      # in $dir$base.o.d.  We have to check for both files, because
-      # one of the two compilations can be disabled.  We should prefer
-      # $dir$base.o.d over $dir.libs/$base.o.d because the latter is
-      # automatically cleaned when .libs/ is deleted, while ignoring
-      # the former would cause a distcleancheck panic.
-      tmpdepfile1=$dir.libs/$base.lo.d   # libtool 1.4
-      tmpdepfile2=$dir$base.o.d          # libtool 1.5
-      tmpdepfile3=$dir.libs/$base.o.d    # libtool 1.5
-      tmpdepfile4=$dir.libs/$base.d      # Compaq CCC V6.2-504
-      "$@" -Wc,-MD
-   else
-      tmpdepfile1=$dir$base.o.d
-      tmpdepfile2=$dir$base.d
-      tmpdepfile3=$dir$base.d
-      tmpdepfile4=$dir$base.d
-      "$@" -MD
-   fi
-
-   stat=$?
-   if test $stat -eq 0; then :
-   else
-      rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" "$tmpdepfile4"
-      exit $stat
-   fi
-
-   for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" "$tmpdepfile4"
-   do
-     test -f "$tmpdepfile" && break
-   done
-   if test -f "$tmpdepfile"; then
-      sed -e "s,^.*\.[a-z]*:,$object:," < "$tmpdepfile" > "$depfile"
-      sed -e 's,^.*\.[a-z]*:['"$tab"' ]*,,' -e 's,$,:,' < "$tmpdepfile" >> "$depfile"
-   else
-      echo "#dummy" > "$depfile"
-   fi
-   rm -f "$tmpdepfile"
-   ;;
+  # The Tru64 compiler uses -MD to generate dependencies as a side
+  # effect.  'cc -MD -o foo.o ...' puts the dependencies into 'foo.o.d'.
+  # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put
+  # dependencies in 'foo.d' instead, so we check for that too.
+  # Subdirectories are respected.
+  set_dir_from  "$object"
+  set_base_from "$object"
+
+  if test "$libtool" = yes; then
+    # Libtool generates 2 separate objects for the 2 libraries.  These
+    # two compilations output dependencies in $dir.libs/$base.o.d and
+    # in $dir$base.o.d.  We have to check for both files, because
+    # one of the two compilations can be disabled.  We should prefer
+    # $dir$base.o.d over $dir.libs/$base.o.d because the latter is
+    # automatically cleaned when .libs/ is deleted, while ignoring
+    # the former would cause a distcleancheck panic.
+    tmpdepfile1=$dir$base.o.d          # libtool 1.5
+    tmpdepfile2=$dir.libs/$base.o.d    # Likewise.
+    tmpdepfile3=$dir.libs/$base.d      # Compaq CCC V6.2-504
+    "$@" -Wc,-MD
+  else
+    tmpdepfile1=$dir$base.d
+    tmpdepfile2=$dir$base.d
+    tmpdepfile3=$dir$base.d
+    "$@" -MD
+  fi
+
+  stat=$?
+  if test $stat -ne 0; then
+    rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
+    exit $stat
+  fi
+
+  for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
+  do
+    test -f "$tmpdepfile" && break
+  done
+  # Same post-processing that is required for AIX mode.
+  aix_post_process_depfile
+  ;;
 
 msvc7)
   if test "$libtool" = yes; then
@@ -525,8 +491,7 @@ msvc7)
   "$@" $showIncludes > "$tmpdepfile"
   stat=$?
   grep -v '^Note: including file: ' "$tmpdepfile"
-  if test "$stat" = 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
@@ -552,6 +517,7 @@ $ {
   G
   p
 }' >> "$depfile"
+  echo >> "$depfile" # make sure the fragment doesn't end with a backslash
   rm -f "$tmpdepfile"
   ;;
 
@@ -603,13 +569,14 @@ dashmstdout)
   # in the target name.  This is to cope with DOS-style filenames:
   # a dependency such as 'c:/foo/bar' could be seen as target 'c' otherwise.
   "$@" $dashmflag |
-    sed 's:^['"$tab"' ]*[^:'"$tab"' ][^:][^:]*\:['"$tab"' ]*:'"$object"'\: :' > "$tmpdepfile"
+    sed "s|^[$tab ]*[^:$tab ][^:][^:]*:[$tab ]*|$object: |" > "$tmpdepfile"
   rm -f "$depfile"
   cat < "$tmpdepfile" > "$depfile"
-  tr ' ' "$nl" < "$tmpdepfile" | \
-## Some versions of the HPUX 10.20 sed can't process this invocation
-## correctly.  Breaking it into two sed invocations is a workaround.
-    sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' | sed -e 's/$/ :/' >> "$depfile"
+  # Some versions of the HPUX 10.20 sed can't process this sed invocation
+  # correctly.  Breaking it into two sed invocations is a workaround.
+  tr ' ' "$nl" < "$tmpdepfile" \
+    | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -662,10 +629,12 @@ makedepend)
   # makedepend may prepend the VPATH from the source file name to the object.
   # No need to regex-escape $object, excess matching of '.' is harmless.
   sed "s|^.*\($object *:\)|\1|" "$tmpdepfile" > "$depfile"
-  sed '1,2d' "$tmpdepfile" | tr ' ' "$nl" | \
-## Some versions of the HPUX 10.20 sed can't process this invocation
-## correctly.  Breaking it into two sed invocations is a workaround.
-    sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' | sed -e 's/$/ :/' >> "$depfile"
+  # Some versions of the HPUX 10.20 sed can't process the last invocation
+  # correctly.  Breaking it into two sed invocations is a workaround.
+  sed '1,2d' "$tmpdepfile" \
+    | tr ' ' "$nl" \
+    | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile" "$tmpdepfile".bak
   ;;
 
@@ -701,10 +670,10 @@ cpp)
     esac
   done
 
-  "$@" -E |
-    sed -n -e '/^# [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
-       -e '/^#line [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' |
-    sed '$ s: \\$::' > "$tmpdepfile"
+  "$@" -E \
+    | sed -n -e '/^# [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
+             -e '/^#line [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
+    | sed '$ s: \\$::' > "$tmpdepfile"
   rm -f "$depfile"
   echo "$object : \\" > "$depfile"
   cat < "$tmpdepfile" >> "$depfile"
@@ -736,15 +705,15 @@ msvisualcpp)
       shift
       ;;
     "-Gm"|"/Gm"|"-Gi"|"/Gi"|"-ZI"|"/ZI")
-	set fnord "$@"
-	shift
-	shift
-	;;
+        set fnord "$@"
+        shift
+        shift
+        ;;
     *)
-	set fnord "$@" "$arg"
-	shift
-	shift
-	;;
+        set fnord "$@" "$arg"
+        shift
+        shift
+        ;;
     esac
   done
   "$@" -E 2>/dev/null |
diff --git a/dfa.c b/dfa.c
index a75d332c..e2a83d43 100644
--- a/dfa.c
+++ b/dfa.c
@@ -1,5 +1,5 @@
 /* dfa.c - deterministic extended regexp routines for GNU
-   Copyright (C) 1988, 1998, 2000, 2002, 2004-2005, 2007-2013 Free Software
+   Copyright (C) 1988, 1998, 2000, 2002, 2004-2005, 2007-2014 Free Software
    Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
@@ -37,14 +37,11 @@
 #if HAVE_SETLOCALE
 #include <locale.h>
 #endif
-#ifdef HAVE_STDBOOL_H
-#include <stdbool.h>
-#else
-#include "missing_d/gawkbool.h"
-#endif /* HAVE_STDBOOL_H */
-
-#include "dfa.h"
 
+/* Gawk doesn't use Gnulib, so don't assume that setlocale is present.  */
+#ifndef LC_ALL
+# define setlocale(category, locale) NULL
+#endif
 
 #define STREQ(a, b) (strcmp (a, b) == 0)
 
@@ -58,7 +55,6 @@
    host does not conform to Posix.  */
 #define ISASCIIDIGIT(c) ((unsigned) (c) - '0' <= 9)
 
-/* gettext.h ensures that we don't use gettext if ENABLE_NLS is not defined */
 #include "gettext.h"
 #define _(str) gettext (str)
 
@@ -69,21 +65,10 @@
 # include <wctype.h>
 #endif
 
-#ifdef GAWK
-/* The __pure__ attribute was added in gcc 2.96.  */
-#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 96)
-# define _GL_ATTRIBUTE_PURE __attribute__ ((__pure__))
-#else
-# define _GL_ATTRIBUTE_PURE /* empty */
-#endif
-#endif /* GAWK */
-
-#if HAVE_LANGINFO_CODESET
-# include <langinfo.h>
-#endif
-
 #include "xalloc.h"
 
+#include "dfa.h"
+
 #ifdef GAWK
 static int
 is_blank (int c)
@@ -108,29 +93,34 @@ extern int gawk_mb_cur_max;
 # undef clrbit
 #endif
 
-/* Number of bits in an unsigned char.  */
-#ifndef CHARBITS
-# define CHARBITS 8
-#endif
-
 /* First integer value that is greater than any character code.  */
-#define NOTCHAR (1 << CHARBITS)
+enum { NOTCHAR = 1 << CHAR_BIT };
 
-/* INTBITS need not be exact, just a lower bound.  */
-#ifndef INTBITS
-# define INTBITS (CHARBITS * sizeof (int))
-#endif
+/* This represents part of a character class.  It must be unsigned and
+   at least CHARCLASS_WORD_BITS wide.  Any excess bits are zero.  */
+typedef unsigned int charclass_word;
+
+/* The number of bits used in a charclass word.  utf8_classes assumes
+   this is exactly 32.  */
+enum { CHARCLASS_WORD_BITS = 32 };
 
-/* Number of ints required to hold a bit for every character.  */
-#define CHARCLASS_INTS ((NOTCHAR + INTBITS - 1) / INTBITS)
+/* The maximum useful value of a charclass_word; all used bits are 1.  */
+#define CHARCLASS_WORD_MASK \
+  (((charclass_word) 1 << (CHARCLASS_WORD_BITS - 1) << 1) - 1)
+
+/* Number of words required to hold a bit for every character.  */
+enum
+{
+  CHARCLASS_WORDS = (NOTCHAR + CHARCLASS_WORD_BITS - 1) / CHARCLASS_WORD_BITS
+};
 
 /* Sets of unsigned characters are stored as bit vectors in arrays of ints.  */
-typedef unsigned int charclass[CHARCLASS_INTS];
+typedef charclass_word charclass[CHARCLASS_WORDS];
 
 /* Convert a possibly-signed character to an unsigned character.  This is
    a bit safer than casting to unsigned char, since it catches some type
    errors that the cast doesn't.  */
-static inline unsigned char
+static unsigned char
 to_uchar (char ch)
 {
   return ch;
@@ -219,7 +209,8 @@ enum
   EMPTY = NOTCHAR,              /* EMPTY is a terminal symbol that matches
                                    the empty string.  */
 
-  BACKREF,                      /* BACKREF is generated by \<digit>; it
+  BACKREF,                      /* BACKREF is generated by \<digit>
+                                   or by any other construct that
                                    is not completely handled.  If the scanner
                                    detects a transition on backref, it returns
                                    a kind of "semi-success" indicating that
@@ -227,27 +218,25 @@ enum
                                    a backtracking matcher.  */
 
   BEGLINE,                      /* BEGLINE is a terminal symbol that matches
-                                   the empty string if it is at the beginning
-                                   of a line.  */
+                                   the empty string at the beginning of a
+                                   line.  */
 
   ENDLINE,                      /* ENDLINE is a terminal symbol that matches
-                                   the empty string if it is at the end of
-                                   a line.  */
+                                   the empty string at the end of a line.  */
 
   BEGWORD,                      /* BEGWORD is a terminal symbol that matches
-                                   the empty string if it is at the beginning
-                                   of a word.  */
+                                   the empty string at the beginning of a
+                                   word.  */
 
   ENDWORD,                      /* ENDWORD is a terminal symbol that matches
-                                   the empty string if it is at the end of
-                                   a word.  */
+                                   the empty string at the end of a word.  */
 
   LIMWORD,                      /* LIMWORD is a terminal symbol that matches
-                                   the empty string if it is at the beginning
-                                   or the end of a word.  */
+                                   the empty string at the beginning or the
+                                   end of a word.  */
 
   NOTLIMWORD,                   /* NOTLIMWORD is a terminal symbol that
-                                   matches the empty string if it is not at
+                                   matches the empty string not at
                                    the beginning or end of a word.  */
 
   QMARK,                        /* QMARK is an operator of one argument that
@@ -328,7 +317,8 @@ typedef struct
   size_t hash;                  /* Hash of the positions of this state.  */
   position_set elems;           /* Positions this state could match.  */
   unsigned char context;        /* Context from previous state.  */
-  char backref;                 /* True if this state matches a \<digit>.  */
+  bool has_backref;		/* This state matches a \<digit>.  */
+  bool has_mbcset;		/* This state matches a MBCSET.  */
   unsigned short constraint;    /* Constraint for this state to accept.  */
   token first_end;              /* Token value of the first END in elems.  */
   position_set mbps;            /* Positions which can match multibyte
@@ -345,13 +335,16 @@ typedef ptrdiff_t state_num;
 struct mb_char_classes
 {
   ptrdiff_t cset;
-  int invert;
+  bool invert;
   wchar_t *chars;               /* Normal characters.  */
   size_t nchars;
   wctype_t *ch_classes;         /* Character classes.  */
   size_t nch_classes;
-  wchar_t *range_sts;           /* Range characters (start of the range).  */
-  wchar_t *range_ends;          /* Range characters (end of the range).  */
+  struct			/* Range characters.  */
+  {
+    wchar_t beg;		/* Range start.  */
+    wchar_t end;		/* Range end.  */
+  } *ranges;
   size_t nranges;
   char **equivs;                /* Equivalence classes.  */
   size_t nequivs;
@@ -377,10 +370,12 @@ struct dfa
   size_t nleaves;               /* Number of leaves on the parse tree.  */
   size_t nregexps;              /* Count of parallel regexps being built
                                    with dfaparse.  */
-  unsigned int mb_cur_max;      /* Cached value of MB_CUR_MAX.  */
+  bool fast;			/* The DFA is fast.  */
+  bool multibyte;		/* MB_CUR_MAX > 1.  */
   token utf8_anychar_classes[5]; /* To lower ANYCHAR in UTF-8 locales.  */
+  mbstate_t mbs;		/* Multibyte conversion state.  */
 
-  /* The following are used only if MB_CUR_MAX > 1.  */
+  /* The following are valid only if MB_CUR_MAX > 1.  */
 
   /* The value of multibyte_prop[i] is defined by following rule.
      if tokens[i] < NOTCHAR
@@ -399,18 +394,27 @@ struct dfa
      multibyte_prop
      = 3     , 1               ,  0              ,  2              , 3
    */
-  size_t nmultibyte_prop;
   int *multibyte_prop;
 
+#if MBS_SUPPORT
+  /* A table indexed by byte values that contains the corresponding wide
+     character (if any) for that byte.  WEOF means the byte is not a
+     valid single-byte character.  */
+  wint_t mbrtowc_cache[NOTCHAR];
+#endif
+
   /* Array of the bracket expression in the DFA.  */
   struct mb_char_classes *mbcsets;
   size_t nmbcsets;
   size_t mbcsets_alloc;
 
+  /* Fields filled by the superset.  */
+  struct dfa *superset;             /* Hint of the dfa.  */
+
   /* Fields filled by the state builder.  */
   dfa_state *states;            /* States of the dfa.  */
   state_num sindex;             /* Index for adding new states.  */
-  state_num salloc;             /* Number of states currently allocated.  */
+  size_t salloc;		/* Number of states currently allocated.  */
 
   /* Fields filled by the parse tree->NFA conversion.  */
   position_set *follows;        /* Array of follow sets, indexed by position
@@ -420,7 +424,7 @@ struct dfa
                                    matching the given position in a string
                                    matching the regexp.  Allocated to the
                                    maximum possible position index.  */
-  int searchflag;               /* True if we are supposed to build a searching
+  bool searchflag;		/* We are supposed to build a searching
                                    as opposed to an exact matcher.  A searching
                                    matcher finds the first and shortest string
                                    matching a regexp anywhere in the buffer,
@@ -430,16 +434,16 @@ struct dfa
 
   /* Fields filled by dfaexec.  */
   state_num tralloc;            /* Number of transition tables that have
-                                   slots so far.  */
+                                   slots so far, not counting trans[-1].  */
   int trcount;                  /* Number of transition tables that have
                                    actually been built.  */
   state_num **trans;            /* Transition tables for states that can
                                    never accept.  If the transitions for a
                                    state have not yet been computed, or the
                                    state could possibly accept, its entry in
-                                   this table is NULL.  */
-  state_num **realtrans;        /* Trans always points to realtrans + 1; this
-                                   is so trans[-1] can contain NULL.  */
+                                   this table is NULL.  This points to one
+                                   past the start of the allocated array,
+                                   and trans[-1] is always NULL.  */
   state_num **fails;            /* Transition tables after failing to accept
                                    on a state that potentially could do so.  */
   int *success;                 /* Table of acceptance conditions used in
@@ -454,56 +458,83 @@ struct dfa
   struct dfamust *musts;        /* List of strings, at least one of which
                                    is known to appear in any r.e. matching
                                    the dfa.  */
+  position_set mb_follows;	/* Follow set added by ANYCHAR and/or MBCSET
+                                   on demand.  */
+  int *mb_match_lens;           /* Array of length reduced by ANYCHAR and/or
+                                   MBCSET.  Null if mb_follows.elems has not
+                                   been allocated.  */
 };
 
 /* Some macros for user access to dfa internals.  */
 
-/* ACCEPTING returns true if s could possibly be an accepting state of r.  */
+/* S could possibly be an accepting state of R.  */
 #define ACCEPTING(s, r) ((r).states[s].constraint)
 
-/* ACCEPTS_IN_CONTEXT returns true if the given state accepts in the
-   specified context.  */
+/* STATE accepts in the specified context.  */
 #define ACCEPTS_IN_CONTEXT(prev, curr, state, dfa) \
   SUCCEEDS_IN_CONTEXT ((dfa).states[state].constraint, prev, curr)
 
 static void dfamust (struct dfa *dfa);
 static void regexp (void);
 
-/* These two macros are identical to the ones in gnulib's xalloc.h,
-   except that they not to case the result to "(t *)", and thus may
-   be used via type-free CALLOC and MALLOC macros.  */
-#undef XNMALLOC
-#undef XCALLOC
-
-/* Allocate memory for N elements of type T, with error checking.  */
-/* extern t *XNMALLOC (size_t n, typename t); */
-# define XNMALLOC(n, t) \
-    (sizeof (t) == 1 ? xmalloc (n) : xnmalloc (n, sizeof (t)))
-
-/* Allocate memory for N elements of type T, with error checking,
-   and zero it.  */
-/* extern t *XCALLOC (size_t n, typename t); */
-# define XCALLOC(n, t) \
-    (sizeof (t) == 1 ? xzalloc (n) : xcalloc (n, sizeof (t)))
-
-#define CALLOC(p, n) do { (p) = XCALLOC (n, *(p)); } while (0)
-#undef MALLOC	/* Irix defines this */
-#define MALLOC(p, n) do { (p) = XNMALLOC (n, *(p)); } while (0)
-#define REALLOC(p, n) do {(p) = xnrealloc (p, n, sizeof (*(p))); } while (0)
-
-/* Reallocate an array of type *P if N_ALLOC is <= N_REQUIRED.  */
-#define REALLOC_IF_NECESSARY(p, n_alloc, n_required)		\
-  do								\
-    {								\
-      if ((n_alloc) <= (n_required))				\
-        {							\
-          size_t new_n_alloc = (n_required) + !(p);		\
-          (p) = x2nrealloc (p, &new_n_alloc, sizeof (*(p)));	\
-          (n_alloc) = new_n_alloc;				\
-        }							\
-    }								\
-  while (false)
+static void
+dfambcache (struct dfa *d)
+{
+#if MBS_SUPPORT
+  int i;
+  for (i = CHAR_MIN; i <= CHAR_MAX; ++i)
+    {
+      char c = i;
+      unsigned char uc = i;
+      mbstate_t s = { 0 };
+      wchar_t wc;
+      d->mbrtowc_cache[uc] = mbrtowc (&wc, &c, 1, &s) <= 1 ? wc : WEOF;
+    }
+#endif
+}
+
+#if MBS_SUPPORT
+/* Store into *PWC the result of converting the leading bytes of the
+   multibyte buffer S of length N bytes, using the mbrtowc_cache in *D
+   and updating the conversion state in *D.  On conversion error,
+   convert just a single byte, to WEOF.  Return the number of bytes
+   converted.
+
+   This differs from mbrtowc (PWC, S, N, &D->mbs) as follows:
+
+   * PWC points to wint_t, not to wchar_t.
+   * The last arg is a dfa *D instead of merely a multibyte conversion
+     state D->mbs.  D also contains an mbrtowc_cache for speed.
+   * N must be at least 1.
+   * S[N - 1] must be a sentinel byte.
+   * Shift encodings are not supported.
+   * The return value is always in the range 1..N.
+   * D->mbs is always valid afterwards.
+   * *PWC is always set to something.  */
+static size_t
+mbs_to_wchar (wint_t *pwc, char const *s, size_t n, struct dfa *d)
+{
+  unsigned char uc = s[0];
+  wint_t wc = d->mbrtowc_cache[uc];
 
+  if (wc == WEOF)
+    {
+      wchar_t wch;
+      size_t nbytes = mbrtowc (&wch, s, n, &d->mbs);
+      if (0 < nbytes && nbytes < (size_t) -2)
+        {
+          *pwc = wch;
+          return nbytes;
+        }
+      memset (&d->mbs, 0, sizeof d->mbs);
+    }
+
+  *pwc = wc;
+  return 1;
+}
+#else
+#define mbs_to_wchar(pwc, s, n, d) (WEOF)
+#endif
 
 #ifdef DEBUG
 
@@ -588,19 +619,20 @@ prtok (token t)
 static bool
 tstbit (unsigned int b, charclass const c)
 {
-  return c[b / INTBITS] >> b % INTBITS & 1;
+  return c[b / CHARCLASS_WORD_BITS] >> b % CHARCLASS_WORD_BITS & 1;
 }
 
 static void
 setbit (unsigned int b, charclass c)
 {
-  c[b / INTBITS] |= 1U << b % INTBITS;
+  c[b / CHARCLASS_WORD_BITS] |= (charclass_word) 1 << b % CHARCLASS_WORD_BITS;
 }
 
 static void
 clrbit (unsigned int b, charclass c)
 {
-  c[b / INTBITS] &= ~(1U << b % INTBITS);
+  c[b / CHARCLASS_WORD_BITS] &= ~((charclass_word) 1
+                                  << b % CHARCLASS_WORD_BITS);
 }
 
 static void
@@ -620,40 +652,64 @@ notset (charclass s)
 {
   int i;
 
-  for (i = 0; i < CHARCLASS_INTS; ++i)
-    s[i] = ~s[i];
+  for (i = 0; i < CHARCLASS_WORDS; ++i)
+    s[i] = CHARCLASS_WORD_MASK & ~s[i];
 }
 
-static int
+static bool
 equal (charclass const s1, charclass const s2)
 {
   return memcmp (s1, s2, sizeof (charclass)) == 0;
 }
 
-/* A pointer to the current dfa is kept here during parsing.  */
-static struct dfa *dfa;
+/* Ensure that the array addressed by PTR holds at least NITEMS +
+   (PTR || !NITEMS) items.  Either return PTR, or reallocate the array
+   and return its new address.  Although PTR may be null, the returned
+   value is never null.
 
-/* Find the index of charclass s in dfa->charclasses, or allocate a
-   new charclass.  */
+   The array holds *NALLOC items; *NALLOC is updated on reallocation.
+   ITEMSIZE is the size of one item.  Avoid O(N**2) behavior on arrays
+   growing linearly.  */
+static void *
+maybe_realloc (void *ptr, size_t nitems, size_t *nalloc, size_t itemsize)
+{
+  if (nitems < *nalloc)
+    return ptr;
+  *nalloc = nitems;
+  return x2nrealloc (ptr, nalloc, itemsize);
+}
+
+/* In DFA D, find the index of charclass S, or allocate a new one.  */
 static size_t
-charclass_index (charclass const s)
+dfa_charclass_index (struct dfa *d, charclass const s)
 {
   size_t i;
 
-  for (i = 0; i < dfa->cindex; ++i)
-    if (equal (s, dfa->charclasses[i]))
+  for (i = 0; i < d->cindex; ++i)
+    if (equal (s, d->charclasses[i]))
       return i;
-  REALLOC_IF_NECESSARY (dfa->charclasses, dfa->calloc, dfa->cindex + 1);
-  ++dfa->cindex;
-  copyset (s, dfa->charclasses[i]);
+  d->charclasses = maybe_realloc (d->charclasses, d->cindex, &d->calloc,
+                                  sizeof *d->charclasses);
+  ++d->cindex;
+  copyset (s, d->charclasses[i]);
   return i;
 }
 
+/* A pointer to the current dfa is kept here during parsing.  */
+static struct dfa *dfa;
+
+/* Find the index of charclass S in the current DFA, or allocate a new one.  */
+static size_t
+charclass_index (charclass const s)
+{
+  return dfa_charclass_index (dfa, s);
+}
+
 /* Syntax bits controlling the behavior of the lexical analyzer.  */
 static reg_syntax_t syntax_bits, syntax_bits_set;
 
 /* Flag for case-folding letters into sets.  */
-static int case_fold;
+static bool case_fold;
 
 /* End-of-line byte in data.  */
 static unsigned char eolbyte;
@@ -676,14 +732,14 @@ static charclass newline;
 # define is_valid_unibyte_character(c) (! (MBS_SUPPORT && btowc (c) == WEOF))
 #endif
 
-/* Return non-zero if C is a "word-constituent" byte; zero otherwise.  */
+/* C is a "word-constituent" byte.  */
 #define IS_WORD_CONSTITUENT(C) \
   (is_valid_unibyte_character (C) && (isalnum (C) || (C) == '_'))
 
 static int
 char_context (unsigned char c)
 {
-  if (c == eolbyte || c == 0)
+  if (c == eolbyte)
     return CTX_NEWLINE;
   if (IS_WORD_CONSTITUENT (c))
     return CTX_LETTER;
@@ -708,7 +764,7 @@ dfasyntax (reg_syntax_t bits, int fold, unsigned char eol)
 
   syntax_bits_set = 1;
   syntax_bits = bits;
-  case_fold = fold;
+  case_fold = fold != 0;
   eolbyte = eol;
 
   for (i = 0; i < NOTCHAR; ++i)
@@ -731,86 +787,95 @@ dfasyntax (reg_syntax_t bits, int fold, unsigned char eol)
    this may happen when folding case in weird Turkish locales where
    dotless i/dotted I are not included in the chosen character set.
    Return whether a bit was set in the charclass.  */
-#if MBS_SUPPORT
 static bool
 setbit_wc (wint_t wc, charclass c)
 {
+#if MBS_SUPPORT
   int b = wctob (wc);
   if (b == EOF)
     return false;
 
   setbit (b, c);
   return true;
-}
-
-/* Set a bit in the charclass for the given single byte character,
-   if it is valid in the current character set.  */
-static void
-setbit_c (int b, charclass c)
-{
-  /* Do nothing if b is invalid in this character set.  */
-  if (MB_CUR_MAX > 1 && btowc (b) == WEOF)
-    return;
-  setbit (b, c);
-}
 #else
-# define setbit_c setbit
-static inline bool
-setbit_wc (wint_t wc, charclass c)
-{
   abort ();
    /*NOTREACHED*/ return false;
-}
 #endif
+}
 
-/* Like setbit_c, but if case is folded, set both cases of a letter.  For
-   MB_CUR_MAX > 1, the resulting charset is only used as an optimization,
-   and the caller takes care of setting the appropriate field of struct
-   mb_char_classes.  */
+/* Set a bit for B and its case variants in the charclass C.
+   MB_CUR_MAX must be 1.  */
 static void
 setbit_case_fold_c (int b, charclass c)
 {
-  if (MB_CUR_MAX > 1)
-    {
-      wint_t wc = btowc (b);
-      if (wc == WEOF)
-        return;
-      setbit (b, c);
-      if (case_fold && iswalpha (wc))
-        setbit_wc (iswupper (wc) ? towlower (wc) : towupper (wc), c);
-    }
-  else
-    {
-      setbit (b, c);
-      if (case_fold && isalpha (b))
-        setbit_c (isupper (b) ? tolower (b) : toupper (b), c);
-    }
+  int ub = toupper (b);
+  int i;
+  for (i = 0; i < NOTCHAR; i++)
+    if (toupper (i) == ub)
+      setbit (i, c);
 }
 
 
 
 /* UTF-8 encoding allows some optimizations that we can't otherwise
    assume in a multibyte encoding.  */
-static inline int
+int
 using_utf8 (void)
 {
   static int utf8 = -1;
-  if (utf8 == -1)
+  if (utf8 < 0)
     {
-#if defined HAVE_LANGINFO_CODESET && MBS_SUPPORT
-      utf8 = (STREQ (nl_langinfo (CODESET), "UTF-8"));
-#else
-      utf8 = 0;
-#endif
+      wchar_t wc;
+      mbstate_t mbs = { 0 };
+      utf8 = mbrtowc (&wc, "\xc4\x80", 2, &mbs) == 2 && wc == 0x100;
 #ifdef LIBC_IS_BORKED
       if (gawk_mb_cur_max == 1)
          utf8 = 0;
 #endif
     }
-
   return utf8;
 }
 
+/* The current locale is known to be a unibyte locale
+   without multicharacter collating sequences and where range
+   comparisons simply use the native encoding.  These locales can be
+   processed more efficiently.  */
+
+static bool
+using_simple_locale (void)
+{
+  /* The native character set is known to be compatible with
+     the C locale.  The following test isn't perfect, but it's good
+     enough in practice, as only ASCII and EBCDIC are in common use
+     and this test correctly accepts ASCII and rejects EBCDIC.  */
+  enum { native_c_charset =
+    ('\b' == 8 && '\t' == 9 && '\n' == 10 && '\v' == 11 && '\f' == 12
+     && '\r' == 13 && ' ' == 32 && '!' == 33 && '"' == 34 && '#' == 35
+     && '%' == 37 && '&' == 38 && '\'' == 39 && '(' == 40 && ')' == 41
+     && '*' == 42 && '+' == 43 && ',' == 44 && '-' == 45 && '.' == 46
+     && '/' == 47 && '0' == 48 && '9' == 57 && ':' == 58 && ';' == 59
+     && '<' == 60 && '=' == 61 && '>' == 62 && '?' == 63 && 'A' == 65
+     && 'Z' == 90 && '[' == 91 && '\\' == 92 && ']' == 93 && '^' == 94
+     && '_' == 95 && 'a' == 97 && 'z' == 122 && '{' == 123 && '|' == 124
+     && '}' == 125 && '~' == 126)
+  };
+
+  if (! native_c_charset || dfa->multibyte)
+    return false;
+  else
+    {
+      static int unibyte_c = -1;
+      if (unibyte_c < 0)
+        {
+          char const *locale = setlocale (LC_ALL, NULL);
+          unibyte_c = (!locale
+                       || STREQ (locale, "C")
+                       || STREQ (locale, "POSIX"));
+        }
+      return unibyte_c;
+    }
+}
+
 /* Lexical analyzer.  All the dross that deals with the obnoxious
    GNU Regex syntax bits is located here.  The poor, suffering
    reader is referred to the GNU Regex documentation for the
@@ -819,39 +884,28 @@ using_utf8 (void)
 static char const *lexptr;      /* Pointer to next input character.  */
 static size_t lexleft;          /* Number of characters remaining.  */
 static token lasttok;           /* Previous token returned; initially END.  */
-static int laststart;           /* True if we're separated from beginning or (,
+static bool laststart;		/* We're separated from beginning or (,
                                    | only by zero-width characters.  */
 static size_t parens;           /* Count of outstanding left parens.  */
 static int minrep, maxrep;      /* Repeat counts for {m,n}.  */
 
 static int cur_mb_len = 1;      /* Length of the multibyte representation of
                                    wctok.  */
-/* These variables are used only if (MB_CUR_MAX > 1).  */
-static mbstate_t mbs;           /* Mbstate for mbrlen.  */
-static wchar_t wctok;           /* Wide character representation of the current
-                                   multibyte character.  */
-static unsigned char *mblen_buf;/* Correspond to the input buffer in dfaexec.
-                                   Each element stores the number of remaining
-                                   bytes of the corresponding multibyte
-                                   character in the input string.  A element's
-                                   value is 0 if the corresponding character is
-                                   single-byte.
-                                   e.g., input : 'a', <mb(0)>, <mb(1)>, <mb(2)>
-                                   mblen_buf   :  0,       3,       2,       1
-                                 */
-static wchar_t *inputwcs;       /* Wide character representation of the input
-                                   string in dfaexec.
-                                   The length of this array is the same as
-                                   the length of input string (char array).
-                                   inputstring[i] is a single-byte char,
-                                   or the first byte of a multibyte char;
-                                   inputwcs[i] is the codepoint.  */
-static unsigned char const *buf_begin;  /* reference to begin in dfaexec.  */
-static unsigned char const *buf_end;    /* reference to end in dfaexec.  */
+
+static wint_t wctok;		/* Wide character representation of the current
+                                   multibyte character, or WEOF if there was
+                                   an encoding error.  Used only if
+                                   MB_CUR_MAX > 1.  */
 
 
 #if MBS_SUPPORT
-/* Note that characters become unsigned here.  */
+/* Fetch the next lexical input character.  Set C (of type int) to the
+   next input byte, except set C to EOF if the input is a multibyte
+   character of length greater than 1.  Set WC (of type wint_t) to the
+   value of the input if it is a valid multibyte character (possibly
+   of length 1); otherwise set WC to WEOF.  If there is no more input,
+   report EOFERR if EOFERR is not null, and return lasttok = END
+   otherwise.  */
 # define FETCH_WC(c, wc, eoferr)		\
   do {						\
     if (! lexleft)				\
@@ -863,33 +917,19 @@ static unsigned char const *buf_end;    /* reference to end in dfaexec.  */
       }						\
     else					\
       {						\
-        wchar_t _wc;				\
-        cur_mb_len = mbrtowc (&_wc, lexptr, lexleft, &mbs); \
-        if (cur_mb_len <= 0)			\
-          {					\
-            cur_mb_len = 1;			\
-            --lexleft;				\
-            (wc) = (c) = to_uchar (*lexptr++);  \
-          }					\
-        else					\
-          {					\
-            lexptr += cur_mb_len;		\
-            lexleft -= cur_mb_len;		\
-            (wc) = _wc;				\
-            (c) = wctob (wc);			\
-          }					\
+        wint_t _wc;				\
+        size_t nbytes = mbs_to_wchar (&_wc, lexptr, lexleft, dfa); \
+        cur_mb_len = nbytes;			\
+        (wc) = _wc;				\
+        (c) = nbytes == 1 ? to_uchar (*lexptr) : EOF;    \
+        lexptr += nbytes;			\
+        lexleft -= nbytes;			\
       }						\
   } while (0)
 
-# define FETCH(c, eoferr)			\
-  do {						\
-    wint_t wc;					\
-    FETCH_WC (c, wc, eoferr);			\
-  } while (0)
-
 #else
 /* Note that characters become unsigned here.  */
-# define FETCH(c, eoferr)	      \
+# define FETCH_WC(c, unused, eoferr)  \
   do {				      \
     if (! lexleft)		      \
       {				      \
@@ -902,14 +942,59 @@ static unsigned char const *buf_end;    /* reference to end in dfaexec.  */
     --lexleft;			      \
   } while (0)
 
-# define FETCH_WC(c, unused, eoferr) FETCH (c, eoferr)
-
 #endif /* MBS_SUPPORT */
 
 #ifndef MIN
 # define MIN(a,b) ((a) < (b) ? (a) : (b))
 #endif
 
+/* The set of wchar_t values C such that there's a useful locale
+   somewhere where C != towupper (C) && C != towlower (towupper (C)).
+   For example, 0x00B5 (U+00B5 MICRO SIGN) is in this table, because
+   towupper (0x00B5) == 0x039C (U+039C GREEK CAPITAL LETTER MU), and
+   towlower (0x039C) == 0x03BC (U+03BC GREEK SMALL LETTER MU).  */
+static short const lonesome_lower[] =
+  {
+    0x00B5, 0x0131, 0x017F, 0x01C5, 0x01C8, 0x01CB, 0x01F2, 0x0345,
+    0x03C2, 0x03D0, 0x03D1, 0x03D5, 0x03D6, 0x03F0, 0x03F1,
+
+    /* U+03F2 GREEK LUNATE SIGMA SYMBOL lacks a specific uppercase
+       counterpart in locales predating Unicode 4.0.0 (April 2003).  */
+    0x03F2,
+
+    0x03F5, 0x1E9B, 0x1FBE,
+  };
+
+/* Maximum number of characters that can be the case-folded
+   counterparts of a single character, not counting the character
+   itself.  This is 1 for towupper, 1 for towlower, and 1 for each
+   entry in LONESOME_LOWER.  */
+enum
+{ CASE_FOLDED_BUFSIZE = 2 + sizeof lonesome_lower / sizeof *lonesome_lower };
+
+/* Find the characters equal to C after case-folding, other than C
+   itself, and store them into FOLDED.  Return the number of characters
+   stored.  */
+static int
+case_folded_counterparts (wchar_t c, wchar_t folded[CASE_FOLDED_BUFSIZE])
+{
+  int i;
+  int n = 0;
+  wint_t uc = towupper (c);
+  wint_t lc = towlower (uc);
+  if (uc != c)
+    folded[n++] = uc;
+  if (lc != uc && lc != c && towupper (lc) == uc)
+    folded[n++] = lc;
+  for (i = 0; i < sizeof lonesome_lower / sizeof *lonesome_lower; i++)
+    {
+      wint_t li = lonesome_lower[i];
+      if (li != lc && li != uc && li != c && towupper (li) == uc)
+        folded[n++] = li;
+    }
+  return n;
+}
+
 typedef int predicate (int);
 
 /* The following list maps the names of the Posix named character classes
@@ -928,7 +1013,7 @@ static const struct dfa_ctype prednames[] = {
   {"upper", isupper, false},
   {"lower", islower, false},
   {"digit", isdigit, true},
-  {"xdigit", isxdigit, true},
+  {"xdigit", isxdigit, false},
   {"space", isspace, false},
   {"punct", ispunct, false},
   {"alnum", isalnum, false},
@@ -955,10 +1040,14 @@ find_pred (const char *str)
 static token
 parse_bracket_exp (void)
 {
-  int invert;
+  bool invert;
   int c, c1, c2;
   charclass ccl;
 
+  /* This is a bracket expression that dfaexec is known to
+     process correctly.  */
+  bool known_bracket_exp = true;
+
   /* Used to warn about [:space:].
      Bit 0 = first character is a colon.
      Bit 1 = last character is a colon.
@@ -972,16 +1061,14 @@ parse_bracket_exp (void)
 
   /* Work area to build a mb_char_classes.  */
   struct mb_char_classes *work_mbc;
-  size_t chars_al, range_sts_al, range_ends_al, ch_classes_al,
-    equivs_al, coll_elems_al;
+  size_t chars_al, ranges_al, ch_classes_al, equivs_al, coll_elems_al;
 
-  chars_al = 0;
-  range_sts_al = range_ends_al = 0;
-  ch_classes_al = equivs_al = coll_elems_al = 0;
-  if (MB_CUR_MAX > 1)
+  chars_al = ranges_al = ch_classes_al = equivs_al = coll_elems_al = 0;
+  if (dfa->multibyte)
     {
-      REALLOC_IF_NECESSARY (dfa->mbcsets, dfa->mbcsets_alloc,
-                            dfa->nmbcsets + 1);
+      dfa->mbcsets = maybe_realloc (dfa->mbcsets, dfa->nmbcsets,
+                                    &dfa->mbcsets_alloc,
+                                    sizeof *dfa->mbcsets);
 
       /* dfa->multibyte_prop[] hold the index of dfa->mbcsets.
          We will update dfa->multibyte_prop[] in addtok, because we can't
@@ -999,32 +1086,31 @@ parse_bracket_exp (void)
   if (c == '^')
     {
       FETCH_WC (c, wc, _("unbalanced ["));
-      invert = 1;
+      invert = true;
+      known_bracket_exp = using_simple_locale ();
     }
   else
-    invert = 0;
+    invert = false;
 
   colon_warning_state = (c == ':');
   do
     {
-      c1 = EOF;                 /* mark c1 is not initialized".  */
+      c1 = NOTCHAR;	/* Mark c1 as not initialized.  */
       colon_warning_state &= ~2;
 
       /* Note that if we're looking at some other [:...:] construct,
          we just treat it as a bunch of ordinary characters.  We can do
          this because we assume regex has checked for syntax errors before
          dfa is ever called.  */
-      if (c == '[' && (syntax_bits & RE_CHAR_CLASSES))
+      if (c == '[')
         {
-#define MAX_BRACKET_STRING_LEN 32
-          char str[MAX_BRACKET_STRING_LEN + 1];
           FETCH_WC (c1, wc1, _("unbalanced ["));
 
-          /* If pattern contains '[[:', '[[.', or '[[='.  */
-          if (c1 == ':'
-              /* TODO: handle '[[.' and '[[=' also for MB_CUR_MAX == 1.  */
-              || (MB_CUR_MAX > 1 && (c1 == '.' || c1 == '=')))
+          if ((c1 == ':' && (syntax_bits & RE_CHAR_CLASSES))
+              || c1 == '.' || c1 == '=')
             {
+              enum { MAX_BRACKET_STRING_LEN = 32 };
+              char str[MAX_BRACKET_STRING_LEN + 1];
               size_t len = 0;
               for (;;)
                 {
@@ -1042,7 +1128,10 @@ parse_bracket_exp (void)
               /* Fetch bracket.  */
               FETCH_WC (c, wc, _("unbalanced ["));
               if (c1 == ':')
-                /* build character class.  */
+                /* Build character class.  POSIX allows character
+                   classes to match multicharacter collating elements,
+                   but the regex code does not support that, so do not
+                   worry about that possibility.  */
                 {
                   char const *class
                     = (case_fold && (STREQ (str, "upper")
@@ -1051,43 +1140,25 @@ parse_bracket_exp (void)
                   if (!pred)
                     dfaerror (_("invalid character class"));
 
-                  if (MB_CUR_MAX > 1 && !pred->single_byte_only)
+                  if (dfa->multibyte && !pred->single_byte_only)
                     {
                       /* Store the character class as wctype_t.  */
                       wctype_t wt = (wctype_t) wctype (class);
 
-                      REALLOC_IF_NECESSARY (work_mbc->ch_classes,
-                                            ch_classes_al,
-                                            work_mbc->nch_classes + 1);
+                      work_mbc->ch_classes
+                        = maybe_realloc (work_mbc->ch_classes,
+                                         work_mbc->nch_classes, &ch_classes_al,
+                                         sizeof *work_mbc->ch_classes);
                       work_mbc->ch_classes[work_mbc->nch_classes++] = wt;
                     }
 
                   for (c2 = 0; c2 < NOTCHAR; ++c2)
                     if (pred->func (c2))
-                      setbit_case_fold_c (c2, ccl);
+                      setbit (c2, ccl);
                 }
+              else
+                known_bracket_exp = false;
 
-              else if (MBS_SUPPORT && (c1 == '=' || c1 == '.'))
-                {
-                  char *elem = xmemdup (str, len + 1);
-
-                  if (c1 == '=')
-                    /* build equivalence class.  */
-                    {
-                      REALLOC_IF_NECESSARY (work_mbc->equivs,
-                                            equivs_al, work_mbc->nequivs + 1);
-                      work_mbc->equivs[work_mbc->nequivs++] = elem;
-                    }
-
-                  if (c1 == '.')
-                    /* build collating element.  */
-                    {
-                      REALLOC_IF_NECESSARY (work_mbc->coll_elems,
-                                            coll_elems_al,
-                                            work_mbc->ncoll_elems + 1);
-                      work_mbc->coll_elems[work_mbc->ncoll_elems++] = elem;
-                    }
-                }
               colon_warning_state |= 8;
 
               /* Fetch new lookahead character.  */
@@ -1102,124 +1173,110 @@ parse_bracket_exp (void)
       if (c == '\\' && (syntax_bits & RE_BACKSLASH_ESCAPE_IN_LISTS))
         FETCH_WC (c, wc, _("unbalanced ["));
 
-      if (c1 == EOF)
+      if (c1 == NOTCHAR)
         FETCH_WC (c1, wc1, _("unbalanced ["));
 
       if (c1 == '-')
         /* build range characters.  */
         {
           FETCH_WC (c2, wc2, _("unbalanced ["));
-          if (c2 == ']')
-            {
-              /* In the case [x-], the - is an ordinary hyphen,
-                 which is left in c1, the lookahead character.  */
-              lexptr -= cur_mb_len;
-              lexleft += cur_mb_len;
-            }
-        }
 
-      if (c1 == '-' && c2 != ']')
-        {
-          if (c2 == '\\' && (syntax_bits & RE_BACKSLASH_ESCAPE_IN_LISTS))
-            FETCH_WC (c2, wc2, _("unbalanced ["));
-
-          if (MB_CUR_MAX > 1)
+          /* A bracket expression like [a-[.aa.]] matches an unknown set.
+             Treat it like [-a[.aa.]] while parsing it, and
+             remember that the set is unknown.  */
+          if (c2 == '[' && *lexptr == '.')
             {
-              /* When case folding map a range, say [m-z] (or even [M-z])
-                 to the pair of ranges, [m-z] [M-Z].  */
-              REALLOC_IF_NECESSARY (work_mbc->range_sts,
-                                    range_sts_al, work_mbc->nranges + 1);
-              REALLOC_IF_NECESSARY (work_mbc->range_ends,
-                                    range_ends_al, work_mbc->nranges + 1);
-              work_mbc->range_sts[work_mbc->nranges] =
-                case_fold ? towlower (wc) : (wchar_t) wc;
-              work_mbc->range_ends[work_mbc->nranges++] =
-                case_fold ? towlower (wc2) : (wchar_t) wc2;
-
-#ifndef GREP
-              if (case_fold && (iswalpha (wc) || iswalpha (wc2)))
-                {
-                  REALLOC_IF_NECESSARY (work_mbc->range_sts,
-                                        range_sts_al, work_mbc->nranges + 1);
-                  work_mbc->range_sts[work_mbc->nranges] = towupper (wc);
-                  REALLOC_IF_NECESSARY (work_mbc->range_ends,
-                                        range_ends_al, work_mbc->nranges + 1);
-                  work_mbc->range_ends[work_mbc->nranges++] = towupper (wc2);
-                }
-#endif
+              known_bracket_exp = false;
+              c2 = ']';
             }
-          else
+
+          if (c2 != ']')
             {
-#ifndef GAWK
-              /* Defer to the system regex library about the meaning
-                 of range expressions.  */
-              regex_t re;
-              char pattern[6] = { '[', 0, '-', 0, ']', 0 };
-              char subject[2] = { 0, 0 };
-              c1 = c;
-              if (case_fold)
-                {
-                  c1 = tolower (c1);
-                  c2 = tolower (c2);
-                }
+              if (c2 == '\\' && (syntax_bits & RE_BACKSLASH_ESCAPE_IN_LISTS))
+                FETCH_WC (c2, wc2, _("unbalanced ["));
 
-              pattern[1] = c1;
-              pattern[3] = c2;
-              regcomp (&re, pattern, REG_NOSUB);
-              for (c = 0; c < NOTCHAR; ++c)
+              if (dfa->multibyte)
                 {
-                  if ((case_fold && isupper (c)))
-                    continue;
-                  subject[0] = c;
-                  if (regexec (&re, subject, 0, NULL, 0) != REG_NOMATCH)
-                    setbit_case_fold_c (c, ccl);
+                  /* When case folding map a range, say [m-z] (or even [M-z])
+                     to the pair of ranges, [m-z] [M-Z].  Although this code
+                     is wrong in multiple ways, it's never used in practice.
+                     FIXME: Remove this (and related) unused code.  */
+                  if (wc != WEOF && wc2 != WEOF)
+                    {
+                      work_mbc->ranges
+                        = maybe_realloc (work_mbc->ranges, work_mbc->nranges + 2,
+                                         &ranges_al, sizeof *work_mbc->ranges);
+                      work_mbc->ranges[work_mbc->nranges].beg
+                        = case_fold ? towlower (wc) : wc;
+                      work_mbc->ranges[work_mbc->nranges++].end
+                        = case_fold ? towlower (wc2) : wc2;
+
+                      if (case_fold && (iswalpha (wc) || iswalpha (wc2)))
+                        {
+                          work_mbc->ranges[work_mbc->nranges].beg = towupper (wc);
+                          work_mbc->ranges[work_mbc->nranges++].end
+                            = towupper (wc2);
+                        }
+                    }
                 }
-              regfree (&re);
-#else
-              c1 = c;
-              if (case_fold)
+              else if (using_simple_locale ())
                 {
-                  c1 = tolower (c1);
-                  c2 = tolower (c2);
+                  for (c1 = c; c1 <= c2; c1++)
+                    setbit (c1, ccl);
+                  if (case_fold)
+                    {
+                      int uc = toupper (c);
+                      int uc2 = toupper (c2);
+                      for (c1 = 0; c1 < NOTCHAR; c1++)
+                        {
+                          int uc1 = toupper (c1);
+                          if (uc <= uc1 && uc1 <= uc2)
+                            setbit (c1, ccl);
+                        }
+                    }
                 }
-              for (c = c1; c <= c2; c++)
-                setbit_case_fold_c (c, ccl);
-#endif
+              else
+                known_bracket_exp = false;
+
+              colon_warning_state |= 8;
+              FETCH_WC (c1, wc1, _("unbalanced ["));
+              continue;
             }
 
-          colon_warning_state |= 8;
-          FETCH_WC (c1, wc1, _("unbalanced ["));
-          continue;
+          /* In the case [x-], the - is an ordinary hyphen,
+             which is left in c1, the lookahead character.  */
+          lexptr -= cur_mb_len;
+          lexleft += cur_mb_len;
         }
 
       colon_warning_state |= (c == ':') ? 2 : 4;
 
-      if (MB_CUR_MAX == 1)
+      if (!dfa->multibyte)
         {
-          setbit_case_fold_c (c, ccl);
+          if (case_fold)
+            setbit_case_fold_c (c, ccl);
+          else
+            setbit (c, ccl);
           continue;
         }
 
-      if (case_fold && iswalpha (wc))
-        {
-          wc = towlower (wc);
-          if (!setbit_wc (wc, ccl))
-            {
-              REALLOC_IF_NECESSARY (work_mbc->chars, chars_al,
-                                    work_mbc->nchars + 1);
-              work_mbc->chars[work_mbc->nchars++] = wc;
-            }
-#ifdef GREP
-          continue;
-#else
-          wc = towupper (wc);
-#endif
-        }
-      if (!setbit_wc (wc, ccl))
+      if (wc == WEOF)
+        known_bracket_exp = false;
+      else
         {
-          REALLOC_IF_NECESSARY (work_mbc->chars, chars_al,
-                                work_mbc->nchars + 1);
-          work_mbc->chars[work_mbc->nchars++] = wc;
+          wchar_t folded[CASE_FOLDED_BUFSIZE + 1];
+          int i;
+          int n = (case_fold ? case_folded_counterparts (wc, folded + 1) + 1
+                   : 1);
+          folded[0] = wc;
+          for (i = 0; i < n; i++)
+            if (!setbit_wc (folded[i], ccl))
+              {
+                work_mbc->chars
+                  = maybe_realloc (work_mbc->chars, work_mbc->nchars,
+                                   &chars_al, sizeof *work_mbc->chars);
+                work_mbc->chars[work_mbc->nchars++] = folded[i];
+              }
         }
     }
   while ((wc = wc1, (c = c1) != ']'));
@@ -1227,7 +1284,10 @@ parse_bracket_exp (void)
   if (colon_warning_state == 7)
     dfawarn (_("character class syntax is [[:space:]], not [:space:]"));
 
-  if (MB_CUR_MAX > 1)
+  if (! known_bracket_exp)
+    return BACKREF;
+
+  if (dfa->multibyte)
     {
       static charclass zeroclass;
       work_mbc->invert = invert;
@@ -1237,7 +1297,7 @@ parse_bracket_exp (void)
 
   if (invert)
     {
-      assert (MB_CUR_MAX == 1);
+      assert (!dfa->multibyte);
       notset (ccl);
       if (syntax_bits & RE_HAT_LISTS_NOT_NEWLINE)
         clrbit (eolbyte, ccl);
@@ -1249,8 +1309,8 @@ parse_bracket_exp (void)
 static token
 lex (void)
 {
-  unsigned int c, c2;
-  int backslash = 0;
+  int c, c2;
+  bool backslash = false;
   charclass ccl;
   int i;
 
@@ -1262,14 +1322,7 @@ lex (void)
      "if (backslash) ...".  */
   for (i = 0; i < 2; ++i)
     {
-      if (MB_CUR_MAX > 1)
-        {
-          FETCH_WC (c, wctok, NULL);
-          if ((int) c == EOF)
-            goto normal_char;
-        }
-      else
-        FETCH (c, NULL);
+      FETCH_WC (c, wctok, NULL);
 
       switch (c)
         {
@@ -1278,7 +1331,7 @@ lex (void)
             goto normal_char;
           if (lexleft == 0)
             dfaerror (_("unfinished \\ escape"));
-          backslash = 1;
+          backslash = true;
           break;
 
         case '^':
@@ -1316,7 +1369,7 @@ lex (void)
         case '9':
           if (backslash && !(syntax_bits & RE_NO_BK_REFS))
             {
-              laststart = 0;
+              laststart = false;
               return lasttok = BACKREF;
             }
           goto normal_char;
@@ -1424,14 +1477,14 @@ lex (void)
               {
                 if (syntax_bits & RE_INVALID_INTERVAL_ORD)
                   goto normal_char;
-                dfaerror (_("Invalid content of \\{\\}"));
+                dfaerror (_("invalid content of \\{\\}"));
               }
             if (RE_DUP_MAX < maxrep)
-              dfaerror (_("Regular expression too big"));
+              dfaerror (_("regular expression too big"));
             lexptr = p;
             lexleft = lim - p;
           }
-          laststart = 0;
+          laststart = false;
           return lasttok = REPMN;
 
         case '|':
@@ -1439,21 +1492,21 @@ lex (void)
             goto normal_char;
           if (backslash != ((syntax_bits & RE_NO_BK_VBAR) == 0))
             goto normal_char;
-          laststart = 1;
+          laststart = true;
           return lasttok = OR;
 
         case '\n':
           if (syntax_bits & RE_LIMITED_OPS
               || backslash || !(syntax_bits & RE_NEWLINE_ALT))
             goto normal_char;
-          laststart = 1;
+          laststart = true;
           return lasttok = OR;
 
         case '(':
           if (backslash != ((syntax_bits & RE_NO_BK_PARENS) == 0))
             goto normal_char;
           ++parens;
-          laststart = 1;
+          laststart = true;
           return lasttok = LPAREN;
 
         case ')':
@@ -1462,17 +1515,17 @@ lex (void)
           if (parens == 0 && syntax_bits & RE_UNMATCHED_RIGHT_PAREN_ORD)
             goto normal_char;
           --parens;
-          laststart = 0;
+          laststart = false;
           return lasttok = RPAREN;
 
         case '.':
           if (backslash)
             goto normal_char;
-          if (MB_CUR_MAX > 1)
+          if (dfa->multibyte)
             {
               /* In multibyte environment period must match with a single
                  character not a byte.  So we use ANYCHAR.  */
-              laststart = 0;
+              laststart = false;
               return lasttok = ANYCHAR;
             }
           zeroset (ccl);
@@ -1481,14 +1534,14 @@ lex (void)
             clrbit (eolbyte, ccl);
           if (syntax_bits & RE_DOT_NOT_NULL)
             clrbit ('\0', ccl);
-          laststart = 0;
+          laststart = false;
           return lasttok = CSET + charclass_index (ccl);
 
         case 's':
         case 'S':
           if (!backslash || (syntax_bits & RE_NO_GNU_OPS))
             goto normal_char;
-          if (MB_CUR_MAX == 1)
+          if (!dfa->multibyte)
             {
               zeroset (ccl);
               for (c2 = 0; c2 < NOTCHAR; ++c2)
@@ -1496,7 +1549,7 @@ lex (void)
                   setbit (c2, ccl);
               if (c == 'S')
                 notset (ccl);
-              laststart = 0;
+              laststart = false;
               return lasttok = CSET + charclass_index (ccl);
             }
 
@@ -1526,7 +1579,7 @@ lex (void)
 
           POP_LEX_STATE ();
 
-          laststart = 0;
+          laststart = false;
           return lasttok;
 
         case 'w':
@@ -1539,21 +1592,21 @@ lex (void)
               setbit (c2, ccl);
           if (c == 'W')
             notset (ccl);
-          laststart = 0;
+          laststart = false;
           return lasttok = CSET + charclass_index (ccl);
 
         case '[':
           if (backslash)
             goto normal_char;
-          laststart = 0;
+          laststart = false;
           return lasttok = parse_bracket_exp ();
 
         default:
         normal_char:
-          laststart = 0;
+          laststart = false;
           /* For multibyte character sets, folding is done in atom.  Always
              return WCHAR.  */
-          if (MB_CUR_MAX > 1)
+          if (dfa->multibyte)
             return lasttok = WCHAR;
 
           if (case_fold && isalpha (c))
@@ -1585,14 +1638,16 @@ static size_t depth;            /* Current depth of a hypothetical stack
 static void
 addtok_mb (token t, int mbprop)
 {
-  if (MB_CUR_MAX > 1)
+  if (dfa->talloc == dfa->tindex)
     {
-      REALLOC_IF_NECESSARY (dfa->multibyte_prop, dfa->nmultibyte_prop,
-                            dfa->tindex + 1);
-      dfa->multibyte_prop[dfa->tindex] = mbprop;
+      dfa->tokens = x2nrealloc (dfa->tokens, &dfa->talloc,
+                                sizeof *dfa->tokens);
+      if (dfa->multibyte)
+        dfa->multibyte_prop = xnrealloc (dfa->multibyte_prop, dfa->talloc,
+                                         sizeof *dfa->multibyte_prop);
     }
-
-  REALLOC_IF_NECESSARY (dfa->tokens, dfa->talloc, dfa->tindex + 1);
+  if (dfa->multibyte)
+    dfa->multibyte_prop[dfa->tindex] = mbprop;
   dfa->tokens[dfa->tindex++] = t;
 
   switch (t)
@@ -1607,8 +1662,12 @@ addtok_mb (token t, int mbprop)
       --depth;
       break;
 
+    case BACKREF:
+      dfa->fast = false;
+      /* fallthrough */
     default:
       ++dfa->nleaves;
+      /* fallthrough */
     case EMPTY:
       ++depth;
       break;
@@ -1624,7 +1683,7 @@ static void addtok_wc (wint_t wc);
 static void
 addtok (token t)
 {
-  if (MB_CUR_MAX > 1 && t == MBCSET)
+  if (dfa->multibyte && t == MBCSET)
     {
       bool need_or = false;
       struct mb_char_classes *work_mbc = &dfa->mbcsets[dfa->nmbcsets - 1];
@@ -1644,10 +1703,11 @@ addtok (token t)
           work_mbc->nchars = 0;
         }
 
-      /* UTF-8 allows treating a simple, non-inverted MBCSET like a CSET.  */
+      /* If the MBCSET is non-inverted and doesn't include neither
+         character classes including multibyte characters, range
+         expressions, equivalence classes nor collating elements,
+         it can be replaced to a simple CSET. */
       if (work_mbc->invert
-          || (!using_utf8 () && work_mbc->cset != -1)
-          || work_mbc->nchars != 0
           || work_mbc->nch_classes != 0
           || work_mbc->nranges != 0
           || work_mbc->nequivs != 0 || work_mbc->ncoll_elems != 0)
@@ -1662,7 +1722,6 @@ addtok (token t)
              that the mbcset is empty now.  Do nothing in that case.  */
           if (work_mbc->cset != -1)
             {
-              assert (using_utf8 ());
               addtok (CSET + work_mbc->cset);
               if (need_or)
                 addtok (OR);
@@ -1686,16 +1745,19 @@ static void
 addtok_wc (wint_t wc)
 {
   unsigned char buf[MB_LEN_MAX];
-  mbstate_t s;
+  mbstate_t s = { 0 };
   int i;
-  memset (&s, 0, sizeof s);
-  cur_mb_len = wcrtomb ((char *) buf, wc, &s);
+  size_t stored_bytes = wcrtomb ((char *) buf, wc, &s);
 
-  /* This is merely stop-gap.  When cur_mb_len is 0 or negative,
-     buf[0] is undefined, yet skipping the addtok_mb call altogether
-     can result in heap corruption.  */
-  if (cur_mb_len <= 0)
-    buf[0] = 0;
+  if (stored_bytes != (size_t) -1)
+    cur_mb_len = stored_bytes;
+  else
+    {
+      /* This is merely stop-gap.  buf[0] is undefined, yet skipping
+         the addtok_mb call altogether can corrupt the heap.  */
+      cur_mb_len = 1;
+      buf[0] = 0;
+    }
 
   addtok_mb (buf[0], cur_mb_len == 1 ? 3 : 1);
   for (i = 1; i < cur_mb_len; i++)
@@ -1716,11 +1778,21 @@ add_utf8_anychar (void)
 {
 #if MBS_SUPPORT
   static const charclass utf8_classes[5] = {
-    {0, 0, 0, 0, ~0, ~0, 0, 0},		/* 80-bf: non-leading bytes */
-    {~0, ~0, ~0, ~0, 0, 0, 0, 0},       /* 00-7f: 1-byte sequence */
-    {0, 0, 0, 0, 0, 0, ~3, 0},          /* c2-df: 2-byte sequence */
-    {0, 0, 0, 0, 0, 0, 0, 0xffff},      /* e0-ef: 3-byte sequence */
-    {0, 0, 0, 0, 0, 0, 0, 0xff0000}     /* f0-f7: 4-byte sequence */
+    /* 80-bf: non-leading bytes.  */
+    {0, 0, 0, 0, CHARCLASS_WORD_MASK, CHARCLASS_WORD_MASK, 0, 0},
+
+    /* 00-7f: 1-byte sequence.  */
+    {CHARCLASS_WORD_MASK, CHARCLASS_WORD_MASK, CHARCLASS_WORD_MASK,
+     CHARCLASS_WORD_MASK, 0, 0, 0, 0},
+
+    /* c2-df: 2-byte sequence.  */
+    {0, 0, 0, 0, 0, 0, ~3 & CHARCLASS_WORD_MASK, 0},
+
+    /* e0-ef: 3-byte sequence.  */
+    {0, 0, 0, 0, 0, 0, 0, 0xffff},
+
+    /* f0-f7: 4-byte sequence.  */
+    {0, 0, 0, 0, 0, 0, 0, 0xff0000}
   };
   const unsigned int n = sizeof (utf8_classes) / sizeof (utf8_classes[0]);
   unsigned int i;
@@ -1800,20 +1872,25 @@ add_utf8_anychar (void)
 static void
 atom (void)
 {
-  if (0)
-    {
-      /* empty */
-    }
-  else if (MBS_SUPPORT && tok == WCHAR)
+  if (MBS_SUPPORT && tok == WCHAR)
     {
-      addtok_wc (case_fold ? towlower (wctok) : wctok);
-#ifndef GREP
-      if (case_fold && iswalpha (wctok))
+      if (wctok == WEOF)
+        addtok (BACKREF);
+      else
         {
-          addtok_wc (towupper (wctok));
-          addtok (OR);
+          addtok_wc (wctok);
+
+          if (case_fold)
+            {
+              wchar_t folded[CASE_FOLDED_BUFSIZE];
+              int i, n = case_folded_counterparts (wctok, folded);
+              for (i = 0; i < n; i++)
+                {
+                  addtok_wc (folded[i]);
+                  addtok (OR);
+                }
+            }
         }
-#endif
 
       tok = lex ();
     }
@@ -1878,7 +1955,7 @@ copytoks (size_t tindex, size_t ntokens)
 {
   size_t i;
 
-  if (MB_CUR_MAX > 1)
+  if (dfa->multibyte)
     for (i = 0; i < ntokens; ++i)
       addtok_mb (dfa->tokens[tindex + i], dfa->multibyte_prop[tindex + i]);
   else
@@ -1961,12 +2038,12 @@ dfaparse (char const *s, size_t len, struct dfa *d)
   lexptr = s;
   lexleft = len;
   lasttok = END;
-  laststart = 1;
+  laststart = true;
   parens = 0;
-  if (MB_CUR_MAX > 1)
+  if (dfa->multibyte)
     {
       cur_mb_len = 0;
-      memset (&mbs, 0, sizeof mbs);
+      memset (&d->mbs, 0, sizeof d->mbs);
     }
 
   if (!syntax_bits_set)
@@ -1991,19 +2068,24 @@ dfaparse (char const *s, size_t len, struct dfa *d)
 
 /* Some primitives for operating on sets of positions.  */
 
-/* Copy one set to another; the destination must be large enough.  */
+/* Copy one set to another.  */
 static void
 copy (position_set const *src, position_set * dst)
 {
-  REALLOC_IF_NECESSARY (dst->elems, dst->alloc, src->nelem);
-  memcpy (dst->elems, src->elems, sizeof (dst->elems[0]) * src->nelem);
+  if (dst->alloc < src->nelem)
+    {
+      free (dst->elems);
+      dst->alloc = src->nelem;
+      dst->elems = x2nrealloc (NULL, &dst->alloc, sizeof *dst->elems);
+    }
+  memcpy (dst->elems, src->elems, src->nelem * sizeof *dst->elems);
   dst->nelem = src->nelem;
 }
 
 static void
 alloc_position_set (position_set * s, size_t size)
 {
-  MALLOC (s->elems, size);
+  s->elems = xnmalloc (size, sizeof *s->elems);
   s->alloc = size;
   s->nelem = 0;
 }
@@ -2033,7 +2115,7 @@ insert (position p, position_set * s)
       return;
     }
 
-  REALLOC_IF_NECESSARY (s->elems, s->alloc, count + 1);
+  s->elems = maybe_realloc (s->elems, count, &s->alloc, sizeof *s->elems);
   for (i = count; i > lo; i--)
     s->elems[i] = s->elems[i - 1];
   s->elems[lo] = p;
@@ -2047,7 +2129,12 @@ merge (position_set const *s1, position_set const *s2, position_set * m)
 {
   size_t i = 0, j = 0;
 
-  REALLOC_IF_NECESSARY (m->elems, m->alloc, s1->nelem + s2->nelem);
+  if (m->alloc < s1->nelem + s2->nelem)
+    {
+      free (m->elems);
+      m->elems = maybe_realloc (NULL, s1->nelem + s2->nelem, &m->alloc,
+                                sizeof *m->elems);
+    }
   m->nelem = 0;
   while (i < s1->nelem && j < s2->nelem)
     if (s1->elems[i].index > s2->elems[j].index)
@@ -2108,19 +2195,19 @@ state_index (struct dfa *d, position_set const *s, int context)
     }
 
   /* We'll have to create a new state.  */
-  REALLOC_IF_NECESSARY (d->states, d->salloc, d->sindex + 1);
+  d->states = maybe_realloc (d->states, d->sindex, &d->salloc,
+                             sizeof *d->states);
   d->states[i].hash = hash;
   alloc_position_set (&d->states[i].elems, s->nelem);
   copy (s, &d->states[i].elems);
   d->states[i].context = context;
-  d->states[i].backref = 0;
+  d->states[i].has_backref = false;
+  d->states[i].has_mbcset = false;
   d->states[i].constraint = 0;
   d->states[i].first_end = 0;
-  if (MBS_SUPPORT)
-    {
-      d->states[i].mbps.nelem = 0;
-      d->states[i].mbps.elems = NULL;
-    }
+  d->states[i].mbps.nelem = 0;
+  d->states[i].mbps.elems = NULL;
+
   for (j = 0; j < s->nelem; ++j)
     if (d->tokens[s->elems[j].index] < 0)
       {
@@ -2133,7 +2220,7 @@ state_index (struct dfa *d, position_set const *s, int context)
     else if (d->tokens[s->elems[j].index] == BACKREF)
       {
         d->states[i].constraint = NO_CONSTRAINT;
-        d->states[i].backref = 1;
+        d->states[i].has_backref = true;
       }
 
   ++d->sindex;
@@ -2147,13 +2234,11 @@ state_index (struct dfa *d, position_set const *s, int context)
    constraint.  Repeat exhaustively until no funny positions are left.
    S->elems must be large enough to hold the result.  */
 static void
-epsclosure (position_set * s, struct dfa const *d)
+epsclosure (position_set *s, struct dfa const *d, char *visited)
 {
   size_t i, j;
-  char *visited;  /* Array of booleans, enough to use char, not int.  */
   position p, old;
-
-  CALLOC (visited, d->tindex);
+  bool initialized = false;
 
   for (i = 0; i < s->nelem; ++i)
     if (d->tokens[s->elems[i].index] >= NOTCHAR
@@ -2164,6 +2249,11 @@ epsclosure (position_set * s, struct dfa const *d)
 #endif
         && d->tokens[s->elems[i].index] < CSET)
       {
+        if (!initialized)
+          {
+            memset (visited, 0, d->tindex * sizeof (*visited));
+            initialized = true;
+          }
         old = s->elems[i];
         p.constraint = old.constraint;
         delete (s->elems[i], s);
@@ -2204,8 +2294,6 @@ epsclosure (position_set * s, struct dfa const *d)
         /* Force rescan to start at the beginning.  */
         i = -1;
       }
-
-  free (visited);
 }
 
 /* Returns the set of contexts for which there is at least one
@@ -2220,7 +2308,7 @@ charclass_context (charclass c)
   if (tstbit (eolbyte, c))
     context |= CTX_NEWLINE;
 
-  for (j = 0; j < CHARCLASS_INTS; ++j)
+  for (j = 0; j < CHARCLASS_WORDS; ++j)
     {
       if (c[j] & letters[j])
         context |= CTX_LETTER;
@@ -2310,19 +2398,29 @@ state_separate_contexts (position_set const *s)
 void
 dfaanalyze (struct dfa *d, int searchflag)
 {
-  int *nullable;                /* Nullable stack.  */
-  size_t *nfirstpos;            /* Element count stack for firstpos sets.  */
-  position *firstpos;           /* Array where firstpos elements are stored.  */
-  size_t *nlastpos;             /* Element count stack for lastpos sets.  */
-  position *lastpos;            /* Array where lastpos elements are stored.  */
+  /* Array allocated to hold position sets.  */
+  position *posalloc = xnmalloc (d->nleaves, 2 * sizeof *posalloc);
+  /* Firstpos and lastpos elements.  */
+  position *firstpos = posalloc + d->nleaves;
+  position *lastpos = firstpos + d->nleaves;
+
+  /* Stack for element counts and nullable flags.  */
+  struct
+  {
+    /* Whether the entry is nullable.  */
+    bool nullable;
+
+    /* Counts of firstpos and lastpos sets.  */
+    size_t nfirstpos;
+    size_t nlastpos;
+  } *stkalloc = xnmalloc (d->depth, sizeof *stkalloc), *stk = stkalloc;
+
   position_set tmp;             /* Temporary set for merging sets.  */
   position_set merged;          /* Result of merging sets.  */
   int separate_contexts;        /* Context wanted by some position.  */
-  int *o_nullable;
-  size_t *o_nfirst, *o_nlast;
-  position *o_firstpos, *o_lastpos;
   size_t i, j;
   position *pos;
+  char *visited = xnmalloc (d->tindex, sizeof *visited);
 
 #ifdef DEBUG
   fprintf (stderr, "dfaanalyze:\n");
@@ -2334,21 +2432,9 @@ dfaanalyze (struct dfa *d, int searchflag)
   putc ('\n', stderr);
 #endif
 
-  d->searchflag = searchflag;
-
-  MALLOC (nullable, d->depth);
-  o_nullable = nullable;
-  MALLOC (nfirstpos, d->depth);
-  o_nfirst = nfirstpos;
-  MALLOC (firstpos, d->nleaves);
-  o_firstpos = firstpos, firstpos += d->nleaves;
-  MALLOC (nlastpos, d->depth);
-  o_nlast = nlastpos;
-  MALLOC (lastpos, d->nleaves);
-  o_lastpos = lastpos, lastpos += d->nleaves;
+  d->searchflag = searchflag != 0;
   alloc_position_set (&merged, d->nleaves);
-
-  CALLOC (d->follows, d->tindex);
+  d->follows = xcalloc (d->tindex, sizeof *d->follows);
 
   for (i = 0; i < d->tindex; ++i)
     {
@@ -2356,38 +2442,40 @@ dfaanalyze (struct dfa *d, int searchflag)
         {
         case EMPTY:
           /* The empty set is nullable.  */
-          *nullable++ = 1;
+          stk->nullable = true;
 
           /* The firstpos and lastpos of the empty leaf are both empty.  */
-          *nfirstpos++ = *nlastpos++ = 0;
+          stk->nfirstpos = stk->nlastpos = 0;
+          stk++;
           break;
 
         case STAR:
         case PLUS:
           /* Every element in the firstpos of the argument is in the follow
              of every element in the lastpos.  */
-          tmp.nelem = nfirstpos[-1];
+          tmp.nelem = stk[-1].nfirstpos;
           tmp.elems = firstpos;
           pos = lastpos;
-          for (j = 0; j < nlastpos[-1]; ++j)
+          for (j = 0; j < stk[-1].nlastpos; ++j)
             {
               merge (&tmp, &d->follows[pos[j].index], &merged);
               copy (&merged, &d->follows[pos[j].index]);
             }
+          /* fallthrough */
 
         case QMARK:
           /* A QMARK or STAR node is automatically nullable.  */
           if (d->tokens[i] != PLUS)
-            nullable[-1] = 1;
+            stk[-1].nullable = true;
           break;
 
         case CAT:
           /* Every element in the firstpos of the second argument is in the
              follow of every element in the lastpos of the first argument.  */
-          tmp.nelem = nfirstpos[-1];
+          tmp.nelem = stk[-1].nfirstpos;
           tmp.elems = firstpos;
-          pos = lastpos + nlastpos[-1];
-          for (j = 0; j < nlastpos[-2]; ++j)
+          pos = lastpos + stk[-1].nlastpos;
+          for (j = 0; j < stk[-2].nlastpos; ++j)
             {
               merge (&tmp, &d->follows[pos[j].index], &merged);
               copy (&merged, &d->follows[pos[j].index]);
@@ -2395,43 +2483,39 @@ dfaanalyze (struct dfa *d, int searchflag)
 
           /* The firstpos of a CAT node is the firstpos of the first argument,
              union that of the second argument if the first is nullable.  */
-          if (nullable[-2])
-            nfirstpos[-2] += nfirstpos[-1];
+          if (stk[-2].nullable)
+            stk[-2].nfirstpos += stk[-1].nfirstpos;
           else
-            firstpos += nfirstpos[-1];
-          --nfirstpos;
+            firstpos += stk[-1].nfirstpos;
 
           /* The lastpos of a CAT node is the lastpos of the second argument,
              union that of the first argument if the second is nullable.  */
-          if (nullable[-1])
-            nlastpos[-2] += nlastpos[-1];
+          if (stk[-1].nullable)
+            stk[-2].nlastpos += stk[-1].nlastpos;
           else
             {
-              pos = lastpos + nlastpos[-2];
-              for (j = nlastpos[-1]; j-- > 0;)
+              pos = lastpos + stk[-2].nlastpos;
+              for (j = stk[-1].nlastpos; j-- > 0;)
                 pos[j] = lastpos[j];
-              lastpos += nlastpos[-2];
-              nlastpos[-2] = nlastpos[-1];
+              lastpos += stk[-2].nlastpos;
+              stk[-2].nlastpos = stk[-1].nlastpos;
             }
-          --nlastpos;
 
           /* A CAT node is nullable if both arguments are nullable.  */
-          nullable[-2] = nullable[-1] && nullable[-2];
-          --nullable;
+          stk[-2].nullable &= stk[-1].nullable;
+          stk--;
           break;
 
         case OR:
           /* The firstpos is the union of the firstpos of each argument.  */
-          nfirstpos[-2] += nfirstpos[-1];
-          --nfirstpos;
+          stk[-2].nfirstpos += stk[-1].nfirstpos;
 
           /* The lastpos is the union of the lastpos of each argument.  */
-          nlastpos[-2] += nlastpos[-1];
-          --nlastpos;
+          stk[-2].nlastpos += stk[-1].nlastpos;
 
           /* An OR node is nullable if either argument is nullable.  */
-          nullable[-2] = nullable[-1] || nullable[-2];
-          --nullable;
+          stk[-2].nullable |= stk[-1].nullable;
+          stk--;
           break;
 
         default:
@@ -2440,10 +2524,12 @@ dfaanalyze (struct dfa *d, int searchflag)
              an "epsilon closure" effectively makes them nullable later.
              Backreferences have to get a real position so we can detect
              transitions on them later.  But they are nullable.  */
-          *nullable++ = d->tokens[i] == BACKREF;
+          stk->nullable = d->tokens[i] == BACKREF;
 
           /* This position is in its own firstpos and lastpos.  */
-          *nfirstpos++ = *nlastpos++ = 1;
+          stk->nfirstpos = stk->nlastpos = 1;
+          stk++;
+
           --firstpos, --lastpos;
           firstpos->index = lastpos->index = i;
           firstpos->constraint = lastpos->constraint = NO_CONSTRAINT;
@@ -2457,15 +2543,16 @@ dfaanalyze (struct dfa *d, int searchflag)
       fprintf (stderr, "node %zd:", i);
       prtok (d->tokens[i]);
       putc ('\n', stderr);
-      fprintf (stderr, nullable[-1] ? " nullable: yes\n" : " nullable: no\n");
+      fprintf (stderr,
+               stk[-1].nullable ? " nullable: yes\n" : " nullable: no\n");
       fprintf (stderr, " firstpos:");
-      for (j = nfirstpos[-1]; j-- > 0;)
+      for (j = stk[-1].nfirstpos; j-- > 0;)
         {
           fprintf (stderr, " %zd:", firstpos[j].index);
           prtok (d->tokens[firstpos[j].index]);
         }
       fprintf (stderr, "\n lastpos:");
-      for (j = nlastpos[-1]; j-- > 0;)
+      for (j = stk[-1].nlastpos; j-- > 0;)
         {
           fprintf (stderr, " %zd:", lastpos[j].index);
           prtok (d->tokens[lastpos[j].index]);
@@ -2495,33 +2582,27 @@ dfaanalyze (struct dfa *d, int searchflag)
         putc ('\n', stderr);
 #endif
         copy (&d->follows[i], &merged);
-        epsclosure (&merged, d);
+        epsclosure (&merged, d, visited);
         copy (&merged, &d->follows[i]);
       }
 
   /* Get the epsilon closure of the firstpos of the regexp.  The result will
      be the set of positions of state 0.  */
   merged.nelem = 0;
-  for (i = 0; i < nfirstpos[-1]; ++i)
+  for (i = 0; i < stk[-1].nfirstpos; ++i)
     insert (firstpos[i], &merged);
-  epsclosure (&merged, d);
+  epsclosure (&merged, d, visited);
 
   /* Build the initial state.  */
-  d->salloc = 1;
-  d->sindex = 0;
-  MALLOC (d->states, d->salloc);
-
   separate_contexts = state_separate_contexts (&merged);
   state_index (d, &merged,
                (separate_contexts & CTX_NEWLINE
                 ? CTX_NEWLINE : separate_contexts ^ CTX_ANY));
 
-  free (o_nullable);
-  free (o_nfirst);
-  free (o_firstpos);
-  free (o_nlast);
-  free (o_lastpos);
+  free (posalloc);
+  free (stkalloc);
   free (merged.elems);
+  free (visited);
 }
 
 
@@ -2558,16 +2639,16 @@ dfaanalyze (struct dfa *d, int searchflag)
 void
 dfastate (state_num s, struct dfa *d, state_num trans[])
 {
-  leaf_set *grps;               /* As many as will ever be needed.  */
-  charclass *labels;            /* Labels corresponding to the groups.  */
+  leaf_set grps[NOTCHAR];       /* As many as will ever be needed.  */
+  charclass labels[NOTCHAR];    /* Labels corresponding to the groups.  */
   size_t ngrps = 0;             /* Number of groups actually used.  */
   position pos;                 /* Current position being considered.  */
   charclass matches;            /* Set of matching characters.  */
-  int matchesf;                 /* True if matches is nonempty.  */
+  charclass_word matchesf;	/* Nonzero if matches is nonempty.  */
   charclass intersect;          /* Intersection with some label set.  */
-  int intersectf;               /* True if intersect is nonempty.  */
+  charclass_word intersectf;	/* Nonzero if intersect is nonempty.  */
   charclass leftovers;          /* Stuff in the label that didn't match.  */
-  int leftoversf;               /* True if leftovers is nonempty.  */
+  charclass_word leftoversf;	/* Nonzero if leftovers is nonempty.  */
   position_set follows;         /* Union of the follows of some group.  */
   position_set tmp;             /* Temporary space for merging sets.  */
   int possible_contexts;        /* Contexts that this group can match.  */
@@ -2575,12 +2656,9 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
   state_num state;              /* New state.  */
   state_num state_newline;      /* New state on a newline transition.  */
   state_num state_letter;       /* New state on a letter transition.  */
-  int next_isnt_1st_byte = 0;   /* Flag if we can't add state0.  */
+  bool next_isnt_1st_byte = false; /* We can't add state0.  */
   size_t i, j, k;
 
-  MALLOC (grps, NOTCHAR);
-  MALLOC (labels, NOTCHAR);
-
   zeroset (matches);
 
   for (i = 0; i < d->states[s].elems.nelem; ++i)
@@ -2590,21 +2668,24 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
         setbit (d->tokens[pos.index], matches);
       else if (d->tokens[pos.index] >= CSET)
         copyset (d->charclasses[d->tokens[pos.index] - CSET], matches);
-      else if (MBS_SUPPORT
-               && (d->tokens[pos.index] == ANYCHAR
-                   || d->tokens[pos.index] == MBCSET))
-        /* MB_CUR_MAX > 1  */
+      else
         {
-          /* ANYCHAR and MBCSET must match with a single character, so we
-             must put it to d->states[s].mbps, which contains the positions
-             which can match with a single character not a byte.  */
-          if (d->states[s].mbps.nelem == 0)
-            alloc_position_set (&d->states[s].mbps, 1);
-          insert (pos, &(d->states[s].mbps));
+          if (MBS_SUPPORT
+               && (d->tokens[pos.index] == MBCSET
+              || d->tokens[pos.index] == ANYCHAR))
+            {
+              /* MB_CUR_MAX > 1 */
+              if (d->tokens[pos.index] == MBCSET)
+                d->states[s].has_mbcset = true;
+              /* ANYCHAR and MBCSET must match with a single character, so we
+                 must put it to d->states[s].mbps, which contains the positions
+                 which can match with a single character not a byte.  */
+              if (d->states[s].mbps.nelem == 0)
+                alloc_position_set (&d->states[s].mbps, 1);
+              insert (pos, &(d->states[s].mbps));
+            }
           continue;
         }
-      else
-        continue;
 
       /* Some characters may need to be eliminated from matches because
          they fail in the current context.  */
@@ -2612,21 +2693,21 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
         {
           if (!SUCCEEDS_IN_CONTEXT (pos.constraint,
                                     d->states[s].context, CTX_NEWLINE))
-            for (j = 0; j < CHARCLASS_INTS; ++j)
+            for (j = 0; j < CHARCLASS_WORDS; ++j)
               matches[j] &= ~newline[j];
           if (!SUCCEEDS_IN_CONTEXT (pos.constraint,
                                     d->states[s].context, CTX_LETTER))
-            for (j = 0; j < CHARCLASS_INTS; ++j)
+            for (j = 0; j < CHARCLASS_WORDS; ++j)
               matches[j] &= ~letters[j];
           if (!SUCCEEDS_IN_CONTEXT (pos.constraint,
                                     d->states[s].context, CTX_NONE))
-            for (j = 0; j < CHARCLASS_INTS; ++j)
+            for (j = 0; j < CHARCLASS_WORDS; ++j)
               matches[j] &= letters[j] | newline[j];
 
           /* If there are no characters left, there's no point in going on.  */
-          for (j = 0; j < CHARCLASS_INTS && !matches[j]; ++j)
+          for (j = 0; j < CHARCLASS_WORDS && !matches[j]; ++j)
             continue;
-          if (j == CHARCLASS_INTS)
+          if (j == CHARCLASS_WORDS)
             continue;
         }
 
@@ -2642,20 +2723,20 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
           /* Check if this group's label has a nonempty intersection with
              matches.  */
           intersectf = 0;
-          for (k = 0; k < CHARCLASS_INTS; ++k)
-            (intersect[k] = matches[k] & labels[j][k]) ? (intersectf = 1) : 0;
+          for (k = 0; k < CHARCLASS_WORDS; ++k)
+            intersectf |= intersect[k] = matches[k] & labels[j][k];
           if (!intersectf)
             continue;
 
           /* It does; now find the set differences both ways.  */
           leftoversf = matchesf = 0;
-          for (k = 0; k < CHARCLASS_INTS; ++k)
+          for (k = 0; k < CHARCLASS_WORDS; ++k)
             {
               /* Even an optimizing compiler can't know this for sure.  */
-              int match = matches[k], label = labels[j][k];
+              charclass_word match = matches[k], label = labels[j][k];
 
-              (leftovers[k] = ~match & label) ? (leftoversf = 1) : 0;
-              (matches[k] = match & ~label) ? (matchesf = 1) : 0;
+              leftoversf |= leftovers[k] = ~match & label;
+              matchesf |= matches[k] = match & ~label;
             }
 
           /* If there were leftovers, create a new group labeled with them.  */
@@ -2663,7 +2744,8 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
             {
               copyset (leftovers, labels[ngrps]);
               copyset (intersect, labels[j]);
-              MALLOC (grps[ngrps].elems, d->nleaves);
+              grps[ngrps].elems = xnmalloc (d->nleaves,
+                                            sizeof *grps[ngrps].elems);
               memcpy (grps[ngrps].elems, grps[j].elems,
                       sizeof (grps[j].elems[0]) * grps[j].nelem);
               grps[ngrps].nelem = grps[j].nelem;
@@ -2686,7 +2768,7 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
         {
           copyset (matches, labels[ngrps]);
           zeroset (matches);
-          MALLOC (grps[ngrps].elems, d->nleaves);
+          grps[ngrps].elems = xnmalloc (d->nleaves, sizeof *grps[ngrps].elems);
           grps[ngrps].nelem = 1;
           grps[ngrps].elems[0] = pos.index;
           ++ngrps;
@@ -2732,7 +2814,7 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
         for (k = 0; k < d->follows[grps[i].elems[j]].nelem; ++k)
           insert (d->follows[grps[i].elems[j]].elems[k], &follows);
 
-      if (d->mb_cur_max > 1)
+      if (d->multibyte)
         {
           /* If a token in follows.elems is not 1st byte of a multibyte
              character, or the states of follows must accept the bytes
@@ -2752,12 +2834,12 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
              codepoint of <sb a>, it must not be <sb a> but 2nd byte of
              <mb A>, so we cannot add state[0].  */
 
-          next_isnt_1st_byte = 0;
+          next_isnt_1st_byte = false;
           for (j = 0; j < follows.nelem; ++j)
             {
               if (!(d->multibyte_prop[follows.elems[j].index] & 1))
                 {
-                  next_isnt_1st_byte = 1;
+                  next_isnt_1st_byte = true;
                   break;
                 }
             }
@@ -2765,10 +2847,11 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
 
       /* If we are building a searching matcher, throw in the positions
          of state 0 as well.  */
-      if (d->searchflag
-          && (!MBS_SUPPORT || (d->mb_cur_max == 1 || !next_isnt_1st_byte)))
-        for (j = 0; j < d->states[0].elems.nelem; ++j)
-          insert (d->states[0].elems.elems[j], &follows);
+      if (d->searchflag && (!d->multibyte || !next_isnt_1st_byte))
+        {
+          merge (&d->states[0].elems, &follows, &tmp);
+          copy (&tmp, &follows);
+        }
 
       /* Find out if the new state will want any context information.  */
       possible_contexts = charclass_context (labels[i]);
@@ -2789,11 +2872,11 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
         state_letter = state;
 
       /* Set the transitions for each character in the current label.  */
-      for (j = 0; j < CHARCLASS_INTS; ++j)
-        for (k = 0; k < INTBITS; ++k)
-          if (labels[i][j] & 1U << k)
+      for (j = 0; j < CHARCLASS_WORDS; ++j)
+        for (k = 0; k < CHARCLASS_WORD_BITS; ++k)
+          if (labels[i][j] >> k & 1)
             {
-              int c = j * INTBITS + k;
+              int c = j * CHARCLASS_WORD_BITS + k;
 
               if (c == eolbyte)
                 trans[c] = state_newline;
@@ -2808,8 +2891,31 @@ dfastate (state_num s, struct dfa *d, state_num trans[])
     free (grps[i].elems);
   free (follows.elems);
   free (tmp.elems);
-  free (grps);
-  free (labels);
+}
+
+/* Make sure D's state arrays are large enough to hold NEW_STATE.  */
+static void
+realloc_trans_if_necessary (struct dfa *d, state_num new_state)
+{
+  state_num oldalloc = d->tralloc;
+  if (oldalloc <= new_state)
+    {
+      state_num **realtrans = d->trans ? d->trans - 1 : NULL;
+      size_t newalloc, newalloc1;
+      newalloc1 = new_state + 1;
+      realtrans = x2nrealloc (realtrans, &newalloc1, sizeof *realtrans);
+      realtrans[0] = NULL;
+      d->trans = realtrans + 1;
+      d->tralloc = newalloc = newalloc1 - 1;
+      d->fails = xnrealloc (d->fails, newalloc, sizeof *d->fails);
+      d->success = xnrealloc (d->success, newalloc, sizeof *d->success);
+      d->newlines = xnrealloc (d->newlines, newalloc, sizeof *d->newlines);
+      for (; oldalloc < newalloc; oldalloc++)
+        {
+          d->trans[oldalloc] = NULL;
+          d->fails[oldalloc] = NULL;
+        }
+    }
 }
 
 /* Some routines for manipulating a compiled dfa's transition tables.
@@ -2823,21 +2929,22 @@ static void
 build_state (state_num s, struct dfa *d)
 {
   state_num *trans;             /* The new transition table.  */
-  state_num i;
+  state_num i, maxstate;
 
   /* Set an upper limit on the number of transition tables that will ever
      exist at once.  1024 is arbitrary.  The idea is that the frequently
      used transition tables will be quickly rebuilt, whereas the ones that
-     were only needed once or twice will be cleared away.  */
+     were only needed once or twice will be cleared away.  However, do
+     not clear the initial state, as it's always used.  */
   if (d->trcount >= 1024)
     {
-      for (i = 0; i < d->tralloc; ++i)
+      for (i = 1; i < d->tralloc; ++i)
         {
           free (d->trans[i]);
           free (d->fails[i]);
           d->trans[i] = d->fails[i] = NULL;
         }
-      d->trcount = 0;
+      d->trcount = 1;
     }
 
   ++d->trcount;
@@ -2851,30 +2958,17 @@ build_state (state_num s, struct dfa *d)
   if (ACCEPTS_IN_CONTEXT (d->states[s].context, CTX_NONE, s, *d))
     d->success[s] |= CTX_NONE;
 
-  MALLOC (trans, NOTCHAR);
+  trans = xmalloc (NOTCHAR * sizeof *trans);
   dfastate (s, d, trans);
 
   /* Now go through the new transition table, and make sure that the trans
      and fail arrays are allocated large enough to hold a pointer for the
      largest state mentioned in the table.  */
+  maxstate = -1;
   for (i = 0; i < NOTCHAR; ++i)
-    if (trans[i] >= d->tralloc)
-      {
-        state_num oldalloc = d->tralloc;
-
-        while (trans[i] >= d->tralloc)
-          d->tralloc *= 2;
-        REALLOC (d->realtrans, d->tralloc + 1);
-        d->trans = d->realtrans + 1;
-        REALLOC (d->fails, d->tralloc);
-        REALLOC (d->success, d->tralloc);
-        REALLOC (d->newlines, d->tralloc);
-        while (oldalloc < d->tralloc)
-          {
-            d->trans[oldalloc] = NULL;
-            d->fails[oldalloc++] = NULL;
-          }
-      }
+    if (maxstate < trans[i])
+      maxstate = trans[i];
+  realloc_trans_if_necessary (d, maxstate);
 
   /* Keep the newline transition in a special place so we can use it as
      a sentinel.  */
@@ -2887,68 +2981,8 @@ build_state (state_num s, struct dfa *d)
     d->trans[s] = trans;
 }
 
-static void
-build_state_zero (struct dfa *d)
-{
-  d->tralloc = 1;
-  d->trcount = 0;
-  CALLOC (d->realtrans, d->tralloc + 1);
-  d->trans = d->realtrans + 1;
-  CALLOC (d->fails, d->tralloc);
-  MALLOC (d->success, d->tralloc);
-  MALLOC (d->newlines, d->tralloc);
-  build_state (0, d);
-}
-
 /* Multibyte character handling sub-routines for dfaexec.  */
 
-/* The initial state may encounter a byte which is not a single byte character
-   nor the first byte of a multibyte character.  But it is incorrect for the
-   initial state to accept such a byte.  For example, in Shift JIS the regular
-   expression "\\" accepts the codepoint 0x5c, but should not accept the second
-   byte of the codepoint 0x815c.  Then the initial state must skip the bytes
-   that are not a single byte character nor the first byte of a multibyte
-   character.  */
-#define SKIP_REMAINS_MB_IF_INITIAL_STATE(s, p)		\
-  if (s == 0)						\
-    {							\
-      while (inputwcs[p - buf_begin] == 0		\
-            && mblen_buf[p - buf_begin] > 0		\
-            && (unsigned char const *) p < buf_end)	\
-        ++p;						\
-      if ((char *) p >= end)				\
-        {						\
-          free (mblen_buf);				\
-          free (inputwcs);				\
-          *end = saved_end;				\
-          return NULL;					\
-        }						\
-    }
-
-static void
-realloc_trans_if_necessary (struct dfa *d, state_num new_state)
-{
-  /* Make sure that the trans and fail arrays are allocated large enough
-     to hold a pointer for the new state.  */
-  if (new_state >= d->tralloc)
-    {
-      state_num oldalloc = d->tralloc;
-
-      while (new_state >= d->tralloc)
-        d->tralloc *= 2;
-      REALLOC (d->realtrans, d->tralloc + 1);
-      d->trans = d->realtrans + 1;
-      REALLOC (d->fails, d->tralloc);
-      REALLOC (d->success, d->tralloc);
-      REALLOC (d->newlines, d->tralloc);
-      while (oldalloc < d->tralloc)
-        {
-          d->trans[oldalloc] = NULL;
-          d->fails[oldalloc++] = NULL;
-        }
-    }
-}
-
 /* Return values of transit_state_singlebyte, and
    transit_state_consume_1char.  */
 typedef enum
@@ -2981,14 +3015,7 @@ transit_state_singlebyte (struct dfa *d, state_num s, unsigned char const *p,
             works = 0;
         }
       else if (works < 0)
-        {
-          if (p == buf_end)
-            {
-              /* At the moment, it must not happen.  */
-              abort ();
-            }
-          works = 0;
-        }
+        works = 0;
       else if (d->fails[works])
         {
           works = d->fails[works][*p];
@@ -3003,18 +3030,13 @@ transit_state_singlebyte (struct dfa *d, state_num s, unsigned char const *p,
   return rval;
 }
 
-/* Match a "." against the current context.  buf_begin[IDX] is the
-   current position.  Return the length of the match, in bytes.
-   POS is the position of the ".".  */
+/* Match a "." against the current context.  Return the length of the
+   match, in bytes.  POS is the position of the ".".  */
 static int
-match_anychar (struct dfa *d, state_num s, position pos, size_t idx)
+match_anychar (struct dfa *d, state_num s, position pos,
+               wint_t wc, size_t mbclen)
 {
   int context;
-  wchar_t wc;
-  int mbclen;
-
-  wc = inputwcs[idx];
-  mbclen = (mblen_buf[idx] == 0) ? 1 : mblen_buf[idx];
 
   /* Check syntax bits.  */
   if (wc == (wchar_t) eolbyte)
@@ -3027,6 +3049,8 @@ match_anychar (struct dfa *d, state_num s, position pos, size_t idx)
       if (syntax_bits & RE_DOT_NOT_NULL)
         return 0;
     }
+  else if (wc == WEOF)
+    return 0;
 
   context = wchar_context (wc);
   if (!SUCCEEDS_IN_CONTEXT (pos.constraint, d->states[s].context, context))
@@ -3036,16 +3060,14 @@ match_anychar (struct dfa *d, state_num s, position pos, size_t idx)
 }
 
 /* Match a bracket expression against the current context.
-   buf_begin[IDX] is the current position.
    Return the length of the match, in bytes.
    POS is the position of the bracket expression.  */
 static int
-match_mb_charset (struct dfa *d, state_num s, position pos, size_t idx)
+match_mb_charset (struct dfa *d, state_num s, position pos,
+                  char const *p, wint_t wc, size_t match_len)
 {
   size_t i;
-  int match;               /* Matching succeeded.  */
-  int match_len;           /* Length of the character (or collating element)
-                              with which this operator matches.  */
+  bool match;              /* Matching succeeded.  */
   int op_len;              /* Length of the operator.  */
   char buffer[128];
 
@@ -3053,9 +3075,6 @@ match_mb_charset (struct dfa *d, state_num s, position pos, size_t idx)
   struct mb_char_classes *work_mbc;
 
   int context;
-  wchar_t wc;                   /* Current referring character.  */
-
-  wc = inputwcs[idx];
 
   /* Check syntax bits.  */
   if (wc == (wchar_t) eolbyte)
@@ -3068,6 +3087,8 @@ match_mb_charset (struct dfa *d, state_num s, position pos, size_t idx)
       if (syntax_bits & RE_DOT_NOT_NULL)
         return 0;
     }
+  else if (wc == WEOF)
+    return 0;
 
   context = wchar_context (wc);
   if (!SUCCEEDS_IN_CONTEXT (pos.constraint, d->states[s].context, context))
@@ -3076,11 +3097,10 @@ match_mb_charset (struct dfa *d, state_num s, position pos, size_t idx)
   /* Assign the current referring operator to work_mbc.  */
   work_mbc = &(d->mbcsets[(d->multibyte_prop[pos.index]) >> 2]);
   match = !work_mbc->invert;
-  match_len = (mblen_buf[idx] == 0) ? 1 : mblen_buf[idx];
 
   /* Match in range 0-255?  */
   if (wc < NOTCHAR && work_mbc->cset != -1
-      && tstbit ((unsigned char) wc, d->charclasses[work_mbc->cset]))
+      && tstbit (to_uchar (wc), d->charclasses[work_mbc->cset]))
     goto charset_matched;
 
   /* match with a character class?  */
@@ -3090,14 +3110,14 @@ match_mb_charset (struct dfa *d, state_num s, position pos, size_t idx)
         goto charset_matched;
     }
 
-  strncpy (buffer, (char const *) buf_begin + idx, match_len);
+  strncpy (buffer, p, match_len);
   buffer[match_len] = '\0';
 
   /* match with an equivalence class?  */
   for (i = 0; i < work_mbc->nequivs; i++)
     {
       op_len = strlen (work_mbc->equivs[i]);
-      strncpy (buffer, (char const *) buf_begin + idx, op_len);
+      strncpy (buffer, p, op_len);
       buffer[op_len] = '\0';
       if (strcoll (work_mbc->equivs[i], buffer) == 0)
         {
@@ -3110,7 +3130,7 @@ match_mb_charset (struct dfa *d, state_num s, position pos, size_t idx)
   for (i = 0; i < work_mbc->ncoll_elems; i++)
     {
       op_len = strlen (work_mbc->coll_elems[i]);
-      strncpy (buffer, (char const *) buf_begin + idx, op_len);
+      strncpy (buffer, p, op_len);
       buffer[op_len] = '\0';
 
       if (strcoll (work_mbc->coll_elems[i], buffer) == 0)
@@ -3123,7 +3143,7 @@ match_mb_charset (struct dfa *d, state_num s, position pos, size_t idx)
   /* match with a range?  */
   for (i = 0; i < work_mbc->nranges; i++)
     {
-      if (work_mbc->range_sts[i] <= wc && wc <= work_mbc->range_ends[i])
+      if (work_mbc->ranges[i].beg <= wc && wc <= work_mbc->ranges[i].end)
         goto charset_matched;
     }
 
@@ -3144,27 +3164,25 @@ charset_matched:
    array which corresponds to 'd->states[s].mbps.elem'; each element of the
    array contains the number of bytes with which the element can match.
 
-   'idx' is the index from buf_begin, and it is the current position
-   in the buffer.
-
    The caller MUST free the array which this function return.  */
 static int *
-check_matching_with_multibyte_ops (struct dfa *d, state_num s, size_t idx)
+check_matching_with_multibyte_ops (struct dfa *d, state_num s,
+                                   char const *p, wint_t wc, size_t mbclen)
 {
   size_t i;
   int *rarray;
 
-  MALLOC (rarray, d->states[s].mbps.nelem);
+  rarray = d->mb_match_lens;
   for (i = 0; i < d->states[s].mbps.nelem; ++i)
     {
       position pos = d->states[s].mbps.elems[i];
       switch (d->tokens[pos.index])
         {
         case ANYCHAR:
-          rarray[i] = match_anychar (d, s, pos, idx);
+          rarray[i] = match_anychar (d, s, pos, wc, mbclen);
           break;
         case MBCSET:
-          rarray[i] = match_mb_charset (d, s, pos, idx);
+          rarray[i] = match_mb_charset (d, s, pos, p, wc, mbclen);
           break;
         default:
           break;                /* cannot happen.  */
@@ -3184,48 +3202,39 @@ check_matching_with_multibyte_ops (struct dfa *d, state_num s, size_t idx)
 static status_transit_state
 transit_state_consume_1char (struct dfa *d, state_num s,
                              unsigned char const **pp,
-                             int *match_lens, int *mbclen, position_set * pps)
+                             wint_t wc, size_t mbclen,
+                             int *match_lens)
 {
   size_t i, j;
   int k;
   state_num s1, s2;
-  int *work_mbls;
   status_transit_state rs = TRANSIT_STATE_DONE;
 
-  /* Calculate the length of the (single/multi byte) character
-     to which p points.  */
-  *mbclen = (mblen_buf[*pp - buf_begin] == 0) ? 1 : mblen_buf[*pp - buf_begin];
+  if (! match_lens && d->states[s].mbps.nelem != 0)
+    match_lens = check_matching_with_multibyte_ops (d, s, (char const *) *pp,
+                                                    wc, mbclen);
 
   /* Calculate the state which can be reached from the state 's' by
-     consuming '*mbclen' single bytes from the buffer.  */
+     consuming 'mbclen' single bytes from the buffer.  */
   s1 = s;
-  for (k = 0; k < *mbclen; k++)
+  for (k = 0; k < mbclen; k++)
     {
       s2 = s1;
       rs = transit_state_singlebyte (d, s2, (*pp)++, &s1);
     }
-  /* Copy the positions contained by 's1' to the set 'pps'.  */
-  copy (&(d->states[s1].elems), pps);
-
-  /* Check (input) match_lens, and initialize if it is NULL.  */
-  if (match_lens == NULL && d->states[s].mbps.nelem != 0)
-    work_mbls = check_matching_with_multibyte_ops (d, s, *pp - buf_begin);
-  else
-    work_mbls = match_lens;
+  copy (&d->states[s1].elems, &d->mb_follows);
 
   /* Add all of the positions which can be reached from 's' by consuming
      a single character.  */
   for (i = 0; i < d->states[s].mbps.nelem; i++)
     {
-      if (work_mbls[i] == *mbclen)
+      if (match_lens[i] == mbclen)
         for (j = 0; j < d->follows[d->states[s].mbps.elems[i].index].nelem;
              j++)
-          insert (d->follows[d->states[s].mbps.elems[i].index].elems[j], pps);
+          insert (d->follows[d->states[s].mbps.elems[i].index].elems[j],
+                  &d->mb_follows);
     }
 
-  if (match_lens == NULL && work_mbls != NULL)
-    free (work_mbls);
-
   /* FIXME: this return value is always ignored.  */
   return rs;
 }
@@ -3234,7 +3243,8 @@ transit_state_consume_1char (struct dfa *d, state_num s,
    buffer.  This function is for some operator which can match with a multi-
    byte character or a collating element (which may be multi characters).  */
 static state_num
-transit_state (struct dfa *d, state_num s, unsigned char const **pp)
+transit_state (struct dfa *d, state_num s, unsigned char const **pp,
+               unsigned char const *end)
 {
   state_num s1;
   int mbclen;  /* The length of current input multibyte character.  */
@@ -3242,16 +3252,17 @@ transit_state (struct dfa *d, state_num s, unsigned char const **pp)
   size_t i, j;
   int *match_lens = NULL;
   size_t nelem = d->states[s].mbps.nelem;       /* Just a alias.  */
-  position_set follows;
   unsigned char const *p1 = *pp;
-  wchar_t wc;
+  wint_t wc;
 
   if (nelem > 0)
     /* This state has (a) multibyte operator(s).
        We check whether each of them can match or not.  */
     {
       /* Note: caller must free the return value of this function.  */
-      match_lens = check_matching_with_multibyte_ops (d, s, *pp - buf_begin);
+      mbclen = mbs_to_wchar (&wc, (char const *) *pp, end - *pp, d);
+      match_lens = check_matching_with_multibyte_ops (d, s, (char const *) *pp,
+                                                      wc, mbclen);
 
       for (i = 0; i < nelem; i++)
         /* Search the operator which match the longest string,
@@ -3273,26 +3284,25 @@ transit_state (struct dfa *d, state_num s, unsigned char const **pp)
       if (rs == TRANSIT_STATE_DONE)
         ++*pp;
 
-      free (match_lens);
       return s1;
     }
 
   /* This state has some operators which can match a multibyte character.  */
-  alloc_position_set (&follows, d->nleaves);
+  d->mb_follows.nelem = 0;
 
   /* 'maxlen' may be longer than the length of a character, because it may
      not be a character but a (multi character) collating element.
      We enumerate all of the positions which 's' can reach by consuming
      'maxlen' bytes.  */
-  transit_state_consume_1char (d, s, pp, match_lens, &mbclen, &follows);
+  transit_state_consume_1char (d, s, pp, wc, mbclen, match_lens);
 
-  wc = inputwcs[*pp - mbclen - buf_begin];
-  s1 = state_index (d, &follows, wchar_context (wc));
+  s1 = state_index (d, &d->mb_follows, wchar_context (wc));
   realloc_trans_if_necessary (d, s1);
 
   while (*pp - p1 < maxlen)
     {
-      transit_state_consume_1char (d, s1, pp, NULL, &mbclen, &follows);
+      mbclen = mbs_to_wchar (&wc, (char const *) *pp, end - *pp, d);
+      transit_state_consume_1char (d, s1, pp, wc, mbclen, NULL);
 
       for (i = 0; i < nelem; i++)
         {
@@ -3300,68 +3310,15 @@ transit_state (struct dfa *d, state_num s, unsigned char const **pp)
             for (j = 0;
                  j < d->follows[d->states[s1].mbps.elems[i].index].nelem; j++)
               insert (d->follows[d->states[s1].mbps.elems[i].index].elems[j],
-                      &follows);
+                      &d->mb_follows);
         }
 
-      wc = inputwcs[*pp - mbclen - buf_begin];
-      s1 = state_index (d, &follows, wchar_context (wc));
+      s1 = state_index (d, &d->mb_follows, wchar_context (wc));
       realloc_trans_if_necessary (d, s1);
     }
-  free (match_lens);
-  free (follows.elems);
   return s1;
 }
 
-
-/* Initialize mblen_buf and inputwcs with data from the next line.  */
-
-static void
-prepare_wc_buf (const char *begin, const char *end)
-{
-#if MBS_SUPPORT
-  unsigned char eol = eolbyte;
-  size_t remain_bytes, i;
-
-  buf_begin = (unsigned char *) begin;
-
-  remain_bytes = 0;
-  for (i = 0; i < end - begin + 1; i++)
-    {
-      if (remain_bytes == 0)
-        {
-          remain_bytes
-            = mbrtowc (inputwcs + i, begin + i, end - begin - i + 1, &mbs);
-          if (remain_bytes < 1
-              || remain_bytes == (size_t) -1
-              || remain_bytes == (size_t) -2
-              || (remain_bytes == 1 && inputwcs[i] == (wchar_t) begin[i]))
-            {
-              remain_bytes = 0;
-              inputwcs[i] = (wchar_t) begin[i];
-              mblen_buf[i] = 0;
-              if (begin[i] == eol)
-                break;
-            }
-          else
-            {
-              mblen_buf[i] = remain_bytes;
-              remain_bytes--;
-            }
-        }
-      else
-        {
-          mblen_buf[i] = remain_bytes;
-          inputwcs[i] = 0;
-          remain_bytes--;
-        }
-    }
-
-  buf_end = (unsigned char *) (begin + i);
-  mblen_buf[i] = 0;
-  inputwcs[i] = 0;              /* sentinel */
-#endif /* MBS_SUPPORT */
-}
-
 /* Search through a buffer looking for a match to the given struct dfa.
    Find the first occurrence of a string matching the regexp in the
    buffer, and the shortest possible version thereof.  Return a pointer to
@@ -3379,39 +3336,67 @@ dfaexec (struct dfa *d, char const *begin, char *end,
          int allow_nl, size_t *count, int *backref)
 {
   state_num s, s1;              /* Current state.  */
-  unsigned char const *p;       /* Current input character.  */
+  unsigned char const *p, *mbp; /* Current input character.  */
   state_num **trans, *t;        /* Copy of d->trans so it can be optimized
                                    into a register.  */
   unsigned char eol = eolbyte;  /* Likewise for eolbyte.  */
   unsigned char saved_end;
+  size_t nlcount = 0;
 
   if (!d->tralloc)
-    build_state_zero (d);
+    {
+      realloc_trans_if_necessary (d, 1);
+      build_state (0, d);
+    }
 
   s = s1 = 0;
-  p = (unsigned char const *) begin;
+  p = mbp = (unsigned char const *) begin;
   trans = d->trans;
   saved_end = *(unsigned char *) end;
   *end = eol;
 
-  if (d->mb_cur_max > 1)
+  if (d->multibyte)
     {
-      MALLOC (mblen_buf, end - begin + 2);
-      MALLOC (inputwcs, end - begin + 2);
-      memset (&mbs, 0, sizeof (mbstate_t));
-      prepare_wc_buf ((const char *) p, end);
+      memset (&d->mbs, 0, sizeof d->mbs);
+      if (! d->mb_match_lens)
+        {
+          d->mb_match_lens = xnmalloc (d->nleaves, sizeof *d->mb_match_lens);
+          alloc_position_set (&d->mb_follows, d->nleaves);
+        }
     }
 
   for (;;)
     {
-      if (d->mb_cur_max > 1)
+      if (d->multibyte)
         {
           while ((t = trans[s]) != NULL)
             {
-              if (p > buf_end)
-                break;
               s1 = s;
-              SKIP_REMAINS_MB_IF_INITIAL_STATE (s, p);
+
+              if (s == 0)
+                {
+                  /* The initial state may encounter a byte which is not
+                     a single byte character nor the first byte of a
+                     multibyte character.  But it is incorrect for the
+                     initial state to accept such a byte.  For example,
+                     in Shift JIS the regular expression "\\" accepts
+                     the codepoint 0x5c, but should not accept the second
+                     byte of the codepoint 0x815c.  Then the initial
+                     state must skip the bytes that are not a single
+                     byte character nor the first byte of a multibyte
+                     character.  */
+                  wint_t wc;
+                  while (mbp < p)
+                    mbp += mbs_to_wchar (&wc, (char const *) mbp,
+                                         end - (char const *) mbp, d);
+                  p = mbp;
+
+                  if ((char *) p > end)
+                    {
+                      p = NULL;
+                      goto done;
+                    }
+                }
 
               if (d->states[s].mbps.nelem == 0)
                 {
@@ -3423,18 +3408,16 @@ dfaexec (struct dfa *d, char const *begin, char *end,
                  better performance (up to 25% better on [a-z], for
                  example) and enables support for collating symbols and
                  equivalence classes.  */
-              if (backref)
+              if (d->states[s].has_mbcset && backref)
                 {
                   *backref = 1;
-                  free (mblen_buf);
-                  free (inputwcs);
-                  *end = saved_end;
-                  return (char *) p;
+                  goto done;
                 }
 
               /* Can match with a multibyte character (and multi character
                  collating element).  Transition table might be updated.  */
-              s = transit_state (d, s, &p);
+              s = transit_state (d, s, &p, (unsigned char *) end);
+              mbp = p;
               trans = d->trans;
             }
         }
@@ -3454,27 +3437,28 @@ dfaexec (struct dfa *d, char const *begin, char *end,
             }
         }
 
-      if (s >= 0 && (char *) p <= end && d->fails[s])
+      if ((char *) p > end)
+        {
+          p = NULL;
+          goto done;
+        }
+
+      if (s >= 0 && d->fails[s])
         {
           if (d->success[s] & sbit[*p])
             {
               if (backref)
-                *backref = (d->states[s].backref != 0);
-              if (d->mb_cur_max > 1)
-                {
-                  free (mblen_buf);
-                  free (inputwcs);
-                }
-              *end = saved_end;
-              return (char *) p;
+                *backref = d->states[s].has_backref;
+              goto done;
             }
 
           s1 = s;
-          if (d->mb_cur_max > 1)
+          if (d->multibyte)
             {
               /* Can match with a multibyte character (and multicharacter
                  collating element).  Transition table might be updated.  */
-              s = transit_state (d, s, &p);
+              s = transit_state (d, s, &p, (unsigned char *) end);
+              mbp = p;
               trans = d->trans;
             }
           else
@@ -3482,31 +3466,18 @@ dfaexec (struct dfa *d, char const *begin, char *end,
           continue;
         }
 
-      /* If the previous character was a newline, count it.  */
-      if ((char *) p <= end && p[-1] == eol)
+      /* If the previous character was a newline, count it, and skip
+         checking of multibyte character boundary until here.  */
+      if (p[-1] == eol)
         {
-          if (count)
-            ++*count;
-
-          if (d->mb_cur_max > 1)
-            prepare_wc_buf ((const char *) p, end);
-        }
-
-      /* Check if we've run off the end of the buffer.  */
-      if ((char *) p > end)
-        {
-          if (d->mb_cur_max > 1)
-            {
-              free (mblen_buf);
-              free (inputwcs);
-            }
-          *end = saved_end;
-          return NULL;
+          nlcount++;
+          mbp = p;
         }
 
       if (s >= 0)
         {
-          build_state (s, d);
+          if (!d->trans[s])
+            build_state (s, d);
           trans = d->trans;
           continue;
         }
@@ -3519,6 +3490,24 @@ dfaexec (struct dfa *d, char const *begin, char *end,
 
       s = 0;
     }
+
+ done:
+  if (count)
+    *count += nlcount;
+  *end = saved_end;
+  return (char *) p;
+}
+
+struct dfa *
+dfasuperset (struct dfa const *d)
+{
+  return d->superset;
+}
+
+bool
+dfaisfast (struct dfa const *d)
+{
+  return d->fast;
 }
 
 static void
@@ -3527,7 +3516,6 @@ free_mbdata (struct dfa *d)
   size_t i;
 
   free (d->multibyte_prop);
-  d->multibyte_prop = NULL;
 
   for (i = 0; i < d->nmbcsets; ++i)
     {
@@ -3535,8 +3523,7 @@ free_mbdata (struct dfa *d)
       struct mb_char_classes *p = &(d->mbcsets[i]);
       free (p->chars);
       free (p->ch_classes);
-      free (p->range_sts);
-      free (p->range_ends);
+      free (p->ranges);
 
       for (j = 0; j < p->nequivs; ++j)
         free (p->equivs[j]);
@@ -3548,8 +3535,9 @@ free_mbdata (struct dfa *d)
     }
 
   free (d->mbcsets);
-  d->mbcsets = NULL;
-  d->nmbcsets = 0;
+  free (d->mb_follows.elems);
+  free (d->mb_match_lens);
+  d->mb_match_lens = NULL;
 }
 
 /* Initialize the components of a dfa that the other routines don't
@@ -3558,28 +3546,15 @@ void
 dfainit (struct dfa *d)
 {
   memset (d, 0, sizeof *d);
-
-  d->calloc = 1;
-  MALLOC (d->charclasses, d->calloc);
-
-  d->talloc = 1;
-  MALLOC (d->tokens, d->talloc);
-
-  d->mb_cur_max = MB_CUR_MAX;
-
-  if (d->mb_cur_max > 1)
-    {
-      d->nmultibyte_prop = 1;
-      MALLOC (d->multibyte_prop, d->nmultibyte_prop);
-      d->mbcsets_alloc = 1;
-      MALLOC (d->mbcsets, d->mbcsets_alloc);
-    }
+  d->multibyte = MB_CUR_MAX > 1;
+  d->fast = !d->multibyte;
 }
 
 static void
 dfaoptimize (struct dfa *d)
 {
   size_t i;
+  bool have_backref = false;
 
   if (!MBS_SUPPORT || !using_utf8 ())
     return;
@@ -3591,6 +3566,9 @@ dfaoptimize (struct dfa *d)
         case ANYCHAR:
           /* Lowered.  */
           abort ();
+        case BACKREF:
+          have_backref = true;
+          break;
         case MBCSET:
           /* Requires multi-byte algorithm.  */
           return;
@@ -3599,8 +3577,95 @@ dfaoptimize (struct dfa *d)
         }
     }
 
+  if (!have_backref && d->superset)
+    {
+      /* The superset DFA is not likely to be much faster, so remove it.  */
+      dfafree (d->superset);
+      free (d->superset);
+      d->superset = NULL;
+    }
+
   free_mbdata (d);
-  d->mb_cur_max = 1;
+  d->multibyte = false;
+}
+
+static void
+dfassbuild (struct dfa *d)
+{
+  size_t i, j;
+  charclass ccl;
+  bool have_achar = false;
+  bool have_nchar = false;
+  struct dfa *sup = dfaalloc ();
+
+  *sup = *d;
+  sup->multibyte = false;
+  sup->multibyte_prop = NULL;
+  sup->mbcsets = NULL;
+  sup->superset = NULL;
+  sup->states = NULL;
+  sup->sindex = 0;
+  sup->follows = NULL;
+  sup->tralloc = 0;
+  sup->trans = NULL;
+  sup->fails = NULL;
+  sup->success = NULL;
+  sup->newlines = NULL;
+  sup->musts = NULL;
+
+  sup->charclasses = xnmalloc (sup->calloc, sizeof *sup->charclasses);
+  memcpy (sup->charclasses, d->charclasses,
+          d->cindex * sizeof *sup->charclasses);
+
+  sup->tokens = xnmalloc (d->tindex, 2 * sizeof *sup->tokens);
+  sup->talloc = d->tindex * 2;
+
+  for (i = j = 0; i < d->tindex; i++)
+    {
+      switch (d->tokens[i])
+        {
+        case ANYCHAR:
+        case MBCSET:
+        case BACKREF:
+          zeroset (ccl);
+          notset (ccl);
+          sup->tokens[j++] = CSET + dfa_charclass_index (sup, ccl);
+          sup->tokens[j++] = STAR;
+          if (d->tokens[i + 1] == QMARK || d->tokens[i + 1] == STAR
+              || d->tokens[i + 1] == PLUS)
+            i++;
+          have_achar = true;
+          break;
+        case BEGWORD:
+        case ENDWORD:
+        case LIMWORD:
+        case NOTLIMWORD:
+          if (d->multibyte)
+            {
+              /* These constraints aren't supported in a multibyte locale.
+                 Ignore them in the superset DFA, and treat them as
+                 backreferences in the main DFA.  */
+              sup->tokens[j++] = EMPTY;
+              d->tokens[i] = BACKREF;
+              break;
+            }
+        default:
+          sup->tokens[j++] = d->tokens[i];
+          if ((0 <= d->tokens[i] && d->tokens[i] < NOTCHAR)
+              || d->tokens[i] >= CSET)
+            have_nchar = true;
+          break;
+        }
+    }
+  sup->tindex = j;
+
+  if (have_nchar && (have_achar || d->multibyte))
+    d->superset = sup;
+  else
+    {
+      dfafree (sup);
+      free (sup);
+    }
 }
 
 /* Parse and analyze a single string of the given length.  */
@@ -3608,10 +3673,17 @@ void
 dfacomp (char const *s, size_t len, struct dfa *d, int searchflag)
 {
   dfainit (d);
+  dfambcache (d);
   dfaparse (s, len, d);
   dfamust (d);
+  dfassbuild (d);
   dfaoptimize (d);
   dfaanalyze (d, searchflag);
+  if (d->superset)
+    {
+      d->fast = true;
+      dfaanalyze (d->superset, searchflag);
+    }
 }
 
 /* Free the storage held by the components of a dfa.  */
@@ -3624,34 +3696,46 @@ dfafree (struct dfa *d)
   free (d->charclasses);
   free (d->tokens);
 
-  if (d->mb_cur_max > 1)
+  if (d->multibyte)
     free_mbdata (d);
 
   for (i = 0; i < d->sindex; ++i)
     {
       free (d->states[i].elems.elems);
-      if (MBS_SUPPORT)
-        free (d->states[i].mbps.elems);
+      free (d->states[i].mbps.elems);
     }
   free (d->states);
-  for (i = 0; i < d->tindex; ++i)
-    free (d->follows[i].elems);
-  free (d->follows);
-  for (i = 0; i < d->tralloc; ++i)
+
+  if (d->follows)
     {
-      free (d->trans[i]);
-      free (d->fails[i]);
+      for (i = 0; i < d->tindex; ++i)
+        free (d->follows[i].elems);
+      free (d->follows);
     }
-  free (d->realtrans);
-  free (d->fails);
-  free (d->newlines);
-  free (d->success);
+
+  if (d->trans)
+    {
+      for (i = 0; i < d->tralloc; ++i)
+        {
+          free (d->trans[i]);
+          free (d->fails[i]);
+        }
+
+      free (d->trans - 1);
+      free (d->fails);
+      free (d->newlines);
+      free (d->success);
+    }
+
   for (dm = d->musts; dm; dm = ndm)
     {
       ndm = dm->next;
       free (dm->must);
       free (dm);
     }
+
+  if (d->superset)
+    dfafree (d->superset);
 }
 
 /* Having found the postfix representation of the regular expression,
@@ -3742,64 +3826,32 @@ static char *
 icatalloc (char *old, char const *new)
 {
   char *result;
-  size_t oldsize = old == NULL ? 0 : strlen (old);
-  size_t newsize = new == NULL ? 0 : strlen (new);
+  size_t oldsize;
+  size_t newsize = strlen (new);
   if (newsize == 0)
     return old;
+  oldsize = strlen (old);
   result = xrealloc (old, oldsize + newsize + 1);
   memcpy (result + oldsize, new, newsize + 1);
   return result;
 }
 
-static char *
-icpyalloc (char const *string)
-{
-  return icatalloc (NULL, string);
-}
-
-static char *_GL_ATTRIBUTE_PURE
-istrstr (char const *lookin, char const *lookfor)
-{
-  char const *cp;
-  size_t len;
-
-  len = strlen (lookfor);
-  for (cp = lookin; *cp != '\0'; ++cp)
-    if (strncmp (cp, lookfor, len) == 0)
-      return (char *) cp;
-  return NULL;
-}
-
 static void
 freelist (char **cpp)
 {
-  size_t i;
-
-  if (cpp == NULL)
-    return;
-  for (i = 0; cpp[i] != NULL; ++i)
-    {
-      free (cpp[i]);
-      cpp[i] = NULL;
-    }
+  while (*cpp)
+    free (*cpp++);
 }
 
 static char **
 enlist (char **cpp, char *new, size_t len)
 {
   size_t i, j;
-
-  if (cpp == NULL)
-    return NULL;
-  if ((new = icpyalloc (new)) == NULL)
-    {
-      freelist (cpp);
-      return NULL;
-    }
+  new = memcpy (xmalloc (len + 1), new, len);
   new[len] = '\0';
   /* Is there already something in the list that's new (or longer)?  */
   for (i = 0; cpp[i] != NULL; ++i)
-    if (istrstr (cpp[i], new) != NULL)
+    if (strstr (cpp[i], new) != NULL)
       {
         free (new);
         return cpp;
@@ -3807,7 +3859,7 @@ enlist (char **cpp, char *new, size_t len)
   /* Eliminate any obsoleted strings.  */
   j = 0;
   while (cpp[j] != NULL)
-    if (istrstr (new, cpp[j]) == NULL)
+    if (strstr (new, cpp[j]) == NULL)
       ++j;
     else
       {
@@ -3818,53 +3870,35 @@ enlist (char **cpp, char *new, size_t len)
         cpp[i] = NULL;
       }
   /* Add the new string.  */
-  REALLOC (cpp, i + 2);
+  cpp = xnrealloc (cpp, i + 2, sizeof *cpp);
   cpp[i] = new;
   cpp[i + 1] = NULL;
   return cpp;
 }
 
 /* Given pointers to two strings, return a pointer to an allocated
-   list of their distinct common substrings.  Return NULL if something
-   seems wild.  */
+   list of their distinct common substrings.  */
 static char **
 comsubs (char *left, char const *right)
 {
-  char **cpp;
+  char **cpp = xzalloc (sizeof *cpp);
   char *lcp;
-  char *rcp;
-  size_t i, len;
-
-  if (left == NULL || right == NULL)
-    return NULL;
-  cpp = malloc (sizeof *cpp);
-  if (cpp == NULL)
-    return NULL;
-  cpp[0] = NULL;
+
   for (lcp = left; *lcp != '\0'; ++lcp)
     {
-      len = 0;
-      rcp = strchr (right, *lcp);
+      size_t len = 0;
+      char *rcp = strchr (right, *lcp);
       while (rcp != NULL)
         {
+          size_t i;
           for (i = 1; lcp[i] != '\0' && lcp[i] == rcp[i]; ++i)
             continue;
           if (i > len)
             len = i;
           rcp = strchr (rcp + 1, *lcp);
         }
-      if (len == 0)
-        continue;
-      {
-        char **p = enlist (cpp, lcp, len);
-        if (p == NULL)
-          {
-            freelist (cpp);
-            cpp = NULL;
-            break;
-          }
-        cpp = p;
-      }
+      if (len != 0)
+        cpp = enlist (cpp, lcp, len);
     }
   return cpp;
 }
@@ -3872,16 +3906,8 @@ comsubs (char *left, char const *right)
 static char **
 addlists (char **old, char **new)
 {
-  size_t i;
-
-  if (old == NULL || new == NULL)
-    return NULL;
-  for (i = 0; new[i] != NULL; ++i)
-    {
-      old = enlist (old, new[i], strlen (new[i]));
-      if (old == NULL)
-        break;
-    }
+  for (; *new; new++)
+    old = enlist (old, *new, strlen (*new));
   return old;
 }
 
@@ -3890,125 +3916,134 @@ addlists (char **old, char **new)
 static char **
 inboth (char **left, char **right)
 {
-  char **both;
-  char **temp;
+  char **both = xzalloc (sizeof *both);
   size_t lnum, rnum;
 
-  if (left == NULL || right == NULL)
-    return NULL;
-  both = malloc (sizeof *both);
-  if (both == NULL)
-    return NULL;
-  both[0] = NULL;
   for (lnum = 0; left[lnum] != NULL; ++lnum)
     {
       for (rnum = 0; right[rnum] != NULL; ++rnum)
         {
-          temp = comsubs (left[lnum], right[rnum]);
-          if (temp == NULL)
-            {
-              freelist (both);
-              return NULL;
-            }
+          char **temp = comsubs (left[lnum], right[rnum]);
           both = addlists (both, temp);
           freelist (temp);
           free (temp);
-          if (both == NULL)
-            return NULL;
         }
     }
   return both;
 }
 
-typedef struct
+typedef struct must must;
+
+struct must
 {
   char **in;
   char *left;
   char *right;
   char *is;
-} must;
+  bool begline;
+  bool endline;
+  must *prev;
+};
+
+static must *
+allocmust (must *mp)
+{
+  must *new_mp = xmalloc (sizeof *new_mp);
+  new_mp->in = xzalloc (sizeof *new_mp->in);
+  new_mp->left = xzalloc (2);
+  new_mp->right = xzalloc (2);
+  new_mp->is = xzalloc (2);
+  new_mp->begline = false;
+  new_mp->endline = false;
+  new_mp->prev = mp;
+  return new_mp;
+}
 
 static void
-resetmust (must * mp)
+resetmust (must *mp)
 {
+  freelist (mp->in);
+  mp->in[0] = NULL;
   mp->left[0] = mp->right[0] = mp->is[0] = '\0';
+  mp->begline = false;
+  mp->endline = false;
+}
+
+static void
+freemust (must *mp)
+{
   freelist (mp->in);
+  free (mp->in);
+  free (mp->left);
+  free (mp->right);
+  free (mp->is);
+  free (mp);
 }
 
 static void
 dfamust (struct dfa *d)
 {
-  must *musts;
-  must *mp;
-  char *result;
+  must *mp = NULL;
+  char const *result = "";
   size_t ri;
   size_t i;
-  int exact;
-  token t;
-  static must must0;
+  bool exact = false;
+  bool begline = false;
+  bool endline = false;
   struct dfamust *dm;
-  static char empty_string[] = "";
-
-  result = empty_string;
-  exact = 0;
-  MALLOC (musts, d->tindex + 1);
-  mp = musts;
-  for (i = 0; i <= d->tindex; ++i)
-    mp[i] = must0;
-  for (i = 0; i <= d->tindex; ++i)
-    {
-      mp[i].in = xmalloc (sizeof *mp[i].in);
-      mp[i].left = xmalloc (2);
-      mp[i].right = xmalloc (2);
-      mp[i].is = xmalloc (2);
-      mp[i].left[0] = mp[i].right[0] = mp[i].is[0] = '\0';
-      mp[i].in[0] = NULL;
-    }
-#ifdef DEBUG
-  fprintf (stderr, "dfamust:\n");
-  for (i = 0; i < d->tindex; ++i)
-    {
-      fprintf (stderr, " %zd:", i);
-      prtok (d->tokens[i]);
-    }
-  putc ('\n', stderr);
-#endif
+
   for (ri = 0; ri < d->tindex; ++ri)
     {
-      switch (t = d->tokens[ri])
+      token t = d->tokens[ri];
+      switch (t)
         {
+        case BEGLINE:
+          mp = allocmust (mp);
+          mp->begline = true;
+          break;
+        case ENDLINE:
+          mp = allocmust (mp);
+          mp->endline = true;
+          break;
         case LPAREN:
         case RPAREN:
           assert (!"neither LPAREN nor RPAREN may appear here");
+
         case EMPTY:
-        case BEGLINE:
-        case ENDLINE:
         case BEGWORD:
         case ENDWORD:
         case LIMWORD:
         case NOTLIMWORD:
         case BACKREF:
-          resetmust (mp);
+        case ANYCHAR:
+        case MBCSET:
+          mp = allocmust (mp);
           break;
+
         case STAR:
         case QMARK:
-          assert (musts < mp);
-          --mp;
           resetmust (mp);
           break;
+
         case OR:
-          assert (&musts[2] <= mp);
           {
             char **new;
-            must *lmp;
-            must *rmp;
+            must *rmp = mp;
+            must *lmp = mp = mp->prev;
             size_t j, ln, rn, n;
 
-            rmp = --mp;
-            lmp = --mp;
             /* Guaranteed to be.  Unlikely, but ...  */
-            if (!STREQ (lmp->is, rmp->is))
-              lmp->is[0] = '\0';
+            if (STREQ (lmp->is, rmp->is))
+              {
+                lmp->begline &= rmp->begline;
+                lmp->endline &= rmp->endline;
+              }
+            else
+              {
+                lmp->is[0] = '\0';
+                lmp->begline = false;
+                lmp->endline = false;
+              }
             /* Left side--easy */
             i = 0;
             while (lmp->left[i] != '\0' && lmp->left[i] == rmp->left[i])
@@ -4027,133 +4062,126 @@ dfamust (struct dfa *d)
               lmp->right[j] = lmp->right[(ln - i) + j];
             lmp->right[j] = '\0';
             new = inboth (lmp->in, rmp->in);
-            if (new == NULL)
-              goto done;
             freelist (lmp->in);
             free (lmp->in);
             lmp->in = new;
+            freemust (rmp);
           }
           break;
+
         case PLUS:
-          assert (musts < mp);
-          --mp;
           mp->is[0] = '\0';
           break;
+
         case END:
-          assert (mp == &musts[1]);
-          for (i = 0; musts[0].in[i] != NULL; ++i)
-            if (strlen (musts[0].in[i]) > strlen (result))
-              result = musts[0].in[i];
-          if (STREQ (result, musts[0].is))
-            exact = 1;
+          assert (!mp->prev);
+          for (i = 0; mp->in[i] != NULL; ++i)
+            if (strlen (mp->in[i]) > strlen (result))
+              result = mp->in[i];
+          if (STREQ (result, mp->is))
+            {
+              exact = true;
+              begline = mp->begline;
+              endline = mp->endline;
+            }
           goto done;
+
         case CAT:
-          assert (&musts[2] <= mp);
           {
-            must *lmp;
-            must *rmp;
+            must *rmp = mp;
+            must *lmp = mp = mp->prev;
 
-            rmp = --mp;
-            lmp = --mp;
             /* In.  Everything in left, plus everything in
                right, plus concatenation of
                left's right and right's left.  */
             lmp->in = addlists (lmp->in, rmp->in);
-            if (lmp->in == NULL)
-              goto done;
             if (lmp->right[0] != '\0' && rmp->left[0] != '\0')
               {
-                char *tp;
-
-                tp = icpyalloc (lmp->right);
-                tp = icatalloc (tp, rmp->left);
-                lmp->in = enlist (lmp->in, tp, strlen (tp));
+                size_t lrlen = strlen (lmp->right);
+                size_t rllen = strlen (rmp->left);
+                char *tp = xmalloc (lrlen + rllen);
+                memcpy (tp, lmp->right, lrlen);
+                memcpy (tp + lrlen, rmp->left, rllen);
+                lmp->in = enlist (lmp->in, tp, lrlen + rllen);
                 free (tp);
-                if (lmp->in == NULL)
-                  goto done;
               }
             /* Left-hand */
             if (lmp->is[0] != '\0')
-              {
-                lmp->left = icatalloc (lmp->left, rmp->left);
-                if (lmp->left == NULL)
-                  goto done;
-              }
+              lmp->left = icatalloc (lmp->left, rmp->left);
             /* Right-hand */
             if (rmp->is[0] == '\0')
               lmp->right[0] = '\0';
             lmp->right = icatalloc (lmp->right, rmp->right);
-            if (lmp->right == NULL)
-              goto done;
             /* Guaranteed to be */
-            if (lmp->is[0] != '\0' && rmp->is[0] != '\0')
+            if ((lmp->is[0] != '\0' || lmp->begline)
+                && (rmp->is[0] != '\0' || rmp->endline))
               {
                 lmp->is = icatalloc (lmp->is, rmp->is);
-                if (lmp->is == NULL)
-                  goto done;
+                lmp->endline = rmp->endline;
               }
             else
-              lmp->is[0] = '\0';
+              {
+                lmp->is[0] = '\0';
+                lmp->begline = false;
+                lmp->endline = false;
+              }
+            freemust (rmp);
           }
           break;
+
+        case '\0':
+          /* Not on *my* shift.  */
+          goto done;
+
         default:
-          if (t < END)
-            {
-              assert (!"oops! t >= END");
-            }
-          else if (t == '\0')
+          mp = allocmust (mp);
+          if (CSET <= t)
             {
-              /* not on *my* shift */
-              goto done;
-            }
-          else if (t >= CSET || !MBS_SUPPORT || t == ANYCHAR || t == MBCSET)
-            {
-              /* easy enough */
-              resetmust (mp);
-            }
-          else
-            {
-              /* plain character */
-              resetmust (mp);
-              mp->is[0] = mp->left[0] = mp->right[0] = t;
-              mp->is[1] = mp->left[1] = mp->right[1] = '\0';
-              mp->in = enlist (mp->in, mp->is, (size_t) 1);
-              if (mp->in == NULL)
-                goto done;
+              /* If T is a singleton, or if case-folding in a unibyte
+                 locale and T's members all case-fold to the same char,
+                 convert T to one of its members.  Otherwise, do
+                 nothing further with T.  */
+              charclass *ccl = &d->charclasses[t - CSET];
+              int j;
+              for (j = 0; j < NOTCHAR; j++)
+                if (tstbit (j, *ccl))
+                  break;
+              if (! (j < NOTCHAR))
+                break;
+              t = j;
+              while (++j < NOTCHAR)
+                if (tstbit (j, *ccl)
+                    && ! (case_fold && !d->multibyte
+                          && toupper (j) == toupper (t)))
+                  break;
+              if (j < NOTCHAR)
+                break;
             }
+          mp->is[0] = mp->left[0] = mp->right[0]
+            = case_fold && !d->multibyte ? toupper (t) : t;
+          mp->is[1] = mp->left[1] = mp->right[1] = '\0';
+          mp->in = enlist (mp->in, mp->is, 1);
           break;
         }
-#ifdef DEBUG
-      fprintf (stderr, " node: %zd:", ri);
-      prtok (d->tokens[ri]);
-      fprintf (stderr, "\n  in:");
-      for (i = 0; mp->in[i]; ++i)
-        fprintf (stderr, " \"%s\"", mp->in[i]);
-      fprintf (stderr, "\n  is: \"%s\"\n", mp->is);
-      fprintf (stderr, "  left: \"%s\"\n", mp->left);
-      fprintf (stderr, "  right: \"%s\"\n", mp->right);
-#endif
-      ++mp;
     }
 done:
-  if (strlen (result))
+  if (*result)
     {
-      MALLOC (dm, 1);
+      dm = xmalloc (sizeof *dm);
       dm->exact = exact;
-      dm->must = xmemdup (result, strlen (result) + 1);
+      dm->begline = begline;
+      dm->endline = endline;
+      dm->must = xstrdup (result);
       dm->next = d->musts;
       d->musts = dm;
     }
-  mp = musts;
-  for (i = 0; i <= d->tindex; ++i)
+
+  while (mp)
     {
-      freelist (mp[i].in);
-      free (mp[i].in);
-      free (mp[i].left);
-      free (mp[i].right);
-      free (mp[i].is);
+      must *prev = mp->prev;
+      freemust (mp);
+      mp = prev;
     }
-  free (mp);
 }
 
 struct dfa *
diff --git a/dfa.h b/dfa.h
index c58485a7..4eb42968 100644
--- a/dfa.h
+++ b/dfa.h
@@ -1,5 +1,5 @@
 /* dfa.h - declarations for GNU deterministic regexp compiler
-   Copyright (C) 1988, 1998, 2007, 2009-2013 Free Software Foundation, Inc.
+   Copyright (C) 1988, 1998, 2007, 2009-2014 Free Software Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -19,13 +19,20 @@
 /* Written June, 1988 by Mike Haertel */
 
 #include <regex.h>
+#ifdef HAVE_STDBOOL_H
+#include <stdbool.h>
+#else
+#include "missing_d/gawkbool.h"
+#endif /* HAVE_STDBOOL_H */
 #include <stddef.h>
 
 /* Element of a list of strings, at least one of which is known to
    appear in any R.E. matching the DFA. */
 struct dfamust
 {
-  int exact;
+  bool exact;
+  bool begline;
+  bool endline;
   char *must;
   struct dfamust *next;
 };
@@ -68,6 +75,15 @@ extern void dfacomp (char const *, size_t, struct dfa *, int);
 extern char *dfaexec (struct dfa *d, char const *begin, char *end,
                       int newline, size_t *count, int *backref);
 
+/* Return a superset for D.  The superset matches everything that D
+   matches, along with some other strings (though the latter should be
+   rare, for efficiency reasons).  Return a null pointer if no useful
+   superset is available.  */
+extern struct dfa *dfasuperset (struct dfa const *d) _GL_ATTRIBUTE_PURE;
+
+/* The DFA is likely to be fast.  */
+extern bool dfaisfast (struct dfa const *) _GL_ATTRIBUTE_PURE;
+
 /* Free the storage held by the components of a struct dfa. */
 extern void dfafree (struct dfa *);
 
@@ -99,3 +115,5 @@ extern void dfawarn (const char *);
    takes a single argument, a NUL-terminated string describing the error.
    The user must supply a dfaerror.  */
 extern _Noreturn void dfaerror (const char *);
+
+extern int using_utf8 (void);
diff --git a/doc/ChangeLog b/doc/ChangeLog
index 10f0165c..5e7d4808 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,8 +1,318 @@
+2014-06-22         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Typo fixes and minor corrections.
+
+2014-06-19         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Add thanks to Patrice Dumas and to Karl Berry.
+	Per request from Hermann Peifer, try to clarify how local variables
+	in functions are initialized.
+
+2014-06-18         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Split 6.1.4 into subsections. Other minor fixes.
+
+2014-06-17         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Finish adding exerices.
+	Rework chapter 15 on floating point and MPFR.
+	Spell check. Fix menues.
+
+2014-06-16         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Start adding exercises.
+
+2014-06-15         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Finish up summaries. Improvements in mystrtonum().
+
+2014-06-13         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Fix typos from changes of 3 June when macros were
+	added for filename, data file, etc. Ooops.
+
+2014-06-12         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: More "Summary" sections. Through chapter 14.
+
+2014-06-11         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: More "Summary" sections. Through chapter 10.
+
+2014-06-10         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Update docbook figure markup.
+
+2014-06-09         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: More "Summary" sections.
+	Judiciously arrange for full xrefs in docbook in a few spots.
+
+2014-06-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Start adding "Summary" sections.
+
+2014-06-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Restore macros for file name vs. filename etc.
+	Go through @if... and @ifnot... and fix them up too. Other misc.
+	cleanup.
+
+2014-05-29         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Remove some obsolete bits, fix up some other 
+	minor stuff.
+
+2014-05-27         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Edits through the end!
+
+2014-05-25         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Edits through Appendix A.
+	* gawktexi.in: Tweak nested lists for docbook.
+
+2014-05-24         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in (Staying current): New section.
+
+2014-05-22         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* gawktexi.in (BEGINFILE/ENDFILE): Update doc for getline - any
+	redirected form is allowed inside BEGINFILE/ENDFILE.
+
+2014-05-21         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Add comments for where we need full xrefs in
+	docbook.
+
+2014-05-20         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Misc improvements for docbook, consistency
+	in table and figure captions.
+
+2014-05-17         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Edits through Chapter 16.
+
+2014-05-16         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Edits through Chapter 14.
+
+2014-05-15         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Fix displays for docbook, edits through Chapter 11.
+
+2014-05-14         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Fix real preface for docbook.
+
+2014-05-13         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Complete formatting for FOR_PRINT and not FOR_PRINT.
+
+2014-05-07         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Docbook edits for preface and parts.
+	Document AWKBUFSIZE.
+
+2014-05-05         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Editing progress. Through Chapter 9.
+
+2014-05-05         Michal Jaegermann     <michal@harddata.com>
+
+	* array-elements.fig: Fix subscripts to be aligned
+	horizontally.  Regenerate the other files.
+
+2014-05-02         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Editing progress. Through Chapter 8.
+	* array-elements.eps, array-elements.fig, array-elements.pdf,
+	array-elements.png array-elements.txt: New files.
+	* Makefile.am (EXTRA_DIST): Add them.
+
+2014-04-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Editing progress. Through Chapter 5.
+	* gawktexi.in: Editing progress. Through Chapter 6 and into
+	Chapter 7.
+
+2014-04-29         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Editing progress. Through Chapter 3.
+
+2014-04-24         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Start on revisions.
+
+2014-04-17         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawk.1: Remove the bit about single character programs overflowing
+	the parse stack. It doesn't seem to be true anymore.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* texinfo.tex: Update to latest.
+	* awkcard.in: Update copyright, patchlevel in download.
+	* gawktexi.in: Update patchlevel, update month, spell check.
+
+2014-03-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Cleanups to docbook, finish math stuff.
+
+2014-03-28         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Minor cleanups to the indexing.
+
+	Unrelated:
+
+	* gawktexi.in: Merge in changes needed for creating valid
+	DocBook XML. Works with post-5.2 Texinfo and dblatex!
+
+2014-03-27         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Finish the massive indexing improvements such that
+	functions are indexed the way I want in TeX and the way Eli
+	wants in Info.
+
+	Unrelated:
+
+	* gawktexi.in: Add a note in extension chapter that lookup of
+	PROCINFO can fail.
+
+2014-03-27         Eli Zaretskii             <eliz@gnu.org>
+
+	* gawktexi.in: First round of massive indexing improvements.
+
+2014-03-27         Antonio Giovanni Colombo   <azc100@gmail.com>
+
+	* gawktexi.in: Redo all the examples using BBS-list to a different
+	file that doesn't use out-of-date concepts.
+
+2014-03-10         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Finish indexing improvements. (For now, anyway.)
+
+	Unrelated:
+
+	* gawk.1: Document the quote flag! (Better late than never.)
+	* awkcard.in: Update documentation of quote flag.
+
+2014-03-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Minor edits to the discussion of the memory allocation
+	functions.
+
+2014-03-08         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* gawktexi.in: Document new extension API functions api_malloc,
+	api_calloc, api_realloc, and api_free.
+
+2014-03-07         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Indexing improvements.
+
+2014-03-02         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawktexi.in: Remove paragraph about obsolete VMS
+	  compilers.  Update reference about building PCSI kit.
+
+2014-02-27         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Lots of small fixes throughout, update of
+	profiling output.  Finished fixes needed before a release.
+
+2014-02-20         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Add a quote to the alarm clock program.
+
+2014-02-15         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* texinfo.tex: Update to latest.
+
+2014-02-14         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Lots of small edits.
+
+2014-02-07         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: More minor fixes, update UPDATE_MONTH.
+
+2014-02-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: More minor fixes, in indexing.
+
+2014-02-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in, gawkinet.texi: Minor fixes, mostly in indexing.
+	* texinfo.tex: Update to latest.
+
+2014-01-31         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Add `()' to names of extension functions in indexing
+	commands and in one place in the text. Consistency, don'tcha know.
+
+2014-01-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Add a few missing STARTOFRANGE comments.
+	* gawk.1: Note that `(i, j) in array' doesn't work in for loops.
+	Update the copyright year.
+
+2014-01-28         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Update info for Anders Wallin.
+
+2014-01-25         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* texinfo.tex: Updated to current version.
+	* gawktexi.in: Add magic stuff so that PDFs have "dark red"
+	links like before.
+
+2014-01-23         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in (Feature History): New node.
+	(Common Extensions): Update features now in mawk, too.
+
+2014-12-14         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawktexi.in: Add information on building VMS PCSI kit.
+
+2014-01-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in (Full Line Fields): New node.
+	Update copyright year.
+
+2013-12-29         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawktexi.in: VMS dynamic extensions.
+
+2013-12-26         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: More minor additions / fixes.
+	(Bugs): Add John Malmberg for VMS. Other minor edits.
+
+2013-12-25         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: Minor additions / fixes.
+
+2013-12-23         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawktexi.in: Document the VMS exit status encoding.
+
 2013-12-21         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* gawktexi.in (Additional Configuration Options): Document
 	the --disable-extensions option.
 
+2013-12-16         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawktexi.in: Updates to VMS sections.
+
 2013-12-12         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* gawktexi.in: Fix the presentation of asort() and asorti().
diff --git a/doc/Makefile.am b/doc/Makefile.am
index 12692bd0..86321bbc 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -36,6 +36,8 @@ EXTRA_DIST = ChangeLog ChangeLog.0 README.card ad.block setter.outline \
 	api-figure2.png api-figure2.txt \
 	api-figure3.eps api-figure3.fig api-figure3.pdf \
 	api-figure3.png api-figure3.txt \
+	array-elements.eps array-elements.fig array-elements.pdf \
+	array-elements.png array-elements.txt \
 	gawktexi.in sidebar.awk \
 	general-program.eps general-program.fig general-program.pdf \
 	general-program.png general-program.txt \
diff --git a/doc/Makefile.in b/doc/Makefile.in
index 52e5f873..abaf5601 100644
--- a/doc/Makefile.in
+++ b/doc/Makefile.in
@@ -350,6 +350,8 @@ EXTRA_DIST = ChangeLog ChangeLog.0 README.card ad.block setter.outline \
 	api-figure2.png api-figure2.txt \
 	api-figure3.eps api-figure3.fig api-figure3.pdf \
 	api-figure3.png api-figure3.txt \
+	array-elements.eps array-elements.fig array-elements.pdf \
+	array-elements.png array-elements.txt \
 	gawktexi.in sidebar.awk \
 	general-program.eps general-program.fig general-program.pdf \
 	general-program.png general-program.txt \
diff --git a/doc/array-elements.eps b/doc/array-elements.eps
new file mode 100644
index 00000000..041c0b39
--- /dev/null
+++ b/doc/array-elements.eps
@@ -0,0 +1,158 @@
+%!PS-Adobe-3.0 EPSF-3.0
+%%Title: array-elements.fig
+%%Creator: fig2dev Version 3.2 Patchlevel 5d
+%%CreationDate: Sun May  4 22:46:26 2014
+%%BoundingBox: 0 0 379 76
+%Magnification: 1.0000
+%%EndComments
+%%BeginProlog
+/$F2psDict 200 dict def
+$F2psDict begin
+$F2psDict /mtrx matrix put
+/col-1 {0 setgray} bind def
+/col0 {0.000 0.000 0.000 srgb} bind def
+/col1 {0.000 0.000 1.000 srgb} bind def
+/col2 {0.000 1.000 0.000 srgb} bind def
+/col3 {0.000 1.000 1.000 srgb} bind def
+/col4 {1.000 0.000 0.000 srgb} bind def
+/col5 {1.000 0.000 1.000 srgb} bind def
+/col6 {1.000 1.000 0.000 srgb} bind def
+/col7 {1.000 1.000 1.000 srgb} bind def
+/col8 {0.000 0.000 0.560 srgb} bind def
+/col9 {0.000 0.000 0.690 srgb} bind def
+/col10 {0.000 0.000 0.820 srgb} bind def
+/col11 {0.530 0.810 1.000 srgb} bind def
+/col12 {0.000 0.560 0.000 srgb} bind def
+/col13 {0.000 0.690 0.000 srgb} bind def
+/col14 {0.000 0.820 0.000 srgb} bind def
+/col15 {0.000 0.560 0.560 srgb} bind def
+/col16 {0.000 0.690 0.690 srgb} bind def
+/col17 {0.000 0.820 0.820 srgb} bind def
+/col18 {0.560 0.000 0.000 srgb} bind def
+/col19 {0.690 0.000 0.000 srgb} bind def
+/col20 {0.820 0.000 0.000 srgb} bind def
+/col21 {0.560 0.000 0.560 srgb} bind def
+/col22 {0.690 0.000 0.690 srgb} bind def
+/col23 {0.820 0.000 0.820 srgb} bind def
+/col24 {0.500 0.190 0.000 srgb} bind def
+/col25 {0.630 0.250 0.000 srgb} bind def
+/col26 {0.750 0.380 0.000 srgb} bind def
+/col27 {1.000 0.500 0.500 srgb} bind def
+/col28 {1.000 0.630 0.630 srgb} bind def
+/col29 {1.000 0.750 0.750 srgb} bind def
+/col30 {1.000 0.880 0.880 srgb} bind def
+/col31 {1.000 0.840 0.000 srgb} bind def
+
+end
+
+/cp {closepath} bind def
+/ef {eofill} bind def
+/gr {grestore} bind def
+/gs {gsave} bind def
+/sa {save} bind def
+/rs {restore} bind def
+/l {lineto} bind def
+/m {moveto} bind def
+/rm {rmoveto} bind def
+/n {newpath} bind def
+/s {stroke} bind def
+/sh {show} bind def
+/slc {setlinecap} bind def
+/slj {setlinejoin} bind def
+/slw {setlinewidth} bind def
+/srgb {setrgbcolor} bind def
+/rot {rotate} bind def
+/sc {scale} bind def
+/sd {setdash} bind def
+/ff {findfont} bind def
+/sf {setfont} bind def
+/scf {scalefont} bind def
+/sw {stringwidth} bind def
+/tr {translate} bind def
+/tnt {dup dup currentrgbcolor
+  4 -2 roll dup 1 exch sub 3 -1 roll mul add
+  4 -2 roll dup 1 exch sub 3 -1 roll mul add
+  4 -2 roll dup 1 exch sub 3 -1 roll mul add srgb}
+  bind def
+/shd {dup dup currentrgbcolor 4 -2 roll mul 4 -2 roll mul
+  4 -2 roll mul srgb} bind def
+/$F2psBegin {$F2psDict begin /$F2psEnteredState save def} def
+/$F2psEnd {$F2psEnteredState restore end} def
+
+/pageheader {
+save
+newpath 0 76 moveto 0 0 lineto 379 0 lineto 379 76 lineto closepath clip newpath
+-203.3 199.4 translate
+1 -1 scale
+$F2psBegin
+10 setmiterlimit
+0 slj 0 slc
+ 0.06299 0.06299 sc
+} bind def
+/pagefooter {
+$F2psEnd
+restore
+} bind def
+%%EndProlog
+pageheader
+%
+% Fig objects follow
+%
+% 
+% here starts figure with depth 50
+% Polyline
+0 slj
+0 slc
+7.500 slw
+n 4455 1980 m 4455 2700 l 4455 2655 l
+ 4455 2700 l gs col0 s gr 
+% Polyline
+n 6075 1980 m
+ 6075 2700 l gs col0 s gr 
+% Polyline
+n 7425 1980 m
+ 7425 2700 l gs col0 s gr 
+/Courier-Bold ff 180.00 scf sf
+3735 2340 m
+gs 1 -1 sc (8) col0 sh gr
+/Courier-Bold ff 180.00 scf sf
+5175 2340 m
+gs 1 -1 sc ("foo") col0 sh gr
+/Courier-Bold ff 180.00 scf sf
+6795 2340 m
+gs 1 -1 sc ("") col0 sh gr
+/Courier-Bold ff 180.00 scf sf
+7875 2340 m
+gs 1 -1 sc (30) col0 sh gr
+/Times-Roman ff 180.00 scf sf
+3735 3150 m
+gs 1 -1 sc (0) col0 sh gr
+/Times-Roman ff 180.00 scf sf
+5175 3150 m
+gs 1 -1 sc (1) col0 sh gr
+/Times-Roman ff 180.00 scf sf
+6795 3150 m
+gs 1 -1 sc (2) col0 sh gr
+/Times-Roman ff 180.00 scf sf
+7875 3150 m
+gs 1 -1 sc (3) col0 sh gr
+/Times-Roman ff 180.00 scf sf
+8730 2340 m
+gs 1 -1 sc (Value) col0 sh gr
+/Times-Roman ff 180.00 scf sf
+8730 3150 m
+gs 1 -1 sc (Index) col0 sh gr
+% here ends figure;
+% 
+% here starts figure with depth 40
+% Polyline
+0 slj
+0 slc
+7.500 slw
+n 3240 1980 m 8415 1980 l 8415 2700 l 3240 2700 l
+ cp gs col0 s gr 
+% here ends figure;
+pagefooter
+showpage
+%%Trailer
+%EOF
diff --git a/doc/array-elements.fig b/doc/array-elements.fig
new file mode 100644
index 00000000..63b5ffbf
--- /dev/null
+++ b/doc/array-elements.fig
@@ -0,0 +1,27 @@
+#FIG 3.2  Produced by xfig version 3.2.5b
+Landscape
+Center
+Metric
+A4      
+100.00
+Single
+-2
+1200 2
+2 2 0 1 0 7 40 -1 -1 0.000 0 0 -1 0 0 5
+	 3240 1980 8415 1980 8415 2700 3240 2700 3240 1980
+2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 4
+	 4455 1980 4455 2700 4455 2655 4455 2700
+2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
+	 6075 1980 6075 2700
+2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
+	 7425 1980 7425 2700
+4 0 0 50 -1 14 12 0.0000 4 120 120 3735 2340 8\001
+4 0 0 50 -1 14 12 0.0000 4 120 600 5175 2340 "foo"\001
+4 0 0 50 -1 14 12 0.0000 4 60 240 6795 2340 ""\001
+4 0 0 50 -1 14 12 0.0000 4 120 240 7875 2340 30\001
+4 0 0 50 -1 0 12 0.0000 4 135 105 3735 3150 0\001
+4 0 0 50 -1 0 12 0.0000 4 135 105 5175 3150 1\001
+4 0 0 50 -1 0 12 0.0000 4 135 105 6795 3150 2\001
+4 0 0 50 -1 0 12 0.0000 4 135 105 7875 3150 3\001
+4 0 0 50 -1 0 12 0.0000 4 135 480 8730 2340 Value\001
+4 0 0 50 -1 0 12 0.0000 4 135 465 8730 3150 Index\001
diff --git a/doc/array-elements.pdf b/doc/array-elements.pdf
new file mode 100644
index 00000000..328cbd1a
--- /dev/null
+++ b/doc/array-elements.pdf
diff --git a/doc/array-elements.png b/doc/array-elements.png
new file mode 100644
index 00000000..b57d66b7
--- /dev/null
+++ b/doc/array-elements.png
diff --git a/doc/array-elements.txt b/doc/array-elements.txt
new file mode 100644
index 00000000..8906318a
--- /dev/null
+++ b/doc/array-elements.txt
@@ -0,0 +1,4 @@
++---------+---------+--------+---------+
+|    8    |  "foo"  |   ""   |    30   |    @r{Value}
++---------+---------+--------+---------+
+     0         1         2         3        @r{Index}
diff --git a/doc/awkcard.in b/doc/awkcard.in
index 610032b7..ca28f0a7 100644
--- a/doc/awkcard.in
+++ b/doc/awkcard.in
@@ -1,7 +1,7 @@
 .\" AWK Reference Card --- Arnold Robbins, arnold@skeeve.com
 .\"
 .\" Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-.\" 2003, 2004, 2005, 2007, 2009, 2010, 2011, 2012, 2013
+.\" 2003, 2004, 2005, 2007, 2009, 2010, 2011, 2012, 2013, 2014
 .\" Free Software Foundation, Inc.
 .\" 
 .\" Permission is granted to make and distribute verbatim copies of
@@ -100,7 +100,7 @@ Brian Kernighan and Michael Brennan who reviewed it.
 \*(CD
 .SL
 .nf
-\*(FRCopyright \(co 1996\(en2005, 2007, 2009\(en2013
+\*(FRCopyright \(co 1996\(en2005, 2007, 2009\(en2014
 Free Software Foundation, Inc.
 .nf
 .BT
@@ -1493,7 +1493,8 @@ Only has an effect when the field width is wider
 than the value to be printed.
 T}
 \*(CB\*(FC'\*(FR	T{
-Use the locale's thousands separator for \*(FC%d\fP, \*(FC%i\fP, and \*(FC%u\fP.\*(CD
+Use the locale's thousands separator and decimal
+point characters.\*(CD
 T}
 \*(FIwidth\fP	T{
 Pad the field to this width. The field is normally
@@ -1938,7 +1939,7 @@ to use the current domain.\*(CB
 .ES
 .nf
 \*(CDHost: \*(FCftp.gnu.org\*(FR
-File: \*(FC/gnu/gawk/gawk-4.1.0.tar.gz\fP
+File: \*(FC/gnu/gawk/gawk-4.1.1.tar.gz\fP
 .in +.2i
 .fi
 GNU \*(AK (\*(GK). There may be a later version.
@@ -1968,8 +1969,8 @@ maintains it.\*(CX
 .\" --- Copying Permissions
 .ES
 .fi
-\*(CDCopyright \(co 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
-2007, 2009, 2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+\*(CDCopyright \(co 1996\(en2005,
+2007, 2009\(en2014 Free Software Foundation, Inc.
 .sp .5   
 Permission is granted to make and distribute verbatim copies of this
 reference card provided the copyright notice and this permission notice
diff --git a/doc/gawk.1 b/doc/gawk.1
index 8d343024..e3275e87 100644
--- a/doc/gawk.1
+++ b/doc/gawk.1
@@ -13,7 +13,7 @@
 .		if \w'\(rq' .ds rq "\(rq
 .	\}
 .\}
-.TH GAWK 1 "Aug 15 2013" "Free Software Foundation" "Utility Commands"
+.TH GAWK 1 "Apr 17 2014" "Free Software Foundation" "Utility Commands"
 .SH NAME
 gawk \- pattern scanning and processing language
 .SH SYNOPSIS
@@ -1370,6 +1370,11 @@ The
 construct may also be used in a
 .B for
 loop to iterate over all the elements of an array.
+However, the
+.B "(i, j) in array"
+construct only works in tests, not in
+.B for
+loops.
 .PP
 An element may be deleted from an array using the
 .B delete
@@ -2449,6 +2454,15 @@ This applies only to the numeric output formats.
 This flag only has an effect when the field width is wider than the
 value to be printed.
 .TP
+.B '
+A single quote character instructs
+.I gawk
+to insert the locale's thousands-separator character
+into decimal numbers, and to also use the locale's
+decimal point character with floating point formats.
+This requires correct locale support in the C library
+and in the definition of the current locale.
+.TP
 .I width
 The field should be padded to this width.  The field is normally padded
 with spaces.  With the
@@ -3898,11 +3912,6 @@ The
 .B \-F
 option is not necessary given the command line variable assignment feature;
 it remains only for backwards compatibility.
-.PP
-Syntactically invalid single character programs tend to overflow
-the parse stack, generating a rather unhelpful message.  Such programs
-are surprisingly difficult to diagnose in the completely general case,
-and the effort to do so really is not worth it.
 .SH SEE ALSO
 .IR egrep (1),
 .IR sed (1),
@@ -3968,7 +3977,7 @@ We thank him.
 .SH COPYING PERMISSIONS
 Copyright \(co 1989, 1991, 1992, 1993, 1994, 1995, 1996,
 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2005, 2007, 2009,
-2010, 2011, 2012, 2013
+2010, 2011, 2012, 2013, 2014
 Free Software Foundation, Inc.
 .PP
 Permission is granted to make and distribute verbatim copies of
diff --git a/doc/gawk.info b/doc/gawk.info
index 845d3be3..44568736 100644
--- a/doc/gawk.info
+++ b/doc/gawk.info
@@ -9,13 +9,12 @@ START-INFO-DIR-ENTRY
 * awk: (gawk)Invoking gawk.                     Text scanning and processing.
 END-INFO-DIR-ENTRY
 
-   Copyright (C) 1989, 1991, 1992, 1993, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2007, 2009, 2010, 2011, 2012, 2013 Free
-Software Foundation, Inc.
+   Copyright (C) 1989, 1991, 1992, 1993, 1996-2005, 2007, 2009-2014
+Free Software Foundation, Inc.
 
 
    This is Edition 4.1 of `GAWK: Effective AWK Programming: A User's
-Guide for GNU Awk', for the 4.1.0 (or later) version of the GNU
+Guide for GNU Awk', for the 4.1.1 (or later) version of the GNU
 implementation of AWK.
 
    Permission is granted to copy, distribute and/or modify this document
@@ -41,13 +40,12 @@ General Introduction
 This file documents `awk', a program that you can use to select
 particular records in a file and perform operations upon them.
 
-   Copyright (C) 1989, 1991, 1992, 1993, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2007, 2009, 2010, 2011, 2012, 2013 Free
-Software Foundation, Inc.
+   Copyright (C) 1989, 1991, 1992, 1993, 1996-2005, 2007, 2009-2014
+Free Software Foundation, Inc.
 
 
    This is Edition 4.1 of `GAWK: Effective AWK Programming: A User's
-Guide for GNU Awk', for the 4.1.0 (or later) version of the GNU
+Guide for GNU Awk', for the 4.1.1 (or later) version of the GNU
 implementation of AWK.
 
    Permission is granted to copy, distribute and/or modify this document
@@ -128,8 +126,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         includes command-line syntax.
 * One-shot::                            Running a short throwaway
                                         `awk' program.
-* Read Terminal::                       Using no input files (input from
-                                        terminal instead).
+* Read Terminal::                       Using no input files (input from the
+                                        keyboard instead).
 * Long::                                Putting permanent `awk'
                                         programs in files.
 * Executable Scripts::                  Making self-contained `awk'
@@ -151,6 +149,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Other Features::                      Other Features of `awk'.
 * When::                                When to use `gawk' and when to
                                         use other things.
+* Intro Summary::                       Summary of the introduction.
 * Command Line::                        How to run `awk'.
 * Options::                             Command-line options and their
                                         meanings.
@@ -172,6 +171,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         program.
 * Obsolete::                            Obsolete Options and/or features.
 * Undocumented::                        Undocumented Options and Features.
+* Invoking Summary::                    Invocation summary.
 * Regexp Usage::                        How to Use Regular Expressions.
 * Escape Sequences::                    How to write nonprinting characters.
 * Regexp Operators::                    Regular Expression Operators.
@@ -180,8 +180,12 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Case-sensitivity::                    How to do case-insensitive matching.
 * Leftmost Longest::                    How much text matches.
 * Computed Regexps::                    Using Dynamic Regexps.
+* Regexp Summary::                      Regular expressions summary.
 * Records::                             Controlling how data is split into
                                         records.
+* awk split records::                   How standard `awk' splits
+                                        records.
+* gawk split records::                  How `gawk' splits records.
 * Fields::                              An introduction to fields.
 * Nonconstant Fields::                  Nonconstant Field Numbers.
 * Changing Fields::                     Changing the Contents of a Field.
@@ -193,6 +197,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         field.
 * Command Line Field Separator::        Setting `FS' from the
                                         command-line.
+* Full Line Fields::                    Making the full line be a single
+                                        field.
 * Field Splitting Summary::             Some final points and a summary table.
 * Constant Size::                       Reading constant width data.
 * Splitting By Content::                Defining Fields By Content
@@ -218,6 +224,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Read Timeout::                        Reading input with a timeout.
 * Command line directories::            What happens if you put a directory on
                                         the command line.
+* Input Summary::                       Input summary.
+* Input Exercises::                     Exercises.
 * Print::                               The `print' statement.
 * Print Examples::                      Simple examples of `print'
                                         statements.
@@ -241,6 +249,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Special Caveats::                     Things to watch out for.
 * Close Files And Pipes::               Closing Input and Output Files and
                                         Pipes.
+* Output Summary::                      Output summary.
+* Output exercises::                    Exercises.
 * Values::                              Constants, Variables, and Regular
                                         Expressions.
 * Constants::                           String, numeric and regexp constants.
@@ -256,6 +266,9 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         This is an advanced method of input.
 * Conversion::                          The conversion of strings to numbers
                                         and vice versa.
+* Strings And Numbers::                 How `awk' Converts Between
+                                        Strings And Numbers.
+* Locale influences conversions::       How the locale may affect conversions.
 * All Operators::                       `gawk''s operators.
 * Arithmetic Ops::                      Arithmetic operations (`+',
                                         `-', etc.)
@@ -283,6 +296,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Function Calls::                      A function call is an expression.
 * Precedence::                          How various operators nest.
 * Locales::                             How the locale affects things.
+* Expressions Summary::                 Expressions summary.
 * Pattern Overview::                    What goes into a pattern.
 * Regexp Patterns::                     Using regexps as patterns.
 * Expression Patterns::                 Any expression can be used as a
@@ -329,6 +343,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         gives you information.
 * ARGC and ARGV::                       Ways to use `ARGC' and
                                         `ARGV'.
+* Pattern Action Summary::              Patterns and Actions summary.
 * Array Basics::                        The basics of arrays.
 * Array Intro::                         Introduction to Arrays
 * Reference to Elements::               How to examine one element of an
@@ -351,6 +366,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         `awk'.
 * Multiscanning::                       Scanning multidimensional arrays.
 * Arrays of Arrays::                    True multidimensional arrays.
+* Arrays Summary::                      Summary of arrays.
 * Built-in::                            Summarizes the built-in functions.
 * Calling Built-in::                    How to call built-in functions.
 * Numeric Functions::                   Functions that work with numbers,
@@ -385,6 +401,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         runtime.
 * Indirect Calls::                      Choosing the function to call at
                                         runtime.
+* Functions Summary::                   Summary of functions.
 * Library Names::                       How to best name private global
                                         variables in library functions.
 * General Functions::                   Functions that are of general use.
@@ -419,6 +436,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Group Functions::                     Functions for getting group
                                         information.
 * Walking Arrays::                      A function to walk arrays of arrays.
+* Library Functions Summary::           Summary of library functions.
+* Library exercises::                   Exercises.
 * Running Examples::                    How to run these examples.
 * Clones::                              Clones of common utilities.
 * Cut Program::                         The `cut' utility.
@@ -448,6 +467,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Anagram Program::                     Finding anagrams from a dictionary.
 * Signature Program::                   People do amazing things with too much
                                         time on their hands.
+* Programs Summary::                    Summary of programs.
+* Programs Exercises::                  Exercises.
 * Nondecimal Data::                     Allowing nondecimal input data.
 * Array Sorting::                       Facilities for controlling array
                                         traversal and sorting arrays.
@@ -459,6 +480,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * TCP/IP Networking::                   Using `gawk' for network
                                         programming.
 * Profiling::                           Profiling your `awk' programs.
+* Advanced Features Summary::           Summary of advanced features.
 * I18N and L10N::                       Internationalization and Localization.
 * Explaining gettext::                  How GNU `gettext' works.
 * Programmer i18n::                     Features for the programmer.
@@ -470,6 +492,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * I18N Example::                        A simple i18n example.
 * Gawk I18N::                           `gawk' is also
                                         internationalized.
+* I18N Summary::                        Summary of I18N stuff.
 * Debugging::                           Introduction to `gawk'
                                         debugger.
 * Debugging Concepts::                  Debugging in General.
@@ -488,31 +511,23 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Miscellaneous Debugger Commands::     Miscellaneous Commands.
 * Readline Support::                    Readline support.
 * Limitations::                         Limitations and future plans.
-* General Arithmetic::                  An introduction to computer
-                                        arithmetic.
-* Floating Point Issues::               Stuff to know about floating-point
-                                        numbers.
-* String Conversion Precision::         The String Value Can Lie.
-* Unexpected Results::                  Floating Point Numbers Are Not
-                                        Abstract Numbers.
-* POSIX Floating Point Problems::       Standards Versus Existing Practice.
-* Integer Programming::                 Effective integer programming.
-* Floating-point Programming::          Effective Floating-point Programming.
-* Floating-point Representation::       Binary floating-point representation.
-* Floating-point Context::              Floating-point context.
-* Rounding Mode::                       Floating-point rounding mode.
-* Gawk and MPFR::                       How `gawk' provides
-                                        arbitrary-precision arithmetic.
-* Arbitrary Precision Floats::          Arbitrary Precision Floating-point
-                                        Arithmetic with `gawk'.
-* Setting Precision::                   Setting the working precision.
-* Setting Rounding Mode::               Setting the rounding mode.
-* Floating-point Constants::            Representing floating-point constants.
-* Changing Precision::                  Changing the precision of a number.
-* Exact Arithmetic::                    Exact arithmetic with floating-point
-                                        numbers.
+* Debugging Summary::                   Debugging summary.
+* Computer Arithmetic::                 A quick intro to computer math.
+* Math Definitions::                    Defining terms used.
+* MPFR features::                       The MPFR features in `gawk'.
+* FP Math Caution::                     Things to know.
+* Inexactness of computations::         Floating point math is not exact.
+* Inexact representation::              Numbers are not exactly represented.
+* Comparing FP Values::                 How to compare floating point values.
+* Errors accumulate::                   Errors get bigger as they go.
+* Getting Accuracy::                    Getting more accuracy takes some work.
+* Try To Round::                        Add digits and round.
+* Setting precision::                   How to set the precision.
+* Setting the rounding mode::           How to set the rounding mode.
 * Arbitrary Precision Integers::        Arbitrary Precision Integer Arithmetic
                                         with `gawk'.
+* POSIX Floating Point Problems::       Standards Versus Existing Practice.
+* Floating point summary::              Summary of floating point discussion.
 * Extension Intro::                     What is an extension.
 * Plugin License::                      A note about licensing.
 * Extension Mechanism Outline::         An outline of how it works.
@@ -520,6 +535,7 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Extension API Functions Introduction:: Introduction to the API functions.
 * General Data Types::                  The data types.
 * Requesting Values::                   How to get a value.
+* Memory Allocation Functions::         Functions for allocating memory.
 * Constructor Functions::               Functions for creating values.
 * Registration Functions::              Functions to register things with
                                         `gawk'.
@@ -573,6 +589,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Extension Sample Time::               An interface to `gettimeofday()'
                                         and `sleep()'.
 * gawkextlib::                          The `gawkextlib' project.
+* Extension summary::                   Extension summary.
+* Extension Exercises::                 Exercises.
 * V7/SVR3.1::                           The major changes between V7 and
                                         System V Release 3.1.
 * SVR4::                                Minor changes between System V
@@ -582,11 +600,14 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         version of `awk'.
 * POSIX/GNU::                           The extensions in `gawk' not
                                         in POSIX `awk'.
+* Feature History::                     The history of the features in
+                                        `gawk'.
 * Common Extensions::                   Common Extensions Summary.
 * Ranges and Locales::                  How locales used to affect regexp
                                         ranges.
 * Contributors::                        The major contributors to
                                         `gawk'.
+* History summary::                     History summary.
 * Gawk Distribution::                   What is in the `gawk'
                                         distribution.
 * Getting::                             How to get the distribution.
@@ -614,14 +635,18 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * VMS Installation::                    Installing `gawk' on VMS.
 * VMS Compilation::                     How to compile `gawk' under
                                         VMS.
+* VMS Dynamic Extensions::              Compiling `gawk' dynamic
+                                        extensions on VMS.
 * VMS Installation Details::            How to install `gawk' under
                                         VMS.
 * VMS Running::                         How to run `gawk' under VMS.
+* VMS GNV::                             The VMS GNV Project.
 * VMS Old Gawk::                        An old version comes with some VMS
                                         systems.
 * Bugs::                                Reporting Problems and Bugs.
 * Other Versions::                      Other freely available `awk'
                                         implementations.
+* Installation summary::                Summary of installation.
 * Compatibility Mode::                  How to disable certain `gawk'
                                         extensions.
 * Additions::                           Making Additions To `gawk'.
@@ -630,8 +655,8 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
                                         `gawk'.
 * New Ports::                           Porting `gawk' to a new
                                         operating system.
-* Derived Files::                       Why derived files are kept in the
-                                        `git' repository.
+* Derived Files::                       Why derived files are kept in the Git
+                                        repository.
 * Future Extensions::                   New features that may be implemented
                                         one day.
 * Implementation Limitations::          Some limitations of the
@@ -642,18 +667,19 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
 * Extension Other Design Decisions::    Some other design decisions.
 * Extension Future Growth::             Some room for future growth.
 * Old Extension Mechanism::             Some compatibility for old extensions.
+* Notes summary::                       Summary of implementation notes.
 * Basic High Level::                    The high level view.
 * Basic Data Typing::                   A very quick intro to data types.
 
-                  To Miriam, for making me complete.
-
-                  To Chana, for the joy you bring us.
+   To my parents, for their love, and for the wonderful example they
+set for me.
 
-                To Rivka, for the exponential increase.
+   To my wife Miriam, for making me complete.  Thank you for building
+your life together with me.
 
-                  To Nachum, for the added dimension.
+   To our children Chana, Rivka, Nachum and Malka, for enrichening our
+lives in innumerable ways.
 
-                   To Malka, for the new beginning.
 
 File: gawk.info,  Node: Foreword,  Next: Preface,  Prev: Top,  Up: Top
 
@@ -785,6 +811,10 @@ and other `awk' implementations.
 
    * Perform simple network communications
 
+   * Profile and debug `awk' programs.
+
+   * Extend the language with functions written in C or C++.
+
    This Info file teaches you about the `awk' language and how you can
 use it effectively.  You should already be familiar with basic system
 commands, such as `cat' and `ls',(2) as well as basic shell facilities,
@@ -793,13 +823,13 @@ such as input/output (I/O) redirection and pipes.
    Implementations of the `awk' language are available for many
 different computing environments.  This Info file, while describing the
 `awk' language in general, also describes the particular implementation
-of `awk' called `gawk' (which stands for "GNU awk").  `gawk' runs on a
-broad range of Unix systems, ranging from Intel(R)-architecture
-PC-based computers up through large-scale systems, such as Crays.
-`gawk' has also been ported to Mac OS X, Microsoft Windows (all
-versions) and OS/2 PCs, and VMS.  (Some other, obsolete systems to
-which `gawk' was once ported are no longer supported and the code for
-those systems has been removed.)
+of `awk' called `gawk' (which stands for "GNU `awk'").  `gawk' runs on
+a broad range of Unix systems, ranging from Intel(R)-architecture
+PC-based computers up through large-scale systems.  `gawk' has also
+been ported to Mac OS X, Microsoft Windows (all versions) and OS/2 PCs,
+and OpenVMS.  (Some other, obsolete systems to which `gawk' was once
+ported are no longer supported and the code for those systems has been
+removed.)
 
 * Menu:
 
@@ -816,7 +846,7 @@ those systems has been removed.)
 
    ---------- Footnotes ----------
 
-   (1) The 2008 POSIX standard is online at
+   (1) The 2008 POSIX standard is accessable online at
 `http://www.opengroup.org/onlinepubs/9699919799/'.
 
    (2) These commands are available on POSIX-compliant systems, as well
@@ -886,20 +916,21 @@ The `awk' language has evolved over the years. Full details are
 provided in *note Language History::.  The language described in this
 Info file is often referred to as "new `awk'" (`nawk').
 
-   Because of this, there are systems with multiple versions of `awk'.
-Some systems have an `awk' utility that implements the original version
-of the `awk' language and a `nawk' utility for the new version.  Others
-have an `oawk' version for the "old `awk'" language and plain `awk' for
-the new one.  Still others only have one version, which is usually the
-new one.(1)
-
-   All in all, this makes it difficult for you to know which version of
-`awk' you should run when writing your programs.  The best advice we
-can give here is to check your local documentation. Look for `awk',
-`oawk', and `nawk', as well as for `gawk'.  It is likely that you
-already have some version of new `awk' on your system, which is what
-you should use when running your programs.  (Of course, if you're
-reading this Info file, chances are good that you have `gawk'!)
+   For some time after new `awk' was introduced, there were systems
+with multiple versions of `awk'.  Some systems had an `awk' utility
+that implemented the original version of the `awk' language and a
+`nawk' utility for the new version.  Others had an `oawk' version for
+the "old `awk'" language and plain `awk' for the new one.  Still others
+only had one version, which is usually the new one.
+
+   Today, only Solaris systems still use an old `awk' for the default
+`awk' utility. (A more modern `awk' lives in `/usr/xpg6/bin' on these
+systems.)  All other modern systems use some version of new `awk'.(1)
+
+   It is likely that you already have some version of new `awk' on your
+system, which is what you should use when running your programs.  (Of
+course, if you're reading this Info file, chances are good that you
+have `gawk'!)
 
    Throughout this Info file, whenever we refer to a language feature
 that should be available in any complete implementation of POSIX `awk',
@@ -908,7 +939,7 @@ specific to the GNU implementation, we use the term `gawk'.
 
    ---------- Footnotes ----------
 
-   (1) Often, these systems use `gawk' for their `awk' implementation!
+   (1) Many of these systems use `gawk' for their `awk' implementation!
 
 
 File: gawk.info,  Node: This Manual,  Next: Conventions,  Prev: Names,  Up: Preface
@@ -1037,7 +1068,7 @@ material for those who are completely unfamiliar with computer
 programming.
 
    The *note Glossary::, defines most, if not all, the significant
-terms used throughout the book.  If you find terms that you aren't
+terms used throughout the Info file.  If you find terms that you aren't
 familiar with, try looking them up here.
 
    *note Copying::, and *note GNU Free Documentation License::, present
@@ -1115,7 +1146,7 @@ editor.  GNU Emacs is the most widely used version of Emacs today.
 Software Foundation to create a complete, freely distributable,
 POSIX-compliant computing environment.  The FSF uses the "GNU General
 Public License" (GPL) to ensure that their software's source code is
-always available to the end user. A copy of the GPL is included for
+always available to the end user.  A copy of the GPL is included for
 your reference (*note Copying::).  The GPL applies to the C language
 source code for `gawk'.  To find out more about the FSF and the GNU
 Project online, see the GNU Project's home page (http://www.gnu.org).
@@ -1154,19 +1185,18 @@ published the first two editions under the title `The GNU Awk User's
 Guide'.
 
    This edition maintains the basic structure of the previous editions.
-For Edition 4.0, the content has been thoroughly reviewed and updated.
-All references to `gawk' versions prior to 4.0 have been removed.  Of
-significant note for this edition was *note Debugger::.
+For FSF edition 4.0, the content has been thoroughly reviewed and
+updated. All references to `gawk' versions prior to 4.0 have been
+removed.  Of significant note for this edition was *note Debugger::.
 
-   For edition 4.1, the content has been reorganized into parts, and
-the major new additions are *note Arbitrary Precision Arithmetic::, and
-*note Dynamic Extensions::.
+   For FSF edition 4.1, the content has been reorganized into parts,
+and the major new additions are *note Arbitrary Precision Arithmetic::,
+and *note Dynamic Extensions::.
 
-   `GAWK: Effective AWK Programming' will undoubtedly continue to
-evolve.  An electronic version comes with the `gawk' distribution from
-the FSF.  If you find an error in this Info file, please report it!
-*Note Bugs::, for information on submitting problem reports
-electronically.
+   This Info file will undoubtedly continue to evolve.  An electronic
+version comes with the `gawk' distribution from the FSF.  If you find
+an error in this Info file, please report it!  *Note Bugs::, for
+information on submitting problem reports electronically.
 
    ---------- Footnotes ----------
 
@@ -1193,14 +1223,17 @@ something more broad, I acquired the `awk.info' domain.
 contributed code: the archive did not grow and the domain went unused
 for several years.
 
-   Fortunately, late in 2008, a volunteer took on the task of setting up
-an `awk'-related web site--`http://awk.info'--and did a very nice job.
+   Late in 2008, a volunteer took on the task of setting up an
+`awk'-related web site--`http://awk.info'--and did a very nice job.
 
    If you have written an interesting `awk' program, or have written a
 `gawk' extension that you would like to share with the rest of the
 world, please see `http://awk.info/?contribute' for how to contribute
 it to the web site.
 
+   As of this writing, this website is in search of a maintainer; please
+contact me if you are interested.
+
 
 File: gawk.info,  Node: Acknowledgments,  Prev: How To Contribute,  Up: Preface
 
@@ -1264,15 +1297,19 @@ acknowledgements:
    Dr. Nelson Beebe, Andreas Buening, Dr. Manuel Collado, Antonio
 Colombo, Stephen Davies, Scott Deifik, Akim Demaille, Darrel Hankerson,
 Michal Jaegermann, Ju"rgen Kahrs, Stepan Kasal, John Malmberg, Dave
-Pitts, Chet Ramey, Pat Rankin, Andrew Schorr, Corinna Vinschen, Anders
-Wallin, and Eli Zaretskii (in alphabetical order) make up the current
-`gawk' "crack portability team."  Without their hard work and help,
-`gawk' would not be nearly the fine program it is today.  It has been
-and continues to be a pleasure working with this team of fine people.
+Pitts, Chet Ramey, Pat Rankin, Andrew Schorr, Corinna Vinschen, and Eli
+Zaretskii (in alphabetical order) make up the current `gawk' "crack
+portability team."  Without their hard work and help, `gawk' would not
+be nearly the fine program it is today.  It has been and continues to
+be a pleasure working with this team of fine people.
 
    Notable code and documentation contributions were made by a number
 of people. *Note Contributors::, for the full list.
 
+   Thanks to Patrice Dumas  for the new `makeinfo' program.  Thanks to
+Karl Berry who continues to work to keep the Texinfo markup language
+sane.
+
    I would like to thank Brian Kernighan for invaluable assistance
 during the testing and debugging of `gawk', and for ongoing help and
 advice in clarifying numerous points about the language.  We could not
@@ -1287,12 +1324,6 @@ also must acknowledge my gratitude to G-d, for the many opportunities
 He has sent my way, as well as for the gifts He has given me with which
 to take advantage of those opportunities.
 
-
-Arnold Robbins
-Nof Ayalon
-ISRAEL
-May, 2013
-
 
 File: gawk.info,  Node: Getting Started,  Next: Invoking Gawk,  Prev: Preface,  Up: Top
 
@@ -1321,7 +1352,7 @@ for now.  *Note User-defined::.)  Each rule specifies one pattern to
 search for and one action to perform upon finding the pattern.
 
    Syntactically, a rule consists of a pattern followed by an action.
-The action is enclosed in curly braces to separate it from the pattern.
+The action is enclosed in braces to separate it from the pattern.
 Newlines usually separate rules.  Therefore, an `awk' program looks
 like this:
 
@@ -1344,6 +1375,7 @@ like this:
 * Other Features::              Other Features of `awk'.
 * When::                        When to use `gawk' and when to use
                                 other things.
+* Intro Summary::               Summary of the introduction.
 
 
 File: gawk.info,  Node: Running gawk,  Next: Sample Data Files,  Up: Getting Started
@@ -1369,7 +1401,7 @@ variations of each.
 
 * One-shot::                    Running a short throwaway `awk'
                                 program.
-* Read Terminal::               Using no input files (input from terminal
+* Read Terminal::               Using no input files (input from the keyboard
                                 instead).
 * Long::                        Putting permanent `awk' programs in
                                 files.
@@ -1419,7 +1451,7 @@ following command line:
      awk 'PROGRAM'
 
 `awk' applies the PROGRAM to the "standard input", which usually means
-whatever you type on the terminal.  This continues until you indicate
+whatever you type on the keyboard.  This continues until you indicate
 end-of-file by typing `Ctrl-d'.  (On other operating systems, the
 end-of-file character may be different.  For example, on OS/2, it is
 `Ctrl-z'.)
@@ -1600,7 +1632,7 @@ at a later time.
      will probably print strange messages about syntax errors.  For
      example, look at the following:
 
-          $ awk '{ print "hello" } # let's be cute'
+          $ awk 'BEGIN { print "hello" } # let's be cute'
           >
 
      The shell sees that the first two quotes match, and that a new
@@ -1640,6 +1672,23 @@ knowledge of shell quoting rules.  The following rules apply only to
 POSIX-compliant, Bourne-style shells (such as Bash, the GNU Bourne-Again
 Shell).  If you use the C shell, you're on your own.
 
+   Before diving into the rules, we introduce a concept that appears
+throughout this Info file, which is that of the "null", or empty,
+string.
+
+   The null string is character data that has no value.  In other
+words, it is empty.  It is written in `awk' programs like this: `""'.
+In the shell, it can be written using single or double quotes: `""' or
+`'''. While the null string has no characters in it, it does exist.
+Consider this command:
+
+     $ echo ""
+
+Here, the `echo' utility receives a single argument, even though that
+argument has no characters in it. In the rest of this Info file, we use
+the terms "null string" and "empty string" interchangeably.  Now, on to
+the quoting rules.
+
    * Quoted items can be concatenated with nonquoted items as well as
      with other quoted items.  The shell turns everything into one
      argument for the command.
@@ -1760,30 +1809,30 @@ File: gawk.info,  Node: Sample Data Files,  Next: Very Simple,  Prev: Running ga
 ===============================
 
 Many of the examples in this Info file take their input from two sample
-data files.  The first, `BBS-list', represents a list of computer
-bulletin board systems together with information about those systems.
+data files.  The first, `mail-list', represents a list of peoples' names
+together with their email addresses and information about those people.
 The second data file, called `inventory-shipped', contains information
 about monthly shipments.  In both files, each line is considered to be
 one "record".
 
-   In the data file `BBS-list', each record contains the name of a
-computer bulletin board, its phone number, the board's baud rate(s),
-and a code for the number of hours it is operational.  An `A' in the
-last column means the board operates 24 hours a day.  A `B' in the last
-column means the board only operates on evening and weekend hours.  A
-`C' means the board operates only on weekends:
-
-     aardvark     555-5553     1200/300          B
-     alpo-net     555-3412     2400/1200/300     A
-     barfly       555-7685     1200/300          A
-     bites        555-1675     2400/1200/300     A
-     camelot      555-0542     300               C
-     core         555-2912     1200/300          C
-     fooey        555-1234     2400/1200/300     B
-     foot         555-6699     1200/300          B
-     macfoo       555-6480     1200/300          A
-     sdace        555-3430     2400/1200/300     A
-     sabafoo      555-2127     1200/300          C
+   In the data file `mail-list', each record contains the name of a
+person, his/her phone number, his/her email-address, and a code for
+their relationship with the author of the list.  An `A' in the last
+column means that the person is an acquaintance.  An `F' in the last
+column means that the person is a friend.  An `R' means that the person
+is a relative:
+
+     Amelia       555-5553     amelia.zodiacusque@gmail.com    F
+     Anthony      555-3412     anthony.asserturo@hotmail.com   A
+     Becky        555-7685     becky.algebrarum@gmail.com      A
+     Bill         555-1675     bill.drowning@hotmail.com       A
+     Broderick    555-0542     broderick.aliquotiens@yahoo.com R
+     Camilla      555-2912     camilla.infusarum@skynet.be     R
+     Fabius       555-1234     fabius.undevicesimus@ucb.edu    F
+     Julie        555-6699     julie.perscrutabor@skeeve.com   F
+     Martin       555-6480     martin.codicibus@hotmail.com    A
+     Samuel       555-3430     samuel.lanceolis@shu.edu        A
+     Jean-Paul    555-2127     jeanpaul.campanorum@nyu.edu     R
 
    The data file `inventory-shipped' represents information about
 shipments during the year.  Each record contains the month, the number
@@ -1810,18 +1859,8 @@ and the first four months of the current year.
      Mar  24  75  70 495
      Apr  21  70  74 514
 
-   If you are reading this in GNU Emacs using Info, you can copy the
-regions of text showing these sample files into your own test files.
-This way you can try out the examples shown in the remainder of this
-document.  You do this by using the command `M-x write-region' to copy
-text from the Info file into a file for use with `awk' (*Note
-Miscellaneous File Operations: (emacs)Misc File Ops, for more
-information).  Using this information, create your own `BBS-list' and
-`inventory-shipped' files and practice what you learn in this Info file.
-
-   If you are using the stand-alone version of Info, see *note Extract
-Program::, for an `awk' program that extracts these data files from
-`gawk.texi', the (generated) Texinfo source file for this Info file.
+   The sample files are included in the `gawk' distribution, in the
+directory `awklib/eg/data'.
 
 
 File: gawk.info,  Node: Very Simple,  Next: Two Rules,  Prev: Sample Data Files,  Up: Getting Started
@@ -1830,32 +1869,32 @@ File: gawk.info,  Node: Very Simple,  Next: Two Rules,  Prev: Sample Data Files,
 ========================
 
 The following command runs a simple `awk' program that searches the
-input file `BBS-list' for the character string `foo' (a grouping of
+input file `mail-list' for the character string `li' (a grouping of
 characters is usually called a "string"; the term "string" is based on
 similar usage in English, such as "a string of pearls," or "a string of
 cars in a train"):
 
-     awk '/foo/ { print $0 }' BBS-list
+     awk '/li/ { print $0 }' mail-list
 
-When lines containing `foo' are found, they are printed because
+When lines containing `li' are found, they are printed because
 `print $0' means print the current line.  (Just `print' by itself means
 the same thing, so we could have written that instead.)
 
-   You will notice that slashes (`/') surround the string `foo' in the
-`awk' program.  The slashes indicate that `foo' is the pattern to
-search for.  This type of pattern is called a "regular expression",
-which is covered in more detail later (*note Regexp::).  The pattern is
-allowed to match parts of words.  There are single quotes around the
-`awk' program so that the shell won't interpret any of it as special
-shell characters.
+   You will notice that slashes (`/') surround the string `li' in the
+`awk' program.  The slashes indicate that `li' is the pattern to search
+for.  This type of pattern is called a "regular expression", which is
+covered in more detail later (*note Regexp::).  The pattern is allowed
+to match parts of words.  There are single quotes around the `awk'
+program so that the shell won't interpret any of it as special shell
+characters.
 
    Here is what this program prints:
 
-     $ awk '/foo/ { print $0 }' BBS-list
-     -| fooey        555-1234     2400/1200/300     B
-     -| foot         555-6699     1200/300          B
-     -| macfoo       555-6480     1200/300          A
-     -| sabafoo      555-2127     1200/300          C
+     $ awk '/li/ { print $0 }' mail-list
+     -| Amelia       555-5553     amelia.zodiacusque@gmail.com    F
+     -| Broderick    555-0542     broderick.aliquotiens@yahoo.com R
+     -| Julie        555-6699     julie.perscrutabor@skeeve.com   F
+     -| Samuel       555-3430     samuel.lanceolis@shu.edu        A
 
    In an `awk' rule, either the pattern or the action can be omitted,
 but not both.  If the pattern is omitted, then the action is performed
@@ -1863,10 +1902,10 @@ for _every_ input line.  If the action is omitted, the default action
 is to print all lines that match the pattern.
 
    Thus, we could leave out the action (the `print' statement and the
-curly braces) in the previous example and the result would be the same:
-`awk' prints all lines matching the pattern `foo'.  By comparison,
-omitting the `print' statement but retaining the curly braces makes an
-empty action that does nothing (i.e., no lines are printed).
+braces) in the previous example and the result would be the same: `awk'
+prints all lines matching the pattern `li'.  By comparison, omitting
+the `print' statement but retaining the braces makes an empty action
+that does nothing (i.e., no lines are printed).
 
    Many practical `awk' programs are just a line or two.  Following is a
 collection of useful, short programs to get you started.  Some of these
@@ -1890,7 +1929,7 @@ different ways to do the same things shown here:
           awk 'length($0) > 80' data
 
      The sole rule has a relational expression as its pattern and it
-     has no action--so the default action, printing the record, is used.
+     has no action--so it uses the default action, printing the record.
 
    * Print the length of the longest line in `data':
 
@@ -1947,9 +1986,8 @@ File: gawk.info,  Node: Two Rules,  Next: More Complex,  Prev: Very Simple,  Up:
 
 The `awk' utility reads the input files one line at a time.  For each
 line, `awk' tries the patterns of each of the rules.  If several
-patterns match, then several actions are run in the order in which they
-appear in the `awk' program.  If no patterns match, then no actions are
-run.
+patterns match, then several actions execute in the order in which they
+appear in the `awk' program.  If no patterns match, then no actions run.
 
    After processing all the rules that match the line (and perhaps
 there are none), `awk' reads the next line.  (However, *note Next
@@ -1970,25 +2008,19 @@ the string `21'.  If a line contains both strings, it is printed twice,
 once by each rule.
 
    This is what happens if we run this program on our two sample data
-files, `BBS-list' and `inventory-shipped':
+files, `mail-list' and `inventory-shipped':
 
      $ awk '/12/ { print $0 }
-     >      /21/ { print $0 }' BBS-list inventory-shipped
-     -| aardvark     555-5553     1200/300          B
-     -| alpo-net     555-3412     2400/1200/300     A
-     -| barfly       555-7685     1200/300          A
-     -| bites        555-1675     2400/1200/300     A
-     -| core         555-2912     1200/300          C
-     -| fooey        555-1234     2400/1200/300     B
-     -| foot         555-6699     1200/300          B
-     -| macfoo       555-6480     1200/300          A
-     -| sdace        555-3430     2400/1200/300     A
-     -| sabafoo      555-2127     1200/300          C
-     -| sabafoo      555-2127     1200/300          C
+     >      /21/ { print $0 }' mail-list inventory-shipped
+     -| Anthony      555-3412     anthony.asserturo@hotmail.com   A
+     -| Camilla      555-2912     camilla.infusarum@skynet.be     R
+     -| Fabius       555-1234     fabius.undevicesimus@ucb.edu    F
+     -| Jean-Paul    555-2127     jeanpaul.campanorum@nyu.edu     R
+     -| Jean-Paul    555-2127     jeanpaul.campanorum@nyu.edu     R
      -| Jan  21  36  64 620
      -| Apr  21  70  74 514
 
-Note how the line beginning with `sabafoo' in `BBS-list' was printed
+Note how the line beginning with `Jean-Paul' in `mail-list' was printed
 twice, once for each rule.
 
 
@@ -2031,12 +2063,12 @@ contains the file name.(1)
 
    The `$6 == "Nov"' in our `awk' program is an expression that tests
 whether the sixth field of the output from `ls -l' matches the string
-`Nov'.  Each time a line has the string `Nov' for its sixth field, the
-action `sum += $5' is performed.  This adds the fifth field (the file's
-size) to the variable `sum'.  As a result, when `awk' has finished
-reading all the input lines, `sum' is the total of the sizes of the
-files whose lines matched the pattern.  (This works because `awk'
-variables are automatically initialized to zero.)
+`Nov'.  Each time a line has the string `Nov' for its sixth field,
+`awk' performs the action `sum += $5'.  This adds the fifth field (the
+file's size) to the variable `sum'.  As a result, when `awk' has
+finished reading all the input lines, `sum' is the total of the sizes
+of the files whose lines matched the pattern.  (This works because
+`awk' variables are automatically initialized to zero.)
 
    After the last line of output from `ls' has been processed, the
 `END' rule executes and prints the value of `sum'.  In this example,
@@ -2064,7 +2096,7 @@ Most often, each line in an `awk' program is a separate statement or
 separate rule, like this:
 
      awk '/12/  { print $0 }
-          /21/  { print $0 }' BBS-list inventory-shipped
+          /21/  { print $0 }' mail-list inventory-shipped
 
    However, `gawk' ignores newlines after any of the following symbols
 and keywords:
@@ -2088,15 +2120,15 @@ We have generally not used backslash continuation in our sample
 programs.  `gawk' places no limit on the length of a line, so backslash
 continuation is never strictly necessary; it just makes programs more
 readable.  For this same reason, as well as for clarity, we have kept
-most statements short in the sample programs presented throughout the
-Info file.  Backslash continuation is most useful when your `awk'
-program is in a separate source file instead of entered from the
-command line.  You should also note that many `awk' implementations are
-more particular about where you may use backslash continuation. For
-example, they may not allow you to split a string constant using
-backslash continuation.  Thus, for maximum portability of your `awk'
-programs, it is best not to split your lines in the middle of a regular
-expression or a string.
+most statements short in the programs presented throughout the Info
+file.  Backslash continuation is most useful when your `awk' program is
+in a separate source file instead of entered from the command line.
+You should also note that many `awk' implementations are more
+particular about where you may use backslash continuation. For example,
+they may not allow you to split a string constant using backslash
+continuation.  Thus, for maximum portability of your `awk' programs, it
+is best not to split your lines in the middle of a regular expression
+or a string.
 
      CAUTION: _Backslash continuation does not work as described with
      the C shell._  It works for `awk' programs in files and for
@@ -2138,7 +2170,7 @@ comment, it ignores _everything_ on the rest of the line. For example:
      >                                    BEGIN rule
      > }'
      error--> gawk: cmd. line:2:                BEGIN rule
-     error--> gawk: cmd. line:2:                ^ parse error
+     error--> gawk: cmd. line:2:                ^ syntax error
 
 In this case, it looks like the backslash would continue the comment
 onto the next line. However, the backslash-newline combination is never
@@ -2187,7 +2219,7 @@ most of the variables and many of the functions. They are described
 systematically in *note Built-in Variables::, and *note Built-in::.
 
 
-File: gawk.info,  Node: When,  Prev: Other Features,  Up: Getting Started
+File: gawk.info,  Node: When,  Next: Intro Summary,  Prev: Other Features,  Up: Getting Started
 
 1.8 When to Use `awk'
 =====================
@@ -2217,14 +2249,39 @@ those that it has are much larger than they used to be.
 
    If you find yourself writing `awk' scripts of more than, say, a few
 hundred lines, you might consider using a different programming
-language.  Emacs Lisp is a good choice if you need sophisticated string
-or pattern matching capabilities.  The shell is also good at string and
-pattern matching; in addition, it allows powerful use of the system
-utilities.  More conventional languages, such as C, C++, and Java, offer
-better facilities for system programming and for managing the complexity
-of large programs.  Programs in these languages may require more lines
-of source code than the equivalent `awk' programs, but they are easier
-to maintain and usually run more efficiently.
+language.  The shell is good at string and pattern matching; in
+addition, it allows powerful use of the system utilities.  More
+conventional languages, such as C, C++, and Java, offer better
+facilities for system programming and for managing the complexity of
+large programs.  Python offers a nice balance between high-level ease
+of programming and access to system facilities.  Programs in these
+languages may require more lines of source code than the equivalent
+`awk' programs, but they are easier to maintain and usually run more
+efficiently.
+
+
+File: gawk.info,  Node: Intro Summary,  Prev: When,  Up: Getting Started
+
+1.9 Summary
+===========
+
+   * Programs in `awk' consist of PATTERN-ACTION pairs.
+
+   * Use either `awk 'PROGRAM' FILES' or `awk -f PROGRAM-FILE FILES' to
+     run `awk'.
+
+   * You may use the special `#!' header line to create `awk' programs
+     that are directly executable.
+
+   * Comments in `awk' programs start with `#' and continue to the end
+     of the same line.
+
+   * Be aware of quoting issues when writing `awk' programs as part of
+     a larger shell script (or MS-Windows batch file).
+
+   * You may use backslash continuation to continue a source line.
+     Lines are automatically continued after a comma, open brace,
+     question mark, colon, `||', `&&', `do' and `else'.
 
 
 File: gawk.info,  Node: Invoking Gawk,  Next: Regexp,  Prev: Getting Started,  Up: Top
@@ -2232,7 +2289,7 @@ File: gawk.info,  Node: Invoking Gawk,  Next: Regexp,  Prev: Getting Started,  U
 2 Running `awk' and `gawk'
 **************************
 
-This major node covers how to run awk, both POSIX-standard and
+This major node covers how to run `awk', both POSIX-standard and
 `gawk'-specific command-line options, and what `awk' and `gawk' do with
 non-option arguments.  It then proceeds to cover how `gawk' searches
 for source files, reading standard input along with other files,
@@ -2256,6 +2313,7 @@ this major node that don't interest you right now.
 * Loading Shared Libraries::    Loading shared libraries into your program.
 * Obsolete::                    Obsolete Options and/or features.
 * Undocumented::                Undocumented Options and Features.
+* Invoking Summary::            Invocation summary.
 
 
 File: gawk.info,  Node: Command Line,  Next: Options,  Up: Invoking Gawk
@@ -2267,8 +2325,8 @@ There are two ways to run `awk'--with an explicit program or with one
 or more program files.  Here are templates for both of them; items
 enclosed in [...] in these templates are optional:
 
-     awk [OPTIONS] -f progfile [`--'] FILE ...
-     awk [OPTIONS] [`--'] 'PROGRAM' FILE ...
+     `awk' [OPTIONS] `-f' PROGFILE [`--'] FILE ...
+     `awk' [OPTIONS] [`--'] `'PROGRAM'' FILE ...
 
    Besides traditional one-letter POSIX-style options, `gawk' also
 supports GNU long options.
@@ -2308,22 +2366,8 @@ The following list describes options mandated by the POSIX standard:
 `--file SOURCE-FILE'
      Read `awk' program source from SOURCE-FILE instead of in the first
      non-option argument.  This option may be given multiple times; the
-     `awk' program consists of the concatenation the contents of each
-     specified SOURCE-FILE.
-
-`-i SOURCE-FILE'
-`--include SOURCE-FILE'
-     Read `awk' source library from SOURCE-FILE.  This option is
-     completely equivalent to using the `@include' directive inside
-     your program.  This option is very similar to the `-f' option, but
-     there are two important differences.  First, when `-i' is used,
-     the program source will not be loaded if it has been previously
-     loaded, whereas the `-f' will always load the file.  Second,
-     because this option is intended to be used with code libraries,
-     `gawk' does not recognize such files as constituting main program
-     input.  Thus, after processing an `-i' argument, `gawk' still
-     expects to find the main source code via the `-f' option or on the
-     command-line.
+     `awk' program consists of the concatenation of the contents of
+     each specified SOURCE-FILE.
 
 `-v VAR=VAL'
 `--assign VAR=VAL'
@@ -2368,11 +2412,11 @@ The following list describes options mandated by the POSIX standard:
      treated as single-byte characters.
 
      Normally, `gawk' follows the POSIX standard and attempts to process
-     its input data according to the current locale. This can often
-     involve converting multibyte characters into wide characters
-     (internally), and can lead to problems or confusion if the input
-     data does not contain valid multibyte characters. This option is
-     an easy way to tell `gawk': "hands off my data!".
+     its input data according to the current locale (*note Locales::).
+     This can often involve converting multibyte characters into wide
+     characters (internally), and can lead to problems or confusion if
+     the input data does not contain valid multibyte characters. This
+     option is an easy way to tell `gawk': "hands off my data!".
 
 `-c'
 `--traditional'
@@ -2386,8 +2430,8 @@ The following list describes options mandated by the POSIX standard:
      Print the short version of the General Public License and then
      exit.
 
-`-d[FILE]'
-`--dump-variables[=FILE]'
+`-d'[FILE]
+`--dump-variables'[`='FILE]
      Print a sorted list of global variables, their types, and final
      values to FILE.  If no FILE is provided, print this list to the
      file named `awkvars.out' in the current directory.  No space is
@@ -2401,25 +2445,25 @@ The following list describes options mandated by the POSIX standard:
      particularly easy mistake to make with simple variable names like
      `i', `j', etc.)
 
-`-D[FILE]'
-`--debug=[FILE]'
+`-D'[FILE]
+`--debug'[`='FILE]
      Enable debugging of `awk' programs (*note Debugging::).  By
      default, the debugger reads commands interactively from the
-     terminal.  The optional FILE argument allows you to specify a file
+     keyboard.  The optional FILE argument allows you to specify a file
      with a list of commands for the debugger to execute
      non-interactively.  No space is allowed between the `-D' and FILE,
      if FILE is supplied.
 
-`-e PROGRAM-TEXT'
-`--source PROGRAM-TEXT'
+`-e' PROGRAM-TEXT
+`--source' PROGRAM-TEXT
      Provide program source code in the PROGRAM-TEXT.  This option
      allows you to mix source code in files with source code that you
      enter on the command line.  This is particularly useful when you
      have library functions that you want to use from your command-line
      programs (*note AWKPATH Variable::).
 
-`-E FILE'
-`--exec FILE'
+`-E' FILE
+`--exec' FILE
      Similar to `-f', read `awk' program text from FILE.  There are two
      differences from `-f':
 
@@ -2452,23 +2496,41 @@ The following list describes options mandated by the POSIX standard:
      Print a "usage" message summarizing the short and long style
      options that `gawk' accepts and then exit.
 
-`-l LIB'
-`--load LIB'
-     Load a shared library LIB. This searches for the library using the
-     `AWKLIBPATH' environment variable.  The correct library suffix for
-     your platform will be supplied by default, so it need not be
-     specified in the library name.  The library initialization routine
-     should be named `dl_load()'.  An alternative is to use the `@load'
-     keyword inside the program to load a shared library.
-
-`-L [value]'
-`--lint[=value]'
+`-i' SOURCE-FILE
+`--include' SOURCE-FILE
+     Read `awk' source library from SOURCE-FILE.  This option is
+     completely equivalent to using the `@include' directive inside
+     your program.  This option is very similar to the `-f' option, but
+     there are two important differences.  First, when `-i' is used,
+     the program source is not loaded if it has been previously loaded,
+     whereas with `-f', `gawk' always loads the file.  Second, because
+     this option is intended to be used with code libraries, `gawk'
+     does not recognize such files as constituting main program input.
+     Thus, after processing an `-i' argument, `gawk' still expects to
+     find the main source code via the `-f' option or on the
+     command-line.
+
+`-l' EXT
+`--load' EXT
+     Load a dynamic extension named EXT. Extensions are stored as
+     system shared libraries.  This option searches for the library
+     using the `AWKLIBPATH' environment variable.  The correct library
+     suffix for your platform will be supplied by default, so it need
+     not be specified in the extension name.  The extension
+     initialization routine should be named `dl_load()'.  An
+     alternative is to use the `@load' keyword inside the program to
+     load a shared library.  This feature is described in detail in
+     *note Dynamic Extensions::.
+
+`-L'[VALUE]
+`--lint'[`='VALUE]
      Warn about constructs that are dubious or nonportable to other
-     `awk' implementations.  Some warnings are issued when `gawk' first
-     reads your program.  Others are issued at runtime, as your program
-     executes.  With an optional argument of `fatal', lint warnings
-     become fatal errors.  This may be drastic, but its use will
-     certainly encourage the development of cleaner `awk' programs.
+     `awk' implementations.  No space is allowed between the `-D' and
+     VALUE, if VALUE is supplied.  Some warnings are issued when `gawk'
+     first reads your program.  Others are issued at runtime, as your
+     program executes.  With an optional argument of `fatal', lint
+     warnings become fatal errors.  This may be drastic, but its use
+     will certainly encourage the development of cleaner `awk' programs.
      With an optional argument of `invalid', only warnings about things
      that are actually invalid are issued. (This is not fully
      implemented yet.)
@@ -2499,23 +2561,26 @@ The following list describes options mandated by the POSIX standard:
      Force the use of the locale's decimal point character when parsing
      numeric input data (*note Locales::).
 
-`-o[FILE]'
-`--pretty-print[=FILE]'
+`-o'[FILE]
+`--pretty-print'[`='FILE]
      Enable pretty-printing of `awk' programs.  By default, output
-     program is created in a file named `awkprof.out'.  The optional
-     FILE argument allows you to specify a different file name for the
-     output.  No space is allowed between the `-o' and FILE, if FILE is
-     supplied.
+     program is created in a file named `awkprof.out' (*note
+     Profiling::).  The optional FILE argument allows you to specify a
+     different file name for the output.  No space is allowed between
+     the `-o' and FILE, if FILE is supplied.
+
+          NOTE: Due to the way `gawk' has evolved, with this option
+          your program is still executed.  This will change in the next
+          major release such that `gawk' will only pretty-print the
+          program and not run it.
 
 `-O'
 `--optimize'
      Enable some optimizations on the internal representation of the
-     program.  At the moment this includes just simple constant
-     folding. The `gawk' maintainer hopes to add more optimizations
-     over time.
+     program.  At the moment this includes just simple constant folding.
 
-`-p[FILE]'
-`--profile[=FILE]'
+`-p'[FILE]
+`--profile'[`='FILE]
      Enable profiling of `awk' programs (*note Profiling::).  By
      default, profiles are created in a file named `awkprof.out'.  The
      optional FILE argument allows you to specify a different file name
@@ -2548,15 +2613,15 @@ The following list describes options mandated by the POSIX standard:
           data (*note Locales::).
 
      If you supply both `--traditional' and `--posix' on the command
-     line, `--posix' takes precedence. `gawk' also issues a warning if
-     both options are supplied.
+     line, `--posix' takes precedence. `gawk' issues a warning if both
+     options are supplied.
 
 `-r'
 `--re-interval'
      Allow interval expressions (*note Regexp Operators::) in regexps.
      This is now `gawk''s default behavior.  Nevertheless, this option
      remains both for backward compatibility, and for use in
-     combination with the `--traditional' option.
+     combination with `--traditional'.
 
 `-S'
 `--sandbox'
@@ -2596,7 +2661,7 @@ having to be included into each individual program.  (As mentioned in
 *note Definition Syntax::, function names must be unique.)
 
    With standard `awk', library functions can still be used, even if
-the program is entered at the terminal, by specifying `-f /dev/tty'.
+the program is entered at the keyboard, by specifying `-f /dev/tty'.
 After typing your program, type `Ctrl-d' (the end-of-file character) to
 terminate it.  (You may also use `-f -' to read program source from the
 standard input but then you will not be able to also use the standard
@@ -2606,25 +2671,25 @@ input as a source of data.)
 source file and command-line `awk' programs, `gawk' provides the
 `--source' option.  This does not require you to pre-empt the standard
 input for your source code; it allows you to easily mix command-line
-and library source code (*note AWKPATH Variable::).  The `--source'
-option may also be used multiple times on the command line.
+and library source code (*note AWKPATH Variable::).  As with `-f', the
+`--source' and `--include' options may also be used multiple times on
+the command line.
 
    If no `-f' or `--source' option is specified, then `gawk' uses the
 first non-option command-line argument as the text of the program
 source code.
 
    If the environment variable `POSIXLY_CORRECT' exists, then `gawk'
-behaves in strict POSIX mode, exactly as if you had supplied the
-`--posix' command-line option.  Many GNU programs look for this
-environment variable to suppress extensions that conflict with POSIX,
-but `gawk' behaves differently: it suppresses all extensions, even
-those that do not conflict with POSIX, and behaves in strict POSIX
-mode. If `--lint' is supplied on the command line and `gawk' turns on
-POSIX mode because of `POSIXLY_CORRECT', then it issues a warning
-message indicating that POSIX mode is in effect.  You would typically
-set this variable in your shell's startup file.  For a
-Bourne-compatible shell (such as Bash), you would add these lines to
-the `.profile' file in your home directory:
+behaves in strict POSIX mode, exactly as if you had supplied `--posix'.
+Many GNU programs look for this environment variable to suppress
+extensions that conflict with POSIX, but `gawk' behaves differently: it
+suppresses all extensions, even those that do not conflict with POSIX,
+and behaves in strict POSIX mode. If `--lint' is supplied on the
+command line and `gawk' turns on POSIX mode because of
+`POSIXLY_CORRECT', then it issues a warning message indicating that
+POSIX mode is in effect.  You would typically set this variable in your
+shell's startup file.  For a Bourne-compatible shell (such as Bash),
+you would add these lines to the `.profile' file in your home directory:
 
      POSIXLY_CORRECT=true
      export POSIXLY_CORRECT
@@ -2676,18 +2741,18 @@ begins scanning the argument list.
    The variable values given on the command line are processed for
 escape sequences (*note Escape Sequences::).  (d.c.)
 
-   In some earlier implementations of `awk', when a variable assignment
-occurred before any file names, the assignment would happen _before_
-the `BEGIN' rule was executed.  `awk''s behavior was thus inconsistent;
-some command-line assignments were available inside the `BEGIN' rule,
-while others were not.  Unfortunately, some applications came to depend
-upon this "feature."  When `awk' was changed to be more consistent, the
-`-v' option was added to accommodate applications that depended upon
-the old behavior.
+   In some very early implementations of `awk', when a variable
+assignment occurred before any file names, the assignment would happen
+_before_ the `BEGIN' rule was executed.  `awk''s behavior was thus
+inconsistent; some command-line assignments were available inside the
+`BEGIN' rule, while others were not.  Unfortunately, some applications
+came to depend upon this "feature."  When `awk' was changed to be more
+consistent, the `-v' option was added to accommodate applications that
+depended upon the old behavior.
 
    The variable assignment feature is most useful for assigning to
 variables such as `RS', `OFS', and `ORS', which control input and
-output formats before scanning the data files.  It is also useful for
+output formats, before scanning the data files.  It is also useful for
 controlling state if multiple passes are needed over a data file.  For
 example:
 
@@ -2722,7 +2787,7 @@ with `getline' (*note Getline/File::).
    In addition, `gawk' allows you to specify the special file name
 `/dev/stdin', both on the command line and with `getline'.  Some other
 versions of `awk' also support this, but it is not standard.  (Some
-operating systems provide a `/dev/stdin' file in the file system,
+operating systems provide a `/dev/stdin' file in the file system;
 however, `gawk' always processes this file name itself.)
 
 
@@ -2752,17 +2817,18 @@ on the command-line with the `-f' option.  In most `awk'
 implementations, you must supply a precise path name for each program
 file, unless the file is in the current directory.  But in `gawk', if
 the file name supplied to the `-f' or `-i' options does not contain a
-`/', then `gawk' searches a list of directories (called the "search
-path"), one by one, looking for a file with the specified name.
+directory separator `/', then `gawk' searches a list of directories
+(called the "search path"), one by one, looking for a file with the
+specified name.
 
 The search path is a string consisting of directory names separated by
-colons.  `gawk' gets its search path from the `AWKPATH' environment
+colons(1).  `gawk' gets its search path from the `AWKPATH' environment
 variable.  If that variable does not exist, `gawk' uses a default path,
-`.:/usr/local/share/awk'.(1)
+`.:/usr/local/share/awk'.(2)
 
-   The search path feature is particularly useful for building libraries
-of useful `awk' functions.  The library files can be placed in a
-standard directory in the default path and then specified on the
+   The search path feature is particularly helpful for building
+libraries of useful `awk' functions.  The library files can be placed
+in a standard directory in the default path and then specified on the
 command line with a short file name.  Otherwise, the full file name
 would have to be typed for each file.
 
@@ -2773,14 +2839,16 @@ in compatibility mode.  This is true for both `--traditional' and
 `--posix'.  *Note Options::.
 
    If the source code is not found after the initial search, the path
-is searched again after adding the default `.awk' suffix to the
-filename.
+is searched again after adding the default `.awk' suffix to the file
+name.
 
      NOTE: To include the current directory in the path, either place
      `.' explicitly in the path or write a null entry in the path.  (A
      null entry is indicated by starting or ending the path with a
-     colon or by placing two colons next to each other (`::').)  This
-     path search mechanism is similar to the shell's.
+     colon or by placing two colons next to each other [`::'].)  This
+     path search mechanism is similar to the shell's.  (See `The
+     Bourne-Again SHell manual'.
+     (http://www.gnu.org/software/bash/manual/))
 
      However, `gawk' always looks in the current directory _before_
      searching `AWKPATH', so there is no real reason to include the
@@ -2788,8 +2856,8 @@ filename.
 
    If `AWKPATH' is not defined in the environment, `gawk' places its
 default search path into `ENVIRON["AWKPATH"]'. This makes it easy to
-determine the actual search path that `gawk' will use from within an
-`awk' program.
+determine the actual search path that `gawk' used from within an `awk'
+program.
 
    While you can change `ENVIRON["AWKPATH"]' within your `awk' program,
 this has no effect on the running program's behavior.  This makes
@@ -2799,7 +2867,9 @@ found, and `gawk' no longer needs to use `AWKPATH'.
 
    ---------- Footnotes ----------
 
-   (1) Your version of `gawk' may use a different directory; it will
+   (1) Semicolons on MS-Windows and MS-DOS.
+
+   (2) Your version of `gawk' may use a different directory; it will
 depend upon how `gawk' was built and installed. The actual directory is
 the value of `$(datadir)' generated when `gawk' was configured.  You
 probably don't need to worry about this, though.
@@ -2811,13 +2881,13 @@ File: gawk.info,  Node: AWKLIBPATH Variable,  Next: Other Environment Variables,
 -------------------------------------------
 
 The `AWKLIBPATH' environment variable is similar to the `AWKPATH'
-variable, but it is used to search for shared libraries specified with
-the `-l' option rather than for source files.  If the library is not
-found, the path is searched again after adding the appropriate shared
-library suffix for the platform.  For example, on GNU/Linux systems,
-the suffix `.so' is used.  The search path specified is also used for
-libraries loaded via the `@load' keyword (*note Loading Shared
-Libraries::).
+variable, but it is used to search for loadable extensions (stored as
+system shared libraries) specified with the `-l' option rather than for
+source files.  If the extension is not found, the path is searched
+again after adding the appropriate shared library suffix for the
+platform.  For example, on GNU/Linux systems, the suffix `.so' is used.
+The search path specified is also used for extensions loaded via the
+`@load' keyword (*note Loading Shared Libraries::).
 
 
 File: gawk.info,  Node: Other Environment Variables,  Prev: AWKLIBPATH Variable,  Up: Environment Variables
@@ -2834,7 +2904,7 @@ used by regular users.
      traditional and GNU extensions.  *Note Options::.
 
 `GAWK_SOCK_RETRIES'
-     Controls the number of time `gawk' will attempt to retry a two-way
+     Controls the number of times `gawk' attempts to retry a two-way
      TCP/IP (socket) connection before giving up.  *Note TCP/IP
      Networking::.
 
@@ -2851,9 +2921,18 @@ used by regular users.
 the `gawk' developers for testing and tuning.  They are subject to
 change. The variables are:
 
+`AWKBUFSIZE'
+     This variable only affects `gawk' on POSIX-compliant systems.
+     With a value of `exact', `gawk' uses the size of each input file
+     as the size of the memory buffer to allocate for I/O. Otherwise,
+     the value should be a number, and `gawk' uses that number as the
+     size of the buffer to allocate.  (When this variable is not set,
+     `gawk' uses the smaller of the file's size and the "default"
+     blocksize, which is usually the file systems I/O blocksize.)
+
 `AWK_HASH'
-     If this variable exists with a value of `gst', `gawk' will switch
-     to using the hash function from GNU Smalltalk for managing arrays.
+     If this variable exists with a value of `gst', `gawk' switches to
+     using the hash function from GNU Smalltalk for managing arrays.
      This function may be marginally faster than the standard function.
 
 `AWKREADFUNC'
@@ -2877,6 +2956,11 @@ change. The variables are:
      supposed to be differences, but occasionally theory and practice
      don't coordinate with each other.)
 
+`GAWK_NO_PP_RUN'
+     If this variable exists, then when invoked with the
+     `--pretty-print' option, `gawk' skips running the program.  This
+     variable will not survive into the next major release.
+
 `GAWK_STACKSIZE'
      This specifies the amount by which `gawk' should grow its internal
      evaluation stack, when needed.
@@ -2956,7 +3040,7 @@ enclosed in double quotes.
 
      NOTE: Keep in mind that this is a language construct and the file
      name cannot be a string variable, but rather just a literal string
-     in double quotes.
+     constant in double quotes.
 
    The files to be included may be nested; e.g., given a third script,
 namely `test3':
@@ -3011,22 +3095,22 @@ and this also applies to files named with `@include'.
 
 File: gawk.info,  Node: Loading Shared Libraries,  Next: Obsolete,  Prev: Include Files,  Up: Invoking Gawk
 
-2.8 Loading Shared Libraries Into Your Program
-==============================================
+2.8 Loading Dynamic Extensions Into Your Program
+================================================
 
 This minor node describes a feature that is specific to `gawk'.
 
-   The `@load' keyword can be used to read external `awk' shared
-libraries.  This allows you to link in compiled code that may offer
-superior performance and/or give you access to extended capabilities
-not supported by the `awk' language.  The `AWKLIBPATH' variable is used
-to search for the shared library.  Using `@load' is completely
-equivalent to using the `-l' command-line option.
+   The `@load' keyword can be used to read external `awk' extensions
+(stored as system shared libraries).  This allows you to link in
+compiled code that may offer superior performance and/or give you
+access to extended capabilities not supported by the `awk' language.
+The `AWKLIBPATH' variable is used to search for the extension.  Using
+`@load' is completely equivalent to using the `-l' command-line option.
 
-   If the shared library is not initially found in `AWKLIBPATH', another
+   If the extension is not initially found in `AWKLIBPATH', another
 search is conducted after appending the platform's default shared
-library suffix to the filename.  For example, on GNU/Linux systems, the
-suffix `.so' is used.
+library suffix to the file name.  For example, on GNU/Linux systems,
+the suffix `.so' is used.
 
      $ gawk '@load "ordchr"; BEGIN {print chr(65)}'
      -| A
@@ -3038,7 +3122,7 @@ This is equivalent to the following example:
 
 For command-line usage, the `-l' option is more convenient, but `@load'
 is useful for embedding inside an `awk' source file that requires
-access to a shared library.
+access to an extension.
 
    *note Dynamic Extensions::, describes how to write extensions (in C
 or C++) that can be loaded with either `@load' or the `-l' option.
@@ -3060,7 +3144,7 @@ worked.  As of version 4.0, they are no longer interpreted specially by
 `gawk'.  (Use `PROCINFO' instead; see *note Auto-set::.)
 
 
-File: gawk.info,  Node: Undocumented,  Prev: Obsolete,  Up: Invoking Gawk
+File: gawk.info,  Node: Undocumented,  Next: Invoking Summary,  Prev: Obsolete,  Up: Invoking Gawk
 
 2.10 Undocumented Options and Features
 ======================================
@@ -3070,6 +3154,48 @@ File: gawk.info,  Node: Undocumented,  Prev: Obsolete,  Up: Invoking Gawk
    This minor node intentionally left blank.
 
 
+File: gawk.info,  Node: Invoking Summary,  Prev: Undocumented,  Up: Invoking Gawk
+
+2.11 Summary
+============
+
+   * Use either `awk 'PROGRAM' FILES' or `awk -f PROGRAM-FILE FILES' to
+     run `awk'.
+
+   * The three standard `awk' options are `-f', `-F' and `-v'.  `gawk'
+     supplies these and many others, as well as corresponding GNU-style
+     long options.
+
+   * Non-option command-line arguments are usually treated as file
+     names, unless they have the form `VAR=VALUE', in which case they
+     are taken as variable assignments to be performed at that point in
+     processing the input.
+
+   * All non-option command-line arguments, excluding the program text,
+     are placed in the `ARGV' array.  Adjusting `ARGC' and `ARGV'
+     affects how `awk' processes input.
+
+   * You can use a single minus sign (`-') to refer to standard input
+     on the command line.
+
+   * `gawk' pays attention to a number of environment variables.
+     `AWKPATH', `AWKLIBPATH', and `POSIXLY_CORRECT' are the most
+     important ones.
+
+   * `gawk''s exit status conveys information to the program that
+     invoked it. Use the `exit' statement from within an `awk' program
+     to set the exit status.
+
+   * `gawk' allows you to include other `awk' source files into your
+     program using the `@include' statement and/or the `-i' and `-f'
+     command-line options.
+
+   * `gawk' allows you to load additional functions written in C or C++
+     using the `@load' statement and/or the `-l' option.  (This
+     advanced feature is described later on in *note Dynamic
+     Extensions::.)
+
+
 File: gawk.info,  Node: Regexp,  Next: Reading Files,  Prev: Invoking Gawk,  Up: Top
 
 3 Regular Expressions
@@ -3098,6 +3224,7 @@ you specify more complicated classes of strings.
 * Case-sensitivity::            How to do case-insensitive matching.
 * Leftmost Longest::            How much text matches.
 * Computed Regexps::            Using Dynamic Regexps.
+* Regexp Summary::              Regular expressions summary.
 
 
 File: gawk.info,  Node: Regexp Usage,  Next: Escape Sequences,  Up: Regexp
@@ -3109,14 +3236,14 @@ A regular expression can be used as a pattern by enclosing it in
 slashes.  Then the regular expression is tested against the entire text
 of each record.  (Normally, it only needs to match some part of the
 text in order to succeed.)  For example, the following prints the
-second field of each record that contains the string `foo' anywhere in
-it:
+second field of each record where the string `li' appears anywhere in
+the record:
 
-     $ awk '/foo/ { print $2 }' BBS-list
-     -| 555-1234
+     $ awk '/li/ { print $2 }' mail-list
+     -| 555-5553
+     -| 555-0542
      -| 555-6699
-     -| 555-6480
-     -| 555-2127
+     -| 555-3430
 
    Regular expressions can also be used in matching expressions.  These
 expressions allow you to specify the string to match against; it need
@@ -3195,8 +3322,8 @@ apply to both string constants and regexp constants:
      A literal backslash, `\'.
 
 `\a'
-     The "alert" character, `Ctrl-g', ASCII code 7 (BEL).  (This
-     usually makes some sort of audible noise.)
+     The "alert" character, `Ctrl-g', ASCII code 7 (BEL).  (This often
+     makes some sort of audible noise.)
 
 `\b'
      Backspace, `Ctrl-h', ASCII code 8 (BS).
@@ -3331,20 +3458,21 @@ sequences and that are not listed in the table stand for themselves:
      at the beginning of the string.
 
      It is important to realize that `^' does not match the beginning of
-     a line embedded in a string.  The condition is not true in the
-     following example:
+     a line (the point right after a `\n' newline character) embedded
+     in a string.  The condition is not true in the following example:
 
           if ("line1\nLINE 2" ~ /^L/) ...
 
 `$'
      This is similar to `^', but it matches only at the end of a string.
      For example, `p$' matches a record that ends with a `p'.  The `$'
-     is an anchor and does not match the end of a line embedded in a
-     string.  The condition in the following example is not true:
+     is an anchor and does not match the end of a line (the point right
+     before a `\n' newline character) embedded in a string.  The
+     condition in the following example is not true:
 
           if ("line1\nLINE 2" ~ /1$/) ...
 
-`. (period)'
+`.' (period)
      This matches any single character, _including_ the newline
      character.  For example, `.P' matches any single character
      followed by a `P' in a string.  Using concatenation, we can make a
@@ -3356,7 +3484,7 @@ sequences and that are not listed in the table stand for themselves:
      Otherwise, NUL is just another character. Other versions of `awk'
      may not be able to match the NUL character.
 
-`[...]'
+`['...`]'
      This is called a "bracket expression".(1) It matches any _one_ of
      the characters that are enclosed in the square brackets.  For
      example, `[MVX]' matches any one of the characters `M', `V', or
@@ -3364,7 +3492,7 @@ sequences and that are not listed in the table stand for themselves:
      square brackets of a bracket expression is given in *note Bracket
      Expressions::.
 
-`[^ ...]'
+`[^'...`]'
      This is a "complemented bracket expression".  The first character
      after the `[' _must_ be a `^'.  It matches any characters _except_
      those in the square brackets.  For example, `[^awk]' matches any
@@ -3380,7 +3508,7 @@ sequences and that are not listed in the table stand for themselves:
      The alternation applies to the largest possible regexps on either
      side.
 
-`(...)'
+`('...`)'
      Parentheses are used for grouping in regular expressions, as in
      arithmetic.  They can be used to concatenate regular expressions
      containing the alternation operator, `|'.  For example,
@@ -3407,8 +3535,8 @@ sequences and that are not listed in the table stand for themselves:
      This symbol is similar to `*', except that the preceding
      expression must be matched at least once.  This means that `wh+y'
      would match `why' and `whhy', but not `wy', whereas `wh*y' would
-     match all three of these strings.  The following is a simpler way
-     of writing the last `*' example:
+     match all three.  The following is a simpler way of writing the
+     last `*' example:
 
           awk '/\(c[ad]+r x\)/ { print }' sample
 
@@ -3417,9 +3545,9 @@ sequences and that are not listed in the table stand for themselves:
      expression can be matched either once or not at all.  For example,
      `fe?d' matches `fed' and `fd', but nothing else.
 
-`{N}'
-`{N,}'
-`{N,M}'
+`{'N`}'
+`{'N`,}'
+`{'N`,'M`}'
      One or two numbers inside braces denote an "interval expression".
      If there is one number in the braces, the preceding regexp is
      repeated N times.  If there are two numbers separated by a comma,
@@ -3699,7 +3827,9 @@ works in any POSIX-compliant `awk'.
    Another method, specific to `gawk', is to set the variable
 `IGNORECASE' to a nonzero value (*note Built-in Variables::).  When
 `IGNORECASE' is not zero, _all_ regexp and string operations ignore
-case.  Changing the value of `IGNORECASE' dynamically controls the
+case.
+
+   Changing the value of `IGNORECASE' dynamically controls the
 case-sensitivity of the program as it runs.  Case is significant by
 default because `IGNORECASE' (like most variables) is initialized to
 zero:
@@ -3722,9 +3852,6 @@ dynamically turn case-sensitivity on or off for all the rules at once.
 `IGNORECASE' from the command line is a way to make a program
 case-insensitive without having to edit it.
 
-   Both regexp and string comparison operations are affected by
-`IGNORECASE'.
-
    In multibyte locales, the equivalences between upper- and lowercase
 characters are tested based on the wide-character values of the
 locale's character set.  Otherwise, the characters are tested based on
@@ -3777,7 +3904,7 @@ this principle is also important for regexp-based record and field
 splitting (*note Records::, and also *note Field Separators::).
 
 
-File: gawk.info,  Node: Computed Regexps,  Prev: Leftmost Longest,  Up: Regexp
+File: gawk.info,  Node: Computed Regexps,  Next: Regexp Summary,  Prev: Leftmost Longest,  Up: Regexp
 
 3.8 Using Dynamic Regexps
 =========================
@@ -3786,7 +3913,8 @@ The righthand side of a `~' or `!~' operator need not be a regexp
 constant (i.e., a string of characters between slashes).  It may be any
 expression.  The expression is evaluated and converted to a string if
 necessary; the contents of the string are then used as the regexp.  A
-regexp computed in this way is called a "dynamic regexp":
+regexp computed in this way is called a "dynamic regexp" or a "computed
+regexp":
 
      BEGIN { digits_regexp = "[[:digit:]]+" }
      $0 ~ digits_regexp    { print }
@@ -3834,8 +3962,8 @@ constants," for several reasons:
 
          Using `\n' in Bracket Expressions of Dynamic Regexps
 
-   Some commercial versions of `awk' do not allow the newline character
-to be used inside a bracket expression for a dynamic regexp:
+   Some versions of `awk' do not allow the newline character to be used
+inside a bracket expression for a dynamic regexp:
 
      $ awk '$0 ~ "[ \t\n]"'
      error--> awk: newline in character class [
@@ -3855,6 +3983,44 @@ to be used inside a bracket expression for a dynamic regexp:
 often in practice, but it's worth noting for future reference.
 
 
+File: gawk.info,  Node: Regexp Summary,  Prev: Computed Regexps,  Up: Regexp
+
+3.9 Summary
+===========
+
+   * Regular expressions describe sets of strings to be matched.  In
+     `awk', regular expression constants are written enclosed between
+     slashes: `/'...`/'.
+
+   * Regexp constants may be used by standalone in patterns and in
+     conditional expressions, or as part of matching expressions using
+     the `~' and `!~' operators.
+
+   * Escape sequences let you represent non-printable characters and
+     also let you represent regexp metacharacters as literal characters
+     to be matched.
+
+   * Regexp operators provide grouping, alternation and repetition.
+
+   * Bracket expressions give you a shorthand for specifying sets of
+     characters that can match at a particular point in a regexp.
+     Within bracket expressions, POSIX character classes let you specify
+     certain groups of characters in a locale-independent fashion.
+
+   * `gawk''s `IGNORECASE' variable lets you control the case
+     sensitivity of regexp matching.  In other `awk' versions, use
+     `tolower()' or `toupper()'.
+
+   * Regular expressions match the leftmost longest text in the string
+     being matched.  This matters for cases where you need to know the
+     extent of the match, such as for text substitution and when the
+     record separator is a regexp.
+
+   * Matching expressions may use dynamic regexps; that is string values
+     treated as regular expressions.
+
+
+
 File: gawk.info,  Node: Reading Files,  Next: Printing,  Prev: Regexp,  Up: Top
 
 4 Reading Input Files
@@ -3894,6 +4060,8 @@ have to be named on the `awk' command line (*note Getline::).
 * Read Timeout::                Reading input with a timeout.
 * Command line directories::    What happens if you put a directory on the
                                 command line.
+* Input Summary::               Input summary.
+* Input Exercises::             Exercises.
 
 
 File: gawk.info,  Node: Records,  Next: Fields,  Up: Reading Files
@@ -3909,8 +4077,19 @@ started.  Another built-in variable, `NR', records the total number of
 input records read so far from all data files.  It starts at zero, but
 is never automatically reset to zero.
 
-   Records are separated by a character called the "record separator".
-By default, the record separator is the newline character.  This is why
+* Menu:
+
+* awk split records::           How standard `awk' splits records.
+* gawk split records::          How `gawk' splits records.
+
+
+File: gawk.info,  Node: awk split records,  Next: gawk split records,  Up: Records
+
+4.1.1 Record Splitting With Standard `awk'
+------------------------------------------
+
+Records are separated by a character called the "record separator".  By
+default, the record separator is the newline character.  This is why
 records are, by default, single lines.  A different character can be
 used for the record separator by assigning the character to the
 built-in variable `RS'.
@@ -3924,67 +4103,82 @@ processed, so that the very first record is read with the proper
 separator.  To do this, use the special `BEGIN' pattern (*note
 BEGIN/END::).  For example:
 
-     awk 'BEGIN { RS = "/" }
-          { print $0 }' BBS-list
-
-changes the value of `RS' to `"/"', before reading any input.  This is
-a string whose first character is a slash; as a result, records are
-separated by slashes.  Then the input file is read, and the second rule
-in the `awk' program (the action with no pattern) prints each record.
-Because each `print' statement adds a newline at the end of its output,
-this `awk' program copies the input with each slash changed to a
-newline.  Here are the results of running the program on `BBS-list':
-
-     $ awk 'BEGIN { RS = "/" }
-     >      { print $0 }' BBS-list
-     -| aardvark     555-5553     1200
-     -| 300          B
-     -| alpo-net     555-3412     2400
-     -| 1200
-     -| 300     A
-     -| barfly       555-7685     1200
-     -| 300          A
-     -| bites        555-1675     2400
-     -| 1200
-     -| 300     A
-     -| camelot      555-0542     300               C
-     -| core         555-2912     1200
-     -| 300          C
-     -| fooey        555-1234     2400
-     -| 1200
-     -| 300     B
-     -| foot         555-6699     1200
-     -| 300          B
-     -| macfoo       555-6480     1200
-     -| 300          A
-     -| sdace        555-3430     2400
-     -| 1200
-     -| 300     A
-     -| sabafoo      555-2127     1200
-     -| 300          C
+     awk 'BEGIN { RS = "u" }
+          { print $0 }' mail-list
+
+changes the value of `RS' to `u', before reading any input.  This is a
+string whose first character is the letter "u;" as a result, records
+are separated by the letter "u."  Then the input file is read, and the
+second rule in the `awk' program (the action with no pattern) prints
+each record.  Because each `print' statement adds a newline at the end
+of its output, this `awk' program copies the input with each `u'
+changed to a newline.  Here are the results of running the program on
+`mail-list':
+
+     $ awk 'BEGIN { RS = "u" }
+     >      { print $0 }' mail-list
+     -| Amelia       555-5553     amelia.zodiac
+     -| sq
+     -| e@gmail.com    F
+     -| Anthony      555-3412     anthony.assert
+     -| ro@hotmail.com   A
+     -| Becky        555-7685     becky.algebrar
+     -| m@gmail.com      A
+     -| Bill         555-1675     bill.drowning@hotmail.com       A
+     -| Broderick    555-0542     broderick.aliq
+     -| otiens@yahoo.com R
+     -| Camilla      555-2912     camilla.inf
+     -| sar
+     -| m@skynet.be     R
+     -| Fabi
+     -| s       555-1234     fabi
+     -| s.
+     -| ndevicesim
+     -| s@
+     -| cb.ed
+     -|     F
+     -| J
+     -| lie        555-6699     j
+     -| lie.perscr
+     -| tabor@skeeve.com   F
+     -| Martin       555-6480     martin.codicib
+     -| s@hotmail.com    A
+     -| Sam
+     -| el       555-3430     sam
+     -| el.lanceolis@sh
+     -| .ed
+     -|         A
+     -| Jean-Pa
+     -| l    555-2127     jeanpa
+     -| l.campanor
+     -| m@ny
+     -| .ed
+     -|      R
      -|
 
-Note that the entry for the `camelot' BBS is not split.  In the
-original data file (*note Sample Data Files::), the line looks like
-this:
+Note that the entry for the name `Bill' is not split.  In the original
+data file (*note Sample Data Files::), the line looks like this:
 
-     camelot      555-0542     300               C
+     Bill         555-1675     bill.drowning@hotmail.com       A
 
-It has one baud rate only, so there are no slashes in the record,
-unlike the others which have two or more baud rates.  In fact, this
-record is treated as part of the record for the `core' BBS; the newline
+It contains no `u' so there is no reason to split the record, unlike
+the others which have one or more occurrences of the `u'.  In fact,
+this record is treated as part of the previous record; the newline
 separating them in the output is the original newline in the data file,
 not the one added by `awk' when it printed the record!
 
    Another way to change the record separator is on the command line,
 using the variable-assignment feature (*note Other Arguments::):
 
-     awk '{ print $0 }' RS="/" BBS-list
+     awk '{ print $0 }' RS="u" mail-list
 
-This sets `RS' to `/' before processing `BBS-list'.
+This sets `RS' to `u' before processing `mail-list'.
 
-   Using an unusual character such as `/' for the record separator
-produces correct behavior in the vast majority of cases.
+   Using an alphabetic character such as `u' for the record separator
+is highly likely to produce strange results.  Using an unusual
+character such as `/' is more likely to produce correct behavior in the
+majority of cases, but there are no guarantees. The moral is: Know Your
+Data.
 
    There is one unusual case, that occurs when `gawk' is being fully
 POSIX-compliant (*note Options::).  Then, the following (extreme)
@@ -4015,16 +4209,22 @@ affected.
    After the end of the record has been determined, `gawk' sets the
 variable `RT' to the text in the input that matched `RS'.
 
-   When using `gawk', the value of `RS' is not limited to a
-one-character string.  It can be any regular expression (*note
-Regexp::). (c.e.)  In general, each record ends at the next string that
-matches the regular expression; the next record starts at the end of
-the matching string.  This general rule is actually at work in the
-usual case, where `RS' contains just a newline: a record ends at the
-beginning of the next matching string (the next newline in the input),
-and the following record starts just after the end of this string (at
-the first character of the following line).  The newline, because it
-matches `RS', is not part of either record.
+
+File: gawk.info,  Node: gawk split records,  Prev: awk split records,  Up: Records
+
+4.1.2 Record Splitting With `gawk'
+----------------------------------
+
+When using `gawk', the value of `RS' is not limited to a one-character
+string.  It can be any regular expression (*note Regexp::). (c.e.)  In
+general, each record ends at the next string that matches the regular
+expression; the next record starts at the end of the matching string.
+This general rule is actually at work in the usual case, where `RS'
+contains just a newline: a record ends at the beginning of the next
+matching string (the next newline in the input), and the following
+record starts just after the end of this string (at the first character
+of the following line).  The newline, because it matches `RS', is not
+part of either record.
 
    When `RS' is a single character, `RT' contains the same single
 character. However, when `RS' is a regular expression, `RT' contains
@@ -4087,17 +4287,23 @@ use for `RS' in this case:
      BEGIN { RS = "\0" }  # whole file becomes one record?
 
    `gawk' in fact accepts this, and uses the NUL character for the
-record separator.  However, this usage is _not_ portable to other `awk'
-implementations.
+record separator.  This works for certain special files, such as
+`/proc/environ' on GNU/Linux systems, where the NUL character is in
+fact the record separator.  However, this usage is _not_ portable to
+most other `awk' implementations.
 
-   All other `awk' implementations(1) store strings internally as
-C-style strings.  C strings use the NUL character as the string
+   Almost all other `awk' implementations(1) store strings internally
+as C-style strings.  C strings use the NUL character as the string
 terminator.  In effect, this means that `RS = "\0"' is the same as `RS
 = ""'.  (d.c.)
 
-   The best way to treat a whole file as a single record is to simply
-read the file in, one record at a time, concatenating each record onto
-the end of the previous ones.
+   It happens that recent versions of `mawk' can use the NUL character
+as a record separator. However, this is a special case: `mawk' does not
+allow embedded NUL characters in strings.
+
+   *Note Readfile Function::, for an interesting, portable way to read
+whole files.  If you are using `gawk', see *note Extension Sample
+Readfile::, for another option.
 
    ---------- Footnotes ----------
 
@@ -4122,7 +4328,7 @@ to these pieces of the record.  You don't have to use them--you can
 operate on the whole record if you want--but fields are what make
 simple `awk' programs so powerful.
 
-   A dollar-sign (`$') is used to refer to a field in an `awk' program,
+   You use a dollar-sign (`$') to refer to a field in an `awk' program,
 followed by the number of the field you want.  Thus, `$1' refers to the
 first field, `$2' to the second, and so on.  (Unlike the Unix shells,
 the field numbers are not limited to single digits.  `$127' is the one
@@ -4145,29 +4351,28 @@ the last one (such as `$8' when the record has only seven fields), you
 get the empty string.  (If used in a numeric operation, you get zero.)
 
    The use of `$0', which looks like a reference to the "zero-th"
-field, is a special case: it represents the whole input record when you
-are not interested in specific fields.  Here are some more examples:
+field, is a special case: it represents the whole input record. Use it
+when you are not interested in specific fields.  Here are some more
+examples:
 
-     $ awk '$1 ~ /foo/ { print $0 }' BBS-list
-     -| fooey        555-1234     2400/1200/300     B
-     -| foot         555-6699     1200/300          B
-     -| macfoo       555-6480     1200/300          A
-     -| sabafoo      555-2127     1200/300          C
+     $ awk '$1 ~ /li/ { print $0 }' mail-list
+     -| Amelia       555-5553     amelia.zodiacusque@gmail.com    F
+     -| Julie        555-6699     julie.perscrutabor@skeeve.com   F
 
-This example prints each record in the file `BBS-list' whose first
-field contains the string `foo'.  The operator `~' is called a
-"matching operator" (*note Regexp Usage::); it tests whether a string
-(here, the field `$1') matches a given regular expression.
+This example prints each record in the file `mail-list' whose first
+field contains the string `li'.  The operator `~' is called a "matching
+operator" (*note Regexp Usage::); it tests whether a string (here, the
+field `$1') matches a given regular expression.
 
-   By contrast, the following example looks for `foo' in _the entire
+   By contrast, the following example looks for `li' in _the entire
 record_ and prints the first field and the last field for each matching
 input record:
 
-     $ awk '/foo/ { print $1, $NF }' BBS-list
-     -| fooey B
-     -| foot B
-     -| macfoo A
-     -| sabafoo C
+     $ awk '/li/ { print $1, $NF }' mail-list
+     -| Amelia F
+     -| Broderick R
+     -| Julie F
+     -| Samuel A
 
    ---------- Footnotes ----------
 
@@ -4180,11 +4385,11 @@ File: gawk.info,  Node: Nonconstant Fields,  Next: Changing Fields,  Prev: Field
 4.3 Nonconstant Field Numbers
 =============================
 
-The number of a field does not need to be a constant.  Any expression in
-the `awk' language can be used after a `$' to refer to a field.  The
-value of the expression specifies the field number.  If the value is a
-string, rather than a number, it is converted to a number.  Consider
-this example:
+A field number need not be a constant.  Any expression in the `awk'
+language can be used after a `$' to refer to a field.  The value of the
+expression specifies the field number.  If the value is a string,
+rather than a number, it is converted to a number.  Consider this
+example:
 
      awk '{ print $NR }'
 
@@ -4195,16 +4400,16 @@ For the twentieth record, field number 20 is printed; most likely, the
 record has fewer than 20 fields, so this prints a blank line.  Here is
 another example of using expressions as field numbers:
 
-     awk '{ print $(2*2) }' BBS-list
+     awk '{ print $(2*2) }' mail-list
 
    `awk' evaluates the expression `(2*2)' and uses its value as the
 number of the field to print.  The `*' sign represents multiplication,
 so the expression `2*2' evaluates to four.  The parentheses are used so
 that the multiplication is done before the `$' operation; they are
-necessary whenever there is a binary operator in the field-number
-expression.  This example, then, prints the hours of operation (the
-fourth field) for every line of the file `BBS-list'.  (All of the `awk'
-operators are listed, in order of decreasing precedence, in *note
+necessary whenever there is a binary operator(1) in the field-number
+expression.  This example, then, prints the type of relationship (the
+fourth field) for every line of the file `mail-list'.  (All of the
+`awk' operators are listed, in order of decreasing precedence, in *note
 Precedence::.)
 
    If the field number you compute is zero, you get the entire record.
@@ -4220,6 +4425,12 @@ Variables::).  The expression `$NF' is not a special feature--it is the
 direct consequence of evaluating `NF' and using its value as a field
 number.
 
+   ---------- Footnotes ----------
+
+   (1) A "binary operator", such as `*' for multiplication, is one that
+takes two operands. The distinction is required, since `awk' also has
+unary (one-operand) and ternary (three-operand) operators.
+
 
 File: gawk.info,  Node: Changing Fields,  Next: Field Separators,  Prev: Nonconstant Fields,  Up: Reading Files
 
@@ -4245,11 +4456,11 @@ three minus ten: `$3 - 10'.  (*Note Arithmetic Ops::.)  Then it prints
 the original and new values for field three.  (Someone in the warehouse
 made a consistent mistake while inventorying the red boxes.)
 
-   For this to work, the text in field `$3' must make sense as a
-number; the string of characters must be converted to a number for the
-computer to do arithmetic on it.  The number resulting from the
-subtraction is converted back to a string of characters that then
-becomes field three.  *Note Conversion::.
+   For this to work, the text in `$3' must make sense as a number; the
+string of characters must be converted to a number for the computer to
+do arithmetic on it.  The number resulting from the subtraction is
+converted back to a string of characters that then becomes field three.
+*Note Conversion::.
 
    When the value of a field is changed (as perceived by `awk'), the
 text of the input record is recalculated to contain the new field where
@@ -4314,7 +4525,7 @@ even when you assign the empty string to a field.  For example:
      -| a::c:d
      -| 4
 
-The field is still there; it just has an empty value, denoted by the
+The field is still there; it just has an empty value, delimited by the
 two colons between `a' and `c'.  This example shows what happens if you
 create a new field:
 
@@ -4381,6 +4592,7 @@ File: gawk.info,  Node: Field Separators,  Next: Constant Size,  Prev: Changing
 * Regexp Field Splitting::       Using regexps as the field separator.
 * Single Character Fields::      Making each character a separate field.
 * Command Line Field Separator:: Setting `FS' from the command-line.
+* Full Line Fields::             Making the full line be a single field.
 * Field Splitting Summary::      Some final points and a summary table.
 
    The "field separator", which is either a single character or a
@@ -4499,7 +4711,7 @@ letter):
      >                                  { print $2 }'
      -| a
 
-In this case, the first field is "null" or empty.
+In this case, the first field is null, or empty.
 
    The stripping of leading and trailing whitespace also comes into
 play whenever `$0' is recomputed.  For instance, study this pipeline:
@@ -4562,7 +4774,7 @@ Options::), if `FS' is the null string, then `gawk' also behaves this
 way.
 
 
-File: gawk.info,  Node: Command Line Field Separator,  Next: Field Splitting Summary,  Prev: Single Character Fields,  Up: Field Separators
+File: gawk.info,  Node: Command Line Field Separator,  Next: Full Line Fields,  Prev: Single Character Fields,  Up: Field Separators
 
 4.5.4 Setting `FS' from the Command Line
 ----------------------------------------
@@ -4600,58 +4812,69 @@ type `-F\t' at the shell, without any quotes, the `\' gets deleted, so
 TABs and not `t's.  Use `-v FS="t"' or `-F"[t]"' on the command line if
 you really do want to separate your fields with `t's.
 
-   As an example, let's use an `awk' program file called `baud.awk'
-that contains the pattern `/300/' and the action `print $1':
+   As an example, let's use an `awk' program file called `edu.awk' that
+contains the pattern `/edu/' and the action `print $1':
 
-     /300/   { print $1 }
+     /edu/   { print $1 }
 
    Let's also set `FS' to be the `-' character and run the program on
-the file `BBS-list'.  The following command prints a list of the names
-of the bulletin boards that operate at 300 baud and the first three
+the file `mail-list'.  The following command prints a list of the names
+of the people that work at or attend a university, and the first three
 digits of their phone numbers:
 
-     $ awk -F- -f baud.awk BBS-list
-     -| aardvark     555
-     -| alpo
-     -| barfly       555
-     -| bites        555
-     -| camelot      555
-     -| core         555
-     -| fooey        555
-     -| foot         555
-     -| macfoo       555
-     -| sdace        555
-     -| sabafoo      555
-
-Note the second line of output.  The second line in the original file
+     $ awk -F- -f edu.awk mail-list
+     -| Fabius       555
+     -| Samuel       555
+     -| Jean
+
+Note the third line of output.  The third line in the original file
 looked like this:
 
-     alpo-net     555-3412     2400/1200/300     A
+     Jean-Paul    555-2127     jeanpaul.campanorum@nyu.edu     R
 
-   The `-' as part of the system's name was used as the field
+   The `-' as part of the person's name was used as the field
 separator, instead of the `-' in the phone number that was originally
 intended.  This demonstrates why you have to be careful in choosing
 your field and record separators.
 
    Perhaps the most common use of a single character as the field
 separator occurs when processing the Unix system password file.  On
-many Unix systems, each user has a separate entry in the system password
-file, one line per user.  The information in these lines is separated
-by colons.  The first field is the user's login name and the second is
-the user's (encrypted or shadow) password.  A password file entry might
-look like this:
+many Unix systems, each user has a separate entry in the system
+password file, one line per user.  The information in these lines is
+separated by colons.  The first field is the user's login name and the
+second is the user's encrypted or shadow password.  (A shadow password
+is indicated by the presence of a single `x' in the second field.)  A
+password file entry might look like this:
 
-     arnold:xyzzy:2076:10:Arnold Robbins:/home/arnold:/bin/bash
+     arnold:x:2076:10:Arnold Robbins:/home/arnold:/bin/bash
 
    The following program searches the system password file and prints
-the entries for users who have no password:
+the entries for users whose full name is not indicated:
 
-     awk -F: '$2 == ""' /etc/passwd
+     awk -F: '$5 == ""' /etc/passwd
 
 
-File: gawk.info,  Node: Field Splitting Summary,  Prev: Command Line Field Separator,  Up: Field Separators
+File: gawk.info,  Node: Full Line Fields,  Next: Field Splitting Summary,  Prev: Command Line Field Separator,  Up: Field Separators
 
-4.5.5 Field-Splitting Summary
+4.5.5 Making The Full Line Be A Single Field
+--------------------------------------------
+
+Occasionally, it's useful to treat the whole input line as a single
+field.  This can be done easily and portably simply by setting `FS' to
+`"\n"' (a newline).(1)
+
+     awk -F'\n' 'PROGRAM' FILES ...
+
+When you do this, `$1' is the same as `$0'.
+
+   ---------- Footnotes ----------
+
+   (1) Thanks to Andrew Schorr for this tip.
+
+
+File: gawk.info,  Node: Field Splitting Summary,  Prev: Full Line Fields,  Up: Field Separators
+
+4.5.6 Field-Splitting Summary
 -----------------------------
 
 It is important to remember that when you assign a string constant as
@@ -4740,14 +4963,15 @@ File: gawk.info,  Node: Constant Size,  Next: Splitting By Content,  Prev: Field
 4.6 Reading Fixed-Width Data
 ============================
 
-(This minor node discusses an advanced feature of `awk'.  If you are a
-novice `awk' user, you might want to skip it on the first reading.)
+     NOTE: This minor node discusses an advanced feature of `gawk'.  If
+     you are a novice `awk' user, you might want to skip it on the
+     first reading.
 
-`gawk' provides a facility for dealing with fixed-width fields with no
-distinctive field separator.  For example, data of this nature arises
-in the input for old Fortran programs where numbers are run together,
-or in the output of programs that did not anticipate the use of their
-output as input for other programs.
+   `gawk' provides a facility for dealing with fixed-width fields with
+no distinctive field separator.  For example, data of this nature
+arises in the input for old Fortran programs where numbers are run
+together, or in the output of programs that did not anticipate the use
+of their output as input for other programs.
 
    An example of the latter is a table where all the columns are lined
 up by the use of a variable number of spaces and _empty fields are just
@@ -4846,10 +5070,11 @@ File: gawk.info,  Node: Splitting By Content,  Next: Multiple Line,  Prev: Const
 4.7 Defining Fields By Content
 ==============================
 
-(This minor node discusses an advanced feature of `awk'.  If you are a
-novice `awk' user, you might want to skip it on the first reading.)
+     NOTE: This minor node discusses an advanced feature of `gawk'.  If
+     you are a novice `awk' user, you might want to skip it on the
+     first reading.
 
-Normally, when using `FS', `gawk' defines the fields as the parts of
+   Normally, when using `FS', `gawk' defines the fields as the parts of
 the record that occur in between each field separator. In other words,
 `FS' defines what a field _is not_, instead of what a field _is_.
 However, there are times when you really want to define the fields by
@@ -4925,7 +5150,7 @@ affects field splitting with `FPAT'.
      deal with this.  Since there is no formal specification for CSV
      data, there isn't much more to be done; the `FPAT' mechanism
      provides an elegant solution for the majority of cases, and the
-     `gawk' maintainer is satisfied with that.
+     `gawk' developers are satisfied with that.
 
    As written, the regexp used for `FPAT' requires that each field have
 a least one character.  A straightforward modification (changing
@@ -4975,8 +5200,8 @@ doesn't start until the first nonblank line that follows--no matter how
 many blank lines appear in a row, they are considered one record
 separator.
 
-   There is an important difference between `RS = ""' and `RS =
-"\n\n+"'. In the first case, leading newlines in the input data file
+   However, there is an important difference between `RS = ""' and `RS
+= "\n\n+"'. In the first case, leading newlines in the input data file
 are ignored, and if a file ends without extra blank lines after the
 last record, the final newline is removed from the record.  In the
 second case, this special processing is not done.  (d.c.)
@@ -5086,7 +5311,7 @@ File: gawk.info,  Node: Getline,  Next: Read Timeout,  Prev: Multiple Line,  Up:
 =================================
 
 So far we have been getting our input data from `awk''s main input
-stream--either the standard input (usually your terminal, sometimes the
+stream--either the standard input (usually your keyboard, sometimes the
 output from another program) or from the files specified on the command
 line.  The `awk' language has a special built-in command called
 `getline' that can be used to read input under your explicit control.
@@ -5248,9 +5473,9 @@ are changed, resulting in a new value of `NF'.  `RT' is also set.
    According to POSIX, `getline < EXPRESSION' is ambiguous if
 EXPRESSION contains unparenthesized operators other than `$'; for
 example, `getline < dir "/" file' is ambiguous because the
-concatenation operator is not parenthesized.  You should write it as
-`getline < (dir "/" file)' if you want your program to be portable to
-all `awk' implementations.
+concatenation operator (not discussed yet; *note Concatenation::) is
+not parenthesized.  You should write it as `getline < (dir "/" file)' if
+you want your program to be portable to all `awk' implementations.
 
 
 File: gawk.info,  Node: Getline/Variable/File,  Next: Getline/Pipe,  Prev: Getline/File,  Up: Getline
@@ -5455,10 +5680,10 @@ in mind:
      testing the new record against every pattern.  However, the new
      record is tested against any subsequent rules.
 
-   * Many `awk' implementations limit the number of pipelines that an
-     `awk' program may have open to just one.  In `gawk', there is no
-     such limit.  You can open as many pipelines (and coprocesses) as
-     the underlying operating system permits.
+   * Some very old `awk' implementations limit the number of pipelines
+     that an `awk' program may have open to just one.  In `gawk', there
+     is no such limit.  You can open as many pipelines (and
+     coprocesses) as the underlying operating system permits.
 
    * An interesting side effect occurs if you use `getline' without a
      redirection inside a `BEGIN' rule. Because an unredirected
@@ -5497,9 +5722,9 @@ in mind:
      file is encountered, before the element in `a' is assigned?
 
      `gawk' treats `getline' like a function call, and evaluates the
-     expression `a[++c]' before attempting to read from `f'.  Other
-     versions of `awk' only evaluate the expression once they know that
-     there is a string value to be assigned.  Caveat Emptor.
+     expression `a[++c]' before attempting to read from `f'.  However,
+     some versions of `awk' only evaluate the expression once they know
+     that there is a string value to be assigned.  Caveat Emptor.
 
 
 File: gawk.info,  Node: Getline Summary,  Prev: Getline Notes,  Up: Getline
@@ -5535,10 +5760,12 @@ File: gawk.info,  Node: Read Timeout,  Next: Command line directories,  Prev: Ge
 4.10 Reading Input With A Timeout
 =================================
 
-You may specify a timeout in milliseconds for reading input from a
-terminal, pipe or two-way communication including, TCP/IP sockets. This
-can be done on a per input, command or connection basis, by setting a
-special element in the `PROCINFO' array:
+This minor node describes a feature that is specific to `gawk'.
+
+   You may specify a timeout in milliseconds for reading input from the
+keyboard, a pipe, or two-way communication, including TCP/IP sockets.
+This can be done on a per input, command or connection basis, by
+setting a special element in the `PROCINFO' (*note Auto-set::) array:
 
      PROCINFO["input_name", "READ_TIMEOUT"] = TIMEOUT IN MILLISECONDS
 
@@ -5554,19 +5781,19 @@ from the server after a certain amount of time:
      else if (ERRNO != "")
          print ERRNO
 
-   Here is how to read interactively from the terminal(1) without
-waiting for more than five seconds:
+   Here is how to read interactively from the user(1) without waiting
+for more than five seconds:
 
      PROCINFO["/dev/stdin", "READ_TIMEOUT"] = 5000
      while ((getline < "/dev/stdin") > 0)
          print $0
 
-   `gawk' will terminate the read operation if input does not arrive
-after waiting for the timeout period, return failure and set the
-`ERRNO' variable to an appropriate string value.  A negative or zero
-value for the timeout is the same as specifying no timeout at all.
+   `gawk' terminates the read operation if input does not arrive after
+waiting for the timeout period, returns failure and sets the `ERRNO'
+variable to an appropriate string value.  A negative or zero value for
+the timeout is the same as specifying no timeout at all.
 
-   A timeout can also be set for reading from the terminal in the
+   A timeout can also be set for reading from the keyboard in the
 implicit loop that reads input records and matches them against
 patterns, like so:
 
@@ -5619,23 +5846,118 @@ writing.
 
    ---------- Footnotes ----------
 
-   (1) This assumes that standard input is the keyboard
+   (1) This assumes that standard input is the keyboard.
 
 
-File: gawk.info,  Node: Command line directories,  Prev: Read Timeout,  Up: Reading Files
+File: gawk.info,  Node: Command line directories,  Next: Input Summary,  Prev: Read Timeout,  Up: Reading Files
 
 4.11 Directories On The Command Line
 ====================================
 
 According to the POSIX standard, files named on the `awk' command line
-must be text files.  It is a fatal error if they are not.  Most
-versions of `awk' treat a directory on the command line as a fatal
-error.
+must be text files; it is a fatal error if they are not.  Most versions
+of `awk' treat a directory on the command line as a fatal error.
 
    By default, `gawk' produces a warning for a directory on the command
-line, but otherwise ignores it.  If either of the `--posix' or
-`--traditional' options is given, then `gawk' reverts to treating a
-directory on the command line as a fatal error.
+line, but otherwise ignores it.  This makes it easier to use shell
+wildcards with your `awk' program:
+
+     $ gawk -f whizprog.awk *        Directories could kill this progam
+
+   If either of the `--posix' or `--traditional' options is given, then
+`gawk' reverts to treating a directory on the command line as a fatal
+error.
+
+   *Note Extension Sample Readdir::, for a way to treat directories as
+usable data from an `awk' program.
+
+
+File: gawk.info,  Node: Input Summary,  Next: Input Exercises,  Prev: Command line directories,  Up: Reading Files
+
+4.12 Summary
+============
+
+   * Input is split into records based on the value of `RS'.  The
+     possibilities are as follows:
+
+     Value of `RS'     Records are split on    `awk' / `gawk'
+     ---------------------------------------------------------------------- 
+     Any single        That character          `awk'
+     character                                 
+     The empty string  Runs of two or more     `awk'
+     (`""')            newlines                
+     A regexp          Text that matches the   `gawk'
+                       regexp                  
+
+   * `gawk' sets `RT' to the text matched by `RS'.
+
+   * After splitting the input into records, `awk' further splits the
+     record into individual fields, named `$1', `$2' and so on. `$0' is
+     the whole record, and `NF' indicates how many fields there are.
+     The default way to split fields is between whitespace characters.
+
+   * Fields may be referenced using a variable, as in `$NF'.  Fields
+     may also be assigned values, which causes the value of `$0' to be
+     recomputed when it is later referenced. Assigning to a field with
+     a number greater than `NF' creates the field and rebuilds the
+     record, using `OFS' to separate the fields.  Incrementing `NF'
+     does the same thing. Decrementing `NF' throws away fields and
+     rebuilds the record.
+
+   * Field splitting is more complicated than record splitting.
+
+     Field separator value       Fields are split ...        `awk' /
+                                                             `gawk'
+     ---------------------------------------------------------------------- 
+     `FS == " "'                 On runs of whitespace       `awk'
+     `FS == ANY SINGLE           On that character           `awk'
+     CHARACTER'                                              
+     `FS == REGEXP'              On text matching the        `awk'
+                                 regexp                      
+     `FS == ""'                  Each individual character   `gawk'
+                                 is a separate field         
+     `FIELDWIDTHS == LIST OF     Based on character          `gawk'
+     COLUMNS'                    position                    
+     `FPAT == REGEXP'            On text around text         `gawk'
+                                 matching the regexp         
+
+     Using `FS = "\n"' causes the entire record to be a single field
+     (assuming that newlines separate records).
+
+   * `FS' may be set from the command line using the `-F' option.  This
+     can also be done using command-line variable assignment.
+
+   * `PROCINFO["FS"]' can be used to see how fields are being split.
+
+   * Use `getline' in its various forms to read additional records,
+     from the default input stream, from a file, or from a pipe or
+     co-process.
+
+   * Use `PROCINFO[FILE, "READ_TIMEOUT"]' to cause reads to timeout for
+     FILE.
+
+   * Directories on the command line are fatal for standard `awk';
+     `gawk' ignores them if not in POSIX mode.
+
+
+
+File: gawk.info,  Node: Input Exercises,  Prev: Input Summary,  Up: Reading Files
+
+4.13 Exercises
+==============
+
+  1. Using the `FIELDWIDTHS' variable (*note Constant Size::), write a
+     program to read election data, where each record represents one
+     voter's votes.  Come up with a way to define which columns are
+     associated with each ballot item, and print the total votes,
+     including abstentions, for each item.
+
+  2. *note Plain Getline::, presented a program to remove C-style
+     comments (`/* ... */') from the input.  That program does not work
+     if one comment ends on one line and another one starts later on
+     the same line.  Write a program that does handle multiple comments
+     on the line.
+
 
 
 File: gawk.info,  Node: Printing,  Next: Expressions,  Prev: Reading Files,  Up: Top
@@ -5671,6 +5993,8 @@ function.
                                 `gawk' allows access to inherited file
                                 descriptors.
 * Close Files And Pipes::       Closing Input and Output Files and Pipes.
+* Output Summary::              Output summary.
+* Output exercises::            Exercises.
 
 
 File: gawk.info,  Node: Print,  Next: Print Examples,  Up: Printing
@@ -5679,9 +6003,9 @@ File: gawk.info,  Node: Print,  Next: Print Examples,  Up: Printing
 =========================
 
 The `print' statement is used for producing output with simple,
-standardized formatting.  Specify only the strings or numbers to print,
-in a list separated by commas.  They are output, separated by single
-spaces, followed by a newline.  The statement looks like this:
+standardized formatting.  You specify only the strings or numbers to
+print, in a list separated by commas.  They are output, separated by
+single spaces, followed by a newline.  The statement looks like this:
 
      print ITEM1, ITEM2, ...
 
@@ -5748,8 +6072,8 @@ Here is the same program, without the comma:
    To someone unfamiliar with the `inventory-shipped' file, neither
 example's output makes much sense.  A heading line at the beginning
 would make it clearer.  Let's add some headings to our table of months
-(`$1') and green crates shipped (`$2').  We do this using the `BEGIN'
-pattern (*note BEGIN/END::) so that the headings are only printed once:
+(`$1') and green crates shipped (`$2').  We do this using a `BEGIN'
+rule (*note BEGIN/END::) so that the headings are only printed once:
 
      awk 'BEGIN {  print "Month Crates"
                    print "----- ------" }
@@ -5812,13 +6136,29 @@ prints the first and second fields of each input record, separated by a
 semicolon, with a blank line added after each newline:
 
      $ awk 'BEGIN { OFS = ";"; ORS = "\n\n" }
-     >            { print $1, $2 }' BBS-list
-     -| aardvark;555-5553
+     >            { print $1, $2 }' mail-list
+     -| Amelia;555-5553
      -|
-     -| alpo-net;555-3412
+     -| Anthony;555-3412
+     -|
+     -| Becky;555-7685
+     -|
+     -| Bill;555-1675
+     -|
+     -| Broderick;555-0542
+     -|
+     -| Camilla;555-2912
+     -|
+     -| Fabius;555-1234
+     -|
+     -| Julie;555-6699
+     -|
+     -| Martin;555-6480
+     -|
+     -| Samuel;555-3430
+     -|
+     -| Jean-Paul;555-2127
      -|
-     -| barfly;555-7685
-     ...
 
    If the value of `ORS' does not contain a newline, the program's
 output runs together on a single line.
@@ -5946,11 +6286,11 @@ width.  Here is a list of the format-control letters:
           the first byte of a string or to numeric values within the
           range of a single byte (0-255).
 
-`%d, %i'
+`%d', `%i'
      Print a decimal integer.  The two control letters are equivalent.
      (The `%i' specification is for compatibility with ISO C.)
 
-`%e, %E'
+`%e', `%E'
      Print a number in scientific (exponential) notation; for example:
 
           printf "%4.3e\n", 1950
@@ -5972,7 +6312,8 @@ width.  Here is a list of the format-control letters:
      On systems supporting IEEE 754 floating point format, values
      representing negative infinity are formatted as `-inf' or
      `-infinity', and positive infinity as `inf' and `infinity'.  The
-     special "not a number" value formats as `-nan' or `nan'.
+     special "not a number" value formats as `-nan' or `nan' (*note
+     Math Definitions::).
 
 `%F'
      Like `%f' but the infinity and "not a number" values are spelled
@@ -5981,7 +6322,7 @@ width.  Here is a list of the format-control letters:
      The `%F' format is a POSIX extension to ISO C; not all systems
      support it.  On those that don't, `gawk' uses `%f' instead.
 
-`%g, %G'
+`%g', `%G'
      Print a number in either scientific notation or in floating-point
      notation, whichever uses fewer characters; if the result is
      printed in scientific notation, `%G' uses `E' instead of `e'.
@@ -5997,7 +6338,7 @@ width.  Here is a list of the format-control letters:
      use, because all numbers in `awk' are floating-point; it is
      provided primarily for compatibility with C.)
 
-`%x, %X'
+`%x', `%X'
      Print an unsigned hexadecimal integer; `%X' uses the letters `A'
      through `F' instead of `a' through `f' (*note
      Nondecimal-numbers::).
@@ -6172,11 +6513,12 @@ string, like so:
 
 This is not particularly easy to read but it does work.
 
-   C programmers may be used to supplying additional `l', `L', and `h'
-modifiers in `printf' format strings. These are not valid in `awk'.
-Most `awk' implementations silently ignore them.  If `--lint' is
-provided on the command line (*note Options::), `gawk' warns about
-their use. If `--posix' is supplied, their use is a fatal error.
+   C programmers may be used to supplying additional modifiers (`h',
+`j', `l', `L', `t', and `z') in `printf' format strings. These are not
+valid in `awk'.  Most `awk' implementations silently ignore them.  If
+`--lint' is provided on the command line (*note Options::), `gawk'
+warns about their use. If `--posix' is supplied, their use is a fatal
+error.
 
 
 File: gawk.info,  Node: Printf Examples,  Prev: Format Modifiers,  Up: Printf
@@ -6187,25 +6529,25 @@ File: gawk.info,  Node: Printf Examples,  Prev: Format Modifiers,  Up: Printf
 The following simple example shows how to use `printf' to make an
 aligned table:
 
-     awk '{ printf "%-10s %s\n", $1, $2 }' BBS-list
+     awk '{ printf "%-10s %s\n", $1, $2 }' mail-list
 
-This command prints the names of the bulletin boards (`$1') in the file
-`BBS-list' as a string of 10 characters that are left-justified.  It
+This command prints the names of the people (`$1') in the file
+`mail-list' as a string of 10 characters that are left-justified.  It
 also prints the phone numbers (`$2') next on the line.  This produces
 an aligned two-column table of names and phone numbers, as shown here:
 
-     $ awk '{ printf "%-10s %s\n", $1, $2 }' BBS-list
-     -| aardvark   555-5553
-     -| alpo-net   555-3412
-     -| barfly     555-7685
-     -| bites      555-1675
-     -| camelot    555-0542
-     -| core       555-2912
-     -| fooey      555-1234
-     -| foot       555-6699
-     -| macfoo     555-6480
-     -| sdace      555-3430
-     -| sabafoo    555-2127
+     $ awk '{ printf "%-10s %s\n", $1, $2 }' mail-list
+     -| Amelia     555-5553
+     -| Anthony    555-3412
+     -| Becky      555-7685
+     -| Bill       555-1675
+     -| Broderick  555-0542
+     -| Camilla    555-2912
+     -| Fabius     555-1234
+     -| Julie      555-6699
+     -| Martin     555-6480
+     -| Samuel     555-3430
+     -| Jean-Paul  555-2127
 
    In this case, the phone numbers had to be printed as strings because
 the numbers are separated by a dash.  Printing the phone numbers as
@@ -6217,20 +6559,20 @@ they are last on their lines.  They don't need to have spaces after
 them.
 
    The table could be made to look even nicer by adding headings to the
-tops of the columns.  This is done using the `BEGIN' pattern (*note
+tops of the columns.  This is done using a `BEGIN' rule (*note
 BEGIN/END::) so that the headers are only printed once, at the
 beginning of the `awk' program:
 
      awk 'BEGIN { print "Name      Number"
                   print "----      ------" }
-          { printf "%-10s %s\n", $1, $2 }' BBS-list
+          { printf "%-10s %s\n", $1, $2 }' mail-list
 
    The above example mixes `print' and `printf' statements in the same
 program.  Using just `printf' statements can produce the same results:
 
      awk 'BEGIN { printf "%-10s %s\n", "Name", "Number"
                   printf "%-10s %s\n", "----", "------" }
-          { printf "%-10s %s\n", $1, $2 }' BBS-list
+          { printf "%-10s %s\n", $1, $2 }' mail-list
 
 Printing each column heading with the same format specification used
 for the column elements ensures that the headings are aligned just like
@@ -6242,12 +6584,7 @@ be emphasized by storing it in a variable, like this:
      awk 'BEGIN { format = "%-10s %s\n"
                   printf format, "Name", "Number"
                   printf format, "----", "------" }
-          { printf format, $1, $2 }' BBS-list
-
-   At this point, it would be a worthwhile exercise to use the `printf'
-statement to line up the headings and table data for the
-`inventory-shipped' example that was covered earlier in the minor node
-on the `print' statement (*note Print::).
+          { printf format, $1, $2 }' mail-list
 
 
 File: gawk.info,  Node: Redirection,  Next: Special Files,  Prev: Printf,  Up: Printing
@@ -6268,7 +6605,7 @@ commands, except that they are written inside the `awk' program.
 
    There are four forms of output redirection: output to a file, output
 appended to a file, output through a pipe to another command, and output
-to a coprocess.  They are all shown for the `print' statement, but they
+to a coprocess.  We show them all for the `print' statement, but they
 work identically for `printf':
 
 `print ITEMS > OUTPUT-FILE'
@@ -6282,19 +6619,19 @@ work identically for `printf':
      the same OUTPUT-FILE do not erase OUTPUT-FILE, but append to it.
      (This is different from how you use redirections in shell scripts.)
      If OUTPUT-FILE does not exist, it is created.  For example, here
-     is how an `awk' program can write a list of BBS names to one file
-     named `name-list', and a list of phone numbers to another file
+     is how an `awk' program can write a list of peoples' names to one
+     file named `name-list', and a list of phone numbers to another file
      named `phone-list':
 
           $ awk '{ print $2 > "phone-list"
-          >        print $1 > "name-list" }' BBS-list
+          >        print $1 > "name-list" }' mail-list
           $ cat phone-list
           -| 555-5553
           -| 555-3412
           ...
           $ cat name-list
-          -| aardvark
-          -| alpo-net
+          -| Amelia
+          -| Anthony
           ...
 
      Each output file contains one name or number per line.
@@ -6315,12 +6652,12 @@ work identically for `printf':
      The redirection argument COMMAND is actually an `awk' expression.
      Its value is converted to a string whose contents give the shell
      command to be run.  For example, the following produces two files,
-     one unsorted list of BBS names, and one list sorted in reverse
+     one unsorted list of peoples' names, and one list sorted in reverse
      alphabetical order:
 
           awk '{ print $1 > "names.unsorted"
                  command = "sort -r > names.sorted"
-                 print $1 | command }' BBS-list
+                 print $1 | command }' mail-list
 
      The unsorted list is written with an ordinary redirection, while
      the sorted list is written by piping through the `sort' utility.
@@ -6349,7 +6686,7 @@ work identically for `printf':
      FILE or COMMAND--it is not necessary to always use a string
      constant.  Using a variable is generally a good idea, because (if
      you mean to refer to that same file or command) `awk' requires
-     that the string value be spelled identically every time.
+     that the string value be written identically every time.
 
 `print ITEMS |& COMMAND'
      This redirection prints the items to the input of COMMAND.  The
@@ -6409,8 +6746,8 @@ to rename the files.  It then sends the list to the shell for execution.
 
 File: gawk.info,  Node: Special Files,  Next: Close Files And Pipes,  Prev: Redirection,  Up: Printing
 
-5.7 Special File Names in `gawk'
-================================
+5.7 Special File Name in `gawk'
+===============================
 
 `gawk' provides a number of special file names that it interprets
 internally.  These file names provide access to standard file
@@ -6461,7 +6798,7 @@ run from a background job, it may not have a terminal at all.  Then
 opening `/dev/tty' fails.
 
    `gawk' provides special file names for accessing the three standard
-streams. (c.e.). It also provides syntax for accessing any other
+streams. (c.e.) It also provides syntax for accessing any other
 inherited open files.  If the file name matches one of these special
 names when `gawk' redirects input or output, then it directly uses the
 stream that the file name stands for.  These special file names work
@@ -6546,7 +6883,7 @@ names that `gawk' provides:
      behavior.
 
 
-File: gawk.info,  Node: Close Files And Pipes,  Prev: Special Files,  Up: Printing
+File: gawk.info,  Node: Close Files And Pipes,  Next: Output Summary,  Prev: Special Files,  Up: Printing
 
 5.8 Closing Input and Output Redirections
 =========================================
@@ -6654,14 +6991,15 @@ end-of-file return status from `getline'), the child process is not
 terminated;(1) more importantly, the file descriptor for the pipe is
 not closed and released until `close()' is called or `awk' exits.
 
-   `close()' will silently do nothing if given an argument that does
-not represent a file, pipe or coprocess that was opened with a
-redirection.
+   `close()' silently does nothing if given an argument that does not
+represent a file, pipe or coprocess that was opened with a redirection.
+In such a case, it returns a negative value, indicating an error. In
+addition, `gawk' sets `ERRNO' to a string indicating the error.
 
    Note also that `close(FILENAME)' has no "magic" effects on the
 implicit loop that reads through the files named on the command line.
-It is, more likely, a close of a file that was never opened, so `awk'
-silently does nothing.
+It is, more likely, a close of a file that was never opened with a
+redirection, so `awk' silently does nothing.
 
    When using the `|&' operator to communicate with a coprocess, it is
 occasionally useful to be able to close one end of the two-way pipe
@@ -6675,9 +7013,9 @@ I/O::, which discusses it in more detail and gives an example.
 
                     Using `close()''s Return Value
 
-   In many versions of Unix `awk', the `close()' function is actually a
-statement.  It is a syntax error to try and use the return value from
-`close()': (d.c.)
+   In many older versions of Unix `awk', the `close()' function is
+actually a statement.  It is a syntax error to try and use the return
+value from `close()': (d.c.)
 
      command = "..."
      command | getline info
@@ -6712,6 +7050,56 @@ call. See the system manual pages for information on how to decode this
 value.
 
 
+File: gawk.info,  Node: Output Summary,  Next: Output exercises,  Prev: Close Files And Pipes,  Up: Printing
+
+5.9 Summary
+===========
+
+   * The `print' statement prints comma-separated expressions. Each
+     expression is separated by the value of `OFS' and terminated by
+     the value of `ORS'.  `OFMT' provides the conversion format for
+     numeric values for the `print' statement.
+
+   * The `printf' statement provides finer-grained control over output,
+     with format control letters for different data types and various
+     flags that modify the behavior of the format control letters.
+
+   * Output from both `print' and `printf' may be redirected to files,
+     pipes, and co-processes.
+
+   * `gawk' provides special file names for access to standard input,
+     output and error, and for network communications.
+
+   * Use `close()' to close open file, pipe and co-process redirections.
+     For co-processes, it is possible to close only one direction of the
+     communications.
+
+
+
+File: gawk.info,  Node: Output exercises,  Prev: Output Summary,  Up: Printing
+
+5.10 Exercises
+==============
+
+  1. Rewrite the program:
+
+          awk 'BEGIN { print "Month Crates"
+                       print "----- ------" }
+                     { print $1, "     ", $2 }' inventory-shipped
+
+     from *note Output Separators::, by using a new value of `OFS'.
+
+  2. Use the `printf' statement to line up the headings and table data
+     for the `inventory-shipped' example that was covered in *note
+     Print::.
+
+  3. What happens if you forget the double quotes when redirecting
+     output, as follows:
+
+          BEGIN { print "Serious error detected!" > /dev/stderr }
+
+
+
 File: gawk.info,  Node: Expressions,  Next: Patterns and Actions,  Prev: Printing,  Up: Top
 
 6 Expressions
@@ -6737,6 +7125,7 @@ operators.
 * Function Calls::              A function call is an expression.
 * Precedence::                  How various operators nest.
 * Locales::                     How the locale affects things.
+* Expressions Summary::         Expressions summary.
 
 
 File: gawk.info,  Node: Values,  Next: All Operators,  Up: Expressions
@@ -6806,7 +7195,8 @@ codes.
 
    (1) The internal representation of all numbers, including integers,
 uses double precision floating-point numbers.  On most modern systems,
-these are in IEEE 754 standard format.
+these are in IEEE 754 standard format.  *Note Arbitrary Precision
+Arithmetic::, for much more information.
 
 
 File: gawk.info,  Node: Nondecimal-numbers,  Next: Regexp Constants,  Prev: Scalar Constants,  Up: Constants
@@ -6939,8 +7329,8 @@ the contents of the current input record.
 
    Constant regular expressions are also used as the first argument for
 the `gensub()', `sub()', and `gsub()' functions, as the second argument
-of the `match()' function, and as the third argument of the
-`patsplit()' function (*note String Functions::).  Modern
+of the `match()' function, and as the third argument of the `split()'
+and `patsplit()' functions (*note String Functions::).  Modern
 implementations of `awk', including `gawk', allow the third argument of
 `split()' to be a regexp constant, but some older implementations do
 not.  (d.c.)  This can lead to confusion when attempting to use regexp
@@ -7050,16 +7440,16 @@ assignment is performed at a time determined by its position among the
 input file arguments--after the processing of the preceding input file
 argument.  For example:
 
-     awk '{ print $n }' n=4 inventory-shipped n=2 BBS-list
+     awk '{ print $n }' n=4 inventory-shipped n=2 mail-list
 
 prints the value of field number `n' for all input records.  Before the
 first file is read, the command line sets the variable `n' equal to
 four.  This causes the fourth field to be printed in lines from
 `inventory-shipped'.  After the first file has finished, but before the
 second file is started, `n' is set to two, so that the second field is
-printed in lines from `BBS-list':
+printed in lines from `mail-list':
 
-     $ awk '{ print $n }' n=4 inventory-shipped n=2 BBS-list
+     $ awk '{ print $n }' n=4 inventory-shipped n=2 mail-list
      -| 15
      -| 24
      ...
@@ -7078,6 +7468,22 @@ File: gawk.info,  Node: Conversion,  Prev: Variables,  Up: Values
 6.1.4 Conversion of Strings and Numbers
 ---------------------------------------
 
+Number to string and string to number conversion are generally
+straightforward.  There can be subtleties to be aware of; this minor
+node discusses this important facet of `awk'.
+
+* Menu:
+
+* Strings And Numbers::         How `awk' Converts Between Strings And
+                                Numbers.
+* Locale influences conversions:: How the locale may affect conversions.
+
+
+File: gawk.info,  Node: Strings And Numbers,  Next: Locale influences conversions,  Up: Conversion
+
+6.1.4.1 How `awk' Converts Between Strings And Numbers
+......................................................
+
 Strings are converted to numbers and numbers are converted to strings,
 if the context of the `awk' program demands it.  For example, if the
 value of either `foo' or `bar' in the expression `foo + bar' happens to
@@ -7127,35 +7533,47 @@ value of `CONVFMT' may be.  Given the following code fragment:
 
 `b' has the value `"12"', not `"12.00"'.  (d.c.)
 
+           Pre-POSIX `awk' Used `OFMT' For String Conversion
+
    Prior to the POSIX standard, `awk' used the value of `OFMT' for
 converting numbers to strings.  `OFMT' specifies the output format to
 use when printing numbers with `print'.  `CONVFMT' was introduced in
 order to separate the semantics of conversion from the semantics of
 printing.  Both `CONVFMT' and `OFMT' have the same default value:
 `"%.6g"'.  In the vast majority of cases, old `awk' programs do not
-change their behavior.  However, these semantics for `OFMT' are
-something to keep in mind if you must port your new-style program to
-older implementations of `awk'.  We recommend that instead of changing
-your programs, just port `gawk' itself.  *Note Print::, for more
-information on the `print' statement.
-
-   And, once again, where you are can matter when it comes to converting
-between numbers and strings.  In *note Locales::, we mentioned that the
-local character set and language (the locale) can affect how `gawk'
-matches characters.  The locale also affects numeric formats.  In
-particular, for `awk' programs, it affects the decimal point character.
-The `"C"' locale, and most English-language locales, use the period
-character (`.') as the decimal point.  However, many (if not most)
-European and non-English locales use the comma (`,') as the decimal
-point character.
+change their behavior.  *Note Print::, for more information on the
+`print' statement.
+
+   ---------- Footnotes ----------
+
+   (1) Pathological cases can require up to 752 digits (!), but we
+doubt that you need to worry about this.
+
+
+File: gawk.info,  Node: Locale influences conversions,  Prev: Strings And Numbers,  Up: Conversion
+
+6.1.4.2 Locales Can Influence Conversion
+........................................
+
+Where you are can matter when it comes to converting between numbers and
+strings.  The local character set and language--the "locale"--can
+affect numeric formats.  In particular, for `awk' programs, it affects
+the decimal point character and the thousands-separator character.  The
+`"C"' locale, and most English-language locales, use the period
+character (`.') as the decimal point and don't have a thousands
+separator.  However, many (if not most) European and non-English
+locales use the comma (`,') as the decimal point character. European
+locales often use either a space or a period as the thousands
+separator, if they have one.
 
    The POSIX standard says that `awk' always uses the period as the
 decimal point when reading the `awk' program source code, and for
 command-line variable assignments (*note Other Arguments::).  However,
 when interpreting input data, for `print' and `printf' output, and for
 number to string conversion, the local decimal point character is used.
-(d.c.).  Here are some examples indicating the difference in behavior,
-on a GNU/Linux system:
+(d.c.) In all cases, numbers in source code and in input data cannot
+have a thousands separator.  Here are some examples indicating the
+difference in behavior, on a GNU/Linux system:
 
      $ export POSIXLY_CORRECT=1                        Force POSIX behavior
      $ gawk 'BEGIN { printf "%g\n", 3.1415927 }'
@@ -7200,11 +7618,6 @@ representation can have an unusual but important effect on the way
 `gawk' converts some special string values to numbers.  The details are
 presented in *note POSIX Floating Point Problems::.
 
-   ---------- Footnotes ----------
-
-   (1) Pathological cases can require up to 752 digits (!), but we
-doubt that you need to worry about this.
-
 
 File: gawk.info,  Node: All Operators,  Next: Truth Values and Conditions,  Prev: Values,  Up: Expressions
 
@@ -7320,17 +7733,17 @@ a specific operator to represent it.  Instead, concatenation is
 performed by writing expressions next to one another, with no operator.
 For example:
 
-     $ awk '{ print "Field number one: " $1 }' BBS-list
-     -| Field number one: aardvark
-     -| Field number one: alpo-net
+     $ awk '{ print "Field number one: " $1 }' mail-list
+     -| Field number one: Amelia
+     -| Field number one: Anthony
      ...
 
    Without the space in the string constant after the `:', the line
 runs together.  For example:
 
-     $ awk '{ print "Field number one:" $1 }' BBS-list
-     -| Field number one:aardvark
-     -| Field number one:alpo-net
+     $ awk '{ print "Field number one:" $1 }' mail-list
+     -| Field number one:Amelia
+     -| Field number one:Anthony
      ...
 
    Because string concatenation does not have an explicit operator, it
@@ -7360,9 +7773,9 @@ example:
          print (a " " (a = "panic"))
      }
 
-It is not defined whether the assignment to `a' happens before or after
-the value of `a' is retrieved for producing the concatenated value.
-The result could be either `don't panic', or `panic panic'.
+It is not defined whether the second assignment to `a' happens before
+or after the value of `a' is retrieved for producing the concatenated
+value.  The result could be either `don't panic', or `panic panic'.
 
    The precedence of concatenation, when mixed with other operators, is
 often counter-intuitive.  Consider this example:
@@ -7435,9 +7848,9 @@ that the assignment stores in the specified variable, field, or array
 element. (Such values are called "rvalues".)
 
    It is important to note that variables do _not_ have permanent types.
-A variable's type is simply the type of whatever value it happens to
-hold at the moment.  In the following program fragment, the variable
-`foo' has a numeric value at first, and a string value later on:
+A variable's type is simply the type of whatever value was last assigned
+to it.  In the following program fragment, the variable `foo' has a
+numeric value at first, and a string value later on:
 
      foo = 1
      print foo
@@ -7510,9 +7923,10 @@ The indices of `bar' are practically guaranteed to be different, because
 the `rand()' function haven't been covered yet.  *Note Arrays::, and
 see *note Numeric Functions::, for more information).  This example
 illustrates an important fact about assignment operators: the lefthand
-expression is only evaluated _once_.  It is up to the implementation as
-to which expression is evaluated first, the lefthand or the righthand.
-Consider this example:
+expression is only evaluated _once_.
+
+   It is up to the implementation as to which expression is evaluated
+first, the lefthand or the righthand.  Consider this example:
 
      i = 1
      a[i += 2] = i + 1
@@ -7525,14 +7939,14 @@ converted to a number.
 
 Operator               Effect
 -------------------------------------------------------------------------- 
-LVALUE `+=' INCREMENT  Adds INCREMENT to the value of LVALUE.
-LVALUE `-=' DECREMENT  Subtracts DECREMENT from the value of LVALUE.
-LVALUE `*='            Multiplies the value of LVALUE by COEFFICIENT.
+LVALUE `+=' INCREMENT  Add INCREMENT to the value of LVALUE.
+LVALUE `-=' DECREMENT  Subtract DECREMENT from the value of LVALUE.
+LVALUE `*='            Multiply the value of LVALUE by COEFFICIENT.
 COEFFICIENT            
-LVALUE `/=' DIVISOR    Divides the value of LVALUE by DIVISOR.
-LVALUE `%=' MODULUS    Sets LVALUE to its remainder by MODULUS.
+LVALUE `/=' DIVISOR    Divide the value of LVALUE by DIVISOR.
+LVALUE `%=' MODULUS    Set LVALUE to its remainder by MODULUS.
 LVALUE `^=' POWER      
-LVALUE `**=' POWER     Raises LVALUE to the power POWER. (c.e.)
+LVALUE `**=' POWER     Raise LVALUE to the power POWER. (c.e.)
 
 Table 6.2: Arithmetic Assignment Operators
 
@@ -7555,8 +7969,8 @@ A workaround is:
 
      awk '/[=]=/' /dev/null
 
-   `gawk' does not have this problem, nor do the other freely available
-versions described in *note Other Versions::.
+   `gawk' does not have this problem; Brian Kernighan's `awk' and
+`mawk' also do not (*note Other Versions::).
 
 
 File: gawk.info,  Node: Increment Ops,  Prev: Assignment Ops,  Up: All Operators
@@ -7571,13 +7985,13 @@ they are convenient abbreviations for very common operations.
 
    The operator used for adding one is written `++'.  It can be used to
 increment a variable either before or after taking its value.  To
-pre-increment a variable `v', write `++v'.  This adds one to the value
-of `v'--that new value is also the value of the expression. (The
+"pre-increment" a variable `v', write `++v'.  This adds one to the
+value of `v'--that new value is also the value of the expression. (The
 assignment expression `v += 1' is completely equivalent.)  Writing the
-`++' after the variable specifies post-increment.  This increments the
-variable value just the same; the difference is that the value of the
-increment expression itself is the variable's _old_ value.  Thus, if
-`foo' has the value four, then the expression `foo++' has the value
+`++' after the variable specifies "post-increment".  This increments
+the variable value just the same; the difference is that the value of
+the increment expression itself is the variable's _old_ value.  Thus,
+if `foo' has the value four, then the expression `foo++' has the value
 four, but it changes the value of `foo' to five.  In other words, the
 operator returns the old value of the variable, but with the side
 effect of incrementing it.
@@ -7724,10 +8138,12 @@ The 1992 POSIX standard introduced the concept of a "numeric string",
 which is simply a string that looks like a number--for example,
 `" +2"'.  This concept is used for determining the type of a variable.
 The type of the variable is important because the types of two variables
-determine how they are compared.  The various versions of the POSIX
-standard did not get the rules quite right for several editions.
-Fortunately, as of at least the 2008 standard (and possibly earlier),
-the standard has been fixed, and variable typing follows these rules:(1)
+determine how they are compared.
+
+   The various versions of the POSIX standard did not get the rules
+quite right for several editions.  Fortunately, as of at least the 2008
+standard (and possibly earlier), the standard has been fixed, and
+variable typing follows these rules:(1)
 
    * A numeric constant or the result of a numeric operation has the
      NUMERIC attribute.
@@ -7784,10 +8200,9 @@ comparison is performed.
 characters, and so is first and foremost of STRING type; input strings
 that look numeric are additionally given the STRNUM attribute.  Thus,
 the six-character input string ` +3.14' receives the STRNUM attribute.
-In contrast, the eight-character literal `" +3.14"' appearing in
-program text is a string constant.  The following examples print `1'
-when the comparison between the two different constants is true, `0'
-otherwise:
+In contrast, the eight characters `" +3.14"' appearing in program text
+comprise a string constant.  The following examples print `1' when the
+comparison between the two different constants is true, `0' otherwise:
 
      $ echo ' +3.14' | gawk '{ print $0 == " +3.14" }'    True
      -| 1
@@ -7881,7 +8296,6 @@ of error is very difficult to spot when scanning the source code.
      string comparison (true)
 
 `a = 2; b = " +2"'
-
 `a == b'
      string comparison (false)
 
@@ -7910,7 +8324,7 @@ has the value one if `x' contains `foo', such as `"Oh, what a fool am
 I!"'.
 
    The righthand operand of the `~' and `!~' operators may be either a
-regexp constant (`/.../') or an ordinary expression. In the latter
+regexp constant (`/'...`/') or an ordinary expression. In the latter
 case, the value of the expression as a string is used as a dynamic
 regexp (*note Regexp Usage::; also *note Computed Regexps::).
 
@@ -7931,9 +8345,10 @@ File: gawk.info,  Node: POSIX String Comparison,  Prev: Comparison Operators,  U
 ..........................................
 
 The POSIX standard says that string comparison is performed based on
-the locale's collating order.  This is usually very different from the
-results obtained when doing straight character-by-character
-comparison.(1)
+the locale's "collating order". This is the order in which characters
+sort, as defined by the locale (for more discussion, *note Ranges and
+Locales::).  This order is usually very different from the results
+obtained when doing straight character-by-character comparison.(1)
 
    Because this behavior differs considerably from existing practice,
 `gawk' only implements it when in POSIX mode (*note Options::).  Here
@@ -7977,9 +8392,9 @@ Boolean operators are:
 `BOOLEAN1 && BOOLEAN2'
      True if both BOOLEAN1 and BOOLEAN2 are true.  For example, the
      following statement prints the current input record if it contains
-     both `2400' and `foo':
+     both `edu' and `li':
 
-          if ($0 ~ /2400/ && $0 ~ /foo/) print
+          if ($0 ~ /edu/ && $0 ~ /li/) print
 
      The subexpression BOOLEAN2 is evaluated only if BOOLEAN1 is true.
      This can make a difference when BOOLEAN2 contains expressions that
@@ -7990,9 +8405,9 @@ Boolean operators are:
 `BOOLEAN1 || BOOLEAN2'
      True if at least one of BOOLEAN1 or BOOLEAN2 is true.  For
      example, the following statement prints all records in the input
-     that contain _either_ `2400' or `foo' or both:
+     that contain _either_ `edu' or `li' or both:
 
-          if ($0 ~ /2400/ || $0 ~ /foo/) print
+          if ($0 ~ /edu/ || $0 ~ /li/) print
 
      The subexpression BOOLEAN2 is evaluated only if BOOLEAN1 is false.
      This can make a difference when BOOLEAN2 contains expressions that
@@ -8085,7 +8500,7 @@ not.  *Note Arrays::, for more information about arrays.
 continued simply by putting a newline after either character.  However,
 putting a newline in front of either character does not work without
 using backslash continuation (*note Statements/Lines::).  If `--posix'
-is specified (*note Options::), then this extension is disabled.
+is specified (*note Options::), this extension is disabled.
 
 
 File: gawk.info,  Node: Function Calls,  Next: Precedence,  Prev: Truth Values and Conditions,  Up: Expressions
@@ -8102,6 +8517,8 @@ available in every `awk' program.  The `sqrt()' function is one of
 these.  *Note Built-in::, for a list of built-in functions and their
 descriptions.  In addition, you can define functions for use in your
 program.  *Note User-defined::, for instructions on how to do this.
+Finally, `gawk' lets you write functions in C or C++ that may be called
+from your program: see *note Dynamic Extensions::.
 
    The way to use a function is with a "function call" expression,
 which consists of the function name followed immediately by a list of
@@ -8133,19 +8550,21 @@ the number of which to take the square root:
 If those arguments are not supplied, the functions use a reasonable
 default value.  *Note Built-in::, for full details.  If arguments are
 omitted in calls to user-defined functions, then those arguments are
-treated as local variables and initialized to the empty string (*note
-User-defined::).
+treated as local variables. Such local variables act like the empty
+string if referenced where a string value is required, and like zero if
+referenced where a numeric value is required (*note User-defined::).
 
    As an advanced feature, `gawk' provides indirect function calls,
 which is a way to choose the function to call at runtime, instead of
 when you write the source code to your program. We defer discussion of
 this feature until later; see *note Indirect Calls::.
 
-   Like every other expression, the function call has a value, which is
-computed by the function based on the arguments you give it.  In this
-example, the value of `sqrt(ARGUMENT)' is the square root of ARGUMENT.
-The following program reads numbers, one number per line, and prints the
-square root of each one:
+   Like every other expression, the function call has a value, often
+called the "return value", which is computed by the function based on
+the arguments you give it.  In this example, the return value of
+`sqrt(ARGUMENT)' is the square root of ARGUMENT.  The following program
+reads numbers, one number per line, and prints the square root of each
+one:
 
      $ awk '{ print "The square root of", $1, "is", sqrt($1) }'
      1
@@ -8218,7 +8637,7 @@ to avoid the problem the expression can be rewritten as `$($0++)--'.
    This table presents `awk''s operators, in order of highest to lowest
 precedence:
 
-`(...)'
+`('...`)'
      Grouping.
 
 `$'
@@ -8239,7 +8658,7 @@ precedence:
 `+ -'
      Addition, subtraction.
 
-`String Concatenation'
+String Concatenation
      There is no special symbol for concatenation.  The operands are
      simply written side by side (*note Concatenation::).
 
@@ -8280,13 +8699,15 @@ precedence:
      POSIX.  For maximum portability, do not use them.
 
 
-File: gawk.info,  Node: Locales,  Prev: Precedence,  Up: Expressions
+File: gawk.info,  Node: Locales,  Next: Expressions Summary,  Prev: Precedence,  Up: Expressions
 
 6.6 Where You Are Makes A Difference
 ====================================
 
 Modern systems support the notion of "locales": a way to tell the
-system about the local character set and language.
+system about the local character set and language.  The ISO C standard
+defines a default `"C"' locale, which is an environment that is typical
+of what many C programmers are used to.
 
    Once upon a time, the locale setting used to affect regexp matching
 (*note Ranges and Locales::), but this is no longer true.
@@ -8298,6 +8719,13 @@ much better performance when reading records.  Otherwise, `gawk' has to
 make several function calls, _per input character_, to find the record
 terminator.
 
+   Locales can affect how dates and times are formatted (*note Time
+Functions::).  For example, a common way to abbreviate the date
+September 4, 2015 in the United States is "9/4/15."  In many countries
+in Europe, however, it is abbreviated "4.9.15."  Thus, the `%x'
+specification in a `"US"' locale might produce `9/4/15', while in a
+`"EUROPE"' locale, it might produce `4.9.15'.
+
    According to POSIX, string comparison is also affected by locales
 (similar to regular expressions).  The details are presented in *note
 POSIX String Comparison::.
@@ -8307,6 +8735,63 @@ used when `gawk' parses input data.  This is discussed in detail in
 *note Conversion::.
 
 
+File: gawk.info,  Node: Expressions Summary,  Prev: Locales,  Up: Expressions
+
+6.7 Summary
+===========
+
+   * Expressions are the basic elements of computation in programs.
+     They are built from constants, variables, function calls and
+     combinations of the various kinds of values with operators.
+
+   * `awk' supplies three kinds of constants: numeric, string, and
+     regexp.  `gawk' lets you specify numeric constants in octal and
+     hexadecimal (bases 8 and 16) in addition to decimal (base 10).  In
+     certain contexts, a standalone regexp constant such as `/foo/' has
+     the same meaning as `$0 ~ /foo/'.
+
+   * Variables hold values between uses in computations. A number of
+     built-in variables provide information to your `awk' program, and
+     a number of others let you control how `awk' behaves.
+
+   * Numbers are automatically converted to strings, and strings to
+     numbers, as needed by `awk'. Numeric values are converted as if
+     they were formatted with `sprintf()' using the format in `CONVFMT'.
+     Locales can influence the conversions.
+
+   * `awk' provides the usual arithmetic operators (addition,
+     subtraction, multiplication, division, modulus), and unary plus
+     and minus.  It also provides comparison operators, boolean
+     operators, and regexp matching operators.  String concatenation is
+     accomplished by placing two expressions next to each other; there
+     is no explicit operator.  The three-operand `?:' operator provides
+     an "if-else" test within expressions.
+
+   * Assignment operators provide convenient shorthands for common
+     arithmetic operations.
+
+   * In `awk', a value is considered to be true if it is non-zero _or_
+     non-null. Otherwise, the value is false.
+
+   * A value's type is set upon each assignment and may change over its
+     lifetime.  The type determines how it behaves in comparisons
+     (string or numeric).
+
+   * Function calls return a value which may be used as part of a larger
+     expression.  Expressions used to pass parameter values are fully
+     evaluated before the function is called.  `awk' provides built-in
+     and user-defined functions; this is described later on in this
+     Info file.
+
+   * Operator precedence specifies the order in which operations are
+     performed, unless explicitly overridden by parentheses.  `awk''s
+     operator precedence is compatible with that of C.
+
+   * Locales can affect the format of data as output by an `awk'
+     program, and occasionally the format for data read as input.
+
+
+
 File: gawk.info,  Node: Patterns and Actions,  Next: Arrays,  Prev: Expressions,  Up: Top
 
 7 Patterns, Actions, and Variables
@@ -8330,6 +8815,7 @@ top of.  Now it's time to start building something useful.
 * Statements::                  Describes the various control statements in
                                 detail.
 * Built-in Variables::          Summarizes the built-in variables.
+* Pattern Action Summary::      Patterns and Actions summary.
 
 
 File: gawk.info,  Node: Pattern Overview,  Next: Using Shell Variables,  Up: Patterns and Actions
@@ -8358,10 +8844,10 @@ summary of the types of `awk' patterns:
      A single expression.  It matches when its value is nonzero (if a
      number) or non-null (if a string).  (*Note Expression Patterns::.)
 
-`PAT1, PAT2'
+`BEGPAT, ENDPAT'
      A pair of patterns separated by a comma, specifying a range of
      records.  The range includes both the initial record that matches
-     PAT1 and the final record that matches PAT2.  (*Note Ranges::.)
+     BEGPAT and the final record that matches ENDPAT.  (*Note Ranges::.)
 
 `BEGIN'
 `END'
@@ -8371,7 +8857,7 @@ summary of the types of `awk' patterns:
 `BEGINFILE'
 `ENDFILE'
      Special patterns for you to supply startup or cleanup actions to be
-     done on a per file basis.  (*Note BEGINFILE/ENDFILE::.)
+     done on a per-file basis.  (*Note BEGINFILE/ENDFILE::.)
 
 `EMPTY'
      The empty pattern matches every input record.  (*Note Empty::.)
@@ -8412,56 +8898,53 @@ operand is either a constant regular expression enclosed in slashes
 (`/REGEXP/'), or any expression whose string value is used as a dynamic
 regular expression (*note Computed Regexps::).  The following example
 prints the second field of each input record whose first field is
-precisely `foo':
+precisely `li':
 
-     $ awk '$1 == "foo" { print $2 }' BBS-list
+     $ awk '$1 == "li" { print $2 }' mail-list
 
-(There is no output, because there is no BBS site with the exact name
-`foo'.)  Contrast this with the following regular expression match,
-which accepts any record with a first field that contains `foo':
+(There is no output, because there is no person with the exact name
+`li'.)  Contrast this with the following regular expression match, which
+accepts any record with a first field that contains `li':
 
-     $ awk '$1 ~ /foo/ { print $2 }' BBS-list
-     -| 555-1234
+     $ awk '$1 ~ /foo/ { print $2 }' mail-list
+     -| 555-5553
      -| 555-6699
-     -| 555-6480
-     -| 555-2127
 
    A regexp constant as a pattern is also a special case of an
-expression pattern.  The expression `/foo/' has the value one if `foo'
-appears in the current input record. Thus, as a pattern, `/foo/'
-matches any record containing `foo'.
+expression pattern.  The expression `/li/' has the value one if `li'
+appears in the current input record. Thus, as a pattern, `/li/' matches
+any record containing `li'.
 
    Boolean expressions are also commonly used as patterns.  Whether the
 pattern matches an input record depends on whether its subexpressions
 match.  For example, the following command prints all the records in
-`BBS-list' that contain both `2400' and `foo':
-
-     $ awk '/2400/ && /foo/' BBS-list
-     -| fooey        555-1234     2400/1200/300     B
-
-   The following command prints all records in `BBS-list' that contain
-_either_ `2400' or `foo' (or both, of course):
-
-     $ awk '/2400/ || /foo/' BBS-list
-     -| alpo-net     555-3412     2400/1200/300     A
-     -| bites        555-1675     2400/1200/300     A
-     -| fooey        555-1234     2400/1200/300     B
-     -| foot         555-6699     1200/300          B
-     -| macfoo       555-6480     1200/300          A
-     -| sdace        555-3430     2400/1200/300     A
-     -| sabafoo      555-2127     1200/300          C
-
-   The following command prints all records in `BBS-list' that do _not_
-contain the string `foo':
-
-     $ awk '! /foo/' BBS-list
-     -| aardvark     555-5553     1200/300          B
-     -| alpo-net     555-3412     2400/1200/300     A
-     -| barfly       555-7685     1200/300          A
-     -| bites        555-1675     2400/1200/300     A
-     -| camelot      555-0542     300               C
-     -| core         555-2912     1200/300          C
-     -| sdace        555-3430     2400/1200/300     A
+`mail-list' that contain both `edu' and `li':
+
+     $ awk '/edu/ && /li/' mail-list
+     -| Samuel       555-3430     samuel.lanceolis@shu.edu        A
+
+   The following command prints all records in `mail-list' that contain
+_either_ `edu' or `li' (or both, of course):
+
+     $ awk '/edu/ || /li/' mail-list
+     -| Amelia       555-5553     amelia.zodiacusque@gmail.com    F
+     -| Broderick    555-0542     broderick.aliquotiens@yahoo.com R
+     -| Fabius       555-1234     fabius.undevicesimus@ucb.edu    F
+     -| Julie        555-6699     julie.perscrutabor@skeeve.com   F
+     -| Samuel       555-3430     samuel.lanceolis@shu.edu        A
+     -| Jean-Paul    555-2127     jeanpaul.campanorum@nyu.edu     R
+
+   The following command prints all records in `mail-list' that do
+_not_ contain the string `li':
+
+     $ awk '! /li/' mail-list
+     -| Anthony      555-3412     anthony.asserturo@hotmail.com   A
+     -| Becky        555-7685     becky.algebrarum@gmail.com      A
+     -| Bill         555-1675     bill.drowning@hotmail.com       A
+     -| Camilla      555-2912     camilla.infusarum@skynet.be     R
+     -| Fabius       555-1234     fabius.undevicesimus@ucb.edu    F
+     -| Martin       555-6480     martin.codicibus@hotmail.com    A
+     -| Jean-Paul    555-2127     jeanpaul.campanorum@nyu.edu     R
 
    The subexpressions of a Boolean operator in a pattern can be
 constant regular expressions, comparisons, or any other `awk'
@@ -8494,7 +8977,7 @@ record.  When a record matches BEGPAT, the range pattern is "turned on"
 and the range pattern matches this record as well.  As long as the
 range pattern stays turned on, it automatically matches every input
 record read.  The range pattern also matches ENDPAT against every input
-record; when this succeeds, the range pattern is turned off again for
+record; when this succeeds, the range pattern is "turned off" again for
 the following record.  Then the range pattern goes back to checking
 BEGPAT against each record.
 
@@ -8538,6 +9021,10 @@ worked around; range patterns do not combine with other patterns:
      error--> gawk: cmd. line:1: (/1/,/2/) || /Yes/
      error--> gawk: cmd. line:1:           ^ syntax error
 
+   As a minor point of interest, although it is poor style, POSIX
+allows you to put a newline after the comma in a range pattern.
+(d.c.)
+
 
 File: gawk.info,  Node: BEGIN/END,  Next: BEGINFILE/ENDFILE,  Prev: Ranges,  Up: Pattern Overview
 
@@ -8568,19 +9055,19 @@ read. Likewise, an `END' rule is executed once only, after all the
 input is read.  For example:
 
      $ awk '
-     > BEGIN { print "Analysis of \"foo\"" }
-     > /foo/ { ++n }
-     > END   { print "\"foo\" appears", n, "times." }' BBS-list
-     -| Analysis of "foo"
-     -| "foo" appears 4 times.
-
-   This program finds the number of records in the input file `BBS-list'
-that contain the string `foo'.  The `BEGIN' rule prints a title for the
-report.  There is no need to use the `BEGIN' rule to initialize the
-counter `n' to zero, since `awk' does this automatically (*note
-Variables::).  The second rule increments the variable `n' every time a
-record containing the pattern `foo' is read.  The `END' rule prints the
-value of `n' at the end of the run.
+     > BEGIN { print "Analysis of \"li\"" }
+     > /li/ { ++n }
+     > END   { print "\"li\" appears in", n, "records." }' mail-list
+     -| Analysis of "li"
+     -| "li" appears in 4 records.
+
+   This program finds the number of records in the input file
+`mail-list' that contain the string `li'.  The `BEGIN' rule prints a
+title for the report.  There is no need to use the `BEGIN' rule to
+initialize the counter `n' to zero, since `awk' does this automatically
+(*note Variables::).  The second rule increments the variable `n' every
+time a record containing the pattern `li' is read.  The `END' rule
+prints the value of `n' at the end of the run.
 
    The special patterns `BEGIN' and `END' cannot be used in ranges or
 with Boolean operators (indeed, they cannot be used with any operators).
@@ -8622,10 +9109,10 @@ File: gawk.info,  Node: I/O And BEGIN/END,  Prev: Using BEGIN/END,  Up: BEGIN/EN
 7.1.4.2 Input/Output from `BEGIN' and `END' Rules
 .................................................
 
-There are several (sometimes subtle) points to remember when doing I/O
-from a `BEGIN' or `END' rule.  The first has to do with the value of
-`$0' in a `BEGIN' rule.  Because `BEGIN' rules are executed before any
-input is read, there simply is no input record, and therefore no
+There are several (sometimes subtle) points to be aware of when doing
+I/O from a `BEGIN' or `END' rule.  The first has to do with the value
+of `$0' in a `BEGIN' rule.  Because `BEGIN' rules are executed before
+any input is read, there simply is no input record, and therefore no
 fields, when executing `BEGIN' rules.  References to `$0' and the fields
 yield a null string or zero, depending upon the context.  One way to
 give `$0' a real value is to execute a `getline' command without a
@@ -8693,10 +9180,10 @@ tasks that would otherwise be difficult or impossible to perform:
      entirely.  Otherwise, `gawk' exits with the usual fatal error.
 
    * If you have written extensions that modify the record handling (by
-     inserting an "input parser"), you can invoke them at this point,
-     before `gawk' has started processing the file.  (This is a _very_
-     advanced feature, currently used only by the `gawkextlib' project
-     (http://gawkextlib.sourceforge.net).)
+     inserting an "input parser," *note Input Parsers::), you can invoke
+     them at this point, before `gawk' has started processing the file.
+     (This is a _very_ advanced feature, currently used only by the
+     `gawkextlib' project (http://gawkextlib.sourceforge.net).)
 
    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
@@ -8715,7 +9202,7 @@ either a `BEGINFILE' or and `ENDFILE' rule.  The `nextfile' statement
 but not inside an `ENDFILE' rule.
 
    The `getline' statement (*note Getline::) is restricted inside both
-`BEGINFILE' and `ENDFILE'.  Only the `getline VARIABLE < FILE' form is
+`BEGINFILE' and `ENDFILE': only redirected forms of `getline' are
 allowed.
 
    `BEGINFILE' and `ENDFILE' are `gawk' extensions.  In most other
@@ -8731,7 +9218,7 @@ File: gawk.info,  Node: Empty,  Prev: BEGINFILE/ENDFILE,  Up: Pattern Overview
 An empty (i.e., nonexistent) pattern is considered to match _every_
 input record.  For example, the program:
 
-     awk '{ print $1 }' BBS-list
+     awk '{ print $1 }' mail-list
 
 prints the first field of every record.
 
@@ -8748,15 +9235,15 @@ to get the value of the shell variable into the body of the `awk'
 program.
 
    The most common method is to use shell quoting to substitute the
-variable's value into the program inside the script.  For example, in
-the following program:
+variable's value into the program inside the script.  For example,
+consider the following program:
 
      printf "Enter search pattern: "
      read pattern
      awk "/$pattern/ "'{ nmatches++ }
           END { print nmatches, "found" }' /path/to/data
 
-the `awk' program consists of two pieces of quoted text that are
+The `awk' program consists of two pieces of quoted text that are
 concatenated together to form the program.  The first part is
 double-quoted, which allows substitution of the `pattern' shell
 variable inside the quotes.  The second part is single-quoted.
@@ -8768,7 +9255,7 @@ quotes when reading the program.
 
    A better method is to use `awk''s variable assignment feature (*note
 Assignment Options::) to assign the shell variable's value to an `awk'
-variable's value.  Then use dynamic regexps to match the pattern (*note
+variable.  Then use dynamic regexps to match the pattern (*note
 Computed Regexps::).  The following shows how to redo the previous
 example using this technique:
 
@@ -8799,19 +9286,19 @@ which (but not both) may be omitted.  The purpose of the "action" is to
 tell `awk' what to do once a match for the pattern is found.  Thus, in
 outline, an `awk' program generally looks like this:
 
-     [PATTERN]  { ACTION }
-      PATTERN  [{ ACTION }]
+     [PATTERN]  `{ ACTION }'
+      PATTERN  [`{ ACTION }']
      ...
-     function NAME(ARGS) { ... }
+     `function NAME(ARGS) { ... }'
      ...
 
    An action consists of one or more `awk' "statements", enclosed in
-curly braces (`{...}').  Each statement specifies one thing to do.  The
-statements are separated by newlines or semicolons.  The curly braces
-around an action must be used even if the action contains only one
-statement, or if it contains no statements at all.  However, if you
-omit the action entirely, omit the curly braces as well.  An omitted
-action is equivalent to `{ print $0 }':
+braces (`{...}').  Each statement specifies one thing to do.  The
+statements are separated by newlines or semicolons.  The braces around
+an action must be used even if the action contains only one statement,
+or if it contains no statements at all.  However, if you omit the
+action entirely, omit the braces as well.  An omitted action is
+equivalent to `{ print $0 }':
 
      /foo/  { }     match `foo', do nothing -- empty action
      /foo/          match `foo', print the record -- omitted action
@@ -8830,9 +9317,9 @@ Control statements
      well as a few special ones (*note Statements::).
 
 Compound statements
-     Consist of one or more statements enclosed in curly braces.  A
-     compound statement is used in order to put several statements
-     together in the body of an `if', `while', `do', or `for' statement.
+     Enclose one or more statements in braces.  A compound statement is
+     used in order to put several statements together in the body of an
+     `if', `while', `do', or `for' statement.
 
 Input statements
      Use the `getline' command (*note Getline::).  Also supplied in
@@ -8861,7 +9348,7 @@ statements contain other statements.  For example, the `if' statement
 contains another statement that may or may not be executed.  The
 contained statement is called the "body".  To include more than one
 statement in the body, group them into a single "compound statement"
-with curly braces, separating them with newlines or semicolons.
+with braces, separating them with newlines or semicolons.
 
 * Menu:
 
@@ -8890,7 +9377,7 @@ File: gawk.info,  Node: If Statement,  Next: While Statement,  Up: Statements
 The `if'-`else' statement is `awk''s decision-making statement.  It
 looks like this:
 
-     if (CONDITION) THEN-BODY [else ELSE-BODY]
+     `if (CONDITION) THEN-BODY' [`else ELSE-BODY']
 
 The CONDITION is an expression that controls what the rest of the
 statement does.  If the CONDITION is true, THEN-BODY is executed;
@@ -8909,8 +9396,8 @@ the value of `x' is evenly divisible by two), then the first `print'
 statement is executed; otherwise, the second `print' statement is
 executed.  If the `else' keyword appears on the same line as THEN-BODY
 and THEN-BODY is not a compound statement (i.e., not surrounded by
-curly braces), then a semicolon must separate THEN-BODY from the `else'.
-To illustrate this, the previous example can be rewritten as:
+braces), then a semicolon must separate THEN-BODY from the `else'.  To
+illustrate this, the previous example can be rewritten as:
 
      if (x % 2 == 0) print "x is even"; else
              print "x is odd"
@@ -9095,9 +9582,12 @@ File: gawk.info,  Node: Switch Statement,  Next: Break Statement,  Prev: For Sta
 7.4.5 The `switch' Statement
 ----------------------------
 
-The `switch' statement allows the evaluation of an expression and the
-execution of statements based on a `case' match. Case statements are
-checked for a match in the order they are defined.  If no suitable
+This minor node describes a `gawk'-specific feature.  If `gawk' is in
+compatibility mode (*note Options::), it is not available.
+
+   The `switch' statement allows the evaluation of an expression and
+the execution of statements based on a `case' match. Case statements
+are checked for a match in the order they are defined.  If no suitable
 `case' is found, the `default' section is executed, if supplied.
 
    Each `case' contains a single constant, be it numeric, string, or
@@ -9144,9 +9634,6 @@ is executed and then falls through into the `default' section,
 executing its `print' statement. In turn, the -1 case will also be
 executed since the `default' does not halt execution.
 
-   This `switch' statement is a `gawk' extension.  If `gawk' is in
-compatibility mode (*note Options::), it is not available.
-
 
 File: gawk.info,  Node: Break Statement,  Next: Continue Statement,  Prev: Switch Statement,  Up: Statements
 
@@ -9159,15 +9646,15 @@ divisor of any integer, and also identifies prime numbers:
 
      # find smallest divisor of num
      {
-        num = $1
-        for (div = 2; div * div <= num; div++) {
-          if (num % div == 0)
-            break
-        }
-        if (num % div == 0)
-          printf "Smallest divisor of %d is %d\n", num, div
-        else
-          printf "%d is prime\n", num
+         num = $1
+         for (div = 2; div * div <= num; div++) {
+             if (num % div == 0)
+                 break
+         }
+         if (num % div == 0)
+             printf "Smallest divisor of %d is %d\n", num, div
+         else
+             printf "%d is prime\n", num
      }
 
    When the remainder is zero in the first `if' statement, `awk'
@@ -9182,17 +9669,17 @@ Statement::.)
 
      # find smallest divisor of num
      {
-       num = $1
-       for (div = 2; ; div++) {
-         if (num % div == 0) {
-           printf "Smallest divisor of %d is %d\n", num, div
-           break
-         }
-         if (div * div > num) {
-           printf "%d is prime\n", num
-           break
+         num = $1
+         for (div = 2; ; div++) {
+             if (num % div == 0) {
+                 printf "Smallest divisor of %d is %d\n", num, div
+                 break
+             }
+             if (div * div > num) {
+                 printf "%d is prime\n", num
+                 break
+             }
          }
-       }
      }
 
    The `break' statement is also used to break out of the `switch'
@@ -9303,7 +9790,7 @@ rules. *Note BEGINFILE/ENDFILE::.
 
    According to the POSIX standard, the behavior is undefined if the
 `next' statement is used in a `BEGIN' or `END' rule.  `gawk' treats it
-as a syntax error.  Although POSIX permits it, some other `awk'
+as a syntax error.  Although POSIX permits it, most other `awk'
 implementations don't allow the `next' statement inside function bodies
 (*note User-defined::).  Just as with any other `next' statement, a
 `next' statement inside a function body reads the next record and
@@ -9356,12 +9843,12 @@ listed in `ARGV'.
      standard.  See the Austin Group website
      (http://austingroupbugs.net/view.php?id=607).
 
-   The current version of the Brian Kernighan's `awk' (*note Other
-Versions::) also supports `nextfile'.  However, it doesn't allow the
-`nextfile' statement inside function bodies (*note User-defined::).
-`gawk' does; a `nextfile' inside a function body reads the next record
-and starts processing it with the first rule in the program, just as
-any other `nextfile' statement.
+   The current version of the Brian Kernighan's `awk', and `mawk'
+(*note Other Versions::) also support `nextfile'.  However, they don't
+allow the `nextfile' statement inside function bodies (*note
+User-defined::).  `gawk' does; a `nextfile' inside a function body
+reads the next record and starts processing it with the first rule in
+the program, just as any other `nextfile' statement.
 
 
 File: gawk.info,  Node: Exit Statement,  Prev: Nextfile Statement,  Up: Statements
@@ -9373,7 +9860,7 @@ The `exit' statement causes `awk' to immediately stop executing the
 current rule and to stop processing input; any remaining input is
 ignored.  The `exit' statement is written as follows:
 
-     exit [RETURN CODE]
+     `exit' [RETURN CODE]
 
    When an `exit' statement is executed from a `BEGIN' rule, the
 program stops processing everything immediately.  No input records are
@@ -9407,12 +9894,12 @@ with a nonzero status.  An `awk' program can do this using an `exit'
 statement with a nonzero argument, as shown in the following example:
 
      BEGIN {
-            if (("date" | getline date_now) <= 0) {
-              print "Can't get system date" > "/dev/stderr"
-              exit 1
-            }
-            print "current date is", date_now
-            close("date")
+         if (("date" | getline date_now) <= 0) {
+             print "Can't get system date" > "/dev/stderr"
+             exit 1
+         }
+         print "current date is", date_now
+         close("date")
      }
 
      NOTE: For full portability, exit values should be between zero and
@@ -9421,7 +9908,7 @@ statement with a nonzero argument, as shown in the following example:
      systems.
 
 
-File: gawk.info,  Node: Built-in Variables,  Prev: Statements,  Up: Patterns and Actions
+File: gawk.info,  Node: Built-in Variables,  Next: Pattern Action Summary,  Prev: Statements,  Up: Patterns and Actions
 
 7.5 Built-in Variables
 ======================
@@ -9434,9 +9921,9 @@ of these automatically, so that they enable you to tell `awk' how to do
 certain things.  Others are set automatically by `awk', so that they
 carry information from the internal workings of `awk' to your program.
 
-   This minor node documents all the built-in variables of `gawk', most
-of which are also documented in the chapters describing their areas of
-activity.
+   This minor node documents all of `gawk''s built-in variables, most
+of which are also documented in the major nodes describing their areas
+of activity.
 
 * Menu:
 
@@ -9453,8 +9940,13 @@ File: gawk.info,  Node: User-modified,  Next: Auto-set,  Up: Built-in Variables
 -------------------------------------------
 
 The following is an alphabetical list of variables that you can change
-to control how `awk' does certain things. The variables that are
-specific to `gawk' are marked with a pound sign (`#').
+to control how `awk' does certain things.
+
+   The variables that are specific to `gawk' are marked with a pound
+sign (`#').  These variables are `gawk' extensions.  In other `awk'
+implementations or if `gawk' is in compatibility mode (*note
+Options::), they are not special.  (Any exceptions are noted in the
+description of each variable.)
 
 `BINMODE #'
      On non-POSIX systems, this variable specifies use of binary mode
@@ -9467,14 +9959,11 @@ specific to `gawk' are marked with a pound sign (`#').
      string value of `"rw"' or `"wr"' indicates that all files should
      use binary I/O.  Any other string value is treated the same as
      `"rw"', but causes `gawk' to generate a warning message.
-     `BINMODE' is described in more detail in *note PC Using::.
+     `BINMODE' is described in more detail in *note PC Using::.  `mawk'
+     *note Other Versions::), also supports this variable, but only
+     using numeric values.
 
-     This variable is a `gawk' extension.  In other `awk'
-     implementations (except `mawk', *note Other Versions::), or if
-     `gawk' is in compatibility mode (*note Options::), it is not
-     special.
-
-`CONVFMT'
+``CONVFMT''
      This string controls conversion of numbers to strings (*note
      Conversion::).  It works by being passed, in effect, as the first
      argument to the `sprintf()' function (*note String Functions::).
@@ -9482,29 +9971,21 @@ specific to `gawk' are marked with a pound sign (`#').
      POSIX standard.
 
 `FIELDWIDTHS #'
-     This is a space-separated list of columns that tells `gawk' how to
-     split input with fixed columnar boundaries.  Assigning a value to
+     A space-separated list of columns that tells `gawk' how to split
+     input with fixed columnar boundaries.  Assigning a value to
      `FIELDWIDTHS' overrides the use of `FS' and `FPAT' for field
      splitting.  *Note Constant Size::, for more information.
 
-     If `gawk' is in compatibility mode (*note Options::), then
-     `FIELDWIDTHS' has no special meaning, and field-splitting
-     operations occur based exclusively on the value of `FS'.
-
 `FPAT #'
-     This is a regular expression (as a string) that tells `gawk' to
-     create the fields based on text that matches the regular
-     expression.  Assigning a value to `FPAT' overrides the use of `FS'
-     and `FIELDWIDTHS' for field splitting.  *Note Splitting By
-     Content::, for more information.
-
-     If `gawk' is in compatibility mode (*note Options::), then `FPAT'
-     has no special meaning, and field-splitting operations occur based
-     exclusively on the value of `FS'.
+     A regular expression (as a string) that tells `gawk' to create the
+     fields based on text that matches the regular expression.
+     Assigning a value to `FPAT' overrides the use of `FS' and
+     `FIELDWIDTHS' for field splitting.  *Note Splitting By Content::,
+     for more information.
 
 `FS'
-     This is the input field separator (*note Field Separators::).  The
-     value is a single-character string or a multicharacter regular
+     The input field separator (*note Field Separators::).  The value
+     is a single-character string or a multicharacter regular
      expression that matches the separations between fields in an input
      record.  If the value is the null string (`""'), then each
      character in the record becomes a separate field.  (This behavior
@@ -9540,13 +10021,9 @@ specific to `gawk' are marked with a pound sign (`#').
      splitting when using a single-character field separator.  *Note
      Case-sensitivity::.
 
-     If `gawk' is in compatibility mode (*note Options::), then
-     `IGNORECASE' has no special meaning.  Thus, string and regexp
-     operations are always case-sensitive.
-
 `LINT #'
      When this variable is true (nonzero or non-null), `gawk' behaves
-     as if the `--lint' command-line option is in effect.  (*note
+     as if the `--lint' command-line option is in effect (*note
      Options::).  With a value of `"fatal"', lint warnings become fatal
      errors.  With a value of `"invalid"', only warnings about things
      that are actually invalid are issued. (This is not fully
@@ -9562,13 +10039,13 @@ specific to `gawk' are marked with a pound sign (`#').
      execution is independent of the flavor of `awk' being executed.
 
 `OFMT'
-     This string controls conversion of numbers to strings (*note
-     Conversion::) for printing with the `print' statement.  It works
-     by being passed as the first argument to the `sprintf()' function
-     (*note String Functions::).  Its default value is `"%.6g"'.
-     Earlier versions of `awk' also used `OFMT' to specify the format
-     for converting numbers to strings in general expressions; this is
-     now done by `CONVFMT'.
+     Controls conversion of numbers to strings (*note Conversion::) for
+     printing with the `print' statement.  It works by being passed as
+     the first argument to the `sprintf()' function (*note String
+     Functions::).  Its default value is `"%.6g"'.  Earlier versions of
+     `awk' also used `OFMT' to specify the format for converting
+     numbers to strings in general expressions; this is now done by
+     `CONVFMT'.
 
 `OFS'
      This is the output field separator (*note Output Separators::).
@@ -9576,49 +10053,45 @@ specific to `gawk' are marked with a pound sign (`#').
      Its default value is `" "', a string consisting of a single space.
 
 `ORS'
-     This is the output record separator.  It is output at the end of
-     every `print' statement.  Its default value is `"\n"', the newline
+     The output record separator.  It is output at the end of every
+     `print' statement.  Its default value is `"\n"', the newline
      character.  (*Note Output Separators::.)
 
 `PREC #'
      The working precision of arbitrary precision floating-point
-     numbers, 53 bits by default (*note Setting Precision::).
+     numbers, 53 bits by default (*note Setting precision::).
 
 `ROUNDMODE #'
      The rounding mode to use for arbitrary precision arithmetic on
-     numbers, by default `"N"' (`roundTiesToEven' in the IEEE-754
-     standard) (*note Setting Rounding Mode::).
+     numbers, by default `"N"' (`roundTiesToEven' in the IEEE 754
+     standard; *note Setting the rounding mode::).
 
-`RS'
-     This is `awk''s input record separator.  Its default value is a
-     string containing a single newline character, which means that an
-     input record consists of a single line of text.  It can also be
-     the null string, in which case records are separated by runs of
-     blank lines.  If it is a regexp, records are separated by matches
-     of the regexp in the input text.  (*Note Records::.)
+``RS''
+     The input record separator.  Its default value is a string
+     containing a single newline character, which means that an input
+     record consists of a single line of text.  It can also be the null
+     string, in which case records are separated by runs of blank lines.
+     If it is a regexp, records are separated by matches of the regexp
+     in the input text.  (*Note Records::.)
 
      The ability for `RS' to be a regular expression is a `gawk'
      extension.  In most other `awk' implementations, or if `gawk' is
      in compatibility mode (*note Options::), just the first character
      of `RS''s value is used.
 
-`SUBSEP'
-     This is the subscript separator.  It has the default value of
-     `"\034"' and is used to separate the parts of the indices of a
-     multidimensional array.  Thus, the expression `foo["A", "B"]'
-     really accesses `foo["A\034B"]' (*note Multidimensional::).
+``SUBSEP''
+     The subscript separator.  It has the default value of `"\034"' and
+     is used to separate the parts of the indices of a multidimensional
+     array.  Thus, the expression `foo["A", "B"]' really accesses
+     `foo["A\034B"]' (*note Multidimensional::).
 
 `TEXTDOMAIN #'
-     This variable is used for internationalization of programs at the
-     `awk' level.  It sets the default text domain for specially marked
-     string constants in the source text, as well as for the
-     `dcgettext()', `dcngettext()' and `bindtextdomain()' functions
-     (*note Internationalization::).  The default value of `TEXTDOMAIN'
-     is `"messages"'.
-
-     This variable is a `gawk' extension.  In other `awk'
-     implementations, or if `gawk' is in compatibility mode (*note
-     Options::), it is not special.
+     Used for internationalization of programs at the `awk' level.  It
+     sets the default text domain for specially marked string constants
+     in the source text, as well as for the `dcgettext()',
+     `dcngettext()' and `bindtextdomain()' functions (*note
+     Internationalization::).  The default value of `TEXTDOMAIN' is
+     `"messages"'.
 
    ---------- Footnotes ----------
 
@@ -9632,10 +10105,14 @@ File: gawk.info,  Node: Auto-set,  Next: ARGC and ARGV,  Prev: User-modified,  U
 
 The following is an alphabetical list of variables that `awk' sets
 automatically on certain occasions in order to provide information to
-your program.  The variables that are specific to `gawk' are marked
-with a pound sign (`#').
+your program.
+
+   The variables that are specific to `gawk' are marked with a pound
+sign (`#').  These variables are `gawk' extensions.  In other `awk'
+implementations or if `gawk' is in compatibility mode (*note
+Options::), they are not special.
 
-`ARGC, ARGV'
+`ARGC', `ARGV'
      The command-line arguments available to `awk' programs are stored
      in an array called `ARGV'.  `ARGC' is the number of command-line
      arguments present.  *Note Other Arguments::.  Unlike most `awk'
@@ -9645,13 +10122,13 @@ with a pound sign (`#').
           $ awk 'BEGIN {
           >         for (i = 0; i < ARGC; i++)
           >             print ARGV[i]
-          >      }' inventory-shipped BBS-list
+          >      }' inventory-shipped mail-list
           -| awk
           -| inventory-shipped
-          -| BBS-list
+          -| mail-list
 
      `ARGV[0]' contains `awk', `ARGV[1]' contains `inventory-shipped',
-     and `ARGV[2]' contains `BBS-list'.  The value of `ARGC' is three,
+     and `ARGV[2]' contains `mail-list'.  The value of `ARGC' is three,
      one more than the index of the last element in `ARGV', because the
      elements are numbered from zero.
 
@@ -9680,10 +10157,6 @@ with a pound sign (`#').
      program, `gawk' automatically sets it to a new value when the next
      file is opened.
 
-     This variable is a `gawk' extension.  In other `awk'
-     implementations, or if `gawk' is in compatibility mode (*note
-     Options::), it is not special.
-
 `ENVIRON'
      An associative array containing the values of the environment.
      The array indices are the environment variable names; the elements
@@ -9703,12 +10176,12 @@ with a pound sign (`#').
 
      Some operating systems may not have environment variables.  On
      such systems, the `ENVIRON' array is empty (except for
-     `ENVIRON["AWKPATH"]', *note AWKPATH Variable:: and
-     `ENVIRON["AWKLIBPATH"]', *note AWKLIBPATH Variable::).
+     `ENVIRON["AWKPATH"]' and `ENVIRON["AWKLIBPATH"]'; *note AWKPATH
+     Variable::, and *note AWKLIBPATH Variable::).
 
 `ERRNO #'
-     If a system error occurs during a redirection for `getline',
-     during a read for `getline', or during a `close()' operation, then
+     If a system error occurs during a redirection for `getline', during
+     a read for `getline', or during a `close()' operation, then
      `ERRNO' contains a string describing the error.
 
      In addition, `gawk' clears `ERRNO' before opening each
@@ -9722,19 +10195,14 @@ with a pound sign (`#').
      `getline' returning -1.  You are, of course, free to clear it
      yourself before doing an I/O operation.
 
-     This variable is a `gawk' extension.  In other `awk'
-     implementations, or if `gawk' is in compatibility mode (*note
-     Options::), it is not special.
-
 `FILENAME'
-     The name of the file that `awk' is currently reading.  When no
-     data files are listed on the command line, `awk' reads from the
-     standard input and `FILENAME' is set to `"-"'.  `FILENAME' is
-     changed each time a new file is read (*note Reading Files::).
-     Inside a `BEGIN' rule, the value of `FILENAME' is `""', since
-     there are no input files being processed yet.(1) (d.c.)  Note,
-     though, that using `getline' (*note Getline::) inside a `BEGIN'
-     rule can give `FILENAME' a value.
+     The name of the current input file.  When no data files are listed
+     on the command line, `awk' reads from the standard input and
+     `FILENAME' is set to `"-"'.  `FILENAME' changes each time a new
+     file is read (*note Reading Files::).  Inside a `BEGIN' rule, the
+     value of `FILENAME' is `""', since there are no input files being
+     processed yet.(1) (d.c.) Note, though, that using `getline' (*note
+     Getline::) inside a `BEGIN' rule can give `FILENAME' a value.
 
 `FNR'
      The current record number in the current file.  `FNR' is
@@ -9757,9 +10225,8 @@ with a pound sign (`#').
      all the user-defined or extension functions in the program.
 
           NOTE: Attempting to use the `delete' statement with the
-          `FUNCTAB' array will cause a fatal error.  Any attempt to
-          assign to an element of the `FUNCTAB' array will also cause a
-          fatal error.
+          `FUNCTAB' array causes a fatal error.  Any attempt to assign
+          to an element of `FUNCTAB' also causes a fatal error.
 
 `NR'
      The number of input records `awk' has processed since the
@@ -9823,8 +10290,8 @@ with a pound sign (`#').
 
     `PROCINFO["sorted_in"]'
           If this element exists in `PROCINFO', its value controls the
-          order in which array indices will be processed by `for (index
-          in array) ...' loops.  Since this is an advanced feature, we
+          order in which array indices will be processed by `for (INDEX
+          in ARRAY)' loops.  Since this is an advanced feature, we
           defer the full description until later; see *note Scanning an
           Array::.
 
@@ -9882,10 +10349,6 @@ with a pound sign (`#').
           open input file, pipe, or coprocess.  *Note Read Timeout::,
           for more information.
 
-     This array is a `gawk' extension.  In other `awk' implementations,
-     or if `gawk' is in compatibility mode (*note Options::), it is not
-     special.
-
 `RLENGTH'
      The length of the substring matched by the `match()' function
      (*note String Functions::).  `RLENGTH' is set by invoking the
@@ -9900,12 +10363,8 @@ with a pound sign (`#').
      match was found.
 
 `RT #'
-     This is set each time a record is read. It contains the input text
-     that matched the text denoted by `RS', the record separator.
-
-     This variable is a `gawk' extension.  In other `awk'
-     implementations, or if `gawk' is in compatibility mode (*note
-     Options::), it is not special.
+     The input text that matched the text denoted by `RS', the record
+     separator.  It is set every time a record is read.
 
 `SYMTAB #'
      An array whose indices are the names of all currently defined
@@ -9921,7 +10380,7 @@ with a pound sign (`#').
      the `delete' statement with the `SYMTAB' array.
 
      You may use an index for `SYMTAB' that is not a predefined
-     identifer:
+     identifier:
 
           SYMTAB["xxx"] = 5
           print SYMTAB["xxx"]
@@ -9941,7 +10400,7 @@ with a pound sign (`#').
               return SYMTAB[variable] *= amount
           }
 
-          NOTE: In order to avoid severe time-travel paradoxes(2),
+          NOTE: In order to avoid severe time-travel paradoxes,(2)
           neither `FUNCTAB' nor `SYMTAB' are available as elements
           within the `SYMTAB' array.
 
@@ -9987,13 +10446,13 @@ information contained in `ARGC' and `ARGV':
      $ awk 'BEGIN {
      >        for (i = 0; i < ARGC; i++)
      >            print ARGV[i]
-     >      }' inventory-shipped BBS-list
+     >      }' inventory-shipped mail-list
      -| awk
      -| inventory-shipped
-     -| BBS-list
+     -| mail-list
 
 In this example, `ARGV[0]' contains `awk', `ARGV[1]' contains
-`inventory-shipped', and `ARGV[2]' contains `BBS-list'.  Notice that
+`inventory-shipped', and `ARGV[2]' contains `mail-list'.  Notice that
 the `awk' program is not entered in `ARGV'.  The other command-line
 options, with their arguments, are also not entered.  This includes
 variable assignments done with the `-v' option (*note Options::).
@@ -10076,6 +10535,55 @@ are passed on to the `awk' program.  (*Note Getopt Function::, for an
 `awk' library function that parses command-line options.)
 
 
+File: gawk.info,  Node: Pattern Action Summary,  Prev: Built-in Variables,  Up: Patterns and Actions
+
+7.6 Summary
+===========
+
+   * Pattern-action pairs make up the basic elements of an `awk'
+     program.  Patterns are either normal expressions, range
+     expressions, regexp constants, one of the special keywords
+     `BEGIN', `END', `BEGINFILE', `ENDFILE', or empty.  The action
+     executes if the current record matches the pattern.  Empty
+     (missing) patterns match all records.
+
+   * I/O from `BEGIN' and `END' rules have certain constraints.  This
+     is also true, only more so, for `BEGINFILE' and `ENDFILE' rules.
+     The latter two give you "hooks" into `gawk''s file processing,
+     allowing you to recover from a file that otherwise would cause a
+     fatal error (such as a file that cannot be opened).
+
+   * Shell variables can be used in `awk' programs by careful use of
+     shell quoting.  It is easier to pass a shell variable into `awk'
+     by using the `-v' option and an `awk' variable.
+
+   * Actions consist of statements enclosed in curly braces. Statements
+     are built up from expressions, control statements, compound
+     statements, input and output statements, and deletion statements.
+
+   * The control statements in `awk' are `if'-`else', `while', `for',
+     and `do'-`while'.  `gawk' adds the `switch' statement.  There are
+     two flavors of `for' statement: one for for performing general
+     looping, and the other iterating through an array.
+
+   * `break' and `continue' let you exit early or start the next
+     iteration of a loop (or get out of a `switch').
+
+   * `next' and `nextfile' let you read the next record and start over
+     at the top of your program, or skip to the next input file and
+     start over, respectively.
+
+   * The `exit' statement terminates your program. When executed from
+     an action (or function body) it transfers control to the `END'
+     statements. From an `END' statement body, it exits immediately.
+     You may pass an optional numeric value to be used at `awk''s exit
+     status.
+
+   * Some built-in variables provide control over `awk', mainly for I/O.
+     Other variables convey information from `awk' to your program.
+
+
+
 File: gawk.info,  Node: Arrays,  Next: Functions,  Prev: Patterns and Actions,  Up: Top
 
 8 Arrays in `awk'
@@ -10091,7 +10599,7 @@ remove array elements.  It also describes how `awk' simulates
 multidimensional arrays, as well as some of the less obvious points
 about array usage.  The major node moves on to discuss `gawk''s facility
 for sorting arrays, and ends with a brief description of `gawk''s
-ability to support true multidimensional arrays.
+ability to support true arrays of arrays.
 
    `awk' maintains a single set of names that may be used for naming
 variables, arrays, and functions (*note User-defined::).  Thus, you
@@ -10109,6 +10617,7 @@ cannot have a variable and an array with the same name in the same
 * Multidimensional::            Emulating multidimensional arrays in
                                 `awk'.
 * Arrays of Arrays::            True multidimensional arrays.
+* Arrays Summary::              Summary of arrays.
 
 
 File: gawk.info,  Node: Array Basics,  Next: Delete,  Up: Arrays
@@ -10169,12 +10678,13 @@ declared.)
 
    A contiguous array of four elements might look like the following
 example, conceptually, if the element values are 8, `"foo"', `""', and
-30:
+30 as shown in *note figure-array-elements:::
 
-     +---------+---------+--------+---------+
-     |    8    |  "foo"  |   ""   |    30   |    Value
-     +---------+---------+--------+---------+
-          0         1         2         3        Index
++---------+---------+--------+---------+
+|    8    |  "foo"  |   ""   |    30   |    @r{Value}
++---------+---------+--------+---------+
+     0         1         2         3        @r{Index}
+Figure 8.1: A Contiguous Array
 
 Only the values are stored; the indices are implicit from the order of
 the values. Here, 8 is the value at index zero, because 8 appears in the
@@ -10217,9 +10727,9 @@ from English to French:
 
 Here we decided to translate the number one in both spelled-out and
 numeric form--thus illustrating that a single array can have both
-numbers and strings as indices.  In fact, array subscripts are always
+numbers and strings as indices.  (In fact, array subscripts are always
 strings; this is discussed in more detail in *note Numeric Array
-Subscripts::.  Here, the number `1' isn't double-quoted, since `awk'
+Subscripts::.)  Here, the number `1' isn't double-quoted, since `awk'
 automatically converts it to a string.
 
    The value of `IGNORECASE' has no effect upon array subscripting.
@@ -10271,11 +10781,11 @@ been assigned any value as well as elements that have been deleted
    To determine whether an element exists in an array at a certain
 index, use the following expression:
 
-     IND in ARRAY
+     INDX in ARRAY
 
-This expression tests whether the particular index IND exists, without
+This expression tests whether the particular index INDX exists, without
 the side effect of creating that element if it is not present.  The
-expression has the value one (true) if `ARRAY[IND]' exists and zero
+expression has the value one (true) if `ARRAY[INDX]' exists and zero
 (false) if it does not exist.  For example, this statement tests
 whether the array `frequencies' contains the index `2':
 
@@ -10410,19 +10920,54 @@ built-in function `length()'.
 
    The order in which elements of the array are accessed by this
 statement is determined by the internal arrangement of the array
-elements within `awk' and normally cannot be controlled or changed.
-This can lead to problems if new elements are added to ARRAY by
-statements in the loop body; it is not predictable whether the `for'
+elements within `awk' and in standard `awk' cannot be controlled or
+changed.  This can lead to problems if new elements are added to ARRAY
+by statements in the loop body; it is not predictable whether the `for'
 loop will reach them.  Similarly, changing VAR inside the loop may
 produce strange results.  It is best to avoid such things.
 
+   As a point of information, `gawk' sets up the list of elements to be
+iterated over before the loop starts, and does not change it.  But not
+all `awk' versions do so. Consider this program, named `loopcheck.awk':
+
+     BEGIN {
+         a["here"] = "here"
+         a["is"] = "is"
+         a["a"] = "a"
+         a["loop"] = "loop"
+         for (i in a) {
+             j++
+             a[j] = j
+             print i
+         }
+     }
+
+   Here is what happens when run with `gawk':
+
+     $ gawk -f loopcheck.awk
+     -| here
+     -| loop
+     -| a
+     -| is
+
+   Contrast this to Brian Kernighan's `awk':
+
+     $ nawk -f loopcheck.awk
+     -| loop
+     -| here
+     -| is
+     -| a
+     -| 1
+
 
 File: gawk.info,  Node: Controlling Scanning,  Prev: Scanning an Array,  Up: Array Basics
 
-8.1.6 Using Predefined Array Scanning Orders
---------------------------------------------
+8.1.6 Using Predefined Array Scanning Orders With `gawk'
+--------------------------------------------------------
+
+This node describes a feature that is specific to `gawk'.
 
-By default, when a `for' loop traverses an array, the order is
+   By default, when a `for' loop traverses an array, the order is
 undefined, meaning that the `awk' implementation determines the order
 in which the array is traversed.  This order is usually based on the
 internal implementation of arrays and will vary from one version of
@@ -10708,7 +11253,7 @@ might look like this:
      -| line 3
      -| line 2
 
-   Unfortunately, the very first line of input data did not come out in
+   Unfortunately, the very first line of input data did not appear in
 the output!
 
    Upon first glance, we would think that this program should have
@@ -10744,7 +11289,7 @@ File: gawk.info,  Node: Multidimensional,  Next: Arrays of Arrays,  Prev: Uninit
 
 * Menu:
 
-* Multiscanning::              Scanning multidimensional arrays.
+* Multiscanning::               Scanning multidimensional arrays.
 
    A multidimensional array is an array in which an element is
 identified by a sequence of indices instead of a single index.  For
@@ -10863,7 +11408,7 @@ The result is to set `separate[1]' to `"1"' and `separate[2]' to
 recovered.
 
 
-File: gawk.info,  Node: Arrays of Arrays,  Prev: Multidimensional,  Up: Arrays
+File: gawk.info,  Node: Arrays of Arrays,  Next: Arrays Summary,  Prev: Multidimensional,  Up: Arrays
 
 8.6 Arrays of Arrays
 ====================
@@ -10985,6 +11530,54 @@ by creating an arbitrary index:
      -| a
 
 
+File: gawk.info,  Node: Arrays Summary,  Prev: Arrays of Arrays,  Up: Arrays
+
+8.7 Summary
+===========
+
+   * Standard `awk' provides one-dimensional associative arrays (arrays
+     indexed by string values).  All arrays are associative; numeric
+     indices are converted automatically to strings.
+
+   * Array elements are referenced as `ARRAY[INDX]'.  Referencing an
+     element creates it if it did not exist previously.
+
+   * The proper way to see if an array has an element with a given index
+     is to use the `in' operator: `INDX in ARRAY'.
+
+   * Use `for (INDX in ARRAY) ...' to scan through all the individual
+     elements of an array. In the body of the loop, INDX takes on the
+     value of each element's index in turn.
+
+   * The order in which a `for (INDX in ARRAY)' loop traverses an array
+     is undefined in POSIX `awk' and varies among implementations.
+     `gawk' lets you control the order by assigning special predefined
+     values to `PROCINFO["sorted_in"]'.
+
+   * Use `delete ARRAY[INDX]' to delete an individual element.  You may
+     also use `delete ARRAY' to delete all of the elements in the
+     array.  This latter feature has been a common extension for many
+     years and is now standard, but may not be supported by all
+     commercial versions of `awk'.
+
+   * Standard `awk' simulates multidimensional arrays by separating
+     subscript values with a comma.  The values are concatenated into a
+     single string, separated by the value of `SUBSEP'.  The fact that
+     such a subscript was created in this way is not retained; thus
+     changing `SUBSEP' may have unexpected consequences.  You can use
+     `(SUB1, SUB2, ...) in ARRAY' to see if such a multidimensional
+     subscript exists in ARRAY.
+
+   * `gawk' provides true arrays of arrays. You use a separate set of
+     square brackets for each dimension in such an array:
+     `data[row][col]', for example. Array elements may thus be either
+     scalar values (number or string) or another array.
+
+   * Use the `isarray()' built-in function to determine if an array
+     element is itself a subarray.
+
+
+
 File: gawk.info,  Node: Functions,  Next: Library Functions,  Prev: Arrays,  Up: Top
 
 9 Functions
@@ -11004,6 +11597,7 @@ major node describes these "user-defined" functions.
 * Built-in::                    Summarizes the built-in functions.
 * User-defined::                Describes User-defined functions in detail.
 * Indirect Calls::              Choosing the function to call at runtime.
+* Functions Summary::           Summary of functions.
 
 
 File: gawk.info,  Node: Built-in,  Next: User-defined,  Up: Functions
@@ -11155,7 +11749,7 @@ brackets ([ ]):
      Return the positive square root of X.  `gawk' prints a warning
      message if X is negative.  Thus, `sqrt(4)' is 2.
 
-`srand([X])'
+`srand('[X]`)'
      Set the starting point, or seed, for generating random numbers to
      the value X.
 
@@ -11209,12 +11803,22 @@ returns the number of characters in a string, and not the number of
 bytes used to represent those characters. Similarly, `index()' works
 with character indices, and not byte indices.
 
+     CAUTION: A number of functions deal with indices into strings.
+     For these functions, the first character of a string is at
+     position (index) one.  This is different from C and the languages
+     descended from it, where the first character is at position zero.
+     You need to remember this when doing index calculations,
+     particularly if you are used to C.
+
    In the following list, optional parameters are enclosed in square
 brackets ([ ]).  Several functions perform string substitution; the
 full discussion is provided in the description of the `sub()' function,
 which comes towards the end since the list is presented in alphabetic
-order.  Those functions that are specific to `gawk' are marked with a
-pound sign (`#'):
+order.
+
+   Those functions that are specific to `gawk' are marked with a pound
+sign (`#').  They are not available in compatibility mode (*note
+Options::):
 
 * Menu:
 
@@ -11222,8 +11826,8 @@ pound sign (`#'):
                                 `&' with `sub()', `gsub()', and
                                 `gensub()'.
 
-`asort(SOURCE [, DEST [, HOW  ] ]) #'
-`asorti(SOURCE [, DEST [, HOW  ] ]) #'
+`asort('SOURCE [`,' DEST [`,' HOW ] ]`) #'
+`asorti('SOURCE [`,' DEST [`,' HOW ] ]`) #'
      These two functions are similar in behavior, so they are described
      together.
 
@@ -11240,9 +11844,10 @@ pound sign (`#'):
      SOURCE is duplicated into DEST.  DEST is then sorted, leaving the
      indices of SOURCE unchanged.
 
-     When comparing strings, `IGNORECASE' affects the sorting.  If the
-     SOURCE array contains subarrays as values (*note Arrays of
-     Arrays::), they will come last, after all scalar values.
+     When comparing strings, `IGNORECASE' affects the sorting (*note
+     Array Sorting Functions::).  If the SOURCE array contains
+     subarrays as values (*note Arrays of Arrays::), they will come
+     last, after all scalar values.
 
      For example, if the contents of `a' are as follows:
 
@@ -11269,10 +11874,7 @@ pound sign (`#'):
           a[2] = "last"
           a[3] = "middle"
 
-     `asort()' and `asorti()' are `gawk' extensions; they are not
-     available in compatibility mode (*note Options::).
-
-`gensub(REGEXP, REPLACEMENT, HOW [, TARGET]) #'
+`gensub(REGEXP, REPLACEMENT, HOW' [`, TARGET']`) #'
      Search the target string TARGET for matches of the regular
      expression REGEXP.  If HOW is a string beginning with `g' or `G'
      (short for "global"), then replace all matches of REGEXP with
@@ -11281,7 +11883,7 @@ pound sign (`#'):
      `$0'.  It returns the modified string as the result of the
      function and the original target string is _not_ changed.
 
-     `gensub()' is a general substitution function.  It's purpose is to
+     `gensub()' is a general substitution function.  Its purpose is to
      provide more features than the standard `sub()' and `gsub()'
      functions.
 
@@ -11322,10 +11924,7 @@ pound sign (`#'):
      If REGEXP does not match TARGET, `gensub()''s return value is the
      original unchanged value of TARGET.
 
-     `gensub()' is a `gawk' extension; it is not available in
-     compatibility mode (*note Options::).
-
-`gsub(REGEXP, REPLACEMENT [, TARGET])'
+`gsub(REGEXP, REPLACEMENT' [`, TARGET']`)'
      Search TARGET for _all_ of the longest, leftmost, _nonoverlapping_
      matching substrings it can find and replace them with REPLACEMENT.
      The `g' in `gsub()' stands for "global," which means replace
@@ -11349,12 +11948,11 @@ pound sign (`#'):
           $ awk 'BEGIN { print index("peanut", "an") }'
           -| 3
 
-     If FIND is not found, `index()' returns zero.  (Remember that
-     string indices in `awk' start at one.)
+     If FIND is not found, `index()' returns zero.
 
      It is a fatal error to use a regexp constant for FIND.
 
-`length([STRING])'
+`length('[STRING]`)'
      Return the number of characters in STRING.  If STRING is a number,
      the length of the digit string representing that number is
      returned.  For example, `length("abcde")' is five.  By contrast,
@@ -11394,14 +11992,14 @@ pound sign (`#'):
      array argument is not portable.  If `--posix' is supplied, using
      an array argument is a fatal error (*note Arrays::).
 
-`match(STRING, REGEXP [, ARRAY])'
+`match(STRING, REGEXP' [`, ARRAY']`)'
      Search STRING for the longest, leftmost substring matched by the
-     regular expression, REGEXP and return the character position, or
-     "index", at which that substring begins (one, if it starts at the
+     regular expression, REGEXP and return the character position
+     (index) at which that substring begins (one, if it starts at the
      beginning of STRING).  If no match is found, return zero.
 
-     The REGEXP argument may be either a regexp constant (`/.../') or a
-     string constant (`"..."').  In the latter case, the string is
+     The REGEXP argument may be either a regexp constant (`/'...`/') or
+     a string constant (`"'...`"').  In the latter case, the string is
      treated as a regexp to be matched.  *Note Computed Regexps::, for a
      discussion of the difference between the two forms, and the
      implications for writing your program correctly.
@@ -11481,7 +12079,7 @@ pound sign (`#'):
      compatibility mode (*note Options::), using a third argument is a
      fatal error.
 
-`patsplit(STRING, ARRAY [, FIELDPAT [, SEPS ] ]) #'
+`patsplit(STRING, ARRAY' [`, FIELDPAT' [`, SEPS' ] ]`) #'
      Divide STRING into pieces defined by FIELDPAT and store the pieces
      in ARRAY and the separator strings in the SEPS array.  The first
      piece is stored in `ARRAY[1]', the second piece in `ARRAY[2]', and
@@ -11500,10 +12098,7 @@ pound sign (`#'):
      Before splitting the string, `patsplit()' deletes any previously
      existing elements in the arrays ARRAY and SEPS.
 
-     The `patsplit()' function is a `gawk' extension.  In compatibility
-     mode (*note Options::), it is not available.
-
-`split(STRING, ARRAY [, FIELDSEP [, SEPS ] ])'
+`split(STRING, ARRAY' [`, FIELDSEP' [`, SEPS' ] ]`)'
      Divide STRING into pieces separated by FIELDSEP and store the
      pieces in ARRAY and the separator strings in the SEPS array.  The
      first piece is stored in `ARRAY[1]', the second piece in
@@ -11568,6 +12163,9 @@ pound sign (`#'):
      has one element only. The value of that element is the original
      STRING.
 
+     In POSIX mode (*note Options::), the fourth argument is not
+     allowed.
+
 `sprintf(FORMAT, EXPRESSION1, ...)'
      Return (without printing) the string that `printf' would have
      printed out with the same arguments (*note Printf::).  For example:
@@ -11593,18 +12191,15 @@ pound sign (`#'):
      Note also that `strtonum()' uses the current locale's decimal point
      for recognizing numbers (*note Locales::).
 
-     `strtonum()' is a `gawk' extension; it is not available in
-     compatibility mode (*note Options::).
-
-`sub(REGEXP, REPLACEMENT [, TARGET])'
+`sub(REGEXP, REPLACEMENT' [`, TARGET']`)'
      Search TARGET, which is treated as a string, for the leftmost,
      longest substring matched by the regular expression REGEXP.
      Modify the entire string by replacing the matched text with
      REPLACEMENT.  The modified string becomes the new value of TARGET.
      Return the number of substitutions made (zero or one).
 
-     The REGEXP argument may be either a regexp constant (`/.../') or a
-     string constant (`"..."').  In the latter case, the string is
+     The REGEXP argument may be either a regexp constant (`/'...`/') or
+     a string constant (`"'...`"').  In the latter case, the string is
      treated as a regexp to be matched.  *Note Computed Regexps::, for a
      discussion of the difference between the two forms, and the
      implications for writing your program correctly.
@@ -11669,7 +12264,7 @@ pound sign (`#'):
      into a string, and then the value of that string is treated as the
      regexp to match.
 
-`substr(STRING, START [, LENGTH])'
+`substr(STRING, START' [`, LENGTH' ]`)'
      Return a LENGTH-character-long substring of STRING, starting at
      character number START.  The first character of a string is
      character number one.(3) For example, `substr("washington", 5, 3)'
@@ -11747,9 +12342,9 @@ backslashes and ampersands into the replacement text, you need to
 remember that there are several levels of "escape processing" going on.
 
    First, there is the "lexical" level, which is when `awk' reads your
-program and builds an internal copy of it that can be executed.  Then
-there is the runtime level, which is when `awk' actually scans the
-replacement string to determine what to generate.
+program and builds an internal copy of it to execute.  Then there is
+the runtime level, which is when `awk' actually scans the replacement
+string to determine what to generate.
 
    At both levels, `awk' looks for a defined set of characters that can
 come after a backslash.  At the lexical level, it looks for the escape
@@ -11926,7 +12521,7 @@ File: gawk.info,  Node: I/O Functions,  Next: Time Functions,  Prev: String Func
 The following functions relate to input/output (I/O).  Optional
 parameters are enclosed in square brackets ([ ]):
 
-`close(FILENAME [, HOW])'
+`close('FILENAME [`,' HOW]`)'
      Close the file FILENAME for input or output. Alternatively, the
      argument may be a shell command that was used for creating a
      coprocess, or for redirecting to or from a pipe; then the
@@ -11941,7 +12536,10 @@ parameters are enclosed in square brackets ([ ]):
      not matter.  *Note Two-way I/O::, which discusses this feature in
      more detail and gives an example.
 
-`fflush([FILENAME])'
+     Note that the second argument to `close()' is a `gawk' extension;
+     it is not available in compatibility mode (*note Options::).
+
+`fflush('[FILENAME]`)'
      Flush any buffered output associated with FILENAME, which is
      either a file opened for writing or a shell command for
      redirecting output to a pipe or coprocess.
@@ -11957,9 +12555,9 @@ parameters are enclosed in square brackets ([ ]):
      function--`gawk' also buffers its output and the `fflush()'
      function forces `gawk' to flush its buffers.
 
-     `fflush()' was added to Brian Kernighan's version of `awk' in 1994.
-     For over two decades, it was not part of the POSIX standard.  As
-     of December, 2012, it was accepted for inclusion into the POSIX
+     `fflush()' was added to Brian Kernighan's `awk' in April of 1992.
+     For two decades, it was not part of the POSIX standard.  As of
+     December, 2012, it was accepted for inclusion into the POSIX
      standard.  See the Austin Group website
      (http://austingroupbugs.net/view.php?id=634).
 
@@ -11978,7 +12576,7 @@ parameters are enclosed in square brackets ([ ]):
           to flush only the standard output.
 
      `fflush()' returns zero if the buffer is successfully flushed;
-     otherwise, it returns non-zero (`gawk' returns -1).  In the case
+     otherwise, it returns non-zero. (`gawk' returns -1.)  In the case
      where all buffers are flushed, the return value is zero only if
      all buffers were flushed successfully.  Otherwise, it is -1, and
      `gawk' warns about the problem FILENAME.
@@ -12148,7 +12746,7 @@ enclosed in square brackets ([ ]):
      If DATESPEC does not contain enough elements or if the resulting
      time is out of range, `mktime()' returns -1.
 
-`strftime([FORMAT [, TIMESTAMP [, UTC-FLAG]]])'
+`strftime(' [FORMAT [`,' TIMESTAMP [`,' UTC-FLAG] ] ]`)'
      Format the time specified by TIMESTAMP based on the contents of
      the FORMAT string and return the result.  It is similar to the
      function of the same name in ISO C.  If UTC-FLAG is present and is
@@ -12163,7 +12761,8 @@ enclosed in square brackets ([ ]):
      Variables::).  The default string value is
      `"%a %b %e %H:%M:%S %Z %Y"'.  This format string produces output
      that is equivalent to that of the `date' utility.  You can assign
-     a new value to `PROCINFO["strftime"]' to change the default format.
+     a new value to `PROCINFO["strftime"]' to change the default
+     format; see below for the various format directives.
 
 `systime()'
      Return the current time as the number of seconds since the system
@@ -12227,11 +12826,11 @@ the following date format specifications:
 
 `%g'
      The year modulo 100 of the ISO 8601 week number, as a decimal
-     number (00-99).  For example, January 1, 1993 is in week 53 of
-     1992. Thus, the year of its ISO 8601 week number is 1992, even
-     though its year is 1993.  Similarly, December 31, 1973 is in week
-     1 of 1974. Thus, the year of its ISO week number is 1974, even
-     though its year is 1973.
+     number (00-99).  For example, January 1, 2012 is in week 53 of
+     2011. Thus, the year of its ISO 8601 week number is 2011, even
+     though its year is 2012.  Similarly, December 31, 2012 is in week
+     1 of 2013. Thus, the year of its ISO week number is 2013, even
+     though its year is 2012.
 
 `%G'
      The full year of the ISO week number, as a decimal number.
@@ -12311,7 +12910,7 @@ the following date format specifications:
      The year modulo 100 as a decimal number (00-99).
 
 `%Y'
-     The full year as a decimal number (e.g., 2011).
+     The full year as a decimal number (e.g., 2015).
 
 `%z'
      The timezone offset in a +HHMM format (e.g., the format necessary
@@ -12333,15 +12932,6 @@ the following date format specifications:
    If a conversion specifier is not one of the above, the behavior is
 undefined.(6)
 
-   Informally, a "locale" is the geographic place in which a program is
-meant to run.  For example, a common way to abbreviate the date
-September 4, 2012 in the United States is "9/4/12."  In many countries
-in Europe, however, it is abbreviated "4.9.12."  Thus, the `%x'
-specification in a `"US"' locale might produce `9/4/12', while in a
-`"EUROPE"' locale, it might produce `4.9.12'.  The ISO C standard
-defines a default `"C"' locale, which is an environment that is typical
-of what many C programmers are used to.
-
    For systems that are not yet fully standards-compliant, `gawk'
 supplies a copy of `strftime()' from the GNU C Library.  It supports
 all of the just-listed format specifications.  If that version is used
@@ -12371,7 +12961,7 @@ to the standard output and interprets the current time according to the
 format specifiers in the string.  For example:
 
      $ date '+Today is %A, %B %d, %Y.'
-     -| Today is Wednesday, March 30, 2011.
+     -| Today is Monday, May 05, 2014.
 
    Here is the `gawk' version of the `date' utility.  It has a shell
 "wrapper" to handle the `-u' option, which requires that `date' run as
@@ -12388,7 +12978,7 @@ if the time zone is set to UTC:
      esac
 
      gawk 'BEGIN  {
-         format = "%a %b %e %H:%M:%S %Z %Y"
+         format = PROCINFO["strftime"]
          exitval = 0
 
          if (ARGC > 2)
@@ -12465,23 +13055,23 @@ again with `10111001' and shift it left by three bits, you end up with
 `11001000'.  `gawk' provides built-in functions that implement the
 bitwise operations just described. They are:
 
-`and(V1, V2 [, ...])'
+``and(V1, V2' [`,' ...]`)''
      Return the bitwise AND of the arguments. There must be at least
      two.
 
-`compl(VAL)'
+``compl(VAL)''
      Return the bitwise complement of VAL.
 
-`lshift(VAL, COUNT)'
+``lshift(VAL, COUNT)''
      Return the value of VAL, shifted left by COUNT bits.
 
-`or(V1, V2 [, ...])'
+``or(V1, V2' [`,' ...]`)''
      Return the bitwise OR of the arguments. There must be at least two.
 
-`rshift(VAL, COUNT)'
+``rshift(VAL, COUNT)''
      Return the value of VAL, shifted right by COUNT bits.
 
-`xor(V1, V2 [, ...])'
+``xor(V1, V2' [`,' ...]`)''
      Return the bitwise XOR of the arguments. There must be at least
      two.
 
@@ -12566,8 +13156,8 @@ File: gawk.info,  Node: Type Functions,  Next: I18N Functions,  Prev: Bitwise Fu
 
 `gawk' provides a single function that lets you distinguish an array
 from a scalar variable.  This is necessary for writing code that
-traverses every element of a true multidimensional array (*note Arrays
-of Arrays::).
+traverses every element of an array of arrays.  (*note Arrays of
+Arrays::).
 
 `isarray(X)'
      Return a true value if X is an array. Otherwise return false.
@@ -12576,7 +13166,7 @@ of Arrays::).
 traversing a multidimensional array: you can test if an element is
 itself an array or not.  The second is inside the body of a
 user-defined function (not discussed yet; *note User-defined::), to
-test if a paramater is an array or not.
+test if a parameter is an array or not.
 
    Note, however, that using `isarray()' at the global level to test
 variables makes no sense. Since you are the one writing the program, you
@@ -12597,7 +13187,7 @@ descriptions here are purposely brief.  *Note Internationalization::,
 for the full story.  Optional parameters are enclosed in square
 brackets ([ ]):
 
-`bindtextdomain(DIRECTORY [, DOMAIN])'
+`bindtextdomain(DIRECTORY' [`,' DOMAIN]`)'
      Set the directory in which `gawk' will look for message
      translation files, in case they will not or cannot be placed in
      the "standard" locations (e.g., during testing).  It returns the
@@ -12607,13 +13197,13 @@ brackets ([ ]):
      the null string (`""'), then `bindtextdomain()' returns the
      current binding for the given DOMAIN.
 
-`dcgettext(STRING [, DOMAIN [, CATEGORY]])'
+`dcgettext(STRING' [`,' DOMAIN [`,' CATEGORY] ]`)'
      Return the translation of STRING in text domain DOMAIN for locale
      category CATEGORY.  The default value for DOMAIN is the current
      value of `TEXTDOMAIN'.  The default value for CATEGORY is
      `"LC_MESSAGES"'.
 
-`dcngettext(STRING1, STRING2, NUMBER [, DOMAIN [, CATEGORY]])'
+`dcngettext(STRING1, STRING2, NUMBER' [`,' DOMAIN [`,' CATEGORY] ]`)'
      Return the plural form used for NUMBER of the translation of
      STRING1 and STRING2 in text domain DOMAIN for locale category
      CATEGORY. STRING1 is the English singular variant of a message,
@@ -12656,10 +13246,10 @@ starting to execute any of it.
 
    The definition of a function named NAME looks like this:
 
-     function NAME([PARAMETER-LIST])
-     {
+     `function' NAME`('[PARAMETER-LIST]`)'
+     `{'
           BODY-OF-FUNCTION
-     }
+     `}'
 
 Here, NAME is the name of the function to define.  A valid function
 name is like a valid variable name: a sequence of letters, digits, and
@@ -12670,14 +13260,20 @@ function.
    PARAMETER-LIST is an optional list of the function's arguments and
 local variable names, separated by commas.  When the function is called,
 the argument names are used to hold the argument values given in the
-call.  The local variables are initialized to the empty string.  A
-function cannot have two parameters with the same name, nor may it have
-a parameter with the same name as the function itself.
+call.
 
-   In addition, according to the POSIX standard, function parameters
-cannot have the same name as one of the special built-in variables
-(*note Built-in Variables::.  Not all versions of `awk' enforce this
-restriction.
+   A function cannot have two parameters with the same name, nor may it
+have a parameter with the same name as the function itself.  In
+addition, according to the POSIX standard, function parameters cannot
+have the same name as one of the special built-in variables (*note
+Built-in Variables::).  Not all versions of `awk' enforce this
+restriction.)
+
+   Local variables act like the empty string if referenced where a
+string value is required, and like zero if referenced where a numeric
+value is required. This is the same as regular variables that have
+never been assigned a value.  (There is more to understand about local
+variables; *note Dynamic Typing::.)
 
    The BODY-OF-FUNCTION consists of `awk' statements.  It is the most
 important part of the definition, because it says what the function
@@ -12720,8 +13316,8 @@ function.  When this happens, we say the function is "recursive".  The
 act of a function calling itself is called "recursion".
 
    All the built-in functions return a value to their caller.
-User-defined functions can do also, using the `return' statement, which
-is described in detail in *note Return Statement::.  Many of the
+User-defined functions can do so also, using the `return' statement,
+which is described in detail in *note Return Statement::.  Many of the
 subsequent examples in this minor node use the `return' statement.
 
    In many `awk' implementations, including `gawk', the keyword
@@ -12791,7 +13387,8 @@ elements in an array and start over with a new list of elements (*note
 Delete::).  Instead of having to repeat this loop everywhere that you
 need to clear out an array, your program can just call `delarray'.
 (This guarantees portability.  The use of `delete ARRAY' to delete the
-contents of an entire array is a nonstandard extension.)
+contents of an entire array is a recent(1) addition to the POSIX
+standard.)
 
    The following is an example of a recursive function.  It takes a
 string as an input parameter and returns the string in backwards order.
@@ -12825,19 +13422,25 @@ an `awk' version of `ctime()':
 
      function ctime(ts,    format)
      {
-         format = "%a %b %e %H:%M:%S %Z %Y"
+         format = PROCINFO["strftime"]
          if (ts == 0)
              ts = systime()       # use current time as default
          return strftime(format, ts)
      }
 
+   ---------- Footnotes ----------
+
+   (1) Late in 2012.
+
 
 File: gawk.info,  Node: Function Caveats,  Next: Return Statement,  Prev: Function Example,  Up: User-defined
 
 9.2.3 Calling User-Defined Functions
 ------------------------------------
 
-This section describes how to call a user-defined function.
+"Calling a function" means causing the function to run and do its job.
+A function call is an expression and its value is the value returned by
+the function.
 
 * Menu:
 
@@ -12851,16 +13454,12 @@ File: gawk.info,  Node: Calling A Function,  Next: Variable Scope,  Up: Function
 9.2.3.1 Writing A Function Call
 ...............................
 
-"Calling a function" means causing the function to run and do its job.
-A function call is an expression and its value is the value returned by
-the function.
-
-   A function call consists of the function name followed by the
-arguments in parentheses.  `awk' expressions are what you write in the
-call for the arguments.  Each time the call is executed, these
-expressions are evaluated, and the values become the actual arguments.
-For example, here is a call to `foo()' with three arguments (the first
-being a string concatenation):
+A function call consists of the function name followed by the arguments
+in parentheses.  `awk' expressions are what you write in the call for
+the arguments.  Each time the call is executed, these expressions are
+evaluated, and the values become the actual arguments.  For example,
+here is a call to `foo()' with three arguments (the first being a
+string concatenation):
 
      foo(x y, "lose", 4 * z)
 
@@ -12877,9 +13476,10 @@ File: gawk.info,  Node: Variable Scope,  Next: Pass By Value/Reference,  Prev: C
 9.2.3.2 Controlling Variable Scope
 ..................................
 
-There is no way to make a variable local to a `{ ... }' block in `awk',
-but you can make a variable local to a function. It is good practice to
-do so whenever a variable is needed only in that function.
+Unlike many languages, there is no way to make a variable local to a
+`{' ... `}' block in `awk', but you can make a variable local to a
+function. It is good practice to do so whenever a variable is needed
+only in that function.
 
    To make a variable local to a function, simply declare the variable
 as an argument after the actual function arguments (*note Definition
@@ -13098,11 +13698,11 @@ control to the calling part of the `awk' program.  It can also be used
 to return a value for use in the rest of the `awk' program.  It looks
 like this:
 
-     return [EXPRESSION]
+     `return' [EXPRESSION]
 
    The EXPRESSION part is optional.  Due most likely to an oversight,
 POSIX does not define what the return value is if you omit the
-EXPRESSION.  Technically speaking, this make the returned value
+EXPRESSION.  Technically speaking, this makes the returned value
 undefined, and therefore, unpredictable.  In practice, though, all
 versions of `awk' simply return the null string, which acts like zero
 if used in a numeric context.
@@ -13196,14 +13796,14 @@ Here is an annotated sample program:
      }
 
    In this example, the first call to `foo()' generates a fatal error,
-so `gawk' will not report the second error. If you comment out that
-call, though, then `gawk' will report the second error.
+so `awk' will not report the second error. If you comment out that
+call, though, then `awk' does report the second error.
 
    Usually, such things aren't a big issue, but it's worth being aware
 of them.
 
 
-File: gawk.info,  Node: Indirect Calls,  Prev: User-defined,  Up: Functions
+File: gawk.info,  Node: Indirect Calls,  Next: Functions Summary,  Prev: User-defined,  Up: Functions
 
 9.3 Indirect Function Calls
 ===========================
@@ -13255,7 +13855,7 @@ and then a closing right parenthesis, with the addition of a leading `@'
 character:
 
      the_func = "sum"
-     result = @the_func()   # calls the `sum' function
+     result = @the_func()   # calls the sum() function
 
    Here is a full program that processes the previously shown data,
 using indirect function calls.
@@ -13406,8 +14006,8 @@ order.
 
    Next comes a sorting function.  It is parameterized with the
 starting and ending field numbers and the comparison function. It
-builds an array with the data and calls `quicksort' appropriately, and
-then formats the results as a single string:
+builds an array with the data and calls `quicksort()' appropriately,
+and then formats the results as a single string:
 
      # do_sort --- sort the data according to `compare'
      #             and return it as a string
@@ -13491,6 +14091,63 @@ example, in the following case:
 `gawk' will look up the actual function to call only once.
 
 
+File: gawk.info,  Node: Functions Summary,  Prev: Indirect Calls,  Up: Functions
+
+9.4 Summary
+===========
+
+   * `awk' provides built-in functions and lets you define your own
+     functions.
+
+   * POSIX `awk' provides three kinds of built-in functions: numeric,
+     string, and I/O.  `gawk' provides functions that work with values
+     representing time, do bit manipulation, sort arrays, and
+     internationalize and localize programs.  `gawk' also provides
+     several extensions to some of standard functions, typically in the
+     form of additional arguments.
+
+   * Functions accept zero or more arguments and return a value.  The
+     expressions that provide the argument values are completely
+     evaluated before the function is called. Order of evaluation is
+     not defined.  The return value can be ignored.
+
+   * The handling of backslash in `sub()' and `gsub()' is not simple.
+     It is more straightforward in `gawk''s `gensub()' function, but
+     that function still requires care in its use.
+
+   * User-defined functions provide important capabilities but come with
+     some syntactic inelegancies. In a function call, there cannot be
+     any space between the function name and the opening left
+     parenthesis of the argument list.  Also, there is no provision for
+     local variables, so the convention is to add extra parameters, and
+     to separate them visually from the real parameters by extra
+     whitespace.
+
+   * User-defined functions may call other user-defined (and built-in)
+     functions and may call themselves recursively. Function parameters
+     "hide" any global variables of the same names.
+
+   * Scalar values are passed to user-defined functions by value. Array
+     parameters are passed by reference; any changes made by the
+     function to array parameters are thus visible after the function
+     has returned.
+
+   * Use the `return' statement to return from a user-defined function.
+     An optional expression becomes the function's return value.  Only
+     scalar values may be returned by a function.
+
+   * If a variable that has never been used is passed to a user-defined
+     function, how that function treats the variable can set its nature:
+     either scalar or array.
+
+   * `gawk' provides indirect function calls using a special syntax.
+     By setting a variable to the name of a user-defined function, you
+     can determine at runtime what function will be called at that
+     point in the program. This is equivalent to function pointers in C
+     and C++.
+
+
+
 File: gawk.info,  Node: Library Functions,  Next: Sample Programs,  Prev: Functions,  Up: Top
 
 10 A Library of `awk' Functions
@@ -13566,6 +14223,8 @@ for different implementations of `awk' is pretty straightforward.
 * Passwd Functions::            Functions for getting user information.
 * Group Functions::             Functions for getting group information.
 * Walking Arrays::              A function to walk arrays of arrays.
+* Library Functions Summary::   Summary of library functions.
+* Library exercises::           Exercises.
 
    ---------- Footnotes ----------
 
@@ -13607,7 +14266,7 @@ will be accidentally shared with the user's program.
 
    In addition, several of the library functions use a prefix that helps
 indicate what function or set of functions use the variables--for
-example, `_pw_byname' in the user database routines (*note Passwd
+example, `_pw_byname()' in the user database routines (*note Passwd
 Functions::).  This convention is recommended, since it even further
 decreases the chance of inadvertent conflict among variable names.
 Note that this convention is used equally well for variable names and
@@ -13692,7 +14351,7 @@ versions of `awk':
 
      # mystrtonum --- convert string to number
 
-     function mystrtonum(str,        ret, chars, n, i, k, c)
+     function mystrtonum(str,        ret, n, i, k, c)
      {
          if (str ~ /^0[0-7]*$/) {
              # octal
@@ -13705,7 +14364,7 @@ versions of `awk':
 
                  ret = ret * 8 + k
              }
-         } else if (str ~ /^0[xX][[:xdigit:]]+/) {
+         } else if (str ~ /^0[xX][[:xdigit:]]+$/) {
              # hexadecimal
              str = substr(str, 3)    # lop off leading 0x
              n = length(str)
@@ -13713,10 +14372,7 @@ versions of `awk':
              for (i = 1; i <= n; i++) {
                  c = substr(str, i, 1)
                  c = tolower(c)
-                 if ((k = index("0123456789", c)) > 0)
-                     k-- # adjust for 1-basing in awk
-                 else if ((k = index("abcdef", c)) > 0)
-                     k += 9
+                 k = index("123456789abcdef", c)
 
                  ret = ret * 16 + k
              }
@@ -13858,9 +14514,9 @@ File: gawk.info,  Node: Round Function,  Next: Cliff Random Function,  Prev: Ass
 
 The way `printf' and `sprintf()' (*note Printf::) perform rounding
 often depends upon the system's C `sprintf()' subroutine.  On many
-machines, `sprintf()' rounding is "unbiased," which means it doesn't
-always round a trailing `.5' up, contrary to naive expectations.  In
-unbiased rounding, `.5' rounds to even, rather than always up, so 1.5
+machines, `sprintf()' rounding is "unbiased", which means it doesn't
+always round a trailing .5 up, contrary to naive expectations.  In
+unbiased rounding, .5 rounds to even, rather than always up, so 1.5
 rounds to 2 but 4.5 rounds to 4.  This means that if you are using a
 format that does rounding (e.g., `"%.0f"'), you should check what your
 system does.  The following function does traditional rounding; it
@@ -13894,7 +14550,7 @@ might be useful if your `awk''s `printf' does unbiased rounding:
      }
 
      # test harness
-     { print $0, round($0) }
+     # { print $0, round($0) }
 
 
 File: gawk.info,  Node: Cliff Random Function,  Next: Ordinal Functions,  Prev: Round Function,  Up: General Functions
@@ -13970,8 +14626,8 @@ corresponding character.  Both functions are written very nicely in
          }
      }
 
-   Some explanation of the numbers used by `chr' is worthwhile.  The
-most prominent character set in use today is ASCII.(1) Although an
+   Some explanation of the numbers used by `_ord_init()' is worthwhile.
+The most prominent character set in use today is ASCII.(1) Although an
 8-bit byte can hold 256 distinct values (from 0 to 255), ASCII only
 defines characters that use the values from 0 to 127.(2) In the now
 distant past, at least one minicomputer manufacturer used ASCII, but
@@ -14021,7 +14677,7 @@ tests such as used here prohibitively expensive.
 
    (2) ASCII has been extended in many countries to use the values from
 128 to 255 for country-specific characters.  If your  system uses these
-extensions, you can simplify `_ord_init' to loop from 0 to 255.
+extensions, you can simplify `_ord_init()' to loop from 0 to 255.
 
 
 File: gawk.info,  Node: Join Function,  Next: Getlocaltime Function,  Prev: Ordinal Functions,  Up: General Functions
@@ -14116,7 +14772,7 @@ current time formatted in the same way as the `date' utility:
          now = systime()
 
          # return date(1)-style output
-         ret = strftime("%a %b %e %H:%M:%S %Z %Y", now)
+         ret = strftime(PROCINFO["strftime"], now)
 
          # clear out target array
          delete time
@@ -14376,8 +15032,8 @@ File: gawk.info,  Node: File Checking,  Next: Empty Files,  Prev: Rewind Functio
 
 Normally, if you give `awk' a data file that isn't readable, it stops
 with a fatal error.  There are times when you might want to just ignore
-such files and keep going.  You can do this by prepending the following
-program to your `awk' program:
+such files and keep going.(1) You can do this by prepending the
+following program to your `awk' program:
 
      # readable.awk --- library file to skip over unreadable files
 
@@ -14397,10 +15053,16 @@ program to your `awk' program:
 element from `ARGV' with `delete' skips the file (since it's no longer
 in the list).  See also *note ARGC and ARGV::.
 
+   ---------- Footnotes ----------
+
+   (1) The `BEGINFILE' special pattern (*note BEGINFILE/ENDFILE::)
+provides an alternative mechanism for dealing with files that can't be
+opened.  However, the code here provides a portable solution.
+
 
 File: gawk.info,  Node: Empty Files,  Next: Ignoring Assigns,  Prev: File Checking,  Up: Data File Management
 
-10.3.4 Checking For Zero-length Files
+10.3.4 Checking for Zero-length Files
 -------------------------------------
 
 All known `awk' implementations silently skip over zero-length files.
@@ -14448,12 +15110,6 @@ normal case.
 end of the command-line arguments.  Note that the test in the condition
 of the `for' loop uses the `<=' operator, not `<'.
 
-   As an exercise, you might consider whether this same problem can be
-solved without relying on `gawk''s `ARGIND' variable.
-
-   As a second exercise, revise this code to handle the case where an
-intervening value in `ARGV' is a variable assignment.
-
 
 File: gawk.info,  Node: Ignoring Assigns,  Prev: Empty Files,  Up: Data File Management
 
@@ -14462,7 +15118,7 @@ File: gawk.info,  Node: Ignoring Assigns,  Prev: Empty Files,  Up: Data File Man
 
 Occasionally, you might not want `awk' to process command-line variable
 assignments (*note Assignment Options::).  In particular, if you have a
-file name that contain an `=' character, `awk' treats the file name as
+file name that contains an `=' character, `awk' treats the file name as
 an assignment, and does not process it.
 
    Some users have suggested an additional command-line option for
@@ -14745,7 +15401,7 @@ is in `ARGV[0]':
          # test program
          if (_getopt_test) {
              while ((_go_c = getopt(ARGC, ARGV, "ab:cd")) != -1)
-                 printf("c = <%c>, optarg = <%s>\n",
+                 printf("c = <%c>, Optarg = <%s>\n",
                                             _go_c, Optarg)
              printf("non-option arguments:\n")
              for (; Optind < ARGC; Optind++)
@@ -14758,17 +15414,17 @@ is in `ARGV[0]':
 result of two sample runs of the test program:
 
      $ awk -f getopt.awk -v _getopt_test=1 -- -a -cbARG bax -x
-     -| c = <a>, optarg = <>
-     -| c = <c>, optarg = <>
-     -| c = <b>, optarg = <ARG>
+     -| c = <a>, Optarg = <>
+     -| c = <c>, Optarg = <>
+     -| c = <b>, Optarg = <ARG>
      -| non-option arguments:
      -|         ARGV[3] = <bax>
      -|         ARGV[4] = <-x>
 
      $ awk -f getopt.awk -v _getopt_test=1 -- -a -x -- xyz abc
-     -| c = <a>, optarg = <>
+     -| c = <a>, Optarg = <>
      error--> x -- invalid option
-     -| c = <?>, optarg = <>
+     -| c = <?>, Optarg = <>
      -| non-option arguments:
      -|         ARGV[4] = <xyz>
      -|         ARGV[5] = <abc>
@@ -14827,7 +15483,7 @@ that "cats" the password database:
      /*
       * pwcat.c
       *
-      * Generate a printable version of the password database
+      * Generate a printable version of the password database.
       */
      #include <stdio.h>
      #include <pwd.h>
@@ -14958,7 +15614,7 @@ later.  The test can only be true for `gawk'.  It is false if using
 `FS' or `FPAT', or on some other `awk' implementation.
 
    The code that checks for using `FPAT', using `using_fpat' and
-`PROCINFO["FS"]' is similar.
+`PROCINFO["FS"]', is similar.
 
    The main part of the function uses a loop to read database lines,
 split the line into fields, and then store the line into each array as
@@ -14978,9 +15634,9 @@ create the element with the null string as its value:
          return _pw_byname[name]
      }
 
-   Similarly, the `getpwuid' function takes a user ID number argument.
-If that user number is in the database, it returns the appropriate
-line. Otherwise, it returns the null string:
+   Similarly, the `getpwuid()' function takes a user ID number
+argument. If that user number is in the database, it returns the
+appropriate line. Otherwise, it returns the null string:
 
      function getpwuid(uid)
      {
@@ -15052,7 +15708,7 @@ group database, is as follows:
      /*
       * grcat.c
       *
-      * Generate a printable version of the group database
+      * Generate a printable version of the group database.
       */
      #include <stdio.h>
      #include <grp.h>
@@ -15088,9 +15744,10 @@ Group Password
      used; it is usually empty or set to `*'.
 
 Group ID Number
-     The group's numeric group ID number; this number must be unique
-     within the file.  (On some systems it's a C `long', and not an
-     `int'.  Thus we cast it to `long' for all cases.)
+     The group's numeric group ID number; the association of name to
+     number must be unique within the file.  (On some systems it's a C
+     `long', and not an `int'.  Thus we cast it to `long' for all
+     cases.)
 
 Group Member List
      A comma-separated list of user names.  These users are members of
@@ -15194,15 +15851,12 @@ the database for the same group.  This is common when a group has a
 large number of members.  A pair of such entries might look like the
 following:
 
-     tvpeople:*:101:johnny,jay,arsenio
+     tvpeople:*:101:johny,jay,arsenio
      tvpeople:*:101:david,conan,tom,joan
 
    For this reason, `_gr_init()' looks to see if a group name or group
 ID number is already seen.  If it is, then the user names are simply
-concatenated onto the previous list of users.  (There is actually a
-subtle problem with the code just presented.  Suppose that the first
-time there were no names. This code adds the names with a leading
-comma. It also doesn't check that there is a `$4'.)
+concatenated onto the previous list of users.(1)
 
    Finally, `_gr_init()' closes the pipeline to `grcat', restores `FS'
 (and `FIELDWIDTHS' or `FPAT' if necessary), `RS', and `$0', initializes
@@ -15267,8 +15921,14 @@ very simple, relying on `awk''s associative arrays to do work.
 
    The `id' program in *note Id Program::, uses these functions.
 
+   ---------- Footnotes ----------
+
+   (1) There is actually a subtle problem with the code just presented.
+Suppose that the first time there were no names. This code adds the
+names with a leading comma. It also doesn't check that there is a `$4'.
+
 
-File: gawk.info,  Node: Walking Arrays,  Prev: Group Functions,  Up: Library Functions
+File: gawk.info,  Node: Walking Arrays,  Next: Library Functions Summary,  Prev: Group Functions,  Up: Library Functions
 
 10.7 Traversing Arrays of Arrays
 ================================
@@ -15318,17 +15978,73 @@ value.  Here is a main program to demonstrate:
      -| a[2][2] = 22
      -| a[3] = 3
 
-   Walking an array and processing each element is a general-purpose
-operation.  You might want to consider generalizing the `walk_array()'
-function by adding an additional parameter named `process'.
+
+File: gawk.info,  Node: Library Functions Summary,  Next: Library exercises,  Prev: Walking Arrays,  Up: Library Functions
+
+10.8 Summary
+============
+
+   * Reading programs is an excellent way to learn Good Programming.
+     The functions provided in this major node and the next are intended
+     to serve that purpose.
+
+   * When writing general-purpose library functions, put some thought
+     into how to name any global variables so that they won't conflict
+     with variables from a user's program.
+
+   * The functions presented here fit into the following categories:
 
-   Then, inside the loop, instead of simply printing the array element's
-index and value, use the indirect function call syntax (*note Indirect
-Calls::) on `process', passing it the index and the value.
+    General problems
+          Number to string conversion, assertions, rounding, random
+          number generation, converting characters to numbers, joining
+          strings, getting easily usable time-of-day information, and
+          reading a whole file in one shot.
+
+    Managing data files
+          Noting data file boundaries, rereading the current file,
+          checking for readable files, checking for zero-length files,
+          and treating assignments as file names.
+
+    Processing command-line options
+          An `awk' version of the standard C `getopt()' function.
+
+    Reading the user and group databases
+          Two sets of routines that parallel the C library versions.
+
+    Traversing arrays of arrays
+          A simple function to traverse an array of arrays to any depth.
+
+
+
+File: gawk.info,  Node: Library exercises,  Prev: Library Functions Summary,  Up: Library Functions
+
+10.9 Exercises
+==============
+
+  1. In *note Empty Files::, we presented the `zerofile.awk' program,
+     which made use of `gawk''s `ARGIND' variable.  Can this problem be
+     solved without relying on `ARGIND'?  If so, how?
+
+  2. As a related challenge, revise that code to handle the case where
+     an intervening value in `ARGV' is a variable assignment.
+
+  3. *note Walking Arrays::, presented a function that walked a
+     multidimensional array to print it out.  However, walking an array
+     and processing each element is a general-purpose operation.
+     Generalize the `walk_array()' function by adding an additional
+     parameter named `process'.
+
+     Then, inside the loop, instead of printing the array element's
+     index and value, use the indirect function call syntax (*note
+     Indirect Calls::) on `process', passing it the index and the value.
+
+     When calling `walk_array()', you would pass the name of a
+     user-defined function that expects to receive an index and a value,
+     and then processes the element.
+
+     Test your new version by printing the array; you should end up with
+     output identical to that of the original version.
 
-   When calling `walk_array()', you would pass the name of a
-user-defined function that expects to receive and index and a value,
-and then processes the element.
 
 
 File: gawk.info,  Node: Sample Programs,  Next: Advanced Features,  Prev: Library Functions,  Up: Top
@@ -15349,6 +16065,8 @@ Library Functions::.
 * Running Examples::            How to run these examples.
 * Clones::                      Clones of common utilities.
 * Miscellaneous Programs::      Some interesting `awk' programs.
+* Programs Summary::            Summary of programs.
+* Programs Exercises::          Exercises.
 
 
 File: gawk.info,  Node: Running Examples,  Next: Clones,  Up: Sample Programs
@@ -15494,7 +16212,7 @@ by characters, the output field separator is set to the null string:
                  OFS = ""
              } else if (c == "d") {
                  if (length(Optarg) > 1) {
-                     printf("Using first character of %s" \
+                     printf("cut: using first character of %s" \
                             " for delimiter\n", Optarg) > "/dev/stderr"
                      Optarg = substr(Optarg, 1, 1)
                  }
@@ -15503,7 +16221,7 @@ by characters, the output field separator is set to the null string:
                  if (FS == " ")    # defeat awk semantics
                      FS = "[ ]"
              } else if (c == "s")
-                 suppress++
+                 suppress = 1
              else
                  usage()
          }
@@ -15561,7 +16279,7 @@ splitting:
              if (index(f[i], "-") != 0) { # a range
                  m = split(f[i], g, "-")
                  if (m != 2 || g[1] >= g[2]) {
-                     printf("bad field list: %s\n",
+                     printf("cut: bad field list: %s\n",
                                        f[i]) > "/dev/stderr"
                      exit 1
                  }
@@ -15589,7 +16307,7 @@ fields to print are `$1', `$3', and `$5'.  The intermediate fields are
 the fields to print, and `t' tracks the complete field list, including
 filler fields:
 
-     function set_charlist(    field, i, j, f, g, t,
+     function set_charlist(    field, i, j, f, g, n, m, t,
                                filler, last, len)
      {
          field = 1   # count total fields
@@ -15599,7 +16317,7 @@ filler fields:
              if (index(f[i], "-") != 0) { # range
                  m = split(f[i], g, "-")
                  if (m != 2 || g[1] >= g[2]) {
-                     printf("bad character list: %s\n",
+                     printf("cut: bad character list: %s\n",
                                     f[i]) > "/dev/stderr"
                      exit 1
                  }
@@ -15672,7 +16390,7 @@ The `egrep' utility searches files for patterns.  It uses regular
 expressions that are almost identical to those available in `awk'
 (*note Regexp::).  You invoke it as follows:
 
-     egrep [ OPTIONS ] 'PATTERN' FILES ...
+     `egrep' [OPTIONS] `'PATTERN'' FILES ...
 
    The PATTERN is a regular expression.  In typical usage, the regular
 expression is quoted to prevent the shell from expanding any of the
@@ -15816,6 +16534,11 @@ know the total number of lines that matched the pattern:
          total += fcount
      }
 
+   The `BEGINFILE' and `ENDFILE' special patterns (*note
+BEGINFILE/ENDFILE::) could be used, but then the program would be
+`gawk'-specific. Additionally, this example was written before `gawk'
+acquired `BEGINFILE' and `ENDFILE'.
+
    The following rule does most of the work of matching lines. The
 variable `matches' is true if the line matched the pattern. If the user
 wants lines that did not match, the sense of `matches' is inverted
@@ -15863,9 +16586,7 @@ there are no matches, the exit status is one; otherwise it is zero:
 
      END    \
      {
-         if (total == 0)
-             exit 1
-         exit 0
+         exit (total == 0)
      }
 
    The `usage()' function prints a usage message in case of invalid
@@ -15907,7 +16628,7 @@ different from the real ones.  If possible, `id' also supplies the
 corresponding user and group names.  The output might look like this:
 
      $ id
-     -| uid=500(arnold) gid=500(arnold) groups=6(disk),7(lp),19(floppy)
+     -| uid=1000(arnold) gid=1000(arnold) groups=1000(arnold),4(adm),7(lp),27(sudo)
 
    This information is part of what is provided by `gawk''s `PROCINFO'
 array (*note Built-in Variables::).  However, the `id' utility provides
@@ -15940,34 +16661,26 @@ and the group numbers:
 
          printf("uid=%d", uid)
          pw = getpwuid(uid)
-         if (pw != "") {
-             split(pw, a, ":")
-             printf("(%s)", a[1])
-         }
+         if (pw != "")
+             pr_first_field(pw)
 
          if (euid != uid) {
              printf(" euid=%d", euid)
              pw = getpwuid(euid)
-             if (pw != "") {
-                 split(pw, a, ":")
-                 printf("(%s)", a[1])
-             }
+             if (pw != "")
+                 pr_first_field(pw)
          }
 
          printf(" gid=%d", gid)
          pw = getgrgid(gid)
-         if (pw != "") {
-             split(pw, a, ":")
-             printf("(%s)", a[1])
-         }
+         if (pw != "")
+             pr_first_field(pw)
 
          if (egid != gid) {
              printf(" egid=%d", egid)
              pw = getgrgid(egid)
-             if (pw != "") {
-                 split(pw, a, ":")
-                 printf("(%s)", a[1])
-             }
+             if (pw != "")
+                 pr_first_field(pw)
          }
 
          for (i = 1; ("group" i) in PROCINFO; i++) {
@@ -15976,10 +16689,8 @@ and the group numbers:
              group = PROCINFO["group" i]
              printf("%d", group)
              pw = getgrgid(group)
-             if (pw != "") {
-                 split(pw, a, ":")
-                 printf("(%s)", a[1])
-             }
+             if (pw != "")
+                 pr_first_field(pw)
              if (("group" (i+1)) in PROCINFO)
                  printf(",")
          }
@@ -15987,20 +16698,30 @@ and the group numbers:
          print ""
      }
 
+     function pr_first_field(str,  a)
+     {
+         split(str, a, ":")
+         printf("(%s)", a[1])
+     }
+
    The test in the `for' loop is worth noting.  Any supplementary
 groups in the `PROCINFO' array have the indices `"group1"' through
 `"groupN"' for some N, i.e., the total number of supplementary groups.
 However, we don't know in advance how many of these groups there are.
 
    This loop works by starting at one, concatenating the value with
-`"group"', and then using `in' to see if that value is in the array.
-Eventually, `i' is incremented past the last group in the array and the
-loop exits.
+`"group"', and then using `in' to see if that value is in the array
+(*note Reference to Elements::).  Eventually, `i' is incremented past
+the last group in the array and the loop exits.
 
    The loop is also correct if there are _no_ supplementary groups;
 then the condition is false the first time it's tested, and the loop
 body never executes.
 
+   The `pr_first_field()' function simply isolates out some code that
+is used repeatedly, making the whole program slightly shorter and
+cleaner.
+
 
 File: gawk.info,  Node: Split Program,  Next: Tee Program,  Prev: Id Program,  Up: Clones
 
@@ -16010,7 +16731,7 @@ File: gawk.info,  Node: Split Program,  Next: Tee Program,  Prev: Id Program,  U
 The `split' program splits large text files into smaller pieces.  Usage
 is as follows:(1)
 
-     split [-COUNT] file [ PREFIX ]
+     `split' [`-COUNT'] [FILE] [PREFIX]
 
    By default, the output files are named `xaa', `xab', and so on. Each
 file has 1000 lines in it, with the likely exception of the last file.
@@ -16034,7 +16755,7 @@ output file names:
      # split.awk --- do split in awk
      #
      # Requires ord() and chr() library functions
-     # usage: split [-num] [file] [outname]
+     # usage: split [-count] [file] [outname]
 
      BEGIN {
          outfile = "x"    # default
@@ -16043,7 +16764,7 @@ output file names:
              usage()
 
          i = 1
-         if (ARGV[i] ~ /^-[[:digit:]]+$/) {
+         if (i in ARGV && ARGV[i] ~ /^-[[:digit:]]+$/) {
              count = -ARGV[i]
              ARGV[i] = ""
              i++
@@ -16119,7 +16840,7 @@ The `tee' program is known as a "pipe fitting."  `tee' copies its
 standard input to its standard output and also duplicates it to the
 files named on the command line.  Its usage is as follows:
 
-     tee [-a] file ...
+     `tee' [`-a'] FILE ...
 
    The `-a' option tells `tee' to append to the named files, instead of
 truncating them and starting over.
@@ -16208,7 +16929,7 @@ and by default removes duplicate lines.  In other words, it only prints
 unique lines--hence the name.  `uniq' has a number of options. The
 usage is as follows:
 
-     uniq [-udc [-N]] [+N] [ INPUT FILE [ OUTPUT FILE ]]
+     `uniq' [`-udc' [`-N']] [`+N'] [INPUTFILE [OUTPUTFILE]]
 
    The options for `uniq' are:
 
@@ -16231,11 +16952,11 @@ usage is as follows:
      Skip N characters before comparing lines.  Any fields specified
      with `-N' are skipped first.
 
-`INPUT FILE'
+`INPUTFILE'
      Data is read from the input file named on the command line,
      instead of from the standard input.
 
-`OUTPUT FILE'
+`OUTPUTFILE'
      The generated output is sent to the named output file, instead of
      to the standard output.
 
@@ -16425,7 +17146,7 @@ File: gawk.info,  Node: Wc Program,  Prev: Uniq Program,  Up: Clones
 The `wc' (word count) utility counts lines, words, and characters in
 one or more input files. Its usage is as follows:
 
-     wc [-lwc] [ FILES ... ]
+     `wc' [`-lwc'] [FILES ...]
 
    If no files are specified on the command line, `wc' reads its
 standard input. If there are multiple files, it also prints total
@@ -16505,7 +17226,7 @@ lines, words, and characters to zero, and saves the current file name in
      }
 
    The `endfile()' function adds the current file's numbers to the
-running totals of lines, words, and characters.(1)  It then prints out
+running totals of lines, words, and characters.  It then prints out
 those numbers for the file that was just read. It relies on
 `beginfile()' to reset the numbers for the following data file:
 
@@ -16524,7 +17245,7 @@ those numbers for the file that was just read. It relies on
      }
 
    There is one rule that is executed for each line. It adds the length
-of the record, plus one, to `chars'.(2) Adding one plus the record
+of the record, plus one, to `chars'.(1) Adding one plus the record
 length is needed because the newline character separating records (the
 value of `RS') is not part of the record itself, and thus not included
 in its length.  Next, `lines' is incremented for each line read, and
@@ -16554,15 +17275,11 @@ in its length.  Next, `lines' is incremented for each line read, and
 
    ---------- Footnotes ----------
 
-   (1) `wc' can't just use the value of `FNR' in `endfile()'. If you
-examine the code in *note Filetrans Function::, you will see that `FNR'
-has already been reset by the time `endfile()' is called.
-
-   (2) Since `gawk' understands multibyte locales, this code counts
+   (1) Since `gawk' understands multibyte locales, this code counts
 characters, not bytes.
 
 
-File: gawk.info,  Node: Miscellaneous Programs,  Prev: Clones,  Up: Sample Programs
+File: gawk.info,  Node: Miscellaneous Programs,  Next: Programs Summary,  Prev: Clones,  Up: Sample Programs
 
 11.3 A Grab Bag of `awk' Programs
 =================================
@@ -16645,6 +17362,8 @@ File: gawk.info,  Node: Alarm Program,  Next: Translate Program,  Prev: Dupword
      Nothing cures insomnia like a ringing alarm clock.  -- Arnold
      Robbins
 
+     Sleep is for web developers.  -- Erik Quanstrom
+
    The following program is a simple "alarm clock" program.  You give
 it a time of day and an optional message.  At the specified time, it
 prints the message on the standard output. In addition, you can give it
@@ -16741,7 +17460,7 @@ alarm:
          # how long to sleep for
          naptime = target - current
          if (naptime <= 0) {
-             print "time is in the past!" > "/dev/stderr"
+             print "alarm: time is in the past!" > "/dev/stderr"
              exit 1
          }
 
@@ -16789,11 +17508,11 @@ there are more characters in the "from" list than in the "to" list, the
 last character of the "to" list is used for the remaining characters in
 the "from" list.
 
-   Some time ago, a user proposed that a transliteration function should
-be added to `gawk'.  The following program was written to prove that
-character transliteration could be done with a user-level function.
-This program is not as complete as the system `tr' utility but it does
-most of the job.
+   Once upon a time, a user proposed that a transliteration function
+should be added to `gawk'.  The following program was written to prove
+that character transliteration could be done with a user-level
+function.  This program is not as complete as the system `tr' utility
+but it does most of the job.
 
    The `translate' program demonstrates one of the few weaknesses of
 standard `awk': dealing with individual characters is very painful,
@@ -16874,8 +17593,8 @@ record:
    While it is possible to do character transliteration in a user-level
 function, it is not necessarily efficient, and we (the `gawk' authors)
 started to consider adding a built-in function.  However, shortly after
-writing this program, we learned that the System V Release 4 `awk' had
-added the `toupper()' and `tolower()' functions (*note String
+writing this program, we learned that Brian Kernighan had added the
+`toupper()' and `tolower()' functions to his `awk' (*note String
 Functions::).  These functions handle the vast majority of the cases
 where character transliteration is necessary, and so we chose to simply
 add those functions to `gawk' as well and then leave well enough alone.
@@ -16887,10 +17606,10 @@ program.
 
    ---------- Footnotes ----------
 
-   (1) On some older systems, including Solaris, `tr' may require that
-the lists be written as range expressions enclosed in square brackets
-(`[a-z]') and quoted, to prevent the shell from attempting a file name
-expansion.  This is not a feature.
+   (1) On some older systems, including Solaris, the system version of
+`tr' may require that the lists be written as range expressions
+enclosed in square brackets (`[a-z]') and quoted, to prevent the shell
+from attempting a file name expansion.  This is not a feature.
 
    (2) This program was written before `gawk' acquired the ability to
 split each character in a string into separate array elements.
@@ -17010,7 +17729,7 @@ File: gawk.info,  Node: Word Sorting,  Next: History Sorting,  Prev: Labels Prog
 
 When working with large amounts of text, it can be interesting to know
 how often different words appear.  For example, an author may overuse
-certain words, in which case she might wish to find synonyms to
+certain words, in which case he or she might wish to find synonyms to
 substitute for words that appear too often. This node develops a
 program for counting words and presenting the frequency information in
 a useful format.
@@ -17073,6 +17792,10 @@ script.  Here is the new version of the program:
              printf "%s\t%d\n", word, freq[word]
      }
 
+   The regexp `/[^[:alnum:]_[:blank:]]/' might have been written
+`/[[:punct:]]/', but then underscores would also be removed, and we
+want to keep them.
+
    Assuming we have saved this program in a file named `wordfreq.awk',
 and that the data is in `file1', the following pipeline:
 
@@ -17150,8 +17873,7 @@ information.  For example, using the following `print' statement in the
 
      print data[lines[i]], lines[i]
 
-   This works because `data[$0]' is incremented each time a line is
-seen.
+This works because `data[$0]' is incremented each time a line is seen.
 
 
 File: gawk.info,  Node: Extract Program,  Next: Simple Sed,  Prev: History Sorting,  Up: Miscellaneous Programs
@@ -17240,7 +17962,7 @@ with a zero exit status, signifying OK:
      /^@c(omment)?[ \t]+system/    \
      {
          if (NF < 3) {
-             e = (FILENAME ":" FNR)
+             e = ("extract: " FILENAME ":" FNR)
              e = (e  ": badly formed `system' line")
              print e > "/dev/stderr"
              next
@@ -17249,7 +17971,7 @@ with a zero exit status, signifying OK:
          $2 = ""
          stat = system($0)
          if (stat != 0) {
-             e = (FILENAME ":" FNR)
+             e = ("extract: " FILENAME ":" FNR)
              e = (e ": warning: system returned " stat)
              print e > "/dev/stderr"
          }
@@ -17279,16 +18001,17 @@ function (*note String Functions::).  The `@' symbol is used as the
 separator character.  Each element of `a' that is empty indicates two
 successive `@' symbols in the original line.  For each two empty
 elements (`@@' in the original file), we have to add a single `@'
-symbol back in.(1)
+symbol back in.
 
    When the processing of the array is finished, `join()' is called
-with the value of `SUBSEP', to rejoin the pieces back into a single
-line.  That line is then printed to the output file:
+with the value of `SUBSEP' (*note Multidimensional::), to rejoin the
+pieces back into a single line.  That line is then printed to the
+output file:
 
      /^@c(omment)?[ \t]+file/    \
      {
          if (NF != 3) {
-             e = (FILENAME ":" FNR ": badly formed `file' line")
+             e = ("extract: " FILENAME ":" FNR ": badly formed `file' line")
              print e > "/dev/stderr"
              next
          }
@@ -17339,7 +18062,7 @@ closing the open file:
 
      function unexpected_eof()
      {
-         printf("%s:%d: unexpected EOF or error\n",
+         printf("extract: %s:%d: unexpected EOF or error\n",
              FILENAME, FNR) > "/dev/stderr"
          exit 1
      }
@@ -17349,11 +18072,6 @@ closing the open file:
              close(curfile)
      }
 
-   ---------- Footnotes ----------
-
-   (1) This program was written before `gawk' had the `gensub()'
-function. Consider how you might use it to simplify the code.
-
 
 File: gawk.info,  Node: Simple Sed,  Next: Igawk Program,  Prev: Extract Program,  Up: Miscellaneous Programs
 
@@ -17530,10 +18248,10 @@ are several cases of interest:
      programming trick.  Don't worry about it if you are not familiar
      with `sh'.)
 
-`-v, -F'
+`-v', `-F'
      These are saved and passed on to `gawk'.
 
-`-f, --file, --file=, -Wfile='
+`-f', `--file', `--file=', `-Wfile='
      The file name is appended to the shell variable `program' with an
      `@include' statement.  The `expr' utility is used to remove the
      leading option part of the argument (e.g., `--file=').  (Typical
@@ -17542,10 +18260,10 @@ are several cases of interest:
      sequences in their arguments, possibly mangling the program text.
      Using `expr' avoids this problem.)
 
-`--source, --source=, -Wsource='
+`--source', `--source=', `-Wsource='
      The source text is appended to `program'.
 
-`--version, -Wversion'
+`--version', `-Wversion'
      `igawk' prints its version number, runs `gawk --version' to get
      the `gawk' version information, and then exits.
 
@@ -17691,12 +18409,12 @@ which represents the current directory:
                  pathlist[i] = "."
          }
 
-   The stack is initialized with `ARGV[1]', which will be `/dev/stdin'.
-The main loop comes next.  Input lines are read in succession. Lines
-that do not start with `@include' are printed verbatim.  If the line
-does start with `@include', the file name is in `$2'.  `pathto()' is
-called to generate the full path.  If it cannot, then the program
-prints an error message and continues.
+   The stack is initialized with `ARGV[1]', which will be
+`"/dev/stdin"'.  The main loop comes next.  Input lines are read in
+succession. Lines that do not start with `@include' are printed
+verbatim.  If the line does start with `@include', the file name is in
+`$2'.  `pathto()' is called to generate the full path.  If it cannot,
+then the program prints an error message and continues.
 
    The next thing to check is if the file is included already.  The
 `processed' array is indexed by the full file name of each included
@@ -17719,7 +18437,7 @@ zero, the program is done:
                  }
                  fpath = pathto($2)
                  if (fpath == "") {
-                     printf("igawk:%s:%d: cannot find %s\n",
+                     printf("igawk: %s:%d: cannot find %s\n",
                          input[stackptr], FNR, $2) > "/dev/stderr"
                      continue
                  }
@@ -17773,7 +18491,7 @@ supplied.
    The `eval' command is a shell construct that reruns the shell's
 parsing process.  This keeps things properly quoted.
 
-   This version of `igawk' represents my fifth version of this program.
+   This version of `igawk' represents the fifth version of this program.
 There are four key simplifications that make the program work better:
 
    * Using `@include' even for the files named with `-f' makes building
@@ -17803,26 +18521,6 @@ manipulation using the shell than it is in `awk'.
    Finally, `igawk' shows that it is not always necessary to add new
 features to a program; they can often be layered on top.
 
-   As an additional example of this, consider the idea of having two
-files in a directory in the search path:
-
-`default.awk'
-     This file contains a set of default library functions, such as
-     `getopt()' and `assert()'.
-
-`site.awk'
-     This file contains library functions that are specific to a site or
-     installation; i.e., locally developed functions.  Having a
-     separate file allows `default.awk' to change with new `gawk'
-     releases, without requiring the system administrator to update it
-     each time by adding the local functions.
-
-   One user suggested that `gawk' be modified to automatically read
-these files upon startup.  Instead, it would be very simple to modify
-`igawk' to do this. Since `igawk' can process nested `@include'
-directives, `default.awk' could simply contain `@include' statements
-for the desired library functions.
-
    ---------- Footnotes ----------
 
    (1) Fully explaining the `sh' language is beyond the scope of this
@@ -17947,7 +18645,129 @@ supplies the following copyright terms:
      X*(X-x)-o*o,(x+X)*o*o+o,x*(X-x)-O-O,x-O+(O+o+X+x)*(o+O),X*X-X*(x-O)-x+O,
      O+X*(o*(o+O)+O),+x+O+X*o,x*(x-o),(o+X+x)*o*o-(x-O-O),O+(X-x)*(X+O),x-O}'
 
-   We leave it to you to determine what the program does.
+   We leave it to you to determine what the program does.  (If you are
+truly desperate to understand it, see Chris Johansen's explanation,
+which is embedded in the Texinfo source file for this Info file.)
+
+
+File: gawk.info,  Node: Programs Summary,  Next: Programs Exercises,  Prev: Miscellaneous Programs,  Up: Sample Programs
+
+11.4 Summary
+============
+
+   * The functions provided in this major node and the previous one
+     continue on the theme that reading programs is an excellent way to
+     learn Good Programming.
+
+   * Using `#!' to make `awk' programs directly runnable makes them
+     easier to use.  Otherwise, invoke the program using `awk -f ...'.
+
+   * Reimplementing standard POSIX programs in `awk' is a pleasant
+     exercise; `awk''s expressive power lets you write such programs in
+     relatively few lines of code, yet they are functionally complete
+     and usable.
+
+   * One of standard `awk''s weaknesses is working with individual
+     characters.  The ability to use `split()' with the empty string as
+     the separator can considerably simplify such tasks.
+
+   * The library functions from *note Library Functions::, proved their
+     usefulness for a number of real (if small) programs.
+
+   * Besides reinventing POSIX wheels, other programs solved a
+     selection of interesting problems, such as finding duplicates
+     words in text, printing mailing labels, and finding anagrams.
+
+
+
+File: gawk.info,  Node: Programs Exercises,  Prev: Programs Summary,  Up: Sample Programs
+
+11.5 Exercises
+==============
+
+  1. Rewrite `cut.awk' (*note Cut Program::) using `split()' with `""'
+     as the seperator.
+
+  2. In *note Egrep Program::, we mentioned that `egrep -i' could be
+     simulated in versions of `awk' without `IGNORECASE' by using
+     `tolower()' on the line and the pattern. In a footnote there, we
+     also mentioned that this solution has a bug: the translated line is
+     output, and not the original one.  Fix this problem.
+
+  3. The POSIX version of `id' takes options that control which
+     information is printed.  Modify the `awk' version (*note Id
+     Program::) to accept the same arguments and perform in the same
+     way.
+
+  4. The `split.awk' program (*note Split Program::) uses the `chr()'
+     and `ord()' functions to move through the letters of the alphabet.
+     Modify the program to instead use only the `awk' built-in
+     functions, such as `index()' and `substr()'.
+
+  5. The `split.awk' program (*note Split Program::) assumes that
+     letters are contiguous in the character set, which isn't true for
+     EBCDIC systems.  Fix this problem.
+
+  6. Why can't the `wc.awk' program (*note Wc Program::) just use the
+     value of `FNR' in `endfile()'?  Hint: Examine the code in *note
+     Filetrans Function::.
+
+  7. Manipulation of individual characters in the `translate' program
+     (*note Translate Program::) is painful using standard `awk'
+     functions.  Given that `gawk' can split strings into individual
+     characters using `""' as the separator, how might you use this
+     feature to simplify the program?
+
+  8. The `extract.awk' program (*note Extract Program::) was written
+     before `gawk' had the `gensub()' function.  Use it to simplify the
+     code.
+
+  9. Compare the performance of the `awksed.awk' program (*note Simple
+     Sed::) with the more straightforward:
+
+          BEGIN {
+              pat = ARGV[1]
+              repl = ARGV[2]
+              ARGV[1] = ARGV[2] = ""
+          }
+
+          { gsub(pat, repl); print }
+
+ 10. What are the advantages and disadvantages of `awksed.awk' versus
+     the real `sed' utility?
+
+ 11. In *note Igawk Program::, we mentioned that not trying to save the
+     line read with `getline' in the `pathto()' function when testing
+     for the file's accessibility for use with the main program
+     simplifies things considerably.  What problem does this engender
+     though?
+
+ 12. As an additional example of the idea that it is not always
+     necessary to add new features to a program, consider the idea of
+     having two files in a directory in the search path:
+
+    `default.awk'
+          This file contains a set of default library functions, such
+          as `getopt()' and `assert()'.
+
+    `site.awk'
+          This file contains library functions that are specific to a
+          site or installation; i.e., locally developed functions.
+          Having a separate file allows `default.awk' to change with
+          new `gawk' releases, without requiring the system
+          administrator to update it each time by adding the local
+          functions.
+
+     One user suggested that `gawk' be modified to automatically read
+     these files upon startup.  Instead, it would be very simple to
+     modify `igawk' to do this. Since `igawk' can process nested
+     `@include' directives, `default.awk' could simply contain
+     `@include' statements for the desired library functions.  Make
+     this change.
+
+ 13. Modify `anagram.awk' (*note Anagram Program::), to avoid the use
+     of the external `sort' utility.
+
 
 
 File: gawk.info,  Node: Advanced Features,  Next: Internationalization,  Prev: Sample Programs,  Up: Top
@@ -17993,6 +18813,7 @@ own:
 * Two-way I/O::                 Two-way communications with another process.
 * TCP/IP Networking::           Using `gawk' for network programming.
 * Profiling::                   Profiling your `awk' programs.
+* Advanced Features Summary::   Summary of advanced features.
 
 
 File: gawk.info,  Node: Nondecimal Data,  Next: Array Sorting,  Up: Advanced Features
@@ -18016,8 +18837,8 @@ your data as numeric:
 
 The `print' statement treats its expressions as strings.  Although the
 fields can act as numbers when necessary, they are still strings, so
-`print' does not try to treat them numerically.  You may need to add
-zero to a field to force it to be treated as a number.  For example:
+`print' does not try to treat them numerically.  You need to add zero
+to a field to force it to be treated as a number.  For example:
 
      $ echo 0123 123 0x123 | gawk --non-decimal-data '
      > { print $1, $2, $3
@@ -18032,7 +18853,7 @@ request it.
 
      CAUTION: _Use of this option is not recommended._ It can break old
      programs very badly.  Instead, use the `strtonum()' function to
-     convert your data (*note Nondecimal-numbers::).  This makes your
+     convert your data (*note String Functions::).  This makes your
      programs easier to write and easier to read, and leads to less
      surprising results.
 
@@ -18071,7 +18892,7 @@ you do this.
 
    *note Controlling Scanning::, describes how you can assign special,
 pre-defined values to `PROCINFO["sorted_in"]' in order to control the
-order in which `gawk' will traverse an array during a `for' loop.
+order in which `gawk' traverses an array during a `for' loop.
 
    In addition, the value of `PROCINFO["sorted_in"]' can be a function
 name.  This lets you traverse an array based on any custom criterion.
@@ -18344,9 +19165,9 @@ become the values of the result array:
 
    So far, so good. Now it starts to get interesting.  Both `asort()'
 and `asorti()' accept a third string argument to control comparison of
-array elements.  In *note String Functions::, we ignored this third
-argument; however, the time has now come to describe how this argument
-affects these two functions.
+array elements.  When we introduced `asort()' and `asorti()' in *note
+String Functions::, we ignored this third argument; however, now is the
+time to describe how this argument affects these two functions.
 
    Basically, the third argument specifies how the array is to be
 sorted.  There are two possibilities.  As with `PROCINFO["sorted_in"]',
@@ -18494,7 +19315,8 @@ the `gawk' program.  Once all of the data has been read, `gawk'
 terminates the coprocess and exits.
 
    As a side note, the assignment `LC_ALL=C' in the `sort' command
-ensures traditional Unix (ASCII) sorting from `sort'.
+ensures traditional Unix (ASCII) sorting from `sort'.  This is not
+strictly necessary here, but it's good to know how to do this.
 
    You may also use pseudo-ttys (ptys) for two-way communication
 instead of pipes, if your system supports them.  This is done on a
@@ -18506,14 +19328,15 @@ per-command basis, by setting a special element in the `PROCINFO' array
      print ... |& command       # start two-way pipe
      ...
 
-Using ptys avoids the buffer deadlock issues described earlier, at some
-loss in performance.  If your system does not have ptys, or if all the
-system's ptys are in use, `gawk' automatically falls back to using
-regular pipes.
+Using ptys usually avoids the buffer deadlock issues described earlier,
+at some loss in performance.  If your system does not have ptys, or if
+all the system's ptys are in use, `gawk' automatically falls back to
+using regular pipes.
 
    ---------- Footnotes ----------
 
-   (1) This is very different from the same operator in the C shell.
+   (1) This is very different from the same operator in the C shell and
+in Bash.
 
 
 File: gawk.info,  Node: TCP/IP Networking,  Next: Profiling,  Prev: Two-way I/O,  Up: Advanced Features
@@ -18593,7 +19416,7 @@ much more complete introduction and discussion, as well as extensive
 examples.
 
 
-File: gawk.info,  Node: Profiling,  Prev: TCP/IP Networking,  Up: Advanced Features
+File: gawk.info,  Node: Profiling,  Next: Advanced Features Summary,  Prev: TCP/IP Networking,  Up: Advanced Features
 
 12.5 Profiling Your `awk' Programs
 ==================================
@@ -18651,56 +19474,64 @@ First, the `awk' program:
      junk
 
    Here is the `awkprof.out' that results from running the `gawk'
-profiler on this program and data (this example also illustrates that
-`awk' programmers sometimes have to work late):
+profiler on this program and data. (This example also illustrates that
+`awk' programmers sometimes get up very early in the morning to work.)
 
-             # gawk profile, created Sun Aug 13 00:00:15 2000
+         # gawk profile, created Thu Feb 27 05:16:21 2014
 
-             # BEGIN block(s)
+         # BEGIN block(s)
 
-             BEGIN {
-          1          print "First BEGIN rule"
-          1          print "Second BEGIN rule"
-             }
+         BEGIN {
+      1          print "First BEGIN rule"
+         }
 
-             # Rule(s)
+         BEGIN {
+      1          print "Second BEGIN rule"
+         }
 
-          5  /foo/   { # 2
-          2          print "matched /foo/, gosh"
-          6          for (i = 1; i <= 3; i++) {
-          6                  sing()
-                     }
-             }
+         # Rule(s)
 
-          5  {
-          5          if (/foo/) { # 2
-          2                  print "if is true"
-          3          } else {
-          3                  print "else is true"
-                     }
-             }
+      5  /foo/ { # 2
+      2          print "matched /foo/, gosh"
+      6          for (i = 1; i <= 3; i++) {
+      6                  sing()
+                 }
+         }
+
+      5  {
+      5          if (/foo/) { # 2
+      2                  print "if is true"
+      3          } else {
+      3                  print "else is true"
+                 }
+         }
 
-             # END block(s)
+         # END block(s)
 
-             END {
-          1          print "First END rule"
-          1          print "Second END rule"
-             }
+         END {
+      1          print "First END rule"
+         }
 
-             # Functions, listed alphabetically
+         END {
+      1          print "Second END rule"
+         }
 
-          6  function sing(dummy)
-             {
-          6          print "I gotta be me!"
-             }
+
+         # Functions, listed alphabetically
+
+      6  function sing(dummy)
+         {
+      6          print "I gotta be me!"
+         }
 
    This example illustrates many of the basic features of profiling
 output.  They are as follows:
 
-   * The program is printed in the order `BEGIN' rule, `BEGINFILE' rule,
-     pattern/action rules, `ENDFILE' rule, `END' rule and functions,
-     listed alphabetically.  Multiple `BEGIN' and `END' rules are
-     merged together, as are multiple `BEGINFILE' and `ENDFILE' rules.
+   * The program is printed in the order `BEGIN' rules, `BEGINFILE'
+     rules, pattern/action rules, `ENDFILE' rules, `END' rules and
+     functions, listed alphabetically.  Multiple `BEGIN' and `END'
+     rules retain their separate identities, as do multiple `BEGINFILE'
+     and `ENDFILE' rules.
 
    * Pattern-action rules have two counts.  The first count, to the
      left of the rule, shows how many times the rule's pattern was
@@ -18751,8 +19582,7 @@ you typed when you wrote it.  This is because `gawk' creates the
 profiled version by "pretty printing" its internal representation of
 the program.  The advantage to this is that `gawk' can produce a
 standard representation.  The disadvantage is that all source-code
-comments are lost, as are the distinctions among multiple `BEGIN',
-`END', `BEGINFILE', and `ENDFILE' rules.  Also, things such as:
+comments are lost.  Also, things such as:
 
      /foo/
 
@@ -18782,7 +19612,7 @@ As usual, the profiled version of the program is written to
 `awkprof.out', or to a different file if one specified with the
 `--profile' option.
 
-   Along with the regular profile, as shown earlier, the profile
+   Along with the regular profile, as shown earlier, the profile file
 includes a trace of any active functions:
 
      # Function Call Stack:
@@ -18811,6 +19641,51 @@ by the `Ctrl-<\>' key.
 called this way, `gawk' "pretty prints" the program into `awkprof.out',
 without any execution counts.
 
+     NOTE: The `--pretty-print' option still runs your program.  This
+     will change in the next major release.
+
+
+File: gawk.info,  Node: Advanced Features Summary,  Prev: Profiling,  Up: Advanced Features
+
+12.6 Summary
+============
+
+   * The `--non-decimal-data' option causes `gawk' to treat octal- and
+     hexadecimal-looking input data as octal and hexadecimal.  This
+     option should be used with caution or not at all; use of
+     `strtonum()' is preferable.
+
+   * You can take over complete control of sorting in `for (INDX in
+     ARRAY)' array traversal by setting `PROCINFO["sorted_in"]' to the
+     name of a user-defined function that does the comparison of array
+     elements based on index and value.
+
+   * Similarly, you can supply the name of a user-defined comparison
+     function as the third argument to either `asort()' or `asorti()'
+     to control how those functions sort arrays. Or you may provide one
+     of the predefined control strings that work for
+     `PROCINFO["sorted_in"]'.
+
+   * You can use the `|&' operator to create a two-way pipe to a
+     co-process.  You read from the co-process with `getline' and write
+     to it with `print' or `printf'. Use `close()' to close off the
+     co-process completely, or optionally, close off one side of the
+     two-way communications.
+
+   * By using special "file names" with the `|&' operator, you can open
+     a TCP/IP (or UDP/IP) connection to remote hosts in the Internet.
+     `gawk' supports both IPv4 an IPv6.
+
+   * You can generate statement count profiles of your program. This
+     can help you determine which parts of your program may be taking
+     the most time and let you tune them more easily.  Sending the
+     `USR1' signal while profiling causes `gawk' to dump the profile
+     and keep going, including a function call stack.
+
+   * You can also just "pretty print" the program. This currently also
+     runs the program, but that will change in the next major release.
+
+
 
 File: gawk.info,  Node: Internationalization,  Next: Debugger,  Prev: Advanced Features,  Up: Top
 
@@ -18841,6 +19716,7 @@ requirement.
 * Translator i18n::             Features for the translator.
 * I18N Example::                A simple i18n example.
 * Gawk I18N::                   `gawk' is also internationalized.
+* I18N Summary::                Summary of I18N stuff.
 
 
 File: gawk.info,  Node: I18N and L10N,  Next: Explaining gettext,  Up: Internationalization
@@ -18863,6 +19739,7 @@ File: gawk.info,  Node: Explaining gettext,  Next: Programmer i18n,  Prev: I18N
 13.2 GNU `gettext'
 ==================
 
+`gawk' uses GNU `gettext' to provide its internationalization features.
 The facilities in GNU `gettext' focus on messages; strings printed by a
 program, either directly or via formatting with `printf' or
 `sprintf()'.(1)
@@ -19009,7 +19886,7 @@ internationalization:
      for translation at runtime.  String constants without a leading
      underscore are not translated.
 
-`dcgettext(STRING [, DOMAIN [, CATEGORY]])'
+``dcgettext(STRING' [`,' DOMAIN [`,' CATEGORY]]`)''
      Return the translation of STRING in text domain DOMAIN for locale
      category CATEGORY.  The default value for DOMAIN is the current
      value of `TEXTDOMAIN'.  The default value for CATEGORY is
@@ -19026,7 +19903,7 @@ internationalization:
           be simple and to allow for reasonable `awk'-style default
           arguments.
 
-`dcngettext(STRING1, STRING2, NUMBER [, DOMAIN [, CATEGORY]])'
+``dcngettext(STRING1, STRING2, NUMBER' [`,' DOMAIN [`,' CATEGORY]]`)''
      Return the plural form used for NUMBER of the translation of
      STRING1 and STRING2 in text domain DOMAIN for locale category
      CATEGORY. STRING1 is the English singular variant of a message,
@@ -19037,7 +19914,7 @@ internationalization:
      The same remarks about argument order as for the `dcgettext()'
      function apply.
 
-`bindtextdomain(DIRECTORY [, DOMAIN])'
+``bindtextdomain(DIRECTORY' [`,' DOMAIN ]`)''
      Change the directory in which `gettext' looks for `.gmo' files, in
      case they will not or cannot be placed in the standard locations
      (e.g., during testing).  Return the directory in which DOMAIN is
@@ -19104,9 +19981,9 @@ File: gawk.info,  Node: Translator i18n,  Next: I18N Example,  Prev: Programmer
 ===============================
 
 Once a program's translatable strings have been marked, they must be
-extracted to create the initial `.po' file.  As part of translation, it
-is often helpful to rearrange the order in which arguments to `printf'
-are output.
+extracted to create the initial `.pot' file.  As part of translation,
+it is often helpful to rearrange the order in which arguments to
+`printf' are output.
 
    `gawk''s `--gen-pot' command-line option extracts the messages and
 is discussed next.  After that, `printf''s ability to rearrange the
@@ -19179,7 +20056,7 @@ second:
 
      $ gawk 'BEGIN {
      >     string = "Dont Panic"
-     >     printf _"%2$d characters live in \"%1$s\"\n",
+     >     printf "%2$d characters live in \"%1$s\"\n",
      >                         string, length(string)
      > }'
      -| 10 characters live in "Dont Panic"
@@ -19204,7 +20081,7 @@ precision capability:
    `gawk' does not allow you to mix regular format specifiers and those
 with positional specifiers in the same string:
 
-     $ gawk 'BEGIN { printf _"%d %3$s\n", 1, 2, "hi" }'
+     $ gawk 'BEGIN { printf "%d %3$s\n", 1, 2, "hi" }'
      error--> gawk: cmd. line:1: fatal: must use `count$' on all formats or none
 
      NOTE: There are some pathological cases that `gawk' may fail to
@@ -19342,19 +20219,20 @@ Following are the translations:
      msgstr "Like, the scoop is"
 
    The next step is to make the directory to hold the binary message
-object file and then to create the `guide.gmo' file.  The directory
+object file and then to create the `guide.mo' file.  We pretend that
+our file is to be used in the `en_US.UTF-8' locale.  The directory
 layout shown here is standard for GNU `gettext' on GNU/Linux systems.
 Other versions of `gettext' may use a different layout:
 
-     $ mkdir en_US en_US/LC_MESSAGES
+     $ mkdir en_US.UTF-8 en_US.UTF-8/LC_MESSAGES
 
    The `msgfmt' utility does the conversion from human-readable `.po'
-file to machine-readable `.gmo' file.  By default, `msgfmt' creates a
+file to machine-readable `.mo' file.  By default, `msgfmt' creates a
 file named `messages'.  This file must be renamed and placed in the
 proper directory so that `gawk' can find it:
 
      $ msgfmt guide-mellow.po
-     $ mv messages en_US/LC_MESSAGES/guide.gmo
+     $ mv messages en_US.UTF-8/LC_MESSAGES/guide.mo
 
    Finally, we run the program to test it:
 
@@ -19377,7 +20255,7 @@ and `bindtextdomain()' (*note I18N Portability::) are in a file named
    (1) Perhaps it would be better if it were called "Hippy." Ah, well.
 
 
-File: gawk.info,  Node: Gawk I18N,  Prev: I18N Example,  Up: Internationalization
+File: gawk.info,  Node: Gawk I18N,  Next: I18N Summary,  Prev: I18N Example,  Up: Internationalization
 
 13.6 `gawk' Can Speak Your Language
 ===================================
@@ -19385,13 +20263,46 @@ File: gawk.info,  Node: Gawk I18N,  Prev: I18N Example,  Up: Internationalizatio
 `gawk' itself has been internationalized using the GNU `gettext'
 package.  (GNU `gettext' is described in complete detail in *note (GNU
 `gettext' utilities)Top:: gettext, GNU gettext tools.)  As of this
-writing, the latest version of GNU `gettext' is version 0.18.2.1
-(ftp://ftp.gnu.org/gnu/gettext/gettext-0.18.2.1.tar.gz).
+writing, the latest version of GNU `gettext' is version 0.19.1
+(ftp://ftp.gnu.org/gnu/gettext/gettext-0.19.1.tar.gz).
 
    If a translation of `gawk''s messages exists, then `gawk' produces
 usage messages, warnings, and fatal errors in the local language.
 
 
+File: gawk.info,  Node: I18N Summary,  Prev: Gawk I18N,  Up: Internationalization
+
+13.7 Summary
+============
+
+   * Internationalization means writing a program such that it can use
+     multiple languages without requiring source-code changes.
+     Localization means providing the data necessary for an
+     internationalized program to work in a particular language.
+
+   * `gawk' uses GNU `gettext' to let you internationalize and localize
+     `awk' programs.  A program's text domain identifies the program
+     for grouping all messages and other data together.
+
+   * You mark a program's strings for translation by preceding them with
+     an underscore. Once that is done, the strings are extracted into a
+     `.pot' file.  This file is copied for each language into a `.po'
+     file, and the `.po' files are compiled into `.gmo' files for use
+     at runtime.
+
+   * You can use position specifications with `sprintf()' and `printf'
+     to rearrange the placement of argument values in formatted strings
+     and output. This is useful for the translations of format control
+     strings.
+
+   * The internationalization features have been designed so that they
+     can be easily worked around in a standard `awk'.
+
+   * `gawk' itself has been internationalized and ships with a number
+     of translations for its messages.
+
+
+
 File: gawk.info,  Node: Debugger,  Next: Arbitrary Precision Arithmetic,  Prev: Internationalization,  Up: Top
 
 14 Debugging `awk' Programs
@@ -19414,12 +20325,13 @@ program is easy.
 * List of Debugger Commands::   Main debugger commands.
 * Readline Support::            Readline support.
 * Limitations::                 Limitations and future plans.
+* Debugging Summary::           Debugging summary.
 
 
 File: gawk.info,  Node: Debugging,  Next: Sample Debugging Session,  Up: Debugger
 
-14.1 Introduction to `gawk' Debugger
-====================================
+14.1 Introduction to The `gawk' Debugger
+========================================
 
 This minor node introduces debugging in general and begins the
 discussion of debugging in `gawk'.
@@ -19566,7 +20478,7 @@ File: gawk.info,  Node: Debugger Invocation,  Next: Finding The Bug,  Up: Sample
 14.2.1 How to Start the Debugger
 --------------------------------
 
-Starting the debugger is almost exactly like running `awk', except you
+Starting the debugger is almost exactly like running `gawk', except you
 have to pass an additional option `--debug' or the corresponding short
 option `-D'.  The file(s) containing the program and any supporting
 code are given on the command line as arguments to one or more `-f'
@@ -19679,8 +20591,8 @@ our test input above.  Let's look at `NR':
      -| NR = number (2)
 
 So we can see that `are_equal()' was only called for the second record
-of the file.  Of course, this is because our program contained a rule
-for `NR == 1':
+of the file.  Of course, this is because our program contains a rule for
+`NR == 1':
 
      NR == 1 {
          last = $0
@@ -19705,11 +20617,7 @@ typing `n' (for "next"):
 decides whether to give the lines the special "field skipping" treatment
 indicated by the `-f' command-line option.  (Notice that we skipped
 from where we were before at line 64 to here, since the condition in
-line 64
-
-     if (fcount == 0 && charcount == 0)
-
-was false.)
+line 64 `if (fcount == 0 && charcount == 0)' was false.)
 
    Continuing to step, we now get to the splitting of the current and
 last records:
@@ -19815,7 +20723,7 @@ following descriptions, commands which may be abbreviated show the
 abbreviation on a second description line.  A debugger command name may
 also be truncated if that partial name is unambiguous. The debugger has
 the built-in capability to automatically repeat the previous command
-when just hitting <Enter>.  This works for the commands `list', `next',
+just by hitting <Enter>.  This works for the commands `list', `next',
 `nexti', `step', `stepi' and `continue' executed without any argument.
 
 * Menu:
@@ -20075,7 +20983,7 @@ AWK STATEMENTS
 `set' VAR`='VALUE
      Assign a constant (number or string) value to an `awk' variable or
      field.  String values must be enclosed between double quotes
-     (`"..."').
+     (`"'...`"').
 
      You can also set special `awk' variables, such as `FS', `NF',
      `NR', etc.
@@ -20129,11 +21037,12 @@ are:
 
 `frame' [N]
 `f' [N]
-     Select and print (frame number, function and argument names,
-     source file, and the source line) stack frame N. Frame 0 is the
-     currently executing, or "innermost", frame (function call), frame
-     1 is the frame that called the innermost one. The highest numbered
-     frame is the one for the main program.
+     Select and print stack frame N.  Frame 0 is the currently
+     executing, or "innermost", frame (function call), frame 1 is the
+     frame that called the innermost one. The highest numbered frame is
+     the one for the main program.  The printed information consists of
+     the frame number, function and argument names, source file, and
+     the source line.
 
 `up' [COUNT]
      Move COUNT (default 1) frames up the stack toward the outermost
@@ -20218,16 +21127,16 @@ from a file.  The commands are:
     `prompt'
           The debugger prompt. The default is `gawk> '.
 
-    `save_history [on | off]'
+    `save_history' [`on' | `off']
           Save command history to file `./.gawk_history'.  The default
           is `on'.
 
-    `save_options [on | off]'
+    `save_options' [`on' | `off']
           Save current options to file `./.gawkrc' upon exit.  The
           default is `on'.  Options are read back in to the next
           session upon startup.
 
-    `trace [on | off]'
+    `trace' [`on' | `off']
           Turn instruction tracing on or off. The default is `off'.
 
 `save' FILENAME
@@ -20266,7 +21175,7 @@ categories, as follows:
      Program::) demonstrates:
 
           gawk> dump
-          -| 	# BEGIN
+          -|        # BEGIN
           -|
           -| [     1:0xfcd340] Op_rule             : [in_rule = BEGIN] [source_file = brini.awk]
           -| [     1:0xfcc240] Op_push_i           : "~" [MALLOC|STRING|STRCUR]
@@ -20356,7 +21265,7 @@ categories, as follows:
      accidentally type `q' or `quit', to make sure you really want to
      quit.
 
-`trace' `on' | `off'
+`trace' [`on' | `off']
      Turn on or off a continuous printing of instructions which are
      about to be executed, along with printing the `awk' line which they
      implement.  The default is `off'.
@@ -20372,9 +21281,10 @@ File: gawk.info,  Node: Readline Support,  Next: Limitations,  Prev: List of Deb
 14.4 Readline Support
 =====================
 
-If `gawk' is compiled with the `readline' library, you can take
-advantage of that library's command completion and history expansion
-features. The following types of completion are available:
+If `gawk' is compiled with the `readline' library
+(http://cnswww.cns.cwru.edu/php/chet/readline/readline.html), you can
+take advantage of that library's command completion and history
+expansion features. The following types of completion are available:
 
 Command completion
      Command names.
@@ -20394,7 +21304,7 @@ Variable name completion
 
 
 
-File: gawk.info,  Node: Limitations,  Prev: Readline Support,  Up: Debugger
+File: gawk.info,  Node: Limitations,  Next: Debugging Summary,  Prev: Readline Support,  Up: Debugger
 
 14.5 Limitations and Future Plans
 =================================
@@ -20413,15 +21323,14 @@ some limitations.  A few which are worth being aware of are:
      you will realize that much of the internal manipulation of data in
      `gawk', as in many interpreters, is done on a stack.  `Op_push',
      `Op_pop', etc., are the "bread and butter" of most `gawk' code.
-     Unfortunately, as of now, the `gawk' debugger does not allow you
-     to examine the stack's contents.
 
-     That is, the intermediate results of expression evaluation are on
-     the stack, but cannot be printed.  Rather, only variables which
-     are defined in the program can be printed.  Of course, a
-     workaround for this is to use more explicit variables at the
-     debugging stage and then change back to obscure, perhaps more
-     optimal code later.
+     Unfortunately, as of now, the `gawk' debugger does not allow you
+     to examine the stack's contents.  That is, the intermediate
+     results of expression evaluation are on the stack, but cannot be
+     printed.  Rather, only variables which are defined in the program
+     can be printed.  Of course, a workaround for this is to use more
+     explicit variables at the debugging stage and then change back to
+     obscure, perhaps more optimal code later.
 
    * There is no way to look "inside" the process of compiling regular
      expressions to see if you got it right.  As an `awk' programmer,
@@ -20442,362 +21351,319 @@ features may be added, and of course feel free to try to add them
 yourself!
 
 
-File: gawk.info,  Node: Arbitrary Precision Arithmetic,  Next: Dynamic Extensions,  Prev: Debugger,  Up: Top
-
-15 Arithmetic and Arbitrary Precision Arithmetic with `gawk'
-************************************************************
+File: gawk.info,  Node: Debugging Summary,  Prev: Limitations,  Up: Debugger
 
-     There's a credibility gap: We don't know how much of the
-     computer's answers to believe. Novice computer users solve this
-     problem by implicitly trusting in the computer as an infallible
-     authority; they tend to believe that all digits of a printed
-     answer are significant. Disillusioned computer users have just the
-     opposite approach; they are constantly afraid that their answers
-     are almost meaningless.(1) -- Donald Knuth
+14.6 Summary
+============
 
-   This major node discusses issues that you may encounter when
-performing arithmetic.  It begins by discussing some of the general
-attributes of computer arithmetic, along with how this can influence
-what you see when running `awk' programs.  This discussion applies to
-all versions of `awk'.
+   * Programs rarely work correctly the first time.  Finding bugs is
+     "debugging" and a program that helps you find bugs is a
+     "debugger".  `gawk' has a built-in debugger that works very
+     similarly to the GNU Debugger, GDB.
 
-   The major node then moves on to describe "arbitrary precision
-arithmetic", a feature which is specific to `gawk'.
+   * Debuggers let you step through your program one statement at a
+     time, examine and change variable and array values, and do a
+     number of other things that let understand what your program is
+     actually doing (as opposed to what it is supposed to do).
 
-* Menu:
+   * Like most debuggers, the `gawk' debugger works in terms of stack
+     frames, and lets you set both breakpoints (stop at a point in the
+     code) and watchpoints (stop when a data value changes).
 
-* General Arithmetic::          An introduction to computer arithmetic.
-* Floating-point Programming::  Effective Floating-point Programming.
-* Gawk and MPFR::               How `gawk' provides
-                                arbitrary-precision arithmetic.
-* Arbitrary Precision Floats::  Arbitrary Precision Floating-point Arithmetic
-                                with `gawk'.
-* Arbitrary Precision Integers:: Arbitrary Precision Integer Arithmetic with
-                                `gawk'.
+   * The debugger command set is fairly complete, providing control over
+     breakpoints, execution, viewing and changing data, working with
+     the stack, getting information, and other tasks.
 
-   ---------- Footnotes ----------
+   * If the `readline' library is available when `gawk' is compiled, it
+     is used by the debugger to provide command-line history and
+     editing.
 
-   (1) Donald E. Knuth.  `The Art of Computer Programming'. Volume 2,
-`Seminumerical Algorithms', third edition, 1998, ISBN 0-201-89683-4, p.
-229.
 
 
-File: gawk.info,  Node: General Arithmetic,  Next: Floating-point Programming,  Up: Arbitrary Precision Arithmetic
+File: gawk.info,  Node: Arbitrary Precision Arithmetic,  Next: Dynamic Extensions,  Prev: Debugger,  Up: Top
 
-15.1 A General Description of Computer Arithmetic
-=================================================
+15 Arithmetic and Arbitrary Precision Arithmetic with `gawk'
+************************************************************
 
-Within computers, there are two kinds of numeric values: "integers" and
-"floating-point".  In school, integer values were referred to as
-"whole" numbers--that is, numbers without any fractional part, such as
-1, 42, or -17.  The advantage to integer numbers is that they represent
-values exactly.  The disadvantage is that their range is limited.  On
-most systems, this range is -2,147,483,648 to 2,147,483,647.  However,
-many systems now support a range from -9,223,372,036,854,775,808 to
-9,223,372,036,854,775,807.
-
-   Integer values come in two flavors: "signed" and "unsigned".  Signed
-values may be negative or positive, with the range of values just
-described.  Unsigned values are always positive.  On most systems, the
-range is from 0 to 4,294,967,295.  However, many systems now support a
-range from 0 to 18,446,744,073,709,551,615.
-
-   Floating-point numbers represent what are called "real" numbers;
-i.e., those that do have a fractional part, such as 3.1415927.  The
-advantage to floating-point numbers is that they can represent a much
-larger range of values.  The disadvantage is that there are numbers
-that they cannot represent exactly.  `awk' uses "double precision"
-floating-point numbers, which can hold more digits than "single
-precision" floating-point numbers.
-
-   There a several important issues to be aware of, described next.
+This major node introduces some basic concepts relating to how
+computers do arithmetic and briefly lists the features in `gawk' for
+performing arbitrary precision floating point computations.  It then
+proceeds to describe floating-point arithmetic, which is what `awk'
+uses for all its computations, including a discussion of arbitrary
+precision floating point arithmetic, which is a feature available only
+in `gawk'. It continues on to present arbitrary precision integers, and
+concludes with a description of some points where `gawk' and the POSIX
+standard are not quite in agreement.
 
 * Menu:
 
-* Floating Point Issues::       Stuff to know about floating-point numbers.
-* Integer Programming::         Effective integer programming.
+* Computer Arithmetic::           A quick intro to computer math.
+* Math Definitions::              Defining terms used.
+* MPFR features::                 The MPFR features in `gawk'.
+* FP Math Caution::               Things to know.
+* Arbitrary Precision Integers::  Arbitrary Precision Integer Arithmetic with
+                                  `gawk'.
+* POSIX Floating Point Problems:: Standards Versus Existing Practice.
+* Floating point summary::        Summary of floating point discussion.
 
 
-File: gawk.info,  Node: Floating Point Issues,  Next: Integer Programming,  Up: General Arithmetic
-
-15.1.1 Floating-Point Number Caveats
-------------------------------------
+File: gawk.info,  Node: Computer Arithmetic,  Next: Math Definitions,  Up: Arbitrary Precision Arithmetic
 
-This minor node describes some of the issues involved in using
-floating-point numbers.
+15.1 A General Description of Computer Arithmetic
+=================================================
 
-   There is a very nice paper on floating-point arithmetic
-(http://www.validlab.com/goldberg/paper.pdf) by David Goldberg, "What
-Every Computer Scientist Should Know About Floating-point Arithmetic,"
-`ACM Computing Surveys' *23*, 1 (1991-03), 5-48.  This is worth reading
-if you are interested in the details, but it does require a background
-in computer science.
+Until now, we have worked with data as either numbers or strings.
+Ultimately, however, computers represent everything in terms of "binary
+digits", or "bits".  A decimal digit can take on any of 10 values: zero
+through nine.  A binary digit can take on any of two values, zero or
+one.  Using binary, computers (and computer software) can represent and
+manipulate numerical and character data.  In general, the more bits you
+can use to represent a particular thing, the greater the range of
+possible values it can take on.
+
+   Modern computers support at least two, and often more, ways to do
+arithmetic.  Each kind of arithmetic uses a different representation
+(organization of the bits) for the numbers.  The kinds of arithmetic
+that interest us are:
+
+Decimal arithmetic
+     This is the kind of arithmetic you learned in elementary school,
+     using paper and pencil (and/or a calculator). In theory, numbers
+     can have an arbitrary number of digits on either side (or both
+     sides) of the decimal point, and the results of a computation are
+     always exact.
+
+     Some modern system can do decimal arithmetic in hardware, but
+     usually you need a special software library to provide access to
+     these instructions.  There are also libraries that do decimal
+     arithmetic entirely in software.
+
+     Despite the fact that some users expect `gawk' to be performing
+     decimal arithmetic,(1) it does not do so.
+
+Integer arithmetic
+     In school, integer values were referred to as "whole" numbers--that
+     is, numbers without any fractional part, such as 1, 42, or -17.
+     The advantage to integer numbers is that they represent values
+     exactly.  The disadvantage is that their range is limited.
+
+     In computers, integer values come in two flavors: "signed" and
+     "unsigned".  Signed values may be negative or positive, whereas
+     unsigned values are always positive (that is, greater than or equal
+     to zero).
+
+     In computer systems, integer arithmetic is exact, but the possible
+     range of values is limited.  Integer arithmetic is generally
+     faster than floating point arithmetic.
+
+Floating point arithmetic
+     Floating-point numbers represent what were called in school "real"
+     numbers; i.e., those that have a fractional part, such as
+     3.1415927.  The advantage to floating-point numbers is that they
+     can represent a much larger range of values than can integers.
+     The disadvantage is that there are numbers that they cannot
+     represent exactly.
+
+     Modern systems support floating point arithmetic in hardware, with
+     a limited range of values.  There are software libraries that allow
+     the use of arbitrary precision floating point calculations.
+
+     POSIX `awk' uses "double precision" floating-point numbers, which
+     can hold more digits than "single precision" floating-point
+     numbers.  `gawk' has facilities for performing arbitrary precision
+     floating point arithmetic, which we describe in more detail
+     shortly.
+
+   Computers work with integer and floating point values of different
+ranges. Integer values are usually either 32 or 64 bits in size.  Single
+precision floating point values occupy 32 bits, whereas double precision
+floating point values occupy 64 bits.  Floating point values are always
+signed. The possible ranges of values are shown in the following table.
+
+Numeric representation   Miniumum value           Maximum value
+--------------------------------------------------------------------------- 
+32-bit signed integer    -2,147,483,648           2,147,483,647
+32-bit unsigned integer  0                        4,294,967,295
+64-bit signed integer    -9,223,372,036,854,775,8089,223,372,036,854,775,807
+64-bit unsigned integer  0                        18,446,744,073,709,551,615
+Single precision         `1.175494e-38'           `3.402823e+38'
+floating point                                    
+(approximate)                                     
+Double precision         `2.225074e-308'          `1.797693e+308'
+floating point                                    
+(approximate)                                     
 
-* Menu:
+   ---------- Footnotes ----------
 
-* String Conversion Precision:: The String Value Can Lie.
-* Unexpected Results::          Floating Point Numbers Are Not Abstract
-                                Numbers.
-* POSIX Floating Point Problems:: Standards Versus Existing Practice.
+   (1) We don't know why they expect this, but they do.
 
 
-File: gawk.info,  Node: String Conversion Precision,  Next: Unexpected Results,  Up: Floating Point Issues
+File: gawk.info,  Node: Math Definitions,  Next: MPFR features,  Prev: Computer Arithmetic,  Up: Arbitrary Precision Arithmetic
 
-15.1.1.1 The String Value Can Lie
-.................................
+15.2 Other Stuff To Know
+========================
 
-Internally, `awk' keeps both the numeric value (double precision
-floating-point) and the string value for a variable.  Separately, `awk'
-keeps track of what type the variable has (*note Typing and
-Comparison::), which plays a role in how variables are used in
-comparisons.
+The rest of this major node uses a number of terms. Here are some
+informal definitions that should help you work your way through the
+material here.
 
-   It is important to note that the string value for a number may not
-reflect the full value (all the digits) that the numeric value actually
-contains.  The following program, `values.awk', illustrates this:
+"Accuracy"
+     A floating-point calculation's accuracy is how close it comes to
+     the real (paper and pencil) value.
 
-     {
-        sum = $1 + $2
-        # see it for what it is
-        printf("sum = %.12g\n", sum)
-        # use CONVFMT
-        a = "<" sum ">"
-        print "a =", a
-        # use OFMT
-        print "sum =", sum
-     }
-
-This program shows the full value of the sum of `$1' and `$2' using
-`printf', and then prints the string values obtained from both
-automatic conversion (via `CONVFMT') and from printing (via `OFMT').
+"Error"
+     The difference between what the result of a computation "should be"
+     and what it actually is.  It is best to minimize error as much as
+     possible.
 
-   Here is what happens when the program is run:
+"Exponent"
+     The order of magnitude of a value; some number of bits in a
+     floating-point value store the exponent.
 
-     $ echo 3.654321 1.2345678 | awk -f values.awk
-     -| sum = 4.8888888
-     -| a = <4.88889>
-     -| sum = 4.88889
+"Inf"
+     A special value representing infinity. Operations involving another
+     number and infinity produce infinity.
 
-   This makes it clear that the full numeric value is different from
-what the default string representations show.
+"NaN"
+     "Not A Number." A special value indicating a result that can't
+     happen in real math, but that can happen in floating-point
+     computations.
 
-   `CONVFMT''s default value is `"%.6g"', which yields a value with at
-most six significant digits.  For some applications, you might want to
-change it to specify more precision.  On most modern machines, most of
-the time, 17 digits is enough to capture a floating-point number's
-value exactly.(1)
+"Normalized"
+     How the significand (see later in this list) is usually stored. The
+     value is adjusted so that the first bit is one, and then that
+     leading one is assumed instead of physically stored.  This
+     provides one extra bit of precision.
 
-   ---------- Footnotes ----------
+"Precision"
+     The number of bits used to represent a floating-point number.  The
+     more bits, the more digits you can represent.  Binary and decimal
+     precisions are related approximately, according to the formula:
 
-   (1) Pathological cases can require up to 752 digits (!), but we
-doubt that you need to worry about this.
+          PREC = 3.322 * DPS
 
-
-File: gawk.info,  Node: Unexpected Results,  Next: POSIX Floating Point Problems,  Prev: String Conversion Precision,  Up: Floating Point Issues
+     Here, PREC denotes the binary precision (measured in bits) and DPS
+     (short for decimal places) is the decimal digits.
 
-15.1.1.2 Floating Point Numbers Are Not Abstract Numbers
-........................................................
+"Rounding mode"
+     How numbers are rounded up or down when necessary.  More details
+     are provided later.
 
-Unlike numbers in the abstract sense (such as what you studied in high
-school or college arithmetic), numbers stored in computers are limited
-in certain ways.  They cannot represent an infinite number of digits,
-nor can they always represent things exactly.  In particular,
-floating-point numbers cannot always represent values exactly.  Here is
-an example:
+"Significand"
+     A floating point value consists the significand multiplied by 10
+     to the power of the exponent. For example, in `1.2345e67', the
+     significand is `1.2345'.
 
-     $ awk '{ printf("%010d\n", $1 * 100) }'
-     515.79
-     -| 0000051579
-     515.80
-     -| 0000051579
-     515.81
-     -| 0000051580
-     515.82
-     -| 0000051582
-     Ctrl-d
+"Stability"
+     From the Wikipedia article on numerical stability
+     (http://en.wikipedia.org/wiki/Numerical_stability): "Calculations
+     that can be proven not to magnify approximation errors are called
+     "numerically stable"."
 
-This shows that some values can be represented exactly, whereas others
-are only approximated.  This is not a "bug" in `awk', but simply an
-artifact of how computers represent numbers.
+   See the Wikipedia article on accuracy and precision
+(http://en.wikipedia.org/wiki/Accuracy_and_precision) for more
+information on some of those terms.
 
-     NOTE: It cannot be emphasized enough that the behavior just
-     described is fundamental to modern computers. You will see this
-     kind of thing happen in _any_ programming language using hardware
-     floating-point numbers. It is _not_ a bug in `gawk', nor is it
-     something that can be "just fixed."
+   On modern systems, floating-point hardware uses the representation
+and operations defined by the IEEE 754 standard.  Three of the standard
+IEEE 754 types are 32-bit single precision, 64-bit double precision and
+128-bit quadruple precision.  The standard also specifies extended
+precision formats to allow greater precisions and larger exponent
+ranges.  (`awk' uses only the 64-bit double precision format.)
 
-   Another peculiarity of floating-point numbers on modern systems is
-that they often have more than one representation for the number zero!
-In particular, it is possible to represent "minus zero" as well as
-regular, or "positive" zero.
+   *note table-ieee-formats:: lists the precision and exponent field
+values for the basic IEEE 754 binary formats:
 
-   This example shows that negative and positive zero are distinct
-values when stored internally, but that they are in fact equal to each
-other, as well as to "regular" zero:
+Name           Total bits     Precision      emin           emax
+--------------------------------------------------------------------------- 
+Single         32             24             -126           +127
+Double         64             53             -1022          +1023
+Quadruple      128            113            -16382         +16383
 
-     $ gawk 'BEGIN { mz = -0 ; pz = 0
-     > printf "-0 = %g, +0 = %g, (-0 == +0) -> %d\n", mz, pz, mz == pz
-     > printf "mz == 0 -> %d, pz == 0 -> %d\n", mz == 0, pz == 0
-     > }'
-     -| -0 = -0, +0 = 0, (-0 == +0) -> 1
-     -| mz == 0 -> 1, pz == 0 -> 1
+Table 15.1: Basic IEEE Format Context Values
 
-   It helps to keep this in mind should you process numeric data that
-contains negative zero values; the fact that the zero is negative is
-noted and can affect comparisons.
+     NOTE: The precision numbers include the implied leading one that
+     gives them one extra bit of significand.
 
 
-File: gawk.info,  Node: POSIX Floating Point Problems,  Prev: Unexpected Results,  Up: Floating Point Issues
-
-15.1.1.3 Standards Versus Existing Practice
-...........................................
-
-Historically, `awk' has converted any non-numeric looking string to the
-numeric value zero, when required.  Furthermore, the original
-definition of the language and the original POSIX standards specified
-that `awk' only understands decimal numbers (base 10), and not octal
-(base 8) or hexadecimal numbers (base 16).
+File: gawk.info,  Node: MPFR features,  Next: FP Math Caution,  Prev: Math Definitions,  Up: Arbitrary Precision Arithmetic
 
-   Changes in the language of the 2001 and 2004 POSIX standards can be
-interpreted to imply that `awk' should support additional features.
-These features are:
+15.3 Arbitrary Precison Arithmetic Features In `gawk'
+=====================================================
 
-   * Interpretation of floating point data values specified in
-     hexadecimal notation (`0xDEADBEEF'). (Note: data values, _not_
-     source code constants.)
+By default, `gawk' uses the double precision floating point values
+supplied by the hardware of the system it runs on.  However, if it was
+compiled to do, `gawk' uses the GNU MPFR (http://www.mpfr.org) and GNU
+MP (http://gmplib.org) (GMP) libraries for arbitrary precision
+arithmetic on numbers.  You can see if MPFR support is available like
+so:
 
-   * Support for the special IEEE 754 floating point values "Not A
-     Number" (NaN), positive Infinity ("inf") and negative Infinity
-     ("-inf").  In particular, the format for these values is as
-     specified by the ISO 1999 C standard, which ignores case and can
-     allow machine-dependent additional characters after the `nan' and
-     allow either `inf' or `infinity'.
+     $ gawk --version
+     -| GNU Awk 4.1.1, API: 1.1 (GNU MPFR 3.1.0-p3, GNU MP 5.0.2)
+     -| Copyright (C) 1989, 1991-2014 Free Software Foundation.
+     ...
 
-   The first problem is that both of these are clear changes to
-historical practice:
+(You may see different version numbers than what's shown here. That's
+OK; what's important is to see that GNU MPFR and GNU MP are listed in
+the output.)
 
-   * The `gawk' maintainer feels that supporting hexadecimal floating
-     point values, in particular, is ugly, and was never intended by the
-     original designers to be part of the language.
+   Additionally, there are a few elements available in the `PROCINFO'
+array to provide information about the MPFR and GMP libraries (*note
+Auto-set::).
 
-   * Allowing completely alphabetic strings to have valid numeric
-     values is also a very severe departure from historical practice.
+   The MPFR library provides precise control over precisions and
+rounding modes, and gives correctly rounded, reproducible,
+platform-independent results.  With either of the command-line options
+`--bignum' or `-M', all floating-point arithmetic operators and numeric
+functions can yield results to any desired precision level supported by
+MPFR.
 
-   The second problem is that the `gawk' maintainer feels that this
-interpretation of the standard, which requires a certain amount of
-"language lawyering" to arrive at in the first place, was not even
-intended by the standard developers.  In other words, "we see how you
-got where you are, but we don't think that that's where you want to be."
+   Two built-in variables, `PREC' and `ROUNDMODE', provide control over
+the working precision and the rounding mode.  The precision and the
+rounding mode are set globally for every operation to follow.  *Note
+Auto-set::, for more information.
 
-   Recognizing the above issues, but attempting to provide compatibility
-with the earlier versions of the standard, the 2008 POSIX standard
-added explicit wording to allow, but not require, that `awk' support
-hexadecimal floating point values and special values for "Not A Number"
-and infinity.
+
+File: gawk.info,  Node: FP Math Caution,  Next: Arbitrary Precision Integers,  Prev: MPFR features,  Up: Arbitrary Precision Arithmetic
 
-   Although the `gawk' maintainer continues to feel that providing
-those features is inadvisable, nevertheless, on systems that support
-IEEE floating point, it seems reasonable to provide _some_ way to
-support NaN and Infinity values.  The solution implemented in `gawk' is
-as follows:
+15.4 Floating Point Arithmetic: Caveat Emptor!
+==============================================
 
-   * With the `--posix' command-line option, `gawk' becomes "hands
-     off." String values are passed directly to the system library's
-     `strtod()' function, and if it successfully returns a numeric
-     value, that is what's used.(1) By definition, the results are not
-     portable across different systems.  They are also a little
-     surprising:
+     Math class is tough!  -- Late 1980's Barbie
 
-          $ echo nanny | gawk --posix '{ print $1 + 0 }'
-          -| nan
-          $ echo 0xDeadBeef | gawk --posix '{ print $1 + 0 }'
-          -| 3735928559
+   This minor node provides a high level overview of the issues
+involved when doing lots of floating-point arithmetic.(1) The
+discussion applies to both hardware and arbitrary-precision
+floating-point arithmetic.
 
-   * Without `--posix', `gawk' interprets the four strings `+inf',
-     `-inf', `+nan', and `-nan' specially, producing the corresponding
-     special numeric values.  The leading sign acts a signal to `gawk'
-     (and the user) that the value is really numeric.  Hexadecimal
-     floating point is not supported (unless you also use
-     `--non-decimal-data', which is _not_ recommended). For example:
+     CAUTION: The material here is purposely general. If you need to do
+     serious computer arithmetic, you should do some research first,
+     and not rely just on what we tell you.
 
-          $ echo nanny | gawk '{ print $1 + 0 }'
-          -| 0
-          $ echo +nan | gawk '{ print $1 + 0 }'
-          -| nan
-          $ echo 0xDeadBeef | gawk '{ print $1 + 0 }'
-          -| 0
+* Menu:
 
-     `gawk' does ignore case in the four special values.  Thus `+nan'
-     and `+NaN' are the same.
+* Inexactness of computations:: Floating point math is not exact.
+* Getting Accuracy::            Getting more accuracy takes some work.
+* Try To Round::                Add digits and round.
+* Setting precision::           How to set the precision.
+* Setting the rounding mode::   How to set the rounding mode.
 
    ---------- Footnotes ----------
 
-   (1) You asked for it, you got it.
+   (1) There is a very nice paper on floating-point arithmetic
+(http://www.validlab.com/goldberg/paper.pdf) by David Goldberg, "What
+Every Computer Scientist Should Know About Floating-point Arithmetic,"
+`ACM Computing Surveys' *23*, 1 (1991-03), 5-48.  This is worth reading
+if you are interested in the details, but it does require a background
+in computer science.
 
 
-File: gawk.info,  Node: Integer Programming,  Prev: Floating Point Issues,  Up: General Arithmetic
-
-15.1.2 Mixing Integers And Floating-point
------------------------------------------
+File: gawk.info,  Node: Inexactness of computations,  Next: Getting Accuracy,  Up: FP Math Caution
 
-As has been mentioned already, `awk' uses hardware double precision
-with 64-bit IEEE binary floating-point representation for numbers on
-most systems. A large integer like 9,007,199,254,740,997 has a binary
-representation that, although finite, is more than 53 bits long; it
-must also be rounded to 53 bits.  The biggest integer that can be
-stored in a C `double' is usually the same as the largest possible
-value of a `double'. If your system `double' is an IEEE 64-bit
-`double', this largest possible value is an integer and can be
-represented precisely.  What more should one know about integers?
-
-   If you want to know what is the largest integer, such that it and
-all smaller integers can be stored in 64-bit doubles without losing
-precision, then the answer is 2^53.  The next representable number is
-the even number 2^53 + 2, meaning it is unlikely that you will be able
-to make `gawk' print 2^53 + 1 in integer format.  The range of integers
-exactly representable by a 64-bit double is [-2^53, 2^53].  If you ever
-see an integer outside this range in `awk' using 64-bit doubles, you
-have reason to be very suspicious about the accuracy of the output.
-Here is a simple program with erroneous output:
-
-     $ gawk 'BEGIN { i = 2^53 - 1; for (j = 0; j < 4; j++) print i + j }'
-     -| 9007199254740991
-     -| 9007199254740992
-     -| 9007199254740992
-     -| 9007199254740994
-
-   The lesson is to not assume that any large integer printed by `awk'
-represents an exact result from your computation, especially if it wraps
-around on your screen.
-
-
-File: gawk.info,  Node: Floating-point Programming,  Next: Gawk and MPFR,  Prev: General Arithmetic,  Up: Arbitrary Precision Arithmetic
-
-15.2 Understanding Floating-point Programming
-=============================================
+15.4.1 Floating Point Arithmetic Is Not Exact
+---------------------------------------------
 
-Numerical programming is an extensive area; if you need to develop
-sophisticated numerical algorithms then `gawk' may not be the ideal
-tool, and this documentation may not be sufficient.  It might require
-digesting a book or two(1) to really internalize how to compute with
-ideal accuracy and precision, and the result often depends on the
-particular application.
-
-     NOTE: A floating-point calculation's "accuracy" is how close it
-     comes to the real value.  This is as opposed to the "precision",
-     which usually refers to the number of bits used to represent the
-     number (see the Wikipedia article
-     (http://en.wikipedia.org/wiki/Accuracy_and_precision) for more
-     information).
-
-   There are two options for doing floating-point calculations:
-hardware floating-point (as used by standard `awk' and the default for
-`gawk'), and "arbitrary-precision" floating-point, which is software
-based.  From this point forward, this major node aims to provide enough
-information to understand both, and then will focus on `gawk''s
-facilities for the latter.(2)
-
-   Binary floating-point representations and arithmetic are inexact.
+Binary floating-point representations and arithmetic are inexact.
 Simple values like 0.1 cannot be precisely represented using binary
 floating-point numbers, and the limited precision of floating-point
 numbers means that slight changes in the order of operations or the
@@ -20806,9 +21672,21 @@ matters worse, with arbitrary precision floating-point, you can set the
 precision before starting a computation, but then you cannot be sure of
 the number of significant decimal places in the final result.
 
-   Sometimes, before you start to write any code, you should think more
-about what you really want and what's really happening. Consider the
-two numbers in the following example:
+* Menu:
+
+* Inexact representation::      Numbers are not exactly represented.
+* Comparing FP Values::         How to compare floating point values.
+* Errors accumulate::           Errors get bigger as they go.
+
+
+File: gawk.info,  Node: Inexact representation,  Next: Comparing FP Values,  Up: Inexactness of computations
+
+15.4.1.1 Many Numbers Cannot Be Represented Exactly
+...................................................
+
+So, before you start to write any code, you should think about what you
+really want and what's really happening. Consider the two numbers in
+the following example:
 
      x = 0.875             # 1/2 + 1/4 + 1/8
      y = 0.425
@@ -20831,20 +21709,44 @@ you can always specify how much precision you would like in your output.
 Usually this is a format string like `"%.15g"', which when used in the
 previous example, produces an output identical to the input.
 
-   Because the underlying representation can be a little bit off from
-the exact value, comparing floating-point values to see if they are
-equal is generally not a good idea.  Here is an example where it does
-not work like you expect:
+
+File: gawk.info,  Node: Comparing FP Values,  Next: Errors accumulate,  Prev: Inexact representation,  Up: Inexactness of computations
+
+15.4.1.2 Be Careful Comparing Values
+....................................
+
+Because the underlying representation can be a little bit off from the
+exact value, comparing floating-point values to see if they are exactly
+equal is generally a bad idea.  Here is an example where it does not
+work like you would expect:
 
      $ gawk 'BEGIN { print (0.1 + 12.2 == 12.3) }'
      -| 0
 
-   The loss of accuracy during a single computation with floating-point
+   The general wisdom when comparing floating-point values is to see if
+they are within some small range of each other (called a "delta", or
+"tolerance").  You have to decide how small a delta is important to
+you. Code to do this looks something like this:
+
+     delta = 0.00001                 # for example
+     difference = abs(a) - abs(b)    # subtract the two values
+     if (difference < delta)
+         # all ok
+     else
+         # not ok
+
+
+File: gawk.info,  Node: Errors accumulate,  Prev: Comparing FP Values,  Up: Inexactness of computations
+
+15.4.1.3 Errors Accumulate
+..........................
+
+The loss of accuracy during a single computation with floating-point
 numbers usually isn't enough to worry about. However, if you compute a
 value which is the result of a sequence of floating point operations,
 the error can accumulate and greatly affect the computation itself.
-Here is an attempt to compute the value of the constant pi using one of
-its many series representations:
+Here is an attempt to compute the value of pi using one of its many
+series representations:
 
      BEGIN {
          x = 1.0 / sqrt(3.0)
@@ -20856,9 +21758,9 @@ its many series representations:
          }
      }
 
-   When run, the early errors propagating through later computations
-cause the loop to terminate prematurely after an attempt to divide by
-zero.
+   When run, the early errors propagate through later computations,
+causing the loop to terminate prematurely after attempting to divide by
+zero:
 
      $ gawk -f pi.awk
      -| 3.215390309173475
@@ -20881,166 +21783,176 @@ representations yield an unexpected result:
      > }'
      -| 4
 
-   Can computation using arbitrary precision help with the previous
-examples?  If you are impatient to know, see *note Exact Arithmetic::.
+
+File: gawk.info,  Node: Getting Accuracy,  Next: Try To Round,  Prev: Inexactness of computations,  Up: FP Math Caution
 
-   Instead of arbitrary precision floating-point arithmetic, often all
-you need is an adjustment of your logic or a different order for the
-operations in your calculation.  The stability and the accuracy of the
-computation of the constant pi in the earlier example can be enhanced
-by using the following simple algebraic transformation:
+15.4.2 Getting The Accuracy You Need
+------------------------------------
 
-     (sqrt(x * x + 1) - 1) / x = x / (sqrt(x * x + 1) + 1)
+Can arbitrary precision arithmetic give exact results? There are no
+easy answers. The standard rules of algebra often do not apply when
+using floating-point arithmetic.  Among other things, the distributive
+and associative laws do not hold completely, and order of operation may
+be important for your computation. Rounding error, cumulative precision
+loss and underflow are often troublesome.
 
-After making this, change the program does converge to pi in under 30
-iterations:
+   When `gawk' tests the expressions `0.1 + 12.2' and `12.3' for
+equality using the machine double precision arithmetic, it decides that
+they are not equal!  (*Note Comparing FP Values::.)  You can get the
+result you want by increasing the precision; 56 bits in this case does
+the job:
 
-     $ gawk -f pi2.awk
-     -| 3.215390309173473
-     -| 3.159659942097501
-     -| 3.146086215131436
-     -| 3.142714599645370
-     -| 3.141873049979825
-     ...
-     -| 3.141592653589797
-     -| 3.141592653589797
+     $ gawk -M -v PREC=56 'BEGIN { print (0.1 + 12.2 == 12.3) }'
+     -| 1
 
-   There is no need to be unduly suspicious about the results from
-floating-point arithmetic. The lesson to remember is that
-floating-point arithmetic is always more complex than arithmetic using
-pencil and paper. In order to take advantage of the power of computer
-floating-point, you need to know its limitations and work within them.
-For most casual use of floating-point arithmetic, you will often get
-the expected result in the end if you simply round the display of your
-final results to the correct number of significant decimal digits.
+   If adding more bits is good, perhaps adding even more bits of
+precision is better?  Here is what happens if we use an even larger
+value of `PREC':
 
-   As general advice, avoid presenting numerical data in a manner that
-implies better precision than is actually the case.
+     $ gawk -M -v PREC=201 'BEGIN { print (0.1 + 12.2 == 12.3) }'
+     -| 0
 
-* Menu:
+   This is not a bug in `gawk' or in the MPFR library.  It is easy to
+forget that the finite number of bits used to store the value is often
+just an approximation after proper rounding.  The test for equality
+succeeds if and only if _all_ bits in the two operands are exactly the
+same. Since this is not necessarily true after floating-point
+computations with a particular precision and effective rounding rule, a
+straight test for equality may not work. Instead, compare the two
+numbers to see if they are within the desirable delta of each other.
 
-* Floating-point Representation:: Binary floating-point representation.
-* Floating-point Context::        Floating-point context.
-* Rounding Mode::                 Floating-point rounding mode.
+   In applications where 15 or fewer decimal places suffice, hardware
+double precision arithmetic can be adequate, and is usually much faster.
+But you need to keep in mind that every floating-point operation can
+suffer a new rounding error with catastrophic consequences as
+illustrated by our earlier attempt to compute the value of pi.  Extra
+precision can greatly enhance the stability and the accuracy of your
+computation in such cases.
 
-   ---------- Footnotes ----------
+   Repeated addition is not necessarily equivalent to multiplication in
+floating-point arithmetic. In the example in *note Errors accumulate:::
 
-   (1) One recommended title is `Numerical Computing with IEEE Floating
-Point Arithmetic', Michael L.  Overton, Society for Industrial and
-Applied Mathematics, 2004.  ISBN: 0-89871-482-6, ISBN-13:
-978-0-89871-482-1. See `http://www.cs.nyu.edu/cs/faculty/overton/book'.
+     $ gawk 'BEGIN {
+     >   for (d = 1.1; d <= 1.5; d += 0.1)    # loop five times (?)
+     >       i++
+     >   print i
+     > }'
+     -| 4
 
-   (2) If you are interested in other tools that perform arbitrary
-precision arithmetic, you may want to investigate the POSIX `bc' tool.
-See the POSIX specification for it
-(http://pubs.opengroup.org/onlinepubs/009695399/utilities/bc.html), for
-more information.
+you may or may not succeed in getting the correct result by choosing an
+arbitrarily large value for `PREC'. Reformulation of the problem at
+hand is often the correct approach in such situations.
 
 
-File: gawk.info,  Node: Floating-point Representation,  Next: Floating-point Context,  Up: Floating-point Programming
-
-15.2.1 Binary Floating-point Representation
--------------------------------------------
-
-Although floating-point representations vary from machine to machine,
-the most commonly encountered representation is that defined by the
-IEEE 754 Standard. An IEEE-754 format value has three components:
+File: gawk.info,  Node: Try To Round,  Next: Setting precision,  Prev: Getting Accuracy,  Up: FP Math Caution
 
-   * A sign bit telling whether the number is positive or negative.
+15.4.3 Try A Few Extra Bits of Precision and Rounding
+-----------------------------------------------------
 
-   * An "exponent", E, giving its order of magnitude.
+Instead of arbitrary precision floating-point arithmetic, often all you
+need is an adjustment of your logic or a different order for the
+operations in your calculation.  The stability and the accuracy of the
+computation of pi in the earlier example can be enhanced by using the
+following simple algebraic transformation:
 
-   * A "significand", S, specifying the actual digits of the number.
+     (sqrt(x * x + 1) - 1) / x == x / (sqrt(x * x + 1) + 1)
 
-   The value of the number is then S * 2^E.  The first bit of a
-non-zero binary significand is always one, so the significand in an
-IEEE-754 format only includes the fractional part, leaving the leading
-one implicit.  The significand is stored in "normalized" format, which
-means that the first bit is always a one.
+After making this, change the program converges to pi in under 30
+iterations:
 
-   Three of the standard IEEE-754 types are 32-bit single precision,
-64-bit double precision and 128-bit quadruple precision.  The standard
-also specifies extended precision formats to allow greater precisions
-and larger exponent ranges.
+     $ gawk -f pi2.awk
+     -| 3.215390309173473
+     -| 3.159659942097501
+     -| 3.146086215131436
+     -| 3.142714599645370
+     -| 3.141873049979825
+     ...
+     -| 3.141592653589797
+     -| 3.141592653589797
 
 
-File: gawk.info,  Node: Floating-point Context,  Next: Rounding Mode,  Prev: Floating-point Representation,  Up: Floating-point Programming
-
-15.2.2 Floating-point Context
------------------------------
-
-A floating-point "context" defines the environment for arithmetic
-operations.  It governs precision, sets rules for rounding, and limits
-the range for exponents.  The context has the following primary
-components:
-
-"Precision"
-     Precision of the floating-point format in bits.
+File: gawk.info,  Node: Setting precision,  Next: Setting the rounding mode,  Prev: Try To Round,  Up: FP Math Caution
 
-"emax"
-     Maximum exponent allowed for the format.
-
-"emin"
-     Minimum exponent allowed for the format.
-
-"Underflow behavior"
-     The format may or may not support gradual underflow.
+15.4.4 Setting The Precision
+----------------------------
 
-"Rounding"
-     The rounding mode of the context.
+`gawk' uses a global working precision; it does not keep track of the
+precision or accuracy of individual numbers. Performing an arithmetic
+operation or calling a built-in function rounds the result to the
+current working precision. The default working precision is 53 bits,
+which you can modify using the built-in variable `PREC'. You can also
+set the value to one of the predefined case-insensitive strings shown
+in *note table-predefined-precision-strings::, to emulate an IEEE 754
+binary format.
 
-   *note table-ieee-formats:: lists the precision and exponent field
-values for the basic IEEE-754 binary formats:
+`PREC'       IEEE 754 Binary Format
+--------------------------------------------------- 
+`"half"'     16-bit half-precision.
+`"single"'   Basic 32-bit single precision.
+`"double"'   Basic 64-bit double precision.
+`"quad"'     Basic 128-bit quadruple precision.
+`"oct"'      256-bit octuple precision.
 
-Name           Total bits     Precision      emin           emax
---------------------------------------------------------------------------- 
-Single         32             24             -126           +127
-Double         64             53             -1022          +1023
-Quadruple      128            113            -16382         +16383
+Table 15.2: Predefined Precision Strings For `PREC'
 
-Table 15.1: Basic IEEE Format Context Values
-
-     NOTE: The precision numbers include the implied leading one that
-     gives them one extra bit of significand.
+   The following example illustrates the effects of changing precision
+on arithmetic operations:
 
-   A floating-point context can also determine which signals are treated
-as exceptions, and can set rules for arithmetic with special values.
-Please consult the IEEE-754 standard or other resources for details.
+     $ gawk -M -v PREC=100 'BEGIN { x = 1.0e-400; print x + 0
+     >   PREC = "double"; print x + 0 }'
+     -| 1e-400
+     -| 0
 
-   `gawk' ordinarily uses the hardware double precision representation
-for numbers.  On most systems, this is IEEE-754 floating-point format,
-corresponding to 64-bit binary with 53 bits of precision.
+     CAUTION: Be wary of floating-point constants! When reading a
+     floating-point constant from program source code, `gawk' uses the
+     default precision (that of a C `double'), unless overridden by an
+     assignment to the special variable `PREC' on the command line, to
+     store it internally as a MPFR number.  Changing the precision
+     using `PREC' in the program text does _not_ change the precision
+     of a constant.
+
+     If you need to represent a floating-point constant at a higher
+     precision than the default and cannot use a command line
+     assignment to `PREC', you should either specify the constant as a
+     string, or as a rational number, whenever possible. The following
+     example illustrates the differences among various ways to print a
+     floating-point constant:
 
-     NOTE: In case an underflow occurs, the standard allows, but does
-     not require, the result from an arithmetic operation to be a
-     number smaller than the smallest nonzero normalized number. Such
-     numbers do not have as many significant digits as normal numbers,
-     and are called "denormals" or "subnormals". The alternative,
-     simply returning a zero, is called "flush to zero". The basic
-     IEEE-754 binary formats support subnormal numbers.
+     $ gawk -M 'BEGIN { PREC = 113; printf("%0.25f\n", 0.1) }'
+     -| 0.1000000000000000055511151
+     $ gawk -M -v PREC=113 'BEGIN { printf("%0.25f\n", 0.1) }'
+     -| 0.1000000000000000000000000
+     $ gawk -M 'BEGIN { PREC = 113; printf("%0.25f\n", "0.1") }'
+     -| 0.1000000000000000000000000
+     $ gawk -M 'BEGIN { PREC = 113; printf("%0.25f\n", 1/10) }'
+     -| 0.1000000000000000000000000
 
 
-File: gawk.info,  Node: Rounding Mode,  Prev: Floating-point Context,  Up: Floating-point Programming
+File: gawk.info,  Node: Setting the rounding mode,  Prev: Setting precision,  Up: FP Math Caution
 
-15.2.3 Floating-point Rounding Mode
------------------------------------
+15.4.5 Setting The Rounding Mode
+--------------------------------
 
-The "rounding mode" specifies the behavior for the results of numerical
-operations when discarding extra precision. Each rounding mode indicates
-how the least significant returned digit of a rounded result is to be
-calculated.  *note table-rounding-modes:: lists the IEEE-754 defined
-rounding modes:
+The `ROUNDMODE' variable provides program level control over the
+rounding mode.  The correspondence between `ROUNDMODE' and the IEEE
+rounding modes is shown in *note table-gawk-rounding-modes::.
 
-Rounding Mode                    IEEE Name
--------------------------------------------------------------------------- 
-Round to nearest, ties to even   `roundTiesToEven'
-Round toward plus Infinity       `roundTowardPositive'
-Round toward negative Infinity   `roundTowardNegative'
-Round toward zero                `roundTowardZero'
-Round to nearest, ties away      `roundTiesToAway'
-from zero                        
+Rounding Mode                    IEEE Name              `ROUNDMODE'
+--------------------------------------------------------------------------- 
+Round to nearest, ties to even   `roundTiesToEven'      `"N"' or `"n"'
+Round toward plus Infinity       `roundTowardPositive'  `"U"' or `"u"'
+Round toward negative Infinity   `roundTowardNegative'  `"D"' or `"d"'
+Round toward zero                `roundTowardZero'      `"Z"' or `"z"'
+Round to nearest, ties away      `roundTiesToAway'      `"A"' or `"a"'
+from zero                                               
 
-Table 15.2: IEEE 754 Rounding Modes
+Table 15.3: `gawk' Rounding Modes
+
+   `ROUNDMODE' has the default value `"N"', which selects the IEEE 754
+rounding mode `roundTiesToEven'.  In *note Table 15.3:
+table-gawk-rounding-modes, the value `"A"' selects `roundTiesToAway'.
+This is only available if your version of the MPFR library supports it;
+otherwise setting `ROUNDMODE' to `"A"' has no effect.
 
    The default mode `roundTiesToEven' is the most preferred, but the
 least intuitive. This method does the obvious thing for most values, by
@@ -21075,20 +21987,19 @@ produces the following output when run on the author's system:(1)
       3.5 => 4
       4.5 => 4
 
-   The theory behind the rounding mode `roundTiesToEven' is that it
-more or less evenly distributes upward and downward rounds of exact
-halves, which might cause any round-off error to cancel itself out.
-This is the default rounding mode used in IEEE-754 computing functions
-and operators.
+   The theory behind `roundTiesToEven' is that it more or less evenly
+distributes upward and downward rounds of exact halves, which might
+cause any accumulating round-off error to cancel itself out. This is the
+default rounding mode for IEEE 754 computing functions and operators.
 
    The other rounding modes are rarely used.  Round toward positive
 infinity (`roundTowardPositive') and round toward negative infinity
-(`roundTowardNegative') are often used to implement interval arithmetic,
-where you adjust the rounding mode to calculate upper and lower bounds
-for the range of output. The `roundTowardZero' mode can be used for
-converting floating-point numbers to integers.  The rounding mode
-`roundTiesToAway' rounds the result to the nearest number and selects
-the number with the larger magnitude if a tie occurs.
+(`roundTowardNegative') are often used to implement interval
+arithmetic, where you adjust the rounding mode to calculate upper and
+lower bounds for the range of output. The `roundTowardZero' mode can be
+used for converting floating-point numbers to integers.  The rounding
+mode `roundTiesToAway' rounds the result to the nearest number and
+selects the number with the larger magnitude if a tie occurs.
 
    Some numerical analysts will tell you that your choice of rounding
 style has tremendous impact on the final outcome, and advise you to
@@ -21097,414 +22008,232 @@ round-off error problems by setting the precision initially to some
 value sufficiently larger than the final desired precision, so that the
 accumulation of round-off error does not influence the outcome.  If you
 suspect that results from your computation are sensitive to
-accumulation of round-off error, one way to be sure is to look for a
-significant difference in output when you change the rounding mode.
+accumulation of round-off error, look for a significant difference in
+output when you change the rounding mode to be sure.
 
    ---------- Footnotes ----------
 
    (1) It is possible for the output to be completely different if the
-C library in your system does not use the IEEE-754 even-rounding rule
+C library in your system does not use the IEEE 754 even-rounding rule
 to round halfway cases for `printf'.
 
 
-File: gawk.info,  Node: Gawk and MPFR,  Next: Arbitrary Precision Floats,  Prev: Floating-point Programming,  Up: Arbitrary Precision Arithmetic
-
-15.3 `gawk' + MPFR = Powerful Arithmetic
-========================================
+File: gawk.info,  Node: Arbitrary Precision Integers,  Next: POSIX Floating Point Problems,  Prev: FP Math Caution,  Up: Arbitrary Precision Arithmetic
 
-The rest of this major node describes how to use the arbitrary precision
-(also known as "multiple precision" or "infinite precision") numeric
-capabilities in `gawk' to produce maximally accurate results when you
-need it.
-
-   But first you should check if your version of `gawk' supports
-arbitrary precision arithmetic.  The easiest way to find out is to look
-at the output of the following command:
-
-     $ gawk --version
-     -| GNU Awk 4.1.0, API: 1.0 (GNU MPFR 3.1.0-p3, GNU MP 5.0.2)
-     -| Copyright (C) 1989, 1991-2013 Free Software Foundation.
-     ...
-
-   `gawk' uses the GNU MPFR (http://www.mpfr.org) and GNU MP
-(http://gmplib.org) (GMP) libraries for arbitrary precision arithmetic
-on numbers. So if you do not see the names of these libraries in the
-output, then your version of `gawk' does not support arbitrary
-precision arithmetic.
-
-   Additionally, there are a few elements available in the `PROCINFO'
-array to provide information about the MPFR and GMP libraries.  *Note
-Auto-set::, for more information.
-
-
-File: gawk.info,  Node: Arbitrary Precision Floats,  Next: Arbitrary Precision Integers,  Prev: Gawk and MPFR,  Up: Arbitrary Precision Arithmetic
-
-15.4 Arbitrary Precision Floating-point Arithmetic with `gawk'
-==============================================================
-
-`gawk' uses the GNU MPFR library for arbitrary precision floating-point
-arithmetic.  The MPFR library provides precise control over precisions
-and rounding modes, and gives correctly rounded, reproducible,
-platform-independent results.  With one of the command-line options
-`--bignum' or `-M', all floating-point arithmetic operators and numeric
-functions can yield results to any desired precision level supported by
-MPFR.  Two built-in variables, `PREC' and `ROUNDMODE', provide control
-over the working precision and the rounding mode (*note Setting
-Precision::, and *note Setting Rounding Mode::).  The precision and the
-rounding mode are set globally for every operation to follow.
-
-   The default working precision for arbitrary precision floating-point
-values is 53 bits, and the default value for `ROUNDMODE' is `"N"',
-which selects the IEEE-754 `roundTiesToEven' rounding mode (*note
-Rounding Mode::).(1) `gawk' uses the default exponent range in MPFR
-(EMAX = 2^30 - 1, EMIN = -EMAX) for all floating-point contexts.  There
-is no explicit mechanism to adjust the exponent range.  MPFR does not
-implement subnormal numbers by default, and this behavior cannot be
-changed in `gawk'.
-
-     NOTE: When emulating an IEEE-754 format (*note Setting
-     Precision::), `gawk' internally adjusts the exponent range to the
-     value defined for the format and also performs computations needed
-     for gradual underflow (subnormal numbers).
-
-     NOTE: MPFR numbers are variable-size entities, consuming only as
-     much space as needed to store the significant digits. Since the
-     performance using MPFR numbers pales in comparison to doing
-     arithmetic using the underlying machine types, you should consider
-     using only as much precision as needed by your program.
+15.5 Arbitrary Precision Integer Arithmetic with `gawk'
+=======================================================
 
-* Menu:
+When given one of the options `--bignum' or `-M', `gawk' performs all
+integer arithmetic using GMP arbitrary precision integers.  Any number
+that looks like an integer in a source or data file is stored as an
+arbitrary precision integer.  The size of the integer is limited only
+by the available memory.  For example, the following computes 5^4^3^2,
+the result of which is beyond the limits of ordinary hardware
+double-precision floating point values:
 
-* Setting Precision::           Setting the working precision.
-* Setting Rounding Mode::       Setting the rounding mode.
-* Floating-point Constants::    Representing floating-point constants.
-* Changing Precision::          Changing the precision of a number.
-* Exact Arithmetic::            Exact arithmetic with floating-point numbers.
+     $ gawk -M 'BEGIN {
+     >   x = 5^4^3^2
+     >   print "# of digits =", length(x)
+     >   print substr(x, 1, 20), "...", substr(x, length(x) - 19, 20)
+     > }'
+     -| # of digits = 183231
+     -| 62060698786608744707 ... 92256259918212890625
 
-   ---------- Footnotes ----------
+   If instead you were to compute the same value using arbitrary
+precision floating-point values, the precision needed for correct
+output (using the formula `prec = 3.322 * dps'), would be 3.322 x
+183231, or 608693.
 
-   (1) The default precision is 53 bits, since according to the MPFR
-documentation, the library should be able to exactly reproduce all
-computations with double-precision machine floating-point numbers
-(`double' type in C), except the default exponent range is much wider
-and subnormal numbers are not implemented.
+   The result from an arithmetic operation with an integer and a
+floating-point value is a floating-point value with a precision equal
+to the working precision.  The following program calculates the eighth
+term in Sylvester's sequence(1) using a recurrence:
 
-
-File: gawk.info,  Node: Setting Precision,  Next: Setting Rounding Mode,  Up: Arbitrary Precision Floats
+     $ gawk -M 'BEGIN {
+     >   s = 2.0
+     >   for (i = 1; i <= 7; i++)
+     >       s = s * (s - 1) + 1
+     >   print s
+     > }'
+     -| 113423713055421845118910464
 
-15.4.1 Setting the Working Precision
-------------------------------------
+   The output differs from the actual number,
+113,423,713,055,421,844,361,000,443, because the default precision of
+53 bits is not enough to represent the floating-point results exactly.
+You can either increase the precision (100 bits is enough in this
+case), or replace the floating-point constant `2.0' with an integer, to
+perform all computations using integer arithmetic to get the correct
+output.
 
-`gawk' uses a global working precision; it does not keep track of the
-precision or accuracy of individual numbers. Performing an arithmetic
-operation or calling a built-in function rounds the result to the
-current working precision. The default working precision is 53 bits,
-which can be modified using the built-in variable `PREC'. You can also
-set the value to one of the pre-defined case-insensitive strings shown
-in *note table-predefined-precision-strings::, to emulate an IEEE-754
-binary format.
+   Sometimes `gawk' must implicitly convert an arbitrary precision
+integer into an arbitrary precision floating-point value.  This is
+primarily because the MPFR library does not always provide the relevant
+interface to process arbitrary precision integers or mixed-mode numbers
+as needed by an operation or function.  In such a case, the precision is
+set to the minimum value necessary for exact conversion, and the working
+precision is not used for this purpose.  If this is not what you need or
+want, you can employ a subterfuge, and convert the integer to floating
+point first, like this:
 
-`PREC'       IEEE-754 Binary Format
---------------------------------------------------- 
-`"half"'     16-bit half-precision.
-`"single"'   Basic 32-bit single precision.
-`"double"'   Basic 64-bit double precision.
-`"quad"'     Basic 128-bit quadruple precision.
-`"oct"'      256-bit octuple precision.
+     gawk -M 'BEGIN { n = 13; print (n + 0.0) % 2.0 }'
 
-Table 15.3: Predefined precision strings for `PREC'
+   You can avoid this issue altogether by specifying the number as a
+floating-point value to begin with:
 
-   The following example illustrates the effects of changing precision
-on arithmetic operations:
+     gawk -M 'BEGIN { n = 13.0; print n % 2.0 }'
 
-     $ gawk -M -v PREC=100 'BEGIN { x = 1.0e-400; print x + 0
-     >   PREC = "double"; print x + 0 }'
-     -| 1e-400
-     -| 0
+   Note that for the particular example above, it is likely best to
+just use the following:
 
-   Binary and decimal precisions are related approximately, according
-to the formula:
-
-   PREC = 3.322 * DPS
-
-Here, PREC denotes the binary precision (measured in bits) and DPS
-(short for decimal places) is the decimal digits. We can easily
-calculate how many decimal digits the 53-bit significand of an IEEE
-double is equivalent to: 53 / 3.322 which is equal to about 15.95.  But
-what does 15.95 digits actually mean? It depends whether you are
-concerned about how many digits you can rely on, or how many digits you
-need.
-
-   It is important to know how many bits it takes to uniquely identify
-a double-precision value (the C type `double').  If you want to convert
-from `double' to decimal and back to `double' (e.g., saving a `double'
-representing an intermediate result to a file, and later reading it
-back to restart the computation), then a few more decimal digits are
-required. 17 digits is generally enough for a `double'.
-
-   It can also be important to know what decimal numbers can be uniquely
-represented with a `double'. If you want to convert from decimal to
-`double' and back again, 15 digits is the most that you can get. Stated
-differently, you should not present the numbers from your
-floating-point computations with more than 15 significant digits in
-them.
+     gawk -M 'BEGIN { n = 13; print n % 2 }'
 
-   Conversely, it takes a precision of 332 bits to hold an approximation
-of the constant pi that is accurate to 100 decimal places.
+   ---------- Footnotes ----------
 
-   You should always add some extra bits in order to avoid the
-confusing round-off issues that occur because numbers are stored
-internally in binary.
+   (1) Weisstein, Eric W.  `Sylvester's Sequence'. From MathWorld--A
+Wolfram Web Resource
+(`http://mathworld.wolfram.com/SylvestersSequence.html').
 
 
-File: gawk.info,  Node: Setting Rounding Mode,  Next: Floating-point Constants,  Prev: Setting Precision,  Up: Arbitrary Precision Floats
-
-15.4.2 Setting the Rounding Mode
---------------------------------
+File: gawk.info,  Node: POSIX Floating Point Problems,  Next: Floating point summary,  Prev: Arbitrary Precision Integers,  Up: Arbitrary Precision Arithmetic
 
-The `ROUNDMODE' variable provides program level control over the
-rounding mode.  The correspondence between `ROUNDMODE' and the IEEE
-rounding modes is shown in *note table-gawk-rounding-modes::.
+15.6 Standards Versus Existing Practice
+=======================================
 
-Rounding Mode                    IEEE Name              `ROUNDMODE'
---------------------------------------------------------------------------- 
-Round to nearest, ties to even   `roundTiesToEven'      `"N"' or `"n"'
-Round toward plus Infinity       `roundTowardPositive'  `"U"' or `"u"'
-Round toward negative Infinity   `roundTowardNegative'  `"D"' or `"d"'
-Round toward zero                `roundTowardZero'      `"Z"' or `"z"'
-Round to nearest, ties away      `roundTiesToAway'      `"A"' or `"a"'
-from zero                                               
+Historically, `awk' has converted any non-numeric looking string to the
+numeric value zero, when required.  Furthermore, the original
+definition of the language and the original POSIX standards specified
+that `awk' only understands decimal numbers (base 10), and not octal
+(base 8) or hexadecimal numbers (base 16).
 
-Table 15.4: `gawk' Rounding Modes
+   Changes in the language of the 2001 and 2004 POSIX standards can be
+interpreted to imply that `awk' should support additional features.
+These features are:
 
-   `ROUNDMODE' has the default value `"N"', which selects the IEEE-754
-rounding mode `roundTiesToEven'.  In *note Table 15.4:
-table-gawk-rounding-modes, `"A"' is listed to select the IEEE-754 mode
-`roundTiesToAway'.  This is only available if your version of the MPFR
-library supports it; otherwise setting `ROUNDMODE' to this value has no
-effect. *Note Rounding Mode::, for the meanings of the various rounding
-modes.
+   * Interpretation of floating point data values specified in
+     hexadecimal notation (e.g., `0xDEADBEEF'). (Note: data values,
+     _not_ source code constants.)
 
-   Here is an example of how to change the default rounding behavior of
-`printf''s output:
+   * Support for the special IEEE 754 floating point values "Not A
+     Number" (NaN), positive Infinity ("inf") and negative Infinity
+     ("-inf").  In particular, the format for these values is as
+     specified by the ISO 1999 C standard, which ignores case and can
+     allow implementation-dependent additional characters after the
+     `nan' and allow either `inf' or `infinity'.
 
-     $ gawk -M -v ROUNDMODE="Z" 'BEGIN { printf("%.2f\n", 1.378) }'
-     -| 1.37
+   The first problem is that both of these are clear changes to
+historical practice:
 
-
-File: gawk.info,  Node: Floating-point Constants,  Next: Changing Precision,  Prev: Setting Rounding Mode,  Up: Arbitrary Precision Floats
+   * The `gawk' maintainer feels that supporting hexadecimal floating
+     point values, in particular, is ugly, and was never intended by the
+     original designers to be part of the language.
 
-15.4.3 Representing Floating-point Constants
---------------------------------------------
+   * Allowing completely alphabetic strings to have valid numeric
+     values is also a very severe departure from historical practice.
 
-Be wary of floating-point constants! When reading a floating-point
-constant from program source code, `gawk' uses the default precision,
-unless overridden by an assignment to the special variable `PREC' on
-the command line, to store it internally as a MPFR number.  Changing
-the precision using `PREC' in the program text does _not_ change the
-precision of a constant. If you need to represent a floating-point
-constant at a higher precision than the default and cannot use a
-command line assignment to `PREC', you should either specify the
-constant as a string, or as a rational number, whenever possible. The
-following example illustrates the differences among various ways to
-print a floating-point constant:
+   The second problem is that the `gawk' maintainer feels that this
+interpretation of the standard, which requires a certain amount of
+"language lawyering" to arrive at in the first place, was not even
+intended by the standard developers.  In other words, "we see how you
+got where you are, but we don't think that that's where you want to be."
 
-     $ gawk -M 'BEGIN { PREC = 113; printf("%0.25f\n", 0.1) }'
-     -| 0.1000000000000000055511151
-     $ gawk -M -v PREC=113 'BEGIN { printf("%0.25f\n", 0.1) }'
-     -| 0.1000000000000000000000000
-     $ gawk -M 'BEGIN { PREC = 113; printf("%0.25f\n", "0.1") }'
-     -| 0.1000000000000000000000000
-     $ gawk -M 'BEGIN { PREC = 113; printf("%0.25f\n", 1/10) }'
-     -| 0.1000000000000000000000000
+   Recognizing the above issues, but attempting to provide compatibility
+with the earlier versions of the standard, the 2008 POSIX standard
+added explicit wording to allow, but not require, that `awk' support
+hexadecimal floating point values and special values for "Not A Number"
+and infinity.
 
-   In the first case, the number is stored with the default precision
-of 53 bits.
+   Although the `gawk' maintainer continues to feel that providing
+those features is inadvisable, nevertheless, on systems that support
+IEEE floating point, it seems reasonable to provide _some_ way to
+support NaN and Infinity values.  The solution implemented in `gawk' is
+as follows:
 
-
-File: gawk.info,  Node: Changing Precision,  Next: Exact Arithmetic,  Prev: Floating-point Constants,  Up: Arbitrary Precision Floats
+   * With the `--posix' command-line option, `gawk' becomes "hands
+     off." String values are passed directly to the system library's
+     `strtod()' function, and if it successfully returns a numeric
+     value, that is what's used.(1) By definition, the results are not
+     portable across different systems.  They are also a little
+     surprising:
 
-15.4.4 Changing the Precision of a Number
------------------------------------------
+          $ echo nanny | gawk --posix '{ print $1 + 0 }'
+          -| nan
+          $ echo 0xDeadBeef | gawk --posix '{ print $1 + 0 }'
+          -| 3735928559
 
-     The point is that in any variable-precision package, a decision is
-     made on how to treat numbers given as data, or arising in
-     intermediate results, which are represented in floating-point
-     format to a precision lower than working precision.  Do we promote
-     them to full membership of the high-precision club, or do we treat
-     them and all their associates as second-class citizens?  Sometimes
-     the first course is proper, sometimes the second, and it takes
-     careful analysis to tell which.(1) -- Dirk Laurie
-
-   `gawk' does not implicitly modify the precision of any previously
-computed results when the working precision is changed with an
-assignment to `PREC'.  The precision of a number is always the one that
-was used at the time of its creation, and there is no way for the user
-to explicitly change it afterwards. However, since the result of a
-floating-point arithmetic operation is always an arbitrary precision
-floating-point value--with a precision set by the value of `PREC'--one
-of the following workarounds effectively accomplishes the desired
-behavior:
-
-     x = x + 0.0
+   * Without `--posix', `gawk' interprets the four strings `+inf',
+     `-inf', `+nan', and `-nan' specially, producing the corresponding
+     special numeric values.  The leading sign acts a signal to `gawk'
+     (and the user) that the value is really numeric.  Hexadecimal
+     floating point is not supported (unless you also use
+     `--non-decimal-data', which is _not_ recommended). For example:
 
-or:
+          $ echo nanny | gawk '{ print $1 + 0 }'
+          -| 0
+          $ echo +nan | gawk '{ print $1 + 0 }'
+          -| nan
+          $ echo 0xDeadBeef | gawk '{ print $1 + 0 }'
+          -| 0
 
-     x += 0.0
+     `gawk' ignores case in the four special values.  Thus `+nan' and
+     `+NaN' are the same.
 
    ---------- Footnotes ----------
 
-   (1) Dirk Laurie.  `Variable-precision Arithmetic Considered Perilous
--- A Detective Story'.  Electronic Transactions on Numerical Analysis.
-Volume 28, pp. 168-173, 2008.
-
-
-File: gawk.info,  Node: Exact Arithmetic,  Prev: Changing Precision,  Up: Arbitrary Precision Floats
-
-15.4.5 Exact Arithmetic with Floating-point Numbers
----------------------------------------------------
-
-     CAUTION: Never depend on the exactness of floating-point
-     arithmetic, even for apparently simple expressions!
-
-   Can arbitrary precision arithmetic give exact results? There are no
-easy answers. The standard rules of algebra often do not apply when
-using floating-point arithmetic.  Among other things, the distributive
-and associative laws do not hold completely, and order of operation may
-be important for your computation. Rounding error, cumulative precision
-loss and underflow are often troublesome.
-
-   When `gawk' tests the expressions `0.1 + 12.2' and `12.3' for
-equality using the machine double precision arithmetic, it decides that
-they are not equal!  (*Note Floating-point Programming::.)  You can get
-the result you want by increasing the precision; 56 bits in this case
-will get the job done:
-
-     $ gawk -M -v PREC=56 'BEGIN { print (0.1 + 12.2 == 12.3) }'
-     -| 1
-
-   If adding more bits is good, perhaps adding even more bits of
-precision is better?  Here is what happens if we use an even larger
-value of `PREC':
-
-     $ gawk -M -v PREC=201 'BEGIN { print (0.1 + 12.2 == 12.3) }'
-     -| 0
-
-   This is not a bug in `gawk' or in the MPFR library.  It is easy to
-forget that the finite number of bits used to store the value is often
-just an approximation after proper rounding.  The test for equality
-succeeds if and only if _all_ bits in the two operands are exactly the
-same. Since this is not necessarily true after floating-point
-computations with a particular precision and effective rounding rule, a
-straight test for equality may not work.
-
-   So, don't assume that floating-point values can be compared for
-equality.  You should also exercise caution when using other forms of
-comparisons.  The standard way to compare between floating-point
-numbers is to determine how much error (or "tolerance") you will allow
-in a comparison and check to see if one value is within this error
-range of the other.
-
-   In applications where 15 or fewer decimal places suffice, hardware
-double precision arithmetic can be adequate, and is usually much faster.
-But you do need to keep in mind that every floating-point operation can
-suffer a new rounding error with catastrophic consequences as
-illustrated by our earlier attempt to compute the value of the constant
-pi (*note Floating-point Programming::).  Extra precision can greatly
-enhance the stability and the accuracy of your computation in such
-cases.
-
-   Repeated addition is not necessarily equivalent to multiplication in
-floating-point arithmetic. In the example in *note Floating-point
-Programming:::
-
-     $ gawk 'BEGIN {
-     >   for (d = 1.1; d <= 1.5; d += 0.1)    # loop five times (?)
-     >       i++
-     >   print i
-     > }'
-     -| 4
-
-you may or may not succeed in getting the correct result by choosing an
-arbitrarily large value for `PREC'. Reformulation of the problem at
-hand is often the correct approach in such situations.
+   (1) You asked for it, you got it.
 
 
-File: gawk.info,  Node: Arbitrary Precision Integers,  Prev: Arbitrary Precision Floats,  Up: Arbitrary Precision Arithmetic
+File: gawk.info,  Node: Floating point summary,  Prev: POSIX Floating Point Problems,  Up: Arbitrary Precision Arithmetic
 
-15.5 Arbitrary Precision Integer Arithmetic with `gawk'
-=======================================================
+15.7 Summary
+============
 
-If one of the options `--bignum' or `-M' is specified, `gawk' performs
-all integer arithmetic using GMP arbitrary precision integers.  Any
-number that looks like an integer in a program source or data file is
-stored as an arbitrary precision integer.  The size of the integer is
-limited only by your computer's memory.  The current floating-point
-context has no effect on operations involving integers.  For example,
-the following computes 5^4^3^2, the result of which is beyond the
-limits of ordinary `gawk' numbers:
+   * Most computer arithmetic is done using either integers or
+     floating-point values.  The default for `awk' is to use
+     double-precision floating-point values.
 
-     $ gawk -M 'BEGIN {
-     >   x = 5^4^3^2
-     >   print "# of digits =", length(x)
-     >   print substr(x, 1, 20), "...", substr(x, length(x) - 19, 20)
-     > }'
-     -| # of digits = 183231
-     -| 62060698786608744707 ... 92256259918212890625
+   * In the 1980's, Barbie mistakenly said "Math class is tough!"
+     While math isn't tough, floating-point arithmetic isn't the same
+     as pencil and paper math, and care must be taken:
 
-   If you were to compute the same value using arbitrary precision
-floating-point values instead, the precision needed for correct output
-(using the formula `prec = 3.322 * dps'), would be 3.322 x 183231, or
-608693.
+        - Not all numbers can be represented exactly.
 
-   The result from an arithmetic operation with an integer and a
-floating-point value is a floating-point value with a precision equal
-to the working precision.  The following program calculates the eighth
-term in Sylvester's sequence(1) using a recurrence:
+        - Comparing values should use a delta, instead of being done
+          directly with `==' and `!='.
 
-     $ gawk -M 'BEGIN {
-     >   s = 2.0
-     >   for (i = 1; i <= 7; i++)
-     >       s = s * (s - 1) + 1
-     >   print s
-     > }'
-     -| 113423713055421845118910464
+        - Errors accumulate.
 
-   The output differs from the actual number,
-113,423,713,055,421,844,361,000,443, because the default precision of
-53 bits is not enough to represent the floating-point results exactly.
-You can either increase the precision (100 bits is enough in this
-case), or replace the floating-point constant `2.0' with an integer, to
-perform all computations using integer arithmetic to get the correct
-output.
+        - Operations are not always truly associative or distributive.
 
-   It will sometimes be necessary for `gawk' to implicitly convert an
-arbitrary precision integer into an arbitrary precision floating-point
-value.  This is primarily because the MPFR library does not always
-provide the relevant interface to process arbitrary precision integers
-or mixed-mode numbers as needed by an operation or function.  In such a
-case, the precision is set to the minimum value necessary for exact
-conversion, and the working precision is not used for this purpose.  If
-this is not what you need or want, you can employ a subterfuge like
-this:
+   * Increasing the accuracy can help, but it is not a panacea.
 
-     gawk -M 'BEGIN { n = 13; print (n + 0.0) % 2.0 }'
+   * Often, increasing the accuracy and then rounding to the desired
+     number of digits produces reasonable results.
 
-   You can avoid this issue altogether by specifying the number as a
-floating-point value to begin with:
+   * Use either `-M' or `--bignum' to enable MPFR arithmetic. Use
+     `PREC' to set the precision in bits, and `ROUNDMODE' to set the
+     IEEE 754 rounding mode.
 
-     gawk -M 'BEGIN { n = 13.0; print n % 2.0 }'
+   * With `-M' or `--bignum', `gawk' performs arbitrary precision
+     integer arithmetic using the GMP library.  This is faster and more
+     space efficient than using MPFR for the same calculations.
 
-   Note that for the particular example above, there is likely best to
-just use the following:
+   * There are several "dark corners" with respect to floating-point
+     numbers where `gawk' disagrees with the POSIX standard.  It pays
+     to be aware of them.
 
-     gawk -M 'BEGIN { n = 13; print n % 2 }'
+   * Overall, there is no need to be unduly suspicious about the
+     results from floating-point arithmetic. The lesson to remember is
+     that floating-point arithmetic is always more complex than
+     arithmetic using pencil and paper. In order to take advantage of
+     the power of computer floating-point, you need to know its
+     limitations and work within them. For most casual use of
+     floating-point arithmetic, you will often get the expected result
+     if you simply round the display of your final results to the
+     correct number of significant decimal digits.
 
-   ---------- Footnotes ----------
+   * As general advice, avoid presenting numerical data in a manner that
+     implies better precision than is actually the case.
 
-   (1) Weisstein, Eric W.  `Sylvester's Sequence'. From MathWorld--A
-Wolfram Web Resource.
-`http://mathworld.wolfram.com/SylvestersSequence.html'
 
 
 File: gawk.info,  Node: Dynamic Extensions,  Next: Language History,  Prev: Arbitrary Precision Arithmetic,  Up: Top
@@ -21537,6 +22266,8 @@ sample extensions are automatically built and installed when `gawk' is.
 * Extension Samples::           The sample extensions that ship with
                                 `gawk'.
 * gawkextlib::                  The `gawkextlib' project.
+* Extension summary::           Extension summary.
+* Extension Exercises::         Exercises.
 
 
 File: gawk.info,  Node: Extension Intro,  Next: Plugin License,  Up: Dynamic Extensions
@@ -21590,7 +22321,8 @@ File: gawk.info,  Node: Extension Mechanism Outline,  Next: Extension API Descri
 
 Communication between `gawk' and an extension is two-way.  First, when
 an extension is loaded, it is passed a pointer to a `struct' whose
-fields are function pointers.  This is shown in *note load-extension::.
+fields are function pointers.  This is shown in *note
+figure-load-extension::.
 
                           API
                          Struct
@@ -21622,7 +22354,7 @@ Figure 16.1: Loading The Extension
 function pointers, at runtime, without needing (link-time) access to
 `gawk''s symbols.  One of these function pointers is to a function for
 "registering" new built-in functions.  This is shown in *note
-load-new-function::.
+figure-load-new-function::.
 
             register_ext_func({ "chdir", do_chdir, 1 });
 
@@ -21642,7 +22374,7 @@ Figure 16.2: Loading The New Function
 with `gawk' by passing function pointers to the functions that provide
 the new feature (`do_chdir()', for example).  `gawk' associates the
 function pointer with a name and can then call it, using a defined
-calling convention.  This is shown in *note call-new-function::.
+calling convention.  This is shown in *note figure-call-new-function::.
 
     BEGIN {
         chdir("/path")                             (*fnptr)(1);
@@ -21663,9 +22395,9 @@ Figure 16.3: Calling The New Function
 the API `struct' to do its work, such as updating variables or arrays,
 printing messages, setting `ERRNO', and so on.
 
-   Convenience macros in the `gawkapi.h' header file make calling
-through the function pointers look like regular function calls so that
-extension code is quite readable and understandable.
+   Convenience macros make calling through the function pointers look
+like regular function calls so that extension code is quite readable
+and understandable.
 
    Although all of this sounds somewhat complicated, the result is that
 extension code is quite straightforward to write and to read. You can
@@ -21692,13 +22424,17 @@ File: gawk.info,  Node: Extension API Description,  Next: Finding Extensions,  P
 16.4 API Description
 ====================
 
-This (rather large) minor node describes the API in detail.
+C or C++ code for an extension must include the header file
+`gawkapi.h', which declares the functions and defines the data types
+used to communicate with `gawk'.  This (rather large) minor node
+describes the API in detail.
 
 * Menu:
 
 * Extension API Functions Introduction:: Introduction to the API functions.
 * General Data Types::                   The data types.
 * Requesting Values::                    How to get a value.
+* Memory Allocation Functions::          Functions for allocating memory.
 * Constructor Functions::                Functions for creating values.
 * Registration Functions::               Functions to register things with
                                          `gawk'.
@@ -21723,7 +22459,7 @@ through function pointers passed into your extension.
    API function pointers are provided for the following kinds of
 operations:
 
-   * Registrations functions. You may register:
+   * Registration functions. You may register:
         - extension functions,
 
         - exit callbacks,
@@ -21747,6 +22483,8 @@ operations:
    * Symbol table access: retrieving a global variable, creating one,
      or changing one.
 
+   * Allocating, reallocating, and releasing memory.
+
    * Creating and releasing cached values; this provides an efficient
      way to use values for multiple variables and can be a big
      performance win.
@@ -21773,12 +22511,11 @@ operations:
      C Entity                 Header File
      ------------------------------------------- 
      `EOF'                    `<stdio.h>'
+     Values for `errno'       `<errno.h>'
      `FILE'                   `<stdio.h>'
      `NULL'                   `<stddef.h>'
-     `malloc()'               `<stdlib.h>'
      `memcpy()'               `<string.h>'
      `memset()'               `<string.h>'
-     `realloc()'              `<stdlib.h>'
      `size_t'                 `<sys/types.h>'
      `struct stat'            `<sys/stat.h>'
 
@@ -21789,9 +22526,6 @@ operations:
      a portability hodge-podge as can be seen in some parts of the
      `gawk' source code.
 
-     To pass reasonable integer values for `ERRNO', you will also need
-     to include `<errno.h>'.
-
    * The `gawkapi.h' file may be included more than once without ill
      effect.  Doing so, however, is poor coding practice.
 
@@ -21804,12 +22538,14 @@ operations:
    * All pointers filled in by `gawk' are to memory managed by `gawk'
      and should be treated by the extension as read-only.  Memory for
      _all_ strings passed into `gawk' from the extension _must_ come
-     from `malloc()' and is managed by `gawk' from then on.
+     from calling the API-provided function pointers `api_malloc()',
+     `api_calloc()' or `api_realloc()', and is managed by `gawk' from
+     then on.
 
    * The API defines several simple `struct's that map values as seen
      from `awk'.  A value can be a `double', a string, or an array (as
      in multidimensional arrays, or when creating a new array).  String
-     values maintain both pointer and length since embedded `NUL'
+     values maintain both pointer and length since embedded NUL
      characters are allowed.
 
           NOTE: By intent, strings are maintained using the current
@@ -21843,8 +22579,10 @@ File: gawk.info,  Node: General Data Types,  Next: Requesting Values,  Prev: Ext
 ---------------------------------
 
      I have a true love/hate relationship with unions.  -- Arnold
-     Robbins That's the thing about unions: the compiler will arrange
-     things so they can accommodate both love and hate.  -- Chet Ramey
+     Robbins
+
+     That's the thing about unions: the compiler will arrange things so
+     they can accommodate both love and hate.  -- Chet Ramey
 
    The extension API defines a number of simple types and structures
 for general purpose use. Additional, more specialized, data structures
@@ -21863,11 +22601,8 @@ that use them.
      allowing `gawk' to use them as it needs to.
 
 `typedef enum awk_bool {'
-
 `    awk_false = 0,'
-
 `    awk_true'
-
 `} awk_bool_t;'
      A simple boolean type.
 
@@ -21877,7 +22612,9 @@ that use them.
 `} awk_string_t;'
      This represents a mutable string. `gawk' owns the memory pointed
      to if it supplied the value. Otherwise, it takes ownership of the
-     memory pointed to.  *Such memory must come from `malloc()'!*
+     memory pointed to.  *Such memory must come from calling the
+     API-provided function pointers `api_malloc()', `api_calloc()', or
+     `api_realloc()'!*
 
      As mentioned earlier, strings are maintained using the current
      multibyte encoding.
@@ -21932,7 +22669,7 @@ that use them.
 indicates what is in the `union'.
 
    Representing numbers is easy--the API uses a C `double'.  Strings
-require more work. Since `gawk' allows embedded `NUL' bytes in string
+require more work. Since `gawk' allows embedded NUL bytes in string
 values, a string must be represented as a pair containing a
 data-pointer and length. This is the `awk_string_t' type.
 
@@ -21982,7 +22719,7 @@ the value.
 See also the entry for "Cookie" in the *note Glossary::.
 
 
-File: gawk.info,  Node: Requesting Values,  Next: Constructor Functions,  Prev: General Data Types,  Up: Extension API Description
+File: gawk.info,  Node: Requesting Values,  Next: Memory Allocation Functions,  Prev: General Data Types,  Up: Extension API Description
 
 16.4.3 Requesting Values
 ------------------------
@@ -22012,58 +22749,56 @@ Requested:   Scalar       Scalar         Scalar      false       false
              Value        false          false       false       false
              Cookie                                              
 
-Table 16.1: Value Types Returned
+Table 16.1: API Value Types Returned
 
 
-File: gawk.info,  Node: Constructor Functions,  Next: Registration Functions,  Prev: Requesting Values,  Up: Extension API Description
+File: gawk.info,  Node: Memory Allocation Functions,  Next: Constructor Functions,  Prev: Requesting Values,  Up: Extension API Description
 
-16.4.4 Constructor Functions and Convenience Macros
----------------------------------------------------
+16.4.4 Memory Allocation Functions and Convenience Macros
+---------------------------------------------------------
 
-The API provides a number of "constructor" functions for creating
-string and numeric values, as well as a number of convenience macros.
-This node presents them all as function prototypes, in the way that
-extension code would use them.
+The API provides a number of "memory allocation" functions for
+allocating memory that can be passed to `gawk', as well as a number of
+convenience macros.
 
-`static inline awk_value_t *'
-`make_const_string(const char *string, size_t length, awk_value_t *result)'
-     This function creates a string value in the `awk_value_t' variable
-     pointed to by `result'. It expects `string' to be a C string
-     constant (or other string data), and automatically creates a
-     _copy_ of the data for storage in `result'. It returns `result'.
+`void *gawk_malloc(size_t size);'
+     Call `gawk'-provided `api_malloc()' to allocate storage that may
+     be passed to `gawk'.
 
-`static inline awk_value_t *'
-`make_malloced_string(const char *string, size_t length, awk_value_t *result)'
-     This function creates a string value in the `awk_value_t' variable
-     pointed to by `result'. It expects `string' to be a `char *' value
-     pointing to data previously obtained from `malloc()'. The idea here
-     is that the data is passed directly to `gawk', which assumes
-     responsibility for it. It returns `result'.
+`void *gawk_calloc(size_t nmemb, size_t size);'
+     Call `gawk'-provided `api_calloc()' to allocate storage that may
+     be passed to `gawk'.
 
-`static inline awk_value_t *'
-`make_null_string(awk_value_t *result)'
-     This specialized function creates a null string (the "undefined"
-     value) in the `awk_value_t' variable pointed to by `result'.  It
-     returns `result'.
+`void *gawk_realloc(void *ptr, size_t size);'
+     Call `gawk'-provided `api_realloc()' to allocate storage that may
+     be passed to `gawk'.
 
-`static inline awk_value_t *'
-`make_number(double num, awk_value_t *result)'
-     This function simply creates a numeric value in the `awk_value_t'
-     variable pointed to by `result'.
+`void gawk_free(void *ptr);'
+     Call `gawk'-provided `api_free()' to release storage that was
+     allocated with `gawk_malloc()', `gawk_calloc()' or
+     `gawk_realloc()'.
 
-   Two convenience macros may be used for allocating storage from
-`malloc()' and `realloc()'. If the allocation fails, they cause `gawk'
-to exit with a fatal error message.  They should be used as if they were
-procedure calls that do not return a value.
+   The API has to provide these functions because it is possible for an
+extension to be compiled and linked against a different version of the
+C library than was used for the `gawk' executable.(1) If `gawk' were to
+use its version of `free()' when the memory came from an unrelated
+version of `malloc()', unexpected behavior would likely result.
+
+   Two convenience macros may be used for allocating storage from the
+API-provided function pointers `api_malloc()' and `api_realloc()'. If
+the allocation fails, they cause `gawk' to exit with a fatal error
+message.  They should be used as if they were procedure calls that do
+not return a value.
 
 `#define emalloc(pointer, type, size, message) ...'
      The arguments to this macro are as follows:
+
     `pointer'
           The pointer variable to point at the allocated storage.
 
     `type'
           The type of the pointer variable, used to create a cast for
-          the call to `malloc()'.
+          the call to `api_malloc()'.
 
     `size'
           The total number of bytes to be allocated.
@@ -22083,14 +22818,57 @@ procedure calls that do not return a value.
           make_malloced_string(message, strlen(message), & result);
 
 `#define erealloc(pointer, type, size, message) ...'
-     This is like `emalloc()', but it calls `realloc()', instead of
-     `malloc()'.  The arguments are the same as for the `emalloc()'
+     This is like `emalloc()', but it calls `api_realloc()', instead of
+     `api_malloc()'.  The arguments are the same as for the `emalloc()'
      macro.
 
+   ---------- Footnotes ----------
+
+   (1) This is more common on MS-Windows systems, but can happen on
+Unix-like systems as well.
+
+
+File: gawk.info,  Node: Constructor Functions,  Next: Registration Functions,  Prev: Memory Allocation Functions,  Up: Extension API Description
+
+16.4.5 Constructor Functions
+----------------------------
+
+The API provides a number of "constructor" functions for creating
+string and numeric values, as well as a number of convenience macros.
+This node presents them all as function prototypes, in the way that
+extension code would use them.
+
+`static inline awk_value_t *'
+`make_const_string(const char *string, size_t length, awk_value_t *result)'
+     This function creates a string value in the `awk_value_t' variable
+     pointed to by `result'. It expects `string' to be a C string
+     constant (or other string data), and automatically creates a
+     _copy_ of the data for storage in `result'. It returns `result'.
+
+`static inline awk_value_t *'
+`make_malloced_string(const char *string, size_t length, awk_value_t *result)'
+     This function creates a string value in the `awk_value_t' variable
+     pointed to by `result'. It expects `string' to be a `char *' value
+     pointing to data previously obtained from the api-provided
+     functions `api_malloc()', `api_calloc()' or `api_realloc()'. The
+     idea here is that the data is passed directly to `gawk', which
+     assumes responsibility for it. It returns `result'.
+
+`static inline awk_value_t *'
+`make_null_string(awk_value_t *result)'
+     This specialized function creates a null string (the "undefined"
+     value) in the `awk_value_t' variable pointed to by `result'.  It
+     returns `result'.
+
+`static inline awk_value_t *'
+`make_number(double num, awk_value_t *result)'
+     This function simply creates a numeric value in the `awk_value_t'
+     variable pointed to by `result'.
+
 
 File: gawk.info,  Node: Registration Functions,  Next: Printing Messages,  Prev: Constructor Functions,  Up: Extension API Description
 
-16.4.5 Registration Functions
+16.4.6 Registration Functions
 -----------------------------
 
 This minor node describes the API functions for registering parts of
@@ -22108,7 +22886,7 @@ your extension with `gawk'.
 
 File: gawk.info,  Node: Extension Functions,  Next: Exit Callback Functions,  Up: Registration Functions
 
-16.4.5.1 Registering An Extension Function
+16.4.6.1 Registering An Extension Function
 ..........................................
 
 Extension functions are described by the following record:
@@ -22133,8 +22911,10 @@ Extension functions are described by the following record:
 `awk_value_t *(*function)(int num_actual_args, awk_value_t *result);'
      This is a pointer to the C function that provides the desired
      functionality.  The function must fill in the result with either a
-     number or a string. `awk' takes ownership of any string memory.
-     As mentioned earlier, string memory *must* come from `malloc()'.
+     number or a string. `gawk' takes ownership of any string memory.
+     As mentioned earlier, string memory *must* come from the
+     api-provided functions `api_malloc()', `api_calloc()' or
+     `api_realloc()'.
 
      The `num_actual_args' argument tells the C function how many
      actual parameters were passed from the calling `awk' code.
@@ -22160,11 +22940,11 @@ register it with `gawk' using this API function:
 
 File: gawk.info,  Node: Exit Callback Functions,  Next: Extension Version String,  Prev: Extension Functions,  Up: Registration Functions
 
-16.4.5.2 Registering An Exit Callback Function
+16.4.6.2 Registering An Exit Callback Function
 ..............................................
 
 An "exit callback" function is a function that `gawk' calls before it
-exits.  Such functions are useful if you have general "clean up" tasks
+exits.  Such functions are useful if you have general "cleanup" tasks
 that should be performed in your extension (such as closing data base
 connections or other resource deallocations).  You can register such a
 function with `gawk' using the following function.
@@ -22172,6 +22952,7 @@ function with `gawk' using the following function.
 `void awk_atexit(void (*funcp)(void *data, int exit_status),'
 `                void *arg0);'
      The parameters are:
+
     `funcp'
           A pointer to the function to be called before `gawk' exits.
           The `data' parameter will be the original value of `arg0'.
@@ -22189,7 +22970,7 @@ order--that is, in the reverse order in which they are registered with
 
 File: gawk.info,  Node: Extension Version String,  Next: Input Parsers,  Prev: Exit Callback Functions,  Up: Registration Functions
 
-16.4.5.3 Registering An Extension Version String
+16.4.6.3 Registering An Extension Version String
 ................................................
 
 You can register a version string which indicates the name and version
@@ -22205,7 +22986,7 @@ invoked with the `--version' option.
 
 File: gawk.info,  Node: Input Parsers,  Next: Output Wrappers,  Prev: Extension Version String,  Up: Registration Functions
 
-16.4.5.4 Customized Input Parsers
+16.4.6.4 Customized Input Parsers
 .................................
 
 By default, `gawk' reads text files as its input. It uses the value of
@@ -22260,7 +23041,8 @@ used for `RT', if any.
      A pointer to your `XXX_take_control_of()' function.
 
 `awk_const struct input_parser *awk_const next;'
-     This pointer is used by `gawk'.  The extension cannot modify it.
+     This is for use by `gawk'; therefore it is marked `awk_const' so
+     that the extension cannot modify it.
 
    The steps are as follows:
 
@@ -22299,8 +23081,8 @@ as follows:
      Otherwise, it will.
 
 `struct stat sbuf;'
-     If file descriptor is valid, then `gawk' will have filled in this
-     structure via a call to the `fstat()' system call.
+     If the file descriptor is valid, then `gawk' will have filled in
+     this structure via a call to the `fstat()' system call.
 
    The `XXX_can_take_file()' function should examine these fields and
 decide if the input parser should be used for the file.  The decision
@@ -22427,7 +23209,7 @@ whether or not to activate an input parser (*note BEGINFILE/ENDFILE::).
 
 File: gawk.info,  Node: Output Wrappers,  Next: Two-way processors,  Prev: Input Parsers,  Up: Registration Functions
 
-16.4.5.5 Customized Output Wrappers
+16.4.6.5 Customized Output Wrappers
 ...................................
 
 An "output wrapper" is the mirror image of an input parser.  It allows
@@ -22463,8 +23245,8 @@ an extension to take over the output to a file opened with the `>' or
      false otherwise.
 
 `awk_const struct output_wrapper *awk_const next;'
-     This is for use by `gawk'; therefore they are marked `awk_const'
-     so that the extension cannot modify them.
+     This is for use by `gawk'; therefore it is marked `awk_const' so
+     that the extension cannot modify it.
 
    The `awk_output_buf_t' structure looks like this:
 
@@ -22521,9 +23303,9 @@ in the `awk_output_buf_t'.  The data members are as follows:
 the `name' and `mode' fields, and any additional state (such as `awk'
 variable values) that is appropriate.
 
-   When `gawk' calls `XXX_take_control_of()', it should fill in the
-other fields, as appropriate, except for `fp', which it should just use
-normally.
+   When `gawk' calls `XXX_take_control_of()', that function should fill
+in the other fields, as appropriate, except for `fp', which it should
+just use normally.
 
    You register your output wrapper with the following function:
 
@@ -22534,7 +23316,7 @@ normally.
 
 File: gawk.info,  Node: Two-way processors,  Prev: Output Wrappers,  Up: Registration Functions
 
-16.4.5.6 Customized Two-way Processors
+16.4.6.6 Customized Two-way Processors
 ......................................
 
 A "two-way processor" combines an input parser and an output wrapper for
@@ -22560,7 +23342,7 @@ structures as described earlier.
 
 `awk_bool_t (*can_take_two_way)(const char *name);'
      This function returns true if it wants to take over two-way I/O
-     for this filename.  It should not change any state (variable
+     for this file name.  It should not change any state (variable
      values, etc.) within `gawk'.
 
 `awk_bool_t (*take_control_of)(const char *name,'
@@ -22571,8 +23353,8 @@ structures as described earlier.
      respectively.  These structures were described earlier.
 
 `awk_const struct two_way_processor *awk_const next;'
-     This is for use by `gawk'; therefore they are marked `awk_const'
-     so that the extension cannot modify them.
+     This is for use by `gawk'; therefore it is marked `awk_const' so
+     that the extension cannot modify it.
 
    As with the input parser and output processor, you provide "yes I
 can take this" and "take over for this" functions,
@@ -22587,7 +23369,7 @@ can take this" and "take over for this" functions,
 
 File: gawk.info,  Node: Printing Messages,  Next: Updating `ERRNO',  Prev: Registration Functions,  Up: Extension API Description
 
-16.4.6 Printing Messages
+16.4.7 Printing Messages
 ------------------------
 
 You can print different kinds of warning messages from your extension,
@@ -22618,7 +23400,7 @@ the pity.
 
 File: gawk.info,  Node: Updating `ERRNO',  Next: Accessing Parameters,  Prev: Printing Messages,  Up: Extension API Description
 
-16.4.7 Updating `ERRNO'
+16.4.8 Updating `ERRNO'
 -----------------------
 
 The following functions allow you to update the `ERRNO' variable:
@@ -22639,7 +23421,7 @@ The following functions allow you to update the `ERRNO' variable:
 
 File: gawk.info,  Node: Accessing Parameters,  Next: Symbol Table Access,  Prev: Updating `ERRNO',  Up: Extension API Description
 
-16.4.8 Accessing and Updating Parameters
+16.4.9 Accessing and Updating Parameters
 ----------------------------------------
 
 Two functions give you access to the arguments (parameters) passed to
@@ -22665,8 +23447,8 @@ your extension function. They are:
 
 File: gawk.info,  Node: Symbol Table Access,  Next: Array Manipulation,  Prev: Accessing Parameters,  Up: Extension API Description
 
-16.4.9 Symbol Table Access
---------------------------
+16.4.10 Symbol Table Access
+---------------------------
 
 Two sets of routines provide access to global variables, and one set
 allows you to create and release cached values.
@@ -22680,8 +23462,8 @@ allows you to create and release cached values.
 
 File: gawk.info,  Node: Symbol table by name,  Next: Symbol table by cookie,  Up: Symbol Table Access
 
-16.4.9.1 Variable Access and Update by Name
-...........................................
+16.4.10.1 Variable Access and Update by Name
+............................................
 
 The following routines provide the ability to access and update global
 `awk'-level variables by name.  In compiler terminology, identifiers of
@@ -22713,11 +23495,16 @@ termed a "symbol table".
 However, with the exception of the `PROCINFO' array, an extension
 cannot change any of those variables.
 
+     NOTE: It is possible for the lookup of `PROCINFO' to fail. This
+     happens if the `awk' program being run does not reference
+     `PROCINFO'; in this case `gawk' doesn't bother to create the array
+     and populate it.
+
 
 File: gawk.info,  Node: Symbol table by cookie,  Next: Cached values,  Prev: Symbol table by name,  Up: Symbol Table Access
 
-16.4.9.2 Variable Access and Update by Cookie
-.............................................
+16.4.10.2 Variable Access and Update by Cookie
+..............................................
 
 A "scalar cookie" is an opaque handle that provides access to a global
 variable or array. It is an optimization that avoids looking up
@@ -22736,7 +23523,7 @@ was discussed earlier, in *note General Data Types::.
 
 `awk_bool_t sym_update_scalar(awk_scalar_t cookie, awk_value_t *value);'
      Update the value associated with a scalar cookie.  Return false if
-     the new value is not one of `AWK_STRING' or `AWK_NUMBER'.  Here
+     the new value is not of type `AWK_STRING' or `AWK_NUMBER'.  Here
      too, the built-in variables may not be updated.
 
    It is not obvious at first glance how to work with scalar cookies or
@@ -22829,8 +23616,8 @@ like this:
 
 File: gawk.info,  Node: Cached values,  Prev: Symbol table by cookie,  Up: Symbol Table Access
 
-16.4.9.3 Creating and Using Cached Values
-.........................................
+16.4.10.3 Creating and Using Cached Values
+..........................................
 
 The routines in this section allow you to create and release cached
 values.  As with scalar cookies, in theory, cached values are not
@@ -22840,8 +23627,9 @@ variables using `sym_update()' or `sym_update_scalar()', as you like.
 
    However, you can understand the point of cached values if you
 remember that _every_ string value's storage _must_ come from
-`malloc()'.  If you have 20 variables, all of which have the same
-string value, you must create 20 identical copies of the string.(1)
+`api_malloc()', `api_calloc()' or `api_realloc()'.  If you have 20
+variables, all of which have the same string value, you must create 20
+identical copies of the string.(1)
 
    It is clearly more efficient, if possible, to create a value once,
 and then tell `gawk' to reuse the value for multiple variables. That is
@@ -22850,9 +23638,10 @@ follows:
 
 `awk_bool_t create_value(awk_value_t *value, awk_value_cookie_t *result);'
      Create a cached string or numeric value from `value' for efficient
-     later assignment.  Only `AWK_NUMBER' and `AWK_STRING' values are
-     allowed.  Any other type is rejected.  While `AWK_UNDEFINED' could
-     be allowed, doing so would result in inferior performance.
+     later assignment.  Only values of type `AWK_NUMBER' and
+     `AWK_STRING' are allowed.  Any other type is rejected.  While
+     `AWK_UNDEFINED' could be allowed, doing so would result in
+     inferior performance.
 
 `awk_bool_t release_value(awk_value_cookie_t vc);'
      Release the memory associated with a value cookie obtained from
@@ -22906,13 +23695,13 @@ if `awk' code assigns a new value to `VAR1', are all the others be
 changed too?"
 
    That's a great question. The answer is that no, it's not a problem.
-Internally, `gawk' uses reference-counted strings. This means that many
-variables can share the same string value, and `gawk' keeps track of
-the usage.  When a variable's value changes, `gawk' simply decrements
-the reference count on the old value and updates the variable to use
-the new value.
+Internally, `gawk' uses "reference-counted strings". This means that
+many variables can share the same string value, and `gawk' keeps track
+of the usage.  When a variable's value changes, `gawk' simply
+decrements the reference count on the old value and updates the
+variable to use the new value.
 
-   Finally, as part of your clean up action (*note Exit Callback
+   Finally, as part of your cleanup action (*note Exit Callback
 Functions::) you should release any cached values that you created,
 using `release_value()'.
 
@@ -22924,7 +23713,7 @@ using `release_value()'.
 
 File: gawk.info,  Node: Array Manipulation,  Next: Extension API Variables,  Prev: Symbol Table Access,  Up: Extension API Description
 
-16.4.10 Array Manipulation
+16.4.11 Array Manipulation
 --------------------------
 
 The primary data structure(1) in `awk' is the associative array (*note
@@ -22951,7 +23740,7 @@ arrays of arrays (*note General Data Types::).
 
 File: gawk.info,  Node: Array Data Types,  Next: Array Functions,  Up: Array Manipulation
 
-16.4.10.1 Array Data Types
+16.4.11.1 Array Data Types
 ..........................
 
 The data types associated with arrays are listed below.
@@ -23018,7 +23807,7 @@ overuse this term.
 
 File: gawk.info,  Node: Array Functions,  Next: Flattening Arrays,  Prev: Array Data Types,  Up: Array Manipulation
 
-16.4.10.2 Array Functions
+16.4.11.2 Array Functions
 .........................
 
 The following functions relate to individual array elements.
@@ -23044,7 +23833,8 @@ The following functions relate to individual array elements.
      strings (*note Conversion::); thus using integral values is safest.
 
      As with _all_ strings passed into `gawk' from an extension, the
-     string value of `index' must come from `malloc()', and `gawk'
+     string value of `index' must come from the API-provided functions
+     `api_malloc()', `api_calloc()' or `api_realloc()' and `gawk'
      releases the storage.
 
 `awk_bool_t set_array_element(awk_array_t a_cookie,'
@@ -23052,7 +23842,7 @@ The following functions relate to individual array elements.
 `                             const awk_value_t *const value);'
      In the array represented by `a_cookie', create or modify the
      element whose index is given by `index'.  The `ARGV' and `ENVIRON'
-     arrays may not be changed.
+     arrays may not be changed, although the `PROCINFO' array can be.
 
 `awk_bool_t set_array_element_by_elem(awk_array_t a_cookie,'
 `                                     awk_element_t element);'
@@ -23095,7 +23885,7 @@ The following functions relate to individual array elements.
 
 File: gawk.info,  Node: Flattening Arrays,  Next: Creating Arrays,  Prev: Array Functions,  Up: Array Manipulation
 
-16.4.10.3 Working With All The Elements of an Array
+16.4.11.3 Working With All The Elements of an Array
 ...................................................
 
 To "flatten" an array is create a structure that represents the full
@@ -23269,7 +24059,7 @@ return value to success, and returns:
 
 File: gawk.info,  Node: Creating Arrays,  Prev: Flattening Arrays,  Up: Array Manipulation
 
-16.4.10.4 How To Create and Populate Arrays
+16.4.11.4 How To Create and Populate Arrays
 ...........................................
 
 Besides working with arrays created by `awk' code, you can create
@@ -23290,8 +24080,8 @@ code:
      Thus, the correct way to build an array is to work "top down."
      Create the array, and immediately install it in `gawk''s symbol
      table using `sym_update()', or install it as an element in a
-     previously existing array using `set_element()'.  We show example
-     code shortly.
+     previously existing array using `set_array_element()'.  We show
+     example code shortly.
 
   2. Due to gawk internals, after using `sym_update()' to install an
      array into `gawk', you have to retrieve the array cookie from the
@@ -23408,7 +24198,7 @@ environment variable.)
 
 File: gawk.info,  Node: Extension API Variables,  Next: Extension API Boilerplate,  Prev: Array Manipulation,  Up: Extension API Description
 
-16.4.11 API Variables
+16.4.12 API Variables
 ---------------------
 
 The API provides two sets of variables.  The first provides information
@@ -23425,7 +24215,7 @@ information about how `gawk' was invoked.
 
 File: gawk.info,  Node: Extension Versioning,  Next: Extension API Informational Variables,  Up: Extension API Variables
 
-16.4.11.1 API Version Constants and Variables
+16.4.12.1 API Version Constants and Variables
 .............................................
 
 The API provides both a "major" and a "minor" version number.  The API
@@ -23474,20 +24264,22 @@ Boilerplate::).
 
 File: gawk.info,  Node: Extension API Informational Variables,  Prev: Extension Versioning,  Up: Extension API Variables
 
-16.4.11.2 Informational Variables
+16.4.12.2 Informational Variables
 .................................
 
 The API provides access to several variables that describe whether the
 corresponding command-line options were enabled when `gawk' was
 invoked.  The variables are:
 
+`do_debug'
+     This variable is true if `gawk' was invoked with `--debug' option.
+
 `do_lint'
      This variable is true if `gawk' was invoked with `--lint' option
      (*note Options::).
 
-`do_traditional'
-     This variable is true if `gawk' was invoked with `--traditional'
-     option.
+`do_mpfr'
+     This variable is true if `gawk' was invoked with `--bignum' option.
 
 `do_profile'
      This variable is true if `gawk' was invoked with `--profile'
@@ -23497,11 +24289,9 @@ invoked.  The variables are:
      This variable is true if `gawk' was invoked with `--sandbox'
      option.
 
-`do_debug'
-     This variable is true if `gawk' was invoked with `--debug' option.
-
-`do_mpfr'
-     This variable is true if `gawk' was invoked with `--bignum' option.
+`do_traditional'
+     This variable is true if `gawk' was invoked with `--traditional'
+     option.
 
    The value of `do_lint' can change if `awk' code modifies the `LINT'
 built-in variable (*note Built-in Variables::).  The others should not
@@ -23510,7 +24300,7 @@ change during execution.
 
 File: gawk.info,  Node: Extension API Boilerplate,  Prev: Extension API Variables,  Up: Extension API Description
 
-16.4.12 Boilerplate Code
+16.4.13 Boilerplate Code
 ------------------------
 
 As mentioned earlier (*note Extension Mechanism Outline::), the function
@@ -24028,7 +24818,7 @@ declarations and argument checking:
          awk_array_t array;
          int ret;
          struct stat sbuf;
-         /* default is stat() */
+         /* default is lstat() */
          int (*statfunc)(const char *path, struct stat *sbuf) = lstat;
 
          assert(result != NULL);
@@ -24101,7 +24891,9 @@ for loading each function into `gawk':
      static awk_ext_func_t func_table[] = {
          { "chdir", do_chdir, 1 },
          { "stat",  do_stat, 2 },
+     #ifndef __MINGW32__
          { "fts",   do_fts, 3 },
+     #endif
      };
 
    Each extension must have a routine named `dl_load()' to load
@@ -24112,8 +24904,7 @@ everything that needs to be loaded.  It is simplest to use the
 
      dl_load_func(func_table, filefuncs, "")
 
-   And that's it!  As an exercise, consider adding functions to
-implement system calls such as `chown()', `chmod()', and `umask()'.
+   And that's it!
 
    ---------- Footnotes ----------
 
@@ -24166,8 +24957,8 @@ create a GNU/Linux shared library:
      }
 
    The `AWKLIBPATH' environment variable tells `gawk' where to find
-shared libraries (*note Finding Extensions::).  We set it to the
-current directory and run the program:
+extensions (*note Finding Extensions::).  We set it to the current
+directory and run the program:
 
      $ AWKLIBPATH=$PWD gawk -f testff.awk
      -| /tmp
@@ -24197,7 +24988,7 @@ current directory and run the program:
    ---------- Footnotes ----------
 
    (1) In practice, you would probably want to use the GNU
-Autotools--Automake, Autoconf, Libtool, and Gettext--to configure and
+Autotools--Automake, Autoconf, Libtool, and `gettext'--to configure and
 build your libraries. Instructions for doing so are beyond the scope of
 this Info file. *Note gawkextlib::, for WWW links to the tools.
 
@@ -24240,7 +25031,7 @@ File: gawk.info,  Node: Extension Sample File Functions,  Next: Extension Sample
 The `filefuncs' extension provides three different functions, as
 follows: The usage is:
 
-`@load "filefuncs"'
+@load "filefuncs"
      This is how you load the extension.
 
 `result = chdir("/some/directory")'
@@ -24249,7 +25040,7 @@ follows: The usage is:
      success or less than zero upon error.  In the latter case it
      updates `ERRNO'.
 
-`result = stat("/some/path", statdata [, follow])'
+`result = stat("/some/path", statdata' [`, follow']`)'
      The `stat()' function provides a hook into the `stat()' system
      call.  It returns zero upon success or less than zero upon error.
      In the latter case it updates `ERRNO'.
@@ -24261,52 +25052,36 @@ follows: The usage is:
      successful, `stat()' fills the `statdata' array with information
      retrieved from the filesystem, as follows:
 
-     `statdata["name"]' The name of the file.
-     `statdata["dev"]'  Corresponds to the `st_dev' field in
-                       the `struct stat'.
-     `statdata["ino"]'  Corresponds to the `st_ino' field in
-                       the `struct stat'.
-     `statdata["mode"]' Corresponds to the `st_mode' field in
-                       the `struct stat'.
-     `statdata["nlink"]' Corresponds to the `st_nlink' field in
-                       the `struct stat'.
-     `statdata["uid"]'  Corresponds to the `st_uid' field in
-                       the `struct stat'.
-     `statdata["gid"]'  Corresponds to the `st_gid' field in
-                       the `struct stat'.
-     `statdata["size"]' Corresponds to the `st_size' field in
-                       the `struct stat'.
-     `statdata["atime"]' Corresponds to the `st_atime' field in
-                       the `struct stat'.
-     `statdata["mtime"]' Corresponds to the `st_mtime' field in
-                       the `struct stat'.
-     `statdata["ctime"]' Corresponds to the `st_ctime' field in
-                       the `struct stat'.
-     `statdata["rdev"]' Corresponds to the `st_rdev' field in
-                       the `struct stat'.  This element is
-                       only present for device files.
-     `statdata["major"]' Corresponds to the `st_major' field in
-                       the `struct stat'.  This element is
-                       only present for device files.
-     `statdata["minor"]' Corresponds to the `st_minor' field in
-                       the `struct stat'.  This element is
-                       only present for device files.
-     `statdata["blksize"]' Corresponds to the `st_blksize' field
-                       in the `struct stat', if this field is
-                       present on your system.  (It is present
-                       on all modern systems that we know of.)
-     `statdata["pmode"]' A human-readable version of the mode
-                       value, such as printed by `ls'.  For
-                       example, `"-rwxr-xr-x"'.
-     `statdata["linkval"]' If the named file is a symbolic link,
-                       this element will exist and its value
-                       is the value of the symbolic link
-                       (where the symbolic link points to).
-     `statdata["type"]' The type of the file as a string. One
-                       of `"file"', `"blockdev"', `"chardev"',
-                       `"directory"', `"socket"', `"fifo"',
-                       `"symlink"', `"door"', or `"unknown"'.
-                       Not all systems support all file types.
+     Subscript  Field in `struct stat'             File type
+     ------------------------------------------------------------ 
+     `"name"'   The file name                      All
+     `"dev"'    `st_dev'                           All
+     `"ino"'    `st_ino'                           All
+     `"mode"'   `st_mode'                          All
+     `"nlink"'  `st_nlink'                         All
+     `"uid"'    `st_uid'                           All
+     `"gid"'    `st_gid'                           All
+     `"size"'   `st_size'                          All
+     `"atime"'  `st_atime'                         All
+     `"mtime"'  `st_mtime'                         All
+     `"ctime"'  `st_ctime'                         All
+     `"rdev"'   `st_rdev'                          Device files
+     `"major"'  `st_major'                         Device files
+     `"minor"'  `st_minor'                         Device files
+     `"blksize"'`st_blksize'                       All
+     `"pmode"'  A human-readable version of the    All
+                mode value, such as printed by     
+                `ls'.  For example,                
+                `"-rwxr-xr-x"'                     
+     `"linkval"'The value of the symbolic link     Symbolic
+                                                   links
+     `"type"'   The type of the file as a string.  All
+                One of `"file"', `"blockdev"',     
+                `"chardev"', `"directory"',        
+                `"socket"', `"fifo"', `"symlink"', 
+                `"door"', or `"unknown"'.  Not     
+                all systems support all file       
+                types.                             
 
 `flags = or(FTS_PHYSICAL, ...)'
 `result = fts(pathlist, flags, filedata)'
@@ -24324,7 +25099,7 @@ requested hierarchies.
    The arguments are as follows:
 
 `pathlist'
-     An array of filenames.  The element values are used; the index
+     An array of file names.  The element values are used; the index
      values are ignored.
 
 `flags'
@@ -24426,43 +25201,39 @@ File: gawk.info,  Node: Extension Sample Fnmatch,  Next: Extension Sample Fork,
 This extension provides an interface to the C library `fnmatch()'
 function.  The usage is:
 
-     @load "fnmatch"
+`@load "fnmatch"'
+     This is how you load the extension.
 
-     result = fnmatch(pattern, string, flags)
+`result = fnmatch(pattern, string, flags)'
+     The return value is zero on success, `FNM_NOMATCH' if the string
+     did not match the pattern, or a different non-zero value if an
+     error occurred.
 
-   The `fnmatch' extension adds a single function named `fnmatch()',
-one constant (`FNM_NOMATCH'), and an array of flag values named `FNM'.
+   Besides the `fnmatch()' function, the `fnmatch' extension adds one
+constant (`FNM_NOMATCH'), and an array of flag values named `FNM'.
 
    The arguments to `fnmatch()' are:
 
 `pattern'
-     The filename wildcard to match.
+     The file name wildcard to match.
 
 `string'
-     The filename string.
+     The file name string.
 
 `flag'
      Either zero, or the bitwise OR of one or more of the flags in the
      `FNM' array.
 
-   The return value is zero on success, `FNM_NOMATCH' if the string did
-not match the pattern, or a different non-zero value if an error
-occurred.
-
    The flags are follows:
 
-`FNM["CASEFOLD"]'   Corresponds to the `FNM_CASEFOLD' flag as defined in
-                   `fnmatch()'.
-`FNM["FILE_NAME"]'  Corresponds to the `FNM_FILE_NAME' flag as defined
-                   in `fnmatch()'.
-`FNM["LEADING_DIR"]' Corresponds to the `FNM_LEADING_DIR' flag as defined
-                   in `fnmatch()'.
-`FNM["NOESCAPE"]'   Corresponds to the `FNM_NOESCAPE' flag as defined in
-                   `fnmatch()'.
-`FNM["PATHNAME"]'   Corresponds to the `FNM_PATHNAME' flag as defined in
-                   `fnmatch()'.
-`FNM["PERIOD"]'     Corresponds to the `FNM_PERIOD' flag as defined in
-                   `fnmatch()'.
+Array element      Corresponding flag defined by `fnmatch()'
+-------------------------------------------------------------------------- 
+`FNM["CASEFOLD"]'  `FNM_CASEFOLD'
+`FNM["FILE_NAME"]' `FNM_FILE_NAME'
+`FNM["LEADING_DIR"]'`FNM_LEADING_DIR'
+`FNM["NOESCAPE"]'  `FNM_NOESCAPE'
+`FNM["PATHNAME"]'  `FNM_PATHNAME'
+`FNM["PERIOD"]'    `FNM_PERIOD'
 
    Here is an example:
 
@@ -24484,14 +25255,14 @@ The `fork' extension adds three functions, as follows.
      This is how you load the extension.
 
 `pid = fork()'
-     This function creates a new process. The return value is the zero
-     in the child and the process-id number of the child in the parent,
-     or -1 upon error. In the latter case, `ERRNO' indicates the
-     problem.  In the child, `PROCINFO["pid"]' and `PROCINFO["ppid"]'
-     are updated to reflect the correct values.
+     This function creates a new process. The return value is zero in
+     the child and the process-ID number of the child in the parent, or
+     -1 upon error. In the latter case, `ERRNO' indicates the problem.
+     In the child, `PROCINFO["pid"]' and `PROCINFO["ppid"]' are updated
+     to reflect the correct values.
 
 `ret = waitpid(pid)'
-     This function takes a numeric argument, which is the process-id to
+     This function takes a numeric argument, which is the process-ID to
      wait for. The return value is that of the `waitpid()' system call.
 
 `ret = wait()'
@@ -24539,8 +25310,8 @@ standard output to a temporary file configured to have the same owner
 and permissions as the original.  After the file has been processed,
 the extension restores standard output to its original destination.  If
 `INPLACE_SUFFIX' is not an empty string, the original file is linked to
-a backup filename created by appending that suffix.  Finally, the
-temporary file is renamed to the original filename.
+a backup file name created by appending that suffix.  Finally, the
+temporary file is renamed to the original file name.
 
    If any error occurs, the extension issues a fatal error to terminate
 processing immediately without damaging the original file.
@@ -24554,9 +25325,6 @@ processing immediately without damaging the original file.
      $ gawk -i inplace -v INPLACE_SUFFIX=.bak '{ gsub(/foo/, "bar") }
      > { print }' file1 file2 file3
 
-   We leave it as an exercise to write a wrapper script that presents an
-interface similar to `sed -i'.
-
 
 File: gawk.info,  Node: Extension Sample Ord,  Next: Extension Sample Readdir,  Prev: Extension Sample Inplace,  Up: Extension Samples
 
@@ -24600,10 +25368,11 @@ on the command line (or with `getline'), they are read, with each entry
 returned as a record.
 
    The record consists of three fields. The first two are the inode
-number and the filename, separated by a forward slash character.  On
+number and the file name, separated by a forward slash character.  On
 systems where the directory entry contains the file type, the record
 has a third field (also separated by a slash) which is a single letter
-indicating the type of the file:
+indicating the type of the file. The letters are file types are shown
+in *note table-readdir-file-types::.
 
 Letter  File Type
 -------------------------------------------------------------------------- 
@@ -24616,6 +25385,8 @@ Letter  File Type
 `s'     Socket
 `u'     Anything else (unknown)
 
+Table 16.2: File Types Returned By `readdir()'
+
    On systems without the file type information, the third field is
 always `u'.
 
@@ -24647,10 +25418,10 @@ unwary.  Here is an example:
 
      BEGIN {
          REVOUT = 1
-         print "hello, world" > "/dev/stdout"
+         print "don't panic" > "/dev/stdout"
      }
 
-   The output from this program is: `dlrow ,olleh'.
+   The output from this program is: `cinap t'nod'.
 
 
 File: gawk.info,  Node: Extension Sample Rev2way,  Next: Extension Sample Read write array,  Prev: Extension Sample Revout,  Up: Extension Samples
@@ -24668,12 +25439,14 @@ example shows how to use it:
 
      BEGIN {
          cmd = "/magic/mirror"
-         print "hello, world" |& cmd
+         print "don't panic" |& cmd
          cmd |& getline result
          print result
          close(cmd)
      }
 
+   The output from this program is: `cinap t'nod'.
+
 
 File: gawk.info,  Node: Extension Sample Read write array,  Next: Extension Sample Readfile,  Prev: Extension Sample Rev2way,  Up: Extension Samples
 
@@ -24685,8 +25458,8 @@ The `rwarray' extension adds two functions, named `writea()' and
 
 `ret = writea(file, array)'
      This function takes a string argument, which is the name of the
-     file to which dump the array, and the array itself as the second
-     argument.  `writea()' understands multidimensional arrays.  It
+     file to which to dump the array, and the array itself as the
+     second argument.  `writea()' understands arrays of arrays.  It
      returns one on success, or zero upon failure.
 
 `ret = reada(file, array)'
@@ -24724,7 +25497,8 @@ File: gawk.info,  Node: Extension Sample Readfile,  Next: Extension Sample API T
 16.7.10 Reading An Entire File
 ------------------------------
 
-The `readfile' extension adds a single function named `readfile()':
+The `readfile' extension adds a single function named `readfile()', and
+an input parser:
 
 `@load "readfile"'
      This is how you load the extension.
@@ -24734,6 +25508,12 @@ The `readfile' extension adds a single function named `readfile()':
      a string containing the entire contents of the requested file.
      Upon error, the function returns the empty string and sets `ERRNO'.
 
+`BEGIN { PROCINFO["readfile"] = 1 }'
+     In addition, the extension adds an input parser that is activated
+     if `PROCINFO["readfile"]' exists.  When activated, each input file
+     is returned in its entirety as `$0'.  `RT' is set to the null
+     string.
+
    Here is an example:
 
      @load "readfile"
@@ -24762,9 +25542,8 @@ File: gawk.info,  Node: Extension Sample Time,  Prev: Extension Sample API Tests
 16.7.12 Extension Time Functions
 --------------------------------
 
-These functions can be used either by invoking `gawk' with a
-command-line argument of `-l time' or by inserting `@load "time"' in
-your script.
+The `time' extension adds two functions, named `gettimeofday()' and
+`sleep()', as follows:
 
 `@load "time"'
      This is how you load the extension.
@@ -24776,7 +25555,7 @@ your script.
      have sub-second precision, but the actual precision may vary based
      on the platform.  If the standard C `gettimeofday()' system call
      is available on this platform, then it simply returns the value.
-     Otherwise, if on Windows, it tries to use
+     Otherwise, if on MS-Windows, it tries to use
      `GetSystemTimeAsFileTime()'.
 
 `result = sleep(SECONDS)'
@@ -24789,7 +25568,7 @@ your script.
      delay.
 
 
-File: gawk.info,  Node: gawkextlib,  Prev: Extension Samples,  Up: Dynamic Extensions
+File: gawk.info,  Node: gawkextlib,  Next: Extension summary,  Prev: Extension Samples,  Up: Dynamic Extensions
 
 16.8 The `gawkextlib' Project
 =============================
@@ -24799,11 +25578,13 @@ provides a number of `gawk' extensions, including one for processing
 XML files.  This is the evolution of the original `xgawk' (XML `gawk')
 project.
 
-   As of this writing, there are four extensions:
+   As of this writing, there are five extensions:
 
    * XML parser extension, using the Expat
      (http://expat.sourceforge.net) XML parsing library.
 
+   * PDF extension.
+
    * PostgreSQL extension.
 
    * GD graphics library extension.
@@ -24816,7 +25597,7 @@ Time::) was originally from this project but has been moved in to the
 main `gawk' distribution.
 
    You can check out the code for the `gawkextlib' project using the
-GIT (http://git-scm.com) distributed source code control system.  The
+Git (http://git-scm.com) distributed source code control system.  The
 command is as follows:
 
      git clone git://git.code.sf.net/p/gawkextlib/code gawkextlib-code
@@ -24827,7 +25608,7 @@ parser library installed in order to build and use the XML extension.
    In addition, you must have the GNU Autotools installed (Autoconf
 (http://www.gnu.org/software/autoconf), Automake
 (http://www.gnu.org/software/automake), Libtool
-(http://www.gnu.org/software/libtool), and Gettext
+(http://www.gnu.org/software/libtool), and GNU `gettext'
 (http://www.gnu.org/software/gettext)).
 
    The simple recipe for building and testing `gawkextlib' is as
@@ -24857,6 +25638,115 @@ users, please consider doing so through the `gawkextlib' project.  See
 the project's web site for more information.
 
 
+File: gawk.info,  Node: Extension summary,  Next: Extension Exercises,  Prev: gawkextlib,  Up: Dynamic Extensions
+
+16.9 Summary
+============
+
+   * You can write extensions (sometimes called plug-ins) for `gawk' in
+     C or C++ using the Application Programming Interface (API) defined
+     by the `gawk' developers.
+
+   * Extensions must have a license compatible with the GNU General
+     Public License (GPL), and they must assert that fact by declaring
+     a variable named `plugin_is_GPL_compatible'.
+
+   * Communication between `gawk' and an extension is two-way.  `gawk'
+     passes a `struct' to the extension which contains various data
+     fields and function pointers.  The extension can then call into
+     `gawk' via the supplied function pointers to accomplish certain
+     tasks.
+
+   * One of these tasks is to "register" the name and implementation of
+     a new `awk'-level function with `gawk'.  The implementation takes
+     the form of a C function pointer with a defined signature.  By
+     convention, implementation functions are named `do_XXXX()' for
+     some `awk'-level function `XXXX()'.
+
+   * The API is defined in a header file named `gawkpi.h'. You must
+     include a number of standard header files _before_ including it in
+     your source file.
+
+   * API function pointers are provided for the following kinds of
+     operations:
+
+        * Registration functions. You may register extension functions,
+          exit callbacks, a version string, input parsers, output
+          wrappers, and two-way processors.
+
+        * Printing fatal, warning, and "lint" warning messages.
+
+        * Updating `ERRNO', or unsetting it.
+
+        * Accessing parameters, including converting an undefined
+          parameter into an array.
+
+        * Symbol table access: retrieving a global variable, creating
+          one, or changing one.
+
+        * Allocating, reallocating, and releasing memory.
+
+        * Creating and releasing cached values; this provides an
+          efficient way to use values for multiple variables and can be
+          a big performance win.
+
+        * Manipulating arrays: retrieving, adding, deleting, and
+          modifying elements; getting the count of elements in an array;
+          creating a new array; clearing an array; and flattening an
+          array for easy C style looping over all its indices and
+          elements
+
+   * The API defines a number of standard data types for representing
+     `awk' values, array elements, and arrays.
+
+   * The API provide convenience functions for constructing values.  It
+     also provides memory management functions to ensure compatibility
+     between memory allocated by `gawk' and memory allocated by an
+     extension.
+
+   * _All_ memory passed from `gawk' to an extension must be treated as
+     read-only by the extension.
+
+   * _All_ memory passed from an extension to `gawk' must come from the
+     API's memory allocation functions. `gawk' takes responsibility for
+     the memory and will release it when appropriate.
+
+   * The API provides information about the running version of `gawk' so
+     that an extension can make sure it is compatible with the `gawk'
+     that loaded it.
+
+   * It is easiest to start a new extension by copying the boilerplate
+     code described in this major node.  Macros in the `gawkapi.h' make
+     this easier to do.
+
+   * The `gawk' distribution includes a number of small but useful
+     sample extensions. The `gawkextlib' project includes several more,
+     larger, extensions.  If you wish to write an extension and
+     contribute it to the community of `gawk' users, the `gawkextlib'
+     project should be the place to do so.
+
+
+
+File: gawk.info,  Node: Extension Exercises,  Prev: Extension summary,  Up: Dynamic Extensions
+
+16.10 Exercises
+===============
+
+  1. Add functions to implement system calls such as `chown()',
+     `chmod()', and `umask()' to the file operations extension
+     presented in *note Internal File Ops::.
+
+  2. (Hard.)  How would you provide namespaces in `gawk', so that the
+     names of functions in different extensions don't conflict with
+     each other?  If you come up with a really good scheme, contact the
+     `gawk' maintainer to tell him about it.
+
+  3. Write a wrapper script that provides an interface similar to `sed
+     -i' for the "inplace" extension presented in *note Extension
+     Sample Inplace::.
+
+
+
 File: gawk.info,  Node: Language History,  Next: Installation,  Prev: Dynamic Extensions,  Up: Top
 
 Appendix A The Evolution of the `awk' Language
@@ -24867,7 +25757,7 @@ the POSIX specification.  Many long-time `awk' users learned `awk'
 programming with the original `awk' implementation in Version 7 Unix.
 (This implementation was the basis for `awk' in Berkeley Unix, through
 4.3-Reno.  Subsequent versions of Berkeley Unix, and some systems
-derived from 4.4BSD-Lite, use various versions of `gawk' for their
+derived from 4.4BSD-Lite, used various versions of `gawk' for their
 `awk'.)  This major node briefly describes the evolution of the `awk'
 language, with cross-references to other parts of the Info file where
 you can find more information.
@@ -24883,9 +25773,11 @@ you can find more information.
                                 `awk'.
 * POSIX/GNU::                   The extensions in `gawk' not in POSIX
                                 `awk'.
+* Feature History::             The history of the features in `gawk'.
 * Common Extensions::           Common Extensions Summary.
 * Ranges and Locales::          How locales used to affect regexp ranges.
 * Contributors::                The major contributors to `gawk'.
+* History summary::             History summary.
 
 
 File: gawk.info,  Node: V7/SVR3.1,  Next: SVR4,  Up: Language History
@@ -25061,7 +25953,7 @@ in his version of `awk'.
 available in his `awk'.
 
 
-File: gawk.info,  Node: POSIX/GNU,  Next: Common Extensions,  Prev: BTL,  Up: Language History
+File: gawk.info,  Node: POSIX/GNU,  Next: Feature History,  Prev: BTL,  Up: Language History
 
 A.5 Extensions in `gawk' Not in POSIX `awk'
 ===========================================
@@ -25213,12 +26105,399 @@ the current version of `gawk'.
 
         - Prestandard VAX C compiler for VAX/VMS
 
+        - GCC for VAX and Alpha has not been tested for a while.
+
+
+
+
+File: gawk.info,  Node: Feature History,  Next: Common Extensions,  Prev: POSIX/GNU,  Up: Language History
+
+A.6 History of `gawk' Features
+==============================
+
+This minor node describes the features in `gawk' over and above those
+in POSIX `awk', in the order they were added to `gawk'.
+
+   Version 2.10 of `gawk' introduced the following features:
+
+   * The `AWKPATH' environment variable for specifying a path search for
+     the `-f' command-line option (*note Options::).
+
+   * The `IGNORECASE' variable and its effects (*note
+     Case-sensitivity::).
+
+   * The `/dev/stdin', `/dev/stdout', `/dev/stderr' and `/dev/fd/N'
+     special file names (*note Special Files::).
+
+   Version 2.13 of `gawk' introduced the following features:
+
+   * The `FIELDWIDTHS' variable and its effects (*note Constant Size::).
+
+   * The `systime()' and `strftime()' built-in functions for obtaining
+     and printing timestamps (*note Time Functions::).
+
+   * Additional command-line options (*note Options::):
+
+        - The `-W lint' option to provide error and portability checking
+          for both the source code and at runtime.
+
+        - The `-W compat' option to turn off the GNU extensions.
+
+        - The `-W posix' option for full POSIX compliance.
+
+   Version 2.14 of `gawk' introduced the following feature:
+
+   * The `next file' statement for skipping to the next data file
+     (*note Nextfile Statement::).
+
+   Version 2.15 of `gawk' introduced the following features:
+
+   * New variables (*note Built-in Variables::):
+
+        - `ARGIND', which tracks the movement of `FILENAME' through
+          `ARGV'.
+
+        - `ERRNO', which contains the system error message when
+          `getline' returns -1 or `close()' fails.
+
+   * The `/dev/pid', `/dev/ppid', `/dev/pgrpid', and `/dev/user'
+     special file names. These have since been removed.
+
+   * The ability to delete all of an array at once with `delete ARRAY'
+     (*note Delete::).
+
+   * Command line option changes (*note Options::):
+
+        - The ability to use GNU-style long-named options that start
+          with `--'.
+
+        - The `--source' option for mixing command-line and library-file
+          source code.
+
+   Version 3.0 of `gawk' introduced the following features:
+
+   * New or changed variables:
+
+        - `IGNORECASE' changed, now applying to string comparison as
+          well as regexp operations (*note Case-sensitivity::).
+
+        - `RT', which contains the input text that matched `RS' (*note
+          Records::).
+
+   * Full support for both POSIX and GNU regexps (*note Regexp::).
+
+   * The `gensub()' function for more powerful text manipulation (*note
+     String Functions::).
+
+   * The `strftime()' function acquired a default time format, allowing
+     it to be called with no arguments (*note Time Functions::).
+
+   * The ability for `FS' and for the third argument to `split()' to be
+     null strings (*note Single Character Fields::).
+
+   * The ability for `RS' to be a regexp (*note Records::).
+
+   * The `next file' statement became `nextfile' (*note Nextfile
+     Statement::).
+
+   * The `fflush()' function from Brian Kernighan's `awk' (then at Bell
+     Laboratories; *note I/O Functions::).
+
+   * New command line options:
+
+        - The `--lint-old' option to warn about constructs that are not
+          available in the original Version 7 Unix version of `awk'
+          (*note V7/SVR3.1::).
+
+        - The `-m' option from Brian Kernighan's `awk'.  (He was still
+          at Bell Laboratories at the time.)  This was later removed
+          from both his `awk' and from `gawk'.
+
+        - The `--re-interval' option to provide interval expressions in
+          regexps (*note Regexp Operators::).
+
+        - The `--traditional' option was added as a better name for
+          `--compat' (*note Options::).
+
+   * The use of GNU Autoconf to control the configuration process
+     (*note Quick Installation::).
+
+   * Amiga support.  This has since been removed.
+
+
+   Version 3.1 of `gawk' introduced the following features:
+
+   * New variables (*note Built-in Variables::):
+
+        - `BINMODE', for non-POSIX systems, which allows binary I/O for
+          input and/or output files (*note PC Using::).
+
+        - `LINT', which dynamically controls lint warnings.
+
+        - `PROCINFO', an array for providing process-related
+          information.
+
+        - `TEXTDOMAIN', for setting an application's
+          internationalization text domain (*note
+          Internationalization::).
+
+   * The ability to use octal and hexadecimal constants in `awk'
+     program source code (*note Nondecimal-numbers::).
+
+   * The `|&' operator for two-way I/O to a coprocess (*note Two-way
+     I/O::).
+
+   * The `/inet' special files for TCP/IP networking using `|&' (*note
+     TCP/IP Networking::).
+
+   * The optional second argument to `close()' that allows closing one
+     end of a two-way pipe to a coprocess (*note Two-way I/O::).
+
+   * The optional third argument to the `match()' function for
+     capturing text-matching subexpressions within a regexp (*note
+     String Functions::).
+
+   * Positional specifiers in `printf' formats for making translations
+     easier (*note Printf Ordering::).
+
+   * A number of new built-in functions:
+
+        - The `asort()' and `asorti()' functions for sorting arrays
+          (*note Array Sorting::).
+
+        - The `bindtextdomain()', `dcgettext()' and `dcngettext()'
+          functions for internationalization (*note Programmer i18n::).
+
+        - The `extension()' function and the ability to add new
+          built-in functions dynamically (*note Dynamic Extensions::).
+
+        - The `mktime()' function for creating timestamps (*note Time
+          Functions::).
+
+        - The `and()', `or()', `xor()', `compl()', `lshift()',
+          `rshift()', and `strtonum()' functions (*note Bitwise
+          Functions::).
+
+   * The support for `next file' as two words was removed completely
+     (*note Nextfile Statement::).
+
+   * Additional command-line options (*note Options::):
+
+        - The `--dump-variables' option to print a list of all global
+          variables.
+
+        - The `--exec' option, for use in CGI scripts.
+
+        - The `--gen-po' command-line option and the use of a leading
+          underscore to mark strings that should be translated (*note
+          String Extraction::).
+
+        - The `--non-decimal-data' option to allow non-decimal input
+          data (*note Nondecimal Data::).
+
+        - The `--profile' option and `pgawk', the profiling version of
+          `gawk', for producing execution profiles of `awk' programs
+          (*note Profiling::).
+
+        - The `--use-lc-numeric' option to force `gawk' to use the
+          locale's decimal point for parsing input data (*note
+          Conversion::).
+
+   * The use of GNU Automake to help in standardizing the configuration
+     process (*note Quick Installation::).
+
+   * The use of GNU `gettext' for `gawk''s own message output (*note
+     Gawk I18N::).
+
+   * BeOS support. This was later removed.
+
+   * Tandem support. This was later removed.
+
+   * The Atari port became officially unsupported and was later removed
+     entirely.
+
+   * The source code changed to use ISO C standard-style function
+     definitions.
+
+   * POSIX compliance for `sub()' and `gsub()' (*note Gory Details::).
+
+   * The `length()' function was extended to accept an array argument
+     and return the number of elements in the array (*note String
+     Functions::).
+
+   * The `strftime()' function acquired a third argument to enable
+     printing times as UTC (*note Time Functions::).
+
+   Version 4.0 of `gawk' introduced the following features:
+
+   * Variable additions:
+
+        - `FPAT', which allows you to specify a regexp that matches the
+          fields, instead of matching the field separator (*note
+          Splitting By Content::).
+
+        - If `PROCINFO["sorted_in"]' exists, `for(iggy in foo)' loops
+          sort the indices before looping over them.  The value of this
+          element provides control over how the indices are sorted
+          before the loop traversal starts (*note Controlling
+          Scanning::).
+
+        - `PROCINFO["strftime"]', which holds the default format for
+          `strftime()' (*note Time Functions::).
+
+   * The special files `/dev/pid', `/dev/ppid', `/dev/pgrpid' and
+     `/dev/user' were removed.
+
+   * Support for IPv6 was added via the `/inet6' special file.
+     `/inet4' forces IPv4 and `/inet' chooses the system default, which
+     is probably IPv4 (*note TCP/IP Networking::).
+
+   * The use of `\s' and `\S' escape sequences in regular expressions
+     (*note GNU Regexp Operators::).
+
+   * Interval expressions became part of default regular expressions
+     (*note Regexp Operators::).
+
+   * POSIX character classes work even with `--traditional' (*note
+     Regexp Operators::).
+
+   * `break' and `continue' became invalid outside a loop, even with
+     `--traditional' (*note Break Statement::, and also see *note
+     Continue Statement::).
+
+   * `fflush()', `nextfile', and `delete ARRAY' are allowed if
+     `--posix' or `--traditional', since they are all now part of POSIX.
+
+   * An optional third argument to `asort()' and `asorti()', specifying
+     how to sort (*note String Functions::).
+
+   * The behavior of `fflush()' changed to match Brian Kernighan's `awk'
+     and for POSIX; now both `fflush()' and `fflush("")' flush all open
+     output redirections (*note I/O Functions::).
+
+   * The `isarray()' function which distinguishes if an item is an array
+     or not, to make it possible to traverse arrays of arrays (*note
+     Type Functions::).
+
+   * The `patsplit()' function which gives the same capability as
+     `FPAT', for splitting (*note String Functions::).
+
+   * An optional fourth argument to the `split()' function, which is an
+     array to hold the values of the separators (*note String
+     Functions::).
+
+   * Arrays of arrays (*note Arrays of Arrays::).
+
+   * The `BEGINFILE' and `ENDFILE' special patterns (*note
+     BEGINFILE/ENDFILE::).
+
+   * Indirect function calls (*note Indirect Calls::).
+
+   * `switch' / `case' are enabled by default (*note Switch
+     Statement::).
+
+   * Command line option changes (*note Options::):
+
+        - The `-b' and `--characters-as-bytes' options which prevent
+          `gawk' from treating input as a multibyte string.
+
+        - The redundant `--compat', `--copyleft', and `--usage' long
+          options were removed.
+
+        - The `--gen-po' option was finally renamed to the correct
+          `--gen-pot'.
+
+        - The `--sandbox' option which disables certain features.
+
+        - All long options acquired corresponding short options, for
+          use in `#!' scripts.
+
+   * Directories named on the command line now produce a warning, not a
+     fatal error, unless `--posix' or `--traditional' are used (*note
+     Command line directories::).
+
+   * The `gawk' internals were rewritten, bringing the `dgawk' debugger
+     and possibly improved performance (*note Debugger::).
+
+   * Per the GNU Coding Standards, dynamic extensions must now define a
+     global symbol indicating that they are GPL-compatible (*note
+     Plugin License::).
+
+   * In POSIX mode, string comparisons use `strcoll()' / `wcscoll()'
+     (*note POSIX String Comparison::).
+
+   * The option for raw sockets was removed, since it was never
+     implemented (*note TCP/IP Networking::).
+
+   * Ranges of the form `[d-h]' are treated as if they were in the C
+     locale, no matter what kind of regexp is being used, and even if
+     `--posix' (*note Ranges and Locales::).
+
+   * Support was removed for the following systems:
+
+        - Atari
+
+        - Amiga
+
+        - BeOS
+
+        - Cray
+
+        - MIPS RiscOS
+
+        - MS-DOS with Microsoft Compiler
+
+        - MS-Windows with Microsoft Compiler
+
+        - NeXT
+
+        - SunOS 3.x, Sun 386 (Road Runner)
+
+        - Tandem (non-POSIX)
+
+        - Prestandard VAX C compiler for VAX/VMS
+
+   Version 4.1 of `gawk' introduced the following features:
+
+   * Three new arrays: `SYMTAB', `FUNCTAB', and
+     `PROCINFO["identifiers"]' (*note Auto-set::).
+
+   * The three executables `gawk', `pgawk', and `dgawk', were merged
+     into one, named just `gawk'.  As a result the command line options
+     changed.
+
+   * Command line option changes (*note Options::):
+
+        - The `-D' option invokes the debugger.
+
+        - The `-i' and `--include' options load `awk' library files.
+
+        - The `-l' and `--load' options load compiled dynamic
+          extensions.
+
+        - The `-M' and `--bignum' options enable MPFR.
+
+        - The `-o' only does pretty-printing.
+
+        - The `-p' option is used for profiling.
+
+        - The `-R' option was removed.
+
+   * Support for high precision arithmetic with MPFR.  (*note Arbitrary
+     Precision Arithmetic::).
+
+   * The `and()', `or()' and `xor()' functions changed to allow any
+     number of arguments, with a minimum of two (*note Bitwise
+     Functions::).
+
+   * The dynamic extension interface was completely redone (*note
+     Dynamic Extensions::).
 
 
 
-File: gawk.info,  Node: Common Extensions,  Next: Ranges and Locales,  Prev: POSIX/GNU,  Up: Language History
+File: gawk.info,  Node: Common Extensions,  Next: Ranges and Locales,  Prev: Feature History,  Up: Language History
 
-A.6 Common Extensions Summary
+A.7 Common Extensions Summary
 =============================
 
 This minor node summarizes the common extensions supported by `gawk',
@@ -25228,18 +26507,18 @@ available versions of `awk' (*note Other Versions::).
 Feature                      BWK Awk   Mawk   GNU Awk
 -------------------------------------------------------- 
 `\x' Escape sequence         X         X      X
-`RS' as regexp                         X      X
 `FS' as null string          X         X      X
-`/dev/stdin' special file    X                X
+`/dev/stdin' special file    X         X      X
 `/dev/stdout' special file   X         X      X
 `/dev/stderr' special file   X         X      X
-`**' and `**=' operators     X                X
+`delete' without subscript   X         X      X
 `fflush()' function          X         X      X
-`func' keyword               X                X
+`length()' of an array       X         X      X
 `nextfile' statement         X         X      X
-`delete' without subscript   X         X      X
-`length()' of an array       X                X
+`**' and `**=' operators     X                X
+`func' keyword               X                X
 `BINMODE' variable                     X      X
+`RS' as regexp                         X      X
 Time related functions                 X      X
 
    (Technically speaking, as of late 2012, `fflush()', `delete ARRAY',
@@ -25249,7 +26528,7 @@ POSIX.)
 
 File: gawk.info,  Node: Ranges and Locales,  Next: Contributors,  Prev: Common Extensions,  Up: Language History
 
-A.7 Regexp Ranges and Locales: A Long Sad Story
+A.8 Regexp Ranges and Locales: A Long Sad Story
 ===============================================
 
 This minor node describes the confusing history of ranges within
@@ -25272,7 +26551,7 @@ as working in this fashion, and in particular, would teach that the
 `[A-Z]' was the "correct" way to match uppercase letters.  And indeed,
 this was true.(1)
 
-   The 1993 POSIX standard introduced the idea of locales (*note
+   The 1992 POSIX standard introduced the idea of locales (*note
 Locales::).  Since many locales include other letters besides the plain
 twenty-six letters of the American English alphabet, the POSIX standard
 added character classes (*note Bracket Expressions::) as a way to match
@@ -25335,17 +26614,17 @@ of range expressions was _undefined_.(3)
    By using this lovely technical term, the standard gives license to
 implementors to implement ranges in whatever way they choose.  The
 `gawk' maintainer chose to apply the pre-POSIX meaning in all cases:
-the default regexp matching; with `--traditional', and with `--posix';
+the default regexp matching; with `--traditional' and with `--posix';
 in all cases, `gawk' remains POSIX compliant.
 
    ---------- Footnotes ----------
 
    (1) And Life was good.
 
-   (2) And thus was born the Campain for Rational Range Interpretation
-(or RRI). A number of GNU tools, such as `grep' and `sed', have either
-implemented this change, or will soon.  Thanks to Karl Berry for
-coining the phrase "Rational Range Interpretation."
+   (2) And thus was born the Campaign for Rational Range Interpretation
+(or RRI). A number of GNU tools have either implemented this change, or
+will soon.  Thanks to Karl Berry for coining the phrase "Rational Range
+Interpretation."
 
    (3) See the standard
 (http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03_05)
@@ -25353,9 +26632,9 @@ and its rationale
 (http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html#tag_21_09_03_05).
 
 
-File: gawk.info,  Node: Contributors,  Prev: Ranges and Locales,  Up: Language History
+File: gawk.info,  Node: Contributors,  Next: History summary,  Prev: Ranges and Locales,  Up: Language History
 
-A.8 Major Contributors to `gawk'
+A.9 Major Contributors to `gawk'
 ================================
 
      Always give credit where credit is due.  -- Anonymous
@@ -25399,8 +26678,8 @@ Info file, in approximate chronological order:
 
    * Michal Jaegermann provided the port to Atari systems and its
      documentation.  (This port is no longer supported.)  He continues
-     to provide portability checking with DEC Alpha systems, and has
-     done a lot of work to make sure `gawk' works on non-32-bit systems.
+     to provide portability checking, and has done a lot of work to
+     make sure `gawk' works on non-32-bit systems.
 
    * Fred Fish provided the port to Amiga systems and its documentation.
      (With Fred's sad passing, this is no longer supported.)
@@ -25455,13 +26734,17 @@ Info file, in approximate chronological order:
    * Patrick T.J. McPhee contributed the code for dynamic loading in
      Windows32 environments.  (This is no longer supported)
 
+   * Anders Wallin helped keep the VMS port going for several years.
+
+   * Assaf Gordon contributed the code to implement the `--sandbox'
+     option.
+
    * John Haque made the following contributions:
 
         - The modifications to convert `gawk' into a byte-code
           interpreter, including the debugger.
 
-        - The addition of true multidimensional arrays.  *note Arrays
-          of Arrays::.
+        - The addition of true arrays of arrays.
 
         - The additional modifications for support of arbitrary
           precision arithmetic.
@@ -25476,17 +26759,56 @@ Info file, in approximate chronological order:
         - The improved array sorting features were driven by John
           together with Pat Rankin.
 
+   * Panos Papadopoulos contributed the original text for *note Include
+     Files::.
+
    * Efraim Yawitz contributed the original text for *note Debugger::.
 
    * The development of the extension API first released with `gawk'
      4.1 was driven primarily by Arnold Robbins and Andrew Schorr, with
      notable contributions from the rest of the development team.
 
+   * Antonio Giovanni Colombo rewrote a number of examples in the early
+     chapters that were severely dated, for which I am incredibly
+     grateful.
+
    * Arnold Robbins has been working on `gawk' since 1988, at first
      helping David Trueman, and as the primary maintainer since around
      1994.
 
 
+File: gawk.info,  Node: History summary,  Prev: Contributors,  Up: Language History
+
+A.10 Summary
+============
+
+   * The `awk' language has evolved over time. The first release was
+     with V7 Unix circa 1978.  In 1987 for System V Release 3.1, major
+     additions, including user-defined functions, were made to the
+     language.  Additional changes were made for System V Release 4, in
+     1989.  Since then, further minor changes happen under the auspices
+     of the POSIX standard.
+
+   * Brian Kernighan's `awk' provides a small number of extensions that
+     are implemented in common with other versions of `awk'.
+
+   * `gawk' provides a large number of extensions over POSIX `awk'.
+     They can be disabled with either the `--traditional' or `--posix'
+     options.
+
+   * The interaction of POSIX locales and regexp matching in `gawk' has
+     been confusing over the years. Today, `gawk' implements Rational
+     Range Interpretation, where ranges of the form `[a-z]' match
+     _only_ the characters numerically between `a' through `z' in the
+     machine's native character set.  Usually this is ASCII but it can
+     be EBCDIC on IBM S/390 systems.
+
+   * Many people have contributed to `gawk' development over the years.
+     We hope that the list provided in this major node is complete and
+     gives the appropriate credit where credit is due.
+
+
+
 File: gawk.info,  Node: Installation,  Next: Notes,  Prev: Language History,  Up: Top
 
 Appendix B Installing `gawk'
@@ -25507,6 +26829,7 @@ people who did the respective ports.
 * Bugs::                        Reporting Problems and Bugs.
 * Other Versions::              Other freely available `awk'
                                 implementations.
+* Installation summary::        Summary of installation.
 
 
 File: gawk.info,  Node: Gawk Distribution,  Next: Unix Installation,  Up: Installation
@@ -25529,7 +26852,7 @@ File: gawk.info,  Node: Getting,  Next: Extracting,  Up: Gawk Distribution
 B.1.1 Getting the `gawk' Distribution
 -------------------------------------
 
-There are three ways to get GNU software:
+There are two ways to get GNU software:
 
    * Copy it from someone else who already has it.
 
@@ -25538,7 +26861,7 @@ There are three ways to get GNU software:
      supported.  If you have the `wget' program, you can use a command
      like the following:
 
-          wget http://ftp.gnu.org/gnu/gawk/gawk-4.1.0.tar.gz
+          wget http://ftp.gnu.org/gnu/gawk/gawk-4.1.1.tar.gz
 
    The GNU software archive is mirrored around the world.  The
 up-to-date list of mirror sites is available from the main FSF web site
@@ -25557,26 +26880,25 @@ compression programs: `gzip', `bzip2', and `xz'. For simplicity, the
 rest of these instructions assume you are using the one compressed with
 the GNU Zip program, `gzip'.
 
-   Once you have the distribution (for example, `gawk-4.1.0.tar.gz'),
+   Once you have the distribution (for example, `gawk-4.1.1.tar.gz'),
 use `gzip' to expand the file and then use `tar' to extract it.  You
 can use the following pipeline to produce the `gawk' distribution:
 
-     # Under System V, add 'o' to the tar options
-     gzip -d -c gawk-4.1.0.tar.gz | tar -xvpf -
+     gzip -d -c gawk-4.1.1.tar.gz | tar -xvpf -
 
    On a system with GNU `tar', you can let `tar' do the decompression
 for you:
 
-     tar -xvpzf gawk-4.1.0.tar.gz
+     tar -xvpzf gawk-4.1.1.tar.gz
 
-Extracting the archive creates a directory named `gawk-4.1.0' in the
+Extracting the archive creates a directory named `gawk-4.1.1' in the
 current directory.
 
    The distribution file name is of the form `gawk-V.R.P.tar.gz'.  The
 V represents the major version of `gawk', the R represents the current
 release of version V, and the P represents a "patch level", meaning
 that minor bugs have been fixed in the release.  The current patch
-level is 0, but when retrieving distributions, you should get the
+level is 1, but when retrieving distributions, you should get the
 version with the highest version, release, and patch level.  (Note,
 however, that patch levels greater than or equal to 70 denote "beta" or
 nonproduction software; you might not want to retrieve such a version
@@ -25697,8 +27019,8 @@ Various `.c', `.y', and `.h' files
 
 `Makefile.am'
 `*/Makefile.am'
-     Files used by the GNU `automake' software for generating the
-     `Makefile.in' files used by `autoconf' and `configure'.
+     Files used by the GNU Automake software for generating the
+     `Makefile.in' files used by Autoconf and `configure'.
 
 `Makefile.in'
 `aclocal.m4'
@@ -25737,6 +27059,11 @@ Various `.c', `.y', and `.h' files
      of the programs in this Info file are available in appropriate
      subdirectories of `awklib/eg'.
 
+`extension/*'
+     The source code, manual pages, and infrastructure files for the
+     sample extensions included with `gawk'.  *Note Dynamic
+     Extensions::, for more information.
+
 `posix/*'
      Files needed for building `gawk' on POSIX-compliant systems.
 
@@ -25745,8 +27072,8 @@ Various `.c', `.y', and `.h' files
      PC Installation::, for details).
 
 `vms/*'
-     Files needed for building `gawk' under VMS (*note VMS
-     Installation::, for details).
+     Files needed for building `gawk' under Vax/VMS and OpenVMS (*note
+     VMS Installation::, for details).
 
 `test/*'
      A test suite for `gawk'.  You can use `make check' from the
@@ -25781,11 +27108,11 @@ Unix-derived systems, GNU/Linux, BSD-based systems, and the Cygwin
 environment for MS-Windows.
 
    After you have extracted the `gawk' distribution, `cd' to
-`gawk-4.1.0'.  Like most GNU software, `gawk' is configured
+`gawk-4.1.1'.  Like most GNU software, `gawk' is configured
 automatically for your system by running the `configure' program.  This
 program is a Bourne shell script that is generated automatically using
-GNU `autoconf'.  (The `autoconf' software is described fully starting
-with *note (Autoconf)Top:: autoconf,Autoconf--Generating Automatic
+GNU Autoconf.  (The Autoconf software is described fully starting with
+*note (Autoconf)Top:: autoconf,Autoconf--Generating Automatic
 Configuration Scripts.)
 
    To configure `gawk', simply run `configure':
@@ -25820,8 +27147,8 @@ failure is not described there, please send in a bug report (*note
 Bugs::).
 
    Of course, once you've built `gawk', it is likely that you will wish
-to install it.  To do so, you need to run the command `make check', as
-a user with the appropriate permissions.  How to do this varies by
+to install it.  To do so, you need to run the command `make install',
+as a user with the appropriate permissions.  How to do this varies by
 system, but on many systems you can use the `sudo' command to do so.
 The command then becomes `sudo make install'. It is likely that you
 will be asked for your password, and you will have to have been set up
@@ -25863,8 +27190,8 @@ command line when compiling `gawk' from scratch, including:
      improvement.
 
 `--with-whiny-user-strftime'
-     Force use of the included version of the `strftime()' function for
-     deficient systems.
+     Force use of the included version of the C `strftime()' function
+     for deficient systems.
 
    Use the command `./configure --help' to see the full list of options
 that `configure' supplies.
@@ -25908,9 +27235,9 @@ any constants that `configure' defined and should not have.  `custom.h'
 is automatically included by `config.h'.
 
    It is also possible that the `configure' program generated by
-`autoconf' will not work on your system in some other fashion.  If you
-do have a problem, the file `configure.ac' is the input for `autoconf'.
-You may be able to change this file and generate a new version of
+Autoconf will not work on your system in some other fashion.  If you do
+have a problem, the file `configure.ac' is the input for Autoconf.  You
+may be able to change this file and generate a new version of
 `configure' that works on your system (*note Bugs::, for information on
 how to report problems in configuring `gawk').  The same mechanism may
 be used to send in updates to `configure.ac' and/or `custom.h'.
@@ -25939,14 +27266,14 @@ B.3.1 Installation on PC Operating Systems
 This minor node covers installation and usage of `gawk' on x86 machines
 running MS-DOS, any version of MS-Windows, or OS/2.  In this minor
 node, the term "Windows32" refers to any of Microsoft
-Windows-95/98/ME/NT/2000/XP/Vista/7.
+Windows-95/98/ME/NT/2000/XP/Vista/7/8.
 
-   The limitations of MS-DOS (and MS-DOS shells under Windows32 or
-OS/2) has meant that various "DOS extenders" are often used with
-programs such as `gawk'.  The varying capabilities of Microsoft Windows
-3.1 and Windows32 can add to the confusion.  For an overview of the
-considerations, please refer to `README_d/README.pc' in the
-distribution.
+   The limitations of MS-DOS (and MS-DOS shells under the other
+operating systems) has meant that various "DOS extenders" are often
+used with programs such as `gawk'.  The varying capabilities of
+Microsoft Windows 3.1 and Windows32 can add to the confusion.  For an
+overview of the considerations, please refer to `README_d/README.pc' in
+the distribution.
 
 * Menu:
 
@@ -26005,13 +27332,13 @@ B.3.1.2 Compiling `gawk' for PC Operating Systems
 .................................................
 
 `gawk' can be compiled for MS-DOS, Windows32, and OS/2 using the GNU
-development tools from DJ Delorie (DJGPP: MS-DOS only) or Eberhard
-Mattes (EMX: MS-DOS, Windows32 and OS/2).  The file
-`README_d/README.pc' in the `gawk' distribution contains additional
-notes, and `pc/Makefile' contains important information on compilation
-options.
+development tools from DJ Delorie (DJGPP: MS-DOS only), MinGW
+(Windows32) or Eberhard Mattes (EMX: MS-DOS, Windows32 and OS/2).  The
+file `README_d/README.pc' in the `gawk' distribution contains
+additional notes, and `pc/Makefile' contains important information on
+compilation options.
 
-   To build `gawk' for MS-DOS and Windows32, copy the files in the `pc'
+To build `gawk' for MS-DOS and Windows32, copy the files in the `pc'
 directory (_except_ for `ChangeLog') to the directory with the rest of
 the `gawk' sources, then invoke `make' with the appropriate target name
 as an argument to build `gawk'.  The `Makefile' copied from the `pc'
@@ -26071,7 +27398,12 @@ other set of (self-consistent) environment variables and compiler flags.
      NOTE: Ancient OS/2 ports of GNU `make' are not able to handle the
      Makefiles of this package.  If you encounter any problems with
      `make', try GNU Make 3.79.1 or later versions.  You should find
-     the latest version on `ftp://hobbes.nmsu.edu/pub/os2/'.
+     the latest version on `ftp://hobbes.nmsu.edu/pub/os2/'.(1)
+
+   ---------- Footnotes ----------
+
+   (1) As of May, 2014, this site is still there, but the author could
+not find a package for GNU Make.
 
 
 File: gawk.info,  Node: PC Testing,  Next: PC Using,  Prev: PC Compiling,  Up: PC Installation
@@ -26104,20 +27436,19 @@ File: gawk.info,  Node: PC Using,  Next: Cygwin,  Prev: PC Testing,  Up: PC Inst
 B.3.1.4 Using `gawk' on PC Operating Systems
 ............................................
 
-With the exception of the Cygwin environment, the `|&' operator and
-TCP/IP networking (*note TCP/IP Networking::) are not supported for
-MS-DOS or MS-Windows.  EMX (OS/2 only) does support at least the `|&'
-operator.
+Under MS-DOS and MS-Windows, the Cygwin and MinGW environments support
+both the `|&' operator and TCP/IP networking (*note TCP/IP
+Networking::).  EMX (OS/2 only) supports at least the `|&' operator.
 
    The MS-DOS and MS-Windows versions of `gawk' search for program
 files as described in *note AWKPATH Variable::.  However, semicolons
 (rather than colons) separate elements in the `AWKPATH' variable.  If
 `AWKPATH' is not set or is empty, then the default search path for
-MS-Windows and MS-DOS versions is `".;c:/lib/awk;c:/gnu/lib/awk"'.
+MS-Windows and MS-DOS versions is `.;c:/lib/awk;c:/gnu/lib/awk'.
 
    The search path for OS/2 (32 bit, EMX) is determined by the prefix
 directory (most likely `/usr' or `c:/usr') that has been specified as
-an option of the `configure' script like it is the case for the Unix
+an option of the `configure' script as is the case for the Unix
 versions.  If `c:/usr' is the prefix directory then the default search
 path contains `.' and `c:/usr/share/awk'.  Additionally, to support
 binary distributions of `gawk' for OS/2 systems whose drive `c:' might
@@ -26125,7 +27456,7 @@ not support long file names or might not exist at all, there is a
 special environment variable.  If `UNIXROOT' specifies a drive then
 this specific drive is also searched for program files.  E.g., if
 `UNIXROOT' is set to `e:' the complete default search path is
-`".;c:/usr/share/awk;e:/usr/share/awk"'.
+`.;c:/usr/share/awk;e:/usr/share/awk'.
 
    An `sh'-like shell (as opposed to `command.com' under MS-DOS or
 `cmd.exe' under MS-Windows or OS/2) may be useful for `awk' programming.
@@ -26133,10 +27464,9 @@ The DJGPP collection of tools includes an MS-DOS port of Bash, and
 several shells are available for OS/2, including `ksh'.
 
    Under MS-Windows, OS/2 and MS-DOS, `gawk' (and many other text
-programs) silently translate end-of-line `"\r\n"' to `"\n"' on input
-and `"\n"' to `"\r\n"' on output.  A special `BINMODE' variable
-(c.e.)  allows control over these translations and is interpreted as
-follows:
+programs) silently translate end-of-line `\r\n' to `\n' on input and
+`\n' to `\r\n' on output.  A special `BINMODE' variable (c.e.)  allows
+control over these translations and is interpreted as follows:
 
    * If `BINMODE' is `"r"', or one, then binary mode is set on read
      (i.e., no translations on reads).
@@ -26162,11 +27492,11 @@ and cannot be changed mid-stream.
 Versions::).  `mawk' and `gawk' handle `BINMODE' similarly; however,
 `mawk' adds a `-W BINMODE=N' option and an environment variable that
 can set `BINMODE', `RS', and `ORS'.  The files `binmode[1-3].awk'
-(under `gnu/lib/awk' in some of the prepared distributions) have been
-chosen to match `mawk''s `-W BINMODE=N' option.  These can be changed
-or discarded; in particular, the setting of `RS' giving the fewest
-"surprises" is open to debate.  `mawk' uses `RS = "\r\n"' if binary
-mode is set on read, which is appropriate for files with the
+(under `gnu/lib/awk' in some of the prepared binary distributions) have
+been chosen to match `mawk''s `-W BINMODE=N' option.  These can be
+changed or discarded; in particular, the setting of `RS' giving the
+fewest "surprises" is open to debate.  `mawk' uses `RS = "\r\n"' if
+binary mode is set on read, which is appropriate for files with the
 MS-DOS-style end-of-line.
 
    To illustrate, the following examples set binary mode on writes for
@@ -26200,13 +27530,13 @@ B.3.1.5 Using `gawk' In The Cygwin Environment
 
 `gawk' can be built and used "out of the box" under MS-Windows if you
 are using the Cygwin environment (http://www.cygwin.com).  This
-environment provides an excellent simulation of Unix, using the GNU
-tools, such as Bash, the GNU Compiler Collection (GCC), GNU Make, and
-other GNU programs.  Compilation and installation for Cygwin is the
+environment provides an excellent simulation of GNU/Linux, using the
+GNU tools, such as Bash, the GNU Compiler Collection (GCC), GNU Make,
+and other GNU programs.  Compilation and installation for Cygwin is the
 same as for a Unix system:
 
-     tar -xvpzf gawk-4.1.0.tar.gz
-     cd gawk-4.1.0
+     tar -xvpzf gawk-4.1.1.tar.gz
+     cd gawk-4.1.1
      ./configure
      make
 
@@ -26214,10 +27544,6 @@ same as for a Unix system:
 on Cygwin takes considerably longer.  However, it does finish, and then
 the `make' proceeds as usual.
 
-     NOTE: The `|&' operator and TCP/IP networking (*note TCP/IP
-     Networking::) are fully supported in the Cygwin environment.  This
-     is not true for any other environment on MS-Windows.
-
 
 File: gawk.info,  Node: MSYS,  Prev: Cygwin,  Up: PC Installation
 
@@ -26235,8 +27561,8 @@ translation of `"\r\n"', since it won't.  Caveat Emptor!
 
 File: gawk.info,  Node: VMS Installation,  Prev: PC Installation,  Up: Non-Unix Installation
 
-B.3.2 How to Compile and Install `gawk' on VMS
-----------------------------------------------
+B.3.2 How to Compile and Install `gawk' on Vax/VMS and OpenVMS
+--------------------------------------------------------------
 
 This node describes how to compile and install `gawk' under VMS.  The
 older designation "VMS" is used throughout to refer to OpenVMS.
@@ -26244,51 +27570,112 @@ older designation "VMS" is used throughout to refer to OpenVMS.
 * Menu:
 
 * VMS Compilation::             How to compile `gawk' under VMS.
+* VMS Dynamic Extensions::      Compiling `gawk' dynamic extensions on
+                                VMS.
 * VMS Installation Details::    How to install `gawk' under VMS.
 * VMS Running::                 How to run `gawk' under VMS.
+* VMS GNV::                     The VMS GNV Project.
 * VMS Old Gawk::                An old version comes with some VMS systems.
 
 
-File: gawk.info,  Node: VMS Compilation,  Next: VMS Installation Details,  Up: VMS Installation
+File: gawk.info,  Node: VMS Compilation,  Next: VMS Dynamic Extensions,  Up: VMS Installation
 
 B.3.2.1 Compiling `gawk' on VMS
 ...............................
 
 To compile `gawk' under VMS, there is a `DCL' command procedure that
 issues all the necessary `CC' and `LINK' commands. There is also a
-`Makefile' for use with the `MMS' utility.  From the source directory,
-use either:
+`Makefile' for use with the `MMS' and `MMK' utilities.  From the source
+directory, use either:
+
+     $ @[.vms]vmsbuild.com
+
+or:
 
-     $ @[.VMS]VMSBUILD.COM
+     $ MMS/DESCRIPTION=[.vms]descrip.mms gawk
 
 or:
 
-     $ MMS/DESCRIPTION=[.VMS]DESCRIP.MMS GAWK
+     $ MMK/DESCRIPTION=[.vms]descrip.mms gawk
+
+   `MMK' is an open source, free, near-clone of `MMS' and can better
+handle ODS-5 volumes with upper- and lowercase file names.  `MMK' is
+available from `https://github.com/endlesssoftware/mmk'.
+
+   With ODS-5 volumes and extended parsing enabled, the case of the
+target parameter may need to be exact.
 
-   Older versions of `gawk' could be built with VAX C or GNU C on
-VAX/VMS, as well as with DEC C, but that is no longer supported.  DEC C
-(also briefly known as "Compaq C" and now known as "HP C," but referred
-to here as "DEC C") is required.  Both `VMSBUILD.COM' and `DESCRIP.MMS'
-contain some obsolete support for the older compilers but are set up to
-use DEC C by default.
+   `gawk' has been tested under VAX/VMS 7.3 and Alpha/VMS 7.3-1 using
+Compaq C V6.4, and Alpha/VMS 7.3, Alpha/VMS 7.3-2, and IA64/VMS 8.3.
+The most recent builds used HP C V7.3 on Alpha VMS 8.3 and both Alpha
+and IA64 VMS 8.4 used HP C 7.3.(1)
 
-   `gawk' has been tested under Alpha/VMS 7.3-1 using Compaq C V6.4,
-and on Alpha/VMS 7.3, Alpha/VMS 7.3-2, and IA64/VMS 8.3.(1)
+   *Note VMS GNV::, for information on building `gawk' as a PCSI kit
+that is compatible with the GNV product.
 
    ---------- Footnotes ----------
 
    (1) The IA64 architecture is also known as "Itanium."
 
 
-File: gawk.info,  Node: VMS Installation Details,  Next: VMS Running,  Prev: VMS Compilation,  Up: VMS Installation
+File: gawk.info,  Node: VMS Dynamic Extensions,  Next: VMS Installation Details,  Prev: VMS Compilation,  Up: VMS Installation
 
-B.3.2.2 Installing `gawk' on VMS
+B.3.2.2 Compiling `gawk' Dynamic Extensions on VMS
+..................................................
+
+The extensions that have been ported to VMS can be built using one of
+the following commands.
+
+     $ MMS/DESCRIPTION=[.vms]descrip.mms extensions
+
+or:
+
+     $ MMK/DESCRIPTION=[.vms]descrip.mms extensions
+
+   `gawk' uses `AWKLIBPATH' as either an environment variable or a
+logical name to find the dynamic extensions.
+
+   Dynamic extensions need to be compiled with the same compiler
+options for floating point, pointer size, and symbol name handling as
+were used to compile `gawk' itself.  Alpha and Itanium should use IEEE
+floating point.  The pointer size is 32 bits, and the symbol name
+handling should be exact case with CRC shortening for symbols longer
+than 32 bits.
+
+   For Alpha and Itanium:
+
+     /name=(as_is,short)
+     /float=ieee/ieee_mode=denorm_results
+
+   For VAX:
+
+     /name=(as_is,short)
+
+   Compile time macros need to be defined before the first VMS-supplied
+header file is included.
+
+     #if (__CRTL_VER >= 70200000) && !defined (__VAX)
+     #define _LARGEFILE 1
+     #endif
+
+     #ifndef __VAX
+     #ifdef __CRTL_VER
+     #if __CRTL_VER >= 80200000
+     #define _USE_STD_STAT 1
+     #endif
+     #endif
+     #endif
+
+
+File: gawk.info,  Node: VMS Installation Details,  Next: VMS Running,  Prev: VMS Dynamic Extensions,  Up: VMS Installation
+
+B.3.2.3 Installing `gawk' on VMS
 ................................
 
-To install `gawk', all you need is a "foreign" command, which is a
-`DCL' symbol whose value begins with a dollar sign. For example:
+To use `gawk', all you need is a "foreign" command, which is a `DCL'
+symbol whose value begins with a dollar sign. For example:
 
-     $ GAWK :== $disk1:[gnubin]GAWK
+     $ GAWK :== $disk1:[gnubin]gawk
 
 Substitute the actual location of `gawk.exe' for `$disk1:[gnubin]'. The
 symbol should be placed in the `login.com' of any user who wants to run
@@ -26296,9 +27683,27 @@ symbol should be placed in the `login.com' of any user who wants to run
 Alternatively, the symbol may be placed in the system-wide
 `sylogin.com' procedure, which allows all users to run `gawk'.
 
-   Optionally, the help entry can be loaded into a VMS help library:
+   If your `gawk' was installed by a PCSI kit into the `GNV$GNU:'
+directory tree, the program will be known as
+`GNV$GNU:[bin]gnv$gawk.exe' and the help file will be
+`GNV$GNU:[vms_help]gawk.hlp'.
+
+   The PCSI kit also installs a `GNV$GNU:[vms_bin]gawk_verb.cld' file
+which can be used to add `gawk' and `awk' as DCL commands.
+
+   For just the current process you can use:
+
+     $ set command gnv$gnu:[vms_bin]gawk_verb.cld
+
+   Or the system manager can use `GNV$GNU:[vms_bin]gawk_verb.cld' to
+add the `gawk' and `awk' to the system wide `DCLTABLES'.
 
-     $ LIBRARY/HELP SYS$HELP:HELPLIB [.VMS]GAWK.HLP
+   The DCL syntax is documented in the `gawk.hlp' file.
+
+   Optionally, the `gawk.hlp' entry can be loaded into a VMS help
+library:
+
+     $ LIBRARY/HELP sys$help:helplib [.vms]gawk.hlp
 
 (You may want to substitute a site-specific help library rather than
 the standard VMS library `HELPLIB'.)  After loading the help text, the
@@ -26315,14 +27720,14 @@ has no device or directory path information in it, `gawk' looks in the
 current directory first, then in the directory specified by the
 translation of `AWK_LIBRARY' if the file is not found.  If, after
 searching in both directories, the file still is not found, `gawk'
-appends the suffix `.awk' to the filename and retries the file search.
+appends the suffix `.awk' to the file name and retries the file search.
 If `AWK_LIBRARY' has no definition, a default value of `SYS$LIBRARY:'
 is used for it.
 
 
-File: gawk.info,  Node: VMS Running,  Next: VMS Old Gawk,  Prev: VMS Installation Details,  Up: VMS Installation
+File: gawk.info,  Node: VMS Running,  Next: VMS GNV,  Prev: VMS Installation Details,  Up: VMS Installation
 
-B.3.2.3 Running `gawk' on VMS
+B.3.2.4 Running `gawk' on VMS
 .............................
 
 Command-line parsing and quoting conventions are significantly different
@@ -26348,6 +27753,35 @@ If any other dash-type options (or multiple parameters such as data
 files to process) are present, there is no ambiguity and `--' can be
 omitted.
 
+   The `exit' value is a Unix-style value and is encoded to a VMS exit
+status value when the program exits.
+
+   The VMS severity bits will be set based on the `exit' value.  A
+failure is indicated by 1 and VMS sets the `ERROR' status.  A fatal
+error is indicated by 2 and VMS will set the `FATAL' status.  All other
+values will have the `SUCCESS' status.  The exit value is encoded to
+comply with VMS coding standards and will have the `C_FACILITY_NO' of
+`0x350000' with the constant `0xA000' added to the number shifted over
+by 3 bits to make room for the severity codes.
+
+   To extract the actual `gawk' exit code from the VMS status use:
+
+     unix_status = (vms_status .and. &x7f8) / 8
+
+A C program that uses `exec()' to call `gawk' will get the original
+Unix-style exit value.
+
+   Older versions of `gawk' treated a Unix exit code 0 as 1, a failure
+as 2, a fatal error as 4, and passed all the other numbers through.
+This violated the VMS exit status coding requirements.
+
+   VAX/VMS floating point uses unbiased rounding. *Note Round
+Function::.
+
+   VMS reports time values in GMT unless one of the `SYS$TIMEZONE_RULE'
+or `TZ' logical names is set.  Older versions of VMS, such as VAX/VMS
+7.3 do not set these logical names.
+
    The default search path, when looking for `awk' program files
 specified by the `-f' option, is `"SYS$DISK:[],AWK_LIBRARY:"'.  The
 logical name `AWKPATH' can be used to override this default.  The format
@@ -26356,9 +27790,27 @@ When defining it, the value should be quoted so that it retains a single
 translation and not a multitranslation `RMS' searchlist.
 
 
-File: gawk.info,  Node: VMS Old Gawk,  Prev: VMS Running,  Up: VMS Installation
+File: gawk.info,  Node: VMS GNV,  Next: VMS Old Gawk,  Prev: VMS Running,  Up: VMS Installation
+
+B.3.2.5 The VMS GNV Project
+...........................
+
+The VMS GNV package provides a build environment similar to POSIX with
+ports of a collection of open source tools.  The `gawk' found in the GNV
+base kit is an older port.  Currently the GNV project is being
+reorganized to supply individual PCSI packages for each component.  See
+`https://sourceforge.net/p/gnv/wiki/InstallingGNVPackages/'.
+
+   The normal build procedure for `gawk' produces a program that is
+suitable for use with GNV.
+
+   The `vms/gawk_build_steps.txt' in the source documents the procedure
+for building a VMS PCSI kit that is compatible with GNV.
+
+
+File: gawk.info,  Node: VMS Old Gawk,  Prev: VMS GNV,  Up: VMS Installation
 
-B.3.2.4 Some VMS Systems Have An Old Version of `gawk'
+B.3.2.6 Some VMS Systems Have An Old Version of `gawk'
 ......................................................
 
 Some versions of VMS have an old version of `gawk'.  To access it,
@@ -26401,11 +27853,12 @@ get this information with the command `gawk --version'.
 
    Once you have a precise problem, send email to <bug-gawk@gnu.org>.
 
-   Using this address automatically sends a copy of your mail to me.
-If necessary, I can be reached directly at <arnold@skeeve.com>.  The
-bug reporting address is preferred since the email list is archived at
-the GNU Project.  _All email should be in English, since that is my
-native language._
+   The `gawk' maintainers subscribe to this address and thus they will
+receive your bug report.  If necessary, the primary maintainer can be
+reached directly at <arnold@skeeve.com>.  The bug reporting address is
+preferred since the email list is archived at the GNU Project.  _All
+email should be in English. This is the only language understood in
+common by all the maintainers._
 
      CAUTION: Do _not_ try to report bugs in `gawk' by posting to the
      Usenet/Internet newsgroup `comp.lang.awk'.  While the `gawk'
@@ -26440,16 +27893,17 @@ considered authoritative if it conflicts with this Info file.
    The people maintaining the non-Unix ports of `gawk' are as follows:
 
 MS-DOS with DJGPP       Scott Deifik, <scottd.mail@sbcglobal.net>.
-MS-Windows with MINGW   Eli Zaretskii, <eliz@gnu.org>.
+MS-Windows with MinGW   Eli Zaretskii, <eliz@gnu.org>.
 OS/2                    Andreas Buening, <andreas.buening@nexgo.de>.
-VMS                     Pat Rankin, <r.pat.rankin@gmail.com>
+VMS                     Pat Rankin, <r.pat.rankin@gmail.com>, and John
+                        Malmberg, <wb8tyw@qsl.net>.
 z/OS (OS/390)           Dave Pitts, <dpitts@cozx.com>.
 
    If your bug is also reproducible under Unix, please send a copy of
 your report to the <bug-gawk@gnu.org> email list as well.
 
 
-File: gawk.info,  Node: Other Versions,  Prev: Bugs,  Up: Installation
+File: gawk.info,  Node: Other Versions,  Next: Installation summary,  Prev: Bugs,  Up: Installation
 
 B.5 Other Freely Available `awk' Implementations
 ================================================
@@ -26545,12 +27999,13 @@ Busybox Awk
      (http://busybox.net).
 
 The OpenSolaris POSIX `awk'
-     The version of `awk' in `/usr/xpg4/bin' on Solaris is more-or-less
-     POSIX-compliant. It is based on the `awk' from Mortice Kern
-     Systems for PCs.  This author was able to make it compile and work
-     under GNU/Linux with 1-2 hours of work.  Making it more generally
-     portable (using GNU Autoconf and/or Automake) would take more
-     work, and this has not been done, at least to our knowledge.
+     The versions of `awk' in `/usr/xpg4/bin' and `/usr/xpg6/bin' on
+     Solaris are more-or-less POSIX-compliant.  They are based on the
+     `awk' from Mortice Kern Systems for PCs.  This author was able to
+     make this code compile and work under GNU/Linux with 1-2 hours of
+     work.  Making it more generally portable (using GNU Autoconf
+     and/or Automake) would take more work, and this has not been done,
+     at least to our knowledge.
 
      The source code used to be available from the OpenSolaris web site.
      However, that project was ended and the web site shut down.
@@ -26588,6 +28043,9 @@ QSE Awk
      `http://www.quiktrim.org/QTawk.html' for more information,
      including the manual and a download link.
 
+     The project may also be frozen; no new code changes have been made
+     since approximately 2008.
+
 Other Versions
      See also the Wikipedia article
      (http://en.wikipedia.org/wiki/Awk_language#Versions_and_implementations),
@@ -26595,6 +28053,34 @@ Other Versions
 
 
 
+File: gawk.info,  Node: Installation summary,  Prev: Other Versions,  Up: Installation
+
+B.6 Summary
+===========
+
+   * The `gawk' distribution is available from GNU project's main
+     distribution site, `ftp.gnu.org'.  The canonical build recipe is:
+
+          wget http://ftp.gnu.org/gnu/gawk/gawk-4.1.1.tar.gz
+          tar -xvpzf gawk-4.1.1.tar.gz
+          cd gawk-4.1.1
+          ./configure && make && make check
+
+   * `gawk' may be built on non-POSIX systems as well. The currently
+     supported systems are MS-Windows using DJGPP, MSYS, MinGW and
+     Cygwin, OS/2 using EMX, and both Vax/VMS and OpenVMS.
+     Instructions for each system are included in this major node.
+
+   * Bug reports should be sent via email to <bug-gawk@gnu.org>.  Bug
+     reports should be in English, and should include the version of
+     `gawk', how it was compiled, and a short program and data file
+     which demonstrate the problem.
+
+   * There are a number of other freely available `awk'
+     implementations.  Many are POSIX compliant; others are less so.
+
+
+
 File: gawk.info,  Node: Notes,  Next: Basic Concepts,  Prev: Installation,  Up: Top
 
 Appendix C Implementation Notes
@@ -26613,6 +28099,7 @@ and maintainers of `gawk'.  Everything in it applies specifically to
 * Implementation Limitations::  Some limitations of the implementation.
 * Extension Design::            Design notes about the extension API.
 * Old Extension Mechanism::     Some compatibility for old extensions.
+* Notes summary::               Summary of implementation notes.
 
 
 File: gawk.info,  Node: Compatibility Mode,  Next: Additions,  Up: Notes
@@ -26630,7 +28117,7 @@ one more option available on the command line:
 
 `-Y'
 `--parsedebug'
-     Prints out the parse stack information as the program is being
+     Print out the parse stack information as the program is being
      parsed.
 
    This option is intended only for serious `gawk' developers and not
@@ -26658,8 +28145,8 @@ as well as any considerations you should bear in mind.
                                 `gawk'.
 * New Ports::                   Porting `gawk' to a new operating
                                 system.
-* Derived Files::               Why derived files are kept in the
-                                `git' repository.
+* Derived Files::               Why derived files are kept in the Git
+                                repository.
 
 
 File: gawk.info,  Node: Accessing The Source,  Next: Adding Code,  Up: Additions
@@ -26680,9 +28167,9 @@ doesn't have it.  Once you have done so, use the command:
 
      git clone git://git.savannah.gnu.org/gawk.git
 
-This will clone the `gawk' repository.  If you are behind a firewall
-that will not allow you to use the Git native protocol, you can still
-access the repository using:
+This clones the `gawk' repository.  If you are behind a firewall that
+does not allow you to use the Git native protocol, you can still access
+the repository using:
 
      git clone http://git.savannah.gnu.org/r/gawk.git
 
@@ -26704,7 +28191,7 @@ C.2.2 Adding New Features
 You are free to add any new features you like to `gawk'.  However, if
 you want your changes to be incorporated into the `gawk' distribution,
 there are several steps that you need to take in order to make it
-possible to include your changes:
+possible to include them:
 
   1. Before building the new feature into `gawk' itself, consider
      writing it as an extension module (*note Dynamic Extensions::).
@@ -26721,9 +28208,10 @@ possible to include your changes:
 
   3. Get the latest version.  It is much easier for me to integrate
      changes if they are relative to the most recent distributed
-     version of `gawk'.  If your version of `gawk' is very old, I may
-     not be able to integrate them at all.  (*Note Getting::, for
-     information on getting the latest version of `gawk'.)
+     version of `gawk', or better yet, relative to the latest code in
+     the Git repository.  If your version of `gawk' is very old, I may
+     not be able to integrate your changes at all.  (*Note Getting::,
+     for information on getting the latest version of `gawk'.)
 
   4. See *note (Version)Top:: standards, GNU Coding Standards.  This
      document describes how GNU software should be written. If you
@@ -26820,7 +28308,8 @@ possible to include your changes:
 
   8. Include an entry for the `ChangeLog' file with your submission.
      This helps further minimize the amount of work I have to do,
-     making it easier for me to accept patches.
+     making it easier for me to accept patches.  It is simplest if you
+     just make this part of your diff.
 
    Although this sounds like a lot of work, please remember that while
 you may write the new code, I have to maintain it and support it. If it
@@ -26861,18 +28350,24 @@ steps:
      people.  Thus, you should not change them unless it is for a very
      good reason; i.e., changes are not out of the question, but
      changes to these files are scrutinized extra carefully.  The files
-     are `dfa.c', `dfa.h', `getopt1.c', `getopt.c', `getopt.h',
-     `install-sh', `mkinstalldirs', `regcomp.c', `regex.c',
-     `regexec.c', `regexex.c', `regex.h', `regex_internal.c', and
-     `regex_internal.h'.
-
-  5. Be willing to continue to maintain the port.  Non-Unix operating
+     are `dfa.c', `dfa.h', `getopt.c', `getopt.h', `getopt1.c',
+     `getopt_int.h', `gettext.h', `regcomp.c', `regex.c', `regex.h',
+     `regex_internal.c', `regex_internal.h', and `regexec.c'.
+
+  5. A number of other files are provided by the GNU Autotools
+     (Autoconf, Automake, and GNU `gettext').  You should not change
+     them either, unless it is for a very good reason. The files are
+     `ABOUT-NLS', `config.guess', `config.rpath', `config.sub',
+     `depcomp', `INSTALL', `install-sh', `missing', `mkinstalldirs',
+     `xalloc.h', and `ylwrap'.
+
+  6. Be willing to continue to maintain the port.  Non-Unix operating
      systems are supported by volunteers who maintain the code needed
      to compile and run `gawk' on their systems. If noone volunteers to
      maintain a port, it becomes unsupported and it may be necessary to
      remove it from the distribution.
 
-  6. Supply an appropriate `gawkmisc.???' file.  Each port has its own
+  7. Supply an appropriate `gawkmisc.???' file.  Each port has its own
      `gawkmisc.???' that implements certain operating system specific
      functions. This is cleaner than a plethora of `#ifdef's scattered
      throughout the code.  The `gawkmisc.c' in the main source
@@ -26888,7 +28383,7 @@ steps:
      (Currently, this is only an issue for the PC operating system
      ports.)
 
-  7. Supply a `Makefile' as well as any other C source and header files
+  8. Supply a `Makefile' as well as any other C source and header files
      that are necessary for your operating system.  All your code
      should be in a separate subdirectory, with a name that is the same
      as, or reminiscent of, either your operating system or the
@@ -26898,7 +28393,7 @@ steps:
      avoid using names for your files that duplicate the names of files
      in the main source directory.
 
-  8. Update the documentation.  Please write a section (or sections)
+  9. Update the documentation.  Please write a section (or sections)
      for this Info file describing the installation and compilation
      steps needed to compile and/or install `gawk' for your system.
 
@@ -26912,13 +28407,13 @@ style and brace layout that suits your taste.
 
 File: gawk.info,  Node: Derived Files,  Prev: New Ports,  Up: Additions
 
-C.2.4 Why Generated Files Are Kept In `git'
--------------------------------------------
+C.2.4 Why Generated Files Are Kept In Git
+-----------------------------------------
 
-If you look at the `gawk' source in the `git' repository, you will
-notice that it includes files that are automatically generated by GNU
-infrastructure tools, such as `Makefile.in' from `automake' and even
-`configure' from `autoconf'.
+If you look at the `gawk' source in the Git repository, you will notice
+that it includes files that are automatically generated by GNU
+infrastructure tools, such as `Makefile.in' from Automake and even
+`configure' from Autoconf.
 
    This is different from many Free Software projects that do not store
 the derived files, because that keeps the repository less cluttered,
@@ -26945,10 +28440,10 @@ build?)
 
    If the repository has all the generated files, then it's easy to
 just check them out and build. (Or _easier_, depending upon how far
-back we go.  `:-)')
+back we go.)
 
    And that brings us to the second (and stronger) reason why all the
-files really need to be in `git'.  It boils down to who do you cater
+files really need to be in Git.  It boils down to who do you cater
 to--the `gawk' developer(s), or the user who just wants to check out a
 version and try it out?
 
@@ -26974,7 +28469,7 @@ idea how to create it, and that was not the only problem.)
 
    He felt _extremely_ frustrated.  With respect to that branch, the
 maintainer is no different than Jane User who wants to try to build
-`gawk-4.0-stable' or `master' from the repository.
+`gawk-4.1-stable' or `master' from the repository.
 
    Thus, the maintainer thinks that it's not just important, but
 critical, that for any given branch, the above incantation _just works_.
@@ -26989,32 +28484,26 @@ critical, that for any given branch, the above incantation _just works_.
 
        B. He is really good at `git diff x y > /tmp/diff1 ; gvim
           /tmp/diff1' to remove the diffs that aren't of interest in
-          order to review code. `:-)'
+          order to review code.
 
   2. It would certainly help if everyone used the same versions of the
      GNU tools as he does, which in general are the latest released
-     versions of `automake', `autoconf', `bison', and `gettext'.
-
-       A. Installing from source is quite easy. It's how the maintainer
-          worked for years under Fedora.  He had `/usr/local/bin' at
-          the front of his `PATH' and just did:
+     versions of Automake, Autoconf, `bison', and GNU `gettext'.
 
-               wget http://ftp.gnu.org/gnu/PACKAGE/PACKAGE-X.Y.Z.tar.gz
-               tar -xpzvf PACKAGE-X.Y.Z.tar.gz
-               cd PACKAGE-X.Y.Z
-               ./configure && make && make check
-               make install    # as root
-
-       B. These days the maintainer uses Ubuntu 12.04 which is medium
-          current, but he is already doing the above for `autoconf',
-          `automake' and `bison'.
+     Installing from source is quite easy. It's how the maintainer
+     worked for years (and still works).  He had `/usr/local/bin' at
+     the front of his `PATH' and just did:
 
+          wget http://ftp.gnu.org/gnu/PACKAGE/PACKAGE-X.Y.Z.tar.gz
+          tar -xpzvf PACKAGE-X.Y.Z.tar.gz
+          cd PACKAGE-X.Y.Z
+          ./configure && make && make check
+          make install    # as root
 
 
    Most of the above was originally written by the maintainer to other
 `gawk' developers.  It raised the objection from one of the developers
-"... that anybody pulling down the source from `git' is not an end
-user."
+"... that anybody pulling down the source from Git is not an end user."
 
    However, this is not true. There are "power `awk' users" who can
 build `gawk' (using the magic incantation shown previously) but who
@@ -27023,12 +28512,12 @@ all the time.
 
    It was then suggested that there be a `cron' job to create nightly
 tarballs of "the source."  Here, the problem is that there are source
-trees, corresponding to the various branches! So, nightly tar balls
+trees, corresponding to the various branches! So, nightly tarballs
 aren't the answer, especially as the repository can go for weeks
 without significant change being introduced.
 
-   Fortunately, the `git' server can meet this need. For any given
-branch named BRANCHNAME, use:
+   Fortunately, the Git server can meet this need. For any given branch
+named BRANCHNAME, use:
 
      wget http://git.savannah.gnu.org/cgit/gawk.git/snapshot/gawk-BRANCHNAME.tar.gz
 
@@ -27039,9 +28528,9 @@ to retrieve a snapshot of the given branch.
    (1) We tried. It was painful.
 
    (2) There is one GNU program that is (in our opinion) severely
-difficult to bootstrap from the `git' repository. For example, on the
-author's old (but still working) PowerPC macintosh with Mac OS X 10.5,
-it was necessary to bootstrap a ton of software, starting with `git'
+difficult to bootstrap from the Git repository. For example, on the
+author's old (but still working) PowerPC Macintosh with Mac OS X 10.5,
+it was necessary to bootstrap a ton of software, starting with Git
 itself, in order to try to work with the latest code.  It's not
 pleasant, and especially on older systems, it's a big waste of time.
 
@@ -27049,8 +28538,8 @@ pleasant, and especially on older systems, it's a big waste of time.
 maintainers had dropped `.gz' and `.bz2' files and only distribute
 `.tar.xz' files.  It was necessary to bootstrap `xz' first!
 
-   (3) A branch created by one of the other developers that did not
-include the generated files.
+   (3) A branch (since removed) created by one of the other developers
+that did not include the generated files.
 
 
 File: gawk.info,  Node: Future Extensions,  Next: Implementation Limitations,  Prev: Additions,  Up: Notes
@@ -27059,13 +28548,15 @@ C.3 Probable Future Extensions
 ==============================
 
      AWK is a language similar to PERL, only considerably more elegant.
-     -- Arnold Robbins Hey!  -- Larry Wall
+     -- Arnold Robbins
+
+     Hey!  -- Larry Wall
 
-   The `TODO' file in the `gawk' Git repository lists possible future
-enhancements.  Some of these relate to the source code, and others to
-possible new features.  Please see that file for the list.  *Note
-Additions::, if you are interested in tackling any of the projects
-listed there.
+   The `TODO' file in the `master' branch of the `gawk' Git repository
+lists possible future enhancements.  Some of these relate to the source
+code, and others to possible new features.  Please see that file for
+the list.  *Note Additions::, if you are interested in tackling any of
+the projects listed there.
 
 
 File: gawk.info,  Node: Implementation Limitations,  Next: Extension Design,  Prev: Future Extensions,  Up: Notes
@@ -27081,7 +28572,7 @@ Item                          Limit
 -------------------------------------------------------------------------- 
 Characters in a character     2^(number of bits per byte)
 class                         
-Length of input record        `MAX_INT '
+Length of input record        `MAX_INT'
 Length of output record       Unlimited
 Length of source line         Unlimited
 Number of fields in a record  `MAX_LONG'
@@ -27094,9 +28585,9 @@ Number of pipe redirections   min(number of processes per user, number
                               of open files)
 Numeric values                Double-precision floating point (if not
                               using MPFR)
-Size of a field               `MAX_INT '
-Size of a literal string      `MAX_INT '
-Size of a printf string       `MAX_INT '
+Size of a field               `MAX_INT'
+Size of a literal string      `MAX_INT'
+Size of a printf string       `MAX_INT'
 
 
 File: gawk.info,  Node: Extension Design,  Next: Old Extension Mechanism,  Prev: Implementation Limitations,  Up: Notes
@@ -27142,9 +28633,9 @@ The old extension mechanism had several problems:
 
    * Being able to call into `gawk' from an extension required linker
      facilities that are common on Unix-derived systems but that did
-     not work on Windows systems; users wanting extensions on Windows
-     had to statically link them into `gawk', even though Windows
-     supports dynamic loading of shared objects.
+     not work on MS-Windows systems; users wanting extensions on
+     MS-Windows had to statically link them into `gawk', even though
+     MS-Windows supports dynamic loading of shared objects.
 
    * The API would change occasionally as `gawk' changed; no
      compatibility between versions was ever offered or planned for.
@@ -27192,8 +28683,8 @@ Some goals for the new API were:
           flattening") in order to loop over all the element in an easy
           fashion for C code.
 
-        - The ability to create arrays (including `gawk''s true
-          multidimensional arrays).
+        - The ability to create arrays (including `gawk''s true arrays
+          of arrays).
 
    Some additional important goals were:
 
@@ -27207,7 +28698,7 @@ Some goals for the new API were:
 
    * The API mechanism should not require access to `gawk''s symbols(1)
      by the compile-time or dynamic linker, in order to enable creation
-     of extensions that also work on Windows.
+     of extensions that also work on MS-Windows.
 
    During development, it became clear that there were other features
 that should be available to extensions, which were also subsequently
@@ -27220,7 +28711,7 @@ provided:
      hook into input processing, output processing, and two-way I/O.
 
    * An extension should be able to provide a "call back" function to
-     perform clean up actions when `gawk' exits.
+     perform cleanup actions when `gawk' exits.
 
    * An extension should be able to provide a version string so that
      `gawk''s `--version' option can provide information about
@@ -27245,7 +28736,7 @@ Mechanism Outline::, for the details.
 
    (1) The "symbols" are the variables and functions defined inside
 `gawk'.  Access to these symbols by code external to `gawk' loaded
-dynamically at runtime is problematic on Windows.
+dynamically at runtime is problematic on MS-Windows.
 
 
 File: gawk.info,  Node: Extension Other Design Decisions,  Next: Extension Future Growth,  Prev: Extension New Mechanism Goals,  Up: Extension Design
@@ -27313,7 +28804,7 @@ The API can later be expanded, in two ways:
 respect to any of the above.
 
 
-File: gawk.info,  Node: Old Extension Mechanism,  Prev: Extension Design,  Up: Notes
+File: gawk.info,  Node: Old Extension Mechanism,  Next: Notes summary,  Prev: Extension Design,  Up: Notes
 
 C.6 Compatibility For Old Extensions
 ====================================
@@ -27351,6 +28842,37 @@ old extensions that you may have to use the new API described in *note
 Dynamic Extensions::.
 
 
+File: gawk.info,  Node: Notes summary,  Prev: Old Extension Mechanism,  Up: Notes
+
+C.7 Summary
+===========
+
+   * `gawk''s extensions can be disabled with either the
+     `--traditional' option or with the `--posix' option.  The
+     `--parsedebug' option is available if `gawk' is compiled with
+     `-DDEBUG'.
+
+   * The source code for `gawk' is maintained in a publicly accessable
+     Git repository. Anyone may check it out and view the source.
+
+   * Contributions to `gawk' are welcome. Following the steps outlined
+     in this major node will make it easier to integrate your
+     contributions into the code base.  This applies both to new
+     feature contributions and to ports to additional operating systems.
+
+   * `gawk' has some limits--generally those that are imposed by the
+     machine architecture.
+
+   * The extension API design was intended to solve a number of problems
+     with the previous extension mechanism, enable features needed by
+     the `xgawk' project, and provide binary compatibility going
+     forward.
+
+   * The previous extension mechanism is still supported in version 4.1
+     of `gawk', but it _will_ be removed in the next major release.
+
+
+
 File: gawk.info,  Node: Basic Concepts,  Next: Glossary,  Prev: Notes,  Up: Top
 
 Appendix D Basic Programming Concepts
@@ -27375,7 +28897,7 @@ D.1 What a Program Does
 =======================
 
 At the most basic level, the job of a program is to process some input
-data and produce results. See *note figure-general-flow::.
+data and produce results.  See *note figure-general-flow::.
 
                   _______
 +------+         /       \         +---------+
@@ -27487,7 +29009,7 @@ characters that comprise them.  Individual variables, as well as
 numeric and string variables, are referred to as "scalar" values.
 Groups of values, such as arrays, are not scalars.
 
-   *note General Arithmetic::, provided a basic introduction to numeric
+   *note Computer Arithmetic::, provided a basic introduction to numeric
 types (integer and floating-point) and how they are used in a computer.
 Please review that information, including a number of caveats that were
 presented.
@@ -27501,15 +29023,14 @@ like this: `""'.
 
    Humans are used to working in decimal; i.e., base 10.  In base 10,
 numbers go from 0 to 9, and then "roll over" into the next column.
-(Remember grade school? 42 is 4 times 10 plus 2.)
+(Remember grade school? 42 = 4 x 10 + 2.)
 
    There are other number bases though.  Computers commonly use base 2
 or "binary", base 8 or "octal", and base 16 or "hexadecimal".  In
 binary, each column represents two times the value in the column to its
 right. Each column may contain either a 0 or a 1.  Thus, binary 1010
-represents 1 times 8, plus 0 times 4, plus 1 times 2, plus 0 times 1,
-or decimal 10.  Octal and hexadecimal are discussed more in *note
-Nondecimal-numbers::.
+represents (1 x 8) + (0 x 4) + (1 x 2) + (0 x 1), or decimal 10.  Octal
+and hexadecimal are discussed more in *note Nondecimal-numbers::.
 
    At the very lowest level, computers store values as groups of binary
 digits, or "bits".  Modern computers group bits into groups of eight,
@@ -27541,8 +29062,7 @@ Glossary
 Action
      A series of `awk' statements attached to a rule.  If the rule's
      pattern matches an input record, `awk' executes the rule's action.
-     Actions are always enclosed in curly braces.  (*Note Action
-     Overview::.)
+     Actions are always enclosed in braces.  (*Note Action Overview::.)
 
 Amazing `awk' Assembler
      Henry Spencer at the University of Toronto wrote a retargetable
@@ -27608,9 +29128,6 @@ Bash
      The GNU version of the standard shell (the Bourne-Again SHell).
      See also "Bourne Shell."
 
-BBS
-     See "Bulletin Board System."
-
 Bit
      Short for "Binary Digit."  All values in computer memory
      ultimately reduce to binary digits: values that are either zero or
@@ -27631,9 +29148,9 @@ Boolean Expression
 
 Bourne Shell
      The standard shell (`/bin/sh') on Unix and Unix-like systems,
-     originally written by Steven R. Bourne.  Many shells (Bash, `ksh',
-     `pdksh', `zsh') are generally upwardly compatible with the Bourne
-     shell.
+     originally written by Steven R. Bourne at Bell Laboratories.  Many
+     shells (Bash, `ksh', `pdksh', `zsh') are generally upwardly
+     compatible with the Bourne shell.
 
 Built-in Function
      The `awk' language provides built-in functions that perform various
@@ -27654,12 +29171,8 @@ Built-in Variable
      Variables::.)
 
 Braces
-     See "Curly Braces."
-
-Bulletin Board System
-     A computer system allowing users to log in and read and/or leave
-     messages for other users of the system, much like leaving paper
-     notes on a bulletin board.
+     The characters `{' and `}'.  Braces are used in `awk' for
+     delimiting actions, compound statements, and function bodies.
 
 C
      The system programming language that most GNU software is written
@@ -27680,8 +29193,8 @@ Character Set
      ASCII (American Standard Code for Information Interchange).  Many
      European countries use an extension of ASCII known as ISO-8859-1
      (ISO Latin-1).  The Unicode character set (http://www.unicode.org)
-     is becoming increasingly popular and standard, and is particularly
-     widely used on GNU/Linux systems.
+     is increasingly popular and standard, and is particularly widely
+     used on GNU/Linux systems.
 
 CHEM
      A preprocessor for `pic' that reads descriptions of molecules and
@@ -27691,7 +29204,7 @@ CHEM
 
 Cookie
      A peculiar goodie, token, saying or remembrance produced by or
-     presented to a program. (With thanks to Doug McIlroy.)
+     presented to a program. (With thanks to Professor Doug McIlroy.)
 
 Coprocess
      A subordinate program with which two-way communications is
@@ -27726,8 +29239,7 @@ Comparison Expression
      process.  (*Note Typing and Comparison::.)
 
 Curly Braces
-     The characters `{' and `}'.  Curly braces are used in `awk' for
-     delimiting actions, compound statements, and function bodies.
+     See "Braces."
 
 Dark Corner
      An area in the language where specifications often were (or still
@@ -27767,7 +29279,7 @@ Dynamic Regular Expression
      (*Note Computed Regexps::.)
 
 Environment
-     A collection of strings, of the form NAME`='VAL, that each program
+     A collection of strings, of the form `NAME=VAL', that each program
      has available to it. Users generally place values into the
      environment in order to provide information to various programs.
      Typical examples are the environment variables `HOME' and `PATH'.
@@ -27818,11 +29330,11 @@ Floating-Point Number
      See also "Double Precision" and "Single Precision."
 
 Format
-     Format strings are used to control the appearance of output in the
-     `strftime()' and `sprintf()' functions, and are used in the
-     `printf' statement as well.  Also, data conversions from numbers
-     to strings are controlled by the format strings contained in the
-     built-in variables `CONVFMT' and `OFMT'. (*Note Control Letters::.)
+     Format strings control the appearance of output in the
+     `strftime()' and `sprintf()' functions, and in the `printf'
+     statement as well.  Also, data conversions from numbers to strings
+     are controlled by the format strings contained in the built-in
+     variables `CONVFMT' and `OFMT'. (*Note Control Letters::.)
 
 Free Documentation License
      This document describes the terms under which this Info file is
@@ -27877,8 +29389,8 @@ Hexadecimal
      Base 16 notation, where the digits are `0'-`9' and `A'-`F', with
      `A' representing 10, `B' representing 11, and so on, up to `F' for
      15.  Hexadecimal numbers are written in C using a leading `0x', to
-     indicate their base.  Thus, `0x12' is 18 (1 times 16 plus 2).
-     *Note Nondecimal-numbers::.
+     indicate their base.  Thus, `0x12' is 18 ((1 x 16) + 2).  *Note
+     Nondecimal-numbers::.
 
 I/O
      Abbreviation for "Input/Output," the act of moving data into and/or
@@ -27935,7 +29447,7 @@ Keyword
      `gawk''s keywords are: `BEGIN', `BEGINFILE', `END', `ENDFILE',
      `break', `case', `continue', `default' `delete', `do...while',
      `else', `exit', `for...in', `for', `function', `func', `if',
-     `nextfile', `next', `switch', and `while'.
+     `next', `nextfile', `switch', and `while'.
 
 Lesser General Public License
      This document describes the terms under which binary library
@@ -27991,11 +29503,7 @@ Number
 Octal
      Base-eight notation, where the digits are `0'-`7'.  Octal numbers
      are written in C using a leading `0', to indicate their base.
-     Thus, `013' is 11 (one times 8 plus 3).  *Note
-     Nondecimal-numbers::.
-
-P1003.1
-     See "POSIX."
+     Thus, `013' is 11 ((1 x 8) + 3).  *Note Nondecimal-numbers::.
 
 Pattern
      Patterns tell `awk' which input records are interesting to which
@@ -28036,9 +29544,9 @@ Range (of input lines)
      specify single lines. (*Note Pattern Overview::.)
 
 Recursion
-     When a function calls itself, either directly or indirectly.  As
-     long as this is not clear, refer to the entry for "recursion."  If
-     this is clear, stop, and proceed to the next entry.
+     When a function calls itself, either directly or indirectly.  If
+     this is clear, stop, and proceed to the next entry.  Otherwise,
+     refer to the entry for "recursion."
 
 Redirection
      Redirection means performing input from something other than the
@@ -28119,8 +29627,8 @@ Single Precision
      parts.  Single precision numbers keep track of fewer digits than
      do double precision numbers, but operations on them are sometimes
      less expensive in terms of CPU time.  This is the type used by
-     some very old versions of `awk' to store numeric values.  It is
-     the C type `float'.
+     some ancient versions of `awk' to store numeric values.  It is the
+     C type `float'.
 
 Space
      The character generated by hitting the space bar on the keyboard.
@@ -28154,7 +29662,7 @@ Text Domain
 Timestamp
      A value in the "seconds since the epoch" format used by Unix and
      POSIX systems.  Used for the `gawk' functions `mktime()',
-     `strftime()', and `systime()'.  See also "Epoch" and "UTC."
+     `strftime()', and `systime()'.  See also "Epoch," "GMT," and "UTC."
 
 Unix
      A computer operating system originally developed in the early
@@ -28183,7 +29691,6 @@ GNU General Public License
 **************************
 
                         Version 3, 29 June 2007
-
      Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/'
 
      Everyone is permitted to copy and distribute verbatim copies of this
@@ -28906,7 +30413,6 @@ GNU Free Documentation License
 ******************************
 
                      Version 1.3, 3 November 2008
-
      Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
      `http://fsf.org/'
 
@@ -29395,7 +30901,7 @@ Index
 * Menu:
 
 * ! (exclamation point), !  operator:    Boolean Ops.         (line  67)
-* ! (exclamation point), ! operator <1>: Egrep Program.       (line 170)
+* ! (exclamation point), ! operator <1>: Egrep Program.       (line 175)
 * ! (exclamation point), ! operator <2>: Ranges.              (line  48)
 * ! (exclamation point), ! operator:     Precedence.          (line  52)
 * ! (exclamation point), != operator <1>: Precedence.         (line  65)
@@ -29410,165 +30916,167 @@ Index
 * ! (exclamation point), !~ operator <5>: Computed Regexps.   (line   6)
 * ! (exclamation point), !~ operator <6>: Case-sensitivity.   (line  26)
 * ! (exclamation point), !~ operator:    Regexp Usage.        (line  19)
-* " (double quote) <1>:                  Quoting.             (line  37)
-* " (double quote):                      Read Terminal.       (line  25)
-* " (double quote), in regexp constants: Computed Regexps.    (line  28)
+* " (double quote) in shell commands:    Read Terminal.       (line  25)
+* " (double quote), in regexp constants: Computed Regexps.    (line  29)
+* " (double quote), in shell commands:   Quoting.             (line  54)
 * # (number sign), #! (executable scripts): Executable Scripts.
                                                               (line   6)
 * # (number sign), commenting:           Comments.            (line   6)
-* $ (dollar sign):                       Regexp Operators.    (line  35)
 * $ (dollar sign), $ field operator <1>: Precedence.          (line  43)
 * $ (dollar sign), $ field operator:     Fields.              (line  19)
 * $ (dollar sign), incrementing fields and arrays: Increment Ops.
                                                               (line  30)
+* $ (dollar sign), regexp operator:      Regexp Operators.    (line  35)
 * % (percent sign), % operator:          Precedence.          (line  55)
 * % (percent sign), %= operator <1>:     Precedence.          (line  95)
-* % (percent sign), %= operator:         Assignment Ops.      (line 129)
+* % (percent sign), %= operator:         Assignment Ops.      (line 130)
 * & (ampersand), && operator <1>:        Precedence.          (line  86)
 * & (ampersand), && operator:            Boolean Ops.         (line  57)
 * & (ampersand), gsub()/gensub()/sub() functions and: Gory Details.
                                                               (line   6)
-* ' (single quote) <1>:                  Quoting.             (line  31)
-* ' (single quote) <2>:                  Long.                (line  33)
 * ' (single quote):                      One-shot.            (line  15)
+* ' (single quote) in gawk command lines: Long.               (line  33)
+* ' (single quote), in shell commands:   Quoting.             (line  48)
 * ' (single quote), vs. apostrophe:      Comments.            (line  27)
-* ' (single quote), with double quotes:  Quoting.             (line  53)
-* () (parentheses) <1>:                  Profiling.           (line 138)
-* () (parentheses):                      Regexp Operators.    (line  79)
+* ' (single quote), with double quotes:  Quoting.             (line  70)
+* () (parentheses), in a profile:        Profiling.           (line 146)
+* () (parentheses), regexp operator:     Regexp Operators.    (line  80)
 * * (asterisk), * operator, as multiplication operator: Precedence.
                                                               (line  55)
 * * (asterisk), * operator, as regexp operator: Regexp Operators.
-                                                              (line  87)
+                                                              (line  88)
 * * (asterisk), * operator, null strings, matching: Gory Details.
                                                               (line 164)
 * * (asterisk), ** operator <1>:         Precedence.          (line  49)
 * * (asterisk), ** operator:             Arithmetic Ops.      (line  81)
 * * (asterisk), **= operator <1>:        Precedence.          (line  95)
-* * (asterisk), **= operator:            Assignment Ops.      (line 129)
+* * (asterisk), **= operator:            Assignment Ops.      (line 130)
 * * (asterisk), *= operator <1>:         Precedence.          (line  95)
-* * (asterisk), *= operator:             Assignment Ops.      (line 129)
-* + (plus sign):                         Regexp Operators.    (line 102)
+* * (asterisk), *= operator:             Assignment Ops.      (line 130)
 * + (plus sign), + operator:             Precedence.          (line  52)
 * + (plus sign), ++ operator <1>:        Precedence.          (line  46)
 * + (plus sign), ++ operator:            Increment Ops.       (line  11)
 * + (plus sign), += operator <1>:        Precedence.          (line  95)
 * + (plus sign), += operator:            Assignment Ops.      (line  82)
+* + (plus sign), regexp operator:        Regexp Operators.    (line 103)
 * , (comma), in range patterns:          Ranges.              (line   6)
 * - (hyphen), - operator:                Precedence.          (line  52)
 * - (hyphen), -- operator <1>:           Precedence.          (line  46)
 * - (hyphen), -- operator:               Increment Ops.       (line  48)
 * - (hyphen), -= operator <1>:           Precedence.          (line  95)
-* - (hyphen), -= operator:               Assignment Ops.      (line 129)
-* - (hyphen), filenames beginning with:  Options.             (line  73)
+* - (hyphen), -= operator:               Assignment Ops.      (line 130)
+* - (hyphen), filenames beginning with:  Options.             (line  59)
 * - (hyphen), in bracket expressions:    Bracket Expressions. (line  17)
-* --assign option:                       Options.             (line  46)
-* --bignum option:                       Options.             (line 201)
-* --c option:                            Options.             (line  95)
-* --characters-as-bytes option:          Options.             (line  82)
-* --copyright option:                    Options.             (line 102)
-* --debug option:                        Options.             (line 122)
+* --assign option:                       Options.             (line  32)
+* --bignum option:                       Options.             (line 205)
+* --characters-as-bytes option:          Options.             (line  68)
+* --copyright option:                    Options.             (line  88)
+* --debug option:                        Options.             (line 108)
 * --disable-extensions configuration option: Additional Configuration Options.
                                                               (line   9)
 * --disable-lint configuration option:   Additional Configuration Options.
                                                               (line  15)
 * --disable-nls configuration option:    Additional Configuration Options.
                                                               (line  30)
-* --dump-variables option <1>:           Library Names.       (line  45)
-* --dump-variables option:               Options.             (line 107)
-* --exec option:                         Options.             (line 139)
+* --dump-variables option:               Options.             (line  93)
+* --dump-variables option, using for library functions: Library Names.
+                                                              (line  45)
+* --exec option:                         Options.             (line 125)
 * --field-separator option:              Options.             (line  21)
 * --file option:                         Options.             (line  25)
 * --gen-pot option <1>:                  String Extraction.   (line   6)
-* --gen-pot option:                      Options.             (line 161)
-* --help option:                         Options.             (line 168)
-* --include option:                      Options.             (line  32)
-* --L option:                            Options.             (line 288)
-* --lint option <1>:                     Options.             (line 182)
+* --gen-pot option:                      Options.             (line 147)
+* --help option:                         Options.             (line 154)
+* --include option:                      Options.             (line 159)
+* --lint option <1>:                     Options.             (line 185)
 * --lint option:                         Command Line.        (line  20)
-* --lint-old option:                     Options.             (line 288)
+* --lint-old option:                     Options.             (line 295)
 * --load option:                         Options.             (line 173)
 * --non-decimal-data option <1>:         Nondecimal Data.     (line   6)
-* --non-decimal-data option:             Options.             (line 207)
+* --non-decimal-data option:             Options.             (line 211)
 * --non-decimal-data option, strtonum() function and: Nondecimal Data.
                                                               (line  36)
-* --optimize option:                     Options.             (line 228)
-* --posix option:                        Options.             (line 247)
-* --posix option, --traditional option and: Options.          (line 266)
-* --pretty-print option:                 Options.             (line 220)
+* --optimize option:                     Options.             (line 237)
+* --posix option:                        Options.             (line 254)
+* --posix option, --traditional option and: Options.          (line 273)
+* --pretty-print option:                 Options.             (line 224)
 * --profile option <1>:                  Profiling.           (line  12)
-* --profile option:                      Options.             (line 235)
-* --re-interval option:                  Options.             (line 272)
-* --sandbox option:                      Options.             (line 279)
+* --profile option:                      Options.             (line 242)
+* --re-interval option:                  Options.             (line 279)
+* --sandbox option:                      Options.             (line 286)
 * --sandbox option, disabling system() function: I/O Functions.
-                                                              (line  94)
+                                                              (line  97)
 * --sandbox option, input redirection with getline: Getline.  (line  19)
 * --sandbox option, output redirection with print, printf: Redirection.
                                                               (line   6)
-* --source option:                       Options.             (line 131)
-* --traditional option:                  Options.             (line  95)
-* --traditional option, --posix option and: Options.          (line 266)
-* --use-lc-numeric option:               Options.             (line 215)
-* --version option:                      Options.             (line 293)
+* --source option:                       Options.             (line 117)
+* --traditional option:                  Options.             (line  81)
+* --traditional option, --posix option and: Options.          (line 273)
+* --use-lc-numeric option:               Options.             (line 219)
+* --version option:                      Options.             (line 300)
 * --with-whiny-user-strftime configuration option: Additional Configuration Options.
                                                               (line  35)
-* -b option:                             Options.             (line  82)
-* -C option:                             Options.             (line 102)
-* -D option:                             Options.             (line 122)
-* -d option:                             Options.             (line 107)
-* -E option:                             Options.             (line 139)
-* -e option:                             Options.             (line 131)
-* -F option:                             Command Line Field Separator.
-                                                              (line   6)
+* -b option:                             Options.             (line  68)
+* -C option:                             Options.             (line  88)
+* -c option:                             Options.             (line  81)
+* -D option:                             Options.             (line 108)
+* -d option:                             Options.             (line  93)
+* -E option:                             Options.             (line 125)
+* -e option:                             Options.             (line 117)
 * -f option:                             Options.             (line  25)
 * -F option:                             Options.             (line  21)
 * -f option:                             Long.                (line  12)
-* -F option, -Ft sets FS to TAB:         Options.             (line 301)
-* -f option, multiple uses:              Options.             (line 306)
-* -g option:                             Options.             (line 161)
-* -h option:                             Options.             (line 168)
-* -i option:                             Options.             (line  32)
+* -F option, -Ft sets FS to TAB:         Options.             (line 308)
+* -F option, command line:               Command Line Field Separator.
+                                                              (line   6)
+* -f option, multiple uses:              Options.             (line 313)
+* -g option:                             Options.             (line 147)
+* -h option:                             Options.             (line 154)
+* -i option:                             Options.             (line 159)
+* -L option:                             Options.             (line 295)
 * -l option:                             Options.             (line 173)
-* -M option:                             Options.             (line 201)
-* -N option:                             Options.             (line 215)
-* -n option:                             Options.             (line 207)
-* -O option:                             Options.             (line 228)
-* -o option:                             Options.             (line 220)
-* -P option:                             Options.             (line 247)
-* -p option:                             Options.             (line 235)
-* -r option:                             Options.             (line 272)
-* -S option:                             Options.             (line 279)
+* -M option:                             Options.             (line 205)
+* -N option:                             Options.             (line 219)
+* -n option:                             Options.             (line 211)
+* -O option:                             Options.             (line 237)
+* -o option:                             Options.             (line 224)
+* -P option:                             Options.             (line 254)
+* -p option:                             Options.             (line 242)
+* -r option:                             Options.             (line 279)
+* -S option:                             Options.             (line 286)
 * -v option:                             Assignment Options.  (line  12)
-* -V option:                             Options.             (line 293)
-* -v option:                             Options.             (line  46)
-* -W option:                             Options.             (line  60)
-* . (period):                            Regexp Operators.    (line  43)
-* .gmo files:                            Explaining gettext.  (line  41)
-* .gmo files, converting from .po:       I18N Example.        (line  62)
+* -V option:                             Options.             (line 300)
+* -v option:                             Options.             (line  32)
+* -W option:                             Options.             (line  46)
+* . (period), regexp operator:           Regexp Operators.    (line  44)
+* .gmo files:                            Explaining gettext.  (line  42)
 * .gmo files, specifying directory of <1>: Programmer i18n.   (line  47)
-* .gmo files, specifying directory of:   Explaining gettext.  (line  53)
+* .gmo files, specifying directory of:   Explaining gettext.  (line  54)
+* .mo files, converting from .po:        I18N Example.        (line  63)
 * .po files <1>:                         Translator i18n.     (line   6)
-* .po files:                             Explaining gettext.  (line  36)
-* .po files, converting to .gmo:         I18N Example.        (line  62)
-* .pot files:                            Explaining gettext.  (line  30)
-* / (forward slash):                     Regexp.              (line  10)
+* .po files:                             Explaining gettext.  (line  37)
+* .po files, converting to .mo:          I18N Example.        (line  63)
+* .pot files:                            Explaining gettext.  (line  31)
+* / (forward slash) to enclose regular expressions: Regexp.   (line  10)
 * / (forward slash), / operator:         Precedence.          (line  55)
 * / (forward slash), /= operator <1>:    Precedence.          (line  95)
-* / (forward slash), /= operator:        Assignment Ops.      (line 129)
+* / (forward slash), /= operator:        Assignment Ops.      (line 130)
 * / (forward slash), /= operator, vs. /=.../ regexp constant: Assignment Ops.
-                                                              (line 147)
+                                                              (line 148)
 * / (forward slash), patterns and:       Expression Patterns. (line  24)
-* /= operator vs. /=.../ regexp constant: Assignment Ops.     (line 147)
-* /dev/... special files (gawk):         Special FD.          (line  46)
-* /dev/fd/N special files:               Special FD.          (line  46)
+* /= operator vs. /=.../ regexp constant: Assignment Ops.     (line 148)
+* /dev/... special files:                Special FD.          (line  46)
+* /dev/fd/N special files (gawk):        Special FD.          (line  46)
 * /inet/... special files (gawk):        TCP/IP Networking.   (line   6)
 * /inet4/... special files (gawk):       TCP/IP Networking.   (line   6)
 * /inet6/... special files (gawk):       TCP/IP Networking.   (line   6)
-* ; (semicolon):                         Statements/Lines.    (line  91)
-* ; (semicolon), AWKPATH variable and:   PC Using.            (line  11)
+* ; (semicolon), AWKPATH variable and:   PC Using.            (line  10)
 * ; (semicolon), separating statements in actions <1>: Statements.
                                                               (line  10)
-* ; (semicolon), separating statements in actions: Action Overview.
+* ; (semicolon), separating statements in actions <2>: Action Overview.
                                                               (line  19)
+* ; (semicolon), separating statements in actions: Statements/Lines.
+                                                              (line  91)
 * < (left angle bracket), < operator <1>: Precedence.         (line  65)
 * < (left angle bracket), < operator:    Comparison Operators.
                                                               (line  11)
@@ -29589,15 +31097,13 @@ Index
                                                               (line  11)
 * > (right angle bracket), >> operator (I/O) <1>: Precedence. (line  65)
 * > (right angle bracket), >> operator (I/O): Redirection.    (line  50)
-* ? (question mark) regexp operator <1>: GNU Regexp Operators.
-                                                              (line  59)
-* ? (question mark) regexp operator:     Regexp Operators.    (line 111)
 * ? (question mark), ?: operator:        Precedence.          (line  92)
-* [] (square brackets):                  Regexp Operators.    (line  55)
-* \ (backslash) <1>:                     Regexp Operators.    (line  18)
-* \ (backslash) <2>:                     Quoting.             (line  31)
-* \ (backslash) <3>:                     Comments.            (line  50)
-* \ (backslash):                         Read Terminal.       (line  25)
+* ? (question mark), regexp operator <1>: GNU Regexp Operators.
+                                                              (line  59)
+* ? (question mark), regexp operator:    Regexp Operators.    (line 112)
+* [] (square brackets), regexp operator: Regexp Operators.    (line  56)
+* \ (backslash):                         Comments.            (line  50)
+* \ (backslash) in shell commands:       Read Terminal.       (line  25)
 * \ (backslash), \" escape sequence:     Escape Sequences.    (line  76)
 * \ (backslash), \' operator (gawk):     GNU Regexp Operators.
                                                               (line  56)
@@ -29631,7 +31137,7 @@ Index
                                                               (line  38)
 * \ (backslash), as field separator:     Command Line Field Separator.
                                                               (line  27)
-* \ (backslash), continuing lines and <1>: Egrep Program.     (line 220)
+* \ (backslash), continuing lines and <1>: Egrep Program.     (line 223)
 * \ (backslash), continuing lines and:   Statements/Lines.    (line  19)
 * \ (backslash), continuing lines and, comments and: Statements/Lines.
                                                               (line  76)
@@ -29643,146 +31149,176 @@ Index
 * \ (backslash), in escape sequences:    Escape Sequences.    (line   6)
 * \ (backslash), in escape sequences, POSIX and: Escape Sequences.
                                                               (line 112)
-* \ (backslash), in regexp constants:    Computed Regexps.    (line  28)
-* ^ (caret):                             GNU Regexp Operators.
-                                                              (line  59)
+* \ (backslash), in regexp constants:    Computed Regexps.    (line  29)
+* \ (backslash), in shell commands:      Quoting.             (line  48)
+* \ (backslash), regexp operator:        Regexp Operators.    (line  18)
 * ^ (caret), ^ operator:                 Precedence.          (line  49)
 * ^ (caret), ^= operator <1>:            Precedence.          (line  95)
-* ^ (caret), ^= operator:                Assignment Ops.      (line 129)
+* ^ (caret), ^= operator:                Assignment Ops.      (line 130)
 * ^ (caret), in bracket expressions:     Bracket Expressions. (line  17)
-* ^ (caret), regexp operator:            Regexp Operators.    (line  22)
-* ^, in FS:                              Regexp Field Splitting.
+* ^ (caret), in FS:                      Regexp Field Splitting.
                                                               (line  59)
-* _ (underscore), C macro:               Explaining gettext.  (line  70)
+* ^ (caret), regexp operator <1>:        GNU Regexp Operators.
+                                                              (line  59)
+* ^ (caret), regexp operator:            Regexp Operators.    (line  22)
+* _ (underscore), C macro:               Explaining gettext.  (line  71)
 * _ (underscore), in names of private variables: Library Names.
                                                               (line  29)
 * _ (underscore), translatable string:   Programmer i18n.     (line  69)
-* _gr_init() user-defined function:      Group Functions.     (line  82)
+* _gr_init() user-defined function:      Group Functions.     (line  83)
+* _ord_init() user-defined function:     Ordinal Functions.   (line  16)
 * _pw_init() user-defined function:      Passwd Functions.    (line 105)
 * accessing fields:                      Fields.              (line   6)
+* accessing global variables from extensions: Symbol Table Access.
+                                                              (line   6)
 * account information <1>:               Group Functions.     (line   6)
 * account information:                   Passwd Functions.    (line  16)
 * actions:                               Action Overview.     (line   6)
 * actions, control statements in:        Statements.          (line   6)
 * actions, default:                      Very Simple.         (line  34)
 * actions, empty:                        Very Simple.         (line  39)
-* Ada programming language:              Glossary.            (line  20)
+* Ada programming language:              Glossary.            (line  19)
 * adding, features to gawk:              Adding Code.         (line   6)
 * adding, fields:                        Changing Fields.     (line  53)
-* advanced features, fixed-width data:   Constant Size.       (line   9)
+* advanced features, fixed-width data:   Constant Size.       (line  10)
 * advanced features, gawk:               Advanced Features.   (line   6)
-* advanced features, network connections, See Also networks, connections: Advanced Features.
-                                                              (line   6)
 * advanced features, network programming: TCP/IP Networking.  (line   6)
 * advanced features, nondecimal input data: Nondecimal Data.  (line   6)
 * advanced features, processes, communicating with: Two-way I/O.
                                                               (line  23)
 * advanced features, specifying field content: Splitting By Content.
-                                                              (line   9)
+                                                              (line  10)
 * Aho, Alfred <1>:                       Contributors.        (line  11)
 * Aho, Alfred:                           History.             (line  17)
-* alarm clock example program:           Alarm Program.       (line   9)
-* alarm.awk program:                     Alarm Program.       (line  29)
+* alarm clock example program:           Alarm Program.       (line  11)
+* alarm.awk program:                     Alarm Program.       (line  31)
 * algorithms:                            Basic High Level.    (line  68)
+* allocating memory for extensions:      Memory Allocation Functions.
+                                                              (line   6)
 * Alpha (DEC):                           Manual History.      (line  28)
-* amazing awk assembler (aaa):           Glossary.            (line  12)
-* amazingly workable formatter (awf):    Glossary.            (line  25)
+* amazing awk assembler (aaa):           Glossary.            (line  11)
+* amazingly workable formatter (awf):    Glossary.            (line  24)
 * ambiguity, syntactic: /= operator vs. /=.../ regexp constant: Assignment Ops.
-                                                              (line 147)
+                                                              (line 148)
 * ampersand (&), && operator <1>:        Precedence.          (line  86)
 * ampersand (&), && operator:            Boolean Ops.         (line  57)
 * ampersand (&), gsub()/gensub()/sub() functions and: Gory Details.
                                                               (line   6)
 * anagram.awk program:                   Anagram Program.     (line  22)
+* anagrams, finding:                     Anagram Program.     (line   6)
+* and:                                   Bitwise Functions.   (line  39)
 * AND bitwise operation:                 Bitwise Functions.   (line   6)
 * and Boolean-logic operator:            Boolean Ops.         (line   6)
-* and() function (gawk):                 Bitwise Functions.   (line  39)
-* ANSI:                                  Glossary.            (line  35)
+* ANSI:                                  Glossary.            (line  34)
+* API informational variables:           Extension API Informational Variables.
+                                                              (line   6)
+* API version:                           Extension Versioning.
+                                                              (line   6)
 * arbitrary precision:                   Arbitrary Precision Arithmetic.
                                                               (line   6)
+* arbitrary precision integers:          Arbitrary Precision Integers.
+                                                              (line   6)
 * archeologists:                         Bugs.                (line   6)
-* ARGC/ARGV variables <1>:               ARGC and ARGV.       (line   6)
-* ARGC/ARGV variables:                   Auto-set.            (line  11)
+* arctangent:                            Numeric Functions.   (line  11)
+* ARGC/ARGV variables:                   Auto-set.            (line  15)
 * ARGC/ARGV variables, command-line arguments: Other Arguments.
                                                               (line  12)
+* ARGC/ARGV variables, how to use:       ARGC and ARGV.       (line   6)
 * ARGC/ARGV variables, portability and:  Executable Scripts.  (line  42)
-* ARGIND variable:                       Auto-set.            (line  40)
+* ARGIND variable:                       Auto-set.            (line  44)
 * ARGIND variable, command-line arguments: Other Arguments.   (line  12)
 * arguments, command-line <1>:           ARGC and ARGV.       (line   6)
-* arguments, command-line <2>:           Auto-set.            (line  11)
+* arguments, command-line <2>:           Auto-set.            (line  15)
 * arguments, command-line:               Other Arguments.     (line   6)
 * arguments, command-line, invoking awk: Command Line.        (line   6)
-* arguments, in function calls:          Function Calls.      (line  16)
+* arguments, in function calls:          Function Calls.      (line  18)
 * arguments, processing:                 Getopt Function.     (line   6)
+* ARGV array, indexing into:             Other Arguments.     (line  12)
 * arithmetic operators:                  Arithmetic Ops.      (line   6)
+* array manipulation in extensions:      Array Manipulation.  (line   6)
+* array members:                         Reference to Elements.
+                                                              (line   6)
+* array scanning order, controlling:     Controlling Scanning.
+                                                              (line  14)
+* array, number of elements:             String Functions.    (line 197)
 * arrays:                                Arrays.              (line   6)
+* arrays of arrays:                      Arrays of Arrays.    (line   6)
+* arrays, an example of using:           Array Example.       (line   6)
+* arrays, and IGNORECASE variable:       Array Intro.         (line  92)
 * arrays, as parameters to functions:    Pass By Value/Reference.
                                                               (line  47)
-* arrays, associative:                   Array Intro.         (line  49)
+* arrays, associative:                   Array Intro.         (line  50)
 * arrays, associative, library functions and: Library Names.  (line  57)
 * arrays, deleting entire contents:      Delete.              (line  39)
-* arrays, elements, assigning:           Assigning Elements.  (line   6)
+* arrays, elements that don't exist:     Reference to Elements.
+                                                              (line  23)
+* arrays, elements, assigning values:    Assigning Elements.  (line   6)
 * arrays, elements, deleting:            Delete.              (line   6)
-* arrays, elements, order of:            Scanning an Array.   (line  48)
-* arrays, elements, referencing:         Reference to Elements.
-                                                              (line   6)
-* arrays, elements, retrieving number of: String Functions.   (line  32)
+* arrays, elements, order of access by in operator: Scanning an Array.
+                                                              (line  48)
+* arrays, elements, retrieving number of: String Functions.   (line  42)
 * arrays, for statement and:             Scanning an Array.   (line  20)
-* arrays, IGNORECASE variable and:       Array Intro.         (line  91)
-* arrays, indexing:                      Array Intro.         (line  49)
+* arrays, indexing:                      Array Intro.         (line  50)
 * arrays, merging into strings:          Join Function.       (line   6)
 * arrays, multidimensional:              Multidimensional.    (line  10)
 * arrays, multidimensional, scanning:    Multiscanning.       (line  11)
-* arrays, names of:                      Arrays.              (line  18)
+* arrays, names of, and names of functions/variables: Arrays. (line  18)
+* arrays, numeric subscripts:            Numeric Array Subscripts.
+                                                              (line   6)
+* arrays, referencing elements:          Reference to Elements.
+                                                              (line   6)
 * arrays, scanning:                      Scanning an Array.   (line   6)
 * arrays, sorting:                       Array Sorting Functions.
                                                               (line   6)
-* arrays, sorting, IGNORECASE variable and: Array Sorting Functions.
+* arrays, sorting, and IGNORECASE variable: Array Sorting Functions.
                                                               (line  83)
-* arrays, sparse:                        Array Intro.         (line  70)
-* arrays, subscripts:                    Numeric Array Subscripts.
-                                                              (line   6)
+* arrays, sparse:                        Array Intro.         (line  71)
 * arrays, subscripts, uninitialized variables as: Uninitialized Subscripts.
                                                               (line   6)
+* arrays, unassigned elements:           Reference to Elements.
+                                                              (line  18)
 * artificial intelligence, gawk and:     Distribution contents.
                                                               (line  52)
-* ASCII <1>:                             Glossary.            (line 141)
+* ASCII <1>:                             Glossary.            (line 133)
 * ASCII:                                 Ordinal Functions.   (line  45)
-* asort() function (gawk) <1>:           Array Sorting Functions.
+* asort <1>:                             Array Sorting Functions.
                                                               (line   6)
-* asort() function (gawk):               String Functions.    (line  32)
+* asort:                                 String Functions.    (line  42)
 * asort() function (gawk), arrays, sorting: Array Sorting Functions.
                                                               (line   6)
-* asorti() function (gawk) <1>:          Array Sorting Functions.
+* asorti <1>:                            Array Sorting Functions.
                                                               (line   6)
-* asorti() function (gawk):              String Functions.    (line  32)
+* asorti:                                String Functions.    (line  42)
 * asorti() function (gawk), arrays, sorting: Array Sorting Functions.
                                                               (line   6)
 * assert() function (C library):         Assert Function.     (line   6)
 * assert() user-defined function:        Assert Function.     (line  28)
 * assertions:                            Assert Function.     (line   6)
+* assign values to variables, in debugger: Viewing And Changing Data.
+                                                              (line  59)
 * assignment operators:                  Assignment Ops.      (line   6)
 * assignment operators, evaluation order: Assignment Ops.     (line 111)
 * assignment operators, lvalues/rvalues: Assignment Ops.      (line  32)
 * assignments as filenames:              Ignoring Assigns.    (line   6)
-* associative arrays:                    Array Intro.         (line  49)
+* associative arrays:                    Array Intro.         (line  50)
 * asterisk (*), * operator, as multiplication operator: Precedence.
                                                               (line  55)
 * asterisk (*), * operator, as regexp operator: Regexp Operators.
-                                                              (line  87)
+                                                              (line  88)
 * asterisk (*), * operator, null strings, matching: Gory Details.
                                                               (line 164)
 * asterisk (*), ** operator <1>:         Precedence.          (line  49)
 * asterisk (*), ** operator:             Arithmetic Ops.      (line  81)
 * asterisk (*), **= operator <1>:        Precedence.          (line  95)
-* asterisk (*), **= operator:            Assignment Ops.      (line 129)
+* asterisk (*), **= operator:            Assignment Ops.      (line 130)
 * asterisk (*), *= operator <1>:         Precedence.          (line  95)
-* asterisk (*), *= operator:             Assignment Ops.      (line 129)
-* atan2() function:                      Numeric Functions.   (line  11)
-* awf (amazingly workable formatter) program: Glossary.       (line  25)
-* awk debugging, enabling:               Options.             (line 122)
-* awk language, POSIX version:           Assignment Ops.      (line 136)
-* awk profiling, enabling:               Options.             (line 235)
+* asterisk (*), *= operator:             Assignment Ops.      (line 130)
+* atan2:                                 Numeric Functions.   (line  11)
+* automatic displays, in debugger:       Debugger Info.       (line  24)
+* awf (amazingly workable formatter) program: Glossary.       (line  24)
+* awk debugging, enabling:               Options.             (line 108)
+* awk language, POSIX version:           Assignment Ops.      (line 137)
+* awk profiling, enabling:               Options.             (line 242)
 * awk programs <1>:                      Two Rules.           (line   6)
 * awk programs <2>:                      Executable Scripts.  (line   6)
 * awk programs:                          Getting Started.     (line  12)
@@ -29813,11 +31349,11 @@ Index
 * awk, implementations, limits:          Getline Notes.       (line  14)
 * awk, invoking:                         Command Line.        (line   6)
 * awk, new vs. old:                      Names.               (line   6)
-* awk, new vs. old, OFMT variable:       Conversion.          (line  55)
+* awk, new vs. old, OFMT variable:       Strings And Numbers. (line  57)
 * awk, POSIX and:                        Preface.             (line  23)
 * awk, POSIX and, See Also POSIX awk:    Preface.             (line  23)
 * awk, regexp constants and:             Comparison Operators.
-                                                              (line 103)
+                                                              (line 102)
 * awk, See Also gawk:                    Preface.             (line  36)
 * awk, terms describing:                 This Manual.         (line   6)
 * awk, uses for <1>:                     When.                (line   6)
@@ -29834,16 +31370,14 @@ Index
 * awk, versions of, See Also Brian Kernighan's awk: BTL.      (line   6)
 * awka compiler for awk:                 Other Versions.      (line  64)
 * AWKLIBPATH environment variable:       AWKLIBPATH Variable. (line   6)
-* AWKPATH environment variable <1>:      PC Using.            (line  11)
+* AWKPATH environment variable <1>:      PC Using.            (line  10)
 * AWKPATH environment variable:          AWKPATH Variable.    (line   6)
 * awkprof.out file:                      Profiling.           (line   6)
 * awksed.awk program:                    Simple Sed.          (line  25)
-* awkvars.out file:                      Options.             (line 107)
+* awkvars.out file:                      Options.             (line  93)
 * b debugger command (alias for break):  Breakpoint Control.  (line  11)
-* backslash (\) <1>:                     Regexp Operators.    (line  18)
-* backslash (\) <2>:                     Quoting.             (line  31)
-* backslash (\) <3>:                     Comments.            (line  50)
-* backslash (\):                         Read Terminal.       (line  25)
+* backslash (\):                         Comments.            (line  50)
+* backslash (\) in shell commands:       Read Terminal.       (line  25)
 * backslash (\), \" escape sequence:     Escape Sequences.    (line  76)
 * backslash (\), \' operator (gawk):     GNU Regexp Operators.
                                                               (line  56)
@@ -29877,7 +31411,7 @@ Index
                                                               (line  38)
 * backslash (\), as field separator:     Command Line Field Separator.
                                                               (line  27)
-* backslash (\), continuing lines and <1>: Egrep Program.     (line 220)
+* backslash (\), continuing lines and <1>: Egrep Program.     (line 223)
 * backslash (\), continuing lines and:   Statements/Lines.    (line  19)
 * backslash (\), continuing lines and, comments and: Statements/Lines.
                                                               (line  76)
@@ -29889,18 +31423,19 @@ Index
 * backslash (\), in escape sequences:    Escape Sequences.    (line   6)
 * backslash (\), in escape sequences, POSIX and: Escape Sequences.
                                                               (line 112)
-* backslash (\), in regexp constants:    Computed Regexps.    (line  28)
+* backslash (\), in regexp constants:    Computed Regexps.    (line  29)
+* backslash (\), in shell commands:      Quoting.             (line  48)
+* backslash (\), regexp operator:        Regexp Operators.    (line  18)
 * backtrace debugger command:            Execution Stack.     (line  13)
-* BBS-list file:                         Sample Data Files.   (line   6)
-* Beebe, Nelson <1>:                     Other Versions.      (line  78)
-* Beebe, Nelson:                         Acknowledgments.     (line  60)
-* BEGIN pattern <1>:                     Profiling.           (line  62)
+* Beebe, Nelson H.F. <1>:                Other Versions.      (line  78)
+* Beebe, Nelson H.F.:                    Acknowledgments.     (line  60)
+* BEGIN pattern <1>:                     Using BEGIN/END.     (line   6)
 * BEGIN pattern <2>:                     BEGIN/END.           (line   6)
-* BEGIN pattern <3>:                     Field Separators.    (line  44)
-* BEGIN pattern:                         Records.             (line  29)
+* BEGIN pattern:                         Field Separators.    (line  45)
+* BEGIN pattern, and profiling:          Profiling.           (line  62)
 * BEGIN pattern, assert() user-defined function and: Assert Function.
                                                               (line  83)
-* BEGIN pattern, Boolean patterns and:   Expression Patterns. (line  73)
+* BEGIN pattern, Boolean patterns and:   Expression Patterns. (line  70)
 * BEGIN pattern, exit statement and:     Exit Statement.      (line  12)
 * BEGIN pattern, getline and:            Getline Notes.       (line  19)
 * BEGIN pattern, headings, adding:       Print Examples.      (line  43)
@@ -29917,40 +31452,47 @@ Index
 * BEGIN pattern, TEXTDOMAIN variable and: Programmer i18n.    (line  60)
 * BEGINFILE pattern:                     BEGINFILE/ENDFILE.   (line   6)
 * BEGINFILE pattern, Boolean patterns and: Expression Patterns.
-                                                              (line  73)
+                                                              (line  70)
 * beginfile() user-defined function:     Filetrans Function.  (line  62)
+* Bentley, Jon:                          Glossary.            (line 143)
 * Benzinger, Michael:                    Contributors.        (line  97)
+* Berry, Karl <1>:                       Ranges and Locales.  (line  74)
 * Berry, Karl:                           Acknowledgments.     (line  33)
-* binary input/output:                   User-modified.       (line  10)
-* bindtextdomain() function (C library): Explaining gettext.  (line  49)
-* bindtextdomain() function (gawk) <1>:  Programmer i18n.     (line  47)
-* bindtextdomain() function (gawk):      I18N Functions.      (line  12)
+* binary input/output:                   User-modified.       (line  15)
+* bindtextdomain <1>:                    Programmer i18n.     (line  47)
+* bindtextdomain:                        I18N Functions.      (line  12)
+* bindtextdomain() function (C library): Explaining gettext.  (line  50)
 * bindtextdomain() function (gawk), portability and: I18N Portability.
                                                               (line  33)
-* BINMODE variable <1>:                  PC Using.            (line  34)
-* BINMODE variable:                      User-modified.       (line  10)
+* BINMODE variable <1>:                  PC Using.            (line  33)
+* BINMODE variable:                      User-modified.       (line  15)
+* bit-manipulation functions:            Bitwise Functions.   (line   6)
 * bits2str() user-defined function:      Bitwise Functions.   (line  70)
+* bitwise AND:                           Bitwise Functions.   (line  39)
+* bitwise complement:                    Bitwise Functions.   (line  43)
+* bitwise OR:                            Bitwise Functions.   (line  49)
+* bitwise XOR:                           Bitwise Functions.   (line  55)
 * bitwise, complement:                   Bitwise Functions.   (line  25)
 * bitwise, operations:                   Bitwise Functions.   (line   6)
 * bitwise, shift:                        Bitwise Functions.   (line  32)
 * body, in actions:                      Statements.          (line  10)
 * body, in loops:                        While Statement.     (line  14)
 * Boolean expressions:                   Boolean Ops.         (line   6)
-* Boolean expressions, as patterns:      Expression Patterns. (line  41)
+* Boolean expressions, as patterns:      Expression Patterns. (line  39)
 * Boolean operators, See Boolean expressions: Boolean Ops.    (line   6)
 * Bourne shell, quoting rules for:       Quoting.             (line  18)
-* braces ({}):                           Profiling.           (line 134)
+* braces ({}):                           Profiling.           (line 142)
 * braces ({}), actions and:              Action Overview.     (line  19)
 * braces ({}), statements, grouping:     Statements.          (line  10)
 * bracket expressions <1>:               Bracket Expressions. (line   6)
-* bracket expressions:                   Regexp Operators.    (line  55)
+* bracket expressions:                   Regexp Operators.    (line  56)
 * bracket expressions, character classes: Bracket Expressions.
                                                               (line  30)
 * bracket expressions, collating elements: Bracket Expressions.
                                                               (line  69)
 * bracket expressions, collating symbols: Bracket Expressions.
                                                               (line  76)
-* bracket expressions, complemented:     Regexp Operators.    (line  63)
+* bracket expressions, complemented:     Regexp Operators.    (line  64)
 * bracket expressions, equivalence classes: Bracket Expressions.
                                                               (line  82)
 * bracket expressions, non-ASCII:        Bracket Expressions. (line  69)
@@ -29958,23 +31500,51 @@ Index
                                                               (line   6)
 * break debugger command:                Breakpoint Control.  (line  11)
 * break statement:                       Break Statement.     (line   6)
+* breakpoint:                            Debugging Terms.     (line  33)
+* breakpoint at location, how to delete: Breakpoint Control.  (line  36)
+* breakpoint commands:                   Debugger Execution Control.
+                                                              (line  10)
+* breakpoint condition:                  Breakpoint Control.  (line  54)
+* breakpoint, delete by number:          Breakpoint Control.  (line  64)
+* breakpoint, how to disable or enable:  Breakpoint Control.  (line  69)
+* breakpoint, setting:                   Breakpoint Control.  (line  11)
 * Brennan, Michael <1>:                  Other Versions.      (line   6)
 * Brennan, Michael <2>:                  Two-way I/O.         (line   6)
 * Brennan, Michael <3>:                  Simple Sed.          (line  25)
-* Brennan, Michael:                      Delete.              (line  56)
-* Brian Kernighan's awk:                 Other Versions.      (line  13)
+* Brennan, Michael <4>:                  Delete.              (line  56)
+* Brennan, Michael:                      Foreword.            (line  83)
+* Brian Kernighan's awk <1>:             I/O Functions.       (line  43)
+* Brian Kernighan's awk <2>:             Gory Details.        (line  15)
+* Brian Kernighan's awk <3>:             String Functions.    (line 490)
+* Brian Kernighan's awk <4>:             Delete.              (line  48)
+* Brian Kernighan's awk <5>:             Nextfile Statement.  (line  47)
+* Brian Kernighan's awk <6>:             Continue Statement.  (line  43)
+* Brian Kernighan's awk <7>:             Break Statement.     (line  51)
+* Brian Kernighan's awk <8>:             I/O And BEGIN/END.   (line  16)
+* Brian Kernighan's awk <9>:             Concatenation.       (line  36)
+* Brian Kernighan's awk <10>:            Getline/Pipe.        (line  62)
+* Brian Kernighan's awk <11>:            Regexp Field Splitting.
+                                                              (line  67)
+* Brian Kernighan's awk <12>:            GNU Regexp Operators.
+                                                              (line  83)
+* Brian Kernighan's awk <13>:            Escape Sequences.    (line 116)
+* Brian Kernighan's awk <14>:            When.                (line  21)
+* Brian Kernighan's awk:                 Preface.             (line  15)
 * Brian Kernighan's awk, extensions:     BTL.                 (line   6)
+* Brian Kernighan's awk, source code:    Other Versions.      (line  13)
+* Brini, Davide:                         Signature Program.   (line   6)
+* Brink, Jeroen:                         DOS Quoting.         (line  10)
 * Broder, Alan J.:                       Contributors.        (line  88)
 * Brown, Martin:                         Contributors.        (line  82)
-* BSD-based operating systems:           Glossary.            (line 624)
+* BSD-based operating systems:           Glossary.            (line 611)
 * bt debugger command (alias for backtrace): Execution Stack. (line  13)
 * Buening, Andreas <1>:                  Bugs.                (line  71)
 * Buening, Andreas <2>:                  Contributors.        (line  92)
 * Buening, Andreas:                      Acknowledgments.     (line  60)
 * buffering, input/output <1>:           Two-way I/O.         (line  70)
-* buffering, input/output:               I/O Functions.       (line 137)
-* buffering, interactive vs. noninteractive: I/O Functions.   (line 106)
-* buffers, flushing:                     I/O Functions.       (line  29)
+* buffering, input/output:               I/O Functions.       (line 140)
+* buffering, interactive vs. noninteractive: I/O Functions.   (line 109)
+* buffers, flushing:                     I/O Functions.       (line  32)
 * buffers, operators for:                GNU Regexp Operators.
                                                               (line  48)
 * bug reports, email address, bug-gawk@gnu.org: Bugs.         (line  30)
@@ -29982,7 +31552,7 @@ Index
 * built-in functions:                    Functions.           (line   6)
 * built-in functions, evaluation order:  Calling Built-in.    (line  30)
 * built-in variables:                    Built-in Variables.  (line   6)
-* built-in variables, -v option, setting with: Options.       (line  54)
+* built-in variables, -v option, setting with: Options.       (line  40)
 * built-in variables, conveying information: Auto-set.        (line   6)
 * built-in variables, user-modifiable:   User-modified.       (line   6)
 * Busybox Awk:                           Other Versions.      (line  88)
@@ -29990,36 +31560,40 @@ Index
                                                               (line  47)
 * call by value:                         Pass By Value/Reference.
                                                               (line  18)
-* caret (^):                             GNU Regexp Operators.
-                                                              (line  59)
+* call stack, display in debugger:       Execution Stack.     (line  13)
 * caret (^), ^ operator:                 Precedence.          (line  49)
 * caret (^), ^= operator <1>:            Precedence.          (line  95)
-* caret (^), ^= operator:                Assignment Ops.      (line 129)
+* caret (^), ^= operator:                Assignment Ops.      (line 130)
 * caret (^), in bracket expressions:     Bracket Expressions. (line  17)
+* caret (^), regexp operator <1>:        GNU Regexp Operators.
+                                                              (line  59)
 * caret (^), regexp operator:            Regexp Operators.    (line  22)
 * case keyword:                          Switch Statement.    (line   6)
-* case sensitivity, array indices and:   Array Intro.         (line  91)
-* case sensitivity, converting case:     String Functions.    (line 519)
+* case sensitivity, and regexps:         User-modified.       (line  76)
+* case sensitivity, and string comparisons: User-modified.    (line  76)
+* case sensitivity, array indices and:   Array Intro.         (line  92)
+* case sensitivity, converting case:     String Functions.    (line 520)
 * case sensitivity, example programs:    Library Functions.   (line  53)
 * case sensitivity, gawk:                Case-sensitivity.    (line  26)
-* case sensitivity, regexps and <1>:     User-modified.       (line  82)
 * case sensitivity, regexps and:         Case-sensitivity.    (line   6)
-* case sensitivity, string comparisons and: User-modified.    (line  82)
-* CGI, awk scripts for:                  Options.             (line 139)
-* character lists, See bracket expressions: Regexp Operators. (line  55)
-* character sets (machine character encodings) <1>: Glossary. (line 141)
+* CGI, awk scripts for:                  Options.             (line 125)
+* character classes, See bracket expressions: Regexp Operators.
+                                                              (line  56)
+* character lists in regular expression: Bracket Expressions. (line   6)
+* character lists, See bracket expressions: Regexp Operators. (line  56)
+* character sets (machine character encodings) <1>: Glossary. (line 133)
 * character sets (machine character encodings): Ordinal Functions.
                                                               (line  45)
 * character sets, See Also bracket expressions: Regexp Operators.
-                                                              (line  55)
+                                                              (line  56)
 * characters, counting:                  Wc Program.          (line   6)
 * characters, transliterating:           Translate Program.   (line   6)
 * characters, values of as numbers:      Ordinal Functions.   (line   6)
 * Chassell, Robert J.:                   Acknowledgments.     (line  33)
-* chdir extension function:              Extension Sample File Functions.
+* chdir() extension function:            Extension Sample File Functions.
                                                               (line  12)
-* chem utility:                          Glossary.            (line 151)
-* chr extension function:                Extension Sample Ord.
+* chem utility:                          Glossary.            (line 143)
+* chr() extension function:              Extension Sample Ord.
                                                               (line  15)
 * chr() user-defined function:           Ordinal Functions.   (line  16)
 * clear debugger command:                Breakpoint Control.  (line  36)
@@ -30027,26 +31601,28 @@ Index
                                                               (line   6)
 * cliff_rand() user-defined function:    Cliff Random Function.
                                                               (line  12)
-* close() function <1>:                  I/O Functions.       (line  10)
-* close() function <2>:                  Close Files And Pipes.
+* close <1>:                             I/O Functions.       (line  10)
+* close:                                 Close Files And Pipes.
                                                               (line  18)
-* close() function <3>:                  Getline/Pipe.        (line  27)
-* close() function:                      Getline/Variable/File.
-                                                              (line  30)
+* close file or coprocess:               I/O Functions.       (line  10)
+* close() function, portability:         Close Files And Pipes.
+                                                              (line  81)
 * close() function, return value:        Close Files And Pipes.
-                                                              (line 130)
+                                                              (line 131)
 * close() function, two-way pipes and:   Two-way I/O.         (line  77)
 * Close, Diane <1>:                      Contributors.        (line  20)
 * Close, Diane:                          Manual History.      (line  41)
 * Collado, Manuel:                       Acknowledgments.     (line  60)
 * collating elements:                    Bracket Expressions. (line  69)
 * collating symbols:                     Bracket Expressions. (line  76)
+* Colombo, Antonio <1>:                  Contributors.        (line 137)
 * Colombo, Antonio:                      Acknowledgments.     (line  60)
 * columns, aligning:                     Print Examples.      (line  70)
 * columns, cutting:                      Cut Program.         (line   6)
 * comma (,), in range patterns:          Ranges.              (line   6)
+* command completion, in debugger:       Readline Support.    (line   6)
 * command line, arguments <1>:           ARGC and ARGV.       (line   6)
-* command line, arguments <2>:           Auto-set.            (line  11)
+* command line, arguments <2>:           Auto-set.            (line  15)
 * command line, arguments:               Other Arguments.     (line   6)
 * command line, directories on:          Command line directories.
                                                               (line   6)
@@ -30054,52 +31630,52 @@ Index
 * command line, FS on, setting:          Command Line Field Separator.
                                                               (line   6)
 * command line, invoking awk from:       Command Line.        (line   6)
-* command line, options <1>:             Command Line Field Separator.
-                                                              (line   6)
-* command line, options <2>:             Options.             (line   6)
-* command line, options:                 Long.                (line  12)
-* command line, options, end of:         Options.             (line  68)
+* command line, option -f:               Long.                (line  12)
+* command line, options:                 Options.             (line   6)
+* command line, options, end of:         Options.             (line  54)
 * command line, variables, assigning on: Assignment Options.  (line   6)
 * command-line options, processing:      Getopt Function.     (line   6)
 * command-line options, string extraction: String Extraction. (line   6)
 * commands debugger command:             Debugger Execution Control.
                                                               (line  10)
+* commands to execute at breakpoint:     Debugger Execution Control.
+                                                              (line  10)
 * commenting:                            Comments.            (line   6)
 * commenting, backslash continuation and: Statements/Lines.   (line  76)
 * common extensions, ** operator:        Arithmetic Ops.      (line  30)
-* common extensions, **= operator:       Assignment Ops.      (line 136)
+* common extensions, **= operator:       Assignment Ops.      (line 137)
 * common extensions, /dev/stderr special file: Special FD.    (line  46)
 * common extensions, /dev/stdin special file: Special FD.     (line  46)
 * common extensions, /dev/stdout special file: Special FD.    (line  46)
 * common extensions, \x escape sequence: Escape Sequences.    (line  61)
-* common extensions, BINMODE variable:   PC Using.            (line  34)
+* common extensions, BINMODE variable:   PC Using.            (line  33)
 * common extensions, delete to delete entire arrays: Delete.  (line  39)
-* common extensions, func keyword:       Definition Syntax.   (line  83)
+* common extensions, func keyword:       Definition Syntax.   (line  89)
 * common extensions, length() applied to an array: String Functions.
-                                                              (line 193)
-* common extensions, RS as a regexp:     Records.             (line 120)
+                                                              (line 197)
+* common extensions, RS as a regexp:     gawk split records.  (line   6)
 * common extensions, single character fields: Single Character Fields.
                                                               (line   6)
-* comp.lang.awk newsgroup:               Bugs.                (line  38)
+* comp.lang.awk newsgroup:               Bugs.                (line  39)
 * comparison expressions:                Typing and Comparison.
                                                               (line   9)
 * comparison expressions, as patterns:   Expression Patterns. (line  14)
 * comparison expressions, string vs. regexp: Comparison Operators.
-                                                              (line  79)
+                                                              (line  78)
 * compatibility mode (gawk), extensions: POSIX/GNU.           (line   6)
 * compatibility mode (gawk), file names: Special Caveats.     (line   9)
 * compatibility mode (gawk), hexadecimal numbers: Nondecimal-numbers.
                                                               (line  60)
 * compatibility mode (gawk), octal numbers: Nondecimal-numbers.
                                                               (line  60)
-* compatibility mode (gawk), specifying: Options.             (line  95)
-* compiled programs <1>:                 Glossary.            (line 165)
+* compatibility mode (gawk), specifying: Options.             (line  81)
+* compiled programs <1>:                 Glossary.            (line 157)
 * compiled programs:                     Basic High Level.    (line  15)
 * compiling gawk for Cygwin:             Cygwin.              (line   6)
 * compiling gawk for MS-DOS and MS-Windows: PC Compiling.     (line  13)
 * compiling gawk for VMS:                VMS Compilation.     (line   6)
 * compiling gawk with EMX for OS/2:      PC Compiling.        (line  28)
-* compl() function (gawk):               Bitwise Functions.   (line  43)
+* compl:                                 Bitwise Functions.   (line  43)
 * complement, bitwise:                   Bitwise Functions.   (line  25)
 * compound statements, control statements and: Statements.    (line  10)
 * concatenating:                         Concatenation.       (line   8)
@@ -30115,105 +31691,115 @@ Index
                                                               (line  35)
 * configuration options, gawk:           Additional Configuration Options.
                                                               (line   6)
-* constants, floating-point:             Floating-point Constants.
-                                                              (line   6)
+* constant regexps:                      Regexp Usage.        (line  57)
 * constants, nondecimal:                 Nondecimal Data.     (line   6)
+* constants, numeric:                    Scalar Constants.    (line   6)
 * constants, types of:                   Constants.           (line   6)
-* context, floating-point:               Floating-point Context.
-                                                              (line   6)
+* continue program, in debugger:         Debugger Execution Control.
+                                                              (line  33)
 * continue statement:                    Continue Statement.  (line   6)
 * control statements:                    Statements.          (line   6)
-* converting, case:                      String Functions.    (line 519)
-* converting, dates to timestamps:       Time Functions.      (line  75)
-* converting, during subscripting:       Numeric Array Subscripts.
+* controlling array scanning order:      Controlling Scanning.
+                                                              (line  14)
+* convert string to lower case:          String Functions.    (line 521)
+* convert string to number:              String Functions.    (line 388)
+* convert string to upper case:          String Functions.    (line 527)
+* converting integer array subscripts:   Numeric Array Subscripts.
                                                               (line  31)
+* converting, dates to timestamps:       Time Functions.      (line  76)
 * converting, numbers to strings <1>:    Bitwise Functions.   (line 109)
-* converting, numbers to strings:        Conversion.          (line   6)
+* converting, numbers to strings:        Strings And Numbers. (line   6)
 * converting, strings to numbers <1>:    Bitwise Functions.   (line 109)
-* converting, strings to numbers:        Conversion.          (line   6)
-* CONVFMT variable <1>:                  User-modified.       (line  28)
-* CONVFMT variable:                      Conversion.          (line  29)
-* CONVFMT variable, array subscripts and: Numeric Array Subscripts.
+* converting, strings to numbers:        Strings And Numbers. (line   6)
+* CONVFMT variable <1>:                  User-modified.       (line  30)
+* CONVFMT variable:                      Strings And Numbers. (line  29)
+* CONVFMT variable, and array subscripts: Numeric Array Subscripts.
                                                               (line   6)
-* cookie:                                Glossary.            (line 157)
+* cookie:                                Glossary.            (line 149)
 * coprocesses <1>:                       Two-way I/O.         (line  44)
 * coprocesses:                           Redirection.         (line 102)
 * coprocesses, closing:                  Close Files And Pipes.
                                                               (line   6)
 * coprocesses, getline from:             Getline/Coprocess.   (line   6)
-* cos() function:                        Numeric Functions.   (line  15)
+* cos:                                   Numeric Functions.   (line  15)
+* cosine:                                Numeric Functions.   (line  15)
 * counting:                              Wc Program.          (line   6)
 * csh utility:                           Statements/Lines.    (line  44)
-* csh utility, POSIXLY_CORRECT environment variable: Options. (line 348)
+* csh utility, POSIXLY_CORRECT environment variable: Options. (line 355)
 * csh utility, |& operator, comparison with: Two-way I/O.     (line  44)
-* ctime() user-defined function:         Function Example.    (line  72)
-* currency symbols, localization:        Explaining gettext.  (line 103)
+* ctime() user-defined function:         Function Example.    (line  73)
+* currency symbols, localization:        Explaining gettext.  (line 104)
+* current system time:                   Time Functions.      (line  66)
 * custom.h file:                         Configuration Philosophy.
                                                               (line  30)
+* customized input parser:               Input Parsers.       (line   6)
+* customized output wrapper:             Output Wrappers.     (line   6)
+* customized two-way processor:          Two-way processors.  (line   6)
 * cut utility:                           Cut Program.         (line   6)
 * cut.awk program:                       Cut Program.         (line  45)
 * d debugger command (alias for delete): Breakpoint Control.  (line  64)
 * d.c., See dark corner:                 Conventions.         (line  38)
-* dark corner <1>:                       Glossary.            (line 197)
+* dark corner <1>:                       Glossary.            (line 188)
 * dark corner:                           Conventions.         (line  38)
 * dark corner, "0" is actually true:     Truth Values.        (line  24)
 * dark corner, /= operator vs. /=.../ regexp constant: Assignment Ops.
-                                                              (line 147)
+                                                              (line 148)
 * dark corner, ^, in FS:                 Regexp Field Splitting.
                                                               (line  59)
 * dark corner, array subscripts:         Uninitialized Subscripts.
                                                               (line  43)
 * dark corner, break statement:          Break Statement.     (line  51)
 * dark corner, close() function:         Close Files And Pipes.
-                                                              (line 130)
+                                                              (line 131)
 * dark corner, command-line arguments:   Assignment Options.  (line  43)
 * dark corner, continue statement:       Continue Statement.  (line  43)
-* dark corner, CONVFMT variable:         Conversion.          (line  40)
+* dark corner, CONVFMT variable:         Strings And Numbers. (line  40)
 * dark corner, escape sequences:         Other Arguments.     (line  31)
 * dark corner, escape sequences, for metacharacters: Escape Sequences.
                                                               (line 134)
 * dark corner, exit statement:           Exit Statement.      (line  30)
 * dark corner, field separators:         Field Splitting Summary.
                                                               (line  46)
-* dark corner, FILENAME variable <1>:    Auto-set.            (line 102)
+* dark corner, FILENAME variable <1>:    Auto-set.            (line  98)
 * dark corner, FILENAME variable:        Getline Notes.       (line  19)
-* dark corner, FNR/NR variables:         Auto-set.            (line 323)
+* dark corner, FNR/NR variables:         Auto-set.            (line 309)
 * dark corner, format-control characters: Control Letters.    (line  18)
 * dark corner, FS as null string:        Single Character Fields.
                                                               (line  20)
-* dark corner, input files:              Records.             (line 103)
+* dark corner, input files:              awk split records.   (line 110)
 * dark corner, invoking awk:             Command Line.        (line  16)
-* dark corner, length() function:        String Functions.    (line 179)
-* dark corner, locale's decimal point character: Conversion.  (line  77)
+* dark corner, length() function:        String Functions.    (line 183)
+* dark corner, locale's decimal point character: Locale influences conversions.
+                                                              (line  17)
 * dark corner, multiline records:        Multiple Line.       (line  35)
 * dark corner, NF variable, decrementing: Changing Fields.    (line 107)
 * dark corner, OFMT variable:            OFMT.                (line  27)
 * dark corner, regexp constants:         Using Constant Regexps.
                                                               (line   6)
 * dark corner, regexp constants, /= operator and: Assignment Ops.
-                                                              (line 147)
+                                                              (line 148)
 * dark corner, regexp constants, as arguments to user-defined functions: Using Constant Regexps.
                                                               (line  43)
-* dark corner, split() function:         String Functions.    (line 358)
-* dark corner, strings, storing:         Records.             (line 195)
-* dark corner, value of ARGV[0]:         Auto-set.            (line  35)
-* data, fixed-width:                     Constant Size.       (line   9)
+* dark corner, split() function:         String Functions.    (line 359)
+* dark corner, strings, storing:         gawk split records.  (line  83)
+* dark corner, value of ARGV[0]:         Auto-set.            (line  39)
+* data, fixed-width:                     Constant Size.       (line  10)
 * data-driven languages:                 Basic High Level.    (line  85)
 * database, group, reading:              Group Functions.     (line   6)
 * database, users, reading:              Passwd Functions.    (line   6)
 * date utility, GNU:                     Time Functions.      (line  17)
-* date utility, POSIX:                   Time Functions.      (line 262)
-* dates, converting to timestamps:       Time Functions.      (line  75)
+* date utility, POSIX:                   Time Functions.      (line 254)
+* dates, converting to timestamps:       Time Functions.      (line  76)
 * dates, information related to, localization: Explaining gettext.
-                                                              (line 115)
+                                                              (line 116)
 * Davies, Stephen <1>:                   Contributors.        (line  74)
 * Davies, Stephen:                       Acknowledgments.     (line  60)
-* dcgettext() function (gawk) <1>:       Programmer i18n.     (line  19)
-* dcgettext() function (gawk):           I18N Functions.      (line  22)
+* dcgettext <1>:                         Programmer i18n.     (line  19)
+* dcgettext:                             I18N Functions.      (line  22)
 * dcgettext() function (gawk), portability and: I18N Portability.
                                                               (line  33)
-* dcngettext() function (gawk) <1>:      Programmer i18n.     (line  36)
-* dcngettext() function (gawk):          I18N Functions.      (line  28)
+* dcngettext <1>:                        Programmer i18n.     (line  36)
+* dcngettext:                            I18N Functions.      (line  28)
 * dcngettext() function (gawk), portability and: I18N Portability.
                                                               (line  33)
 * deadlocks:                             Two-way I/O.         (line  70)
@@ -30308,28 +31894,41 @@ Index
                                                               (line  83)
 * debugger commands, unwatch:            Viewing And Changing Data.
                                                               (line  84)
-* debugger commands, up:                 Execution Stack.     (line  33)
+* debugger commands, up:                 Execution Stack.     (line  34)
 * debugger commands, w (watch):          Viewing And Changing Data.
                                                               (line  67)
 * debugger commands, watch:              Viewing And Changing Data.
                                                               (line  67)
+* debugger default list amount:          Debugger Info.       (line  69)
+* debugger history file:                 Debugger Info.       (line  80)
+* debugger history size:                 Debugger Info.       (line  65)
+* debugger options:                      Debugger Info.       (line  57)
+* debugger prompt:                       Debugger Info.       (line  77)
+* debugger, how to start:                Debugger Invocation. (line   6)
+* debugger, read commands from a file:   Debugger Info.       (line  96)
 * debugging awk programs:                Debugger.            (line   6)
 * debugging gawk, bug reports:           Bugs.                (line   9)
-* decimal point character, locale specific: Options.          (line 263)
+* decimal point character, locale specific: Options.          (line 270)
 * decrement operators:                   Increment Ops.       (line  35)
 * default keyword:                       Switch Statement.    (line   6)
-* Deifik, Scott <1>:                     Bugs.                (line  70)
+* Deifik, Scott <1>:                     Bugs.                (line  71)
 * Deifik, Scott <2>:                     Contributors.        (line  53)
 * Deifik, Scott:                         Acknowledgments.     (line  60)
+* delete ARRAY:                          Delete.              (line  39)
+* delete breakpoint at location:         Breakpoint Control.  (line  36)
+* delete breakpoint by number:           Breakpoint Control.  (line  64)
 * delete debugger command:               Breakpoint Control.  (line  64)
 * delete statement:                      Delete.              (line   6)
+* delete watchpoint:                     Viewing And Changing Data.
+                                                              (line  84)
 * deleting elements in arrays:           Delete.              (line   6)
 * deleting entire arrays:                Delete.              (line  39)
 * Demaille, Akim:                        Acknowledgments.     (line  60)
-* differences between gawk and awk:      String Functions.    (line 193)
+* describe call stack frame, in debugger: Debugger Info.      (line  27)
+* differences between gawk and awk:      String Functions.    (line 197)
 * differences in awk and gawk, ARGC/ARGV variables: ARGC and ARGV.
                                                               (line  88)
-* differences in awk and gawk, ARGIND variable: Auto-set.     (line  40)
+* differences in awk and gawk, ARGIND variable: Auto-set.     (line  44)
 * differences in awk and gawk, array elements, deleting: Delete.
                                                               (line  39)
 * differences in awk and gawk, AWKLIBPATH environment variable: AWKLIBPATH Variable.
@@ -30341,22 +31940,24 @@ Index
 * differences in awk and gawk, BEGINFILE/ENDFILE patterns: BEGINFILE/ENDFILE.
                                                               (line   6)
 * differences in awk and gawk, BINMODE variable <1>: PC Using.
-                                                              (line  34)
+                                                              (line  33)
 * differences in awk and gawk, BINMODE variable: User-modified.
-                                                              (line  23)
+                                                              (line  15)
 * differences in awk and gawk, close() function: Close Files And Pipes.
                                                               (line  81)
+* differences in awk and gawk, command line directories: Command line directories.
+                                                              (line   6)
 * differences in awk and gawk, ERRNO variable: Auto-set.      (line  82)
 * differences in awk and gawk, error messages: Special FD.    (line  16)
 * differences in awk and gawk, FIELDWIDTHS variable: User-modified.
-                                                              (line  35)
-* differences in awk and gawk, FPAT variable: User-modified.  (line  45)
-* differences in awk and gawk, FUNCTAB variable: Auto-set.    (line 128)
+                                                              (line  37)
+* differences in awk and gawk, FPAT variable: User-modified.  (line  43)
+* differences in awk and gawk, FUNCTAB variable: Auto-set.    (line 123)
 * differences in awk and gawk, function arguments (gawk): Calling Built-in.
                                                               (line  16)
 * differences in awk and gawk, getline command: Getline.      (line  19)
 * differences in awk and gawk, IGNORECASE variable: User-modified.
-                                                              (line  82)
+                                                              (line  76)
 * differences in awk and gawk, implementation limitations <1>: Redirection.
                                                               (line 135)
 * differences in awk and gawk, implementation limitations: Getline Notes.
@@ -30369,85 +31970,100 @@ Index
                                                               (line   6)
 * differences in awk and gawk, line continuations: Conditional Exp.
                                                               (line  34)
-* differences in awk and gawk, LINT variable: User-modified.  (line  98)
+* differences in awk and gawk, LINT variable: User-modified.  (line  88)
 * differences in awk and gawk, match() function: String Functions.
-                                                              (line 256)
+                                                              (line 260)
 * differences in awk and gawk, print/printf statements: Format Modifiers.
                                                               (line  13)
-* differences in awk and gawk, PROCINFO array: Auto-set.      (line 142)
-* differences in awk and gawk, record separators: Records.    (line 117)
+* differences in awk and gawk, PROCINFO array: Auto-set.      (line 136)
+* differences in awk and gawk, read timeouts: Read Timeout.   (line   6)
+* differences in awk and gawk, record separators: awk split records.
+                                                              (line 124)
 * differences in awk and gawk, regexp constants: Using Constant Regexps.
                                                               (line  43)
 * differences in awk and gawk, regular expressions: Case-sensitivity.
                                                               (line  26)
-* differences in awk and gawk, RS/RT variables: Records.      (line 172)
-* differences in awk and gawk, RT variable: Auto-set.         (line 275)
+* differences in awk and gawk, RS/RT variables: gawk split records.
+                                                              (line  58)
+* differences in awk and gawk, RT variable: Auto-set.         (line 265)
 * differences in awk and gawk, single-character fields: Single Character Fields.
                                                               (line   6)
 * differences in awk and gawk, split() function: String Functions.
-                                                              (line 346)
+                                                              (line 347)
 * differences in awk and gawk, strings:  Scalar Constants.    (line  20)
-* differences in awk and gawk, strings, storing: Records.     (line 191)
-* differences in awk and gawk, strtonum() function (gawk): String Functions.
-                                                              (line 401)
-* differences in awk and gawk, SYMTAB variable: Auto-set.     (line 283)
+* differences in awk and gawk, strings, storing: gawk split records.
+                                                              (line  77)
+* differences in awk and gawk, SYMTAB variable: Auto-set.     (line 269)
 * differences in awk and gawk, TEXTDOMAIN variable: User-modified.
-                                                              (line 162)
+                                                              (line 152)
 * differences in awk and gawk, trunc-mod operation: Arithmetic Ops.
                                                               (line  66)
 * directories, command line:             Command line directories.
                                                               (line   6)
-* directories, searching <1>:            Igawk Program.       (line 368)
-* directories, searching <2>:            AWKLIBPATH Variable. (line   6)
-* directories, searching:                AWKPATH Variable.    (line   6)
+* directories, searching:                Programs Exercises.  (line  63)
+* directories, searching for loadable extensions: AWKLIBPATH Variable.
+                                                              (line   6)
+* directories, searching for source files: AWKPATH Variable.  (line   6)
+* disable breakpoint:                    Breakpoint Control.  (line  69)
 * disable debugger command:              Breakpoint Control.  (line  69)
 * display debugger command:              Viewing And Changing Data.
                                                               (line   8)
+* display debugger options:              Debugger Info.       (line  57)
 * division:                              Arithmetic Ops.      (line  44)
-* do-while statement <1>:                Do Statement.        (line   6)
-* do-while statement:                    Regexp Usage.        (line  19)
+* do-while statement:                    Do Statement.        (line   6)
+* do-while statement, use of regexps in: Regexp Usage.        (line  19)
 * documentation, of awk programs:        Library Names.       (line   6)
 * documentation, online:                 Manual History.      (line  11)
 * documents, searching:                  Dupword Program.     (line   6)
-* dollar sign ($):                       Regexp Operators.    (line  35)
 * dollar sign ($), $ field operator <1>: Precedence.          (line  43)
 * dollar sign ($), $ field operator:     Fields.              (line  19)
 * dollar sign ($), incrementing fields and arrays: Increment Ops.
                                                               (line  30)
-* double precision floating-point:       General Arithmetic.  (line  21)
-* double quote (") <1>:                  Quoting.             (line  37)
-* double quote ("):                      Read Terminal.       (line  25)
-* double quote ("), in regexp constants: Computed Regexps.    (line  28)
+* dollar sign ($), regexp operator:      Regexp Operators.    (line  35)
+* double quote (") in shell commands:    Read Terminal.       (line  25)
+* double quote ("), in regexp constants: Computed Regexps.    (line  29)
+* double quote ("), in shell commands:   Quoting.             (line  54)
 * down debugger command:                 Execution Stack.     (line  21)
 * Drepper, Ulrich:                       Acknowledgments.     (line  52)
+* dump all variables of a program:       Options.             (line  93)
 * dump debugger command:                 Miscellaneous Debugger Commands.
                                                               (line   9)
 * dupword.awk program:                   Dupword Program.     (line  31)
+* dynamic profiling:                     Profiling.           (line 179)
+* dynamically loaded extensions:         Dynamic Extensions.  (line   6)
 * e debugger command (alias for enable): Breakpoint Control.  (line  73)
 * EBCDIC:                                Ordinal Functions.   (line  45)
+* effective group ID of gawk user:       Auto-set.            (line 141)
+* effective user ID of gawk user:        Auto-set.            (line 145)
 * egrep utility <1>:                     Egrep Program.       (line   6)
 * egrep utility:                         Bracket Expressions. (line  24)
 * egrep.awk program:                     Egrep Program.       (line  54)
-* elements in arrays:                    Reference to Elements.
-                                                              (line   6)
-* elements in arrays, assigning:         Assigning Elements.  (line   6)
+* elements in arrays, assigning values:  Assigning Elements.  (line   6)
 * elements in arrays, deleting:          Delete.              (line   6)
-* elements in arrays, order of:          Scanning an Array.   (line  48)
+* elements in arrays, order of access by in operator: Scanning an Array.
+                                                              (line  48)
 * elements in arrays, scanning:          Scanning an Array.   (line   6)
+* elements of arrays:                    Reference to Elements.
+                                                              (line   6)
 * email address for bug reports, bug-gawk@gnu.org: Bugs.      (line  30)
 * EMISTERED:                             TCP/IP Networking.   (line   6)
+* empty array elements:                  Reference to Elements.
+                                                              (line  18)
 * empty pattern:                         Empty.               (line   6)
+* empty strings:                         awk split records.   (line 114)
 * empty strings, See null strings:       Regexp Field Splitting.
                                                               (line  43)
+* enable breakpoint:                     Breakpoint Control.  (line  73)
 * enable debugger command:               Breakpoint Control.  (line  73)
 * end debugger command:                  Debugger Execution Control.
                                                               (line  10)
-* END pattern <1>:                       Profiling.           (line  62)
+* END pattern <1>:                       Using BEGIN/END.     (line   6)
 * END pattern:                           BEGIN/END.           (line   6)
+* END pattern, and profiling:            Profiling.           (line  62)
 * END pattern, assert() user-defined function and: Assert Function.
                                                               (line  75)
-* END pattern, backslash continuation and: Egrep Program.     (line 220)
-* END pattern, Boolean patterns and:     Expression Patterns. (line  73)
+* END pattern, backslash continuation and: Egrep Program.     (line 223)
+* END pattern, Boolean patterns and:     Expression Patterns. (line  70)
 * END pattern, exit statement and:       Exit Statement.      (line  12)
 * END pattern, next/nextfile statements and <1>: Next Statement.
                                                               (line  45)
@@ -30456,39 +32072,44 @@ Index
 * END pattern, operators and:            Using BEGIN/END.     (line  17)
 * END pattern, print statement and:      I/O And BEGIN/END.   (line  16)
 * ENDFILE pattern:                       BEGINFILE/ENDFILE.   (line   6)
-* ENDFILE pattern, Boolean patterns and: Expression Patterns. (line  73)
+* ENDFILE pattern, Boolean patterns and: Expression Patterns. (line  70)
 * endfile() user-defined function:       Filetrans Function.  (line  62)
-* endgrent() function (C library):       Group Functions.     (line 215)
-* endgrent() user-defined function:      Group Functions.     (line 218)
+* endgrent() function (C library):       Group Functions.     (line 213)
+* endgrent() user-defined function:      Group Functions.     (line 216)
 * endpwent() function (C library):       Passwd Functions.    (line 210)
 * endpwent() user-defined function:      Passwd Functions.    (line 213)
+* English, Steve:                        Advanced Features.   (line   6)
 * ENVIRON array:                         Auto-set.            (line  60)
-* environment variables:                 Auto-set.            (line  60)
-* epoch, definition of:                  Glossary.            (line 243)
+* environment variables used by gawk:    Environment Variables.
+                                                              (line   6)
+* environment variables, in ENVIRON array: Auto-set.          (line  60)
+* epoch, definition of:                  Glossary.            (line 234)
 * equals sign (=), = operator:           Assignment Ops.      (line   6)
 * equals sign (=), == operator <1>:      Precedence.          (line  65)
 * equals sign (=), == operator:          Comparison Operators.
                                                               (line  11)
 * EREs (Extended Regular Expressions):   Bracket Expressions. (line  24)
 * ERRNO variable <1>:                    TCP/IP Networking.   (line  54)
-* ERRNO variable <2>:                    Auto-set.            (line  82)
-* ERRNO variable <3>:                    BEGINFILE/ENDFILE.   (line  26)
-* ERRNO variable <4>:                    Close Files And Pipes.
-                                                              (line 138)
-* ERRNO variable:                        Getline.             (line  19)
+* ERRNO variable:                        Auto-set.            (line  82)
+* ERRNO variable, with BEGINFILE pattern: BEGINFILE/ENDFILE.  (line  26)
+* ERRNO variable, with close() function: Close Files And Pipes.
+                                                              (line 139)
+* ERRNO variable, with getline command:  Getline.             (line  19)
 * error handling:                        Special FD.          (line  16)
 * error handling, ERRNO variable and:    Auto-set.            (line  82)
 * error output:                          Special FD.          (line   6)
 * escape processing, gsub()/gensub()/sub() functions: Gory Details.
                                                               (line   6)
-* escape sequences:                      Escape Sequences.    (line   6)
+* escape sequences, in strings:          Escape Sequences.    (line   6)
 * eval debugger command:                 Viewing And Changing Data.
                                                               (line  23)
+* evaluate expressions, in debugger:     Viewing And Changing Data.
+                                                              (line  23)
 * evaluation order:                      Increment Ops.       (line  60)
 * evaluation order, concatenation:       Concatenation.       (line  41)
 * evaluation order, functions:           Calling Built-in.    (line  30)
 * examining fields:                      Fields.              (line   6)
-* exclamation point (!), ! operator <1>: Egrep Program.       (line 170)
+* exclamation point (!), ! operator <1>: Egrep Program.       (line 175)
 * exclamation point (!), ! operator <2>: Precedence.          (line  52)
 * exclamation point (!), ! operator:     Boolean Ops.         (line  67)
 * exclamation point (!), != operator <1>: Precedence.         (line  65)
@@ -30505,9 +32126,13 @@ Index
 * exclamation point (!), !~ operator:    Regexp Usage.        (line  19)
 * exit statement:                        Exit Statement.      (line   6)
 * exit status, of gawk:                  Exit Status.         (line   6)
-* exp() function:                        Numeric Functions.   (line  18)
+* exit status, of VMS:                   VMS Running.         (line  29)
+* exit the debugger:                     Miscellaneous Debugger Commands.
+                                                              (line  99)
+* exp:                                   Numeric Functions.   (line  18)
 * expand utility:                        Very Simple.         (line  69)
-* Expat XML parser library:              gawkextlib.          (line  33)
+* Expat XML parser library:              gawkextlib.          (line  35)
+* exponent:                              Numeric Functions.   (line  18)
 * expressions:                           Expressions.         (line   6)
 * expressions, as patterns:              Expression Patterns. (line   6)
 * expressions, assignment:               Assignment Ops.      (line   6)
@@ -30519,55 +32144,70 @@ Index
                                                               (line   9)
 * expressions, selecting:                Conditional Exp.     (line   6)
 * Extended Regular Expressions (EREs):   Bracket Expressions. (line  24)
+* extension API:                         Extension API Description.
+                                                              (line   6)
+* extension API informational variables: Extension API Informational Variables.
+                                                              (line   6)
+* extension API version:                 Extension Versioning.
+                                                              (line   6)
+* extension API, version number:         Auto-set.            (line 232)
+* extension example:                     Extension Example.   (line   6)
+* extension registration:                Registration Functions.
+                                                              (line   6)
+* extension search path:                 Finding Extensions.  (line   6)
+* extensions distributed with gawk:      Extension Samples.   (line   6)
+* extensions, allocating memory:         Memory Allocation Functions.
+                                                              (line   6)
 * extensions, Brian Kernighan's awk <1>: Common Extensions.   (line   6)
 * extensions, Brian Kernighan's awk:     BTL.                 (line   6)
 * extensions, common, ** operator:       Arithmetic Ops.      (line  30)
-* extensions, common, **= operator:      Assignment Ops.      (line 136)
+* extensions, common, **= operator:      Assignment Ops.      (line 137)
 * extensions, common, /dev/stderr special file: Special FD.   (line  46)
 * extensions, common, /dev/stdin special file: Special FD.    (line  46)
 * extensions, common, /dev/stdout special file: Special FD.   (line  46)
 * extensions, common, \x escape sequence: Escape Sequences.   (line  61)
-* extensions, common, BINMODE variable:  PC Using.            (line  34)
+* extensions, common, BINMODE variable:  PC Using.            (line  33)
 * extensions, common, delete to delete entire arrays: Delete. (line  39)
-* extensions, common, func keyword:      Definition Syntax.   (line  83)
+* extensions, common, fflush() function: I/O Functions.       (line  43)
+* extensions, common, func keyword:      Definition Syntax.   (line  89)
 * extensions, common, length() applied to an array: String Functions.
-                                                              (line 193)
-* extensions, common, RS as a regexp:    Records.             (line 120)
+                                                              (line 197)
+* extensions, common, RS as a regexp:    gawk split records.  (line   6)
 * extensions, common, single character fields: Single Character Fields.
                                                               (line   6)
 * extensions, in gawk, not in POSIX awk: POSIX/GNU.           (line   6)
 * extensions, mawk:                      Common Extensions.   (line   6)
+* extensions, where to find:             gawkextlib.          (line   6)
 * extract.awk program:                   Extract Program.     (line  79)
 * extraction, of marked strings (internationalization): String Extraction.
                                                               (line   6)
 * f debugger command (alias for frame):  Execution Stack.     (line  25)
 * false, logical:                        Truth Values.        (line   6)
 * FDL (Free Documentation License):      GNU Free Documentation License.
-                                                              (line   6)
+                                                              (line   7)
 * features, adding to gawk:              Adding Code.         (line   6)
-* features, advanced, See advanced features: Obsolete.        (line   6)
 * features, deprecated:                  Obsolete.            (line   6)
 * features, undocumented:                Undocumented.        (line   6)
 * Fenlason, Jay <1>:                     Contributors.        (line  18)
 * Fenlason, Jay:                         History.             (line  30)
-* fflush() function:                     I/O Functions.       (line  25)
+* fflush:                                I/O Functions.       (line  28)
 * field numbers:                         Nonconstant Fields.  (line   6)
 * field operator $:                      Fields.              (line  19)
 * field operators, dollar sign as:       Fields.              (line  19)
-* field separators <1>:                  User-modified.       (line  56)
-* field separators:                      Field Separators.    (line  14)
-* field separators, choice of:           Field Separators.    (line  50)
-* field separators, FIELDWIDTHS variable and: User-modified.  (line  35)
-* field separators, FPAT variable and:   User-modified.       (line  45)
-* field separators, in multiline records: Multiple Line.      (line  41)
-* field separators, on command line:     Command Line Field Separator.
+* field separator, in multiline records: Multiple Line.       (line  41)
+* field separator, on command line:      Command Line Field Separator.
                                                               (line   6)
-* field separators, POSIX and <1>:       Field Splitting Summary.
+* field separator, POSIX and:            Field Splitting Summary.
                                                               (line  40)
+* field separators <1>:                  User-modified.       (line  50)
+* field separators:                      Field Separators.    (line  15)
+* field separators, choice of:           Field Separators.    (line  51)
+* field separators, FIELDWIDTHS variable and: User-modified.  (line  37)
+* field separators, FPAT variable and:   User-modified.       (line  43)
 * field separators, POSIX and:           Fields.              (line   6)
 * field separators, regular expressions as <1>: Regexp Field Splitting.
                                                               (line   6)
-* field separators, regular expressions as: Field Separators. (line  50)
+* field separators, regular expressions as: Field Separators. (line  51)
 * field separators, See Also OFS:        Changing Fields.     (line  64)
 * field separators, spaces as:           Cut Program.         (line 109)
 * fields <1>:                            Basic High Level.    (line  73)
@@ -30580,35 +32220,34 @@ Index
 * fields, number of:                     Fields.              (line  33)
 * fields, numbers:                       Nonconstant Fields.  (line   6)
 * fields, printing:                      Print Examples.      (line  21)
-* fields, separating:                    Field Separators.    (line  14)
+* fields, separating:                    Field Separators.    (line  15)
 * fields, single-character:              Single Character Fields.
                                                               (line   6)
-* FIELDWIDTHS variable <1>:              User-modified.       (line  35)
-* FIELDWIDTHS variable:                  Constant Size.       (line  22)
+* FIELDWIDTHS variable <1>:              User-modified.       (line  37)
+* FIELDWIDTHS variable:                  Constant Size.       (line  23)
 * file descriptors:                      Special FD.          (line   6)
-* file names, distinguishing:            Auto-set.            (line  52)
+* file names, distinguishing:            Auto-set.            (line  56)
 * file names, in compatibility mode:     Special Caveats.     (line   9)
 * file names, standard streams in gawk:  Special FD.          (line  46)
-* FILENAME variable <1>:                 Auto-set.            (line 102)
+* FILENAME variable <1>:                 Auto-set.            (line  98)
 * FILENAME variable:                     Reading Files.       (line   6)
 * FILENAME variable, getline, setting with: Getline Notes.    (line  19)
 * filenames, assignments as:             Ignoring Assigns.    (line   6)
-* files, .gmo:                           Explaining gettext.  (line  41)
-* files, .gmo, converting from .po:      I18N Example.        (line  62)
+* files, .gmo:                           Explaining gettext.  (line  42)
 * files, .gmo, specifying directory of <1>: Programmer i18n.  (line  47)
-* files, .gmo, specifying directory of:  Explaining gettext.  (line  53)
+* files, .gmo, specifying directory of:  Explaining gettext.  (line  54)
+* files, .mo, converting from .po:       I18N Example.        (line  63)
 * files, .po <1>:                        Translator i18n.     (line   6)
-* files, .po:                            Explaining gettext.  (line  36)
-* files, .po, converting to .gmo:        I18N Example.        (line  62)
-* files, .pot:                           Explaining gettext.  (line  30)
+* files, .po:                            Explaining gettext.  (line  37)
+* files, .po, converting to .mo:         I18N Example.        (line  63)
+* files, .pot:                           Explaining gettext.  (line  31)
 * files, /dev/... special files:         Special FD.          (line  46)
 * files, /inet/... (gawk):               TCP/IP Networking.   (line   6)
 * files, /inet4/... (gawk):              TCP/IP Networking.   (line   6)
 * files, /inet6/... (gawk):              TCP/IP Networking.   (line   6)
-* files, as single records:              Records.             (line 200)
 * files, awk programs in:                Long.                (line   6)
 * files, awkprof.out:                    Profiling.           (line   6)
-* files, awkvars.out:                    Options.             (line 107)
+* files, awkvars.out:                    Options.             (line  93)
 * files, closing:                        I/O Functions.       (line  10)
 * files, descriptors, See file descriptors: Special FD.       (line   6)
 * files, group:                          Group Functions.     (line   6)
@@ -30618,96 +32257,102 @@ Index
 * files, managing:                       Data File Management.
                                                               (line   6)
 * files, managing, data file boundaries: Filetrans Function.  (line   6)
-* files, message object:                 Explaining gettext.  (line  41)
+* files, message object:                 Explaining gettext.  (line  42)
 * files, message object, converting from portable object files: I18N Example.
-                                                              (line  62)
+                                                              (line  63)
 * files, message object, specifying directory of <1>: Programmer i18n.
                                                               (line  47)
 * files, message object, specifying directory of: Explaining gettext.
-                                                              (line  53)
+                                                              (line  54)
 * files, multiple passes over:           Other Arguments.     (line  49)
 * files, multiple, duplicating output into: Tee Program.      (line   6)
 * files, output, See output files:       Close Files And Pipes.
                                                               (line   6)
 * files, password:                       Passwd Functions.    (line  16)
 * files, portable object <1>:            Translator i18n.     (line   6)
-* files, portable object:                Explaining gettext.  (line  36)
-* files, portable object template:       Explaining gettext.  (line  30)
+* files, portable object:                Explaining gettext.  (line  37)
+* files, portable object template:       Explaining gettext.  (line  31)
 * files, portable object, converting to message object files: I18N Example.
-                                                              (line  62)
-* files, portable object, generating:    Options.             (line 161)
-* files, processing, ARGIND variable and: Auto-set.           (line  47)
+                                                              (line  63)
+* files, portable object, generating:    Options.             (line 147)
+* files, processing, ARGIND variable and: Auto-set.           (line  51)
 * files, reading:                        Rewind Function.     (line   6)
 * files, reading, multiline records:     Multiple Line.       (line   6)
 * files, searching for regular expressions: Egrep Program.    (line   6)
 * files, skipping:                       File Checking.       (line   6)
-* files, source, search path for:        Igawk Program.       (line 368)
+* files, source, search path for:        Programs Exercises.  (line  63)
 * files, splitting:                      Split Program.       (line   6)
 * files, Texinfo, extracting programs from: Extract Program.  (line   6)
+* find substring in string:              String Functions.    (line 155)
+* finding extensions:                    Finding Extensions.  (line   6)
 * finish debugger command:               Debugger Execution Control.
                                                               (line  39)
 * Fish, Fred:                            Contributors.        (line  50)
-* fixed-width data:                      Constant Size.       (line   9)
+* fixed-width data:                      Constant Size.       (line  10)
 * flag variables <1>:                    Tee Program.         (line  20)
 * flag variables:                        Boolean Ops.         (line  67)
-* floating-point numbers, arbitrary precision: Arbitrary Precision Arithmetic.
-                                                              (line   6)
-* floating-point, numbers <1>:           Unexpected Results.  (line   6)
-* floating-point, numbers:               General Arithmetic.  (line   6)
-* fnmatch extension function:            Extension Sample Fnmatch.
+* floating-point, numbers, arbitrary precision: Arbitrary Precision Arithmetic.
                                                               (line   6)
-* FNR variable <1>:                      Auto-set.            (line 112)
+* floating-point, VAX/VMS:               VMS Running.         (line  51)
+* flush buffered output:                 I/O Functions.       (line  28)
+* fnmatch() extension function:          Extension Sample Fnmatch.
+                                                              (line  12)
+* FNR variable <1>:                      Auto-set.            (line 107)
 * FNR variable:                          Records.             (line   6)
-* FNR variable, changing:                Auto-set.            (line 323)
+* FNR variable, changing:                Auto-set.            (line 309)
 * for statement:                         For Statement.       (line   6)
 * for statement, looping over arrays:    Scanning an Array.   (line  20)
-* fork extension function:               Extension Sample Fork.
+* fork() extension function:             Extension Sample Fork.
                                                               (line  11)
+* format specifiers:                     Basic Printf.        (line  15)
 * format specifiers, mixing regular with positional specifiers: Printf Ordering.
                                                               (line  57)
 * format specifiers, printf statement:   Control Letters.     (line   6)
 * format specifiers, strftime() function (gawk): Time Functions.
-                                                              (line  88)
-* format strings:                        Basic Printf.        (line  15)
+                                                              (line  89)
+* format time string:                    Time Functions.      (line  48)
 * formats, numeric output:               OFMT.                (line   6)
 * formatting output:                     Printf.              (line   6)
-* forward slash (/):                     Regexp.              (line  10)
+* formatting strings:                    String Functions.    (line 381)
+* forward slash (/) to enclose regular expressions: Regexp.   (line  10)
 * forward slash (/), / operator:         Precedence.          (line  55)
 * forward slash (/), /= operator <1>:    Precedence.          (line  95)
-* forward slash (/), /= operator:        Assignment Ops.      (line 129)
+* forward slash (/), /= operator:        Assignment Ops.      (line 130)
 * forward slash (/), /= operator, vs. /=.../ regexp constant: Assignment Ops.
-                                                              (line 147)
+                                                              (line 148)
 * forward slash (/), patterns and:       Expression Patterns. (line  24)
-* FPAT variable <1>:                     User-modified.       (line  45)
+* FPAT variable <1>:                     User-modified.       (line  43)
 * FPAT variable:                         Splitting By Content.
-                                                              (line  26)
+                                                              (line  27)
 * frame debugger command:                Execution Stack.     (line  25)
 * Free Documentation License (FDL):      GNU Free Documentation License.
-                                                              (line   6)
-* Free Software Foundation (FSF) <1>:    Glossary.            (line 305)
+                                                              (line   7)
+* Free Software Foundation (FSF) <1>:    Glossary.            (line 296)
 * Free Software Foundation (FSF) <2>:    Getting.             (line  10)
 * Free Software Foundation (FSF):        Manual History.      (line   6)
-* FreeBSD:                               Glossary.            (line 624)
-* FS variable <1>:                       User-modified.       (line  56)
-* FS variable:                           Field Separators.    (line  14)
+* FreeBSD:                               Glossary.            (line 611)
+* FS variable <1>:                       User-modified.       (line  50)
+* FS variable:                           Field Separators.    (line  15)
 * FS variable, --field-separator option and: Options.         (line  21)
 * FS variable, as null string:           Single Character Fields.
                                                               (line  20)
-* FS variable, as TAB character:         Options.             (line 259)
-* FS variable, changing value of:        Field Separators.    (line  34)
+* FS variable, as TAB character:         Options.             (line 266)
+* FS variable, changing value of:        Field Separators.    (line  35)
 * FS variable, running awk programs and: Cut Program.         (line  68)
 * FS variable, setting from command line: Command Line Field Separator.
                                                               (line   6)
 * FS, containing ^:                      Regexp Field Splitting.
                                                               (line  59)
-* FSF (Free Software Foundation) <1>:    Glossary.            (line 305)
+* FS, in multiline records:              Multiple Line.       (line  41)
+* FSF (Free Software Foundation) <1>:    Glossary.            (line 296)
 * FSF (Free Software Foundation) <2>:    Getting.             (line  10)
 * FSF (Free Software Foundation):        Manual History.      (line   6)
-* fts extension function:                Extension Sample File Functions.
-                                                              (line  77)
-* FUNCTAB array:                         Auto-set.            (line 128)
+* fts() extension function:              Extension Sample File Functions.
+                                                              (line  61)
+* FUNCTAB array:                         Auto-set.            (line 123)
 * function calls:                        Function Calls.      (line   6)
 * function calls, indirect:              Indirect Calls.      (line   6)
+* function definition example:           Function Example.    (line   6)
 * function pointers:                     Indirect Calls.      (line   6)
 * functions, arrays as parameters to:    Pass By Value/Reference.
                                                               (line  47)
@@ -30739,21 +32384,22 @@ Index
                                                               (line   6)
 * functions, names of <1>:               Definition Syntax.   (line  20)
 * functions, names of:                   Arrays.              (line  18)
-* functions, recursive:                  Definition Syntax.   (line  73)
+* functions, recursive:                  Definition Syntax.   (line  79)
 * functions, string-translation:         I18N Functions.      (line   6)
 * functions, undefined:                  Pass By Value/Reference.
                                                               (line  71)
 * functions, user-defined:               User-defined.        (line   6)
-* functions, user-defined, calling:      Calling A Function.  (line   6)
-* functions, user-defined, counts:       Profiling.           (line 129)
+* functions, user-defined, calling:      Function Caveats.    (line   6)
+* functions, user-defined, counts, in a profile: Profiling.   (line 137)
 * functions, user-defined, library of:   Library Functions.   (line   6)
 * functions, user-defined, next/nextfile statements and <1>: Nextfile Statement.
                                                               (line  47)
 * functions, user-defined, next/nextfile statements and: Next Statement.
                                                               (line  45)
-* G-d:                                   Acknowledgments.     (line  78)
+* G-d:                                   Acknowledgments.     (line  82)
 * Garfinkle, Scott:                      Contributors.        (line  34)
-* gawk program, dynamic profiling:       Profiling.           (line 172)
+* gawk program, dynamic profiling:       Profiling.           (line 179)
+* gawk version:                          Auto-set.            (line 207)
 * gawk, ARGIND variable in:              Other Arguments.     (line  12)
 * gawk, awk and <1>:                     This Manual.         (line  14)
 * gawk, awk and:                         Preface.             (line  23)
@@ -30761,8 +32407,8 @@ Index
 * gawk, break statement in:              Break Statement.     (line  51)
 * gawk, built-in variables and:          Built-in Variables.  (line  14)
 * gawk, character classes and:           Bracket Expressions. (line  90)
-* gawk, coding style in:                 Adding Code.         (line  38)
-* gawk, command-line options:            GNU Regexp Operators.
+* gawk, coding style in:                 Adding Code.         (line  39)
+* gawk, command-line options, and regular expressions: GNU Regexp Operators.
                                                               (line  70)
 * gawk, comparison operators and:        Comparison Operators.
                                                               (line  50)
@@ -30777,28 +32423,28 @@ Index
 * gawk, ERRNO variable in <2>:           Auto-set.            (line  82)
 * gawk, ERRNO variable in <3>:           BEGINFILE/ENDFILE.   (line  26)
 * gawk, ERRNO variable in <4>:           Close Files And Pipes.
-                                                              (line 138)
+                                                              (line 139)
 * gawk, ERRNO variable in:               Getline.             (line  19)
 * gawk, escape sequences:                Escape Sequences.    (line 124)
-* gawk, extensions, disabling:           Options.             (line 247)
+* gawk, extensions, disabling:           Options.             (line 254)
 * gawk, features, adding:                Adding Code.         (line   6)
 * gawk, features, advanced:              Advanced Features.   (line   6)
-* gawk, field separators and:            User-modified.       (line  77)
-* gawk, FIELDWIDTHS variable in <1>:     User-modified.       (line  35)
-* gawk, FIELDWIDTHS variable in:         Constant Size.       (line  22)
+* gawk, field separators and:            User-modified.       (line  71)
+* gawk, FIELDWIDTHS variable in <1>:     User-modified.       (line  37)
+* gawk, FIELDWIDTHS variable in:         Constant Size.       (line  23)
 * gawk, file names in:                   Special Files.       (line   6)
 * gawk, format-control characters:       Control Letters.     (line  18)
-* gawk, FPAT variable in <1>:            User-modified.       (line  45)
+* gawk, FPAT variable in <1>:            User-modified.       (line  43)
 * gawk, FPAT variable in:                Splitting By Content.
-                                                              (line  26)
-* gawk, FUNCTAB array in:                Auto-set.            (line 128)
+                                                              (line  27)
+* gawk, FUNCTAB array in:                Auto-set.            (line 123)
 * gawk, function arguments and:          Calling Built-in.    (line  16)
 * gawk, hexadecimal numbers and:         Nondecimal-numbers.  (line  42)
 * gawk, IGNORECASE variable in <1>:      Array Sorting Functions.
                                                               (line  83)
-* gawk, IGNORECASE variable in <2>:      String Functions.    (line  32)
-* gawk, IGNORECASE variable in <3>:      Array Intro.         (line  91)
-* gawk, IGNORECASE variable in <4>:      User-modified.       (line  82)
+* gawk, IGNORECASE variable in <2>:      String Functions.    (line  58)
+* gawk, IGNORECASE variable in <3>:      Array Intro.         (line  92)
+* gawk, IGNORECASE variable in <4>:      User-modified.       (line  76)
 * gawk, IGNORECASE variable in:          Case-sensitivity.    (line  26)
 * gawk, implementation issues:           Notes.               (line   6)
 * gawk, implementation issues, debugging: Compatibility Mode. (line   6)
@@ -30811,61 +32457,61 @@ Index
                                                               (line  13)
 * gawk, interpreter, adding code to:     Using Internal File Ops.
                                                               (line   6)
-* gawk, interval expressions and:        Regexp Operators.    (line 139)
+* gawk, interval expressions and:        Regexp Operators.    (line 140)
 * gawk, line continuation in:            Conditional Exp.     (line  34)
-* gawk, LINT variable in:                User-modified.       (line  98)
+* gawk, LINT variable in:                User-modified.       (line  88)
 * gawk, list of contributors to:         Contributors.        (line   6)
-* gawk, MS-DOS version of:               PC Using.            (line  11)
-* gawk, MS-Windows version of:           PC Using.            (line  11)
+* gawk, MS-DOS version of:               PC Using.            (line  10)
+* gawk, MS-Windows version of:           PC Using.            (line  10)
 * gawk, newlines in:                     Statements/Lines.    (line  12)
 * gawk, octal numbers and:               Nondecimal-numbers.  (line  42)
-* gawk, OS/2 version of:                 PC Using.            (line  11)
-* gawk, PROCINFO array in <1>:           Two-way I/O.         (line 116)
+* gawk, OS/2 version of:                 PC Using.            (line  16)
+* gawk, PROCINFO array in <1>:           Two-way I/O.         (line 117)
 * gawk, PROCINFO array in <2>:           Time Functions.      (line  47)
-* gawk, PROCINFO array in:               Auto-set.            (line 142)
+* gawk, PROCINFO array in:               Auto-set.            (line 136)
 * gawk, regexp constants and:            Using Constant Regexps.
                                                               (line  28)
 * gawk, regular expressions, case sensitivity: Case-sensitivity.
                                                               (line  26)
 * gawk, regular expressions, operators:  GNU Regexp Operators.
                                                               (line   6)
-* gawk, regular expressions, precedence: Regexp Operators.    (line 161)
-* gawk, RT variable in <1>:              Auto-set.            (line 275)
-* gawk, RT variable in <2>:              Getline/Variable/File.
-                                                              (line  10)
-* gawk, RT variable in <3>:              Multiple Line.       (line 129)
-* gawk, RT variable in:                  Records.             (line 117)
+* gawk, regular expressions, precedence: Regexp Operators.    (line 162)
+* gawk, RT variable in <1>:              Auto-set.            (line 265)
+* gawk, RT variable in <2>:              Multiple Line.       (line 129)
+* gawk, RT variable in:                  awk split records.   (line 124)
 * gawk, See Also awk:                    Preface.             (line  36)
 * gawk, source code, obtaining:          Getting.             (line   6)
-* gawk, splitting fields and:            Constant Size.       (line  87)
+* gawk, splitting fields and:            Constant Size.       (line  88)
 * gawk, string-translation functions:    I18N Functions.      (line   6)
-* gawk, SYMTAB array in:                 Auto-set.            (line 283)
-* gawk, TEXTDOMAIN variable in:          User-modified.       (line 162)
+* gawk, SYMTAB array in:                 Auto-set.            (line 269)
+* gawk, TEXTDOMAIN variable in:          User-modified.       (line 152)
 * gawk, timestamps:                      Time Functions.      (line   6)
 * gawk, uses for:                        Preface.             (line  36)
-* gawk, versions of, information about, printing: Options.    (line 293)
+* gawk, versions of, information about, printing: Options.    (line 300)
 * gawk, VMS version of:                  VMS Installation.    (line   6)
 * gawk, word-boundary operator:          GNU Regexp Operators.
                                                               (line  63)
+* gawkextlib:                            gawkextlib.          (line   6)
 * gawkextlib project:                    gawkextlib.          (line   6)
-* General Public License (GPL):          Glossary.            (line 314)
+* General Public License (GPL):          Glossary.            (line 305)
 * General Public License, See GPL:       Manual History.      (line  11)
-* gensub() function (gawk) <1>:          String Functions.    (line  81)
-* gensub() function (gawk):              Using Constant Regexps.
+* generate time values:                  Time Functions.      (line  25)
+* gensub <1>:                            String Functions.    (line  89)
+* gensub:                                Using Constant Regexps.
                                                               (line  43)
 * gensub() function (gawk), escape processing: Gory Details.  (line   6)
 * getaddrinfo() function (C library):    TCP/IP Networking.   (line  38)
 * getgrent() function (C library):       Group Functions.     (line   6)
 * getgrent() user-defined function:      Group Functions.     (line   6)
-* getgrgid() function (C library):       Group Functions.     (line 186)
-* getgrgid() user-defined function:      Group Functions.     (line 189)
-* getgrnam() function (C library):       Group Functions.     (line 175)
-* getgrnam() user-defined function:      Group Functions.     (line 180)
-* getgruser() function (C library):      Group Functions.     (line 195)
-* getgruser() function, user-defined:    Group Functions.     (line 198)
+* getgrgid() function (C library):       Group Functions.     (line 184)
+* getgrgid() user-defined function:      Group Functions.     (line 187)
+* getgrnam() function (C library):       Group Functions.     (line 173)
+* getgrnam() user-defined function:      Group Functions.     (line 178)
+* getgruser() function (C library):      Group Functions.     (line 193)
+* getgruser() function, user-defined:    Group Functions.     (line 196)
 * getline command:                       Reading Files.       (line  20)
 * getline command, _gr_init() user-defined function: Group Functions.
-                                                              (line  82)
+                                                              (line  83)
 * getline command, _pw_init() function:  Passwd Functions.    (line 154)
 * getline command, coprocesses, using from <1>: Close Files And Pipes.
                                                               (line   6)
@@ -30876,6 +32522,8 @@ Index
 * getline command, FILENAME variable and: Getline Notes.      (line  19)
 * getline command, return values:        Getline.             (line  19)
 * getline command, variants:             Getline Summary.     (line   6)
+* getline from a file:                   Getline/File.        (line   6)
+* getline into a variable:               Getline/Variable.    (line   6)
 * getline statement, BEGINFILE/ENDFILE patterns and: BEGINFILE/ENDFILE.
                                                               (line  54)
 * getlocaltime() user-defined function:  Getlocaltime Function.
@@ -30889,99 +32537,104 @@ Index
 * getpwuid() function (C library):       Passwd Functions.    (line 188)
 * getpwuid() user-defined function:      Passwd Functions.    (line 192)
 * gettext library:                       Explaining gettext.  (line   6)
-* gettext library, locale categories:    Explaining gettext.  (line  80)
-* gettext() function (C library):        Explaining gettext.  (line  62)
-* gettimeofday extension function:       Extension Sample Time.
-                                                              (line  13)
-* GMP:                                   Arbitrary Precision Arithmetic.
-                                                              (line   6)
+* gettext library, locale categories:    Explaining gettext.  (line  81)
+* gettext() function (C library):        Explaining gettext.  (line  63)
+* gettimeofday() extension function:     Extension Sample Time.
+                                                              (line  12)
+* git utility <1>:                       Adding Code.         (line 112)
+* git utility <2>:                       Accessing The Source.
+                                                              (line  10)
+* git utility <3>:                       Other Versions.      (line  29)
+* git utility:                           gawkextlib.          (line  29)
+* Git, use of for gawk source code:      Derived Files.       (line   6)
 * GNITS mailing list:                    Acknowledgments.     (line  52)
-* GNU awk, See gawk:                     Preface.             (line  49)
+* GNU awk, See gawk:                     Preface.             (line  53)
 * GNU Free Documentation License:        GNU Free Documentation License.
-                                                              (line   6)
-* GNU General Public License:            Glossary.            (line 314)
-* GNU Lesser General Public License:     Glossary.            (line 405)
+                                                              (line   7)
+* GNU General Public License:            Glossary.            (line 305)
+* GNU Lesser General Public License:     Glossary.            (line 396)
 * GNU long options <1>:                  Options.             (line   6)
 * GNU long options:                      Command Line.        (line  13)
-* GNU long options, printing list of:    Options.             (line 168)
-* GNU Project <1>:                       Glossary.            (line 323)
+* GNU long options, printing list of:    Options.             (line 154)
+* GNU Project <1>:                       Glossary.            (line 314)
 * GNU Project:                           Manual History.      (line  11)
-* GNU/Linux <1>:                         Glossary.            (line 624)
+* GNU/Linux <1>:                         Glossary.            (line 611)
 * GNU/Linux <2>:                         I18N Example.        (line  55)
 * GNU/Linux:                             Manual History.      (line  28)
-* GPL (General Public License) <1>:      Glossary.            (line 314)
+* Gordon, Assaf:                         Contributors.        (line 105)
+* GPL (General Public License) <1>:      Glossary.            (line 305)
 * GPL (General Public License):          Manual History.      (line  11)
-* GPL (General Public License), printing: Options.            (line 102)
+* GPL (General Public License), printing: Options.            (line  88)
 * grcat program:                         Group Functions.     (line  16)
 * Grigera, Juan:                         Contributors.        (line  57)
 * group database, reading:               Group Functions.     (line   6)
 * group file:                            Group Functions.     (line   6)
+* group ID of gawk user:                 Auto-set.            (line 180)
 * groups, information about:             Group Functions.     (line   6)
-* gsub() function <1>:                   String Functions.    (line 134)
-* gsub() function:                       Using Constant Regexps.
+* gsub <1>:                              String Functions.    (line 139)
+* gsub:                                  Using Constant Regexps.
                                                               (line  43)
-* gsub() function, arguments of:         String Functions.    (line 459)
+* gsub() function, arguments of:         String Functions.    (line 460)
 * gsub() function, escape processing:    Gory Details.        (line   6)
 * h debugger command (alias for help):   Miscellaneous Debugger Commands.
                                                               (line  66)
 * Hankerson, Darrel <1>:                 Contributors.        (line  60)
 * Hankerson, Darrel:                     Acknowledgments.     (line  60)
-* Haque, John:                           Contributors.        (line 103)
+* Haque, John:                           Contributors.        (line 108)
 * Hartholz, Elaine:                      Acknowledgments.     (line  38)
 * Hartholz, Marshall:                    Acknowledgments.     (line  38)
 * Hasegawa, Isamu:                       Contributors.        (line  94)
 * help debugger command:                 Miscellaneous Debugger Commands.
                                                               (line  66)
 * hexadecimal numbers:                   Nondecimal-numbers.  (line   6)
-* hexadecimal values, enabling interpretation of: Options.    (line 207)
+* hexadecimal values, enabling interpretation of: Options.    (line 211)
+* history expansion, in debugger:        Readline Support.    (line   6)
 * histsort.awk program:                  History Sorting.     (line  25)
 * Hughes, Phil:                          Acknowledgments.     (line  43)
-* HUP signal:                            Profiling.           (line 204)
+* HUP signal, for dynamic profiling:     Profiling.           (line 211)
 * hyphen (-), - operator:                Precedence.          (line  52)
 * hyphen (-), -- operator <1>:           Precedence.          (line  46)
 * hyphen (-), -- operator:               Increment Ops.       (line  48)
 * hyphen (-), -= operator <1>:           Precedence.          (line  95)
-* hyphen (-), -= operator:               Assignment Ops.      (line 129)
-* hyphen (-), filenames beginning with:  Options.             (line  73)
+* hyphen (-), -= operator:               Assignment Ops.      (line 130)
+* hyphen (-), filenames beginning with:  Options.             (line  59)
 * hyphen (-), in bracket expressions:    Bracket Expressions. (line  17)
 * i debugger command (alias for info):   Debugger Info.       (line  13)
 * id utility:                            Id Program.          (line   6)
 * id.awk program:                        Id Program.          (line  30)
-* IEEE-754 format:                       Floating-point Representation.
-                                                              (line   6)
-* if statement <1>:                      If Statement.        (line   6)
-* if statement:                          Regexp Usage.        (line  19)
+* if statement:                          If Statement.        (line   6)
 * if statement, actions, changing:       Ranges.              (line  25)
+* if statement, use of regexps in:       Regexp Usage.        (line  19)
 * igawk.sh program:                      Igawk Program.       (line 124)
+* ignore breakpoint:                     Breakpoint Control.  (line  87)
 * ignore debugger command:               Breakpoint Control.  (line  87)
-* IGNORECASE variable <1>:               Array Sorting Functions.
+* IGNORECASE variable:                   User-modified.       (line  76)
+* IGNORECASE variable, and array indices: Array Intro.        (line  92)
+* IGNORECASE variable, and array sorting functions: Array Sorting Functions.
                                                               (line  83)
-* IGNORECASE variable <2>:               String Functions.    (line  32)
-* IGNORECASE variable <3>:               Array Intro.         (line  91)
-* IGNORECASE variable <4>:               User-modified.       (line  82)
-* IGNORECASE variable:                   Case-sensitivity.    (line  26)
-* IGNORECASE variable, array sorting and: Array Sorting Functions.
-                                                              (line  83)
-* IGNORECASE variable, array subscripts and: Array Intro.     (line  91)
 * IGNORECASE variable, in example programs: Library Functions.
                                                               (line  53)
-* Illumos:                               Other Versions.      (line 104)
-* Illumos, POSIX-compliant awk:          Other Versions.      (line 104)
+* IGNORECASE variable, with ~ and !~ operators: Case-sensitivity.
+                                                              (line  26)
+* Illumos:                               Other Versions.      (line 105)
+* Illumos, POSIX-compliant awk:          Other Versions.      (line 105)
 * implementation issues, gawk:           Notes.               (line   6)
 * implementation issues, gawk, debugging: Compatibility Mode. (line   6)
 * implementation issues, gawk, limits <1>: Redirection.       (line 135)
 * implementation issues, gawk, limits:   Getline Notes.       (line  14)
-* in operator <1>:                       Id Program.          (line  93)
-* in operator <2>:                       Scanning an Array.   (line  17)
-* in operator <3>:                       Reference to Elements.
-                                                              (line  37)
-* in operator <4>:                       For Statement.       (line  75)
-* in operator <5>:                       Precedence.          (line  83)
+* in operator <1>:                       For Statement.       (line  75)
+* in operator <2>:                       Precedence.          (line  83)
 * in operator:                           Comparison Operators.
                                                               (line  11)
+* in operator, index existence in multidimensional arrays: Multidimensional.
+                                                              (line  43)
+* in operator, order of array access:    Scanning an Array.   (line  48)
+* in operator, testing if array element exists: Reference to Elements.
+                                                              (line  37)
+* in operator, use in loops:             Scanning an Array.   (line  17)
 * increment operators:                   Increment Ops.       (line   6)
-* index() function:                      String Functions.    (line 150)
-* indexing arrays:                       Array Intro.         (line  49)
+* index:                                 String Functions.    (line 155)
+* indexing arrays:                       Array Intro.         (line  50)
 * indirect function calls:               Indirect Calls.      (line   6)
 * infinite precision:                    Arbitrary Precision Arithmetic.
                                                               (line   6)
@@ -30998,6 +32651,7 @@ Index
 * input files, running awk without:      Read Terminal.       (line   6)
 * input files, variable assignments and: Other Arguments.     (line  19)
 * input pipeline:                        Getline/Pipe.        (line   9)
+* input record, length of:               String Functions.    (line 174)
 * input redirection:                     Getline/File.        (line   6)
 * input, data, nondecimal:               Nondecimal Data.     (line   6)
 * input, explicit:                       Getline.             (line   6)
@@ -31006,83 +32660,89 @@ Index
 * input, splitting into records:         Records.             (line   6)
 * input, standard <1>:                   Special FD.          (line   6)
 * input, standard:                       Read Terminal.       (line   6)
-* input/output, binary:                  User-modified.       (line  10)
+* input/output functions:                I/O Functions.       (line   6)
+* input/output, binary:                  User-modified.       (line  15)
 * input/output, from BEGIN and END:      I/O And BEGIN/END.   (line   6)
 * input/output, two-way:                 Two-way I/O.         (line  44)
 * insomnia, cure for:                    Alarm Program.       (line   6)
 * installation, VMS:                     VMS Installation.    (line   6)
 * installing gawk:                       Installation.        (line   6)
-* INT signal (MS-Windows):               Profiling.           (line 207)
-* int() function:                        Numeric Functions.   (line  23)
-* integer, arbitrary precision:          Arbitrary Precision Integers.
+* instruction tracing, in debugger:      Debugger Info.       (line  89)
+* int:                                   Numeric Functions.   (line  23)
+* INT signal (MS-Windows):               Profiling.           (line 214)
+* integer array indices:                 Numeric Array Subscripts.
+                                                              (line  31)
+* integers, arbitrary precision:         Arbitrary Precision Integers.
                                                               (line   6)
-* integers:                              General Arithmetic.  (line   6)
-* integers, unsigned:                    General Arithmetic.  (line  15)
-* interacting with other programs:       I/O Functions.       (line  72)
+* integers, unsigned:                    Computer Arithmetic. (line  41)
+* interacting with other programs:       I/O Functions.       (line  75)
 * internationalization <1>:              I18N and L10N.       (line   6)
 * internationalization:                  I18N Functions.      (line   6)
 * internationalization, localization <1>: Internationalization.
                                                               (line  13)
-* internationalization, localization:    User-modified.       (line 162)
+* internationalization, localization:    User-modified.       (line 152)
 * internationalization, localization, character classes: Bracket Expressions.
                                                               (line  90)
 * internationalization, localization, gawk and: Internationalization.
                                                               (line  13)
 * internationalization, localization, locale categories: Explaining gettext.
-                                                              (line  80)
+                                                              (line  81)
 * internationalization, localization, marked strings: Programmer i18n.
                                                               (line  14)
 * internationalization, localization, portability and: I18N Portability.
                                                               (line   6)
 * internationalizing a program:          Explaining gettext.  (line   6)
-* interpreted programs <1>:              Glossary.            (line 365)
+* interpreted programs <1>:              Glossary.            (line 356)
 * interpreted programs:                  Basic High Level.    (line  15)
-* interval expressions:                  Regexp Operators.    (line 116)
+* interval expressions, regexp operator: Regexp Operators.    (line 117)
 * inventory-shipped file:                Sample Data Files.   (line  32)
-* isarray() function (gawk):             Type Functions.      (line  11)
-* ISO:                                   Glossary.            (line 376)
-* ISO 8859-1:                            Glossary.            (line 141)
-* ISO Latin-1:                           Glossary.            (line 141)
+* invoke shell command:                  I/O Functions.       (line  75)
+* isarray:                               Type Functions.      (line  11)
+* ISO:                                   Glossary.            (line 367)
+* ISO 8859-1:                            Glossary.            (line 133)
+* ISO Latin-1:                           Glossary.            (line 133)
 * Jacobs, Andrew:                        Passwd Functions.    (line  90)
 * Jaegermann, Michal <1>:                Contributors.        (line  45)
 * Jaegermann, Michal:                    Acknowledgments.     (line  60)
-* Java implementation of awk:            Other Versions.      (line 112)
-* Java programming language:             Glossary.            (line 388)
-* jawk:                                  Other Versions.      (line 112)
+* Java implementation of awk:            Other Versions.      (line 113)
+* Java programming language:             Glossary.            (line 379)
+* jawk:                                  Other Versions.      (line 113)
 * Jedi knights:                          Undocumented.        (line   6)
+* Johansen, Chris:                       Signature Program.   (line  25)
 * join() user-defined function:          Join Function.       (line  18)
 * Kahrs, Ju"rgen <1>:                    Contributors.        (line  70)
 * Kahrs, Ju"rgen:                        Acknowledgments.     (line  60)
 * Kasal, Stepan:                         Acknowledgments.     (line  60)
 * Kenobi, Obi-Wan:                       Undocumented.        (line   6)
-* Kernighan, Brian <1>:                  Basic Data Typing.   (line  55)
-* Kernighan, Brian <2>:                  Other Versions.      (line  13)
-* Kernighan, Brian <3>:                  Contributors.        (line  11)
-* Kernighan, Brian <4>:                  BTL.                 (line   6)
-* Kernighan, Brian <5>:                  Concatenation.       (line   6)
-* Kernighan, Brian <6>:                  Acknowledgments.     (line  72)
-* Kernighan, Brian <7>:                  Conventions.         (line  34)
+* Kernighan, Brian <1>:                  Glossary.            (line 143)
+* Kernighan, Brian <2>:                  Basic Data Typing.   (line  54)
+* Kernighan, Brian <3>:                  Other Versions.      (line  13)
+* Kernighan, Brian <4>:                  Contributors.        (line  11)
+* Kernighan, Brian <5>:                  BTL.                 (line   6)
+* Kernighan, Brian <6>:                  Library Functions.   (line  12)
+* Kernighan, Brian <7>:                  Concatenation.       (line   6)
+* Kernighan, Brian <8>:                  Getline/Pipe.        (line   6)
+* Kernighan, Brian <9>:                  Acknowledgments.     (line  76)
+* Kernighan, Brian <10>:                 Conventions.         (line  34)
 * Kernighan, Brian:                      History.             (line  17)
-* kill command, dynamic profiling:       Profiling.           (line 181)
+* kill command, dynamic profiling:       Profiling.           (line 188)
 * Knights, jedi:                         Undocumented.        (line   6)
-* Knuth, Donald:                         Arbitrary Precision Arithmetic.
-                                                              (line   6)
 * Kwok, Conrad:                          Contributors.        (line  34)
 * l debugger command (alias for list):   Miscellaneous Debugger Commands.
                                                               (line  72)
 * labels.awk program:                    Labels Program.      (line  51)
+* Langston, Peter:                       Advanced Features.   (line   6)
 * languages, data-driven:                Basic High Level.    (line  85)
-* Laurie, Dirk:                          Changing Precision.  (line   6)
-* LC_ALL locale category:                Explaining gettext.  (line 120)
-* LC_COLLATE locale category:            Explaining gettext.  (line  93)
-* LC_CTYPE locale category:              Explaining gettext.  (line  97)
-* LC_MESSAGES locale category:           Explaining gettext.  (line  87)
+* LC_ALL locale category:                Explaining gettext.  (line 121)
+* LC_COLLATE locale category:            Explaining gettext.  (line  94)
+* LC_CTYPE locale category:              Explaining gettext.  (line  98)
+* LC_MESSAGES locale category:           Explaining gettext.  (line  88)
 * LC_MESSAGES locale category, bindtextdomain() function (gawk): Programmer i18n.
                                                               (line  88)
-* LC_MONETARY locale category:           Explaining gettext.  (line 103)
-* LC_NUMERIC locale category:            Explaining gettext.  (line 107)
-* LC_RESPONSE locale category:           Explaining gettext.  (line 111)
-* LC_TIME locale category:               Explaining gettext.  (line 115)
+* LC_MONETARY locale category:           Explaining gettext.  (line 104)
+* LC_NUMERIC locale category:            Explaining gettext.  (line 108)
+* LC_RESPONSE locale category:           Explaining gettext.  (line 112)
+* LC_TIME locale category:               Explaining gettext.  (line 116)
 * left angle bracket (<), < operator <1>: Precedence.         (line  65)
 * left angle bracket (<), < operator:    Comparison Operators.
                                                               (line  11)
@@ -31090,12 +32750,15 @@ Index
 * left angle bracket (<), <= operator <1>: Precedence.        (line  65)
 * left angle bracket (<), <= operator:   Comparison Operators.
                                                               (line  11)
+* left shift:                            Bitwise Functions.   (line  46)
 * left shift, bitwise:                   Bitwise Functions.   (line  32)
 * leftmost longest match:                Multiple Line.       (line  26)
-* length() function:                     String Functions.    (line 163)
-* Lesser General Public License (LGPL):  Glossary.            (line 405)
-* LGPL (Lesser General Public License):  Glossary.            (line 405)
-* libmawk:                               Other Versions.      (line 120)
+* length:                                String Functions.    (line 167)
+* length of input record:                String Functions.    (line 174)
+* length of string:                      String Functions.    (line 167)
+* Lesser General Public License (LGPL):  Glossary.            (line 396)
+* LGPL (Lesser General Public License):  Glossary.            (line 396)
+* libmawk:                               Other Versions.      (line 121)
 * libraries of awk functions:            Library Functions.   (line   6)
 * libraries of awk functions, assertions: Assert Function.    (line   6)
 * libraries of awk functions, associative arrays and: Library Names.
@@ -31128,77 +32791,97 @@ Index
 * lines, duplicate, removing:            History Sorting.     (line   6)
 * lines, matching ranges of:             Ranges.              (line   6)
 * lines, skipping between markers:       Ranges.              (line  43)
-* lint checking:                         User-modified.       (line  98)
+* lint checking:                         User-modified.       (line  88)
 * lint checking, array elements:         Delete.              (line  34)
 * lint checking, array subscripts:       Uninitialized Subscripts.
                                                               (line  43)
 * lint checking, empty programs:         Command Line.        (line  16)
-* lint checking, issuing warnings:       Options.             (line 182)
+* lint checking, issuing warnings:       Options.             (line 185)
 * lint checking, POSIXLY_CORRECT environment variable: Options.
-                                                              (line 332)
+                                                              (line 340)
 * lint checking, undefined functions:    Pass By Value/Reference.
                                                               (line  88)
-* LINT variable:                         User-modified.       (line  98)
-* Linux <1>:                             Glossary.            (line 624)
+* LINT variable:                         User-modified.       (line  88)
+* Linux <1>:                             Glossary.            (line 611)
 * Linux <2>:                             I18N Example.        (line  55)
 * Linux:                                 Manual History.      (line  28)
+* list all global variables, in debugger: Debugger Info.      (line  48)
 * list debugger command:                 Miscellaneous Debugger Commands.
                                                               (line  72)
-* loading, library:                      Options.             (line 173)
-* local variables:                       Variable Scope.      (line   6)
-* locale categories:                     Explaining gettext.  (line  80)
-* locale decimal point character:        Options.             (line 263)
+* list function definitions, in debugger: Debugger Info.      (line  30)
+* loading, extensions:                   Options.             (line 173)
+* local variables, in a function:        Variable Scope.      (line   6)
+* locale categories:                     Explaining gettext.  (line  81)
+* locale decimal point character:        Options.             (line 270)
 * locale, definition of:                 Locales.             (line   6)
 * localization:                          I18N and L10N.       (line   6)
 * localization, See internationalization, localization: I18N and L10N.
                                                               (line   6)
+* log:                                   Numeric Functions.   (line  30)
 * log files, timestamps in:              Time Functions.      (line   6)
-* log() function:                        Numeric Functions.   (line  30)
+* logarithm:                             Numeric Functions.   (line  30)
 * logical false/true:                    Truth Values.        (line   6)
 * logical operators, See Boolean expressions: Boolean Ops.    (line   6)
 * login information:                     Passwd Functions.    (line  16)
 * long options:                          Command Line.        (line  13)
 * loops:                                 While Statement.     (line   6)
+* loops, break statement and:            Break Statement.     (line   6)
 * loops, continue statements and:        For Statement.       (line  64)
-* loops, count for header:               Profiling.           (line 123)
+* loops, count for header, in a profile: Profiling.           (line 131)
+* loops, do-while:                       Do Statement.        (line   6)
 * loops, exiting:                        Break Statement.     (line   6)
+* loops, for, array scanning:            Scanning an Array.   (line   6)
+* loops, for, iterative:                 For Statement.       (line   6)
 * loops, See Also while statement:       While Statement.     (line   6)
+* loops, while:                          While Statement.     (line   6)
 * ls utility:                            More Complex.        (line  15)
-* lshift() function (gawk):              Bitwise Functions.   (line  46)
+* lshift:                                Bitwise Functions.   (line  46)
 * lvalues/rvalues:                       Assignment Ops.      (line  32)
+* mail-list file:                        Sample Data Files.   (line   6)
 * mailing labels, printing:              Labels Program.      (line   6)
 * mailing list, GNITS:                   Acknowledgments.     (line  52)
+* Malmberg, John <1>:                    Bugs.                (line  71)
 * Malmberg, John:                        Acknowledgments.     (line  60)
 * mark parity:                           Ordinal Functions.   (line  45)
 * marked string extraction (internationalization): String Extraction.
                                                               (line   6)
 * marked strings, extracting:            String Extraction.   (line   6)
 * Marx, Groucho:                         Increment Ops.       (line  60)
-* match() function:                      String Functions.    (line 203)
+* match:                                 String Functions.    (line 207)
+* match regexp in string:                String Functions.    (line 207)
 * match() function, RSTART/RLENGTH variables: String Functions.
-                                                              (line 220)
+                                                              (line 224)
 * matching, expressions, See comparison expressions: Typing and Comparison.
                                                               (line   9)
 * matching, leftmost longest:            Multiple Line.       (line  26)
 * matching, null strings:                Gory Details.        (line 164)
-* mawk program:                          Other Versions.      (line  44)
+* mawk utility <1>:                      Other Versions.      (line  44)
+* mawk utility <2>:                      Nextfile Statement.  (line  47)
+* mawk utility <3>:                      Concatenation.       (line  36)
+* mawk utility <4>:                      Getline/Pipe.        (line  62)
+* mawk utility:                          Escape Sequences.    (line 124)
+* maximum precision supported by MPFR library: Auto-set.      (line 221)
+* McIlroy, Doug:                         Glossary.            (line 149)
 * McPhee, Patrick:                       Contributors.        (line 100)
-* message object files:                  Explaining gettext.  (line  41)
+* message object files:                  Explaining gettext.  (line  42)
 * message object files, converting from portable object files: I18N Example.
-                                                              (line  62)
+                                                              (line  63)
 * message object files, specifying directory of <1>: Programmer i18n.
                                                               (line  47)
 * message object files, specifying directory of: Explaining gettext.
-                                                              (line  53)
+                                                              (line  54)
+* messages from extensions:              Printing Messages.   (line   6)
+* metacharacters in regular expressions: Regexp Operators.    (line   6)
 * metacharacters, escape sequences for:  Escape Sequences.    (line 130)
-* mktime() function (gawk):              Time Functions.      (line  25)
+* minimum precision supported by MPFR library: Auto-set.      (line 224)
+* mktime:                                Time Functions.      (line  25)
 * modifiers, in format specifiers:       Format Modifiers.    (line   6)
-* monetary information, localization:    Explaining gettext.  (line 103)
-* MPFR:                                  Arbitrary Precision Arithmetic.
-                                                              (line   6)
-* msgfmt utility:                        I18N Example.        (line  62)
+* monetary information, localization:    Explaining gettext.  (line 104)
+* Moore, Duncan:                         Getline Notes.       (line  40)
+* msgfmt utility:                        I18N Example.        (line  63)
 * multiple precision:                    Arbitrary Precision Arithmetic.
                                                               (line   6)
+* multiple-line records:                 Multiple Line.       (line   6)
 * n debugger command (alias for next):   Debugger Execution Control.
                                                               (line  43)
 * names, arrays/variables <1>:           Library Names.       (line   6)
@@ -31208,25 +32891,25 @@ Index
 * namespace issues <1>:                  Library Names.       (line   6)
 * namespace issues:                      Arrays.              (line  18)
 * namespace issues, functions:           Definition Syntax.   (line  20)
-* nawk utility:                          Names.               (line  17)
-* negative zero:                         Unexpected Results.  (line  34)
-* NetBSD:                                Glossary.            (line 624)
+* nawk utility:                          Names.               (line  10)
+* NetBSD:                                Glossary.            (line 611)
 * networks, programming:                 TCP/IP Networking.   (line   6)
 * networks, support for:                 Special Network.     (line   6)
 * newlines <1>:                          Boolean Ops.         (line  67)
-* newlines <2>:                          Options.             (line 253)
+* newlines <2>:                          Options.             (line 260)
 * newlines:                              Statements/Lines.    (line   6)
 * newlines, as field separators:         Default Field Splitting.
                                                               (line   6)
-* newlines, as record separators:        Records.             (line  20)
-* newlines, in dynamic regexps:          Computed Regexps.    (line  58)
-* newlines, in regexp constants:         Computed Regexps.    (line  68)
+* newlines, as record separators:        awk split records.   (line  12)
+* newlines, in dynamic regexps:          Computed Regexps.    (line  59)
+* newlines, in regexp constants:         Computed Regexps.    (line  69)
 * newlines, printing:                    Print Examples.      (line  12)
 * newlines, separating statements in actions <1>: Statements. (line  10)
 * newlines, separating statements in actions: Action Overview.
                                                               (line  19)
 * next debugger command:                 Debugger Execution Control.
                                                               (line  43)
+* next file statement:                   Feature History.     (line 169)
 * next statement <1>:                    Next Statement.      (line   6)
 * next statement:                        Boolean Ops.         (line  85)
 * next statement, BEGIN/END patterns and: I/O And BEGIN/END.  (line  37)
@@ -31242,27 +32925,32 @@ Index
                                                               (line  47)
 * nexti debugger command:                Debugger Execution Control.
                                                               (line  49)
-* NF variable <1>:                       Auto-set.            (line 117)
+* NF variable <1>:                       Auto-set.            (line 112)
 * NF variable:                           Fields.              (line  33)
 * NF variable, decrementing:             Changing Fields.     (line 107)
 * ni debugger command (alias for nexti): Debugger Execution Control.
                                                               (line  49)
 * noassign.awk program:                  Ignoring Assigns.    (line  15)
+* non-existent array elements:           Reference to Elements.
+                                                              (line  23)
 * not Boolean-logic operator:            Boolean Ops.         (line   6)
-* NR variable <1>:                       Auto-set.            (line 137)
+* NR variable <1>:                       Auto-set.            (line 131)
 * NR variable:                           Records.             (line   6)
-* NR variable, changing:                 Auto-set.            (line 323)
+* NR variable, changing:                 Auto-set.            (line 309)
 * null strings <1>:                      Basic Data Typing.   (line  26)
 * null strings <2>:                      Truth Values.        (line   6)
 * null strings <3>:                      Regexp Field Splitting.
                                                               (line  43)
-* null strings:                          Records.             (line 107)
-* null strings, array elements and:      Delete.              (line  27)
+* null strings:                          awk split records.   (line 114)
+* null strings in gawk arguments, quoting and: Quoting.       (line  79)
+* null strings, and deleting array elements: Delete.          (line  27)
 * null strings, as array subscripts:     Uninitialized Subscripts.
                                                               (line  43)
-* null strings, converting numbers to strings: Conversion.    (line  21)
+* null strings, converting numbers to strings: Strings And Numbers.
+                                                              (line  21)
 * null strings, matching:                Gory Details.        (line 164)
-* null strings, quoting and:             Quoting.             (line  62)
+* number as string of bits:              Bitwise Functions.   (line 109)
+* number of array elements:              String Functions.    (line 197)
 * number sign (#), #! (executable scripts): Executable Scripts.
                                                               (line   6)
 * number sign (#), commenting:           Comments.            (line   6)
@@ -31272,29 +32960,28 @@ Index
 * numbers, Cliff random:                 Cliff Random Function.
                                                               (line   6)
 * numbers, converting <1>:               Bitwise Functions.   (line 109)
-* numbers, converting:                   Conversion.          (line   6)
-* numbers, converting, to strings:       User-modified.       (line  28)
-* numbers, floating-point:               General Arithmetic.  (line   6)
+* numbers, converting:                   Strings And Numbers. (line   6)
+* numbers, converting, to strings:       User-modified.       (line  30)
 * numbers, hexadecimal:                  Nondecimal-numbers.  (line   6)
 * numbers, octal:                        Nondecimal-numbers.  (line   6)
-* numbers, random:                       Numeric Functions.   (line  64)
 * numbers, rounding:                     Round Function.      (line   6)
-* numeric, constants:                    Scalar Constants.    (line   6)
+* numeric constants:                     Scalar Constants.    (line   6)
+* numeric functions:                     Numeric Functions.   (line   6)
 * numeric, output format:                OFMT.                (line   6)
 * numeric, strings:                      Variable Typing.     (line   6)
 * o debugger command (alias for option): Debugger Info.       (line  57)
-* oawk utility:                          Names.               (line  17)
+* oawk utility:                          Names.               (line  10)
 * obsolete features:                     Obsolete.            (line   6)
 * octal numbers:                         Nondecimal-numbers.  (line   6)
-* octal values, enabling interpretation of: Options.          (line 207)
-* OFMT variable <1>:                     User-modified.       (line 115)
-* OFMT variable <2>:                     Conversion.          (line  55)
+* octal values, enabling interpretation of: Options.          (line 211)
+* OFMT variable <1>:                     User-modified.       (line 105)
+* OFMT variable <2>:                     Strings And Numbers. (line  57)
 * OFMT variable:                         OFMT.                (line  15)
 * OFMT variable, POSIX awk and:          OFMT.                (line  27)
-* OFS variable <1>:                      User-modified.       (line 124)
+* OFS variable <1>:                      User-modified.       (line 114)
 * OFS variable <2>:                      Output Separators.   (line   6)
 * OFS variable:                          Changing Fields.     (line  64)
-* OpenBSD:                               Glossary.            (line 624)
+* OpenBSD:                               Glossary.            (line 611)
 * OpenSolaris:                           Other Versions.      (line  96)
 * operating systems, BSD-based:          Manual History.      (line  28)
 * operating systems, PC, gawk on:        PC Using.            (line   6)
@@ -31329,31 +33016,29 @@ Index
 * operators, word-boundary (gawk):       GNU Regexp Operators.
                                                               (line  63)
 * option debugger command:               Debugger Info.       (line  57)
-* options, command-line <1>:             Command Line Field Separator.
-                                                              (line   6)
-* options, command-line <2>:             Options.             (line   6)
-* options, command-line:                 Long.                (line  12)
-* options, command-line, end of:         Options.             (line  68)
+* options, command-line:                 Options.             (line   6)
+* options, command-line, end of:         Options.             (line  54)
 * options, command-line, invoking awk:   Command Line.        (line   6)
 * options, command-line, processing:     Getopt Function.     (line   6)
 * options, deprecated:                   Obsolete.            (line   6)
 * options, long <1>:                     Options.             (line   6)
 * options, long:                         Command Line.        (line  13)
-* options, printing list of:             Options.             (line 168)
+* options, printing list of:             Options.             (line 154)
+* or:                                    Bitwise Functions.   (line  49)
 * OR bitwise operation:                  Bitwise Functions.   (line   6)
 * or Boolean-logic operator:             Boolean Ops.         (line   6)
-* or() function (gawk):                  Bitwise Functions.   (line  49)
-* ord extension function:                Extension Sample Ord.
+* ord() extension function:              Extension Sample Ord.
                                                               (line  12)
 * ord() user-defined function:           Ordinal Functions.   (line  16)
 * order of evaluation, concatenation:    Concatenation.       (line  41)
-* ORS variable <1>:                      User-modified.       (line 129)
+* ORS variable <1>:                      User-modified.       (line 119)
 * ORS variable:                          Output Separators.   (line  20)
 * output field separator, See OFS variable: Changing Fields.  (line  64)
 * output record separator, See ORS variable: Output Separators.
                                                               (line  20)
 * output redirection:                    Redirection.         (line   6)
-* output, buffering:                     I/O Functions.       (line  29)
+* output wrapper:                        Output Wrappers.     (line   6)
+* output, buffering:                     I/O Functions.       (line  32)
 * output, duplicating into files:        Tee Program.         (line   6)
 * output, files, closing:                Close Files And Pipes.
                                                               (line   6)
@@ -31365,89 +33050,92 @@ Index
 * output, standard:                      Special FD.          (line   6)
 * p debugger command (alias for print):  Viewing And Changing Data.
                                                               (line  36)
-* P1003.1 POSIX standard:                Glossary.            (line 462)
-* parentheses () <1>:                    Profiling.           (line 138)
-* parentheses ():                        Regexp Operators.    (line  79)
+* Papadopoulos, Panos:                   Contributors.        (line 128)
+* parent process ID of gawk process:     Auto-set.            (line 189)
+* parentheses (), in a profile:          Profiling.           (line 146)
+* parentheses (), regexp operator:       Regexp Operators.    (line  80)
 * password file:                         Passwd Functions.    (line  16)
-* patsplit() function (gawk):            String Functions.    (line 290)
+* patsplit:                              String Functions.    (line 294)
 * patterns:                              Patterns and Actions.
                                                               (line   6)
 * patterns, comparison expressions as:   Expression Patterns. (line  14)
-* patterns, counts:                      Profiling.           (line 110)
+* patterns, counts, in a profile:        Profiling.           (line 118)
 * patterns, default:                     Very Simple.         (line  34)
 * patterns, empty:                       Empty.               (line   6)
 * patterns, expressions as:              Regexp Patterns.     (line   6)
 * patterns, ranges in:                   Ranges.              (line   6)
-* patterns, regexp constants as:         Expression Patterns. (line  36)
+* patterns, regexp constants as:         Expression Patterns. (line  34)
 * patterns, types of:                    Pattern Overview.    (line  15)
 * pawk (profiling version of Brian Kernighan's awk): Other Versions.
                                                               (line  78)
-* pawk, awk-like facilities for Python:  Other Versions.      (line 124)
+* pawk, awk-like facilities for Python:  Other Versions.      (line 125)
 * PC operating systems, gawk on:         PC Using.            (line   6)
 * PC operating systems, gawk on, installing: PC Installation. (line   6)
 * percent sign (%), % operator:          Precedence.          (line  55)
 * percent sign (%), %= operator <1>:     Precedence.          (line  95)
-* percent sign (%), %= operator:         Assignment Ops.      (line 129)
-* period (.):                            Regexp Operators.    (line  43)
+* percent sign (%), %= operator:         Assignment Ops.      (line 130)
+* period (.), regexp operator:           Regexp Operators.    (line  44)
 * Perl:                                  Future Extensions.   (line   6)
 * Peters, Arno:                          Contributors.        (line  85)
 * Peterson, Hal:                         Contributors.        (line  39)
-* pipes, closing:                        Close Files And Pipes.
+* pipe, closing:                         Close Files And Pipes.
                                                               (line   6)
-* pipes, input:                          Getline/Pipe.        (line   9)
-* pipes, output:                         Redirection.         (line  57)
-* Pitts, Dave <1>:                       Bugs.                (line  73)
+* pipe, input:                           Getline/Pipe.        (line   9)
+* pipe, output:                          Redirection.         (line  57)
+* Pitts, Dave <1>:                       Bugs.                (line  71)
 * Pitts, Dave:                           Acknowledgments.     (line  60)
-* plus sign (+):                         Regexp Operators.    (line 102)
+* Plauger, P.J.:                         Library Functions.   (line  12)
+* plug-in:                               Extension Intro.     (line   6)
 * plus sign (+), + operator:             Precedence.          (line  52)
 * plus sign (+), ++ operator <1>:        Precedence.          (line  46)
 * plus sign (+), ++ operator:            Increment Ops.       (line  11)
 * plus sign (+), += operator <1>:        Precedence.          (line  95)
 * plus sign (+), += operator:            Assignment Ops.      (line  82)
+* plus sign (+), regexp operator:        Regexp Operators.    (line 103)
 * pointers to functions:                 Indirect Calls.      (line   6)
 * portability:                           Escape Sequences.    (line  94)
 * portability, #! (executable scripts):  Executable Scripts.  (line  33)
 * portability, ** operator and:          Arithmetic Ops.      (line  81)
-* portability, **= operator and:         Assignment Ops.      (line 142)
+* portability, **= operator and:         Assignment Ops.      (line 143)
 * portability, ARGV variable:            Executable Scripts.  (line  42)
 * portability, backslash continuation and: Statements/Lines.  (line  30)
 * portability, backslash in escape sequences: Escape Sequences.
                                                               (line 112)
 * portability, close() function and:     Close Files And Pipes.
                                                               (line  81)
-* portability, data files as single record: Records.          (line 179)
+* portability, data files as single record: gawk split records.
+                                                              (line  65)
 * portability, deleting array elements:  Delete.              (line  56)
 * portability, example programs:         Library Functions.   (line  42)
-* portability, functions, defining:      Definition Syntax.   (line  99)
+* portability, functions, defining:      Definition Syntax.   (line 105)
 * portability, gawk:                     New Ports.           (line   6)
-* portability, gettext library and:      Explaining gettext.  (line  10)
+* portability, gettext library and:      Explaining gettext.  (line  11)
 * portability, internationalization and: I18N Portability.    (line   6)
-* portability, length() function:        String Functions.    (line 172)
-* portability, new awk vs. old awk:      Conversion.          (line  55)
+* portability, length() function:        String Functions.    (line 176)
+* portability, new awk vs. old awk:      Strings And Numbers. (line  57)
 * portability, next statement in user-defined functions: Pass By Value/Reference.
                                                               (line  91)
 * portability, NF variable, decrementing: Changing Fields.    (line 115)
 * portability, operators:                Increment Ops.       (line  60)
 * portability, operators, not in POSIX awk: Precedence.       (line  98)
-* portability, POSIXLY_CORRECT environment variable: Options. (line 353)
-* portability, substr() function:        String Functions.    (line 509)
+* portability, POSIXLY_CORRECT environment variable: Options. (line 360)
+* portability, substr() function:        String Functions.    (line 510)
 * portable object files <1>:             Translator i18n.     (line   6)
-* portable object files:                 Explaining gettext.  (line  36)
+* portable object files:                 Explaining gettext.  (line  37)
 * portable object files, converting to message object files: I18N Example.
-                                                              (line  62)
-* portable object files, generating:     Options.             (line 161)
-* portable object template files:        Explaining gettext.  (line  30)
+                                                              (line  63)
+* portable object files, generating:     Options.             (line 147)
+* portable object template files:        Explaining gettext.  (line  31)
 * porting gawk:                          New Ports.           (line   6)
 * positional specifiers, printf statement <1>: Printf Ordering.
                                                               (line   6)
 * positional specifiers, printf statement: Format Modifiers.  (line  13)
 * positional specifiers, printf statement, mixing with regular formats: Printf Ordering.
                                                               (line  57)
-* positive zero:                         Unexpected Results.  (line  34)
-* POSIX awk <1>:                         Assignment Ops.      (line 136)
+* POSIX awk <1>:                         Assignment Ops.      (line 137)
 * POSIX awk:                             This Manual.         (line  14)
 * POSIX awk, ** operator and:            Precedence.          (line  98)
-* POSIX awk, **= operator and:           Assignment Ops.      (line 142)
+* POSIX awk, **= operator and:           Assignment Ops.      (line 143)
 * POSIX awk, < operator and:             Getline/File.        (line  26)
 * POSIX awk, arithmetic operators and:   Arithmetic Ops.      (line  30)
 * POSIX awk, backslashes in string constants: Escape Sequences.
@@ -31459,36 +33147,35 @@ Index
 * POSIX awk, break statement and:        Break Statement.     (line  51)
 * POSIX awk, changes in awk versions:    POSIX.               (line   6)
 * POSIX awk, continue statement and:     Continue Statement.  (line  43)
-* POSIX awk, CONVFMT variable and:       User-modified.       (line  28)
-* POSIX awk, date utility and:           Time Functions.      (line 262)
+* POSIX awk, CONVFMT variable and:       User-modified.       (line  30)
+* POSIX awk, date utility and:           Time Functions.      (line 254)
 * POSIX awk, field separators and <1>:   Field Splitting Summary.
                                                               (line  40)
 * POSIX awk, field separators and:       Fields.              (line   6)
-* POSIX awk, FS variable and:            User-modified.       (line  66)
-* POSIX awk, function keyword in:        Definition Syntax.   (line  83)
+* POSIX awk, FS variable and:            User-modified.       (line  60)
+* POSIX awk, function keyword in:        Definition Syntax.   (line  89)
 * POSIX awk, functions and, gsub()/sub(): Gory Details.       (line  54)
-* POSIX awk, functions and, length():    String Functions.    (line 172)
+* POSIX awk, functions and, length():    String Functions.    (line 176)
 * POSIX awk, GNU long options and:       Options.             (line  15)
-* POSIX awk, interval expressions in:    Regexp Operators.    (line 135)
+* POSIX awk, interval expressions in:    Regexp Operators.    (line 136)
 * POSIX awk, next/nextfile statements and: Next Statement.    (line  45)
 * POSIX awk, numeric strings and:        Variable Typing.     (line   6)
-* POSIX awk, OFMT variable and <1>:      Conversion.          (line  55)
+* POSIX awk, OFMT variable and <1>:      Strings And Numbers. (line  57)
 * POSIX awk, OFMT variable and:          OFMT.                (line  27)
-* POSIX awk, period (.), using:          Regexp Operators.    (line  50)
+* POSIX awk, period (.), using:          Regexp Operators.    (line  51)
 * POSIX awk, printf format strings and:  Format Modifiers.    (line 159)
-* POSIX awk, regular expressions and:    Regexp Operators.    (line 161)
+* POSIX awk, regular expressions and:    Regexp Operators.    (line 162)
 * POSIX awk, timestamps and:             Time Functions.      (line   6)
 * POSIX awk, | I/O operator and:         Getline/Pipe.        (line  55)
-* POSIX mode:                            Options.             (line 247)
+* POSIX mode:                            Options.             (line 254)
 * POSIX, awk and:                        Preface.             (line  23)
 * POSIX, gawk extensions not included in: POSIX/GNU.          (line   6)
 * POSIX, programs, implementing in awk:  Clones.              (line   6)
-* POSIXLY_CORRECT environment variable:  Options.             (line 332)
-* PREC variable <1>:                     Setting Precision.   (line   6)
-* PREC variable:                         User-modified.       (line 134)
+* POSIXLY_CORRECT environment variable:  Options.             (line 340)
+* PREC variable:                         User-modified.       (line 124)
 * precedence <1>:                        Precedence.          (line   6)
 * precedence:                            Increment Ops.       (line  60)
-* precedence, regexp operators:          Regexp Operators.    (line 156)
+* precedence, regexp operators:          Regexp Operators.    (line 157)
 * print debugger command:                Viewing And Changing Data.
                                                               (line  36)
 * print statement:                       Printing.            (line  16)
@@ -31496,10 +33183,12 @@ Index
 * print statement, commas, omitting:     Print Examples.      (line  31)
 * print statement, I/O operators in:     Precedence.          (line  71)
 * print statement, line continuations and: Print Examples.    (line  76)
-* print statement, OFMT variable and:    User-modified.       (line 124)
+* print statement, OFMT variable and:    User-modified.       (line 114)
 * print statement, See Also redirection, of output: Redirection.
                                                               (line  17)
 * print statement, sprintf() function and: Round Function.    (line   6)
+* print variables, in debugger:          Viewing And Changing Data.
+                                                              (line  36)
 * printf debugger command:               Viewing And Changing Data.
                                                               (line  54)
 * printf statement <1>:                  Printf.              (line   6)
@@ -31519,67 +33208,75 @@ Index
 * printf statement, sprintf() function and: Round Function.   (line   6)
 * printf statement, syntax of:           Basic Printf.        (line   6)
 * printing:                              Printing.            (line   6)
-* printing, list of options:             Options.             (line 168)
+* printing messages from extensions:     Printing Messages.   (line   6)
+* printing, list of options:             Options.             (line 154)
 * printing, mailing labels:              Labels Program.      (line   6)
 * printing, unduplicated lines of text:  Uniq Program.        (line   6)
 * printing, user information:            Id Program.          (line   6)
 * private variables:                     Library Names.       (line  11)
+* process group idIDof gawk process:     Auto-set.            (line 183)
+* process ID of gawk process:            Auto-set.            (line 186)
 * processes, two-way communications with: Two-way I/O.        (line  23)
 * processing data:                       Basic High Level.    (line   6)
-* PROCINFO array <1>:                    Two-way I/O.         (line 116)
-* PROCINFO array <2>:                    Id Program.          (line  15)
-* PROCINFO array <3>:                    Group Functions.     (line   6)
-* PROCINFO array <4>:                    Passwd Functions.    (line   6)
-* PROCINFO array <5>:                    Time Functions.      (line  47)
-* PROCINFO array <6>:                    Auto-set.            (line 142)
-* PROCINFO array:                        Obsolete.            (line  11)
+* PROCINFO array <1>:                    Passwd Functions.    (line   6)
+* PROCINFO array <2>:                    Time Functions.      (line  47)
+* PROCINFO array:                        Auto-set.            (line 136)
+* PROCINFO array, and communications via ptys: Two-way I/O.   (line 117)
+* PROCINFO array, and group membership:  Group Functions.     (line   6)
+* PROCINFO array, and user and group ID numbers: Id Program.  (line  15)
+* PROCINFO array, testing the field splitting: Passwd Functions.
+                                                              (line 161)
+* PROCINFO array, uses:                  Auto-set.            (line 242)
+* PROCINFO, values of sorted_in:         Controlling Scanning.
+                                                              (line  26)
 * profiling awk programs:                Profiling.           (line   6)
-* profiling awk programs, dynamically:   Profiling.           (line 172)
+* profiling awk programs, dynamically:   Profiling.           (line 179)
+* program identifiers:                   Auto-set.            (line 154)
 * program, definition of:                Getting Started.     (line  21)
 * programmers, attractiveness of:        Two-way I/O.         (line   6)
 * programming conventions, --non-decimal-data option: Nondecimal Data.
                                                               (line  36)
-* programming conventions, ARGC/ARGV variables: Auto-set.     (line  31)
+* programming conventions, ARGC/ARGV variables: Auto-set.     (line  35)
 * programming conventions, exit statement: Exit Statement.    (line  38)
 * programming conventions, function parameters: Return Statement.
                                                               (line  45)
 * programming conventions, functions, calling: Calling Built-in.
                                                               (line  10)
 * programming conventions, functions, writing: Definition Syntax.
-                                                              (line  55)
+                                                              (line  61)
 * programming conventions, gawk extensions: Internal File Ops.
                                                               (line  45)
 * programming conventions, private variable names: Library Names.
                                                               (line  23)
 * programming language, recipe for:      History.             (line   6)
-* Programming languages, Ada:            Glossary.            (line  20)
+* programming languages, Ada:            Glossary.            (line  19)
 * programming languages, data-driven vs. procedural: Getting Started.
                                                               (line  12)
-* Programming languages, Java:           Glossary.            (line 388)
+* programming languages, Java:           Glossary.            (line 379)
 * programming, basic steps:              Basic High Level.    (line  20)
 * programming, concepts:                 Basic Concepts.      (line   6)
 * pwcat program:                         Passwd Functions.    (line  23)
 * q debugger command (alias for quit):   Miscellaneous Debugger Commands.
                                                               (line  99)
-* QSE Awk:                               Other Versions.      (line 130)
-* question mark (?) regexp operator <1>: GNU Regexp Operators.
-                                                              (line  59)
-* question mark (?) regexp operator:     Regexp Operators.    (line 111)
+* QSE Awk:                               Other Versions.      (line 131)
+* Quanstrom, Erik:                       Alarm Program.       (line   8)
 * question mark (?), ?: operator:        Precedence.          (line  92)
-* QuikTrim Awk:                          Other Versions.      (line 134)
+* question mark (?), regexp operator <1>: GNU Regexp Operators.
+                                                              (line  59)
+* question mark (?), regexp operator:    Regexp Operators.    (line 112)
+* QuikTrim Awk:                          Other Versions.      (line 135)
 * quit debugger command:                 Miscellaneous Debugger Commands.
                                                               (line  99)
-* QUIT signal (MS-Windows):              Profiling.           (line 207)
-* quoting <1>:                           Comments.            (line  27)
-* quoting <2>:                           Long.                (line  26)
-* quoting:                               Read Terminal.       (line  25)
-* quoting, rules for:                    Quoting.             (line   6)
-* quoting, tricks for:                   Quoting.             (line  71)
+* QUIT signal (MS-Windows):              Profiling.           (line 214)
+* quoting in gawk command lines:         Long.                (line  26)
+* quoting in gawk command lines, tricks for: Quoting.         (line  88)
+* quoting, for small awk programs:       Comments.            (line  27)
 * r debugger command (alias for run):    Debugger Execution Control.
                                                               (line  62)
 * Rakitzis, Byron:                       History Sorting.     (line  25)
+* Ramey, Chet <1>:                       General Data Types.  (line   6)
 * Ramey, Chet:                           Acknowledgments.     (line  60)
-* rand() function:                       Numeric Functions.   (line  34)
+* rand:                                  Numeric Functions.   (line  34)
 * random numbers, Cliff:                 Cliff Random Function.
                                                               (line   6)
 * random numbers, rand()/srand() functions: Numeric Functions.
@@ -31587,67 +33284,74 @@ Index
 * random numbers, seed of:               Numeric Functions.   (line  64)
 * range expressions (regexps):           Bracket Expressions. (line   6)
 * range patterns:                        Ranges.              (line   6)
-* Rankin, Pat <1>:                       Bugs.                (line  72)
+* range patterns, line continuation and: Ranges.              (line  65)
+* Rankin, Pat <1>:                       Bugs.                (line  71)
 * Rankin, Pat <2>:                       Contributors.        (line  37)
 * Rankin, Pat <3>:                       Assignment Ops.      (line 100)
 * Rankin, Pat:                           Acknowledgments.     (line  60)
-* reada extension function:              Extension Sample Read write array.
+* reada() extension function:            Extension Sample Read write array.
                                                               (line  15)
 * readable data files, checking:         File Checking.       (line   6)
 * readable.awk program:                  File Checking.       (line  11)
 * readdir extension:                     Extension Sample Readdir.
                                                               (line   9)
-* readfile extension function:           Extension Sample Readfile.
-                                                              (line  11)
+* readfile() extension function:         Extension Sample Readfile.
+                                                              (line  12)
 * readfile() user-defined function:      Readfile Function.   (line  30)
+* reading input files:                   Reading Files.       (line   6)
 * recipe for a programming language:     History.             (line   6)
-* record separators <1>:                 User-modified.       (line 143)
-* record separators:                     Records.             (line  14)
-* record separators, changing:           Records.             (line  81)
-* record separators, regular expressions as: Records.         (line 117)
+* record separators <1>:                 User-modified.       (line 133)
+* record separators:                     awk split records.   (line   6)
+* record separators, changing:           awk split records.   (line  85)
+* record separators, regular expressions as: awk split records.
+                                                              (line 124)
 * record separators, with multiline records: Multiple Line.   (line  10)
 * records <1>:                           Basic High Level.    (line  73)
 * records:                               Reading Files.       (line  14)
 * records, multiline:                    Multiple Line.       (line   6)
 * records, printing:                     Print.               (line  22)
 * records, splitting input into:         Records.             (line   6)
-* records, terminating:                  Records.             (line 117)
-* records, treating files as:            Records.             (line 200)
-* recursive functions:                   Definition Syntax.   (line  73)
+* records, terminating:                  awk split records.   (line 124)
+* records, treating files as:            gawk split records.  (line  92)
+* recursive functions:                   Definition Syntax.   (line  79)
+* redirect gawk output, in debugger:     Debugger Info.       (line  72)
 * redirection of input:                  Getline/File.        (line   6)
 * redirection of output:                 Redirection.         (line   6)
 * reference counting, sorting arrays:    Array Sorting Functions.
                                                               (line  77)
+* regexp:                                Regexp.              (line   6)
 * regexp constants <1>:                  Comparison Operators.
-                                                              (line 103)
+                                                              (line 102)
 * regexp constants <2>:                  Regexp Constants.    (line   6)
 * regexp constants:                      Regexp Usage.        (line  57)
-* regexp constants, /=.../, /= operator and: Assignment Ops.  (line 147)
-* regexp constants, as patterns:         Expression Patterns. (line  36)
+* regexp constants, /=.../, /= operator and: Assignment Ops.  (line 148)
+* regexp constants, as patterns:         Expression Patterns. (line  34)
 * regexp constants, in gawk:             Using Constant Regexps.
                                                               (line  28)
-* regexp constants, slashes vs. quotes:  Computed Regexps.    (line  28)
-* regexp constants, vs. string constants: Computed Regexps.   (line  38)
-* regexp, See regular expressions:       Regexp.              (line   6)
+* regexp constants, slashes vs. quotes:  Computed Regexps.    (line  29)
+* regexp constants, vs. string constants: Computed Regexps.   (line  39)
+* register extension:                    Registration Functions.
+                                                              (line   6)
 * regular expressions:                   Regexp.              (line   6)
-* regular expressions as field separators: Field Separators.  (line  50)
+* regular expressions as field separators: Field Separators.  (line  51)
 * regular expressions, anchors in:       Regexp Operators.    (line  22)
 * regular expressions, as field separators: Regexp Field Splitting.
                                                               (line   6)
 * regular expressions, as patterns <1>:  Regexp Patterns.     (line   6)
 * regular expressions, as patterns:      Regexp Usage.        (line   6)
-* regular expressions, as record separators: Records.         (line 117)
-* regular expressions, case sensitivity <1>: User-modified.   (line  82)
+* regular expressions, as record separators: awk split records.
+                                                              (line 124)
+* regular expressions, case sensitivity <1>: User-modified.   (line  76)
 * regular expressions, case sensitivity: Case-sensitivity.    (line   6)
 * regular expressions, computed:         Computed Regexps.    (line   6)
 * regular expressions, constants, See regexp constants: Regexp Usage.
                                                               (line  57)
 * regular expressions, dynamic:          Computed Regexps.    (line   6)
 * regular expressions, dynamic, with embedded newlines: Computed Regexps.
-                                                              (line  58)
+                                                              (line  59)
 * regular expressions, gawk, command-line options: GNU Regexp Operators.
                                                               (line  70)
-* regular expressions, interval expressions and: Options.     (line 272)
+* regular expressions, interval expressions and: Options.     (line 279)
 * regular expressions, leftmost longest match: Leftmost Longest.
                                                               (line   6)
 * regular expressions, operators <1>:    Regexp Operators.    (line   6)
@@ -31659,16 +33363,17 @@ Index
 * regular expressions, operators, gawk:  GNU Regexp Operators.
                                                               (line   6)
 * regular expressions, operators, precedence of: Regexp Operators.
-                                                              (line 156)
+                                                              (line 157)
 * regular expressions, searching for:    Egrep Program.       (line   6)
 * relational operators, See comparison operators: Typing and Comparison.
                                                               (line   9)
+* replace in string:                     String Functions.    (line 406)
 * return debugger command:               Debugger Execution Control.
                                                               (line  54)
 * return statement, user-defined functions: Return Statement. (line   6)
 * return value, close() function:        Close Files And Pipes.
-                                                              (line 130)
-* rev() user-defined function:           Function Example.    (line  52)
+                                                              (line 131)
+* rev() user-defined function:           Function Example.    (line  53)
 * revoutput extension:                   Extension Sample Revout.
                                                               (line  11)
 * revtwoway extension:                   Extension Sample Rev2way.
@@ -31683,42 +33388,40 @@ Index
                                                               (line  11)
 * right angle bracket (>), >> operator (I/O) <1>: Precedence. (line  65)
 * right angle bracket (>), >> operator (I/O): Redirection.    (line  50)
+* right shift:                           Bitwise Functions.   (line  52)
 * right shift, bitwise:                  Bitwise Functions.   (line  32)
-* Ritchie, Dennis:                       Basic Data Typing.   (line  55)
-* RLENGTH variable:                      Auto-set.            (line 262)
-* RLENGTH variable, match() function and: String Functions.   (line 220)
+* Ritchie, Dennis:                       Basic Data Typing.   (line  54)
+* RLENGTH variable:                      Auto-set.            (line 252)
+* RLENGTH variable, match() function and: String Functions.   (line 224)
 * Robbins, Arnold <1>:                   Future Extensions.   (line   6)
 * Robbins, Arnold <2>:                   Bugs.                (line  32)
-* Robbins, Arnold <3>:                   Contributors.        (line 130)
-* Robbins, Arnold <4>:                   Alarm Program.       (line   6)
-* Robbins, Arnold <5>:                   Passwd Functions.    (line  90)
-* Robbins, Arnold <6>:                   Getline/Pipe.        (line  39)
+* Robbins, Arnold <3>:                   Contributors.        (line 141)
+* Robbins, Arnold <4>:                   General Data Types.  (line   6)
+* Robbins, Arnold <5>:                   Alarm Program.       (line   6)
+* Robbins, Arnold <6>:                   Passwd Functions.    (line  90)
+* Robbins, Arnold <7>:                   Getline/Pipe.        (line  39)
 * Robbins, Arnold:                       Command Line Field Separator.
-                                                              (line  80)
+                                                              (line  73)
 * Robbins, Bill:                         Getline/Pipe.        (line  39)
-* Robbins, Harry:                        Acknowledgments.     (line  78)
-* Robbins, Jean:                         Acknowledgments.     (line  78)
+* Robbins, Harry:                        Acknowledgments.     (line  82)
+* Robbins, Jean:                         Acknowledgments.     (line  82)
 * Robbins, Miriam <1>:                   Passwd Functions.    (line  90)
 * Robbins, Miriam <2>:                   Getline/Pipe.        (line  39)
-* Robbins, Miriam:                       Acknowledgments.     (line  78)
+* Robbins, Miriam:                       Acknowledgments.     (line  82)
 * Rommel, Kai Uwe:                       Contributors.        (line  42)
+* round to nearest integer:              Numeric Functions.   (line  23)
 * round() user-defined function:         Round Function.      (line  16)
-* rounding mode, floating-point:         Rounding Mode.       (line   6)
 * rounding numbers:                      Round Function.      (line   6)
-* ROUNDMODE variable <1>:                Setting Rounding Mode.
-                                                              (line   6)
-* ROUNDMODE variable:                    User-modified.       (line 138)
-* RS variable <1>:                       User-modified.       (line 143)
-* RS variable:                           Records.             (line  20)
+* ROUNDMODE variable:                    User-modified.       (line 128)
+* RS variable <1>:                       User-modified.       (line 133)
+* RS variable:                           awk split records.   (line  12)
 * RS variable, multiline records and:    Multiple Line.       (line  17)
-* rshift() function (gawk):              Bitwise Functions.   (line  52)
-* RSTART variable:                       Auto-set.            (line 268)
-* RSTART variable, match() function and: String Functions.    (line 220)
-* RT variable <1>:                       Auto-set.            (line 275)
-* RT variable <2>:                       Getline/Variable/File.
-                                                              (line  10)
-* RT variable <3>:                       Multiple Line.       (line 129)
-* RT variable:                           Records.             (line 117)
+* rshift:                                Bitwise Functions.   (line  52)
+* RSTART variable:                       Auto-set.            (line 258)
+* RSTART variable, match() function and: String Functions.    (line 224)
+* RT variable <1>:                       Auto-set.            (line 265)
+* RT variable <2>:                       Multiple Line.       (line 129)
+* RT variable:                           awk split records.   (line 124)
 * Rubin, Paul <1>:                       Contributors.        (line  15)
 * Rubin, Paul:                           History.             (line  30)
 * rule, definition of:                   Getting Started.     (line  21)
@@ -31727,55 +33430,79 @@ Index
 * rvalues/lvalues:                       Assignment Ops.      (line  32)
 * s debugger command (alias for step):   Debugger Execution Control.
                                                               (line  68)
-* sandbox mode:                          Options.             (line 279)
+* sample debugging session:              Sample Debugging Session.
+                                                              (line   6)
+* sandbox mode:                          Options.             (line 286)
+* save debugger options:                 Debugger Info.       (line  84)
+* scalar or array:                       Type Functions.      (line  11)
 * scalar values:                         Basic Data Typing.   (line  13)
-* Schorr, Andrew <1>:                    Contributors.        (line 126)
+* scanning arrays:                       Scanning an Array.   (line   6)
+* scanning multidimensional arrays:      Multiscanning.       (line  11)
+* Schorr, Andrew <1>:                    Contributors.        (line 133)
+* Schorr, Andrew <2>:                    Auto-set.            (line 292)
 * Schorr, Andrew:                        Acknowledgments.     (line  60)
 * Schreiber, Bert:                       Acknowledgments.     (line  38)
 * Schreiber, Rita:                       Acknowledgments.     (line  38)
-* search paths <1>:                      VMS Running.         (line  29)
-* search paths <2>:                      PC Using.            (line  11)
-* search paths <3>:                      Igawk Program.       (line 368)
-* search paths <4>:                      AWKLIBPATH Variable. (line   6)
-* search paths:                          AWKPATH Variable.    (line   6)
-* search paths, for shared libraries:    AWKLIBPATH Variable. (line   6)
-* search paths, for source files <1>:    VMS Running.         (line  29)
-* search paths, for source files <2>:    PC Using.            (line  11)
-* search paths, for source files <3>:    Igawk Program.       (line 368)
+* search and replace in strings:         String Functions.    (line  89)
+* search in string:                      String Functions.    (line 155)
+* search paths <1>:                      VMS Running.         (line  58)
+* search paths <2>:                      PC Using.            (line  10)
+* search paths:                          Programs Exercises.  (line  63)
+* search paths, for loadable extensions: AWKLIBPATH Variable. (line   6)
+* search paths, for source files <1>:    VMS Running.         (line  58)
+* search paths, for source files <2>:    PC Using.            (line  10)
+* search paths, for source files <3>:    Programs Exercises.  (line  63)
 * search paths, for source files:        AWKPATH Variable.    (line   6)
-* searching:                             String Functions.    (line 150)
 * searching, files for regular expressions: Egrep Program.    (line   6)
 * searching, for words:                  Dupword Program.     (line   6)
-* sed utility <1>:                       Glossary.            (line  12)
+* sed utility <1>:                       Glossary.            (line  11)
 * sed utility <2>:                       Simple Sed.          (line   6)
 * sed utility:                           Field Splitting Summary.
                                                               (line  46)
-* semicolon (;):                         Statements/Lines.    (line  91)
-* semicolon (;), AWKPATH variable and:   PC Using.            (line  11)
+* seeding random number generator:       Numeric Functions.   (line  64)
+* semicolon (;), AWKPATH variable and:   PC Using.            (line  10)
 * semicolon (;), separating statements in actions <1>: Statements.
                                                               (line  10)
-* semicolon (;), separating statements in actions: Action Overview.
+* semicolon (;), separating statements in actions <2>: Action Overview.
                                                               (line  19)
-* separators, field:                     User-modified.       (line  56)
-* separators, field, FIELDWIDTHS variable and: User-modified. (line  35)
-* separators, field, FPAT variable and:  User-modified.       (line  45)
+* semicolon (;), separating statements in actions: Statements/Lines.
+                                                              (line  91)
+* separators, field:                     User-modified.       (line  50)
+* separators, field, FIELDWIDTHS variable and: User-modified. (line  37)
+* separators, field, FPAT variable and:  User-modified.       (line  43)
 * separators, field, POSIX and:          Fields.              (line   6)
-* separators, for records <1>:           User-modified.       (line 143)
-* separators, for records:               Records.             (line  14)
-* separators, for records, regular expressions as: Records.   (line 117)
+* separators, for records <1>:           User-modified.       (line 133)
+* separators, for records:               awk split records.   (line   6)
+* separators, for records, regular expressions as: awk split records.
+                                                              (line 124)
 * separators, for statements in actions: Action Overview.     (line  19)
-* separators, subscript:                 User-modified.       (line 156)
+* separators, subscript:                 User-modified.       (line 146)
+* set breakpoint:                        Breakpoint Control.  (line  11)
 * set debugger command:                  Viewing And Changing Data.
                                                               (line  59)
+* set directory of message catalogs:     I18N Functions.      (line  12)
+* set watchpoint:                        Viewing And Changing Data.
+                                                              (line  67)
+* shadowing of variable values:          Definition Syntax.   (line  67)
+* shell quoting, double quote:           Read Terminal.       (line  25)
+* shell quoting, rules for:              Quoting.             (line   6)
 * shells, piping commands into:          Redirection.         (line 142)
 * shells, quoting:                       Using Shell Variables.
                                                               (line  12)
 * shells, quoting, rules for:            Quoting.             (line  18)
 * shells, scripts:                       One-shot.            (line  22)
+* shells, sea:                           Undocumented.        (line   8)
 * shells, variables:                     Using Shell Variables.
                                                               (line   6)
 * shift, bitwise:                        Bitwise Functions.   (line  32)
 * short-circuit operators:               Boolean Ops.         (line  57)
+* show all source files, in debugger:    Debugger Info.       (line  45)
+* show breakpoints:                      Debugger Info.       (line  21)
+* show function arguments, in debugger:  Debugger Info.       (line  18)
+* show local variables, in debugger:     Debugger Info.       (line  34)
+* show name of current source file, in debugger: Debugger Info.
+                                                              (line  37)
+* show watchpoints:                      Debugger Info.       (line  51)
 * si debugger command (alias for stepi): Debugger Execution Control.
                                                               (line  76)
 * side effects <1>:                      Increment Ops.       (line  11)
@@ -31789,7 +33516,7 @@ Index
 * side effects, conditional expressions: Conditional Exp.     (line  22)
 * side effects, decrement/increment operators: Increment Ops. (line  11)
 * side effects, FILENAME variable:       Getline Notes.       (line  19)
-* side effects, function calls:          Function Calls.      (line  54)
+* side effects, function calls:          Function Calls.      (line  57)
 * side effects, statements:              Action Overview.     (line  32)
 * sidebar, A Constant's Base Does Not Affect Its Value: Nondecimal-numbers.
                                                               (line  64)
@@ -31797,89 +33524,100 @@ Index
                                                               (line 110)
 * sidebar, Changing FS Does Not Affect the Fields: Field Splitting Summary.
                                                               (line  38)
-* sidebar, Changing NR and FNR:          Auto-set.            (line 321)
+* sidebar, Changing NR and FNR:          Auto-set.            (line 307)
 * sidebar, Controlling Output Buffering with system(): I/O Functions.
-                                                              (line 135)
+                                                              (line 138)
 * sidebar, Escape Sequences for Metacharacters: Escape Sequences.
                                                               (line 128)
 * sidebar, FS and IGNORECASE:            Field Splitting Summary.
                                                               (line  64)
 * sidebar, Interactive Versus Noninteractive Buffering: I/O Functions.
-                                                              (line 104)
+                                                              (line 107)
 * sidebar, Matching the Null String:     Gory Details.        (line 162)
 * sidebar, Operator Evaluation Order:    Increment Ops.       (line  58)
 * sidebar, Piping into sh:               Redirection.         (line 140)
 * sidebar, Portability Issues with #!:   Executable Scripts.  (line  31)
+* sidebar, Pre-POSIX awk Used OFMT For String Conversion: Strings And Numbers.
+                                                              (line  55)
 * sidebar, Recipe For A Programming Language: History.        (line   6)
-* sidebar, RS = "\0" Is Not Portable:    Records.             (line 177)
+* sidebar, RS = "\0" Is Not Portable:    gawk split records.  (line  63)
 * sidebar, So Why Does gawk have BEGINFILE and ENDFILE?: Filetrans Function.
                                                               (line  83)
 * sidebar, Syntactic Ambiguities Between /= and Regular Expressions: Assignment Ops.
-                                                              (line 145)
+                                                              (line 146)
 * sidebar, Understanding $0:             Changing Fields.     (line 134)
 * sidebar, Using \n in Bracket Expressions of Dynamic Regexps: Computed Regexps.
-                                                              (line  56)
+                                                              (line  57)
 * sidebar, Using close()'s Return Value: Close Files And Pipes.
-                                                              (line 128)
-* SIGHUP signal:                         Profiling.           (line 204)
-* SIGINT signal (MS-Windows):            Profiling.           (line 207)
-* signals, HUP/SIGHUP:                   Profiling.           (line 204)
-* signals, INT/SIGINT (MS-Windows):      Profiling.           (line 207)
-* signals, QUIT/SIGQUIT (MS-Windows):    Profiling.           (line 207)
-* signals, USR1/SIGUSR1:                 Profiling.           (line 181)
-* SIGQUIT signal (MS-Windows):           Profiling.           (line 207)
-* SIGUSR1 signal:                        Profiling.           (line 181)
+                                                              (line 129)
+* SIGHUP signal, for dynamic profiling:  Profiling.           (line 211)
+* SIGINT signal (MS-Windows):            Profiling.           (line 214)
+* signals, HUP/SIGHUP, for profiling:    Profiling.           (line 211)
+* signals, INT/SIGINT (MS-Windows):      Profiling.           (line 214)
+* signals, QUIT/SIGQUIT (MS-Windows):    Profiling.           (line 214)
+* signals, USR1/SIGUSR1, for profiling:  Profiling.           (line 188)
+* signature program:                     Signature Program.   (line   6)
+* SIGQUIT signal (MS-Windows):           Profiling.           (line 214)
+* SIGUSR1 signal, for dynamic profiling: Profiling.           (line 188)
 * silent debugger command:               Debugger Execution Control.
                                                               (line  10)
-* sin() function:                        Numeric Functions.   (line  75)
-* single precision floating-point:       General Arithmetic.  (line  21)
-* single quote (') <1>:                  Quoting.             (line  31)
-* single quote (') <2>:                  Long.                (line  33)
+* sin:                                   Numeric Functions.   (line  75)
+* sine:                                  Numeric Functions.   (line  75)
 * single quote ('):                      One-shot.            (line  15)
+* single quote (') in gawk command lines: Long.               (line  33)
+* single quote ('), in shell commands:   Quoting.             (line  48)
 * single quote ('), vs. apostrophe:      Comments.            (line  27)
-* single quote ('), with double quotes:  Quoting.             (line  53)
+* single quote ('), with double quotes:  Quoting.             (line  70)
 * single-character fields:               Single Character Fields.
                                                               (line   6)
+* single-step execution, in the debugger: Debugger Execution Control.
+                                                              (line  43)
 * Skywalker, Luke:                       Undocumented.        (line   6)
-* sleep extension function:              Extension Sample Time.
-                                                              (line  23)
-* sleep utility:                         Alarm Program.       (line 109)
+* sleep utility:                         Alarm Program.       (line 111)
+* sleep() extension function:            Extension Sample Time.
+                                                              (line  22)
 * Solaris, POSIX-compliant awk:          Other Versions.      (line  96)
+* sort array:                            String Functions.    (line  42)
+* sort array indices:                    String Functions.    (line  42)
 * sort function, arrays, sorting:        Array Sorting Functions.
                                                               (line   6)
 * sort utility:                          Word Sorting.        (line  50)
 * sort utility, coprocesses and:         Two-way I/O.         (line  83)
 * sorting characters in different languages: Explaining gettext.
-                                                              (line  93)
+                                                              (line  94)
 * source code, awka:                     Other Versions.      (line  64)
 * source code, Brian Kernighan's awk:    Other Versions.      (line  13)
 * source code, Busybox Awk:              Other Versions.      (line  88)
 * source code, gawk:                     Gawk Distribution.   (line   6)
-* source code, Illumos awk:              Other Versions.      (line 104)
-* source code, jawk:                     Other Versions.      (line 112)
-* source code, libmawk:                  Other Versions.      (line 120)
+* source code, Illumos awk:              Other Versions.      (line 105)
+* source code, jawk:                     Other Versions.      (line 113)
+* source code, libmawk:                  Other Versions.      (line 121)
 * source code, mawk:                     Other Versions.      (line  44)
-* source code, mixing:                   Options.             (line 131)
+* source code, mixing:                   Options.             (line 117)
 * source code, pawk:                     Other Versions.      (line  78)
-* source code, QSE Awk:                  Other Versions.      (line 130)
-* source code, QuikTrim Awk:             Other Versions.      (line 134)
+* source code, pawk (Python version):    Other Versions.      (line 125)
+* source code, QSE Awk:                  Other Versions.      (line 131)
+* source code, QuikTrim Awk:             Other Versions.      (line 135)
 * source code, Solaris awk:              Other Versions.      (line  96)
-* source files, search path for:         Igawk Program.       (line 368)
-* sparse arrays:                         Array Intro.         (line  70)
-* Spencer, Henry:                        Glossary.            (line  12)
+* source files, search path for:         Programs Exercises.  (line  63)
+* sparse arrays:                         Array Intro.         (line  71)
+* Spencer, Henry:                        Glossary.            (line  11)
+* split:                                 String Functions.    (line 313)
+* split string into array:               String Functions.    (line 294)
 * split utility:                         Split Program.       (line   6)
-* split() function:                      String Functions.    (line 312)
 * split() function, array elements, deleting: Delete.         (line  61)
 * split.awk program:                     Split Program.       (line  30)
-* sprintf() function <1>:                String Functions.    (line 377)
-* sprintf() function:                    OFMT.                (line  15)
-* sprintf() function, OFMT variable and: User-modified.       (line 124)
+* sprintf <1>:                           String Functions.    (line 381)
+* sprintf:                               OFMT.                (line  15)
+* sprintf() function, OFMT variable and: User-modified.       (line 114)
 * sprintf() function, print/printf statements and: Round Function.
                                                               (line   6)
-* sqrt() function:                       Numeric Functions.   (line  78)
-* square brackets ([]):                  Regexp Operators.    (line  55)
-* srand() function:                      Numeric Functions.   (line  82)
-* Stallman, Richard <1>:                 Glossary.            (line 305)
+* sqrt:                                  Numeric Functions.   (line  78)
+* square brackets ([]), regexp operator: Regexp Operators.    (line  56)
+* square root:                           Numeric Functions.   (line  78)
+* srand:                                 Numeric Functions.   (line  82)
+* stack frame:                           Debugging Terms.     (line  10)
+* Stallman, Richard <1>:                 Glossary.            (line 296)
 * Stallman, Richard <2>:                 Contributors.        (line  23)
 * Stallman, Richard <3>:                 Acknowledgments.     (line  18)
 * Stallman, Richard:                     Manual History.      (line   6)
@@ -31887,7 +33625,8 @@ Index
 * standard input <1>:                    Special FD.          (line   6)
 * standard input:                        Read Terminal.       (line   6)
 * standard output:                       Special FD.          (line   6)
-* stat extension function:               Extension Sample File Functions.
+* starting the debugger:                 Debugger Invocation. (line   6)
+* stat() extension function:             Extension Sample File Functions.
                                                               (line  18)
 * statements, compound, control statements and: Statements.   (line  10)
 * statements, control, in actions:       Statements.          (line   6)
@@ -31896,37 +33635,44 @@ Index
                                                               (line  68)
 * stepi debugger command:                Debugger Execution Control.
                                                               (line  76)
+* stop automatic display, in debugger:   Viewing And Changing Data.
+                                                              (line  80)
 * stream editors <1>:                    Simple Sed.          (line   6)
 * stream editors:                        Field Splitting Summary.
                                                               (line  46)
-* strftime() function (gawk):            Time Functions.      (line  48)
+* strftime:                              Time Functions.      (line  48)
 * string constants:                      Scalar Constants.    (line  15)
-* string constants, vs. regexp constants: Computed Regexps.   (line  38)
+* string constants, vs. regexp constants: Computed Regexps.   (line  39)
 * string extraction (internationalization): String Extraction.
                                                               (line   6)
+* string length:                         String Functions.    (line 167)
 * string operators:                      Concatenation.       (line   8)
+* string, regular expression match:      String Functions.    (line 207)
+* string-manipulation functions:         String Functions.    (line   6)
 * string-matching operators:             Regexp Usage.        (line  19)
+* string-translation functions:          I18N Functions.      (line   6)
+* strings splitting, example:            String Functions.    (line 333)
 * strings, converting <1>:               Bitwise Functions.   (line 109)
-* strings, converting:                   Conversion.          (line   6)
-* strings, converting, numbers to:       User-modified.       (line  28)
-* strings, empty, See null strings:      Records.             (line 107)
+* strings, converting:                   Strings And Numbers. (line   6)
+* strings, converting letter case:       String Functions.    (line 520)
+* strings, converting, numbers to:       User-modified.       (line  30)
+* strings, empty, See null strings:      awk split records.   (line 114)
 * strings, extracting:                   String Extraction.   (line   6)
 * strings, for localization:             Programmer i18n.     (line  14)
-* strings, length of:                    Scalar Constants.    (line  20)
+* strings, length limitations:           Scalar Constants.    (line  20)
 * strings, merging arrays into:          Join Function.       (line   6)
 * strings, null:                         Regexp Field Splitting.
                                                               (line  43)
 * strings, numeric:                      Variable Typing.     (line   6)
-* strings, splitting:                    String Functions.    (line 332)
-* strtonum() function (gawk):            String Functions.    (line 384)
+* strtonum:                              String Functions.    (line 388)
 * strtonum() function (gawk), --non-decimal-data option and: Nondecimal Data.
                                                               (line  36)
-* sub() function <1>:                    String Functions.    (line 405)
-* sub() function:                        Using Constant Regexps.
+* sub <1>:                               String Functions.    (line 406)
+* sub:                                   Using Constant Regexps.
                                                               (line  43)
-* sub() function, arguments of:          String Functions.    (line 459)
+* sub() function, arguments of:          String Functions.    (line 460)
 * sub() function, escape processing:     Gory Details.        (line   6)
-* subscript separators:                  User-modified.       (line 156)
+* subscript separators:                  User-modified.       (line 146)
 * subscripts in arrays, multidimensional: Multidimensional.   (line  10)
 * subscripts in arrays, multidimensional, scanning: Multiscanning.
                                                               (line  11)
@@ -31934,16 +33680,20 @@ Index
                                                               (line   6)
 * subscripts in arrays, uninitialized variables as: Uninitialized Subscripts.
                                                               (line   6)
-* SUBSEP variable:                       User-modified.       (line 156)
-* SUBSEP variable, multidimensional arrays: Multidimensional. (line  16)
-* substr() function:                     String Functions.    (line 478)
+* SUBSEP variable:                       User-modified.       (line 146)
+* SUBSEP variable, and multidimensional arrays: Multidimensional.
+                                                              (line  16)
+* substitute in string:                  String Functions.    (line  89)
+* substr:                                String Functions.    (line 479)
+* substring:                             String Functions.    (line 479)
 * Sumner, Andrew:                        Other Versions.      (line  64)
+* supplementary groups of gawk process:  Auto-set.            (line 237)
 * switch statement:                      Switch Statement.    (line   6)
-* SYMTAB array:                          Auto-set.            (line 283)
+* SYMTAB array:                          Auto-set.            (line 269)
 * syntactic ambiguity: /= operator vs. /=.../ regexp constant: Assignment Ops.
-                                                              (line 147)
-* system() function:                     I/O Functions.       (line  72)
-* systime() function (gawk):             Time Functions.      (line  65)
+                                                              (line 148)
+* system:                                I/O Functions.       (line  75)
+* systime:                               Time Functions.      (line  66)
 * t debugger command (alias for tbreak): Breakpoint Control.  (line  90)
 * tbreak debugger command:               Breakpoint Control.  (line  90)
 * Tcl:                                   Library Names.       (line  57)
@@ -31951,17 +33701,17 @@ Index
 * TCP/IP, support for:                   Special Network.     (line   6)
 * tee utility:                           Tee Program.         (line   6)
 * tee.awk program:                       Tee Program.         (line  26)
-* terminating records:                   Records.             (line 117)
+* temporary breakpoint:                  Breakpoint Control.  (line  90)
+* terminating records:                   awk split records.   (line 124)
 * testbits.awk program:                  Bitwise Functions.   (line  70)
 * testext extension:                     Extension Sample API Tests.
                                                               (line   6)
-* Texinfo <1>:                           Adding Code.         (line  99)
+* Texinfo <1>:                           Adding Code.         (line 100)
 * Texinfo <2>:                           Distribution contents.
                                                               (line  77)
 * Texinfo <3>:                           Extract Program.     (line  12)
 * Texinfo <4>:                           Dupword Program.     (line  17)
 * Texinfo <5>:                           Library Functions.   (line  33)
-* Texinfo <6>:                           Sample Data Files.   (line  66)
 * Texinfo:                               Conventions.         (line   6)
 * Texinfo, chapter beginnings in files:  Regexp Operators.    (line  22)
 * Texinfo, extracting programs from source files: Extract Program.
@@ -31969,10 +33719,10 @@ Index
 * text, printing:                        Print.               (line  22)
 * text, printing, unduplicated lines of: Uniq Program.        (line   6)
 * TEXTDOMAIN variable <1>:               Programmer i18n.     (line   9)
-* TEXTDOMAIN variable:                   User-modified.       (line 162)
+* TEXTDOMAIN variable:                   User-modified.       (line 152)
 * TEXTDOMAIN variable, BEGIN pattern and: Programmer i18n.    (line  60)
 * TEXTDOMAIN variable, portability and:  I18N Portability.    (line  20)
-* textdomain() function (C library):     Explaining gettext.  (line  27)
+* textdomain() function (C library):     Explaining gettext.  (line  28)
 * tilde (~), ~ operator <1>:             Expression Patterns. (line  24)
 * tilde (~), ~ operator <2>:             Precedence.          (line  80)
 * tilde (~), ~ operator <3>:             Comparison Operators.
@@ -31981,103 +33731,111 @@ Index
 * tilde (~), ~ operator <5>:             Computed Regexps.    (line   6)
 * tilde (~), ~ operator <6>:             Case-sensitivity.    (line  26)
 * tilde (~), ~ operator:                 Regexp Usage.        (line  19)
-* time, alarm clock example program:     Alarm Program.       (line   9)
-* time, localization and:                Explaining gettext.  (line 115)
+* time functions:                        Time Functions.      (line   6)
+* time, alarm clock example program:     Alarm Program.       (line  11)
+* time, localization and:                Explaining gettext.  (line 116)
 * time, managing:                        Getlocaltime Function.
                                                               (line   6)
 * time, retrieving:                      Time Functions.      (line  17)
 * timeout, reading input:                Read Timeout.        (line   6)
 * timestamps:                            Time Functions.      (line   6)
-* timestamps, converting dates to:       Time Functions.      (line  75)
+* timestamps, converting dates to:       Time Functions.      (line  76)
 * timestamps, formatted:                 Getlocaltime Function.
                                                               (line   6)
-* tolower() function:                    String Functions.    (line 520)
-* toupper() function:                    String Functions.    (line 526)
+* tolower:                               String Functions.    (line 521)
+* toupper:                               String Functions.    (line 527)
 * tr utility:                            Translate Program.   (line   6)
 * trace debugger command:                Miscellaneous Debugger Commands.
                                                               (line 108)
+* traceback, display in debugger:        Execution Stack.     (line  13)
+* translate string:                      I18N Functions.      (line  22)
 * translate.awk program:                 Translate Program.   (line  55)
-* troubleshooting, --non-decimal-data option: Options.        (line 207)
+* treating files, as single records:     gawk split records.  (line  92)
+* troubleshooting, --non-decimal-data option: Options.        (line 211)
 * troubleshooting, == operator:          Comparison Operators.
                                                               (line  37)
-* troubleshooting, awk uses FS not IFS:  Field Separators.    (line  29)
+* troubleshooting, awk uses FS not IFS:  Field Separators.    (line  30)
 * troubleshooting, backslash before nonspecial character: Escape Sequences.
                                                               (line 112)
 * troubleshooting, division:             Arithmetic Ops.      (line  44)
 * troubleshooting, fatal errors, field widths, specifying: Constant Size.
-                                                              (line  22)
+                                                              (line  23)
 * troubleshooting, fatal errors, printf format strings: Format Modifiers.
                                                               (line 159)
-* troubleshooting, fflush() function:    I/O Functions.       (line  60)
-* troubleshooting, function call syntax: Function Calls.      (line  28)
+* troubleshooting, fflush() function:    I/O Functions.       (line  63)
+* troubleshooting, function call syntax: Function Calls.      (line  30)
 * troubleshooting, gawk:                 Compatibility Mode.  (line   6)
 * troubleshooting, gawk, bug reports:    Bugs.                (line   9)
 * troubleshooting, gawk, fatal errors, function arguments: Calling Built-in.
                                                               (line  16)
 * troubleshooting, getline function:     File Checking.       (line  25)
-* troubleshooting, gsub()/sub() functions: String Functions.  (line 469)
-* troubleshooting, match() function:     String Functions.    (line 285)
-* troubleshooting, patsplit() function:  String Functions.    (line 308)
+* troubleshooting, gsub()/sub() functions: String Functions.  (line 470)
+* troubleshooting, match() function:     String Functions.    (line 289)
 * troubleshooting, print statement, omitting commas: Print Examples.
                                                               (line  31)
 * troubleshooting, printing:             Redirection.         (line 118)
 * troubleshooting, quotes with file names: Special FD.        (line  68)
 * troubleshooting, readable data files:  File Checking.       (line   6)
 * troubleshooting, regexp constants vs. string constants: Computed Regexps.
-                                                              (line  38)
+                                                              (line  39)
 * troubleshooting, string concatenation: Concatenation.       (line  26)
-* troubleshooting, substr() function:    String Functions.    (line 496)
-* troubleshooting, system() function:    I/O Functions.       (line  94)
+* troubleshooting, substr() function:    String Functions.    (line 497)
+* troubleshooting, system() function:    I/O Functions.       (line  97)
 * troubleshooting, typographical errors, global variables: Options.
-                                                              (line 112)
+                                                              (line  98)
 * true, logical:                         Truth Values.        (line   6)
 * Trueman, David <1>:                    Contributors.        (line  30)
 * Trueman, David <2>:                    Acknowledgments.     (line  47)
 * Trueman, David:                        History.             (line  30)
 * trunc-mod operation:                   Arithmetic Ops.      (line  66)
 * truth values:                          Truth Values.        (line   6)
-* type conversion:                       Conversion.          (line  21)
+* type conversion:                       Strings And Numbers. (line  21)
 * u debugger command (alias for until):  Debugger Execution Control.
                                                               (line  83)
+* unassigned array elements:             Reference to Elements.
+                                                              (line  18)
 * undefined functions:                   Pass By Value/Reference.
                                                               (line  71)
-* underscore (_), C macro:               Explaining gettext.  (line  70)
+* underscore (_), C macro:               Explaining gettext.  (line  71)
 * underscore (_), in names of private variables: Library Names.
                                                               (line  29)
 * underscore (_), translatable string:   Programmer i18n.     (line  69)
 * undisplay debugger command:            Viewing And Changing Data.
                                                               (line  80)
 * undocumented features:                 Undocumented.        (line   6)
-* Unicode:                               Glossary.            (line 141)
+* Unicode <1>:                           Glossary.            (line 133)
+* Unicode <2>:                           Ranges and Locales.  (line  61)
+* Unicode:                               Ordinal Functions.   (line  45)
 * uninitialized variables, as array subscripts: Uninitialized Subscripts.
                                                               (line   6)
 * uniq utility:                          Uniq Program.        (line   6)
 * uniq.awk program:                      Uniq Program.        (line  65)
-* Unix:                                  Glossary.            (line 624)
+* Unix:                                  Glossary.            (line 611)
 * Unix awk, backslashes in escape sequences: Escape Sequences.
                                                               (line 124)
 * Unix awk, close() function and:        Close Files And Pipes.
-                                                              (line 130)
+                                                              (line 131)
 * Unix awk, password files, field separators and: Command Line Field Separator.
-                                                              (line  72)
+                                                              (line  64)
 * Unix, awk scripts and:                 Executable Scripts.  (line   6)
-* UNIXROOT variable, on OS/2 systems:    PC Using.            (line  17)
-* unsigned integers:                     General Arithmetic.  (line  15)
+* UNIXROOT variable, on OS/2 systems:    PC Using.            (line  16)
+* unsigned integers:                     Computer Arithmetic. (line  41)
 * until debugger command:                Debugger Execution Control.
                                                               (line  83)
 * unwatch debugger command:              Viewing And Changing Data.
                                                               (line  84)
-* up debugger command:                   Execution Stack.     (line  33)
+* up debugger command:                   Execution Stack.     (line  34)
 * user database, reading:                Passwd Functions.    (line   6)
-* user-defined, functions:               User-defined.        (line   6)
-* user-defined, functions, counts:       Profiling.           (line 129)
+* user-defined functions:                User-defined.        (line   6)
+* user-defined, functions, counts, in a profile: Profiling.   (line 137)
 * user-defined, variables:               Variables.           (line   6)
 * user-modifiable variables:             User-modified.       (line   6)
 * users, information about, printing:    Id Program.          (line   6)
 * users, information about, retrieving:  Passwd Functions.    (line  16)
-* USR1 signal:                           Profiling.           (line 181)
+* USR1 signal, for dynamic profiling:    Profiling.           (line 188)
 * values, numeric:                       Basic Data Typing.   (line  13)
 * values, string:                        Basic Data Typing.   (line  13)
+* variable assignments and input files:  Other Arguments.     (line  19)
 * variable typing:                       Typing and Comparison.
                                                               (line   9)
 * variables <1>:                         Basic Data Typing.   (line   6)
@@ -32085,7 +33843,7 @@ Index
 * variables, assigning on command line:  Assignment Options.  (line   6)
 * variables, built-in <1>:               Built-in Variables.  (line   6)
 * variables, built-in:                   Using Variables.     (line  20)
-* variables, built-in, -v option, setting with: Options.      (line  54)
+* variables, built-in, -v option, setting with: Options.      (line  40)
 * variables, built-in, conveying information: Auto-set.       (line   6)
 * variables, flag:                       Boolean Ops.         (line  67)
 * variables, getline command into, using <1>: Getline/Variable/Coprocess.
@@ -32096,20 +33854,24 @@ Index
                                                               (line   6)
 * variables, getline command into, using: Getline/Variable.   (line   6)
 * variables, global, for library functions: Library Names.    (line  11)
-* variables, global, printing list of:   Options.             (line 107)
+* variables, global, printing list of:   Options.             (line  93)
 * variables, initializing:               Using Variables.     (line  20)
-* variables, local:                      Variable Scope.      (line   6)
+* variables, local to a function:        Variable Scope.      (line   6)
 * variables, names of:                   Arrays.              (line  18)
 * variables, private:                    Library Names.       (line  11)
-* variables, setting:                    Options.             (line  46)
-* variables, shadowing:                  Definition Syntax.   (line  61)
+* variables, setting:                    Options.             (line  32)
+* variables, shadowing:                  Definition Syntax.   (line  67)
 * variables, types of:                   Assignment Ops.      (line  40)
 * variables, types of, comparison expressions and: Typing and Comparison.
                                                               (line   9)
 * variables, uninitialized, as array subscripts: Uninitialized Subscripts.
                                                               (line   6)
 * variables, user-defined:               Variables.           (line   6)
-* vertical bar (|):                      Regexp Operators.    (line  69)
+* version of gawk:                       Auto-set.            (line 207)
+* version of gawk extension API:         Auto-set.            (line 232)
+* version of GNU MP library:             Auto-set.            (line 218)
+* version of GNU MPFR library:           Auto-set.            (line 214)
+* vertical bar (|):                      Regexp Operators.    (line  70)
 * vertical bar (|), | operator (I/O) <1>: Precedence.         (line  65)
 * vertical bar (|), | operator (I/O):    Getline/Pipe.        (line   9)
 * vertical bar (|), |& operator (I/O) <1>: Two-way I/O.       (line  44)
@@ -32120,28 +33882,29 @@ Index
 * Vinschen, Corinna:                     Acknowledgments.     (line  60)
 * w debugger command (alias for watch):  Viewing And Changing Data.
                                                               (line  67)
-* w utility:                             Constant Size.       (line  22)
-* wait extension function:               Extension Sample Fork.
+* w utility:                             Constant Size.       (line  23)
+* wait() extension function:             Extension Sample Fork.
                                                               (line  22)
-* waitpid extension function:            Extension Sample Fork.
+* waitpid() extension function:          Extension Sample Fork.
                                                               (line  18)
 * walk_array() user-defined function:    Walking Arrays.      (line  14)
 * Wall, Larry <1>:                       Future Extensions.   (line   6)
 * Wall, Larry:                           Array Intro.         (line   6)
-* Wallin, Anders:                        Acknowledgments.     (line  60)
-* warnings, issuing:                     Options.             (line 182)
+* Wallin, Anders:                        Contributors.        (line 103)
+* warnings, issuing:                     Options.             (line 185)
 * watch debugger command:                Viewing And Changing Data.
                                                               (line  67)
+* watchpoint:                            Debugging Terms.     (line  42)
 * wc utility:                            Wc Program.          (line   6)
 * wc.awk program:                        Wc Program.          (line  46)
 * Weinberger, Peter <1>:                 Contributors.        (line  11)
 * Weinberger, Peter:                     History.             (line  17)
-* while statement <1>:                   While Statement.     (line   6)
-* while statement:                       Regexp Usage.        (line  19)
+* while statement:                       While Statement.     (line   6)
+* while statement, use of regexps in:    Regexp Usage.        (line  19)
 * whitespace, as field separators:       Default Field Splitting.
                                                               (line   6)
 * whitespace, functions, calling:        Calling Built-in.    (line  10)
-* whitespace, newlines as:               Options.             (line 253)
+* whitespace, newlines as:               Options.             (line 260)
 * Williams, Kent:                        Contributors.        (line  34)
 * Woehlke, Matthew:                      Contributors.        (line  79)
 * Woods, John:                           Contributors.        (line  27)
@@ -32155,22 +33918,21 @@ Index
 * words, counting:                       Wc Program.          (line   6)
 * words, duplicate, searching for:       Dupword Program.     (line   6)
 * words, usage counts, generating:       Word Sorting.        (line   6)
-* writea extension function:             Extension Sample Read write array.
+* writea() extension function:           Extension Sample Read write array.
                                                               (line   9)
 * xgettext utility:                      String Extraction.   (line  13)
+* xor:                                   Bitwise Functions.   (line  55)
 * XOR bitwise operation:                 Bitwise Functions.   (line   6)
-* xor() function (gawk):                 Bitwise Functions.   (line  55)
-* Yawitz, Efraim:                        Contributors.        (line 124)
-* Zaretskii, Eli <1>:                    Bugs.                (line  70)
+* Yawitz, Efraim:                        Contributors.        (line 131)
+* Zaretskii, Eli <1>:                    Bugs.                (line  71)
 * Zaretskii, Eli <2>:                    Contributors.        (line  55)
 * Zaretskii, Eli:                        Acknowledgments.     (line  60)
-* zero, negative vs. positive:           Unexpected Results.  (line  34)
 * zerofile.awk program:                  Empty Files.         (line  21)
 * Zoulas, Christos:                      Contributors.        (line  66)
-* {} (braces):                           Profiling.           (line 134)
+* {} (braces):                           Profiling.           (line 142)
 * {} (braces), actions and:              Action Overview.     (line  19)
 * {} (braces), statements, grouping:     Statements.          (line  10)
-* | (vertical bar):                      Regexp Operators.    (line  69)
+* | (vertical bar):                      Regexp Operators.    (line  70)
 * | (vertical bar), | operator (I/O) <1>: Precedence.         (line  65)
 * | (vertical bar), | operator (I/O) <2>: Redirection.        (line  57)
 * | (vertical bar), | operator (I/O):    Getline/Pipe.        (line   9)
@@ -32179,7 +33941,7 @@ Index
 * | (vertical bar), |& operator (I/O) <3>: Redirection.       (line 102)
 * | (vertical bar), |& operator (I/O):   Getline/Coprocess.   (line   6)
 * | (vertical bar), |& operator (I/O), pipes, closing: Close Files And Pipes.
-                                                              (line 118)
+                                                              (line 119)
 * | (vertical bar), || operator <1>:     Precedence.          (line  89)
 * | (vertical bar), || operator:         Boolean Ops.         (line  57)
 * ~ (tilde), ~ operator <1>:             Expression Patterns. (line  24)
@@ -32194,521 +33956,553 @@ Index
 
 
 Tag Table:
-Node: Top1360
-Node: Foreword40460
-Node: Preface44805
-Ref: Preface-Footnote-147858
-Ref: Preface-Footnote-247954
-Node: History48186
-Node: Names50560
-Ref: Names-Footnote-152037
-Node: This Manual52109
-Ref: This Manual-Footnote-157883
-Node: Conventions57983
-Node: Manual History60139
-Ref: Manual History-Footnote-163587
-Ref: Manual History-Footnote-263628
-Node: How To Contribute63702
-Node: Acknowledgments64846
-Node: Getting Started69055
-Node: Running gawk71434
-Node: One-shot72620
-Node: Read Terminal73845
-Ref: Read Terminal-Footnote-175495
-Ref: Read Terminal-Footnote-275771
-Node: Long75942
-Node: Executable Scripts77318
-Ref: Executable Scripts-Footnote-179151
-Ref: Executable Scripts-Footnote-279253
-Node: Comments79800
-Node: Quoting82267
-Node: DOS Quoting86890
-Node: Sample Data Files87565
-Node: Very Simple90609
-Node: Two Rules95208
-Node: More Complex97355
-Ref: More Complex-Footnote-1100285
-Node: Statements/Lines100370
-Ref: Statements/Lines-Footnote-1104832
-Node: Other Features105097
-Node: When106025
-Node: Invoking Gawk108172
-Node: Command Line109633
-Node: Options110416
-Ref: Options-Footnote-1125808
-Node: Other Arguments125833
-Node: Naming Standard Input128491
-Node: Environment Variables129585
-Node: AWKPATH Variable130143
-Ref: AWKPATH Variable-Footnote-1132901
-Node: AWKLIBPATH Variable133161
-Node: Other Environment Variables133879
-Node: Exit Status136842
-Node: Include Files137517
-Node: Loading Shared Libraries141086
-Node: Obsolete142450
-Node: Undocumented143147
-Node: Regexp143389
-Node: Regexp Usage144778
-Node: Escape Sequences146804
-Node: Regexp Operators152473
-Ref: Regexp Operators-Footnote-1159853
-Ref: Regexp Operators-Footnote-2160000
-Node: Bracket Expressions160098
-Ref: table-char-classes161988
-Node: GNU Regexp Operators164511
-Node: Case-sensitivity168234
-Ref: Case-sensitivity-Footnote-1171202
-Ref: Case-sensitivity-Footnote-2171437
-Node: Leftmost Longest171545
-Node: Computed Regexps172746
-Node: Reading Files176083
-Node: Records178085
-Ref: Records-Footnote-1186974
-Node: Fields187011
-Ref: Fields-Footnote-1190044
-Node: Nonconstant Fields190130
-Node: Changing Fields192332
-Node: Field Separators198291
-Node: Default Field Splitting200920
-Node: Regexp Field Splitting202037
-Node: Single Character Fields205379
-Node: Command Line Field Separator206438
-Node: Field Splitting Summary209879
-Ref: Field Splitting Summary-Footnote-1212990
-Node: Constant Size213091
-Node: Splitting By Content217675
-Ref: Splitting By Content-Footnote-1221401
-Node: Multiple Line221441
-Ref: Multiple Line-Footnote-1227288
-Node: Getline227467
-Node: Plain Getline229683
-Node: Getline/Variable231778
-Node: Getline/File232925
-Node: Getline/Variable/File234266
-Ref: Getline/Variable/File-Footnote-1235865
-Node: Getline/Pipe235952
-Node: Getline/Variable/Pipe238651
-Node: Getline/Coprocess239758
-Node: Getline/Variable/Coprocess241010
-Node: Getline Notes241747
-Node: Getline Summary244534
-Ref: table-getline-variants244942
-Node: Read Timeout245854
-Ref: Read Timeout-Footnote-1249595
-Node: Command line directories249652
-Node: Printing250282
-Node: Print251913
-Node: Print Examples253250
-Node: Output Separators256034
-Node: OFMT257794
-Node: Printf259152
-Node: Basic Printf260058
-Node: Control Letters261597
-Node: Format Modifiers265409
-Node: Printf Examples271418
-Node: Redirection274133
-Node: Special Files281098
-Node: Special FD281631
-Ref: Special FD-Footnote-1285256
-Node: Special Network285330
-Node: Special Caveats286180
-Node: Close Files And Pipes286976
-Ref: Close Files And Pipes-Footnote-1293959
-Ref: Close Files And Pipes-Footnote-2294107
-Node: Expressions294257
-Node: Values295389
-Node: Constants296065
-Node: Scalar Constants296745
-Ref: Scalar Constants-Footnote-1297604
-Node: Nondecimal-numbers297786
-Node: Regexp Constants300786
-Node: Using Constant Regexps301261
-Node: Variables304316
-Node: Using Variables304971
-Node: Assignment Options306695
-Node: Conversion308567
-Ref: table-locale-affects314068
-Ref: Conversion-Footnote-1314692
-Node: All Operators314801
-Node: Arithmetic Ops315431
-Node: Concatenation317936
-Ref: Concatenation-Footnote-1320728
-Node: Assignment Ops320848
-Ref: table-assign-ops325836
-Node: Increment Ops327167
-Node: Truth Values and Conditions330601
-Node: Truth Values331684
-Node: Typing and Comparison332733
-Node: Variable Typing333526
-Ref: Variable Typing-Footnote-1337423
-Node: Comparison Operators337545
-Ref: table-relational-ops337955
-Node: POSIX String Comparison341504
-Ref: POSIX String Comparison-Footnote-1342460
-Node: Boolean Ops342598
-Ref: Boolean Ops-Footnote-1346676
-Node: Conditional Exp346767
-Node: Function Calls348499
-Node: Precedence352093
-Node: Locales355762
-Node: Patterns and Actions356851
-Node: Pattern Overview357905
-Node: Regexp Patterns359574
-Node: Expression Patterns360117
-Node: Ranges363802
-Node: BEGIN/END366768
-Node: Using BEGIN/END367530
-Ref: Using BEGIN/END-Footnote-1370261
-Node: I/O And BEGIN/END370367
-Node: BEGINFILE/ENDFILE372649
-Node: Empty375563
-Node: Using Shell Variables375879
-Node: Action Overview378164
-Node: Statements380521
-Node: If Statement382375
-Node: While Statement383874
-Node: Do Statement385918
-Node: For Statement387074
-Node: Switch Statement390226
-Node: Break Statement392323
-Node: Continue Statement394313
-Node: Next Statement396106
-Node: Nextfile Statement398496
-Node: Exit Statement401139
-Node: Built-in Variables403555
-Node: User-modified404650
-Ref: User-modified-Footnote-1413008
-Node: Auto-set413070
-Ref: Auto-set-Footnote-1426540
-Ref: Auto-set-Footnote-2426745
-Node: ARGC and ARGV426801
-Node: Arrays430652
-Node: Array Basics432157
-Node: Array Intro432983
-Node: Reference to Elements437300
-Node: Assigning Elements439570
-Node: Array Example440061
-Node: Scanning an Array441793
-Node: Controlling Scanning444107
-Ref: Controlling Scanning-Footnote-1449194
-Node: Delete449510
-Ref: Delete-Footnote-1452275
-Node: Numeric Array Subscripts452332
-Node: Uninitialized Subscripts454515
-Node: Multidimensional456142
-Node: Multiscanning459234
-Node: Arrays of Arrays460823
-Node: Functions465463
-Node: Built-in466282
-Node: Calling Built-in467360
-Node: Numeric Functions469348
-Ref: Numeric Functions-Footnote-1473180
-Ref: Numeric Functions-Footnote-2473537
-Ref: Numeric Functions-Footnote-3473585
-Node: String Functions473854
-Ref: String Functions-Footnote-1496774
-Ref: String Functions-Footnote-2496903
-Ref: String Functions-Footnote-3497151
-Node: Gory Details497238
-Ref: table-sub-escapes498917
-Ref: table-sub-posix-92500271
-Ref: table-sub-proposed501622
-Ref: table-posix-sub502976
-Ref: table-gensub-escapes504521
-Ref: Gory Details-Footnote-1505697
-Ref: Gory Details-Footnote-2505748
-Node: I/O Functions505899
-Ref: I/O Functions-Footnote-1512884
-Node: Time Functions513031
-Ref: Time Functions-Footnote-1523964
-Ref: Time Functions-Footnote-2524032
-Ref: Time Functions-Footnote-3524190
-Ref: Time Functions-Footnote-4524301
-Ref: Time Functions-Footnote-5524413
-Ref: Time Functions-Footnote-6524640
-Node: Bitwise Functions524906
-Ref: table-bitwise-ops525468
-Ref: Bitwise Functions-Footnote-1529689
-Node: Type Functions529873
-Node: I18N Functions531024
-Node: User-defined532651
-Node: Definition Syntax533455
-Ref: Definition Syntax-Footnote-1538365
-Node: Function Example538434
-Node: Function Caveats541028
-Node: Calling A Function541449
-Node: Variable Scope542564
-Node: Pass By Value/Reference545527
-Node: Return Statement549035
-Node: Dynamic Typing552016
-Node: Indirect Calls552947
-Node: Library Functions562632
-Ref: Library Functions-Footnote-1566145
-Ref: Library Functions-Footnote-2566288
-Node: Library Names566459
-Ref: Library Names-Footnote-1569930
-Ref: Library Names-Footnote-2570150
-Node: General Functions570236
-Node: Strtonum Function571264
-Node: Assert Function574194
-Node: Round Function577520
-Node: Cliff Random Function579063
-Node: Ordinal Functions580079
-Ref: Ordinal Functions-Footnote-1583149
-Ref: Ordinal Functions-Footnote-2583401
-Node: Join Function583610
-Ref: Join Function-Footnote-1585381
-Node: Getlocaltime Function585581
-Node: Readfile Function589322
-Node: Data File Management591161
-Node: Filetrans Function591793
-Node: Rewind Function595862
-Node: File Checking597249
-Node: Empty Files598343
-Node: Ignoring Assigns600573
-Node: Getopt Function602126
-Ref: Getopt Function-Footnote-1613429
-Node: Passwd Functions613632
-Ref: Passwd Functions-Footnote-1622607
-Node: Group Functions622695
-Node: Walking Arrays630779
-Node: Sample Programs632916
-Node: Running Examples633590
-Node: Clones634318
-Node: Cut Program635542
-Node: Egrep Program645387
-Ref: Egrep Program-Footnote-1653160
-Node: Id Program653270
-Node: Split Program656886
-Ref: Split Program-Footnote-1660405
-Node: Tee Program660533
-Node: Uniq Program663336
-Node: Wc Program670765
-Ref: Wc Program-Footnote-1675031
-Ref: Wc Program-Footnote-2675231
-Node: Miscellaneous Programs675323
-Node: Dupword Program676511
-Node: Alarm Program678542
-Node: Translate Program683295
-Ref: Translate Program-Footnote-1687682
-Ref: Translate Program-Footnote-2687930
-Node: Labels Program688064
-Ref: Labels Program-Footnote-1691435
-Node: Word Sorting691519
-Node: History Sorting695403
-Node: Extract Program697242
-Ref: Extract Program-Footnote-1704745
-Node: Simple Sed704873
-Node: Igawk Program707935
-Ref: Igawk Program-Footnote-1723092
-Ref: Igawk Program-Footnote-2723293
-Node: Anagram Program723431
-Node: Signature Program726499
-Node: Advanced Features727599
-Node: Nondecimal Data729485
-Node: Array Sorting731068
-Node: Controlling Array Traversal731765
-Node: Array Sorting Functions740049
-Ref: Array Sorting Functions-Footnote-1743918
-Node: Two-way I/O744112
-Ref: Two-way I/O-Footnote-1749544
-Node: TCP/IP Networking749614
-Node: Profiling752458
-Node: Internationalization759955
-Node: I18N and L10N761380
-Node: Explaining gettext762066
-Ref: Explaining gettext-Footnote-1767134
-Ref: Explaining gettext-Footnote-2767318
-Node: Programmer i18n767483
-Node: Translator i18n771685
-Node: String Extraction772478
-Ref: String Extraction-Footnote-1773439
-Node: Printf Ordering773525
-Ref: Printf Ordering-Footnote-1776309
-Node: I18N Portability776373
-Ref: I18N Portability-Footnote-1778822
-Node: I18N Example778885
-Ref: I18N Example-Footnote-1781523
-Node: Gawk I18N781595
-Node: Debugger782216
-Node: Debugging783187
-Node: Debugging Concepts783620
-Node: Debugging Terms785476
-Node: Awk Debugging788073
-Node: Sample Debugging Session788965
-Node: Debugger Invocation789485
-Node: Finding The Bug790817
-Node: List of Debugger Commands797305
-Node: Breakpoint Control798639
-Node: Debugger Execution Control802303
-Node: Viewing And Changing Data805663
-Node: Execution Stack809019
-Node: Debugger Info810486
-Node: Miscellaneous Debugger Commands814468
-Node: Readline Support819644
-Node: Limitations820475
-Node: Arbitrary Precision Arithmetic822727
-Ref: Arbitrary Precision Arithmetic-Footnote-1824376
-Node: General Arithmetic824524
-Node: Floating Point Issues826244
-Node: String Conversion Precision827125
-Ref: String Conversion Precision-Footnote-1828830
-Node: Unexpected Results828939
-Node: POSIX Floating Point Problems831092
-Ref: POSIX Floating Point Problems-Footnote-1834917
-Node: Integer Programming834955
-Node: Floating-point Programming836694
-Ref: Floating-point Programming-Footnote-1843025
-Ref: Floating-point Programming-Footnote-2843295
-Node: Floating-point Representation843559
-Node: Floating-point Context844724
-Ref: table-ieee-formats845563
-Node: Rounding Mode846947
-Ref: table-rounding-modes847426
-Ref: Rounding Mode-Footnote-1850441
-Node: Gawk and MPFR850620
-Node: Arbitrary Precision Floats851875
-Ref: Arbitrary Precision Floats-Footnote-1854318
-Node: Setting Precision854634
-Ref: table-predefined-precision-strings855320
-Node: Setting Rounding Mode857465
-Ref: table-gawk-rounding-modes857869
-Node: Floating-point Constants859056
-Node: Changing Precision860485
-Ref: Changing Precision-Footnote-1861882
-Node: Exact Arithmetic862056
-Node: Arbitrary Precision Integers865194
-Ref: Arbitrary Precision Integers-Footnote-1868212
-Node: Dynamic Extensions868359
-Node: Extension Intro869817
-Node: Plugin License871082
-Node: Extension Mechanism Outline871767
-Ref: load-extension872184
-Ref: load-new-function873662
-Ref: call-new-function874657
-Node: Extension API Description876672
-Node: Extension API Functions Introduction877885
-Node: General Data Types882751
-Ref: General Data Types-Footnote-1888350
-Node: Requesting Values888649
-Ref: table-value-types-returned889380
-Node: Constructor Functions890334
-Node: Registration Functions893354
-Node: Extension Functions894039
-Node: Exit Callback Functions896264
-Node: Extension Version String897513
-Node: Input Parsers898163
-Node: Output Wrappers907920
-Node: Two-way processors912430
-Node: Printing Messages914638
-Ref: Printing Messages-Footnote-1915715
-Node: Updating `ERRNO'915867
-Node: Accessing Parameters916606
-Node: Symbol Table Access917836
-Node: Symbol table by name918348
-Node: Symbol table by cookie920095
-Ref: Symbol table by cookie-Footnote-1924225
-Node: Cached values924288
-Ref: Cached values-Footnote-1927737
-Node: Array Manipulation927828
-Ref: Array Manipulation-Footnote-1928926
-Node: Array Data Types928965
-Ref: Array Data Types-Footnote-1931668
-Node: Array Functions931760
-Node: Flattening Arrays935526
-Node: Creating Arrays942378
-Node: Extension API Variables947103
-Node: Extension Versioning947739
-Node: Extension API Informational Variables949640
-Node: Extension API Boilerplate950726
-Node: Finding Extensions954530
-Node: Extension Example955090
-Node: Internal File Description955820
-Node: Internal File Ops959911
-Ref: Internal File Ops-Footnote-1971419
-Node: Using Internal File Ops971559
-Ref: Using Internal File Ops-Footnote-1973912
-Node: Extension Samples974178
-Node: Extension Sample File Functions975702
-Node: Extension Sample Fnmatch984187
-Node: Extension Sample Fork985913
-Node: Extension Sample Inplace987131
-Node: Extension Sample Ord988909
-Node: Extension Sample Readdir989745
-Node: Extension Sample Revout991277
-Node: Extension Sample Rev2way991870
-Node: Extension Sample Read write array992560
-Node: Extension Sample Readfile994443
-Node: Extension Sample API Tests995261
-Node: Extension Sample Time995786
-Node: gawkextlib997150
-Node: Language History999910
-Node: V7/SVR3.11001432
-Node: SVR41003752
-Node: POSIX1005194
-Node: BTL1006580
-Node: POSIX/GNU1007314
-Node: Common Extensions1012849
-Node: Ranges and Locales1014155
-Ref: Ranges and Locales-Footnote-11018773
-Ref: Ranges and Locales-Footnote-21018800
-Ref: Ranges and Locales-Footnote-31019060
-Node: Contributors1019281
-Node: Installation1024356
-Node: Gawk Distribution1025250
-Node: Getting1025734
-Node: Extracting1026560
-Node: Distribution contents1028252
-Node: Unix Installation1033772
-Node: Quick Installation1034389
-Node: Additional Configuration Options1036833
-Node: Configuration Philosophy1038569
-Node: Non-Unix Installation1040923
-Node: PC Installation1041381
-Node: PC Binary Installation1042680
-Node: PC Compiling1044528
-Node: PC Testing1047472
-Node: PC Using1048648
-Node: Cygwin1052833
-Node: MSYS1053833
-Node: VMS Installation1054347
-Node: VMS Compilation1054950
-Ref: VMS Compilation-Footnote-11055957
-Node: VMS Installation Details1056015
-Node: VMS Running1057650
-Node: VMS Old Gawk1059257
-Node: Bugs1059731
-Node: Other Versions1063587
-Node: Notes1069671
-Node: Compatibility Mode1070471
-Node: Additions1071254
-Node: Accessing The Source1072181
-Node: Adding Code1073621
-Node: New Ports1079666
-Node: Derived Files1083801
-Ref: Derived Files-Footnote-11089122
-Ref: Derived Files-Footnote-21089156
-Ref: Derived Files-Footnote-31089756
-Node: Future Extensions1089854
-Node: Implementation Limitations1090431
-Node: Extension Design1091683
-Node: Old Extension Problems1092837
-Ref: Old Extension Problems-Footnote-11094345
-Node: Extension New Mechanism Goals1094402
-Ref: Extension New Mechanism Goals-Footnote-11097767
-Node: Extension Other Design Decisions1097953
-Node: Extension Future Growth1100059
-Node: Old Extension Mechanism1100895
-Node: Basic Concepts1102635
-Node: Basic High Level1103316
-Ref: figure-general-flow1103587
-Ref: figure-process-flow1104186
-Ref: Basic High Level-Footnote-11107415
-Node: Basic Data Typing1107600
-Node: Glossary1110955
-Node: Copying1136417
-Node: GNU Free Documentation License1173974
-Node: Index1199111
+Node: Top1292
+Node: Foreword42034
+Node: Preface46379
+Ref: Preface-Footnote-149526
+Ref: Preface-Footnote-249633
+Node: History49865
+Node: Names52239
+Ref: Names-Footnote-153703
+Node: This Manual53776
+Ref: This Manual-Footnote-159555
+Node: Conventions59655
+Node: Manual History61811
+Ref: Manual History-Footnote-165250
+Ref: Manual History-Footnote-265291
+Node: How To Contribute65365
+Node: Acknowledgments66604
+Node: Getting Started70900
+Node: Running gawk73334
+Node: One-shot74524
+Node: Read Terminal75749
+Ref: Read Terminal-Footnote-177399
+Ref: Read Terminal-Footnote-277675
+Node: Long77846
+Node: Executable Scripts79222
+Ref: Executable Scripts-Footnote-181055
+Ref: Executable Scripts-Footnote-281157
+Node: Comments81704
+Node: Quoting84177
+Node: DOS Quoting89493
+Node: Sample Data Files90168
+Node: Very Simple92683
+Node: Two Rules97321
+Node: More Complex99215
+Ref: More Complex-Footnote-1102147
+Node: Statements/Lines102232
+Ref: Statements/Lines-Footnote-1106688
+Node: Other Features106953
+Node: When107881
+Node: Intro Summary110051
+Node: Invoking Gawk110817
+Node: Command Line112332
+Node: Options113123
+Ref: Options-Footnote-1128952
+Node: Other Arguments128977
+Node: Naming Standard Input131639
+Node: Environment Variables132733
+Node: AWKPATH Variable133291
+Ref: AWKPATH Variable-Footnote-1136163
+Ref: AWKPATH Variable-Footnote-2136208
+Node: AWKLIBPATH Variable136468
+Node: Other Environment Variables137227
+Node: Exit Status140882
+Node: Include Files141557
+Node: Loading Shared Libraries145135
+Node: Obsolete146519
+Node: Undocumented147216
+Node: Invoking Summary147483
+Node: Regexp149063
+Node: Regexp Usage150513
+Node: Escape Sequences152546
+Node: Regexp Operators158213
+Ref: Regexp Operators-Footnote-1165693
+Ref: Regexp Operators-Footnote-2165840
+Node: Bracket Expressions165938
+Ref: table-char-classes167828
+Node: GNU Regexp Operators170351
+Node: Case-sensitivity174074
+Ref: Case-sensitivity-Footnote-1176966
+Ref: Case-sensitivity-Footnote-2177201
+Node: Leftmost Longest177309
+Node: Computed Regexps178510
+Node: Regexp Summary181882
+Node: Reading Files183353
+Node: Records185445
+Node: awk split records186188
+Node: gawk split records191046
+Ref: gawk split records-Footnote-1195567
+Node: Fields195604
+Ref: Fields-Footnote-1198568
+Node: Nonconstant Fields198654
+Ref: Nonconstant Fields-Footnote-1200884
+Node: Changing Fields201086
+Node: Field Separators207040
+Node: Default Field Splitting209742
+Node: Regexp Field Splitting210859
+Node: Single Character Fields214200
+Node: Command Line Field Separator215259
+Node: Full Line Fields218601
+Ref: Full Line Fields-Footnote-1219109
+Node: Field Splitting Summary219155
+Ref: Field Splitting Summary-Footnote-1222254
+Node: Constant Size222355
+Node: Splitting By Content226962
+Ref: Splitting By Content-Footnote-1230712
+Node: Multiple Line230752
+Ref: Multiple Line-Footnote-1236608
+Node: Getline236787
+Node: Plain Getline239003
+Node: Getline/Variable241098
+Node: Getline/File242245
+Node: Getline/Variable/File243629
+Ref: Getline/Variable/File-Footnote-1245228
+Node: Getline/Pipe245315
+Node: Getline/Variable/Pipe248014
+Node: Getline/Coprocess249121
+Node: Getline/Variable/Coprocess250373
+Node: Getline Notes251110
+Node: Getline Summary253914
+Ref: table-getline-variants254322
+Node: Read Timeout255234
+Ref: Read Timeout-Footnote-1259061
+Node: Command line directories259119
+Node: Input Summary260023
+Node: Input Exercises263160
+Node: Printing263893
+Node: Print265615
+Node: Print Examples266956
+Node: Output Separators269735
+Node: OFMT271751
+Node: Printf273109
+Node: Basic Printf274015
+Node: Control Letters275554
+Node: Format Modifiers279406
+Node: Printf Examples285433
+Node: Redirection287897
+Node: Special Files294869
+Node: Special FD295400
+Ref: Special FD-Footnote-1299024
+Node: Special Network299098
+Node: Special Caveats299948
+Node: Close Files And Pipes300744
+Ref: Close Files And Pipes-Footnote-1307905
+Ref: Close Files And Pipes-Footnote-2308053
+Node: Output Summary308203
+Node: Output exercises309200
+Node: Expressions309880
+Node: Values311065
+Node: Constants311741
+Node: Scalar Constants312421
+Ref: Scalar Constants-Footnote-1313280
+Node: Nondecimal-numbers313530
+Node: Regexp Constants316530
+Node: Using Constant Regexps317005
+Node: Variables320075
+Node: Using Variables320730
+Node: Assignment Options322454
+Node: Conversion324329
+Node: Strings And Numbers324853
+Ref: Strings And Numbers-Footnote-1327915
+Node: Locale influences conversions328024
+Ref: table-locale-affects330741
+Node: All Operators331329
+Node: Arithmetic Ops331959
+Node: Concatenation334464
+Ref: Concatenation-Footnote-1337260
+Node: Assignment Ops337380
+Ref: table-assign-ops342363
+Node: Increment Ops343680
+Node: Truth Values and Conditions347118
+Node: Truth Values348201
+Node: Typing and Comparison349250
+Node: Variable Typing350043
+Ref: Variable Typing-Footnote-1353943
+Node: Comparison Operators354065
+Ref: table-relational-ops354475
+Node: POSIX String Comparison358025
+Ref: POSIX String Comparison-Footnote-1359109
+Node: Boolean Ops359247
+Ref: Boolean Ops-Footnote-1363317
+Node: Conditional Exp363408
+Node: Function Calls365135
+Node: Precedence369015
+Node: Locales372684
+Node: Expressions Summary374315
+Node: Patterns and Actions376856
+Node: Pattern Overview377972
+Node: Regexp Patterns379649
+Node: Expression Patterns380192
+Node: Ranges383973
+Node: BEGIN/END387079
+Node: Using BEGIN/END387841
+Ref: Using BEGIN/END-Footnote-1390577
+Node: I/O And BEGIN/END390683
+Node: BEGINFILE/ENDFILE392968
+Node: Empty395899
+Node: Using Shell Variables396216
+Node: Action Overview398499
+Node: Statements400826
+Node: If Statement402674
+Node: While Statement404172
+Node: Do Statement406216
+Node: For Statement407372
+Node: Switch Statement410524
+Node: Break Statement412627
+Node: Continue Statement414682
+Node: Next Statement416475
+Node: Nextfile Statement418865
+Node: Exit Statement421520
+Node: Built-in Variables423924
+Node: User-modified425051
+Ref: User-modified-Footnote-1432740
+Node: Auto-set432802
+Ref: Auto-set-Footnote-1445721
+Ref: Auto-set-Footnote-2445926
+Node: ARGC and ARGV445982
+Node: Pattern Action Summary449836
+Node: Arrays452059
+Node: Array Basics453608
+Node: Array Intro454434
+Ref: figure-array-elements456407
+Node: Reference to Elements458814
+Node: Assigning Elements461087
+Node: Array Example461578
+Node: Scanning an Array463310
+Node: Controlling Scanning466325
+Ref: Controlling Scanning-Footnote-1471498
+Node: Delete471814
+Ref: Delete-Footnote-1474579
+Node: Numeric Array Subscripts474636
+Node: Uninitialized Subscripts476819
+Node: Multidimensional478444
+Node: Multiscanning481537
+Node: Arrays of Arrays483126
+Node: Arrays Summary487789
+Node: Functions489894
+Node: Built-in490767
+Node: Calling Built-in491845
+Node: Numeric Functions493833
+Ref: Numeric Functions-Footnote-1497667
+Ref: Numeric Functions-Footnote-2498024
+Ref: Numeric Functions-Footnote-3498072
+Node: String Functions498341
+Ref: String Functions-Footnote-1521352
+Ref: String Functions-Footnote-2521481
+Ref: String Functions-Footnote-3521729
+Node: Gory Details521816
+Ref: table-sub-escapes523485
+Ref: table-sub-posix-92524839
+Ref: table-sub-proposed526190
+Ref: table-posix-sub527544
+Ref: table-gensub-escapes529089
+Ref: Gory Details-Footnote-1530265
+Ref: Gory Details-Footnote-2530316
+Node: I/O Functions530467
+Ref: I/O Functions-Footnote-1537590
+Node: Time Functions537737
+Ref: Time Functions-Footnote-1548201
+Ref: Time Functions-Footnote-2548269
+Ref: Time Functions-Footnote-3548427
+Ref: Time Functions-Footnote-4548538
+Ref: Time Functions-Footnote-5548650
+Ref: Time Functions-Footnote-6548877
+Node: Bitwise Functions549143
+Ref: table-bitwise-ops549705
+Ref: Bitwise Functions-Footnote-1553950
+Node: Type Functions554134
+Node: I18N Functions555276
+Node: User-defined556921
+Node: Definition Syntax557725
+Ref: Definition Syntax-Footnote-1562904
+Node: Function Example562973
+Ref: Function Example-Footnote-1565617
+Node: Function Caveats565639
+Node: Calling A Function566157
+Node: Variable Scope567112
+Node: Pass By Value/Reference570100
+Node: Return Statement573608
+Node: Dynamic Typing576592
+Node: Indirect Calls577521
+Node: Functions Summary587234
+Node: Library Functions589773
+Ref: Library Functions-Footnote-1593391
+Ref: Library Functions-Footnote-2593534
+Node: Library Names593705
+Ref: Library Names-Footnote-1597178
+Ref: Library Names-Footnote-2597398
+Node: General Functions597484
+Node: Strtonum Function598512
+Node: Assert Function601292
+Node: Round Function604618
+Node: Cliff Random Function606159
+Node: Ordinal Functions607175
+Ref: Ordinal Functions-Footnote-1610252
+Ref: Ordinal Functions-Footnote-2610504
+Node: Join Function610715
+Ref: Join Function-Footnote-1612486
+Node: Getlocaltime Function612686
+Node: Readfile Function616422
+Node: Data File Management618261
+Node: Filetrans Function618893
+Node: Rewind Function622962
+Node: File Checking624349
+Ref: File Checking-Footnote-1625481
+Node: Empty Files625682
+Node: Ignoring Assigns627661
+Node: Getopt Function629215
+Ref: Getopt Function-Footnote-1640518
+Node: Passwd Functions640721
+Ref: Passwd Functions-Footnote-1649700
+Node: Group Functions649788
+Ref: Group Functions-Footnote-1657729
+Node: Walking Arrays657942
+Node: Library Functions Summary659545
+Node: Library exercises660933
+Node: Sample Programs662213
+Node: Running Examples662983
+Node: Clones663711
+Node: Cut Program664935
+Node: Egrep Program674803
+Ref: Egrep Program-Footnote-1682774
+Node: Id Program682884
+Node: Split Program686548
+Ref: Split Program-Footnote-1690086
+Node: Tee Program690214
+Node: Uniq Program693021
+Node: Wc Program700451
+Ref: Wc Program-Footnote-1704716
+Node: Miscellaneous Programs704808
+Node: Dupword Program706021
+Node: Alarm Program708052
+Node: Translate Program712866
+Ref: Translate Program-Footnote-1717257
+Ref: Translate Program-Footnote-2717527
+Node: Labels Program717661
+Ref: Labels Program-Footnote-1721032
+Node: Word Sorting721116
+Node: History Sorting725159
+Node: Extract Program726995
+Node: Simple Sed734531
+Node: Igawk Program737593
+Ref: Igawk Program-Footnote-1751904
+Ref: Igawk Program-Footnote-2752105
+Node: Anagram Program752243
+Node: Signature Program755311
+Node: Programs Summary756558
+Node: Programs Exercises757773
+Node: Advanced Features761424
+Node: Nondecimal Data763372
+Node: Array Sorting764949
+Node: Controlling Array Traversal765646
+Node: Array Sorting Functions773926
+Ref: Array Sorting Functions-Footnote-1777833
+Node: Two-way I/O778027
+Ref: Two-way I/O-Footnote-1783543
+Node: TCP/IP Networking783625
+Node: Profiling786469
+Node: Advanced Features Summary794011
+Node: Internationalization795875
+Node: I18N and L10N797355
+Node: Explaining gettext798041
+Ref: Explaining gettext-Footnote-1803181
+Ref: Explaining gettext-Footnote-2803365
+Node: Programmer i18n803530
+Node: Translator i18n807755
+Node: String Extraction808549
+Ref: String Extraction-Footnote-1809510
+Node: Printf Ordering809596
+Ref: Printf Ordering-Footnote-1812378
+Node: I18N Portability812442
+Ref: I18N Portability-Footnote-1814891
+Node: I18N Example814954
+Ref: I18N Example-Footnote-1817676
+Node: Gawk I18N817748
+Node: I18N Summary818386
+Node: Debugger819725
+Node: Debugging820747
+Node: Debugging Concepts821188
+Node: Debugging Terms823044
+Node: Awk Debugging825641
+Node: Sample Debugging Session826533
+Node: Debugger Invocation827053
+Node: Finding The Bug828386
+Node: List of Debugger Commands834868
+Node: Breakpoint Control836200
+Node: Debugger Execution Control839864
+Node: Viewing And Changing Data843224
+Node: Execution Stack846582
+Node: Debugger Info848095
+Node: Miscellaneous Debugger Commands852089
+Node: Readline Support857273
+Node: Limitations858165
+Node: Debugging Summary860439
+Node: Arbitrary Precision Arithmetic861603
+Node: Computer Arithmetic862932
+Ref: Computer Arithmetic-Footnote-1867319
+Node: Math Definitions867376
+Ref: table-ieee-formats870260
+Node: MPFR features870764
+Node: FP Math Caution872406
+Ref: FP Math Caution-Footnote-1873447
+Node: Inexactness of computations873816
+Node: Inexact representation874764
+Node: Comparing FP Values876119
+Node: Errors accumulate877083
+Node: Getting Accuracy878516
+Node: Try To Round881175
+Node: Setting precision882074
+Ref: table-predefined-precision-strings882756
+Node: Setting the rounding mode884549
+Ref: table-gawk-rounding-modes884913
+Ref: Setting the rounding mode-Footnote-1888367
+Node: Arbitrary Precision Integers888546
+Ref: Arbitrary Precision Integers-Footnote-1891549
+Node: POSIX Floating Point Problems891698
+Ref: POSIX Floating Point Problems-Footnote-1895574
+Node: Floating point summary895612
+Node: Dynamic Extensions897829
+Node: Extension Intro899381
+Node: Plugin License900646
+Node: Extension Mechanism Outline901331
+Ref: figure-load-extension901755
+Ref: figure-load-new-function903240
+Ref: figure-call-new-function904242
+Node: Extension API Description906226
+Node: Extension API Functions Introduction907676
+Node: General Data Types912541
+Ref: General Data Types-Footnote-1918234
+Node: Requesting Values918533
+Ref: table-value-types-returned919270
+Node: Memory Allocation Functions920228
+Ref: Memory Allocation Functions-Footnote-1922975
+Node: Constructor Functions923071
+Node: Registration Functions924829
+Node: Extension Functions925514
+Node: Exit Callback Functions927816
+Node: Extension Version String929065
+Node: Input Parsers929715
+Node: Output Wrappers939518
+Node: Two-way processors944034
+Node: Printing Messages946238
+Ref: Printing Messages-Footnote-1947315
+Node: Updating `ERRNO'947467
+Node: Accessing Parameters948206
+Node: Symbol Table Access949436
+Node: Symbol table by name949950
+Node: Symbol table by cookie951926
+Ref: Symbol table by cookie-Footnote-1956059
+Node: Cached values956122
+Ref: Cached values-Footnote-1959626
+Node: Array Manipulation959717
+Ref: Array Manipulation-Footnote-1960815
+Node: Array Data Types960854
+Ref: Array Data Types-Footnote-1963557
+Node: Array Functions963649
+Node: Flattening Arrays967523
+Node: Creating Arrays974375
+Node: Extension API Variables979106
+Node: Extension Versioning979742
+Node: Extension API Informational Variables981643
+Node: Extension API Boilerplate982729
+Node: Finding Extensions986533
+Node: Extension Example987093
+Node: Internal File Description987823
+Node: Internal File Ops991914
+Ref: Internal File Ops-Footnote-11003346
+Node: Using Internal File Ops1003486
+Ref: Using Internal File Ops-Footnote-11005833
+Node: Extension Samples1006101
+Node: Extension Sample File Functions1007625
+Node: Extension Sample Fnmatch1015193
+Node: Extension Sample Fork1016675
+Node: Extension Sample Inplace1017888
+Node: Extension Sample Ord1019563
+Node: Extension Sample Readdir1020399
+Ref: table-readdir-file-types1021255
+Node: Extension Sample Revout1022054
+Node: Extension Sample Rev2way1022645
+Node: Extension Sample Read write array1023386
+Node: Extension Sample Readfile1025265
+Node: Extension Sample API Tests1026365
+Node: Extension Sample Time1026890
+Node: gawkextlib1028205
+Node: Extension summary1031018
+Node: Extension Exercises1034711
+Node: Language History1035433
+Node: V7/SVR3.11037076
+Node: SVR41039396
+Node: POSIX1040838
+Node: BTL1042224
+Node: POSIX/GNU1042958
+Node: Feature History1048557
+Node: Common Extensions1061687
+Node: Ranges and Locales1062999
+Ref: Ranges and Locales-Footnote-11067616
+Ref: Ranges and Locales-Footnote-21067643
+Ref: Ranges and Locales-Footnote-31067877
+Node: Contributors1068098
+Node: History summary1073523
+Node: Installation1074892
+Node: Gawk Distribution1075843
+Node: Getting1076327
+Node: Extracting1077151
+Node: Distribution contents1078793
+Node: Unix Installation1084510
+Node: Quick Installation1085127
+Node: Additional Configuration Options1087569
+Node: Configuration Philosophy1089307
+Node: Non-Unix Installation1091658
+Node: PC Installation1092116
+Node: PC Binary Installation1093427
+Node: PC Compiling1095275
+Ref: PC Compiling-Footnote-11098274
+Node: PC Testing1098379
+Node: PC Using1099555
+Node: Cygwin1103713
+Node: MSYS1104522
+Node: VMS Installation1105036
+Node: VMS Compilation1105832
+Ref: VMS Compilation-Footnote-11107054
+Node: VMS Dynamic Extensions1107112
+Node: VMS Installation Details1108485
+Node: VMS Running1110737
+Node: VMS GNV1113571
+Node: VMS Old Gawk1114294
+Node: Bugs1114764
+Node: Other Versions1118768
+Node: Installation summary1125023
+Node: Notes1126079
+Node: Compatibility Mode1126944
+Node: Additions1127726
+Node: Accessing The Source1128651
+Node: Adding Code1130087
+Node: New Ports1136265
+Node: Derived Files1140746
+Ref: Derived Files-Footnote-11145827
+Ref: Derived Files-Footnote-21145861
+Ref: Derived Files-Footnote-31146457
+Node: Future Extensions1146571
+Node: Implementation Limitations1147177
+Node: Extension Design1148425
+Node: Old Extension Problems1149579
+Ref: Old Extension Problems-Footnote-11151096
+Node: Extension New Mechanism Goals1151153
+Ref: Extension New Mechanism Goals-Footnote-11154513
+Node: Extension Other Design Decisions1154702
+Node: Extension Future Growth1156808
+Node: Old Extension Mechanism1157644
+Node: Notes summary1159406
+Node: Basic Concepts1160592
+Node: Basic High Level1161273
+Ref: figure-general-flow1161545
+Ref: figure-process-flow1162144
+Ref: Basic High Level-Footnote-11165373
+Node: Basic Data Typing1165558
+Node: Glossary1168886
+Node: Copying1194038
+Node: GNU Free Documentation License1231594
+Node: Index1256730
 
 End Tag Table
diff --git a/doc/gawk.texi b/doc/gawk.texi
index 6e5fb555..f8fc1269 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -19,6 +19,31 @@
 * awk: (gawk)Invoking gawk.                     Text scanning and processing.
 @end direntry
 
+@ifset FOR_PRINT
+@tex
+\gdef\xrefprintnodename#1{``#1''}
+@end tex
+@end ifset
+
+@ifclear FOR_PRINT
+@c With early 2014 texinfo.tex, restore PDF links and colors
+@tex
+\gdef\linkcolor{0.5 0.09 0.12} % Dark Red
+\gdef\urlcolor{0.5 0.09 0.12} % Also
+\global\urefurlonlylinktrue
+@end tex
+@end ifclear
+
+@ifnotdocbook
+@set BULLET @bullet{}
+@set MINUS @minus{}
+@end ifnotdocbook
+
+@ifdocbook
+@set BULLET
+@set MINUS
+@end ifdocbook
+
 @set xref-automatic-section-title
 
 @c The following information should be updated here only!
@@ -26,11 +51,9 @@
 @c applies to and all the info about who's publishing this edition
 
 @c These apply across the board.
-@set UPDATE-MONTH May, 2013
+@set UPDATE-MONTH June, 2014
 @set VERSION 4.1
-@set PATCHLEVEL 0
-
-@set FSF
+@set PATCHLEVEL 1
 
 @set TITLE GAWK: Effective AWK Programming
 @set SUBTITLE A User's Guide for GNU Awk
@@ -44,6 +67,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER @inmargin{@image{lflashlight,1cm}, @image{rflashlight,1cm}}
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end iftex
 @ifinfo
 @set DOCUMENT Info file
@@ -53,6 +77,7 @@
 @set SUBSECTION node
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE screen
 @end ifinfo
 @ifhtml
 @set DOCUMENT Web page
@@ -62,6 +87,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE screen
 @end ifhtml
 @ifdocbook
 @set DOCUMENT book
@@ -71,6 +97,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end ifdocbook
 @ifxml
 @set DOCUMENT book
@@ -80,6 +107,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end ifxml
 @ifplaintext
 @set DOCUMENT book
@@ -89,24 +117,69 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end ifplaintext
 
+@ifdocbook
+@c empty on purpose
+@set PART1
+@set PART2
+@set PART3
+@set PART4
+@end ifdocbook
+
+@ifnotdocbook
+@set PART1 Part I:@*
+@set PART2 Part II:@*
+@set PART3 Part III:@*
+@set PART4 Part IV:@*
+@end ifnotdocbook
+
 @c some special symbols
 @iftex
 @set LEQ @math{@leq}
 @set PI @math{@pi}
 @end iftex
+@ifdocbook
+@set LEQ @inlineraw{docbook, &le;}
+@set PI @inlineraw{docbook, &pgr;}
+@end ifdocbook
 @ifnottex
+@ifnotdocbook
 @set LEQ <=
 @set PI @i{pi}
+@end ifnotdocbook
 @end ifnottex
 
 @ifnottex
+@ifnotdocbook
 @macro ii{text}
 @i{\text\}
 @end macro
+@end ifnotdocbook
 @end ifnottex
 
+@ifdocbook
+@macro ii{text}
+@inlineraw{docbook,<lineannotation>\text\</lineannotation>}
+@end macro
+@end ifdocbook
+
+@ifclear FOR_PRINT
+@set FN file name
+@set FFN File Name
+@set DF data file
+@set DDF Data File
+@set PVERSION version
+@end ifclear
+@ifset FOR_PRINT
+@set FN filename
+@set FFN Filename
+@set DF datafile
+@set DDF Datafile
+@set PVERSION Version
+@end ifset
+
 @c For HTML, spell out email addresses, to avoid problems with
 @c address harvesters for spammers.
 @ifhtml
@@ -120,12 +193,36 @@
 @end macro
 @end ifnothtml
 
+@c Indexing macros
+@ifinfo
+
+@macro cindexawkfunc{name}
+@cindex @code{\name\}
+@end macro
+
+@macro cindexgawkfunc{name}
+@cindex @code{\name\}
+@end macro
+
+@end ifinfo
+
+@ifnotinfo
+
+@macro cindexawkfunc{name}
+@cindex @code{\name\()} function
+@end macro
+
+@macro cindexgawkfunc{name}
+@cindex @code{\name\()} function (@command{gawk})
+@end macro
+@end ifnotinfo
+
 @ignore
 Some comments on the layout for TeX.
-1. Use at least texinfo.tex 2000-09-06.09
-2. I have done A LOT of work to make this look good. There are  `@page' commands
-   and use of `@group ... @end group' in a number of places. If you muck
-   with anything, it's your responsibility not to break the layout.
+1. Use at least texinfo.tex 2014-01-30.15
+2. When using @docbook, if the last line is part of a paragraph, end
+it with a space and @c so that the lines won't run together. This is a
+quirk of the language / makeinfo, and isn't going to change.
 @end ignore
 
 @c merge the function and variable indexes into the concept index
@@ -141,6 +238,10 @@ Some comments on the layout for TeX.
 @syncodeindex fn cp
 @syncodeindex vr cp
 @end ifxml
+@ifdocbook
+@synindex fn cp
+@synindex vr cp
+@end ifdocbook
 
 @c If "finalout" is commented out, the printed output will show
 @c black boxes that mark lines that are too long.  Thus, it is
@@ -152,9 +253,30 @@ Some comments on the layout for TeX.
 @end iftex
 
 @copying
-Copyright @copyright{} 1989, 1991, 1992, 1993, 1996, 1997, 1998, 1999,
-2000, 2001, 2002, 2003, 2004, 2005, 2007, 2009, 2010, 2011, 2012, 2013
+@docbook
+<para>
+&ldquo;To boldly go where no man has gone before&rdquo; is a
+Registered Trademark of Paramount Pictures Corporation.</para>
+
+<para>Published by:</para>
+
+<literallayout class="normal">Free Software Foundation
+51 Franklin Street, Fifth Floor
+Boston, MA  02110-1301 USA
+Phone: +1-617-542-5942
+Fax: +1-617-542-2652
+Email: <email>gnu@@gnu.org</email>
+URL: <ulink url="http://www.gnu.org">http://www.gnu.org/</ulink></literallayout>
+
+<literallayout class="normal">Copyright &copy; 1989, 1991, 1992, 1993, 1996&ndash;2005, 2007, 2009&ndash;2014
 Free Software Foundation, Inc.
+All Rights Reserved.</literallayout>
+@end docbook
+
+@ifnotdocbook
+Copyright @copyright{} 1989, 1991, 1992, 1993, 1996--2005, 2007, 2009--2014 @*
+Free Software Foundation, Inc.
+@end ifnotdocbook
 @sp 2
 
 This is Edition @value{EDITION} of @cite{@value{TITLE}: @value{SUBTITLE}},
@@ -202,6 +324,7 @@ supports it in developing GNU and promoting software freedom.''
 @subtitle @value{UPDATE-MONTH}
 @author Arnold D. Robbins
 
+@ifnotdocbook
 @c Include the Distribution inside the titlepage environment so
 @c that headings are turned off.  Headings on and off do not work.
 
@@ -226,6 +349,7 @@ URL: @uref{http://www.gnu.org/} @*
 ISBN 1-882114-28-0 @*
 @sp 2
 @insertcopying
+@end ifnotdocbook
 @end titlepage
 
 @c Thanks to Bob Chassell for directions on doing dedications.
@@ -234,15 +358,13 @@ ISBN 1-882114-28-0 @*
 @page
 @w{ }
 @sp 9
-@center @i{To Miriam, for making me complete.}
-@sp 1
-@center @i{To Chana, for the joy you bring us.}
+@center @i{To my parents, for their love, and for the wonderful example they set for me.}
 @sp 1
-@center @i{To Rivka, for the exponential increase.}
+@center @i{To my wife Miriam, for making me complete.
+Thank you for building your life together with me.}
 @sp 1
-@center @i{To Nachum, for the added dimension.}
+@center @i{To our children Chana, Rivka, Nachum and Malka, for enrichening our lives in innumerable ways.}
 @sp 1
-@center @i{To Malka, for the new beginning.}
 @w{ }
 @page
 @w{ }
@@ -250,6 +372,17 @@ ISBN 1-882114-28-0 @*
 @headings on
 @end iftex
 
+@docbook
+<dedication>
+<para>To my parents, for their love, and for the wonderful
+example they set for me.</para>
+<para>To my wife Miriam, for making me complete.
+Thank you for building your life together with me.</para>
+<para>To our children Chana, Rivka, Nachum and Malka,
+for enrichening our lives in innumerable ways.</para>
+</dedication>
+@end docbook
+
 @iftex
 @headings off
 @evenheading @thispage@ @ @ @strong{@value{TITLE}} @| @|
@@ -258,6 +391,7 @@ ISBN 1-882114-28-0 @*
 
 @ifnottex
 @ifnotxml
+@ifnotdocbook
 @node Top
 @top General Introduction
 @c Preface node should come right after the Top
@@ -269,6 +403,7 @@ particular records in a file and perform operations upon them.
 
 @insertcopying
 
+@end ifnotdocbook
 @end ifnotxml
 @end ifnottex
 
@@ -336,8 +471,8 @@ particular records in a file and perform operations upon them.
                                         includes command-line syntax.
 * One-shot::                            Running a short throwaway
                                         @command{awk} program.
-* Read Terminal::                       Using no input files (input from
-                                        terminal instead).
+* Read Terminal::                       Using no input files (input from the
+                                        keyboard instead).
 * Long::                                Putting permanent @command{awk}
                                         programs in files.
 * Executable Scripts::                  Making self-contained @command{awk}
@@ -359,6 +494,7 @@ particular records in a file and perform operations upon them.
 * Other Features::                      Other Features of @command{awk}.
 * When::                                When to use @command{gawk} and when to
                                         use other things.
+* Intro Summary::                       Summary of the introduction.
 * Command Line::                        How to run @command{awk}.
 * Options::                             Command-line options and their
                                         meanings.
@@ -380,6 +516,7 @@ particular records in a file and perform operations upon them.
                                         program.
 * Obsolete::                            Obsolete Options and/or features.
 * Undocumented::                        Undocumented Options and Features.
+* Invoking Summary::                    Invocation summary.
 * Regexp Usage::                        How to Use Regular Expressions.
 * Escape Sequences::                    How to write nonprinting characters.
 * Regexp Operators::                    Regular Expression Operators.
@@ -388,8 +525,12 @@ particular records in a file and perform operations upon them.
 * Case-sensitivity::                    How to do case-insensitive matching.
 * Leftmost Longest::                    How much text matches.
 * Computed Regexps::                    Using Dynamic Regexps.
+* Regexp Summary::                      Regular expressions summary.
 * Records::                             Controlling how data is split into
                                         records.
+* awk split records::                   How standard @command{awk} splits
+                                        records.
+* gawk split records::                  How @command{gawk} splits records.
 * Fields::                              An introduction to fields.
 * Nonconstant Fields::                  Nonconstant Field Numbers.
 * Changing Fields::                     Changing the Contents of a Field.
@@ -401,6 +542,8 @@ particular records in a file and perform operations upon them.
                                         field.
 * Command Line Field Separator::        Setting @code{FS} from the
                                         command-line.
+* Full Line Fields::                    Making the full line be a single
+                                        field.
 * Field Splitting Summary::             Some final points and a summary table.
 * Constant Size::                       Reading constant width data.
 * Splitting By Content::                Defining Fields By Content
@@ -426,6 +569,8 @@ particular records in a file and perform operations upon them.
 * Read Timeout::                        Reading input with a timeout.
 * Command line directories::            What happens if you put a directory on
                                         the command line.
+* Input Summary::                       Input summary.
+* Input Exercises::                     Exercises.
 * Print::                               The @code{print} statement.
 * Print Examples::                      Simple examples of @code{print}
                                         statements.
@@ -449,6 +594,8 @@ particular records in a file and perform operations upon them.
 * Special Caveats::                     Things to watch out for.
 * Close Files And Pipes::               Closing Input and Output Files and
                                         Pipes.
+* Output Summary::                      Output summary.
+* Output exercises::                    Exercises.
 * Values::                              Constants, Variables, and Regular
                                         Expressions.
 * Constants::                           String, numeric and regexp constants.
@@ -464,6 +611,9 @@ particular records in a file and perform operations upon them.
                                         This is an advanced method of input.
 * Conversion::                          The conversion of strings to numbers
                                         and vice versa.
+* Strings And Numbers::                 How @command{awk} Converts Between
+                                        Strings And Numbers.
+* Locale influences conversions::       How the locale may affect conversions.
 * All Operators::                       @command{gawk}'s operators.
 * Arithmetic Ops::                      Arithmetic operations (@samp{+},
                                         @samp{-}, etc.)
@@ -491,6 +641,7 @@ particular records in a file and perform operations upon them.
 * Function Calls::                      A function call is an expression.
 * Precedence::                          How various operators nest.
 * Locales::                             How the locale affects things.
+* Expressions Summary::                 Expressions summary.
 * Pattern Overview::                    What goes into a pattern.
 * Regexp Patterns::                     Using regexps as patterns.
 * Expression Patterns::                 Any expression can be used as a
@@ -537,6 +688,7 @@ particular records in a file and perform operations upon them.
                                         gives you information.
 * ARGC and ARGV::                       Ways to use @code{ARGC} and
                                         @code{ARGV}.
+* Pattern Action Summary::              Patterns and Actions summary.
 * Array Basics::                        The basics of arrays.
 * Array Intro::                         Introduction to Arrays
 * Reference to Elements::               How to examine one element of an
@@ -559,6 +711,7 @@ particular records in a file and perform operations upon them.
                                         @command{awk}.
 * Multiscanning::                       Scanning multidimensional arrays.
 * Arrays of Arrays::                    True multidimensional arrays.
+* Arrays Summary::                      Summary of arrays.
 * Built-in::                            Summarizes the built-in functions.
 * Calling Built-in::                    How to call built-in functions.
 * Numeric Functions::                   Functions that work with numbers,
@@ -593,6 +746,7 @@ particular records in a file and perform operations upon them.
                                         runtime.
 * Indirect Calls::                      Choosing the function to call at
                                         runtime.
+* Functions Summary::                   Summary of functions.
 * Library Names::                       How to best name private global
                                         variables in library functions.
 * General Functions::                   Functions that are of general use.
@@ -627,6 +781,8 @@ particular records in a file and perform operations upon them.
 * Group Functions::                     Functions for getting group
                                         information.
 * Walking Arrays::                      A function to walk arrays of arrays.
+* Library Functions Summary::           Summary of library functions.
+* Library exercises::                   Exercises.
 * Running Examples::                    How to run these examples.
 * Clones::                              Clones of common utilities.
 * Cut Program::                         The @command{cut} utility.
@@ -656,6 +812,8 @@ particular records in a file and perform operations upon them.
 * Anagram Program::                     Finding anagrams from a dictionary.
 * Signature Program::                   People do amazing things with too much
                                         time on their hands.
+* Programs Summary::                    Summary of programs.
+* Programs Exercises::                  Exercises.
 * Nondecimal Data::                     Allowing nondecimal input data.
 * Array Sorting::                       Facilities for controlling array
                                         traversal and sorting arrays.
@@ -667,8 +825,9 @@ particular records in a file and perform operations upon them.
 * TCP/IP Networking::                   Using @command{gawk} for network
                                         programming.
 * Profiling::                           Profiling your @command{awk} programs.
+* Advanced Features Summary::           Summary of advanced features.
 * I18N and L10N::                       Internationalization and Localization.
-* Explaining gettext::                  How GNU @code{gettext} works.
+* Explaining gettext::                  How GNU @command{gettext} works.
 * Programmer i18n::                     Features for the programmer.
 * Translator i18n::                     Features for the translator.
 * String Extraction::                   Extracting marked strings.
@@ -678,6 +837,7 @@ particular records in a file and perform operations upon them.
 * I18N Example::                        A simple i18n example.
 * Gawk I18N::                           @command{gawk} is also
                                         internationalized.
+* I18N Summary::                        Summary of I18N stuff.
 * Debugging::                           Introduction to @command{gawk}
                                         debugger.
 * Debugging Concepts::                  Debugging in General.
@@ -696,31 +856,23 @@ particular records in a file and perform operations upon them.
 * Miscellaneous Debugger Commands::     Miscellaneous Commands.
 * Readline Support::                    Readline support.
 * Limitations::                         Limitations and future plans.
-* General Arithmetic::                  An introduction to computer
-                                        arithmetic.
-* Floating Point Issues::               Stuff to know about floating-point
-                                        numbers.
-* String Conversion Precision::         The String Value Can Lie.
-* Unexpected Results::                  Floating Point Numbers Are Not
-                                        Abstract Numbers.
-* POSIX Floating Point Problems::       Standards Versus Existing Practice.
-* Integer Programming::                 Effective integer programming.
-* Floating-point Programming::          Effective Floating-point Programming.
-* Floating-point Representation::       Binary floating-point representation.
-* Floating-point Context::              Floating-point context.
-* Rounding Mode::                       Floating-point rounding mode.
-* Gawk and MPFR::                       How @command{gawk} provides
-                                        arbitrary-precision arithmetic.
-* Arbitrary Precision Floats::          Arbitrary Precision Floating-point
-                                        Arithmetic with @command{gawk}.
-* Setting Precision::                   Setting the working precision.
-* Setting Rounding Mode::               Setting the rounding mode.
-* Floating-point Constants::            Representing floating-point constants.
-* Changing Precision::                  Changing the precision of a number.
-* Exact Arithmetic::                    Exact arithmetic with floating-point
-                                        numbers.
+* Debugging Summary::                   Debugging summary.
+* Computer Arithmetic::                 A quick intro to computer math.
+* Math Definitions::                    Defining terms used.
+* MPFR features::                       The MPFR features in @command{gawk}.
+* FP Math Caution::                     Things to know.
+* Inexactness of computations::         Floating point math is not exact.
+* Inexact representation::              Numbers are not exactly represented.
+* Comparing FP Values::                 How to compare floating point values.
+* Errors accumulate::                   Errors get bigger as they go.
+* Getting Accuracy::                    Getting more accuracy takes some work.
+* Try To Round::                        Add digits and round.
+* Setting precision::                   How to set the precision.
+* Setting the rounding mode::           How to set the rounding mode.
 * Arbitrary Precision Integers::        Arbitrary Precision Integer Arithmetic
                                         with @command{gawk}.
+* POSIX Floating Point Problems::       Standards Versus Existing Practice.
+* Floating point summary::              Summary of floating point discussion.
 * Extension Intro::                     What is an extension.
 * Plugin License::                      A note about licensing.
 * Extension Mechanism Outline::         An outline of how it works.
@@ -728,6 +880,7 @@ particular records in a file and perform operations upon them.
 * Extension API Functions Introduction:: Introduction to the API functions.
 * General Data Types::                  The data types.
 * Requesting Values::                   How to get a value.
+* Memory Allocation Functions::         Functions for allocating memory.
 * Constructor Functions::               Functions for creating values.
 * Registration Functions::              Functions to register things with
                                         @command{gawk}.
@@ -781,6 +934,8 @@ particular records in a file and perform operations upon them.
 * Extension Sample Time::               An interface to @code{gettimeofday()}
                                         and @code{sleep()}.
 * gawkextlib::                          The @code{gawkextlib} project.
+* Extension summary::                   Extension summary.
+* Extension Exercises::                 Exercises.
 * V7/SVR3.1::                           The major changes between V7 and
                                         System V Release 3.1.
 * SVR4::                                Minor changes between System V
@@ -790,11 +945,14 @@ particular records in a file and perform operations upon them.
                                         version of @command{awk}.
 * POSIX/GNU::                           The extensions in @command{gawk} not
                                         in POSIX @command{awk}.
+* Feature History::                     The history of the features in
+                                        @command{gawk}.
 * Common Extensions::                   Common Extensions Summary.
 * Ranges and Locales::                  How locales used to affect regexp
                                         ranges.
 * Contributors::                        The major contributors to
                                         @command{gawk}.
+* History summary::                     History summary.
 * Gawk Distribution::                   What is in the @command{gawk}
                                         distribution.
 * Getting::                             How to get the distribution.
@@ -822,14 +980,18 @@ particular records in a file and perform operations upon them.
 * VMS Installation::                    Installing @command{gawk} on VMS.
 * VMS Compilation::                     How to compile @command{gawk} under
                                         VMS.
+* VMS Dynamic Extensions::              Compiling @command{gawk} dynamic
+                                        extensions on VMS.
 * VMS Installation Details::            How to install @command{gawk} under
                                         VMS.
 * VMS Running::                         How to run @command{gawk} under VMS.
+* VMS GNV::                             The VMS GNV Project.
 * VMS Old Gawk::                        An old version comes with some VMS
                                         systems.
 * Bugs::                                Reporting Problems and Bugs.
 * Other Versions::                      Other freely available @command{awk}
                                         implementations.
+* Installation summary::                Summary of installation.
 * Compatibility Mode::                  How to disable certain @command{gawk}
                                         extensions.
 * Additions::                           Making Additions To @command{gawk}.
@@ -838,8 +1000,8 @@ particular records in a file and perform operations upon them.
                                         @command{gawk}.
 * New Ports::                           Porting @command{gawk} to a new
                                         operating system.
-* Derived Files::                       Why derived files are kept in the
-                                        @command{git} repository.
+* Derived Files::                       Why derived files are kept in the Git
+                                        repository.
 * Future Extensions::                   New features that may be implemented
                                         one day.
 * Implementation Limitations::          Some limitations of the
@@ -850,6 +1012,7 @@ particular records in a file and perform operations upon them.
 * Extension Other Design Decisions::    Some other design decisions.
 * Extension Future Growth::             Some room for future growth.
 * Old Extension Mechanism::             Some compatibility for old extensions.
+* Notes summary::                       Summary of implementation notes.
 * Basic High Level::                    The high level view.
 * Basic Data Typing::                   A very quick intro to data types.
 @end detailmenu
@@ -857,15 +1020,14 @@ particular records in a file and perform operations upon them.
 
 @c dedication for Info file
 @ifinfo
-@center To Miriam, for making me complete.
-@sp 1
-@center To Chana, for the joy you bring us.
-@sp 1
-@center To Rivka, for the exponential increase.
+To my parents, for their love, and for the wonderful
+example they set for me.
 @sp 1
-@center To Nachum, for the added dimension.
+To my wife Miriam, for making me complete.
+Thank you for building your life together with me.
 @sp 1
-@center To Malka, for the new beginning.
+To our children Chana, Rivka, Nachum and Malka,
+for enrichening our lives in innumerable ways.
 @end ifinfo
 
 @summarycontents
@@ -874,6 +1036,21 @@ particular records in a file and perform operations upon them.
 @node Foreword
 @unnumbered Foreword
 
+@c This bit is post-processed by a script which turns the chapter
+@c tag into a preface tag, and moves this stuff to before the title.
+@c Bleah.
+@docbook
+  <prefaceinfo>
+    <author>
+      <firstname>Michael</firstname>
+      <surname>Brennan</surname>
+      <!-- can't put mawk into command tags. sigh. -->
+      <affiliation><jobtitle>Author of mawk</jobtitle></affiliation>
+    </author>
+    <date>March, 2001</date>
+   </prefaceinfo>
+@end docbook
+
 Arnold Robbins and I are good friends. We were introduced
 @c 11 years ago
 in 1990
@@ -958,21 +1135,37 @@ and the AWK prototype becomes the product.
 The new @command{pgawk} (profiling @command{gawk}), produces
 program execution counts.
 I recently experimented with an algorithm that for
-@math{n} lines of input, exhibited
+@ifnotdocbook
+@math{n}
+@end ifnotdocbook
+@ifdocbook
+@i{n}
+@end ifdocbook
+lines of input, exhibited
 @tex
 $\sim\! Cn^2$
 @end tex
 @ifnottex
+@ifnotdocbook
 ~ C n^2
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<emphasis>&sim; Cn<superscript>2</superscript></emphasis> @c
+@end docbook
 performance, while
 theory predicted
 @tex
 $\sim\! Cn\log n$
 @end tex
 @ifnottex
+@ifnotdocbook
 ~ C n log n
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<emphasis>&sim; Cn log n</emphasis> @c
+@end docbook
 behavior. A few minutes poring
 over the @file{awkprof.out} profile pinpointed the problem to
 a single line of code.  @command{pgawk} is a welcome addition to
@@ -982,11 +1175,14 @@ Arnold has distilled over a decade of experience writing and
 using AWK programs, and developing @command{gawk}, into this book.  If you use
 AWK or want to learn how, then read this book.
 
+@ifnotdocbook
+@cindex Brennan, Michael
 @display
 Michael Brennan
 Author of @command{mawk}
 March, 2001
 @end display
+@end ifnotdocbook
 
 @node Preface
 @unnumbered Preface
@@ -995,6 +1191,21 @@ March, 2001
 @c
 @c 12/2000: Chuck wants the preface & intro combined.
 
+@c This bit is post-processed by a script which turns the chapter
+@c tag into a preface tag, and moves this stuff to before the title.
+@c Bleah.
+@docbook
+  <prefaceinfo>
+    <author>
+      <firstname>Arnold</firstname>
+      <surname>Robbins</surname>
+      <affiliation><jobtitle>Nof Ayalon</jobtitle></affiliation>
+      <affiliation><jobtitle>ISRAEL</jobtitle></affiliation>
+    </author>
+    <date>June, 2014</date>
+   </prefaceinfo>
+@end docbook
+
 Several kinds of tasks occur repeatedly
 when working with text files.
 You might want to extract certain lines and discard the rest.
@@ -1006,12 +1217,13 @@ Such jobs are often easier with @command{awk}.
 The @command{awk} utility interprets a special-purpose programming language
 that makes it easy to handle simple data-reformatting jobs.
 
+@cindex Brian Kernighan's @command{awk}
 The GNU implementation of @command{awk} is called @command{gawk}; if you
 invoke it with the proper options or environment variables
 (@pxref{Options}), it is fully
 compatible with
-the POSIX@footnote{The 2008 POSIX standard is online at
-@url{http://www.opengroup.org/onlinepubs/9699919799/}.}
+the POSIX@footnote{The 2008 POSIX standard is accessable online at
+@w{@url{http://www.opengroup.org/onlinepubs/9699919799/}.}}
 specification of the @command{awk} language
 and with the Unix version of @command{awk} maintained
 by Brian Kernighan.
@@ -1028,7 +1240,7 @@ Thus, we usually don't distinguish between @command{gawk} and other
 @cindex @command{awk}, uses for
 Using @command{awk} allows you to:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Manage small, personal databases
 
@@ -1053,7 +1265,7 @@ In addition,
 @command{gawk}
 provides facilities that make it easy to:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Extract bits and pieces of data for processing
 
@@ -1062,6 +1274,12 @@ Sort data
 
 @item
 Perform simple network communications
+
+@item
+Profile and debug @command{awk} programs.
+
+@item
+Extend the language with functions written in C or C++.
 @end itemize
 
 This @value{DOCUMENT} teaches you about the @command{awk} language and
@@ -1077,12 +1295,18 @@ Implementations of the @command{awk} language are available for many
 different computing environments.  This @value{DOCUMENT}, while describing
 the @command{awk} language in general, also describes the particular
 implementation of @command{awk} called @command{gawk} (which stands for
-``GNU awk'').  @command{gawk} runs on a broad range of Unix systems,
+``GNU @command{awk}'').  @command{gawk} runs on a broad range of Unix systems,
 ranging from Intel@registeredsymbol{}-architecture PC-based computers
-up through large-scale systems,
-such as Crays. @command{gawk} has also been ported to Mac OS X,
-Microsoft Windows (all versions) and OS/2 PCs,
-and VMS.
+up through large-scale systems.
+@command{gawk} has also been ported to Mac OS X,
+Microsoft Windows
+@ifset FOR_PRINT
+(all versions),
+@end ifset
+@ifclear FOR_PRINT
+(all versions) and OS/2 PCs,
+@end ifclear
+and OpenVMS.
 (Some other, obsolete systems to which @command{gawk} was once ported
 are no longer supported and the code for those systems
 has been removed.)
@@ -1184,11 +1408,11 @@ wrote the bulk of
 @cite{TCP/IP Internetworking with @command{gawk}}
 (a separate document, available as part of the @command{gawk} distribution).
 His code finally became part of the main @command{gawk} distribution
-with @command{gawk} version 3.1.
+with @command{gawk} @value{PVERSION} 3.1.
 
 John Haque rewrote the @command{gawk} internals, in the process providing
 an @command{awk}-level debugger. This version became available as
-@command{gawk} version 4.0, in 2011.
+@command{gawk} @value{PVERSION} 4.0, in 2011.
 
 @xref{Contributors},
 for a complete list of those who made important contributions to @command{gawk}.
@@ -1203,26 +1427,26 @@ The language described in this @value{DOCUMENT}
 is often referred to as ``new @command{awk}'' (@command{nawk}).
 
 @cindex @command{awk}, versions of
-Because of this, there are systems with multiple
-versions of @command{awk}.
-Some systems have an @command{awk} utility that implements the
-original version of the @command{awk} language and a @command{nawk} utility
-for the new version.
-Others have an @command{oawk} version for the ``old @command{awk}''
-language and plain @command{awk} for the new one.  Still others only
-have one version, which is usually the new one.@footnote{Often, these systems
-use @command{gawk} for their @command{awk} implementation!}
-
 @cindex @command{nawk} utility
 @cindex @command{oawk} utility
-All in all, this makes it difficult for you to know which version of
-@command{awk} you should run when writing your programs.  The best advice
-we can give here is to check your local documentation. Look for @command{awk},
-@command{oawk}, and @command{nawk}, as well as for @command{gawk}.
-It is likely that you already
-have some version of new @command{awk} on your system, which is what
-you should use when running your programs.  (Of course, if you're reading
-this @value{DOCUMENT}, chances are good that you have @command{gawk}!)
+For some time after new @command{awk} was introduced, there were
+systems with multiple versions of @command{awk}.  Some systems had
+an @command{awk} utility that implemented the original version of the
+@command{awk} language and a @command{nawk} utility for the new version.
+Others had an @command{oawk} version for the ``old @command{awk}''
+language and plain @command{awk} for the new one.  Still others only
+had one version, which is usually the new one.
+
+Today, only Solaris systems still use an old @command{awk} for the
+default @command{awk} utility. (A more modern @command{awk} lives in
+@file{/usr/xpg6/bin} on these systems.)  All other modern systems use
+some version of new @command{awk}.@footnote{Many of these systems use
+@command{gawk} for their @command{awk} implementation!}
+
+It is likely that you already have some version of new @command{awk} on
+your system, which is what you should use when running your programs.
+(Of course, if you're reading this @value{DOCUMENT}, chances are good
+that you have @command{gawk}!)
 
 Throughout this @value{DOCUMENT}, whenever we refer to a language feature
 that should be available in any complete implementation of POSIX @command{awk},
@@ -1240,7 +1464,7 @@ and the program ``the @command{awk} utility.''
 This @value{DOCUMENT} explains
 both how to write programs in the @command{awk} language and how to
 run the @command{awk} utility.
-The term @dfn{@command{awk} program} refers to a program written by you in
+The term ``@command{awk} program'' refers to a program written by you in
 the @command{awk} programming language.
 
 @cindex @command{gawk}, @command{awk} and
@@ -1250,9 +1474,15 @@ Primarily, this @value{DOCUMENT} explains the features of @command{awk}
 as defined in the POSIX standard.  It does so in the context of the
 @command{gawk} implementation.  While doing so, it also
 attempts to describe important differences between @command{gawk}
-and other @command{awk} implementations.@footnote{All such differences
+and other @command{awk}
+@ifclear FOR_PRINT
+implementations.@footnote{All such differences
 appear in the index under the
 entry ``differences in @command{awk} and @command{gawk}.''}
+@end ifclear
+@ifset FOR_PRINT
+implementations.
+@end ifset
 Finally, any @command{gawk} features that are not in
 the POSIX standard for @command{awk} are noted.
 
@@ -1260,7 +1490,7 @@ the POSIX standard for @command{awk} are noted.
 This @value{DOCUMENT} has the difficult task of being both a tutorial and a reference.
 If you are a novice, feel free to skip over details that seem too complex.
 You should also ignore the many cross-references; they are for the
-expert user and for the online Info and HTML versions of the document.
+expert user and for the online Info and HTML versions of the @value{DOCUMENT}.
 @end ifnotinfo
 
 There are sidebars
@@ -1284,6 +1514,8 @@ should be of interest.
 
 This @value{DOCUMENT} is split into several parts, as follows:
 
+@c FULLXREF ON
+
 Part I describes the @command{awk} language and @command{gawk} program in detail.
 It starts with the basics, and continues through all of the features of @command{awk}.
 It contains the following chapters:
@@ -1367,9 +1599,14 @@ describes advanced arithmetic facilities provided by
 @ref{Dynamic Extensions}, describes how to add new variables and
 functions to @command{gawk} by writing extensions in C or C++.
 
+@ifclear FOR_PRINT
 Part IV provides the appendices, the Glossary, and two licenses that cover
 the @command{gawk} source code and this @value{DOCUMENT}, respectively.
 It contains the following appendices:
+@end ifclear
+@ifset FOR_PRINT
+Part IV provides the following appendices:
+@end ifset
 
 @ref{Language History},
 describes how the @command{awk} language has evolved since
@@ -1384,6 +1621,36 @@ non-POSIX systems.  It also describes how to report bugs
 in @command{gawk} and where to get other freely
 available @command{awk} implementations.
 
+@ifset FOR_PRINT
+The version of this @value{DOCUMENT} distributed with @command{gawk}
+contains additional appendices and other end material.
+To save space, we have omitted them from the
+printed edition. You may find them online, as follows:
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Notes.html,
+The appendix on implementation notes}
+describes how to disable @command{gawk}'s extensions, as
+well as how to contribute new code to @command{gawk},
+and some possible future directions for @command{gawk} development.
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Basic-Concepts.html,
+The appendix on basic concepts}
+provides some very cursory background material for those who
+are completely unfamiliar with computer programming.
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Glossary.html,
+The Glossary}
+defines most, if not all, the significant terms used
+throughout the @value{DOCUMENT}.  If you find terms that you aren't familiar with,
+try looking them up here.
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Copying.html, The GNU GPL} and
+@uref{http://www.gnu.org/software/gawk/manual/html_node/GNU-Free-Documentation-License.html, the GNU FDL}
+are the licenses that cover the @command{gawk} source code
+and this @value{DOCUMENT}, respectively.
+@end ifset
+
+@ifclear FOR_PRINT
 @ref{Notes},
 describes how to disable @command{gawk}'s extensions, as
 well as how to contribute new code to @command{gawk},
@@ -1394,13 +1661,16 @@ provides some very cursory background material for those who
 are completely unfamiliar with computer programming.
 
 The @ref{Glossary}, defines most, if not all, the significant terms used
-throughout the book.  If you find terms that you aren't familiar with,
+throughout the @value{DOCUMENT}.  If you find terms that you aren't familiar with,
 try looking them up here.
 
 @ref{Copying}, and
 @ref{GNU Free Documentation License},
 present the licenses that cover the @command{gawk} source code
 and this @value{DOCUMENT}, respectively.
+@end ifclear
+
+@c FULLXREF OFF
 
 @node Conventions
 @unnumberedsec Typographical Conventions
@@ -1442,7 +1712,7 @@ emphasized @emph{like this}, and if a point needs to be made
 strongly, it is done @strong{like this}.  The first occurrence of
 a new term is usually its @dfn{definition} and appears in the same
 font as the previous occurrence of ``definition'' in this sentence.
-Finally, file names are indicated like this: @file{/path/to/ourfile}.
+Finally, @value{FN}s are indicated like this: @file{/path/to/ourfile}.
 @end ifnotinfo
 
 Characters that you type at the keyboard look @kbd{like this}.  In particular,
@@ -1474,16 +1744,22 @@ the picture of a flashlight in the margin, as shown here.
 @ifnottex
 ``(d.c.)''.
 @end ifnottex
+@ifclear FOR_PRINT
 They also appear in the index under the heading ``dark corner.''
+@end ifclear
 
-As noted by the opening quote, though, any
-coverage of dark corners
-is, by definition, incomplete.
+As noted by the opening quote, though, any coverage of dark corners is,
+by definition, incomplete.
 
 Extensions to the standard @command{awk} language that are supported by
 more than one @command{awk} implementation are marked
+@ifclear FOR_PRINT
 ``@value{COMMONEXT},'' and listed in the index under ``common extensions''
 and ``extensions, common.''
+@end ifclear
+@ifset FOR_PRINT
+``@value{COMMONEXT}.''
+@end ifset
 
 @node Manual History
 @unnumberedsec The GNU Project and This Book
@@ -1506,13 +1782,15 @@ Foundation to create a complete, freely distributable, POSIX-compliant
 computing environment.
 The FSF uses the ``GNU General Public License'' (GPL) to ensure that
 their software's
-source code is always available to the end user. A
-copy of the GPL is included
+source code is always available to the end user.
+@ifclear FOR_PRINT
+A copy of the GPL is included
 @ifnotinfo
 in this @value{DOCUMENT}
 @end ifnotinfo
 for your reference
 (@pxref{Copying}).
+@end ifclear
 The GPL applies to the C language source code for @command{gawk}.
 To find out more about the FSF and the GNU Project online,
 see @uref{http://www.gnu.org, the GNU Project's home page}.
@@ -1535,8 +1813,13 @@ consider using GNU/Linux, a freely distributable, Unix-like operating
 system for Intel@registeredsymbol{},
 Power Architecture,
 Sun SPARC, IBM S/390, and other
+@ifclear FOR_PRINT
 systems.@footnote{The terminology ``GNU/Linux'' is explained
 in the @ref{Glossary}.}
+@end ifclear
+@ifset FOR_PRINT
+systems.
+@end ifset
 Many GNU/Linux distributions are
 available for download from the Internet.
 
@@ -1556,53 +1839,13 @@ The @value{DOCUMENT} you are reading is actually free---at least, the
 information in it is free to anyone.  The machine-readable
 source code for the @value{DOCUMENT} comes with @command{gawk}; anyone
 may take this @value{DOCUMENT} to a copying machine and make as many
-copies as they like.  (Take a moment to check the Free Documentation
+copies as they like.
+@ifclear FOR_PRINT
+(Take a moment to check the Free Documentation
 License in @ref{GNU Free Documentation License}.)
+@end ifclear
 @end ifnotinfo
 
-@ignore
-@cindex Close, Diane
-The @value{DOCUMENT} itself has gone through several previous,
-preliminary editions.
-Paul Rubin wrote the very first draft of @cite{The GAWK Manual};
-it was around 40 pages in size.
-Diane Close and Richard Stallman improved it, yielding the
-version which I started working with in the fall of 1988.
-It was around 90 pages long and barely described the original, ``old''
-version of @command{awk}. After substantial revision, the first version of
-the @cite{The GAWK Manual} to be released was Edition 0.11 Beta in
-October of 1989.  The manual then underwent more substantial revision
-for Edition 0.13 of December 1991.
-David Trueman, Pat Rankin and Michal Jaegermann contributed sections
-of the manual for Edition 0.13.
-That edition was published by the
-FSF as a bound book early in 1992.  Since then there were several
-minor revisions, notably Edition 0.14 of November 1992 that was published
-by the FSF in January of 1993 and Edition 0.16 of August 1993.
-
-Edition 1.0 of @cite{GAWK: The GNU Awk User's Guide} represented a significant re-working
-of @cite{The GAWK Manual}, with much additional material.
-The FSF and I agreed that I was now the primary author.
-@c I also felt that the manual needed a more descriptive title.
-
-In January 1996, SSC published Edition 1.0 under the title @cite{Effective AWK Programming}.
-In February 1997, they published Edition 1.0.3 which had minor changes
-as a ``second edition.''
-In 1999, the FSF published this same version as Edition 2
-of @cite{GAWK: The GNU Awk User's Guide}.
-
-Edition @value{EDITION} maintains the basic structure of Edition 1.0,
-but with significant additional material, reflecting the host of new features
-in @command{gawk} version @value{VERSION}.
-Of particular note is
-@ref{Array Sorting},
-@ref{Bitwise Functions},
-@ref{Internationalization},
-@ref{Advanced Features},
-and
-@ref{Dynamic Extensions}.
-@end ignore
-
 @cindex Close, Diane
 The @value{DOCUMENT} itself has gone through a number of previous editions.
 Paul Rubin wrote the very first draft of @cite{The GAWK Manual};
@@ -1618,24 +1861,50 @@ the FSF published several preliminary versions (numbered 0.@var{x}).
 In 1996, Edition 1.0 was released with @command{gawk} 3.0.0.
 The FSF published the first two editions under
 the title @cite{The GNU Awk User's Guide}.
+@ifset FOR_PRINT
+SSC published two editions of the @value{DOCUMENT} under the
+title @cite{Effective awk Programming}, and in O'Reilly published
+the third edition in 2001.
+@end ifset
 
 This edition maintains the basic structure of the previous editions.
-For Edition 4.0, the content has been thoroughly reviewed
+For FSF edition 4.0, the content has been thoroughly reviewed
 and updated. All references to @command{gawk} versions prior to 4.0 have been
 removed.
 Of significant note for this edition was @ref{Debugger}.
 
-For edition @value{EDITION}, the content has been reorganized into parts,
+For FSF edition
+@ifclear FOR_PRINT
+@value{EDITION},
+@end ifclear
+@ifset FOR_PRINT
+@value{EDITION}
+(the fourth edition as published by O'Reilly),
+@end ifset
+the content has been reorganized into parts,
 and the major new additions are @ref{Arbitrary Precision Arithmetic},
 and @ref{Dynamic Extensions}.
 
-@cite{@value{TITLE}} will undoubtedly continue to evolve.
-An electronic version
-comes with the @command{gawk} distribution from the FSF.
-If you find an error in this @value{DOCUMENT}, please report it!
-@xref{Bugs}, for information on submitting
-problem reports electronically.
+This @value{DOCUMENT} will undoubtedly continue to evolve.  An electronic
+version comes with the @command{gawk} distribution from the FSF.  If you
+find an error in this @value{DOCUMENT}, please report it!  @xref{Bugs},
+for information on submitting problem reports electronically.
 
+@ifset FOR_PRINT
+@c fakenode --- for prepinfo
+@unnumberedsec How to Stay Current
+
+It may be you have a version of @command{gawk} which is newer than the
+one described in this @value{DOCUMENT}.  To find out what has changed,
+you should first look at the @file{NEWS} file in the @command{gawk}
+distribution, which provides a high level summary of what changed in
+each release.
+
+You can then look at the @uref{http://www.gnu.org/software/gawk/manual/,
+online version} of this @value{DOCUMENT} to read about any new features.
+@end ifset
+
+@ifclear FOR_PRINT
 @node How To Contribute
 @unnumberedsec How to Contribute
 
@@ -1652,7 +1921,7 @@ However, I found that I could not dedicate enough time to managing
 contributed code: the archive did not grow and the domain went unused
 for several years.
 
-Fortunately, late in 2008, a volunteer took on the task of setting up
+Late in 2008, a volunteer took on the task of setting up
 an @command{awk}-related web site---@uref{http://awk.info}---and did a very
 nice job.
 
@@ -1661,11 +1930,15 @@ a @command{gawk} extension that you would like to share with the rest
 of the world, please see @uref{http://awk.info/?contribute} for how to
 contribute it to the web site.
 
+As of this writing, this website is in search of a maintainer; please
+contact me if you are interested.
+
 @ignore
 Other links:
 
 http://www.reddit.com/r/linux/comments/dtect/composing_music_in_awk/
 @end ignore
+@end ifclear
 
 @node Acknowledgments
 @unnumberedsec Acknowledgments
@@ -1756,7 +2029,7 @@ significant editorial help for this @value{DOCUMENT} for the
 3.1 release of @command{gawk}.
 @end quotation
 
-@cindex Beebe, Nelson
+@cindex Beebe, Nelson H.F.@:
 @cindex Buening, Andreas
 @cindex Collado, Manuel
 @cindex Colombo, Antonio
@@ -1773,7 +2046,6 @@ significant editorial help for this @value{DOCUMENT} for the
 @cindex Rankin, Pat
 @cindex Schorr, Andrew
 @cindex Vinschen, Corinna
-@cindex Wallin, Anders
 @cindex Zaretskii, Eli
 
 Dr.@: Nelson Beebe,
@@ -1793,7 +2065,6 @@ Chet Ramey,
 Pat Rankin,
 Andrew Schorr,
 Corinna Vinschen,
-Anders Wallin,
 and Eli Zaretskii
 (in alphabetical order)
 make up the current
@@ -1805,6 +2076,10 @@ people.
 Notable code and documentation contributions were made by
 a number of people. @xref{Contributors}, for the full list.
 
+Thanks to Patrice Dumas  for the new @command{makeinfo} program.
+Thanks to Karl Berry who continues to work to keep
+the Texinfo markup language sane.
+
 @cindex Kernighan, Brian
 I would like to thank Brian Kernighan for invaluable assistance during the
 testing and debugging of @command{gawk}, and for ongoing
@@ -1824,26 +2099,28 @@ which they raised and educated me.
 Finally, I also must acknowledge my gratitude to G-d, for the many opportunities
 He has sent my way, as well as for the gifts He has given me with which to
 take advantage of those opportunities.
+@iftex
 @sp 2
 @noindent
 Arnold Robbins @*
 Nof Ayalon @*
 ISRAEL @*
-May, 2013
-
-@iftex
-@part Part I:@* The @command{awk} Language
+May, 2014
 @end iftex
 
-@ignore
+@ifnotinfo
+@part @value{PART1}The @command{awk} Language
+@end ifnotinfo
+
 @ifdocbook
-@part Part I:@* The @command{awk} Language
 
-Part I describes the @command{awk} language and @command{gawk} program in detail.
-It starts with the basics, and continues through all of the features of @command{awk}
-and @command{gawk}.  It contains the following chapters:
+Part I describes the @command{awk} language and @command{gawk} program
+in detail.  It starts with the basics, and continues through all of
+the features of @command{awk}. Included also are many, but not all,
+of the features of @command{gawk}.  This part contains the
+following chapters:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Getting Started}.
 
@@ -1872,7 +2149,6 @@ and @command{gawk}.  It contains the following chapters:
 @ref{Functions}.
 @end itemize
 @end ifdocbook
-@end ignore
 
 @node Getting Started
 @chapter Getting Started with @command{awk}
@@ -1912,7 +2188,7 @@ pattern to search for and one action to perform
 upon finding the pattern.
 
 Syntactically, a rule consists of a pattern followed by an action.  The
-action is enclosed in curly braces to separate it from the pattern.
+action is enclosed in braces to separate it from the pattern.
 Newlines usually separate rules.  Therefore, an @command{awk}
 program looks like this:
 
@@ -1936,6 +2212,7 @@ program looks like this:
 * Other Features::              Other Features of @command{awk}.
 * When::                        When to use @command{gawk} and when to use
                                 other things.
+* Intro Summary::               Summary of the introduction.
 @end menu
 
 @node Running gawk
@@ -1964,7 +2241,7 @@ variations of each.
 @menu
 * One-shot::                    Running a short throwaway @command{awk}
                                 program.
-* Read Terminal::               Using no input files (input from terminal
+* Read Terminal::               Using no input files (input from the keyboard
                                 instead).
 * Long::                        Putting permanent @command{awk} programs in
                                 files.
@@ -2028,10 +2305,15 @@ awk '@var{program}'
 
 @noindent
 @command{awk} applies the @var{program} to the @dfn{standard input},
-which usually means whatever you type on the terminal.  This continues
+which usually means whatever you type on the keyboard.  This continues
 until you indicate end-of-file by typing @kbd{Ctrl-d}.
+@ifset FOR_PRINT
+(On other operating systems, the end-of-file character may be different.)
+@end ifset
+@ifclear FOR_PRINT
 (On other operating systems, the end-of-file character may be different.
 For example, on OS/2, it is @kbd{Ctrl-z}.)
+@end ifclear
 
 @cindex files, input, See input files
 @cindex input files, running @command{awk} without
@@ -2051,11 +2333,11 @@ $ @kbd{awk "BEGIN @{ print \"Don't Panic!\" @}"}
 @print{} Don't Panic!
 @end example
 
-@cindex quoting
-@cindex double quote (@code{"})
-@cindex @code{"} (double quote)
-@cindex @code{\} (backslash)
-@cindex backslash (@code{\})
+@cindex shell quoting, double quote
+@cindex double quote (@code{"}) in shell commands
+@cindex @code{"} (double quote) in shell commands
+@cindex @code{\} (backslash) in shell commands
+@cindex backslash (@code{\}) in shell commands
 This program does not read any input.  The @samp{\} before each of the
 inner double quotes is necessary because of the shell's quoting
 rules---in particular because it mixes both single quotes and
@@ -2094,11 +2376,10 @@ more convenient to put the program into a separate file.  In order to tell
 awk -f @var{source-file} @var{input-file1} @var{input-file2} @dots{}
 @end example
 
-@cindex @code{-f} option
-@cindex command line, options
-@cindex options, command-line
+@cindex @option{-f} option
+@cindex command line, option @option{-f}
 The @option{-f} instructs the @command{awk} utility to get the @command{awk} program
-from the file @var{source-file}.  Any file name can be used for
+from the file @var{source-file}.  Any @value{FN} can be used for
 @var{source-file}.  For example, you could put the program:
 
 @example
@@ -2119,22 +2400,22 @@ does the same thing as this one:
 awk "BEGIN @{ print \"Don't Panic!\" @}"
 @end example
 
-@cindex quoting
+@cindex quoting in @command{gawk} command lines
 @noindent
 This was explained earlier
 (@pxref{Read Terminal}).
-Note that you don't usually need single quotes around the file name that you
-specify with @option{-f}, because most file names don't contain any of the shell's
+Note that you don't usually need single quotes around the @value{FN} that you
+specify with @option{-f}, because most @value{FN}s don't contain any of the shell's
 special characters.  Notice that in @file{advice}, the @command{awk}
 program did not have single quotes around it.  The quotes are only needed
 for programs that are provided on the @command{awk} command line.
 
 @c STARTOFRANGE sq1x
-@cindex single quote (@code{'})
+@cindex single quote (@code{'}) in @command{gawk} command lines
 @c STARTOFRANGE qs2x
-@cindex @code{'} (single quote)
+@cindex @code{'} (single quote) in @command{gawk} command lines
 If you want to clearly identify your @command{awk} program files as such,
-you can add the extension @file{.awk} to the file name.  This doesn't
+you can add the extension @file{.awk} to the @value{FN}.  This doesn't
 affect the execution of the @command{awk} program but it does make
 ``housekeeping'' easier.
 
@@ -2161,13 +2442,13 @@ BEGIN @{ print "Don't Panic!" @}
 After making this file executable (with the @command{chmod} utility),
 simply type @samp{advice}
 at the shell and the system arranges to run @command{awk}@footnote{The
-line beginning with @samp{#!} lists the full file name of an interpreter
+line beginning with @samp{#!} lists the full @value{FN} of an interpreter
 to run and an optional initial command-line argument to pass to that
 interpreter.  The operating system then runs the interpreter with the given
 argument and the full argument list of the executed program.  The first argument
-in the list is the full file name of the @command{awk} program.
+in the list is the full @value{FN} of the @command{awk} program.
 The rest of the
-argument list contains either options to @command{awk}, or data files,
+argument list contains either options to @command{awk}, or @value{DF}s,
 or both. Note that on many systems @command{awk} may be found in
 @file{/usr/bin} instead of in @file{/bin}. Caveat Emptor.} as if you had
 typed @samp{awk -f advice}:
@@ -2281,7 +2562,7 @@ programs, but this usually isn't very useful; the purpose of a
 comment is to help you or another person understand the program
 when reading it at a later time.
 
-@cindex quoting
+@cindex quoting, for small awk programs
 @cindex single quote (@code{'}), vs.@: apostrophe
 @cindex @code{'} (single quote), vs.@: apostrophe
 @quotation CAUTION
@@ -2297,7 +2578,7 @@ runs, it will probably print strange messages about syntax errors.
 For example, look at the following:
 
 @example
-$ @kbd{awk '@{ print "hello" @} # let's be cute'}
+$ @kbd{awk 'BEGIN @{ print "hello" @} # let's be cute'}
 >
 @end example
 
@@ -2322,7 +2603,7 @@ The next @value{SUBSECTION} describes the shell's quoting rules.
 
 @node Quoting
 @subsection Shell-Quoting Issues
-@cindex quoting, rules for
+@cindex shell quoting, rules for
 
 @menu
 * DOS Quoting::                 Quoting in Windows Batch Files.
@@ -2345,7 +2626,28 @@ knowledge of shell quoting rules.  The following rules apply only to
 POSIX-compliant, Bourne-style shells (such as Bash, the GNU Bourne-Again
 Shell).  If you use the C shell, you're on your own.
 
-@itemize @bullet
+Before diving into the rules, we introduce a concept that appears
+throughout this @value{DOCUMENT}, which is that of the @dfn{null},
+or empty, string.
+
+The null string is character data that has no value.
+In other words, it is empty.  It is written in @command{awk} programs
+like this: @code{""}. In the shell, it can be written using single
+or double quotes: @code{""} or @code{''}. While the null string has
+no characters in it, it does exist. Consider this command:
+
+@example
+$ @kbd{echo ""}
+@end example
+
+@noindent
+Here, the @command{echo} utility receives a single argument, even
+though that argument has no characters in it. In the rest of this
+@value{DOCUMENT}, we use the terms @dfn{null string} and @dfn{empty string}
+interchangeably.  Now, on to the quoting rules.
+
+
+@itemize @value{BULLET}
 @item
 Quoted items can be concatenated with nonquoted items as well as with other
 quoted items.  The shell turns everything into one argument for
@@ -2357,10 +2659,10 @@ that character.  The shell removes the backslash and passes the quoted
 character on to the command.
 
 @item
-@cindex @code{\} (backslash)
-@cindex backslash (@code{\})
-@cindex single quote (@code{'})
-@cindex @code{'} (single quote)
+@cindex @code{\} (backslash), in shell commands
+@cindex backslash (@code{\}), in shell commands
+@cindex single quote (@code{'}), in shell commands
+@cindex @code{'} (single quote), in shell commands
 Single quotes protect everything between the opening and closing quotes.
 The shell does no interpretation of the quoted text, passing it on verbatim
 to the command.
@@ -2370,8 +2672,8 @@ Refer back to
 for an example of what happens if you try.
 
 @item
-@cindex double quote (@code{"})
-@cindex @code{"} (double quote)
+@cindex double quote (@code{"}), in shell commands
+@cindex @code{"} (double quote), in shell commands
 Double quotes protect most things between the opening and closing quotes.
 The shell does at least variable and command substitution on the quoted text.
 Different shells may do additional kinds of processing on double-quoted text.
@@ -2408,7 +2710,7 @@ awk -F "" '@var{program}' @var{files} # correct
 @end example
 
 @noindent
-@cindex null strings, quoting and
+@cindex null strings in @command{gawk} arguments, quoting and
 Don't use this:
 
 @example
@@ -2417,11 +2719,11 @@ awk -F"" '@var{program}' @var{files}  # wrong!
 
 @noindent
 In the second case, @command{awk} will attempt to use the text of the program
-as the value of @code{FS}, and the first file name as the text of the program!
+as the value of @code{FS}, and the first @value{FN} as the text of the program!
 This results in syntax errors at best, and confusing behavior at worst.
 @end itemize
 
-@cindex quoting, tricks for
+@cindex quoting in @command{gawk} command lines, tricks for
 Mixing single and double quotes is difficult.  You have to resort
 to shell quoting tricks, like this:
 
@@ -2520,6 +2822,7 @@ Although this @value{DOCUMENT} generally only worries about POSIX systems and th
 POSIX shell, the following issue arises often enough for many users that
 it is worth addressing.
 
+@cindex Brink, Jeroen
 The ``shells'' on Microsoft Windows systems use the double-quote
 character for quoting, and make it difficult or impossible to include an
 escaped double-quote character in a command-line script.
@@ -2532,49 +2835,47 @@ gawk "@{ print \"\042\" $0 \"\042\" @}" @var{file}
 
 
 @node Sample Data Files
-@section Data Files for the Examples
-@c For gawk >= 4.0, update these data files. No-one has such slow modems!
+@section @value{DDF}s for the Examples
 
 @cindex input files, examples
-@cindex @code{BBS-list} file
+@cindex @code{mail-list} file
 Many of the examples in this @value{DOCUMENT} take their input from two sample
-data files.  The first, @file{BBS-list}, represents a list of
-computer bulletin board systems together with information about those systems.
-The second data file, called @file{inventory-shipped}, contains
+@value{DF}s.  The first, @file{mail-list}, represents a list of peoples' names
+together with their email addresses and information about those people.
+The second @value{DF}, called @file{inventory-shipped}, contains
 information about monthly shipments.  In both files,
 each line is considered to be one @dfn{record}.
 
-In the data file @file{BBS-list}, each record contains the name of a computer
-bulletin board, its phone number, the board's baud rate(s), and a code for
-the number of hours it is operational.  An @samp{A} in the last column
-means the board operates 24 hours a day.  A @samp{B} in the last
-column means the board only operates on evening and weekend hours.
-A @samp{C} means the board operates only on weekends:
+In the @value{DF} @file{mail-list}, each record contains the name of a person,
+his/her phone number, his/her email-address, and a code for their relationship
+with the author of the list.  An @samp{A} in the last column
+means that the person is an acquaintance.  An @samp{F} in the last
+column means that the person is a friend.
+An @samp{R} means that the person is a relative:
 
-@c 2e: Update the baud rates to reflect today's faster modems
 @example
 @c system if test ! -d eg      ; then mkdir eg      ; fi
 @c system if test ! -d eg/lib  ; then mkdir eg/lib  ; fi
 @c system if test ! -d eg/data ; then mkdir eg/data ; fi
 @c system if test ! -d eg/prog ; then mkdir eg/prog ; fi
 @c system if test ! -d eg/misc ; then mkdir eg/misc ; fi
-@c file eg/data/BBS-list
-aardvark     555-5553     1200/300          B
-alpo-net     555-3412     2400/1200/300     A
-barfly       555-7685     1200/300          A
-bites        555-1675     2400/1200/300     A
-camelot      555-0542     300               C
-core         555-2912     1200/300          C
-fooey        555-1234     2400/1200/300     B
-foot         555-6699     1200/300          B
-macfoo       555-6480     1200/300          A
-sdace        555-3430     2400/1200/300     A
-sabafoo      555-2127     1200/300          C
+@c file eg/data/mail-list
+Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+Anthony      555-3412     anthony.asserturo@@hotmail.com   A
+Becky        555-7685     becky.algebrarum@@gmail.com      A
+Bill         555-1675     bill.drowning@@hotmail.com       A
+Broderick    555-0542     broderick.aliquotiens@@yahoo.com R
+Camilla      555-2912     camilla.infusarum@@skynet.be     R
+Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+Julie        555-6699     julie.perscrutabor@@skeeve.com   F
+Martin       555-6480     martin.codicibus@@hotmail.com    A
+Samuel       555-3430     samuel.lanceolis@@shu.edu        A
+Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @c endfile
 @end example
 
 @cindex @code{inventory-shipped} file
-The data file @file{inventory-shipped} represents
+The @value{DF} @file{inventory-shipped} represents
 information about shipments during the year.
 Each record contains the month, the number
 of green crates shipped, the number of red boxes shipped, the number of
@@ -2604,45 +2905,30 @@ Apr  21  70  74 514
 @c endfile
 @end example
 
-@ifinfo
-If you are reading this in GNU Emacs using Info, you can copy the regions
-of text showing these sample files into your own test files.  This way you
-can try out the examples shown in the remainder of this document.  You do
-this by using the command @kbd{M-x write-region} to copy text from the Info
-file into a file for use with @command{awk}
-(@xref{Misc File Ops, , Miscellaneous File Operations, emacs, GNU Emacs Manual},
-for more information).  Using this information, create your own
-@file{BBS-list} and @file{inventory-shipped} files and practice what you
-learn in this @value{DOCUMENT}.
-
-@cindex Texinfo
-If you are using the stand-alone version of Info,
-see @ref{Extract Program},
-for an @command{awk} program that extracts these data files from
-@file{gawk.texi}, the (generated) Texinfo source file for this Info file.
-@end ifinfo
+The sample files are included in the @command{gawk} distribution,
+in the directory @file{awklib/eg/data}.
 
 @node Very Simple
 @section Some Simple Examples
 
 The following command runs a simple @command{awk} program that searches the
-input file @file{BBS-list} for the character string @samp{foo} (a
+input file @file{mail-list} for the character string @samp{li} (a
 grouping of characters is usually called a @dfn{string};
 the term @dfn{string} is based on similar usage in English, such
 as ``a string of pearls,'' or ``a string of cars in a train''):
 
 @example
-awk '/foo/ @{ print $0 @}' BBS-list
+awk '/li/ @{ print $0 @}' mail-list
 @end example
 
 @noindent
-When lines containing @samp{foo} are found, they are printed because
+When lines containing @samp{li} are found, they are printed because
 @w{@samp{print $0}} means print the current line.  (Just @samp{print} by
 itself means the same thing, so we could have written that
 instead.)
 
-You will notice that slashes (@samp{/}) surround the string @samp{foo}
-in the @command{awk} program.  The slashes indicate that @samp{foo}
+You will notice that slashes (@samp{/}) surround the string @samp{li}
+in the @command{awk} program.  The slashes indicate that @samp{li}
 is the pattern to search for.  This type of pattern is called a
 @dfn{regular expression}, which is covered in more detail later
 (@pxref{Regexp}).
@@ -2654,11 +2940,11 @@ interpret any of it as special shell characters.
 Here is what this program prints:
 
 @example
-$ @kbd{awk '/foo/ @{ print $0 @}' BBS-list}
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sabafoo      555-2127     1200/300          C
+$ @kbd{awk '/li/ @{ print $0 @}' mail-list}
+@print{} Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+@print{} Broderick    555-0542     broderick.aliquotiens@@yahoo.com R
+@print{} Julie        555-6699     julie.perscrutabor@@skeeve.com   F
+@print{} Samuel       555-3430     samuel.lanceolis@@shu.edu        A
 @end example
 
 @cindex actions, default
@@ -2669,10 +2955,10 @@ for @emph{every} input line.  If the action is omitted, the default
 action is to print all lines that match the pattern.
 
 @cindex actions, empty
-Thus, we could leave out the action (the @code{print} statement and the curly
+Thus, we could leave out the action (the @code{print} statement and the
 braces) in the previous example and the result would be the same:
-@command{awk} prints all lines matching the pattern @samp{foo}.  By comparison,
-omitting the @code{print} statement but retaining the curly braces makes an
+@command{awk} prints all lines matching the pattern @samp{li}.  By comparison,
+omitting the @code{print} statement but retaining the braces makes an
 empty action that does nothing (i.e., no lines are printed).
 
 @cindex @command{awk} programs, one-line examples
@@ -2681,15 +2967,15 @@ collection of useful, short programs to get you started.  Some of these
 programs contain constructs that haven't been covered yet. (The description
 of the program will give you a good idea of what is going on, but please
 read the rest of the @value{DOCUMENT} to become an @command{awk} expert!)
-Most of the examples use a data file named @file{data}.  This is just a
+Most of the examples use a @value{DF} named @file{data}.  This is just a
 placeholder; if you use these programs yourself, substitute
-your own file names for @file{data}.
+your own @value{FN}s for @file{data}.
 For future reference, note that there is often more than
 one way to do things in @command{awk}.  At some point, you may want
 to look back at these examples and see if
 you can come up with different ways to do the same things shown here:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Print the length of the longest input line:
 
@@ -2706,7 +2992,7 @@ awk 'length($0) > 80' data
 @end example
 
 The sole rule has a relational expression as its pattern and it has no
-action---so the default action, printing the record, is used.
+action---so it uses the default action, printing the record.
 
 @cindex @command{expand} utility
 @item
@@ -2773,7 +3059,7 @@ awk 'END @{ print NR @}' data
 @end example
 
 @item
-Print the even-numbered lines in the data file:
+Print the even-numbered lines in the @value{DF}:
 
 @example
 awk 'NR % 2 == 0' data
@@ -2789,9 +3075,9 @@ the program would print the odd-numbered lines.
 
 The @command{awk} utility reads the input files one line at a
 time.  For each line, @command{awk} tries the patterns of each of the rules.
-If several patterns match, then several actions are run in the order in
+If several patterns match, then several actions execute in the order in
 which they appear in the @command{awk} program.  If no patterns match, then
-no actions are run.
+no actions run.
 
 After processing all the rules that match the line (and perhaps there are none),
 @command{awk} reads the next line.  (However,
@@ -2815,30 +3101,24 @@ This program prints every line that contains the string
 @samp{12} @emph{or} the string @samp{21}.  If a line contains both
 strings, it is printed twice, once by each rule.
 
-This is what happens if we run this program on our two sample data files,
-@file{BBS-list} and @file{inventory-shipped}:
+This is what happens if we run this program on our two sample @value{DF}s,
+@file{mail-list} and @file{inventory-shipped}:
 
 @example
 $ @kbd{awk '/12/ @{ print $0 @}}
->      @kbd{/21/ @{ print $0 @}' BBS-list inventory-shipped}
-@print{} aardvark     555-5553     1200/300          B
-@print{} alpo-net     555-3412     2400/1200/300     A
-@print{} barfly       555-7685     1200/300          A
-@print{} bites        555-1675     2400/1200/300     A
-@print{} core         555-2912     1200/300          C
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sdace        555-3430     2400/1200/300     A
-@print{} sabafoo      555-2127     1200/300          C
-@print{} sabafoo      555-2127     1200/300          C
+>      @kbd{/21/ @{ print $0 @}' mail-list inventory-shipped}
+@print{} Anthony      555-3412     anthony.asserturo@@hotmail.com   A
+@print{} Camilla      555-2912     camilla.infusarum@@skynet.be     R
+@print{} Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @print{} Jan  21  36  64 620
 @print{} Apr  21  70  74 514
 @end example
 
 @noindent
-Note how the line beginning with @samp{sabafoo}
-in @file{BBS-list} was printed twice, once for each rule.
+Note how the line beginning with @samp{Jean-Paul}
+in @file{mail-list} was printed twice, once for each rule.
 
 @node More Complex
 @section A More Complex Example
@@ -2881,7 +3161,7 @@ the file. The fourth field identifies the group of the file.
 The fifth field contains the size of the file in bytes.  The
 sixth, seventh, and eighth fields contain the month, day, and time,
 respectively, that the file was last modified.  Finally, the ninth field
-contains the file name.@footnote{The @samp{LC_ALL=C} is
+contains the @value{FN}.@footnote{The @samp{LC_ALL=C} is
 needed to produce this traditional-style output from @command{ls}.}
 
 @c @cindex automatic initialization
@@ -2889,8 +3169,8 @@ needed to produce this traditional-style output from @command{ls}.}
 The @samp{$6 == "Nov"} in our @command{awk} program is an expression that
 tests whether the sixth field of the output from @w{@samp{ls -l}}
 matches the string @samp{Nov}.  Each time a line has the string
-@samp{Nov} for its sixth field, the action @samp{sum += $5} is
-performed.  This adds the fifth field (the file's size) to the variable
+@samp{Nov} for its sixth field, @command{awk} performs the action
+@samp{sum += $5}.  This adds the fifth field (the file's size) to the variable
 @code{sum}.  As a result, when @command{awk} has finished reading all the
 input lines, @code{sum} is the total of the sizes of the files whose
 lines matched the pattern.  (This works because @command{awk} variables
@@ -2917,7 +3197,7 @@ separate rule, like this:
 
 @example
 awk '/12/  @{ print $0 @}
-     /21/  @{ print $0 @}' BBS-list inventory-shipped
+     /21/  @{ print $0 @}' mail-list inventory-shipped
 @end example
 
 @cindex @command{gawk}, newlines in
@@ -2957,7 +3237,7 @@ We have generally not used backslash continuation in our sample programs.
 @command{gawk} places no limit on the
 length of a line, so backslash continuation is never strictly necessary;
 it just makes programs more readable.  For this same reason, as well as
-for clarity, we have kept most statements short in the sample programs
+for clarity, we have kept most statements short in the programs
 presented throughout the @value{DOCUMENT}.  Backslash continuation is
 most useful when your @command{awk} program is in a separate source file
 instead of entered from the command line.  You should also note that
@@ -3022,7 +3302,7 @@ $ gawk 'BEGIN @{ print "dont panic" # a friendly \
 >                                    BEGIN rule
 > @}'
 @error{} gawk: cmd. line:2:                BEGIN rule
-@error{} gawk: cmd. line:2:                ^ parse error
+@error{} gawk: cmd. line:2:                ^ syntax error
 @end example
 
 @noindent
@@ -3032,8 +3312,8 @@ noticed because it is ``hidden'' inside the comment. Thus, the
 @code{BEGIN} is noted as a syntax error.
 
 @cindex statements, multiple
-@cindex @code{;} (semicolon)
-@cindex semicolon (@code{;})
+@cindex @code{;} (semicolon), separating statements in actions
+@cindex semicolon (@code{;}), separating statements in actions
 When @command{awk} statements within one rule are short, you might want to put
 more than one of them on a line.  This is accomplished by separating the statements
 with a semicolon (@samp{;}).
@@ -3093,9 +3373,16 @@ used once, and thrown away.  Because @command{awk} programs are interpreted, you
 can avoid the (usually lengthy) compilation part of the typical
 edit-compile-test-debug cycle of software development.
 
+@cindex Brian Kernighan's @command{awk}
 Complex programs have been written in @command{awk}, including a complete
-retargetable assembler for eight-bit microprocessors (@pxref{Glossary}, for
-more information), and a microcode assembler for a special-purpose Prolog
+retargetable assembler for
+@ifclear FOR_PRINT
+eight-bit microprocessors (@pxref{Glossary}, for more information),
+@end ifclear
+@ifset FOR_PRINT
+eight-bit microprocessors,
+@end ifset
+and a microcode assembler for a special-purpose Prolog
 computer.
 While the original @command{awk}'s capabilities were strained by tasks
 of such complexity, modern versions are more capable.  Even Brian Kernighan's
@@ -3105,19 +3392,55 @@ that it has are much larger than they used to be.
 @cindex @command{awk} programs, complex
 If you find yourself writing @command{awk} scripts of more than, say, a few
 hundred lines, you might consider using a different programming
-language.  Emacs Lisp is a good choice if you need sophisticated string
-or pattern matching capabilities.  The shell is also good at string and
+language.
+The shell is good at string and
 pattern matching; in addition, it allows powerful use of the system
 utilities.  More conventional languages, such as C, C++, and Java, offer
 better facilities for system programming and for managing the complexity
-of large programs.  Programs in these languages may require more lines
+of large programs.
+Python offers a nice balance between high-level ease of programming and
+access to system facilities.
+Programs in these languages may require more lines
 of source code than the equivalent @command{awk} programs, but they are
 easier to maintain and usually run more efficiently.
 
+@node Intro Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Programs in @command{awk} consist of @var{pattern}-@var{action} pairs.
+
+@item
+Use either
+@samp{awk '@var{program}' @var{files}}
+or
+@samp{awk -f @var{program-file} @var{files}}
+to run @command{awk}.
+
+@item
+You may use the special @samp{#!} header line to create @command{awk}
+programs that are directly executable.
+
+@item
+Comments in @command{awk} programs start with @samp{#} and continue to
+the end of the same line.
+
+@item
+Be aware of quoting issues when writing @command{awk} programs as
+part of a larger shell script (or MS-Windows batch file).
+
+@item
+You may use backslash continuation to continue a source line.
+Lines are automatically continued after
+a comma, open brace, question mark, colon,
+@samp{||}, @samp{&&}, @code{do} and @code{else}.
+@end itemize
+
 @node Invoking Gawk
 @chapter Running @command{awk} and @command{gawk}
 
-This @value{CHAPTER} covers how to run awk, both POSIX-standard
+This @value{CHAPTER} covers how to run @command{awk}, both POSIX-standard
 and @command{gawk}-specific command-line options, and what
 @command{awk} and
 @command{gawk} do with non-option arguments.
@@ -3142,6 +3465,7 @@ things in this @value{CHAPTER} that don't interest you right now.
 * Loading Shared Libraries::    Loading shared libraries into your program.
 * Obsolete::                    Obsolete Options and/or features.
 * Undocumented::                Undocumented Options and Features.
+* Invoking Summary::            Invocation summary.
 @end menu
 
 @node Command Line
@@ -3155,10 +3479,10 @@ There are two ways to run @command{awk}---with an explicit program or with
 one or more program files.  Here are templates for both of them; items
 enclosed in [@dots{}] in these templates are optional:
 
-@example
-awk @r{[@var{options}]} -f progfile @r{[@code{--}]} @var{file} @dots{}
-awk @r{[@var{options}]} @r{[@code{--}]} '@var{program}' @var{file} @dots{}
-@end example
+@display
+@command{awk} [@var{options}] @option{-f} @var{progfile} [@option{--}] @var{file} @dots{}
+@command{awk} [@var{options}] [@option{--}] @code{'@var{program}'} @var{file} @dots{}
+@end display
 
 @cindex GNU long options
 @cindex long options
@@ -3174,7 +3498,7 @@ It is possible to invoke @command{awk} with an empty program:
 awk '' datafile1 datafile2
 @end example
 
-@cindex @code{--lint} option
+@cindex @option{--lint} option
 @noindent
 Doing so makes little sense, though; @command{awk} exits
 silently when given an empty program.
@@ -3214,43 +3538,27 @@ The following list describes options mandated by the POSIX standard:
 @table @code
 @item -F @var{fs}
 @itemx --field-separator @var{fs}
-@cindex @code{-F} option
-@cindex @code{--field-separator} option
+@cindex @option{-F} option
+@cindex @option{--field-separator} option
 @cindex @code{FS} variable, @code{--field-separator} option and
 Set the @code{FS} variable to @var{fs}
 (@pxref{Field Separators}).
 
 @item -f @var{source-file}
 @itemx --file @var{source-file}
-@cindex @code{-f} option
-@cindex @code{--file} option
+@cindex @option{-f} option
+@cindex @option{--file} option
 @cindex @command{awk} programs, location of
 Read @command{awk} program source from @var{source-file}
 instead of in the first non-option argument.
 This option may be given multiple times; the @command{awk}
-program consists of the concatenation the contents of
+program consists of the concatenation of the contents of
 each specified @var{source-file}.
 
-@item -i @var{source-file}
-@itemx --include @var{source-file}
-@cindex @code{-i} option
-@cindex @code{--include} option
-@cindex @command{awk} programs, location of
-Read @command{awk} source library from @var{source-file}.  This option is
-completely equivalent to using the @samp{@@include} directive inside
-your program.  This option is very
-similar to the @option{-f} option, but there are two important differences.
-First, when @option{-i} is used, the program source will not be loaded if it has
-been previously loaded, whereas the @option{-f} will always load the file.
-Second, because this option is intended to be used with code libraries,
-@command{gawk} does not recognize such files as constituting main program
-input.  Thus, after processing an @option{-i} argument, @command{gawk} still expects to
-find the main source code via the @option{-f} option or on the command-line.
-
 @item -v @var{var}=@var{val}
 @itemx --assign @var{var}=@var{val}
-@cindex @code{-v} option
-@cindex @code{--assign} option
+@cindex @option{-v} option
+@cindex @option{--assign} option
 @cindex variables, setting
 Set the variable @var{var} to the value @var{val} @emph{before}
 execution of the program begins.  Such variable values are available
@@ -3271,7 +3579,7 @@ predefined value you may have given.
 @end quotation
 
 @item -W @var{gawk-opt}
-@cindex @code{-W} option
+@cindex @option{-W} option
 Provide an implementation-specific option.
 This is the POSIX convention for providing implementation-specific options.
 These options
@@ -3290,8 +3598,8 @@ conventions.
 
 @cindex @code{-} (hyphen), filenames beginning with
 @cindex hyphen (@code{-}), filenames beginning with
-This is useful if you have file names that start with @samp{-},
-or in shell scripts, if you have file names that will be specified
+This is useful if you have @value{FN}s that start with @samp{-},
+or in shell scripts, if you have @value{FN}s that will be specified
 by the user that could start with @samp{-}.
 It is also useful for passing options on to the @command{awk}
 program; see @ref{Getopt Function}.
@@ -3301,47 +3609,52 @@ program; see @ref{Getopt Function}.
 
 The following list describes @command{gawk}-specific options:
 
-@table @code
-@item -b
-@itemx --characters-as-bytes
-@cindex @code{-b} option
-@cindex @code{--characters-as-bytes} option
+@c Have to use @asis here to get docbook to come out right.
+@table @asis
+@item @option{-b}
+@itemx @option{--characters-as-bytes}
+@cindex @option{-b} option
+@cindex @option{--characters-as-bytes} option
 Cause @command{gawk} to treat all input data as single-byte characters.
 In addition, all output written with @code{print} or @code{printf}
 are treated as single-byte characters.
 
 Normally, @command{gawk} follows the POSIX standard and attempts to process
-its input data according to the current locale. This can often involve
+its input data according to the current locale (@pxref{Locales}). This can often involve
 converting multibyte characters into wide characters (internally), and
 can lead to problems or confusion if the input data does not contain valid
 multibyte characters. This option is an easy way to tell @command{gawk}:
 ``hands off my data!''.
 
-@item -c
-@itemx --traditional
-@cindex @code{--c} option
-@cindex @code{--traditional} option
+@item @option{-c}
+@itemx @option{--traditional}
+@cindex @option{-c} option
+@cindex @option{--traditional} option
 @cindex compatibility mode (@command{gawk}), specifying
 Specify @dfn{compatibility mode}, in which the GNU extensions to
 the @command{awk} language are disabled, so that @command{gawk} behaves just
 like Brian Kernighan's version @command{awk}.
 @xref{POSIX/GNU},
-which summarizes the extensions.  Also see
+which summarizes the extensions.
+@ifclear FOR_PRINT
+Also see
 @ref{Compatibility Mode}.
+@end ifclear
 
-@item -C
-@itemx --copyright
-@cindex @code{-C} option
-@cindex @code{--copyright} option
+@item @option{-C}
+@itemx @option{--copyright}
+@cindex @option{-C} option
+@cindex @option{--copyright} option
 @cindex GPL (General Public License), printing
 Print the short version of the General Public License and then exit.
 
-@item -d@r{[}@var{file}@r{]}
-@itemx --dump-variables@r{[}=@var{file}@r{]}
-@cindex @code{-d} option
-@cindex @code{--dump-variables} option
-@cindex @code{awkvars.out} file
-@cindex files, @code{awkvars.out}
+@item @option{-d}[@var{file}]
+@itemx @option{--dump-variables}[@code{=}@var{file}]
+@cindex @option{-d} option
+@cindex @option{--dump-variables} option
+@cindex dump all variables of a program
+@cindex @file{awkvars.out} file
+@cindex files, @file{awkvars.out}
 @cindex variables, global, printing list of
 Print a sorted list of global variables, their types, and final values
 to @var{file}.  If no @var{file} is provided, print this
@@ -3358,23 +3671,23 @@ inadvertently use global variables that you meant to be local.
 (This is a particularly easy mistake to make with simple variable
 names like @code{i}, @code{j}, etc.)
 
-@item -D@r{[}@var{file}@r{]}
-@itemx --debug=@r{[}@var{file}@r{]}
-@cindex @code{-D} option
-@cindex @code{--debug} option
+@item @option{-D}[@var{file}]
+@itemx @option{--debug}[@code{=}@var{file}]
+@cindex @option{-D} option
+@cindex @option{--debug} option
 @cindex @command{awk} debugging, enabling
 Enable debugging of @command{awk} programs
 (@pxref{Debugging}).
-By default, the debugger reads commands interactively from the terminal.
+By default, the debugger reads commands interactively from the keyboard.
 The optional @var{file} argument allows you to specify a file with a list
 of commands for the debugger to execute non-interactively.
 No space is allowed between the @option{-D} and @var{file}, if
 @var{file} is supplied.
 
-@item -e @var{program-text}
-@itemx --source @var{program-text}
-@cindex @code{-e} option
-@cindex @code{--source} option
+@item @option{-e} @var{program-text}
+@itemx @option{--source} @var{program-text}
+@cindex @option{-e} option
+@cindex @option{--source} option
 @cindex source code, mixing
 Provide program source code in the @var{program-text}.
 This option allows you to mix source code in files with source
@@ -3383,16 +3696,16 @@ This is particularly useful
 when you have library functions that you want to use from your command-line
 programs (@pxref{AWKPATH Variable}).
 
-@item -E @var{file}
-@itemx --exec @var{file}
-@cindex @code{-E} option
-@cindex @code{--exec} option
+@item @option{-E} @var{file}
+@itemx @option{--exec} @var{file}
+@cindex @option{-E} option
+@cindex @option{--exec} option
 @cindex @command{awk} programs, location of
 @cindex CGI, @command{awk} scripts for
 Similar to @option{-f}, read @command{awk} program text from @var{file}.
 There are two differences from @option{-f}:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 This option terminates option processing; anything
 else on the command line is passed on directly to the @command{awk} program.
@@ -3414,48 +3727,69 @@ with @samp{#!} scripts (@pxref{Executable Scripts}), like so:
 @var{awk program here @dots{}}
 @end example
 
-@item -g
-@itemx --gen-pot
-@cindex @code{-g} option
-@cindex @code{--gen-pot} option
+@item @option{-g}
+@itemx @option{--gen-pot}
+@cindex @option{-g} option
+@cindex @option{--gen-pot} option
 @cindex portable object files, generating
 @cindex files, portable object, generating
 Analyze the source program and
-generate a GNU @code{gettext} Portable Object Template file on standard
+generate a GNU @command{gettext} Portable Object Template file on standard
 output for all string constants that have been marked for translation.
 @xref{Internationalization},
 for information about this option.
 
-@item -h
-@itemx --help
-@cindex @code{-h} option
-@cindex @code{--help} option
+@item @option{-h}
+@itemx @option{--help}
+@cindex @option{-h} option
+@cindex @option{--help} option
 @cindex GNU long options, printing list of
 @cindex options, printing list of
 @cindex printing, list of options
 Print a ``usage'' message summarizing the short and long style options
 that @command{gawk} accepts and then exit.
 
-@item -l @var{lib}
-@itemx --load @var{lib}
-@cindex @code{-l} option
-@cindex @code{--load} option
-@cindex loading, library
-Load a shared library @var{lib}. This searches for the library using the @env{AWKLIBPATH}
+@item @option{-i} @var{source-file}
+@itemx @option{--include} @var{source-file}
+@cindex @option{-i} option
+@cindex @option{--include} option
+@cindex @command{awk} programs, location of
+Read @command{awk} source library from @var{source-file}.  This option
+is completely equivalent to using the @code{@@include} directive inside
+your program.  This option is very similar to the @option{-f} option,
+but there are two important differences.  First, when @option{-i} is
+used, the program source is not loaded if it has been previously
+loaded, whereas with @option{-f}, @command{gawk} always loads the file.
+Second, because this option is intended to be used with code libraries,
+@command{gawk} does not recognize such files as constituting main program
+input.  Thus, after processing an @option{-i} argument, @command{gawk}
+still expects to find the main source code via the @option{-f} option
+or on the command-line.
+
+@item @option{-l} @var{ext}
+@itemx @option{--load} @var{ext}
+@cindex @option{-l} option
+@cindex @option{--load} option
+@cindex loading, extensions
+Load a dynamic extension named @var{ext}. Extensions
+are stored as system shared libraries.
+This option searches for the library using the @env{AWKLIBPATH}
 environment variable.  The correct library suffix for your platform will be
-supplied by default, so it need not be specified in the library name.
-The library initialization routine should be named @code{dl_load()}.
-An alternative is to use the @samp{@@load} keyword inside the program to load
-a shared library.
-
-@item -L @r{[}value@r{]}
-@itemx --lint@r{[}=value@r{]}
-@cindex @code{-l} option
-@cindex @code{--lint} option
+supplied by default, so it need not be specified in the extension name.
+The extension initialization routine should be named @code{dl_load()}.
+An alternative is to use the @code{@@load} keyword inside the program to load
+a shared library.  This feature is described in detail in @ref{Dynamic Extensions}.
+
+@item @option{-L}[@var{value}]
+@itemx @option{--lint}[@code{=}@var{value}]
+@cindex @option{-l} option
+@cindex @option{--lint} option
 @cindex lint checking, issuing warnings
 @cindex warnings, issuing
 Warn about constructs that are dubious or nonportable to
 other @command{awk} implementations.
+No space is allowed between the @option{-D} and @var{value}, if
+@var{value} is supplied.
 Some warnings are issued when @command{gawk} first reads your program.  Others
 are issued at runtime, as your program executes.
 With an optional argument of @samp{fatal},
@@ -3471,18 +3805,18 @@ when eliminating problems pointed out by @option{--lint}, you should take
 care to search for all occurrences of each inappropriate construct. As
 @command{awk} programs are usually short, doing so is not burdensome.
 
-@item -M
-@itemx --bignum
-@cindex @code{-M} option
-@cindex @code{--bignum} option
+@item @option{-M}
+@itemx @option{--bignum}
+@cindex @option{-M} option
+@cindex @option{--bignum} option
 Force arbitrary precision arithmetic on numbers. This option has no effect
 if @command{gawk} is not compiled to use the GNU MPFR and MP libraries
 (@pxref{Arbitrary Precision Arithmetic}).
 
-@item -n
-@itemx --non-decimal-data
-@cindex @code{-n} option
-@cindex @code{--non-decimal-data} option
+@item @option{-n}
+@itemx @option{--non-decimal-data}
+@cindex @option{-n} option
+@cindex @option{--non-decimal-data} option
 @cindex hexadecimal values@comma{} enabling interpretation of
 @cindex octal values@comma{} enabling interpretation of
 @cindex troubleshooting, @code{--non-decimal-data} option
@@ -3495,52 +3829,59 @@ This option can severely break old programs.
 Use with care.
 @end quotation
 
-@item -N
-@itemx --use-lc-numeric
-@cindex @code{-N} option
-@cindex @code{--use-lc-numeric} option
+@item @option{-N}
+@itemx @option{--use-lc-numeric}
+@cindex @option{-N} option
+@cindex @option{--use-lc-numeric} option
 Force the use of the locale's decimal point character
 when parsing numeric input data (@pxref{Locales}).
 
-@item -o@r{[}@var{file}@r{]}
-@itemx --pretty-print@r{[}=@var{file}@r{]}
-@cindex @code{-o} option
-@cindex @code{--pretty-print} option
+@item @option{-o}[@var{file}]
+@itemx @option{--pretty-print}[@code{=}@var{file}]
+@cindex @option{-o} option
+@cindex @option{--pretty-print} option
 Enable pretty-printing of @command{awk} programs.
-By default, output program is created in a file named @file{awkprof.out}.
+By default, output program is created in a file named @file{awkprof.out}
+(@pxref{Profiling}).
 The optional @var{file} argument allows you to specify a different
-file name for the output.
+@value{FN} for the output.
 No space is allowed between the @option{-o} and @var{file}, if
 @var{file} is supplied.
 
-@item -O
-@itemx --optimize
-@cindex @code{--optimize} option
-@cindex @code{-O} option
+@quotation NOTE
+Due to the way @command{gawk} has evolved, with this option
+your program is still executed.  This will change in the
+next major release such that @command{gawk} will only
+pretty-print the program and not run it.
+@end quotation
+
+@item @option{-O}
+@itemx @option{--optimize}
+@cindex @option{--optimize} option
+@cindex @option{-O} option
 Enable some optimizations on the internal representation of the program.
-At the moment this includes just simple constant folding. The @command{gawk}
-maintainer hopes to add more optimizations over time.
+At the moment this includes just simple constant folding.
 
-@item -p@r{[}@var{file}@r{]}
-@itemx --profile@r{[}=@var{file}@r{]}
-@cindex @code{-p} option
-@cindex @code{--profile} option
+@item @option{-p}[@var{file}]
+@itemx @option{--profile}[@code{=}@var{file}]
+@cindex @option{-p} option
+@cindex @option{--profile} option
 @cindex @command{awk} profiling, enabling
 Enable profiling of @command{awk} programs
 (@pxref{Profiling}).
 By default, profiles are created in a file named @file{awkprof.out}.
 The optional @var{file} argument allows you to specify a different
-file name for the profile file.
+@value{FN} for the profile file.
 No space is allowed between the @option{-p} and @var{file}, if
 @var{file} is supplied.
 
 The profile contains execution counts for each statement in the program
 in the left margin, and function call counts for each function.
 
-@item -P
-@itemx --posix
-@cindex @code{-P} option
-@cindex @code{--posix} option
+@item @option{-P}
+@itemx @option{--posix}
+@cindex @option{-P} option
+@cindex @option{--posix} option
 @cindex POSIX mode
 @cindex @command{gawk}, extensions@comma{} disabling
 Operate in strict POSIX mode.  This disables all @command{gawk}
@@ -3552,7 +3893,7 @@ Also,
 the following additional
 restrictions apply:
 
-@itemize @bullet
+@itemize @value{BULLET}
 
 @cindex newlines
 @cindex whitespace, newlines as
@@ -3581,28 +3922,28 @@ data (@pxref{Locales}).
 
 @c @cindex automatic warnings
 @c @cindex warnings, automatic
-@cindex @code{--traditional} option, @code{--posix} option and
-@cindex @code{--posix} option, @code{--traditional} option and
+@cindex @option{--traditional} option, @code{--posix} option and
+@cindex @option{--posix} option, @code{--traditional} option and
 If you supply both @option{--traditional} and @option{--posix} on the
 command line, @option{--posix} takes precedence. @command{gawk}
-also issues a warning if both options are supplied.
+issues a warning if both options are supplied.
 
-@item -r
-@itemx --re-interval
-@cindex @code{-r} option
-@cindex @code{--re-interval} option
+@item @option{-r}
+@itemx @option{--re-interval}
+@cindex @option{-r} option
+@cindex @option{--re-interval} option
 @cindex regular expressions, interval expressions and
 Allow interval expressions
 (@pxref{Regexp Operators})
 in regexps.
 This is now @command{gawk}'s default behavior.
 Nevertheless, this option remains both for backward compatibility,
-and for use in combination with the @option{--traditional} option.
+and for use in combination with @option{--traditional}.
 
-@item -S
-@itemx --sandbox
-@cindex @code{-S} option
-@cindex @code{--sandbox} option
+@item @option{-S}
+@itemx @option{--sandbox}
+@cindex @option{-S} option
+@cindex @option{--sandbox} option
 @cindex sandbox mode
 Disable the @code{system()} function,
 input redirections with @code{getline},
@@ -3610,20 +3951,20 @@ output redirections with @code{print} and @code{printf},
 and dynamic extensions.
 This is particularly useful when you want to run @command{awk} scripts
 from questionable sources and need to make sure the scripts
-can't access your system (other than the specified input data file).
+can't access your system (other than the specified input @value{DF}).
 
-@item -t
-@itemx --lint-old
-@cindex @code{--L} option
-@cindex @code{--lint-old} option
+@item @option{-t}
+@itemx @option{--lint-old}
+@cindex @option{-L} option
+@cindex @option{--lint-old} option
 Warn about constructs that are not available in the original version of
 @command{awk} from Version 7 Unix
 (@pxref{V7/SVR3.1}).
 
-@item -V
-@itemx --version
-@cindex @code{-V} option
-@cindex @code{--version} option
+@item @option{-V}
+@itemx @option{--version}
+@cindex @option{-V} option
+@cindex @option{--version} option
 @cindex @command{gawk}, versions of, information about@comma{} printing
 Print version information for this particular copy of @command{gawk}.
 This allows you to determine if your copy of @command{gawk} is up to date
@@ -3637,14 +3978,14 @@ As long as program text has been supplied,
 any other options are flagged as invalid with a warning message but
 are otherwise ignored.
 
-@cindex @code{-F} option, @code{-Ft} sets @code{FS} to TAB
+@cindex @option{-F} option, @option{-Ft} sets @code{FS} to TAB
 In compatibility mode, as a special case, if the value of @var{fs} supplied
 to the @option{-F} option is @samp{t}, then @code{FS} is set to the TAB
 character (@code{"\t"}).  This is true only for @option{--traditional} and not
 for @option{--posix}
 (@pxref{Field Separators}).
 
-@cindex @code{-f} option, multiple uses
+@cindex @option{-f} option, multiple uses
 The @option{-f} option may be used more than once on the command line.
 If it is, @command{awk} reads its program source from all of the named files, as
 if they had been concatenated together into one big file.  This is
@@ -3656,22 +3997,22 @@ of having to be included into each individual program.
 function names must be unique.)
 
 With standard @command{awk}, library functions can still be used, even
-if the program is entered at the terminal,
+if the program is entered at the keyboard,
 by specifying @samp{-f /dev/tty}.  After typing your program,
 type @kbd{Ctrl-d} (the end-of-file character) to terminate it.
 (You may also use @samp{-f -} to read program source from the standard
 input but then you will not be able to also use the standard input as a
 source of data.)
 
-Because it is clumsy using the standard @command{awk} mechanisms to mix source
-file and command-line @command{awk} programs, @command{gawk} provides the
-@option{--source} option.  This does not require you to pre-empt the standard
-input for your source code; it allows you to easily mix command-line
-and library source code
-(@pxref{AWKPATH Variable}).
-The @option{--source} option may also be used multiple times on the command line.
+Because it is clumsy using the standard @command{awk} mechanisms to mix
+source file and command-line @command{awk} programs, @command{gawk}
+provides the @option{--source} option.  This does not require you to
+pre-empt the standard input for your source code; it allows you to easily
+mix command-line and library source code (@pxref{AWKPATH Variable}).
+As with @option{-f}, the @option{--source} and @option{--include}
+options may also be used multiple times on the command line.
 
-@cindex @code{--source} option
+@cindex @option{--source} option
 If no @option{-f} or @option{--source} option is specified, then @command{gawk}
 uses the first non-option command-line argument as the text of the
 program source code.
@@ -3681,7 +4022,7 @@ program source code.
 @cindex POSIX mode
 If the environment variable @env{POSIXLY_CORRECT} exists,
 then @command{gawk} behaves in strict POSIX mode, exactly as if
-you had supplied the @option{--posix} command-line option.
+you had supplied @option{--posix}.
 Many GNU programs look for this environment variable to suppress
 extensions that conflict with POSIX, but @command{gawk} behaves
 differently: it suppresses all extensions, even those that do not
@@ -3730,6 +4071,7 @@ file at all.
 
 @cindex @command{gawk}, @code{ARGIND} variable in
 @cindex @code{ARGIND} variable, command-line arguments
+@cindex @code{ARGV} array, indexing into
 @cindex @code{ARGC}/@code{ARGV} variables, command-line arguments
 All these arguments are made available to your @command{awk} program in the
 @code{ARGV} array (@pxref{Built-in Variables}).  Command-line options
@@ -3740,9 +4082,10 @@ sets the variable @code{ARGIND} to the index in @code{ARGV} of the
 current element.
 
 @cindex input files, variable assignments and
-The distinction between file name arguments and variable-assignment
+@cindex variable assignments and input files
+The distinction between @value{FN} arguments and variable-assignment
 arguments is made when @command{awk} is about to open the next input file.
-At that point in execution, it checks the file name to see whether
+At that point in execution, it checks the @value{FN} to see whether
 it is really a variable assignment; if so, @command{awk} sets the variable
 instead of reading a file.
 
@@ -3758,8 +4101,8 @@ The variable values given on the command line are processed for escape
 sequences (@pxref{Escape Sequences}).
 @value{DARKCORNER}
 
-In some earlier implementations of @command{awk}, when a variable assignment
-occurred before any file names, the assignment would happen @emph{before}
+In some very early implementations of @command{awk}, when a variable assignment
+occurred before any @value{FN}s, the assignment would happen @emph{before}
 the @code{BEGIN} rule was executed.  @command{awk}'s behavior was thus
 inconsistent; some command-line assignments were available inside the
 @code{BEGIN} rule, while others were not.  Unfortunately,
@@ -3770,8 +4113,8 @@ upon the old behavior.
 
 The variable assignment feature is most useful for assigning to variables
 such as @code{RS}, @code{OFS}, and @code{ORS}, which control input and
-output formats before scanning the data files.  It is also useful for
-controlling state if multiple passes are needed over a data file.  For
+output formats, before scanning the @value{DF}s.  It is also useful for
+controlling state if multiple passes are needed over a @value{DF}.  For
 example:
 
 @cindex files, multiple passes over
@@ -3807,16 +4150,17 @@ You may also use @code{"-"} to name standard input when reading
 files with @code{getline} (@pxref{Getline/File}).
 
 In addition, @command{gawk} allows you to specify the special
-file name @file{/dev/stdin}, both on the command line and
+@value{FN} @file{/dev/stdin}, both on the command line and
 with @code{getline}.
 Some other versions of @command{awk} also support this, but it
 is not standard.
 (Some operating systems provide a @file{/dev/stdin} file
-in the file system, however, @command{gawk} always processes
-this file name itself.)
+in the file system; however, @command{gawk} always processes
+this @value{FN} itself.)
 
 @node Environment Variables
 @section The Environment Variables @command{gawk} Uses
+@cindex environment variables used by @command{gawk}
 
 A number of environment variables influence how @command{gawk}
 behaves.
@@ -3832,8 +4176,7 @@ behaves.
 @node AWKPATH Variable
 @subsection The @env{AWKPATH} Environment Variable
 @cindex @env{AWKPATH} environment variable
-@cindex directories, searching
-@cindex search paths
+@cindex directories, searching for source files
 @cindex search paths, for source files
 @cindex differences in @command{awk} and @command{gawk}, @code{AWKPATH} environment variable
 @ifinfo
@@ -3843,14 +4186,14 @@ on the command-line with the @option{-f} option.
 In most @command{awk}
 implementations, you must supply a precise path name for each program
 file, unless the file is in the current directory.
-But in @command{gawk}, if the file name supplied to the @option{-f}
+But in @command{gawk}, if the @value{FN} supplied to the @option{-f}
 or @option{-i} options
-does not contain a @samp{/}, then @command{gawk} searches a list of
+does not contain a directory separator @samp{/}, then @command{gawk} searches a list of
 directories (called the @dfn{search path}), one by one, looking for a
 file with the specified name.
 
 The search path is a string consisting of directory names
-separated by colons.  @command{gawk} gets its search path from the
+separated by colons@footnote{Semicolons on MS-Windows and MS-DOS.}.  @command{gawk} gets its search path from the
 @env{AWKPATH} environment variable.  If that variable does not exist,
 @command{gawk} uses a default path,
 @samp{.:/usr/local/share/awk}.@footnote{Your version of @command{gawk}
@@ -3860,10 +4203,10 @@ directory is the value of @samp{$(datadir)} generated when
 @command{gawk} was configured.  You probably don't need to worry about this,
 though.}
 
-The search path feature is particularly useful for building libraries
+The search path feature is particularly helpful for building libraries
 of useful @command{awk} functions.  The library files can be placed in a
 standard directory in the default path and then specified on
-the command line with a short file name.  Otherwise, the full file name
+the command line with a short @value{FN}.  Otherwise, the full @value{FN}
 would have to be typed for each file.
 
 By using the @option{-i} option, or the @option{--source} and @option{-f} options, your command-line
@@ -3874,17 +4217,20 @@ This is true for both @option{--traditional} and @option{--posix}.
 @xref{Options}.
 
 If the source code is not found after the initial search, the path is searched
-again after adding the default @samp{.awk} suffix to the filename.
+again after adding the default @samp{.awk} suffix to the @value{FN}.
 
 @quotation NOTE
+@c 4/2014:
+@c using @samp{.} to get quotes, since @file{} no longer supplies them.
 To include
 the current directory in the path, either place
-@file{.} explicitly in the path or write a null entry in the
+@samp{.} explicitly in the path or write a null entry in the
 path.  (A null entry is indicated by starting or ending the path with a
-colon or by placing two colons next to each other (@samp{::}).)
+colon or by placing two colons next to each other [@samp{::}].)
 This path search mechanism is similar
 to the shell's.
-@c someday, @cite{The Bourne Again Shell}....
+(See @uref{http://www.gnu.org/software/bash/manual/,
+@cite{The Bourne-Again SHell manual}.})
 
 However, @command{gawk} always looks in the current directory @emph{before}
 searching @env{AWKPATH}, so there is no real reason to include
@@ -3896,7 +4242,7 @@ the current directory in the search path.
 If @env{AWKPATH} is not defined in the
 environment, @command{gawk} places its default search path into
 @code{ENVIRON["AWKPATH"]}. This makes it easy to determine
-the actual search path that @command{gawk} will use
+the actual search path that @command{gawk} used
 from within an @command{awk} program.
 
 While you can change @code{ENVIRON["AWKPATH"]} within your @command{awk}
@@ -3908,19 +4254,18 @@ found, and @command{gawk} no longer needs to use @env{AWKPATH}.
 @node AWKLIBPATH Variable
 @subsection The @env{AWKLIBPATH} Environment Variable
 @cindex @env{AWKLIBPATH} environment variable
-@cindex directories, searching
-@cindex search paths
-@cindex search paths, for shared libraries
+@cindex directories, searching for loadable extensions
+@cindex search paths, for loadable extensions
 @cindex differences in @command{awk} and @command{gawk}, @code{AWKLIBPATH} environment variable
 
 The @env{AWKLIBPATH} environment variable is similar to the @env{AWKPATH}
-variable, but it is used to search for shared libraries specified
-with the @option{-l} option rather than for source files.  If the library
-is not found, the path is searched again after adding the appropriate
-shared library suffix for the platform.  For example, on GNU/Linux systems,
-the suffix @samp{.so} is used.
-The search path specified is also used for libraries loaded via the
-@samp{@@load} keyword (@pxref{Loading Shared Libraries}).
+variable, but it is used to search for loadable extensions (stored as
+system shared libraries) specified with the @option{-l} option rather
+than for source files.  If the extension is not found, the path is
+searched again after adding the appropriate shared library suffix for
+the platform.  For example, on GNU/Linux systems, the suffix @samp{.so}
+is used.  The search path specified is also used for extensions loaded
+via the @code{@@load} keyword (@pxref{Loading Shared Libraries}).
 
 @node Other Environment Variables
 @subsection Other Environment Variables
@@ -3936,7 +4281,7 @@ mode, disabling all traditional and GNU extensions.
 @xref{Options}.
 
 @item GAWK_SOCK_RETRIES
-Controls the number of time @command{gawk} will attempt to
+Controls the number of times @command{gawk} attempts to
 retry a two-way TCP/IP (socket) connection before giving up.
 @xref{TCP/IP Networking}.
 
@@ -3957,9 +4302,18 @@ for use by the @command{gawk} developers for testing and tuning.
 They are subject to change. The variables are:
 
 @table @env
+@item AWKBUFSIZE
+This variable only affects @command{gawk} on POSIX-compliant systems.
+With a value of @samp{exact}, @command{gawk} uses the size of each input
+file as the size of the memory buffer to allocate for I/O. Otherwise,
+the value should be a number, and @command{gawk} uses that number as
+the size of the buffer to allocate.  (When this variable is not set,
+@command{gawk} uses the smaller of the file's size and the ``default''
+blocksize, which is usually the file systems I/O blocksize.)
+
 @item AWK_HASH
 If this variable exists with a value of @samp{gst}, @command{gawk}
-will switch to using the hash function from GNU Smalltalk for
+switches to using the hash function from GNU Smalltalk for
 managing arrays.
 This function may be marginally faster than the standard function.
 
@@ -3984,6 +4338,11 @@ two regexp matchers that @command{gawk} uses internally. (There aren't
 supposed to be differences, but occasionally theory and practice don't
 coordinate with each other.)
 
+@item GAWK_NO_PP_RUN
+If this variable exists, then when invoked with the @option{--pretty-print}
+option, @command{gawk} skips running the program.  This variable will
+not survive into the next major release.
+
 @item GAWK_STACKSIZE
 This specifies the amount by which @command{gawk} should grow its
 internal evaluation stack, when needed.
@@ -4028,13 +4387,13 @@ to @code{EXIT_FAILURE}.
 
 This @value{SECTION} describes a feature that is specific to @command{gawk}.
 
-The @samp{@@include} keyword can be used to read external @command{awk} source
+The @code{@@include} keyword can be used to read external @command{awk} source
 files.  This gives you the ability to split large @command{awk} source files
 into smaller, more manageable pieces, and also lets you reuse common @command{awk}
 code from various @command{awk} scripts.  In other words, you can group
 together @command{awk} functions, used to carry out specific tasks,
 into external files. These files can be used just like function libraries,
-using the @samp{@@include} keyword in conjunction with the @env{AWKPATH}
+using the @code{@@include} keyword in conjunction with the @env{AWKPATH}
 environment variable.  Note that source files may also be included
 using the @option{-i} option.
 
@@ -4068,14 +4427,14 @@ $ @kbd{gawk -f test2}
 @end example
 
 @code{gawk} runs the @file{test2} script which includes @file{test1}
-using the @samp{@@include}
+using the @code{@@include}
 keyword.  So, to include external @command{awk} source files you just
-use @samp{@@include} followed by the name of the file to be included,
+use @code{@@include} followed by the name of the file to be included,
 enclosed in double quotes.
 
 @quotation NOTE
-Keep in mind that this is a language construct and the file name cannot
-be a string variable, but rather just a literal string in double quotes.
+Keep in mind that this is a language construct and the @value{FN} cannot
+be a string variable, but rather just a literal string constant in double quotes.
 @end quotation
 
 The files to be included may be nested; e.g., given a third
@@ -4099,7 +4458,7 @@ $ @kbd{gawk -f test3}
 @print{} This is file test3.
 @end example
 
-The file name can, of course, be a pathname. For example:
+The @value{FN} can, of course, be a pathname. For example:
 
 @example
 @@include "../io_funcs"
@@ -4114,49 +4473,50 @@ or:
 
 @noindent
 are valid. The @code{AWKPATH} environment variable can be of great
-value when using @samp{@@include}. The same rules for the use
+value when using @code{@@include}. The same rules for the use
 of the @code{AWKPATH} variable in command-line file searches
 (@pxref{AWKPATH Variable}) apply to
-@samp{@@include} also.
+@code{@@include} also.
 
 This is very helpful in constructing @command{gawk} function libraries.
 If you have a large script with useful, general purpose @command{awk}
 functions, you can break it down into library files and put those files
 in a special directory.  You can then include those ``libraries,'' using
 either the full pathnames of the files, or by setting the @code{AWKPATH}
-environment variable accordingly and then using @samp{@@include} with
+environment variable accordingly and then using @code{@@include} with
 just the file part of the full pathname. Of course you can have more
 than one directory to keep library files; the more complex the working
 environment is, the more directories you may need to organize the files
 to be included.
 
 Given the ability to specify multiple @option{-f} options, the
-@samp{@@include} mechanism is not strictly necessary.
-However, the @samp{@@include} keyword
+@code{@@include} mechanism is not strictly necessary.
+However, the @code{@@include} keyword
 can help you in constructing self-contained @command{gawk} programs,
 thus reducing the need for writing complex and tedious command lines.
-In particular, @samp{@@include} is very useful for writing CGI scripts
+In particular, @code{@@include} is very useful for writing CGI scripts
 to be run from web pages.
 
 As mentioned in @ref{AWKPATH Variable}, the current directory is always
 searched first for source files, before searching in @env{AWKPATH},
-and this also applies to files named with @samp{@@include}.
+and this also applies to files named with @code{@@include}.
 
 @node Loading Shared Libraries
-@section Loading Shared Libraries Into Your Program
+@section Loading Dynamic Extensions Into Your Program
 
 This @value{SECTION} describes a feature that is specific to @command{gawk}.
 
-The @samp{@@load} keyword can be used to read external @command{awk} shared
-libraries.  This allows you to link in compiled code that may offer superior
+The @code{@@load} keyword can be used to read external @command{awk} extensions
+(stored as system shared libraries).
+This allows you to link in compiled code that may offer superior
 performance and/or give you access to extended capabilities not supported 
 by the @command{awk} language.  The @env{AWKLIBPATH} variable is used to
-search for the shared library.  Using @samp{@@load} is completely equivalent
+search for the extension.  Using @code{@@load} is completely equivalent
 to using the @option{-l} command-line option.
 
-If the shared library is not initially found in @env{AWKLIBPATH}, another
+If the extension is not initially found in @env{AWKLIBPATH}, another
 search is conducted after appending the platform's default shared library
-suffix to the filename.  For example, on GNU/Linux systems, the suffix
+suffix to the @value{FN}.  For example, on GNU/Linux systems, the suffix
 @samp{.so} is used.
 
 @example
@@ -4174,16 +4534,17 @@ $ @kbd{gawk -lordchr 'BEGIN @{print chr(65)@}'}
 
 @noindent
 For command-line usage, the @option{-l} option is more convenient,
-but @samp{@@load} is useful for embedding inside an @command{awk} source file
-that requires access to a shared library.
+but @code{@@load} is useful for embedding inside an @command{awk} source file
+that requires access to an extension.
 
 @ref{Dynamic Extensions}, describes how to write extensions (in C or C++)
-that can be loaded with either @samp{@@load} or the @option{-l} option.
+that can be loaded with either @code{@@load} or the @option{-l} option.
 
 @node Obsolete
 @section Obsolete Options and/or Features
 
-@cindex features, advanced, See advanced features
+@c update this section for each release!
+
 @cindex options, deprecated
 @cindex features, deprecated
 @cindex obsolete features
@@ -4192,12 +4553,9 @@ previous releases of @command{gawk} that are either not available in the
 current version or that are still supported but deprecated (meaning that
 they will @emph{not} be in the next release).
 
-@c update this section for each release!
-
-@cindex @code{PROCINFO} array
 The process-related special files @file{/dev/pid}, @file{/dev/ppid},
 @file{/dev/pgrpid}, and @file{/dev/user} were deprecated in @command{gawk}
-3.1, but still worked.  As of version 4.0, they are no longer
+3.1, but still worked.  As of @value{PVERSION} 4.0, they are no longer
 interpreted specially by @command{gawk}.  (Use @code{PROCINFO} instead;
 see @ref{Auto-set}.)
 
@@ -4220,6 +4578,7 @@ in case some option becomes obsolete in a future version of @command{gawk}.
 @author Obi-Wan
 @end quotation
 
+@cindex shells, sea
 This @value{SECTION} intentionally left
 blank.
 
@@ -4232,7 +4591,7 @@ blank.
 @table @code
 @item -W nostalgia
 @itemx --nostalgia
-Print the message @code{"awk: bailing out near line 1"} and dump core.
+Print the message @samp{awk: bailing out near line 1} and dump core.
 This option was inspired by the common behavior of very early versions of
 Unix @command{awk} and by a t--shirt.
 The message is @emph{not} subject to translation in non-English locales.
@@ -4276,9 +4635,61 @@ long-undocumented ``feature'' of Unix @code{awk}.
 
 @end ignore
 
+@node Invoking Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Use either
+@samp{awk '@var{program}' @var{files}}
+or
+@samp{awk -f @var{program-file} @var{files}}
+to run @command{awk}.
+
+@item
+The three standard @command{awk} options are @option{-f}, @option{-F}
+and @option{-v}.  @command{gawk} supplies these and many others, as well
+as corresponding GNU-style long options.
+
+@item
+Non-option command-line arguments are usually treated as @value{FN}s,
+unless they have the form @samp{@var{var}=@var{value}}, in which case
+they are taken as variable assignments to be performed at that point
+in processing the input.
+
+@item
+All non-option command-line arguments, excluding the program text,
+are placed in the @code{ARGV} array.  Adjusting @code{ARGC} and @code{ARGV}
+affects how @command{awk} processes input.
+
+@item
+You can use a single minus sign (@samp{-}) to refer to standard input
+on the command line.
+
+@item
+@command{gawk} pays attention to a number of environment variables.
+@env{AWKPATH}, @env{AWKLIBPATH}, and @env{POSIXLY_CORRECT} are the
+most important ones.
+
+@item
+@command{gawk}'s exit status conveys information to the program
+that invoked it. Use the @code{exit} statement from within
+an @command{awk} program to set the exit status.
+
+@item
+@command{gawk} allows you to include other @command{awk} source files into
+your program using the @code{@@include} statement and/or the @option{-i}
+and @option{-f} command-line options.
+
+@item
+@command{gawk} allows you to load additional functions written in C
+or C++ using the @code{@@load} statement and/or the @option{-l} option.
+(This advanced feature is described later on in @ref{Dynamic Extensions}.)
+@end itemize
+
 @node Regexp
 @chapter Regular Expressions
-@cindex regexp, See regular expressions
+@cindex regexp
 @c STARTOFRANGE regexp
 @cindex regular expressions
 
@@ -4287,8 +4698,8 @@ set of strings.
 Because regular expressions are such a fundamental part of @command{awk}
 programming, their format and use deserve a separate @value{CHAPTER}.
 
-@cindex forward slash (@code{/})
-@cindex @code{/} (forward slash)
+@cindex forward slash (@code{/}) to enclose regular expressions
+@cindex @code{/} (forward slash) to enclose regular expressions
 A regular expression enclosed in slashes (@samp{/})
 is an @command{awk} pattern that matches every input record whose text
 belongs to that set.
@@ -4314,6 +4725,7 @@ regular expressions work, we present more complicated instances.
 * Case-sensitivity::            How to do case-insensitive matching.
 * Leftmost Longest::            How much text matches.
 * Computed Regexps::            Using Dynamic Regexps.
+* Regexp Summary::              Regular expressions summary.
 @end menu
 
 @node Regexp Usage
@@ -4324,15 +4736,15 @@ A regular expression can be used as a pattern by enclosing it in
 slashes.  Then the regular expression is tested against the
 entire text of each record.  (Normally, it only needs
 to match some part of the text in order to succeed.)  For example, the
-following prints the second field of each record that contains the string
-@samp{foo} anywhere in it:
+following prints the second field of each record where the string
+@samp{li} appears anywhere in the record:
 
 @example
-$ @kbd{awk '/foo/ @{ print $2 @}' BBS-list}
-@print{} 555-1234
+$ @kbd{awk '/li/ @{ print $2 @}' mail-list}
+@print{} 555-5553
+@print{} 555-0542
 @print{} 555-6699
-@print{} 555-6480
-@print{} 555-2127
+@print{} 555-3430
 @end example
 
 @cindex regular expressions, operators
@@ -4344,9 +4756,9 @@ $ @kbd{awk '/foo/ @{ print $2 @}' BBS-list}
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
 @c @cindex operators, @code{!~}
-@cindex @code{if} statement
-@cindex @code{while} statement
-@cindex @code{do}-@code{while} statement
+@cindex @code{if} statement, use of regexps in
+@cindex @code{while} statement, use of regexps in
+@cindex @code{do}-@code{while} statement, use of regexps in
 @c @cindex statements, @code{if}
 @c @cindex statements, @code{while}
 @c @cindex statements, @code{do}
@@ -4405,6 +4817,7 @@ $ @kbd{awk '$1 !~ /J/' inventory-shipped}
 @end example
 
 @cindex regexp constants
+@cindex constant regexps
 @cindex regular expressions, constants, See regexp constants
 When a regexp is enclosed in slashes, such as @code{/foo/}, we call it
 a @dfn{regexp constant}, much like @code{5.27} is a numeric constant and
@@ -4413,7 +4826,7 @@ a @dfn{regexp constant}, much like @code{5.27} is a numeric constant and
 @node Escape Sequences
 @section Escape Sequences
 
-@cindex escape sequences
+@cindex escape sequences, in strings
 @cindex backslash (@code{\}), in escape sequences
 @cindex @code{\} (backslash), in escape sequences
 Some characters cannot be included literally in string constants
@@ -4454,7 +4867,7 @@ A literal backslash, @samp{\}.
 @cindex backslash (@code{\}), @code{\a} escape sequence
 @item \a
 The ``alert'' character, @kbd{Ctrl-g}, ASCII code 7 (BEL).
-(This usually makes some sort of audible noise.)
+(This often makes some sort of audible noise.)
 
 @cindex @code{\} (backslash), @code{\b} escape sequence
 @cindex backslash (@code{\}), @code{\b} escape sequence
@@ -4548,7 +4961,7 @@ shown in the previous list.
 
 To summarize:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The escape sequences in the table above are always processed first,
 for both string constants and regexp constants. This happens very early,
@@ -4583,6 +4996,7 @@ leaves what happens as undefined.  There are two choices:
 
 @c @cindex automatic warnings
 @c @cindex warnings, automatic
+@cindex Brian Kernighan's @command{awk}
 @table @asis
 @item Strip the backslash out
 This is what Brian Kernighan's @command{awk} and @command{gawk} both do.
@@ -4596,6 +5010,7 @@ two backslashes in the string: @samp{FS = @w{"[ \t]+\\|[ \t]+"}}.)
 
 @cindex @command{gawk}, escape sequences
 @cindex Unix @command{awk}, backslashes in escape sequences
+@cindex @command{mawk} utility
 @item Leave the backslash alone
 Some other @command{awk} implementations do this.
 In such implementations, typing @code{"a\qc"} is the same as typing
@@ -4624,6 +5039,7 @@ leaves what happens as undefined.  There are two choices:
 
 @c @cindex automatic warnings
 @c @cindex warnings, automatic
+@cindex Brian Kernighan's @command{awk}
 @table @asis
 @item Strip the backslash out
 This is what Brian Kernighan's @command{awk} and @command{gawk} both do.
@@ -4637,6 +5053,7 @@ two backslashes in the string: @samp{FS = @w{"[ \t]+\\|[ \t]+"}}.)
 
 @cindex @command{gawk}, escape sequences
 @cindex Unix @command{awk}, backslashes in escape sequences
+@cindex @command{mawk} utility
 @item Leave the backslash alone
 Some other @command{awk} implementations do this.
 In such implementations, typing @code{"a\qc"} is the same as typing
@@ -4703,6 +5120,7 @@ escape sequences literally when used in regexp constants. Thus,
 @section Regular Expression Operators
 @c STARTOFRANGE regexpo
 @cindex regular expressions, operators
+@cindex metacharacters in regular expressions
 
 You can combine regular expressions with special characters,
 called @dfn{regular expression operators} or @dfn{metacharacters}, to
@@ -4720,10 +5138,11 @@ the very first step in processing regexps.
 Here is a list of metacharacters.  All characters that are not escape
 sequences and that are not listed in the table stand for themselves:
 
-@table @code
-@cindex backslash (@code{\})
-@cindex @code{\} (backslash)
-@item \
+@c Use @asis so the docbook comes out ok. Sigh.
+@table @asis
+@cindex backslash (@code{\}), regexp operator
+@cindex @code{\} (backslash), regexp operator
+@item @code{\}
 This is used to suppress the special meaning of a character when
 matching.  For example, @samp{\$}
 matches the character @samp{$}.
@@ -4732,7 +5151,7 @@ matches the character @samp{$}.
 @cindex Texinfo, chapter beginnings in files
 @cindex @code{^} (caret), regexp operator
 @cindex caret (@code{^}), regexp operator
-@item ^
+@item @code{^}
 This matches the beginning of a string.  For example, @samp{^@@chapter}
 matches @samp{@@chapter} at the beginning of a string and can be used
 to identify chapter beginnings in Texinfo source files.
@@ -4740,29 +5159,31 @@ The @samp{^} is known as an @dfn{anchor}, because it anchors the pattern to
 match only at the beginning of the string.
 
 It is important to realize that @samp{^} does not match the beginning of
-a line embedded in a string.
+a line (the point right after a @samp{\n} newline character) embedded in a string.
 The condition is not true in the following example:
 
 @example
 if ("line1\nLINE 2" ~ /^L/) @dots{}
 @end example
 
-@cindex @code{$} (dollar sign)
-@cindex dollar sign (@code{$})
-@item $
+@cindex @code{$} (dollar sign), regexp operator
+@cindex dollar sign (@code{$}), regexp operator
+@item @code{$}
 This is similar to @samp{^}, but it matches only at the end of a string.
 For example, @samp{p$}
 matches a record that ends with a @samp{p}.  The @samp{$} is an anchor
-and does not match the end of a line embedded in a string.
+and does not match the end of a line
+(the point right before a @samp{\n} newline character)
+embedded in a string.
 The condition in the following example is not true:
 
 @example
 if ("line1\nLINE 2" ~ /1$/) @dots{}
 @end example
 
-@cindex @code{.} (period)
-@cindex period (@code{.})
-@item . @r{(period)}
+@cindex @code{.} (period), regexp operator
+@cindex period (@code{.}), regexp operator
+@item @code{.} (period)
 This matches any single character,
 @emph{including} the newline character.  For example, @samp{.P}
 matches any single character followed by a @samp{P} in a string.  Using
@@ -4777,12 +5198,13 @@ character, which is a character with all bits equal to zero.
 Otherwise, @sc{nul} is just another character. Other versions of @command{awk}
 may not be able to match the @sc{nul} character.
 
-@cindex @code{[]} (square brackets)
-@cindex square brackets (@code{[]})
+@cindex @code{[]} (square brackets), regexp operator
+@cindex square brackets (@code{[]}), regexp operator
 @cindex bracket expressions
 @cindex character sets, See Also bracket expressions
 @cindex character lists, See bracket expressions
-@item [@dots{}]
+@cindex character classes, See bracket expressions
+@item @code{[}@dots{}@code{]}
 This is called a @dfn{bracket expression}.@footnote{In other literature,
 you may see a bracket expression referred to as either a
 @dfn{character set}, a @dfn{character class}, or a @dfn{character list}.}
@@ -4794,7 +5216,7 @@ is given in
 @ref{Bracket Expressions}.
 
 @cindex bracket expressions, complemented
-@item [^ @dots{}]
+@item @code{[^}@dots{}@code{]}
 This is a @dfn{complemented bracket expression}.  The first character after
 the @samp{[} @emph{must} be a @samp{^}.  It matches any characters
 @emph{except} those in the square brackets.  For example, @samp{[^awk]}
@@ -4803,7 +5225,7 @@ or @samp{k}.
 
 @cindex @code{|} (vertical bar)
 @cindex vertical bar (@code{|})
-@item |
+@item @code{|}
 This is the @dfn{alternation operator} and it is used to specify
 alternatives.
 The @samp{|} has the lowest precedence of all the regular
@@ -4814,9 +5236,9 @@ means it matches any string that starts with @samp{P} or contains a digit.
 
 The alternation applies to the largest possible regexps on either side.
 
-@cindex @code{()} (parentheses)
-@cindex parentheses @code{()}
-@item (@dots{})
+@cindex @code{()} (parentheses), regexp operator
+@cindex parentheses @code{()}, regexp operator
+@item @code{(}@dots{}@code{)}
 Parentheses are used for grouping in regular expressions, as in
 arithmetic.  They can be used to concatenate regular expressions
 containing the alternation operator, @samp{|}.  For example,
@@ -4827,7 +5249,7 @@ explained further on in this list.)
 
 @cindex @code{*} (asterisk), @code{*} operator, as regexp operator
 @cindex asterisk (@code{*}), @code{*} operator, as regexp operator
-@item *
+@item @code{*}
 This symbol means that the preceding regular expression should be
 repeated as many times as necessary to find a match.  For example, @samp{ph*}
 applies the @samp{*} symbol to the preceding @samp{h} and looks for matches
@@ -4843,13 +5265,13 @@ prints every record in @file{sample} containing a string of the form
 Notice the escaping of the parentheses by preceding them
 with backslashes.
 
-@cindex @code{+} (plus sign)
-@cindex plus sign (@code{+})
-@item +
+@cindex @code{+} (plus sign), regexp operator
+@cindex plus sign (@code{+}), regexp operator
+@item @code{+}
 This symbol is similar to @samp{*}, except that the preceding expression must be
 matched at least once.  This means that @samp{wh+y}
 would match @samp{why} and @samp{whhy}, but not @samp{wy}, whereas
-@samp{wh*y} would match all three of these strings.
+@samp{wh*y} would match all three.
 The following is a simpler
 way of writing the last @samp{*} example:
 
@@ -4857,17 +5279,17 @@ way of writing the last @samp{*} example:
 awk '/\(c[ad]+r x\)/ @{ print @}' sample
 @end example
 
-@cindex @code{?} (question mark) regexp operator
-@cindex question mark (@code{?}) regexp operator
-@item ?
+@cindex @code{?} (question mark), regexp operator
+@cindex question mark (@code{?}), regexp operator
+@item @code{?}
 This symbol is similar to @samp{*}, except that the preceding expression can be
 matched either once or not at all.  For example, @samp{fe?d}
 matches @samp{fed} and @samp{fd}, but nothing else.
 
-@cindex interval expressions
-@item @{@var{n}@}
-@itemx @{@var{n},@}
-@itemx @{@var{n},@var{m}@}
+@cindex interval expressions, regexp operator
+@item @code{@{}@var{n}@code{@}}
+@itemx @code{@{}@var{n}@code{,@}}
+@itemx @code{@{}@var{n}@code{,}@var{m}@code{@}}
 One or two numbers inside braces denote an @dfn{interval expression}.
 If there is one number in the braces, the preceding regexp is repeated
 @var{n} times.
@@ -4898,7 +5320,7 @@ constants,
 @command{gawk} did @emph{not} match interval expressions
 in regexps.
 
-However, beginning with version 4.0,
+However, beginning with @value{PVERSION} 4.0,
 @command{gawk} does match interval expressions by default.
 This is because compatibility with POSIX has become more
 important to most @command{gawk} users than compatibility with
@@ -4941,6 +5363,7 @@ expressions are not available in regular expressions.
 @cindex bracket expressions
 @cindex bracket expressions, range expressions
 @cindex range expressions (regexps)
+@cindex character lists in regular expression
 
 As mentioned earlier, a bracket expression matches any character amongst
 those listed between the opening and closing square brackets.
@@ -5042,8 +5465,8 @@ These sequences are:
 @item Collating symbols
 Multicharacter collating elements enclosed between
 @samp{[.} and @samp{.]}.  For example, if @samp{ch} is a collating element,
-then @code{[[.ch.]]} is a regexp that matches this collating element, whereas
-@code{[ch]} is a regexp that matches either @samp{c} or @samp{h}.
+then @samp{[[.ch.]]} is a regexp that matches this collating element, whereas
+@samp{[ch]} is a regexp that matches either @samp{c} or @samp{h}.
 
 @cindex bracket expressions, equivalence classes
 @item Equivalence classes
@@ -5051,7 +5474,7 @@ Locale-specific names for a list of
 characters that are equal. The name is enclosed between
 @samp{[=} and @samp{=]}.
 For example, the name @samp{e} might be used to represent all of
-``e,'' ``@`e,'' and ``@'e.'' In this case, @code{[[=e=]]} is a regexp
+``e,'' ``@`e,'' and ``@'e.'' In this case, @samp{[[=e=]]} is a regexp
 that matches any of @samp{e}, @samp{@'e}, or @samp{@`e}.
 @end table
 
@@ -5095,7 +5518,7 @@ or underscores (@samp{_}):
 @item \s
 Matches any whitespace character.
 Think of it as shorthand for
-@w{@code{[[:space:]]}}.
+@w{@samp{[[:space:]]}}.
 
 @c @cindex operators, @code{\S} (@command{gawk})
 @cindex backslash (@code{\}), @code{\S} operator (@command{gawk})
@@ -5103,7 +5526,7 @@ Think of it as shorthand for
 @item \S
 Matches any character that is not whitespace.
 Think of it as shorthand for
-@w{@code{[^[:space:]]}}.
+@w{@samp{[^[:space:]]}}.
 
 @c @cindex operators, @code{\w} (@command{gawk})
 @cindex backslash (@code{\}), @code{\w} operator (@command{gawk})
@@ -5111,7 +5534,7 @@ Think of it as shorthand for
 @item \w
 Matches any word-constituent character---that is, it matches any
 letter, digit, or underscore. Think of it as shorthand for
-@w{@code{[[:alnum:]_]}}.
+@w{@samp{[[:alnum:]_]}}.
 
 @c @cindex operators, @code{\W} (@command{gawk})
 @cindex backslash (@code{\}), @code{\W} operator (@command{gawk})
@@ -5119,7 +5542,7 @@ letter, digit, or underscore. Think of it as shorthand for
 @item \W
 Matches any character that is not word-constituent.
 Think of it as shorthand for
-@w{@code{[^[:alnum:]_]}}.
+@w{@samp{[^[:alnum:]_]}}.
 
 @c @cindex operators, @code{\<} (@command{gawk})
 @cindex backslash (@code{\}), @code{\<} operator (@command{gawk})
@@ -5180,10 +5603,10 @@ Matches the empty string at the
 end of a buffer (string).
 @end table
 
-@cindex @code{^} (caret)
-@cindex caret (@code{^})
-@cindex @code{?} (question mark) regexp operator
-@cindex question mark (@code{?}) regexp operator
+@cindex @code{^} (caret), regexp operator
+@cindex caret (@code{^}), regexp operator
+@cindex @code{?} (question mark), regexp operator
+@cindex question mark (@code{?}), regexp operator
 Because @samp{^} and @samp{$} always work in terms of the beginning
 and end of strings, these operators don't add any new capabilities
 for @command{awk}.  They are provided for compatibility with other
@@ -5200,11 +5623,8 @@ GNU operators, but this was deemed too confusing. The current
 method of using @samp{\y} for the GNU @samp{\b} appears to be the
 lesser of two evils.
 
-@c NOTE!!! Keep this in sync with the same table in the summary appendix!
-@c
-@c Should really do this with file inclusion.
 @cindex regular expressions, @command{gawk}, command-line options
-@cindex @command{gawk}, command-line options
+@cindex @command{gawk}, command-line options, and regular expressions
 The various command-line options
 (@pxref{Options})
 control how @command{gawk} interprets characters in regexps:
@@ -5218,8 +5638,10 @@ previously described
 GNU regexp operators.
 @end ifnotinfo
 @ifnottex
+@ifnotdocbook
 GNU regexp operators described
 in @ref{Regexp Operators}.
+@end ifnotdocbook
 @end ifnottex
 
 @item @code{--posix}
@@ -5227,10 +5649,11 @@ Only POSIX regexps are supported; the GNU operators are not special
 (e.g., @samp{\w} matches a literal @samp{w}).  Interval expressions
 are allowed.
 
+@cindex Brian Kernighan's @command{awk}
 @item @code{--traditional}
 Traditional Unix @command{awk} regexps are matched. The GNU operators
 are not special, and interval expressions are not available.
-The POSIX character classes (@code{[[:alnum:]]}, etc.) are supported,
+The POSIX character classes (@samp{[[:alnum:]]}, etc.) are supported,
 as Brian Kernighan's @command{awk} does support them.
 Characters described by octal and hexadecimal escape sequences are
 treated literally, even if they represent regexp metacharacters.
@@ -5282,16 +5705,18 @@ This works in any POSIX-compliant @command{awk}.
 @cindex tilde (@code{~}), @code{~} operator
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
-@cindex @code{IGNORECASE} variable
+@cindex @code{IGNORECASE} variable, with @code{~} and @code{!~} operators
 @cindex @command{gawk}, @code{IGNORECASE} variable in
 @c @cindex variables, @code{IGNORECASE}
 Another method, specific to @command{gawk}, is to set the variable
 @code{IGNORECASE} to a nonzero value (@pxref{Built-in Variables}).
 When @code{IGNORECASE} is not zero, @emph{all} regexp and string
-operations ignore case.  Changing the value of
-@code{IGNORECASE} dynamically controls the case-sensitivity of the
-program as it runs.  Case is significant by default because
-@code{IGNORECASE} (like most variables) is initialized to zero:
+operations ignore case.
+
+Changing the value of @code{IGNORECASE} dynamically controls the
+case-sensitivity of the program as it runs.  Case is significant by
+default because @code{IGNORECASE} (like most variables) is initialized
+to zero:
 
 @example
 x = "aB"
@@ -5321,9 +5746,6 @@ case-sensitivity on or off for all the rules at once.
 Setting @code{IGNORECASE} from the command line is a way to make
 a program case-insensitive without having to edit it.
 
-Both regexp and string comparison
-operations are affected by @code{IGNORECASE}.
-
 @c @cindex ISO 8859-1
 @c @cindex ISO Latin-1
 In multibyte locales,
@@ -5401,7 +5823,7 @@ regexp constant (i.e., a string of characters between slashes).  It may
 be any expression.  The expression is evaluated and converted to a string
 if necessary; the contents of the string are then used as the
 regexp.  A regexp computed in this way is called a @dfn{dynamic
-regexp}:
+regexp} or a @dfn{computed regexp}:
 
 @example
 BEGIN @{ digits_regexp = "[[:digit:]]+" @}
@@ -5447,7 +5869,7 @@ Given that you can use both regexp and string constants to describe
 regular expressions, which should you use?  The answer is ``regexp
 constants,'' for several reasons:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 String constants are more complicated to write and
 more difficult to read. Using regexp constants makes your programs
@@ -5475,7 +5897,7 @@ intend a regexp match.
 @cindex regular expressions, dynamic, with embedded newlines
 @cindex newlines, in dynamic regexps
 
-Some commercial versions of @command{awk} do not allow the newline
+Some versions of @command{awk} do not allow the newline
 character to be used inside a bracket expression for a dynamic regexp:
 
 @example
@@ -5513,7 +5935,7 @@ occur often in practice, but it's worth noting for future reference.
 @cindex regular expressions, dynamic, with embedded newlines
 @cindex newlines, in dynamic regexps
 
-Some commercial versions of @command{awk} do not allow the newline
+Some versions of @command{awk} do not allow the newline
 character to be used inside a bracket expression for a dynamic regexp:
 
 @example
@@ -5541,12 +5963,59 @@ occur often in practice, but it's worth noting for future reference.
 @end ifnotdocbook
 @c ENDOFRANGE dregexp
 @c ENDOFRANGE regexpd
+
+@node Regexp Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Regular expressions describe sets of strings to be matched.
+In @command{awk}, regular expression constants are written enclosed
+between slashes: @code{/}@dots{}@code{/}.
+
+@item
+Regexp constants may be used by standalone in patterns and
+in conditional expressions, or as part of matching expressions
+using the @samp{~} and @samp{!~} operators.
+
+@item
+Escape sequences let you represent non-printable characters and
+also let you represent regexp metacharacters as literal characters
+to be matched.
+
+@item
+Regexp operators provide grouping, alternation and repetition.
+
+@item
+Bracket expressions give you a shorthand for specifying sets
+of characters that can match at a particular point in a regexp.
+Within bracket expressions, POSIX character classes let you specify
+certain groups of characters in a locale-independent fashion.
+
+@item
+@command{gawk}'s @code{IGNORECASE} variable lets you control the
+case sensitivity of regexp matching.  In other @command{awk}
+versions, use @code{tolower()} or @code{toupper()}.
+
+@item
+Regular expressions match the leftmost longest text in the string being
+matched.  This matters for cases where you need to know the extent of
+the match, such as for text substitution and when the record separator
+is a regexp.
+
+@item
+Matching expressions may use dynamic regexps; that is string values
+treated as regular expressions.
+
+@end itemize
+
 @c ENDOFRANGE regexp
 
 @node Reading Files
 @chapter Reading Input Files
 
 @c STARTOFRANGE infir
+@cindex reading input files
 @cindex input files, reading
 @cindex input files
 @cindex @code{FILENAME} variable
@@ -5589,6 +6058,8 @@ used with it do not have to be named on the @command{awk} command line
 * Read Timeout::                Reading input with a timeout.
 * Command line directories::    What happens if you put a directory on the
                                 command line.
+* Input Summary::               Input summary.
+* Input Exercises::             Exercises.
 @end menu
 
 @node Records
@@ -5608,9 +6079,17 @@ so far
 from the current input file.  This value is stored in a
 built-in variable called @code{FNR}.  It is reset to zero when a new
 file is started.  Another built-in variable, @code{NR}, records the total
-number of input records read so far from all data files.  It starts at zero,
+number of input records read so far from all @value{DF}s.  It starts at zero,
 but is never automatically reset to zero.
 
+@menu
+* awk split records::           How standard @command{awk} splits records.
+* gawk split records::          How @command{gawk} splits records.
+@end menu
+
+@node awk split records
+@subsection Record Splitting With Standard @command{awk}
+
 @cindex separators, for records
 @cindex record separators
 Records are separated by a character called the @dfn{record separator}.
@@ -5633,69 +6112,80 @@ To do this, use the special @code{BEGIN} pattern
 (@pxref{BEGIN/END}).
 For example:
 
-@cindex @code{BEGIN} pattern
 @example
-awk 'BEGIN @{ RS = "/" @}
-     @{ print $0 @}' BBS-list
+awk 'BEGIN @{ RS = "u" @}
+     @{ print $0 @}' mail-list
 @end example
 
 @noindent
-changes the value of @code{RS} to @code{"/"}, before reading any input.
-This is a string whose first character is a slash; as a result, records
-are separated by slashes.  Then the input file is read, and the second
+changes the value of @code{RS} to @samp{u}, before reading any input.
+This is a string whose first character is the letter ``u;'' as a result, records
+are separated by the letter ``u.''  Then the input file is read, and the second
 rule in the @command{awk} program (the action with no pattern) prints each
 record.  Because each @code{print} statement adds a newline at the end of
 its output, this @command{awk} program copies the input
-with each slash changed to a newline.  Here are the results of running
-the program on @file{BBS-list}:
-
-@example
-$ @kbd{awk 'BEGIN @{ RS = "/" @}}
->      @kbd{@{ print $0 @}' BBS-list}
-@print{} aardvark     555-5553     1200
-@print{} 300          B
-@print{} alpo-net     555-3412     2400
-@print{} 1200
-@print{} 300     A
-@print{} barfly       555-7685     1200
-@print{} 300          A
-@print{} bites        555-1675     2400
-@print{} 1200
-@print{} 300     A
-@print{} camelot      555-0542     300               C
-@print{} core         555-2912     1200
-@print{} 300          C
-@print{} fooey        555-1234     2400
-@print{} 1200
-@print{} 300     B
-@print{} foot         555-6699     1200
-@print{} 300          B
-@print{} macfoo       555-6480     1200
-@print{} 300          A
-@print{} sdace        555-3430     2400
-@print{} 1200
-@print{} 300     A
-@print{} sabafoo      555-2127     1200
-@print{} 300          C
-@print{}
+with each @samp{u} changed to a newline.  Here are the results of running
+the program on @file{mail-list}:
+
+@example
+$ @kbd{awk 'BEGIN @{ RS = "u" @}}
+>      @kbd{@{ print $0 @}' mail-list}
+@print{} Amelia       555-5553     amelia.zodiac
+@print{} sq
+@print{} e@@gmail.com    F
+@print{} Anthony      555-3412     anthony.assert
+@print{} ro@@hotmail.com   A
+@print{} Becky        555-7685     becky.algebrar
+@print{} m@@gmail.com      A
+@print{} Bill         555-1675     bill.drowning@@hotmail.com       A
+@print{} Broderick    555-0542     broderick.aliq
+@print{} otiens@@yahoo.com R
+@print{} Camilla      555-2912     camilla.inf
+@print{} sar
+@print{} m@@skynet.be     R
+@print{} Fabi
+@print{} s       555-1234     fabi
+@print{} s.
+@print{} ndevicesim
+@print{} s@@
+@print{} cb.ed
+@print{}     F
+@print{} J
+@print{} lie        555-6699     j
+@print{} lie.perscr
+@print{} tabor@@skeeve.com   F
+@print{} Martin       555-6480     martin.codicib
+@print{} s@@hotmail.com    A
+@print{} Sam
+@print{} el       555-3430     sam
+@print{} el.lanceolis@@sh
+@print{} .ed
+@print{}         A
+@print{} Jean-Pa
+@print{} l    555-2127     jeanpa
+@print{} l.campanor
+@print{} m@@ny
+@print{} .ed
+@print{}      R
+@print{} 
 @end example
 
 @noindent
-Note that the entry for the @samp{camelot} BBS is not split.
-In the original data file
+Note that the entry for the name @samp{Bill} is not split.
+In the original @value{DF}
 (@pxref{Sample Data Files}),
 the line looks like this:
 
 @example
-camelot      555-0542     300               C
+Bill         555-1675     bill.drowning@@hotmail.com       A
 @end example
 
 @noindent
-It has one baud rate only, so there are no slashes in the record,
-unlike the others which have two or more baud rates.
-In fact, this record is treated as part of the record
-for the @samp{core} BBS; the newline separating them in the output
-is the original newline in the data file, not the one added by
+It contains no @samp{u} so there is no reason to split the record,
+unlike the others which have one or more occurrences of the @samp{u}.
+In fact, this record is treated as part of the previous record;
+the newline separating them in the output
+is the original newline in the @value{DF}, not the one added by
 @command{awk} when it printed the record!
 
 @cindex record separators, changing
@@ -5705,14 +6195,17 @@ using the variable-assignment feature
 (@pxref{Other Arguments}):
 
 @example
-awk '@{ print $0 @}' RS="/" BBS-list
+awk '@{ print $0 @}' RS="u" mail-list
 @end example
 
 @noindent
-This sets @code{RS} to @samp{/} before processing @file{BBS-list}.
+This sets @code{RS} to @samp{u} before processing @file{mail-list}.
 
-Using an unusual character such as @samp{/} for the record separator
-produces correct behavior in the vast majority of cases.
+Using an alphabetic character such as @samp{u} for the record separator
+is highly likely to produce strange results.
+Using an unusual character such as @samp{/} is more likely to
+produce correct behavior in the majority of cases, but there
+are no guarantees. The moral is: Know Your Data.
 
 There is one unusual case, that occurs when @command{gawk} is
 being fully POSIX-compliant (@pxref{Options}).
@@ -5734,6 +6227,7 @@ Reaching the end of an input file terminates the current input record,
 even if the last character in the file is not the character in @code{RS}.
 @value{DARKCORNER}
 
+@cindex empty strings
 @cindex null strings
 @cindex strings, empty, See null strings
 The empty string @code{""} (a string without any characters)
@@ -5759,6 +6253,9 @@ After the end of the record has been determined, @command{gawk}
 sets the variable @code{RT} to the text in the input that matched
 @code{RS}.
 
+@node gawk split records
+@subsection Record Splitting With @command{gawk}
+
 @cindex common extensions, @code{RS} as a regexp
 @cindex extensions, common@comma{} @code{RS} as a regexp
 When using @command{gawk},
@@ -5837,12 +6334,11 @@ In compatibility mode, only the first character of the value of
 @end docbook
 
 @cindex portability, data files as single record
-There are times when you might want to treat an entire data file as a
+There are times when you might want to treat an entire @value{DF} as a
 single record.  The only way to make this happen is to give @code{RS}
 a value that you know doesn't occur in the input file.  This is hard
 to do in a general way, such that a program always works for arbitrary
 input files.
-@c can you say `understatement' boys and girls?
 
 You might think that for text files, the @sc{nul} character, which
 consists of a character with all bits equal to zero, is a good
@@ -5855,21 +6351,27 @@ BEGIN @{ RS = "\0" @}  # whole file becomes one record?
 @cindex differences in @command{awk} and @command{gawk}, strings, storing
 @command{gawk} in fact accepts this, and uses the @sc{nul}
 character for the record separator.
+This works for certain special files, such as @file{/proc/environ} on
+GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
 However, this usage is @emph{not} portable
-to other @command{awk} implementations.
+to most other @command{awk} implementations.
 
 @cindex dark corner, strings, storing
-All other @command{awk} implementations@footnote{At least that we know
+Almost all other @command{awk} implementations@footnote{At least that we know
 about.} store strings internally as C-style strings.  C strings use the
 @sc{nul} character as the string terminator.  In effect, this means that
 @samp{RS = "\0"} is the same as @samp{RS = ""}.
 @value{DARKCORNER}
 
+It happens that recent versions of @command{mawk} can use the @sc{nul}
+character as a record separator. However, this is a special case:
+@command{mawk} does not allow embedded @sc{nul} characters in strings.
+
 @cindex records, treating files as
-@cindex files, as single records
-The best way to treat a whole file as a single record is to
-simply read the file in, one record at a time, concatenating each
-record onto the end of the previous ones.
+@cindex treating files, as single records
+@xref{Readfile Function}, for an interesting, portable way to read
+whole files.  If you are using @command{gawk}, see @ref{Extension Sample
+Readfile}, for another option.
 
 @docbook
 </sidebar>
@@ -5882,12 +6384,11 @@ record onto the end of the previous ones.
 
 
 @cindex portability, data files as single record
-There are times when you might want to treat an entire data file as a
+There are times when you might want to treat an entire @value{DF} as a
 single record.  The only way to make this happen is to give @code{RS}
 a value that you know doesn't occur in the input file.  This is hard
 to do in a general way, such that a program always works for arbitrary
 input files.
-@c can you say `understatement' boys and girls?
 
 You might think that for text files, the @sc{nul} character, which
 consists of a character with all bits equal to zero, is a good
@@ -5900,21 +6401,27 @@ BEGIN @{ RS = "\0" @}  # whole file becomes one record?
 @cindex differences in @command{awk} and @command{gawk}, strings, storing
 @command{gawk} in fact accepts this, and uses the @sc{nul}
 character for the record separator.
+This works for certain special files, such as @file{/proc/environ} on
+GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
 However, this usage is @emph{not} portable
-to other @command{awk} implementations.
+to most other @command{awk} implementations.
 
 @cindex dark corner, strings, storing
-All other @command{awk} implementations@footnote{At least that we know
+Almost all other @command{awk} implementations@footnote{At least that we know
 about.} store strings internally as C-style strings.  C strings use the
 @sc{nul} character as the string terminator.  In effect, this means that
 @samp{RS = "\0"} is the same as @samp{RS = ""}.
 @value{DARKCORNER}
 
+It happens that recent versions of @command{mawk} can use the @sc{nul}
+character as a record separator. However, this is a special case:
+@command{mawk} does not allow embedded @sc{nul} characters in strings.
+
 @cindex records, treating files as
-@cindex files, as single records
-The best way to treat a whole file as a single record is to
-simply read the file in, one record at a time, concatenating each
-record onto the end of the previous ones.
+@cindex treating files, as single records
+@xref{Readfile Function}, for an interesting, portable way to read
+whole files.  If you are using @command{gawk}, see @ref{Extension Sample
+Readfile}, for another option.
 @end cartouche
 @end ifnotdocbook
 @c ENDOFRANGE inspl
@@ -5951,7 +6458,7 @@ simple @command{awk} programs so powerful.
 @cindex @code{$} (dollar sign), @code{$} field operator
 @cindex dollar sign (@code{$}), @code{$} field operator
 @cindex field operators@comma{} dollar sign as
-A dollar-sign (@samp{$}) is used
+You use a dollar-sign (@samp{$})
 to refer to a field in an @command{awk} program,
 followed by the number of the field you want.  Thus, @code{$1}
 refers to the first field, @code{$2} to the second, and so on.
@@ -5982,36 +6489,34 @@ one (such as @code{$8} when the record has only seven fields), you get
 the empty string.  (If used in a numeric operation, you get zero.)
 
 The use of @code{$0}, which looks like a reference to the ``zero-th'' field, is
-a special case: it represents the whole input record
+a special case: it represents the whole input record. Use it
 when you are not interested in specific fields.
 Here are some more examples:
 
 @example
-$ @kbd{awk '$1 ~ /foo/ @{ print $0 @}' BBS-list}
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sabafoo      555-2127     1200/300          C
+$ @kbd{awk '$1 ~ /li/ @{ print $0 @}' mail-list}
+@print{} Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+@print{} Julie        555-6699     julie.perscrutabor@@skeeve.com   F
 @end example
 
 @noindent
-This example prints each record in the file @file{BBS-list} whose first
-field contains the string @samp{foo}.  The operator @samp{~} is called a
+This example prints each record in the file @file{mail-list} whose first
+field contains the string @samp{li}.  The operator @samp{~} is called a
 @dfn{matching operator}
 (@pxref{Regexp Usage});
 it tests whether a string (here, the field @code{$1}) matches a given regular
 expression.
 
 By contrast, the following example
-looks for @samp{foo} in @emph{the entire record} and prints the first
+looks for @samp{li} in @emph{the entire record} and prints the first
 field and the last field for each matching input record:
 
 @example
-$ @kbd{awk '/foo/ @{ print $1, $NF @}' BBS-list}
-@print{} fooey B
-@print{} foot B
-@print{} macfoo A
-@print{} sabafoo C
+$ @kbd{awk '/li/ @{ print $1, $NF @}' mail-list}
+@print{} Amelia F
+@print{} Broderick R
+@print{} Julie F
+@print{} Samuel A
 @end example
 @c ENDOFRANGE fiex
 
@@ -6020,7 +6525,7 @@ $ @kbd{awk '/foo/ @{ print $1, $NF @}' BBS-list}
 @cindex fields, numbers
 @cindex field numbers
 
-The number of a field does not need to be a constant.  Any expression in
+A field number need not be a constant.  Any expression in
 the @command{awk} language can be used after a @samp{$} to refer to a
 field.  The value of the expression specifies the field number.  If the
 value is a string, rather than a number, it is converted to a number.
@@ -6039,7 +6544,7 @@ the record has fewer than 20 fields, so this prints a blank line.
 Here is another example of using expressions as field numbers:
 
 @example
-awk '@{ print $(2*2) @}' BBS-list
+awk '@{ print $(2*2) @}' mail-list
 @end example
 
 @command{awk} evaluates the expression @samp{(2*2)} and uses
@@ -6047,9 +6552,13 @@ its value as the number of the field to print.  The @samp{*} sign
 represents multiplication, so the expression @samp{2*2} evaluates to four.
 The parentheses are used so that the multiplication is done before the
 @samp{$} operation; they are necessary whenever there is a binary
-operator in the field-number expression.  This example, then, prints the
-hours of operation (the fourth field) for every line of the file
-@file{BBS-list}.  (All of the @command{awk} operators are listed, in
+operator@footnote{A @dfn{binary operator}, such as @samp{*} for
+multiplication, is one that takes two operands. The distinction
+is required, since @command{awk} also has unary (one-operand)
+and ternary (three-operand) operators.}
+in the field-number expression.  This example, then, prints the
+type of relationship (the fourth field) for every line of the file
+@file{mail-list}.  (All of the @command{awk} operators are listed, in
 order of decreasing precedence, in
 @ref{Precedence}.)
 
@@ -6097,7 +6606,7 @@ Then it prints the original and new values for field three.
 (Someone in the warehouse made a consistent mistake while inventorying
 the red boxes.)
 
-For this to work, the text in field @code{$3} must make sense
+For this to work, the text in @code{$3} must make sense
 as a number; the string of characters must be converted to a number
 for the computer to do arithmetic on it.  The number resulting
 from the subtraction is converted back to a string of characters that
@@ -6188,7 +6697,7 @@ $ @kbd{echo a b c d | awk '@{ OFS = ":"; $2 = ""}
 @end example
 
 @noindent
-The field is still there; it just has an empty value, denoted by
+The field is still there; it just has an empty value, delimited by
 the two colons between @samp{a} and @samp{c}.
 This example shows what happens if you create a new field:
 
@@ -6303,6 +6812,7 @@ with a statement such as @samp{$1 = $1}, as described earlier.
 * Regexp Field Splitting::       Using regexps as the field separator.
 * Single Character Fields::      Making each character a separate field.
 * Command Line Field Separator:: Setting @code{FS} from the command-line.
+* Full Line Fields::             Making the full line be a single field.
 * Field Splitting Summary::      Some final points and a summary table.
 @end menu
 
@@ -6470,7 +6980,7 @@ $ @kbd{echo ' a  b  c  d ' | awk 'BEGIN @{ FS = "[ \t\n]+" @}}
 @cindex null strings
 @cindex strings, null
 @cindex empty strings, See null strings
-In this case, the first field is @dfn{null} or empty.
+In this case, the first field is null, or empty.
 
 The stripping of leading and trailing whitespace also comes into
 play whenever @code{$0} is recomputed.  For instance, study this pipeline:
@@ -6490,7 +7000,7 @@ was ignored when finding @code{$1}, it is not part of the new @code{$0}.
 Finally, the last @code{print} statement prints the new @code{$0}.
 
 @cindex @code{FS}, containing @code{^}
-@cindex @code{^}, in @code{FS}
+@cindex @code{^} (caret), in @code{FS}
 @cindex dark corner, @code{^}, in @code{FS}
 There is an additional subtlety to be aware of when using regular expressions
 for field splitting.
@@ -6501,6 +7011,7 @@ different @command{awk} versions answer this question differently, and you
 should not rely on any specific behavior in your programs.
 @value{DARKCORNER}
 
+@cindex Brian Kernighan's @command{awk}
 As a point of information, Brian Kernighan's @command{awk} allows @samp{^}
 to match only at the beginning of the record. @command{gawk}
 also works this way. For example:
@@ -6544,7 +7055,7 @@ $ @kbd{echo a b | gawk 'BEGIN @{ FS = "" @}}
 @end example
 
 @cindex dark corner, @code{FS} as null string
-@cindex FS variable, as null string
+@cindex @code{FS} variable, as null string
 Traditionally, the behavior of @code{FS} equal to @code{""} was not defined.
 In this case, most versions of Unix @command{awk} simply treat the entire record
 as only having one field.
@@ -6556,10 +7067,8 @@ behaves this way.
 
 @node Command Line Field Separator
 @subsection Setting @code{FS} from the Command Line
-@cindex @code{-F} option
-@cindex options, command-line
-@cindex command line, options
-@cindex field separators, on command line
+@cindex @option{-F} option, command line
+@cindex field separator, on command line
 @cindex command line, @code{FS} on@comma{} setting
 @cindex @code{FS} variable, setting from command line
 
@@ -6609,68 +7118,75 @@ figures that you really want your fields to be separated with TABs and
 not @samp{t}s.  Use @samp{-v FS="t"} or @samp{-F"[t]"} on the command line
 if you really do want to separate your fields with @samp{t}s.
 
-As an example, let's use an @command{awk} program file called @file{baud.awk}
-that contains the pattern @code{/300/} and the action @samp{print $1}:
+As an example, let's use an @command{awk} program file called @file{edu.awk}
+that contains the pattern @code{/edu/} and the action @samp{print $1}:
 
 @example
-/300/   @{ print $1 @}
+/edu/   @{ print $1 @}
 @end example
 
 Let's also set @code{FS} to be the @samp{-} character and run the
-program on the file @file{BBS-list}.  The following command prints a
-list of the names of the bulletin boards that operate at 300 baud and
+program on the file @file{mail-list}.  The following command prints a
+list of the names of the people that work at or attend a university, and
 the first three digits of their phone numbers:
 
-@c tweaked to make the tex output look better in @smallbook
 @example
-$ @kbd{awk -F- -f baud.awk BBS-list}
-@print{} aardvark     555
-@print{} alpo
-@print{} barfly       555
-@print{} bites        555
-@print{} camelot      555
-@print{} core         555
-@print{} fooey        555
-@print{} foot         555
-@print{} macfoo       555
-@print{} sdace        555
-@print{} sabafoo      555
+$ @kbd{awk -F- -f edu.awk mail-list}
+@print{} Fabius       555
+@print{} Samuel       555
+@print{} Jean
 @end example
 
 @noindent
-Note the second line of output.  The second line
+Note the third line of output.  The third line
 in the original file looked like this:
 
 @example
-alpo-net     555-3412     2400/1200/300     A
+Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @end example
 
-The @samp{-} as part of the system's name was used as the field
+The @samp{-} as part of the person's name was used as the field
 separator, instead of the @samp{-} in the phone number that was
 originally intended.  This demonstrates why you have to be careful in
 choosing your field and record separators.
 
 @cindex Unix @command{awk}, password files@comma{} field separators and
-Perhaps the most common use of a single character as the field
-separator occurs when processing the Unix system password file.
-On many Unix systems, each user has a separate entry in the system password
-file, one line per user.  The information in these lines is separated
-by colons.  The first field is the user's login name and the second is
-the user's (encrypted or shadow) password.  A password file entry might look
-like this:
+Perhaps the most common use of a single character as the field separator
+occurs when processing the Unix system password file.  On many Unix
+systems, each user has a separate entry in the system password file, one
+line per user.  The information in these lines is separated by colons.
+The first field is the user's login name and the second is the user's
+encrypted or shadow password.  (A shadow password is indicated by the
+presence of a single @samp{x} in the second field.)  A password file
+entry might look like this:
 
 @cindex Robbins, Arnold
 @example
-arnold:xyzzy:2076:10:Arnold Robbins:/home/arnold:/bin/bash
+arnold:x:2076:10:Arnold Robbins:/home/arnold:/bin/bash
 @end example
 
 The following program searches the system password file and prints
-the entries for users who have no password:
+the entries for users whose full name is not indicated:
 
 @example
-awk -F: '$2 == ""' /etc/passwd
+awk -F: '$5 == ""' /etc/passwd
 @end example
 
+@node Full Line Fields
+@subsection Making The Full Line Be A Single Field
+
+Occasionally, it's useful to treat the whole input line as a
+single field.  This can be done easily and portably simply by
+setting @code{FS} to @code{"\n"} (a newline).@footnote{Thanks to
+Andrew Schorr for this tip.}
+
+@example
+awk -F'\n' '@var{program}' @var{files @dots{}}
+@end example
+
+@noindent
+When you do this, @code{$1} is the same as @code{$0}.
+
 @node Field Splitting Summary
 @subsection Field-Splitting Summary
 
@@ -6716,7 +7232,7 @@ POSIX standard.)
 
 
 @cindex POSIX @command{awk}, field separators and
-@cindex field separators, POSIX and
+@cindex field separator, POSIX and
 According to the POSIX standard, @command{awk} is supposed to behave
 as if each record is split into fields at the time it is read.
 In particular, this means that if you change the value of @code{FS}
@@ -6769,7 +7285,7 @@ root:nSijPlPhZZwgE:0:0:Root:/:
 
 
 @cindex POSIX @command{awk}, field separators and
-@cindex field separators, POSIX and
+@cindex field separator, POSIX and
 According to the POSIX standard, @command{awk} is supposed to behave
 as if each record is split into fields at the time it is read.
 In particular, this means that if you change the value of @code{FS}
@@ -6876,19 +7392,11 @@ will take effect.
 @node Constant Size
 @section Reading Fixed-Width Data
 
-@ifnotinfo
 @quotation NOTE
 This @value{SECTION} discusses an advanced
 feature of @command{gawk}.  If you are a novice @command{awk} user,
 you might want to skip it on the first reading.
 @end quotation
-@end ifnotinfo
-
-@ifinfo
-(This @value{SECTION} discusses an advanced feature of @command{awk}.
-If you are a novice @command{awk} user, you might want to skip it on
-the first reading.)
-@end ifinfo
 
 @cindex data, fixed-width
 @cindex fixed-width data
@@ -6986,10 +7494,6 @@ program for processing such data could use the @code{FIELDWIDTHS} feature
 to simplify reading the data.  (Of course, getting @command{gawk} to run on
 a system with card readers is another story!)
 
-@ignore
-Exercise: Write a ballot card reading program
-@end ignore
-
 @cindex @command{gawk}, splitting fields and
 Assigning a value to @code{FS} causes @command{gawk} to use
 @code{FS} for field splitting again.  Use @samp{FS = FS} to make this happen,
@@ -7006,7 +7510,7 @@ if (PROCINFO["FS"] == "FS")
 else if  (PROCINFO["FS"] == "FIELDWIDTHS")
     @var{fixed-width field splitting} @dots{}
 else
-    @var{content-based field splitting} @dots{} (see next @value{SECTION})
+    @var{content-based field splitting} @dots{} @ii{(see next @value{SECTION})}
 @end example
 
 This information is useful when writing a function
@@ -7018,19 +7522,11 @@ for an example of such a function).
 @node Splitting By Content
 @section Defining Fields By Content
 
-@ifnotinfo
 @quotation NOTE
 This @value{SECTION} discusses an advanced
 feature of @command{gawk}.  If you are a novice @command{awk} user,
 you might want to skip it on the first reading.
 @end quotation
-@end ifnotinfo
-
-@ifinfo
-(This @value{SECTION} discusses an advanced feature of @command{awk}.
-If you are a novice @command{awk} user, you might want to skip it on
-the first reading.)
-@end ifinfo
 
 @cindex advanced features, specifying field content
 Normally, when using @code{FS}, @command{gawk} defines the fields as the
@@ -7128,7 +7624,7 @@ the double quotes.  @command{gawk} provides no way to deal with this.
 Since there is no formal specification for CSV data, there isn't much
 more to be done;
 the @code{FPAT} mechanism provides an elegant solution for the majority
-of cases, and the @command{gawk} maintainer is satisfied with that. 
+of cases, and the @command{gawk} developers are satisfied with that. 
 @end quotation
 
 As written, the regexp used for @code{FPAT} requires that each field
@@ -7145,6 +7641,7 @@ available for splitting regular strings (@pxref{String Functions}).
 @node Multiple Line
 @section Multiple-Line Records
 
+@cindex multiple-line records
 @c STARTOFRANGE recm
 @cindex records, multiline
 @c STARTOFRANGE imr
@@ -7189,14 +7686,15 @@ the first nonblank line that follows---no matter how many blank lines
 appear in a row, they are considered one record separator.
 
 @cindex dark corner, multiline records
-There is an important difference between @samp{RS = ""} and
+However, there is an important difference between @samp{RS = ""} and
 @samp{RS = "\n\n+"}. In the first case, leading newlines in the input
-data file are ignored, and if a file ends without extra blank lines
+@value{DF} are ignored, and if a file ends without extra blank lines
 after the last record, the final newline is removed from the record.
 In the second case, this special processing is not done.
 @value{DARKCORNER}
 
-@cindex field separators, in multiline records
+@cindex field separator, in multiline records
+@cindex @code{FS}, in multiline records
 Now that the input is separated into records, the second step is to
 separate the fields in the record.  One way to do this is to divide each
 of the lines into fields in the normal manner.  This happens by default
@@ -7226,7 +7724,7 @@ Another way to separate fields is to
 put each field on a separate line: to do this, just set the
 variable @code{FS} to the string @code{"\n"}.  (This single
 character separator matches a single newline.)
-A practical example of a data file organized this way might be a mailing
+A practical example of a @value{DF} organized this way might be a mailing
 list, where each entry is separated by blank lines.  Consider a mailing
 list in a file named @file{addresses}, which looks like this:
 
@@ -7291,7 +7789,7 @@ value of
 @table @code
 @item RS == "\n"
 Records are separated by the newline character (@samp{\n}).  In effect,
-every line in the data file is a separate record, including blank lines.
+every line in the @value{DF} is a separate record, including blank lines.
 This is the default.
 
 @item RS == @var{any single character}
@@ -7327,9 +7825,10 @@ then @command{gawk} sets @code{RT} to the null string.
 
 @c STARTOFRANGE getl
 @cindex @code{getline} command, explicit input with
+@c STARTOFRANGE inex
 @cindex input, explicit
 So far we have been getting our input data from @command{awk}'s main
-input stream---either the standard input (usually your terminal, sometimes
+input stream---either the standard input (usually your keyboard, sometimes
 the output from another program) or from the
 files specified on the command line.  The @command{awk} language has a
 special built-in command called @code{getline} that
@@ -7340,13 +7839,25 @@ The @code{getline} command is used in several different ways and should
 The examples that follow the explanation of the @code{getline} command
 include material that has not been covered yet.  Therefore, come back
 and study the @code{getline} command @emph{after} you have reviewed the
-rest of this @value{DOCUMENT} and have a good knowledge of how @command{awk} works.
+rest of
+@ifinfo
+this @value{DOCUMENT}
+@end ifinfo
+@ifhtml
+this @value{DOCUMENT}
+@end ifhtml
+@ifnotinfo
+@ifnothtml
+Parts I and II
+@end ifnothtml
+@end ifnotinfo
+and have a good knowledge of how @command{awk} works.
 
 @cindex @command{gawk}, @code{ERRNO} variable in
-@cindex @code{ERRNO} variable
+@cindex @code{ERRNO} variable, with @command{getline} command
 @cindex differences in @command{awk} and @command{gawk}, @code{getline} command
 @cindex @code{getline} command, return values
-@cindex @code{--sandbox} option, input redirection with @command{getline}
+@cindex @option{--sandbox} option, input redirection with @code{getline}
 
 The @code{getline} command returns one if it finds a record and zero if
 it encounters the end of the file.  If there is some error in getting
@@ -7419,11 +7930,6 @@ decommented input, such as searching for matches of a regular
 expression.  (This program has a subtle problem---it does not work if one
 comment ends and another begins on the same line.)
 
-@ignore
-Exercise,
-write a program that does handle multiple comments on the line.
-@end ignore
-
 This form of the @code{getline} command sets @code{NF},
 @code{NR}, @code{FNR}, @code{RT}, and the value of @code{$0}.
 
@@ -7439,6 +7945,7 @@ rule in the program.  @xref{Next Statement}.
 
 @node Getline/Variable
 @subsection Using @code{getline} into a Variable
+@cindex @code{getline} into a variable
 @cindex variables, @code{getline} command into@comma{} using
 
 You can use @samp{getline @var{var}} to read the next record from
@@ -7490,6 +7997,7 @@ the value of @code{NF} do not change.
 @node Getline/File
 @subsection Using @code{getline} from a File
 
+@cindex @code{getline} from a file
 @cindex input redirection
 @cindex redirection of input
 @cindex @code{<} (left angle bracket), @code{<} operator (I/O)
@@ -7497,7 +8005,7 @@ the value of @code{NF} do not change.
 @cindex operators, input/output
 Use @samp{getline < @var{file}} to read the next record from @var{file}.
 Here @var{file} is a string-valued expression that
-specifies the file name.  @samp{< @var{file}} is called a @dfn{redirection}
+specifies the @value{FN}.  @samp{< @var{file}} is called a @dfn{redirection}
 because it directs input to come from a different place.
 For example, the following
 program reads its input record from the file @file{secondary.input} when it
@@ -7525,9 +8033,9 @@ changed, resulting in a new value of @code{NF}.
 According to POSIX, @samp{getline < @var{expression}} is ambiguous if
 @var{expression} contains unparenthesized operators other than
 @samp{$}; for example, @samp{getline < dir "/" file} is ambiguous
-because the concatenation operator is not parenthesized.  You should
-write it as @samp{getline < (dir "/" file)} if you want your program
-to be portable to all @command{awk} implementations.
+because the concatenation operator (not discussed yet; @pxref{Concatenation})
+is not parenthesized.  You should write it as @samp{getline < (dir "/" file)} if
+you want your program to be portable to all @command{awk} implementations.
 
 @node Getline/Variable/File
 @subsection Using @code{getline} into a Variable from a File
@@ -7538,8 +8046,6 @@ from the file
 @var{file}, and put it in the variable @var{var}.  As above, @var{file}
 is a string-valued expression that specifies the file from which to read.
 
-@cindex @command{gawk}, @code{RT} variable in
-@cindex @code{RT} variable
 In this version of @code{getline}, none of the built-in variables are
 changed and the record is not split into fields.  The only variable
 changed is @var{var}.@footnote{This is not quite true. @code{RT} could
@@ -7562,25 +8068,25 @@ Such a record is replaced by the contents of the file
 
 Note here how the name of the extra input file is not built into
 the program; it is taken directly from the data, specifically from the second field on
-the @samp{@@include} line.
+the @code{@@include} line.
 
-@cindex @code{close()} function
 The @code{close()} function is called to ensure that if two identical
-@samp{@@include} lines appear in the input, the entire specified file is
+@code{@@include} lines appear in the input, the entire specified file is
 included twice.
 @xref{Close Files And Pipes}.
 
 One deficiency of this program is that it does not process nested
-@samp{@@include} statements
-(i.e., @samp{@@include} statements in included files)
+@code{@@include} statements
+(i.e., @code{@@include} statements in included files)
 the way a true macro preprocessor would.
 @xref{Igawk Program}, for a program
-that does handle nested @samp{@@include} statements.
+that does handle nested @code{@@include} statements.
 
 @node Getline/Pipe
 @subsection Using @code{getline} from a Pipe
 
 @c From private email, dated October 2, 1988. Used by permission, March 2013.
+@cindex Kernighan, Brian
 @quotation
 @i{Omniscience has much to recommend it.
 Failing that, attention to details would be useful.}
@@ -7590,7 +8096,7 @@ Failing that, attention to details would be useful.}
 @cindex @code{|} (vertical bar), @code{|} operator (I/O)
 @cindex vertical bar (@code{|}), @code{|} operator (I/O)
 @cindex input pipeline
-@cindex pipes, input
+@cindex pipe, input
 @cindex operators, input/output
 The output of a command can also be piped into @code{getline}, using
 @samp{@var{command} | getline}.  In
@@ -7614,14 +8120,14 @@ produced by running the rest of the line as a shell command:
 @end example
 
 @noindent
-@cindex @code{close()} function
 The @code{close()} function is called to ensure that if two identical
 @samp{@@execute} lines appear in the input, the command is run for
 each one.
 @ifnottex
+@ifnotdocbook
 @xref{Close Files And Pipes}.
+@end ifnotdocbook
 @end ifnottex
-@c Exercise!!
 @c This example is unrealistic, since you could just use system
 Given the input:
 
@@ -7668,6 +8174,8 @@ because the concatenation operator is not parenthesized.  You should
 write it as @samp{(@w{"echo "} "date") | getline} if you want your program
 to be portable to all @command{awk} implementations.
 
+@cindex Brian Kernighan's @command{awk}
+@cindex @command{mawk} utility
 @quotation NOTE
 Unfortunately, @command{gawk} has not been consistent in its treatment
 of a construct like @samp{@w{"echo "} "date" | getline}.
@@ -7779,7 +8287,7 @@ where coprocesses are discussed in more detail.
 Here are some miscellaneous points about @code{getline} that
 you should bear in mind:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 When @code{getline} changes the value of @code{$0} and @code{NF},
 @command{awk} does @emph{not} automatically jump to the start of the
@@ -7791,7 +8299,7 @@ However, the new record is tested against any subsequent rules.
 @cindex @command{awk}, implementations, limits
 @cindex @command{gawk}, implementation issues, limits
 @item
-Many @command{awk} implementations limit the number of pipelines that an @command{awk}
+Some very old @command{awk} implementations limit the number of pipelines that an @command{awk}
 program may have open to just one.  In @command{gawk}, there is no such limit.
 You can open as many pipelines (and coprocesses) as the underlying operating
 system permits.
@@ -7804,10 +8312,10 @@ system permits.
 @item
 An interesting side effect occurs if you use @code{getline} without a
 redirection inside a @code{BEGIN} rule. Because an unredirected @code{getline}
-reads from the command-line data files, the first @code{getline} command
+reads from the command-line @value{DF}s, the first @code{getline} command
 causes @command{awk} to set the value of @code{FILENAME}. Normally,
 @code{FILENAME} does not have a value inside @code{BEGIN} rules, because you
-have not yet started to process the command-line data files.
+have not yet started to process the command-line @value{DF}s.
 @value{DARKCORNER}
 (@xref{BEGIN/END},
 also @pxref{Auto-set}.)
@@ -7830,6 +8338,7 @@ can cause @code{FILENAME} to be updated if they cause
 @command{awk} to start reading a new input file.
 
 @item
+@cindex Moore, Duncan
 If the variable being assigned is an expression with side effects,
 different versions of @command{awk} behave differently upon encountering
 end-of-file.  Some versions don't evaluate the expression; many versions
@@ -7854,7 +8363,7 @@ end of file is encountered, before the element in @code{a} is assigned?
 
 @command{gawk} treats @code{getline} like a function call, and evaluates
 the expression @samp{a[++c]} before attempting to read from @file{f}.
-Other versions of @command{awk} only evaluate the expression once they
+However, some versions of @command{awk} only evaluate the expression once they
 know that there is a string value to be assigned.  Caveat Emptor.
 @end itemize
 
@@ -7890,10 +8399,13 @@ Note: for each variant, @command{gawk} sets the @code{RT} built-in variable.
 @section Reading Input With A Timeout
 @cindex timeout, reading input
 
-You may specify a timeout in milliseconds for reading input from a terminal,
-pipe or two-way communication including, TCP/IP sockets. This can be done
+@cindex differences in @command{awk} and @command{gawk}, read timeouts
+This @value{SECTION} describes a feature that is specific to @command{gawk}.
+
+You may specify a timeout in milliseconds for reading input from the keyboard,
+a pipe, or two-way communication, including TCP/IP sockets. This can be done
 on a per input, command or connection basis, by setting a special element
-in the @code{PROCINFO} array:
+in the @code{PROCINFO} (@pxref{Auto-set}) array:
 
 @example
 PROCINFO["input_name", "READ_TIMEOUT"] = @var{timeout in milliseconds}
@@ -7913,8 +8425,8 @@ else if (ERRNO != "")
     print ERRNO
 @end example
 
-Here is how to read interactively from the terminal@footnote{This assumes
-that standard input is the keyboard} without waiting
+Here is how to read interactively from the user@footnote{This assumes
+that standard input is the keyboard.} without waiting
 for more than five seconds:
 
 @example
@@ -7923,13 +8435,13 @@ while ((getline < "/dev/stdin") > 0)
     print $0
 @end example
 
-@command{gawk} will terminate the read operation if input does not
-arrive after waiting for the timeout period, return failure
-and set the @code{ERRNO} variable to an appropriate string value.
+@command{gawk} terminates the read operation if input does not
+arrive after waiting for the timeout period, returns failure
+and sets the @code{ERRNO} variable to an appropriate string value.
 A negative or zero value for the timeout is the same as specifying
 no timeout at all.
 
-A timeout can also be set for reading from the terminal in the implicit
+A timeout can also be set for reading from the keyboard in the implicit
 loop that reads input records and matches them against patterns,
 like so:
 
@@ -7992,19 +8504,120 @@ indefinitely until some other process opens it for writing.
 
 @node Command line directories
 @section Directories On The Command Line
+@cindex differences in @command{awk} and @command{gawk}, command line directories
 @cindex directories, command line
 @cindex command line, directories on
 
 According to the POSIX standard, files named on the @command{awk}
-command line must be text files.  It is a fatal error if they are not.
+command line must be text files; it is a fatal error if they are not.
 Most versions of @command{awk} treat a directory on the command line as
 a fatal error.
 
 By default, @command{gawk} produces a warning for a directory on the
-command line, but otherwise ignores it.  If either of the @option{--posix}
+command line, but otherwise ignores it.  This makes it easier to use
+shell wildcards with your @command{awk} program:
+
+@example
+$ @kbd{gawk -f whizprog.awk *}        @ii{Directories could kill this progam}
+@end example
+
+If either of the @option{--posix}
 or @option{--traditional} options is given, then @command{gawk} reverts
 to treating a directory on the command line as a fatal error.
 
+@xref{Extension Sample Readdir}, for a way to treat directories
+as usable data from an @command{awk} program.
+
+@node Input Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Input is split into records based on the value of @code{RS}.
+The possibilities are as follows:
+
+@multitable @columnfractions .25 .35 .40
+@headitem Value of @code{RS} @tab Records are split on @tab @command{awk} / @command{gawk}
+@item Any single character @tab That character @tab @command{awk}
+@item The empty string (@code{""}) @tab Runs of two or more newlines @tab @command{awk}
+@item A regexp @tab Text that matches the regexp @tab @command{gawk}
+@end multitable
+
+@item
+@command{gawk} sets @code{RT} to the text matched by @code{RS}.
+
+@item
+After splitting the input into records, @command{awk} further splits
+the record into individual fields, named @code{$1}, @code{$2} and so
+on. @code{$0} is the whole record, and @code{NF} indicates how many
+fields there are.  The default way to split fields is between whitespace
+characters.
+
+@item
+Fields may be referenced using a variable, as in @samp{$NF}.  Fields
+may also be assigned values, which causes the value of @code{$0} to be
+recomputed when it is later referenced. Assigning to a field with a number
+greater than @code{NF} creates the field and rebuilds the record, using
+@code{OFS} to separate the fields.  Incrementing @code{NF} does the same
+thing. Decrementing @code{NF} throws away fields and rebuilds the record.
+
+@item
+Field splitting is more complicated than record splitting.
+
+@multitable @columnfractions .40 .40 .20
+@headitem Field separator value @tab Fields are split @dots{} @tab @command{awk} / @command{gawk}
+@item @code{FS == " "} @tab On runs of whitespace @tab @command{awk}
+@item @code{FS == @var{any single character}} @tab On that character @tab @command{awk}
+@item @code{FS == @var{regexp}} @tab On text matching the regexp @tab @command{awk}
+@item @code{FS == ""}  @tab Each individual character is a separate field @tab @command{gawk}
+@item @code{FIELDWIDTHS == @var{list of columns}} @tab Based on character position @tab @command{gawk}
+@item @code{FPAT == @var{regexp}} @tab On text around text matching the regexp @tab @command{gawk}
+@end multitable
+
+Using @samp{FS = "\n"} causes the entire record to be a single field
+(assuming that newlines separate records).
+
+@item
+@code{FS} may be set from the command line using the @option{-F} option.
+This can also be done using command-line variable assignment.
+
+@item
+@code{PROCINFO["FS"]} can be used to see how fields are being split.
+
+@item
+Use @code{getline} in its various forms to read additional records,
+from the default input stream, from a file, or from a pipe or co-process.
+
+@item
+Use @code{PROCINFO[@var{file}, "READ_TIMEOUT"]} to cause reads to timeout
+for @var{file}.
+
+@item
+Directories on the command line are fatal for standard @command{awk};
+@command{gawk} ignores them if not in POSIX mode.
+
+@end itemize
+
+@node Input Exercises
+@section Exercises
+
+@enumerate
+@item
+Using the @code{FIELDWIDTHS} variable (@pxref{Constant Size}),
+write a program to read election data, where each record represents
+one voter's votes.  Come up with a way to define which columns are
+associated with each ballot item, and print the total votes,
+including abstentions, for each item.
+
+@item
+@ref{Plain Getline}, presented a program to remove C-style
+comments (@samp{/* @dots{} */}) from the input.  That program
+does not work if one comment ends on one line and another one
+starts later on the same line.
+Write a program that does handle multiple comments on the line.
+
+@end enumerate
+
 @node Printing
 @chapter Printing Output
 
@@ -8029,7 +8642,7 @@ For printing with specifications, you need the @code{printf} statement
 @cindex @code{printf} statement
 Besides basic and formatted printing, this @value{CHAPTER}
 also covers I/O redirections to files and pipes, introduces
-the special file names that @command{gawk} processes internally,
+the special @value{FN}s that @command{gawk} processes internally,
 and discusses the @code{close()} built-in function.
 
 @menu
@@ -8044,13 +8657,15 @@ and discusses the @code{close()} built-in function.
                                 @command{gawk} allows access to inherited file
                                 descriptors.
 * Close Files And Pipes::       Closing Input and Output Files and Pipes.
+* Output Summary::              Output summary.
+* Output exercises::            Exercises.
 @end menu
 
 @node Print
 @section The @code{print} Statement
 
 The @code{print} statement is used for producing output with simple, standardized
-formatting.  Specify only the strings or numbers to print, in a
+formatting.  You specify only the strings or numbers to print, in a
 list separated by commas.  They are output, separated by single spaces,
 followed by a newline.  The statement looks like this:
 
@@ -8133,10 +8748,9 @@ $ @kbd{awk '@{ print $1 $2 @}' inventory-shipped}
 To someone unfamiliar with the @file{inventory-shipped} file, neither
 example's output makes much sense.  A heading line at the beginning
 would make it clearer.  Let's add some headings to our table of months
-(@code{$1}) and green crates shipped (@code{$2}).  We do this using the
-@code{BEGIN} pattern
-(@pxref{BEGIN/END})
-so that the headings are only printed once:
+(@code{$1}) and green crates shipped (@code{$2}).  We do this using
+a @code{BEGIN} rule (@pxref{BEGIN/END}) so that the headings are only
+printed once:
 
 @example
 awk 'BEGIN @{  print "Month Crates"
@@ -8222,26 +8836,32 @@ The following example prints the first and second fields of each input
 record, separated by a semicolon, with a blank line added after each
 newline:
 
-@ignore
-Exercise,
-Rewrite the
-@example
-awk 'BEGIN @{ print "Month Crates"
-             print "----- ------" @}
-           @{ print $1, "     ", $2 @}' inventory-shipped
-@end example
-program by using a new value of @code{OFS}.
-@end ignore
 
 @example
 $ @kbd{awk 'BEGIN @{ OFS = ";"; ORS = "\n\n" @}}
->            @kbd{@{ print $1, $2 @}' BBS-list}
-@print{} aardvark;555-5553
-@print{}
-@print{} alpo-net;555-3412
-@print{}
-@print{} barfly;555-7685
-@dots{}
+>            @kbd{@{ print $1, $2 @}' mail-list}
+@print{} Amelia;555-5553
+@print{} 
+@print{} Anthony;555-3412
+@print{} 
+@print{} Becky;555-7685
+@print{} 
+@print{} Bill;555-1675
+@print{} 
+@print{} Broderick;555-0542
+@print{} 
+@print{} Camilla;555-2912
+@print{} 
+@print{} Fabius;555-1234
+@print{} 
+@print{} Julie;555-6699
+@print{} 
+@print{} Martin;555-6480
+@print{} 
+@print{} Samuel;555-3430
+@print{} 
+@print{} Jean-Paul;555-2127
+@print{} 
 @end example
 
 If the value of @code{ORS} does not contain a newline, the program's output
@@ -8263,7 +8883,7 @@ numbers can be formatted.  The different format specifications are discussed
 more fully in
 @ref{Control Letters}.
 
-@cindex @code{sprintf()} function
+@cindexawkfunc{sprintf}
 @cindex @code{OFMT} variable
 @cindex output, format specifier@comma{} @code{OFMT}
 The built-in variable @code{OFMT} contains the default format specification
@@ -8329,7 +8949,7 @@ parentheses are necessary if any of the item expressions use the @samp{>}
 relational operator; otherwise, it can be confused with an output redirection
 (@pxref{Redirection}).
 
-@cindex format strings
+@cindex format specifiers
 The difference between @code{printf} and @code{print} is the @var{format}
 argument.  This is an expression whose value is taken as a string; it
 specifies how to output each of the other arguments.  It is called the
@@ -8372,8 +8992,9 @@ of value to print.  The rest of the format specifier is made up of
 optional @dfn{modifiers} that control @emph{how} to print the value, such as
 the field width.  Here is a list of the format-control letters:
 
-@table @code
-@item %c
+@c @asis for docbook to come out right
+@table @asis
+@item @code{%c}
 Print a number as an ASCII character; thus, @samp{printf "%c",
 65} outputs the letter @samp{A}. The output for a string value is
 the first character of the string.
@@ -8381,16 +9002,6 @@ the first character of the string.
 @cindex dark corner, format-control characters
 @cindex @command{gawk}, format-control characters
 @quotation NOTE
-@ignore
-The @samp{%c} format does @emph{not} handle values outside the range
-0--255.  On most systems, values from 0--127 are within the range of
-ASCII and will yield an ASCII character.  Values in the range 128--255
-may format as characters in some extended character set, or they may not.
-System 390 (IBM architecture mainframe) systems use 8-bit characters,
-and thus values from 0--255 yield the corresponding EBCDIC character.
-Any value above 255 is treated as modulo 255; i.e., the lowest eight bits
-of the value are used.  The locale and character set are always ignored.
-@end ignore
 The POSIX standard says the first character of a string is printed.
 In locales with multibyte characters, @command{gawk} attempts to
 convert the leading bytes of the string into a valid wide character
@@ -8405,12 +9016,12 @@ a single byte (0--255).
 @end quotation
 
 
-@item %d@r{,} %i
+@item @code{%d}, @code{%i}
 Print a decimal integer.
 The two control letters are equivalent.
 (The @samp{%i} specification is for compatibility with ISO C.)
 
-@item %e@r{,} %E
+@item @code{%e}, @code{%E}
 Print a number in scientific (exponential) notation;
 for example:
 
@@ -8425,7 +9036,7 @@ which follow the decimal point.
 discussed in the next @value{SUBSECTION}.)
 @samp{%E} uses @samp{E} instead of @samp{e} in the output.
 
-@item %f
+@item @code{%f}
 Print a number in floating-point notation.
 For example:
 
@@ -8445,39 +9056,40 @@ infinity are formatted as
 @samp{-inf} or @samp{-infinity},
 and positive infinity as
 @samp{inf} and @samp{infinity}.
-The special ``not a number'' value formats as @samp{-nan} or @samp{nan}.
+The special ``not a number'' value formats as @samp{-nan} or @samp{nan}
+(@pxref{Math Definitions}).
 
-@item %F
+@item @code{%F}
 Like @samp{%f} but the infinity and ``not a number'' values are spelled
 using uppercase letters.
 
 The @samp{%F} format is a POSIX extension to ISO C; not all systems
 support it.  On those that don't, @command{gawk} uses @samp{%f} instead.
 
-@item %g@r{,} %G
+@item @code{%g}, @code{%G}
 Print a number in either scientific notation or in floating-point
 notation, whichever uses fewer characters; if the result is printed in
 scientific notation, @samp{%G} uses @samp{E} instead of @samp{e}.
 
-@item %o
+@item @code{%o}
 Print an unsigned octal integer
 (@pxref{Nondecimal-numbers}).
 
-@item %s
+@item @code{%s}
 Print a string.
 
-@item %u
+@item @code{%u}
 Print an unsigned decimal integer.
 (This format is of marginal use, because all numbers in @command{awk}
 are floating-point; it is provided primarily for compatibility with C.)
 
-@item %x@r{,} %X
+@item @code{%x}, @code{%X}
 Print an unsigned hexadecimal integer;
 @samp{%X} uses the letters @samp{A} through @samp{F}
 instead of @samp{a} through @samp{f}
 (@pxref{Nondecimal-numbers}).
 
-@item %%
+@item @code{%%}
 Print a single @samp{%}.
 This does not consume an
 argument and it ignores any modifiers.
@@ -8512,7 +9124,7 @@ which they may appear:
 @table @code
 @cindex differences in @command{awk} and @command{gawk}, @code{print}/@code{printf} statements
 @cindex @code{printf} statement, positional specifiers
-@c the command does NOT start a secondary
+@c the code{} does NOT start a secondary
 @cindex positional specifiers, @code{printf} statement
 @item @var{N}$
 An integer constant followed by a @samp{$} is a @dfn{positional specifier}.
@@ -8588,7 +9200,7 @@ For example:
 $ @kbd{cat thousands.awk}          @ii{Show source program}
 @print{} BEGIN @{ printf "%'d\n", 1234567 @}
 $ @kbd{LC_ALL=C gawk -f thousands.awk}
-@print{} 1234567                   @ii{Results in "C" locale}
+@print{} 1234567                   @ii{Results in} "C" @ii{locale}
 $ @kbd{LC_ALL=en_US.UTF-8 gawk -f thousands.awk}
 @print{} 1,234,567                 @ii{Results in US English UTF locale}
 @end example
@@ -8698,14 +9310,12 @@ This is not particularly easy to read but it does work.
 @c @cindex lint checks
 @cindex troubleshooting, fatal errors, @code{printf} format strings
 @cindex POSIX @command{awk}, @code{printf} format strings and
-C programmers may be used to supplying additional
-@samp{l}, @samp{L}, and @samp{h}
-modifiers in @code{printf} format strings. These are not valid in @command{awk}.
-Most @command{awk} implementations silently ignore them.
-If @option{--lint} is provided on the command line
-(@pxref{Options}),
-@command{gawk} warns about their use. If @option{--posix} is supplied,
-their use is a fatal error.
+C programmers may be used to supplying additional modifiers (@samp{h},
+@samp{j}, @samp{l}, @samp{L}, @samp{t}, and @samp{z}) in @code{printf}
+format strings. These are not valid in @command{awk}.  Most @command{awk}
+implementations silently ignore them.  If @option{--lint} is provided
+on the command line (@pxref{Options}), @command{gawk} warns about their
+use. If @option{--posix} is supplied, their use is a fatal error.
 @c ENDOFRANGE pfm
 
 @node Printf Examples
@@ -8715,30 +9325,30 @@ The following simple example shows
 how to use @code{printf} to make an aligned table:
 
 @example
-awk '@{ printf "%-10s %s\n", $1, $2 @}' BBS-list
+awk '@{ printf "%-10s %s\n", $1, $2 @}' mail-list
 @end example
 
 @noindent
 This command
-prints the names of the bulletin boards (@code{$1}) in the file
-@file{BBS-list} as a string of 10 characters that are left-justified.  It also
+prints the names of the people (@code{$1}) in the file
+@file{mail-list} as a string of 10 characters that are left-justified.  It also
 prints the phone numbers (@code{$2}) next on the line.  This
 produces an aligned two-column table of names and phone numbers,
 as shown here:
 
 @example
-$ @kbd{awk '@{ printf "%-10s %s\n", $1, $2 @}' BBS-list}
-@print{} aardvark   555-5553
-@print{} alpo-net   555-3412
-@print{} barfly     555-7685
-@print{} bites      555-1675
-@print{} camelot    555-0542
-@print{} core       555-2912
-@print{} fooey      555-1234
-@print{} foot       555-6699
-@print{} macfoo     555-6480
-@print{} sdace      555-3430
-@print{} sabafoo    555-2127
+$ @kbd{awk '@{ printf "%-10s %s\n", $1, $2 @}' mail-list}
+@print{} Amelia     555-5553
+@print{} Anthony    555-3412
+@print{} Becky      555-7685
+@print{} Bill       555-1675
+@print{} Broderick  555-0542
+@print{} Camilla    555-2912
+@print{} Fabius     555-1234
+@print{} Julie      555-6699
+@print{} Martin     555-6480
+@print{} Samuel     555-3430
+@print{} Jean-Paul  555-2127
 @end example
 
 In this case, the phone numbers had to be printed as strings because
@@ -8751,7 +9361,7 @@ they are last on their lines.  They don't need to have spaces
 after them.
 
 The table could be made to look even nicer by adding headings to the
-tops of the columns.  This is done using the @code{BEGIN} pattern
+tops of the columns.  This is done using a @code{BEGIN} rule
 (@pxref{BEGIN/END})
 so that the headers are only printed once, at the beginning of
 the @command{awk} program:
@@ -8759,7 +9369,7 @@ the @command{awk} program:
 @example
 awk 'BEGIN @{ print "Name      Number"
              print "----      ------" @}
-     @{ printf "%-10s %s\n", $1, $2 @}' BBS-list
+     @{ printf "%-10s %s\n", $1, $2 @}' mail-list
 @end example
 
 The above example mixes @code{print} and @code{printf} statements in
@@ -8769,7 +9379,7 @@ same results:
 @example
 awk 'BEGIN @{ printf "%-10s %s\n", "Name", "Number"
              printf "%-10s %s\n", "----", "------" @}
-     @{ printf "%-10s %s\n", $1, $2 @}' BBS-list
+     @{ printf "%-10s %s\n", $1, $2 @}' mail-list
 @end example
 
 @noindent
@@ -8784,23 +9394,19 @@ emphasized by storing it in a variable, like this:
 awk 'BEGIN @{ format = "%-10s %s\n"
              printf format, "Name", "Number"
              printf format, "----", "------" @}
-     @{ printf format, $1, $2 @}' BBS-list
+     @{ printf format, $1, $2 @}' mail-list
 @end example
 
-@c !!! exercise
-At this point, it would be a worthwhile exercise to use the
-@code{printf} statement to line up the headings and table data for the
-@file{inventory-shipped} example that was covered earlier in the @value{SECTION}
-on the @code{print} statement
-(@pxref{Print}).
 @c ENDOFRANGE printfs
 
 @node Redirection
 @section Redirecting Output of @code{print} and @code{printf}
 
+@c STARTOFRANGE outre
 @cindex output redirection
+@c STARTOFRANGE reout
 @cindex redirection of output
-@cindex @code{--sandbox} option, output redirection with @code{print}, @code{printf}
+@cindex @option{--sandbox} option, output redirection with @code{print}, @code{printf}
 So far, the output from @code{print} and @code{printf} has gone
 to the standard
 output, usually the screen.  Both @code{print} and @code{printf} can
@@ -8817,11 +9423,11 @@ Redirections in @command{awk} are written just like redirections in shell
 commands, except that they are written inside the @command{awk} program.
 
 @c the commas here are part of the see also
-@cindex @code{print} statement, See Also redirection, of output
-@cindex @code{printf} statement, See Also redirection, of output
+@cindex @code{print} statement, See Also redirection@comma{} of output
+@cindex @code{printf} statement, See Also redirection@comma{} of output
 There are four forms of output redirection: output to a file, output
 appended to a file, output through a pipe to another command, and output
-to a coprocess.  They are all shown for the @code{print} statement,
+to a coprocess.  We show them all for the @code{print} statement,
 but they work identically for @code{printf}:
 
 @table @code
@@ -8830,29 +9436,29 @@ but they work identically for @code{printf}:
 @cindex operators, input/output
 @item print @var{items} > @var{output-file}
 This redirection prints the items into the output file named
-@var{output-file}.  The file name @var{output-file} can be any
+@var{output-file}.  The @value{FN} @var{output-file} can be any
 expression.  Its value is changed to a string and then used as a
-file name (@pxref{Expressions}).
+@value{FN} (@pxref{Expressions}).
 
 When this type of redirection is used, the @var{output-file} is erased
 before the first output is written to it.  Subsequent writes to the same
 @var{output-file} do not erase @var{output-file}, but append to it.
 (This is different from how you use redirections in shell scripts.)
 If @var{output-file} does not exist, it is created.  For example, here
-is how an @command{awk} program can write a list of BBS names to one
+is how an @command{awk} program can write a list of peoples' names to one
 file named @file{name-list}, and a list of phone numbers to another file
 named @file{phone-list}:
 
 @example
 $ @kbd{awk '@{ print $2 > "phone-list"}
->        @kbd{print $1 > "name-list" @}' BBS-list}
+>        @kbd{print $1 > "name-list" @}' mail-list}
 $ @kbd{cat phone-list}
 @print{} 555-5553
 @print{} 555-3412
 @dots{}
 $ @kbd{cat name-list}
-@print{} aardvark
-@print{} alpo-net
+@print{} Amelia
+@print{} Anthony
 @dots{}
 @end example
 
@@ -8870,7 +9476,7 @@ appended to the file.
 If @var{output-file} does not exist, then it is created.
 
 @cindex @code{|} (vertical bar), @code{|} operator (I/O)
-@cindex pipes, output
+@cindex pipe, output
 @cindex output, pipes
 @item print @var{items} | @var{command}
 It is possible to send output to another program through a pipe
@@ -8881,7 +9487,7 @@ to another process created to execute @var{command}.
 The redirection argument @var{command} is actually an @command{awk}
 expression.  Its value is converted to a string whose contents give
 the shell command to be run.  For example, the following produces two
-files, one unsorted list of BBS names, and one list sorted in reverse
+files, one unsorted list of peoples' names, and one list sorted in reverse
 alphabetical order:
 
 @ignore
@@ -8894,7 +9500,7 @@ alone for now and let's hope no-one notices.
 @example
 awk '@{ print $1 > "names.unsorted"
        command = "sort -r > names.sorted"
-       print $1 | command @}' BBS-list
+       print $1 | command @}' mail-list
 @end example
 
 The unsorted list is written with an ordinary redirection, while
@@ -8926,7 +9532,7 @@ This example also illustrates the use of a variable to represent
 a @var{file} or @var{command}---it is not necessary to always
 use a string constant.  Using a variable is generally a good idea,
 because (if you mean to refer to that same file or command)
-@command{awk} requires that the string value be spelled identically
+@command{awk} requires that the string value be written identically
 every time.
 
 @cindex coprocesses
@@ -8985,7 +9591,9 @@ As mentioned earlier
 many
 @end ifnotinfo
 @ifnottex
+@ifnotdocbook
 Many
+@end ifnotdocbook
 @end ifnottex
 older
 @command{awk} implementations limit the number of pipelines that an @command{awk}
@@ -9003,7 +9611,7 @@ open as many pipelines as the underlying operating system permits.
 
 A particularly powerful way to use redirection is to build command lines
 and pipe them into the shell, @command{sh}.  For example, suppose you
-have a list of files brought over from a system where all the file names
+have a list of files brought over from a system where all the @value{FN}s
 are stored in uppercase, and you wish to rename them to have names in
 all lowercase.  The following program is both simple and efficient:
 
@@ -9035,7 +9643,7 @@ It then sends the list to the shell for execution.
 
 A particularly powerful way to use redirection is to build command lines
 and pipe them into the shell, @command{sh}.  For example, suppose you
-have a list of files brought over from a system where all the file names
+have a list of files brought over from a system where all the @value{FN}s
 are stored in uppercase, and you wish to rename them to have names in
 all lowercase.  The following program is both simple and efficient:
 
@@ -9058,12 +9666,12 @@ It then sends the list to the shell for execution.
 @c ENDOFRANGE reout
 
 @node Special Files
-@section Special File Names in @command{gawk}
+@section Special @value{FFN} in @command{gawk}
 @c STARTOFRANGE gfn
 @cindex @command{gawk}, file names in
 
-@command{gawk} provides a number of special file names that it interprets
-internally.  These file names provide access to standard file descriptors
+@command{gawk} provides a number of special @value{FN}s that it interprets
+internally.  These @value{FN}s provide access to standard file descriptors
 and TCP/IP networking.
 
 @menu
@@ -9127,12 +9735,12 @@ that happens, writing to the screen is not correct.  In fact, if
 terminal at all.
 Then opening @file{/dev/tty} fails.
 
-@command{gawk} provides special file names for accessing the three standard
-streams. @value{COMMONEXT}. It also provides syntax for accessing
-any other inherited open files.  If the file name matches
+@command{gawk} provides special @value{FN}s for accessing the three standard
+streams. @value{COMMONEXT} It also provides syntax for accessing
+any other inherited open files.  If the @value{FN} matches
 one of these special names when @command{gawk} redirects input or output,
-then it directly uses the stream that the file name stands for.
-These special file names work for all operating systems that @command{gawk}
+then it directly uses the stream that the @value{FN} stands for.
+These special @value{FN}s work for all operating systems that @command{gawk}
 has been ported to, not just those that are POSIX-compliant:
 
 @cindex common extensions, @code{/dev/stdin} special file
@@ -9142,9 +9750,9 @@ has been ported to, not just those that are POSIX-compliant:
 @cindex extensions, common@comma{} @code{/dev/stdout} special file
 @cindex extensions, common@comma{} @code{/dev/stderr} special file
 @cindex file names, standard streams in @command{gawk}
-@cindex @code{/dev/@dots{}} special files (@command{gawk})
+@cindex @code{/dev/@dots{}} special files
 @cindex files, @code{/dev/@dots{}} special files
-@cindex @code{/dev/fd/@var{N}} special files
+@cindex @code{/dev/fd/@var{N}} special files (@command{gawk})
 @table @file
 @item /dev/stdin
 The standard input (file descriptor 0).
@@ -9162,7 +9770,7 @@ the shell).  Unless special pains are taken in the shell from which
 @command{gawk} is invoked, only descriptors 0, 1, and 2 are available.
 @end table
 
-The file names @file{/dev/stdin}, @file{/dev/stdout}, and @file{/dev/stderr}
+The @value{FN}s @file{/dev/stdin}, @file{/dev/stdout}, and @file{/dev/stderr}
 are aliases for @file{/dev/fd/0}, @file{/dev/fd/1}, and @file{/dev/fd/2},
 respectively. However, they are more self-explanatory.
 The proper way to write an error message in a @command{gawk} program
@@ -9173,13 +9781,12 @@ print "Serious error detected!" > "/dev/stderr"
 @end example
 
 @cindex troubleshooting, quotes with file names
-Note the use of quotes around the file name.
+Note the use of quotes around the @value{FN}.
 Like any other redirection, the value must be a string.
 It is a common error to omit the quotes, which leads
 to confusing results.
-@c Exercise: What does it do?  :-)
 
-Finally, using the @code{close()} function on a file name of the
+Finally, using the @code{close()} function on a @value{FN} of the
 form @code{"/dev/fd/@var{N}"}, for file descriptor numbers
 above two, does actually close the given file descriptor.
 
@@ -9195,7 +9802,7 @@ versions of @command{awk}.
 @command{gawk} programs
 can open a two-way
 TCP/IP connection, acting as either a client or a server.
-This is done using a special file name of the form:
+This is done using a special @value{FN} of the form:
 
 @example
 @file{/@var{net-type}/@var{protocol}/@var{local-port}/@var{remote-host}/@var{remote-port}}
@@ -9205,7 +9812,7 @@ The @var{net-type} is one of @samp{inet}, @samp{inet4} or @samp{inet6}.
 The @var{protocol} is one of @samp{tcp} or @samp{udp},
 and the other fields represent the other essential pieces of information
 for making a networking connection.
-These file names are used with the @samp{|&} operator for communicating
+These @value{FN}s are used with the @samp{|&} operator for communicating
 with a coprocess
 (@pxref{Two-way I/O}).
 This is an advanced feature, mentioned here only for completeness.
@@ -9213,21 +9820,21 @@ Full discussion is delayed until
 @ref{TCP/IP Networking}.
 
 @node Special Caveats
-@subsection Special File Name Caveats
+@subsection Special @value{FFN} Caveats
 
 Here is a list of things to bear in mind when using the
-special file names that @command{gawk} provides:
+special @value{FN}s that @command{gawk} provides:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @cindex compatibility mode (@command{gawk}), file names
 @cindex file names, in compatibility mode
 @item
-Recognition of these special file names is disabled if @command{gawk} is in
+Recognition of these special @value{FN}s is disabled if @command{gawk} is in
 compatibility mode (@pxref{Options}).
 
 @item
 @command{gawk} @emph{always}
-interprets these special file names.
+interprets these special @value{FN}s.
 For example, using @samp{/dev/fd/4}
 for output actually writes on file descriptor 4, and not on a new
 file descriptor that is @code{dup()}'ed from file descriptor 4.  Most of
@@ -9245,12 +9852,12 @@ Doing so results in unpredictable behavior.
 @c STARTOFRANGE ofc
 @cindex output, files@comma{} closing
 @c STARTOFRANGE pc
-@cindex pipes, closing
+@cindex pipe, closing
 @c STARTOFRANGE cc
 @cindex coprocesses, closing
 @cindex @code{getline} command, coprocesses@comma{} using from
 
-If the same file name or the same shell command is used with @code{getline}
+If the same @value{FN} or the same shell command is used with @code{getline}
 more than once during the execution of an @command{awk} program
 (@pxref{Getline}),
 the file is opened (or the command is executed) the first time only.
@@ -9259,11 +9866,11 @@ The next time the same file or command is used with @code{getline},
 another record is read from it, and so on.
 
 Similarly, when a file or pipe is opened for output, @command{awk} remembers
-the file name or command associated with it, and subsequent
+the @value{FN} or command associated with it, and subsequent
 writes to the same file or command are appended to the previous writes.
 The file or pipe stays open until @command{awk} exits.
 
-@cindex @code{close()} function
+@cindexawkfunc{close}
 This implies that special steps are necessary in order to read the same
 file again from the beginning, or to rerun a shell command (rather than
 reading more output from the same command).  The @code{close()} function
@@ -9301,7 +9908,7 @@ file or command, or the next @code{print} or @code{printf} to that
 file or command, reopens the file or reruns the command.
 Because the expression that you use to close a file or pipeline must
 exactly match the expression used to open the file or run the command,
-it is good practice to use a variable to store the file name or command.
+it is good practice to use a variable to store the @value{FN} or command.
 The previous example becomes the following:
 
 @example
@@ -9315,7 +9922,7 @@ close(sortcom)
 This helps avoid hard-to-find typographical errors in your @command{awk}
 programs.  Here are some of the reasons for closing an output file:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 To write a file and read it back later on in the same @command{awk}
 program.  Close the file after writing it, then
@@ -9348,9 +9955,10 @@ a separate message.
 
 @cindex differences in @command{awk} and @command{gawk}, @code{close()} function
 @cindex portability, @code{close()} function and
+@cindex @code{close()} function, portability
 If you use more files than the system allows you to have open,
 @command{gawk} attempts to multiplex the available open files among
-your data files.  @command{gawk}'s ability to do this depends upon the
+your @value{DF}s.  @command{gawk}'s ability to do this depends upon the
 facilities of your operating system, so it may not always work.  It is
 therefore both good practice and good portability advice to always
 use @code{close()} on your files when you are done with them.
@@ -9383,15 +9991,16 @@ more importantly, the file descriptor for the pipe
 is not closed and released until @code{close()} is called or
 @command{awk} exits.
 
-@code{close()} will silently do nothing if given an argument that
+@code{close()} silently does nothing if given an argument that
 does not represent a file, pipe or coprocess that was opened with
-a redirection.
+a redirection.  In such a case, it returns a negative value,
+indicating an error. In addition, @command{gawk} sets @code{ERRNO}
+to a string indicating the error.
 
-Note also that @samp{close(FILENAME)} has no
-``magic'' effects on the implicit loop that reads through the
-files named on the command line.  It is, more likely, a close
-of a file that was never opened, so @command{awk} silently
-does nothing.
+Note also that @samp{close(FILENAME)} has no ``magic'' effects on the
+implicit loop that reads through the files named on the command line.
+It is, more likely, a close of a file that was never opened with a
+redirection, so @command{awk} silently does nothing.
 
 @cindex @code{|} (vertical bar), @code{|&} operator (I/O), pipes@comma{} closing
 When using the @samp{|&} operator to communicate with a coprocess,
@@ -9420,7 +10029,7 @@ which discusses it in more detail and gives an example.
 @cindex differences in @command{awk} and @command{gawk}, @code{close()} function
 @cindex Unix @command{awk}, @code{close()} function and
 
-In many versions of Unix @command{awk}, the @code{close()} function
+In many older versions of Unix @command{awk}, the @code{close()} function
 is actually a statement.  It is a syntax error to try and use the return
 value from @code{close()}:
 @value{DARKCORNER}
@@ -9432,7 +10041,7 @@ retval = close(command)  # syntax error in many Unix awks
 @end example
 
 @cindex @command{gawk}, @code{ERRNO} variable in
-@cindex @code{ERRNO} variable
+@cindex @code{ERRNO} variable, with @command{close()} function
 @command{gawk} treats @code{close()} as a function.
 The return value is @minus{}1 if the argument names something
 that was never opened with a redirection, or if there is
@@ -9476,7 +10085,7 @@ when closing a pipe.
 @cindex differences in @command{awk} and @command{gawk}, @code{close()} function
 @cindex Unix @command{awk}, @code{close()} function and
 
-In many versions of Unix @command{awk}, the @code{close()} function
+In many older versions of Unix @command{awk}, the @code{close()} function
 is actually a statement.  It is a syntax error to try and use the return
 value from @code{close()}:
 @value{DARKCORNER}
@@ -9488,7 +10097,7 @@ retval = close(command)  # syntax error in many Unix awks
 @end example
 
 @cindex @command{gawk}, @code{ERRNO} variable in
-@cindex @code{ERRNO} variable
+@cindex @code{ERRNO} variable, with @command{close()} function
 @command{gawk} treats @code{close()} as a function.
 The return value is @minus{}1 if the argument names something
 that was never opened with a redirection, or if there is
@@ -9522,6 +10131,67 @@ when closing a pipe.
 @c ENDOFRANGE ofc
 @c ENDOFRANGE pc
 @c ENDOFRANGE cc
+
+@node Output Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+The @code{print} statement prints comma-separated expressions. Each
+expression is separated by the value of @code{OFS} and terminated by
+the value of @code{ORS}.  @code{OFMT} provides the conversion format
+for numeric values for the @code{print} statement.
+
+@item
+The @code{printf} statement provides finer-grained control over output,
+with format control letters for different data types and various flags
+that modify the behavior of the format control letters.
+
+@item
+Output from both @code{print} and @code{printf} may be redirected to
+files, pipes, and co-processes.
+
+@item
+@command{gawk} provides special file names for access to standard input,
+output and error, and for network communications.
+
+@item
+Use @code{close()} to close open file, pipe and co-process redirections.
+For co-processes, it is possible to close only one direction of the
+communications.
+
+@end itemize
+
+@node Output exercises
+@section Exercises
+
+@enumerate
+@item
+Rewrite the program:
+
+@example
+awk 'BEGIN @{ print "Month Crates"
+             print "----- ------" @}
+           @{ print $1, "     ", $2 @}' inventory-shipped
+@end example
+
+@noindent
+from @ref{Output Separators}, by using a new value of @code{OFS}.
+
+@item
+Use the @code{printf} statement to line up the headings and table data
+for the @file{inventory-shipped} example that was covered in @ref{Print}.
+
+@item
+What happens if you forget the double quotes when redirecting
+output, as follows:
+
+@example
+BEGIN @{ print "Serious error detected!" > /dev/stderr @}
+@end example
+
+@end enumerate
+
 @c ENDOFRANGE prnt
 
 @node Expressions
@@ -9548,6 +10218,7 @@ combinations of these with various operators.
 * Function Calls::              A function call is an expression.
 * Precedence::                  How various operators nest.
 * Locales::                     How the locale affects things.
+* Expressions Summary::         Expressions summary.
 @end menu
 
 @node Values
@@ -9567,6 +10238,8 @@ which provide the values used in expressions.
 
 @node Constants
 @subsection Constant Expressions
+
+@c STARTOFRANGE cnst
 @cindex constants, types of
 
 The simplest type of expression is the @dfn{constant}, which always has
@@ -9586,13 +10259,14 @@ have different forms, but are stored identically internally.
 @node Scalar Constants
 @subsubsection Numeric and String Constants
 
-@cindex numeric, constants
+@cindex constants, numeric
+@cindex numeric constants
 A @dfn{numeric constant} stands for a number.  This number can be an
 integer, a decimal fraction, or a number in scientific (exponential)
 notation.@footnote{The internal representation of all numbers,
-including integers, uses double precision
-floating-point numbers.
-On most modern systems, these are in IEEE 754 standard format.}
+including integers, uses double precision floating-point numbers.
+On most modern systems, these are in IEEE 754 standard format.
+@xref{Arbitrary Precision Arithmetic}, for much more information.}
 Here are some examples of numeric constants that all
 have the same value:
 
@@ -9612,7 +10286,7 @@ double-quotation marks.  For example:
 
 @noindent
 @cindex differences in @command{awk} and @command{gawk}, strings
-@cindex strings, length of
+@cindex strings, length limitations
 represents the string whose contents are @samp{parrot}.  Strings in
 @command{gawk} can be of any length, and they can contain any of the possible
 eight-bit ASCII characters including ASCII @sc{nul} (character code zero).
@@ -9828,13 +10502,13 @@ upon the contents of the current input record.
 
 @cindex differences in @command{awk} and @command{gawk}, regexp constants
 @cindex dark corner, regexp constants, as arguments to user-defined functions
-@cindex @code{gensub()} function (@command{gawk})
-@cindex @code{sub()} function
-@cindex @code{gsub()} function
+@cindexgawkfunc{gensub}
+@cindexawkfunc{sub}
+@cindexawkfunc{gsub}
 Constant regular expressions are also used as the first argument for
 the @code{gensub()}, @code{sub()}, and @code{gsub()} functions, as the
 second argument of the @code{match()} function,
-and as the third argument of the @code{patsplit()} function
+and as the third argument of the @code{split()} and @code{patsplit()} functions
 (@pxref{String Functions}).
 Modern implementations of @command{awk}, including @command{gawk}, allow
 the third argument of @code{split()} to be a regexp constant, but some
@@ -9941,7 +10615,7 @@ Such an assignment has the following form:
 @var{variable}=@var{text}
 @end example
 
-@cindex @code{-v} option
+@cindex @option{-v} option
 @noindent
 With it, a variable is set either at the beginning of the
 @command{awk} run or in between input files.
@@ -9955,7 +10629,7 @@ as in the following:
 @noindent
 the variable is set at the very beginning, even before the
 @code{BEGIN} rules execute.  The @option{-v} option and its assignment
-must precede all the file name arguments, as well as the program text.
+must precede all the @value{FN} arguments, as well as the program text.
 (@xref{Options}, for more information about
 the @option{-v} option.)
 Otherwise, the variable assignment is performed at a time determined by
@@ -9963,7 +10637,7 @@ its position among the input file arguments---after the processing of the
 preceding input file argument.  For example:
 
 @example
-awk '@{ print $n @}' n=4 inventory-shipped n=2 BBS-list
+awk '@{ print $n @}' n=4 inventory-shipped n=2 mail-list
 @end example
 
 @noindent
@@ -9972,10 +10646,10 @@ the first file is read, the command line sets the variable @code{n}
 equal to four.  This causes the fourth field to be printed in lines from
 @file{inventory-shipped}.  After the first file has finished,
 but before the second file is started, @code{n} is set to two, so that the
-second field is printed in lines from @file{BBS-list}:
+second field is printed in lines from @file{mail-list}:
 
 @example
-$ @kbd{awk '@{ print $n @}' n=4 inventory-shipped n=2 BBS-list}
+$ @kbd{awk '@{ print $n @}' n=4 inventory-shipped n=2 mail-list}
 @print{} 15
 @print{} 24
 @dots{}
@@ -9996,6 +10670,19 @@ sequences
 @node Conversion
 @subsection Conversion of Strings and Numbers
 
+Number to string and string to number conversion are generally
+straightforward.  There can be subtleties to be aware of;
+this @value{SECTION} discusses this important facet of @command{awk}.
+
+@menu
+* Strings And Numbers::         How @command{awk} Converts Between Strings And
+                                Numbers.
+* Locale influences conversions:: How the locale may affect conversions.
+@end menu
+
+@node Strings And Numbers
+@subsubsection How @command{awk} Converts Between Strings And Numbers
+
 @cindex converting, strings to numbers
 @cindex strings, converting
 @cindex numbers, converting
@@ -10065,6 +10752,12 @@ b = a ""
 @code{b} has the value @code{"12"}, not @code{"12.00"}.
 @value{DARKCORNER}
 
+@cindex sidebar, Pre-POSIX @command{awk} Used @code{OFMT} For String Conversion
+@ifdocbook
+@docbook
+<sidebar><title>Pre-POSIX @command{awk} Used @code{OFMT} For String Conversion</title>
+@end docbook
+
 @cindex POSIX @command{awk}, @code{OFMT} variable and
 @cindex @code{OFMT} variable
 @cindex portability, new @command{awk} vs.@: old @command{awk}
@@ -10076,32 +10769,56 @@ specifies the output format to use when printing numbers with @code{print}.
 conversion from the semantics of printing.  Both @code{CONVFMT} and
 @code{OFMT} have the same default value: @code{"%.6g"}.  In the vast majority
 of cases, old @command{awk} programs do not change their behavior.
-However, these semantics for @code{OFMT} are something to keep in mind if you must
-port your new-style program to older implementations of @command{awk}.
-We recommend
-that instead of changing your programs, just port @command{gawk} itself.
-@xref{Print},
-for more information on the @code{print} statement.
-
-And, once again, where you are can matter when it comes to converting
-between numbers and strings.  In @ref{Locales}, we mentioned that
-the local character set and language (the locale) can affect how
-@command{gawk} matches characters.  The locale also affects numeric
-formats.  In particular, for @command{awk} programs, it affects the
-decimal point character.  The @code{"C"} locale, and most English-language
-locales, use the period character (@samp{.}) as the decimal point.
-However, many (if not most) European and non-English locales use the comma
-(@samp{,}) as the decimal point character.
+@xref{Print}, for more information on the @code{print} statement.
+
+@docbook
+</sidebar>
+@end docbook
+@end ifdocbook
+
+@ifnotdocbook
+@cartouche
+@center @b{Pre-POSIX @command{awk} Used @code{OFMT} For String Conversion}
+
+
+@cindex POSIX @command{awk}, @code{OFMT} variable and
+@cindex @code{OFMT} variable
+@cindex portability, new @command{awk} vs.@: old @command{awk}
+@cindex @command{awk}, new vs.@: old, @code{OFMT} variable
+Prior to the POSIX standard, @command{awk} used the value
+of @code{OFMT} for converting numbers to strings.  @code{OFMT}
+specifies the output format to use when printing numbers with @code{print}.
+@code{CONVFMT} was introduced in order to separate the semantics of
+conversion from the semantics of printing.  Both @code{CONVFMT} and
+@code{OFMT} have the same default value: @code{"%.6g"}.  In the vast majority
+of cases, old @command{awk} programs do not change their behavior.
+@xref{Print}, for more information on the @code{print} statement.
+@end cartouche
+@end ifnotdocbook
+
+@node Locale influences conversions
+@subsubsection Locales Can Influence Conversion
+
+Where you are can matter when it comes to converting between numbers and
+strings.  The local character set and language---the @dfn{locale}---can
+affect numeric formats.  In particular, for @command{awk} programs,
+it affects the decimal point character and the thousands-separator
+character.  The @code{"C"} locale, and most English-language locales,
+use the period character (@samp{.}) as the decimal point and don't
+have a thousands separator.  However, many (if not most) European and
+non-English locales use the comma (@samp{,}) as the decimal point
+character. European locales often use either a space or a period as
+the thousands separator, if they have one.
 
 @cindex dark corner, locale's decimal point character
 The POSIX standard says that @command{awk} always uses the period as the decimal
-point when reading the @command{awk} program source code, and for command-line
-variable assignments (@pxref{Other Arguments}).
-However, when interpreting input data, for @code{print} and @code{printf} output,
-and for number to string conversion, the local decimal point character is used.
-@value{DARKCORNER}.
-Here are some examples indicating the difference in behavior,
-on a GNU/Linux system:
+point when reading the @command{awk} program source code, and for
+command-line variable assignments (@pxref{Other Arguments}).  However,
+when interpreting input data, for @code{print} and @code{printf} output,
+and for number to string conversion, the local decimal point character
+is used.  @value{DARKCORNER} In all cases, numbers in source code and
+in input data cannot have a thousands separator.  Here are some examples
+indicating the difference in behavior, on a GNU/Linux system:
 
 @example
 $ @kbd{export POSIXLY_CORRECT=1}                        @ii{Force POSIX behavior}
@@ -10116,7 +10833,7 @@ $ @kbd{echo 4,321 | LC_ALL=en_DK.utf-8 gawk '@{ print $1 + 1 @}'}
 @end example
 
 @noindent
-The @samp{en_DK.utf-8} locale is for English in Denmark, where the comma acts as
+The @code{en_DK.utf-8} locale is for English in Denmark, where the comma acts as
 the decimal point separator.  In the normal @code{"C"} locale, @command{gawk}
 treats @samp{4,321} as @samp{4}, while in the Danish locale, it's treated
 as the full number, 4.321.
@@ -10263,7 +10980,7 @@ b * int(a / b) + (a % b) == a
 @end example
 
 One possibly undesirable effect of this definition of remainder is that
-@code{@var{x} % @var{y}} is negative if @var{x} is negative.  Thus:
+@samp{@var{x} % @var{y}} is negative if @var{x} is negative.  Thus:
 
 @example
 -17 % 8 = -1
@@ -10271,7 +10988,7 @@ One possibly undesirable effect of this definition of remainder is that
 
 In other @command{awk} implementations, the signedness of the remainder
 may be machine-dependent.
-@c !!! what does posix say?
+@c FIXME !!! what does posix say?
 
 @cindex portability, @code{**} operator and
 @cindex @code{*} (asterisk), @code{**} operator
@@ -10298,9 +11015,9 @@ specific operator to represent it.  Instead, concatenation is performed by
 writing expressions next to one another, with no operator.  For example:
 
 @example
-$ @kbd{awk '@{ print "Field number one: " $1 @}' BBS-list}
-@print{} Field number one: aardvark
-@print{} Field number one: alpo-net
+$ @kbd{awk '@{ print "Field number one: " $1 @}' mail-list}
+@print{} Field number one: Amelia
+@print{} Field number one: Anthony
 @dots{}
 @end example
 
@@ -10308,9 +11025,9 @@ Without the space in the string constant after the @samp{:}, the line
 runs together.  For example:
 
 @example
-$ @kbd{awk '@{ print "Field number one:" $1 @}' BBS-list}
-@print{} Field number one:aardvark
-@print{} Field number one:alpo-net
+$ @kbd{awk '@{ print "Field number one:" $1 @}' mail-list}
+@print{} Field number one:Amelia
+@print{} Field number one:Anthony
 @dots{}
 @end example
 
@@ -10327,6 +11044,8 @@ name = "name"
 print "something meaningful" > file name
 @end example
 
+@cindex Brian Kernighan's @command{awk}
+@cindex @command{mawk} utility
 @noindent
 This produces a syntax error with some versions of Unix
 @command{awk}.@footnote{It happens that Brian Kernighan's
@@ -10355,7 +11074,7 @@ BEGIN @{
 @end example
 
 @noindent
-It is not defined whether the assignment to @code{a} happens
+It is not defined whether the second assignment to @code{a} happens
 before or after the value of @code{a} is retrieved for producing the
 concatenated value.  The result could be either @samp{don't panic},
 or @samp{panic panic}.
@@ -10477,8 +11196,8 @@ element. (Such values are called @dfn{rvalues}.)
 
 @cindex variables, types of
 It is important to note that variables do @emph{not} have permanent types.
-A variable's type is simply the type of whatever value it happens
-to hold at the moment.  In the following program fragment, the variable
+A variable's type is simply the type of whatever value was last assigned
+to it.  In the following program fragment, the variable
 @code{foo} has a numeric value at first, and a string value later on:
 
 @example
@@ -10579,6 +11298,7 @@ The indices of @code{bar} are practically guaranteed to be different, because
 and see @ref{Numeric Functions}, for more information).
 This example illustrates an important fact about assignment
 operators: the lefthand expression is only evaluated @emph{once}.
+
 It is up to the implementation as to which expression is evaluated
 first, the lefthand or the righthand.
 Consider this example:
@@ -10611,17 +11331,17 @@ to a number.
 @caption{Arithmetic Assignment Operators}
 @multitable @columnfractions .30 .70
 @headitem Operator @tab Effect
-@item @var{lvalue} @code{+=} @var{increment} @tab Adds @var{increment} to the value of @var{lvalue}.
-@item @var{lvalue} @code{-=} @var{decrement} @tab Subtracts @var{decrement} from the value of @var{lvalue}.
-@item @var{lvalue} @code{*=} @var{coefficient} @tab Multiplies the value of @var{lvalue} by @var{coefficient}.
-@item @var{lvalue} @code{/=} @var{divisor} @tab Divides the value of @var{lvalue} by @var{divisor}.
-@item @var{lvalue} @code{%=} @var{modulus} @tab Sets @var{lvalue} to its remainder by @var{modulus}.
+@item @var{lvalue} @code{+=} @var{increment} @tab Add @var{increment} to the value of @var{lvalue}.
+@item @var{lvalue} @code{-=} @var{decrement} @tab Subtract @var{decrement} from the value of @var{lvalue}.
+@item @var{lvalue} @code{*=} @var{coefficient} @tab Multiply the value of @var{lvalue} by @var{coefficient}.
+@item @var{lvalue} @code{/=} @var{divisor} @tab Divide the value of @var{lvalue} by @var{divisor}.
+@item @var{lvalue} @code{%=} @var{modulus} @tab Set @var{lvalue} to its remainder by @var{modulus}.
 @cindex common extensions, @code{**=} operator
 @cindex extensions, common@comma{} @code{**=} operator
 @cindex @command{awk} language, POSIX version
 @cindex POSIX @command{awk}
 @item @var{lvalue} @code{^=} @var{power} @tab
-@item @var{lvalue} @code{**=} @var{power} @tab Raises @var{lvalue} to the power @var{power}. @value{COMMONEXT}
+@item @var{lvalue} @code{**=} @var{power} @tab Raise @var{lvalue} to the power @var{power}. @value{COMMONEXT}
 @end multitable
 @end float
 
@@ -10671,10 +11391,8 @@ A workaround is:
 awk '/[=]=/' /dev/null
 @end example
 
-@command{gawk} does not have this problem,
-nor do the other
-freely available versions described in
-@ref{Other Versions}.
+@command{gawk} does not have this problem; Brian Kernighan's @command{awk}
+and @command{mawk} also do not (@pxref{Other Versions}).
 
 @docbook
 </sidebar>
@@ -10719,10 +11437,8 @@ A workaround is:
 awk '/[=]=/' /dev/null
 @end example
 
-@command{gawk} does not have this problem,
-nor do the other
-freely available versions described in
-@ref{Other Versions}.
+@command{gawk} does not have this problem; Brian Kernighan's @command{awk}
+and @command{mawk} also do not (@pxref{Other Versions}).
 @end cartouche
 @end ifnotdocbook
 @c ENDOFRANGE exas
@@ -10747,11 +11463,10 @@ are convenient abbreviations for very common operations.
 @cindex side effects, decrement/increment operators
 The operator used for adding one is written @samp{++}.  It can be used to increment
 a variable either before or after taking its value.
-To pre-increment a variable @code{v}, write @samp{++v}.  This adds
+To @dfn{pre-increment} a variable @code{v}, write @samp{++v}.  This adds
 one to the value of @code{v}---that new value is also the value of the
-expression. (The assignment expression @samp{v += 1} is completely
-equivalent.)
-Writing the @samp{++} after the variable specifies post-increment.  This
+expression. (The assignment expression @samp{v += 1} is completely equivalent.)
+Writing the @samp{++} after the variable specifies @dfn{post-increment}.  This
 increments the variable value just the same; the difference is that the
 value of the increment expression itself is the variable's @emph{old}
 value.  Thus, if @code{foo} has the value four, then the expression @samp{foo++}
@@ -10763,7 +11478,18 @@ The post-increment @samp{foo++} is nearly the same as writing @samp{(foo
 += 1) - 1}.  It is not perfectly equivalent because all numbers in
 @command{awk} are floating-point---in floating-point, @samp{foo + 1 - 1} does
 not necessarily equal @code{foo}.  But the difference is minute as
-long as you stick to numbers that are fairly small (less than 10e12).
+long as you stick to numbers that are fairly small (less than
+@iftex
+@math{10^12}).
+@end iftex
+@ifnottex
+@ifnotdocbook
+10e12).
+@end ifnotdocbook
+@end ifnottex
+@docbook
+10<superscript>12</superscript>). @c
+@end docbook
 
 @cindex @code{$} (dollar sign), incrementing fields and arrays
 @cindex dollar sign (@code{$}), incrementing fields and arrays
@@ -10772,6 +11498,7 @@ just like variables.  (Use @samp{$(i++)} when you want to do a field reference
 and a variable increment at the same time.  The parentheses are necessary
 because of the precedence of the field reference operator @samp{$}.)
 
+@c STARTOFRANGE deop
 @cindex decrement operators
 The decrement operator @samp{--} works just like @samp{++}, except that
 it subtracts one instead of adding it.  As with @samp{++}, it can be used before
@@ -11008,6 +11735,7 @@ like a number---for example, @code{@w{" +2"}}.  This concept is used
 for determining the type of a variable.
 The type of the variable is important because the types of two variables
 determine how they are compared.
+
 The various versions of the POSIX standard did not get the rules
 quite right for several editions.  Fortunately, as of at least the
 2008 standard (and possibly earlier), the standard has been fixed,
@@ -11015,7 +11743,7 @@ and variable typing follows these rules:@footnote{@command{gawk} has
 followed these rules for many years,
 and it is gratifying that the POSIX standard is also now correct.}
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 A numeric constant or the result of a numeric operation has the @var{numeric}
 attribute.
@@ -11101,6 +11829,7 @@ STRNUM  &&string	&numeric	&numeric\cr
 }}}
 @end tex
 @ifnottex
+@ifnotdocbook
 @display
         +----------------------------------------------
         |       STRING          NUMERIC         STRNUM
@@ -11113,7 +11842,51 @@ NUMERIC |       string          numeric         numeric
 STRNUM  |       string          numeric         numeric
 --------+----------------------------------------------
 @end display
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<informaltable>
+<tgroup cols="4">
+<colspec colname="1" align="left"/>
+<colspec colname="2" align="left"/>
+<colspec colname="3" align="left"/>
+<colspec colname="4" align="left"/>
+<thead>
+<row>
+<entry/>
+<entry>STRING</entry>
+<entry>NUMERIC</entry>
+<entry>STRNUM</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+<entry><emphasis role="bold">STRING</emphasis></entry>
+<entry>string</entry>
+<entry>string</entry>
+<entry>string</entry>
+</row>
+
+<row>
+<entry><emphasis role="bold">NUMERIC</emphasis></entry>
+<entry>string</entry>
+<entry>numeric</entry>
+<entry>numeric</entry>
+</row>
+
+<row>
+<entry><emphasis role="bold">STRNUM</emphasis></entry>
+<entry>string</entry>
+<entry>numeric</entry>
+<entry>numeric</entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 The basic idea is that user input that looks numeric---and @emph{only}
 user input---should be treated as numeric, even though it is actually
@@ -11132,8 +11905,8 @@ This point bears additional emphasis: All user input is made of characters,
 and so is first and foremost of @var{string} type; input strings
 that look numeric are additionally given the @var{strnum} attribute.
 Thus, the six-character input string @w{@samp{ +3.14}} receives the
-@var{strnum} attribute. In contrast, the eight-character literal
-@w{@code{" +3.14"}} appearing in program text is a string constant.
+@var{strnum} attribute. In contrast, the eight characters
+@w{@code{" +3.14"}} appearing in program text comprise a string constant.
 The following examples print @samp{1} when the comparison between
 the two different constants is true, @samp{0} otherwise:
 
@@ -11248,7 +12021,7 @@ string comparison (true)
 string comparison (true)
 
 @item a = 2; b = " +2"
-@item a == b
+@itemx a == b
 string comparison (false)
 @end table
 
@@ -11294,7 +12067,7 @@ has the value one if @code{x} contains @samp{foo}, such as
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
 The righthand operand of the @samp{~} and @samp{!~} operators may be
-either a regexp constant (@code{/@dots{}/}) or an ordinary
+either a regexp constant (@code{/}@dots{}@code{/}) or an ordinary
 expression. In the latter case, the value of the expression as a string is used as a
 dynamic regexp (@pxref{Regexp Usage}; also
 @pxref{Computed Regexps}).
@@ -11319,7 +12092,9 @@ where this is discussed in more detail.
 @subsubsection String Comparison With POSIX Rules
 
 The POSIX standard says that string comparison is performed based
-on the locale's collating order.  This is usually very different
+on the locale's @dfn{collating order}. This is the order in which
+characters sort, as defined by the locale (for more discussion,
+@pxref{Ranges and Locales}).  This order is usually very different
 from the results obtained when doing straight character-by-character
 comparison.@footnote{Technically, string comparison is supposed
 to behave the same way as if the strings are compared with the C
@@ -11327,7 +12102,7 @@ to behave the same way as if the strings are compared with the C
 
 Because this behavior differs considerably from existing practice,
 @command{gawk} only implements it when in POSIX mode (@pxref{Options}).
-Here is an example to illustrate the difference, in an @samp{en_US.UTF-8}
+Here is an example to illustrate the difference, in an @code{en_US.UTF-8}
 locale:
 
 @example
@@ -11382,10 +12157,10 @@ The Boolean operators are:
 @item @var{boolean1} && @var{boolean2}
 True if both @var{boolean1} and @var{boolean2} are true.  For example,
 the following statement prints the current input record if it contains
-both @samp{2400} and @samp{foo}:
+both @samp{edu} and @samp{li}:
 
 @example
-if ($0 ~ /2400/ && $0 ~ /foo/) print
+if ($0 ~ /edu/ && $0 ~ /li/) print
 @end example
 
 @cindex side effects, Boolean operators
@@ -11398,11 +12173,11 @@ no substring @samp{foo} in the record.
 @item @var{boolean1} || @var{boolean2}
 True if at least one of @var{boolean1} or @var{boolean2} is true.
 For example, the following statement prints all records in the input
-that contain @emph{either} @samp{2400} or
-@samp{foo} or both:
+that contain @emph{either} @samp{edu} or
+@samp{li} or both:
 
 @example
-if ($0 ~ /2400/ || $0 ~ /foo/) print
+if ($0 ~ /edu/ || $0 ~ /li/) print
 @end example
 
 The subexpression @var{boolean2} is evaluated only if @var{boolean1}
@@ -11543,7 +12318,7 @@ However, putting a newline in front
 of either character does not work without using backslash continuation
 (@pxref{Statements/Lines}).
 If @option{--posix} is specified
-(@pxref{Options}), then this extension is disabled.
+(@pxref{Options}), this extension is disabled.
 
 @node Function Calls
 @section Function Calls
@@ -11562,6 +12337,8 @@ functions and their descriptions.  In addition, you can define
 functions for use in your program.
 @xref{User-defined},
 for instructions on how to do this.
+Finally, @command{gawk} lets you write functions in C or C++
+that may be called from your program: see @ref{Dynamic Extensions}.
 
 @cindex arguments, in function calls
 The way to use a function is with a @dfn{function call} expression,
@@ -11603,7 +12380,9 @@ If those arguments are not supplied, the functions
 use a reasonable default value.
 @xref{Built-in}, for full details.  If arguments
 are omitted in calls to user-defined functions, then those arguments are
-treated as local variables and initialized to the empty string
+treated as local variables. Such local variables act like the
+empty string if referenced where a string value is required,
+and like zero if referenced where a numeric value is required
 (@pxref{User-defined}).
 
 As an advanced feature, @command{gawk} provides indirect function calls,
@@ -11612,12 +12391,12 @@ when you write the source code to your program. We defer discussion of
 this feature until later; see @ref{Indirect Calls}.
 
 @cindex side effects, function calls
-Like every other expression, the function call has a value, which is
-computed by the function based on the arguments you give it.  In this
-example, the value of @samp{sqrt(@var{argument})} is the square root of
-@var{argument}.
-The following program reads numbers, one number per line, and prints the
-square root of each one:
+Like every other expression, the function call has a value, often
+called the @dfn{return value}, which is computed by the function
+based on the arguments you give it.  In this example, the return value
+of @samp{sqrt(@var{argument})} is the square root of @var{argument}.
+The following program reads numbers, one number per line, and prints
+the square root of each one:
 
 @example
 $ @kbd{awk '@{ print "The square root of", $1, "is", sqrt($1) @}'}
@@ -11705,28 +12484,28 @@ expression because the first @samp{$} has higher precedence than the
 This table presents @command{awk}'s operators, in order of highest
 to lowest precedence:
 
-@c use @code in the items, looks better in TeX w/o all the quotes
-@table @code
-@item (@dots{})
+@c @asis for docbook to come out right
+@table @asis
+@item @code{(}@dots{}@code{)}
 Grouping.
 
 @cindex @code{$} (dollar sign), @code{$} field operator
 @cindex dollar sign (@code{$}), @code{$} field operator
-@item $
+@item @code{$}
 Field reference.
 
 @cindex @code{+} (plus sign), @code{++} operator
 @cindex plus sign (@code{+}), @code{++} operator
 @cindex @code{-} (hyphen), @code{--} operator
 @cindex hyphen (@code{-}), @code{--} operator
-@item ++ --
+@item @code{++ --}
 Increment, decrement.
 
 @cindex @code{^} (caret), @code{^} operator
 @cindex caret (@code{^}), @code{^} operator
 @cindex @code{*} (asterisk), @code{**} operator
 @cindex asterisk (@code{*}), @code{**} operator
-@item ^ **
+@item @code{^ **}
 Exponentiation.  These operators group right-to-left.
 
 @cindex @code{+} (plus sign), @code{+} operator
@@ -11735,7 +12514,7 @@ Exponentiation.  These operators group right-to-left.
 @cindex hyphen (@code{-}), @code{-} operator
 @cindex @code{!} (exclamation point), @code{!} operator
 @cindex exclamation point (@code{!}), @code{!} operator
-@item + - !
+@item @code{+ - !}
 Unary plus, minus, logical ``not.''
 
 @cindex @code{*} (asterisk), @code{*} operator, as multiplication operator
@@ -11744,17 +12523,17 @@ Unary plus, minus, logical ``not.''
 @cindex forward slash (@code{/}), @code{/} operator
 @cindex @code{%} (percent sign), @code{%} operator
 @cindex percent sign (@code{%}), @code{%} operator
-@item * / %
+@item @code{* / %}
 Multiplication, division, remainder.
 
 @cindex @code{+} (plus sign), @code{+} operator
 @cindex plus sign (@code{+}), @code{+} operator
 @cindex @code{-} (hyphen), @code{-} operator
 @cindex hyphen (@code{-}), @code{-} operator
-@item + -
+@item @code{+ -}
 Addition, subtraction.
 
-@item @r{String Concatenation}
+@item String Concatenation
 There is no special symbol for concatenation.
 The operands are simply written side by side
 (@pxref{Concatenation}).
@@ -11780,7 +12559,7 @@ The operands are simply written side by side
 @cindex @code{|} (vertical bar), @code{|&} operator (I/O)
 @cindex vertical bar (@code{|}), @code{|&} operator (I/O)
 @cindex operators, input/output
-@item < <= == != > >= >> | |&
+@item @code{< <= == != > >= >> | |&}
 Relational and redirection.
 The relational operators and the redirections have the same precedence
 level.  Characters such as @samp{>} serve both as relationals and as
@@ -11801,26 +12580,26 @@ The correct way to write this statement is @samp{print foo > (a ? b : c)}.
 @cindex tilde (@code{~}), @code{~} operator
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
-@item ~ !~
+@item @code{~ !~}
 Matching, nonmatching.
 
 @cindex @code{in} operator
-@item in
+@item @code{in}
 Array membership.
 
 @cindex @code{&} (ampersand), @code{&&} operator
 @cindex ampersand (@code{&}), @code{&&} operator
-@item &&
+@item @code{&&}
 Logical ``and''.
 
 @cindex @code{|} (vertical bar), @code{||} operator
 @cindex vertical bar (@code{|}), @code{||} operator
-@item ||
+@item @code{||}
 Logical ``or''.
 
 @cindex @code{?} (question mark), @code{?:} operator
 @cindex question mark (@code{?}), @code{?:} operator
-@item ?:
+@item @code{?:}
 Conditional.  This operator groups right-to-left.
 
 @cindex @code{+} (plus sign), @code{+=} operator
@@ -11837,7 +12616,7 @@ Conditional.  This operator groups right-to-left.
 @cindex percent sign (@code{%}), @code{%=} operator
 @cindex @code{^} (caret), @code{^=} operator
 @cindex caret (@code{^}), @code{^=} operator
-@item = += -= *= /= %= ^= **=
+@item @code{= += -= *= /= %= ^= **=}
 Assignment.  These operators group right-to-left.
 @end table
 
@@ -11854,27 +12633,102 @@ For maximum portability, do not use them.
 @section Where You Are Makes A Difference
 @cindex locale, definition of
 
-Modern systems support the notion of @dfn{locales}: a way to tell
-the system about the local character set and language.
+Modern systems support the notion of @dfn{locales}: a way to tell the
+system about the local character set and language.  The ISO C standard
+defines a default @code{"C"} locale, which is an environment that is
+typical of what many C programmers are used to.
 
 Once upon a time, the locale setting used to affect regexp matching
 (@pxref{Ranges and Locales}), but this is no longer true.
 
-Locales can affect record splitting.
-For the normal case of @samp{RS = "\n"}, the locale is largely irrelevant.
-For other single-character record separators, setting @samp{LC_ALL=C}
-in the environment
-will give you much better performance when reading records.  Otherwise,
+Locales can affect record splitting.  For the normal case of @samp{RS =
+"\n"}, the locale is largely irrelevant.  For other single-character
+record separators, setting @samp{LC_ALL=C} in the environment will
+give you much better performance when reading records.  Otherwise,
 @command{gawk} has to make several function calls, @emph{per input
 character}, to find the record terminator.
 
-According to POSIX, string comparison is also affected by locales
-(similar to regular expressions).  The details are presented in
-@ref{POSIX String Comparison}.
+Locales can affect how dates and times are formatted (@pxref{Time
+Functions}).  For example, a common way to abbreviate the date September
+4, 2015 in the United States is ``9/4/15.''  In many countries in
+Europe, however, it is abbreviated ``4.9.15.''  Thus, the @samp{%x}
+specification in a @code{"US"} locale might produce @samp{9/4/15},
+while in a @code{"EUROPE"} locale, it might produce @samp{4.9.15}.
+
+According to POSIX, string comparison is also affected by locales (similar
+to regular expressions).  The details are presented in @ref{POSIX String
+Comparison}.
 
 Finally, the locale affects the value of the decimal point character
-used when @command{gawk} parses input data.  This is discussed in
-detail in @ref{Conversion}.
+used when @command{gawk} parses input data.  This is discussed in detail
+in @ref{Conversion}.
+
+@node Expressions Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Expressions are the basic elements of computation in programs.  They are
+built from constants, variables, function calls and combinations of the
+various kinds of values with operators.
+
+@item
+@command{awk} supplies three kinds of constants: numeric, string, and
+regexp.  @command{gawk} lets you specify numeric constants in octal
+and hexadecimal (bases 8 and 16) in addition to decimal (base 10).
+In certain contexts, a standalone regexp constant such as @code{/foo/}
+has the same meaning as @samp{$0 ~ /foo/}.
+
+@item
+Variables hold values between uses in computations. A number of built-in
+variables provide information to your @command{awk} program, and a number
+of others let you control how @command{awk} behaves.
+
+@item
+Numbers are automatically converted to strings, and strings to numbers,
+as needed by @command{awk}. Numeric values are converted as if they were
+formatted with @code{sprintf()} using the format in @code{CONVFMT}.
+Locales can influence the conversions.
+
+@item
+@command{awk} provides the usual arithmetic operators (addition,
+subtraction, multiplication, division, modulus), and unary plus and minus.
+It also provides comparison operators, boolean operators, and regexp
+matching operators.  String concatenation is accomplished by placing
+two expressions next to each other; there is no explicit operator.
+The three-operand @samp{?:} operator provides an ``if-else'' test within
+expressions.
+
+@item
+Assignment operators provide convenient shorthands for common arithmetic
+operations.
+
+@item
+In @command{awk}, a value is considered to be true if it is non-zero
+@emph{or} non-null. Otherwise, the value is false.
+
+@item
+A value's type is set upon each assignment and may change over its
+lifetime.  The type determines how it behaves in comparisons (string
+or numeric).
+
+@item
+Function calls return a value which may be used as part of a larger
+expression.  Expressions used to pass parameter values are fully
+evaluated before the function is called.  @command{awk} provides
+built-in and user-defined functions; this is described later on in this
+@value{DOCUMENT}.
+
+@item
+Operator precedence specifies the order in which operations are performed,
+unless explicitly overridden by parentheses.  @command{awk}'s operator
+precedence is compatible with that of C.
+
+@item
+Locales can affect the format of data as output by an @command{awk}
+program, and occasionally the format for data read as input.
+
+@end itemize
 
 @c ENDOFRANGE exps
 
@@ -11902,6 +12756,7 @@ building something useful.
 * Statements::                  Describes the various control statements in
                                 detail.
 * Built-in Variables::          Summarizes the built-in variables.
+* Pattern Action Summary::      Patterns and Actions summary.
 @end menu
 
 @node Pattern Overview
@@ -11932,10 +12787,10 @@ A single expression.  It matches when its value
 is nonzero (if a number) or non-null (if a string).
 (@xref{Expression Patterns}.)
 
-@item @var{pat1}, @var{pat2}
+@item @var{begpat}, @var{endpat}
 A pair of patterns separated by a comma, specifying a range of records.
-The range includes both the initial record that matches @var{pat1} and
-the final record that matches @var{pat2}.
+The range includes both the initial record that matches @var{begpat} and
+the final record that matches @var{endpat}.
 (@xref{Ranges}.)
 
 @item BEGIN
@@ -11947,7 +12802,7 @@ Special patterns for you to supply startup or cleanup actions for your
 @item BEGINFILE
 @itemx ENDFILE
 Special patterns for you to supply startup or cleanup actions to be
-done on a per file basis.
+done on a per-file basis.
 (@xref{BEGINFILE/ENDFILE}.)
 
 @item @var{empty}
@@ -11997,7 +12852,7 @@ slashes (@code{/@var{regexp}/}), or any expression whose string value
 is used as a dynamic regular expression
 (@pxref{Computed Regexps}).
 The following example prints the second field of each input record
-whose first field is precisely @samp{foo}:
+whose first field is precisely @samp{li}:
 
 @cindex @code{/} (forward slash), patterns and
 @cindex forward slash (@code{/}), patterns and
@@ -12006,68 +12861,65 @@ whose first field is precisely @samp{foo}:
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
 @example
-$ @kbd{awk '$1 == "foo" @{ print $2 @}' BBS-list}
+$ @kbd{awk '$1 == "li" @{ print $2 @}' mail-list}
 @end example
 
 @noindent
-(There is no output, because there is no BBS site with the exact name @samp{foo}.)
+(There is no output, because there is no person with the exact name @samp{li}.)
 Contrast this with the following regular expression match, which
-accepts any record with a first field that contains @samp{foo}:
+accepts any record with a first field that contains @samp{li}:
 
 @example
-$ @kbd{awk '$1 ~ /foo/ @{ print $2 @}' BBS-list}
-@print{} 555-1234
+$ @kbd{awk '$1 ~ /foo/ @{ print $2 @}' mail-list}
+@print{} 555-5553
 @print{} 555-6699
-@print{} 555-6480
-@print{} 555-2127
 @end example
 
 @cindex regexp constants, as patterns
 @cindex patterns, regexp constants as
 A regexp constant as a pattern is also a special case of an expression
-pattern.  The expression @code{/foo/} has the value one if @samp{foo}
-appears in the current input record. Thus, as a pattern, @code{/foo/}
-matches any record containing @samp{foo}.
+pattern.  The expression @code{/li/} has the value one if @samp{li}
+appears in the current input record. Thus, as a pattern, @code{/li/}
+matches any record containing @samp{li}.
 
 @cindex Boolean expressions, as patterns
 Boolean expressions are also commonly used as patterns.
 Whether the pattern
 matches an input record depends on whether its subexpressions match.
 For example, the following command prints all the records in
-@file{BBS-list} that contain both @samp{2400} and @samp{foo}:
+@file{mail-list} that contain both @samp{edu} and @samp{li}:
 
 @example
-$ @kbd{awk '/2400/ && /foo/' BBS-list}
-@print{} fooey        555-1234     2400/1200/300     B
+$ @kbd{awk '/edu/ && /li/' mail-list}
+@print{} Samuel       555-3430     samuel.lanceolis@@shu.edu        A
 @end example
 
 The following command prints all records in
-@file{BBS-list} that contain @emph{either} @samp{2400} or @samp{foo}
+@file{mail-list} that contain @emph{either} @samp{edu} or @samp{li}
 (or both, of course):
 
 @example
-$ @kbd{awk '/2400/ || /foo/' BBS-list}
-@print{} alpo-net     555-3412     2400/1200/300     A
-@print{} bites        555-1675     2400/1200/300     A
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sdace        555-3430     2400/1200/300     A
-@print{} sabafoo      555-2127     1200/300          C
+$ @kbd{awk '/edu/ || /li/' mail-list}
+@print{} Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+@print{} Broderick    555-0542     broderick.aliquotiens@@yahoo.com R
+@print{} Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+@print{} Julie        555-6699     julie.perscrutabor@@skeeve.com   F
+@print{} Samuel       555-3430     samuel.lanceolis@@shu.edu        A
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @end example
 
 The following command prints all records in
-@file{BBS-list} that do @emph{not} contain the string @samp{foo}:
+@file{mail-list} that do @emph{not} contain the string @samp{li}:
 
 @example
-$ @kbd{awk '! /foo/' BBS-list}
-@print{} aardvark     555-5553     1200/300          B
-@print{} alpo-net     555-3412     2400/1200/300     A
-@print{} barfly       555-7685     1200/300          A
-@print{} bites        555-1675     2400/1200/300     A
-@print{} camelot      555-0542     300               C
-@print{} core         555-2912     1200/300          C
-@print{} sdace        555-3430     2400/1200/300     A
+$ @kbd{awk '! /li/' mail-list}
+@print{} Anthony      555-3412     anthony.asserturo@@hotmail.com   A
+@print{} Becky        555-7685     becky.algebrarum@@gmail.com      A
+@print{} Bill         555-1675     bill.drowning@@hotmail.com       A
+@print{} Camilla      555-2912     camilla.infusarum@@skynet.be     R
+@print{} Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+@print{} Martin       555-6480     martin.codicibus@@hotmail.com    A
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @end example
 
 @cindex @code{BEGIN} pattern, Boolean patterns and
@@ -12111,7 +12963,7 @@ input record.  When a record matches @var{begpat}, the range pattern is
 @dfn{turned on} and the range pattern matches this record as well.  As long as
 the range pattern stays turned on, it automatically matches every input
 record read.  The range pattern also matches @var{endpat} against every
-input record; when this succeeds, the range pattern is turned off again
+input record; when this succeeds, the range pattern is @dfn{turned off} again
 for the following record.  Then the range pattern goes back to checking
 @var{begpat} against each record.
 
@@ -12171,6 +13023,11 @@ $ @kbd{echo Yes | gawk '(/1/,/2/) || /Yes/'}
 @error{} gawk: cmd. line:1:           ^ syntax error
 @end example
 
+@cindex range patterns, line continuation and
+As a minor point of interest, although it is poor style,
+POSIX allows you to put a newline after the comma in
+a range pattern.  @value{DARKCORNER}
+
 @node BEGIN/END
 @subsection The @code{BEGIN} and @code{END} Special Patterns
 
@@ -12195,28 +13052,30 @@ programmers.
 @node Using BEGIN/END
 @subsubsection Startup and Cleanup Actions
 
+@cindex @code{BEGIN} pattern
+@cindex @code{END} pattern
 A @code{BEGIN} rule is executed once only, before the first input record
 is read. Likewise, an @code{END} rule is executed once only, after all the
 input is read.  For example:
 
 @example
 $ @kbd{awk '}
-> @kbd{BEGIN @{ print "Analysis of \"foo\"" @}}
-> @kbd{/foo/ @{ ++n @}}
-> @kbd{END   @{ print "\"foo\" appears", n, "times." @}' BBS-list}
-@print{} Analysis of "foo"
-@print{} "foo" appears 4 times.
+> @kbd{BEGIN @{ print "Analysis of \"li\"" @}}
+> @kbd{/li/ @{ ++n @}}
+> @kbd{END   @{ print "\"li\" appears in", n, "records." @}' mail-list}
+@print{} Analysis of "li"
+@print{} "li" appears in 4 records.
 @end example
 
 @cindex @code{BEGIN} pattern, operators and
 @cindex @code{END} pattern, operators and
-This program finds the number of records in the input file @file{BBS-list}
-that contain the string @samp{foo}.  The @code{BEGIN} rule prints a title
+This program finds the number of records in the input file @file{mail-list}
+that contain the string @samp{li}.  The @code{BEGIN} rule prints a title
 for the report.  There is no need to use the @code{BEGIN} rule to
 initialize the counter @code{n} to zero, since @command{awk} does this
 automatically (@pxref{Variables}).
 The second rule increments the variable @code{n} every time a
-record containing the pattern @samp{foo} is read.  The @code{END} rule
+record containing the pattern @samp{li} is read.  The @code{END} rule
 prints the value of @code{n} at the end of the run.
 
 The special patterns @code{BEGIN} and @code{END} cannot be used in ranges
@@ -12258,7 +13117,7 @@ rule checks the @code{FNR} and @code{NR} variables.
 @subsubsection Input/Output from @code{BEGIN} and @code{END} Rules
 
 @cindex input/output, from @code{BEGIN} and @code{END}
-There are several (sometimes subtle) points to remember when doing I/O
+There are several (sometimes subtle) points to be aware of when doing I/O
 from a @code{BEGIN} or @code{END} rule.
 The first has to do with the value of @code{$0} in a @code{BEGIN}
 rule.  Because @code{BEGIN} rules are executed before any input is read,
@@ -12269,6 +13128,7 @@ to give @code{$0} a real value is to execute a @code{getline} command
 without a variable (@pxref{Getline}).
 Another way is simply to assign a value to @code{$0}.
 
+@cindex Brian Kernighan's @command{awk}
 @cindex differences in @command{awk} and @command{gawk}, @code{BEGIN}/@code{END} patterns
 @cindex POSIX @command{awk}, @code{BEGIN}/@code{END} patterns
 @cindex @code{print} statement, @code{BEGIN}/@code{END} patterns and
@@ -12318,8 +13178,19 @@ This @value{SECTION} describes a @command{gawk}-specific feature.
 
 Two special kinds of rule, @code{BEGINFILE} and @code{ENDFILE}, give
 you ``hooks'' into @command{gawk}'s command-line file processing loop.
-As with the @code{BEGIN} and @code{END} rules (@pxref{BEGIN/END}), all
-@code{BEGINFILE} rules in a program are merged, in the order they are
+As with the @code{BEGIN} and @code{END} rules
+@ifnottex
+@ifnotdocbook
+(@pxref{BEGIN/END}),
+@end ifnotdocbook
+@end ifnottex
+@iftex
+(see the previous section),
+@end iftex
+@ifdocbook
+(see the previous section),
+@end ifdocbook
+all @code{BEGINFILE} rules in a program are merged, in the order they are
 read by @command{gawk}, and all @code{ENDFILE} rules are merged as well.
 
 The body of the @code{BEGINFILE} rules is executed just before
@@ -12329,7 +13200,7 @@ is set to the name of the current file, and @code{FNR} is set to zero.
 The @code{BEGINFILE} rule provides you the opportunity to accomplish two tasks
 that would otherwise be difficult or impossible to perform:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 You can test if the file is readable.  Normally, it is a fatal error if a
 file named on the command line cannot be opened for reading.  However,
@@ -12337,7 +13208,7 @@ you can bypass the fatal error and move on to the next file on the
 command line.
 
 @cindex @command{gawk}, @code{ERRNO} variable in
-@cindex @code{ERRNO} variable
+@cindex @code{ERRNO} variable, with @code{BEGINFILE} pattern
 @cindex @code{nextfile} statement, @code{BEGINFILE}/@code{ENDFILE} patterns and
 You do this by checking if the @code{ERRNO} variable is not the empty
 string; if so, then @command{gawk} was not able to open the file. In
@@ -12347,10 +13218,11 @@ the file entirely.  Otherwise, @command{gawk} exits with the usual
 fatal error.
 
 @item
-If you have written extensions that modify the record handling (by inserting
-an ``input parser''), you can invoke them at this point, before @command{gawk}
-has started processing the file.  (This is a @emph{very} advanced feature,
-currently used only by the @uref{http://gawkextlib.sourceforge.net, @code{gawkextlib} project}.)
+If you have written extensions that modify the record handling (by
+inserting an ``input parser,'' @pxref{Input Parsers}), you can invoke
+them at this point, before @command{gawk} has started processing the file.
+(This is a @emph{very} advanced feature, currently used only by the
+@uref{http://gawkextlib.sourceforge.net, @code{gawkextlib} project}.)
 @end itemize
 
 The @code{ENDFILE} rule is called when @command{gawk} has finished processing
@@ -12372,14 +13244,14 @@ statement (@pxref{Nextfile Statement}) is allowed only inside a
 
 @cindex @code{getline} statement, @code{BEGINFILE}/@code{ENDFILE} patterns and
 The @code{getline} statement (@pxref{Getline}) is restricted inside
-both @code{BEGINFILE} and @code{ENDFILE}.  Only the @samp{getline
-@var{variable} < @var{file}} form is allowed.
+both @code{BEGINFILE} and @code{ENDFILE}: only redirected
+forms of @code{getline} are allowed.
 
 @code{BEGINFILE} and @code{ENDFILE} are @command{gawk} extensions.
 In most other @command{awk} implementations, or if @command{gawk} is in
 compatibility mode (@pxref{Options}), they are not special.
 
-@c FIXME: For 4.1 maybe deal with this?
+@c FIXME: For 4.2 maybe deal with this?
 @ignore
 Date:     Tue, 17 May 2011 02:06:10 PDT
 From:     rankin@pactechdata.com (Pat Rankin)
@@ -12410,7 +13282,7 @@ An empty (i.e., nonexistent) pattern is considered to match @emph{every}
 input record.  For example, the program:
 
 @example
-awk '@{ print $1 @}' BBS-list
+awk '@{ print $1 @}' mail-list
 @end example
 
 @noindent
@@ -12433,7 +13305,7 @@ into the body of the @command{awk} program.
 @cindex shells, quoting
 The most common method is to use shell quoting to substitute
 the variable's value into the program inside the script.
-For example, in the following program:
+For example, consider the following program:
 
 @example
 printf "Enter search pattern: "
@@ -12443,7 +13315,7 @@ awk "/$pattern/ "'@{ nmatches++ @}
 @end example
 
 @noindent
-the @command{awk} program consists of two pieces of quoted text
+The @command{awk} program consists of two pieces of quoted text
 that are concatenated together to form the program.
 The first part is double-quoted, which allows substitution of
 the @code{pattern} shell variable inside the quotes.
@@ -12457,8 +13329,8 @@ match up the quotes when reading the program.
 
 A better method is to use @command{awk}'s variable assignment feature
 (@pxref{Assignment Options})
-to assign the shell variable's value to an @command{awk} variable's
-value.  Then use dynamic regexps to match the pattern
+to assign the shell variable's value to an @command{awk} variable.
+Then use dynamic regexps to match the pattern
 (@pxref{Computed Regexps}).
 The following shows how to redo the
 previous example using this technique:
@@ -12496,13 +13368,13 @@ both) may be omitted.  The purpose of the @dfn{action} is to tell
 @command{awk} what to do once a match for the pattern is found.  Thus,
 in outline, an @command{awk} program generally looks like this:
 
-@example
-@r{[}@var{pattern}@r{]}  @{ @var{action} @}
- @var{pattern}  @r{[}@{ @var{action} @}@r{]}
+@display
+[@var{pattern}]  @code{@{ @var{action} @}}
+ @var{pattern}  [@code{@{ @var{action} @}}]
 @dots{}
-function @var{name}(@var{args}) @{ @dots{} @}
+@code{function @var{name}(@var{args}) @{ @dots{} @}}
 @dots{}
-@end example
+@end display
 
 @cindex @code{@{@}} (braces), actions and
 @cindex braces (@code{@{@}}), actions and
@@ -12511,11 +13383,11 @@ function @var{name}(@var{args}) @{ @dots{} @}
 @cindex @code{;} (semicolon), separating statements in actions
 @cindex semicolon (@code{;}), separating statements in actions
 An action consists of one or more @command{awk} @dfn{statements}, enclosed
-in curly braces (@samp{@{@dots{}@}}).  Each statement specifies one
+in braces (@samp{@{@r{@dots{}}@}}).  Each statement specifies one
 thing to do.  The statements are separated by newlines or semicolons.
-The curly braces around an action must be used even if the action
+The braces around an action must be used even if the action
 contains only one statement, or if it contains no statements at
-all.  However, if you omit the action entirely, omit the curly braces as
+all.  However, if you omit the action entirely, omit the braces as
 well.  An omitted action is equivalent to @samp{@{ print $0 @}}:
 
 @example
@@ -12541,10 +13413,9 @@ programs.  The @command{awk} language gives you C-like constructs
 special ones (@pxref{Statements}).
 
 @item Compound statements
-Consist of one or more statements enclosed in
-curly braces.  A compound statement is used in order to put several
-statements together in the body of an @code{if}, @code{while}, @code{do},
-or @code{for} statement.
+Enclose one or more statements in braces.  A compound statement
+is used in order to put several statements together in the body of an
+@code{if}, @code{while}, @code{do}, or @code{for} statement.
 
 @item Input statements
 Use the @code{getline} command
@@ -12590,7 +13461,7 @@ Many control statements contain other statements.  For example, the
 @code{if} statement contains another statement that may or may not be
 executed.  The contained statement is called the @dfn{body}.
 To include more than one statement in the body, group them into a
-single @dfn{compound statement} with curly braces, separating them with
+single @dfn{compound statement} with braces, separating them with
 newlines or semicolons.
 
 @menu
@@ -12618,9 +13489,9 @@ newlines or semicolons.
 The @code{if}-@code{else} statement is @command{awk}'s decision-making
 statement.  It looks like this:
 
-@example
-if (@var{condition}) @var{then-body} @r{[}else @var{else-body}@r{]}
-@end example
+@display
+@code{if (@var{condition}) @var{then-body}} [@code{else @var{else-body}}]
+@end display
 
 @noindent
 The @var{condition} is an expression that controls what the rest of the
@@ -12644,7 +13515,7 @@ if the value of @code{x} is evenly divisible by two), then the first
 statement is executed.
 If the @code{else} keyword appears on the same line as @var{then-body} and
 @var{then-body} is not a compound statement (i.e., not surrounded by
-curly braces), then a semicolon must separate @var{then-body} from
+braces), then a semicolon must separate @var{then-body} from
 the @code{else}.
 To illustrate this, the previous example can be rewritten as:
 
@@ -12663,6 +13534,7 @@ the first thing on its line.
 @subsection The @code{while} Statement
 @cindex @code{while} statement
 @cindex loops
+@cindex loops, @code{while}
 @cindex loops, See Also @code{while} statement
 
 In programming, a @dfn{loop} is a part of a program that can
@@ -12723,6 +13595,7 @@ program is harder to read without it.
 @node Do Statement
 @subsection The @code{do}-@code{while} Statement
 @cindex @code{do}-@code{while} statement
+@cindex loops, @code{do}-@code{while}
 
 The @code{do} loop is a variation of the @code{while} looping statement.
 The @code{do} loop executes the @var{body} once and then repeats the
@@ -12768,6 +13641,7 @@ occasionally is there a real use for a @code{do} statement.
 @node For Statement
 @subsection The @code{for} Statement
 @cindex @code{for} statement
+@cindex loops, @code{for}, iterative
 
 The @code{for} statement makes it more convenient to count iterations of a
 loop.  The general form of the @code{for} statement looks like this:
@@ -12874,6 +13748,10 @@ for more information on this version of the @code{for} loop.
 @cindex @code{case} keyword
 @cindex @code{default} keyword
 
+This @value{SECTION} describes a @command{gawk}-specific feature.
+If @command{gawk} is in compatibility mode (@pxref{Options}),
+it is not available.
+
 The @code{switch} statement allows the evaluation of an expression and
 the execution of statements based on a @code{case} match. Case statements
 are checked for a match in the order they are defined.  If no suitable
@@ -12929,15 +13807,11 @@ the @code{print} statement is executed and then falls through into the
 the @minus{}1 case will also be executed since the @code{default} does
 not halt execution.
 
-This @code{switch} statement is a @command{gawk} extension.
-If @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not available.
-
 @node Break Statement
 @subsection The @code{break} Statement
 @cindex @code{break} statement
 @cindex loops, exiting
+@cindex loops, @code{break} statement and
 
 The @code{break} statement jumps out of the innermost @code{for},
 @code{while}, or @code{do} loop that encloses it.  The following example
@@ -12947,15 +13821,15 @@ numbers:
 @example
 # find smallest divisor of num
 @{
-   num = $1
-   for (div = 2; div * div <= num; div++) @{
-     if (num % div == 0)
-       break
-   @}
-   if (num % div == 0)
-     printf "Smallest divisor of %d is %d\n", num, div
-   else
-     printf "%d is prime\n", num
+    num = $1
+    for (div = 2; div * div <= num; div++) @{
+        if (num % div == 0)
+            break
+    @}
+    if (num % div == 0)
+        printf "Smallest divisor of %d is %d\n", num, div
+    else
+        printf "%d is prime\n", num
 @}
 @end example
 
@@ -12973,17 +13847,17 @@ an @code{if}:
 @example
 # find smallest divisor of num
 @{
-  num = $1
-  for (div = 2; ; div++) @{
-    if (num % div == 0) @{
-      printf "Smallest divisor of %d is %d\n", num, div
-      break
-    @}
-    if (div * div > num) @{
-      printf "%d is prime\n", num
-      break
+    num = $1
+    for (div = 2; ; div++) @{
+        if (num % div == 0) @{
+            printf "Smallest divisor of %d is %d\n", num, div
+            break
+        @}
+        if (div * div > num) @{
+            printf "%d is prime\n", num
+            break
+        @}
     @}
-  @}
 @}
 @end example
 
@@ -12997,6 +13871,7 @@ This is discussed in @ref{Switch Statement}.
 @cindex POSIX @command{awk}, @code{break} statement and
 @cindex dark corner, @code{break} statement
 @cindex @command{gawk}, @code{break} statement in
+@cindex Brian Kernighan's @command{awk}
 The @code{break} statement has no meaning when
 used outside the body of a loop or @code{switch}.
 However, although it was never documented,
@@ -13061,6 +13936,7 @@ This program loops forever once @code{x} reaches 5.
 @cindex POSIX @command{awk}, @code{continue} statement and
 @cindex dark corner, @code{continue} statement
 @cindex @command{gawk}, @code{continue} statement in
+@cindex Brian Kernighan's @command{awk}
 The @code{continue} statement has no special meaning with respect to the
 @code{switch} statement, nor does it have any meaning when used outside the
 body of a loop.  Historical versions of @command{awk} treated a @code{continue}
@@ -13130,16 +14006,14 @@ The @code{next} statement is not allowed inside @code{BEGINFILE} and
 @cindex POSIX @command{awk}, @code{next}/@code{nextfile} statements and
 @cindex @code{next} statement, user-defined functions and
 @cindex functions, user-defined, @code{next}/@code{nextfile} statements and
-According to the POSIX standard, the behavior is undefined if
-the @code{next} statement is used in a @code{BEGIN} or @code{END} rule.
-@command{gawk} treats it as a syntax error.
-Although POSIX permits it,
-some other @command{awk} implementations don't allow the @code{next}
-statement inside function bodies
-(@pxref{User-defined}).
-Just as with any other @code{next} statement, a @code{next} statement inside a
-function body reads the next record and starts processing it with the
-first rule in the program.
+According to the POSIX standard, the behavior is undefined if the
+@code{next} statement is used in a @code{BEGIN} or @code{END} rule.
+@command{gawk} treats it as a syntax error.  Although POSIX permits it,
+most other @command{awk} implementations don't allow the @code{next}
+statement inside function bodies (@pxref{User-defined}).  Just as with any
+other @code{next} statement, a @code{next} statement inside a function
+body reads the next record and starts processing it with the first rule
+in the program.
 
 @node Nextfile Statement
 @subsection The @code{nextfile} Statement
@@ -13149,11 +14023,11 @@ The @code{nextfile} statement
 is similar to the @code{next} statement.
 However, instead of abandoning processing of the current record, the
 @code{nextfile} statement instructs @command{awk} to stop processing the
-current data file.
+current @value{DF}.
 
 Upon execution of the @code{nextfile} statement,
 @code{FILENAME} is
-updated to the name of the next data file listed on the command line,
+updated to the name of the next @value{DF} listed on the command line,
 @code{FNR} is reset to one,
 and processing
 starts over with the first rule in the program.
@@ -13162,10 +14036,10 @@ then the code in any @code{END} rules is executed. An exception to this is
 when @code{nextfile} is invoked during execution of any statement in an
 @code{END} rule; In this case, it causes the program to stop immediately. @xref{BEGIN/END}.
 
-The @code{nextfile} statement is useful when there are many data files
+The @code{nextfile} statement is useful when there are many @value{DF}s
 to process but it isn't necessary to process every record in every file.
 Without @code{nextfile},
-in order to move on to the next data file, a program
+in order to move on to the next @value{DF}, a program
 would have to continue scanning the unwanted records.  The @code{nextfile}
 statement accomplishes this much more efficiently.
 
@@ -13198,8 +14072,10 @@ See @uref{http://austingroupbugs.net/view.php?id=607, the Austin Group website}.
 
 @cindex functions, user-defined, @code{next}/@code{nextfile} statements and
 @cindex @code{nextfile} statement, user-defined functions and
-The current version of the Brian Kernighan's @command{awk} (@pxref{Other
-Versions}) also supports @code{nextfile}.  However, it doesn't allow the
+@cindex Brian Kernighan's @command{awk}
+@cindex @command{mawk} utility
+The current version of the Brian Kernighan's @command{awk}, and @command{mawk} (@pxref{Other
+Versions}) also support @code{nextfile}.  However, they don't allow the
 @code{nextfile} statement inside function bodies (@pxref{User-defined}).
 @command{gawk} does; a @code{nextfile} inside a function body reads the
 next record and starts processing it with the first rule in the program,
@@ -13213,9 +14089,9 @@ The @code{exit} statement causes @command{awk} to immediately stop
 executing the current rule and to stop processing input; any remaining input
 is ignored.  The @code{exit} statement is written as follows:
 
-@example
-exit @r{[}@var{return code}@r{]}
-@end example
+@display
+@code{exit} [@var{return code}]
+@end display
 
 @cindex @code{BEGIN} pattern, @code{exit} statement and
 @cindex @code{END} pattern, @code{exit} statement and
@@ -13248,8 +14124,7 @@ status code for the @command{awk} process.  If no argument is supplied,
 In the case where an argument
 is supplied to a first @code{exit} statement, and then @code{exit} is
 called a second time from an @code{END} rule with no argument,
-@command{awk} uses the previously supplied exit value.
-@value{DARKCORNER}
+@command{awk} uses the previously supplied exit value.  @value{DARKCORNER}
 @xref{Exit Status}, for more information.
 
 @cindex programming conventions, @code{exit} statement
@@ -13261,12 +14136,12 @@ in the following example:
 
 @example
 BEGIN @{
-       if (("date" | getline date_now) <= 0) @{
-         print "Can't get system date" > "/dev/stderr"
-         exit 1
-       @}
-       print "current date is", date_now
-       close("date")
+    if (("date" | getline date_now) <= 0) @{
+        print "Can't get system date" > "/dev/stderr"
+        exit 1
+    @}
+    print "current date is", date_now
+    close("date")
 @}
 @end example
 
@@ -13297,9 +14172,9 @@ automatically by @command{awk}, so that they carry information from the
 internal workings of @command{awk} to your program.
 
 @cindex @command{gawk}, built-in variables and
-This @value{SECTION} documents all the built-in variables of
-@command{gawk}, most of which are also documented in the chapters
-describing their areas of activity.
+This @value{SECTION} documents all of @command{gawk}'s built-in variables,
+most of which are also documented in the @value{CHAPTER}s describing
+their areas of activity.
 
 @menu
 * User-modified::               Built-in variables that you change to control
@@ -13317,44 +14192,38 @@ describing their areas of activity.
 @cindex user-modifiable variables
 
 The following is an alphabetical list of variables that you can change to
-control how @command{awk} does certain things. The variables that are
-specific to @command{gawk} are marked with a pound sign@w{ (@samp{#}).}
+control how @command{awk} does certain things.
+
+The variables that are specific to @command{gawk} are marked with a pound
+sign (@samp{#}).  These variables are @command{gawk} extensions.  In other
+@command{awk} implementations or if @command{gawk} is in compatibility
+mode (@pxref{Options}), they are not special.  (Any exceptions are noted
+in the description of each variable.)
 
 @table @code
 @cindex @code{BINMODE} variable
 @cindex binary input/output
 @cindex input/output, binary
-@item BINMODE #
-On non-POSIX systems, this variable specifies use of binary mode for all I/O.
-Numeric values of one, two, or three specify that input files, output files, or
-all files, respectively, should use binary I/O.
-A numeric value less than zero is treated as zero, and a numeric value greater than
-three is treated as three.
-Alternatively,
-string values of @code{"r"} or @code{"w"} specify that input files and
-output files, respectively, should use binary I/O.
-A string value of @code{"rw"} or @code{"wr"} indicates that all
-files should use binary I/O.
-Any other string value is treated the same as @code{"rw"},
-but causes @command{gawk}
-to generate a warning message.
-@code{BINMODE} is described in more detail in
-@ref{PC Using}.
-
 @cindex differences in @command{awk} and @command{gawk}, @code{BINMODE} variable
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations
-(except @command{mawk},
-@pxref{Other Versions}),
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
+@item BINMODE #
+On non-POSIX systems, this variable specifies use of binary mode
+for all I/O.  Numeric values of one, two, or three specify that input
+files, output files, or all files, respectively, should use binary I/O.
+A numeric value less than zero is treated as zero, and a numeric value
+greater than three is treated as three.  Alternatively, string values
+of @code{"r"} or @code{"w"} specify that input files and output files,
+respectively, should use binary I/O.  A string value of @code{"rw"} or
+@code{"wr"} indicates that all files should use binary I/O.  Any other
+string value is treated the same as @code{"rw"}, but causes @command{gawk}
+to generate a warning message.  @code{BINMODE} is described in more
+detail in @ref{PC Using}.  @command{mawk} @pxref{Other Versions}),
+also supports this variable, but only using numeric values.
 
 @cindex @code{CONVFMT} variable
 @cindex POSIX @command{awk}, @code{CONVFMT} variable and
 @cindex numbers, converting, to strings
 @cindex strings, converting, numbers to
-@item CONVFMT
+@item @code{CONVFMT}
 This string controls conversion of numbers to
 strings (@pxref{Conversion}).
 It works by being passed, in effect, as the first argument to the
@@ -13369,40 +14238,29 @@ Its default value is @code{"%.6g"}.
 @cindex field separators, @code{FIELDWIDTHS} variable and
 @cindex separators, field, @code{FIELDWIDTHS} variable and
 @item FIELDWIDTHS #
-This is a space-separated list of columns that tells @command{gawk}
+A space-separated list of columns that tells @command{gawk}
 how to split input with fixed columnar boundaries.
 Assigning a value to @code{FIELDWIDTHS}
 overrides the use of @code{FS} and @code{FPAT} for field splitting.
 @xref{Constant Size}, for more information.
 
-If @command{gawk} is in compatibility mode
-(@pxref{Options}), then @code{FIELDWIDTHS}
-has no special meaning, and field-splitting operations occur based
-exclusively on the value of @code{FS}.
-
 @cindex @command{gawk}, @code{FPAT} variable in
 @cindex @code{FPAT} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{FPAT} variable
 @cindex field separators, @code{FPAT} variable and
 @cindex separators, field, @code{FPAT} variable and
 @item FPAT #
-This is a regular expression (as a string) that tells @command{gawk}
+A regular expression (as a string) that tells @command{gawk}
 to create the fields based on text that matches the regular expression.
 Assigning a value to @code{FPAT}
 overrides the use of @code{FS} and @code{FIELDWIDTHS} for field splitting.
 @xref{Splitting By Content}, for more information.
 
-If @command{gawk} is in compatibility mode
-(@pxref{Options}), then @code{FPAT}
-has no special meaning, and field-splitting operations occur based
-exclusively on the value of @code{FS}.
-
 @cindex @code{FS} variable
 @cindex separators, field
 @cindex field separators
 @item FS
-This is the input field separator
-(@pxref{Field Separators}).
+The input field separator (@pxref{Field Separators}).
 The value is a single-character string or a multicharacter regular
 expression that matches the separations between fields in an input
 record.  If the value is the null string (@code{""}), then each
@@ -13436,8 +14294,8 @@ is to simply say @samp{FS = FS}, perhaps with an explanatory comment.
 @cindex @command{gawk}, @code{IGNORECASE} variable in
 @cindex @code{IGNORECASE} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{IGNORECASE} variable
-@cindex case sensitivity, string comparisons and
-@cindex case sensitivity, regexps and
+@cindex case sensitivity, and string comparisons
+@cindex case sensitivity, and regexps
 @cindex regular expressions, case sensitivity
 @item IGNORECASE #
 If @code{IGNORECASE} is nonzero or non-null, then all string comparisons
@@ -13452,18 +14310,13 @@ and it does not affect field splitting when using a single-character
 field separator.
 @xref{Case-sensitivity}.
 
-If @command{gawk} is in compatibility mode
-(@pxref{Options}),
-then @code{IGNORECASE} has no special meaning.  Thus, string
-and regexp operations are always case-sensitive.
-
 @cindex @command{gawk}, @code{LINT} variable in
 @cindex @code{LINT} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{LINT} variable
 @cindex lint checking
 @item LINT #
 When this variable is true (nonzero or non-null), @command{gawk}
-behaves as if the @option{--lint} command-line option is in effect.
+behaves as if the @option{--lint} command-line option is in effect
 (@pxref{Options}).
 With a value of @code{"fatal"}, lint warnings become fatal errors.
 With a value of @code{"invalid"}, only warnings about things that are
@@ -13484,7 +14337,7 @@ of @command{awk} being executed.
 @cindex numbers, converting, to strings
 @cindex strings, converting, numbers to
 @item OFMT
-This string controls conversion of numbers to
+Controls conversion of numbers to
 strings (@pxref{Conversion}) for
 printing with the @code{print} statement.  It works by being passed
 as the first argument to the @code{sprintf()} function
@@ -13505,27 +14358,26 @@ default value is @w{@code{" "}}, a string consisting of a single space.
 
 @cindex @code{ORS} variable
 @item ORS
-This is the output record separator.  It is output at the end of every
+The output record separator.  It is output at the end of every
 @code{print} statement.  Its default value is @code{"\n"}, the newline
 character.  (@xref{Output Separators}.)
 
 @cindex @code{PREC} variable
 @item PREC #
 The working precision of arbitrary precision floating-point numbers,
-53 bits by default (@pxref{Setting Precision}).
+53 bits by default (@pxref{Setting precision}).
 
 @cindex @code{ROUNDMODE} variable
 @item ROUNDMODE #
 The rounding mode to use for arbitrary precision arithmetic on
 numbers, by default @code{"N"} (@samp{roundTiesToEven} in
-the IEEE-754 standard)
-(@pxref{Setting Rounding Mode}).
+the IEEE 754 standard; @pxref{Setting the rounding mode}).
 
 @cindex @code{RS} variable
 @cindex separators, for records
 @cindex record separators
-@item RS
-This is @command{awk}'s input record separator.  Its default value is a string
+@item @code{RS}
+The input record separator.  Its default value is a string
 containing a single newline character, which means that an input record
 consists of a single line of text.
 It can also be the null string, in which case records are separated by
@@ -13544,8 +14396,8 @@ just the first character of @code{RS}'s value is used.
 @cindex @code{SUBSEP} variable
 @cindex separators, subscript
 @cindex subscript separators
-@item SUBSEP
-This is the subscript separator.  It has the default value of
+@item @code{SUBSEP}
+The subscript separator.  It has the default value of
 @code{"\034"} and is used to separate the parts of the indices of a
 multidimensional array.  Thus, the expression @code{@w{foo["A", "B"]}}
 really accesses @code{foo["A\034B"]}
@@ -13556,18 +14408,12 @@ really accesses @code{foo["A\034B"]}
 @cindex differences in @command{awk} and @command{gawk}, @code{TEXTDOMAIN} variable
 @cindex internationalization, localization
 @item TEXTDOMAIN #
-This variable is used for internationalization of programs at the
+Used for internationalization of programs at the
 @command{awk} level.  It sets the default text domain for specially
 marked string constants in the source text, as well as for the
 @code{dcgettext()}, @code{dcngettext()} and @code{bindtextdomain()} functions
 (@pxref{Internationalization}).
 The default value of @code{TEXTDOMAIN} is @code{"messages"}.
-
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
 @end table
 @c ENDOFRANGE bvar
 @c ENDOFRANGE varb
@@ -13583,14 +14429,19 @@ it is not special.
 @cindex variables, built-in, conveying information
 The following is an alphabetical list of variables that @command{awk}
 sets automatically on certain occasions in order to provide
-information to your program.  The variables that are specific to
-@command{gawk} are marked with a pound sign@w{ (@samp{#}).}
+information to your program.
 
-@table @code
+The variables that are specific to @command{gawk} are marked with a pound
+sign (@samp{#}).  These variables are @command{gawk} extensions.  In other
+@command{awk} implementations or if @command{gawk} is in compatibility
+mode (@pxref{Options}), they are not special.
+
+@c @asis for docbook
+@table @asis
 @cindex @code{ARGC}/@code{ARGV} variables
 @cindex arguments, command-line
 @cindex command line, arguments
-@item ARGC@r{,} ARGV
+@item @code{ARGC}, @code{ARGV}
 The command-line arguments available to @command{awk} programs are stored in
 an array called @code{ARGV}.  @code{ARGC} is the number of command-line
 arguments present.  @xref{Other Arguments}.
@@ -13602,16 +14453,16 @@ In the following example:
 $ @kbd{awk 'BEGIN @{}
 >         @kbd{for (i = 0; i < ARGC; i++)}
 >             @kbd{print ARGV[i]}
->      @kbd{@}' inventory-shipped BBS-list}
+>      @kbd{@}' inventory-shipped mail-list}
 @print{} awk
 @print{} inventory-shipped
-@print{} BBS-list
+@print{} mail-list
 @end example
 
 @noindent
 @code{ARGV[0]} contains @samp{awk}, @code{ARGV[1]}
 contains @samp{inventory-shipped}, and @code{ARGV[2]} contains
-@samp{BBS-list}.  The value of @code{ARGC} is three, one more than the
+@samp{mail-list}.  The value of @code{ARGC} is three, one more than the
 index of the last element in @code{ARGV}, because the elements are numbered
 from zero.
 
@@ -13630,36 +14481,30 @@ about how @command{awk} uses these variables.
 
 @cindex @code{ARGIND} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{ARGIND} variable
-@item ARGIND #
+@item @code{ARGIND #}
 The index in @code{ARGV} of the current file being processed.
-Every time @command{gawk} opens a new data file for processing, it sets
-@code{ARGIND} to the index in @code{ARGV} of the file name.
+Every time @command{gawk} opens a new @value{DF} for processing, it sets
+@code{ARGIND} to the index in @code{ARGV} of the @value{FN}.
 When @command{gawk} is processing the input files,
 @samp{FILENAME == ARGV[ARGIND]} is always true.
 
 @cindex files, processing@comma{} @code{ARGIND} variable and
 This variable is useful in file processing; it allows you to tell how far
-along you are in the list of data files as well as to distinguish between
-successive instances of the same file name on the command line.
+along you are in the list of @value{DF}s as well as to distinguish between
+successive instances of the same @value{FN} on the command line.
 
 @cindex file names, distinguishing
 While you can change the value of @code{ARGIND} within your @command{awk}
 program, @command{gawk} automatically sets it to a new value when the
 next file is opened.
 
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
-
 @cindex @code{ENVIRON} array
-@cindex environment variables
-@item ENVIRON
+@cindex environment variables, in @code{ENVIRON} array
+@item @code{ENVIRON}
 An associative array containing the values of the environment.  The array
 indices are the environment variable names; the elements are the values of
 the particular environment variables.  For example,
-@code{ENVIRON["HOME"]} might be @file{/home/arnold}.
+@code{ENVIRON["HOME"]} might be @code{/home/arnold}.
 
 For POSIX @command{awk}, changing this array does not affect the
 environment passed on to any programs that @command{awk} may spawn via
@@ -13674,80 +14519,60 @@ executable programs.
 
 Some operating systems may not have environment variables.
 On such systems, the @code{ENVIRON} array is empty (except for
-@w{@code{ENVIRON["AWKPATH"]}},
-@pxref{AWKPATH Variable} and
-@w{@code{ENVIRON["AWKLIBPATH"]}},
+@w{@code{ENVIRON["AWKPATH"]}} and
+@w{@code{ENVIRON["AWKLIBPATH"]}};
+@pxref{AWKPATH Variable}, and
 @pxref{AWKLIBPATH Variable}).
 
 @cindex @command{gawk}, @code{ERRNO} variable in
 @cindex @code{ERRNO} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{ERRNO} variable
 @cindex error handling, @code{ERRNO} variable and
-@item ERRNO #
-If a system error occurs during a redirection for @code{getline},
-during a read for @code{getline}, or during a @code{close()} operation,
-then @code{ERRNO} contains a string describing the error.
-
-In addition, @command{gawk} clears @code{ERRNO}
-before opening each command-line input file. This enables checking if
-the file is readable inside a @code{BEGINFILE} pattern (@pxref{BEGINFILE/ENDFILE}).
-
-Otherwise,
-@code{ERRNO} works similarly to the C variable @code{errno}.
-Except for the case just mentioned,
-@command{gawk} @emph{never} clears it (sets it
-to zero or @code{""}).  Thus, you should only expect its value
-to be meaningful when an I/O operation returns a failure
-value, such as @code{getline} returning @minus{}1.
-You are, of course, free to clear it yourself before doing an
-I/O operation.
-
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
+@item @code{ERRNO #}
+If a system error occurs during a redirection for @code{getline}, during
+a read for @code{getline}, or during a @code{close()} operation, then
+@code{ERRNO} contains a string describing the error.
+
+In addition, @command{gawk} clears @code{ERRNO} before opening each
+command-line input file. This enables checking if the file is readable
+inside a @code{BEGINFILE} pattern (@pxref{BEGINFILE/ENDFILE}).
+
+Otherwise, @code{ERRNO} works similarly to the C variable @code{errno}.
+Except for the case just mentioned, @command{gawk} @emph{never} clears
+it (sets it to zero or @code{""}).  Thus, you should only expect its
+value to be meaningful when an I/O operation returns a failure value,
+such as @code{getline} returning @minus{}1.  You are, of course, free
+to clear it yourself before doing an I/O operation.
 
 @cindex @code{FILENAME} variable
 @cindex dark corner, @code{FILENAME} variable
-@item FILENAME
-The name of the file that @command{awk} is currently reading.
-When no data files are listed on the command line, @command{awk} reads
-from the standard input and @code{FILENAME} is set to @code{"-"}.
-@code{FILENAME} is changed each time a new file is read
-(@pxref{Reading Files}).
-Inside a @code{BEGIN} rule, the value of @code{FILENAME} is
-@code{""}, since there are no input files being processed
-yet.@footnote{Some early implementations of Unix @command{awk} initialized
-@code{FILENAME} to @code{"-"}, even if there were data files to be
-processed. This behavior was incorrect and should not be relied
-upon in your programs.}
-@value{DARKCORNER}
-Note, though, that using @code{getline}
-(@pxref{Getline})
-inside a @code{BEGIN} rule can give
-@code{FILENAME} a value.
+@item @code{FILENAME}
+The name of the current input file.  When no @value{DF}s are listed
+on the command line, @command{awk} reads from the standard input and
+@code{FILENAME} is set to @code{"-"}.  @code{FILENAME} changes each
+time a new file is read (@pxref{Reading Files}).  Inside a @code{BEGIN}
+rule, the value of @code{FILENAME} is @code{""}, since there are no input
+files being processed yet.@footnote{Some early implementations of Unix
+@command{awk} initialized @code{FILENAME} to @code{"-"}, even if there
+were @value{DF}s to be processed. This behavior was incorrect and should
+not be relied upon in your programs.} @value{DARKCORNER} Note, though,
+that using @code{getline} (@pxref{Getline}) inside a @code{BEGIN} rule
+can give @code{FILENAME} a value.
 
 @cindex @code{FNR} variable
-@item FNR
+@item @code{FNR}
 The current record number in the current file.  @code{FNR} is
 incremented each time a new record is read
 (@pxref{Records}).  It is reinitialized
 to zero each time a new input file is started.
 
 @cindex @code{NF} variable
-@item NF
+@item @code{NF}
 The number of fields in the current input record.
 @code{NF} is set each time a new record is read, when a new field is
 created or when @code{$0} changes (@pxref{Fields}).
 
-Unlike most of the variables described in this
-@ifnotinfo
-section,
-@end ifnotinfo
-@ifinfo
-node,
-@end ifinfo
+Unlike most of the variables described in this @value{SUBSECTION},
 assigning a value to @code{NF} has the potential to affect
 @command{awk}'s internal workings.  In particular, assignments
 to @code{NF} can be used to create or remove fields from the
@@ -13756,18 +14581,18 @@ current record. @xref{Changing Fields}.
 @cindex @code{FUNCTAB} array
 @cindex @command{gawk}, @code{FUNCTAB} array in
 @cindex differences in @command{awk} and @command{gawk}, @code{FUNCTAB} variable
-@item FUNCTAB #
+@item @code{FUNCTAB #}
 An array whose indices and corresponding values are the names of all
 the user-defined or extension functions in the program.
 
 @quotation NOTE
 Attempting to use the @code{delete} statement with the @code{FUNCTAB}
-array will cause a fatal error.  Any attempt to assign to an element of
-the @code{FUNCTAB} array will also cause a fatal error.
+array causes a fatal error.  Any attempt to assign to an element of
+@code{FUNCTAB} also causes a fatal error.
 @end quotation
 
 @cindex @code{NR} variable
-@item NR
+@item @code{NR}
 The number of input records @command{awk} has processed since
 the beginning of the program's execution
 (@pxref{Records}).
@@ -13776,17 +14601,19 @@ the beginning of the program's execution
 @cindex @command{gawk}, @code{PROCINFO} array in
 @cindex @code{PROCINFO} array
 @cindex differences in @command{awk} and @command{gawk}, @code{PROCINFO} array
-@item PROCINFO #
+@item @code{PROCINFO #}
 The elements of this array provide access to information about the
 running @command{awk} program.
 The following elements (listed alphabetically)
 are guaranteed to be available:
 
 @table @code
+@cindex effective group ID of @command{gawk} user
 @item PROCINFO["egid"]
 The value of the @code{getegid()} system call.
 
 @item PROCINFO["euid"]
+@cindex effective user ID of @command{gawk} user
 The value of the @code{geteuid()} system call.
 
 @item PROCINFO["FS"]
@@ -13796,6 +14623,7 @@ This is
 or @code{"FPAT"} if field matching with @code{FPAT} is in effect.
 
 @item PROCINFO["identifiers"]
+@cindex program identifiers
 A subarray, indexed by the names of all identifiers used in the
 text of the AWK program.  For each identifier, the value of the element is one of the following:
 
@@ -13824,21 +14652,25 @@ after it has finished parsing the program; they are @emph{not} updated
 while the program runs.
 
 @item PROCINFO["gid"]
+@cindex group ID of @command{gawk} user
 The value of the @code{getgid()} system call.
 
 @item PROCINFO["pgrpid"]
+@cindex process group idIDof @command{gawk} process
 The process group ID of the current process.
 
 @item PROCINFO["pid"]
+@cindex process ID of @command{gawk} process
 The process ID of the current process.
 
 @item PROCINFO["ppid"]
+@cindex parent process ID of @command{gawk} process
 The parent process ID of the current process.
 
 @item PROCINFO["sorted_in"]
 If this element exists in @code{PROCINFO}, its value controls the
 order in which array indices will be processed by
-@samp{for (index in array) @dots{}} loops.
+@samp{for (@var{index} in @var{array})} loops.
 Since this is an advanced feature, we defer the
 full description until later; see
 @ref{Scanning an Array}.
@@ -13852,6 +14684,8 @@ Assigning a new value to this element changes the default.
 The value of the @code{getuid()} system call.
 
 @item PROCINFO["version"]
+@cindex version of @command{gawk}
+@cindex @command{gawk} version
 The version of @command{gawk}.
 @end table
 
@@ -13861,16 +14695,20 @@ if your version of @command{gawk} supports arbitrary precision numbers
 (@pxref{Arbitrary Precision Arithmetic}): 
 
 @table @code 
+@cindex version of GNU MPFR library
 @item PROCINFO["mpfr_version"]
 The version of the GNU MPFR library.
 
 @item PROCINFO["gmp_version"]
+@cindex version of GNU MP library
 The version of the GNU MP library.
 
 @item PROCINFO["prec_max"]
+@cindex maximum precision supported by MPFR library
 The maximum precision supported by MPFR.
 
 @item PROCINFO["prec_min"]
+@cindex minimum precision supported by MPFR library
 The minimum precision required by MPFR.
 @end table
 
@@ -13881,12 +14719,15 @@ of @command{gawk} supports dynamic loading of extension functions
 
 @table @code
 @item PROCINFO["api_major"]
+@cindex version of @command{gawk} extension API
+@cindex extension API, version number
 The major version of the extension API.
 
 @item PROCINFO["api_minor"]
 The minor version of the extension API.
 @end table
 
+@cindex supplementary groups of @command{gawk} process
 On some systems, there may be elements in the array, @code{"group1"}
 through @code{"group@var{N}"} for some @var{N}. @var{N} is the number of
 supplementary groups that the process has.  Use the @code{in} operator
@@ -13894,15 +14735,14 @@ to test for these elements
 (@pxref{Reference to Elements}).
 
 @cindex @command{gawk}, @code{PROCINFO} array in
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, uses
 The @code{PROCINFO} array has the following additional uses:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-It may be
-used to cause coprocesses
-to communicate over pseudo-ttys instead of through two-way pipes;
-this is discussed further in @ref{Two-way I/O}.
+It may be used to cause coprocesses to communicate over pseudo-ttys
+instead of through two-way pipes; this is discussed further in
+@ref{Two-way I/O}.
 
 @item
 It may be used to provide a timeout when reading from any
@@ -13910,14 +14750,8 @@ open input file, pipe, or coprocess.
 @xref{Read Timeout}, for more information.
 @end itemize
 
-This array is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
-
 @cindex @code{RLENGTH} variable
-@item RLENGTH
+@item @code{RLENGTH}
 The length of the substring matched by the
 @code{match()} function
 (@pxref{String Functions}).
@@ -13925,7 +14759,7 @@ The length of the substring matched by the
 is the length of the matched string, or @minus{}1 if no match is found.
 
 @cindex @code{RSTART} variable
-@item RSTART
+@item @code{RSTART}
 The start-index in characters of the substring that is matched by the
 @code{match()} function
 (@pxref{String Functions}).
@@ -13936,20 +14770,14 @@ if no match was found.
 @cindex @command{gawk}, @code{RT} variable in
 @cindex @code{RT} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{RT} variable
-@item RT #
-This is set each time a record is read. It contains the input text
-that matched the text denoted by @code{RS}, the record separator.
-
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
+@item @code{RT #}
+The input text that matched the text denoted by @code{RS},
+the record separator.  It is set every time a record is read.
 
 @cindex @command{gawk}, @code{SYMTAB} array in
 @cindex @code{SYMTAB} array
 @cindex differences in @command{awk} and @command{gawk}, @code{SYMTAB} variable
-@item SYMTAB #
+@item @code{SYMTAB #}
 An array whose indices are the names of all currently defined
 global variables and arrays in the program.  The array may be used
 for indirect access to read or write the value of a variable:
@@ -13966,7 +14794,7 @@ if an element in @code{SYMTAB} is an array.
 Also, you may not use the @code{delete} statement with the
 @code{SYMTAB} array.
 
-You may use an index for @code{SYMTAB} that is not a predefined identifer:
+You may use an index for @code{SYMTAB} that is not a predefined identifier:
 
 @example
 SYMTAB["xxx"] = 5
@@ -13978,6 +14806,7 @@ This works as expected: in this case @code{SYMTAB} acts just like
 a regular array.  The only difference is that you can't then delete
 @code{SYMTAB["xxx"]}.
 
+@cindex Schorr, Andrew
 The @code{SYMTAB} array is more interesting than it looks. Andrew Schorr
 points out that it effectively gives @command{awk} data pointers. Consider his
 example:
@@ -13992,8 +14821,8 @@ function multiply(variable, amount)
 @end example
 
 @quotation NOTE
-In order to avoid severe time-travel paradoxes@footnote{Not to mention difficult
-implementation issues.}, neither @code{FUNCTAB} nor @code{SYMTAB}
+In order to avoid severe time-travel paradoxes,@footnote{Not to mention difficult
+implementation issues.} neither @code{FUNCTAB} nor @code{SYMTAB}
 are available as elements within the @code{SYMTAB} array.
 @end quotation
 @end table
@@ -14080,7 +14909,7 @@ changed.
 
 @node ARGC and ARGV
 @subsection Using @code{ARGC} and @code{ARGV}
-@cindex @code{ARGC}/@code{ARGV} variables
+@cindex @code{ARGC}/@code{ARGV} variables, how to use
 @cindex arguments, command-line
 @cindex command line, arguments
 
@@ -14092,16 +14921,16 @@ and @code{ARGV}:
 $ @kbd{awk 'BEGIN @{}
 >        @kbd{for (i = 0; i < ARGC; i++)}
 >            @kbd{print ARGV[i]}
->      @kbd{@}' inventory-shipped BBS-list}
+>      @kbd{@}' inventory-shipped mail-list}
 @print{} awk
 @print{} inventory-shipped
-@print{} BBS-list
+@print{} mail-list
 @end example
 
 @noindent
 In this example, @code{ARGV[0]} contains @samp{awk}, @code{ARGV[1]}
 contains @samp{inventory-shipped}, and @code{ARGV[2]} contains
-@samp{BBS-list}.
+@samp{mail-list}.
 Notice that the @command{awk} program is not entered in @code{ARGV}.  The
 other command-line options, with their arguments, are also not
 entered.  This includes variable assignments done with the @option{-v}
@@ -14142,11 +14971,11 @@ additional files to be read.
 If the value of @code{ARGC} is decreased, that eliminates input files
 from the end of the list.  By recording the old value of @code{ARGC}
 elsewhere, a program can treat the eliminated arguments as
-something other than file names.
+something other than @value{FN}s.
 
 To eliminate a file from the middle of the list, store the null string
 (@code{""}) into @code{ARGV} in place of the file's name.  As a
-special feature, @command{awk} ignores file names that have been
+special feature, @command{awk} ignores @value{FN}s that have been
 replaced with the null string.
 Another option is to
 use the @code{delete} statement to remove elements from
@@ -14205,6 +15034,65 @@ are passed on to the @command{awk} program.
 (@xref{Getopt Function}, for an @command{awk} library function
 that parses command-line options.)
 
+@node Pattern Action Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Pattern-action pairs make up the basic elements of an @command{awk}
+program.  Patterns are either normal expressions, range expressions,
+regexp constants, one of the special keywords @code{BEGIN}, @code{END},
+@code{BEGINFILE}, @code{ENDFILE}, or empty.  The action executes if
+the current record matches the pattern.  Empty (missing) patterns match
+all records.
+
+@item
+I/O from @code{BEGIN} and @code{END} rules have certain constraints.
+This is also true, only more so, for @code{BEGINFILE} and @code{ENDFILE}
+rules.  The latter two give you ``hooks'' into @command{gawk}'s file
+processing, allowing you to recover from a file that otherwise would
+cause a fatal error (such as a file that cannot be opened).
+
+@item
+Shell variables can be used in @command{awk} programs by careful
+use of shell quoting.  It is easier to pass a shell variable into
+@command{awk} by using the @option{-v} option and an @command{awk}
+variable.
+
+@item
+Actions consist of statements enclosed in curly braces. Statements
+are built up from expressions, control statements, compound statements,
+input and output statements, and deletion statements.
+
+@item
+The control statements in @command{awk} are @code{if}-@code{else},
+@code{while}, @code{for}, and @code{do}-@code{while}.  @command{gawk}
+adds the @code{switch} statement.  There are two flavors of @code{for}
+statement: one for for performing general looping, and the other iterating
+through an array.
+
+@item
+@code{break} and @code{continue} let you exit early or start the next
+iteration of a loop (or get out of a @code{switch}).
+
+@item
+@code{next} and @code{nextfile} let you read the next record and start
+over at the top of your program, or skip to the next input file and
+start over, respectively.
+
+@item
+The @code{exit} statement terminates your program. When executed
+from an action (or function body) it transfers control to the
+@code{END} statements. From an @code{END} statement body, it exits
+immediately.  You may pass an optional numeric value to be used
+at @command{awk}'s exit status.
+
+@item
+Some built-in variables provide control over @command{awk}, mainly for I/O.
+Other variables convey information from @command{awk} to your program.
+
+@end itemize
+
 @node Arrays
 @chapter Arrays in @command{awk}
 @c STARTOFRANGE arrs
@@ -14221,11 +15109,11 @@ It also describes how @command{awk} simulates multidimensional
 arrays, as well as some of the less obvious points about array usage.
 The @value{CHAPTER} moves on to discuss @command{gawk}'s facility
 for sorting arrays, and ends with a brief description of @command{gawk}'s
-ability to support true multidimensional arrays.
+ability to support true arrays of arrays.
 
 @cindex variables, names of
 @cindex functions, names of
-@cindex arrays, names of
+@cindex arrays, names of, and names of functions/variables
 @cindex names, arrays/variables
 @cindex namespace issues
 @command{awk} maintains a single set
@@ -14244,6 +15132,7 @@ same @command{awk} program.
 * Multidimensional::            Emulating multidimensional arrays in
                                 @command{awk}.
 * Arrays of Arrays::            True multidimensional arrays.
+* Arrays Summary::              Summary of arrays.
 @end menu
 
 @node Array Basics
@@ -14305,35 +15194,34 @@ the array is declared.)
 
 A contiguous array of four elements might look like the following example,
 conceptually, if the element values are 8, @code{"foo"},
-@code{""}, and 30:
+@code{""}, and 30
+@ifnotdocbook
+as shown in @ref{figure-array-elements}:
+@end ifnotdocbook
+@ifdocbook
+as shown in @inlineraw{docbook, <xref linkend="figure-array-elements"/>}:
+@end ifdocbook
 
-@c @strong{FIXME: NEXT ED:} Use real images here, and an @float
-@iftex
-@c from Karl Berry, much thanks for the help.
-@tex
-\bigskip % space above the table (about 1 linespace)
-\offinterlineskip
-\newdimen\width \width = 1.5cm
-\newdimen\hwidth \hwidth = 4\width \advance\hwidth by 2pt % 5 * 0.4pt
-\centerline{\vbox{
-\halign{\strut\hfil\ignorespaces#&&\vrule#&\hbox to\width{\hfil#\unskip\hfil}\cr
-\noalign{\hrule width\hwidth}
-	&&{\tt 8} &&{\tt "foo"} &&{\tt ""} &&{\tt 30} &&\quad Value\cr
-\noalign{\hrule width\hwidth}
-\noalign{\smallskip}
-	&\omit&0&\omit &1   &\omit&2 &\omit&3 &\omit&\quad Index\cr
-}
-}}
-@end tex
-@end iftex
-@ifnottex
-@example
-+---------+---------+--------+---------+
-|    8    |  "foo"  |   ""   |    30   |    @r{Value}
-+---------+---------+--------+---------+
-     0         1         2         3        @r{Index}
-@end example
-@end ifnottex
+@ifnotdocbook
+@float Figure,figure-array-elements
+@caption{A Contiguous Array}
+@ifinfo
+@center @image{array-elements, , , Basic Program Stages, txt}
+@end ifinfo
+@ifnotinfo
+@center @image{array-elements, , , Basic Program Stages}
+@end ifnotinfo
+@end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-array-elements" float="0">
+<title>A Contiguous Array</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="array-elements.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 @noindent
 Only the values are stored; the indices are implicit from the order of
@@ -14350,12 +15238,53 @@ Arrays in @command{awk} are different---they are @dfn{associative}.  This means
 that each array is a collection of pairs: an index and its corresponding
 array element value:
 
+@ifnotdocbook
 @example
 @r{Index} 3     @r{Value} 30
 @r{Index} 1     @r{Value} "foo"
 @r{Index} 0     @r{Value} 8
 @r{Index} 2     @r{Value} ""
 @end example
+@end ifnotdocbook
+
+@docbook
+<informaltable>
+<tgroup cols="2">
+<colspec colname="1" align="center"/>
+<colspec colname="2" align="center"/>
+<thead>
+<row>
+<entry>Index</entry>
+<entry>Value</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+<entry><literal>3</literal></entry>
+<entry><literal>30</literal></entry>
+</row>
+
+<row>
+<entry><literal>1</literal></entry>
+<entry><literal>"foo"</literal></entry>
+</row>
+
+<row>
+<entry><literal>0</literal></entry>
+<entry><literal>8</literal></entry>
+</row>
+
+<row>
+<entry><literal>2</literal></entry>
+<entry><literal>""</literal></entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 @noindent
 The pairs are shown in jumbled order because their order is irrelevant.
@@ -14364,6 +15293,7 @@ One advantage of associative arrays is that new pairs can be added
 at any time.  For example, suppose a tenth element is added to the array
 whose value is @w{@code{"number ten"}}.  The result is:
 
+@ifnotdocbook
 @example
 @r{Index} 10    @r{Value} "number ten"
 @r{Index} 3     @r{Value} 30
@@ -14371,6 +15301,51 @@ whose value is @w{@code{"number ten"}}.  The result is:
 @r{Index} 0     @r{Value} 8
 @r{Index} 2     @r{Value} ""
 @end example
+@end ifnotdocbook
+
+@docbook
+<informaltable>
+<tgroup cols="2">
+<colspec colname="1" align="center"/>
+<colspec colname="2" align="center"/>
+<thead>
+<row>
+<entry>Index</entry>
+<entry>Value</entry>
+</row>
+</thead>
+<tbody>
+
+<row>
+<entry><literal>10</literal></entry>
+<entry><literal>"number ten"</literal></entry>
+</row>
+
+<row>
+<entry><literal>3</literal></entry>
+<entry><literal>30</literal></entry>
+</row>
+
+<row>
+<entry><literal>1</literal></entry>
+<entry><literal>"foo"</literal></entry>
+</row>
+
+<row>
+<entry><literal>0</literal></entry>
+<entry><literal>8</literal></entry>
+</row>
+
+<row>
+<entry><literal>2</literal></entry>
+<entry><literal>""</literal></entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 @noindent
 @cindex sparse arrays
@@ -14383,28 +15358,67 @@ have to be positive integers.  Any number, or even a string, can be
 an index.  For example, the following is an array that translates words from
 English to French:
 
+@ifnotdocbook
 @example
 @r{Index} "dog" @r{Value} "chien"
 @r{Index} "cat" @r{Value} "chat"
 @r{Index} "one" @r{Value} "un"
 @r{Index} 1     @r{Value} "un"
 @end example
+@end ifnotdocbook
+
+@docbook
+<informaltable>
+<tgroup cols="2">
+<colspec colname="1" align="center"/>
+<colspec colname="2" align="center"/>
+<thead>
+<row>
+<entry>Index</entry>
+<entry>Value</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry><literal>"dog"</literal></entry>
+<entry><literal>"chien"</literal></entry>
+</row>
+
+<row>
+<entry><literal>"cat"</literal></entry>
+<entry><literal>"chat"</literal></entry>
+</row>
+
+<row>
+<entry><literal>"one"</literal></entry>
+<entry><literal>"un"</literal></entry>
+</row>
+
+<row>
+<entry><literal>1</literal></entry>
+<entry><literal>"un"</literal></entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 @noindent
 Here we decided to translate the number one in both spelled-out and
 numeric form---thus illustrating that a single array can have both
 numbers and strings as indices.
-In fact, array subscripts are always strings; this is discussed
+(In fact, array subscripts are always strings; this is discussed
 in more detail in
-@ref{Numeric Array Subscripts}.
+@ref{Numeric Array Subscripts}.)
 Here, the number @code{1} isn't double-quoted, since @command{awk}
 automatically converts it to a string.
 
 @cindex @command{gawk}, @code{IGNORECASE} variable in
-@cindex @code{IGNORECASE} variable
 @cindex case sensitivity, array indices and
-@cindex arrays, @code{IGNORECASE} variable and
-@cindex @code{IGNORECASE} variable, array subscripts and
+@cindex arrays, and @code{IGNORECASE} variable
+@cindex @code{IGNORECASE} variable, and array indices
 The value of @code{IGNORECASE} has no effect upon array subscripting.
 The identical string value used to store an array element must be used
 to retrieve it.
@@ -14420,8 +15434,9 @@ is independent of the number of elements in the array.
 
 @node Reference to Elements
 @subsection Referring to an Array Element
-@cindex arrays, elements, referencing
-@cindex elements in arrays
+@cindex arrays, referencing elements
+@cindex array members
+@cindex elements of arrays
 
 The principal way to use an array is to refer to one of its elements.
 An array reference is an expression as follows:
@@ -14438,11 +15453,16 @@ The value of the array reference is the current value of that array
 element.  For example, @code{foo[4.3]} is an expression for the element
 of array @code{foo} at index @samp{4.3}.
 
+@cindex arrays, unassigned elements
+@cindex unassigned array elements
+@cindex empty array elements
 A reference to an array element that has no recorded value yields a value of
 @code{""}, the null string.  This includes elements
 that have not been assigned any value as well as elements that have been
 deleted (@pxref{Delete}).
 
+@cindex non-existent array elements
+@cindex arrays, elements that don't exist
 @quotation NOTE
 A reference to an element that does not exist @emph{automatically} creates
 that array element, with the null string as its value.  (In some cases,
@@ -14462,19 +15482,19 @@ if it didn't exist before!
 @end quotation
 
 @c @cindex arrays, @code{in} operator and
-@cindex @code{in} operator
+@cindex @code{in} operator, testing if array element exists
 To determine whether an element exists in an array at a certain index, use
 the following expression:
 
 @example
-@var{ind} in @var{array}
+@var{indx} in @var{array}
 @end example
 
 @cindex side effects, array indexing
 @noindent
-This expression tests whether the particular index @var{ind} exists,
+This expression tests whether the particular index @var{indx} exists,
 without the side effect of creating that element if it is not present.
-The expression has the value one (true) if @code{@var{array}[@var{ind}]}
+The expression has the value one (true) if @code{@var{array}[@var{indx}]}
 exists and zero (false) if it does not exist.
 For example, this statement tests whether the array @code{frequencies}
 contains the index @samp{2}:
@@ -14497,8 +15517,8 @@ if (frequencies[2] != "")
 
 @node Assigning Elements
 @subsection Assigning Array Elements
-@cindex arrays, elements, assigning
-@cindex elements in arrays, assigning
+@cindex arrays, elements, assigning values
+@cindex elements in arrays, assigning values
 
 Array elements can be assigned values just like
 @command{awk} variables:
@@ -14515,6 +15535,7 @@ assign to that element of the array.
 
 @node Array Example
 @subsection Basic Array Example
+@cindex arrays, an example of using
 
 The following program takes a list of lines, each beginning with a line
 number, and prints them out in order of line number.  The line numbers
@@ -14584,7 +15605,9 @@ END @{
 @node Scanning an Array
 @subsection Scanning All Elements of an Array
 @cindex elements in arrays, scanning
+@cindex scanning arrays
 @cindex arrays, scanning
+@cindex loops, @code{for}, array scanning
 
 In programs that use arrays, it is often necessary to use a loop that
 executes once for each element of an array.  In other languages, where
@@ -14601,7 +15624,7 @@ for (@var{var} in @var{array})
 @end example
 
 @noindent
-@cindex @code{in} operator
+@cindex @code{in} operator, use in loops
 This loop executes @var{body} once for each index in @var{array} that the
 program has previously used, with the variable @var{var} set to that index.
 
@@ -14640,18 +15663,61 @@ END @{
 @xref{Word Sorting},
 for a more detailed example of this type.
 
-@cindex arrays, elements, order of
-@cindex elements in arrays, order of
+@cindex arrays, elements, order of access by @code{in} operator
+@cindex elements in arrays, order of access by @code{in} operator
+@cindex @code{in} operator, order of array access
 The order in which elements of the array are accessed by this statement
 is determined by the internal arrangement of the array elements within
-@command{awk} and normally cannot be controlled or changed.  This can lead to
-problems if new elements are added to @var{array} by statements in
-the loop body; it is not predictable whether the @code{for} loop will
-reach them.  Similarly, changing @var{var} inside the loop may produce
-strange results.  It is best to avoid such things.
+@command{awk} and in standard @command{awk} cannot be controlled
+or changed.  This can lead to problems if new elements are added to
+@var{array} by statements in the loop body; it is not predictable whether
+the @code{for} loop will reach them.  Similarly, changing @var{var} inside
+the loop may produce strange results.  It is best to avoid such things.
+
+As a point of information, @command{gawk} sets up the list of elements
+to be iterated over before the loop starts, and does not change it.
+But not all @command{awk} versions do so. Consider this program, named
+@file{loopcheck.awk}:
+
+@example
+BEGIN @{
+    a["here"] = "here"
+    a["is"] = "is"
+    a["a"] = "a"
+    a["loop"] = "loop"
+    for (i in a) @{
+        j++
+        a[j] = j
+        print i
+    @}
+@}
+@end example
+
+Here is what happens when run with @command{gawk}:
+
+@example
+$ @kbd{gawk -f loopcheck.awk}
+@print{} here
+@print{} loop
+@print{} a
+@print{} is
+@end example
+
+Contrast this to Brian Kernighan's @command{awk}:
+
+@example
+$ @kbd{nawk -f loopcheck.awk}
+@print{} loop
+@print{} here
+@print{} is
+@print{} a
+@print{} 1
+@end example
 
 @node Controlling Scanning
-@subsection Using Predefined Array Scanning Orders
+@subsection Using Predefined Array Scanning Orders With @command{gawk}
+
+This @value{SUBSECTION} describes a feature that is specific to @command{gawk}.
 
 By default, when a @code{for} loop traverses an array, the order
 is undefined, meaning that the @command{awk} implementation
@@ -14659,12 +15725,14 @@ determines the order in which the array is traversed.
 This order is usually based on the internal implementation of arrays
 and will vary from one version of @command{awk} to the next.
 
+@cindex array scanning order, controlling
+@cindex controlling array scanning order
 Often, though, you may wish to do something simple, such as
 ``traverse the array by comparing the indices in ascending order,''
 or ``traverse the array by comparing the values in descending order.''
 @command{gawk} provides two mechanisms which give you this control.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Set @code{PROCINFO["sorted_in"]} to one of a set of predefined values.
 We describe this now.
@@ -14675,6 +15743,7 @@ to use for comparison of array elements. This advanced feature
 is described later, in @ref{Array Sorting}.
 @end itemize
 
+@cindex @code{PROCINFO}, values of @code{sorted_in}
 The following special values for @code{PROCINFO["sorted_in"]} are available:
 
 @table @code
@@ -14770,7 +15839,7 @@ order relative to each other is determined by their index strings.
 Here are some additional things to bear in mind about sorted
 array traversal.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The value of @code{PROCINFO["sorted_in"]} is global. That is, it affects
 all array traversal @code{for} loops.  If you need to change it within your
@@ -14835,7 +15904,7 @@ if (4 in foo)
     print "This will never be printed"
 @end example
 
-@cindex null strings, array elements and
+@cindex null strings, and deleting array elements
 It is important to note that deleting an element is @emph{not} the
 same as assigning it a null value (the empty string, @code{""}).
 For example:
@@ -14857,6 +15926,7 @@ is not in the array is deleted.
 @cindex extensions, common@comma{} @code{delete} to delete entire arrays
 @cindex arrays, deleting entire contents
 @cindex deleting entire arrays
+@cindex @code{delete} @var{array}
 @cindex differences in @command{awk} and @command{gawk}, array elements, deleting
 All the elements of an array may be deleted with a single statement
 by leaving off the subscript in the @code{delete} statement,
@@ -14871,6 +15941,7 @@ Using this version of the @code{delete} statement is about three times
 more efficient than the equivalent loop that deletes each element one
 at a time.
 
+@cindex Brian Kernighan's @command{awk}
 @quotation NOTE
 For many years,
 using @code{delete} without a subscript was a @command{gawk} extension.
@@ -14913,9 +15984,9 @@ a = 3
 @section Using Numbers to Subscript Arrays
 
 @cindex numbers, as array subscripts
-@cindex arrays, subscripts
+@cindex arrays, numeric subscripts
 @cindex subscripts in arrays, numbers as
-@cindex @code{CONVFMT} variable, array subscripts and
+@cindex @code{CONVFMT} variable, and array subscripts
 An important aspect to remember about arrays is that @emph{array subscripts
 are always strings}.  When a numeric value is used as a subscript,
 it is converted to a string value before being used for subscripting
@@ -14945,7 +16016,8 @@ string value from @code{xyz}---this time @code{"12.15"}---because the value of
 @code{CONVFMT} only allows two significant digits.  This test fails,
 since @code{"12.15"} is different from @code{"12.153"}.
 
-@cindex converting, during subscripting
+@cindex converting integer array subscripts
+@cindex integer array indices
 According to the rules for conversions
 (@pxref{Conversion}), integer
 values are always converted to strings as integers, no matter what the
@@ -14999,7 +16071,7 @@ $ @kbd{echo 'line 1}
 @print{} line 2
 @end example
 
-Unfortunately, the very first line of input data did not come out in the
+Unfortunately, the very first line of input data did not appear in the
 output!
 
 Upon first glance, we would think that this program should have worked.
@@ -15039,7 +16111,7 @@ on the command line (@pxref{Options}).
 @section Multidimensional Arrays
 
 @menu
-* Multiscanning::              Scanning multidimensional arrays.
+* Multiscanning::               Scanning multidimensional arrays.
 @end menu
 
 @cindex subscripts in arrays, multidimensional
@@ -15051,7 +16123,7 @@ languages, including @command{awk}) to refer to an element of a
 two-dimensional array named @code{grid} is with
 @code{grid[@var{x},@var{y}]}.
 
-@cindex @code{SUBSEP} variable, multidimensional arrays
+@cindex @code{SUBSEP} variable, and multidimensional arrays
 Multidimensional arrays are supported in @command{awk} through
 concatenation of indices into one string.
 @command{awk} converts the indices into strings
@@ -15083,6 +16155,7 @@ combined strings that are ambiguous.  Suppose that @code{SUBSEP} is
 "b@@c"]}} are indistinguishable because both are actually
 stored as @samp{foo["a@@b@@c"]}.
 
+@cindex @code{in} operator, index existence in multidimensional arrays
 To test whether a particular index sequence exists in a
 multidimensional array, use the same operator (@code{in}) that is
 used for single dimensional arrays.  Write the whole sequence of indices
@@ -15148,6 +16221,7 @@ multidimensional @emph{way of accessing} an array.
 
 @cindex subscripts in arrays, multidimensional, scanning
 @cindex arrays, multidimensional, scanning
+@cindex scanning multidimensional arrays
 However, if your program has an array that is always accessed as
 multidimensional, you can get the effect of scanning it by combining
 the scanning @code{for} statement
@@ -15189,12 +16263,13 @@ separate indices is recovered.
 
 @node Arrays of Arrays
 @section Arrays of Arrays
+@cindex arrays of arrays
 
 @command{gawk} goes beyond standard @command{awk}'s multidimensional
 array access and provides true arrays of
 arrays. Elements of a subarray are referred to by their own indices
 enclosed in square brackets, just like the elements of the main array.
-For example, the following creates a two-element subarray at index @samp{1}
+For example, the following creates a two-element subarray at index @code{1}
 of the main array @code{a}:
 
 @example
@@ -15218,7 +16293,7 @@ Each subarray and the main array can be of different length. In fact, the
 elements of an array or its subarray do not all have to have the same
 type. This means that the main array and any of its subarrays can be
 non-rectangular, or jagged in structure. One can assign a scalar value to
-the index @samp{4} of the main array @code{a}:
+the index @code{4} of the main array @code{a}:
 
 @example
 a[4] = "An element in a jagged array"
@@ -15239,7 +16314,7 @@ a[4][5][6][7] = "An element in a four-dimensional array"
 @end example
 
 @noindent
-This removes the scalar value from index @samp{4} and then inserts a
+This removes the scalar value from index @code{4} and then inserts a
 subarray of subarray of subarray containing a scalar. You can also
 delete an entire subarray or subarray of subarrays:
 
@@ -15340,6 +16415,63 @@ creating an arbitrary index:
 $ @kbd{gawk 'BEGIN @{ b[1][1] = ""; split("a b c d", b[1]); print b[1][1] @}'}
 @print{} a
 @end example
+
+@node Arrays Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Standard @command{awk} provides one-dimensional associative arrays
+(arrays indexed by string values).  All arrays are associative; numeric
+indices are converted automatically to strings.
+
+@item
+Array elements are referenced as @code{@var{array}[@var{indx}]}.
+Referencing an element creates it if it did not exist previously.
+
+@item
+The proper way to see if an array has an element with a given index
+is to use the @code{in} operator: @samp{@var{indx} in @var{array}}.
+
+@item
+Use @samp{for (@var{indx} in @var{array}) @dots{}} to scan through all the
+individual elements of an array. In the body of the loop, @var{indx} takes
+on the value of each element's index in turn.
+
+@item
+The order in which a @samp{for (@var{indx} in @var{array})} loop
+traverses an array is undefined in POSIX @command{awk} and varies among
+implementations.  @command{gawk} lets you control the order by assigning
+special predefined values to @code{PROCINFO["sorted_in"]}.
+
+@item
+Use @samp{delete @var{array}[@var{indx}]} to delete an individual element.
+You may also use @samp{delete @var{array}} to delete all of the elements
+in the array.  This latter feature has been a common extension for many
+years and is now standard, but may not be supported by all commercial
+versions of @command{awk}.
+
+@item
+Standard @command{awk} simulates multidimensional arrays by separating
+subscript values with a comma.  The values are concatenated into a
+single string, separated by the value of @code{SUBSEP}.  The fact
+that such a subscript was created in this way is not retained; thus
+changing @code{SUBSEP} may have unexpected consequences.  You can use
+@samp{(@var{sub1}, @var{sub2}, @dots{}) in @var{array}} to see if such
+a multidimensional subscript exists in @var{array}.
+
+@item
+@command{gawk} provides true arrays of arrays. You use a separate
+set of square brackets for each dimension in such an array:
+@code{data[row][col]}, for example. Array elements may thus be either
+scalar values (number or string) or another array.
+
+@item
+Use the @code{isarray()} built-in function to determine if an array
+element is itself a subarray.
+
+@end itemize
+
 @c ENDOFRANGE arrs
 
 @node Functions
@@ -15364,6 +16496,7 @@ The second half of this @value{CHAPTER} describes these
 * Built-in::                    Summarizes the built-in functions.
 * User-defined::                Describes User-defined functions in detail.
 * Indirect Calls::              Choosing the function to call at runtime.
+* Functions Summary::           Summary of functions.
 @end menu
 
 @node Built-in
@@ -15448,42 +16581,50 @@ two arguments 11 and 10.
 
 @node Numeric Functions
 @subsection Numeric Functions
+@cindex numeric functions
 
 The following list describes all of
 the built-in functions that work with numbers.
 Optional parameters are enclosed in square brackets@w{ ([ ]):}
 
-@table @code
-@item atan2(@var{y}, @var{x})
-@cindex @code{atan2()} function
+@c @asis for docbook
+@table @asis
+@item @code{atan2(@var{y}, @var{x})}
+@cindexawkfunc{atan2}
+@cindex arctangent
 Return the arctangent of @code{@var{y} / @var{x}} in radians.
-You can use @samp{pi = atan2(0, -1)} to retrieve the value of @value{PI}.
+You can use @samp{pi = atan2(0, -1)} to retrieve the value of
+@value{PI}.
 
-@item cos(@var{x})
-@cindex @code{cos()} function
+@item @code{cos(@var{x})}
+@cindexawkfunc{cos}
+@cindex cosine
 Return the cosine of @var{x}, with @var{x} in radians.
 
-@item exp(@var{x})
-@cindex @code{exp()} function
+@item @code{exp(@var{x})}
+@cindexawkfunc{exp}
+@cindex exponent
 Return the exponential of @var{x} (@code{e ^ @var{x}}) or report
 an error if @var{x} is out of range.  The range of values @var{x} can have
 depends on your machine's floating-point representation.
 
-@item int(@var{x})
-@cindex @code{int()} function
+@item @code{int(@var{x})}
+@cindexawkfunc{int}
+@cindex round to nearest integer
 Return the nearest integer to @var{x}, located between @var{x} and zero and
 truncated toward zero.
 
 For example, @code{int(3)} is 3, @code{int(3.9)} is 3, @code{int(-3.9)}
 is @minus{}3, and @code{int(-3)} is @minus{}3 as well.
 
-@item log(@var{x})
-@cindex @code{log()} function
+@item @code{log(@var{x})}
+@cindexawkfunc{log}
+@cindex logarithm
 Return the natural logarithm of @var{x}, if @var{x} is positive;
 otherwise, report an error.
 
-@item rand()
-@cindex @code{rand()} function
+@item @code{rand()}
+@cindexawkfunc{rand}
 @cindex random numbers, @code{rand()}/@code{srand()} functions
 Return a random number.  The values of @code{rand()} are
 uniformly distributed between zero and one.
@@ -15525,7 +16666,7 @@ function roll(n) @{ return 1 + int(rand() * n) @}
 @}
 @end example
 
-@cindex numbers, random
+@cindex seeding random number generator
 @cindex random numbers, seed of
 @quotation CAUTION
 In most @command{awk} implementations, including @command{gawk},
@@ -15540,18 +16681,20 @@ the seed to a value that is different in each run.  To do this,
 use @code{srand()}.
 @end quotation
 
-@item sin(@var{x})
-@cindex @code{sin()} function
+@item @code{sin(@var{x})}
+@cindexawkfunc{sin}
+@cindex sine
 Return the sine of @var{x}, with @var{x} in radians.
 
-@item sqrt(@var{x})
-@cindex @code{sqrt()} function
+@item @code{sqrt(@var{x})}
+@cindexawkfunc{sqrt}
+@cindex square root
 Return the positive square root of @var{x}.
 @command{gawk} prints a warning message
 if @var{x} is negative.  Thus, @code{sqrt(4)} is 2.
 
-@item srand(@r{[}@var{x}@r{]})
-@cindex @code{srand()} function
+@item @code{srand(}[@var{x}]@code{)}
+@cindexawkfunc{srand}
 Set the starting point, or seed,
 for generating random numbers to the value @var{x}.
 
@@ -15581,6 +16724,7 @@ sequences of random numbers.
 
 @node String Functions
 @subsection String-Manipulation Functions
+@cindex string-manipulation functions
 
 The functions in this @value{SECTION} look at or change the text of one
 or more strings.
@@ -15593,12 +16737,23 @@ example, @code{length()} returns the number of characters in a string,
 and not the number of bytes used to represent those characters. Similarly,
 @code{index()} works with character indices, and not byte indices.
 
+@quotation CAUTION
+A number of functions deal with indices into strings.  For these
+functions, the first character of a string is at position (index) one.
+This is different from C and the languages descended from it, where the
+first character is at position zero.  You need to remember this when
+doing index calculations, particularly if you are used to C.
+@end quotation
+
 In the following list, optional parameters are enclosed in square brackets@w{ ([ ]).}
 Several functions perform string substitution; the full discussion is
 provided in the description of the @code{sub()} function, which comes
 towards the end since the list is presented in alphabetic order.
+
 Those functions that are specific to @command{gawk} are marked with a
-pound sign@w{ (@samp{#}):}
+pound sign (@samp{#}).  They are not available in compatibility mode
+(@pxref{Options}):
+
 
 @menu
 * Gory Details::                More than you want to know about @samp{\} and
@@ -15606,14 +16761,15 @@ pound sign@w{ (@samp{#}):}
                                 @code{gensub()}.
 @end menu
 
-@table @code
-@item asort(@var{source} @r{[}, @var{dest} @r{[}, @var{how}  @r{]} @r{]}) #
-@itemx asorti(@var{source} @r{[}, @var{dest} @r{[}, @var{how}  @r{]} @r{]}) #
-@cindex @code{asorti()} function (@command{gawk})
+@c @asis for docbook
+@table @asis
+@item @code{asort(}@var{source} [@code{,} @var{dest} [@code{,} @var{how} ] ]@code{) #}
+@itemx @code{asorti(}@var{source} [@code{,} @var{dest} [@code{,} @var{how} ] ]@code{) #}
+@cindexgawkfunc{asorti}
+@cindex sort array
 @cindex arrays, elements, retrieving number of
-@cindex @code{asort()} function (@command{gawk})
-@cindex @command{gawk}, @code{IGNORECASE} variable in
-@cindex @code{IGNORECASE} variable
+@cindexgawkfunc{asort}
+@cindex sort array indices
 These two functions are similar in behavior, so they are described
 together.
 
@@ -15631,7 +16787,9 @@ sequential integers starting with one.  If the optional array @var{dest}
 is specified, then @var{source} is duplicated into @var{dest}.  @var{dest}
 is then sorted, leaving the indices of @var{source} unchanged.
 
-When comparing strings, @code{IGNORECASE} affects the sorting.  If the
+@cindex @command{gawk}, @code{IGNORECASE} variable in
+When comparing strings, @code{IGNORECASE} affects the sorting
+(@pxref{Array Sorting Functions}).  If the
 @var{source} array contains subarrays as values (@pxref{Arrays of
 Arrays}), they will come last, after all scalar values.
 
@@ -15670,11 +16828,10 @@ a[2] = "last"
 a[3] = "middle"
 @end example
 
-@code{asort()} and @code{asorti()} are @command{gawk} extensions; they
-are not available in compatibility mode (@pxref{Options}).
-
-@item gensub(@var{regexp}, @var{replacement}, @var{how} @r{[}, @var{target}@r{]}) #
-@cindex @code{gensub()} function (@command{gawk})
+@item @code{gensub(@var{regexp}, @var{replacement}, @var{how}} [@code{, @var{target}}]@code{) #}
+@cindexgawkfunc{gensub}
+@cindex search and replace in strings
+@cindex substitute in string
 Search the target string @var{target} for matches of the regular
 expression @var{regexp}.  If @var{how} is a string beginning with
 @samp{g} or @samp{G} (short for ``global''), then replace all matches of @var{regexp} with
@@ -15683,7 +16840,7 @@ which match of @var{regexp} to replace. If no @var{target} is supplied,
 use @code{$0}.  It returns the modified string as the result
 of the function and the original target string is @emph{not} changed.
 
-@code{gensub()} is a general substitution function.  It's purpose is
+@code{gensub()} is a general substitution function.  Its purpose is
 to provide more features than the standard @code{sub()} and @code{gsub()}
 functions.
 
@@ -15733,11 +16890,8 @@ a warning message.
 If @var{regexp} does not match @var{target}, @code{gensub()}'s return value
 is the original unchanged value of @var{target}.
 
-@code{gensub()} is a @command{gawk} extension; it is not available
-in compatibility mode (@pxref{Options}).
-
-@item gsub(@var{regexp}, @var{replacement} @r{[}, @var{target}@r{]})
-@cindex @code{gsub()} function
+@item @code{gsub(@var{regexp}, @var{replacement}} [@code{, @var{target}}]@code{)}
+@cindexawkfunc{gsub}
 Search @var{target} for
 @emph{all} of the longest, leftmost, @emph{nonoverlapping} matching
 substrings it can find and replace them with @var{replacement}.
@@ -15758,9 +16912,10 @@ omitted, then the entire input record (@code{$0}) is used.
 As in @code{sub()}, the characters @samp{&} and @samp{\} are special,
 and the third argument must be assignable.
 
-@item index(@var{in}, @var{find})
-@cindex @code{index()} function
-@cindex searching
+@item @code{index(@var{in}, @var{find})}
+@cindexawkfunc{index}
+@cindex search in string
+@cindex find substring in string
 Search the string @var{in} for the first occurrence of the string
 @var{find}, and return the position in characters where that occurrence
 begins in the string @var{in}.  Consider the following example:
@@ -15772,19 +16927,33 @@ $ @kbd{awk 'BEGIN @{ print index("peanut", "an") @}'}
 
 @noindent
 If @var{find} is not found, @code{index()} returns zero.
-(Remember that string indices in @command{awk} start at one.)
 
 It is a fatal error to use a regexp constant for @var{find}.
 
-@item length(@r{[}@var{string}@r{]})
-@cindex @code{length()} function
+@item @code{length(}[@var{string}]@code{)}
+@cindexawkfunc{length}
+@cindex string length
+@cindex length of string
 Return the number of characters in @var{string}.  If
 @var{string} is a number, the length of the digit string representing
 that number is returned.  For example, @code{length("abcde")} is five.  By
-contrast, @code{length(15 * 35)} works out to three. In this example, 15 * 35 =
-525, and 525 is then converted to the string @code{"525"}, which has
+contrast, @code{length(15 * 35)} works out to three. In this example,
+@iftex
+@math{15 @cdot 35 = 525},
+@end iftex
+@ifnottex
+@ifnotdocbook
+15 * 35 = 525,
+@end ifnotdocbook
+@end ifnottex
+@docbook
+15 &sdot; 35 = 525, @c
+@end docbook
+and 525 is then converted to the string @code{"525"}, which has
 three characters.
 
+@cindex length of input record
+@cindex input record, length of
 If no argument is supplied, @code{length()} returns the length of @code{$0}.
 
 @c @cindex historical features
@@ -15823,6 +16992,8 @@ warning about this.
 @cindex common extensions, @code{length()} applied to an array
 @cindex extensions, common@comma{} @code{length()} applied to an array
 @cindex differences between @command{gawk} and @command{awk}
+@cindex number of array elements
+@cindex array, number of elements
 With @command{gawk} and several other @command{awk} implementations, when given an
 array argument, the @code{length()} function returns the number of elements
 in the array. @value{COMMONEXT}
@@ -15835,16 +17006,18 @@ If @option{--lint} is provided on the command line
 If @option{--posix} is supplied, using an array argument is a fatal error
 (@pxref{Arrays}).
 
-@item match(@var{string}, @var{regexp} @r{[}, @var{array}@r{]})
-@cindex @code{match()} function
+@item @code{match(@var{string}, @var{regexp}} [@code{, @var{array}}]@code{)}
+@cindexawkfunc{match}
+@cindex string, regular expression match
+@cindex match regexp in string
 Search @var{string} for the
 longest, leftmost substring matched by the regular expression,
-@var{regexp} and return the character position, or @dfn{index},
+@var{regexp} and return the character position (index)
 at which that substring begins (one, if it starts at the beginning of
 @var{string}).  If no match is found, return zero.
 
 The @var{regexp} argument may be either a regexp constant
-(@code{/@dots{}/}) or a string constant (@code{"@dots{}"}).
+(@code{/}@dots{}@code{/}) or a string constant (@code{"}@dots{}@code{"}).
 In the latter case, the string is treated as a regexp to be matched.
 @xref{Computed Regexps}, for a
 discussion of the difference between the two forms, and the
@@ -15950,8 +17123,9 @@ The @var{array} argument to @code{match()} is a
 (@pxref{Options}),
 using a third argument is a fatal error.
 
-@item patsplit(@var{string}, @var{array} @r{[}, @var{fieldpat} @r{[}, @var{seps} @r{]} @r{]}) #
-@cindex @code{patsplit()} function (@command{gawk})
+@item @code{patsplit(@var{string}, @var{array}} [@code{, @var{fieldpat}} [@code{, @var{seps}} ] ]@code{) #}
+@cindexgawkfunc{patsplit}
+@cindex split string into array
 Divide
 @var{string} into pieces defined by @var{fieldpat}
 and store the pieces in @var{array} and the separator strings in the
@@ -15975,14 +17149,8 @@ manner similar to the way input lines are split into fields using @code{FPAT}
 Before splitting the string, @code{patsplit()} deletes any previously existing
 elements in the arrays @var{array} and @var{seps}.
 
-@cindex troubleshooting, @code{patsplit()} function
-The @code{patsplit()} function is a
-@command{gawk} extension.  In compatibility mode
-(@pxref{Options}),
-it is not available.
-
-@item split(@var{string}, @var{array} @r{[}, @var{fieldsep} @r{[}, @var{seps} @r{]} @r{]})
-@cindex @code{split()} function
+@item @code{split(@var{string}, @var{array}} [@code{, @var{fieldsep}} [@code{, @var{seps}} ] ]@code{)}
+@cindexawkfunc{split}
 Divide @var{string} into pieces separated by @var{fieldsep}
 and store the pieces in @var{array} and the separator strings in the
 @var{seps} array.  The first piece is stored in
@@ -16011,7 +17179,7 @@ split("cul-de-sac", a, "-", seps)
 @end example
 
 @noindent
-@cindex strings, splitting
+@cindex strings splitting, example
 splits the string @samp{cul-de-sac} into three fields using @samp{-} as the
 separator.  It sets the contents of the array @code{a} as follows:
 
@@ -16066,8 +17234,11 @@ If @var{string} does not match @var{fieldsep} at all (but is not null),
 @var{array} has one element only. The value of that element is the original
 @var{string}.
 
-@item sprintf(@var{format}, @var{expression1}, @dots{})
-@cindex @code{sprintf()} function
+In POSIX mode (@pxref{Options}), the fourth argument is not allowed.
+
+@item @code{sprintf(@var{format}, @var{expression1}, @dots{})}
+@cindexawkfunc{sprintf}
+@cindex formatting strings
 Return (without printing) the string that @code{printf} would
 have printed out with the same arguments
 (@pxref{Printf}).
@@ -16080,8 +17251,9 @@ pival = sprintf("pi = %.2f (approx.)", 22/7)
 @noindent
 assigns the string @w{@samp{pi = 3.14 (approx.)}} to the variable @code{pival}.
 
-@cindex @code{strtonum()} function (@command{gawk})
-@item strtonum(@var{str}) #
+@cindexgawkfunc{strtonum}
+@cindex convert string to number
+@item @code{strtonum(@var{str}) #}
 Examine @var{str} and return its numeric value.  If @var{str}
 begins with a leading @samp{0}, @code{strtonum()} assumes that @var{str}
 is an octal number.  If @var{str} begins with a leading @samp{0x} or
@@ -16103,12 +17275,9 @@ you use the @option{--non-decimal-data} option, which isn't recommended.
 Note also that @code{strtonum()} uses the current locale's decimal point
 for recognizing numbers (@pxref{Locales}).
 
-@cindex differences in @command{awk} and @command{gawk}, @code{strtonum()} function (@command{gawk})
-@code{strtonum()} is a @command{gawk} extension; it is not available
-in compatibility mode (@pxref{Options}).
-
-@item sub(@var{regexp}, @var{replacement} @r{[}, @var{target}@r{]})
-@cindex @code{sub()} function
+@item @code{sub(@var{regexp}, @var{replacement}} [@code{, @var{target}}]@code{)}
+@cindexawkfunc{sub}
+@cindex replace in string
 Search @var{target}, which is treated as a string, for the
 leftmost, longest substring matched by the regular expression @var{regexp}.
 Modify the entire string
@@ -16117,7 +17286,7 @@ The modified string becomes the new value of @var{target}.
 Return the number of substitutions made (zero or one).
 
 The @var{regexp} argument may be either a regexp constant
-(@code{/@dots{}/}) or a string constant (@code{"@dots{}"}).
+(@code{/}@dots{}@code{/}) or a string constant (@code{"}@dots{}@code{"}).
 In the latter case, the string is treated as a regexp to be matched.
 @xref{Computed Regexps}, for a
 discussion of the difference between the two forms, and the
@@ -16207,8 +17376,9 @@ will not run.
 Finally, if the @var{regexp} is not a regexp constant, it is converted into a
 string, and then the value of that string is treated as the regexp to match.
 
-@item substr(@var{string}, @var{start} @r{[}, @var{length}@r{]})
-@cindex @code{substr()} function
+@item @code{substr(@var{string}, @var{start}} [@code{, @var{length}} ]@code{)}
+@cindexawkfunc{substr}
+@cindex substring
 Return a @var{length}-character-long substring of @var{string},
 starting at character number @var{start}.  The first character of a
 string is character number one.@footnote{This is different from
@@ -16222,6 +17392,7 @@ suffix is also returned
 if @var{length} is greater than the number of characters remaining
 in the string, counting from character @var{start}.
 
+@cindex Brian Kernighan's @command{awk}
 If @var{start} is less than one, @code{substr()} treats it as
 if it was one. (POSIX doesn't specify what to do in this case:
 Brian Kernighan's @command{awk} acts this way, and therefore @command{gawk}
@@ -16264,16 +17435,18 @@ string = substr(string, 1, 2) "CDE" substr(string, 6)
 @end example
 
 @cindex case sensitivity, converting case
-@cindex converting, case
-@item tolower(@var{string})
-@cindex @code{tolower()} function
+@cindex strings, converting letter case
+@item @code{tolower(@var{string})}
+@cindexawkfunc{tolower}
+@cindex convert string to lower case
 Return a copy of @var{string}, with each uppercase character
 in the string replaced with its corresponding lowercase character.
 Nonalphabetic characters are left unchanged.  For example,
 @code{tolower("MiXeD cAsE 123")} returns @code{"mixed case 123"}.
 
-@item toupper(@var{string})
-@cindex @code{toupper()} function
+@item @code{toupper(@var{string})}
+@cindexawkfunc{toupper}
+@cindex convert string to upper case
 Return a copy of @var{string}, with each lowercase character
 in the string replaced with its corresponding uppercase character.
 Nonalphabetic characters are left unchanged.  For example,
@@ -16297,10 +17470,11 @@ that there are several levels of @dfn{escape processing} going on.
 
 First, there is the @dfn{lexical} level, which is when @command{awk} reads
 your program
-and builds an internal copy of it that can be executed.
+and builds an internal copy of it to execute.
 Then there is the runtime level, which is when @command{awk} actually scans the
 replacement string to determine what to generate.
 
+@cindex Brian Kernighan's @command{awk}
 At both levels, @command{awk} looks for a defined set of characters that
 can come after a backslash.  At the lexical level, it looks for the
 escape sequences listed in @ref{Escape Sequences}.
@@ -16439,7 +17613,7 @@ says, in effect, that @samp{\} turns off the special meaning of any
 following character, but for anything other than @samp{\} and @samp{&},
 such special meaning is undefined.  This wording leads to two problems:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Backslashes must now be doubled in the @var{replacement} string, breaking
 historical @command{awk} programs.
@@ -16570,17 +17744,17 @@ _bigskip}
 The only case where the difference is noticeable is the last one: @samp{\\\\}
 is seen as @samp{\\} and produces @samp{\} instead of @samp{\\}.
 
-Starting with version 3.1.4, @command{gawk} followed the POSIX rules
+Starting with @value{PVERSION} 3.1.4, @command{gawk} followed the POSIX rules
 when @option{--posix} is specified (@pxref{Options}). Otherwise,
 it continued to follow the 1996 proposed rules, since
 that had been its behavior for many years.
 
-When version 4.0.0 was released, the @command{gawk} maintainer
+When @value{PVERSION} 4.0.0 was released, the @command{gawk} maintainer
 made the POSIX rules the default, breaking well over a decade's worth
 of backwards compatibility.@footnote{This was rather naive of him, despite
 there being a note in this section indicating that the next major version
 would move to the POSIX rules.} Needless to say, this was a bad idea,
-and as of version 4.0.1, @command{gawk} resumed its historical
+and as of @value{PVERSION} 4.0.1, @command{gawk} resumed its historical
 behavior, and only follows the POSIX rules when @option{--posix} is given.
 
 The rules for @code{gensub()} are considerably simpler. At the runtime
@@ -16698,14 +17872,16 @@ Although this makes a certain amount of sense, it can be surprising.
 
 @node I/O Functions
 @subsection Input/Output Functions
+@cindex input/output functions
 
 The following functions relate to input/output (I/O).
 Optional parameters are enclosed in square brackets ([ ]):
 
-@table @code
-@item close(@var{filename} @r{[}, @var{how}@r{]})
-@cindex @code{close()} function
+@table @asis
+@item @code{close(}@var{filename} [@code{,} @var{how}]@code{)}
+@cindexawkfunc{close}
 @cindex files, closing
+@cindex close file or coprocess
 Close the file @var{filename} for input or output. Alternatively, the
 argument may be a shell command that was used for creating a coprocess, or
 for redirecting to or from a pipe; then the coprocess or pipe is closed.
@@ -16721,8 +17897,12 @@ not matter.
 @xref{Two-way I/O},
 which discusses this feature in more detail and gives an example.
 
-@item fflush(@r{[}@var{filename}@r{]})
-@cindex @code{fflush()} function
+Note that the second argument to @code{close()} is a @command{gawk}
+extension; it is not available in compatibility mode (@pxref{Options}).
+
+@item @code{fflush(}[@var{filename}]@code{)}
+@cindexawkfunc{fflush}
+@cindex flush buffered output
 Flush any buffered output associated with @var{filename}, which is either a
 file opened for writing or a shell command for redirecting output to
 a pipe or coprocess.
@@ -16740,11 +17920,12 @@ This is the purpose of the @code{fflush()} function---@command{gawk} also
 buffers its output and the @code{fflush()} function forces
 @command{gawk} to flush its buffers.
 
-@code{fflush()} was added to Brian Kernighan's
-version of @command{awk} in 1994.
-For over two decades, it was not part of the POSIX standard.
-As of December, 2012, it was accepted for
-inclusion into the POSIX standard.
+@cindex extensions, common@comma{} @code{fflush()} function
+@cindex Brian Kernighan's @command{awk}
+@code{fflush()} was added to Brian Kernighan's @command{awk} in
+April of 1992.  For two decades, it was not part of the POSIX standard.
+As of December, 2012, it was accepted for inclusion into the POSIX
+standard.
 See @uref{http://austingroupbugs.net/view.php?id=634, the Austin Group website}.
 
 POSIX standardizes @code{fflush()} as follows: If there
@@ -16753,7 +17934,7 @@ then @command{awk} flushes the buffers for @emph{all} open output files
 and pipes.
 
 @quotation NOTE
-Prior to version 4.0.2, @command{gawk}
+Prior to @value{PVERSION} 4.0.2, @command{gawk}
 would flush only the standard output if there was no argument,
 and flush all output files and pipes if the argument was the null
 string. This was changed in order to be compatible with Brian
@@ -16769,7 +17950,7 @@ only the standard output.
 @c @cindex warnings, automatic
 @cindex troubleshooting, @code{fflush()} function
 @code{fflush()} returns zero if the buffer is successfully flushed;
-otherwise, it returns non-zero (@command{gawk} returns @minus{}1).
+otherwise, it returns non-zero. (@command{gawk} returns @minus{}1.)
 In the case where all buffers are flushed, the return value is zero
 only if all buffers were flushed successfully.  Otherwise, it is
 @minus{}1, and @command{gawk} warns about the problem @var{filename}.
@@ -16779,8 +17960,9 @@ a file or pipe that was opened for reading (such as with @code{getline}),
 or if @var{filename} is not an open file, pipe, or coprocess.
 In such a case, @code{fflush()} returns @minus{}1, as well.
 
-@item system(@var{command})
-@cindex @code{system()} function
+@item @code{system(@var{command})}
+@cindexawkfunc{system}
+@cindex invoke shell command
 @cindex interacting with other programs
 Execute the operating-system
 command @var{command} and then return to the @command{awk} program.
@@ -16811,7 +17993,7 @@ close("/bin/sh")
 
 @noindent
 @cindex troubleshooting, @code{system()} function
-@cindex @code{--sandbox} option, disabling @code{system()} function
+@cindex @option{--sandbox} option, disabling @code{system()} function
 However, if your @command{awk}
 program is interactive, @code{system()} is useful for running large
 self-contained programs, such as a shell or an editor.
@@ -17055,6 +18237,7 @@ you would see the latter (undesirable) output.
 
 @node Time Functions
 @subsection Time Functions
+@cindex time functions
 
 @c STARTOFRANGE tst
 @cindex timestamps
@@ -17071,10 +18254,26 @@ particular log record was written.  Many programs log their timestamp
 in the form returned by the @code{time()} system call, which is the
 number of seconds since a particular epoch.  On POSIX-compliant systems,
 it is the number of seconds since
-1970-01-01 00:00:00 UTC, not counting leap seconds.@footnote{@xref{Glossary},
-especially the entries ``Epoch'' and ``UTC.''}
+1970-01-01 00:00:00 UTC, not counting leap
+@ifclear FOR_PRINT
+seconds.@footnote{@xref{Glossary}, especially the entries ``Epoch'' and ``UTC.''}
+@end ifclear
+@ifset FOR_PRINT
+seconds.
+@end ifset
 All known POSIX-compliant systems support timestamps from 0 through
-@math{2^{31} - 1}, which is sufficient to represent times through
+@iftex
+@math{2^{31} - 1},
+@end iftex
+@ifnottex
+@ifnotdocbook
+2^31 - 1,
+@end ifnotdocbook
+@end ifnottex
+@docbook
+2<superscript>31</superscript> &minus; 1, @c
+@end docbook
+which is sufficient to represent times through
 2038-01-19 03:14:07 UTC.  Many systems support a wider range of timestamps,
 including negative timestamps that represent times before the
 epoch.
@@ -17091,9 +18290,11 @@ However, recent versions
 of @command{mawk} (@pxref{Other Versions}) also support these functions.
 Optional parameters are enclosed in square brackets ([ ]):
 
-@table @code
-@item mktime(@var{datespec})
-@cindex @code{mktime()} function (@command{gawk})
+@c @asis for docbook
+@table @asis
+@item @code{mktime(@var{datespec})}
+@cindexgawkfunc{mktime}
+@cindex generate time values
 Turn @var{datespec} into a timestamp in the same form
 as is returned by @code{systime()}.  It is similar to the function of the
 same name in ISO C.  The argument, @var{datespec}, is a string of the form
@@ -17121,9 +18322,10 @@ is out of range, @code{mktime()} returns @minus{}1.
 
 @cindex @command{gawk}, @code{PROCINFO} array in
 @cindex @code{PROCINFO} array
-@item strftime(@r{[}@var{format} @r{[}, @var{timestamp} @r{[}, @var{utc-flag}@r{]]]})
+@item @code{strftime(} [@var{format} [@code{,} @var{timestamp} [@code{,} @var{utc-flag}] ] ]@code{)}
 @c STARTOFRANGE strf
-@cindex @code{strftime()} function (@command{gawk})
+@cindexgawkfunc{strftime}
+@cindex format time string
 Format the time specified by @var{timestamp}
 based on the contents of the @var{format} string and return the result.
 It is similar to the function of the same name in ISO C.
@@ -17140,11 +18342,12 @@ The default string value is
 @code{@w{"%a %b %e %H:%M:%S %Z %Y"}}.  This format string produces
 output that is equivalent to that of the @command{date} utility.
 You can assign a new value to @code{PROCINFO["strftime"]} to
-change the default format.
+change the default format; see below for the various format directives.
 
-@item systime()
-@cindex @code{systime()} function (@command{gawk})
+@item @code{systime()}
+@cindexgawkfunc{systime}
 @cindex timestamps
+@cindex current system time
 Return the current time as the number of seconds since
 the system epoch.  On POSIX systems, this is the number of seconds
 since 1970-01-01 00:00:00 UTC, not counting leap seconds.
@@ -17216,10 +18419,10 @@ This is the ISO 8601 date format.
 
 @item %g
 The year modulo 100 of the ISO 8601 week number, as a decimal number (00--99).
-For example, January 1, 1993 is in week 53 of 1992. Thus, the year
-of its ISO 8601 week number is 1992, even though its year is 1993.
-Similarly, December 31, 1973 is in week 1 of 1974. Thus, the year
-of its ISO week number is 1974, even though its year is 1973.
+For example, January 1, 2012 is in week 53 of 2011. Thus, the year
+of its ISO 8601 week number is 2011, even though its year is 2012.
+Similarly, December 31, 2012 is in week 1 of 2013. Thus, the year
+of its ISO week number is 2013, even though its year is 2012.
 
 @item %G
 The full year of the ISO week number, as a decimal number.
@@ -17300,7 +18503,7 @@ The locale's ``appropriate'' time representation.
 The year modulo 100 as a decimal number (00--99).
 
 @item %Y
-The full year as a decimal number (e.g., 2011).
+The full year as a decimal number (e.g., 2015).
 
 @c @cindex RFC 822
 @c @cindex RFC 1036
@@ -17334,17 +18537,6 @@ uses the system's version of @code{strftime()} if it's there.
 Typically, the conversion specifier either does not appear in the
 returned string or appears literally.}
 
-@c @cindex locale, definition of
-Informally, a @dfn{locale} is the geographic place in which a program
-is meant to run.  For example, a common way to abbreviate the date
-September 4, 2012 in the United States is ``9/4/12.''
-In many countries in Europe, however, it is abbreviated ``4.9.12.''
-Thus, the @samp{%x} specification in a @code{"US"} locale might produce
-@samp{9/4/12}, while in a @code{"EUROPE"} locale, it might produce
-@samp{4.9.12}.  The ISO C standard defines a default @code{"C"}
-locale, which is an environment that is typical of what many C programmers
-are used to.
-
 For systems that are not yet fully standards-compliant,
 @command{gawk} supplies a copy of
 @code{strftime()} from the GNU C Library.
@@ -17397,7 +18589,7 @@ the string.  For example:
 
 @example
 $ date '+Today is %A, %B %d, %Y.'
-@print{} Today is Wednesday, March 30, 2011.
+@print{} Today is Monday, May 05, 2014.
 @end example
 
 Here is the @command{gawk} version of the @command{date} utility.
@@ -17417,7 +18609,7 @@ case $1 in
 esac
 
 gawk 'BEGIN  @{
-    format = "%a %b %e %H:%M:%S %Z %Y"
+    format = PROCINFO["strftime"]
     exitval = 0
 
     if (ARGC > 2)
@@ -17438,6 +18630,7 @@ gawk 'BEGIN  @{
 
 @node Bitwise Functions
 @subsection Bit-Manipulation Functions
+@cindex bit-manipulation functions
 @c STARTOFRANGE bit
 @cindex bitwise, operations
 @c STARTOFRANGE and
@@ -17504,9 +18697,7 @@ Operands  | 0 | 1 | 0 | 1 | 0 | 1
 @end tex
 
 @docbook
-<!-- FIXME: Fix ID and add xref in text. -->
-<table id="table-bitwise-ops">
-<title>Bitwise Operations</title>
+<informaltable>
 
 <tgroup cols="7" colsep="1">
 <colspec colname="c1"/>
@@ -17566,7 +18757,7 @@ Operands  | 0 | 1 | 0 | 1 | 0 | 1
 
 </tbody>
 </tgroup>
-</table>
+</informaltable>
 @end docbook
 @end float
 
@@ -17600,28 +18791,34 @@ bitwise operations just described. They are:
 
 @cindex @command{gawk}, bitwise operations in
 @table @code
-@cindex @code{and()} function (@command{gawk})
-@item and(@var{v1}, @var{v2} @r{[}, @r{@dots{}]})
+@cindexgawkfunc{and}
+@cindex bitwise AND
+@item @code{and(@var{v1}, @var{v2}} [@code{,} @dots{}]@code{)}
 Return the bitwise AND of the arguments. There must be at least two.
 
-@cindex @code{compl()} function (@command{gawk})
-@item compl(@var{val})
+@cindexgawkfunc{compl}
+@cindex bitwise complement
+@item @code{compl(@var{val})}
 Return the bitwise complement of @var{val}.
 
-@cindex @code{lshift()} function (@command{gawk})
-@item lshift(@var{val}, @var{count})
+@cindexgawkfunc{lshift}
+@cindex left shift
+@item @code{lshift(@var{val}, @var{count})}
 Return the value of @var{val}, shifted left by @var{count} bits.
 
-@cindex @code{or()} function (@command{gawk})
-@item or(@var{v1}, @var{v2} @r{[}, @r{@dots{}]})
+@cindexgawkfunc{or}
+@cindex bitwise OR
+@item @code{or(@var{v1}, @var{v2}} [@code{,} @dots{}]@code{)}
 Return the bitwise OR of the arguments. There must be at least two.
 
-@cindex @code{rshift()} function (@command{gawk})
-@item rshift(@var{val}, @var{count})
+@cindexgawkfunc{rshift}
+@cindex right shift
+@item @code{rshift(@var{val}, @var{count})}
 Return the value of @var{val}, shifted right by @var{count} bits.
 
-@cindex @code{xor()} function (@command{gawk})
-@item xor(@var{v1}, @var{v2} @r{[}, @r{@dots{}]})
+@cindexgawkfunc{xor}
+@cindex bitwise XOR
+@item @code{xor(@var{v1}, @var{v2}} [@code{,} @dots{}]@code{)}
 Return the bitwise XOR of the arguments. There must be at least two.
 @end table
 
@@ -17712,6 +18909,7 @@ $ @kbd{gawk -f testbits.awk}
 @cindex strings, converting
 @cindex numbers, converting
 @cindex converting, numbers to strings
+@cindex number as string of bits
 The @code{bits2str()} function turns a binary number into a string.
 The number @code{1} represents a binary value where the rightmost bit
 is set to 1.  Using this mask,
@@ -17743,11 +18941,12 @@ results of the @code{compl()}, @code{lshift()}, and @code{rshift()} functions.
 
 @command{gawk} provides a single function that lets you distinguish
 an array from a scalar variable.  This is necessary for writing code
-that traverses every element of a true multidimensional array
+that traverses every element of an array of arrays.
 (@pxref{Arrays of Arrays}).
 
 @table @code
-@cindex @code{isarray()} function (@command{gawk})
+@cindexgawkfunc{isarray}
+@cindex scalar or array
 @item isarray(@var{x})
 Return a true value if @var{x} is an array. Otherwise return false.
 @end table
@@ -17755,7 +18954,7 @@ Return a true value if @var{x} is an array. Otherwise return false.
 @code{isarray()} is meant for use in two circumstances. The first is when
 traversing a multidimensional array: you can test if an element is itself
 an array or not.  The second is inside the body of a user-defined function
-(not discussed yet; @pxref{User-defined}), to test if a paramater is an
+(not discussed yet; @pxref{User-defined}), to test if a parameter is an
 array or not.
 
 Note, however, that using @code{isarray()} at the global level to test 
@@ -17769,6 +18968,7 @@ will end up turning it into a scalar.
 @subsection String-Translation Functions
 @cindex @command{gawk}, string-translation functions
 @cindex functions, string-translation
+@cindex string-translation functions
 @cindex internationalization
 @cindex @command{awk} programs, internationalizing
 
@@ -17779,9 +18979,10 @@ The descriptions here are purposely brief.
 for the full story.
 Optional parameters are enclosed in square brackets ([ ]):
 
-@table @code
-@cindex @code{bindtextdomain()} function (@command{gawk})
-@item bindtextdomain(@var{directory} @r{[}, @var{domain}@r{]})
+@table @asis
+@cindexgawkfunc{bindtextdomain}
+@cindex set directory of message catalogs
+@item @code{bindtextdomain(@var{directory}} [@code{,} @var{domain}]@code{)}
 Set the directory in which
 @command{gawk} will look for message translation files, in case they
 will not or cannot be placed in the ``standard'' locations
@@ -17793,15 +18994,16 @@ If @var{directory} is the null string (@code{""}), then
 @code{bindtextdomain()} returns the current binding for the
 given @var{domain}.
 
-@cindex @code{dcgettext()} function (@command{gawk})
-@item dcgettext(@var{string} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcgettext}
+@cindex translate string
+@item @code{dcgettext(@var{string}} [@code{,} @var{domain} [@code{,} @var{category}] ]@code{)}
 Return the translation of @var{string} in
 text domain @var{domain} for locale category @var{category}.
 The default value for @var{domain} is the current value of @code{TEXTDOMAIN}.
 The default value for @var{category} is @code{"LC_MESSAGES"}.
 
-@cindex @code{dcngettext()} function (@command{gawk})
-@item dcngettext(@var{string1}, @var{string2}, @var{number} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcngettext}
+@item @code{dcngettext(@var{string1}, @var{string2}, @var{number}} [@code{,} @var{domain} [@code{,} @var{category}] ]@code{)}
 Return the plural form used for @var{number} of the
 translation of @var{string1} and @var{string2} in text domain
 @var{domain} for locale category @var{category}. @var{string1} is the
@@ -17817,7 +19019,7 @@ The default value for @var{category} is @code{"LC_MESSAGES"}.
 @section User-Defined Functions
 
 @c STARTOFRANGE udfunc
-@cindex user-defined, functions
+@cindex user-defined functions
 @c STARTOFRANGE funcud
 @cindex functions, user-defined
 Complicated @command{awk} programs can often be simplified by defining
@@ -17849,12 +19051,12 @@ entire program before starting to execute any of it.
 
 The definition of a function named @var{name} looks like this:
 
-@example
-function @var{name}(@r{[}@var{parameter-list}@r{]})
-@{
+@display
+@code{function} @var{name}@code{(}[@var{parameter-list}]@code{)}
+@code{@{}
      @var{body-of-function}
-@}
-@end example
+@code{@}}
+@end display
 
 @cindex names, functions
 @cindex functions, names of
@@ -17869,14 +19071,20 @@ used as a variable, array, or function.
 @var{parameter-list} is an optional list of the function's arguments and local
 variable names, separated by commas.  When the function is called,
 the argument names are used to hold the argument values given in
-the call.  The local variables are initialized to the empty string.
+the call.
+
 A function cannot have two parameters with the same name, nor may it
 have a parameter with the same name as the function itself.
+In addition, according to the POSIX standard, function parameters
+cannot have the same name as one of the special built-in variables
+(@pxref{Built-in Variables}).  Not all versions of @command{awk} enforce
+this restriction.)
 
-In addition, according to the POSIX standard, function parameters cannot have the same
-name as one of the special built-in variables
-(@pxref{Built-in Variables}.  Not all versions of @command{awk}
-enforce this restriction.
+Local variables act like the empty string if referenced where a string
+value is required, and like zero if referenced where a numeric value
+is required. This is the same as regular variables that have never been
+assigned a value.  (There is more to understand about local variables;
+@pxref{Dynamic Typing}.)
 
 The @var{body-of-function} consists of @command{awk} statements.  It is the
 most important part of the definition, because it says what the function
@@ -17903,6 +19111,7 @@ conventional to place some extra space between the arguments and
 the local variables, in order to document how your function is supposed to be used.
 
 @cindex variables, shadowing
+@cindex shadowing of variable values
 During execution of the function body, the arguments and local variable
 values hide, or @dfn{shadow}, any variables of the same names used in the
 rest of the program.  The shadowed variables are not accessible in the
@@ -17923,7 +19132,7 @@ function.  When this happens, we say the function is @dfn{recursive}.
 The act of a function calling itself is called @dfn{recursion}.
 
 All the built-in functions return a value to their caller.
-User-defined functions can do also, using the @code{return} statement,
+User-defined functions can do so also, using the @code{return} statement,
 which is described in detail in @ref{Return Statement}.
 Many of the subsequent examples in this @value{SECTION} use
 the @code{return} statement.
@@ -17961,6 +19170,7 @@ keyword @code{function} when defining a function.
 
 @node Function Example
 @subsection Function Definition Examples
+@cindex function definition example
 
 Here is an example of a user-defined function, called @code{myprint()}, that
 takes a number and prints it in a specific format:
@@ -18015,7 +19225,8 @@ Instead of having
 to repeat this loop everywhere that you need to clear out
 an array, your program can just call @code{delarray}.
 (This guarantees portability.  The use of @samp{delete @var{array}} to delete
-the contents of an entire array is a nonstandard extension.)
+the contents of an entire array is a recent@footnote{Late in 2012.}
+addition to the POSIX standard.)
 
 The following is an example of a recursive function.  It takes a string
 as an input parameter and returns the string in backwards order.
@@ -18058,7 +19269,7 @@ to create an @command{awk} version of @code{ctime()}:
 
 function ctime(ts,    format)
 @{
-    format = "%a %b %e %H:%M:%S %Z %Y"
+    format = PROCINFO["strftime"]
     if (ts == 0)
         ts = systime()       # use current time as default
     return strftime(format, ts)
@@ -18071,7 +19282,10 @@ function ctime(ts,    format)
 @subsection Calling User-Defined Functions
 
 @c STARTOFRANGE fudc
-This section describes how to call a user-defined function.
+@cindex functions, user-defined, calling
+@dfn{Calling a function} means causing the function to run and do its job.
+A function call is an expression and its value is the value returned by
+the function.
 
 @menu
 * Calling A Function::          Don't use spaces.
@@ -18082,11 +19296,6 @@ This section describes how to call a user-defined function.
 @node Calling A Function
 @subsubsection Writing A Function Call
 
-@cindex functions, user-defined, calling
-@dfn{Calling a function} means causing the function to run and do its job.
-A function call is an expression and its value is the value returned by
-the function.
-
 A function call consists of the function name followed by the arguments
 in parentheses.  @command{awk} expressions are what you write in the
 call for the arguments.  Each time the call is executed, these
@@ -18110,9 +19319,10 @@ an error.
 @node Variable Scope
 @subsubsection Controlling Variable Scope
 
-@cindex local variables
-@cindex variables, local
-There is no way to make a variable local to a @code{@{ @dots{} @}} block in
+@cindex local variables, in a function
+@cindex variables, local to a function
+Unlike many languages,
+there is no way to make a variable local to a @code{@{} @dots{} @code{@}} block in
 @command{awk}, but you can make a variable local to a function. It is
 good practice to do so whenever a variable is needed only in that
 function.
@@ -18374,14 +19584,14 @@ This statement returns control to the calling part of the @command{awk} program.
 can also be used to return a value for use in the rest of the @command{awk}
 program.  It looks like this:
 
-@example
-return @r{[}@var{expression}@r{]}
-@end example
+@display
+@code{return} [@var{expression}]
+@end display
 
 The @var{expression} part is optional.
 Due most likely to an oversight, POSIX does not define what the return
 value is if you omit the @var{expression}.  Technically speaking, this
-make the returned value undefined, and therefore, unpredictable.
+makes the returned value undefined, and therefore, unpredictable.
 In practice, though, all versions of @command{awk} simply return the
 null string, which acts like zero if used in a numeric context.
 
@@ -18484,9 +19694,9 @@ BEGIN @{
 @end example
 
 In this example, the first call to @code{foo()} generates
-a fatal error, so @command{gawk} will not report the second
-error. If you comment out that call, though, then @command{gawk}
-will report the second error.
+a fatal error, so @command{awk} will not report the second
+error. If you comment out that call, though, then @command{awk}
+does report the second error.
 
 Usually, such things aren't a big issue, but it's worth
 being aware of them.
@@ -18556,7 +19766,7 @@ character:
 
 @example
 the_func = "sum"
-result = @@the_func()   # calls the `sum' function
+result = @@the_func()   # calls the sum() function
 @end example
 
 Here is a full program that processes the previously shown data,
@@ -18677,8 +19887,9 @@ We can do something similar using @command{gawk}, like this:
 @ignore
 @c file eg/lib/quicksort.awk
 #
-# Arnold Robbins, arnold@skeeve.com, Public Domain
+# Arnold Robbins, arnold@@skeeve.com, Public Domain
 # January 2009
+
 @c endfile
 
 @end ignore
@@ -18751,7 +19962,7 @@ or equal to), which yields data sorted in descending order.
 
 Next comes a sorting function.  It is parameterized with the starting and
 ending field numbers and the comparison function. It builds an array with
-the data and calls @code{quicksort} appropriately, and then formats the
+the data and calls @code{quicksort()} appropriately, and then formats the
 results as a single string:
 
 @example
@@ -18799,7 +20010,7 @@ function rsort(first, last)
 @c endfile
 @end example
 
-Here is an extended version of the data file:
+Here is an extended version of the @value{DF}:
 
 @example
 @c file eg/data/class_data2
@@ -18850,21 +20061,80 @@ for (i = 1; i <= n; i++)
 @noindent
 @code{gawk} will look up the actual function to call only once.
 
+@node Functions Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+@command{awk} provides built-in functions and lets you define your own
+functions.
+
+@item
+POSIX @command{awk} provides three kinds of built-in functions: numeric,
+string, and I/O.  @command{gawk} provides functions that work with values
+representing time, do bit manipulation, sort arrays, and internationalize
+and localize programs.  @command{gawk} also provides several extensions to
+some of standard functions, typically in the form of additional arguments.
+
+@item
+Functions accept zero or more arguments and return a value.  The
+expressions that provide the argument values are completely evaluated
+before the function is called. Order of evaluation is not defined.
+The return value can be ignored.
+
+@item
+The handling of backslash in @code{sub()} and @code{gsub()} is not simple.
+It is more straightforward in @command{gawk}'s @code{gensub()} function,
+but that function still requires care in its use.
+
+@item
+User-defined functions provide important capabilities but come with
+some syntactic inelegancies. In a function call, there cannot be any
+space between the function name and the opening left parenthesis of the
+argument list.  Also, there is no provision for local variables, so the
+convention is to add extra parameters, and to separate them visually
+from the real parameters by extra whitespace.
+
+@item
+User-defined functions may call other user-defined (and built-in)
+functions and may call themselves recursively. Function parameters
+``hide'' any global variables of the same names.
+
+@item
+Scalar values are passed to user-defined functions by value. Array
+parameters are passed by reference; any changes made by the function to
+array parameters are thus visible after the function has returned.
+
+@item
+Use the @code{return} statement to return from a user-defined function.
+An optional expression becomes the function's return value.  Only scalar
+values may be returned by a function.
+
+@item
+If a variable that has never been used is passed to a user-defined
+function, how that function treats the variable can set its nature:
+either scalar or array.
+
+@item
+@command{gawk} provides indirect function calls using a special syntax.
+By setting a variable to the name of a user-defined function, you can
+determine at runtime what function will be called at that point in the
+program. This is equivalent to function pointers in C and C++.
+
+@end itemize
+
 @c ENDOFRANGE funcud
 
-@iftex
-@part Part II:@* Problem Solving With @command{awk}
-@end iftex
+@ifnotinfo
+@part @value{PART2}Problem Solving With @command{awk}
+@end ifnotinfo
 
-@ignore
 @ifdocbook
-@part Part II:@* Problem Solving With @command{awk}
-
 Part II shows how to use @command{awk} and @command{gawk} for problem solving.
 There is lots of code here for you to read and learn from.
 It contains the following chapters:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Library Functions}.
 
@@ -18872,7 +20142,6 @@ It contains the following chapters:
 @ref{Sample Programs}.
 @end itemize
 @end ifdocbook
-@end ignore
 
 @node Library Functions
 @chapter A Library of @command{awk} Functions
@@ -18889,6 +20158,8 @@ it allows you to encapsulate algorithms and program tasks in a single
 place.  It simplifies programming, making program development more
 manageable, and making programs more readable.
 
+@cindex Kernighan, Brian
+@cindex Plauger, P.J.@:
 In their seminal 1976 book, @cite{Software Tools},@footnote{Sadly, over 35
 years later, many of the lessons taught by this book have yet to be
 learned by a vast number of practicing programmers.} Brian Kernighan
@@ -18908,7 +20179,6 @@ that their statement is correct, this @value{CHAPTER} and @ref{Sample
 Programs}, provide a good-sized body of code for you to read, and we hope,
 to learn from.
 
-@c 2e: USE TEXINFO-2 FUNCTION DEFINITION STUFF!!!!!!!!!!!!!
 This @value{CHAPTER} presents a library of useful @command{awk} functions.
 Many of the sample programs presented later in this @value{DOCUMENT}
 use these functions.
@@ -18921,9 +20191,11 @@ these example library functions and programs from the Texinfo source
 for this @value{DOCUMENT}.
 (This has already been done as part of the @command{gawk} distribution.)
 
+@ifclear FOR_PRINT
 If you have written one or more useful, general-purpose @command{awk} functions
 and would like to contribute them to the @command{awk} user community, see
 @ref{How To Contribute}, for more information.
+@end ifclear
 
 @cindex portability, example programs
 The programs in this @value{CHAPTER} and in
@@ -18932,7 +20204,7 @@ freely use features that are @command{gawk}-specific.
 Rewriting these programs for different implementations of @command{awk}
 is pretty straightforward.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Diagnostic error messages are sent to @file{/dev/stderr}.
 Use @samp{| "cat 1>&2"} instead of @samp{> "/dev/stderr"} if your system
@@ -18976,6 +20248,8 @@ comparisons use only lowercase letters.
 * Passwd Functions::            Functions for getting user information.
 * Group Functions::             Functions for getting group information.
 * Walking Arrays::              A function to walk arrays of arrays.
+* Library Functions Summary::   Summary of library functions.
+* Library exercises::           Exercises.
 @end menu
 
 @node Library Names
@@ -19018,7 +20292,7 @@ with the user's program.
 @cindex underscore (@code{_}), in names of private variables
 In addition, several of the library functions use a prefix that helps
 indicate what function or set of functions use the variables---for example,
-@code{_pw_byname} in the user database routines
+@code{_pw_byname()} in the user database routines
 (@pxref{Passwd Functions}).
 This convention is recommended, since it even further decreases the
 chance of inadvertent conflict among variable names.  Note that this
@@ -19037,7 +20311,7 @@ The leading capital letter indicates that it is global, while the fact that
 the variable name is not all capital letters indicates that the variable is
 not one of @command{awk}'s built-in variables, such as @code{FS}.
 
-@cindex @code{--dump-variables} option
+@cindex @option{--dump-variables} option, using for library functions
 It is also important that @emph{all} variables in library
 functions that do not need to save state are, in fact, declared
 local.@footnote{@command{gawk}'s @option{--dump-variables} command-line
@@ -19110,11 +20384,12 @@ provides an implementation for other versions of @command{awk}:
 #
 # Arnold Robbins, arnold@@skeeve.com, Public Domain
 # February, 2004
+# Revised June, 2014
 
 @c endfile
 @end ignore
 @c file eg/lib/strtonum.awk
-function mystrtonum(str,        ret, chars, n, i, k, c)
+function mystrtonum(str,        ret, n, i, k, c)
 @{
     if (str ~ /^0[0-7]*$/) @{
         # octal
@@ -19127,7 +20402,7 @@ function mystrtonum(str,        ret, chars, n, i, k, c)
 
             ret = ret * 8 + k
         @}
-    @} else if (str ~ /^0[xX][[:xdigit:]]+/) @{
+    @} else if (str ~ /^0[xX][[:xdigit:]]+$/) @{
         # hexadecimal
         str = substr(str, 3)    # lop off leading 0x
         n = length(str)
@@ -19135,10 +20410,7 @@ function mystrtonum(str,        ret, chars, n, i, k, c)
         for (i = 1; i <= n; i++) @{
             c = substr(str, i, 1)
             c = tolower(c)
-            if ((k = index("0123456789", c)) > 0)
-                k-- # adjust for 1-basing in awk
-            else if ((k = index("abcdef", c)) > 0)
-                k += 9
+            k = index("123456789abcdef", c)
 
             ret = ret * 16 + k
         @}
@@ -19306,7 +20578,7 @@ An @code{END} rule is automatically added
 to the program calling @code{assert()}.  Normally, if a program consists
 of just a @code{BEGIN} rule, the input files and/or standard input are
 not read. However, now that the program has an @code{END} rule, @command{awk}
-attempts to read the input data files or standard input
+attempts to read the input @value{DF}s or standard input
 (@pxref{Using BEGIN/END}),
 most likely causing the program to hang as it waits for input.
 
@@ -19332,9 +20604,9 @@ with an @code{exit} statement.
 The way @code{printf} and @code{sprintf()}
 (@pxref{Printf})
 perform rounding often depends upon the system's C @code{sprintf()}
-subroutine.  On many machines, @code{sprintf()} rounding is ``unbiased,''
-which means it doesn't always round a trailing @samp{.5} up, contrary
-to naive expectations.  In unbiased rounding, @samp{.5} rounds to even,
+subroutine.  On many machines, @code{sprintf()} rounding is @dfn{unbiased},
+which means it doesn't always round a trailing .5 up, contrary
+to naive expectations.  In unbiased rounding, .5 rounds to even,
 rather than always up, so 1.5 rounds to 2 but 4.5 rounds to 4.  This means
 that if you are using a format that does rounding (e.g., @code{"%.0f"}),
 you should check what your system does.  The following function does
@@ -19383,7 +20655,7 @@ function round(x,   ival, aval, fraction)
 @c don't include test harness in the file that gets installed
 
 # test harness
-@{ print $0, round($0) @}
+# @{ print $0, round($0) @}
 @end example
 
 @node Cliff Random Function
@@ -19450,6 +20722,7 @@ reason to build them into the @command{awk} interpreter:
 
 @cindex @code{ord()} user-defined function
 @cindex @code{chr()} user-defined function
+@cindex @code{_ord_init()} user-defined function
 @example
 @c file eg/lib/ord.awk
 # ord.awk --- do ord and chr
@@ -19496,8 +20769,9 @@ function _ord_init(    low, high, i, t)
 @cindex character sets (machine character encodings)
 @cindex ASCII
 @cindex EBCDIC
+@cindex Unicode
 @cindex mark parity
-Some explanation of the numbers used by @code{chr} is worthwhile.
+Some explanation of the numbers used by @code{_ord_init()} is worthwhile.
 The most prominent character set in use today is ASCII.@footnote{This
 is changing; many systems use Unicode, a very large character set
 that includes ASCII as a subset.  On systems with full Unicode support,
@@ -19508,7 +20782,7 @@ Although an
 defines characters that use the values from 0 to 127.@footnote{ASCII
 has been extended in many countries to use the values from 128 to 255
 for country-specific characters.  If your  system uses these extensions,
-you can simplify @code{_ord_init} to loop from 0 to 255.}
+you can simplify @code{_ord_init()} to loop from 0 to 255.}
 In the now distant past,
 at least one minicomputer manufacturer
 @c Pr1me, blech
@@ -19675,7 +20949,7 @@ function getlocaltime(time,    ret, now, i)
     now = systime()
 
     # return date(1)-style output
-    ret = strftime("%a %b %e %H:%M:%S %Z %Y", now)
+    ret = strftime(PROCINFO["strftime"], now)
 
     # clear out target array
     delete time
@@ -19791,7 +21065,7 @@ This tests the result to see if it is empty or not. An equivalent
 test would be @samp{contents == ""}.
 
 @node Data File Management
-@section Data File Management
+@section @value{DDF} Management
 
 @c STARTOFRANGE dataf
 @cindex files, managing
@@ -19800,7 +21074,7 @@ test would be @samp{contents == ""}.
 @c STARTOFRANGE flibdataf
 @cindex functions, library, managing data files
 This @value{SECTION} presents functions that are useful for managing
-command-line data files.
+command-line @value{DF}s.
 
 @menu
 * Filetrans Function::          A function for handling data file transitions.
@@ -19811,7 +21085,7 @@ command-line data files.
 @end menu
 
 @node Filetrans Function
-@subsection Noting Data File Boundaries
+@subsection Noting @value{DDF} Boundaries
 
 @cindex files, managing, data file boundaries
 @cindex files, initialization and cleanup
@@ -19819,8 +21093,8 @@ The @code{BEGIN} and @code{END} rules are each executed exactly once at
 the beginning and end of your @command{awk} program, respectively
 (@pxref{BEGIN/END}).
 We (the @command{gawk} authors) once had a user who mistakenly thought that the
-@code{BEGIN} rule is executed at the beginning of each data file and the
-@code{END} rule is executed at the end of each data file.
+@code{BEGIN} rule is executed at the beginning of each @value{DF} and the
+@code{END} rule is executed at the end of each @value{DF}.
 
 When informed
 that this was not the case, the user requested that we add new special
@@ -19831,7 +21105,7 @@ Adding these special patterns to @command{gawk} wasn't necessary;
 the job can be done cleanly in @command{awk} itself, as illustrated
 by the following library program.
 It arranges to call two user-supplied functions, @code{beginfile()} and
-@code{endfile()}, at the beginning and end of each data file.
+@code{endfile()}, at the beginning and end of each @value{DF}.
 Besides solving the problem in only nine(!) lines of code, it does so
 @emph{portably}; this works with any implementation of @command{awk}:
 
@@ -19862,17 +21136,17 @@ This file must be loaded before the user's ``main'' program, so that the
 rule it supplies is executed first.
 
 This rule relies on @command{awk}'s @code{FILENAME} variable that
-automatically changes for each new data file.  The current file name is
+automatically changes for each new @value{DF}.  The current @value{FN} is
 saved in a private variable, @code{_oldfilename}.  If @code{FILENAME} does
-not equal @code{_oldfilename}, then a new data file is being processed and
+not equal @code{_oldfilename}, then a new @value{DF} is being processed and
 it is necessary to call @code{endfile()} for the old file.  Because
 @code{endfile()} should only be called if a file has been processed, the
 program first checks to make sure that @code{_oldfilename} is not the null
-string.  The program then assigns the current file name to
+string.  The program then assigns the current @value{FN} to
 @code{_oldfilename} and calls @code{beginfile()} for the file.
 Because, like all @command{awk} variables, @code{_oldfilename} is
 initialized to the null string, this rule executes correctly even for the
-first data file.
+first @value{DF}.
 
 The program also supplies an @code{END} rule to do the final processing for
 the last file.  Because this @code{END} rule comes before any @code{END} rules
@@ -19881,7 +21155,7 @@ again the value of multiple @code{BEGIN} and @code{END} rules should be clear.
 
 @cindex @code{beginfile()} user-defined function
 @cindex @code{endfile()} user-defined function
-If the same data file occurs twice in a row on the command line, then
+If the same @value{DF} occurs twice in a row on the command line, then
 @code{endfile()} and @code{beginfile()} are not executed at the end of the
 first pass and at the beginning of the second pass.
 The following version solves the problem:
@@ -20025,16 +21299,18 @@ The @code{rewind()} function also relies on the @code{nextfile} keyword
 (@pxref{Nextfile Statement}).
 
 @node File Checking
-@subsection Checking for Readable Data Files
+@subsection Checking for Readable @value{DDF}s
 
 @cindex troubleshooting, readable data files
 @cindex readable data files@comma{} checking
 @cindex files, skipping
-Normally, if you give @command{awk} a data file that isn't readable,
-it stops with a fatal error.  There are times when you
-might want to just ignore such files and keep going.  You can
-do this by prepending the following program to your @command{awk}
-program:
+Normally, if you give @command{awk} a @value{DF} that isn't readable,
+it stops with a fatal error.  There are times when you might want to
+just ignore such files and keep going.@footnote{The @code{BEGINFILE}
+special pattern (@pxref{BEGINFILE/ENDFILE}) provides an alternative
+mechanism for dealing with files that can't be opened.  However, the
+code here provides a portable solution.} You can do this by prepending
+the following program to your @command{awk} program:
 
 @cindex @code{readable.awk} program
 @example
@@ -20072,22 +21348,22 @@ skips the file (since it's no longer in the list).
 See also @ref{ARGC and ARGV}.
 
 @node Empty Files
-@subsection Checking For Zero-length Files
+@subsection Checking for Zero-length Files
 
 All known @command{awk} implementations silently skip over zero-length files.
 This is a by-product of @command{awk}'s implicit 
 read-a-record-and-match-against-the-rules loop: when @command{awk}
 tries to read a record from an empty file, it immediately receives an
 end of file indication, closes the file, and proceeds on to the next
-command-line data file, @emph{without} executing any user-level
+command-line @value{DF}, @emph{without} executing any user-level
 @command{awk} program code.
 
 Using @command{gawk}'s @code{ARGIND} variable
 (@pxref{Built-in Variables}), it is possible to detect when an empty
-data file has been skipped.  Similar to the library file presented
+@value{DF} has been skipped.  Similar to the library file presented
 in @ref{Filetrans Function}, the following library file calls a function named
 @code{zerofile()} that the user must provide.  The arguments passed are
-the file name and the position in @code{ARGV} where it was found:
+the @value{FN} and the position in @code{ARGV} where it was found:
 
 @cindex @code{zerofile.awk} program
 @example
@@ -20134,56 +21410,16 @@ the end of the command-line arguments.  Note that the test in the
 condition of the @code{for} loop uses the @samp{<=} operator,
 not @samp{<}.
 
-As an exercise, you might consider whether this same problem can
-be solved without relying on @command{gawk}'s @code{ARGIND} variable.
-
-As a second exercise, revise this code to handle the case where
-an intervening value in @code{ARGV} is a variable assignment.
-
-@ignore
-# zerofile2.awk --- same thing, portably
-
-BEGIN @{
-    ARGIND = Argind = 0
-    for (i = 1; i < ARGC; i++)
-        Fnames[ARGV[i]]++
-
-@}
-FNR == 1 @{
-    while (ARGV[ARGIND] != FILENAME)
-        ARGIND++
-    Seen[FILENAME]++
-    if (Seen[FILENAME] == Fnames[FILENAME])
-        do
-            ARGIND++
-        while (ARGV[ARGIND] != FILENAME)
-@}
-ARGIND > Argind + 1 @{
-    for (Argind++; Argind < ARGIND; Argind++)
-        zerofile(ARGV[Argind], Argind)
-@}
-ARGIND != Argind @{
-    Argind = ARGIND
-@}
-END @{
-    if (ARGIND < ARGC - 1)
-        ARGIND = ARGC - 1 
-    if (ARGIND > Argind)
-        for (Argind++; Argind <= ARGIND; Argind++)
-            zerofile(ARGV[Argind], Argind)
-@}
-@end ignore
-
 @node Ignoring Assigns
-@subsection Treating Assignments as File Names
+@subsection Treating Assignments as @value{FFN}s
 
 @cindex assignments as filenames
 @cindex filenames, assignments as
 Occasionally, you might not want @command{awk} to process command-line
 variable assignments
 (@pxref{Assignment Options}).
-In particular, if you have a file name that contain an @samp{=} character,
-@command{awk} treats the file name as an assignment, and does not process it.
+In particular, if you have a @value{FN} that contains an @samp{=} character,
+@command{awk} treats the @value{FN} as an assignment, and does not process it.
 
 Some users have suggested an additional command-line option for @command{gawk}
 to disable command-line assignments.  However, some simple programming with
@@ -20227,7 +21463,7 @@ awk -v No_command_assign=1 -f noassign.awk -f yourprog.awk *
 The function works by looping through the arguments.
 It prepends @samp{./} to
 any argument that matches the form
-of a variable assignment, turning that argument into a file name.
+of a variable assignment, turning that argument into a @value{FN}.
 
 The use of @code{No_command_assign} allows you to disable command-line
 assignments at invocation time, by giving the variable a true value.
@@ -20311,7 +21547,6 @@ application might want to print its own error message.)
 
 @item optopt
 The letter representing the command-line option.
-@c While not usually documented, most versions supply this variable.
 @end table
 
 The following C fragment shows how @code{getopt()} might process command-line
@@ -20362,7 +21597,6 @@ necessary for accessing individual characters
 function was written before @command{gawk} acquired the ability to
 split strings into single characters using @code{""} as the separator.
 We have left it alone, since using @code{substr()} is more portable.}
-@c FIXME: could use split(str, a, "") to do it more easily.
 
 The discussion that follows walks through the code a bit at a time:
 
@@ -20545,7 +21779,7 @@ BEGIN @{
     # test program
     if (_getopt_test) @{
         while ((_go_c = getopt(ARGC, ARGV, "ab:cd")) != -1)
-            printf("c = <%c>, optarg = <%s>\n",
+            printf("c = <%c>, Optarg = <%s>\n",
                                        _go_c, Optarg)
         printf("non-option arguments:\n")
         for (; Optind < ARGC; Optind++)
@@ -20561,32 +21795,31 @@ result of two sample runs of the test program:
 
 @example
 $ @kbd{awk -f getopt.awk -v _getopt_test=1 -- -a -cbARG bax -x}
-@print{} c = <a>, optarg = <>
-@print{} c = <c>, optarg = <>
-@print{} c = <b>, optarg = <ARG>
+@print{} c = <a>, Optarg = <>
+@print{} c = <c>, Optarg = <>
+@print{} c = <b>, Optarg = <ARG>
 @print{} non-option arguments:
 @print{}         ARGV[3] = <bax>
 @print{}         ARGV[4] = <-x>
 
 $ @kbd{awk -f getopt.awk -v _getopt_test=1 -- -a -x -- xyz abc}
-@print{} c = <a>, optarg = <>
+@print{} c = <a>, Optarg = <>
 @error{} x -- invalid option
-@print{} c = <?>, optarg = <>
+@print{} c = <?>, Optarg = <>
 @print{} non-option arguments:
 @print{}         ARGV[4] = <xyz>
 @print{}         ARGV[5] = <abc>
 @end example
 
-In both runs,
-the first @option{--} terminates the arguments to @command{awk}, so that it does
-not try to interpret the @option{-a}, etc., as its own options.
+In both runs, the first @option{--} terminates the arguments to
+@command{awk}, so that it does not try to interpret the @option{-a},
+etc., as its own options.
 
 @quotation NOTE
-After @code{getopt()} is through, it is the responsibility of the user level
-code to
-clear out all the elements of @code{ARGV} from 1 to @code{Optind},
-so that @command{awk} does not try to process the command-line options
-as file names.
+After @code{getopt()} is through, it is the responsibility of the
+user level code to clear out all the elements of @code{ARGV} from 1
+to @code{Optind}, so that @command{awk} does not try to process the
+command-line options as @value{FN}s.
 @end quotation
 
 Several of the sample programs presented in
@@ -20603,7 +21836,7 @@ use @code{getopt()} to process their arguments.
 @c STARTOFRANGE libfudata
 @cindex libraries of @command{awk} functions, user database, reading
 @c STARTOFRANGE flibudata
-@cindex functions, library, user database, reading
+@cindex functions, library, user database@comma{} reading
 @c STARTOFRANGE udatar
 @cindex user database@comma{} reading
 @c STARTOFRANGE dataur
@@ -20648,14 +21881,12 @@ no more entries, it returns @code{NULL}, the null pointer.  When this
 happens, the C program should call @code{endpwent()} to close the database.
 Following is @command{pwcat}, a C program that ``cats'' the password database:
 
-@c Use old style function header for portability to old systems (SunOS, HP/UX).
-
 @example
 @c file eg/lib/pwcat.c
 /*
  * pwcat.c
  *
- * Generate a printable version of the password database
+ * Generate a printable version of the password database.
  */
 @c endfile
 @ignore
@@ -20852,7 +22083,7 @@ from anywhere within a user's program, and the user may have his
 or her
 own way of splitting records and fields.
 
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, testing the field splitting
 The @code{using_fw} variable checks @code{PROCINFO["FS"]}, which
 is @code{"FIELDWIDTHS"} if field splitting is being done with
 @code{FIELDWIDTHS}.  This makes it possible to restore the correct
@@ -20861,7 +22092,7 @@ field-splitting mechanism later.  The test can only be true for
 or on some other @command{awk} implementation.
 
 The code that checks for using @code{FPAT}, using @code{using_fpat}
-and @code{PROCINFO["FS"]} is similar.
+and @code{PROCINFO["FS"]}, is similar.
 
 The main part of the function uses a loop to read database lines, split
 the line into fields, and then store the line into each array as necessary.
@@ -20891,10 +22122,9 @@ function getpwnam(name)
 @end example
 
 @cindex @code{getpwuid()} function (C library)
-Similarly,
-the @code{getpwuid} function takes a user ID number argument. If that
-user number is in the database, it returns the appropriate line. Otherwise, it
-returns the null string:
+Similarly, the @code{getpwuid()} function takes a user ID number
+argument. If that user number is in the database, it returns the
+appropriate line. Otherwise, it returns the null string:
 
 @cindex @code{getpwuid()} user-defined function
 @example
@@ -20971,12 +22201,12 @@ uses these functions.
 @c STARTOFRANGE libfgdata
 @cindex libraries of @command{awk} functions, group database, reading
 @c STARTOFRANGE flibgdata
-@cindex functions, library, group database, reading
+@cindex functions, library, group database@comma{} reading
 @c STARTOFRANGE gdatar
 @cindex group database, reading
 @c STARTOFRANGE datagr
 @cindex database, group, reading
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, and group membership
 @cindex @code{getgrent()} function (C library)
 @cindex @code{getgrent()} user-defined function
 @cindex groups@comma{} information about
@@ -21002,7 +22232,7 @@ is as follows:
 /*
  * grcat.c
  *
- * Generate a printable version of the group database
+ * Generate a printable version of the group database.
  */
 @c endfile
 @ignore
@@ -21089,7 +22319,7 @@ it is usually empty or set to @samp{*}.
 
 @item Group ID Number
 The group's numeric group ID number;
-this number must be unique within the file.
+the association of name to number must be unique within the file.
 (On some systems it's a C @code{long}, and not an @code{int}.  Thus
 we cast it to @code{long} for all cases.)
 
@@ -21219,16 +22449,16 @@ database for the same group.  This is common when a group has a large number
 of members.  A pair of such entries might look like the following:
 
 @example
-tvpeople:*:101:johnny,jay,arsenio
+tvpeople:*:101:johny,jay,arsenio
 tvpeople:*:101:david,conan,tom,joan
 @end example
 
 For this reason, @code{_gr_init()} looks to see if a group name or
 group ID number is already seen.  If it is, then the user names are
-simply concatenated onto the previous list of users.  (There is actually a
+simply concatenated onto the previous list of users.@footnote{There is actually a
 subtle problem with the code just presented.  Suppose that
 the first time there were no names. This code adds the names with
-a leading comma. It also doesn't check that there is a @code{$4}.)
+a leading comma. It also doesn't check that there is a @code{$4}.}
 
 Finally, @code{_gr_init()} closes the pipeline to @command{grcat}, restores
 @code{FS} (and @code{FIELDWIDTHS} or @code{FPAT} if necessary), @code{RS}, and @code{$0},
@@ -21388,24 +22618,121 @@ $ @kbd{gawk -f walk_array.awk}
 @print{} a[3] = 3
 @end example
 
-Walking an array and processing each element is a general-purpose
-operation.  You might want to consider generalizing the @code{walk_array()}
-function by adding an additional parameter named @code{process}.
-
-Then, inside the loop, instead of simply printing the array element's
-index and value, use the indirect function call syntax
-(@pxref{Indirect Calls}) on @code{process}, passing it the index
-and the value.
-
-When calling @code{walk_array()}, you would pass the name of a user-defined
-function that expects to receive and index and a value, and then processes
-the element.
-
-
 @c ENDOFRANGE libfgdata
 @c ENDOFRANGE flibgdata
 @c ENDOFRANGE gdatar
 @c ENDOFRANGE libf
+
+@node Library Functions Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Reading programs is an excellent way to learn Good Programming.
+The functions provided in this @value{CHAPTER} and the next are intended
+to serve that purpose.
+
+@item
+When writing general-purpose library functions, put some thought into how
+to name any global variables so that they won't conflict with variables
+from a user's program.
+
+@item
+The functions presented here fit into the following categories:
+
+@c nested list
+@table @asis
+@item General problems
+Number to string conversion, assertions, rounding, random number
+generation, converting characters to numbers, joining strings, getting
+easily usable time-of-day information, and reading a whole file in
+one shot.
+
+@item Managing @value{DF}s
+Noting @value{DF} boundaries, rereading the current file, checking for
+readable files, checking for zero-length files, and treating assignments
+as @value{FN}s.
+
+@item Processing command-line options
+An @command{awk} version of the standard C @code{getopt()} function.
+
+@item Reading the user and group databases
+Two sets of routines that parallel the C library versions.
+
+@item Traversing arrays of arrays
+A simple function to traverse an array of arrays to any depth.
+@end table
+@c end nested list
+
+@end itemize
+
+@node Library exercises
+@section Exercises
+
+@enumerate
+@item
+In @ref{Empty Files}, we presented the @file{zerofile.awk} program,
+which made use of @command{gawk}'s @code{ARGIND} variable.  Can this
+problem be solved without relying on @code{ARGIND}?  If so, how?
+
+@ignore
+# zerofile2.awk --- same thing, portably
+
+BEGIN @{
+    ARGIND = Argind = 0
+    for (i = 1; i < ARGC; i++)
+        Fnames[ARGV[i]]++
+
+@}
+FNR == 1 @{
+    while (ARGV[ARGIND] != FILENAME)
+        ARGIND++
+    Seen[FILENAME]++
+    if (Seen[FILENAME] == Fnames[FILENAME])
+        do
+            ARGIND++
+        while (ARGV[ARGIND] != FILENAME)
+@}
+ARGIND > Argind + 1 @{
+    for (Argind++; Argind < ARGIND; Argind++)
+        zerofile(ARGV[Argind], Argind)
+@}
+ARGIND != Argind @{
+    Argind = ARGIND
+@}
+END @{
+    if (ARGIND < ARGC - 1)
+        ARGIND = ARGC - 1 
+    if (ARGIND > Argind)
+        for (Argind++; Argind <= ARGIND; Argind++)
+            zerofile(ARGV[Argind], Argind)
+@}
+@end ignore
+
+@item
+As a related challenge, revise that code to handle the case where
+an intervening value in @code{ARGV} is a variable assignment.
+
+@item
+@ref{Walking Arrays}, presented a function that walked a multidimensional
+array to print it out.  However, walking an array and processing
+each element is a general-purpose operation.  Generalize the
+@code{walk_array()} function by adding an additional parameter named
+@code{process}.
+
+Then, inside the loop, instead of printing the array element's index and
+value, use the indirect function call syntax (@pxref{Indirect Calls})
+on @code{process}, passing it the index and the value.
+
+When calling @code{walk_array()}, you would pass the name of a
+user-defined function that expects to receive an index and a value,
+and then processes the element.
+
+Test your new version by printing the array; you should end up with
+output identical to that of the original version.
+
+@end enumerate
+
 @c ENDOFRANGE flib
 @c ENDOFRANGE fudlib
 @c ENDOFRANGE datagr
@@ -21415,11 +22742,13 @@ the element.
 @c STARTOFRANGE awkpex
 @cindex @command{awk} programs, examples of
 
+@c FULLXREF ON
 @ref{Library Functions},
 presents the idea that reading programs in a language contributes to
 learning that language.  This @value{CHAPTER} continues that theme,
 presenting a potpourri of @command{awk} programs for your reading
 enjoyment.
+@c FULLXREF OFF
 @ifnotinfo
 There are three sections.
 The first describes how to run the programs presented
@@ -21446,6 +22775,8 @@ Many of these programs use library functions presented in
 * Running Examples::            How to run these examples.
 * Clones::                      Clones of common utilities.
 * Miscellaneous Programs::      Some interesting @command{awk} programs.
+* Programs Summary::            Summary of programs.
+* Programs Exercises::          Exercises.
 @end menu
 
 @node Running Examples
@@ -21460,7 +22791,7 @@ awk -f @var{program} -- @var{options} @var{files}
 @noindent
 Here, @var{program} is the name of the @command{awk} program (such as
 @file{cut.awk}), @var{options} are any command-line options for the
-program that start with a @samp{-}, and @var{files} are the actual data files.
+program that start with a @samp{-}, and @var{files} are the actual @value{DF}s.
 
 If your system supports the @samp{#!} executable interpreter mechanism
 (@pxref{Executable Scripts}),
@@ -21598,13 +22929,7 @@ function usage(    e1, e2)
 
 @noindent
 The variables @code{e1} and @code{e2} are used so that the function
-fits nicely on the
-@ifnotinfo
-page.
-@end ifnotinfo
-@ifnottex
-screen.
-@end ifnottex
+fits nicely on the @value{PAGE}.
 
 @cindex @code{BEGIN} pattern, running @command{awk} programs and
 @cindex @code{FS} variable, running @command{awk} programs and
@@ -21634,7 +22959,7 @@ BEGIN    \
             OFS = ""
         @} else if (c == "d") @{
             if (length(Optarg) > 1) @{
-                printf("Using first character of %s" \
+                printf("cut: using first character of %s" \
                        " for delimiter\n", Optarg) > "/dev/stderr"
                 Optarg = substr(Optarg, 1, 1)
             @}
@@ -21643,7 +22968,7 @@ BEGIN    \
             if (FS == " ")    # defeat awk semantics
                 FS = "[ ]"
         @} else if (c == "s")
-            suppress++
+            suppress = 1
         else
             usage()
     @}
@@ -21665,7 +22990,7 @@ spaces.  Also remember that after @code{getopt()} is through
 we have to
 clear out all the elements of @code{ARGV} from 1 to @code{Optind},
 so that @command{awk} does not try to process the command-line options
-as file names.
+as @value{FN}s.
 
 After dealing with the command-line options, the program verifies that the
 options make sense.  Only one or the other of @option{-c} and @option{-f}
@@ -21715,7 +23040,7 @@ function set_fieldlist(        n, m, i, j, k, f, g)
             m = split(f[i], g, "-")
 @group
             if (m != 2 || g[1] >= g[2]) @{
-                printf("bad field list: %s\n",
+                printf("cut: bad field list: %s\n",
                                   f[i]) > "/dev/stderr"
                 exit 1
             @}
@@ -21752,7 +23077,7 @@ complete field list, including filler fields:
 
 @example
 @c file eg/prog/cut.awk
-function set_charlist(    field, i, j, f, g, t,
+function set_charlist(    field, i, j, f, g, n, m, t,
                           filler, last, len)
 @{
     field = 1   # count total fields
@@ -21762,7 +23087,7 @@ function set_charlist(    field, i, j, f, g, t,
         if (index(f[i], "-") != 0) @{ # range
             m = split(f[i], g, "-")
             if (m != 2 || g[1] >= g[2]) @{
-                printf("bad character list: %s\n",
+                printf("cut: bad character list: %s\n",
                                f[i]) > "/dev/stderr"
                 exit 1
             @}
@@ -21838,7 +23163,6 @@ of picking the input line apart by characters.
 @c ENDOFRANGE ficut
 @c ENDOFRANGE colcut
 
-@c Exercise: Rewrite using split with "".
 
 @node Egrep Program
 @subsection Searching for Regular Expressions in Files
@@ -21849,20 +23173,21 @@ of picking the input line apart by characters.
 @cindex searching, files for regular expressions
 @c STARTOFRANGE fsregexp
 @cindex files, searching for regular expressions
+@c STARTOFRANGE egrep
 @cindex @command{egrep} utility
 The @command{egrep} utility searches files for patterns.  It uses regular
 expressions that are almost identical to those available in @command{awk}
 (@pxref{Regexp}).
 You invoke it as follows:
 
-@example
-egrep @r{[} @var{options} @r{]} '@var{pattern}' @var{files} @dots{}
-@end example
+@display
+@command{egrep} [@var{options}] @code{'@var{pattern}'} @var{files} @dots{}
+@end display
 
 The @var{pattern} is a regular expression.  In typical usage, the regular
 expression is quoted to prevent the shell from expanding any of the
-special characters as file name wildcards.  Normally, @command{egrep}
-prints the lines that matched.  If multiple file names are provided on
+special characters as @value{FN} wildcards.  Normally, @command{egrep}
+prints the lines that matched.  If multiple @value{FN}s are provided on
 the command line, each output line is preceded by the name of the file
 and a colon.
 
@@ -21953,7 +23278,7 @@ pattern is supplied with @option{-e}, the first nonoption on the
 command line is used.  The @command{awk} command-line arguments up to @code{ARGV[Optind]}
 are cleared, so that @command{awk} won't try to process them as files.  If no
 files are specified, the standard input is used, and if multiple files are
-specified, we make sure to note this so that the file names can precede the
+specified, we make sure to note this so that the @value{FN}s can precede the
 matched lines in the output:
 
 @example
@@ -21987,8 +23312,6 @@ if a match happens, we output the translated line, not the original.}
 The rule is
 commented out since it is not necessary with @command{gawk}:
 
-@c Exercise: Fix this, w/array and new line as key to original line
-
 @example
 @c file eg/prog/egrep.awk
 #@{
@@ -22039,6 +23362,11 @@ function endfile(file)
 @c endfile
 @end example
 
+The @code{BEGINFILE} and @code{ENDFILE} special patterns
+(@pxref{BEGINFILE/ENDFILE}) could be used, but then the program would be
+@command{gawk}-specific. Additionally, this example was written before
+@command{gawk} acquired @code{BEGINFILE} and @code{ENDFILE}.
+
 The following rule does most of the work of matching lines. The variable
 @code{matches} is true if the line matched the pattern. If the user
 wants lines that did not match, the sense of @code{matches} is inverted
@@ -22051,9 +23379,9 @@ A number of additional tests are made, but they are only done if we
 are not counting lines.  First, if the user only wants exit status
 (@code{no_print} is true), then it is enough to know that @emph{one}
 line in this file matched, and we can skip on to the next file with
-@code{nextfile}.  Similarly, if we are only printing file names, we can
-print the file name, and then skip to the next file with @code{nextfile}.
-Finally, each line is printed, with a leading file name and colon
+@code{nextfile}.  Similarly, if we are only printing @value{FN}s, we can
+print the @value{FN}, and then skip to the next file with @code{nextfile}.
+Finally, each line is printed, with a leading @value{FN} and colon
 if necessary:
 
 @cindex @code{!} (exclamation point), @code{!} operator
@@ -22095,9 +23423,7 @@ there are no matches, the exit status is one; otherwise it is zero:
 @c file eg/prog/egrep.awk
 END    \
 @{
-    if (total == 0)
-        exit 1
-    exit 0
+    exit (total == 0)
 @}
 @c endfile
 @end example
@@ -22134,12 +23460,14 @@ or not.
 @c ENDOFRANGE regexps
 @c ENDOFRANGE sfregexp
 @c ENDOFRANGE fsregexp
+@c ENDOFRANGE egrep
 
 @node Id Program
 @subsection Printing out User Information
 
 @cindex printing, user information
 @cindex users, information about, printing
+@c STARTOFRANGE id
 @cindex @command{id} utility
 The @command{id} utility lists a user's real and effective user ID numbers,
 real and effective group ID numbers, and the user's group set, if any.
@@ -22149,10 +23477,10 @@ corresponding user and group names.  The output might look like this:
 
 @example
 $ @kbd{id}
-@print{} uid=500(arnold) gid=500(arnold) groups=6(disk),7(lp),19(floppy)
+@print{} uid=1000(arnold) gid=1000(arnold) groups=1000(arnold),4(adm),7(lp),27(sudo)
 @end example
 
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, and user and group ID numbers
 This information is part of what is provided by @command{gawk}'s
 @code{PROCINFO} array (@pxref{Built-in Variables}).
 However, the @command{id} utility provides a more palatable output than just
@@ -22185,6 +23513,7 @@ numbers:
 # Arnold Robbins, arnold@@skeeve.com, Public Domain
 # May 1993
 # Revised February 1996
+# Revised May 2014
 
 @c endfile
 @end ignore
@@ -22204,34 +23533,26 @@ BEGIN    \
 
     printf("uid=%d", uid)
     pw = getpwuid(uid)
-    if (pw != "") @{
-        split(pw, a, ":")
-        printf("(%s)", a[1])
-    @}
+    if (pw != "")
+        pr_first_field(pw)
 
     if (euid != uid) @{
         printf(" euid=%d", euid)
         pw = getpwuid(euid)
-        if (pw != "") @{
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        @}
+        if (pw != "")
+            pr_first_field(pw)
     @}
 
     printf(" gid=%d", gid)
     pw = getgrgid(gid)
-    if (pw != "") @{
-        split(pw, a, ":")
-        printf("(%s)", a[1])
-    @}
+    if (pw != "")
+        pr_first_field(pw)
 
     if (egid != gid) @{
         printf(" egid=%d", egid)
         pw = getgrgid(egid)
-        if (pw != "") @{
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        @}
+        if (pw != "")
+            pr_first_field(pw)
     @}
 
     for (i = 1; ("group" i) in PROCINFO; i++) @{
@@ -22240,20 +23561,23 @@ BEGIN    \
         group = PROCINFO["group" i]
         printf("%d", group)
         pw = getgrgid(group)
-        if (pw != "") @{
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        @}
+        if (pw != "")
+            pr_first_field(pw)
         if (("group" (i+1)) in PROCINFO)
             printf(",")
     @}
 
     print ""
 @}
+
+function pr_first_field(str,  a)
+@{
+    split(str, a, ":")
+    printf("(%s)", a[1])
+@}
 @c endfile
 @end example
 
-@cindex @code{in} operator
 The test in the @code{for} loop is worth noting.
 Any supplementary groups in the @code{PROCINFO} array have the
 indices @code{"group1"} through @code{"group@var{N}"} for some
@@ -22263,19 +23587,18 @@ there are.
 
 This loop works by starting at one, concatenating the value with
 @code{"group"}, and then using @code{in} to see if that value is
-in the array.  Eventually, @code{i} is incremented past
+in the array (@pxref{Reference to Elements}).  Eventually, @code{i} is incremented past
 the last group in the array and the loop exits.
 
 The loop is also correct if there are @emph{no} supplementary
 groups; then the condition is false the first time it's
 tested, and the loop body never executes.
 
-@c exercise!!!
-@ignore
-The POSIX version of @command{id} takes arguments that control which
-information is printed.  Modify this version to accept the same
-arguments and perform in the same way.
-@end ignore
+The @code{pr_first_field()} function simply isolates out some
+code that is used repeatedly, making the whole program
+slightly shorter and cleaner.
+
+@c ENDOFRANGE id
 
 @node Split Program
 @subsection Splitting a Large File into Pieces
@@ -22284,15 +23607,16 @@ arguments and perform in the same way.
 
 @c STARTOFRANGE filspl
 @cindex files, splitting
+@c STARTOFRANGE split
 @cindex @code{split} utility
 The @command{split} program splits large text files into smaller pieces.
 Usage is as follows:@footnote{This is the traditional usage. The
 POSIX usage is different, but not relevant for what the program
 aims to demonstrate.}
 
-@example
-split @r{[}-@var{count}@r{]} file @r{[} @var{prefix} @r{]}
-@end example
+@display
+@command{split} [@code{-@var{count}}] [@var{file}] [@var{prefix}]
+@end display
 
 By default,
 the output files are named @file{xaa}, @file{xab}, and so on. Each file has
@@ -22301,7 +23625,7 @@ number of lines in each file, supply a number on the command line
 preceded with a minus; e.g., @samp{-500} for files with 500 lines in them
 instead of 1000.  To change the name of the output files to something like
 @file{myfileaa}, @file{myfileab}, and so on, supply an additional
-argument that specifies the file name prefix.
+argument that specifies the @value{FN} prefix.
 
 Here is a version of @command{split} in @command{awk}. It uses the
 @code{ord()} and @code{chr()} functions presented in
@@ -22311,8 +23635,8 @@ The program first sets its defaults, and then tests to make sure there are
 not too many arguments.  It then looks at each argument in turn.  The
 first argument could be a minus sign followed by a number. If it is, this happens
 to look like a negative number, so it is made positive, and that is the
-count of lines.  The data file name is skipped over and the final argument
-is used as the prefix for the output file names:
+count of lines.  The @value{DF} name is skipped over and the final argument
+is used as the prefix for the output @value{FN}s:
 
 @cindex @code{split.awk} program
 @example
@@ -22326,11 +23650,12 @@ is used as the prefix for the output file names:
 #
 # Arnold Robbins, arnold@@skeeve.com, Public Domain
 # May 1993
+# Revised slightly, May 2014
 
 @c endfile
 @end ignore
 @c file eg/prog/split.awk
-# usage: split [-num] [file] [outname]
+# usage: split [-count] [file] [outname]
 
 BEGIN @{
     outfile = "x"    # default
@@ -22339,7 +23664,7 @@ BEGIN @{
         usage()
 
     i = 1
-    if (ARGV[i] ~ /^-[[:digit:]]+$/) @{
+    if (i in ARGV && ARGV[i] ~ /^-[[:digit:]]+$/) @{
         count = -ARGV[i]
         ARGV[i] = ""
         i++
@@ -22361,7 +23686,7 @@ BEGIN @{
 The next rule does most of the work. @code{tcount} (temporary count) tracks
 how many lines have been printed to the output file so far. If it is greater
 than @code{count}, it is time to close the current file and start a new one.
-@code{s1} and @code{s2} track the current suffixes for the file name. If
+@code{s1} and @code{s2} track the current suffixes for the @value{FN}. If
 they are both @samp{z}, the file is just too big.  Otherwise, @code{s1}
 moves to the next letter in the alphabet and @code{s2} starts over again at
 @samp{a}:
@@ -22393,8 +23718,6 @@ moves to the next letter in the alphabet and @code{s2} starts over again at
 @c endfile
 @end example
 
-@c Exercise: do this with just awk builtin functions, index("abc..."), substr, etc.
-
 @noindent
 The @code{usage()} function simply prints an error message and exits:
 
@@ -22411,36 +23734,30 @@ function usage(   e)
 
 @noindent
 The variable @code{e} is used so that the function
-fits nicely on the
-@ifinfo
-screen.
-@end ifinfo
-@ifnotinfo
-page.
-@end ifnotinfo
+fits nicely on the @value{PAGE}.
 
 This program is a bit sloppy; it relies on @command{awk} to automatically close the last file
 instead of doing it in an @code{END} rule.
 It also assumes that letters are contiguous in the character set,
 which isn't true for EBCDIC systems.
 
-@c Exercise: Fix these problems.
-@c BFD...
 @c ENDOFRANGE filspl
+@c ENDOFRANGE split
 
 @node Tee Program
 @subsection Duplicating Output into Multiple Files
 
 @cindex files, multiple@comma{} duplicating output into
 @cindex output, duplicating into files
+@c STARTOFRANGE tee
 @cindex @code{tee} utility
 The @code{tee} program is known as a ``pipe fitting.''  @code{tee} copies
 its standard input to its standard output and also duplicates it to the
 files named on the command line.  Its usage is as follows:
 
-@example
-tee @r{[}-a@r{]} file @dots{}
-@end example
+@display
+@command{tee} [@option{-a}] @var{file} @dots{}
+@end display
 
 The @option{-a} option tells @code{tee} to append to the named files, instead of
 truncating them and starting over.
@@ -22449,13 +23766,13 @@ The @code{BEGIN} rule first makes a copy of all the command-line arguments
 into an array named @code{copy}.
 @code{ARGV[0]} is not copied, since it is not needed.
 @code{tee} cannot use @code{ARGV} directly, since @command{awk} attempts to
-process each file name in @code{ARGV} as input data.
+process each @value{FN} in @code{ARGV} as input data.
 
 @cindex flag variables
 If the first argument is @option{-a}, then the flag variable
 @code{append} is set to true, and both @code{ARGV[1]} and
 @code{copy[1]} are deleted. If @code{ARGC} is less than two, then no
-file names were supplied and @code{tee} prints a usage message and exits.
+@value{FN}s were supplied and @code{tee} prints a usage message and exits.
 Finally, @command{awk} is forced to read the standard input by setting
 @code{ARGV[1]} to @code{"-"} and @code{ARGC} to two:
 
@@ -22547,6 +23864,7 @@ END    \
 @}
 @c endfile
 @end example
+@c ENDOFRANGE tee
 
 @node Uniq Program
 @subsection Printing Nonduplicated Lines of Text
@@ -22557,15 +23875,16 @@ END    \
 @cindex printing, unduplicated lines of text
 @c STARTOFRANGE tpul
 @cindex text@comma{} printing, unduplicated lines of
+@c STARTOFRANGE uniq
 @cindex @command{uniq} utility
 The @command{uniq} utility reads sorted lines of data on its standard
 input, and by default removes duplicate lines.  In other words, it only
 prints unique lines---hence the name.  @command{uniq} has a number of
 options. The usage is as follows:
 
-@example
-uniq @r{[}-udc @r{[}-@var{n}@r{]]} @r{[}+@var{n}@r{]} @r{[} @var{input file} @r{[} @var{output file} @r{]]}
-@end example
+@display
+@command{uniq} [@option{-udc} [@code{-@var{n}}]] [@code{+@var{n}}] [@var{inputfile} [@var{outputfile}]]
+@end display
 
 The options for @command{uniq} are:
 
@@ -22589,11 +23908,11 @@ by runs of spaces and/or TABs.
 Skip @var{n} characters before comparing lines.  Any fields specified with
 @samp{-@var{n}} are skipped first.
 
-@item @var{input file}
+@item @var{inputfile}
 Data is read from the input file named on the command line, instead of from
 the standard input.
 
-@item @var{output file}
+@item @var{outputfile}
 The generated output is sent to the named output file, instead of to the
 standard output.
 @end table
@@ -22808,6 +24127,7 @@ END @{
 @end example
 @c ENDOFRANGE prunt
 @c ENDOFRANGE tpul
+@c ENDOFRANGE uniq
 
 @node Wc Program
 @subsection Counting Things
@@ -22824,13 +24144,14 @@ END @{
 @cindex characters, counting
 @c STARTOFRANGE lico
 @cindex lines, counting
+@c STARTOFRANGE wc
 @cindex @command{wc} utility
 The @command{wc} (word count) utility counts lines, words, and characters in
 one or more input files. Its usage is as follows:
 
-@example
-wc @r{[}-lwc@r{]} @r{[} @var{files} @dots{} @r{]}
-@end example
+@display
+@command{wc} [@option{-lwc}] [@var{files} @dots{}]
+@end display
 
 If no files are specified on the command line, @command{wc} reads its standard
 input. If there are multiple files, it also prints total counts for all
@@ -22917,7 +24238,7 @@ BEGIN @{
 @end example
 
 The @code{beginfile()} function is simple; it just resets the counts of lines,
-words, and characters to zero, and saves the current file name in
+words, and characters to zero, and saves the current @value{FN} in
 @code{fname}:
 
 @example
@@ -22930,18 +24251,10 @@ function beginfile(file)
 @c endfile
 @end example
 
-The @code{endfile()} function adds the current file's numbers to the running
-totals of lines, words, and characters.@footnote{@command{wc} can't just use the value of
-@code{FNR} in @code{endfile()}. If you examine
-the code in
-@ref{Filetrans Function},
-you will see that
-@code{FNR} has already been reset by the time
-@code{endfile()} is called.}  It then prints out those numbers
-for the file that was just read. It relies on @code{beginfile()} to reset the
-numbers for the following data file:
-@c FIXME: ONE DAY: make the above footnote an exercise,
-@c instead of giving away the answer.
+The @code{endfile()} function adds the current file's numbers to the
+running totals of lines, words, and characters.  It then prints out those
+numbers for the file that was just read. It relies on @code{beginfile()}
+to reset the numbers for the following @value{DF}:
 
 @example
 @c file eg/prog/wc.awk
@@ -23006,6 +24319,7 @@ END @{
 @c ENDOFRANGE lico
 @c ENDOFRANGE woco
 @c ENDOFRANGE chco
+@c ENDOFRANGE wc
 @c ENDOFRANGE posimawk
 
 @node Miscellaneous Programs
@@ -23110,6 +24424,32 @@ word, comparing it to the previous one:
 @i{Nothing cures insomnia like a ringing alarm clock.}
 @author Arnold Robbins
 @end quotation
+@cindex Quanstrom, Erik
+@ignore
+Date: Sat, 15 Feb 2014 16:47:09 -0500
+Subject: Re: 9atom install question
+Message-ID: <l2jcvx6j6mey60xnrkb0hhob.1392500829294@email.android.com>
+From: Erik Quanstrom <quanstro@quanstro.net>
+To: Aharon Robbins <arnold@skeeve.com>
+
+yes.
+
+- erik
+
+Aharon Robbins <arnold@skeeve.com> wrote:
+
+>> sleep is for web developers.
+>
+>Can I quote you, in the gawk manual?
+>
+>Thanks,
+>
+>Arnold
+@end ignore
+@quotation
+@i{Sleep is for web developers.}
+@author Erik Quanstrom
+@end quotation
 
 @c STARTOFRANGE tialarm
 @cindex time, alarm clock example program
@@ -23231,7 +24571,7 @@ is how long to wait before setting off the alarm:
     # how long to sleep for
     naptime = target - current
     if (naptime <= 0) @{
-        print "time is in the past!" > "/dev/stderr"
+        print "alarm: time is in the past!" > "/dev/stderr"
         exit 1
     @}
 @c endfile
@@ -23274,6 +24614,7 @@ seconds are necessary:
 
 @c STARTOFRANGE chtra
 @cindex characters, transliterating
+@c STARTOFRANGE tr
 @cindex @command{tr} utility
 The system @command{tr} utility transliterates characters.  For example, it is
 often used to map uppercase letters into lowercase for further processing:
@@ -23283,19 +24624,18 @@ often used to map uppercase letters into lowercase for further processing:
 @end example
 
 @command{tr} requires two lists of characters.@footnote{On some older
-systems,
-including Solaris,
-@command{tr} may require that the lists be written as
-range expressions enclosed in square brackets (@samp{[a-z]}) and quoted,
-to prevent the shell from attempting a file name expansion.  This is
-not a feature.}  When processing the input, the first character in the
-first list is replaced with the first character in the second list,
-the second character in the first list is replaced with the second
-character in the second list, and so on.  If there are more characters
-in the ``from'' list than in the ``to'' list, the last character of the
-``to'' list is used for the remaining characters in the ``from'' list.
-
-Some time ago,
+systems, including Solaris, the system version of @command{tr} may require
+that the lists be written as range expressions enclosed in square brackets
+(@samp{[a-z]}) and quoted, to prevent the shell from attempting a file
+name expansion.  This is not a feature.}  When processing the input, the
+first character in the first list is replaced with the first character
+in the second list, the second character in the first list is replaced
+with the second character in the second list, and so on.  If there are
+more characters in the ``from'' list than in the ``to'' list, the last
+character of the ``to'' list is used for the remaining characters in the
+``from'' list.
+
+Once upon a time,
 @c early or mid-1989!
 a user proposed that a transliteration function should
 be added to @command{gawk}.
@@ -23313,7 +24653,6 @@ and @code{gsub()} built-in functions
 (@pxref{String Functions}).@footnote{This
 program was written before @command{gawk} acquired the ability to
 split each character in a string into separate array elements.}
-@c Exercise: How might you use this new feature to simplify the program?
 There are two functions.  The first, @code{stranslate()}, takes three
 arguments:
 
@@ -23409,19 +24748,19 @@ BEGIN @{
 While it is possible to do character transliteration in a user-level
 function, it is not necessarily efficient, and we (the @command{gawk}
 authors) started to consider adding a built-in function.  However,
-shortly after writing this program, we learned that the System V Release 4
-@command{awk} had added the @code{toupper()} and @code{tolower()} functions
-(@pxref{String Functions}).
-These functions handle the vast majority of the
-cases where character transliteration is necessary, and so we chose to
-simply add those functions to @command{gawk} as well and then leave well
-enough alone.
+shortly after writing this program, we learned that Brian Kernighan
+had added the @code{toupper()} and @code{tolower()} functions to his
+@command{awk} (@pxref{String Functions}).  These functions handle the
+vast majority of the cases where character transliteration is necessary,
+and so we chose to simply add those functions to @command{gawk} as well
+and then leave well enough alone.
 
 An obvious improvement to this program would be to set up the
 @code{t_ar} array only once, in a @code{BEGIN} rule. However, this
 assumes that the ``from'' and ``to'' lists
 will never change throughout the lifetime of the program.
 @c ENDOFRANGE chtra
+@c ENDOFRANGE tr
 
 @node Labels Program
 @subsection Printing Mailing Labels
@@ -23447,7 +24786,18 @@ The @code{BEGIN} rule simply sets @code{RS} to the empty string, so that
 @command{awk} splits records at blank lines
 (@pxref{Records}).
 It sets @code{MAXLINES} to 100, since 100 is the maximum number
-of lines on the page (20 * 5 = 100).
+of lines on the page
+@iftex
+(@math{20 @cdot 5 = 100}).
+@end iftex
+@ifnottex
+@ifnotdocbook
+(20 * 5 = 100).
+@end ifnotdocbook
+@end ifnottex
+@docbook
+(20 &sdot; 5 = 100). @c
+@end docbook
 
 Most of the work is done in the @code{printpage()} function.
 The label lines are stored sequentially in the @code{line} array.  But they
@@ -23481,6 +24831,7 @@ that there are two blank lines at the top and two blank lines at the bottom.
 The @code{END} rule arranges to flush the final page of labels; there may
 not have been an even multiple of 20 labels in the data:
 
+@c STARTOFRANGE labels
 @cindex @code{labels.awk} program
 @example
 @c file eg/prog/labels.awk
@@ -23548,6 +24899,7 @@ END    \
 @end example
 @c ENDOFRANGE prml
 @c ENDOFRANGE mlprint
+@c ENDOFRANGE labels
 
 @node Word Sorting
 @subsection Generating Word-Usage Counts
@@ -23557,7 +24909,7 @@ END    \
 
 When working with large amounts of text, it can be interesting to know
 how often different words appear.  For example, an author may overuse
-certain words, in which case she might wish to find synonyms to substitute
+certain words, in which case he or she might wish to find synonyms to substitute
 for words that appear too often. This @value{SUBSECTION} develops a
 program for counting words and presenting the frequency information
 in a useful format.
@@ -23587,7 +24939,7 @@ it prints the counts.
 This program has several problems that prevent it from being
 useful on real text files:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @command{awk} language considers upper- and lowercase characters to be
 distinct.  Therefore, ``bartender'' and ``Bartender'' are not treated
@@ -23614,6 +24966,7 @@ to remove punctuation characters.  Finally, we solve the third problem
 by using the system @command{sort} utility to process the output of the
 @command{awk} script.  Here is the new version of the program:
 
+@c STARTOFRANGE wordfreq
 @cindex @code{wordfreq.awk} program
 @example
 @c file eg/prog/wordfreq.awk
@@ -23634,6 +24987,10 @@ END @{
 @}
 @end example
 
+The regexp @samp{/[^[:alnum:]_[:blank:]]/} might have been written
+@samp{/[[:punct:]]/}, but then underscores would also be removed,
+and we want to keep them.
+
 Assuming we have saved this program in a file named @file{wordfreq.awk},
 and that the data is in @file{file1}, the following pipeline:
 
@@ -23675,6 +25032,7 @@ have true pipes at the command-line (or batch-file) level.
 See the general operating system documentation for more information on how
 to use the @command{sort} program.
 @c ENDOFRANGE worus
+@c ENDOFRANGE wordfreq
 
 @node History Sorting
 @subsection Removing Duplicates from Unsorted Text
@@ -23685,7 +25043,7 @@ The @command{uniq} program
 (@pxref{Uniq Program}),
 removes duplicate lines from @emph{sorted} data.
 
-Suppose, however, you need to remove duplicate lines from a data file but
+Suppose, however, you need to remove duplicate lines from a @value{DF} but
 that you want to preserve the order the lines are in.  A good example of
 this might be a shell history file.  The history file keeps a copy of all
 the commands you have entered, and it is not unusual to repeat a command
@@ -23704,6 +25062,7 @@ Each element of @code{lines} is a unique command, and the indices of
 The @code{END} rule simply prints out the lines, in order:
 
 @cindex Rakitzis, Byron
+@c STARTOFRANGE histsort
 @cindex @code{histsort.awk} program
 @example
 @c file eg/prog/histsort.awk
@@ -23743,9 +25102,11 @@ information.  For example, using the following @code{print} statement in the
 print data[lines[i]], lines[i]
 @end example
 
+@noindent
 This works because @code{data[$0]} is incremented each time a line is
 seen.
 @c ENDOFRANGE lidu
+@c ENDOFRANGE histsort
 
 @node Extract Program
 @subsection Extracting Programs from Texinfo Source Files
@@ -23777,7 +25138,8 @@ printed and online documentation.
 @ifnotinfo
 Texinfo is fully documented in the book
 @cite{Texinfo---The GNU Documentation Format},
-available from the Free Software Foundation.
+available from the Free Software Foundation,
+and also available @uref{http://www.gnu.org/software/texinfo/manual/texinfo/, online}.
 @end ifnotinfo
 @ifinfo
 The Texinfo language is described fully, starting with
@@ -23787,7 +25149,7 @@ The Texinfo language is described fully, starting with
 For our purposes, it is enough to know three things about Texinfo input
 files:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The ``at'' symbol (@samp{@@}) is special in Texinfo, much as
 the backslash (@samp{\}) is in C
@@ -23855,6 +25217,7 @@ The first rule handles calling @code{system()}, checking that a command is
 given (@code{NF} is at least three) and also checking that the command
 exits with a zero exit status, signifying OK:
 
+@c STARTOFRANGE extract
 @cindex @code{extract.awk} program
 @example
 @c file eg/prog/extract.awk
@@ -23876,7 +25239,7 @@ BEGIN    @{ IGNORECASE = 1 @}
 /^@@c(omment)?[ \t]+system/    \
 @{
     if (NF < 3) @{
-        e = (FILENAME ":" FNR)
+        e = ("extract: " FILENAME ":" FNR)
         e = (e  ": badly formed `system' line")
         print e > "/dev/stderr"
         next
@@ -23885,7 +25248,7 @@ BEGIN    @{ IGNORECASE = 1 @}
     $2 = ""
     stat = system($0)
     if (stat != 0) @{
-        e = (FILENAME ":" FNR)
+        e = ("extract: " FILENAME ":" FNR)
         e = (e ": warning: system returned " stat)
         print e > "/dev/stderr"
     @}
@@ -23895,16 +25258,10 @@ BEGIN    @{ IGNORECASE = 1 @}
 
 @noindent
 The variable @code{e} is used so that the rule
-fits nicely on the
-@ifnotinfo
-page.
-@end ifnotinfo
-@ifnottex
-screen.
-@end ifnottex
+fits nicely on the @value{PAGE}.
 
 The second rule handles moving data into files.  It verifies that a
-file name is given in the directive.  If the file named is not the
+@value{FN} is given in the directive.  If the file named is not the
 current file, then the current file is closed.  Keeping the current file
 open until a new file is encountered allows the use of the @samp{>}
 redirection for printing the contents, keeping open file management
@@ -23928,12 +25285,11 @@ the array @code{a}, using the @code{split()} function
 The @samp{@@} symbol is used as the separator character.
 Each element of @code{a} that is empty indicates two successive @samp{@@}
 symbols in the original line.  For each two empty elements (@samp{@@@@} in
-the original file), we have to add a single @samp{@@} symbol back
-in.@footnote{This program was written before @command{gawk} had the
-@code{gensub()} function. Consider how you might use it to simplify the code.}
+the original file), we have to add a single @samp{@@} symbol back in.
 
 When the processing of the array is finished, @code{join()} is called with the
-value of @code{SUBSEP}, to rejoin the pieces back into a single
+value of @code{SUBSEP} (@pxref{Multidimensional}),
+to rejoin the pieces back into a single
 line.  That line is then printed to the output file:
 
 @example
@@ -23941,7 +25297,7 @@ line.  That line is then printed to the output file:
 /^@@c(omment)?[ \t]+file/    \
 @{
     if (NF != 3) @{
-        e = (FILENAME ":" FNR ": badly formed `file' line")
+        e = ("extract: " FILENAME ":" FNR ": badly formed `file' line")
         print e > "/dev/stderr"
         next
     @}
@@ -23986,20 +25342,19 @@ subsequent output is appended to the file
 (@pxref{Redirection}).
 This makes it easy to mix program text and explanatory prose for the same
 sample source file (as has been done here!) without any hassle.  The file is
-only closed when a new data file name is encountered or at the end of the
+only closed when a new @value{DF} name is encountered or at the end of the
 input file.
 
 Finally, the function @code{@w{unexpected_eof()}} prints an appropriate
 error message and then exits.
 The @code{END} rule handles the final cleanup, closing the open file:
 
-@c function lb put on same line for page breaking. sigh
 @example
 @c file eg/prog/extract.awk
 @group
 function unexpected_eof()
 @{
-    printf("%s:%d: unexpected EOF or error\n",
+    printf("extract: %s:%d: unexpected EOF or error\n",
         FILENAME, FNR) > "/dev/stderr"
     exit 1
 @}
@@ -24013,6 +25368,7 @@ END @{
 @end example
 @c ENDOFRANGE texse
 @c ENDOFRANGE fitex
+@c ENDOFRANGE extract
 
 @node Simple Sed
 @subsection A Simple Stream Editor
@@ -24038,10 +25394,11 @@ Here, @samp{s/old/new/g} tells @command{sed} to look for the regexp
 
 The following program, @file{awksed.awk}, accepts at least two command-line
 arguments: the pattern to look for and the text to replace it with. Any
-additional arguments are treated as data file names to process. If none
+additional arguments are treated as @value{DF} names to process. If none
 are provided, the standard input is used:
 
 @cindex Brennan, Michael
+@c STARTOFRANGE awksed
 @cindex @command{awksed.awk} program
 @c @cindex simple stream editor
 @c @cindex stream editor, simple
@@ -24111,33 +25468,14 @@ The @code{BEGIN} rule handles the setup, checking for the right number
 of arguments and calling @code{usage()} if there is a problem. Then it sets
 @code{RS} and @code{ORS} from the command-line arguments and sets
 @code{ARGV[1]} and @code{ARGV[2]} to the null string, so that they are
-not treated as file names
+not treated as @value{FN}s
 (@pxref{ARGC and ARGV}).
 
 The @code{usage()} function prints an error message and exits.
 Finally, the single rule handles the printing scheme outlined above,
 using @code{print} or @code{printf} as appropriate, depending upon the
 value of @code{RT}.
-
-@ignore
-Exercise, compare the performance of this version with the more
-straightforward:
-
-BEGIN {
-    pat = ARGV[1]
-    repl = ARGV[2]
-    ARGV[1] = ARGV[2] = ""
-}
-
-{ gsub(pat, repl); print }
-
-Exercise: what are the advantages and disadvantages of this version versus sed?
-  Advantage: egrep regexps
-             speed (?)
-  Disadvantage: no & in replacement text
-
-Others?
-@end ignore
+@c ENDOFRANGE awksed
 
 @node Igawk Program
 @subsection An Easy Way to Use Library Functions
@@ -24179,7 +25517,7 @@ BEGIN @{
 The following program, @file{igawk.sh}, provides this service.
 It simulates @command{gawk}'s searching of the @env{AWKPATH} variable
 and also allows @dfn{nested} includes; i.e., a file that is included
-with @samp{@@include} can contain further @samp{@@include} statements.
+with @code{@@include} can contain further @code{@@include} statements.
 @command{igawk} makes an effort to only include files once, so that nested
 includes don't accidentally include a library function twice.
 
@@ -24209,7 +25547,7 @@ Literal text, provided with @option{--source} or @option{--source=}.  This
 text is just appended directly.
 
 @item
-Source file names, provided with @option{-f}.  We use a neat trick and append
+Source @value{FN}s, provided with @option{-f}.  We use a neat trick and append
 @samp{@@include @var{filename}} to the shell variable's contents.  Since the file-inclusion
 program works the way @command{gawk} does, this gets the text
 of the file included into the program at the correct point.
@@ -24217,12 +25555,12 @@ of the file included into the program at the correct point.
 
 @item
 Run an @command{awk} program (naturally) over the shell variable's contents to expand
-@samp{@@include} statements.  The expanded program is placed in a second
+@code{@@include} statements.  The expanded program is placed in a second
 shell variable.
 
 @item
 Run the expanded program with @command{gawk} and any other original command-line
-arguments that the user supplied (such as the data file names).
+arguments that the user supplied (such as the @value{DF} names).
 @end enumerate
 
 This program uses shell variables extensively: for storing command-line arguments,
@@ -24237,24 +25575,25 @@ argument is @samp{debug}.
 The next part loops through all the command-line arguments.
 There are several cases of interest:
 
-@table @code
-@item --
+@c @asis for docbook
+@table @asis
+@item @option{--}
 This ends the arguments to @command{igawk}.  Anything else should be passed on
 to the user's @command{awk} program without being evaluated.
 
-@item -W
+@item @option{-W}
 This indicates that the next option is specific to @command{gawk}.  To make
 argument processing easier, the @option{-W} is appended to the front of the
 remaining arguments and the loop continues.  (This is an @command{sh}
 programming trick.  Don't worry about it if you are not familiar with
 @command{sh}.)
 
-@item -v@r{,} -F
+@item @option{-v}, @option{-F}
 These are saved and passed on to @command{gawk}.
 
-@item -f@r{,} --file@r{,} --file=@r{,} -Wfile=
-The file name is appended to the shell variable @code{program} with an
-@samp{@@include} statement.
+@item @option{-f}, @option{--file}, @option{--file=}, @option{-Wfile=}
+The @value{FN} is appended to the shell variable @code{program} with an
+@code{@@include} statement.
 The @command{expr} utility is used to remove the leading option part of the
 argument (e.g., @samp{--file=}).
 (Typical @command{sh} usage would be to use the @command{echo} and @command{sed}
@@ -24262,10 +25601,10 @@ utilities to do this work.  Unfortunately, some versions of @command{echo} evalu
 escape sequences in their arguments, possibly mangling the program text.
 Using @command{expr} avoids this problem.)
 
-@item --source@r{,} --source=@r{,} -Wsource=
+@item @option{--source}, @option{--source=}, @option{-Wsource=}
 The source text is appended to @code{program}.
 
-@item --version@r{,} -Wversion
+@item @option{--version}, @option{-Wversion}
 @command{igawk} prints its version number, runs @samp{gawk --version}
 to get the @command{gawk} version information, and then exits.
 @end table
@@ -24281,6 +25620,7 @@ program.
 
 The program is as follows:
 
+@c STARTOFRANGE igawk
 @cindex @code{igawk.sh} program
 @example
 @c file eg/prog/igawk.sh
@@ -24372,15 +25712,15 @@ fi
 @c endfile
 @end example
 
-The @command{awk} program to process @samp{@@include} directives
+The @command{awk} program to process @code{@@include} directives
 is stored in the shell variable @code{expand_prog}.  Doing this keeps
 the shell script readable.  The @command{awk} program
 reads through the user's program, one line at a time, using @code{getline}
 (@pxref{Getline}).  The input
-file names and @samp{@@include} statements are managed using a stack.
-As each @samp{@@include} is encountered, the current file name is
-``pushed'' onto the stack and the file named in the @samp{@@include}
-directive becomes the current file name.  As each file is finished,
+@value{FN}s and @code{@@include} statements are managed using a stack.
+As each @code{@@include} is encountered, the current @value{FN} is
+``pushed'' onto the stack and the file named in the @code{@@include}
+directive becomes the current @value{FN}.  As each file is finished,
 the stack is ``popped,'' and the previous input file becomes the current
 input file again.  The process is started by making the original file
 the first one on the stack.
@@ -24389,16 +25729,16 @@ The @code{pathto()} function does the work of finding the full path to
 a file.  It simulates @command{gawk}'s behavior when searching the
 @env{AWKPATH} environment variable
 (@pxref{AWKPATH Variable}).
-If a file name has a @samp{/} in it, no path search is done.
-Similarly, if the file name is @code{"-"}, then that string is
+If a @value{FN} has a @samp{/} in it, no path search is done.
+Similarly, if the @value{FN} is @code{"-"}, then that string is
 used as-is.  Otherwise,
-the file name is concatenated with the name of each directory in
-the path, and an attempt is made to open the generated file name.
+the @value{FN} is concatenated with the name of each directory in
+the path, and an attempt is made to open the generated @value{FN}.
 The only way to test if a file can be read in @command{awk} is to go
 ahead and try to read it with @code{getline}; this is what @code{pathto()}
 does.@footnote{On some very old versions of @command{awk}, the test
 @samp{getline junk < t} can loop forever if the file exists but is empty.
-Caveat emptor.} If the file can be read, it is closed and the file name
+Caveat emptor.} If the file can be read, it is closed and the @value{FN}
 is returned:
 
 @ignore
@@ -24453,17 +25793,17 @@ BEGIN @{
 @c endfile
 @end example
 
-The stack is initialized with @code{ARGV[1]}, which will be @file{/dev/stdin}.
+The stack is initialized with @code{ARGV[1]}, which will be @code{"/dev/stdin"}.
 The main loop comes next.  Input lines are read in succession. Lines that
-do not start with @samp{@@include} are printed verbatim.
-If the line does start with @samp{@@include}, the file name is in @code{$2}.
+do not start with @code{@@include} are printed verbatim.
+If the line does start with @code{@@include}, the @value{FN} is in @code{$2}.
 @code{pathto()} is called to generate the full path.  If it cannot, then the program
 prints an error message and continues.
 
 The next thing to check is if the file is included already.  The
-@code{processed} array is indexed by the full file name of each included
+@code{processed} array is indexed by the full @value{FN} of each included
 file and it tracks this information for us.  If the file is
-seen again, a warning message is printed. Otherwise, the new file name is
+seen again, a warning message is printed. Otherwise, the new @value{FN} is
 pushed onto the stack and processing continues.
 
 Finally, when @code{getline} encounters the end of the input file, the file
@@ -24484,7 +25824,7 @@ the program is done:
             fpath = pathto($2)
 @group
             if (fpath == "") @{
-                printf("igawk:%s:%d: cannot find %s\n",
+                printf("igawk: %s:%d: cannot find %s\n",
                     input[stackptr], FNR, $2) > "/dev/stderr"
                 continue
             @}
@@ -24524,7 +25864,7 @@ It's done in these steps:
 
 @enumerate
 @item
-Run @command{gawk} with the @samp{@@include}-processing program (the
+Run @command{gawk} with the @code{@@include}-processing program (the
 value of the @code{expand_prog} shell variable) on standard input.
 
 @item
@@ -24541,10 +25881,10 @@ options and command-line arguments that the user supplied.
 
 @c this causes more problems than it solves, so leave it out.
 @ignore
-The special file @file{/dev/null} is passed as a data file to @command{gawk}
+The special file @file{/dev/null} is passed as a @value{DF} to @command{gawk}
 to handle an interesting case. Suppose that the user's program only has
-a @code{BEGIN} rule and there are no data files to read.
-The program should exit without reading any data files.
+a @code{BEGIN} rule and there are no @value{DF}s to read.
+The program should exit without reading any @value{DF}s.
 However, suppose that an included library file defines an @code{END}
 rule of its own. In this case, @command{gawk} will hang, reading standard
 input. In order to avoid this, @file{/dev/null} is explicitly added to the
@@ -24563,27 +25903,25 @@ eval gawk $opts -- '"$processed_program"' '"$@@"'
 The @command{eval} command is a shell construct that reruns the shell's parsing
 process.  This keeps things properly quoted.
 
-This version of @command{igawk} represents my fifth version of this program.
+This version of @command{igawk} represents the fifth version of this program.
 There are four key simplifications that make the program work better:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-Using @samp{@@include} even for the files named with @option{-f} makes building
+Using @code{@@include} even for the files named with @option{-f} makes building
 the initial collected @command{awk} program much simpler; all the
-@samp{@@include} processing can be done once.
+@code{@@include} processing can be done once.
 
 @item
 Not trying to save the line read with @code{getline}
 in the @code{pathto()} function when testing for the
 file's accessibility for use with the main program simplifies things
 considerably.
-@c what problem does this engender though - exercise
-@c answer, reading from "-" or /dev/stdin
 
 @item
 Using a @code{getline} loop in the @code{BEGIN} rule does it all in one
 place.  It is not necessary to call out to a separate loop for processing
-nested @samp{@@include} statements.
+nested @code{@@include} statements.
 
 @item
 Instead of saving the expanded program in a temporary file, putting it in a shell variable
@@ -24603,47 +25941,18 @@ Finally, @command{igawk} shows that it is not always necessary to add new
 features to a program; they can often be layered on top.
 @ignore
 With @command{igawk},
-there is no real reason to build @samp{@@include} processing into
+there is no real reason to build @code{@@include} processing into
 @command{gawk} itself.
 @end ignore
-
-@cindex search paths
-@cindex search paths, for source files
-@cindex source files@comma{} search path for
-@cindex files, source@comma{} search path for
-@cindex directories, searching
-As an additional example of this, consider the idea of having two
-files in a directory in the search path:
-
-@table @file
-@item default.awk
-This file contains a set of default library functions, such
-as @code{getopt()} and @code{assert()}.
-
-@item site.awk
-This file contains library functions that are specific to a site or
-installation; i.e., locally developed functions.
-Having a separate file allows @file{default.awk} to change with
-new @command{gawk} releases, without requiring the system administrator to
-update it each time by adding the local functions.
-@end table
-
-One user
-@c Karl Berry, karl@ileaf.com, 10/95
-suggested that @command{gawk} be modified to automatically read these files
-upon startup.  Instead, it would be very simple to modify @command{igawk}
-to do this. Since @command{igawk} can process nested @samp{@@include}
-directives, @file{default.awk} could simply contain @samp{@@include}
-statements for the desired library functions.
-
-@c Exercise: make this change
 @c ENDOFRANGE libfex
 @c ENDOFRANGE flibex
 @c ENDOFRANGE awkpex
+@c ENDOFRANGE igawk
 
 @node Anagram Program
 @subsection Finding Anagrams From A Dictionary
 
+@cindex anagrams, finding
 An interesting programming challenge is to
 search for @dfn{anagrams} in a
 word list (such as
@@ -24663,6 +25972,7 @@ The following program uses arrays of arrays to bring together
 words with the same signature and array sorting to print the words
 in sorted order.
 
+@c STARTOFRANGE anagram
 @cindex @code{anagram.awk} program
 @example
 @c file eg/prog/anagram.awk
@@ -24771,9 +26081,13 @@ babery yabber
 @dots{}
 @end example
 
+@c ENDOFRANGE anagram
+
 @node Signature Program
 @subsection And Now For Something Completely Different
 
+@cindex signature program
+@cindex Brini, Davide
 The following program was written by Davide Brini
 @c (@email{dave_br@@gmx.com})
 and is published on @uref{http://backreference.org/2011/02/03/obfuscated-awk/,
@@ -24798,7 +26112,10 @@ X*(X-x)-o*o,(x+X)*o*o+o,x*(X-x)-O-O,x-O+(O+o+X+x)*(o+O),X*X-X*(x-O)-x+O,
 O+X*(o*(o+O)+O),+x+O+X*o,x*(x-o),(o+X+x)*o*o-(x-O-O),O+(X-x)*(X+O),x-O@}'
 @end example
 
-We leave it to you to determine what the program does.
+@cindex Johansen, Chris
+We leave it to you to determine what the program does.  (If you are
+truly desperate to understand it, see Chris Johansen's explanation,
+which is embedded in the Texinfo source file for this @value{DOCUMENT}.)
 
 @ignore
 To: "Arnold Robbins" <arnold@skeeve.com>
@@ -24878,19 +26195,181 @@ BEGIN {
 }
 @end ignore
 
-@iftex
-@part Part III:@* Moving Beyond Standard @command{awk} With @command{gawk}
-@end iftex
+@node Programs Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+The functions provided in this @value{CHAPTER} and the previous one
+continue on the theme that reading programs is an excellent way to learn
+Good Programming.
+
+@item
+Using @samp{#!} to make @command{awk} programs directly runnable makes
+them easier to use.  Otherwise, invoke the program using @samp{awk
+-f @dots{}}.
+
+@item
+Reimplementing standard POSIX programs in @command{awk} is a pleasant
+exercise; @command{awk}'s expressive power lets you write such programs
+in relatively few lines of code, yet they are functionally complete
+and usable.
+
+@item
+One of standard @command{awk}'s weaknesses is working with individual
+characters.  The ability to use @code{split()} with the empty string as
+the separator can considerably simplify such tasks.
+
+@item
+The library functions from @ref{Library Functions}, proved their
+usefulness for a number of real (if small) programs.
+
+@item
+Besides reinventing POSIX wheels, other programs solved a selection of
+interesting problems, such as finding duplicates words in text, printing
+mailing labels, and finding anagrams.
+
+@end itemize
+
+@node Programs Exercises
+@section Exercises
+
+@enumerate
+@item
+Rewrite @file{cut.awk} (@pxref{Cut Program})
+using @code{split()} with @code{""} as the seperator.
+
+@item
+In @ref{Egrep Program}, we mentioned that @samp{egrep -i} could be
+simulated in versions of @command{awk} without @code{IGNORECASE} by
+using @code{tolower()} on the line and the pattern. In a footnote there,
+we also mentioned that this solution has a bug: the translated line is
+output, and not the original one.  Fix this problem.
+@c Exercise: Fix this, w/array and new line as key to original line
+
+@item
+The POSIX version of @command{id} takes options that control which
+information is printed.  Modify the @command{awk} version
+(@pxref{Id Program}) to accept the same arguments and perform in the
+same way.
+
+@item
+The @code{split.awk} program (@pxref{Split Program}) uses
+the @code{chr()} and @code{ord()} functions to move through the
+letters of the alphabet.
+Modify the program to instead use only the @command{awk}
+built-in functions, such as @code{index()} and @code{substr()}.
+
+@item
+The @code{split.awk} program (@pxref{Split Program}) assumes
+that letters are contiguous in the character set,
+which isn't true for EBCDIC systems.
+Fix this problem.
+
+@item
+Why can't the @file{wc.awk} program (@pxref{Wc Program}) just
+use the value of @code{FNR} in @code{endfile()}?
+Hint: Examine the code in @ref{Filetrans Function}.
 
 @ignore
-@ifdocbook
+@command{wc} can't just use the value of @code{FNR} in
+@code{endfile()}. If you examine the code in @ref{Filetrans Function},
+you will see that @code{FNR} has already been reset by the time
+@code{endfile()} is called.
+@end ignore
+
+@item
+Manipulation of individual characters in the @command{translate} program
+(@pxref{Translate Program}) is painful using standard @command{awk}
+functions.  Given that @command{gawk} can split strings into individual
+characters using @code{""} as the separator, how might you use this
+feature to simplify the program?
 
-@part Part III:@* Moving Beyond Standard @command{awk} With @command{gawk}
+@item
+The @file{extract.awk} program (@pxref{Extract Program}) was written
+before @command{gawk} had the @code{gensub()} function.  Use it
+to simplify the code.
+
+@item
+Compare the performance of the @file{awksed.awk} program
+(@pxref{Simple Sed}) with the more straightforward:
+
+@example
+BEGIN @{
+    pat = ARGV[1]
+    repl = ARGV[2]
+    ARGV[1] = ARGV[2] = ""
+@}
+
+@{ gsub(pat, repl); print @}
+@end example
+
+@item
+What are the advantages and disadvantages of @file{awksed.awk} versus
+the real @command{sed} utility?
+
+@ignore
+  Advantage: egrep regexps
+             speed (?)
+  Disadvantage: no & in replacement text
+
+Others?
+@end ignore
 
+@item
+In @ref{Igawk Program}, we mentioned that not trying to save the line
+read with @code{getline} in the @code{pathto()} function when testing
+for the file's accessibility for use with the main program simplifies
+things considerably.  What problem does this engender though?
+@c answer, reading from "-" or /dev/stdin
+
+@cindex search paths
+@cindex search paths, for source files
+@cindex source files@comma{} search path for
+@cindex files, source@comma{} search path for
+@cindex directories, searching
+@item
+As an additional example of the idea that it is not always necessary to
+add new features to a program, consider the idea of having two files in
+a directory in the search path:
+
+@table @file
+@item default.awk
+This file contains a set of default library functions, such
+as @code{getopt()} and @code{assert()}.
+
+@item site.awk
+This file contains library functions that are specific to a site or
+installation; i.e., locally developed functions.
+Having a separate file allows @file{default.awk} to change with
+new @command{gawk} releases, without requiring the system administrator to
+update it each time by adding the local functions.
+@end table
+
+One user
+@c Karl Berry, karl@ileaf.com, 10/95
+suggested that @command{gawk} be modified to automatically read these files
+upon startup.  Instead, it would be very simple to modify @command{igawk}
+to do this. Since @command{igawk} can process nested @code{@@include}
+directives, @file{default.awk} could simply contain @code{@@include}
+statements for the desired library functions.
+Make this change.
+
+@item
+Modify @file{anagram.awk} (@pxref{Anagram Program}), to avoid
+the use of the external @command{sort} utility.
+
+@end enumerate
+
+@ifnotinfo
+@part @value{PART3}Moving Beyond Standard @command{awk} With @command{gawk}
+@end ifnotinfo
+
+@ifdocbook
 Part III focuses on features specific to @command{gawk}.
 It contains the following chapters:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Advanced Features}.
 
@@ -24905,12 +26384,11 @@ It contains the following chapters:
 
 @item
 @ref{Dynamic Extensions}.
+@end itemize
 @end ifdocbook
-@end ignore
 
 @node Advanced Features
 @chapter Advanced Features of @command{gawk}
-@cindex advanced features, network connections, See Also networks, connections
 @c STARTOFRANGE gawadv
 @cindex @command{gawk}, features, advanced
 @c STARTOFRANGE advgaw
@@ -24923,6 +26401,8 @@ Contributed by: Peter Langston <pud!psl@bellcore.bellcore.com>
 "Write documentation as if whoever reads it is a violent psychopath
 who knows where you live."
 @end ignore
+@cindex Langston, Peter
+@cindex English, Steve
 @quotation
 @i{Write documentation as if whoever reads it is
 a violent psychopath who knows where you live.}
@@ -24942,10 +26422,11 @@ of TCP/IP networking.  Finally, @command{gawk}
 can @dfn{profile} an @command{awk} program, making it possible to tune
 it for performance.
 
+@c FULLXREF ON
 A number of advanced features require separate @value{CHAPTER}s of their
 own:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Internationalization}, discusses how to internationalize
 your @command{awk} programs, so that they can speak multiple
@@ -24964,6 +26445,7 @@ debugger for debugging @command{awk} programs.
 discusses the ability to dynamically add new built-in functions to
 @command{gawk}.
 @end itemize
+@c FULLXREF OFF
 
 @menu
 * Nondecimal Data::             Allowing nondecimal input data.
@@ -24972,11 +26454,12 @@ discusses the ability to dynamically add new built-in functions to
 * Two-way I/O::                 Two-way communications with another process.
 * TCP/IP Networking::           Using @command{gawk} for network programming.
 * Profiling::                   Profiling your @command{awk} programs.
+* Advanced Features Summary::   Summary of advanced features.
 @end menu
 
 @node Nondecimal Data
 @section Allowing Nondecimal Input Data
-@cindex @code{--non-decimal-data} option
+@cindex @option{--non-decimal-data} option
 @cindex advanced features, nondecimal input data
 @cindex input, data@comma{} nondecimal
 @cindex constants, nondecimal
@@ -25004,7 +26487,7 @@ $ @kbd{echo 0123 123 0x123 | gawk '@{ print $1, $2, $3 @}'}
 The @code{print} statement treats its expressions as strings.
 Although the fields can act as numbers when necessary,
 they are still strings, so @code{print} does not try to treat them
-numerically.  You may need to add zero to a field to force it to
+numerically.  You need to add zero to a field to force it to
 be treated as a number.  For example:
 
 @example
@@ -25020,13 +26503,13 @@ using this facility could lead to surprising results, the default is to leave it
 disabled.  If you want it, you must explicitly request it.
 
 @cindex programming conventions, @code{--non-decimal-data} option
-@cindex @code{--non-decimal-data} option, @code{strtonum()} function and
+@cindex @option{--non-decimal-data} option, @code{strtonum()} function and
 @cindex @code{strtonum()} function (@command{gawk}), @code{--non-decimal-data} option and
 @quotation CAUTION
 @emph{Use of this option is not recommended.}
 It can break old programs very badly.
 Instead, use the @code{strtonum()} function to convert your data
-(@pxref{Nondecimal-numbers}).
+(@pxref{String Functions}).
 This makes your programs easier to write and easier to read, and
 leads to less surprising results.
 @end quotation
@@ -25060,7 +26543,7 @@ lets you do this.
 
 @ref{Controlling Scanning}, describes how you can assign special,
 pre-defined values to @code{PROCINFO["sorted_in"]} in order to
-control the order in which @command{gawk} will traverse an array
+control the order in which @command{gawk} traverses an array
 during a @code{for} loop.
 
 In addition, the value of @code{PROCINFO["sorted_in"]} can be a function name.
@@ -25317,9 +26800,9 @@ sorted array traversal is not the default.
 @subsection Sorting Array Values and Indices with @command{gawk}
 
 @cindex arrays, sorting
-@cindex @code{asort()} function (@command{gawk})
+@cindexgawkfunc{asort}
 @cindex @code{asort()} function (@command{gawk}), arrays@comma{} sorting
-@cindex @code{asorti()} function (@command{gawk})
+@cindexgawkfunc{asorti}
 @cindex @code{asorti()} function (@command{gawk}), arrays@comma{} sorting
 @cindex sort function, arrays, sorting
 In most @command{awk} implementations, sorting an array requires writing
@@ -25384,9 +26867,9 @@ END @{
 
 So far, so good. Now it starts to get interesting.  Both @code{asort()}
 and @code{asorti()} accept a third string argument to control comparison
-of array elements.  In @ref{String Functions}, we ignored this third
-argument; however, the time has now come to describe how this argument
-affects these two functions.
+of array elements.  When we introduced @code{asort()} and @code{asorti()}
+in @ref{String Functions}, we ignored this third argument; however,
+now is the time to describe how this argument affects these two functions.
 
 Basically, the third argument specifies how the array is to be sorted.
 There are two possibilities.  As with @code{PROCINFO["sorted_in"]},
@@ -25414,9 +26897,8 @@ both arrays use the values.
 
 @c Document It And Call It A Feature. Sigh.
 @cindex @command{gawk}, @code{IGNORECASE} variable in
-@cindex @code{IGNORECASE} variable
-@cindex arrays, sorting, @code{IGNORECASE} variable and
-@cindex @code{IGNORECASE} variable, array sorting and
+@cindex arrays, sorting, and @code{IGNORECASE} variable
+@cindex @code{IGNORECASE} variable, and array sorting functions
 Because @code{IGNORECASE} affects string comparisons, the value
 of @code{IGNORECASE} also affects sorting for both @code{asort()} and @code{asorti()}.
 Note also that the locale's sorting order does @emph{not}
@@ -25495,7 +26977,7 @@ open a @emph{two-way} pipe to another process.  The second process is
 termed a @dfn{coprocess}, since it runs in parallel with @command{gawk}.
 The two-way connection is created using the @samp{|&} operator
 (borrowed from the Korn shell, @command{ksh}):@footnote{This is very
-different from the same operator in the C shell.}
+different from the same operator in the C shell and in Bash.}
 
 @example
 do @{
@@ -25517,7 +26999,7 @@ the shell.
 
 There are some cautionary items to be aware of:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 As the code inside @command{gawk} currently stands, the coprocess's
 standard error goes to the same place that the parent @command{gawk}'s
@@ -25583,9 +27065,10 @@ has been read, @command{gawk} terminates the coprocess and exits.
 
 As a side note, the assignment @samp{LC_ALL=C} in the @command{sort}
 command ensures traditional Unix (ASCII) sorting from @command{sort}.
+This is not strictly necessary here, but it's good to know how to do this.
 
 @cindex @command{gawk}, @code{PROCINFO} array in
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, and communications via ptys
 You may also use pseudo-ttys (ptys) for
 two-way communication instead of pipes, if your system supports them.
 This is done on a per-command basis, by setting a special element
@@ -25601,7 +27084,7 @@ print @dots{} |& command       # start two-way pipe
 @end example
 
 @noindent
-Using ptys avoids the buffer deadlock issues described earlier, at some
+Using ptys usually avoids the buffer deadlock issues described earlier, at some
 loss in performance.  If your system does not have ptys, or if all the
 system's ptys are in use, @command{gawk} automatically falls back to
 using regular pipes.
@@ -25636,10 +27119,10 @@ another process on another system across an IP network connection.
 You can think of this as just a @emph{very long} two-way pipeline to
 a coprocess.
 The way @command{gawk} decides that you want to use TCP/IP networking is
-by recognizing special file names that begin with one of @samp{/inet/},
+by recognizing special @value{FN}s that begin with one of @samp{/inet/},
 @samp{/inet4/} or @samp{/inet6}.
 
-The full syntax of the special file name is
+The full syntax of the special @value{FN} is
 @file{/@var{net-type}/@var{protocol}/@var{local-port}/@var{remote-host}/@var{remote-port}}.
 The components are:
 
@@ -25705,7 +27188,9 @@ See
 @inforef{Top, , General Introduction, gawkinet, TCP/IP Internetworking with @command{gawk}},
 @end ifinfo
 @ifnotinfo
-See @cite{TCP/IP Internetworking with @command{gawk}},
+See
+@uref{http://www.gnu.org/software/gawk/manual/gawkinet/,
+@cite{TCP/IP Internetworking with @command{gawk}}},
 which comes as part of the @command{gawk} distribution,
 @end ifnotinfo
 for a much more complete introduction and discussion, as well as
@@ -25728,7 +27213,7 @@ When @command{gawk} has finished running, it creates a profile of your program i
 named @file{awkprof.out}. Because it is profiling, it also executes up to 45% slower than
 @command{gawk} normally does.
 
-@cindex @code{--profile} option
+@cindex @option{--profile} option
 As shown in the following example,
 the @option{--profile} option can be used to change the name of the file
 where @command{gawk} will write the profile:
@@ -25783,68 +27268,77 @@ foo
 junk
 @end example
 
-Here is the @file{awkprof.out} that results from running the @command{gawk}
-profiler on this program and data (this example also illustrates that @command{awk}
-programmers sometimes have to work late):
+Here is the @file{awkprof.out} that results from running the
+@command{gawk} profiler on this program and data. (This example also
+illustrates that @command{awk} programmers sometimes get up very early
+in the morning to work.)
 
-@cindex @code{BEGIN} pattern
-@cindex @code{END} pattern
+@cindex @code{BEGIN} pattern, and profiling
+@cindex @code{END} pattern, and profiling
 @example
-        # gawk profile, created Sun Aug 13 00:00:15 2000
+    # gawk profile, created Thu Feb 27 05:16:21 2014
 
-        # BEGIN block(s)
+    # BEGIN block(s)
 
-        BEGIN @{
-     1          print "First BEGIN rule"
-     1          print "Second BEGIN rule"
-        @}
+    BEGIN @{
+ 1          print "First BEGIN rule"
+    @}
 
-        # Rule(s)
+    BEGIN @{
+ 1          print "Second BEGIN rule"
+    @}
 
-     5  /foo/   @{ # 2
-     2          print "matched /foo/, gosh"
-     6          for (i = 1; i <= 3; i++) @{
-     6                  sing()
-                @}
-        @}
+    # Rule(s)
 
-     5  @{
-     5          if (/foo/) @{ # 2
-     2                  print "if is true"
-     3          @} else @{
-     3                  print "else is true"
-                @}
-        @}
+ 5  /foo/ @{ # 2
+ 2          print "matched /foo/, gosh"
+ 6          for (i = 1; i <= 3; i++) @{
+ 6                  sing()
+            @}
+    @}
 
-        # END block(s)
+ 5  @{
+ 5          if (/foo/) @{ # 2
+ 2                  print "if is true"
+ 3          @} else @{
+ 3                  print "else is true"
+            @}
+    @}
 
-        END @{
-     1          print "First END rule"
-     1          print "Second END rule"
-        @}
+    # END block(s)
 
-        # Functions, listed alphabetically
+    END @{
+ 1          print "First END rule"
+    @}
 
-     6  function sing(dummy)
-        @{
-     6          print "I gotta be me!"
-        @}
+    END @{
+ 1          print "Second END rule"
+    @}
+
+
+    # Functions, listed alphabetically
+
+ 6  function sing(dummy)
+    @{
+ 6          print "I gotta be me!"
+    @}
 @end example
 
 This example illustrates many of the basic features of profiling output.
 They are as follows:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-The program is printed in the order @code{BEGIN} rule,
-@code{BEGINFILE} rule,
+The program is printed in the order @code{BEGIN} rules,
+@code{BEGINFILE} rules,
 pattern/action rules,
-@code{ENDFILE} rule, @code{END} rule and functions, listed
+@code{ENDFILE} rules, @code{END} rules and functions, listed
 alphabetically.
-Multiple @code{BEGIN} and @code{END} rules are merged together,
-as are multiple @code{BEGINFILE} and @code{ENDFILE} rules.
+Multiple @code{BEGIN} and @code{END} rules retain their
+separate identities, as do
+multiple @code{BEGINFILE} and @code{ENDFILE} rules.
 
-@cindex patterns, counts
+@cindex patterns, counts, in a profile
 @item
 Pattern-action rules have two counts.
 The first count, to the left of the rule, shows how many times
@@ -25864,7 +27358,7 @@ is a count showing how many times the condition was true.
 The count for the @code{else}
 indicates how many times the test failed.
 
-@cindex loops, count for header
+@cindex loops, count for header, in a profile
 @item
 The count for a loop header (such as @code{for}
 or @code{while}) shows how many times the loop test was executed.
@@ -25872,8 +27366,8 @@ or @code{while}) shows how many times the loop test was executed.
 statement in a rule to determine how many times the rule was executed.
 If the first statement is a loop, the count is misleading.)
 
-@cindex functions, user-defined, counts
-@cindex user-defined, functions, counts
+@cindex functions, user-defined, counts, in a profile
+@cindex user-defined, functions, counts, in a profile
 @item
 For user-defined functions, the count next to the @code{function}
 keyword indicates how many times the function was called.
@@ -25887,12 +27381,11 @@ The layout uses ``K&R'' style with TABs.
 Braces are used everywhere, even when
 the body of an @code{if}, @code{else}, or loop is only a single statement.
 
-@cindex @code{()} (parentheses)
-@cindex parentheses @code{()}
+@cindex @code{()} (parentheses), in a profile
+@cindex parentheses @code{()}, in a profile
 @item
 Parentheses are used only where needed, as indicated by the structure
 of the program and the precedence rules.
-@c extra verbiage here satisfies the copyeditor. ugh.
 For example, @samp{(3 + 5) * 4} means add three plus five, then multiply
 the total by four.  However, @samp{3 + 5 * 4} has no parentheses, and
 means @samp{3 + (5 * 4)}.
@@ -25923,8 +27416,8 @@ typed when you wrote it.  This is because @command{gawk} creates the
 profiled version by ``pretty printing'' its internal representation of
 the program.  The advantage to this is that @command{gawk} can produce
 a standard representation.  The disadvantage is that all source-code
-comments are lost, as are the distinctions among multiple @code{BEGIN},
-@code{END}, @code{BEGINFILE}, and @code{ENDFILE} rules.  Also, things such as:
+comments are lost.
+Also, things such as:
 
 @example
 /foo/
@@ -25944,6 +27437,7 @@ which is correct, but possibly surprising.
 
 @cindex profiling @command{awk} programs, dynamically
 @cindex @command{gawk} program, dynamic profiling
+@cindex dynamic profiling
 Besides creating profiles when a program has completed,
 @command{gawk} can produce a profile while it is running.
 This is useful if your @command{awk} program goes into an
@@ -25957,9 +27451,9 @@ $ @kbd{gawk --profile -f myprog &}
 @end example
 
 @cindex @command{kill} command@comma{} dynamic profiling
-@cindex @code{USR1} signal
-@cindex @code{SIGUSR1} signal
-@cindex signals, @code{USR1}/@code{SIGUSR1}
+@cindex @code{USR1} signal, for dynamic profiling
+@cindex @code{SIGUSR1} signal, for dynamic profiling
+@cindex signals, @code{USR1}/@code{SIGUSR1}, for profiling
 @noindent
 The shell prints a job number and process ID number; in this case, 13992.
 Use the @command{kill} command to send the @code{USR1} signal
@@ -25974,7 +27468,7 @@ As usual, the profiled version of the program is written to
 @file{awkprof.out}, or to a different file if one specified with
 the @option{--profile} option.
 
-Along with the regular profile, as shown earlier, the profile
+Along with the regular profile, as shown earlier, the profile file
 includes a trace of any active functions:
 
 @example
@@ -25990,9 +27484,9 @@ You may send @command{gawk} the @code{USR1} signal as many times as you like.
 Each time, the profile and function call trace are appended to the output
 profile file.
 
-@cindex @code{HUP} signal
-@cindex @code{SIGHUP} signal
-@cindex signals, @code{HUP}/@code{SIGHUP}
+@cindex @code{HUP} signal, for dynamic profiling
+@cindex @code{SIGHUP} signal, for dynamic profiling
+@cindex signals, @code{HUP}/@code{SIGHUP}, for profiling
 If you use the @code{HUP} signal instead of the @code{USR1} signal,
 @command{gawk} produces the profile and the function call trace and then exits.
 
@@ -26014,11 +27508,61 @@ keyboard.  The @code{INT} signal is generated by the
 Finally, @command{gawk} also accepts another option, @option{--pretty-print}.
 When called this way, @command{gawk} ``pretty prints'' the program into
 @file{awkprof.out}, without any execution counts.
-@c ENDOFRANGE advgaw
-@c ENDOFRANGE gawadv
+
+@quotation NOTE
+The @option{--pretty-print} option still runs your program.
+This will change in the next major release.
+@end quotation
 @c ENDOFRANGE awkp
 @c ENDOFRANGE proawk
 
+@node Advanced Features Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+The @option{--non-decimal-data} option causes @command{gawk} to treat
+octal- and hexadecimal-looking input data as octal and hexadecimal.
+This option should be used with caution or not at all; use of @code{strtonum()}
+is preferable.
+
+@item
+You can take over complete control of sorting in @samp{for (@var{indx} in @var{array})}
+array traversal by setting @code{PROCINFO["sorted_in"]} to the name of a user-defined
+function that does the comparison of array elements based on index and value.
+
+@item
+Similarly, you can supply the name of a user-defined comparison function as the
+third argument to either @code{asort()} or @command{asorti()} to control how
+those functions sort arrays. Or you may provide one of the predefined control
+strings that work for @code{PROCINFO["sorted_in"]}.
+
+@item
+You can use the @samp{|&} operator to create a two-way pipe to a co-process.
+You read from the co-process with @code{getline} and write to it with @code{print}
+or @code{printf}. Use @code{close()} to close off the co-process completely, or
+optionally, close off one side of the two-way communications.
+
+@item
+By using special ``@value{FN}s'' with the @samp{|&} operator, you can open a
+TCP/IP (or UDP/IP) connection to remote hosts in the Internet. @command{gawk}
+supports both IPv4 an IPv6.
+
+@item
+You can generate statement count profiles of your program. This can help you
+determine which parts of your program may be taking the most time and let
+you tune them more easily.  Sending the @code{USR1} signal while profiling causes
+@command{gawk} to dump the profile and keep going, including a function call stack.
+
+@item
+You can also just ``pretty print'' the program. This currently also runs
+the program, but that will change in the next major release.
+
+@end itemize
+
+@c ENDOFRANGE advgaw
+@c ENDOFRANGE gawadv
+
 @node Internationalization
 @chapter Internationalization with @command{gawk}
 
@@ -26047,11 +27591,12 @@ a requirement.
 
 @menu
 * I18N and L10N::               Internationalization and Localization.
-* Explaining gettext::          How GNU @code{gettext} works.
+* Explaining gettext::          How GNU @command{gettext} works.
 * Programmer i18n::             Features for the programmer.
 * Translator i18n::             Features for the translator.
 * I18N Example::                A simple i18n example.
 * Gawk I18N::                   @command{gawk} is also internationalized.
+* I18N Summary::                Summary of I18N stuff.
 @end menu
 
 @node I18N and L10N
@@ -26071,20 +27616,22 @@ responses, and information related to how numerical and
 monetary values are printed and read.
 
 @node Explaining gettext
-@section GNU @code{gettext}
+@section GNU @command{gettext}
 
 @cindex internationalizing a program
 @c STARTOFRANGE gettex
-@cindex @code{gettext} library
-The facilities in GNU @code{gettext} focus on messages; strings printed
+@cindex @command{gettext} library
+@command{gawk} uses GNU @command{gettext} to provide its internationalization
+features.
+The facilities in GNU @command{gettext} focus on messages; strings printed
 by a program, either directly or via formatting with @code{printf} or
 @code{sprintf()}.@footnote{For some operating systems, the @command{gawk}
-port doesn't support GNU @code{gettext}.
+port doesn't support GNU @command{gettext}.
 Therefore, these features are not available
 if you are using one of those operating systems. Sorry.}
 
-@cindex portability, @code{gettext} library and
-When using GNU @code{gettext}, each application has its own
+@cindex portability, @command{gettext} library and
+When using GNU @command{gettext}, each application has its own
 @dfn{text domain}.  This is a unique name, such as @samp{kpilot} or @samp{gawk},
 that identifies the application.
 A complete application may have multiple components---programs written
@@ -26108,7 +27655,7 @@ language).
 @cindex @code{textdomain()} function (C library)
 @item
 The programmer indicates the application's text domain
-(@code{"guide"}) to the @code{gettext} library,
+(@command{"guide"}) to the @command{gettext} library,
 by calling the @code{textdomain()} function.
 
 @cindex @code{.pot} files
@@ -26125,6 +27672,7 @@ lookup of the translations.
 
 @cindex @code{.po} files
 @cindex files, @code{.po}
+@c STARTOFRANGE portobfi
 @cindex portable object files
 @cindex files, portable object
 @item
@@ -26136,6 +27684,7 @@ For example, there might be a @file{fr.po} for a French translation.
 @cindex @code{.gmo} files
 @cindex files, @code{.gmo}
 @cindex message object files
+@c STARTOFRANGE portmsgfi
 @cindex files, message object
 @item
 Each language's @file{.po} file is converted into a binary
@@ -26150,7 +27699,7 @@ are installed in a standard place.
 
 @cindex @code{bindtextdomain()} function (C library)
 @item
-For testing and development, it is possible to tell @code{gettext}
+For testing and development, it is possible to tell @command{gettext}
 to use @file{.gmo} files in a different directory than the standard
 one by using the @code{bindtextdomain()} function.
 
@@ -26183,7 +27732,7 @@ strings enclosed in calls to @code{gettext()}.
 
 @cindex @code{_} (underscore), C macro
 @cindex underscore (@code{_}), C macro
-The GNU @code{gettext} developers, recognizing that typing
+The GNU @command{gettext} developers, recognizing that typing
 @samp{gettext(@dots{})} over and over again is both painful and ugly to look
 at, use the macro @samp{_} (an underscore) to make things easier:
 
@@ -26196,7 +27745,7 @@ printf("%s", _("Don't Panic!\n"));
 @end example
 
 @cindex internationalization, localization, locale categories
-@cindex @code{gettext} library, locale categories
+@cindex @command{gettext} library, locale categories
 @cindex locale categories
 @noindent
 This reduces the typing overhead to just three extra characters per string
@@ -26204,12 +27753,12 @@ and is considerably easier to read as well.
 
 There are locale @dfn{categories}
 for different types of locale-related information.
-The defined locale categories that @code{gettext} knows about are:
+The defined locale categories that @command{gettext} knows about are:
 
 @table @code
 @cindex @code{LC_MESSAGES} locale category
 @item LC_MESSAGES
-Text messages.  This is the default category for @code{gettext}
+Text messages.  This is the default category for @command{gettext}
 operations, but it is possible to supply a different one explicitly,
 if necessary.  (It is almost never necessary to supply a different category.)
 
@@ -26257,7 +27806,7 @@ before or after the day in a date, local month abbreviations, and so on.
 
 @cindex @code{LC_ALL} locale category
 @item LC_ALL
-All of the above.  (Not too useful in the context of @code{gettext}.)
+All of the above.  (Not too useful in the context of @command{gettext}.)
 @end table
 @c ENDOFRANGE gettex
 
@@ -26273,7 +27822,7 @@ internationalization:
 @cindex @code{TEXTDOMAIN} variable
 @item TEXTDOMAIN
 This variable indicates the application's text domain.
-For compatibility with GNU @code{gettext}, the default
+For compatibility with GNU @command{gettext}, the default
 value is @code{"messages"}.
 
 @cindex internationalization, localization, marked strings
@@ -26283,8 +27832,8 @@ String constants marked with a leading underscore
 are candidates for translation at runtime.
 String constants without a leading underscore are not translated.
 
-@cindex @code{dcgettext()} function (@command{gawk})
-@item dcgettext(@var{string} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcgettext}
+@item @code{dcgettext(@var{string}} [@code{,} @var{domain} [@code{,} @var{category}]]@code{)}
 Return the translation of @var{string} in
 text domain @var{domain} for locale category @var{category}.
 The default value for @var{domain} is the current value of @code{TEXTDOMAIN}.
@@ -26309,8 +27858,8 @@ chosen to be simple and to allow for reasonable @command{awk}-style
 default arguments.
 @end quotation
 
-@cindex @code{dcngettext()} function (@command{gawk})
-@item dcngettext(@var{string1}, @var{string2}, @var{number} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcngettext}
+@item @code{dcngettext(@var{string1}, @var{string2}, @var{number}} [@code{,} @var{domain} [@code{,} @var{category}]]@code{)}
 Return the plural form used for @var{number} of the
 translation of @var{string1} and @var{string2} in text domain
 @var{domain} for locale category @var{category}. @var{string1} is the
@@ -26325,10 +27874,10 @@ The same remarks about argument order as for the @code{dcgettext()} function app
 @cindex files, @code{.gmo}, specifying directory of
 @cindex message object files, specifying directory of
 @cindex files, message object, specifying directory of
-@cindex @code{bindtextdomain()} function (@command{gawk})
-@item bindtextdomain(@var{directory} @r{[}, @var{domain}@r{]})
+@cindexgawkfunc{bindtextdomain}
+@item @code{bindtextdomain(@var{directory}} [@code{,} @var{domain} ]@code{)}
 Change the directory in which
-@code{gettext} looks for @file{.gmo} files, in case they
+@command{gettext} looks for @file{.gmo} files, in case they
 will not or cannot be placed in the standard locations
 (e.g., during testing).
 Return the directory in which @var{domain} is ``bound.''
@@ -26427,7 +27976,7 @@ and use translations from @command{awk}.
 @cindex portable object files
 @cindex files, portable object
 Once a program's translatable strings have been marked, they must
-be extracted to create the initial @file{.po} file.
+be extracted to create the initial @file{.pot} file.
 As part of translation, it is often helpful to rearrange the order
 in which arguments to @code{printf} are output.
 
@@ -26447,13 +27996,13 @@ is covered.
 @subsection Extracting Marked Strings
 @cindex strings, extracting
 @cindex marked strings@comma{} extracting
-@cindex @code{--gen-pot} option
+@cindex @option{--gen-pot} option
 @cindex command-line options, string extraction
 @cindex string extraction (internationalization)
 @cindex marked string extraction (internationalization)
 @cindex extraction, of marked strings (internationalization)
 
-@cindex @code{--gen-pot} option
+@cindex @option{--gen-pot} option
 Once your @command{awk} program is working, and all the strings have
 been marked and you've set (and perhaps bound) the text domain,
 it is time to produce translations.
@@ -26467,15 +28016,17 @@ $ @kbd{gawk --gen-pot -f guide.awk > guide.pot}
 @cindex @code{xgettext} utility
 When run with @option{--gen-pot}, @command{gawk} does not execute your
 program.  Instead, it parses it as usual and prints all marked strings
-to standard output in the format of a GNU @code{gettext} Portable Object
+to standard output in the format of a GNU @command{gettext} Portable Object
 file.  Also included in the output are any constant strings that
 appear as the first argument to @code{dcgettext()} or as the first and
 second argument to @code{dcngettext()}.@footnote{The
 @command{xgettext} utility that comes with GNU
-@code{gettext} can handle @file{.awk} files.}
+@command{gettext} can handle @file{.awk} files.}
 @xref{I18N Example},
 for the full list of steps to go through to create and test
 translations for @command{guide}.
+@c ENDOFRANGE portobfi
+@c ENDOFRANGE portmsgfi
 
 @node Printf Ordering
 @subsection Rearranging @code{printf} Arguments
@@ -26486,9 +28037,8 @@ Format strings for @code{printf} and @code{sprintf()}
 (@pxref{Printf})
 present a special problem for translation.
 Consider the following:@footnote{This example is borrowed
-from the GNU @code{gettext} manual.}
+from the GNU @command{gettext} manual.}
 
-@c line broken here only for smallbook format
 @example
 printf(_"String `%s' has %d characters\n",
           string, length(string)))
@@ -26522,7 +28072,7 @@ example, @samp{string} is the first argument and @samp{length(string)} is the se
 @example
 $ @kbd{gawk 'BEGIN @{}
 >     @kbd{string = "Dont Panic"}
->     @kbd{printf _"%2$d characters live in \"%1$s\"\n",}
+>     @kbd{printf "%2$d characters live in \"%1$s\"\n",}
 >                         @kbd{string, length(string)}
 > @kbd{@}'}
 @print{} 10 characters live in "Dont Panic"
@@ -26556,7 +28106,7 @@ This is somewhat counterintuitive.
 and those with positional specifiers in the same string:
 
 @example
-$ @kbd{gawk 'BEGIN @{ printf _"%d %3$s\n", 1, 2, "hi" @}'}
+$ @kbd{gawk 'BEGIN @{ printf "%d %3$s\n", 1, 2, "hi" @}'}
 @error{} gawk: cmd. line:1: fatal: must use `count$' on all formats or none
 @end example
 
@@ -26596,7 +28146,7 @@ As written, it won't work on other versions of @command{awk}.
 However, it is actually almost portable, requiring very little
 change:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @cindex @code{TEXTDOMAIN} variable, portability and
 @item
 Assignments to @code{TEXTDOMAIN} won't have any effect,
@@ -26736,33 +28286,34 @@ msgstr "Like, the scoop is"
 @cindex Linux
 @cindex GNU/Linux
 The next step is to make the directory to hold the binary message object
-file and then to create the @file{guide.gmo} file.
-The directory layout shown here is standard for GNU @code{gettext} on
-GNU/Linux systems.  Other versions of @code{gettext} may use a different
+file and then to create the @file{guide.mo} file.
+We pretend that our file is to be used in the @code{en_US.UTF-8} locale.
+The directory layout shown here is standard for GNU @command{gettext} on
+GNU/Linux systems.  Other versions of @command{gettext} may use a different
 layout:
 
 @example
-$ @kbd{mkdir en_US en_US/LC_MESSAGES}
+$ @kbd{mkdir en_US.UTF-8 en_US.UTF-8/LC_MESSAGES}
 @end example
 
-@cindex @code{.po} files, converting to @code{.gmo}
-@cindex files, @code{.po}, converting to @code{.gmo}
-@cindex @code{.gmo} files, converting from @code{.po}
-@cindex files, @code{.gmo}, converting from @code{.po}
+@cindex @code{.po} files, converting to @code{.mo}
+@cindex files, @code{.po}, converting to @code{.mo}
+@cindex @code{.mo} files, converting from @code{.po}
+@cindex files, @code{.mo}, converting from @code{.po}
 @cindex portable object files, converting to message object files
 @cindex files, portable object, converting to message object files
 @cindex message object files, converting from portable object files
 @cindex files, message object, converting from portable object files
 @cindex @command{msgfmt} utility
 The @command{msgfmt} utility does the conversion from human-readable
-@file{.po} file to machine-readable @file{.gmo} file.
+@file{.po} file to machine-readable @file{.mo} file.
 By default, @command{msgfmt} creates a file named @file{messages}.
 This file must be renamed and placed in the proper directory so that
 @command{gawk} can find it:
 
 @example
 $ @kbd{msgfmt guide-mellow.po}
-$ @kbd{mv messages en_US/LC_MESSAGES/guide.gmo}
+$ @kbd{mv messages en_US.UTF-8/LC_MESSAGES/guide.mo}
 @end example
 
 Finally, we run the program to test it:
@@ -26791,30 +28342,71 @@ $ @kbd{gawk --posix -f guide.awk -f libintl.awk}
 @section @command{gawk} Can Speak Your Language
 
 @command{gawk} itself has been internationalized
-using the GNU @code{gettext} package.
-(GNU @code{gettext} is described in
+using the GNU @command{gettext} package.
+(GNU @command{gettext} is described in
 complete detail in
 @ifinfo
-@inforef{Top, , GNU @code{gettext} utilities, gettext, GNU gettext tools}.)
+@inforef{Top, , GNU @command{gettext} utilities, gettext, GNU gettext tools}.)
 @end ifinfo
 @ifnotinfo
-@cite{GNU gettext tools}.)
+@uref{http://www.gnu.org/software/gettext/manual/,
+@cite{GNU gettext tools}}.)
 @end ifnotinfo
-As of this writing, the latest version of GNU @code{gettext} is
-@uref{ftp://ftp.gnu.org/gnu/gettext/gettext-0.18.2.1.tar.gz, version 0.18.2.1}.
+As of this writing, the latest version of GNU @command{gettext} is
+@uref{ftp://ftp.gnu.org/gnu/gettext/gettext-0.19.1.tar.gz,
+@value{PVERSION} 0.19.1}.
 
 If a translation of @command{gawk}'s messages exists,
 then @command{gawk} produces usage messages, warnings,
 and fatal errors in the local language.
-@c ENDOFRANGE inloc
 
-@c The original text for this chapter was contributed by Efraim Yawitz.
-@c FIXME: Add more indexing.
+@node I18N Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Internationalization means writing a program such that it can use multiple
+languages without requiring source-code changes.  Localization means
+providing the data necessary for an internationalized program to work
+in a particular language.
+
+@item
+@command{gawk} uses GNU @command{gettext} to let you internationalize
+and localize @command{awk} programs.  A program's text domain identifies
+the program for grouping all messages and other data together.
+
+@item
+You mark a program's strings for translation by preceding them with
+an underscore. Once that is done, the strings are extracted into a
+@file{.pot} file.  This file is copied for each language into a @file{.po}
+file, and the @file{.po} files are compiled into @file{.gmo} files for
+use at runtime.
+
+@item
+You can use position specifications with @code{sprintf()} and
+@code{printf} to rearrange the placement of argument values in formatted
+strings and output. This is useful for the translations of format
+control strings.
+
+@item
+The internationalization features have been designed so that they
+can be easily worked around in a standard @command{awk}.
+
+@item
+@command{gawk} itself has been internationalized and ships with
+a number of translations for its messages.
+
+@end itemize
+
+@c ENDOFRANGE inloc
 
 @node Debugger
 @chapter Debugging @command{awk} Programs
 @cindex debugging @command{awk} programs
 
+@c The original text for this chapter was contributed by Efraim Yawitz.
+@c FIXME: Add more indexing.
+
 It would be nice if computer programs worked perfectly the first time they
 were run, but in real life, this rarely happens for programs of
 any complexity.  Thus, most programming languages have facilities available
@@ -26831,10 +28423,11 @@ how to use @command{gawk} for debugging your program is easy.
 * List of Debugger Commands::   Main debugger commands.
 * Readline Support::            Readline support.
 * Limitations::                 Limitations and future plans.
+* Debugging Summary::           Debugging summary.
 @end menu
 
 @node Debugging
-@section Introduction to @command{gawk} Debugger
+@section Introduction to The @command{gawk} Debugger
 
 This @value{SECTION} introduces debugging in general and begins
 the discussion of debugging in @command{gawk}.
@@ -26859,7 +28452,7 @@ In that case, what can you expect from such a tool?  The answer to that
 depends on the language being debugged, but in general, you can expect at
 least the following:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The ability to watch a program execute its instructions one by one,
 giving you, the programmer, the opportunity to think about what is happening
@@ -26897,6 +28490,7 @@ The following list defines terms used throughout the rest of
 this @value{CHAPTER}.
 
 @table @dfn
+@cindex stack frame
 @item Stack Frame
 Programs generally call functions during the course of their execution.
 One function can call another, or a function can call itself (recursion).
@@ -26918,6 +28512,7 @@ invoked. Commands that print the call stack print information about
 each stack frame (as detailed later on).
 
 @item Breakpoint
+@cindex breakpoint
 During debugging, you often wish to let the program run until it
 reaches a certain point, and then continue execution from there one
 statement (or instruction) at a time.  The way to do this is to set
@@ -26927,6 +28522,7 @@ take over control of the program's execution.  You can add and remove
 as many breakpoints as you like.
 
 @item Watchpoint
+@cindex watchpoint
 A watchpoint is similar to a breakpoint.  The difference is that
 breakpoints are oriented around the code: stop when a certain point in the
 code is reached.  A watchpoint, however, specifies that program execution
@@ -26958,6 +28554,7 @@ by the higher-level @command{awk} commands.
 
 @node Sample Debugging Session
 @section Sample Debugging Session
+@cindex sample debugging session
 
 In order to illustrate the use of @command{gawk} as a debugger, let's look at a sample
 debugging session.  We will use the @command{awk} implementation of the
@@ -26971,13 +28568,16 @@ as our example.
 
 @node Debugger Invocation
 @subsection How to Start the Debugger
+@cindex starting the debugger
+@cindex debugger, how to start
 
-Starting the debugger is almost exactly like running @command{awk}, except you have to
-pass an additional option @option{--debug} or the corresponding short option @option{-D}.
-The file(s) containing the program and any supporting code are given on the command
-line as arguments to one or more @option{-f} options. (@command{gawk} is not designed
-to debug command-line programs, only programs contained in files.)  In our case,
-we invoke the debugger like this:
+Starting the debugger is almost exactly like running @command{gawk},
+except you have to pass an additional option @option{--debug} or the
+corresponding short option @option{-D}.  The file(s) containing the
+program and any supporting code are given on the command line as arguments
+to one or more @option{-f} options. (@command{gawk} is not designed
+to debug command-line programs, only programs contained in files.)
+In our case, we invoke the debugger like this:
 
 @example
 $ @kbd{gawk -D -f getopt.awk -f join.awk -f uniq.awk inputfile}
@@ -27110,7 +28710,7 @@ gawk> @kbd{p NR}
 
 @noindent
 So we can see that @code{are_equal()} was only called for the second record
-of the file.  Of course, this is because our program contained a rule for
+of the file.  Of course, this is because our program contains a rule for
 @samp{NR == 1}:
 
 @example
@@ -27142,13 +28742,7 @@ This tells us that @command{gawk} is now ready to execute line 67, which
 decides whether to give the lines the special ``field skipping'' treatment
 indicated by the @option{-f} command-line option.  (Notice that we skipped
 from where we were before at line 64 to here, since the condition in line 64
-
-@example
-if (fcount == 0 && charcount == 0)
-@end example
-
-@noindent
-was false.)
+@samp{if (fcount == 0 && charcount == 0)} was false.)
 
 Continuing to step, we now get to the splitting of the current and
 last records:
@@ -27257,7 +28851,7 @@ and problem solved!
 The @command{gawk} debugger command set can be divided into the
 following categories:
 
-@itemize @bullet{}
+@itemize @value{BULLET}
 
 @item
 Breakpoint control
@@ -27283,7 +28877,7 @@ In the following descriptions, commands which may be abbreviated
 show the abbreviation on a second description line.
 A debugger command name may also be truncated if that partial
 name is unambiguous. The debugger has the built-in capability to
-automatically repeat the previous command when just hitting @key{Enter}.
+automatically repeat the previous command just by hitting @key{Enter}.
 This works for the commands @code{list}, @code{next}, @code{nexti}, @code{step}, @code{stepi}
 and @code{continue} executed without any argument.
 
@@ -27310,21 +28904,24 @@ controlling breakpoints are:
 @cindex debugger commands, @code{break}
 @cindex @code{break} debugger command
 @cindex @code{b} debugger command (alias for @code{break})
+@cindex set breakpoint
+@cindex breakpoint, setting
 @item @code{break} [[@var{filename}@code{:}]@var{n} | @var{function}] [@code{"@var{expression}"}]
 @itemx @code{b} [[@var{filename}@code{:}]@var{n} | @var{function}] [@code{"@var{expression}"}]
 Without any argument, set a breakpoint at the next instruction
 to be executed in the selected stack frame.
 Arguments can be one of the following:
 
+@c @asis for docbook
 @c nested table
-@table @var
-@item n
+@table @asis
+@item @var{n}
 Set a breakpoint at line number @var{n} in the current source file.
 
-@item filename@code{:}n
+@item @var{filename}@code{:}@var{n}
 Set a breakpoint at line number @var{n} in source file @var{filename}.
 
-@item function
+@item @var{function}
 Set a breakpoint at entry to (the first instruction of)
 function @var{function}.
 @end table
@@ -27340,6 +28937,8 @@ it continues executing the program.
 
 @cindex debugger commands, @code{clear}
 @cindex @code{clear} debugger command
+@cindex delete breakpoint at location
+@cindex breakpoint at location, how to delete
 @item @code{clear} [[@var{filename}@code{:}]@var{n} | @var{function}]
 Without any argument, delete any breakpoint at the next instruction
 to be executed in the selected stack frame. If the program stops at
@@ -27347,19 +28946,20 @@ a breakpoint, this deletes that breakpoint so that the program
 does not stop at that location again.  Arguments can be one of the following:
 
 @c nested table
-@table @var
-@item n
+@table @asis
+@item @var{n}
 Delete breakpoint(s) set at line number @var{n} in the current source file.
 
-@item filename@code{:}n
+@item @var{filename}@code{:}@var{n}
 Delete breakpoint(s) set at line number @var{n} in source file @var{filename}.
 
-@item function
+@item @var{function}
 Delete breakpoint(s) set at entry to function @var{function}.
 @end table
 
 @cindex debugger commands, @code{condition}
 @cindex @code{condition} debugger command
+@cindex breakpoint condition
 @item @code{condition} @var{n} @code{"@var{expression}"}
 Add a condition to existing breakpoint or watchpoint @var{n}. The
 condition is an @command{awk} expression that the debugger evaluates
@@ -27373,6 +28973,8 @@ watchpoint is made unconditional.
 @cindex debugger commands, @code{delete}
 @cindex @code{delete} debugger command
 @cindex @code{d} debugger command (alias for @code{delete})
+@cindex delete breakpoint by number
+@cindex breakpoint, delete by number
 @item @code{delete} [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 @itemx @code{d} [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 Delete specified breakpoints or a range of breakpoints. Deletes
@@ -27380,6 +28982,8 @@ all defined breakpoints if no argument is supplied.
 
 @cindex debugger commands, @code{disable}
 @cindex @code{disable} debugger command
+@cindex disable breakpoint
+@cindex breakpoint, how to disable or enable
 @item @code{disable} [@var{n1 n2} @dots{} | @var{n}--@var{m}]
 Disable specified breakpoints or a range of breakpoints. Without
 any argument, disables all breakpoints.
@@ -27388,6 +28992,7 @@ any argument, disables all breakpoints.
 @cindex debugger commands, @code{enable}
 @cindex @code{enable} debugger command
 @cindex @code{e} debugger command (alias for @code{enable})
+@cindex enable breakpoint
 @item @code{enable} [@code{del} | @code{once}] [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 @itemx @code{e} [@code{del} | @code{once}] [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 Enable specified breakpoints or a range of breakpoints. Without
@@ -27407,6 +29012,7 @@ the program stops at the breakpoint.
 
 @cindex debugger commands, @code{ignore}
 @cindex @code{ignore} debugger command
+@cindex ignore breakpoint
 @item @code{ignore} @var{n} @var{count}
 Ignore breakpoint number @var{n} the next @var{count} times it is
 hit.
@@ -27415,6 +29021,7 @@ hit.
 @cindex debugger commands, @code{tbreak}
 @cindex @code{tbreak} debugger command
 @cindex @code{t} debugger command (alias for @code{tbreak})
+@cindex temporary breakpoint
 @item @code{tbreak} [[@var{filename}@code{:}]@var{n} | @var{function}]
 @itemx @code{t} [[@var{filename}@code{:}]@var{n} | @var{function}]
 Set a temporary breakpoint (enabled for only one stop).
@@ -27435,6 +29042,8 @@ execution of the program than we saw in our earlier example:
 @cindex @code{silent} debugger command
 @cindex debugger commands, @code{end}
 @cindex @code{end} debugger command
+@cindex breakpoint commands
+@cindex commands to execute at breakpoint
 @item @code{commands} [@var{n}]
 @itemx @code{silent}
 @itemx @dots{}
@@ -27462,6 +29071,7 @@ gawk>
 
 @cindex debugger commands, @code{c} (@code{continue})
 @cindex debugger commands, @code{continue}
+@cindex continue program, in debugger
 @item @code{continue} [@var{count}]
 @itemx @code{c} [@var{count}]
 Resume program execution. If continued from a breakpoint and @var{count} is
@@ -27478,6 +29088,7 @@ Print the returned value.
 @cindex debugger commands, @code{next}
 @cindex @code{next} debugger command
 @cindex @code{n} debugger command (alias for @code{next})
+@cindex single-step execution, in the debugger
 @item @code{next} [@var{count}]
 @itemx @code{n} [@var{count}]
 Continue execution to the next source line, stepping over function calls.
@@ -27572,6 +29183,7 @@ items on the list.
 
 @cindex debugger commands, @code{eval}
 @cindex @code{eval} debugger command
+@cindex evaluate expressions, in debugger
 @item @code{eval "@var{awk statements}"}
 Evaluate @var{awk statements} in the context of the running program.
 You can do anything that an @command{awk} program would do: assign
@@ -27589,6 +29201,7 @@ parameters defined by the program.
 @cindex debugger commands, @code{print}
 @cindex @code{print} debugger command
 @cindex @code{p} debugger command (alias for @code{print})
+@cindex print variables, in debugger
 @item @code{print} @var{var1}[@code{,} @var{var2} @dots{}]
 @itemx @code{p} @var{var1}[@code{,} @var{var2} @dots{}]
 Print the value of a @command{gawk} variable or field.
@@ -27622,10 +29235,11 @@ No newline is printed unless one is specified.
 
 @cindex debugger commands, @code{set}
 @cindex @code{set} debugger command
+@cindex assign values to variables, in debugger
 @item @code{set} @var{var}@code{=}@var{value}
 Assign a constant (number or string) value to an @command{awk} variable
 or field.
-String values must be enclosed between double quotes (@code{"@dots{}"}).
+String values must be enclosed between double quotes (@code{"}@dots{}@code{"}).
 
 You can also set special @command{awk} variables, such as @code{FS},
 @code{NF}, @code{NR}, etc.
@@ -27634,6 +29248,7 @@ You can also set special @command{awk} variables, such as @code{FS},
 @cindex debugger commands, @code{watch}
 @cindex @code{watch} debugger command
 @cindex @code{w} debugger command (alias for @code{watch})
+@cindex set watchpoint
 @item @code{watch} @var{var} | @code{$}@var{n} [@code{"@var{expression}"}]
 @itemx @code{w} @var{var} | @code{$}@var{n} [@code{"@var{expression}"}]
 Add variable @var{var} (or field @code{$@var{n}}) to the watch list.
@@ -27650,12 +29265,14 @@ then the debugger stops execution and prompts for a command. Otherwise,
 
 @cindex debugger commands, @code{undisplay}
 @cindex @code{undisplay} debugger command
+@cindex stop automatic display, in debugger
 @item @code{undisplay} [@var{n}]
 Remove item number @var{n} (or all items, if no argument) from the
 automatic display list.
 
 @cindex debugger commands, @code{unwatch}
 @cindex @code{unwatch} debugger command
+@cindex delete watchpoint
 @item @code{unwatch} [@var{n}]
 Remove item number @var{n} (or all items, if no argument) from the
 watch list.
@@ -27676,12 +29293,14 @@ functions which called the one you are in.  The commands for doing this are:
 @cindex debugger commands, @code{backtrace}
 @cindex @code{backtrace} debugger command
 @cindex @code{bt} debugger command (alias for @code{backtrace})
+@cindex call stack, display in debugger
+@cindex traceback, display in debugger
 @item @code{backtrace} [@var{count}]
 @itemx @code{bt} [@var{count}]
 Print a backtrace of all function calls (stack frames), or innermost @var{count}
 frames if @var{count} > 0. Print the outermost @var{count} frames if
 @var{count} < 0.  The backtrace displays the name and arguments to each
-function, the source file name, and the line number.
+function, the source @value{FN}, and the line number.
 
 @cindex debugger commands, @code{down}
 @cindex @code{down} debugger command
@@ -27695,10 +29314,11 @@ Then select and print the frame.
 @cindex @code{f} debugger command (alias for @code{frame})
 @item @code{frame} [@var{n}]
 @itemx @code{f} [@var{n}]
-Select and print (frame number, function and argument names, source file,
-and the source line) stack frame @var{n}. Frame 0 is the currently executing,
-or @dfn{innermost}, frame (function call), frame 1 is the frame that called the
-innermost one. The highest numbered frame is the one for the main program.
+Select and print stack frame @var{n}.  Frame 0 is the currently executing,
+or @dfn{innermost}, frame (function call), frame 1 is the frame that
+called the innermost one. The highest numbered frame is the one for the
+main program.  The printed information consists of the frame number,
+function and argument names, source file, and the source line.
 
 @cindex debugger commands, @code{up}
 @cindex @code{up} debugger command
@@ -27729,25 +29349,32 @@ The value for @var{what} should be one of the following:
 @c nested table
 @table @code
 @item args
+@cindex show function arguments, in debugger
 Arguments of the selected frame.
 
 @item break
+@cindex show breakpoints
 List all currently set breakpoints.
 
 @item display
+@cindex automatic displays, in debugger
 List all items in the automatic display list.
 
 @item frame
+@cindex describe call stack frame, in debugger
 Description of the selected stack frame.
 
 @item functions
-List all function definitions including source file names and
+@cindex list function definitions, in debugger
+List all function definitions including source @value{FN}s and
 line numbers.
 
 @item locals
+@cindex show local variables, in debugger
 Local variables of the selected frame.
 
 @item source
+@cindex show name of current source file, in debugger
 The name of the current source file. Each time the program stops, the
 current source file is the file containing the current instruction.
 When the debugger first starts, the current source file is the first file
@@ -27756,12 +29383,15 @@ included via the @option{-f} option. The
 be used at any time to change the current source.
 
 @item sources
+@cindex show all source files, in debugger
 List all program sources.
 
 @item variables
+@cindex list all global variables, in debugger
 List all global variables.
 
 @item watch
+@cindex show watchpoints
 List all items in the watch list.
 @end table
 @end table
@@ -27775,6 +29405,8 @@ from a file.  The commands are:
 @cindex debugger commands, @code{option}
 @cindex @code{option} debugger command
 @cindex @code{o} debugger command (alias for @code{option})
+@cindex display debugger options
+@cindex debugger options
 @item @code{option} [@var{name}[@code{=}@var{value}]]
 @itemx @code{o} [@var{name}[@code{=}@var{value}]]
 Without an argument, display the available debugger options
@@ -27784,40 +29416,49 @@ a new value to the named option.
 The available options are:
 
 @c nested table
-@table @code
-@item history_size
+@c asis for docbook
+@table @asis
+@item @code{history_size}
+@cindex debugger history size
 The maximum number of lines to keep in the history file @file{./.gawk_history}.
 The default is 100.
 
-@item listsize
+@item @code{listsize}
+@cindex debugger default list amount
 The number of lines that @code{list} prints. The default is 15.
 
-@item outfile
+@item @code{outfile}
+@cindex redirect @command{gawk} output, in debugger
 Send @command{gawk} output to a file; debugger output still goes
 to standard output. An empty string (@code{""}) resets output to
 standard output.
 
-@item prompt
+@item @code{prompt}
+@cindex debugger prompt
 The debugger prompt. The default is @samp{@w{gawk> }}.
 
-@item save_history @r{[}on @r{|} off@r{]}
+@item @code{save_history} [@code{on} | @code{off}]
+@cindex debugger history file
 Save command history to file @file{./.gawk_history}.
 The default is @code{on}.
 
-@item save_options @r{[}on @r{|} off@r{]}
+@item @code{save_options} [@code{on} | @code{off}]
+@cindex save debugger options
 Save current options to file @file{./.gawkrc} upon exit.
 The default is @code{on}.
 Options are read back in to the next session upon startup.
 
-@item trace @r{[}on @r{|} off@r{]}
+@item @code{trace} [@code{on} | @code{off}]
+@cindex instruction tracing, in debugger
 Turn instruction tracing on or off. The default is @code{off}.
 @end table
 
 @item @code{save} @var{filename}
-Save the commands from the current session to the given file name,
+Save the commands from the current session to the given @value{FN},
 so that they can be replayed using the @command{source} command.
 
 @item @code{source} @var{filename}
+@cindex debugger, read commands from a file
 Run command(s) from a file; an error in any command does not
 terminate execution of subsequent commands. Comments (lines starting
 with @samp{#}) are allowed in a command file.
@@ -27853,7 +29494,7 @@ partial dump of Davide Brini's obfuscated code
 
 @smallexample
 gawk> @kbd{dump}
-@print{} 	# BEGIN
+@print{}        # BEGIN
 @print{} 
 @print{} [     1:0xfcd340] Op_rule             : [in_rule = BEGIN] [source_file = brini.awk]
 @print{} [     1:0xfcc240] Op_push_i           : "~" [MALLOC|STRING|STRCUR]
@@ -27916,8 +29557,8 @@ about the command @var{command}.
 @cindex debugger commands, @code{list}
 @cindex @code{list} debugger command
 @cindex @code{l} debugger command (alias for @code{list})
-@item @code{list} [@code{-} | @code{+} | @var{n} | @var{filename@code{:}n} | @var{n}--@var{m} | @var{function}]
-@itemx @code{l} [@code{-} | @code{+} | @var{n} | @var{filename@code{:}n} | @var{n}--@var{m} | @var{function}]
+@item @code{list} [@code{-} | @code{+} | @var{n} | @var{filename}@code{:}@var{n} | @var{n}--@var{m} | @var{function}]
+@itemx @code{l} [@code{-} | @code{+} | @var{n} | @var{filename}@code{:}@var{n} | @var{n}--@var{m} | @var{function}]
 Print the specified lines (default 15) from the current source file
 or the file named @var{filename}. The possible arguments to @code{list}
 are as follows:
@@ -27937,7 +29578,7 @@ Print lines centered around line number @var{n}.
 @item  @var{n}--@var{m}
 Print lines from @var{n} to @var{m}.
 
-@item @var{filename@code{:}n}
+@item @var{filename}@code{:}@var{n}
 Print lines centered around line number @var{n} in
 source file @var{filename}. This command may change the current source file.
 
@@ -27950,6 +29591,7 @@ function @var{function}. This command may change the current source file.
 @cindex debugger commands, @code{quit}
 @cindex @code{quit} debugger command
 @cindex @code{q} debugger command (alias for @code{quit})
+@cindex exit the debugger
 @item @code{quit}
 @itemx @code{q}
 Exit the debugger.  Debugging is great fun, but sometimes we all have
@@ -27960,7 +29602,7 @@ running a program, the debugger warns you if you accidentally type
 
 @cindex debugger commands, @code{trace}
 @cindex @code{trace} debugger command
-@item @code{trace} @code{on} @r{|} @code{off}
+@item @code{trace} [@code{on} | @code{off}]
 Turn on or off a continuous printing of instructions which are about to
 be executed, along with printing the @command{awk} line which they
 implement.  The default is @code{off}.
@@ -27973,17 +29615,21 @@ fairly self-explanatory, and using @code{stepi} and @code{nexti} while
 
 @node Readline Support
 @section Readline Support
+@cindex command completion, in debugger
+@cindex history expansion, in debugger
 
-If @command{gawk} is compiled with the @code{readline} library, you
-can take advantage of that library's command completion and history expansion
-features. The following types of completion are available:
+If @command{gawk} is compiled with
+@uref{http://cnswww.cns.cwru.edu/php/chet/readline/readline.html,
+the @code{readline} library}, you can take advantage of that library's
+command completion and history expansion features. The following types
+of completion are available:
 
 @table @asis
 @item Command completion
 Command names.
 
-@item Source file name completion
-Source file names. Relevant commands are
+@item Source @value{FN} completion
+Source @value{FN}s. Relevant commands are
 @code{break},
 @code{clear},
 @code{list},
@@ -28013,7 +29659,7 @@ We hope you find the @command{gawk} debugger useful and enjoyable to work with,
 but as with any program, especially in its early releases, it still has
 some limitations.  A few which are worth being aware of are:
 
-@itemize @bullet{}
+@itemize @value{BULLET}
 @item
 At this point, the debugger does not give a detailed explanation of
 what you did wrong when you type in something it doesn't like. Rather, it just
@@ -28026,9 +29672,10 @@ If you perused the dump of opcodes in @ref{Miscellaneous Debugger Commands},
 you will realize that much of the internal manipulation of data
 in @command{gawk}, as in many interpreters, is done on a stack.
 @code{Op_push}, @code{Op_pop}, etc., are the ``bread and butter'' of
-most @command{gawk} code.  Unfortunately, as of now, the @command{gawk}
-debugger does not allow you to examine the stack's contents.
+most @command{gawk} code.
 
+Unfortunately, as of now, the @command{gawk}
+debugger does not allow you to examine the stack's contents.
 That is, the intermediate results of expression evaluation are on the
 stack, but cannot be printed.  Rather, only variables which are defined
 in the program can be printed.  Of course, a workaround for
@@ -28055,433 +29702,329 @@ The @command{gawk} debugger only accepts source supplied with the @option{-f} op
 Look forward to a future release when these and other missing features may
 be added, and of course feel free to try to add them yourself!
 
+@node Debugging Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Programs rarely work correctly the first time.  Finding bugs
+is @dfn{debugging} and a program that helps you find bugs is a
+@dfn{debugger}.  @command{gawk} has a built-in debugger that works very
+similarly to the GNU Debugger, GDB.
+
+@item
+Debuggers let you step through your program one statement at a time,
+examine and change variable and array values, and do a number of other
+things that let understand what your program is actually doing (as
+opposed to what it is supposed to do).
+
+@item
+Like most debuggers, the @command{gawk} debugger works in terms of stack
+frames, and lets you set both breakpoints (stop at a point in the code)
+and watchpoints (stop when a data value changes).
+
+@item
+The debugger command set is fairly complete, providing control over
+breakpoints, execution, viewing and changing data, working with the stack,
+getting information, and other tasks.
+
+@item
+If the @code{readline} library is available when @command{gawk} is
+compiled, it is used by the debugger to provide command-line history
+and editing.
+
+@end itemize
+
 @node Arbitrary Precision Arithmetic
 @chapter Arithmetic and Arbitrary Precision Arithmetic with @command{gawk}
 @cindex arbitrary precision
 @cindex multiple precision
 @cindex infinite precision
-@cindex floating-point numbers, arbitrary precision
-@cindex MPFR
-@cindex GMP
-
-@cindex Knuth, Donald
-@quotation
-@i{There's a credibility gap: We don't know how much of the computer's answers
-to believe. Novice computer users solve this problem by implicitly trusting
-in the computer as an infallible authority; they tend to believe that all
-digits of a printed answer are significant. Disillusioned computer users have
-just the opposite approach; they are constantly afraid that their answers
-are almost meaningless.}@footnote{Donald E.@: Knuth.
-@cite{The Art of Computer Programming}. Volume 2,
-@cite{Seminumerical Algorithms}, third edition,
-1998, ISBN 0-201-89683-4, p.@: 229.}
-@author Donald Knuth
-@end quotation
-
-This @value{CHAPTER} discusses issues that you may encounter
-when performing arithmetic.  It begins by discussing some of
-the general attributes of computer arithmetic, along with how
-this can influence what you see when running @command{awk} programs.
-This discussion applies to all versions of @command{awk}.
-
-The @value{CHAPTER} then moves on to describe @dfn{arbitrary precision
-arithmetic}, a feature which is specific to @command{gawk}.
+@cindex floating-point, numbers@comma{} arbitrary precision
+
+This @value{CHAPTER} introduces some basic concepts relating to
+how computers do arithmetic and briefly lists the features in
+@command{gawk} for performing arbitrary precision floating point
+computations.  It then proceeds to describe floating-point arithmetic,
+which is what @command{awk} uses for all its computations, including a
+discussion of arbitrary precision floating point arithmetic, which is
+a feature available only in @command{gawk}. It continues on to present
+arbitrary precision integers, and concludes with a description of some
+points where @command{gawk} and the POSIX standard are not quite in
+agreement.
 
 @menu
-* General Arithmetic::          An introduction to computer arithmetic.
-* Floating-point Programming::  Effective Floating-point Programming.
-* Gawk and MPFR::               How @command{gawk} provides
-                                arbitrary-precision arithmetic.
-* Arbitrary Precision Floats::  Arbitrary Precision Floating-point Arithmetic
-                                with @command{gawk}.
-* Arbitrary Precision Integers:: Arbitrary Precision Integer Arithmetic with
-                                @command{gawk}.
+* Computer Arithmetic::           A quick intro to computer math.
+* Math Definitions::              Defining terms used.
+* MPFR features::                 The MPFR features in @command{gawk}.
+* FP Math Caution::               Things to know.
+* Arbitrary Precision Integers::  Arbitrary Precision Integer Arithmetic with
+                                  @command{gawk}.
+* POSIX Floating Point Problems:: Standards Versus Existing Practice.
+* Floating point summary::        Summary of floating point discussion.
 @end menu
 
-@node General Arithmetic
+@node Computer Arithmetic
 @section A General Description of Computer Arithmetic
 
-@cindex integers
-@cindex floating-point, numbers
-@cindex numbers, floating-point
-Within computers, there are two kinds of numeric values: @dfn{integers}
-and @dfn{floating-point}.
-In school, integer values were referred to as ``whole'' numbers---that is,
-numbers without any fractional part, such as 1, 42, or @minus{}17.
+Until now, we have worked with data as either numbers or
+strings.  Ultimately, however, computers represent everything in terms
+of @dfn{binary digits}, or @dfn{bits}.  A decimal digit can take on any
+of 10 values: zero through nine.  A binary digit can take on any of two
+values, zero or one.  Using binary, computers (and computer software)
+can represent and manipulate numerical and character data.  In general,
+the more bits you can use to represent a particular thing, the greater
+the range of possible values it can take on.
+
+Modern computers support at least two, and often more, ways to do
+arithmetic.  Each kind of arithmetic uses a different representation
+(organization of the bits) for the numbers.  The kinds of arithmetic
+that interest us are:
+
+@table @asis
+@item Decimal arithmetic
+This is the kind of arithmetic you learned in elementary school, using
+paper and pencil (and/or a calculator). In theory, numbers can have an
+arbitrary number of digits on either side (or both sides) of the decimal
+point, and the results of a computation are always exact.
+
+Some modern system can do decimal arithmetic in hardware, but usually you
+need a special software library to provide access to these instructions.
+There are also libraries that do decimal arithmetic entirely in software.
+
+Despite the fact that some users expect @command{gawk} to be performing
+decimal arithmetic,@footnote{We don't know why they expect this, but
+they do.} it does not do so.
+
+@item Integer arithmetic
+In school, integer values were referred to as ``whole'' numbers---that
+is, numbers without any fractional part, such as 1, 42, or @minus{}17.
 The advantage to integer numbers is that they represent values exactly.
-The disadvantage is that their range is limited.  On most systems,
-this range is @minus{}2,147,483,648 to 2,147,483,647.
-However, many systems now support a range from
-@minus{}9,223,372,036,854,775,808 to 9,223,372,036,854,775,807.
+The disadvantage is that their range is limited.
 
 @cindex unsigned integers
 @cindex integers, unsigned
-Integer values come in two flavors: @dfn{signed} and @dfn{unsigned}.
-Signed values may be negative or positive, with the range of values just
-described.
-Unsigned values are always positive.  On most systems,
-the range is from 0 to 4,294,967,295.
-However, many systems now support a range from
-0 to 18,446,744,073,709,551,615.
-
-@cindex double precision floating-point
-@cindex single precision floating-point
-Floating-point numbers represent what are called ``real'' numbers; i.e.,
-those that do have a fractional part, such as 3.1415927.
-The advantage to floating-point numbers is that they
-can represent a much larger range of values.
-The disadvantage is that there are numbers that they cannot represent
-exactly.
-@command{awk} uses @dfn{double precision} floating-point numbers, which
-can hold more digits than @dfn{single precision}
-floating-point numbers.
-@c Floating-point issues are discussed more fully in
-@c @ref{Floating Point Issues}.
-
-There a several important issues to be aware of, described next.
+In computers, integer values come in two flavors: @dfn{signed} and
+@dfn{unsigned}.  Signed values may be negative or positive, whereas
+unsigned values are always positive (that is, greater than or equal
+to zero).
+
+In computer systems, integer arithmetic is exact, but the possible
+range of values is limited.  Integer arithmetic is generally faster than
+floating point arithmetic.
+
+@item Floating point arithmetic
+Floating-point numbers represent what were called in school ``real''
+numbers; i.e., those that have a fractional part, such as 3.1415927.
+The advantage to floating-point numbers is that they can represent a
+much larger range of values than can integers.  The disadvantage is that
+there are numbers that they cannot represent exactly.
+
+Modern systems support floating point arithmetic in hardware, with a
+limited range of values.  There are software libraries that allow
+the use of arbitrary precision floating point calculations.
+
+POSIX @command{awk} uses @dfn{double precision} floating-point numbers, which
+can hold more digits than @dfn{single precision} floating-point numbers.
+@command{gawk} has facilities for performing arbitrary precision floating
+point arithmetic, which we describe in more detail shortly.
+@end table
 
-@menu
-* Floating Point Issues::       Stuff to know about floating-point numbers.
-* Integer Programming::         Effective integer programming.
-@end menu
+Computers work with integer and floating point values of different
+ranges. Integer values are usually either 32 or 64 bits in size.  Single
+precision floating point values occupy 32 bits, whereas double precision
+floating point values occupy 64 bits.  Floating point values are always
+signed. The possible ranges of values are shown in the following table.
+
+@multitable @columnfractions .34 .33 .33
+@headitem Numeric representation @tab Miniumum value @tab Maximum value
+@item 32-bit signed integer @tab @minus{}2,147,483,648 @tab 2,147,483,647
+@item 32-bit unsigned integer @tab 0 @tab 4,294,967,295
+@item 64-bit signed integer @tab @minus{}9,223,372,036,854,775,808 @tab 9,223,372,036,854,775,807
+@item 64-bit unsigned integer @tab 0 @tab 18,446,744,073,709,551,615
+@item Single precision floating point (approximate) @tab @code{1.175494e-38} @tab @code{3.402823e+38}
+@item Double precision floating point (approximate) @tab @code{2.225074e-308} @tab @code{1.797693e+308}
+@end multitable
 
-@node Floating Point Issues
-@subsection Floating-Point Number Caveats
+@node Math Definitions
+@section Other Stuff To Know
 
-This @value{SECTION} describes some of the issues
-involved in using floating-point numbers.
+The rest of this @value{CHAPTER} uses a number of terms. Here are some
+informal definitions that should help you work your way through the material
+here.
 
-There is a very nice
-@uref{http://www.validlab.com/goldberg/paper.pdf, paper on floating-point arithmetic}
-by David Goldberg,
-``What Every Computer Scientist Should Know About Floating-point Arithmetic,''
-@cite{ACM Computing Surveys} @strong{23}, 1 (1991-03), 5-48.
-This is worth reading if you are interested in the details,
-but it does require a background in computer science.
+@table @dfn
+@item Accuracy
+A floating-point calculation's accuracy is how close it comes
+to the real (paper and pencil) value.
 
-@menu
-* String Conversion Precision:: The String Value Can Lie.
-* Unexpected Results::          Floating Point Numbers Are Not Abstract
-                                Numbers.
-* POSIX Floating Point Problems:: Standards Versus Existing Practice.
-@end menu
+@item Error
+The difference between what the result of a computation ``should be''
+and what it actually is.  It is best to minimize error as much
+as possible.
 
-@node String Conversion Precision
-@subsubsection The String Value Can Lie
+@item Exponent
+The order of magnitude of a value;
+some number of bits in a floating-point value store the exponent.
 
-Internally, @command{awk} keeps both the numeric value
-(double precision floating-point) and the string value for a variable.
-Separately, @command{awk} keeps
-track of what type the variable has
-(@pxref{Typing and Comparison}),
-which plays a role in how variables are used in comparisons.
+@item Inf
+A special value representing infinity. Operations involving another
+number and infinity produce infinity.
 
-It is important to note that the string value for a number may not
-reflect the full value (all the digits) that the numeric value
-actually contains.
-The following program, @file{values.awk}, illustrates this:
+@item NaN
+``Not A Number.'' A special value indicating a result that can't
+happen in real math, but that can happen in floating-point computations.
 
-@example
-@{
-   sum = $1 + $2
-   # see it for what it is
-   printf("sum = %.12g\n", sum)
-   # use CONVFMT
-   a = "<" sum ">"
-   print "a =", a
-   # use OFMT
-   print "sum =", sum
-@}
-@end example
+@item Normalized
+How the significand (see later in this list) is usually stored. The
+value is adjusted so that the first bit is one, and then that leading
+one is assumed instead of physically stored.  This provides one
+extra bit of precision.
 
-@noindent
-This program shows the full value of the sum of @code{$1} and @code{$2}
-using @code{printf}, and then prints the string values obtained
-from both automatic conversion (via @code{CONVFMT}) and
-from printing (via @code{OFMT}).
+@item Precision
+The number of bits used to represent a floating-point number.
+The more bits, the more digits you can represent.
+Binary and decimal precisions are related approximately, according to the
+formula:
 
-Here is what happens when the program is run:
+@display
+@iftex
+@math{prec = 3.322 @cdot dps}
+@end iftex
+@ifnottex
+@ifnotdocbook
+@var{prec} = 3.322 * @var{dps}
+@end ifnotdocbook
+@end ifnottex
+@docbook
+<emphasis>prec</emphasis> = 3.322 &sdot; <emphasis>dps</emphasis> @c
+@end docbook
+@end display
 
-@example
-$ @kbd{echo 3.654321 1.2345678 | awk -f values.awk}
-@print{} sum = 4.8888888
-@print{} a = <4.88889>
-@print{} sum = 4.88889
-@end example
+@noindent
+Here, @var{prec} denotes the binary precision
+(measured in bits) and @var{dps} (short for decimal places)
+is the decimal digits.
+
+@item Rounding mode
+How numbers are rounded up or down when necessary.
+More details are provided later.
+
+@item Significand
+A floating point value consists the significand multiplied by 10
+to the power of the exponent. For example, in @code{1.2345e67},
+the significand is @code{1.2345}.
+
+@item Stability
+From @uref{http://en.wikipedia.org/wiki/Numerical_stability,
+the Wikipedia article on numerical stability}:
+``Calculations that can be proven not to magnify approximation errors
+are called @dfn{numerically stable}.''
+@end table
 
-This makes it clear that the full numeric value is different from
-what the default string representations show.
+See @uref{http://en.wikipedia.org/wiki/Accuracy_and_precision,
+the Wikipedia article on accuracy and precision} for more information
+on some of those terms.
 
-@code{CONVFMT}'s default value is @code{"%.6g"}, which yields a value with
-at most six significant digits.  For some applications, you might want to
-change it to specify more precision.
-On most modern machines, most of the time,
-17 digits is enough to capture a floating-point number's
-value exactly.@footnote{Pathological cases can require up to
-752 digits (!), but we doubt that you need to worry about this.}
+On modern systems, floating-point hardware uses the representation and
+operations defined by the IEEE 754 standard.
+Three of the standard IEEE 754 types are 32-bit single precision,
+64-bit double precision and 128-bit quadruple precision.
+The standard also specifies extended precision formats
+to allow greater precisions and larger exponent ranges.
+(@command{awk} uses only the 64-bit double precision format.)
 
-@node Unexpected Results
-@subsubsection Floating Point Numbers Are Not Abstract Numbers
-
-@cindex floating-point, numbers
-Unlike numbers in the abstract sense (such as what you studied in high school
-or college arithmetic), numbers stored in computers are limited in certain ways.
-They cannot represent an infinite number of digits, nor can they always
-represent things exactly.
-In particular,
-floating-point numbers cannot
-always represent values exactly.  Here is an example:
-
-@example
-$ @kbd{awk '@{ printf("%010d\n", $1 * 100) @}'}
-515.79
-@print{} 0000051579
-515.80
-@print{} 0000051579
-515.81
-@print{} 0000051580
-515.82
-@print{} 0000051582
-@kbd{Ctrl-d}
-@end example
+@ref{table-ieee-formats} lists the precision and exponent
+field values for the basic IEEE 754 binary formats:
 
-@noindent
-This shows that some values can be represented exactly,
-whereas others are only approximated.  This is not a ``bug''
-in @command{awk}, but simply an artifact of how computers
-represent numbers.
+@float Table,table-ieee-formats
+@caption{Basic IEEE Format Context Values}
+@multitable @columnfractions .20 .20 .20 .20 .20
+@headitem Name @tab Total bits @tab Precision @tab emin @tab emax
+@item Single @tab 32 @tab 24 @tab @minus{}126 @tab +127 
+@item Double @tab 64 @tab 53 @tab @minus{}1022 @tab +1023
+@item Quadruple @tab 128 @tab 113 @tab @minus{}16382 @tab +16383
+@end multitable
+@end float
 
 @quotation NOTE
-It cannot be emphasized enough that the behavior just
-described is fundamental to modern computers. You will
-see this kind of thing happen in @emph{any} programming
-language using hardware floating-point numbers. It is @emph{not}
-a bug in @command{gawk}, nor is it something that can be ``just
-fixed.''
+The precision numbers include the implied leading one that gives them
+one extra bit of significand.
 @end quotation
 
-@cindex negative zero
-@cindex positive zero
-@cindex zero@comma{} negative vs.@: positive
-Another peculiarity of floating-point numbers on modern systems
-is that they often have more than one representation for the number zero!
-In particular, it is possible to represent ``minus zero'' as well as
-regular, or ``positive'' zero.
-
-This example shows that negative and positive zero are distinct values
-when stored internally, but that they are in fact equal to each other,
-as well as to ``regular'' zero:
-
-@example
-$ @kbd{gawk 'BEGIN @{ mz = -0 ; pz = 0}
-> @kbd{printf "-0 = %g, +0 = %g, (-0 == +0) -> %d\n", mz, pz, mz == pz}
-> @kbd{printf "mz == 0 -> %d, pz == 0 -> %d\n", mz == 0, pz == 0}
-> @kbd{@}'}
-@print{} -0 = -0, +0 = 0, (-0 == +0) -> 1
-@print{} mz == 0 -> 1, pz == 0 -> 1
-@end example
-
-It helps to keep this in mind should you process numeric data
-that contains negative zero values; the fact that the zero is negative
-is noted and can affect comparisons.
-
-@node POSIX Floating Point Problems
-@subsubsection Standards Versus Existing Practice
+@node MPFR features
+@section Arbitrary Precison Arithmetic Features In @command{gawk}
 
-Historically, @command{awk} has converted any non-numeric looking string
-to the numeric value zero, when required.  Furthermore, the original
-definition of the language and the original POSIX standards specified that
-@command{awk} only understands decimal numbers (base 10), and not octal
-(base 8) or hexadecimal numbers (base 16).
-
-Changes in the language of the
-2001 and 2004 POSIX standards can be interpreted to imply that @command{awk}
-should support additional features.  These features are:
-
-@itemize @bullet
-@item
-Interpretation of floating point data values specified in hexadecimal
-notation (@samp{0xDEADBEEF}). (Note: data values, @emph{not}
-source code constants.)
-
-@item
-Support for the special IEEE 754 floating point values ``Not A Number''
-(NaN), positive Infinity (``inf'') and negative Infinity (``@minus{}inf'').
-In particular, the format for these values is as specified by the ISO 1999
-C standard, which ignores case and can allow machine-dependent additional
-characters after the @samp{nan} and allow either @samp{inf} or @samp{infinity}.
-@end itemize
-
-The first problem is that both of these are clear changes to historical
-practice:
-
-@itemize @bullet
-@item
-The @command{gawk} maintainer feels that supporting hexadecimal floating
-point values, in particular, is ugly, and was never intended by the
-original designers to be part of the language.
-
-@item
-Allowing completely alphabetic strings to have valid numeric
-values is also a very severe departure from historical practice.
-@end itemize
-
-The second problem is that the @code{gawk} maintainer feels that this
-interpretation of the standard, which requires a certain amount of
-``language lawyering'' to arrive at in the first place, was not even
-intended by the standard developers.  In other words, ``we see how you
-got where you are, but we don't think that that's where you want to be.''
-
-Recognizing the above issues, but attempting to provide compatibility
-with the earlier versions of the standard,
-the 2008 POSIX standard added explicit wording to allow, but not require,
-that @command{awk} support hexadecimal floating point values and
-special values for ``Not A Number'' and infinity.
-
-Although the @command{gawk} maintainer continues to feel that
-providing those features is inadvisable,
-nevertheless, on systems that support IEEE floating point, it seems
-reasonable to provide @emph{some} way to support NaN and Infinity values.
-The solution implemented in @command{gawk} is as follows:
-
-@itemize @bullet
-@item
-With the @option{--posix} command-line option, @command{gawk} becomes
-``hands off.'' String values are passed directly to the system library's
-@code{strtod()} function, and if it successfully returns a numeric value,
-that is what's used.@footnote{You asked for it, you got it.}
-By definition, the results are not portable across
-different systems.  They are also a little surprising:
+By default, @command{gawk} uses the double precision floating point values
+supplied by the hardware of the system it runs on.  However, if it was
+compiled to do, @command{gawk} uses the @uref{http://www.mpfr.org, GNU
+MPFR} and @uref{http://gmplib.org, GNU MP} (GMP) libraries for arbitrary
+precision arithmetic on numbers.  You can see if MPFR support is available
+like so:
 
 @example
-$ @kbd{echo nanny | gawk --posix '@{ print $1 + 0 @}'}
-@print{} nan
-$ @kbd{echo 0xDeadBeef | gawk --posix '@{ print $1 + 0 @}'}
-@print{} 3735928559
+$ @kbd{gawk --version}
+@print{} GNU Awk 4.1.1, API: 1.1 (GNU MPFR 3.1.0-p3, GNU MP 5.0.2)
+@print{} Copyright (C) 1989, 1991-2014 Free Software Foundation.
+@dots{}
 @end example
 
-@item
-Without @option{--posix}, @command{gawk} interprets the four strings
-@samp{+inf},
-@samp{-inf},
-@samp{+nan},
-and
-@samp{-nan}
-specially, producing the corresponding special numeric values.
-The leading sign acts a signal to @command{gawk} (and the user)
-that the value is really numeric.  Hexadecimal floating point is
-not supported (unless you also use @option{--non-decimal-data},
-which is @emph{not} recommended). For example:
-
-@example
-$ @kbd{echo nanny | gawk '@{ print $1 + 0 @}'}
-@print{} 0
-$ @kbd{echo +nan | gawk '@{ print $1 + 0 @}'}
-@print{} nan
-$ @kbd{echo 0xDeadBeef | gawk '@{ print $1 + 0 @}'}
-@print{} 0
-@end example
+@noindent
+(You may see different version numbers than what's shown here. That's OK;
+what's important is to see that GNU MPFR and GNU MP are listed in
+the output.)
 
-@command{gawk} does ignore case in the four special values.
-Thus @samp{+nan} and @samp{+NaN} are the same.
-@end itemize
+Additionally, there are a few elements available in the @code{PROCINFO}
+array to provide information about the MPFR and GMP libraries
+(@pxref{Auto-set}).
 
-@node Integer Programming
-@subsection Mixing Integers And Floating-point
-
-As has been mentioned already, @command{awk} uses hardware double
-precision with 64-bit IEEE binary floating-point representation
-for numbers on most systems. A large integer like 9,007,199,254,740,997
-has a binary representation that, although finite, is more than 53 bits long;
-it must also be rounded to 53 bits.
-The biggest integer that can be stored in a C @code{double} is usually the same
-as the largest possible value of a @code{double}. If your system @code{double}
-is an IEEE 64-bit @code{double}, this largest possible value is an integer and
-can be represented precisely.  What more should one know about integers?
-
-If you want to know what is the largest integer, such that it and
-all smaller integers can be stored in 64-bit doubles without losing precision,
-then the answer is
-@iftex
-@math{2^{53}}.
-@end iftex
-@ifnottex
-2^53.
-@end ifnottex
-The next representable number is the even number
-@iftex
-@math{2^{53} + 2},
-@end iftex
-@ifnottex
-2^53 + 2,
-@end ifnottex
-meaning it is unlikely that you will be able to make
-@command{gawk} print
-@iftex
-@math{2^{53} + 1}
-@end iftex
-@ifnottex
-2^53 + 1
-@end ifnottex
-in integer format.
-The range of integers exactly representable by a 64-bit double
-is
-@iftex
-@math{[-2^{53}, 2^{53}]}.
-@end iftex
-@ifnottex
-[@minus{}2^53, 2^53].
-@end ifnottex
-If you ever see an integer outside this range in @command{awk}
-using 64-bit doubles, you have reason to be very suspicious about
-the accuracy of the output. Here is a simple program with erroneous output:
+The MPFR library provides precise control over precisions and rounding
+modes, and gives correctly rounded, reproducible, platform-independent
+results.  With either of the command-line options @option{--bignum} or
+@option{-M}, all floating-point arithmetic operators and numeric functions
+can yield results to any desired precision level supported by MPFR.
 
-@example
-$ @kbd{gawk 'BEGIN @{ i = 2^53 - 1; for (j = 0; j < 4; j++) print i + j @}'}
-@print{} 9007199254740991
-@print{} 9007199254740992
-@print{} 9007199254740992
-@print{} 9007199254740994
-@end example
+Two built-in variables, @code{PREC} and @code{ROUNDMODE},
+provide control over the working precision and the rounding mode.
+The precision and the rounding mode are set globally for every operation
+to follow.
+@xref{Auto-set}, for more information.
 
-The lesson is to not assume that any large integer printed by @command{awk}
-represents an exact result from your computation, especially if it wraps
-around on your screen.
+@node FP Math Caution
+@section Floating Point Arithmetic: Caveat Emptor!
 
-@node Floating-point Programming
-@section Understanding Floating-point Programming
+@quotation
+Math class is tough!
+@author Late 1980's Barbie
+@end quotation
 
-Numerical programming is an extensive area; if you need to develop
-sophisticated numerical algorithms then @command{gawk} may not be
-the ideal tool, and this documentation may not be sufficient.
-It might require digesting a book or two@footnote{One recommended title is
-@cite{Numerical Computing with IEEE Floating Point Arithmetic}, Michael L.@:
-Overton, Society for Industrial and Applied Mathematics, 2004.
-ISBN: 0-89871-482-6, ISBN-13: 978-0-89871-482-1. See
-@uref{http://www.cs.nyu.edu/cs/faculty/overton/book}.}
-to really internalize how to compute
-with ideal accuracy and precision,
-and the result often depends on the particular application.
+This @value{SECTION} provides a high level overview of the issues
+involved when doing lots of floating-point arithmetic.@footnote{There
+is a very nice @uref{http://www.validlab.com/goldberg/paper.pdf,
+paper on floating-point arithmetic} by David Goldberg, ``What Every
+Computer Scientist Should Know About Floating-point Arithmetic,''
+@cite{ACM Computing Surveys} @strong{23}, 1 (1991-03), 5-48.  This is
+worth reading if you are interested in the details, but it does require
+a background in computer science.}
+The discussion applies to both hardware and arbitrary-precision
+floating-point arithmetic.
 
-@quotation NOTE
-A floating-point calculation's @dfn{accuracy} is how close it comes
-to the real value.  This is as opposed to the @dfn{precision}, which
-usually refers to the number of bits used to represent the number
-(see @uref{http://en.wikipedia.org/wiki/Accuracy_and_precision,
-the Wikipedia article} for more information).
+@quotation CAUTION
+The material here is purposely general. If you need to do serious
+computer arithmetic, you should do some research first, and not
+rely just on what we tell you.
 @end quotation
 
-There are two options for doing floating-point calculations:
-hardware floating-point (as used by standard @command{awk} and
-the default for @command{gawk}), and @dfn{arbitrary-precision}
-floating-point, which is software based.
-From this point forward, this @value{CHAPTER}
-aims to provide enough information to understand both, and then
-will focus on @command{gawk}'s facilities for the latter.@footnote{If you
-are interested in other tools that perform arbitrary precision arithmetic,
-you may want to investigate the POSIX @command{bc} tool. See
-@uref{http://pubs.opengroup.org/onlinepubs/009695399/utilities/bc.html,
-the POSIX specification for it}, for more information.}
+@menu
+* Inexactness of computations:: Floating point math is not exact.
+* Getting Accuracy::            Getting more accuracy takes some work.
+* Try To Round::                Add digits and round.
+* Setting precision::           How to set the precision.
+* Setting the rounding mode::   How to set the rounding mode.
+@end menu
+
+@node Inexactness of computations
+@subsection Floating Point Arithmetic Is Not Exact
 
 Binary floating-point representations and arithmetic are inexact.
 Simple values like 0.1 cannot be precisely represented using
@@ -28493,7 +30036,16 @@ floating-point, you can set the precision before starting a computation,
 but then you cannot be sure of the number of significant decimal places
 in the final result.
 
-Sometimes, before you start to write any code, you should think more
+@menu
+* Inexact representation::      Numbers are not exactly represented.
+* Comparing FP Values::         How to compare floating point values.
+* Errors accumulate::           Errors get bigger as they go.
+@end menu
+
+@node Inexact representation
+@subsubsection Many Numbers Cannot Be Represented Exactly
+
+So, before you start to write any code, you should think
 about what you really want and what's really happening. Consider the
 two numbers in the following example:
 
@@ -28523,21 +30075,42 @@ you can always specify how much precision you would like in your output.
 Usually this is a format string like @code{"%.15g"}, which when
 used in the previous example, produces an output identical to the input.
 
+@node Comparing FP Values
+@subsubsection Be Careful Comparing Values
+
 Because the underlying representation can be a little bit off from the exact value,
-comparing floating-point values to see if they are equal is generally not a good idea.
-Here is an example where it does not work like you expect:
+comparing floating-point values to see if they are exactly equal is generally a bad idea.
+Here is an example where it does not work like you would expect:
 
 @example 
 $ @kbd{gawk 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
 @print{} 0
 @end example
 
-The loss of accuracy during a single computation with floating-point numbers
-usually isn't enough to worry about. However, if you compute a value
-which is the result of a sequence of floating point operations,
+The general wisdom when comparing floating-point values is to see if
+they are within some small range of each other (called a @dfn{delta},
+or @dfn{tolerance}).
+You have to decide how small a delta is important to you. Code to do
+this looks something like this:
+
+@example
+delta = 0.00001                 # for example
+difference = abs(a) - abs(b)    # subtract the two values
+if (difference < delta)
+    # all ok
+else
+    # not ok
+@end example
+
+@node Errors accumulate
+@subsubsection Errors Accumulate
+
+The loss of accuracy during a single computation with floating-point
+numbers usually isn't enough to worry about. However, if you compute a
+value which is the result of a sequence of floating point operations,
 the error can accumulate and greatly affect the computation itself.
-Here is an attempt to compute the value of the constant
-@value{PI} using one of its many series representations:
+Here is an attempt to compute the value of @value{PI} using one of its
+many series representations:
 
 @example
 BEGIN @{
@@ -28551,8 +30124,8 @@ BEGIN @{
 @}
 @end example
 
-When run, the early errors propagating through later computations
-cause the loop to terminate prematurely after an attempt to divide by zero.
+When run, the early errors propagate through later computations,
+causing the loop to terminate prematurely after attempting to divide by zero:
 
 @example
 $ @kbd{gawk -f pi.awk}
@@ -28579,23 +30152,88 @@ $ @kbd{gawk 'BEGIN @{}
 @print{} 4
 @end example
 
-Can computation using arbitrary precision help with the previous examples?
-If you are impatient to know, see
-@ref{Exact Arithmetic}.
+@node Getting Accuracy
+@subsection Getting The Accuracy You Need
+
+Can arbitrary precision arithmetic give exact results? There are
+no easy answers. The standard rules of algebra often do not apply
+when using floating-point arithmetic.
+Among other things, the distributive and associative laws
+do not hold completely, and order of operation may be important
+for your computation. Rounding error, cumulative precision loss
+and underflow are often troublesome.
+
+When @command{gawk} tests the expressions @samp{0.1 + 12.2} and
+@samp{12.3} for equality using the machine double precision arithmetic,
+it decides that they are not equal!  (@xref{Comparing FP Values}.)
+You can get the result you want by increasing the precision; 56 bits in
+this case does the job:
+
+@example 
+$ @kbd{gawk -M -v PREC=56 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
+@print{} 1
+@end example
+
+If adding more bits is good, perhaps adding even more bits of
+precision is better?
+Here is what happens if we use an even larger value of @code{PREC}:
+
+@example 
+$ @kbd{gawk -M -v PREC=201 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
+@print{} 0
+@end example
+
+This is not a bug in @command{gawk} or in the MPFR library.
+It is easy to forget that the finite number of bits used to store the value
+is often just an approximation after proper rounding.
+The test for equality succeeds if and only if @emph{all} bits in the two operands
+are exactly the same. Since this is not necessarily true after floating-point
+computations with a particular precision and effective rounding rule,
+a straight test for equality may not work. Instead, compare the
+two numbers to see if they are within the desirable delta of each other.
+
+In applications where 15 or fewer decimal places suffice,
+hardware double precision arithmetic can be adequate, and is usually much faster.
+But you need to keep in mind that every floating-point operation
+can suffer a new rounding error with catastrophic consequences as illustrated
+by our earlier attempt to compute the value of @value{PI}.
+Extra precision can greatly enhance the stability and the accuracy
+of your computation in such cases.
+
+Repeated addition is not necessarily equivalent to multiplication
+in floating-point arithmetic. In the example in
+@ref{Errors accumulate}:
+
+@example
+$ @kbd{gawk 'BEGIN @{}
+>   @kbd{for (d = 1.1; d <= 1.5; d += 0.1)    # loop five times (?)}
+>       @kbd{i++}
+>   @kbd{print i}
+> @kbd{@}'}
+@print{} 4
+@end example
+
+@noindent
+you may or may not succeed in getting the correct result by choosing
+an arbitrarily large value for @code{PREC}. Reformulation of
+the problem at hand is often the correct approach in such situations.
+
+@node Try To Round
+@subsection Try A Few Extra Bits of Precision and Rounding
 
 Instead of arbitrary precision floating-point arithmetic,
 often all you need is an adjustment of your logic
 or a different order for the operations in your calculation.
-The stability and the accuracy of the computation of the constant @value{PI}
+The stability and the accuracy of the computation of @value{PI}
 in the earlier example can be enhanced by using the following
 simple algebraic transformation:
 
 @example
-(sqrt(x * x + 1) - 1) / x = x / (sqrt(x * x + 1) + 1)
+(sqrt(x * x + 1) - 1) / x @equiv{} x / (sqrt(x * x + 1) + 1)
 @end example
 
 @noindent
-After making this, change the program does converge to
+After making this, change the program converges to
 @value{PI} in under 30 iterations:
 
 @example
@@ -28610,340 +30248,22 @@ $ @kbd{gawk -f pi2.awk}
 @print{} 3.141592653589797
 @end example
 
-There is no need to be unduly suspicious about the results from
-floating-point arithmetic. The lesson to remember is that
-floating-point arithmetic is always more complex than arithmetic using
-pencil and paper. In order to take advantage of the power
-of computer floating-point, you need to know its limitations
-and work within them. For most casual use of floating-point arithmetic,
-you will often get the expected result in the end if you simply round
-the display of your final results to the correct number of significant
-decimal digits.
-
-As general advice, avoid presenting numerical data in a manner that
-implies better precision than is actually the case.
-
-@menu
-* Floating-point Representation:: Binary floating-point representation.
-* Floating-point Context::        Floating-point context.
-* Rounding Mode::                 Floating-point rounding mode.
-@end menu
-
-@node Floating-point Representation
-@subsection Binary Floating-point Representation
-@cindex IEEE-754 format
-
-Although floating-point representations vary from machine to machine,
-the most commonly encountered representation is that defined by the
-IEEE 754 Standard. An IEEE-754 format value has three components:
-
-@itemize @bullet
-@item
-A sign bit telling whether the number is positive or negative.
-
-@item
-An @dfn{exponent}, @var{e}, giving its order of magnitude.
-
-@item
-A @dfn{significand}, @var{s},
-specifying the actual digits of the number.
-@end itemize
-
-The value of the
-number is then
-@iftex
-@math{s @cdot 2^e}.
-@end iftex
-@ifnottex
-@var{s * 2^e}.
-@end ifnottex
-The first bit of a non-zero binary significand
-is always one, so the significand in an IEEE-754 format only includes the
-fractional part, leaving the leading one implicit.
-The significand is stored in @dfn{normalized} format,
-which means that the first bit is always a one.
-
-Three of the standard IEEE-754 types are 32-bit single precision,
-64-bit double precision and 128-bit quadruple precision.
-The standard also specifies extended precision formats
-to allow greater precisions and larger exponent ranges.
-
-@node Floating-point Context
-@subsection Floating-point Context
-@cindex context, floating-point
-
-A floating-point @dfn{context} defines the environment for arithmetic operations.
-It governs precision, sets rules for rounding, and limits the range for exponents.
-The context has the following primary components:
-
-@table @dfn
-@item Precision
-Precision of the floating-point format in bits.
-
-@item emax
-Maximum exponent allowed for the format.
-
-@item emin
-Minimum exponent allowed for the format.
-
-@item Underflow behavior
-The format may or may not support gradual underflow.
-
-@item Rounding
-The rounding mode of the context.
-@end table
-
-@ref{table-ieee-formats} lists the precision and exponent
-field values for the basic IEEE-754 binary formats:
-
-@float Table,table-ieee-formats
-@caption{Basic IEEE Format Context Values}
-@multitable @columnfractions .20 .20 .20 .20 .20
-@headitem Name @tab Total bits @tab Precision @tab emin @tab emax
-@item Single @tab 32 @tab 24 @tab @minus{}126 @tab +127 
-@item Double @tab 64 @tab 53 @tab @minus{}1022 @tab +1023
-@item Quadruple @tab 128 @tab 113 @tab @minus{}16382 @tab +16383
-@end multitable
-@end float
-
-@quotation NOTE
-The precision numbers include the implied leading one that gives them
-one extra bit of significand.
-@end quotation
-
-A floating-point context can also determine which signals are treated
-as exceptions, and can set rules for arithmetic with special values.
-Please consult the IEEE-754 standard or other resources for details.
-
-@command{gawk} ordinarily uses the hardware double precision
-representation for numbers.  On most systems, this is IEEE-754
-floating-point format, corresponding to 64-bit binary with 53 bits
-of precision.
-
-@quotation NOTE
-In case an underflow occurs, the standard allows, but does not require,
-the result from an arithmetic operation to be a number smaller than
-the smallest nonzero normalized number. Such numbers do
-not have as many significant digits as normal numbers, and are called
-@dfn{denormals} or @dfn{subnormals}. The alternative, simply returning a zero,
-is called @dfn{flush to zero}. The basic IEEE-754 binary formats
-support subnormal numbers.
-@end quotation
-
-@node Rounding Mode
-@subsection Floating-point Rounding Mode
-@cindex rounding mode, floating-point
-
-The @dfn{rounding mode} specifies the behavior for the results of numerical
-operations when discarding extra precision. Each rounding mode indicates
-how the least significant returned digit of a rounded result is to
-be calculated.
-@ref{table-rounding-modes} lists the IEEE-754 defined
-rounding modes:
-
-@float Table,table-rounding-modes
-@caption{IEEE 754 Rounding Modes}
-@multitable @columnfractions .45 .55
-@headitem Rounding Mode @tab IEEE Name
-@item Round to nearest, ties to even @tab @code{roundTiesToEven}
-@item Round toward plus Infinity @tab @code{roundTowardPositive}
-@item Round toward negative Infinity @tab @code{roundTowardNegative}
-@item Round toward zero @tab @code{roundTowardZero}
-@item Round to nearest, ties away from zero @tab @code{roundTiesToAway}
-@end multitable
-@end float
-
-The default mode @code{roundTiesToEven} is the most preferred,
-but the least intuitive. This method does the obvious thing for most values,
-by rounding them up or down to the nearest digit.
-For example, rounding 1.132 to two digits yields 1.13,
-and rounding 1.157 yields 1.16.
-
-However, when it comes to rounding a value that is exactly halfway between,
-things do not work the way you probably learned in school.
-In this case, the number is rounded to the nearest even digit.
-So rounding 0.125 to two digits rounds down to 0.12,
-but rounding 0.6875 to three digits rounds up to 0.688.
-You probably have already encountered this rounding mode when
-using @code{printf} to format floating-point numbers.
-For example:
-
-@example
-BEGIN @{
-    x = -4.5
-    for (i = 1; i < 10; i++) @{
-        x += 1.0
-        printf("%4.1f => %2.0f\n", x, x)
-    @}
-@}
-@end example
-
-@noindent
-produces the following output when run on the author's system:@footnote{It
-is possible for the output to be completely different if the
-C library in your system does not use the IEEE-754 even-rounding
-rule to round halfway cases for @code{printf}.}
-
-@example
--3.5 => -4
--2.5 => -2
--1.5 => -2
--0.5 => 0
- 0.5 => 0
- 1.5 => 2
- 2.5 => 2
- 3.5 => 4
- 4.5 => 4
-@end example
-
-The theory behind the rounding mode @code{roundTiesToEven} is that
-it more or less evenly distributes upward and downward rounds
-of exact halves, which might cause any round-off error
-to cancel itself out. This is the default rounding mode used
-in IEEE-754 computing functions and operators.
-
-The other rounding modes are rarely used.
-Round toward positive infinity (@code{roundTowardPositive})
-and round toward negative infinity (@code{roundTowardNegative})
-are often used to implement interval arithmetic,
-where you adjust the rounding mode to calculate upper and lower bounds
-for the range of output. The @code{roundTowardZero}
-mode can be used for converting floating-point numbers to integers.
-The rounding mode @code{roundTiesToAway} rounds the result to the
-nearest number and selects the number with the larger magnitude
-if a tie occurs.
-
-Some numerical analysts will tell you that your choice of rounding style
-has tremendous impact on the final outcome, and advise you to wait until
-final output for any rounding. Instead, you can often avoid round-off error problems by
-setting the precision initially to some value sufficiently larger than
-the final desired precision, so that the accumulation of round-off error
-does not influence the outcome.
-If you suspect that results from your computation are
-sensitive to accumulation of round-off error,
-one way to be sure is to look for a significant difference in output
-when you change the rounding mode.
-
-@node Gawk and MPFR
-@section @command{gawk} + MPFR = Powerful Arithmetic
-
-The rest of this @value{CHAPTER} describes how to use the arbitrary precision
-(also known as @dfn{multiple precision} or @dfn{infinite precision}) numeric
-capabilities in @command{gawk} to produce maximally accurate results
-when you need it.
-
-But first you should check if your version of
-@command{gawk} supports arbitrary precision arithmetic.
-The easiest way to find out is to look at the output of
-the following command:
-
-@example
-$ @kbd{gawk --version}
-@print{} GNU Awk 4.1.0, API: 1.0 (GNU MPFR 3.1.0-p3, GNU MP 5.0.2)
-@print{} Copyright (C) 1989, 1991-2013 Free Software Foundation.
-@dots{}
-@end example
-
-@command{gawk} uses the
-@uref{http://www.mpfr.org, GNU MPFR}
-and
-@uref{http://gmplib.org, GNU MP} (GMP)
-libraries for arbitrary precision
-arithmetic on numbers. So if you do not see the names of these libraries
-in the output, then your version of @command{gawk} does not support
-arbitrary precision arithmetic.
-
-Additionally,
-there are a few elements available in the @code{PROCINFO} array
-to provide information about the MPFR and GMP libraries.
-@xref{Auto-set}, for more information.
-
-@ignore
-Even if you aren't interested in arbitrary precision arithmetic, you
-may still benefit from knowing about how @command{gawk} handles numbers
-in general, and the limitations of doing arithmetic with ordinary
-@command{gawk} numbers.
-@end ignore
-
-
-@node Arbitrary Precision Floats
-@section Arbitrary Precision Floating-point Arithmetic with @command{gawk}
-
-@command{gawk} uses the GNU MPFR library
-for arbitrary precision floating-point arithmetic.  The MPFR library
-provides precise control over precisions and rounding modes, and gives
-correctly rounded, reproducible, platform-independent results.  With one
-of the command-line options @option{--bignum} or @option{-M},
-all floating-point arithmetic operators and numeric functions can yield
-results to any desired precision level supported by MPFR.
-Two built-in variables, @code{PREC} and @code{ROUNDMODE},
-provide control over the working precision and the rounding mode
-(@pxref{Setting Precision}, and
-@pxref{Setting Rounding Mode}).
-The precision and the rounding mode are set globally for every operation
-to follow.
-
-The default working precision for arbitrary precision floating-point values is
-53 bits, and the default value for @code{ROUNDMODE} is @code{"N"},
-which selects the IEEE-754 @code{roundTiesToEven} rounding mode
-(@pxref{Rounding Mode}).@footnote{The
-default precision is 53 bits, since according to the MPFR documentation,
-the library should be able to exactly reproduce all computations with
-double-precision machine floating-point numbers (@code{double} type
-in C), except the default exponent range is much wider and subnormal
-numbers are not implemented.}
-@command{gawk} uses the default exponent range in MPFR
-@iftex
-(@math{emax = 2^{30} - 1, emin = -emax})
-@end iftex
-@ifnottex
-(@var{emax} = 2^30 @minus{} 1, @var{emin} = @minus{}@var{emax})
-@end ifnottex
-for all floating-point contexts.
-There is no explicit mechanism to adjust the exponent range.
-MPFR does not implement subnormal numbers by default,
-and this behavior cannot be changed in @command{gawk}.
-
-@quotation NOTE
-When emulating an IEEE-754 format (@pxref{Setting Precision}),
-@command{gawk} internally adjusts the exponent range
-to the value defined for the format and also performs computations needed for
-gradual underflow (subnormal numbers).
-@end quotation
-
-@quotation NOTE
-MPFR numbers are variable-size entities, consuming only as much space as
-needed to store the significant digits. Since the performance using MPFR
-numbers pales in comparison to doing arithmetic using the underlying machine
-types, you should consider using only as much precision as needed by
-your program.
-@end quotation
-
-@menu
-* Setting Precision::           Setting the working precision.
-* Setting Rounding Mode::       Setting the rounding mode.
-* Floating-point Constants::    Representing floating-point constants.
-* Changing Precision::          Changing the precision of a number.
-* Exact Arithmetic::            Exact arithmetic with floating-point numbers.
-@end menu
-
-@node Setting Precision
-@subsection Setting the Working Precision
-@cindex @code{PREC} variable
+@node Setting precision
+@subsection Setting The Precision
 
 @command{gawk} uses a global working precision; it does not keep track of
 the precision or accuracy of individual numbers. Performing an arithmetic
 operation or calling a built-in function rounds the result to the current
-working precision. The default working precision is 53 bits, which can be
-modified using the built-in variable @code{PREC}. You can also set the
-value to one of the pre-defined case-insensitive strings
+working precision. The default working precision is 53 bits, which you can
+modify using the built-in variable @code{PREC}. You can also set the
+value to one of the predefined case-insensitive strings
 shown in @ref{table-predefined-precision-strings},
-to emulate an IEEE-754 binary format.
+to emulate an IEEE 754 binary format.
 
 @float Table,table-predefined-precision-strings
-@caption{Predefined precision strings for @code{PREC}}
+@caption{Predefined Precision Strings For @code{PREC}}
 @multitable {@code{"double"}} {12345678901234567890123456789012345}
-@headitem @code{PREC} @tab IEEE-754 Binary Format
+@headitem @code{PREC} @tab IEEE 754 Binary Format
 @item @code{"half"} @tab 16-bit half-precision.
 @item @code{"single"} @tab Basic 32-bit single precision.
 @item @code{"double"} @tab Basic 64-bit double precision.
@@ -28962,49 +30282,34 @@ $ @kbd{gawk -M -v PREC=100 'BEGIN @{ x = 1.0e-400; print x + 0}
 @print{} 0
 @end example
 
-Binary and decimal precisions are related approximately, according to the
-formula:
+@quotation CAUTION
+Be wary of floating-point constants! When reading a floating-point
+constant from program source code, @command{gawk} uses the default
+precision (that of a C @code{double}), unless overridden by an assignment
+to the special variable @code{PREC} on the command line, to store it
+internally as a MPFR number.  Changing the precision using @code{PREC}
+in the program text does @emph{not} change the precision of a constant.
+
+If you need to represent a floating-point constant at a higher precision
+than the default and cannot use a command line assignment to @code{PREC},
+you should either specify the constant as a string, or as a rational
+number, whenever possible. The following example illustrates the
+differences among various ways to print a floating-point constant:
+@end quotation
 
-@iftex
-@math{prec = 3.322 @cdot dps}
-@end iftex
-@ifnottex
-@var{prec} = 3.322 * @var{dps}
-@end ifnottex
+@example
+$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 0.1) @}'}
+@print{} 0.1000000000000000055511151 
+$ @kbd{gawk -M -v PREC=113 'BEGIN @{ printf("%0.25f\n", 0.1) @}'}
+@print{} 0.1000000000000000000000000
+$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", "0.1") @}'}
+@print{} 0.1000000000000000000000000
+$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 1/10) @}'}
+@print{} 0.1000000000000000000000000
+@end example
 
-@noindent
-Here, @var{prec} denotes the binary precision
-(measured in bits) and @var{dps} (short for decimal places)
-is the decimal digits. We can easily calculate how many decimal
-digits the 53-bit significand of an IEEE double is equivalent to:
-53 / 3.322 which is equal to about 15.95.
-But what does 15.95 digits actually mean? It depends whether you are
-concerned about how many digits you can rely on, or how many digits
-you need.
-
-It is important to know how many bits it takes to uniquely identify
-a double-precision value (the C type @code{double}).  If you want to
-convert from @code{double} to decimal and back to @code{double} (e.g.,
-saving a @code{double} representing an intermediate result to a file, and
-later reading it back to restart the computation), then a few more decimal
-digits are required. 17 digits is generally enough for a @code{double}.
-
-It can also be important to know what decimal numbers can be uniquely
-represented with a @code{double}. If you want to convert
-from decimal to @code{double} and back again, 15 digits is the most that
-you can get. Stated differently, you should not present
-the numbers from your floating-point computations with more than 15
-significant digits in them.
-
-Conversely, it takes a precision of 332 bits to hold an approximation
-of the constant @value{PI} that is accurate to 100 decimal places.
-
-You should always add some extra bits in order to avoid the confusing round-off
-issues that occur because numbers are stored internally in binary.
-
-@node Setting Rounding Mode
-@subsection Setting the Rounding Mode
-@cindex @code{ROUNDMODE} variable
+@node Setting the rounding mode
+@subsection Setting The Rounding Mode
 
 The @code{ROUNDMODE} variable provides
 program level control over the rounding mode.
@@ -29023,190 +30328,104 @@ rounding modes is shown in @ref{table-gawk-rounding-modes}.
 @end multitable
 @end float
 
-@code{ROUNDMODE} has the default value @code{"N"},
-which selects the IEEE-754 rounding mode @code{roundTiesToEven}.
-In @ref{table-gawk-rounding-modes}, @code{"A"} is listed to select the IEEE-754 mode
-@code{roundTiesToAway}.  This is only available
-if your version of the MPFR library supports it; otherwise setting
-@code{ROUNDMODE} to this value has no effect. @xref{Rounding Mode},
-for the meanings of the various rounding modes.
-
-Here is an example of how to change the default rounding behavior of
-@code{printf}'s output:
+@code{ROUNDMODE} has the default value @code{"N"}, which
+selects the IEEE 754 rounding mode @code{roundTiesToEven}.
+In @ref{table-gawk-rounding-modes}, the value @code{"A"} selects
+@code{roundTiesToAway}.  This is only available if your version of the
+MPFR library supports it; otherwise setting @code{ROUNDMODE} to @code{"A"}
+has no effect.
 
-@example
-$ @kbd{gawk -M -v ROUNDMODE="Z" 'BEGIN @{ printf("%.2f\n", 1.378) @}'}
-@print{} 1.37
-@end example
-
-@node Floating-point Constants
-@subsection Representing Floating-point Constants
-@cindex constants, floating-point
-
-Be wary of floating-point constants! When reading a floating-point constant
-from program source code, @command{gawk} uses the default precision,
-unless overridden
-by an assignment to the special variable @code{PREC} on the command
-line, to store it internally as a MPFR number.
-Changing the precision using @code{PREC} in the program text does
-@emph{not} change the precision of a constant. If you need to
-represent a floating-point constant at a higher precision than the
-default and cannot use a command line assignment to @code{PREC},
-you should either specify the constant as a string, or 
-as a rational number, whenever possible. The following example
-illustrates the differences among various ways to
-print a floating-point constant:
-
-@example
-$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 0.1) @}'}
-@print{} 0.1000000000000000055511151 
-$ @kbd{gawk -M -v PREC=113 'BEGIN @{ printf("%0.25f\n", 0.1) @}'}
-@print{} 0.1000000000000000000000000
-$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", "0.1") @}'}
-@print{} 0.1000000000000000000000000
-$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 1/10) @}'}
-@print{} 0.1000000000000000000000000
-@end example
-
-In the first case, the number is stored with the default precision of 53 bits.
-
-@node Changing Precision
-@subsection Changing the Precision of a Number
-
-@cindex Laurie, Dirk
-@quotation
-@i{The point is that in any variable-precision package,
-a decision is made on how to treat numbers given as data,
-or arising in intermediate results, which are represented in
-floating-point format to a precision lower than working precision.
-Do we promote them to full membership of the high-precision club,
-or do we treat them and all their associates as second-class citizens?
-Sometimes the first course is proper, sometimes the second, and it takes
-careful analysis to tell which.}@footnote{Dirk Laurie.
-@cite{Variable-precision Arithmetic Considered Perilous --- A Detective Story}.
-Electronic Transactions on Numerical Analysis. Volume 28, pp. 168-173, 2008.}
-@author Dirk Laurie
-@end quotation
+The default mode @code{roundTiesToEven} is the most preferred,
+but the least intuitive. This method does the obvious thing for most values,
+by rounding them up or down to the nearest digit.
+For example, rounding 1.132 to two digits yields 1.13,
+and rounding 1.157 yields 1.16.
 
-@command{gawk} does not implicitly modify the precision of any previously
-computed results when the working precision is changed with an assignment
-to @code{PREC}.  The precision of a number is always the one that was
-used at the time of its creation, and there is no way for the user
-to explicitly change it afterwards. However, since the result of a
-floating-point arithmetic operation is always an arbitrary precision
-floating-point value---with a precision set by the value of @code{PREC}---one of the
-following workarounds effectively accomplishes the desired behavior:
+However, when it comes to rounding a value that is exactly halfway between,
+things do not work the way you probably learned in school.
+In this case, the number is rounded to the nearest even digit.
+So rounding 0.125 to two digits rounds down to 0.12,
+but rounding 0.6875 to three digits rounds up to 0.688.
+You probably have already encountered this rounding mode when
+using @code{printf} to format floating-point numbers.
+For example:
 
 @example
-x = x + 0.0
+BEGIN @{
+    x = -4.5
+    for (i = 1; i < 10; i++) @{
+        x += 1.0
+        printf("%4.1f => %2.0f\n", x, x)
+    @}
+@}
 @end example
 
 @noindent
-or:
-
-@example
-x += 0.0
-@end example
-
-@node Exact Arithmetic
-@subsection Exact Arithmetic with Floating-point Numbers
-
-@quotation CAUTION
-Never depend on the exactness of floating-point arithmetic,
-even for apparently simple expressions!
-@end quotation
-
-Can arbitrary precision arithmetic give exact results? There are
-no easy answers. The standard rules of algebra often do not apply
-when using floating-point arithmetic.
-Among other things, the distributive and associative laws
-do not hold completely, and order of operation may be important
-for your computation. Rounding error, cumulative precision loss
-and underflow are often troublesome.
-
-When @command{gawk} tests the expressions @samp{0.1 + 12.2} and @samp{12.3}
-for equality
-using the machine double precision arithmetic, it decides that they
-are not equal!
-(@xref{Floating-point Programming}.)
-You can get the result you want by increasing the precision;
-56 bits in this case will get the job done:
-
-@example 
-$ @kbd{gawk -M -v PREC=56 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
-@print{} 1
-@end example
-
-If adding more bits is good, perhaps adding even more bits of
-precision is better?
-Here is what happens if we use an even larger value of @code{PREC}:
-
-@example 
-$ @kbd{gawk -M -v PREC=201 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
-@print{} 0
-@end example
-
-This is not a bug in @command{gawk} or in the MPFR library.
-It is easy to forget that the finite number of bits used to store the value
-is often just an approximation after proper rounding.
-The test for equality succeeds if and only if @emph{all} bits in the two operands
-are exactly the same. Since this is not necessarily true after floating-point
-computations with a particular precision and effective rounding rule,
-a straight test for equality may not work. 
-
-So, don't assume that floating-point values can be compared for equality.
-You should also exercise caution when using other forms of comparisons.
-The standard way to compare between floating-point numbers is to determine
-how much error (or @dfn{tolerance}) you will allow in a comparison and
-check to see if one value is within this error range of the other.
-
-In applications where 15 or fewer decimal places suffice,
-hardware double precision arithmetic can be adequate, and is usually much faster.
-But you do need to keep in mind that every floating-point operation
-can suffer a new rounding error with catastrophic consequences as illustrated
-by our earlier attempt to compute the value of the constant @value{PI}
-(@pxref{Floating-point Programming}).
-Extra precision can greatly enhance the stability and the accuracy
-of your computation in such cases.
-
-Repeated addition is not necessarily equivalent to multiplication
-in floating-point arithmetic. In the example in
-@ref{Floating-point Programming}:
+produces the following output when run on the author's system:@footnote{It
+is possible for the output to be completely different if the
+C library in your system does not use the IEEE 754 even-rounding
+rule to round halfway cases for @code{printf}.}
 
 @example
-$ @kbd{gawk 'BEGIN @{}
->   @kbd{for (d = 1.1; d <= 1.5; d += 0.1)    # loop five times (?)}
->       @kbd{i++}
->   @kbd{print i}
-> @kbd{@}'}
-@print{} 4
+-3.5 => -4
+-2.5 => -2
+-1.5 => -2
+-0.5 => 0
+ 0.5 => 0
+ 1.5 => 2
+ 2.5 => 2
+ 3.5 => 4
+ 4.5 => 4
 @end example
 
-@noindent
-you may or may not succeed in getting the correct result by choosing
-an arbitrarily large value for @code{PREC}. Reformulation of
-the problem at hand is often the correct approach in such situations.
+The theory behind @code{roundTiesToEven} is that it more or less evenly
+distributes upward and downward rounds of exact halves, which might
+cause any accumulating round-off error to cancel itself out. This is the
+default rounding mode for IEEE 754 computing functions and operators.
+
+The other rounding modes are rarely used.  Round toward positive infinity
+(@code{roundTowardPositive}) and round toward negative infinity
+(@code{roundTowardNegative}) are often used to implement interval
+arithmetic, where you adjust the rounding mode to calculate upper and
+lower bounds for the range of output. The @code{roundTowardZero} mode can
+be used for converting floating-point numbers to integers.  The rounding
+mode @code{roundTiesToAway} rounds the result to the nearest number and
+selects the number with the larger magnitude if a tie occurs.
+
+Some numerical analysts will tell you that your choice of rounding
+style has tremendous impact on the final outcome, and advise you to
+wait until final output for any rounding. Instead, you can often avoid
+round-off error problems by setting the precision initially to some
+value sufficiently larger than the final desired precision, so that
+the accumulation of round-off error does not influence the outcome.
+If you suspect that results from your computation are sensitive to
+accumulation of round-off error, look for a significant difference in
+output when you change the rounding mode to be sure.
 
 @node Arbitrary Precision Integers
 @section Arbitrary Precision Integer Arithmetic with @command{gawk}
-@cindex integer, arbitrary precision
-
-If one of the options @option{--bignum} or @option{-M} is specified,
-@command{gawk} performs all
-integer arithmetic using GMP arbitrary precision integers.
-Any number that looks like an integer in a program source or data file
-is stored as an arbitrary precision integer.
-The size of the integer is limited only by your computer's memory.
-The current floating-point context has no effect on operations involving integers.
-For example, the following computes
+@cindex integers, arbitrary precision
+@cindex arbitrary precision integers
+
+When given one of the options @option{--bignum} or @option{-M},
+@command{gawk} performs all integer arithmetic using GMP arbitrary
+precision integers.  Any number that looks like an integer in a source
+or @value{DF} is stored as an arbitrary precision integer.  The size
+of the integer is limited only by the available memory.  For example,
+the following computes
 @iftex
 @math{5^{4^{3^{2}}}},
 @end iftex
 @ifnottex
+@ifnotdocbook
 5^4^3^2,
+@end ifnotdocbook
 @end ifnottex
+@docbook
+5<superscript>4<superscript>3<superscript>2</superscript></superscript></superscript>, @c
+@end docbook
 the result of which is beyond the
-limits of ordinary @command{gawk} numbers:
+limits of ordinary hardware double-precision floating point values:
 
 @example
 $ @kbd{gawk -M 'BEGIN @{}
@@ -29218,25 +30437,32 @@ $ @kbd{gawk -M 'BEGIN @{}
 @print{} 62060698786608744707 ... 92256259918212890625
 @end example
 
-If you were to compute the same value using arbitrary precision
-floating-point values instead, the precision needed for correct output
-(using the formula
+If instead you were to compute the same value using arbitrary precision
+floating-point values, the precision needed for correct output (using
+the formula
 @iftex
 @math{prec = 3.322 @cdot dps}),
 would be @math{3.322 @cdot 183231},
 @end iftex
 @ifnottex
+@ifnotdocbook
 @samp{prec = 3.322 * dps}),
 would be 3.322 x 183231,
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<emphasis>prec</emphasis> = 3.322 &sdot; <emphasis>dps</emphasis>),
+would be
+<emphasis>prec</emphasis> = 3.322 &sdot; 183231, @c
+@end docbook
 or 608693.
 
 The result from an arithmetic operation with an integer and a floating-point value
 is a floating-point value with a precision equal to the working precision.
 The following program calculates the eighth term in
 Sylvester's sequence@footnote{Weisstein, Eric W.
-@cite{Sylvester's Sequence}. From MathWorld---A Wolfram Web Resource.
-@url{http://mathworld.wolfram.com/SylvestersSequence.html}}
+@cite{Sylvester's Sequence}. From MathWorld---A Wolfram Web Resource
+@w{(@url{http://mathworld.wolfram.com/SylvestersSequence.html}).}}
 using a recurrence:
 
 @example
@@ -29256,15 +30482,15 @@ floating-point results exactly. You can either increase the precision
 @samp{2.0} with an integer, to perform all computations using integer
 arithmetic to get the correct output.
 
-It will sometimes be necessary for @command{gawk} to implicitly convert an
-arbitrary precision integer into an arbitrary precision floating-point value.
-This is primarily because the MPFR library does not always provide the
-relevant interface to process arbitrary precision integers or mixed-mode
-numbers as needed by an operation or function.
-In such a case, the precision is set to the minimum value necessary
-for exact conversion, and the working precision is not used for this purpose.
-If this is not what you need or want, you can employ a subterfuge
-like this:
+Sometimes @command{gawk} must implicitly convert an arbitrary precision
+integer into an arbitrary precision floating-point value.  This is
+primarily because the MPFR library does not always provide the relevant
+interface to process arbitrary precision integers or mixed-mode numbers
+as needed by an operation or function.  In such a case, the precision is
+set to the minimum value necessary for exact conversion, and the working
+precision is not used for this purpose.  If this is not what you need or
+want, you can employ a subterfuge, and convert the integer to floating
+point first, like this:
 
 @example
 gawk -M 'BEGIN @{ n = 13; print (n + 0.0) % 2.0 @}'
@@ -29277,15 +30503,186 @@ to begin with:
 gawk -M 'BEGIN @{ n = 13.0; print n % 2.0 @}'
 @end example
 
-Note that for the particular example above, there is likely best
+Note that for the particular example above, it is likely best
 to just use the following:
 
 @example
 gawk -M 'BEGIN @{ n = 13; print n % 2 @}'
 @end example
 
+@node POSIX Floating Point Problems
+@section Standards Versus Existing Practice
+
+Historically, @command{awk} has converted any non-numeric looking string
+to the numeric value zero, when required.  Furthermore, the original
+definition of the language and the original POSIX standards specified that
+@command{awk} only understands decimal numbers (base 10), and not octal
+(base 8) or hexadecimal numbers (base 16).
+
+Changes in the language of the
+2001 and 2004 POSIX standards can be interpreted to imply that @command{awk}
+should support additional features.  These features are:
+
+@itemize @value{BULLET}
+@item
+Interpretation of floating point data values specified in hexadecimal
+notation (e.g., @code{0xDEADBEEF}). (Note: data values, @emph{not}
+source code constants.)
+
+@item
+Support for the special IEEE 754 floating point values ``Not A Number''
+(NaN), positive Infinity (``inf'') and negative Infinity (``@minus{}inf'').
+In particular, the format for these values is as specified by the ISO 1999
+C standard, which ignores case and can allow implementation-dependent additional
+characters after the @samp{nan} and allow either @samp{inf} or @samp{infinity}.
+@end itemize
+
+The first problem is that both of these are clear changes to historical
+practice:
+
+@itemize @value{BULLET}
+@item
+The @command{gawk} maintainer feels that supporting hexadecimal floating
+point values, in particular, is ugly, and was never intended by the
+original designers to be part of the language.
+
+@item
+Allowing completely alphabetic strings to have valid numeric
+values is also a very severe departure from historical practice.
+@end itemize
+
+The second problem is that the @code{gawk} maintainer feels that this
+interpretation of the standard, which requires a certain amount of
+``language lawyering'' to arrive at in the first place, was not even
+intended by the standard developers.  In other words, ``we see how you
+got where you are, but we don't think that that's where you want to be.''
+
+Recognizing the above issues, but attempting to provide compatibility
+with the earlier versions of the standard,
+the 2008 POSIX standard added explicit wording to allow, but not require,
+that @command{awk} support hexadecimal floating point values and
+special values for ``Not A Number'' and infinity.
+
+Although the @command{gawk} maintainer continues to feel that
+providing those features is inadvisable,
+nevertheless, on systems that support IEEE floating point, it seems
+reasonable to provide @emph{some} way to support NaN and Infinity values.
+The solution implemented in @command{gawk} is as follows:
+
+@itemize @value{BULLET}
+@item
+With the @option{--posix} command-line option, @command{gawk} becomes
+``hands off.'' String values are passed directly to the system library's
+@code{strtod()} function, and if it successfully returns a numeric value,
+that is what's used.@footnote{You asked for it, you got it.}
+By definition, the results are not portable across
+different systems.  They are also a little surprising:
+
+@example
+$ @kbd{echo nanny | gawk --posix '@{ print $1 + 0 @}'}
+@print{} nan
+$ @kbd{echo 0xDeadBeef | gawk --posix '@{ print $1 + 0 @}'}
+@print{} 3735928559
+@end example
+
+@item
+Without @option{--posix}, @command{gawk} interprets the four strings
+@samp{+inf},
+@samp{-inf},
+@samp{+nan},
+and
+@samp{-nan}
+specially, producing the corresponding special numeric values.
+The leading sign acts a signal to @command{gawk} (and the user)
+that the value is really numeric.  Hexadecimal floating point is
+not supported (unless you also use @option{--non-decimal-data},
+which is @emph{not} recommended). For example:
+
+@example
+$ @kbd{echo nanny | gawk '@{ print $1 + 0 @}'}
+@print{} 0
+$ @kbd{echo +nan | gawk '@{ print $1 + 0 @}'}
+@print{} nan
+$ @kbd{echo 0xDeadBeef | gawk '@{ print $1 + 0 @}'}
+@print{} 0
+@end example
+
+@command{gawk} ignores case in the four special values.
+Thus @samp{+nan} and @samp{+NaN} are the same.
+@end itemize
+
+@node Floating point summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Most computer arithmetic is done using either integers or floating-point
+values.  The default for @command{awk} is to use double-precision
+floating-point values.
+
+@item
+In the 1980's, Barbie mistakenly said ``Math class is tough!''
+While math isn't tough, floating-point arithmetic isn't the same
+as pencil and paper math, and care must be taken:
+
+@c nested list
+@itemize @value{MINUS}
+@item
+Not all numbers can be represented exactly.
+
+@item
+Comparing values should use a delta, instead of being done directly
+with @samp{==} and @samp{!=}.
+
+@item
+Errors accumulate.
+
+@item
+Operations are not always truly associative or distributive.
+@end itemize
+
+@item
+Increasing the accuracy can help, but it is not a panacea.
+
+@item
+Often, increasing the accuracy and then rounding to the desired
+number of digits produces reasonable results.
+
+@item
+Use either @option{-M} or @option{--bignum} to enable MPFR
+arithmetic. Use @code{PREC} to set the precision in bits, and
+@code{ROUNDMODE} to set the IEEE 754 rounding mode.
+
+@item
+With @option{-M} or @option{--bignum}, @command{gawk} performs
+arbitrary precision integer arithmetic using the GMP library.
+This is faster and more space efficient than using MPFR for
+the same calculations.
+
+@item
+There are several ``dark corners'' with respect to floating-point
+numbers where @command{gawk} disagrees with the POSIX standard.
+It pays to be aware of them.
+
+@item
+Overall, there is no need to be unduly suspicious about the results from
+floating-point arithmetic. The lesson to remember is that floating-point
+arithmetic is always more complex than arithmetic using pencil and
+paper. In order to take advantage of the power of computer floating-point,
+you need to know its limitations and work within them. For most casual
+use of floating-point arithmetic, you will often get the expected result
+if you simply round the display of your final results to the correct number
+of significant decimal digits.
+
+@item
+As general advice, avoid presenting numerical data in a manner that
+implies better precision than is actually the case.
+
+@end itemize
+
 @node Dynamic Extensions
 @chapter Writing Extensions for @command{gawk}
+@cindex dynamically loaded extensions
 
 It is possible to add new functions written in C or C++ to @command{gawk} using
 dynamically loaded libraries. This facility is available on systems
@@ -29315,11 +30712,14 @@ When @option{--sandbox} is specified, extensions are disabled
 * Extension Samples::           The sample extensions that ship with
                                 @code{gawk}.
 * gawkextlib::                  The @code{gawkextlib} project.
+* Extension summary::           Extension summary.
+* Extension Exercises::         Exercises.
 @end menu
 
 @node Extension Intro
 @section Introduction
 
+@cindex plug-in
 An @dfn{extension} (sometimes called a @dfn{plug-in}) is a piece of
 external compiled code that @command{gawk} can load at runtime to
 provide additional functionality, over and above the built-in capabilities
@@ -29339,8 +30739,15 @@ the facilities that the API provides and how to use
 them, and presents a small sample extension.  In addition, it documents
 the sample extensions included in the @command{gawk} distribution,
 and describes the @code{gawkextlib} project.
+@ifclear FOR_PRINT
 @xref{Extension Design}, for a discussion of the extension mechanism
 goals and design.
+@end ifclear
+@ifset FOR_PRINT
+See @uref{http://www.gnu.org/software/gawk/manual/html_node/Extension-Design.html}
+for a discussion of the extension mechanism
+goals and design.
+@end ifset
 
 @node Plugin License
 @section Extension Licensing
@@ -29365,45 +30772,83 @@ Communication between
 @command{gawk} and an extension is two-way.  First, when an extension
 is loaded, it is passed a pointer to a @code{struct} whose fields are
 function pointers.
-This is shown in @ref{load-extension}.
+@ifnotdocbook
+This is shown in @ref{figure-load-extension}.
+@end ifnotdocbook
+@ifdocbook
+This is shown in @inlineraw{docbook, <xref linkend="figure-load-extension"/>}.
+@end ifdocbook
 
-@float Figure,load-extension
+@ifnotdocbook
+@float Figure,figure-load-extension
 @caption{Loading The Extension}
 @c FIXME: One day, it should not be necessary to have two cases,
 @c but rather just the one without the "txt" final argument.
 @c This applies to the other figures as well.
 @ifinfo
-@center @image{api-figure1, , , Loading the extension, txt}
+@center @image{api-figure1, , , Loading The Extension, txt}
 @end ifinfo
 @ifnotinfo
-@center @image{api-figure1, , , Loading the extension}
+@center @image{api-figure1, , , Loading The Extension}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-load-extension" float="0">
+<title>Loading The Extension</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="api-figure1.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 The extension can call functions inside @command{gawk} through these
 function pointers, at runtime, without needing (link-time) access
 to @command{gawk}'s symbols.  One of these function pointers is to a
 function for ``registering'' new built-in functions.
-This is shown in @ref{load-new-function}.
+@ifnotdocbook
+This is shown in @ref{figure-load-new-function}.
+@end ifnotdocbook
+@ifdocbook
+This is shown in @inlineraw{docbook, <xref linkend="figure-load-new-function"/>}.
+@end ifdocbook
 
-@float Figure,load-new-function
+@ifnotdocbook
+@float Figure,figure-load-new-function
 @caption{Loading The New Function}
 @ifinfo
-@center @image{api-figure2, , , Loading the new function, txt}
+@center @image{api-figure2, , , Loading The New Function, txt}
 @end ifinfo
 @ifnotinfo
-@center @image{api-figure2, , , Loading the new function}
+@center @image{api-figure2, , , Loading The New Function}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-load-new-function" float="0">
+<title>Loading The New Function</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="api-figure2.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 In the other direction, the extension registers its new functions
 with @command{gawk} by passing function pointers to the functions that
 provide the new feature (@code{do_chdir()}, for example).  @command{gawk}
 associates the function pointer with a name and can then call it, using a
 defined calling convention.
-This is shown in @ref{call-new-function}.
+@ifnotdocbook
+This is shown in @ref{figure-call-new-function}.
+@end ifnotdocbook
+@ifdocbook
+This is shown in @inlineraw{docbook, <xref linkend="figure-call-new-function"/>}.
+@end ifdocbook
 
-@float Figure,call-new-function
+@ifnotdocbook
+@float Figure,figure-call-new-function
 @caption{Calling The New Function}
 @ifinfo
 @center @image{api-figure3, , , Calling the new function, txt}
@@ -29412,14 +30857,24 @@ This is shown in @ref{call-new-function}.
 @center @image{api-figure3, , , Calling the new function}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-call-new-function" float="0">
+<title>Calling The New Function</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="api-figure3.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 The @code{do_@var{xxx}()} function, in turn, then uses the function
 pointers in the API @code{struct} to do its work, such as updating
 variables or arrays, printing messages, setting @code{ERRNO}, and so on.
 
-Convenience macros in the @file{gawkapi.h} header file make calling
-through the function pointers look like regular function calls so that
-extension code is quite readable and understandable.
+Convenience macros make calling through the function pointers look
+like regular function calls so that extension code is quite readable
+and understandable.
 
 Although all of this sounds somewhat complicated, the result is that
 extension code is quite straightforward to write and to read. You can
@@ -29428,7 +30883,7 @@ Example}) and also the @file{testext.c} code for testing the APIs.
 
 Some other bits and pieces:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The API provides access to @command{gawk}'s @code{do_@var{xxx}} values,
 reflecting command line options, like @code{do_lint}, @code{do_profiling}
@@ -29448,13 +30903,18 @@ happen, but we all know how @emph{that} goes.)
 
 @node Extension API Description
 @section API Description
+@cindex extension API
 
+C or C++ code for an extension must include the header file
+@file{gawkapi.h}, which declares the functions and defines the data
+types used to communicate with @command{gawk}.
 This (rather large) @value{SECTION} describes the API in detail.
 
 @menu
 * Extension API Functions Introduction:: Introduction to the API functions.
 * General Data Types::                   The data types.
 * Requesting Values::                    How to get a value.
+* Memory Allocation Functions::          Functions for allocating memory.
 * Constructor Functions::                Functions for creating values.
 * Registration Functions::               Functions to register things with
                                          @command{gawk}.
@@ -29476,10 +30936,10 @@ by calling through function pointers passed into your extension.
 
 API function pointers are provided for the following kinds of operations:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-Registrations functions. You may register:
-@itemize @minus
+Registration functions. You may register:
+@itemize @value{MINUS}
 @item
 extension functions,
 @item
@@ -29510,6 +30970,9 @@ Symbol table access: retrieving a global variable, creating one,
 or changing one.
 
 @item
+Allocating, reallocating, and releasing memory.
+
+@item
 Creating and releasing cached values; this provides an
 efficient way to use values for multiple variables and
 can be a big performance win.
@@ -29517,7 +30980,7 @@ can be a big performance win.
 @item
 Manipulating arrays:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 Retrieving, adding, deleting, and modifying elements
 
@@ -29537,7 +31000,7 @@ Flattening an array for easy C style looping over all its indices and elements
 
 Some points about using the API:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The following types and/or macros and/or functions are referenced
 in @file{gawkapi.h}.  For correct use, you must therefore include the
@@ -29546,12 +31009,11 @@ corresponding standard header file @emph{before} including @file{gawkapi.h}:
 @multitable {@code{memset()}, @code{memcpy()}} {@code{<sys/types.h>}}
 @headitem C Entity @tab Header File
 @item @code{EOF} @tab @code{<stdio.h>}
+@item Values for @code{errno} @tab @code{<errno.h>}
 @item @code{FILE} @tab @code{<stdio.h>}
 @item @code{NULL} @tab @code{<stddef.h>}
-@item @code{malloc()} @tab @code{<stdlib.h>}
 @item @code{memcpy()} @tab @code{<string.h>}
 @item @code{memset()} @tab @code{<string.h>}
-@item @code{realloc()} @tab @code{<stdlib.h>}
 @item @code{size_t} @tab @code{<sys/types.h>}
 @item @code{struct stat} @tab @code{<sys/stat.h>}
 @end multitable 
@@ -29563,9 +31025,6 @@ is necessary in order to keep @file{gawkapi.h} clean, instead of becoming
 a portability hodge-podge as can be seen in some parts of
 the @command{gawk} source code.
 
-To pass reasonable integer values for @code{ERRNO}, you will also need to
-include @code{<errno.h>}.
-
 @item
 The @file{gawkapi.h} file may be included more than once without ill effect.
 Doing so, however, is poor coding practice.
@@ -29581,14 +31040,15 @@ does not support this keyword, you should either place
 All pointers filled in by @command{gawk} are to memory
 managed by @command{gawk} and should be treated by the extension as
 read-only.  Memory for @emph{all} strings passed into @command{gawk}
-from the extension @emph{must} come from @code{malloc()} and is managed
-by @command{gawk} from then on.
+from the extension @emph{must} come from calling the API-provided function
+pointers @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()},
+and is managed by @command{gawk} from then on.
 
 @item
 The API defines several simple @code{struct}s that map values as seen
 from @command{awk}.  A value can be a @code{double}, a string, or an
 array (as in multidimensional arrays, or when creating a new array).
-String values maintain both pointer and length since embedded @code{NUL}
+String values maintain both pointer and length since embedded @sc{nul}
 characters are allowed.
 
 @quotation NOTE
@@ -29622,10 +31082,14 @@ the macros as if they were functions.
 @node General Data Types
 @subsection General Purpose Data Types
 
+@cindex Robbins, Arnold
+@cindex Ramey, Chet
 @quotation
 @i{I have a true love/hate relationship with unions.}
 @author Arnold Robbins
+@end quotation
 
+@quotation
 @i{That's the thing about unions: the compiler will arrange things so they
 can accommodate both love and hate.}
 @author Chet Ramey
@@ -29648,9 +31112,9 @@ certain fields in the API data structures unwritable from extension code,
 while allowing @command{gawk} to use them as it needs to.
 
 @item typedef enum awk_bool @{
-@item @ @ @ @ awk_false = 0,
-@item @ @ @ @ awk_true
-@item @} awk_bool_t;
+@itemx @ @ @ @ awk_false = 0,
+@itemx @ @ @ @ awk_true
+@itemx @} awk_bool_t;
 A simple boolean type.
 
 @item typedef struct awk_string @{
@@ -29660,7 +31124,8 @@ A simple boolean type.
 This represents a mutable string. @command{gawk}
 owns the memory pointed to if it supplied
 the value. Otherwise, it takes ownership of the memory pointed to.
-@strong{Such memory must come from @code{malloc()}!}
+@strong{Such memory must come from calling the API-provided function
+pointers @code{api_malloc()}, @code{api_calloc()}, or @code{api_realloc()}!}
 
 As mentioned earlier, strings are maintained using the current
 multibyte encoding.
@@ -29715,7 +31180,7 @@ Scalar values in @command{awk} are either numbers or strings. The
 indicates what is in the @code{union}.
 
 Representing numbers is easy---the API uses a C @code{double}.  Strings
-require more work. Since @command{gawk} allows embedded @code{NUL} bytes
+require more work. Since @command{gawk} allows embedded @sc{nul} bytes
 in string values, a string must be represented as a pair containing a
 data-pointer and length. This is the @code{awk_string_t} type.
 
@@ -29745,8 +31210,11 @@ reading and/or changing the value of one or more scalar variables, you
 can obtain a @dfn{scalar cookie}@footnote{See
 @uref{http://catb.org/jargon/html/C/cookie.html, the ``cookie'' entry in the Jargon file} for a
 definition of @dfn{cookie}, and @uref{http://catb.org/jargon/html/M/magic-cookie.html,
-the ``magic cookie'' entry in the Jargon file} for a nice example. See
-also the entry for ``Cookie'' in the @ref{Glossary}.}
+the ``magic cookie'' entry in the Jargon file} for a nice example.
+@ifclear FOR_PRINT
+See also the entry for ``Cookie'' in the @ref{Glossary}.
+@end ifclear
+}
 object for that variable, and then use
 the cookie for getting the variable's value or for changing the variable's
 value.
@@ -29776,9 +31244,94 @@ print an error message, or reissue the request for the actual
 value type, as appropriate.  This behavior is summarized in
 @ref{table-value-types-returned}.
 
-@ifnotplaintext
+@c FIXME: Try to do this with spans...
+
 @float Table,table-value-types-returned
-@caption{Value Types Returned}
+@caption{API Value Types Returned}
+@docbook
+<informaltable>
+<tgroup cols="2">
+  <colspec colwidth="50*"/><colspec colwidth="50*"/>
+  <thead>
+    <row><entry></entry><entry><para>Type of Actual Value:</para></entry></row>
+  </thead>
+  <tbody>
+    <row><entry></entry><entry></entry></row>
+  </tbody>
+</tgroup>
+<tgroup cols="6">
+  <colspec colwidth="16.6*"/>
+  <colspec colwidth="16.6*"/>
+  <colspec colwidth="19.8*"/>
+  <colspec colwidth="15*"/>
+  <colspec colwidth="15*"/>
+  <colspec colwidth="16.6*"/>
+  <thead>
+    <row>
+      <entry></entry>
+      <entry></entry>
+      <entry><para>String</para></entry>
+      <entry><para>Number</para></entry>
+      <entry><para>Array</para></entry>
+      <entry><para>Undefined</para></entry>
+    </row>
+  </thead>
+  <tbody>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">String</emphasis></para></entry>
+      <entry><para>String</para></entry>
+      <entry><para>String</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">Number</emphasis></para></entry>
+      <entry><para>Number if can be converted, else false</para></entry>
+      <entry><para>Number</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry><para><emphasis role="bold">Type</emphasis></para></entry>
+      <entry><para><emphasis role="bold">Array</emphasis></para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>Array</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry><para><emphasis role="bold">Requested:</emphasis></para></entry>
+      <entry><para><emphasis role="bold">Scalar</emphasis></para></entry>
+      <entry><para>Scalar</para></entry>
+      <entry><para>Scalar</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">Undefined</emphasis></para></entry>
+      <entry><para>String</para></entry>
+      <entry><para>Number</para></entry>
+      <entry><para>Array</para></entry>
+      <entry><para>Undefined</para></entry>
+    </row>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">Value Cookie</emphasis></para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para>
+      </entry><entry><para>false</para></entry>
+    </row>
+  </tbody>
+</tgroup>
+</informaltable>
+@end docbook
+
+@ifnotplaintext
+@ifnotdocbook
 @multitable @columnfractions .50 .50
 @headitem @tab Type of Actual Value:
 @end multitable
@@ -29791,11 +31344,9 @@ value type, as appropriate.  This behavior is summarized in
 @item @tab @b{Undefined} @tab String @tab Number @tab Array @tab Undefined
 @item @tab @b{Value Cookie} @tab false @tab false @tab false @tab false
 @end multitable
-@end float
+@end ifnotdocbook
 @end ifnotplaintext
 @ifplaintext
-@float Table,table-value-types-returned
-@caption{Value Types Returned}
 @example
                         +-------------------------------------------------+
                         |                Type of Actual Value:            |
@@ -29819,60 +31370,62 @@ value type, as appropriate.  This behavior is summarized in
 |           | Cookie    |            |            |           |           |
 +-----------+-----------+------------+------------+-----------+-----------+
 @end example
-@end float
 @end ifplaintext
+@end float
 
-@node Constructor Functions
-@subsection Constructor Functions and Convenience Macros
+@node Memory Allocation Functions
+@subsection Memory Allocation Functions and Convenience Macros
+@cindex allocating memory for extensions
+@cindex extensions, allocating memory
 
-The API provides a number of @dfn{constructor} functions for creating
-string and numeric values, as well as a number of convenience macros.
-This @value{SUBSECTION} presents them all as function prototypes, in
-the way that extension code would use them.
+The API provides a number of @dfn{memory allocation} functions for
+allocating memory that can be passed to @command{gawk}, as well as a number of
+convenience macros.
 
 @table @code
-@item static inline awk_value_t *
-@itemx make_const_string(const char *string, size_t length, awk_value_t *result)
-This function creates a string value in the @code{awk_value_t} variable
-pointed to by @code{result}. It expects @code{string} to be a C string constant
-(or other string data), and automatically creates a @emph{copy} of the data
-for storage in @code{result}. It returns @code{result}.
+@item void *gawk_malloc(size_t size);
+Call @command{gawk}-provided @code{api_malloc()} to allocate storage that may
+be passed to @command{gawk}.
 
-@item static inline awk_value_t *
-@itemx make_malloced_string(const char *string, size_t length, awk_value_t *result)
-This function creates a string value in the @code{awk_value_t} variable
-pointed to by @code{result}. It expects @code{string} to be a @samp{char *}
-value pointing to data previously obtained from @code{malloc()}. The idea here
-is that the data is passed directly to @command{gawk}, which assumes
-responsibility for it. It returns @code{result}.
+@item void *gawk_calloc(size_t nmemb, size_t size);
+Call @command{gawk}-provided @code{api_calloc()} to allocate storage that may
+be passed to @command{gawk}.
 
-@item static inline awk_value_t *
-@itemx make_null_string(awk_value_t *result)
-This specialized function creates a null string (the ``undefined'' value)
-in the @code{awk_value_t} variable pointed to by @code{result}.
-It returns @code{result}.
+@item void *gawk_realloc(void *ptr, size_t size);
+Call @command{gawk}-provided @code{api_realloc()} to allocate storage that may
+be passed to @command{gawk}.
 
-@item static inline awk_value_t *
-@itemx make_number(double num, awk_value_t *result)
-This function simply creates a numeric value in the @code{awk_value_t} variable
-pointed to by @code{result}.
+@item void gawk_free(void *ptr);
+Call @command{gawk}-provided @code{api_free()} to release storage that was
+allocated with @code{gawk_malloc()}, @code{gawk_calloc()} or @code{gawk_realloc()}.
 @end table
 
-Two convenience macros may be used for allocating storage from @code{malloc()}
-and @code{realloc()}. If the allocation fails, they cause @command{gawk} to
-exit with a fatal error message.  They should be used as if they were
+The API has to provide these functions because it is possible
+for an extension to be compiled and linked against a different
+version of the C library than was used for the @command{gawk}
+executable.@footnote{This is more common on MS-Windows systems, but
+can happen on Unix-like systems as well.} If @command{gawk} were
+to use its version of @code{free()} when the memory came from an
+unrelated version of @code{malloc()}, unexpected behavior would
+likely result.
+
+Two convenience macros may be used for allocating storage
+from the API-provided function pointers @code{api_malloc()} and
+@code{api_realloc()}. If the allocation fails, they cause @command{gawk}
+to exit with a fatal error message.  They should be used as if they were
 procedure calls that do not return a value.
 
 @table @code
 @item #define emalloc(pointer, type, size, message) @dots{}
 The arguments to this macro are as follows:
+
 @c nested table
 @table @code
 @item pointer
 The pointer variable to point at the allocated storage.
 
 @item type
-The type of the pointer variable, used to create a cast for the call to @code{malloc()}.
+The type of the pointer variable, used to create a cast for the call to @code{api_malloc()}.
 
 @item size
 The total number of bytes to be allocated.
@@ -29896,13 +31449,51 @@ make_malloced_string(message, strlen(message), & result);
 @end example
 
 @item #define erealloc(pointer, type, size, message) @dots{}
-This is like @code{emalloc()}, but it calls @code{realloc()},
-instead of @code{malloc()}.
+This is like @code{emalloc()}, but it calls @code{api_realloc()},
+instead of @code{api_malloc()}.
 The arguments are the same as for the @code{emalloc()} macro.
 @end table
 
+@node Constructor Functions
+@subsection Constructor Functions
+
+The API provides a number of @dfn{constructor} functions for creating
+string and numeric values, as well as a number of convenience macros.
+This @value{SUBSECTION} presents them all as function prototypes, in
+the way that extension code would use them.
+
+@table @code
+@item static inline awk_value_t *
+@itemx make_const_string(const char *string, size_t length, awk_value_t *result)
+This function creates a string value in the @code{awk_value_t} variable
+pointed to by @code{result}. It expects @code{string} to be a C string constant
+(or other string data), and automatically creates a @emph{copy} of the data
+for storage in @code{result}. It returns @code{result}.
+
+@item static inline awk_value_t *
+@itemx make_malloced_string(const char *string, size_t length, awk_value_t *result)
+This function creates a string value in the @code{awk_value_t} variable
+pointed to by @code{result}. It expects @code{string} to be a @samp{char *}
+value pointing to data previously obtained from the api-provided functions @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()}. The idea here
+is that the data is passed directly to @command{gawk}, which assumes
+responsibility for it. It returns @code{result}.
+
+@item static inline awk_value_t *
+@itemx make_null_string(awk_value_t *result)
+This specialized function creates a null string (the ``undefined'' value)
+in the @code{awk_value_t} variable pointed to by @code{result}.
+It returns @code{result}.
+
+@item static inline awk_value_t *
+@itemx make_number(double num, awk_value_t *result)
+This function simply creates a numeric value in the @code{awk_value_t} variable
+pointed to by @code{result}.
+@end table
+
 @node Registration Functions
 @subsection Registration Functions
+@cindex register extension
+@cindex extension registration
 
 This @value{SECTION} describes the API functions for
 registering parts of your extension with @command{gawk}.
@@ -29947,8 +31538,8 @@ Letter case in function names is significant.
 This is a pointer to the C function that provides the desired
 functionality.
 The function must fill in the result with either a number
-or a string. @command{awk} takes ownership of any string memory.
-As mentioned earlier, string memory @strong{must} come from @code{malloc()}.
+or a string. @command{gawk} takes ownership of any string memory.
+As mentioned earlier, string memory @strong{must} come from the api-provided functions @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()}.
 
 The @code{num_actual_args} argument tells the C function how many
 actual parameters were passed from the calling @command{awk} code.
@@ -29979,7 +31570,7 @@ empty string (@code{""}).  The @code{func} pointer is the address of a
 
 An @dfn{exit callback} function is a function that
 @command{gawk} calls before it exits.
-Such functions are useful if you have general ``clean up'' tasks
+Such functions are useful if you have general ``cleanup'' tasks
 that should be performed in your extension (such as closing data
 base connections or other resource deallocations).
 You can register such
@@ -29989,6 +31580,7 @@ a function with @command{gawk} using the following function.
 @item void awk_atexit(void (*funcp)(void *data, int exit_status),
 @itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ void *arg0);
 The parameters are:
+
 @c nested table
 @table @code
 @item funcp
@@ -30024,6 +31616,7 @@ is invoked with the @option{--version} option.
 
 @node Input Parsers
 @subsubsection Customized Input Parsers
+@cindex customized input parser
 
 By default, @command{gawk} reads text files as its input. It uses the value
 of @code{RS} to find the end of the record, and then uses @code{FS}
@@ -30081,8 +31674,9 @@ A pointer to your @code{@var{XXX}_can_take_file()} function.
 A pointer to your @code{@var{XXX}_take_control_of()} function.
 
 @item awk_const struct input_parser *awk_const next;
-This pointer is used by @command{gawk}.
-The extension cannot modify it.
+This is for use by @command{gawk};
+therefore it is marked @code{awk_const} so that the extension cannot
+modify it.
 @end table
 
 The steps are as follows:
@@ -30129,7 +31723,7 @@ open the file, then @code{fd} will @emph{not} be equal to
 @code{INVALID_HANDLE}. Otherwise, it will.
 
 @item struct stat sbuf;
-If file descriptor is valid, then @command{gawk} will have filled
+If the file descriptor is valid, then @command{gawk} will have filled
 in this structure via a call to the @code{fstat()} system call.
 @end table
 
@@ -30271,7 +31865,9 @@ Register the input parser pointed to by @code{input_parser} with
 
 @node Output Wrappers
 @subsubsection Customized Output Wrappers
+@cindex customized output wrapper
 
+@cindex output wrapper
 An @dfn{output wrapper} is the mirror image of an input parser.
 It allows an extension to take over the output to a file opened
 with the @samp{>} or @samp{>>} I/O redirection operators (@pxref{Redirection}).
@@ -30308,8 +31904,8 @@ as described below, and return true if successful, false otherwise.
 
 @item awk_const struct output_wrapper *awk_const next;
 This is for use by @command{gawk};
-therefore they are marked @code{awk_const} so that the extension cannot
-modify them.
+therefore it is marked @code{awk_const} so that the extension cannot
+modify it.
 @end table
 
 The @code{awk_output_buf_t} structure looks like this:
@@ -30371,7 +31967,7 @@ The @code{@var{XXX}_can_take_file()} function should make a decision based
 upon the @code{name} and @code{mode} fields, and any additional state
 (such as @command{awk} variable values) that is appropriate.
 
-When @command{gawk} calls @code{@var{XXX}_take_control_of()}, it should fill
+When @command{gawk} calls @code{@var{XXX}_take_control_of()}, that function should fill
 in the other fields, as appropriate, except for @code{fp}, which it should just
 use normally.
 
@@ -30385,6 +31981,7 @@ Register the output wrapper pointed to by @code{output_wrapper} with
 
 @node Two-way processors
 @subsubsection Customized Two-way Processors
+@cindex customized two-way processor
 
 A @dfn{two-way processor} combines an input parser and an output wrapper for
 two-way I/O with the @samp{|&} operator (@pxref{Redirection}).  It makes identical
@@ -30411,7 +32008,7 @@ The fields are as follows:
 The name of the two-way processor.
 
 @item awk_bool_t (*can_take_two_way)(const char *name);
-This function returns true if it wants to take over two-way I/O for this filename.
+This function returns true if it wants to take over two-way I/O for this @value{FN}.
 It should not change any state (variable
 values, etc.) within @command{gawk}.
 
@@ -30424,8 +32021,8 @@ This function should fill in the @code{awk_input_buf_t} and
 
 @item awk_const struct two_way_processor *awk_const next;
 This is for use by @command{gawk};
-therefore they are marked @code{awk_const} so that the extension cannot
-modify them.
+therefore it is marked @code{awk_const} so that the extension cannot
+modify it.
 @end table
 
 As with the input parser and output processor, you provide
@@ -30442,6 +32039,8 @@ Register the two-way processor pointed to by @code{two_way_processor} with
 
 @node Printing Messages
 @subsection Printing Messages
+@cindex printing messages from extensions
+@cindex messages from extensions
 
 You can print different kinds of warning messages from your
 extension, as described below.  Note that for these functions,
@@ -30515,6 +32114,7 @@ for more information on creating arrays.
 
 @node Symbol Table Access
 @subsection Symbol Table Access
+@cindex accessing global variables from extensions
 
 Two sets of routines provide access to global variables, and one set
 allows you to create and release cached values.
@@ -30560,6 +32160,13 @@ An extension can look up the value of @command{gawk}'s special variables.
 However, with the exception of the @code{PROCINFO} array, an extension
 cannot change any of those variables.
 
+@quotation NOTE
+It is possible for the lookup of @code{PROCINFO} to fail. This happens if
+the @command{awk} program being run does not reference @code{PROCINFO};
+in this case @command{gawk} doesn't bother to create the array and
+populate it.
+@end quotation
+
 @node Symbol table by cookie
 @subsubsection Variable Access and Update by Cookie
 
@@ -30581,7 +32188,7 @@ Return false if the value cannot be retrieved.
 
 @item awk_bool_t sym_update_scalar(awk_scalar_t cookie, awk_value_t *value);
 Update the value associated with a scalar cookie.  Return false if
-the new value is not one of @code{AWK_STRING} or @code{AWK_NUMBER}.
+the new value is not of type @code{AWK_STRING} or @code{AWK_NUMBER}.
 Here too, the built-in variables may not be updated.
 @end table
 
@@ -30686,7 +32293,7 @@ assign those values to variables using @code{sym_update()}
 or @code{sym_update_scalar()}, as you like.
 
 However, you can understand the point of cached values if you remember that
-@emph{every} string value's storage @emph{must} come from @code{malloc()}.
+@emph{every} string value's storage @emph{must} come from @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()}.
 If you have 20 variables, all of which have the same string value, you
 must create 20 identical copies of the string.@footnote{Numeric values
 are clearly less problematic, requiring only a C @code{double} to store.}
@@ -30699,7 +32306,7 @@ is what the routines in this section let you do.  The functions are as follows:
 @item awk_bool_t create_value(awk_value_t *value, awk_value_cookie_t *result);
 Create a cached string or numeric value from @code{value} for efficient later
 assignment.
-Only @code{AWK_NUMBER} and @code{AWK_STRING} values are allowed.  Any other type
+Only values of type @code{AWK_NUMBER} and @code{AWK_STRING} are allowed.  Any other type
 is rejected.  While @code{AWK_UNDEFINED} could be allowed, doing so would
 result in inferior performance.
 
@@ -30760,18 +32367,19 @@ What happens if @command{awk} code assigns a new value to @code{VAR1},
 are all the others be changed too?''
 
 That's a great question. The answer is that no, it's not a problem.
-Internally, @command{gawk} uses reference-counted strings. This means
+Internally, @command{gawk} uses @dfn{reference-counted strings}. This means
 that many variables can share the same string value, and @command{gawk}
 keeps track of the usage.  When a variable's value changes, @command{gawk}
 simply decrements the reference count on the old value and updates
 the variable to use the new value.
 
-Finally, as part of your clean up action (@pxref{Exit Callback Functions})
+Finally, as part of your cleanup action (@pxref{Exit Callback Functions})
 you should release any cached values that you created, using
 @code{release_value()}.
 
 @node Array Manipulation
 @subsection Array Manipulation
+@cindex array manipulation in extensions
 
 The primary data structure@footnote{Okay, the only data structure.} in @command{awk}
 is the associative array (@pxref{Arrays}).
@@ -30883,7 +32491,7 @@ requires that you understand how such values are converted to strings
 (@pxref{Conversion}); thus using integral values is safest.
 
 As with @emph{all} strings passed into @code{gawk} from an extension,
-the string value of @code{index} must come from @code{malloc()}, and
+the string value of @code{index} must come from the API-provided functions @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()} and
 @command{gawk} releases the storage.
 
 @item awk_bool_t set_array_element(awk_array_t a_cookie,
@@ -30891,7 +32499,8 @@ the string value of @code{index} must come from @code{malloc()}, and
 @itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ const@ awk_value_t *const value);
 In the array represented by @code{a_cookie}, create or modify
 the element whose index is given by @code{index}.
-The @code{ARGV} and @code{ENVIRON} arrays may not be changed.
+The @code{ARGV} and @code{ENVIRON} arrays may not be changed,
+although the @code{PROCINFO} array can be.
 
 @item awk_bool_t set_array_element_by_elem(awk_array_t a_cookie,
 @itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ awk_element_t element);
@@ -31162,7 +32771,7 @@ you must add the new array to its parent before adding any elements to it.
 Thus, the correct way to build an array is to work ``top down.''  Create
 the array, and immediately install it in @command{gawk}'s symbol table
 using @code{sym_update()}, or install it as an element in a previously
-existing array using @code{set_element()}.  We show example code shortly.
+existing array using @code{set_array_element()}.  We show example code shortly.
 
 @item
 Due to gawk internals, after using @code{sym_update()} to install an array
@@ -31188,7 +32797,7 @@ of the array cookie after the call to @code{set_element()}.
 @end enumerate
 
 The following C code is a simple test extension to create an array
-with two regular elements and with a subarray. The leading @samp{#include}
+with two regular elements and with a subarray. The leading @code{#include}
 directives and boilerplate variable declarations are omitted for brevity.
 The first step is to create a new array and then install it
 in the symbol table:
@@ -31351,6 +32960,8 @@ information about how @command{gawk} was invoked.
 
 @node Extension Versioning
 @subsubsection API Version Constants and Variables
+@cindex API version
+@cindex extension API version
 
 The API provides both a ``major'' and a ``minor'' version number.
 The API versions are available at compile time as constants:
@@ -31404,18 +33015,23 @@ provided in @file{gawkapi.h} (discussed later, in
 
 @node Extension API Informational Variables
 @subsubsection Informational Variables
+@cindex API informational variables
+@cindex extension API informational variables
 
 The API provides access to several variables that describe
 whether the corresponding command-line options were enabled when
 @command{gawk} was invoked.  The variables are:
 
 @table @code
+@item do_debug
+This variable is true if @command{gawk} was invoked with @option{--debug} option.
+
 @item do_lint
 This variable is true if @command{gawk} was invoked with @option{--lint} option
 (@pxref{Options}).
 
-@item do_traditional
-This variable is true if @command{gawk} was invoked with @option{--traditional} option.
+@item do_mpfr
+This variable is true if @command{gawk} was invoked with @option{--bignum} option.
 
 @item do_profile
 This variable is true if @command{gawk} was invoked with @option{--profile} option.
@@ -31423,11 +33039,8 @@ This variable is true if @command{gawk} was invoked with @option{--profile} opti
 @item do_sandbox
 This variable is true if @command{gawk} was invoked with @option{--sandbox} option.
 
-@item do_debug
-This variable is true if @command{gawk} was invoked with @option{--debug} option.
-
-@item do_mpfr
-This variable is true if @command{gawk} was invoked with @option{--bignum} option.
+@item do_traditional
+This variable is true if @command{gawk} was invoked with @option{--traditional} option.
 @end table
 
 The value of @code{do_lint} can change if @command{awk} code
@@ -31478,8 +33091,14 @@ These variables and functions are as follows:
 
 @table @code
 @item int plugin_is_GPL_compatible;
-This asserts that the extension is compatible with the GNU GPL
-(@pxref{Copying}).  If your extension does not have this, @command{gawk}
+This asserts that the extension is compatible with
+@ifclear FOR_PRINT
+the GNU GPL (@pxref{Copying}).
+@end ifclear
+@ifset FOR_PRINT
+the GNU GPL.
+@end ifset
+If your extension does not have this, @command{gawk}
 will not load it (@pxref{Plugin License}).
 
 @item static gawk_api_t *const api;
@@ -31503,8 +33122,9 @@ as described earlier (@pxref{Extension Functions}).
 It can then be looped over for multiple calls to
 @code{add_ext_func()}.
 
+@c Use @var{OR} for docbook
 @item static awk_bool_t (*init_func)(void) = NULL;
-@itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @r{OR}
+@itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @var{OR}
 @itemx static awk_bool_t init_my_module(void) @{ @dots{} @}
 @itemx static awk_bool_t (*init_func)(void) = init_my_module;
 If you need to do some initialization work, you should define a
@@ -31549,6 +33169,8 @@ the version string with @command{gawk}.
 
 @node Finding Extensions
 @section How @command{gawk} Finds Extensions
+@cindex extension search path
+@cindex finding extensions
 
 Compiled extensions have to be installed in a directory where
 @command{gawk} can find them.  If @command{gawk} is configured and
@@ -31559,6 +33181,7 @@ path with a list of directories to search for compiled extensions.
 
 @node Extension Example
 @section Example: Some File Functions
+@cindex extension example
 
 @quotation
 @i{No matter where you go, there you are.}
@@ -31740,7 +33363,6 @@ Those are followed by the necessary variable declarations
 to make use of the API macros and boilerplate code
 (@pxref{Extension API Boilerplate}).
 
-@c break line for page breaking
 @example
 #ifdef HAVE_CONFIG_H
 #include <config.h>
@@ -31827,7 +33449,6 @@ The @code{stat()} extension is more involved.  First comes a function
 that turns a numeric mode into a printable representation
 (e.g., 644 becomes @samp{-rw-r--r--}). This is omitted here for brevity:
 
-@c break line for page breaking
 @example
 /* format_mode --- turn a stat mode field into something readable */
 
@@ -32017,7 +33638,7 @@ do_stat(int nargs, awk_value_t *result)
     awk_array_t array;
     int ret;
     struct stat sbuf;
-    /* default is stat() */
+    /* default is lstat() */
     int (*statfunc)(const char *path, struct stat *sbuf) = lstat;
 
     assert(result != NULL);
@@ -32101,7 +33722,9 @@ structures for loading each function into @command{gawk}:
 static awk_ext_func_t func_table[] = @{
     @{ "chdir", do_chdir, 1 @},
     @{ "stat",  do_stat, 2 @},
+#ifndef __MINGW32__
     @{ "fts",   do_fts, 3 @},
+#endif
 @};
 @end example
 
@@ -32115,9 +33738,7 @@ everything that needs to be loaded.  It is simplest to use the
 dl_load_func(func_table, filefuncs, "")
 @end example
 
-And that's it!  As an exercise, consider adding functions to
-implement system calls such as @code{chown()}, @code{chmod()},
-and @code{umask()}.
+And that's it!
 
 @node Using Internal File Ops
 @subsection Integrating The Extensions
@@ -32129,7 +33750,7 @@ code must be compiled.  Assuming that the functions are in
 a file named @file{filefuncs.c}, and @var{idir} is the location
 of the @file{gawkapi.h} header file,
 the following steps@footnote{In practice, you would probably want to
-use the GNU Autotools---Automake, Autoconf, Libtool, and Gettext---to
+use the GNU Autotools---Automake, Autoconf, Libtool, and @command{gettext}---to
 configure and build your libraries. Instructions for doing so are beyond
 the scope of this @value{DOCUMENT}. @xref{gawkextlib}, for WWW links to
 the tools.} create a GNU/Linux shared library:
@@ -32171,7 +33792,7 @@ BEGIN @{
 @end example
 
 The @env{AWKLIBPATH} environment variable tells
-@command{gawk} where to find shared libraries (@pxref{Finding Extensions}).
+@command{gawk} where to find extensions (@pxref{Finding Extensions}).
 We set it to the current directory and run the program:
 
 @example
@@ -32203,6 +33824,7 @@ $ @kbd{AWKLIBPATH=$PWD gawk -f testff.awk}
 
 @node Extension Samples
 @section The Sample Extensions In The @command{gawk} Distribution
+@cindex extensions distributed with @command{gawk}
 
 This @value{SECTION} provides brief overviews of the sample extensions
 that come in the @command{gawk} distribution. Some of them are intended
@@ -32233,19 +33855,19 @@ Others mainly provide example code that shows how to use the extension API.
 The @code{filefuncs} extension provides three different functions, as follows:
 The usage is:
 
-@table @code
+@table @asis
 @item @@load "filefuncs"
 This is how you load the extension.
 
-@cindex @code{chdir} extension function
-@item result = chdir("/some/directory")
+@cindex @code{chdir()} extension function
+@item @code{result = chdir("/some/directory")}
 The @code{chdir()} function is a direct hook to the @code{chdir()}
 system call to change the current directory.  It returns zero
 upon success or less than zero upon error.  In the latter case it updates
 @code{ERRNO}.
 
-@cindex @code{stat} extension function
-@item result = stat("/some/path", statdata [, follow])
+@cindex @code{stat()} extension function
+@item @code{result = stat("/some/path", statdata} [@code{, follow}]@code{)}
 The @code{stat()} function provides a hook into the
 @code{stat()} system call.
 It returns zero upon success or less than zero upon error.
@@ -32258,69 +33880,27 @@ In all cases, it clears the @code{statdata} array.
 When the call is successful, @code{stat()} fills the @code{statdata}
 array with information retrieved from the filesystem, as follows:
 
-@c nested table
-@multitable @columnfractions .25 .60
-@item @code{statdata["name"]} @tab
-The name of the file.
-
-@item @code{statdata["dev"]} @tab
-Corresponds to the @code{st_dev} field in the @code{struct stat}.
-
-@item @code{statdata["ino"]} @tab
-Corresponds to the @code{st_ino} field in the @code{struct stat}.
-
-@item @code{statdata["mode"]} @tab
-Corresponds to the @code{st_mode} field in the @code{struct stat}.
-
-@item @code{statdata["nlink"]} @tab
-Corresponds to the @code{st_nlink} field in the @code{struct stat}.
-
-@item @code{statdata["uid"]} @tab
-Corresponds to the @code{st_uid} field in the @code{struct stat}.
-
-@item @code{statdata["gid"]} @tab
-Corresponds to the @code{st_gid} field in the @code{struct stat}.
-
-@item @code{statdata["size"]} @tab
-Corresponds to the @code{st_size} field in the @code{struct stat}.
-
-@item @code{statdata["atime"]} @tab
-Corresponds to the @code{st_atime} field in the @code{struct stat}.
-
-@item @code{statdata["mtime"]} @tab
-Corresponds to the @code{st_mtime} field in the @code{struct stat}.
-
-@item @code{statdata["ctime"]} @tab
-Corresponds to the @code{st_ctime} field in the @code{struct stat}.
-
-@item @code{statdata["rdev"]} @tab
-Corresponds to the @code{st_rdev} field in the @code{struct stat}.
-This element is only present for device files.
-
-@item @code{statdata["major"]} @tab
-Corresponds to the @code{st_major} field in the @code{struct stat}.
-This element is only present for device files.
-
-@item @code{statdata["minor"]} @tab
-Corresponds to the @code{st_minor} field in the @code{struct stat}.
-This element is only present for device files.
-
-@item @code{statdata["blksize"]} @tab
-Corresponds to the @code{st_blksize} field in the @code{struct stat},
-if this field is present on your system.
-(It is present on all modern systems that we know of.)
-
-@item @code{statdata["pmode"]} @tab
-A human-readable version of the mode value, such as printed by
-@command{ls}.  For example, @code{"-rwxr-xr-x"}.
-
-@item @code{statdata["linkval"]} @tab
-If the named file is a symbolic link, this element will exist
-and its value is the value of the symbolic link (where the
-symbolic link points to).
-
-@item @code{statdata["type"]} @tab
-The type of the file as a string. One of
+@multitable @columnfractions .15 .50 .20
+@headitem Subscript @tab Field in @code{struct stat} @tab File type
+@item @code{"name"} @tab The @value{FN} @tab All
+@item @code{"dev"} @tab @code{st_dev} @tab All
+@item @code{"ino"} @tab @code{st_ino} @tab All
+@item @code{"mode"} @tab @code{st_mode} @tab All
+@item @code{"nlink"} @tab @code{st_nlink} @tab All
+@item @code{"uid"} @tab @code{st_uid} @tab All
+@item @code{"gid"} @tab @code{st_gid} @tab All
+@item @code{"size"} @tab @code{st_size} @tab All
+@item @code{"atime"} @tab @code{st_atime} @tab All
+@item @code{"mtime"} @tab @code{st_mtime} @tab All
+@item @code{"ctime"} @tab @code{st_ctime} @tab All
+@item @code{"rdev"} @tab @code{st_rdev} @tab Device files
+@item @code{"major"} @tab @code{st_major} @tab Device files
+@item @code{"minor"} @tab @code{st_minor} @tab Device files
+@item @code{"blksize"} @tab @code{st_blksize} @tab All
+@item @code{"pmode"} @tab A human-readable version of the mode value, such as printed by
+@command{ls}.  For example, @code{"-rwxr-xr-x"} @tab All
+@item @code{"linkval"} @tab The value of the symbolic link @tab Symbolic links
+@item @code{"type"} @tab The type of the file as a string. One of
 @code{"file"},
 @code{"blockdev"},
 @code{"chardev"},
@@ -32331,12 +33911,12 @@ The type of the file as a string. One of
 @code{"door"},
 or
 @code{"unknown"}.
-Not all systems support all file types.
+Not all systems support all file types. @tab All
 @end multitable
 
-@cindex @code{fts} extension function
-@item flags = or(FTS_PHYSICAL, ...)
-@itemx result = fts(pathlist, flags, filedata)
+@cindex @code{fts()} extension function
+@item @code{flags = or(FTS_PHYSICAL, ...)}
+@itemx @code{result = fts(pathlist, flags, filedata)}
 Walk the file trees provided in @code{pathlist} and fill in the
 @code{filedata} array as described below.  @code{flags} is the bitwise
 OR of several predefined constant values, also described below.
@@ -32353,7 +33933,7 @@ The arguments are as follows:
 
 @table @code
 @item pathlist
-An array of filenames.  The element values are used; the index values are ignored.
+An array of @value{FN}s.  The element values are used; the index values are ignored.
 
 @item flags
 This should be the bitwise OR of one or more of the following
@@ -32455,58 +34035,48 @@ See @file{test/fts.awk} in the @command{gawk} distribution for an example.
 @node Extension Sample Fnmatch
 @subsection Interface To @code{fnmatch()}
 
-@cindex @code{fnmatch} extension function
 This extension provides an interface to the C library
 @code{fnmatch()} function.  The usage is:
 
-@example
-@@load "fnmatch"
+@table @code
+@item @@load "fnmatch"
+This is how you load the extension.
 
-result = fnmatch(pattern, string, flags)
-@end example
+@cindex @code{fnmatch()} extension function
+@item result = fnmatch(pattern, string, flags)
+The return value is zero on success, @code{FNM_NOMATCH}
+if the string did not match the pattern, or
+a different non-zero value if an error occurred.
+@end table
 
-The @code{fnmatch} extension adds a single function named
-@code{fnmatch()}, one constant (@code{FNM_NOMATCH}), and an array of
-flag values named @code{FNM}.
+Besides the @code{fnmatch()} function, the @code{fnmatch} extension
+adds one constant (@code{FNM_NOMATCH}), and an array of flag values
+named @code{FNM}.
 
 The arguments to @code{fnmatch()} are:
 
 @table @code
 @item pattern
-The filename wildcard to match.
+The @value{FN} wildcard to match.
 
 @item string
-The filename string.
+The @value{FN} string.
 
 @item flag
 Either zero, or the bitwise OR of one or more of the
 flags in the @code{FNM} array.
 @end table
 
-The return value is zero on success, @code{FNM_NOMATCH}
-if the string did not match the pattern, or
-a different non-zero value if an error occurred.
-
 The flags are follows:
 
 @multitable @columnfractions .25 .75
-@item @code{FNM["CASEFOLD"]} @tab
-Corresponds to the @code{FNM_CASEFOLD} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["FILE_NAME"]} @tab
-Corresponds to the @code{FNM_FILE_NAME} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["LEADING_DIR"]} @tab
-Corresponds to the @code{FNM_LEADING_DIR} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["NOESCAPE"]} @tab
-Corresponds to the @code{FNM_NOESCAPE} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["PATHNAME"]} @tab
-Corresponds to the @code{FNM_PATHNAME} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["PERIOD"]} @tab
-Corresponds to the @code{FNM_PERIOD} flag as defined in @code{fnmatch()}.
+@headitem Array element @tab Corresponding flag defined by @code{fnmatch()}
+@item @code{FNM["CASEFOLD"]} @tab @code{FNM_CASEFOLD}
+@item @code{FNM["FILE_NAME"]} @tab @code{FNM_FILE_NAME}
+@item @code{FNM["LEADING_DIR"]} @tab @code{FNM_LEADING_DIR}
+@item @code{FNM["NOESCAPE"]} @tab @code{FNM_NOESCAPE}
+@item @code{FNM["PATHNAME"]} @tab @code{FNM_PATHNAME}
+@item @code{FNM["PERIOD"]} @tab @code{FNM_PERIOD}
 @end multitable
 
 Here is an example:
@@ -32528,21 +34098,21 @@ The @code{fork} extension adds three functions, as follows.
 @item @@load "fork"
 This is how you load the extension.
 
-@cindex @code{fork} extension function
+@cindex @code{fork()} extension function
 @item pid = fork()
-This function creates a new process. The return value is the zero in the
-child and the process-id number of the child in the parent, or @minus{}1
+This function creates a new process. The return value is zero in the
+child and the process-ID number of the child in the parent, or @minus{}1
 upon error. In the latter case, @code{ERRNO} indicates the problem.
 In the child, @code{PROCINFO["pid"]} and @code{PROCINFO["ppid"]} are
 updated to reflect the correct values.
 
-@cindex @code{waitpid} extension function
+@cindex @code{waitpid()} extension function
 @item ret = waitpid(pid)
-This function takes a numeric argument, which is the process-id to
+This function takes a numeric argument, which is the process-ID to
 wait for. The return value is that of the
 @code{waitpid()} system call.
 
-@cindex @code{wait} extension function
+@cindex @code{wait()} extension function
 @item ret = wait()
 This function waits for the first child to die.
 The return value is that of the
@@ -32597,8 +34167,8 @@ standard output to a temporary file configured to have the same owner
 and permissions as the original.  After the file has been processed,
 the extension restores standard output to its original destination.
 If @code{INPLACE_SUFFIX} is not an empty string, the original file is
-linked to a backup filename created by appending that suffix.  Finally,
-the temporary file is renamed to the original filename.
+linked to a backup @value{FN} created by appending that suffix.  Finally,
+the temporary file is renamed to the original @value{FN}.
 
 If any error occurs, the extension issues a fatal error to terminate
 processing immediately without damaging the original file.
@@ -32616,9 +34186,6 @@ $ @kbd{gawk -i inplace -v INPLACE_SUFFIX=.bak '@{ gsub(/foo/, "bar") @}}
 > @kbd{@{ print @}' file1 file2 file3}
 @end example
 
-We leave it as an exercise to write a wrapper script that presents an
-interface similar to @samp{sed -i}.
-
 @node Extension Sample Ord
 @subsection Character and Numeric values: @code{ord()} and @code{chr()}
 
@@ -32629,11 +34196,11 @@ The @code{ordchr} extension adds two functions, named
 @item @@load "ordchr"
 This is how you load the extension.
 
-@cindex @code{ord} extension function
+@cindex @code{ord()} extension function
 @item number = ord(string)
 Return the numeric value of the first character in @code{string}.
 
-@cindex @code{chr} extension function
+@cindex @code{chr()} extension function
 @item char = chr(number)
 Return a string whose first character is that represented by @code{number}.
 @end table
@@ -32664,11 +34231,14 @@ on the command line (or with @code{getline}),
 they are read, with each entry returned as a record.
 
 The record consists of three fields. The first two are the inode number and the
-filename, separated by a forward slash character.
+@value{FN}, separated by a forward slash character.
 On systems where the directory entry contains the file type, the record
 has a third field (also separated by a slash) which is a single letter
-indicating the type of the file:
+indicating the type of the file. The letters are file types are shown
+in @ref{table-readdir-file-types}.
 
+@float Table,table-readdir-file-types
+@caption{File Types Returned By @code{readdir()}}
 @multitable @columnfractions .1 .9
 @headitem Letter @tab File Type
 @item @code{b} @tab Block device
@@ -32680,6 +34250,7 @@ indicating the type of the file:
 @item @code{s} @tab Socket
 @item @code{u} @tab Anything else (unknown)
 @end multitable
+@end float
 
 On systems without the file type information, the third field is always
 @samp{u}.
@@ -32714,12 +34285,12 @@ Here is an example:
 
 BEGIN @{
     REVOUT = 1
-    print "hello, world" > "/dev/stdout"
+    print "don't panic" > "/dev/stdout"
 @}
 @end example
 
 The output from this program is:
-@samp{dlrow ,olleh}.
+@samp{cinap t'nod}.
 
 @node Extension Sample Rev2way
 @subsection Two-Way I/O Example
@@ -32736,13 +34307,22 @@ The following example shows how to use it:
 
 BEGIN @{
     cmd = "/magic/mirror"
-    print "hello, world" |& cmd
+    print "don't panic" |& cmd
     cmd |& getline result
     print result
     close(cmd)
 @}
 @end example
 
+The output from this program
+@ifnotinfo
+also is:
+@end ifnotinfo
+@ifinfo
+is:
+@end ifinfo
+@samp{cinap t'nod}.
+
 @node Extension Sample Read write array
 @subsection Dumping and Restoring An Array
 
@@ -32750,14 +34330,14 @@ The @code{rwarray} extension adds two functions,
 named @code{writea()} and @code{reada()}, as follows:
 
 @table @code
-@cindex @code{writea} extension function
+@cindex @code{writea()} extension function
 @item ret = writea(file, array)
 This function takes a string argument, which is the name of the file
-to which dump the array, and the array itself as the second argument.
-@code{writea()} understands multidimensional arrays.  It returns one on
+to which to dump the array, and the array itself as the second argument.
+@code{writea()} understands arrays of arrays.  It returns one on
 success, or zero upon failure.
 
-@cindex @code{reada} extension function
+@cindex @code{reada()} extension function
 @item ret = reada(file, array)
 @code{reada()} is the inverse of @code{writea()};
 it reads the file named as its first argument, filling in
@@ -32794,17 +34374,23 @@ ret = reada("arraydump.bin", array)
 @subsection Reading An Entire File
 
 The @code{readfile} extension adds a single function
-named @code{readfile()}:
+named @code{readfile()}, and an input parser:
 
 @table @code
 @item @@load "readfile"
 This is how you load the extension.
 
-@cindex @code{readfile} extension function
+@cindex @code{readfile()} extension function
 @item result = readfile("/some/path")
 The argument is the name of the file to read.  The return value is a
 string containing the entire contents of the requested file.  Upon error,
 the function returns the empty string and sets @code{ERRNO}.
+
+@item BEGIN @{ PROCINFO["readfile"] = 1 @}
+In addition, the extension adds an input parser that is activated if
+@code{PROCINFO["readfile"]} exists.
+When activated, each input file is returned in its entirety as @code{$0}.
+@code{RT} is set to the null string.
 @end table
 
 Here is an example:
@@ -32833,25 +34419,24 @@ for more information.
 @node Extension Sample Time
 @subsection Extension Time Functions
 
-These functions can be used either by invoking @command{gawk}
-with a command-line argument of @samp{-l time} or by
-inserting @samp{@@load "time"} in your script.
+The @code{time} extension adds two functions, named @code{gettimeofday()}
+and @code{sleep()}, as follows:
 
 @table @code
 @item @@load "time"
 This is how you load the extension.
 
-@cindex @code{gettimeofday} extension function
+@cindex @code{gettimeofday()} extension function
 @item the_time = gettimeofday()
 Return the time in seconds that has elapsed since 1970-01-01 UTC as a
 floating point value.  If the time is unavailable on this platform, return
 @minus{}1 and set @code{ERRNO}.  The returned time should have sub-second
 precision, but the actual precision may vary based on the platform.
 If the standard C @code{gettimeofday()} system call is available on this
-platform, then it simply returns the value.  Otherwise, if on Windows,
+platform, then it simply returns the value.  Otherwise, if on MS-Windows,
 it tries to use @code{GetSystemTimeAsFileTime()}.
 
-@cindex @code{sleep} extension function
+@cindex @code{sleep()} extension function
 @item result = sleep(@var{seconds})
 Attempt to sleep for @var{seconds} seconds.  If @var{seconds} is negative,
 or the attempt to sleep fails, return @minus{}1 and set @code{ERRNO}.
@@ -32863,6 +34448,8 @@ tries to use @code{nanosleep()} or @code{select()} to implement the delay.
 
 @node gawkextlib
 @section The @code{gawkextlib} Project
+@cindex @code{gawkextlib}
+@cindex extensions, where to find
 
 @cindex @code{gawkextlib} project
 The @uref{http://sourceforge.net/projects/gawkextlib/, @code{gawkextlib}}
@@ -32870,14 +34457,17 @@ project provides a number of @command{gawk} extensions, including one for
 processing XML files.  This is the evolution of the original @command{xgawk}
 (XML @command{gawk}) project.
 
-As of this writing, there are four extensions:
+As of this writing, there are five extensions:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 XML parser extension, using the @uref{http://expat.sourceforge.net, Expat}
 XML parsing library.
 
 @item
+PDF extension.
+
+@item
 PostgreSQL extension.
 
 @item
@@ -32893,8 +34483,9 @@ The @code{time} extension described earlier (@pxref{Extension Sample
 Time}) was originally from this project but has been moved in to the
 main @command{gawk} distribution.
 
+@cindex @command{git} utility
 You can check out the code for the @code{gawkextlib} project
-using the @uref{http://git-scm.com, GIT} distributed source
+using the @uref{http://git-scm.com, Git} distributed source
 code control system.  The command is as follows:
 
 @example
@@ -32910,7 +34501,7 @@ In addition, you must have the GNU Autotools installed
 @uref{http://www.gnu.org/software/automake, Automake},
 @uref{http://www.gnu.org/software/libtool, Libtool},
 and
-@uref{http://www.gnu.org/software/gettext, Gettext}).
+@uref{http://www.gnu.org/software/gettext, GNU @command{gettext}}).
 
 The simple recipe for building and testing @code{gawkextlib} is as follows.
 First, build and install @command{gawk}:
@@ -32944,26 +34535,168 @@ If you write an extension that you wish to share with other
 @code{gawkextlib} project.
 See the project's web site for more information.
 
-@iftex
-@part Part IV:@* Appendices
-@end iftex
+@node Extension summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+You can write extensions (sometimes called plug-ins) for @command{gawk}
+in C or C++ using the Application Programming Interface (API) defined
+by the @command{gawk} developers.
+
+@item
+Extensions must have a license compatible with the GNU General Public
+License (GPL), and they must assert that fact by declaring a variable
+named @code{plugin_is_GPL_compatible}.
+
+@item
+Communication between @command{gawk} and an extension is two-way.
+@command{gawk} passes a @code{struct} to the extension which contains
+various data fields and function pointers.  The extension can then call
+into @command{gawk} via the supplied function pointers to accomplish
+certain tasks.
+
+@item
+One of these tasks is to ``register'' the name and implementation of
+a new @command{awk}-level function with @command{gawk}.  The implementation
+takes the form of a C function pointer with a defined signature.
+By convention, implementation functions are named @code{do_@var{XXXX}()}
+for some @command{awk}-level function @code{@var{XXXX}()}.
+
+@item
+The API is defined in a header file named @file{gawkpi.h}. You must include
+a number of standard header files @emph{before} including it in your source file.
+
+@item
+API function pointers are provided for the following kinds of operations:
+
+@itemize @value{BULLET}
+@item
+Registration functions. You may register
+extension functions,
+exit callbacks,
+a version string,
+input parsers,
+output wrappers,
+and two-way processors.
+
+@item
+Printing fatal, warning, and ``lint'' warning messages.
+
+@item
+Updating @code{ERRNO}, or unsetting it.
+
+@item
+Accessing parameters, including converting an undefined parameter into
+an array.
+
+@item
+Symbol table access: retrieving a global variable, creating one,
+or changing one.
+
+@item
+Allocating, reallocating, and releasing memory.
+
+@item
+Creating and releasing cached values; this provides an
+efficient way to use values for multiple variables and
+can be a big performance win.
+
+@item
+Manipulating arrays:
+retrieving, adding, deleting, and modifying elements;
+getting the count of elements in an array;
+creating a new array;
+clearing an array;
+and
+flattening an array for easy C style looping over all its indices and elements
+@end itemize
+
+@item
+The API defines a number of standard data types for representing
+@command{awk} values, array elements, and arrays.
+
+@item
+The API provide convenience functions for constructing values.
+It also provides memory management functions to ensure compatibility
+between memory allocated by @command{gawk} and memory allocated by an
+extension.
+
+@item
+@emph{All} memory passed from @command{gawk} to an extension must be
+treated as read-only by the extension.
+
+@item
+@emph{All} memory passed from an extension to @command{gawk} must come from
+the API's memory allocation functions. @command{gawk} takes responsibility for
+the memory and will release it when appropriate.
+
+@item
+The API provides information about the running version of @command{gawk} so
+that an extension can make sure it is compatible with the @command{gawk}
+that loaded it.
+
+@item
+It is easiest to start a new extension by copying the boilerplate code
+described in this @value{CHAPTER}.  Macros in the @file{gawkapi.h} make
+this easier to do.
+
+@item
+The @command{gawk} distribution includes a number of small but useful
+sample extensions. The @code{gawkextlib} project includes several more,
+larger, extensions.  If you wish to write an extension and contribute it
+to the community of @command{gawk} users, the @code{gawkextlib} project
+should be the place to do so.
+
+@end itemize
+
+@node Extension Exercises
+@section Exercises
+
+@enumerate
+@item
+Add functions to implement system calls such as @code{chown()},
+@code{chmod()}, and @code{umask()} to the file operations extension
+presented in @ref{Internal File Ops}.
+
+@item
+(Hard.)
+How would you provide namespaces in @command{gawk}, so that the
+names of functions in different extensions don't conflict with each other?
+If you come up with a really good scheme, contact the @command{gawk}
+maintainer to tell him about it.
+
+@item
+Write a wrapper script that provides an interface similar to
+@samp{sed -i} for the ``inplace'' extension presented in
+@ref{Extension Sample Inplace}.
+
+@end enumerate
+
+@ifnotinfo
+@part @value{PART4}Appendices
+@end ifnotinfo
 
-@ignore
 @ifdocbook
 
-@part Part IV:@* Appendices
+@ifclear FOR_PRINT
+Part IV contains the appendixes (including the two licenses that cover
+the @command{gawk} source code and this @value{DOCUMENT}, respectively)
+and the Glossary:
+@end ifclear
 
-Part IV provides the appendices, the Glossary, and two licenses that cover
-the @command{gawk} source code and this @value{DOCUMENT}, respectively.
-It contains the following appendices:
+@ifset FOR_PRINT
+Part IV contains two appendixes:
+@end ifset
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Language History}.
 
 @item
 @ref{Installation}.
 
+@ifclear FOR_PRINT
 @item
 @ref{Notes}.
 
@@ -32978,24 +34711,31 @@ It contains the following appendices:
 
 @item
 @ref{GNU Free Documentation License}.
+@end ifclear
 @end itemize
 @end ifdocbook
-@end ignore
 
 @node Language History
 @appendix The Evolution of the @command{awk} Language
 
-This @value{DOCUMENT} describes the GNU implementation of @command{awk}, which follows
-the POSIX specification.
-Many long-time @command{awk} users learned @command{awk} programming
-with the original @command{awk} implementation in Version 7 Unix.
-(This implementation was the basis for @command{awk} in Berkeley Unix,
-through 4.3-Reno.  Subsequent versions of Berkeley Unix, and some systems
-derived from 4.4BSD-Lite, use various versions of @command{gawk}
-for their @command{awk}.)
-This @value{CHAPTER} briefly describes the
-evolution of the @command{awk} language, with cross-references to other parts
-of the @value{DOCUMENT} where you can find more information.
+This @value{DOCUMENT} describes the GNU implementation of @command{awk},
+which follows the POSIX specification.  Many long-time @command{awk}
+users learned @command{awk} programming with the original @command{awk}
+implementation in Version 7 Unix.  (This implementation was the basis for
+@command{awk} in Berkeley Unix, through 4.3-Reno.  Subsequent versions
+of Berkeley Unix, and some systems derived from 4.4BSD-Lite, used various
+versions of @command{gawk} for their @command{awk}.)  This @value{CHAPTER}
+briefly describes the evolution of the @command{awk} language, with
+cross-references to other parts of the @value{DOCUMENT} where you can
+find more information.
+
+@ifset FOR_PRINT
+To save space, we have omitted
+information on the history of features in @command{gawk} from this
+edition. You can find it in the
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Feature-History.html,
+online documentation}.
+@end ifset
 
 @menu
 * V7/SVR3.1::                   The major changes between V7 and System V
@@ -33007,9 +34747,11 @@ of the @value{DOCUMENT} where you can find more information.
                                 @command{awk}.
 * POSIX/GNU::                   The extensions in @command{gawk} not in POSIX
                                 @command{awk}.
+* Feature History::             The history of the features in @command{gawk}.
 * Common Extensions::           Common Extensions Summary.
 * Ranges and Locales::          How locales used to affect regexp ranges.
 * Contributors::                The major contributors to @command{gawk}.
+* History summary::             History summary.
 @end menu
 
 @node V7/SVR3.1
@@ -33024,7 +34766,7 @@ Version 7 Unix (1978) and the new version that was first made generally availabl
 System V Release 3.1 (1987).  This @value{SECTION} summarizes the changes, with
 cross-references to further details:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The requirement for @samp{;} to separate rules on a line
 (@pxref{Statements/Lines}).
@@ -33115,7 +34857,7 @@ Multidimensional arrays
 The System V Release 4 (1989) version of Unix @command{awk} added these features
 (some of which originated in @command{gawk}):
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @code{ENVIRON} array (@pxref{Built-in Variables}).
 @c gawk and MKS awk
@@ -33175,7 +34917,7 @@ Processing of escape sequences inside command-line variable assignments
 The POSIX Command Language and Utilities standard for @command{awk} (1992)
 introduced the following changes into the language:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The use of @option{-W} for implementation-specific options
 (@pxref{Options}).
@@ -33200,7 +34942,7 @@ features of the language.
 In 2012, a number of extensions that had been commonly available for
 many years were finally added to POSIX. They are:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @code{fflush()} built-in function for flushing buffered output
 (@pxref{I/O Functions}).
@@ -33237,7 +34979,7 @@ has made his version available via his home page
 This @value{SECTION} describes common extensions that
 originally appeared in his version of @command{awk}.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @samp{**} and @samp{**=} operators
 (@pxref{Arithmetic Ops}
@@ -33255,7 +34997,7 @@ The @code{fflush()} built-in function for flushing buffered output
 @ignore
 @item
 The @code{SYMTAB} array, that allows access to @command{awk}'s internal symbol
-table. This feature is not documented, largely because
+table. This feature was never documented for his @command{awk}, largely because
 it is somewhat shakily implemented. For instance, you cannot access arrays
 or array elements through it.
 @end ignore
@@ -33282,12 +35024,12 @@ A number of features have come and gone over the years. This @value{SECTION}
 summarizes the additional features over POSIX @command{awk} that are
 in the current version of @command{gawk}.
 
-@itemize @bullet
+@itemize @value{BULLET}
 
 @item
 Additional built-in variables:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The
 @code{ARGIND}
@@ -33308,10 +35050,10 @@ variables
 @item
 Special files in I/O redirections:
 
-@itemize @minus{}
+@itemize @value{MINUS}
 @item
 The @file{/dev/stdin}, @file{/dev/stdout}, @file{/dev/stderr} and
-@file{/dev/fd/@var{N}} special file names
+@file{/dev/fd/@var{N}} special @value{FN}s
 (@pxref{Special Files}).
 
 @item
@@ -33324,7 +35066,7 @@ IP protocol to use.
 @item
 Changes and/or additions to the language:
 
-@itemize @minus{}
+@itemize @value{MINUS}
 @item
 The @samp{\x} escape sequence
 (@pxref{Escape Sequences}).
@@ -33363,7 +35105,7 @@ Directories on the command line produce a warning and are skipped
 @item
 New keywords:
 
-@itemize @minus{}
+@itemize @value{MINUS}
 @item
 The @code{BEGINFILE} and @code{ENDFILE} special patterns.
 (@pxref{BEGINFILE/ENDFILE}).
@@ -33384,7 +35126,7 @@ The @code{switch} statement
 @item
 Changes to standard @command{awk} functions:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The optional second argument to @code{close()} that allows closing one end
 of a two-way pipe to a coprocess
@@ -33417,7 +35159,7 @@ argument which is an array to hold the text of the field separators.
 @item
 Additional functions only in @command{gawk}:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The
 @code{and()},
@@ -33460,7 +35202,7 @@ functions for working with timestamps
 @item
 Changes and/or additions in the command-line options:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The @env{AWKPATH} environment variable for specifying a path search for
 the @option{-f} command-line option
@@ -33535,10 +35277,10 @@ long options
 
 @item
 Support for the following obsolete systems was removed from the code
-and the documentation for @command{gawk} version 4.0:
+and the documentation for @command{gawk} @value{PVERSION} 4.0:
 
 @c nested table
-@itemize @minus
+@itemize @value{MINUS}
 @item
 Amiga
 
@@ -33572,6 +35314,9 @@ Tandem (non-POSIX)
 @item
 Prestandard VAX C compiler for VAX/VMS
 
+@item
+GCC for VAX and Alpha has not been tested for a while.
+
 @end itemize
 
 @end itemize
@@ -33582,6 +35327,618 @@ Prestandard VAX C compiler for VAX/VMS
 @c ENDOFRANGE exgnot
 @c ENDOFRANGE posnot
 
+@c This does not need to be in the formal book.
+@ifclear FOR_PRINT
+@node Feature History
+@appendixsec History of @command{gawk} Features
+
+@ignore
+See the thread:
+https://groups.google.com/forum/#!topic/comp.lang.awk/SAUiRuff30c
+This motivated me to add this section.
+@end ignore
+
+@ignore
+I've tried to follow this general order, esp.@: for the 3.0 and 3.1 sections:
+       variables
+       special files
+       language changes (e.g., hex constants)
+       differences in standard awk functions
+       new gawk functions
+       new keywords
+       new command-line options
+       behavioral changes
+       new ports
+Within each category, be alphabetical.
+@end ignore
+
+This @value{SECTION} describes the features in @command{gawk}
+over and above those in POSIX @command{awk},
+in the order they were added to @command{gawk}.
+
+Version 2.10 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+The @env{AWKPATH} environment variable for specifying a path search for
+the @option{-f} command-line option
+(@pxref{Options}).
+
+@item
+The @code{IGNORECASE} variable and its effects
+(@pxref{Case-sensitivity}).
+
+@item
+The @file{/dev/stdin}, @file{/dev/stdout}, @file{/dev/stderr} and
+@file{/dev/fd/@var{N}} special @value{FN}s
+(@pxref{Special Files}).
+@end itemize
+
+Version 2.13 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+The @code{FIELDWIDTHS} variable and its effects
+(@pxref{Constant Size}).
+
+@item
+The @code{systime()} and @code{strftime()} built-in functions for obtaining
+and printing timestamps
+(@pxref{Time Functions}).
+
+@item
+Additional command-line options
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{-W lint} option to provide error and portability checking
+for both the source code and at runtime.
+
+@item
+The @option{-W compat} option to turn off the GNU extensions.
+
+@item
+The @option{-W posix} option for full POSIX compliance.
+@end itemize
+@end itemize
+
+Version 2.14 of @command{gawk} introduced the following feature:
+
+@itemize @value{BULLET}
+@item
+The @code{next file} statement for skipping to the next @value{DF}
+(@pxref{Nextfile Statement}).
+@end itemize
+
+Version 2.15 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+New variables (@pxref{Built-in Variables}):
+
+@itemize @value{MINUS}
+@item
+@code{ARGIND}, which tracks the movement of @code{FILENAME}
+through @code{ARGV}.
+
+@item
+@code{ERRNO}, which contains the system error message when
+@code{getline} returns @minus{}1 or @code{close()} fails.
+@end itemize
+
+@item
+The @file{/dev/pid}, @file{/dev/ppid}, @file{/dev/pgrpid}, and
+@file{/dev/user} special @value{FN}s. These have since been removed.
+
+@item
+The ability to delete all of an array at once with @samp{delete @var{array}}
+(@pxref{Delete}).
+
+@item
+Command line option changes
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The ability to use GNU-style long-named options that start with @option{--}.
+
+@item
+The @option{--source} option for mixing command-line and library-file
+source code.
+@end itemize
+@end itemize
+
+Version 3.0 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+New or changed variables:
+
+@itemize @value{MINUS}
+@item
+@code{IGNORECASE} changed, now applying to string comparison as well
+as regexp operations
+(@pxref{Case-sensitivity}).
+
+@item
+@code{RT}, which contains the input text that matched @code{RS}
+(@pxref{Records}).
+@end itemize
+
+@item
+Full support for both POSIX and GNU regexps
+(@pxref{Regexp}).
+
+@item
+The @code{gensub()} function for more powerful text manipulation
+(@pxref{String Functions}).
+
+@item
+The @code{strftime()} function acquired a default time format,
+allowing it to be called with no arguments
+(@pxref{Time Functions}).
+
+@item
+The ability for @code{FS} and for the third
+argument to @code{split()} to be null strings
+(@pxref{Single Character Fields}).
+
+@item
+The ability for @code{RS} to be a regexp
+(@pxref{Records}).
+
+@item
+The @code{next file} statement became @code{nextfile}
+(@pxref{Nextfile Statement}).
+
+@item
+The @code{fflush()} function from
+Brian Kernighan's @command{awk}
+(then at Bell Laboratories;
+@pxref{I/O Functions}).
+
+@item
+New command line options:
+
+@itemize @value{MINUS}
+@item
+The @option{--lint-old} option to
+warn about constructs that are not available in
+the original Version 7 Unix version of @command{awk}
+(@pxref{V7/SVR3.1}).
+
+@item
+The @option{-m} option from Brian Kernighan's @command{awk}.  (He was
+still at Bell Laboratories at the time.)  This was later removed from
+both his @command{awk} and from @command{gawk}.
+
+@item
+The @option{--re-interval} option to provide interval expressions in regexps
+(@pxref{Regexp Operators}).
+
+@item
+The @option{--traditional} option was added as a better name for
+@option{--compat} (@pxref{Options}).
+@end itemize
+
+@item
+The use of GNU Autoconf to control the configuration process
+(@pxref{Quick Installation}).
+
+@item
+Amiga support.
+This has since been removed.
+
+@end itemize
+
+Version 3.1 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+New variables
+(@pxref{Built-in Variables}):
+
+@itemize @value{MINUS}
+@item
+@code{BINMODE}, for non-POSIX systems,
+which allows binary I/O for input and/or output files
+(@pxref{PC Using}).
+
+@item
+@code{LINT}, which dynamically controls lint warnings.
+
+@item
+@code{PROCINFO}, an array for providing process-related information.
+
+@item
+@code{TEXTDOMAIN}, for setting an application's internationalization text domain
+(@pxref{Internationalization}).
+@end itemize
+
+@item
+The ability to use octal and hexadecimal constants in @command{awk}
+program source code
+(@pxref{Nondecimal-numbers}).
+
+@item
+The @samp{|&} operator for two-way I/O to a coprocess
+(@pxref{Two-way I/O}).
+
+@item
+The @file{/inet} special files for TCP/IP networking using @samp{|&}
+(@pxref{TCP/IP Networking}).
+
+@item
+The optional second argument to @code{close()} that allows closing one end
+of a two-way pipe to a coprocess
+(@pxref{Two-way I/O}).
+
+@item
+The optional third argument to the @code{match()} function
+for capturing text-matching subexpressions within a regexp
+(@pxref{String Functions}).
+
+@item
+Positional specifiers in @code{printf} formats for
+making translations easier
+(@pxref{Printf Ordering}).
+
+@item
+A number of new built-in functions:
+
+@itemize @value{MINUS}
+@item
+The @code{asort()} and @code{asorti()} functions for sorting arrays
+(@pxref{Array Sorting}).
+
+@item
+The @code{bindtextdomain()}, @code{dcgettext()} and @code{dcngettext()} functions
+for internationalization
+(@pxref{Programmer i18n}).
+
+@item
+The @code{extension()} function and the ability to add
+new built-in functions dynamically
+(@pxref{Dynamic Extensions}).
+
+@item
+The @code{mktime()} function for creating timestamps
+(@pxref{Time Functions}).
+
+@item
+The @code{and()}, @code{or()}, @code{xor()}, @code{compl()},
+@code{lshift()}, @code{rshift()}, and @code{strtonum()} functions
+(@pxref{Bitwise Functions}).
+@end itemize
+
+@item
+@cindex @code{next file} statement
+The support for @samp{next file} as two words was removed completely
+(@pxref{Nextfile Statement}).
+
+@item
+Additional command-line options
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{--dump-variables} option to print a list of all global variables.
+
+@item
+The @option{--exec} option, for use in CGI scripts.
+
+@item
+The @option{--gen-po} command-line option and the use of a leading
+underscore to mark strings that should be translated
+(@pxref{String Extraction}).
+
+@item
+The @option{--non-decimal-data} option to allow non-decimal
+input data
+(@pxref{Nondecimal Data}).
+
+@item
+The @option{--profile} option and @command{pgawk}, the
+profiling version of @command{gawk}, for producing execution
+profiles of @command{awk} programs
+(@pxref{Profiling}).
+
+@item
+The @option{--use-lc-numeric} option to force @command{gawk}
+to use the locale's decimal point for parsing input data
+(@pxref{Conversion}).
+@end itemize
+
+@item
+The use of GNU Automake to help in standardizing the configuration process
+(@pxref{Quick Installation}).
+
+@item
+The use of GNU @command{gettext} for @command{gawk}'s own message output
+(@pxref{Gawk I18N}).
+
+@item
+BeOS support. This was later removed.
+
+@item
+Tandem support. This was later removed.
+
+@item
+The Atari port became officially unsupported and was
+later removed entirely.
+
+@item
+The source code changed to use ISO C standard-style function definitions.
+
+@item
+POSIX compliance for @code{sub()} and @code{gsub()}
+(@pxref{Gory Details}).
+
+@item
+The @code{length()} function was extended to accept an array argument
+and return the number of elements in the array
+(@pxref{String Functions}).
+
+@item
+The @code{strftime()} function acquired a third argument to
+enable printing times as UTC
+(@pxref{Time Functions}).
+@end itemize
+
+Version 4.0 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+
+@item
+Variable additions:
+
+@itemize @value{MINUS}
+@item
+@code{FPAT}, which allows you to specify a regexp that matches
+the fields, instead of matching the field separator
+(@pxref{Splitting By Content}).
+
+@item
+If @code{PROCINFO["sorted_in"]} exists, @samp{for(iggy in foo)} loops sort the
+indices before looping over them.  The value of this element
+provides control over how the indices are sorted before the loop
+traversal starts
+(@pxref{Controlling Scanning}).
+
+@item
+@code{PROCINFO["strftime"]}, which holds
+the default format for @code{strftime()}
+(@pxref{Time Functions}).
+@end itemize
+
+@item
+The special files @file{/dev/pid}, @file{/dev/ppid}, @file{/dev/pgrpid}
+and @file{/dev/user} were removed.
+
+@item
+Support for IPv6 was added via the @file{/inet6} special file.
+@file{/inet4} forces IPv4 and @file{/inet} chooses the system
+default, which is probably IPv4
+(@pxref{TCP/IP Networking}).
+
+@item
+The use of @samp{\s} and @samp{\S} escape sequences in regular expressions
+(@pxref{GNU Regexp Operators}).
+
+@item
+Interval expressions became part of default regular expressions
+(@pxref{Regexp Operators}).
+
+@item
+POSIX character classes work even with @option{--traditional}
+(@pxref{Regexp Operators}).
+
+@item
+@code{break} and @code{continue} became invalid outside a loop,
+even with @option{--traditional}
+(@pxref{Break Statement}, and also see
+@ref{Continue Statement}).
+
+@item
+@code{fflush()}, @code{nextfile}, and @samp{delete @var{array}}
+are allowed if @option{--posix} or @option{--traditional}, since they
+are all now part of POSIX.
+
+@item
+An optional third argument to
+@code{asort()} and @code{asorti()}, specifying how to sort
+(@pxref{String Functions}).
+
+@item
+The behavior of @code{fflush()} changed to match Brian Kernighan's @command{awk}
+and for POSIX; now both @samp{fflush()} and @samp{fflush("")}
+flush all open output redirections
+(@pxref{I/O Functions}).
+
+@item
+The @code{isarray()}
+function which distinguishes if an item is an array
+or not, to make it possible to traverse arrays of arrays
+(@pxref{Type Functions}).
+
+@item
+The @code{patsplit()}
+function which gives the same capability as @code{FPAT}, for splitting
+(@pxref{String Functions}).
+
+@item
+An optional fourth argument to the @code{split()} function,
+which is an array to hold the values of the separators
+(@pxref{String Functions}).
+
+@item
+Arrays of arrays
+(@pxref{Arrays of Arrays}).
+
+@item
+The @code{BEGINFILE} and @code{ENDFILE} special patterns
+(@pxref{BEGINFILE/ENDFILE}).
+
+@item
+Indirect function calls
+(@pxref{Indirect Calls}).
+
+@item
+@code{switch} / @code{case} are enabled by default
+(@pxref{Switch Statement}).
+
+@item
+Command line option changes
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{-b} and @option{--characters-as-bytes} options
+which prevent @command{gawk} from treating input as a multibyte string.
+
+@item
+The redundant @option{--compat}, @option{--copyleft}, and @option{--usage}
+long options were removed.
+
+@item
+The @option{--gen-po} option was finally renamed to the correct @option{--gen-pot}.
+
+@item
+The @option{--sandbox} option which disables certain features.
+
+@item
+All long options acquired corresponding short options, for use in @samp{#!} scripts.
+@end itemize
+
+@item
+Directories named on the command line now produce a warning, not a fatal
+error, unless @option{--posix} or @option{--traditional} are used
+(@pxref{Command line directories}).
+
+@item
+The @command{gawk} internals were rewritten, bringing the @command{dgawk}
+debugger and possibly improved performance
+(@pxref{Debugger}).
+
+@item
+Per the GNU Coding Standards, dynamic extensions must now define
+a global symbol indicating that they are GPL-compatible
+(@pxref{Plugin License}).
+
+@item
+In POSIX mode, string comparisons use @code{strcoll()} / @code{wcscoll()}
+(@pxref{POSIX String Comparison}).
+
+@item
+The option for raw sockets was removed, since it was never implemented
+(@pxref{TCP/IP Networking}).
+
+@item
+Ranges of the form @samp{[d-h]} are treated as if they were in the
+C locale, no matter what kind of regexp is being used, and even if
+@option{--posix}
+(@pxref{Ranges and Locales}).
+
+@item
+Support was removed for the following systems:
+
+@itemize @value{MINUS}
+@item
+Atari
+
+@item
+Amiga
+
+@item
+BeOS
+
+@item
+Cray
+
+@item
+MIPS RiscOS
+
+@item
+MS-DOS with Microsoft Compiler
+
+@item
+MS-Windows with Microsoft Compiler
+
+@item
+NeXT
+
+@item
+SunOS 3.x, Sun 386 (Road Runner)
+
+@item
+Tandem (non-POSIX)
+
+@item
+Prestandard VAX C compiler for VAX/VMS
+@end itemize
+@end itemize
+
+Version 4.1 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+
+@item
+Three new arrays:
+@code{SYMTAB}, @code{FUNCTAB}, and @code{PROCINFO["identifiers"]}
+(@pxref{Auto-set}).
+
+@item
+The three executables @command{gawk}, @command{pgawk}, and @command{dgawk}, were merged into
+one, named just @command{gawk}.  As a result the command line options changed.
+
+@item
+Command line option changes
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{-D} option invokes the debugger.
+
+@item
+The @option{-i} and @option{--include} options
+load @command{awk} library files.
+
+@item
+The @option{-l} and @option{--load} options load compiled dynamic extensions.
+
+@item 
+The @option{-M} and @option{--bignum} options enable MPFR.
+
+@item
+The @option{-o} only does pretty-printing.
+
+@item
+The @option{-p} option is used for profiling.
+
+@item
+The @option{-R} option was removed.
+@end itemize
+
+@item
+Support for high precision arithmetic with MPFR.
+(@pxref{Arbitrary Precision Arithmetic}).
+
+@item
+The @code{and()}, @code{or()} and @code{xor()} functions
+changed to allow any number of arguments,
+with a minimum of two
+(@pxref{Bitwise Functions}).
+
+@item
+The dynamic extension interface was completely redone
+(@pxref{Dynamic Extensions}).
+
+@end itemize
+
+@c XXX ADD MORE STUFF HERE
+@end ifclear
+
 @node Common Extensions
 @appendixsec Common Extensions Summary
 
@@ -33595,18 +35952,18 @@ the three most widely-used freely available versions of @command{awk}
 @multitable {@file{/dev/stderr} special file} {BWK Awk} {Mawk} {GNU Awk}
 @headitem Feature @tab BWK Awk @tab Mawk @tab GNU Awk
 @item @samp{\x} Escape sequence @tab X @tab X @tab X
-@item @code{RS} as regexp @tab @tab X @tab X
 @item @code{FS} as null string @tab X @tab X @tab X
-@item @file{/dev/stdin} special file @tab X @tab @tab X
+@item @file{/dev/stdin} special file @tab X @tab X @tab X
 @item @file{/dev/stdout} special file @tab X @tab X @tab X
 @item @file{/dev/stderr} special file @tab X @tab X @tab X
-@item @code{**} and @code{**=} operators @tab X @tab @tab X
+@item @code{delete} without subscript @tab X @tab X @tab X
 @item @code{fflush()} function @tab X @tab X @tab X
-@item @code{func} keyword @tab X @tab @tab X
+@item @code{length()} of an array @tab X @tab X @tab X
 @item @code{nextfile} statement @tab X @tab X @tab X
-@item @code{delete} without subscript @tab X @tab X @tab X
-@item @code{length()} of an array @tab X @tab @tab X
+@item @code{**} and @code{**=} operators @tab X @tab @tab X
+@item @code{func} keyword @tab X @tab @tab X
 @item @code{BINMODE} variable @tab @tab X @tab X
+@item @code{RS} as regexp @tab @tab X @tab X
 @item Time related functions @tab @tab X @tab X
 @end multitable
 
@@ -33626,7 +35983,7 @@ character ranges (such as @samp{[a-z]}) to match any character between
 the first character in the range and the last character in the range,
 inclusive.  Ordering was based on the numeric value of each character
 in the machine's native character set.  Thus, on ASCII-based systems,
-@code{[a-z]} matched all the lowercase letters, and only the lowercase
+@samp{[a-z]} matched all the lowercase letters, and only the lowercase
 letters, since the numeric values for the letters from @samp{a} through
 @samp{z} were contiguous.  (On an EBCDIC system, the range @samp{[a-z]}
 includes additional, non-alphabetic characters as well.)
@@ -33637,7 +35994,7 @@ as working in this fashion, and in particular, would teach that the
 that @samp{[A-Z]} was the ``correct'' way to match uppercase letters.
 And indeed, this was true.@footnote{And Life was good.}
 
-The 1993 POSIX standard introduced the idea of locales (@pxref{Locales}).
+The 1992 POSIX standard introduced the idea of locales (@pxref{Locales}).
 Since many locales include other letters besides the plain twenty-six
 letters of the American English alphabet, the POSIX standard added
 character classes (@pxref{Bracket Expressions}) as a way to match
@@ -33676,9 +36033,10 @@ This output is unexpected, since the @samp{bc} at the end of
 This result is due to the locale setting (and thus you may not see
 it on your system).
 
+@cindex Unicode
 Similar considerations apply to other ranges.  For example, @samp{["-/]}
 is perfectly valid in ASCII, but is not valid in many Unicode locales,
-such as @samp{en_US.UTF-8}.
+such as @code{en_US.UTF-8}.
 
 Early versions of @command{gawk} used regexp matching code that was not
 locale aware, so ranges had their traditional interpretation.
@@ -33687,18 +36045,19 @@ When @command{gawk} switched to using locale-aware regexp matchers,
 the problems began; especially as both GNU/Linux and commercial Unix
 vendors started implementing non-ASCII locales, @emph{and making them
 the default}.  Perhaps the most frequently asked question became something
-like ``why does @code{[A-Z]} match lowercase letters?!?''
+like ``why does @samp{[A-Z]} match lowercase letters?!?''
 
+@cindex Berry, Karl
 This situation existed for close to 10 years, if not more, and
 the @command{gawk} maintainer grew weary of trying to explain that
 @command{gawk} was being nicely standards-compliant, and that the issue
-was in the user's locale.  During the development of version 4.0,
+was in the user's locale.  During the development of @value{PVERSION} 4.0,
 he modified @command{gawk} to always treat ranges in the original,
 pre-POSIX fashion, unless @option{--posix} was used (@pxref{Options}).@footnote{And
-thus was born the Campain for Rational Range Interpretation (or RRI). A number
-of GNU tools, such as @command{grep} and @command{sed}, have either
-implemented this change, or will soon.  Thanks to Karl Berry for coining the phrase
-``Rational Range Interpretation.''}
+thus was born the Campaign for Rational Range Interpretation (or
+RRI). A number of GNU tools have either implemented this change,
+or will soon.  Thanks to Karl Berry for coining the phrase ``Rational
+Range Interpretation.''}
 
 Fortunately, shortly before the final release of @command{gawk} 4.0,
 the maintainer learned that the 2008 standard had changed the
@@ -33711,7 +36070,7 @@ and
 By using this lovely technical term, the standard gives license
 to implementors to implement ranges in whatever way they choose.
 The @command{gawk} maintainer chose to apply the pre-POSIX meaning in all
-cases: the default regexp matching; with @option{--traditional}, and with
+cases: the default regexp matching; with @option{--traditional} and with
 @option{--posix}; in all cases, @command{gawk} remains POSIX compliant.
 
 @node Contributors
@@ -33725,7 +36084,7 @@ cases: the default regexp matching; with @option{--traditional}, and with
 This @value{SECTION} names the major contributors to @command{gawk}
 and/or this @value{DOCUMENT}, in approximate chronological order:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @cindex Aho, Alfred
 @cindex Weinberger, Peter
@@ -33805,8 +36164,8 @@ provided the initial port to OS/2 and its documentation.
 Michal Jaegermann
 provided the port to Atari systems and its documentation.
 (This port is no longer supported.)
-He continues to provide portability checking with DEC Alpha
-systems, and has done a lot of work to make sure @command{gawk}
+He continues to provide portability checking,
+and has done a lot of work to make sure @command{gawk}
 works on non-32-bit systems.
 
 @item
@@ -33877,7 +36236,7 @@ provided the port to BeOS and its documentation.
 @cindex Peters, Arno
 Arno Peters
 did the initial work to convert @command{gawk} to use
-GNU Automake and GNU @code{gettext}.
+GNU Automake and GNU @command{gettext}.
 
 @item
 @cindex Broder, Alan J.@:
@@ -33907,17 +36266,25 @@ environments.
 (This is no longer supported)
 
 @item
+@cindex Wallin, Anders
+Anders Wallin helped keep the VMS port going for several years.
+
+@item
+@cindex Gordon, Assaf
+Assaf Gordon contributed the code to implement the
+@option{--sandbox} option.
+
+@item
 @cindex Haque, John
 John Haque made the following contributions:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The modifications to convert @command{gawk}
 into a byte-code interpreter, including the debugger.
 
 @item
-The addition of true multidimensional arrays.
-@ref{Arrays of Arrays}.
+The addition of true arrays of arrays.
 
 @item
 The additional modifications for support of arbitrary precision arithmetic.
@@ -33938,6 +36305,10 @@ The improved array sorting features were driven by John together
 with Pat Rankin.
 @end itemize
 
+@cindex Papadopoulos, Panos
+@item
+Panos Papadopoulos contributed the original text for @ref{Include Files}.
+
 @item
 @cindex Yawitz, Efraim
 Efraim Yawitz contributed the original text for @ref{Debugger}.
@@ -33950,17 +36321,57 @@ Arnold Robbins and Andrew Schorr, with notable contributions from
 the rest of the development team.
 
 @item
+@cindex Colombo, Antonio
+Antonio Giovanni Colombo rewrote a number of examples in the early
+chapters that were severely dated, for which I am incredibly grateful.
+
+@item
 @cindex Robbins, Arnold
 Arnold Robbins
 has been working on @command{gawk} since 1988, at first
 helping David Trueman, and as the primary maintainer since around 1994.
 @end itemize
 
+@node History summary
+@appendixsec Summary
+
+@itemize @value{BULLET}
+@item
+The @command{awk} language has evolved over time. The first release
+was with V7 Unix circa 1978.  In 1987 for System V Release 3.1,
+major additions, including user-defined functions, were made to the language.
+Additional changes were made for System V Release 4, in 1989.
+Since then, further minor changes happen under the auspices of the
+POSIX standard.
+
+@item
+Brian Kernighan's @command{awk} provides a small number of extensions
+that are implemented in common with other versions of @command{awk}.
+
+@item
+@command{gawk} provides a large number of extensions over POSIX @command{awk}.
+They can be disabled with either the @option{--traditional} or @option{--posix}
+options.
+
+@item
+The interaction of POSIX locales and regexp matching in @command{gawk} has been confusing over
+the years. Today, @command{gawk} implements Rational Range Interpretation, where
+ranges of the form @samp{[a-z]} match @emph{only} the characters numerically between
+@samp{a} through @samp{z} in the machine's native character set.  Usually this is ASCII
+but it can be EBCDIC on IBM S/390 systems.
+
+@item
+Many people have contributed to @command{gawk} development over the years.
+We hope that the list provided in this @value{CHAPTER} is complete and gives
+the appropriate credit where credit is due.
+
+@end itemize
+
 @node Installation
 @appendix Installing @command{gawk}
 
 @c last two commas are part of see also
-@cindex operating systems, See Also GNU/Linux, PC operating systems, Unix
+@cindex operating systems, See Also GNU/Linux@comma{} PC operating systems@comma{} Unix
 @c STARTOFRANGE gligawk
 @cindex @command{gawk}, installing
 @c STARTOFRANGE ingawk
@@ -33981,6 +36392,7 @@ the respective ports.
 * Bugs::                        Reporting Problems and Bugs.
 * Other Versions::              Other freely available @command{awk}
                                 implementations.
+* Installation summary::        Summary of installation.
 @end menu
 
 @node Gawk Distribution
@@ -34000,9 +36412,9 @@ subdirectories.
 @node Getting
 @appendixsubsec Getting the @command{gawk} Distribution
 @cindex @command{gawk}, source code@comma{} obtaining
-There are three ways to get GNU software:
+There are two ways to get GNU software:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Copy it from someone else who already has it.
 
@@ -34041,7 +36453,6 @@ file and then use @code{tar} to extract it.  You can use the following
 pipeline to produce the @command{gawk} distribution:
 
 @example
-# Under System V, add 'o' to the tar options
 gzip -d -c gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz | tar -xvpf -
 @end example
 
@@ -34057,7 +36468,7 @@ Extracting the archive
 creates a directory named @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}
 in the current directory.
 
-The distribution file name is of the form
+The distribution @value{FN} is of the form
 @file{gawk-@var{V}.@var{R}.@var{P}.tar.gz}.
 The @var{V} represents the major version of @command{gawk},
 the @var{R} represents the current release of version @var{V}, and
@@ -34196,8 +36607,8 @@ actual @file{Makefile} for creating the documentation.
 
 @item Makefile.am
 @itemx */Makefile.am
-Files used by the GNU @command{automake} software for generating
-the @file{Makefile.in} files used by @command{autoconf} and
+Files used by the GNU Automake software for generating
+the @file{Makefile.in} files used by Autoconf and
 @command{configure}.
 
 @item Makefile.in
@@ -34240,15 +36651,23 @@ They are installed as part of the installation process.
 The rest of the programs in this @value{DOCUMENT} are available in appropriate
 subdirectories of @file{awklib/eg}.
 
+@item extension/*
+The source code, manual pages, and infrastructure files for
+the sample extensions included with @command{gawk}.
+@xref{Dynamic Extensions}, for more information.
+
 @item posix/*
 Files needed for building @command{gawk} on POSIX-compliant systems.
 
 @item pc/*
-Files needed for building @command{gawk} under MS-Windows and OS/2
+Files needed for building @command{gawk} under MS-Windows
+@ifclear FOR_PRINT
+and OS/2
+@end ifclear
 (@pxref{PC Installation}, for details).
 
 @item vms/*
-Files needed for building @command{gawk} under VMS
+Files needed for building @command{gawk} under Vax/VMS and OpenVMS
 (@pxref{VMS Installation}, for details).
 
 @item test/*
@@ -34285,9 +36704,9 @@ to @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}.  Like most GNU software,
 @command{gawk} is configured
 automatically for your system by running the @command{configure} program.
 This program is a Bourne shell script that is generated automatically using
-GNU @command{autoconf}.
+GNU Autoconf.
 @ifnotinfo
-(The @command{autoconf} software is
+(The Autoconf software is
 described fully in
 @cite{Autoconf---Generating Automatic Configuration Scripts},
 which can be found online at
@@ -34295,7 +36714,7 @@ which can be found online at
 the Free Software Foundation's web site}.)
 @end ifnotinfo
 @ifinfo
-(The @command{autoconf} software is described fully starting with
+(The Autoconf software is described fully starting with
 @inforef{Top, , Autoconf, autoconf,Autoconf---Generating Automatic Configuration Scripts}.)
 @end ifinfo
 
@@ -34343,7 +36762,7 @@ please send in a bug report (@pxref{Bugs}).
 
 Of course, once you've built @command{gawk}, it is likely that you will
 wish to install it.  To do so, you need to run the command @samp{make
-check}, as a user with the appropriate permissions.  How to do this
+install}, as a user with the appropriate permissions.  How to do this
 varies by system, but on many systems you can use the @command{sudo}
 command to do so.  The command then becomes @samp{sudo make install}. It
 is likely that you will be asked for your password, and you will have
@@ -34360,7 +36779,7 @@ command line when compiling @command{gawk} from scratch, including:
 
 @table @code
 
-@cindex @code{--disable-extensions} configuration option
+@cindex @option{--disable-extensions} configuration option
 @cindex configuration option, @code{--disable-extensions}
 @item --disable-extensions
 Disable configuring and building the sample extensions in the
@@ -34368,7 +36787,7 @@ Disable configuring and building the sample extensions in the
 The default action is to dynamically check if the extensions
 can be configured and compiled.
 
-@cindex @code{--disable-lint} configuration option
+@cindex @option{--disable-lint} configuration option
 @cindex configuration option, @code{--disable-lint}
 @item --disable-lint
 Disable all lint checking within @code{gawk}.  The
@@ -34388,17 +36807,17 @@ Using this option may bring you some slight performance improvement.
 Using this option will cause some of the tests in the test suite
 to fail.  This option may be removed at a later date.
 
-@cindex @code{--disable-nls} configuration option
+@cindex @option{--disable-nls} configuration option
 @cindex configuration option, @code{--disable-nls}
 @item --disable-nls
 Disable all message-translation facilities.
 This is usually not desirable, but it may bring you some slight performance
 improvement.
 
-@cindex @code{--with-whiny-user-strftime} configuration option
+@cindex @option{--with-whiny-user-strftime} configuration option
 @cindex configuration option, @code{--with-whiny-user-strftime}
 @item  --with-whiny-user-strftime
-Force use of the included version of the @code{strftime()}
+Force use of the included version of the C @code{strftime()}
 function for deficient systems.
 @end table
 
@@ -34445,9 +36864,9 @@ should not have.  @file{custom.h} is automatically included by
 @file{config.h}.
 
 It is also possible that the @command{configure} program generated by
-@command{autoconf} will not work on your system in some other fashion.
+Autoconf will not work on your system in some other fashion.
 If you do have a problem, the file @file{configure.ac} is the input for
-@command{autoconf}.  You may be able to change this file and generate a
+Autoconf.  You may be able to change this file and generate a
 new version of @command{configure} that works on your system
 (@pxref{Bugs},
 for information on how to report problems in configuring @command{gawk}).
@@ -34475,16 +36894,21 @@ various non-Unix systems.
 @cindex PC operating systems@comma{} @command{gawk} on, installing
 @cindex operating systems, PC@comma{} @command{gawk} on, installing
 This @value{SECTION} covers installation and usage of @command{gawk} on x86 machines
+@ifclear FOR_PRINT
 running MS-DOS, any version of MS-Windows, or OS/2.
+@end ifclear
+@ifset FOR_PRINT
+running MS-DOS and any version of MS-Windows.
+@end ifset
 In this @value{SECTION}, the term ``Windows32''
-refers to any of Microsoft Windows-95/98/ME/NT/2000/XP/Vista/7.
+refers to any of Microsoft Windows-95/98/ME/NT/2000/XP/Vista/7/8.
 
-The limitations of MS-DOS (and MS-DOS shells under Windows32 or OS/2) has meant
-that various ``DOS extenders'' are often used with programs such as
-@command{gawk}.  The varying capabilities of Microsoft Windows 3.1
-and Windows32 can add to the confusion.  For an overview of the
-considerations, please refer to @file{README_d/README.pc} in the
-distribution.
+The limitations of MS-DOS (and MS-DOS shells under the other operating
+systems) has meant that various ``DOS extenders'' are often used with
+programs such as @command{gawk}.  The varying capabilities of Microsoft
+Windows 3.1 and Windows32 can add to the confusion.  For an overview
+of the considerations, please refer to @file{README_d/README.pc} in
+the distribution.
 
 @menu
 * PC Binary Installation::      Installing a prepared distribution.
@@ -34498,6 +36922,7 @@ distribution.
 * MSYS::                        Using @command{gawk} In The MSYS Environment.
 @end menu
 
+@ifclear FOR_PRINT
 @node PC Binary Installation
 @appendixsubsubsec Installing a Prepared Distribution for PC Systems
 
@@ -34536,13 +36961,21 @@ install-info --info-dir=x:/usr/info x:/usr/info/gawkinet.info
 
 The binary distribution may contain a separate file containing additional
 or more detailed installation instructions.
+@end ifclear
 
 @node PC Compiling
 @appendixsubsubsec Compiling @command{gawk} for PC Operating Systems
 
+@ifclear FOR_PRINT
 @command{gawk} can be compiled for MS-DOS, Windows32, and OS/2 using the GNU
-development tools from DJ Delorie (DJGPP: MS-DOS only) or Eberhard
-Mattes (EMX: MS-DOS, Windows32 and OS/2).  The file
+development tools from DJ Delorie (DJGPP: MS-DOS only), MinGW (Windows32) or Eberhard
+Mattes (EMX: MS-DOS, Windows32 and OS/2).
+@end ifclear
+@ifset FOR_PRINT
+@command{gawk} can be compiled for MS-DOS and Windows32 using the GNU
+development tools from DJ Delorie (DJGPP: MS-DOS only) or MinGW (Windows32).
+@end ifset
+The file
 @file{README_d/README.pc} in the @command{gawk} distribution contains
 additional notes, and @file{pc/Makefile} contains important information on
 compilation options.
@@ -34564,6 +36997,7 @@ build @command{gawk} using the DJGPP tools, enter @samp{make djgpp}.
 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/}.)  To build a
 native MS-Windows binary of @command{gawk}, type @samp{make mingw32}.
 
+@ifclear FOR_PRINT
 @cindex compiling @command{gawk} with EMX for OS/2
 The 32 bit EMX version of @command{gawk} works ``out of the box'' under OS/2.
 However, it is highly recommended to use GCC 2.95.3 for the compilation.
@@ -34598,7 +37032,7 @@ and @option{--libexecdir=c:/usr/lib}.
 @end ignore
 
 @ignore
-The internal @code{gettext} library tends to be problematic. It is therefore recommended
+The internal @command{gettext} library tends to be problematic. It is therefore recommended
 to use either an external one (@option{--without-included-gettext}) or to disable
 NLS entirely (@option{--disable-nls}).
 @end ignore
@@ -34635,8 +37069,11 @@ Ancient OS/2 ports of GNU @command{make} are not able to handle
 the Makefiles of this package.  If you encounter any problems with
 @command{make}, try GNU Make 3.79.1 or later versions.  You should
 find the latest version on
-@uref{ftp://hobbes.nmsu.edu/pub/os2/}.
+@uref{ftp://hobbes.nmsu.edu/pub/os2/}.@footnote{As of May, 2014,
+this site is still there, but the author could not find a package
+for GNU Make.}
 @end quotation
+@end ifclear
 
 @node PC Testing
 @appendixsubsubsec Testing @command{gawk} on PC Operating Systems
@@ -34648,6 +37085,7 @@ be converted so that they have the usual MS-DOS-style end-of-line markers.
 Alternatively, run @command{make check CMP="diff -a"} to use GNU @command{diff}
 in text mode instead of @command{cmp} to compare the resulting files.
 
+@ifclear FOR_PRINT
 Most
 of the tests work properly with Stewartson's shell along with the
 companion utilities or appropriate GNU utilities.  However, some editing of
@@ -34660,7 +37098,7 @@ On OS/2 the @code{pid} test fails because @code{spawnl()} is used instead of
 @code{fork()}/@code{execl()} to start child processes.
 Also the @code{mbfw1} and @code{mbprintf1} tests fail because the needed
 multibyte functionality is not available.
-
+@end ifclear
 
 @node PC Using
 @appendixsubsubsec Using @command{gawk} on PC Operating Systems
@@ -34669,15 +37107,15 @@ multibyte functionality is not available.
 @c STARTOFRANGE pcgawon
 @cindex PC operating systems, @command{gawk} on
 
-With the exception of the Cygwin environment,
-the @samp{|&} operator and TCP/IP networking
-(@pxref{TCP/IP Networking})
-are not supported for MS-DOS or MS-Windows.  EMX (OS/2 only) does support
-at least the @samp{|&} operator.
+Under MS-DOS and MS-Windows, the Cygwin and MinGW environments support
+both the @samp{|&} operator and TCP/IP networking
+(@pxref{TCP/IP Networking}).
+@ifclear FOR_PRINT
+EMX (OS/2 only) supports at least the @samp{|&} operator.
+@end ifclear
 
 @cindex search paths
 @cindex search paths, for source files
-@cindex @command{gawk}, OS/2 version of
 @cindex @command{gawk}, MS-DOS version of
 @cindex @command{gawk}, MS-Windows version of
 @cindex @code{;} (semicolon), @code{AWKPATH} variable and
@@ -34688,36 +37126,50 @@ program files as described in @ref{AWKPATH Variable}.  However,
 semicolons (rather than colons) separate elements in the @env{AWKPATH}
 variable.  If @env{AWKPATH} is not set or is empty, then the default
 search path for MS-Windows and MS-DOS versions is
-@code{@w{".;c:/lib/awk;c:/gnu/lib/awk"}}.
+@samp{@w{.;c:/lib/awk;c:/gnu/lib/awk}}.
 
+@ifclear FOR_PRINT
+@cindex @command{gawk}, OS/2 version of
 @cindex @code{UNIXROOT} variable, on OS/2 systems
 The search path for OS/2 (32 bit, EMX) is determined by the prefix directory
 (most likely @file{/usr} or @file{c:/usr}) that has been specified as an option of
-the @command{configure} script like it is the case for the Unix versions.
+the @command{configure} script as is the case for the Unix versions.
 If @file{c:/usr} is the prefix directory then the default search path contains @file{.}
 and @file{c:/usr/share/awk}.
 Additionally, to support binary distributions of @command{gawk} for OS/2
-systems whose drive @samp{c:} might not support long file names or might not exist
+systems whose drive @samp{c:} might not support long @value{FN}s or might not exist
 at all, there is a special environment variable.  If @env{UNIXROOT} specifies
 a drive then this specific drive is also searched for program files.
 E.g., if @env{UNIXROOT} is set to @file{e:} the complete default search path is
-@code{@w{".;c:/usr/share/awk;e:/usr/share/awk"}}.
+@samp{@w{.;c:/usr/share/awk;e:/usr/share/awk}}.
 
 An @command{sh}-like shell (as opposed to @command{command.com} under MS-DOS
 or @command{cmd.exe} under MS-Windows or OS/2) may be useful for @command{awk} programming.
 The DJGPP collection of tools includes an MS-DOS port of Bash,
 and several shells are available for OS/2, including @command{ksh}.
+@end ifclear
+@ifset FOR_PRINT
+An @command{sh}-like shell (as opposed to @command{command.com} under MS-DOS
+or @command{cmd.exe} under MS-Windows) may be useful for @command{awk} programming.
+The DJGPP collection of tools includes an MS-DOS port of Bash.
+@end ifset
 
 @cindex common extensions, @code{BINMODE} variable
 @cindex extensions, common@comma{} @code{BINMODE} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{BINMODE} variable
 @cindex @code{BINMODE} variable
-Under MS-Windows, OS/2 and MS-DOS, @command{gawk} (and many other text programs) silently
-translate end-of-line @code{"\r\n"} to @code{"\n"} on input and @code{"\n"}
-to @code{"\r\n"} on output.  A special @code{BINMODE} variable @value{COMMONEXT}
+@ifclear FOR_PRINT
+Under MS-Windows, OS/2 and MS-DOS,
+@end ifclear
+@ifset FOR_PRINT
+Under MS-Windows and MS-DOS,
+@end ifset
+@command{gawk} (and many other text programs) silently
+translate end-of-line @samp{\r\n} to @samp{\n} on input and @samp{\n}
+to @samp{\r\n} on output.  A special @code{BINMODE} variable @value{COMMONEXT}
 allows control over these translations and is interpreted as follows:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 If @code{BINMODE} is @code{"r"}, or one,
 then
@@ -34755,7 +37207,7 @@ The name @code{BINMODE} was chosen to match @command{mawk}
 @command{mawk} adds a @samp{-W BINMODE=@var{N}} option and an environment
 variable that can set @code{BINMODE}, @code{RS}, and @code{ORS}.  The
 files @file{binmode[1-3].awk} (under @file{gnu/lib/awk} in some of the
-prepared distributions) have been chosen to match @command{mawk}'s @samp{-W
+prepared binary distributions) have been chosen to match @command{mawk}'s @samp{-W
 BINMODE=@var{N}} option.  These can be changed or discarded; in particular,
 the setting of @code{RS} giving the fewest ``surprises'' is open to debate.
 @command{mawk} uses @samp{RS = "\r\n"} if binary mode is set on read, which is
@@ -34803,7 +37255,7 @@ moved into the @code{BEGIN} rule.
 
 @command{gawk} can be built and used ``out of the box'' under MS-Windows
 if you are using the @uref{http://www.cygwin.com, Cygwin environment}.
-This environment provides an excellent simulation of Unix, using the
+This environment provides an excellent simulation of GNU/Linux, using the
 GNU tools, such as Bash, the GNU Compiler Collection (GCC), GNU Make,
 and other GNU programs.  Compilation and installation for Cygwin is the
 same as for a Unix system:
@@ -34819,13 +37271,6 @@ When compared to GNU/Linux on the same system, the @samp{configure}
 step on Cygwin takes considerably longer.  However, it does finish,
 and then the @samp{make} proceeds as usual.
 
-@quotation NOTE
-The @samp{|&} operator and TCP/IP networking
-(@pxref{TCP/IP Networking})
-are fully supported in the Cygwin environment.  This is not true
-for any other environment on MS-Windows.
-@end quotation
-
 @node MSYS
 @appendixsubsubsec Using @command{gawk} In The MSYS Environment
 
@@ -34838,7 +37283,7 @@ been ported to MS-Windows that expect @command{gawk} to do automatic
 translation of @code{"\r\n"}, since it won't.  Caveat Emptor!
 
 @node VMS Installation
-@appendixsubsec How to Compile and Install @command{gawk} on VMS
+@appendixsubsec How to Compile and Install @command{gawk} on Vax/VMS and OpenVMS
 
 @c based on material from Pat Rankin <rankin@eql.caltech.edu>
 @c now rankin@pactechdata.com
@@ -34851,8 +37296,11 @@ The older designation ``VMS'' is used throughout to refer to OpenVMS.
 
 @menu
 * VMS Compilation::             How to compile @command{gawk} under VMS.
+* VMS Dynamic Extensions::      Compiling @command{gawk} dynamic extensions on
+                                VMS.
 * VMS Installation Details::    How to install @command{gawk} under VMS.
 * VMS Running::                 How to run @command{gawk} under VMS.
+* VMS GNV::                     The VMS GNV Project.
 * VMS Old Gawk::                An old version comes with some VMS systems.
 @end menu
 
@@ -34860,41 +37308,110 @@ The older designation ``VMS'' is used throughout to refer to OpenVMS.
 @appendixsubsubsec Compiling @command{gawk} on VMS
 @cindex compiling @command{gawk} for VMS
 
-To compile @command{gawk} under VMS, there is a @code{DCL} command procedure that
-issues all the necessary @code{CC} and @code{LINK} commands. There is
-also a @file{Makefile} for use with the @code{MMS} utility.  From the source
-directory, use either:
+To compile @command{gawk} under VMS, there is a @code{DCL} command procedure
+that issues all the necessary @code{CC} and @code{LINK} commands. There is
+also a @file{Makefile} for use with the @code{MMS} and @code{MMK} utilities.
+From the source directory, use either:
 
 @example
-$ @kbd{@@[.VMS]VMSBUILD.COM}
+$ @kbd{@@[.vms]vmsbuild.com}
 @end example
 
 @noindent
 or:
 
 @example
-$ @kbd{MMS/DESCRIPTION=[.VMS]DESCRIP.MMS GAWK}
+$ @kbd{MMS/DESCRIPTION=[.vms]descrip.mms gawk}
 @end example
 
-Older versions of @command{gawk} could be built with VAX C or
-GNU C on VAX/VMS, as well as with DEC C, but that is no longer
-supported.  DEC C (also briefly known as ``Compaq C'' and now known
-as ``HP C,'' but referred to here as ``DEC C'') is required.  Both
-@code{VMSBUILD.COM} and @code{DESCRIP.MMS} contain some obsolete support
-for the older compilers but are set up to use DEC C by default.
+@noindent
+or:
+
+@example
+$ @kbd{MMK/DESCRIPTION=[.vms]descrip.mms gawk}
+@end example
+
+@command{MMK} is an open source, free, near-clone of @command{MMS} and
+can better handle ODS-5 volumes with upper- and lowercase @value{FN}s.
+@command{MMK} is available from @uref{https://github.com/endlesssoftware/mmk}.
+
+With ODS-5 volumes and extended parsing enabled, the case of the target
+parameter may need to be exact.
+
+@command{gawk} has been tested under VAX/VMS 7.3 and Alpha/VMS 7.3-1
+using Compaq C V6.4, and Alpha/VMS 7.3, Alpha/VMS 7.3-2, and IA64/VMS 8.3.
+The most recent builds used HP C V7.3 on Alpha VMS 8.3 and both
+Alpha and IA64 VMS 8.4 used HP C 7.3.@footnote{The IA64 architecture
+is also known as ``Itanium.''}
+
+@xref{VMS GNV}, for information on building
+@command{gawk} as a PCSI kit that is compatible with the GNV product.
+
+@node VMS Dynamic Extensions
+@appendixsubsubsec Compiling @command{gawk} Dynamic Extensions on VMS
+
+The extensions that have been ported to VMS can be built using one of
+the following commands.
+
+@example
+$ @kbd{MMS/DESCRIPTION=[.vms]descrip.mms extensions}
+@end example
+
+@noindent
+or:
+
+@example
+$ @kbd{MMK/DESCRIPTION=[.vms]descrip.mms extensions}
+@end example
+
+@command{gawk} uses @code{AWKLIBPATH} as either an environment variable
+or a logical name to find the dynamic extensions.
+
+Dynamic extensions need to be compiled with the same compiler options for
+floating point, pointer size, and symbol name handling as were used
+to compile @command{gawk} itself.
+Alpha and Itanium should use IEEE floating point.  The pointer size is 32 bits,
+and the symbol name handling should be exact case with CRC shortening for
+symbols longer than 32 bits.
+
+For Alpha and Itanium:
+
+@example
+/name=(as_is,short)
+/float=ieee/ieee_mode=denorm_results
+@end example
+
+For VAX:
+
+@example
+/name=(as_is,short)
+@end example
+
+Compile time macros need to be defined before the first VMS-supplied
+header file is included.
+
+@example
+#if (__CRTL_VER >= 70200000) && !defined (__VAX)
+#define _LARGEFILE 1
+#endif
 
-@command{gawk} has been tested under Alpha/VMS 7.3-1 using Compaq C V6.4,
-and on Alpha/VMS 7.3, Alpha/VMS 7.3-2, and IA64/VMS 8.3.@footnote{The IA64
-architecture is also known as ``Itanium.''}
+#ifndef __VAX
+#ifdef __CRTL_VER
+#if __CRTL_VER >= 80200000
+#define _USE_STD_STAT 1
+#endif
+#endif
+#endif
+@end example
 
 @node VMS Installation Details
 @appendixsubsubsec Installing @command{gawk} on VMS
 
-To install @command{gawk}, all you need is a ``foreign'' command, which is
-a @code{DCL} symbol whose value begins with a dollar sign. For example:
+To use @command{gawk}, all you need is a ``foreign'' command, which is a
+@code{DCL} symbol whose value begins with a dollar sign. For example:
 
 @example
-$ @kbd{GAWK :== $disk1:[gnubin]GAWK}
+$ @kbd{GAWK :== $disk1:[gnubin]gawk}
 @end example
 
 @noindent
@@ -34906,10 +37423,29 @@ Alternatively, the symbol may be placed in the system-wide
 @file{sylogin.com} procedure, which allows all users
 to run @command{gawk}.
 
-Optionally, the help entry can be loaded into a VMS help library:
+If your @command{gawk} was installed by a PCSI kit into the
+@file{GNV$GNU:} directory tree, the program will be known as
+@file{GNV$GNU:[bin]gnv$gawk.exe} and the help file will be
+@file{GNV$GNU:[vms_help]gawk.hlp}.
+
+The PCSI kit also installs a @file{GNV$GNU:[vms_bin]gawk_verb.cld} file
+which can be used to add @command{gawk} and @command{awk} as DCL commands.
+
+For just the current process you can use:
 
 @example
-$ @kbd{LIBRARY/HELP SYS$HELP:HELPLIB [.VMS]GAWK.HLP}
+$ @kbd{set command gnv$gnu:[vms_bin]gawk_verb.cld}
+@end example
+
+Or the system manager can use @file{GNV$GNU:[vms_bin]gawk_verb.cld} to
+add the @command{gawk} and @command{awk} to the system wide @samp{DCLTABLES}.
+
+The DCL syntax is documented in the @file{gawk.hlp} file.
+
+Optionally, the @file{gawk.hlp} entry can be loaded into a VMS help library:
+
+@example
+$ @kbd{LIBRARY/HELP sys$help:helplib [.vms]gawk.hlp}
 @end example
 
 @noindent
@@ -34927,11 +37463,11 @@ provides information about both the @command{gawk} implementation and the
 
 The logical name @samp{AWK_LIBRARY} can designate a default location
 for @command{awk} program files.  For the @option{-f} option, if the specified
-file name has no device or directory path information in it, @command{gawk}
+@value{FN} has no device or directory path information in it, @command{gawk}
 looks in the current directory first, then in the directory specified
 by the translation of @samp{AWK_LIBRARY} if the file is not found.
 If, after searching in both directories, the file still is not found,
-@command{gawk} appends the suffix @samp{.awk} to the filename and retries
+@command{gawk} appends the suffix @samp{.awk} to the @value{FN} and retries
 the file search.  If @samp{AWK_LIBRARY} has no definition, a default value
 of @samp{SYS$LIBRARY:} is used for it.
 
@@ -34960,9 +37496,42 @@ One side effect of dual command-line parsing is that if there is only a
 single parameter (as in the quoted string program above), the command
 becomes ambiguous.  To work around this, the normally optional @option{--}
 flag is required to force Unix-style parsing rather than @code{DCL} parsing.  If any
-other dash-type options (or multiple parameters such as data files to
+other dash-type options (or multiple parameters such as @value{DF}s to
 process) are present, there is no ambiguity and @option{--} can be omitted.
 
+@cindex exit status, of VMS
+The @code{exit} value is a Unix-style value and is encoded to a VMS exit
+status value when the program exits.
+
+The VMS severity bits will be set based on the @code{exit} value.
+A failure is indicated by 1 and VMS sets the @code{ERROR} status.
+A fatal error is indicated by 2 and VMS will set the @code{FATAL} status.
+All other values will have the @code{SUCCESS} status.  The exit value is
+encoded to comply with VMS coding standards and will have the
+@code{C_FACILITY_NO} of @code{0x350000} with the constant @code{0xA000}
+added to the number shifted over by 3 bits to make room for the severity codes.
+
+To extract the actual @command{gawk} exit code from the VMS status use:
+
+@example
+unix_status = (vms_status .and. &x7f8) / 8
+@end example
+
+@noindent
+A C program that uses @code{exec()} to call @command{gawk} will get the original
+Unix-style exit value.
+
+Older versions of @command{gawk} treated a Unix exit code 0 as 1, a failure
+as 2, a fatal error as 4, and passed all the other numbers through.
+This violated the VMS exit status coding requirements.
+
+@cindex floating-point, VAX/VMS
+VAX/VMS floating point uses unbiased rounding. @xref{Round Function}.
+
+VMS reports time values in GMT unless one of the @code{SYS$TIMEZONE_RULE}
+or @code{TZ} logical names is set.  Older versions of VMS, such as VAX/VMS
+7.3 do not set these logical names.
+
 @c @cindex directory search
 @c @cindex path, search
 @cindex search paths
@@ -34974,6 +37543,21 @@ of @env{AWKPATH} is a comma-separated list of directory specifications.
 When defining it, the value should be quoted so that it retains a single
 translation and not a multitranslation @code{RMS} searchlist.
 
+@node VMS GNV
+@appendixsubsubsec The VMS GNV Project
+
+The VMS GNV package provides a build environment similar to POSIX with ports
+of a collection of open source tools.  The @command{gawk} found in the GNV
+base kit is an older port.  Currently the GNV project is being reorganized
+to supply individual PCSI packages for each component.
+See @w{@uref{https://sourceforge.net/p/gnv/wiki/InstallingGNVPackages/}.}
+
+The normal build procedure for @command{gawk} produces a program that
+is suitable for use with GNV.
+
+The @file{vms/gawk_build_steps.txt} in the source documents the procedure
+for building a VMS PCSI kit that is compatible with GNV.
+
 @ignore
 @c The VMS POSIX product, also known as POSIX for OpenVMS, is long defunct
 @c and building gawk for it has not been tested in many years, but these
@@ -35021,7 +37605,7 @@ define a symbol, as follows:
 $ @kbd{gawk :== $sys$common:[syshlp.examples.tcpip.snmp]gawk.exe}
 @end example
 
-This is apparently version 2.15.6, which is extremely old. We
+This is apparently @value{PVERSION} 2.15.6, which is extremely old. We
 recommend compiling and using the current version.
 
 @c ENDOFRANGE opgawx
@@ -35050,8 +37634,8 @@ what you're trying to do.  If it's not clear whether you should be able
 to do something or not, report that too; it's a bug in the documentation!
 
 Before reporting a bug or trying to fix it yourself, try to isolate it
-to the smallest possible @command{awk} program and input data file that
-reproduces the problem.  Then send us the program and data file,
+to the smallest possible @command{awk} program and input @value{DF} that
+reproduces the problem.  Then send us the program and @value{DF},
 some idea of what kind of Unix system you're using,
 the compiler you used to compile @command{gawk}, and the exact results
 @command{gawk} gave you.  Also say what you expected to occur; this helps
@@ -35067,12 +37651,14 @@ Once you have a precise problem, send email to
 @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}.
 
 @cindex Robbins, Arnold
-Using this address automatically sends a copy of your
-mail to me.  If necessary, I can be reached directly at
+The @command{gawk} maintainers subscribe to this address and
+thus they will receive your bug report.
+If necessary, the primary maintainer can be reached directly at
 @EMAIL{arnold@@skeeve.com,arnold at skeeve dot com}.
 The bug reporting address is preferred since the
 email list is archived at the GNU Project.
-@emph{All email should be in English, since that is my native language.}
+@emph{All email should be in English. This is the only language
+understood in common by all the maintainers.}
 
 @cindex @code{comp.lang.awk} newsgroup
 @quotation CAUTION
@@ -35105,32 +37691,39 @@ mail at the Internet address noted previously.
 
 If you find bugs in one of the non-Unix ports of @command{gawk}, please send
 an electronic mail message to the person who maintains that port.  They
-are named in the following list, as well as in the @file{README} file in the @command{gawk}
-distribution.  Information in the @file{README} file should be considered
-authoritative if it conflicts with this @value{DOCUMENT}.
+are named in the following list, as well as in the @file{README} file
+in the @command{gawk} distribution.  Information in the @file{README}
+file should be considered authoritative if it conflicts with this
+@value{DOCUMENT}.
 
 The people maintaining the non-Unix ports of @command{gawk} are
 as follows:
 
-@multitable {MS-Windows with MINGW} {123456789012345678901234567890123456789001234567890}
+@c put the index entries outside the table, for docbook
 @cindex Deifik, Scott
+@cindex Zaretskii, Eli
+@cindex Buening, Andreas
+@cindex Rankin, Pat
+@cindex Malmberg, John
+@cindex Pitts, Dave
+@multitable {MS-Windows with MinGW} {123456789012345678901234567890123456789001234567890}
 @item MS-DOS with DJGPP @tab Scott Deifik, @EMAIL{scottd.mail@@sbcglobal.net,scottd dot mail at sbcglobal dot net}.
 
-@cindex Zaretskii, Eli
-@item MS-Windows with MINGW @tab Eli Zaretskii, @EMAIL{eliz@@gnu.org,eliz at gnu dot org}.
+@item MS-Windows with MinGW @tab Eli Zaretskii, @EMAIL{eliz@@gnu.org,eliz at gnu dot org}.
 
-@cindex Buening, Andreas
+@c Leave this in the print version on purpose.
+@c OS/2 is not mentioned anywhere else in the print version though.
 @item OS/2 @tab Andreas Buening, @EMAIL{andreas.buening@@nexgo.de,andreas dot buening at nexgo dot de}.
 
-@cindex Rankin, Pat
-@item VMS @tab Pat Rankin, @EMAIL{r.pat.rankin@@gmail.com,r.pat.rankin at gmail.com}
+@item VMS @tab Pat Rankin, @EMAIL{r.pat.rankin@@gmail.com,r.pat.rankin at gmail.com}, and
+John Malmberg, @EMAIL{wb8tyw@@qsl.net,wb8tyw at qsl.net}.
 
-@cindex Pitts, Dave
 @item z/OS (OS/390) @tab Dave Pitts, @EMAIL{dpitts@@cozx.com,dpitts at cozx dot com}.
 @end multitable
 
 If your bug is also reproducible under Unix, please send a copy of your
-report to the @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org} email list as well.
+report to the @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org} email
+list as well.
 @c ENDOFRANGE dbugg
 @c ENDOFRANGE tblgawb
 
@@ -35159,7 +37752,7 @@ This @value{SECTION} briefly describes where to get them:
 @cindex Kernighan, Brian
 @cindex source code, Brian Kernighan's @command{awk}
 @cindex @command{awk}, versions of, See Also Brian Kernighan's @command{awk}
-@cindex Brian Kernighan's @command{awk}
+@cindex Brian Kernighan's @command{awk}, source code
 @item Unix @command{awk}
 Brian Kernighan, one of the original designers of Unix @command{awk},
 has made his implementation of
@@ -35179,6 +37772,7 @@ It is available in several archive formats:
 @uref{http://www.cs.princeton.edu/~bwk/btl.mirror/awk.zip}
 @end table
 
+@cindex @command{git} utility
 You can also retrieve it from Git Hub:
 
 @example
@@ -35198,12 +37792,17 @@ from GCC (the GNU Compiler Collection) works quite nicely.
 for a list of extensions in this @command{awk} that are not in POSIX @command{awk}.
 
 @cindex Brennan, Michael
-@cindex @command{mawk} program
+@cindex @command{mawk} utility
 @cindex source code, @command{mawk}
 @item @command{mawk}
 Michael Brennan wrote an independent implementation of @command{awk},
-called @command{mawk}.  It is available under the GPL
-(@pxref{Copying}),
+called @command{mawk}.  It is available under the
+@ifclear FOR_PRINT
+GPL (@pxref{Copying}),
+@end ifclear
+@ifset FOR_PRINT
+GPL,
+@end ifset
 just as @command{gawk} is.
 
 The original distribution site for the @command{mawk} source code
@@ -35244,7 +37843,7 @@ To get @command{awka}, go to @url{http://sourceforge.net/projects/awka}.
 The project seems to be frozen; no new code changes have been made
 since approximately 2003.
 
-@cindex Beebe, Nelson
+@cindex Beebe, Nelson H.F.@:
 @cindex @command{pawk} (profiling version of Brian Kernighan's @command{awk})
 @cindex source code, @command{pawk}
 @item @command{pawk}
@@ -35272,10 +37871,10 @@ information, see the @uref{http://busybox.net, project's home page}.
 @cindex Solaris, POSIX-compliant @command{awk}
 @cindex source code, Solaris @command{awk}
 @item The OpenSolaris POSIX @command{awk}
-The version of @command{awk} in @file{/usr/xpg4/bin} on Solaris is
-more-or-less POSIX-compliant. It is based on the @command{awk} from
-Mortice Kern Systems for PCs.
-This author was able to make it compile and work under GNU/Linux
+The versions of @command{awk} in @file{/usr/xpg4/bin} and
+@file{/usr/xpg6/bin} on Solaris are more-or-less POSIX-compliant.
+They are based on the @command{awk} from Mortice Kern Systems for PCs.
+This author was able to make this code compile and work under GNU/Linux
 with 1--2 hours of work.  Making it more generally portable (using
 GNU Autoconf and/or Automake) would take more work, and this
 has not been done, at least to our knowledge.
@@ -35307,6 +37906,7 @@ This is an embeddable @command{awk} interpreter derived from
 @uref{http://repo.hu/projects/libmawk/}.
 
 @item @code{pawk}
+@cindex source code, @command{pawk} (Python version)
 @cindex @code{pawk}, @command{awk}-like facilities for Python
 This is a Python module that claims to bring @command{awk}-like
 features to Python. See @uref{https://github.com/alecthomas/pawk}
@@ -35329,15 +37929,56 @@ under the GPL. It has a large number of extensions over standard
 See @uref{http://www.quiktrim.org/QTawk.html} for more information,
 including the manual and a download link.
 
+The project may also be frozen; no new code changes have been made
+since approximately 2008.
+
 @item Other Versions
 See also the @uref{http://en.wikipedia.org/wiki/Awk_language#Versions_and_implementations,
 Wikipedia article}, for information on additional versions.
 
 @end table
+@c ENDOFRANGE awkim
+
+@node Installation summary
+@appendixsec Summary
+
+@itemize @value{BULLET}
+@item
+The @command{gawk} distribution is available from GNU project's main
+distribution site, @code{ftp.gnu.org}.  The canonical build recipe is:
+
+@example
+wget http://ftp.gnu.org/gnu/gawk/gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz
+tar -xvpzf gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz
+cd gawk-@value{VERSION}.@value{PATCHLEVEL}
+./configure && make && make check
+@end example
+
+@item
+@command{gawk} may be built on non-POSIX systems as well. The currently
+supported systems are MS-Windows using DJGPP, MSYS, MinGW and Cygwin,
+@ifclear FOR_PRINT
+OS/2 using EMX,
+@end ifclear
+and both Vax/VMS and OpenVMS.
+Instructions for each system are included in this @value{CHAPTER}.
+
+@item
+Bug reports should be sent via email to @email{bug-gawk@@gnu.org}.
+Bug reports should be in English, and should include the version of @command{gawk},
+how it was compiled, and a short program and @value{DF} which demonstrate
+the problem.
+
+@item
+There are a number of other freely available @command{awk}
+implementations.  Many are POSIX compliant; others are less so.
+
+@end itemize
+
 @c ENDOFRANGE gligawk
 @c ENDOFRANGE ingawk
-@c ENDOFRANGE awkim
 
+@ifclear FOR_PRINT
 @node Notes
 @appendix Implementation Notes
 @c STARTOFRANGE gawii
@@ -35357,6 +37998,7 @@ maintainers of @command{gawk}.  Everything in it applies specifically to
 * Implementation Limitations::  Some limitations of the implementation.
 * Extension Design::            Design notes about the extension API.
 * Old Extension Mechanism::     Some compatibility for old extensions.
+* Notes summary::               Summary of implementation notes.
 @end menu
 
 @node Compatibility Mode
@@ -35377,7 +38019,7 @@ is one more option available on the command line:
 @table @code
 @item -Y
 @itemx --parsedebug
-Prints out the parse stack information as the program is being parsed.
+Print out the parse stack information as the program is being parsed.
 @end table
 
 This option is intended only for serious @command{gawk} developers
@@ -35401,8 +38043,8 @@ as well as any considerations you should bear in mind.
                                 @command{gawk}.
 * New Ports::                   Porting @command{gawk} to a new operating
                                 system.
-* Derived Files::               Why derived files are kept in the
-                                @command{git} repository.
+* Derived Files::               Why derived files are kept in the Git
+                                repository.
 @end menu
 
 @node Accessing The Source
@@ -35412,6 +38054,7 @@ As @command{gawk} is Free Software, the source code is always available.
 @ref{Gawk Distribution}, describes how to get and build the formal,
 released versions of @command{gawk}.
 
+@cindex @command{git} utility
 However, if you want to modify @command{gawk} and contribute back your
 changes, you will probably wish to work with the development version.
 To do so, you will need to access the @command{gawk} source code
@@ -35425,8 +38068,8 @@ git clone git://git.savannah.gnu.org/gawk.git
 @end example
 
 @noindent
-This will clone the @command{gawk} repository.  If you are behind a
-firewall that will not allow you to use the Git native protocol, you
+This clones the @command{gawk} repository.  If you are behind a
+firewall that does not allow you to use the Git native protocol, you
 can still access the repository using:
 
 @example
@@ -35454,7 +38097,7 @@ that has a Git plug-in for working with Git repositories.
 You are free to add any new features you like to @command{gawk}.
 However, if you want your changes to be incorporated into the @command{gawk}
 distribution, there are several steps that you need to take in order to
-make it possible to include your changes:
+make it possible to include them:
 
 @enumerate 1
 @item
@@ -35476,14 +38119,15 @@ or @EMAIL{assign@@gnu.org,assign at gnu dot org}.
 @item
 Get the latest version.
 It is much easier for me to integrate changes if they are relative to
-the most recent distributed version of @command{gawk}.  If your version of
-@command{gawk} is very old, I may not be able to integrate them at all.
+the most recent distributed version of @command{gawk}, or better yet,
+relative to the latest code in the Git repository.  If your version of
+@command{gawk} is very old, I may not be able to integrate your changes at all.
 (@xref{Getting},
 for information on getting the latest version of @command{gawk}.)
 
 @item
 @ifnotinfo
-Follow the @cite{GNU Coding Standards}.
+Follow the @uref{http://www.gnu.org/prep/standards/, @cite{GNU Coding Standards}}.
 @end ifnotinfo
 @ifinfo
 See @inforef{Top, , Version, standards, GNU Coding Standards}.
@@ -35504,7 +38148,7 @@ using the traditional ``K&R'' style, particularly as regards to the placement
 of braces and the use of TABs.  In brief, the coding rules for @command{gawk}
 are as follows:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Use ANSI/ISO style (prototype) function headers when defining functions.
 
@@ -35587,6 +38231,7 @@ If possible, please update the @command{man} page as well.
 
 You will also have to sign paperwork for your documentation changes.
 
+@cindex @command{git} utility
 @item
 Submit changes as unified diffs.
 Use @samp{diff -u -r -N} to compare
@@ -35607,6 +38252,7 @@ not do so, particularly if there are lots of changes.
 Include an entry for the @file{ChangeLog} file with your submission.
 This helps further minimize the amount of work I have to do,
 making it easier for me to accept patches.
+It is simplest if you just make this part of your diff.
 @end enumerate
 
 Although this sounds like a lot of work, please remember that while you
@@ -35642,11 +38288,9 @@ Be prepared to sign the appropriate paperwork.
 In order for the FSF to distribute your code, you must either place
 your code in the public domain and submit a signed statement to that
 effect, or assign the copyright in your code to the FSF.
-@ifinfo
 Both of these actions are easy to do and @emph{many} people have done so
 already. If you have questions, please contact me, or
 @email{gnu@@gnu.org}.
-@end ifinfo
 
 @item
 When doing a port, bear in mind that your code must coexist peacefully
@@ -35666,10 +38310,39 @@ A number of the files that come with @command{gawk} are maintained by other
 people.  Thus, you should not change them
 unless it is for a very good reason; i.e., changes are not out of the
 question, but changes to these files are scrutinized extra carefully.
-The files are @file{dfa.c}, @file{dfa.h}, @file{getopt1.c}, @file{getopt.c},
-@file{getopt.h}, @file{install-sh}, @file{mkinstalldirs}, @file{regcomp.c},
-@file{regex.c}, @file{regexec.c}, @file{regexex.c}, @file{regex.h},
-@file{regex_internal.c}, and @file{regex_internal.h}.
+The files are
+@file{dfa.c},
+@file{dfa.h},
+@file{getopt.c},
+@file{getopt.h},
+@file{getopt1.c},
+@file{getopt_int.h},
+@file{gettext.h},
+@file{regcomp.c},
+@file{regex.c},
+@file{regex.h},
+@file{regex_internal.c},
+@file{regex_internal.h},
+and
+@file{regexec.c}.
+
+@item
+A number of other files are provided by the GNU
+Autotools (Autoconf, Automake, and GNU @command{gettext}).
+You should not change them either, unless it is for a very
+good reason. The files are
+@file{ABOUT-NLS},
+@file{config.guess},
+@file{config.rpath},
+@file{config.sub},
+@file{depcomp},
+@file{INSTALL},
+@file{install-sh},
+@file{missing},
+@file{mkinstalldirs},
+@file{xalloc.h},
+and
+@file{ylwrap}.
 
 @item
 Be willing to continue to maintain the port.
@@ -35720,14 +38393,16 @@ In the code that you supply and maintain, feel free to use a
 coding style and brace layout that suits your taste.
 
 @node Derived Files
-@appendixsubsec Why Generated Files Are Kept In @command{git}
+@appendixsubsec Why Generated Files Are Kept In Git
 
+@c STARTOFRANGE gawkgit
+@cindex Git, use of for @command{gawk} source code
 @c From emails written March 22, 2012, to the gawk developers list.
 
-If you look at the @command{gawk} source in the @command{git}
+If you look at the @command{gawk} source in the Git
 repository, you will notice that it includes files that are automatically
 generated by GNU infrastructure tools, such as @file{Makefile.in} from
-@command{automake} and even @file{configure} from @command{autoconf}.
+Automake and even @file{configure} from Autoconf.
 
 This is different from many Free Software projects that do not store
 the derived files, because that keeps the repository less cluttered,
@@ -35753,11 +38428,10 @@ there a guarantee that we could find that @command{bison} version? Or that
 @emph{it} would build?)
 
 If the repository has all the generated files, then it's easy to just check
-them out and build. (Or @emph{easier}, depending upon how far back we go.
-@code{:-)})
+them out and build. (Or @emph{easier}, depending upon how far back we go.)
 
 And that brings us to the second (and stronger) reason why all the files
-really need to be in @command{git}.  It boils down to who do you cater
+really need to be in Git.  It boils down to who do you cater
 to---the @command{gawk} developer(s), or the user who just wants to check
 out a version and try it out?
 
@@ -35766,10 +38440,10 @@ wants it to be possible for any interested @command{awk} user in the
 world to just clone the repository, check out the branch of interest and
 build it. Without their having to have the correct version(s) of the
 autotools.@footnote{There is one GNU program that is (in our opinion)
-severely difficult to bootstrap from the @command{git} repository. For
-example, on the author's old (but still working) PowerPC macintosh with
+severely difficult to bootstrap from the Git repository. For
+example, on the author's old (but still working) PowerPC Macintosh with
 Mac OS X 10.5, it was necessary to bootstrap a ton of software, starting
-with @command{git} itself, in order to try to work with the latest code.
+with Git itself, in order to try to work with the latest code.
 It's not pleasant, and especially on older systems, it's a big waste
 of time.
 
@@ -35792,14 +38466,14 @@ This is extremely important for the @code{master} and
 
 Further, the @command{gawk} maintainer would argue that it's also
 important for the @command{gawk} developers. When he tried to check out
-the @code{xgawk} branch@footnote{A branch created by one of the other
+the @code{xgawk} branch@footnote{A branch (since removed) created by one of the other
 developers that did not include the generated files.} to build it, he
 couldn't. (No @file{ltmain.sh} file, and he had no idea how to create it,
 and that was not the only problem.)
 
 He felt @emph{extremely} frustrated.  With respect to that branch,
 the maintainer is no different than Jane User who wants to try to build
-@code{gawk-4.0-stable} or @code{master} from the repository.
+@code{gawk-4.1-stable} or @code{master} from the repository.
 
 Thus, the maintainer thinks that it's not just important, but critical,
 that for any given branch, the above incantation @emph{just works}.
@@ -35819,29 +38493,29 @@ It's the maintainer's job to merge them and he will deal with it.
 
 @item
 He is really good at @samp{git diff x y > /tmp/diff1 ; gvim /tmp/diff1} to
-remove the diffs that aren't of interest in order to review code. @code{:-)}
+remove the diffs that aren't of interest in order to review code.
 @end enumerate
 
 @item
 It would certainly help if everyone used the same versions of the GNU tools
 as he does, which in general are the latest released versions of
-@command{automake},
-@command{autoconf},
+Automake,
+Autoconf,
 @command{bison},
 and
-@command{gettext}.
+GNU @command{gettext}.
 
 @ignore
-If it would help if I sent out an "I just upgraded to version x.y
-of tool Z" kind of message to this list, I can do that.  Up until
+If it would help if I sent out an ``I just upgraded to version x.y
+of tool Z'' kind of message to this list, I can do that.  Up until
 now it hasn't been a real issue since I'm the only one who's been
 dorking with the configuration machinery.
 @end ignore
 
-@enumerate A
-@item
+@c @enumerate A
+@c @item
 Installing from source is quite easy. It's how the maintainer worked for years
-under Fedora.
+(and still works).
 He had @file{/usr/local/bin} at the front of his @env{PATH} and just did:
 
 @example
@@ -35852,10 +38526,11 @@ cd @var{package}-@var{x}.@var{y}.@var{z}
 make install    # as root
 @end example
 
-@item
+@c @item
+@ignore
 These days the maintainer uses Ubuntu 12.04 which is medium current, but
-he is already doing the above for @command{autoconf}, @command{automake}
-and @command{bison}.
+he is already doing the above for Automake, Autoconf, and @command{bison}.
+@end ignore
 
 @ignore
 (C. Rant: Recent Linux versions with GNOME 3 really suck. What
@@ -35863,7 +38538,7 @@ and @command{bison}.
     me to Ubuntu, but Ubuntu 11.04 and 11.10 are totally unusable from
     a UI perspective. Bleah.)
 @end ignore
-@end enumerate
+@c @end enumerate
 
 @ignore
 @item
@@ -35879,7 +38554,7 @@ the "real" changes and the second with "everything else needed for
 Most of the above was originally written by the maintainer to other
 @command{gawk} developers.  It raised the objection from one of
 the developers ``@dots{} that anybody pulling down the source from
-@command{git} is not an end user.''
+Git is not an end user.''
 
 However, this is not true. There are ``power @command{awk} users''
 who can build @command{gawk} (using the magic incantation shown previously)
@@ -35889,10 +38564,10 @@ kept buildable all the time.
 It was then suggested that there be a @command{cron} job to create
 nightly tarballs of ``the source.''  Here, the problem is that there
 are source trees, corresponding to the various branches! So,
-nightly tar balls aren't the answer, especially as the repository can go
+nightly tarballs aren't the answer, especially as the repository can go
 for weeks without significant change being introduced.
 
-Fortunately, the @command{git} server can meet this need. For any given
+Fortunately, the Git server can meet this need. For any given
 branch named @var{branchname}, use:
 
 @example
@@ -35901,7 +38576,7 @@ wget http://git.savannah.gnu.org/cgit/gawk.git/snapshot/gawk-@var{branchname}.ta
 
 @noindent
 to retrieve a snapshot of the given branch.
-
+@c ENDOFRANGE gawkgit
 
 @node Future Extensions
 @appendixsec Probable Future Extensions
@@ -35945,14 +38620,17 @@ Larry
 @quotation
 @i{AWK is a language similar to PERL, only considerably more elegant.}
 @author Arnold Robbins
+@end quotation
 
+@quotation
 @i{Hey!}
 @author Larry Wall
 @end quotation
 
-The @file{TODO} file in the @command{gawk} Git repository lists possible
-future enhancements.  Some of these relate to the source code, and others
-to possible new features.  Please see that file for the list.
+The @file{TODO} file in the @code{master} branch of the @command{gawk}
+Git repository lists possible future enhancements.  Some of these relate
+to the source code, and others to possible new features.  Please see
+that file for the list.
 @xref{Additions},
 if you are interested in tackling any of the projects listed there.
 
@@ -35966,7 +38644,7 @@ different limits.
 @multitable @columnfractions .40 .60
 @headitem Item @tab Limit
 @item Characters in a character class @tab 2^(number of bits per byte)
-@item Length of input record @tab @code{MAX_INT }
+@item Length of input record @tab @code{MAX_INT}
 @item Length of output record @tab Unlimited
 @item Length of source line @tab Unlimited
 @item Number of fields in a record @tab @code{MAX_LONG}
@@ -35975,9 +38653,9 @@ different limits.
 @item Number of input records total @tab @code{MAX_LONG}
 @item Number of pipe redirections @tab min(number of processes per user, number of open files)
 @item Numeric values @tab Double-precision floating point (if not using MPFR)
-@item Size of a field @tab @code{MAX_INT }
-@item Size of a literal string @tab @code{MAX_INT }
-@item Size of a printf string @tab @code{MAX_INT }
+@item Size of a field @tab @code{MAX_INT}
+@item Size of a literal string @tab @code{MAX_INT}
+@item Size of a printf string @tab @code{MAX_INT}
 @end multitable
 
 @node Extension Design
@@ -36012,7 +38690,7 @@ mechanism was bolted onto the side and was not really well thought out.
 
 The old extension mechanism had several problems:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 It depended heavily upon @command{gawk} internals.  Any time the
 @code{NODE} structure@footnote{A critical central data structure
@@ -36024,8 +38702,8 @@ documentation in this @value{DOCUMENT}, but it was quite minimal.
 @item
 Being able to call into @command{gawk} from an extension required linker
 facilities that are common on Unix-derived systems but that did
-not work on Windows systems; users wanting extensions on Windows
-had to statically link them into @command{gawk}, even though Windows supports
+not work on MS-Windows systems; users wanting extensions on MS-Windows
+had to statically link them into @command{gawk}, even though MS-Windows supports
 dynamic loading of shared objects.
 
 @item
@@ -36048,7 +38726,7 @@ project is provided in @ref{gawkextlib}.
 
 Some goals for the new API were:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The API should be independent of @command{gawk} internals.  Changes in
 @command{gawk} internals should not be visible to the writer of an
@@ -36063,7 +38741,7 @@ The API should enable extensions written in C or C++ to have roughly the
 same ``appearance'' to @command{awk}-level code as @command{awk}
 functions do. This means that extensions should have:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The ability to access function parameters.
 
@@ -36079,13 +38757,13 @@ in order to loop over all the element in an easy fashion for C code.
 
 @item
 The ability to create arrays (including @command{gawk}'s true
-multidimensional arrays).
+arrays of arrays).
 @end itemize
 @end itemize
 
 Some additional important goals were:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The API should use only features in ISO C 90, so that extensions
 can be written using the widest range of C and C++ compilers. The header
@@ -36100,15 +38778,15 @@ The API mechanism should not require access to @command{gawk}'s
 symbols@footnote{The @dfn{symbols} are the variables and functions
 defined inside @command{gawk}.  Access to these symbols by code
 external to @command{gawk} loaded dynamically at runtime is
-problematic on Windows.} by the compile-time or dynamic linker,
-in order to enable creation of extensions that also work on Windows.
+problematic on MS-Windows.} by the compile-time or dynamic linker,
+in order to enable creation of extensions that also work on MS-Windows.
 @end itemize
 
 During development, it became clear that there were other features
 that should be available to extensions, which were also subsequently
 provided:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Extensions should have the ability to hook into @command{gawk}'s
 I/O redirection mechanism.  In particular, the @command{xgawk}
@@ -36119,7 +38797,7 @@ two-way I/O.
 
 @item
 An extension should be able to provide a ``call back'' function
-to perform clean up actions when @command{gawk} exits.
+to perform cleanup actions when @command{gawk} exits.
 
 @item
 An extension should be able to provide a version string so that
@@ -36189,7 +38867,7 @@ to provide a minimal yet powerful set of features for creating extensions.
 
 The API can later be expanded, in two ways:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @command{gawk} passes an ``extension id'' into the extension when it
 first loads the extension.  The extension then passes this id back
@@ -36212,12 +38890,12 @@ to any of the above.
 
 @ref{Dynamic Extensions}, describes the supported API and mechanisms
 for writing extensions for @command{gawk}.  This API was introduced
-in version 4.1.  However, for many years @command{gawk}
+in @value{PVERSION} 4.1.  However, for many years @command{gawk}
 provided an extension mechanism that required knowledge of @command{gawk}
 internals and that was not as well designed.
 
-In order to provide a transition period, @command{gawk} version
-4.1 continues to support the original extension mechanism.
+In order to provide a transition period, @command{gawk} @value{PVERSION} 4.1
+continues to support the original extension mechanism.
 This will be true for the life of exactly one major release.  This support
 will be withdrawn, and removed from the source code, at the next major
 release.
@@ -36243,6 +38921,42 @@ The @command{gawk} development team strongly recommends that you
 convert any old extensions that you may have to use the new API
 described in @ref{Dynamic Extensions}.
 
+@node Notes summary
+@appendixsec Summary
+
+@itemize @value{BULLET}
+@item
+@command{gawk}'s extensions can be disabled with either the
+@option{--traditional} option or with the @option{--posix} option.
+The @option{--parsedebug} option is available if @command{gawk} is
+compiled with @samp{-DDEBUG}.
+
+@item
+The source code for @command{gawk} is maintained in a publicly
+accessable Git repository. Anyone may check it out and view the source.
+
+@item
+Contributions to @command{gawk} are welcome. Following the steps
+outlined in this @value{CHAPTER} will make it easier to integrate
+your contributions into the code base.
+This applies both to new feature contributions and to ports to
+additional operating systems.
+
+@item
+@command{gawk} has some limits---generally those that are imposed by
+the machine architecture.
+
+@item
+The extension API design was intended to solve a number of problems
+with the previous extension mechanism, enable features needed by
+the @code{xgawk} project, and provide binary compatibility going forward.
+
+@item
+The previous extension mechanism is still supported in @value{PVERSION} 4.1
+of @command{gawk}, but it @emph{will} be removed in the next major release.
+
+@end itemize
+
 @c ENDOFRANGE impis
 @c ENDOFRANGE gawii
 
@@ -36270,8 +38984,15 @@ other introductory texts that you should refer to instead.)
 
 @cindex processing data
 At the most basic level, the job of a program is to process
-some input data and produce results. See @ref{figure-general-flow}.
+some input data and produce results.
+@ifnotdocbook
+See @ref{figure-general-flow}.
+@end ifnotdocbook
+@ifdocbook
+See @inlineraw{docbook, <xref linkend="figure-general-flow"/>}.
+@end ifdocbook
 
+@ifnotdocbook
 @float Figure,figure-general-flow
 @caption{General Program Flow}
 @ifinfo
@@ -36281,6 +39002,16 @@ some input data and produce results. See @ref{figure-general-flow}.
 @center @image{general-program, , , General program flow}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-general-flow" float="0">
+<title>General Program Flow</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="general-program.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 @cindex compiled programs
 @cindex interpreted programs
@@ -36296,9 +39027,15 @@ instructions in your program to process the data.
 
 @cindex programming, basic steps
 When you write a program, it usually consists
-of the following, very basic set of steps, as shown
-in @ref{figure-process-flow}:
+of the following, very basic set of steps,
+@ifnotdocbook
+as shown in @ref{figure-process-flow}:
+@end ifnotdocbook
+@ifdocbook
+as shown in @inlineraw{docbook, <xref linkend="figure-process-flow"/>}:
+@end ifdocbook
 
+@ifnotdocbook
 @float Figure,figure-process-flow
 @caption{Basic Program Steps}
 @ifinfo
@@ -36308,6 +39045,16 @@ in @ref{figure-process-flow}:
 @center @image{process-flow, , , Basic Program Stages}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-process-flow" float="0">
+<title>Basic Program Stages</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="process-flow.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 @table @asis
 @item Initialization
@@ -36403,7 +39150,7 @@ Individual variables, as well as numeric and string variables, are
 referred to as @dfn{scalar} values.
 Groups of values, such as arrays, are not scalars.
 
-@ref{General Arithmetic}, provided a basic introduction to numeric
+@ref{Computer Arithmetic}, provided a basic introduction to numeric
 types (integer and floating-point) and how they are used in a computer.
 Please review that information, including a number of caveats that
 were presented.
@@ -36419,14 +39166,14 @@ like this: @code{""}.
 
 Humans are used to working in decimal; i.e., base 10.  In base 10,
 numbers go from 0 to 9, and then ``roll over'' into the next
-column.  (Remember grade school? 42 is 4 times 10 plus 2.)
+column.  (Remember grade school? 42 = 4 x 10 + 2.)
 
 There are other number bases though.  Computers commonly use base 2
 or @dfn{binary}, base 8 or @dfn{octal}, and base 16 or @dfn{hexadecimal}.
 In binary, each column represents two times the value in the column to
 its right. Each column may contain either a 0 or a 1.
-Thus, binary 1010 represents 1 times 8, plus 0 times 4, plus 1 times 2,
-plus 0 times 1, or decimal 10.
+Thus, binary 1010 represents (1 x 8) + (0 x 4) + (1 x 2)
++ (0 x 1), or decimal 10.
 Octal and hexadecimal are discussed more in
 @ref{Nondecimal-numbers}.
 
@@ -36463,7 +39210,7 @@ Where it makes sense, POSIX @command{awk} is compatible with 1999 ISO C.
 @item Action
 A series of @command{awk} statements attached to a rule.  If the rule's
 pattern matches an input record, @command{awk} executes the
-rule's action.  Actions are always enclosed in curly braces.
+rule's action.  Actions are always enclosed in braces.
 (@xref{Action Overview}.)
 
 @cindex Spencer, Henry
@@ -36478,7 +39225,7 @@ better written in another language.
 You can get it from @uref{http://awk.info/?awk100/aaa}.
 
 @cindex Ada programming language
-@cindex Programming languages, Ada
+@cindex programming languages, Ada
 @item Ada
 A programming language originally defined by the U.S.@: Department of
 Defense for embedded programming. It was designed to enforce good
@@ -36546,9 +39293,6 @@ The GNU version of the standard shell
 @end ifinfo
 See also ``Bourne Shell.''
 
-@item BBS
-See ``Bulletin Board System.''
-
 @item Bit
 Short for ``Binary Digit.''
 All values in computer memory ultimately reduce to binary digits: values
@@ -36571,7 +39315,7 @@ Named after the English mathematician Boole. See also ``Logical Expression.''
 
 @item Bourne Shell
 The standard shell (@file{/bin/sh}) on Unix and Unix-like systems,
-originally written by Steven R.@: Bourne.
+originally written by Steven R.@: Bourne at Bell Laboratories.
 Many shells (Bash, @command{ksh}, @command{pdksh}, @command{zsh}) are
 generally upwardly compatible with the Bourne shell.
 
@@ -36621,12 +39365,9 @@ Changing some of them affects @command{awk}'s running environment.
 (@xref{Built-in Variables}.)
 
 @item Braces
-See ``Curly Braces.''
-
-@item Bulletin Board System
-A computer system allowing users to log in and read and/or leave messages
-for other users of the system, much like leaving paper notes on a bulletin
-board.
+The characters @samp{@{} and @samp{@}}.  Braces are used in
+@command{awk} for delimiting actions, compound statements, and function
+bodies.
 
 @item C
 The system programming language that most GNU software is written in.  The
@@ -36651,9 +39392,11 @@ or place. The most common character set in use today is ASCII (American
 Standard Code for Information Interchange).  Many European
 countries use an extension of ASCII known as ISO-8859-1 (ISO Latin-1).
 The @uref{http://www.unicode.org, Unicode character set} is
-becoming increasingly popular and standard, and is particularly
+increasingly popular and standard, and is particularly
 widely used on GNU/Linux systems.
 
+@cindex Kernighan, Brian
+@cindex Bentley, Jon
 @cindex @command{chem} utility
 @item CHEM
 A preprocessor for @command{pic} that reads descriptions of molecules
@@ -36662,10 +39405,11 @@ It was written in @command{awk}
 by Brian Kernighan and Jon Bentley, and is available from
 @uref{http://netlib.sandia.gov/netlib/typesetting/chem.gz}.
 
+@cindex McIlroy, Doug
 @cindex cookie
 @item Cookie
 A peculiar goodie, token, saying or remembrance
-produced by or presented to a program. (With thanks to Doug McIlroy.)
+produced by or presented to a program. (With thanks to Professor Doug McIlroy.)
 @ignore
 From: Doug McIlroy <doug@cs.dartmouth.edu>
 Date: Sat, 13 Oct 2012 19:55:25 -0400
@@ -36743,9 +39487,7 @@ statements, and in patterns to select which input records to process.
 (@xref{Typing and Comparison}.)
 
 @item Curly Braces
-The characters @samp{@{} and @samp{@}}.  Curly braces are used in
-@command{awk} for delimiting actions, compound statements, and function
-bodies.
+See ``Braces.''
 
 @cindex dark corner
 @item Dark Corner
@@ -36790,7 +39532,7 @@ ordinary expression.  It could be a string constant, such as
 (@xref{Computed Regexps}.)
 
 @item Environment
-A collection of strings, of the form @var{name@code{=}val}, that each
+A collection of strings, of the form @samp{@var{name}=@var{val}}, that each
 program has available to it. Users generally place values into the
 environment in order to provide information to various programs. Typical
 examples are the environment variables @env{HOME} and @env{PATH}.
@@ -36844,8 +39586,8 @@ this is just a number that can have a fractional part.
 See also ``Double Precision'' and ``Single Precision.''
 
 @item Format
-Format strings are used to control the appearance of output in the
-@code{strftime()} and @code{sprintf()} functions, and are used in the
+Format strings control the appearance of output in the
+@code{strftime()} and @code{sprintf()} functions, and in the
 @code{printf} statement as well.  Also, data conversions from numbers to strings
 are controlled by the format strings contained in the built-in variables
 @code{CONVFMT} and @code{OFMT}. (@xref{Control Letters}.)
@@ -36914,7 +39656,7 @@ Base 16 notation, where the digits are @code{0}--@code{9} and
 @code{A}--@code{F}, with @samp{A}
 representing 10, @samp{B} representing 11, and so on, up to @samp{F} for 15.
 Hexadecimal numbers are written in C using a leading @samp{0x},
-to indicate their base.  Thus, @code{0x12} is 18 (1 times 16 plus 2).
+to indicate their base.  Thus, @code{0x12} is 18 ((1 x 16) + 2).
 @xref{Nondecimal-numbers}.
 
 @item I/O
@@ -36959,7 +39701,7 @@ information about the name of the organization and its language-independent
 three-letter acronym.
 
 @cindex Java programming language
-@cindex Programming languages, Java
+@cindex programming languages, Java
 @item Java
 A modern programming language originally developed by Sun Microsystems
 (now Oracle) supporting Object-Oriented programming.  Although usually
@@ -36988,8 +39730,8 @@ meaning.  Keywords are reserved and may not be used as variable names.
 @code{function},
 @code{func},
 @code{if},
-@code{nextfile},
 @code{next},
+@code{nextfile},
 @code{switch},
 and
 @code{while}.
@@ -37050,13 +39792,9 @@ Ancient @command{awk} implementations used single precision floating-point.
 @item Octal
 Base-eight notation, where the digits are @code{0}--@code{7}.
 Octal numbers are written in C using a leading @samp{0},
-to indicate their base.  Thus, @code{013} is 11 (one times 8 plus 3).
+to indicate their base.  Thus, @code{013} is 11 ((1 x 8) + 3).
 @xref{Nondecimal-numbers}.
 
-@cindex P1003.1 POSIX standard
-@item P1003.1
-See ``POSIX.''
-
 @item Pattern
 Patterns tell @command{awk} which input records are interesting to which
 rules.
@@ -37097,8 +39835,8 @@ specify single lines. (@xref{Pattern Overview}.)
 
 @item Recursion
 When a function calls itself, either directly or indirectly.
-As long as this is not clear, refer to the entry for ``recursion.''
 If this is clear, stop, and proceed to the next entry.
+Otherwise, refer to the entry for ``recursion.''
 
 @item Redirection
 Redirection means performing input from something other than the standard input
@@ -37177,14 +39915,14 @@ expressions, and function calls have side effects.
 An internal representation of numbers that can have fractional parts.
 Single precision numbers keep track of fewer digits than do double precision
 numbers, but operations on them are sometimes less expensive in terms of CPU time.
-This is the type used by some very old versions of @command{awk} to store
+This is the type used by some ancient versions of @command{awk} to store
 numeric values.  It is the C type @code{float}.
 
 @item Space
 The character generated by hitting the space bar on the keyboard.
 
 @item Special File
-A file name interpreted internally by @command{gawk}, instead of being handed
+A @value{FN} interpreted internally by @command{gawk}, instead of being handed
 directly to the underlying operating system---for example, @file{/dev/stderr}.
 (@xref{Special Files}.)
 
@@ -37214,7 +39952,7 @@ into the local language.
 A value in the ``seconds since the epoch'' format used by Unix
 and POSIX systems.  Used for the @command{gawk} functions
 @code{mktime()}, @code{strftime()}, and @code{systime()}.
-See also ``Epoch'' and ``UTC.''
+See also ``Epoch,'' ``GMT,'' and ``UTC.''
 
 @cindex Linux
 @cindex GNU/Linux
@@ -37246,7 +39984,12 @@ record or a string.
 @c The GNU General Public License.
 @node Copying
 @unnumbered GNU General Public License
+@ifnotdocbook
 @center Version 3, 29 June 2007
+@end ifnotdocbook
+@docbook
+<subtitle>Version 3, 29 June 2007</subtitle>
+@end docbook
 
 @c This file is intended to be included within another document,
 @c hence no sectioning command or @node.  
@@ -37971,10 +40714,17 @@ first, please read @url{http://www.gnu.org/philosophy/why-not-lgpl.html}.
 @c The GNU Free Documentation License.
 @node GNU Free Documentation License
 @unnumbered GNU Free Documentation License
+@ifnotdocbook
+@center Version 1.3, 3 November 2008
+@end ifnotdocbook
+
+@docbook
+<subtitle>Version 1.3, 3 November 2008</subtitle>
+@end docbook
+
 @cindex FDL (Free Documentation License)
 @cindex Free Documentation License (FDL)
 @cindex GNU Free Documentation License
-@center Version 1.3, 3 November 2008
 
 @c This file is intended to be included within another document,
 @c hence no sectioning command or @node.
@@ -38475,12 +41225,12 @@ recommend releasing these examples in parallel under your choice of
 free software license, such as the GNU General Public License,
 to permit their use in free software.
 
-@c Local Variables:
-@c ispell-local-pdict: "ispell-dict"
-@c End:
+@end ifclear
 
+@ifnotdocbook
 @node Index
 @unnumbered Index
+@end ifnotdocbook
 @printindex cp
 
 @bye
@@ -38588,11 +41338,6 @@ ORA uses filename, thus the macro.
 
 Suggestions:
 ------------
-% Next edition:
-%	1. Standardize the error messages from the functions and programs
-%	   in the two sample code chapters.
-%	2. Nuke the BBS stuff and use something that won't be obsolete
-%	3. Turn the advanced notes into sidebars by using @cartouche
 
 Better sidebars can almost sort of be done with:
 
@@ -38625,3 +41370,5 @@ But to use it you have to say
 
 which sorta sucks.
 
+TODO:
+-----
diff --git a/doc/gawkinet.info b/doc/gawkinet.info
index c8ce6b8d..0a0d69d8 100644
--- a/doc/gawkinet.info
+++ b/doc/gawkinet.info
@@ -613,7 +613,7 @@ tcp, udp    x           0           x           Invalid
 tcp, udp    0           0           0           Invalid
 tcp, udp    0           x           0           Invalid
 
-Table    2.1: /inet Special File Components
+Table 2.1: /inet Special File Components
 
    In general, TCP is the preferred mechanism to use.  It is the
 simplest protocol to understand and to use.  Use UDP only if
@@ -4358,40 +4358,40 @@ Node: Using Networking17966
 Node: Gawk Special Files20284
 Node: Special File Fields22094
 Ref: table-inet-components25967
-Node: Comparing Protocols27290
-Node: File /inet/tcp27823
-Node: File /inet/udp28849
-Node: TCP Connecting29947
-Node: Troubleshooting32285
-Ref: Troubleshooting-Footnote-135337
-Node: Interacting35906
-Node: Setting Up38636
-Node: Email42130
-Node: Web page44456
-Ref: Web page-Footnote-147261
-Node: Primitive Service47458
-Node: Interacting Service50192
-Ref: Interacting Service-Footnote-159321
-Node: CGI Lib59353
-Node: Simple Server66314
-Ref: Simple Server-Footnote-174037
-Node: Caveats74138
-Node: Challenges75281
-Node: Some Applications and Techniques83960
-Node: PANIC86417
-Node: GETURL88135
-Node: REMCONF90758
-Node: URLCHK96234
-Node: WEBGRAB100069
-Node: STATIST104519
-Ref: STATIST-Footnote-1116227
-Node: MAZE116672
-Node: MOBAGWHO122856
-Ref: MOBAGWHO-Footnote-1136800
-Node: STOXPRED136855
-Node: PROTBASE151110
-Node: Links164191
-Node: GNU Free Documentation License167625
-Node: Index192764
+Node: Comparing Protocols27287
+Node: File /inet/tcp27820
+Node: File /inet/udp28846
+Node: TCP Connecting29944
+Node: Troubleshooting32282
+Ref: Troubleshooting-Footnote-135334
+Node: Interacting35903
+Node: Setting Up38633
+Node: Email42127
+Node: Web page44453
+Ref: Web page-Footnote-147258
+Node: Primitive Service47455
+Node: Interacting Service50189
+Ref: Interacting Service-Footnote-159318
+Node: CGI Lib59350
+Node: Simple Server66311
+Ref: Simple Server-Footnote-174034
+Node: Caveats74135
+Node: Challenges75278
+Node: Some Applications and Techniques83957
+Node: PANIC86414
+Node: GETURL88132
+Node: REMCONF90755
+Node: URLCHK96231
+Node: WEBGRAB100066
+Node: STATIST104516
+Ref: STATIST-Footnote-1116224
+Node: MAZE116669
+Node: MOBAGWHO122853
+Ref: MOBAGWHO-Footnote-1136797
+Node: STOXPRED136852
+Node: PROTBASE151107
+Node: Links164188
+Node: GNU Free Documentation License167622
+Node: Index192761
 
 End Tag Table
diff --git a/doc/gawkinet.texi b/doc/gawkinet.texi
index eb0f2d81..40198e1d 100644
--- a/doc/gawkinet.texi
+++ b/doc/gawkinet.texi
@@ -597,7 +597,7 @@ is started, @command{gawk} creates the appropriate network
 connection, and then two-way I/O proceeds as usual.
 
 @c last comma is part of see-also
-@cindex input/output, two-way, See Also @command{gawk}, networking
+@cindex input/output, two-way, See Also @command{gawk}@comma{} networking
 @cindex TCP/IP, sockets and
 At the C, C++, and Perl level, networking is accomplished
 via @dfn{sockets}, an Application Programming Interface (API) originally
@@ -1144,9 +1144,9 @@ or the application cannot tolerate virtual circuit overhead.
 @node Setting Up, Email, Interacting, Using Networking
 @section Setting Up a Service
 @c last comma is part of tertiary
-@cindex networks, @command{gawk} and, service, establishing
+@cindex networks, @command{gawk} and, service@comma{} establishing
 @c last comma is part of tertiary
-@cindex @command{gawk}, networking, service, establishing
+@cindex @command{gawk}, networking, service@comma{} establishing
 The preceding programs behaved as clients that connect to a server somewhere
 on the Internet and request a particular service. Now we set up such a
 service to mimic the behavior of the @samp{daytime} service.
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index aac8c2af..00d544b4 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -14,6 +14,31 @@
 * awk: (gawk)Invoking gawk.                     Text scanning and processing.
 @end direntry
 
+@ifset FOR_PRINT
+@tex
+\gdef\xrefprintnodename#1{``#1''}
+@end tex
+@end ifset
+
+@ifclear FOR_PRINT
+@c With early 2014 texinfo.tex, restore PDF links and colors
+@tex
+\gdef\linkcolor{0.5 0.09 0.12} % Dark Red
+\gdef\urlcolor{0.5 0.09 0.12} % Also
+\global\urefurlonlylinktrue
+@end tex
+@end ifclear
+
+@ifnotdocbook
+@set BULLET @bullet{}
+@set MINUS @minus{}
+@end ifnotdocbook
+
+@ifdocbook
+@set BULLET
+@set MINUS
+@end ifdocbook
+
 @set xref-automatic-section-title
 
 @c The following information should be updated here only!
@@ -21,11 +46,9 @@
 @c applies to and all the info about who's publishing this edition
 
 @c These apply across the board.
-@set UPDATE-MONTH May, 2013
+@set UPDATE-MONTH June, 2014
 @set VERSION 4.1
-@set PATCHLEVEL 0
-
-@set FSF
+@set PATCHLEVEL 1
 
 @set TITLE GAWK: Effective AWK Programming
 @set SUBTITLE A User's Guide for GNU Awk
@@ -39,6 +62,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER @inmargin{@image{lflashlight,1cm}, @image{rflashlight,1cm}}
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end iftex
 @ifinfo
 @set DOCUMENT Info file
@@ -48,6 +72,7 @@
 @set SUBSECTION node
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE screen
 @end ifinfo
 @ifhtml
 @set DOCUMENT Web page
@@ -57,6 +82,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE screen
 @end ifhtml
 @ifdocbook
 @set DOCUMENT book
@@ -66,6 +92,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end ifdocbook
 @ifxml
 @set DOCUMENT book
@@ -75,6 +102,7 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end ifxml
 @ifplaintext
 @set DOCUMENT book
@@ -84,24 +112,69 @@
 @set SUBSECTION subsection
 @set DARKCORNER (d.c.)
 @set COMMONEXT (c.e.)
+@set PAGE page
 @end ifplaintext
 
+@ifdocbook
+@c empty on purpose
+@set PART1
+@set PART2
+@set PART3
+@set PART4
+@end ifdocbook
+
+@ifnotdocbook
+@set PART1 Part I:@*
+@set PART2 Part II:@*
+@set PART3 Part III:@*
+@set PART4 Part IV:@*
+@end ifnotdocbook
+
 @c some special symbols
 @iftex
 @set LEQ @math{@leq}
 @set PI @math{@pi}
 @end iftex
+@ifdocbook
+@set LEQ @inlineraw{docbook, &le;}
+@set PI @inlineraw{docbook, &pgr;}
+@end ifdocbook
 @ifnottex
+@ifnotdocbook
 @set LEQ <=
 @set PI @i{pi}
+@end ifnotdocbook
 @end ifnottex
 
 @ifnottex
+@ifnotdocbook
 @macro ii{text}
 @i{\text\}
 @end macro
+@end ifnotdocbook
 @end ifnottex
 
+@ifdocbook
+@macro ii{text}
+@inlineraw{docbook,<lineannotation>\text\</lineannotation>}
+@end macro
+@end ifdocbook
+
+@ifclear FOR_PRINT
+@set FN file name
+@set FFN File Name
+@set DF data file
+@set DDF Data File
+@set PVERSION version
+@end ifclear
+@ifset FOR_PRINT
+@set FN filename
+@set FFN Filename
+@set DF datafile
+@set DDF Datafile
+@set PVERSION Version
+@end ifset
+
 @c For HTML, spell out email addresses, to avoid problems with
 @c address harvesters for spammers.
 @ifhtml
@@ -115,12 +188,36 @@
 @end macro
 @end ifnothtml
 
+@c Indexing macros
+@ifinfo
+
+@macro cindexawkfunc{name}
+@cindex @code{\name\}
+@end macro
+
+@macro cindexgawkfunc{name}
+@cindex @code{\name\}
+@end macro
+
+@end ifinfo
+
+@ifnotinfo
+
+@macro cindexawkfunc{name}
+@cindex @code{\name\()} function
+@end macro
+
+@macro cindexgawkfunc{name}
+@cindex @code{\name\()} function (@command{gawk})
+@end macro
+@end ifnotinfo
+
 @ignore
 Some comments on the layout for TeX.
-1. Use at least texinfo.tex 2000-09-06.09
-2. I have done A LOT of work to make this look good. There are  `@page' commands
-   and use of `@group ... @end group' in a number of places. If you muck
-   with anything, it's your responsibility not to break the layout.
+1. Use at least texinfo.tex 2014-01-30.15
+2. When using @docbook, if the last line is part of a paragraph, end
+it with a space and @c so that the lines won't run together. This is a
+quirk of the language / makeinfo, and isn't going to change.
 @end ignore
 
 @c merge the function and variable indexes into the concept index
@@ -136,6 +233,10 @@ Some comments on the layout for TeX.
 @syncodeindex fn cp
 @syncodeindex vr cp
 @end ifxml
+@ifdocbook
+@synindex fn cp
+@synindex vr cp
+@end ifdocbook
 
 @c If "finalout" is commented out, the printed output will show
 @c black boxes that mark lines that are too long.  Thus, it is
@@ -147,9 +248,30 @@ Some comments on the layout for TeX.
 @end iftex
 
 @copying
-Copyright @copyright{} 1989, 1991, 1992, 1993, 1996, 1997, 1998, 1999,
-2000, 2001, 2002, 2003, 2004, 2005, 2007, 2009, 2010, 2011, 2012, 2013
+@docbook
+<para>
+&ldquo;To boldly go where no man has gone before&rdquo; is a
+Registered Trademark of Paramount Pictures Corporation.</para>
+
+<para>Published by:</para>
+
+<literallayout class="normal">Free Software Foundation
+51 Franklin Street, Fifth Floor
+Boston, MA  02110-1301 USA
+Phone: +1-617-542-5942
+Fax: +1-617-542-2652
+Email: <email>gnu@@gnu.org</email>
+URL: <ulink url="http://www.gnu.org">http://www.gnu.org/</ulink></literallayout>
+
+<literallayout class="normal">Copyright &copy; 1989, 1991, 1992, 1993, 1996&ndash;2005, 2007, 2009&ndash;2014
+Free Software Foundation, Inc.
+All Rights Reserved.</literallayout>
+@end docbook
+
+@ifnotdocbook
+Copyright @copyright{} 1989, 1991, 1992, 1993, 1996--2005, 2007, 2009--2014 @*
 Free Software Foundation, Inc.
+@end ifnotdocbook
 @sp 2
 
 This is Edition @value{EDITION} of @cite{@value{TITLE}: @value{SUBTITLE}},
@@ -197,6 +319,7 @@ supports it in developing GNU and promoting software freedom.''
 @subtitle @value{UPDATE-MONTH}
 @author Arnold D. Robbins
 
+@ifnotdocbook
 @c Include the Distribution inside the titlepage environment so
 @c that headings are turned off.  Headings on and off do not work.
 
@@ -221,6 +344,7 @@ URL: @uref{http://www.gnu.org/} @*
 ISBN 1-882114-28-0 @*
 @sp 2
 @insertcopying
+@end ifnotdocbook
 @end titlepage
 
 @c Thanks to Bob Chassell for directions on doing dedications.
@@ -229,15 +353,13 @@ ISBN 1-882114-28-0 @*
 @page
 @w{ }
 @sp 9
-@center @i{To Miriam, for making me complete.}
-@sp 1
-@center @i{To Chana, for the joy you bring us.}
+@center @i{To my parents, for their love, and for the wonderful example they set for me.}
 @sp 1
-@center @i{To Rivka, for the exponential increase.}
+@center @i{To my wife Miriam, for making me complete.
+Thank you for building your life together with me.}
 @sp 1
-@center @i{To Nachum, for the added dimension.}
+@center @i{To our children Chana, Rivka, Nachum and Malka, for enrichening our lives in innumerable ways.}
 @sp 1
-@center @i{To Malka, for the new beginning.}
 @w{ }
 @page
 @w{ }
@@ -245,6 +367,17 @@ ISBN 1-882114-28-0 @*
 @headings on
 @end iftex
 
+@docbook
+<dedication>
+<para>To my parents, for their love, and for the wonderful
+example they set for me.</para>
+<para>To my wife Miriam, for making me complete.
+Thank you for building your life together with me.</para>
+<para>To our children Chana, Rivka, Nachum and Malka,
+for enrichening our lives in innumerable ways.</para>
+</dedication>
+@end docbook
+
 @iftex
 @headings off
 @evenheading @thispage@ @ @ @strong{@value{TITLE}} @| @|
@@ -253,6 +386,7 @@ ISBN 1-882114-28-0 @*
 
 @ifnottex
 @ifnotxml
+@ifnotdocbook
 @node Top
 @top General Introduction
 @c Preface node should come right after the Top
@@ -264,6 +398,7 @@ particular records in a file and perform operations upon them.
 
 @insertcopying
 
+@end ifnotdocbook
 @end ifnotxml
 @end ifnottex
 
@@ -331,8 +466,8 @@ particular records in a file and perform operations upon them.
                                         includes command-line syntax.
 * One-shot::                            Running a short throwaway
                                         @command{awk} program.
-* Read Terminal::                       Using no input files (input from
-                                        terminal instead).
+* Read Terminal::                       Using no input files (input from the
+                                        keyboard instead).
 * Long::                                Putting permanent @command{awk}
                                         programs in files.
 * Executable Scripts::                  Making self-contained @command{awk}
@@ -354,6 +489,7 @@ particular records in a file and perform operations upon them.
 * Other Features::                      Other Features of @command{awk}.
 * When::                                When to use @command{gawk} and when to
                                         use other things.
+* Intro Summary::                       Summary of the introduction.
 * Command Line::                        How to run @command{awk}.
 * Options::                             Command-line options and their
                                         meanings.
@@ -375,6 +511,7 @@ particular records in a file and perform operations upon them.
                                         program.
 * Obsolete::                            Obsolete Options and/or features.
 * Undocumented::                        Undocumented Options and Features.
+* Invoking Summary::                    Invocation summary.
 * Regexp Usage::                        How to Use Regular Expressions.
 * Escape Sequences::                    How to write nonprinting characters.
 * Regexp Operators::                    Regular Expression Operators.
@@ -383,8 +520,12 @@ particular records in a file and perform operations upon them.
 * Case-sensitivity::                    How to do case-insensitive matching.
 * Leftmost Longest::                    How much text matches.
 * Computed Regexps::                    Using Dynamic Regexps.
+* Regexp Summary::                      Regular expressions summary.
 * Records::                             Controlling how data is split into
                                         records.
+* awk split records::                   How standard @command{awk} splits
+                                        records.
+* gawk split records::                  How @command{gawk} splits records.
 * Fields::                              An introduction to fields.
 * Nonconstant Fields::                  Nonconstant Field Numbers.
 * Changing Fields::                     Changing the Contents of a Field.
@@ -396,6 +537,8 @@ particular records in a file and perform operations upon them.
                                         field.
 * Command Line Field Separator::        Setting @code{FS} from the
                                         command-line.
+* Full Line Fields::                    Making the full line be a single
+                                        field.
 * Field Splitting Summary::             Some final points and a summary table.
 * Constant Size::                       Reading constant width data.
 * Splitting By Content::                Defining Fields By Content
@@ -421,6 +564,8 @@ particular records in a file and perform operations upon them.
 * Read Timeout::                        Reading input with a timeout.
 * Command line directories::            What happens if you put a directory on
                                         the command line.
+* Input Summary::                       Input summary.
+* Input Exercises::                     Exercises.
 * Print::                               The @code{print} statement.
 * Print Examples::                      Simple examples of @code{print}
                                         statements.
@@ -444,6 +589,8 @@ particular records in a file and perform operations upon them.
 * Special Caveats::                     Things to watch out for.
 * Close Files And Pipes::               Closing Input and Output Files and
                                         Pipes.
+* Output Summary::                      Output summary.
+* Output exercises::                    Exercises.
 * Values::                              Constants, Variables, and Regular
                                         Expressions.
 * Constants::                           String, numeric and regexp constants.
@@ -459,6 +606,9 @@ particular records in a file and perform operations upon them.
                                         This is an advanced method of input.
 * Conversion::                          The conversion of strings to numbers
                                         and vice versa.
+* Strings And Numbers::                 How @command{awk} Converts Between
+                                        Strings And Numbers.
+* Locale influences conversions::       How the locale may affect conversions.
 * All Operators::                       @command{gawk}'s operators.
 * Arithmetic Ops::                      Arithmetic operations (@samp{+},
                                         @samp{-}, etc.)
@@ -486,6 +636,7 @@ particular records in a file and perform operations upon them.
 * Function Calls::                      A function call is an expression.
 * Precedence::                          How various operators nest.
 * Locales::                             How the locale affects things.
+* Expressions Summary::                 Expressions summary.
 * Pattern Overview::                    What goes into a pattern.
 * Regexp Patterns::                     Using regexps as patterns.
 * Expression Patterns::                 Any expression can be used as a
@@ -532,6 +683,7 @@ particular records in a file and perform operations upon them.
                                         gives you information.
 * ARGC and ARGV::                       Ways to use @code{ARGC} and
                                         @code{ARGV}.
+* Pattern Action Summary::              Patterns and Actions summary.
 * Array Basics::                        The basics of arrays.
 * Array Intro::                         Introduction to Arrays
 * Reference to Elements::               How to examine one element of an
@@ -554,6 +706,7 @@ particular records in a file and perform operations upon them.
                                         @command{awk}.
 * Multiscanning::                       Scanning multidimensional arrays.
 * Arrays of Arrays::                    True multidimensional arrays.
+* Arrays Summary::                      Summary of arrays.
 * Built-in::                            Summarizes the built-in functions.
 * Calling Built-in::                    How to call built-in functions.
 * Numeric Functions::                   Functions that work with numbers,
@@ -588,6 +741,7 @@ particular records in a file and perform operations upon them.
                                         runtime.
 * Indirect Calls::                      Choosing the function to call at
                                         runtime.
+* Functions Summary::                   Summary of functions.
 * Library Names::                       How to best name private global
                                         variables in library functions.
 * General Functions::                   Functions that are of general use.
@@ -622,6 +776,8 @@ particular records in a file and perform operations upon them.
 * Group Functions::                     Functions for getting group
                                         information.
 * Walking Arrays::                      A function to walk arrays of arrays.
+* Library Functions Summary::           Summary of library functions.
+* Library exercises::                   Exercises.
 * Running Examples::                    How to run these examples.
 * Clones::                              Clones of common utilities.
 * Cut Program::                         The @command{cut} utility.
@@ -651,6 +807,8 @@ particular records in a file and perform operations upon them.
 * Anagram Program::                     Finding anagrams from a dictionary.
 * Signature Program::                   People do amazing things with too much
                                         time on their hands.
+* Programs Summary::                    Summary of programs.
+* Programs Exercises::                  Exercises.
 * Nondecimal Data::                     Allowing nondecimal input data.
 * Array Sorting::                       Facilities for controlling array
                                         traversal and sorting arrays.
@@ -662,8 +820,9 @@ particular records in a file and perform operations upon them.
 * TCP/IP Networking::                   Using @command{gawk} for network
                                         programming.
 * Profiling::                           Profiling your @command{awk} programs.
+* Advanced Features Summary::           Summary of advanced features.
 * I18N and L10N::                       Internationalization and Localization.
-* Explaining gettext::                  How GNU @code{gettext} works.
+* Explaining gettext::                  How GNU @command{gettext} works.
 * Programmer i18n::                     Features for the programmer.
 * Translator i18n::                     Features for the translator.
 * String Extraction::                   Extracting marked strings.
@@ -673,6 +832,7 @@ particular records in a file and perform operations upon them.
 * I18N Example::                        A simple i18n example.
 * Gawk I18N::                           @command{gawk} is also
                                         internationalized.
+* I18N Summary::                        Summary of I18N stuff.
 * Debugging::                           Introduction to @command{gawk}
                                         debugger.
 * Debugging Concepts::                  Debugging in General.
@@ -691,31 +851,23 @@ particular records in a file and perform operations upon them.
 * Miscellaneous Debugger Commands::     Miscellaneous Commands.
 * Readline Support::                    Readline support.
 * Limitations::                         Limitations and future plans.
-* General Arithmetic::                  An introduction to computer
-                                        arithmetic.
-* Floating Point Issues::               Stuff to know about floating-point
-                                        numbers.
-* String Conversion Precision::         The String Value Can Lie.
-* Unexpected Results::                  Floating Point Numbers Are Not
-                                        Abstract Numbers.
-* POSIX Floating Point Problems::       Standards Versus Existing Practice.
-* Integer Programming::                 Effective integer programming.
-* Floating-point Programming::          Effective Floating-point Programming.
-* Floating-point Representation::       Binary floating-point representation.
-* Floating-point Context::              Floating-point context.
-* Rounding Mode::                       Floating-point rounding mode.
-* Gawk and MPFR::                       How @command{gawk} provides
-                                        arbitrary-precision arithmetic.
-* Arbitrary Precision Floats::          Arbitrary Precision Floating-point
-                                        Arithmetic with @command{gawk}.
-* Setting Precision::                   Setting the working precision.
-* Setting Rounding Mode::               Setting the rounding mode.
-* Floating-point Constants::            Representing floating-point constants.
-* Changing Precision::                  Changing the precision of a number.
-* Exact Arithmetic::                    Exact arithmetic with floating-point
-                                        numbers.
+* Debugging Summary::                   Debugging summary.
+* Computer Arithmetic::                 A quick intro to computer math.
+* Math Definitions::                    Defining terms used.
+* MPFR features::                       The MPFR features in @command{gawk}.
+* FP Math Caution::                     Things to know.
+* Inexactness of computations::         Floating point math is not exact.
+* Inexact representation::              Numbers are not exactly represented.
+* Comparing FP Values::                 How to compare floating point values.
+* Errors accumulate::                   Errors get bigger as they go.
+* Getting Accuracy::                    Getting more accuracy takes some work.
+* Try To Round::                        Add digits and round.
+* Setting precision::                   How to set the precision.
+* Setting the rounding mode::           How to set the rounding mode.
 * Arbitrary Precision Integers::        Arbitrary Precision Integer Arithmetic
                                         with @command{gawk}.
+* POSIX Floating Point Problems::       Standards Versus Existing Practice.
+* Floating point summary::              Summary of floating point discussion.
 * Extension Intro::                     What is an extension.
 * Plugin License::                      A note about licensing.
 * Extension Mechanism Outline::         An outline of how it works.
@@ -723,6 +875,7 @@ particular records in a file and perform operations upon them.
 * Extension API Functions Introduction:: Introduction to the API functions.
 * General Data Types::                  The data types.
 * Requesting Values::                   How to get a value.
+* Memory Allocation Functions::         Functions for allocating memory.
 * Constructor Functions::               Functions for creating values.
 * Registration Functions::              Functions to register things with
                                         @command{gawk}.
@@ -776,6 +929,8 @@ particular records in a file and perform operations upon them.
 * Extension Sample Time::               An interface to @code{gettimeofday()}
                                         and @code{sleep()}.
 * gawkextlib::                          The @code{gawkextlib} project.
+* Extension summary::                   Extension summary.
+* Extension Exercises::                 Exercises.
 * V7/SVR3.1::                           The major changes between V7 and
                                         System V Release 3.1.
 * SVR4::                                Minor changes between System V
@@ -785,11 +940,14 @@ particular records in a file and perform operations upon them.
                                         version of @command{awk}.
 * POSIX/GNU::                           The extensions in @command{gawk} not
                                         in POSIX @command{awk}.
+* Feature History::                     The history of the features in
+                                        @command{gawk}.
 * Common Extensions::                   Common Extensions Summary.
 * Ranges and Locales::                  How locales used to affect regexp
                                         ranges.
 * Contributors::                        The major contributors to
                                         @command{gawk}.
+* History summary::                     History summary.
 * Gawk Distribution::                   What is in the @command{gawk}
                                         distribution.
 * Getting::                             How to get the distribution.
@@ -817,14 +975,18 @@ particular records in a file and perform operations upon them.
 * VMS Installation::                    Installing @command{gawk} on VMS.
 * VMS Compilation::                     How to compile @command{gawk} under
                                         VMS.
+* VMS Dynamic Extensions::              Compiling @command{gawk} dynamic
+                                        extensions on VMS.
 * VMS Installation Details::            How to install @command{gawk} under
                                         VMS.
 * VMS Running::                         How to run @command{gawk} under VMS.
+* VMS GNV::                             The VMS GNV Project.
 * VMS Old Gawk::                        An old version comes with some VMS
                                         systems.
 * Bugs::                                Reporting Problems and Bugs.
 * Other Versions::                      Other freely available @command{awk}
                                         implementations.
+* Installation summary::                Summary of installation.
 * Compatibility Mode::                  How to disable certain @command{gawk}
                                         extensions.
 * Additions::                           Making Additions To @command{gawk}.
@@ -833,8 +995,8 @@ particular records in a file and perform operations upon them.
                                         @command{gawk}.
 * New Ports::                           Porting @command{gawk} to a new
                                         operating system.
-* Derived Files::                       Why derived files are kept in the
-                                        @command{git} repository.
+* Derived Files::                       Why derived files are kept in the Git
+                                        repository.
 * Future Extensions::                   New features that may be implemented
                                         one day.
 * Implementation Limitations::          Some limitations of the
@@ -845,6 +1007,7 @@ particular records in a file and perform operations upon them.
 * Extension Other Design Decisions::    Some other design decisions.
 * Extension Future Growth::             Some room for future growth.
 * Old Extension Mechanism::             Some compatibility for old extensions.
+* Notes summary::                       Summary of implementation notes.
 * Basic High Level::                    The high level view.
 * Basic Data Typing::                   A very quick intro to data types.
 @end detailmenu
@@ -852,15 +1015,14 @@ particular records in a file and perform operations upon them.
 
 @c dedication for Info file
 @ifinfo
-@center To Miriam, for making me complete.
-@sp 1
-@center To Chana, for the joy you bring us.
+To my parents, for their love, and for the wonderful
+example they set for me.
 @sp 1
-@center To Rivka, for the exponential increase.
+To my wife Miriam, for making me complete.
+Thank you for building your life together with me.
 @sp 1
-@center To Nachum, for the added dimension.
-@sp 1
-@center To Malka, for the new beginning.
+To our children Chana, Rivka, Nachum and Malka,
+for enrichening our lives in innumerable ways.
 @end ifinfo
 
 @summarycontents
@@ -869,6 +1031,21 @@ particular records in a file and perform operations upon them.
 @node Foreword
 @unnumbered Foreword
 
+@c This bit is post-processed by a script which turns the chapter
+@c tag into a preface tag, and moves this stuff to before the title.
+@c Bleah.
+@docbook
+  <prefaceinfo>
+    <author>
+      <firstname>Michael</firstname>
+      <surname>Brennan</surname>
+      <!-- can't put mawk into command tags. sigh. -->
+      <affiliation><jobtitle>Author of mawk</jobtitle></affiliation>
+    </author>
+    <date>March, 2001</date>
+   </prefaceinfo>
+@end docbook
+
 Arnold Robbins and I are good friends. We were introduced
 @c 11 years ago
 in 1990
@@ -953,21 +1130,37 @@ and the AWK prototype becomes the product.
 The new @command{pgawk} (profiling @command{gawk}), produces
 program execution counts.
 I recently experimented with an algorithm that for
-@math{n} lines of input, exhibited
+@ifnotdocbook
+@math{n}
+@end ifnotdocbook
+@ifdocbook
+@i{n}
+@end ifdocbook
+lines of input, exhibited
 @tex
 $\sim\! Cn^2$
 @end tex
 @ifnottex
+@ifnotdocbook
 ~ C n^2
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<emphasis>&sim; Cn<superscript>2</superscript></emphasis> @c
+@end docbook
 performance, while
 theory predicted
 @tex
 $\sim\! Cn\log n$
 @end tex
 @ifnottex
+@ifnotdocbook
 ~ C n log n
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<emphasis>&sim; Cn log n</emphasis> @c
+@end docbook
 behavior. A few minutes poring
 over the @file{awkprof.out} profile pinpointed the problem to
 a single line of code.  @command{pgawk} is a welcome addition to
@@ -977,11 +1170,14 @@ Arnold has distilled over a decade of experience writing and
 using AWK programs, and developing @command{gawk}, into this book.  If you use
 AWK or want to learn how, then read this book.
 
+@ifnotdocbook
+@cindex Brennan, Michael
 @display
 Michael Brennan
 Author of @command{mawk}
 March, 2001
 @end display
+@end ifnotdocbook
 
 @node Preface
 @unnumbered Preface
@@ -990,6 +1186,21 @@ March, 2001
 @c
 @c 12/2000: Chuck wants the preface & intro combined.
 
+@c This bit is post-processed by a script which turns the chapter
+@c tag into a preface tag, and moves this stuff to before the title.
+@c Bleah.
+@docbook
+  <prefaceinfo>
+    <author>
+      <firstname>Arnold</firstname>
+      <surname>Robbins</surname>
+      <affiliation><jobtitle>Nof Ayalon</jobtitle></affiliation>
+      <affiliation><jobtitle>ISRAEL</jobtitle></affiliation>
+    </author>
+    <date>June, 2014</date>
+   </prefaceinfo>
+@end docbook
+
 Several kinds of tasks occur repeatedly
 when working with text files.
 You might want to extract certain lines and discard the rest.
@@ -1001,12 +1212,13 @@ Such jobs are often easier with @command{awk}.
 The @command{awk} utility interprets a special-purpose programming language
 that makes it easy to handle simple data-reformatting jobs.
 
+@cindex Brian Kernighan's @command{awk}
 The GNU implementation of @command{awk} is called @command{gawk}; if you
 invoke it with the proper options or environment variables
 (@pxref{Options}), it is fully
 compatible with
-the POSIX@footnote{The 2008 POSIX standard is online at
-@url{http://www.opengroup.org/onlinepubs/9699919799/}.}
+the POSIX@footnote{The 2008 POSIX standard is accessable online at
+@w{@url{http://www.opengroup.org/onlinepubs/9699919799/}.}}
 specification of the @command{awk} language
 and with the Unix version of @command{awk} maintained
 by Brian Kernighan.
@@ -1023,7 +1235,7 @@ Thus, we usually don't distinguish between @command{gawk} and other
 @cindex @command{awk}, uses for
 Using @command{awk} allows you to:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Manage small, personal databases
 
@@ -1048,7 +1260,7 @@ In addition,
 @command{gawk}
 provides facilities that make it easy to:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Extract bits and pieces of data for processing
 
@@ -1057,6 +1269,12 @@ Sort data
 
 @item
 Perform simple network communications
+
+@item
+Profile and debug @command{awk} programs.
+
+@item
+Extend the language with functions written in C or C++.
 @end itemize
 
 This @value{DOCUMENT} teaches you about the @command{awk} language and
@@ -1072,12 +1290,18 @@ Implementations of the @command{awk} language are available for many
 different computing environments.  This @value{DOCUMENT}, while describing
 the @command{awk} language in general, also describes the particular
 implementation of @command{awk} called @command{gawk} (which stands for
-``GNU awk'').  @command{gawk} runs on a broad range of Unix systems,
+``GNU @command{awk}'').  @command{gawk} runs on a broad range of Unix systems,
 ranging from Intel@registeredsymbol{}-architecture PC-based computers
-up through large-scale systems,
-such as Crays. @command{gawk} has also been ported to Mac OS X,
-Microsoft Windows (all versions) and OS/2 PCs,
-and VMS.
+up through large-scale systems.
+@command{gawk} has also been ported to Mac OS X,
+Microsoft Windows
+@ifset FOR_PRINT
+(all versions),
+@end ifset
+@ifclear FOR_PRINT
+(all versions) and OS/2 PCs,
+@end ifclear
+and OpenVMS.
 (Some other, obsolete systems to which @command{gawk} was once ported
 are no longer supported and the code for those systems
 has been removed.)
@@ -1151,11 +1375,11 @@ wrote the bulk of
 @cite{TCP/IP Internetworking with @command{gawk}}
 (a separate document, available as part of the @command{gawk} distribution).
 His code finally became part of the main @command{gawk} distribution
-with @command{gawk} version 3.1.
+with @command{gawk} @value{PVERSION} 3.1.
 
 John Haque rewrote the @command{gawk} internals, in the process providing
 an @command{awk}-level debugger. This version became available as
-@command{gawk} version 4.0, in 2011.
+@command{gawk} @value{PVERSION} 4.0, in 2011.
 
 @xref{Contributors},
 for a complete list of those who made important contributions to @command{gawk}.
@@ -1170,26 +1394,26 @@ The language described in this @value{DOCUMENT}
 is often referred to as ``new @command{awk}'' (@command{nawk}).
 
 @cindex @command{awk}, versions of
-Because of this, there are systems with multiple
-versions of @command{awk}.
-Some systems have an @command{awk} utility that implements the
-original version of the @command{awk} language and a @command{nawk} utility
-for the new version.
-Others have an @command{oawk} version for the ``old @command{awk}''
-language and plain @command{awk} for the new one.  Still others only
-have one version, which is usually the new one.@footnote{Often, these systems
-use @command{gawk} for their @command{awk} implementation!}
-
 @cindex @command{nawk} utility
 @cindex @command{oawk} utility
-All in all, this makes it difficult for you to know which version of
-@command{awk} you should run when writing your programs.  The best advice
-we can give here is to check your local documentation. Look for @command{awk},
-@command{oawk}, and @command{nawk}, as well as for @command{gawk}.
-It is likely that you already
-have some version of new @command{awk} on your system, which is what
-you should use when running your programs.  (Of course, if you're reading
-this @value{DOCUMENT}, chances are good that you have @command{gawk}!)
+For some time after new @command{awk} was introduced, there were
+systems with multiple versions of @command{awk}.  Some systems had
+an @command{awk} utility that implemented the original version of the
+@command{awk} language and a @command{nawk} utility for the new version.
+Others had an @command{oawk} version for the ``old @command{awk}''
+language and plain @command{awk} for the new one.  Still others only
+had one version, which is usually the new one.
+
+Today, only Solaris systems still use an old @command{awk} for the
+default @command{awk} utility. (A more modern @command{awk} lives in
+@file{/usr/xpg6/bin} on these systems.)  All other modern systems use
+some version of new @command{awk}.@footnote{Many of these systems use
+@command{gawk} for their @command{awk} implementation!}
+
+It is likely that you already have some version of new @command{awk} on
+your system, which is what you should use when running your programs.
+(Of course, if you're reading this @value{DOCUMENT}, chances are good
+that you have @command{gawk}!)
 
 Throughout this @value{DOCUMENT}, whenever we refer to a language feature
 that should be available in any complete implementation of POSIX @command{awk},
@@ -1207,7 +1431,7 @@ and the program ``the @command{awk} utility.''
 This @value{DOCUMENT} explains
 both how to write programs in the @command{awk} language and how to
 run the @command{awk} utility.
-The term @dfn{@command{awk} program} refers to a program written by you in
+The term ``@command{awk} program'' refers to a program written by you in
 the @command{awk} programming language.
 
 @cindex @command{gawk}, @command{awk} and
@@ -1217,9 +1441,15 @@ Primarily, this @value{DOCUMENT} explains the features of @command{awk}
 as defined in the POSIX standard.  It does so in the context of the
 @command{gawk} implementation.  While doing so, it also
 attempts to describe important differences between @command{gawk}
-and other @command{awk} implementations.@footnote{All such differences
+and other @command{awk}
+@ifclear FOR_PRINT
+implementations.@footnote{All such differences
 appear in the index under the
 entry ``differences in @command{awk} and @command{gawk}.''}
+@end ifclear
+@ifset FOR_PRINT
+implementations.
+@end ifset
 Finally, any @command{gawk} features that are not in
 the POSIX standard for @command{awk} are noted.
 
@@ -1227,7 +1457,7 @@ the POSIX standard for @command{awk} are noted.
 This @value{DOCUMENT} has the difficult task of being both a tutorial and a reference.
 If you are a novice, feel free to skip over details that seem too complex.
 You should also ignore the many cross-references; they are for the
-expert user and for the online Info and HTML versions of the document.
+expert user and for the online Info and HTML versions of the @value{DOCUMENT}.
 @end ifnotinfo
 
 There are sidebars
@@ -1251,6 +1481,8 @@ should be of interest.
 
 This @value{DOCUMENT} is split into several parts, as follows:
 
+@c FULLXREF ON
+
 Part I describes the @command{awk} language and @command{gawk} program in detail.
 It starts with the basics, and continues through all of the features of @command{awk}.
 It contains the following chapters:
@@ -1334,9 +1566,14 @@ describes advanced arithmetic facilities provided by
 @ref{Dynamic Extensions}, describes how to add new variables and
 functions to @command{gawk} by writing extensions in C or C++.
 
+@ifclear FOR_PRINT
 Part IV provides the appendices, the Glossary, and two licenses that cover
 the @command{gawk} source code and this @value{DOCUMENT}, respectively.
 It contains the following appendices:
+@end ifclear
+@ifset FOR_PRINT
+Part IV provides the following appendices:
+@end ifset
 
 @ref{Language History},
 describes how the @command{awk} language has evolved since
@@ -1351,6 +1588,36 @@ non-POSIX systems.  It also describes how to report bugs
 in @command{gawk} and where to get other freely
 available @command{awk} implementations.
 
+@ifset FOR_PRINT
+The version of this @value{DOCUMENT} distributed with @command{gawk}
+contains additional appendices and other end material.
+To save space, we have omitted them from the
+printed edition. You may find them online, as follows:
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Notes.html,
+The appendix on implementation notes}
+describes how to disable @command{gawk}'s extensions, as
+well as how to contribute new code to @command{gawk},
+and some possible future directions for @command{gawk} development.
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Basic-Concepts.html,
+The appendix on basic concepts}
+provides some very cursory background material for those who
+are completely unfamiliar with computer programming.
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Glossary.html,
+The Glossary}
+defines most, if not all, the significant terms used
+throughout the @value{DOCUMENT}.  If you find terms that you aren't familiar with,
+try looking them up here.
+
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Copying.html, The GNU GPL} and
+@uref{http://www.gnu.org/software/gawk/manual/html_node/GNU-Free-Documentation-License.html, the GNU FDL}
+are the licenses that cover the @command{gawk} source code
+and this @value{DOCUMENT}, respectively.
+@end ifset
+
+@ifclear FOR_PRINT
 @ref{Notes},
 describes how to disable @command{gawk}'s extensions, as
 well as how to contribute new code to @command{gawk},
@@ -1361,13 +1628,16 @@ provides some very cursory background material for those who
 are completely unfamiliar with computer programming.
 
 The @ref{Glossary}, defines most, if not all, the significant terms used
-throughout the book.  If you find terms that you aren't familiar with,
+throughout the @value{DOCUMENT}.  If you find terms that you aren't familiar with,
 try looking them up here.
 
 @ref{Copying}, and
 @ref{GNU Free Documentation License},
 present the licenses that cover the @command{gawk} source code
 and this @value{DOCUMENT}, respectively.
+@end ifclear
+
+@c FULLXREF OFF
 
 @node Conventions
 @unnumberedsec Typographical Conventions
@@ -1409,7 +1679,7 @@ emphasized @emph{like this}, and if a point needs to be made
 strongly, it is done @strong{like this}.  The first occurrence of
 a new term is usually its @dfn{definition} and appears in the same
 font as the previous occurrence of ``definition'' in this sentence.
-Finally, file names are indicated like this: @file{/path/to/ourfile}.
+Finally, @value{FN}s are indicated like this: @file{/path/to/ourfile}.
 @end ifnotinfo
 
 Characters that you type at the keyboard look @kbd{like this}.  In particular,
@@ -1441,16 +1711,22 @@ the picture of a flashlight in the margin, as shown here.
 @ifnottex
 ``(d.c.)''.
 @end ifnottex
+@ifclear FOR_PRINT
 They also appear in the index under the heading ``dark corner.''
+@end ifclear
 
-As noted by the opening quote, though, any
-coverage of dark corners
-is, by definition, incomplete.
+As noted by the opening quote, though, any coverage of dark corners is,
+by definition, incomplete.
 
 Extensions to the standard @command{awk} language that are supported by
 more than one @command{awk} implementation are marked
+@ifclear FOR_PRINT
 ``@value{COMMONEXT},'' and listed in the index under ``common extensions''
 and ``extensions, common.''
+@end ifclear
+@ifset FOR_PRINT
+``@value{COMMONEXT}.''
+@end ifset
 
 @node Manual History
 @unnumberedsec The GNU Project and This Book
@@ -1473,13 +1749,15 @@ Foundation to create a complete, freely distributable, POSIX-compliant
 computing environment.
 The FSF uses the ``GNU General Public License'' (GPL) to ensure that
 their software's
-source code is always available to the end user. A
-copy of the GPL is included
+source code is always available to the end user.
+@ifclear FOR_PRINT
+A copy of the GPL is included
 @ifnotinfo
 in this @value{DOCUMENT}
 @end ifnotinfo
 for your reference
 (@pxref{Copying}).
+@end ifclear
 The GPL applies to the C language source code for @command{gawk}.
 To find out more about the FSF and the GNU Project online,
 see @uref{http://www.gnu.org, the GNU Project's home page}.
@@ -1502,8 +1780,13 @@ consider using GNU/Linux, a freely distributable, Unix-like operating
 system for Intel@registeredsymbol{},
 Power Architecture,
 Sun SPARC, IBM S/390, and other
+@ifclear FOR_PRINT
 systems.@footnote{The terminology ``GNU/Linux'' is explained
 in the @ref{Glossary}.}
+@end ifclear
+@ifset FOR_PRINT
+systems.
+@end ifset
 Many GNU/Linux distributions are
 available for download from the Internet.
 
@@ -1523,53 +1806,13 @@ The @value{DOCUMENT} you are reading is actually free---at least, the
 information in it is free to anyone.  The machine-readable
 source code for the @value{DOCUMENT} comes with @command{gawk}; anyone
 may take this @value{DOCUMENT} to a copying machine and make as many
-copies as they like.  (Take a moment to check the Free Documentation
+copies as they like.
+@ifclear FOR_PRINT
+(Take a moment to check the Free Documentation
 License in @ref{GNU Free Documentation License}.)
+@end ifclear
 @end ifnotinfo
 
-@ignore
-@cindex Close, Diane
-The @value{DOCUMENT} itself has gone through several previous,
-preliminary editions.
-Paul Rubin wrote the very first draft of @cite{The GAWK Manual};
-it was around 40 pages in size.
-Diane Close and Richard Stallman improved it, yielding the
-version which I started working with in the fall of 1988.
-It was around 90 pages long and barely described the original, ``old''
-version of @command{awk}. After substantial revision, the first version of
-the @cite{The GAWK Manual} to be released was Edition 0.11 Beta in
-October of 1989.  The manual then underwent more substantial revision
-for Edition 0.13 of December 1991.
-David Trueman, Pat Rankin and Michal Jaegermann contributed sections
-of the manual for Edition 0.13.
-That edition was published by the
-FSF as a bound book early in 1992.  Since then there were several
-minor revisions, notably Edition 0.14 of November 1992 that was published
-by the FSF in January of 1993 and Edition 0.16 of August 1993.
-
-Edition 1.0 of @cite{GAWK: The GNU Awk User's Guide} represented a significant re-working
-of @cite{The GAWK Manual}, with much additional material.
-The FSF and I agreed that I was now the primary author.
-@c I also felt that the manual needed a more descriptive title.
-
-In January 1996, SSC published Edition 1.0 under the title @cite{Effective AWK Programming}.
-In February 1997, they published Edition 1.0.3 which had minor changes
-as a ``second edition.''
-In 1999, the FSF published this same version as Edition 2
-of @cite{GAWK: The GNU Awk User's Guide}.
-
-Edition @value{EDITION} maintains the basic structure of Edition 1.0,
-but with significant additional material, reflecting the host of new features
-in @command{gawk} version @value{VERSION}.
-Of particular note is
-@ref{Array Sorting},
-@ref{Bitwise Functions},
-@ref{Internationalization},
-@ref{Advanced Features},
-and
-@ref{Dynamic Extensions}.
-@end ignore
-
 @cindex Close, Diane
 The @value{DOCUMENT} itself has gone through a number of previous editions.
 Paul Rubin wrote the very first draft of @cite{The GAWK Manual};
@@ -1585,24 +1828,50 @@ the FSF published several preliminary versions (numbered 0.@var{x}).
 In 1996, Edition 1.0 was released with @command{gawk} 3.0.0.
 The FSF published the first two editions under
 the title @cite{The GNU Awk User's Guide}.
+@ifset FOR_PRINT
+SSC published two editions of the @value{DOCUMENT} under the
+title @cite{Effective awk Programming}, and in O'Reilly published
+the third edition in 2001.
+@end ifset
 
 This edition maintains the basic structure of the previous editions.
-For Edition 4.0, the content has been thoroughly reviewed
+For FSF edition 4.0, the content has been thoroughly reviewed
 and updated. All references to @command{gawk} versions prior to 4.0 have been
 removed.
 Of significant note for this edition was @ref{Debugger}.
 
-For edition @value{EDITION}, the content has been reorganized into parts,
+For FSF edition
+@ifclear FOR_PRINT
+@value{EDITION},
+@end ifclear
+@ifset FOR_PRINT
+@value{EDITION}
+(the fourth edition as published by O'Reilly),
+@end ifset
+the content has been reorganized into parts,
 and the major new additions are @ref{Arbitrary Precision Arithmetic},
 and @ref{Dynamic Extensions}.
 
-@cite{@value{TITLE}} will undoubtedly continue to evolve.
-An electronic version
-comes with the @command{gawk} distribution from the FSF.
-If you find an error in this @value{DOCUMENT}, please report it!
-@xref{Bugs}, for information on submitting
-problem reports electronically.
+This @value{DOCUMENT} will undoubtedly continue to evolve.  An electronic
+version comes with the @command{gawk} distribution from the FSF.  If you
+find an error in this @value{DOCUMENT}, please report it!  @xref{Bugs},
+for information on submitting problem reports electronically.
+
+@ifset FOR_PRINT
+@c fakenode --- for prepinfo
+@unnumberedsec How to Stay Current
+
+It may be you have a version of @command{gawk} which is newer than the
+one described in this @value{DOCUMENT}.  To find out what has changed,
+you should first look at the @file{NEWS} file in the @command{gawk}
+distribution, which provides a high level summary of what changed in
+each release.
+
+You can then look at the @uref{http://www.gnu.org/software/gawk/manual/,
+online version} of this @value{DOCUMENT} to read about any new features.
+@end ifset
 
+@ifclear FOR_PRINT
 @node How To Contribute
 @unnumberedsec How to Contribute
 
@@ -1619,7 +1888,7 @@ However, I found that I could not dedicate enough time to managing
 contributed code: the archive did not grow and the domain went unused
 for several years.
 
-Fortunately, late in 2008, a volunteer took on the task of setting up
+Late in 2008, a volunteer took on the task of setting up
 an @command{awk}-related web site---@uref{http://awk.info}---and did a very
 nice job.
 
@@ -1628,11 +1897,15 @@ a @command{gawk} extension that you would like to share with the rest
 of the world, please see @uref{http://awk.info/?contribute} for how to
 contribute it to the web site.
 
+As of this writing, this website is in search of a maintainer; please
+contact me if you are interested.
+
 @ignore
 Other links:
 
 http://www.reddit.com/r/linux/comments/dtect/composing_music_in_awk/
 @end ignore
+@end ifclear
 
 @node Acknowledgments
 @unnumberedsec Acknowledgments
@@ -1723,7 +1996,7 @@ significant editorial help for this @value{DOCUMENT} for the
 3.1 release of @command{gawk}.
 @end quotation
 
-@cindex Beebe, Nelson
+@cindex Beebe, Nelson H.F.@:
 @cindex Buening, Andreas
 @cindex Collado, Manuel
 @cindex Colombo, Antonio
@@ -1740,7 +2013,6 @@ significant editorial help for this @value{DOCUMENT} for the
 @cindex Rankin, Pat
 @cindex Schorr, Andrew
 @cindex Vinschen, Corinna
-@cindex Wallin, Anders
 @cindex Zaretskii, Eli
 
 Dr.@: Nelson Beebe,
@@ -1760,7 +2032,6 @@ Chet Ramey,
 Pat Rankin,
 Andrew Schorr,
 Corinna Vinschen,
-Anders Wallin,
 and Eli Zaretskii
 (in alphabetical order)
 make up the current
@@ -1772,6 +2043,10 @@ people.
 Notable code and documentation contributions were made by
 a number of people. @xref{Contributors}, for the full list.
 
+Thanks to Patrice Dumas  for the new @command{makeinfo} program.
+Thanks to Karl Berry who continues to work to keep
+the Texinfo markup language sane.
+
 @cindex Kernighan, Brian
 I would like to thank Brian Kernighan for invaluable assistance during the
 testing and debugging of @command{gawk}, and for ongoing
@@ -1791,26 +2066,28 @@ which they raised and educated me.
 Finally, I also must acknowledge my gratitude to G-d, for the many opportunities
 He has sent my way, as well as for the gifts He has given me with which to
 take advantage of those opportunities.
+@iftex
 @sp 2
 @noindent
 Arnold Robbins @*
 Nof Ayalon @*
 ISRAEL @*
-May, 2013
-
-@iftex
-@part Part I:@* The @command{awk} Language
+May, 2014
 @end iftex
 
-@ignore
+@ifnotinfo
+@part @value{PART1}The @command{awk} Language
+@end ifnotinfo
+
 @ifdocbook
-@part Part I:@* The @command{awk} Language
 
-Part I describes the @command{awk} language and @command{gawk} program in detail.
-It starts with the basics, and continues through all of the features of @command{awk}
-and @command{gawk}.  It contains the following chapters:
+Part I describes the @command{awk} language and @command{gawk} program
+in detail.  It starts with the basics, and continues through all of
+the features of @command{awk}. Included also are many, but not all,
+of the features of @command{gawk}.  This part contains the
+following chapters:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Getting Started}.
 
@@ -1839,7 +2116,6 @@ and @command{gawk}.  It contains the following chapters:
 @ref{Functions}.
 @end itemize
 @end ifdocbook
-@end ignore
 
 @node Getting Started
 @chapter Getting Started with @command{awk}
@@ -1879,7 +2155,7 @@ pattern to search for and one action to perform
 upon finding the pattern.
 
 Syntactically, a rule consists of a pattern followed by an action.  The
-action is enclosed in curly braces to separate it from the pattern.
+action is enclosed in braces to separate it from the pattern.
 Newlines usually separate rules.  Therefore, an @command{awk}
 program looks like this:
 
@@ -1903,6 +2179,7 @@ program looks like this:
 * Other Features::              Other Features of @command{awk}.
 * When::                        When to use @command{gawk} and when to use
                                 other things.
+* Intro Summary::               Summary of the introduction.
 @end menu
 
 @node Running gawk
@@ -1931,7 +2208,7 @@ variations of each.
 @menu
 * One-shot::                    Running a short throwaway @command{awk}
                                 program.
-* Read Terminal::               Using no input files (input from terminal
+* Read Terminal::               Using no input files (input from the keyboard
                                 instead).
 * Long::                        Putting permanent @command{awk} programs in
                                 files.
@@ -1995,10 +2272,15 @@ awk '@var{program}'
 
 @noindent
 @command{awk} applies the @var{program} to the @dfn{standard input},
-which usually means whatever you type on the terminal.  This continues
+which usually means whatever you type on the keyboard.  This continues
 until you indicate end-of-file by typing @kbd{Ctrl-d}.
+@ifset FOR_PRINT
+(On other operating systems, the end-of-file character may be different.)
+@end ifset
+@ifclear FOR_PRINT
 (On other operating systems, the end-of-file character may be different.
 For example, on OS/2, it is @kbd{Ctrl-z}.)
+@end ifclear
 
 @cindex files, input, See input files
 @cindex input files, running @command{awk} without
@@ -2018,11 +2300,11 @@ $ @kbd{awk "BEGIN @{ print \"Don't Panic!\" @}"}
 @print{} Don't Panic!
 @end example
 
-@cindex quoting
-@cindex double quote (@code{"})
-@cindex @code{"} (double quote)
-@cindex @code{\} (backslash)
-@cindex backslash (@code{\})
+@cindex shell quoting, double quote
+@cindex double quote (@code{"}) in shell commands
+@cindex @code{"} (double quote) in shell commands
+@cindex @code{\} (backslash) in shell commands
+@cindex backslash (@code{\}) in shell commands
 This program does not read any input.  The @samp{\} before each of the
 inner double quotes is necessary because of the shell's quoting
 rules---in particular because it mixes both single quotes and
@@ -2061,11 +2343,10 @@ more convenient to put the program into a separate file.  In order to tell
 awk -f @var{source-file} @var{input-file1} @var{input-file2} @dots{}
 @end example
 
-@cindex @code{-f} option
-@cindex command line, options
-@cindex options, command-line
+@cindex @option{-f} option
+@cindex command line, option @option{-f}
 The @option{-f} instructs the @command{awk} utility to get the @command{awk} program
-from the file @var{source-file}.  Any file name can be used for
+from the file @var{source-file}.  Any @value{FN} can be used for
 @var{source-file}.  For example, you could put the program:
 
 @example
@@ -2086,22 +2367,22 @@ does the same thing as this one:
 awk "BEGIN @{ print \"Don't Panic!\" @}"
 @end example
 
-@cindex quoting
+@cindex quoting in @command{gawk} command lines
 @noindent
 This was explained earlier
 (@pxref{Read Terminal}).
-Note that you don't usually need single quotes around the file name that you
-specify with @option{-f}, because most file names don't contain any of the shell's
+Note that you don't usually need single quotes around the @value{FN} that you
+specify with @option{-f}, because most @value{FN}s don't contain any of the shell's
 special characters.  Notice that in @file{advice}, the @command{awk}
 program did not have single quotes around it.  The quotes are only needed
 for programs that are provided on the @command{awk} command line.
 
 @c STARTOFRANGE sq1x
-@cindex single quote (@code{'})
+@cindex single quote (@code{'}) in @command{gawk} command lines
 @c STARTOFRANGE qs2x
-@cindex @code{'} (single quote)
+@cindex @code{'} (single quote) in @command{gawk} command lines
 If you want to clearly identify your @command{awk} program files as such,
-you can add the extension @file{.awk} to the file name.  This doesn't
+you can add the extension @file{.awk} to the @value{FN}.  This doesn't
 affect the execution of the @command{awk} program but it does make
 ``housekeeping'' easier.
 
@@ -2128,13 +2409,13 @@ BEGIN @{ print "Don't Panic!" @}
 After making this file executable (with the @command{chmod} utility),
 simply type @samp{advice}
 at the shell and the system arranges to run @command{awk}@footnote{The
-line beginning with @samp{#!} lists the full file name of an interpreter
+line beginning with @samp{#!} lists the full @value{FN} of an interpreter
 to run and an optional initial command-line argument to pass to that
 interpreter.  The operating system then runs the interpreter with the given
 argument and the full argument list of the executed program.  The first argument
-in the list is the full file name of the @command{awk} program.
+in the list is the full @value{FN} of the @command{awk} program.
 The rest of the
-argument list contains either options to @command{awk}, or data files,
+argument list contains either options to @command{awk}, or @value{DF}s,
 or both. Note that on many systems @command{awk} may be found in
 @file{/usr/bin} instead of in @file{/bin}. Caveat Emptor.} as if you had
 typed @samp{awk -f advice}:
@@ -2209,7 +2490,7 @@ programs, but this usually isn't very useful; the purpose of a
 comment is to help you or another person understand the program
 when reading it at a later time.
 
-@cindex quoting
+@cindex quoting, for small awk programs
 @cindex single quote (@code{'}), vs.@: apostrophe
 @cindex @code{'} (single quote), vs.@: apostrophe
 @quotation CAUTION
@@ -2225,7 +2506,7 @@ runs, it will probably print strange messages about syntax errors.
 For example, look at the following:
 
 @example
-$ @kbd{awk '@{ print "hello" @} # let's be cute'}
+$ @kbd{awk 'BEGIN @{ print "hello" @} # let's be cute'}
 >
 @end example
 
@@ -2250,7 +2531,7 @@ The next @value{SUBSECTION} describes the shell's quoting rules.
 
 @node Quoting
 @subsection Shell-Quoting Issues
-@cindex quoting, rules for
+@cindex shell quoting, rules for
 
 @menu
 * DOS Quoting::                 Quoting in Windows Batch Files.
@@ -2273,7 +2554,28 @@ knowledge of shell quoting rules.  The following rules apply only to
 POSIX-compliant, Bourne-style shells (such as Bash, the GNU Bourne-Again
 Shell).  If you use the C shell, you're on your own.
 
-@itemize @bullet
+Before diving into the rules, we introduce a concept that appears
+throughout this @value{DOCUMENT}, which is that of the @dfn{null},
+or empty, string.
+
+The null string is character data that has no value.
+In other words, it is empty.  It is written in @command{awk} programs
+like this: @code{""}. In the shell, it can be written using single
+or double quotes: @code{""} or @code{''}. While the null string has
+no characters in it, it does exist. Consider this command:
+
+@example
+$ @kbd{echo ""}
+@end example
+
+@noindent
+Here, the @command{echo} utility receives a single argument, even
+though that argument has no characters in it. In the rest of this
+@value{DOCUMENT}, we use the terms @dfn{null string} and @dfn{empty string}
+interchangeably.  Now, on to the quoting rules.
+
+
+@itemize @value{BULLET}
 @item
 Quoted items can be concatenated with nonquoted items as well as with other
 quoted items.  The shell turns everything into one argument for
@@ -2285,10 +2587,10 @@ that character.  The shell removes the backslash and passes the quoted
 character on to the command.
 
 @item
-@cindex @code{\} (backslash)
-@cindex backslash (@code{\})
-@cindex single quote (@code{'})
-@cindex @code{'} (single quote)
+@cindex @code{\} (backslash), in shell commands
+@cindex backslash (@code{\}), in shell commands
+@cindex single quote (@code{'}), in shell commands
+@cindex @code{'} (single quote), in shell commands
 Single quotes protect everything between the opening and closing quotes.
 The shell does no interpretation of the quoted text, passing it on verbatim
 to the command.
@@ -2298,8 +2600,8 @@ Refer back to
 for an example of what happens if you try.
 
 @item
-@cindex double quote (@code{"})
-@cindex @code{"} (double quote)
+@cindex double quote (@code{"}), in shell commands
+@cindex @code{"} (double quote), in shell commands
 Double quotes protect most things between the opening and closing quotes.
 The shell does at least variable and command substitution on the quoted text.
 Different shells may do additional kinds of processing on double-quoted text.
@@ -2336,7 +2638,7 @@ awk -F "" '@var{program}' @var{files} # correct
 @end example
 
 @noindent
-@cindex null strings, quoting and
+@cindex null strings in @command{gawk} arguments, quoting and
 Don't use this:
 
 @example
@@ -2345,11 +2647,11 @@ awk -F"" '@var{program}' @var{files}  # wrong!
 
 @noindent
 In the second case, @command{awk} will attempt to use the text of the program
-as the value of @code{FS}, and the first file name as the text of the program!
+as the value of @code{FS}, and the first @value{FN} as the text of the program!
 This results in syntax errors at best, and confusing behavior at worst.
 @end itemize
 
-@cindex quoting, tricks for
+@cindex quoting in @command{gawk} command lines, tricks for
 Mixing single and double quotes is difficult.  You have to resort
 to shell quoting tricks, like this:
 
@@ -2448,6 +2750,7 @@ Although this @value{DOCUMENT} generally only worries about POSIX systems and th
 POSIX shell, the following issue arises often enough for many users that
 it is worth addressing.
 
+@cindex Brink, Jeroen
 The ``shells'' on Microsoft Windows systems use the double-quote
 character for quoting, and make it difficult or impossible to include an
 escaped double-quote character in a command-line script.
@@ -2460,49 +2763,47 @@ gawk "@{ print \"\042\" $0 \"\042\" @}" @var{file}
 
 
 @node Sample Data Files
-@section Data Files for the Examples
-@c For gawk >= 4.0, update these data files. No-one has such slow modems!
+@section @value{DDF}s for the Examples
 
 @cindex input files, examples
-@cindex @code{BBS-list} file
+@cindex @code{mail-list} file
 Many of the examples in this @value{DOCUMENT} take their input from two sample
-data files.  The first, @file{BBS-list}, represents a list of
-computer bulletin board systems together with information about those systems.
-The second data file, called @file{inventory-shipped}, contains
+@value{DF}s.  The first, @file{mail-list}, represents a list of peoples' names
+together with their email addresses and information about those people.
+The second @value{DF}, called @file{inventory-shipped}, contains
 information about monthly shipments.  In both files,
 each line is considered to be one @dfn{record}.
 
-In the data file @file{BBS-list}, each record contains the name of a computer
-bulletin board, its phone number, the board's baud rate(s), and a code for
-the number of hours it is operational.  An @samp{A} in the last column
-means the board operates 24 hours a day.  A @samp{B} in the last
-column means the board only operates on evening and weekend hours.
-A @samp{C} means the board operates only on weekends:
+In the @value{DF} @file{mail-list}, each record contains the name of a person,
+his/her phone number, his/her email-address, and a code for their relationship
+with the author of the list.  An @samp{A} in the last column
+means that the person is an acquaintance.  An @samp{F} in the last
+column means that the person is a friend.
+An @samp{R} means that the person is a relative:
 
-@c 2e: Update the baud rates to reflect today's faster modems
 @example
 @c system if test ! -d eg      ; then mkdir eg      ; fi
 @c system if test ! -d eg/lib  ; then mkdir eg/lib  ; fi
 @c system if test ! -d eg/data ; then mkdir eg/data ; fi
 @c system if test ! -d eg/prog ; then mkdir eg/prog ; fi
 @c system if test ! -d eg/misc ; then mkdir eg/misc ; fi
-@c file eg/data/BBS-list
-aardvark     555-5553     1200/300          B
-alpo-net     555-3412     2400/1200/300     A
-barfly       555-7685     1200/300          A
-bites        555-1675     2400/1200/300     A
-camelot      555-0542     300               C
-core         555-2912     1200/300          C
-fooey        555-1234     2400/1200/300     B
-foot         555-6699     1200/300          B
-macfoo       555-6480     1200/300          A
-sdace        555-3430     2400/1200/300     A
-sabafoo      555-2127     1200/300          C
+@c file eg/data/mail-list
+Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+Anthony      555-3412     anthony.asserturo@@hotmail.com   A
+Becky        555-7685     becky.algebrarum@@gmail.com      A
+Bill         555-1675     bill.drowning@@hotmail.com       A
+Broderick    555-0542     broderick.aliquotiens@@yahoo.com R
+Camilla      555-2912     camilla.infusarum@@skynet.be     R
+Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+Julie        555-6699     julie.perscrutabor@@skeeve.com   F
+Martin       555-6480     martin.codicibus@@hotmail.com    A
+Samuel       555-3430     samuel.lanceolis@@shu.edu        A
+Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @c endfile
 @end example
 
 @cindex @code{inventory-shipped} file
-The data file @file{inventory-shipped} represents
+The @value{DF} @file{inventory-shipped} represents
 information about shipments during the year.
 Each record contains the month, the number
 of green crates shipped, the number of red boxes shipped, the number of
@@ -2532,45 +2833,30 @@ Apr  21  70  74 514
 @c endfile
 @end example
 
-@ifinfo
-If you are reading this in GNU Emacs using Info, you can copy the regions
-of text showing these sample files into your own test files.  This way you
-can try out the examples shown in the remainder of this document.  You do
-this by using the command @kbd{M-x write-region} to copy text from the Info
-file into a file for use with @command{awk}
-(@xref{Misc File Ops, , Miscellaneous File Operations, emacs, GNU Emacs Manual},
-for more information).  Using this information, create your own
-@file{BBS-list} and @file{inventory-shipped} files and practice what you
-learn in this @value{DOCUMENT}.
-
-@cindex Texinfo
-If you are using the stand-alone version of Info,
-see @ref{Extract Program},
-for an @command{awk} program that extracts these data files from
-@file{gawk.texi}, the (generated) Texinfo source file for this Info file.
-@end ifinfo
+The sample files are included in the @command{gawk} distribution,
+in the directory @file{awklib/eg/data}.
 
 @node Very Simple
 @section Some Simple Examples
 
 The following command runs a simple @command{awk} program that searches the
-input file @file{BBS-list} for the character string @samp{foo} (a
+input file @file{mail-list} for the character string @samp{li} (a
 grouping of characters is usually called a @dfn{string};
 the term @dfn{string} is based on similar usage in English, such
 as ``a string of pearls,'' or ``a string of cars in a train''):
 
 @example
-awk '/foo/ @{ print $0 @}' BBS-list
+awk '/li/ @{ print $0 @}' mail-list
 @end example
 
 @noindent
-When lines containing @samp{foo} are found, they are printed because
+When lines containing @samp{li} are found, they are printed because
 @w{@samp{print $0}} means print the current line.  (Just @samp{print} by
 itself means the same thing, so we could have written that
 instead.)
 
-You will notice that slashes (@samp{/}) surround the string @samp{foo}
-in the @command{awk} program.  The slashes indicate that @samp{foo}
+You will notice that slashes (@samp{/}) surround the string @samp{li}
+in the @command{awk} program.  The slashes indicate that @samp{li}
 is the pattern to search for.  This type of pattern is called a
 @dfn{regular expression}, which is covered in more detail later
 (@pxref{Regexp}).
@@ -2582,11 +2868,11 @@ interpret any of it as special shell characters.
 Here is what this program prints:
 
 @example
-$ @kbd{awk '/foo/ @{ print $0 @}' BBS-list}
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sabafoo      555-2127     1200/300          C
+$ @kbd{awk '/li/ @{ print $0 @}' mail-list}
+@print{} Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+@print{} Broderick    555-0542     broderick.aliquotiens@@yahoo.com R
+@print{} Julie        555-6699     julie.perscrutabor@@skeeve.com   F
+@print{} Samuel       555-3430     samuel.lanceolis@@shu.edu        A
 @end example
 
 @cindex actions, default
@@ -2597,10 +2883,10 @@ for @emph{every} input line.  If the action is omitted, the default
 action is to print all lines that match the pattern.
 
 @cindex actions, empty
-Thus, we could leave out the action (the @code{print} statement and the curly
+Thus, we could leave out the action (the @code{print} statement and the
 braces) in the previous example and the result would be the same:
-@command{awk} prints all lines matching the pattern @samp{foo}.  By comparison,
-omitting the @code{print} statement but retaining the curly braces makes an
+@command{awk} prints all lines matching the pattern @samp{li}.  By comparison,
+omitting the @code{print} statement but retaining the braces makes an
 empty action that does nothing (i.e., no lines are printed).
 
 @cindex @command{awk} programs, one-line examples
@@ -2609,15 +2895,15 @@ collection of useful, short programs to get you started.  Some of these
 programs contain constructs that haven't been covered yet. (The description
 of the program will give you a good idea of what is going on, but please
 read the rest of the @value{DOCUMENT} to become an @command{awk} expert!)
-Most of the examples use a data file named @file{data}.  This is just a
+Most of the examples use a @value{DF} named @file{data}.  This is just a
 placeholder; if you use these programs yourself, substitute
-your own file names for @file{data}.
+your own @value{FN}s for @file{data}.
 For future reference, note that there is often more than
 one way to do things in @command{awk}.  At some point, you may want
 to look back at these examples and see if
 you can come up with different ways to do the same things shown here:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Print the length of the longest input line:
 
@@ -2634,7 +2920,7 @@ awk 'length($0) > 80' data
 @end example
 
 The sole rule has a relational expression as its pattern and it has no
-action---so the default action, printing the record, is used.
+action---so it uses the default action, printing the record.
 
 @cindex @command{expand} utility
 @item
@@ -2701,7 +2987,7 @@ awk 'END @{ print NR @}' data
 @end example
 
 @item
-Print the even-numbered lines in the data file:
+Print the even-numbered lines in the @value{DF}:
 
 @example
 awk 'NR % 2 == 0' data
@@ -2717,9 +3003,9 @@ the program would print the odd-numbered lines.
 
 The @command{awk} utility reads the input files one line at a
 time.  For each line, @command{awk} tries the patterns of each of the rules.
-If several patterns match, then several actions are run in the order in
+If several patterns match, then several actions execute in the order in
 which they appear in the @command{awk} program.  If no patterns match, then
-no actions are run.
+no actions run.
 
 After processing all the rules that match the line (and perhaps there are none),
 @command{awk} reads the next line.  (However,
@@ -2743,30 +3029,24 @@ This program prints every line that contains the string
 @samp{12} @emph{or} the string @samp{21}.  If a line contains both
 strings, it is printed twice, once by each rule.
 
-This is what happens if we run this program on our two sample data files,
-@file{BBS-list} and @file{inventory-shipped}:
+This is what happens if we run this program on our two sample @value{DF}s,
+@file{mail-list} and @file{inventory-shipped}:
 
 @example
 $ @kbd{awk '/12/ @{ print $0 @}}
->      @kbd{/21/ @{ print $0 @}' BBS-list inventory-shipped}
-@print{} aardvark     555-5553     1200/300          B
-@print{} alpo-net     555-3412     2400/1200/300     A
-@print{} barfly       555-7685     1200/300          A
-@print{} bites        555-1675     2400/1200/300     A
-@print{} core         555-2912     1200/300          C
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sdace        555-3430     2400/1200/300     A
-@print{} sabafoo      555-2127     1200/300          C
-@print{} sabafoo      555-2127     1200/300          C
+>      @kbd{/21/ @{ print $0 @}' mail-list inventory-shipped}
+@print{} Anthony      555-3412     anthony.asserturo@@hotmail.com   A
+@print{} Camilla      555-2912     camilla.infusarum@@skynet.be     R
+@print{} Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @print{} Jan  21  36  64 620
 @print{} Apr  21  70  74 514
 @end example
 
 @noindent
-Note how the line beginning with @samp{sabafoo}
-in @file{BBS-list} was printed twice, once for each rule.
+Note how the line beginning with @samp{Jean-Paul}
+in @file{mail-list} was printed twice, once for each rule.
 
 @node More Complex
 @section A More Complex Example
@@ -2809,7 +3089,7 @@ the file. The fourth field identifies the group of the file.
 The fifth field contains the size of the file in bytes.  The
 sixth, seventh, and eighth fields contain the month, day, and time,
 respectively, that the file was last modified.  Finally, the ninth field
-contains the file name.@footnote{The @samp{LC_ALL=C} is
+contains the @value{FN}.@footnote{The @samp{LC_ALL=C} is
 needed to produce this traditional-style output from @command{ls}.}
 
 @c @cindex automatic initialization
@@ -2817,8 +3097,8 @@ needed to produce this traditional-style output from @command{ls}.}
 The @samp{$6 == "Nov"} in our @command{awk} program is an expression that
 tests whether the sixth field of the output from @w{@samp{ls -l}}
 matches the string @samp{Nov}.  Each time a line has the string
-@samp{Nov} for its sixth field, the action @samp{sum += $5} is
-performed.  This adds the fifth field (the file's size) to the variable
+@samp{Nov} for its sixth field, @command{awk} performs the action
+@samp{sum += $5}.  This adds the fifth field (the file's size) to the variable
 @code{sum}.  As a result, when @command{awk} has finished reading all the
 input lines, @code{sum} is the total of the sizes of the files whose
 lines matched the pattern.  (This works because @command{awk} variables
@@ -2845,7 +3125,7 @@ separate rule, like this:
 
 @example
 awk '/12/  @{ print $0 @}
-     /21/  @{ print $0 @}' BBS-list inventory-shipped
+     /21/  @{ print $0 @}' mail-list inventory-shipped
 @end example
 
 @cindex @command{gawk}, newlines in
@@ -2885,7 +3165,7 @@ We have generally not used backslash continuation in our sample programs.
 @command{gawk} places no limit on the
 length of a line, so backslash continuation is never strictly necessary;
 it just makes programs more readable.  For this same reason, as well as
-for clarity, we have kept most statements short in the sample programs
+for clarity, we have kept most statements short in the programs
 presented throughout the @value{DOCUMENT}.  Backslash continuation is
 most useful when your @command{awk} program is in a separate source file
 instead of entered from the command line.  You should also note that
@@ -2950,7 +3230,7 @@ $ gawk 'BEGIN @{ print "dont panic" # a friendly \
 >                                    BEGIN rule
 > @}'
 @error{} gawk: cmd. line:2:                BEGIN rule
-@error{} gawk: cmd. line:2:                ^ parse error
+@error{} gawk: cmd. line:2:                ^ syntax error
 @end example
 
 @noindent
@@ -2960,8 +3240,8 @@ noticed because it is ``hidden'' inside the comment. Thus, the
 @code{BEGIN} is noted as a syntax error.
 
 @cindex statements, multiple
-@cindex @code{;} (semicolon)
-@cindex semicolon (@code{;})
+@cindex @code{;} (semicolon), separating statements in actions
+@cindex semicolon (@code{;}), separating statements in actions
 When @command{awk} statements within one rule are short, you might want to put
 more than one of them on a line.  This is accomplished by separating the statements
 with a semicolon (@samp{;}).
@@ -3021,9 +3301,16 @@ used once, and thrown away.  Because @command{awk} programs are interpreted, you
 can avoid the (usually lengthy) compilation part of the typical
 edit-compile-test-debug cycle of software development.
 
+@cindex Brian Kernighan's @command{awk}
 Complex programs have been written in @command{awk}, including a complete
-retargetable assembler for eight-bit microprocessors (@pxref{Glossary}, for
-more information), and a microcode assembler for a special-purpose Prolog
+retargetable assembler for
+@ifclear FOR_PRINT
+eight-bit microprocessors (@pxref{Glossary}, for more information),
+@end ifclear
+@ifset FOR_PRINT
+eight-bit microprocessors,
+@end ifset
+and a microcode assembler for a special-purpose Prolog
 computer.
 While the original @command{awk}'s capabilities were strained by tasks
 of such complexity, modern versions are more capable.  Even Brian Kernighan's
@@ -3033,19 +3320,55 @@ that it has are much larger than they used to be.
 @cindex @command{awk} programs, complex
 If you find yourself writing @command{awk} scripts of more than, say, a few
 hundred lines, you might consider using a different programming
-language.  Emacs Lisp is a good choice if you need sophisticated string
-or pattern matching capabilities.  The shell is also good at string and
+language.
+The shell is good at string and
 pattern matching; in addition, it allows powerful use of the system
 utilities.  More conventional languages, such as C, C++, and Java, offer
 better facilities for system programming and for managing the complexity
-of large programs.  Programs in these languages may require more lines
+of large programs.
+Python offers a nice balance between high-level ease of programming and
+access to system facilities.
+Programs in these languages may require more lines
 of source code than the equivalent @command{awk} programs, but they are
 easier to maintain and usually run more efficiently.
 
+@node Intro Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Programs in @command{awk} consist of @var{pattern}-@var{action} pairs.
+
+@item
+Use either
+@samp{awk '@var{program}' @var{files}}
+or
+@samp{awk -f @var{program-file} @var{files}}
+to run @command{awk}.
+
+@item
+You may use the special @samp{#!} header line to create @command{awk}
+programs that are directly executable.
+
+@item
+Comments in @command{awk} programs start with @samp{#} and continue to
+the end of the same line.
+
+@item
+Be aware of quoting issues when writing @command{awk} programs as
+part of a larger shell script (or MS-Windows batch file).
+
+@item
+You may use backslash continuation to continue a source line.
+Lines are automatically continued after
+a comma, open brace, question mark, colon,
+@samp{||}, @samp{&&}, @code{do} and @code{else}.
+@end itemize
+
 @node Invoking Gawk
 @chapter Running @command{awk} and @command{gawk}
 
-This @value{CHAPTER} covers how to run awk, both POSIX-standard
+This @value{CHAPTER} covers how to run @command{awk}, both POSIX-standard
 and @command{gawk}-specific command-line options, and what
 @command{awk} and
 @command{gawk} do with non-option arguments.
@@ -3070,6 +3393,7 @@ things in this @value{CHAPTER} that don't interest you right now.
 * Loading Shared Libraries::    Loading shared libraries into your program.
 * Obsolete::                    Obsolete Options and/or features.
 * Undocumented::                Undocumented Options and Features.
+* Invoking Summary::            Invocation summary.
 @end menu
 
 @node Command Line
@@ -3083,10 +3407,10 @@ There are two ways to run @command{awk}---with an explicit program or with
 one or more program files.  Here are templates for both of them; items
 enclosed in [@dots{}] in these templates are optional:
 
-@example
-awk @r{[@var{options}]} -f progfile @r{[@code{--}]} @var{file} @dots{}
-awk @r{[@var{options}]} @r{[@code{--}]} '@var{program}' @var{file} @dots{}
-@end example
+@display
+@command{awk} [@var{options}] @option{-f} @var{progfile} [@option{--}] @var{file} @dots{}
+@command{awk} [@var{options}] [@option{--}] @code{'@var{program}'} @var{file} @dots{}
+@end display
 
 @cindex GNU long options
 @cindex long options
@@ -3102,7 +3426,7 @@ It is possible to invoke @command{awk} with an empty program:
 awk '' datafile1 datafile2
 @end example
 
-@cindex @code{--lint} option
+@cindex @option{--lint} option
 @noindent
 Doing so makes little sense, though; @command{awk} exits
 silently when given an empty program.
@@ -3142,43 +3466,27 @@ The following list describes options mandated by the POSIX standard:
 @table @code
 @item -F @var{fs}
 @itemx --field-separator @var{fs}
-@cindex @code{-F} option
-@cindex @code{--field-separator} option
+@cindex @option{-F} option
+@cindex @option{--field-separator} option
 @cindex @code{FS} variable, @code{--field-separator} option and
 Set the @code{FS} variable to @var{fs}
 (@pxref{Field Separators}).
 
 @item -f @var{source-file}
 @itemx --file @var{source-file}
-@cindex @code{-f} option
-@cindex @code{--file} option
+@cindex @option{-f} option
+@cindex @option{--file} option
 @cindex @command{awk} programs, location of
 Read @command{awk} program source from @var{source-file}
 instead of in the first non-option argument.
 This option may be given multiple times; the @command{awk}
-program consists of the concatenation the contents of
+program consists of the concatenation of the contents of
 each specified @var{source-file}.
 
-@item -i @var{source-file}
-@itemx --include @var{source-file}
-@cindex @code{-i} option
-@cindex @code{--include} option
-@cindex @command{awk} programs, location of
-Read @command{awk} source library from @var{source-file}.  This option is
-completely equivalent to using the @samp{@@include} directive inside
-your program.  This option is very
-similar to the @option{-f} option, but there are two important differences.
-First, when @option{-i} is used, the program source will not be loaded if it has
-been previously loaded, whereas the @option{-f} will always load the file.
-Second, because this option is intended to be used with code libraries,
-@command{gawk} does not recognize such files as constituting main program
-input.  Thus, after processing an @option{-i} argument, @command{gawk} still expects to
-find the main source code via the @option{-f} option or on the command-line.
-
 @item -v @var{var}=@var{val}
 @itemx --assign @var{var}=@var{val}
-@cindex @code{-v} option
-@cindex @code{--assign} option
+@cindex @option{-v} option
+@cindex @option{--assign} option
 @cindex variables, setting
 Set the variable @var{var} to the value @var{val} @emph{before}
 execution of the program begins.  Such variable values are available
@@ -3199,7 +3507,7 @@ predefined value you may have given.
 @end quotation
 
 @item -W @var{gawk-opt}
-@cindex @code{-W} option
+@cindex @option{-W} option
 Provide an implementation-specific option.
 This is the POSIX convention for providing implementation-specific options.
 These options
@@ -3218,8 +3526,8 @@ conventions.
 
 @cindex @code{-} (hyphen), filenames beginning with
 @cindex hyphen (@code{-}), filenames beginning with
-This is useful if you have file names that start with @samp{-},
-or in shell scripts, if you have file names that will be specified
+This is useful if you have @value{FN}s that start with @samp{-},
+or in shell scripts, if you have @value{FN}s that will be specified
 by the user that could start with @samp{-}.
 It is also useful for passing options on to the @command{awk}
 program; see @ref{Getopt Function}.
@@ -3229,47 +3537,52 @@ program; see @ref{Getopt Function}.
 
 The following list describes @command{gawk}-specific options:
 
-@table @code
-@item -b
-@itemx --characters-as-bytes
-@cindex @code{-b} option
-@cindex @code{--characters-as-bytes} option
+@c Have to use @asis here to get docbook to come out right.
+@table @asis
+@item @option{-b}
+@itemx @option{--characters-as-bytes}
+@cindex @option{-b} option
+@cindex @option{--characters-as-bytes} option
 Cause @command{gawk} to treat all input data as single-byte characters.
 In addition, all output written with @code{print} or @code{printf}
 are treated as single-byte characters.
 
 Normally, @command{gawk} follows the POSIX standard and attempts to process
-its input data according to the current locale. This can often involve
+its input data according to the current locale (@pxref{Locales}). This can often involve
 converting multibyte characters into wide characters (internally), and
 can lead to problems or confusion if the input data does not contain valid
 multibyte characters. This option is an easy way to tell @command{gawk}:
 ``hands off my data!''.
 
-@item -c
-@itemx --traditional
-@cindex @code{--c} option
-@cindex @code{--traditional} option
+@item @option{-c}
+@itemx @option{--traditional}
+@cindex @option{-c} option
+@cindex @option{--traditional} option
 @cindex compatibility mode (@command{gawk}), specifying
 Specify @dfn{compatibility mode}, in which the GNU extensions to
 the @command{awk} language are disabled, so that @command{gawk} behaves just
 like Brian Kernighan's version @command{awk}.
 @xref{POSIX/GNU},
-which summarizes the extensions.  Also see
+which summarizes the extensions.
+@ifclear FOR_PRINT
+Also see
 @ref{Compatibility Mode}.
+@end ifclear
 
-@item -C
-@itemx --copyright
-@cindex @code{-C} option
-@cindex @code{--copyright} option
+@item @option{-C}
+@itemx @option{--copyright}
+@cindex @option{-C} option
+@cindex @option{--copyright} option
 @cindex GPL (General Public License), printing
 Print the short version of the General Public License and then exit.
 
-@item -d@r{[}@var{file}@r{]}
-@itemx --dump-variables@r{[}=@var{file}@r{]}
-@cindex @code{-d} option
-@cindex @code{--dump-variables} option
-@cindex @code{awkvars.out} file
-@cindex files, @code{awkvars.out}
+@item @option{-d}[@var{file}]
+@itemx @option{--dump-variables}[@code{=}@var{file}]
+@cindex @option{-d} option
+@cindex @option{--dump-variables} option
+@cindex dump all variables of a program
+@cindex @file{awkvars.out} file
+@cindex files, @file{awkvars.out}
 @cindex variables, global, printing list of
 Print a sorted list of global variables, their types, and final values
 to @var{file}.  If no @var{file} is provided, print this
@@ -3286,23 +3599,23 @@ inadvertently use global variables that you meant to be local.
 (This is a particularly easy mistake to make with simple variable
 names like @code{i}, @code{j}, etc.)
 
-@item -D@r{[}@var{file}@r{]}
-@itemx --debug=@r{[}@var{file}@r{]}
-@cindex @code{-D} option
-@cindex @code{--debug} option
+@item @option{-D}[@var{file}]
+@itemx @option{--debug}[@code{=}@var{file}]
+@cindex @option{-D} option
+@cindex @option{--debug} option
 @cindex @command{awk} debugging, enabling
 Enable debugging of @command{awk} programs
 (@pxref{Debugging}).
-By default, the debugger reads commands interactively from the terminal.
+By default, the debugger reads commands interactively from the keyboard.
 The optional @var{file} argument allows you to specify a file with a list
 of commands for the debugger to execute non-interactively.
 No space is allowed between the @option{-D} and @var{file}, if
 @var{file} is supplied.
 
-@item -e @var{program-text}
-@itemx --source @var{program-text}
-@cindex @code{-e} option
-@cindex @code{--source} option
+@item @option{-e} @var{program-text}
+@itemx @option{--source} @var{program-text}
+@cindex @option{-e} option
+@cindex @option{--source} option
 @cindex source code, mixing
 Provide program source code in the @var{program-text}.
 This option allows you to mix source code in files with source
@@ -3311,16 +3624,16 @@ This is particularly useful
 when you have library functions that you want to use from your command-line
 programs (@pxref{AWKPATH Variable}).
 
-@item -E @var{file}
-@itemx --exec @var{file}
-@cindex @code{-E} option
-@cindex @code{--exec} option
+@item @option{-E} @var{file}
+@itemx @option{--exec} @var{file}
+@cindex @option{-E} option
+@cindex @option{--exec} option
 @cindex @command{awk} programs, location of
 @cindex CGI, @command{awk} scripts for
 Similar to @option{-f}, read @command{awk} program text from @var{file}.
 There are two differences from @option{-f}:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 This option terminates option processing; anything
 else on the command line is passed on directly to the @command{awk} program.
@@ -3342,48 +3655,69 @@ with @samp{#!} scripts (@pxref{Executable Scripts}), like so:
 @var{awk program here @dots{}}
 @end example
 
-@item -g
-@itemx --gen-pot
-@cindex @code{-g} option
-@cindex @code{--gen-pot} option
+@item @option{-g}
+@itemx @option{--gen-pot}
+@cindex @option{-g} option
+@cindex @option{--gen-pot} option
 @cindex portable object files, generating
 @cindex files, portable object, generating
 Analyze the source program and
-generate a GNU @code{gettext} Portable Object Template file on standard
+generate a GNU @command{gettext} Portable Object Template file on standard
 output for all string constants that have been marked for translation.
 @xref{Internationalization},
 for information about this option.
 
-@item -h
-@itemx --help
-@cindex @code{-h} option
-@cindex @code{--help} option
+@item @option{-h}
+@itemx @option{--help}
+@cindex @option{-h} option
+@cindex @option{--help} option
 @cindex GNU long options, printing list of
 @cindex options, printing list of
 @cindex printing, list of options
 Print a ``usage'' message summarizing the short and long style options
 that @command{gawk} accepts and then exit.
 
-@item -l @var{lib}
-@itemx --load @var{lib}
-@cindex @code{-l} option
-@cindex @code{--load} option
-@cindex loading, library
-Load a shared library @var{lib}. This searches for the library using the @env{AWKLIBPATH}
+@item @option{-i} @var{source-file}
+@itemx @option{--include} @var{source-file}
+@cindex @option{-i} option
+@cindex @option{--include} option
+@cindex @command{awk} programs, location of
+Read @command{awk} source library from @var{source-file}.  This option
+is completely equivalent to using the @code{@@include} directive inside
+your program.  This option is very similar to the @option{-f} option,
+but there are two important differences.  First, when @option{-i} is
+used, the program source is not loaded if it has been previously
+loaded, whereas with @option{-f}, @command{gawk} always loads the file.
+Second, because this option is intended to be used with code libraries,
+@command{gawk} does not recognize such files as constituting main program
+input.  Thus, after processing an @option{-i} argument, @command{gawk}
+still expects to find the main source code via the @option{-f} option
+or on the command-line.
+
+@item @option{-l} @var{ext}
+@itemx @option{--load} @var{ext}
+@cindex @option{-l} option
+@cindex @option{--load} option
+@cindex loading, extensions
+Load a dynamic extension named @var{ext}. Extensions
+are stored as system shared libraries.
+This option searches for the library using the @env{AWKLIBPATH}
 environment variable.  The correct library suffix for your platform will be
-supplied by default, so it need not be specified in the library name.
-The library initialization routine should be named @code{dl_load()}.
-An alternative is to use the @samp{@@load} keyword inside the program to load
-a shared library.
-
-@item -L @r{[}value@r{]}
-@itemx --lint@r{[}=value@r{]}
-@cindex @code{-l} option
-@cindex @code{--lint} option
+supplied by default, so it need not be specified in the extension name.
+The extension initialization routine should be named @code{dl_load()}.
+An alternative is to use the @code{@@load} keyword inside the program to load
+a shared library.  This feature is described in detail in @ref{Dynamic Extensions}.
+
+@item @option{-L}[@var{value}]
+@itemx @option{--lint}[@code{=}@var{value}]
+@cindex @option{-l} option
+@cindex @option{--lint} option
 @cindex lint checking, issuing warnings
 @cindex warnings, issuing
 Warn about constructs that are dubious or nonportable to
 other @command{awk} implementations.
+No space is allowed between the @option{-D} and @var{value}, if
+@var{value} is supplied.
 Some warnings are issued when @command{gawk} first reads your program.  Others
 are issued at runtime, as your program executes.
 With an optional argument of @samp{fatal},
@@ -3399,18 +3733,18 @@ when eliminating problems pointed out by @option{--lint}, you should take
 care to search for all occurrences of each inappropriate construct. As
 @command{awk} programs are usually short, doing so is not burdensome.
 
-@item -M
-@itemx --bignum
-@cindex @code{-M} option
-@cindex @code{--bignum} option
+@item @option{-M}
+@itemx @option{--bignum}
+@cindex @option{-M} option
+@cindex @option{--bignum} option
 Force arbitrary precision arithmetic on numbers. This option has no effect
 if @command{gawk} is not compiled to use the GNU MPFR and MP libraries
 (@pxref{Arbitrary Precision Arithmetic}).
 
-@item -n
-@itemx --non-decimal-data
-@cindex @code{-n} option
-@cindex @code{--non-decimal-data} option
+@item @option{-n}
+@itemx @option{--non-decimal-data}
+@cindex @option{-n} option
+@cindex @option{--non-decimal-data} option
 @cindex hexadecimal values@comma{} enabling interpretation of
 @cindex octal values@comma{} enabling interpretation of
 @cindex troubleshooting, @code{--non-decimal-data} option
@@ -3423,52 +3757,59 @@ This option can severely break old programs.
 Use with care.
 @end quotation
 
-@item -N
-@itemx --use-lc-numeric
-@cindex @code{-N} option
-@cindex @code{--use-lc-numeric} option
+@item @option{-N}
+@itemx @option{--use-lc-numeric}
+@cindex @option{-N} option
+@cindex @option{--use-lc-numeric} option
 Force the use of the locale's decimal point character
 when parsing numeric input data (@pxref{Locales}).
 
-@item -o@r{[}@var{file}@r{]}
-@itemx --pretty-print@r{[}=@var{file}@r{]}
-@cindex @code{-o} option
-@cindex @code{--pretty-print} option
+@item @option{-o}[@var{file}]
+@itemx @option{--pretty-print}[@code{=}@var{file}]
+@cindex @option{-o} option
+@cindex @option{--pretty-print} option
 Enable pretty-printing of @command{awk} programs.
-By default, output program is created in a file named @file{awkprof.out}.
+By default, output program is created in a file named @file{awkprof.out}
+(@pxref{Profiling}).
 The optional @var{file} argument allows you to specify a different
-file name for the output.
+@value{FN} for the output.
 No space is allowed between the @option{-o} and @var{file}, if
 @var{file} is supplied.
 
-@item -O
-@itemx --optimize
-@cindex @code{--optimize} option
-@cindex @code{-O} option
+@quotation NOTE
+Due to the way @command{gawk} has evolved, with this option
+your program is still executed.  This will change in the
+next major release such that @command{gawk} will only
+pretty-print the program and not run it.
+@end quotation
+
+@item @option{-O}
+@itemx @option{--optimize}
+@cindex @option{--optimize} option
+@cindex @option{-O} option
 Enable some optimizations on the internal representation of the program.
-At the moment this includes just simple constant folding. The @command{gawk}
-maintainer hopes to add more optimizations over time.
+At the moment this includes just simple constant folding.
 
-@item -p@r{[}@var{file}@r{]}
-@itemx --profile@r{[}=@var{file}@r{]}
-@cindex @code{-p} option
-@cindex @code{--profile} option
+@item @option{-p}[@var{file}]
+@itemx @option{--profile}[@code{=}@var{file}]
+@cindex @option{-p} option
+@cindex @option{--profile} option
 @cindex @command{awk} profiling, enabling
 Enable profiling of @command{awk} programs
 (@pxref{Profiling}).
 By default, profiles are created in a file named @file{awkprof.out}.
 The optional @var{file} argument allows you to specify a different
-file name for the profile file.
+@value{FN} for the profile file.
 No space is allowed between the @option{-p} and @var{file}, if
 @var{file} is supplied.
 
 The profile contains execution counts for each statement in the program
 in the left margin, and function call counts for each function.
 
-@item -P
-@itemx --posix
-@cindex @code{-P} option
-@cindex @code{--posix} option
+@item @option{-P}
+@itemx @option{--posix}
+@cindex @option{-P} option
+@cindex @option{--posix} option
 @cindex POSIX mode
 @cindex @command{gawk}, extensions@comma{} disabling
 Operate in strict POSIX mode.  This disables all @command{gawk}
@@ -3480,7 +3821,7 @@ Also,
 the following additional
 restrictions apply:
 
-@itemize @bullet
+@itemize @value{BULLET}
 
 @cindex newlines
 @cindex whitespace, newlines as
@@ -3509,28 +3850,28 @@ data (@pxref{Locales}).
 
 @c @cindex automatic warnings
 @c @cindex warnings, automatic
-@cindex @code{--traditional} option, @code{--posix} option and
-@cindex @code{--posix} option, @code{--traditional} option and
+@cindex @option{--traditional} option, @code{--posix} option and
+@cindex @option{--posix} option, @code{--traditional} option and
 If you supply both @option{--traditional} and @option{--posix} on the
 command line, @option{--posix} takes precedence. @command{gawk}
-also issues a warning if both options are supplied.
+issues a warning if both options are supplied.
 
-@item -r
-@itemx --re-interval
-@cindex @code{-r} option
-@cindex @code{--re-interval} option
+@item @option{-r}
+@itemx @option{--re-interval}
+@cindex @option{-r} option
+@cindex @option{--re-interval} option
 @cindex regular expressions, interval expressions and
 Allow interval expressions
 (@pxref{Regexp Operators})
 in regexps.
 This is now @command{gawk}'s default behavior.
 Nevertheless, this option remains both for backward compatibility,
-and for use in combination with the @option{--traditional} option.
+and for use in combination with @option{--traditional}.
 
-@item -S
-@itemx --sandbox
-@cindex @code{-S} option
-@cindex @code{--sandbox} option
+@item @option{-S}
+@itemx @option{--sandbox}
+@cindex @option{-S} option
+@cindex @option{--sandbox} option
 @cindex sandbox mode
 Disable the @code{system()} function,
 input redirections with @code{getline},
@@ -3538,20 +3879,20 @@ output redirections with @code{print} and @code{printf},
 and dynamic extensions.
 This is particularly useful when you want to run @command{awk} scripts
 from questionable sources and need to make sure the scripts
-can't access your system (other than the specified input data file).
+can't access your system (other than the specified input @value{DF}).
 
-@item -t
-@itemx --lint-old
-@cindex @code{--L} option
-@cindex @code{--lint-old} option
+@item @option{-t}
+@itemx @option{--lint-old}
+@cindex @option{-L} option
+@cindex @option{--lint-old} option
 Warn about constructs that are not available in the original version of
 @command{awk} from Version 7 Unix
 (@pxref{V7/SVR3.1}).
 
-@item -V
-@itemx --version
-@cindex @code{-V} option
-@cindex @code{--version} option
+@item @option{-V}
+@itemx @option{--version}
+@cindex @option{-V} option
+@cindex @option{--version} option
 @cindex @command{gawk}, versions of, information about@comma{} printing
 Print version information for this particular copy of @command{gawk}.
 This allows you to determine if your copy of @command{gawk} is up to date
@@ -3565,14 +3906,14 @@ As long as program text has been supplied,
 any other options are flagged as invalid with a warning message but
 are otherwise ignored.
 
-@cindex @code{-F} option, @code{-Ft} sets @code{FS} to TAB
+@cindex @option{-F} option, @option{-Ft} sets @code{FS} to TAB
 In compatibility mode, as a special case, if the value of @var{fs} supplied
 to the @option{-F} option is @samp{t}, then @code{FS} is set to the TAB
 character (@code{"\t"}).  This is true only for @option{--traditional} and not
 for @option{--posix}
 (@pxref{Field Separators}).
 
-@cindex @code{-f} option, multiple uses
+@cindex @option{-f} option, multiple uses
 The @option{-f} option may be used more than once on the command line.
 If it is, @command{awk} reads its program source from all of the named files, as
 if they had been concatenated together into one big file.  This is
@@ -3584,22 +3925,22 @@ of having to be included into each individual program.
 function names must be unique.)
 
 With standard @command{awk}, library functions can still be used, even
-if the program is entered at the terminal,
+if the program is entered at the keyboard,
 by specifying @samp{-f /dev/tty}.  After typing your program,
 type @kbd{Ctrl-d} (the end-of-file character) to terminate it.
 (You may also use @samp{-f -} to read program source from the standard
 input but then you will not be able to also use the standard input as a
 source of data.)
 
-Because it is clumsy using the standard @command{awk} mechanisms to mix source
-file and command-line @command{awk} programs, @command{gawk} provides the
-@option{--source} option.  This does not require you to pre-empt the standard
-input for your source code; it allows you to easily mix command-line
-and library source code
-(@pxref{AWKPATH Variable}).
-The @option{--source} option may also be used multiple times on the command line.
+Because it is clumsy using the standard @command{awk} mechanisms to mix
+source file and command-line @command{awk} programs, @command{gawk}
+provides the @option{--source} option.  This does not require you to
+pre-empt the standard input for your source code; it allows you to easily
+mix command-line and library source code (@pxref{AWKPATH Variable}).
+As with @option{-f}, the @option{--source} and @option{--include}
+options may also be used multiple times on the command line.
 
-@cindex @code{--source} option
+@cindex @option{--source} option
 If no @option{-f} or @option{--source} option is specified, then @command{gawk}
 uses the first non-option command-line argument as the text of the
 program source code.
@@ -3609,7 +3950,7 @@ program source code.
 @cindex POSIX mode
 If the environment variable @env{POSIXLY_CORRECT} exists,
 then @command{gawk} behaves in strict POSIX mode, exactly as if
-you had supplied the @option{--posix} command-line option.
+you had supplied @option{--posix}.
 Many GNU programs look for this environment variable to suppress
 extensions that conflict with POSIX, but @command{gawk} behaves
 differently: it suppresses all extensions, even those that do not
@@ -3658,6 +3999,7 @@ file at all.
 
 @cindex @command{gawk}, @code{ARGIND} variable in
 @cindex @code{ARGIND} variable, command-line arguments
+@cindex @code{ARGV} array, indexing into
 @cindex @code{ARGC}/@code{ARGV} variables, command-line arguments
 All these arguments are made available to your @command{awk} program in the
 @code{ARGV} array (@pxref{Built-in Variables}).  Command-line options
@@ -3668,9 +4010,10 @@ sets the variable @code{ARGIND} to the index in @code{ARGV} of the
 current element.
 
 @cindex input files, variable assignments and
-The distinction between file name arguments and variable-assignment
+@cindex variable assignments and input files
+The distinction between @value{FN} arguments and variable-assignment
 arguments is made when @command{awk} is about to open the next input file.
-At that point in execution, it checks the file name to see whether
+At that point in execution, it checks the @value{FN} to see whether
 it is really a variable assignment; if so, @command{awk} sets the variable
 instead of reading a file.
 
@@ -3686,8 +4029,8 @@ The variable values given on the command line are processed for escape
 sequences (@pxref{Escape Sequences}).
 @value{DARKCORNER}
 
-In some earlier implementations of @command{awk}, when a variable assignment
-occurred before any file names, the assignment would happen @emph{before}
+In some very early implementations of @command{awk}, when a variable assignment
+occurred before any @value{FN}s, the assignment would happen @emph{before}
 the @code{BEGIN} rule was executed.  @command{awk}'s behavior was thus
 inconsistent; some command-line assignments were available inside the
 @code{BEGIN} rule, while others were not.  Unfortunately,
@@ -3698,8 +4041,8 @@ upon the old behavior.
 
 The variable assignment feature is most useful for assigning to variables
 such as @code{RS}, @code{OFS}, and @code{ORS}, which control input and
-output formats before scanning the data files.  It is also useful for
-controlling state if multiple passes are needed over a data file.  For
+output formats, before scanning the @value{DF}s.  It is also useful for
+controlling state if multiple passes are needed over a @value{DF}.  For
 example:
 
 @cindex files, multiple passes over
@@ -3735,16 +4078,17 @@ You may also use @code{"-"} to name standard input when reading
 files with @code{getline} (@pxref{Getline/File}).
 
 In addition, @command{gawk} allows you to specify the special
-file name @file{/dev/stdin}, both on the command line and
+@value{FN} @file{/dev/stdin}, both on the command line and
 with @code{getline}.
 Some other versions of @command{awk} also support this, but it
 is not standard.
 (Some operating systems provide a @file{/dev/stdin} file
-in the file system, however, @command{gawk} always processes
-this file name itself.)
+in the file system; however, @command{gawk} always processes
+this @value{FN} itself.)
 
 @node Environment Variables
 @section The Environment Variables @command{gawk} Uses
+@cindex environment variables used by @command{gawk}
 
 A number of environment variables influence how @command{gawk}
 behaves.
@@ -3760,8 +4104,7 @@ behaves.
 @node AWKPATH Variable
 @subsection The @env{AWKPATH} Environment Variable
 @cindex @env{AWKPATH} environment variable
-@cindex directories, searching
-@cindex search paths
+@cindex directories, searching for source files
 @cindex search paths, for source files
 @cindex differences in @command{awk} and @command{gawk}, @code{AWKPATH} environment variable
 @ifinfo
@@ -3771,14 +4114,14 @@ on the command-line with the @option{-f} option.
 In most @command{awk}
 implementations, you must supply a precise path name for each program
 file, unless the file is in the current directory.
-But in @command{gawk}, if the file name supplied to the @option{-f}
+But in @command{gawk}, if the @value{FN} supplied to the @option{-f}
 or @option{-i} options
-does not contain a @samp{/}, then @command{gawk} searches a list of
+does not contain a directory separator @samp{/}, then @command{gawk} searches a list of
 directories (called the @dfn{search path}), one by one, looking for a
 file with the specified name.
 
 The search path is a string consisting of directory names
-separated by colons.  @command{gawk} gets its search path from the
+separated by colons@footnote{Semicolons on MS-Windows and MS-DOS.}.  @command{gawk} gets its search path from the
 @env{AWKPATH} environment variable.  If that variable does not exist,
 @command{gawk} uses a default path,
 @samp{.:/usr/local/share/awk}.@footnote{Your version of @command{gawk}
@@ -3788,10 +4131,10 @@ directory is the value of @samp{$(datadir)} generated when
 @command{gawk} was configured.  You probably don't need to worry about this,
 though.}
 
-The search path feature is particularly useful for building libraries
+The search path feature is particularly helpful for building libraries
 of useful @command{awk} functions.  The library files can be placed in a
 standard directory in the default path and then specified on
-the command line with a short file name.  Otherwise, the full file name
+the command line with a short @value{FN}.  Otherwise, the full @value{FN}
 would have to be typed for each file.
 
 By using the @option{-i} option, or the @option{--source} and @option{-f} options, your command-line
@@ -3802,17 +4145,20 @@ This is true for both @option{--traditional} and @option{--posix}.
 @xref{Options}.
 
 If the source code is not found after the initial search, the path is searched
-again after adding the default @samp{.awk} suffix to the filename.
+again after adding the default @samp{.awk} suffix to the @value{FN}.
 
 @quotation NOTE
+@c 4/2014:
+@c using @samp{.} to get quotes, since @file{} no longer supplies them.
 To include
 the current directory in the path, either place
-@file{.} explicitly in the path or write a null entry in the
+@samp{.} explicitly in the path or write a null entry in the
 path.  (A null entry is indicated by starting or ending the path with a
-colon or by placing two colons next to each other (@samp{::}).)
+colon or by placing two colons next to each other [@samp{::}].)
 This path search mechanism is similar
 to the shell's.
-@c someday, @cite{The Bourne Again Shell}....
+(See @uref{http://www.gnu.org/software/bash/manual/,
+@cite{The Bourne-Again SHell manual}.})
 
 However, @command{gawk} always looks in the current directory @emph{before}
 searching @env{AWKPATH}, so there is no real reason to include
@@ -3824,7 +4170,7 @@ the current directory in the search path.
 If @env{AWKPATH} is not defined in the
 environment, @command{gawk} places its default search path into
 @code{ENVIRON["AWKPATH"]}. This makes it easy to determine
-the actual search path that @command{gawk} will use
+the actual search path that @command{gawk} used
 from within an @command{awk} program.
 
 While you can change @code{ENVIRON["AWKPATH"]} within your @command{awk}
@@ -3836,19 +4182,18 @@ found, and @command{gawk} no longer needs to use @env{AWKPATH}.
 @node AWKLIBPATH Variable
 @subsection The @env{AWKLIBPATH} Environment Variable
 @cindex @env{AWKLIBPATH} environment variable
-@cindex directories, searching
-@cindex search paths
-@cindex search paths, for shared libraries
+@cindex directories, searching for loadable extensions
+@cindex search paths, for loadable extensions
 @cindex differences in @command{awk} and @command{gawk}, @code{AWKLIBPATH} environment variable
 
 The @env{AWKLIBPATH} environment variable is similar to the @env{AWKPATH}
-variable, but it is used to search for shared libraries specified
-with the @option{-l} option rather than for source files.  If the library
-is not found, the path is searched again after adding the appropriate
-shared library suffix for the platform.  For example, on GNU/Linux systems,
-the suffix @samp{.so} is used.
-The search path specified is also used for libraries loaded via the
-@samp{@@load} keyword (@pxref{Loading Shared Libraries}).
+variable, but it is used to search for loadable extensions (stored as
+system shared libraries) specified with the @option{-l} option rather
+than for source files.  If the extension is not found, the path is
+searched again after adding the appropriate shared library suffix for
+the platform.  For example, on GNU/Linux systems, the suffix @samp{.so}
+is used.  The search path specified is also used for extensions loaded
+via the @code{@@load} keyword (@pxref{Loading Shared Libraries}).
 
 @node Other Environment Variables
 @subsection Other Environment Variables
@@ -3864,7 +4209,7 @@ mode, disabling all traditional and GNU extensions.
 @xref{Options}.
 
 @item GAWK_SOCK_RETRIES
-Controls the number of time @command{gawk} will attempt to
+Controls the number of times @command{gawk} attempts to
 retry a two-way TCP/IP (socket) connection before giving up.
 @xref{TCP/IP Networking}.
 
@@ -3885,9 +4230,18 @@ for use by the @command{gawk} developers for testing and tuning.
 They are subject to change. The variables are:
 
 @table @env
+@item AWKBUFSIZE
+This variable only affects @command{gawk} on POSIX-compliant systems.
+With a value of @samp{exact}, @command{gawk} uses the size of each input
+file as the size of the memory buffer to allocate for I/O. Otherwise,
+the value should be a number, and @command{gawk} uses that number as
+the size of the buffer to allocate.  (When this variable is not set,
+@command{gawk} uses the smaller of the file's size and the ``default''
+blocksize, which is usually the file systems I/O blocksize.)
+
 @item AWK_HASH
 If this variable exists with a value of @samp{gst}, @command{gawk}
-will switch to using the hash function from GNU Smalltalk for
+switches to using the hash function from GNU Smalltalk for
 managing arrays.
 This function may be marginally faster than the standard function.
 
@@ -3912,6 +4266,11 @@ two regexp matchers that @command{gawk} uses internally. (There aren't
 supposed to be differences, but occasionally theory and practice don't
 coordinate with each other.)
 
+@item GAWK_NO_PP_RUN
+If this variable exists, then when invoked with the @option{--pretty-print}
+option, @command{gawk} skips running the program.  This variable will
+not survive into the next major release.
+
 @item GAWK_STACKSIZE
 This specifies the amount by which @command{gawk} should grow its
 internal evaluation stack, when needed.
@@ -3956,13 +4315,13 @@ to @code{EXIT_FAILURE}.
 
 This @value{SECTION} describes a feature that is specific to @command{gawk}.
 
-The @samp{@@include} keyword can be used to read external @command{awk} source
+The @code{@@include} keyword can be used to read external @command{awk} source
 files.  This gives you the ability to split large @command{awk} source files
 into smaller, more manageable pieces, and also lets you reuse common @command{awk}
 code from various @command{awk} scripts.  In other words, you can group
 together @command{awk} functions, used to carry out specific tasks,
 into external files. These files can be used just like function libraries,
-using the @samp{@@include} keyword in conjunction with the @env{AWKPATH}
+using the @code{@@include} keyword in conjunction with the @env{AWKPATH}
 environment variable.  Note that source files may also be included
 using the @option{-i} option.
 
@@ -3996,14 +4355,14 @@ $ @kbd{gawk -f test2}
 @end example
 
 @code{gawk} runs the @file{test2} script which includes @file{test1}
-using the @samp{@@include}
+using the @code{@@include}
 keyword.  So, to include external @command{awk} source files you just
-use @samp{@@include} followed by the name of the file to be included,
+use @code{@@include} followed by the name of the file to be included,
 enclosed in double quotes.
 
 @quotation NOTE
-Keep in mind that this is a language construct and the file name cannot
-be a string variable, but rather just a literal string in double quotes.
+Keep in mind that this is a language construct and the @value{FN} cannot
+be a string variable, but rather just a literal string constant in double quotes.
 @end quotation
 
 The files to be included may be nested; e.g., given a third
@@ -4027,7 +4386,7 @@ $ @kbd{gawk -f test3}
 @print{} This is file test3.
 @end example
 
-The file name can, of course, be a pathname. For example:
+The @value{FN} can, of course, be a pathname. For example:
 
 @example
 @@include "../io_funcs"
@@ -4042,49 +4401,50 @@ or:
 
 @noindent
 are valid. The @code{AWKPATH} environment variable can be of great
-value when using @samp{@@include}. The same rules for the use
+value when using @code{@@include}. The same rules for the use
 of the @code{AWKPATH} variable in command-line file searches
 (@pxref{AWKPATH Variable}) apply to
-@samp{@@include} also.
+@code{@@include} also.
 
 This is very helpful in constructing @command{gawk} function libraries.
 If you have a large script with useful, general purpose @command{awk}
 functions, you can break it down into library files and put those files
 in a special directory.  You can then include those ``libraries,'' using
 either the full pathnames of the files, or by setting the @code{AWKPATH}
-environment variable accordingly and then using @samp{@@include} with
+environment variable accordingly and then using @code{@@include} with
 just the file part of the full pathname. Of course you can have more
 than one directory to keep library files; the more complex the working
 environment is, the more directories you may need to organize the files
 to be included.
 
 Given the ability to specify multiple @option{-f} options, the
-@samp{@@include} mechanism is not strictly necessary.
-However, the @samp{@@include} keyword
+@code{@@include} mechanism is not strictly necessary.
+However, the @code{@@include} keyword
 can help you in constructing self-contained @command{gawk} programs,
 thus reducing the need for writing complex and tedious command lines.
-In particular, @samp{@@include} is very useful for writing CGI scripts
+In particular, @code{@@include} is very useful for writing CGI scripts
 to be run from web pages.
 
 As mentioned in @ref{AWKPATH Variable}, the current directory is always
 searched first for source files, before searching in @env{AWKPATH},
-and this also applies to files named with @samp{@@include}.
+and this also applies to files named with @code{@@include}.
 
 @node Loading Shared Libraries
-@section Loading Shared Libraries Into Your Program
+@section Loading Dynamic Extensions Into Your Program
 
 This @value{SECTION} describes a feature that is specific to @command{gawk}.
 
-The @samp{@@load} keyword can be used to read external @command{awk} shared
-libraries.  This allows you to link in compiled code that may offer superior
+The @code{@@load} keyword can be used to read external @command{awk} extensions
+(stored as system shared libraries).
+This allows you to link in compiled code that may offer superior
 performance and/or give you access to extended capabilities not supported 
 by the @command{awk} language.  The @env{AWKLIBPATH} variable is used to
-search for the shared library.  Using @samp{@@load} is completely equivalent
+search for the extension.  Using @code{@@load} is completely equivalent
 to using the @option{-l} command-line option.
 
-If the shared library is not initially found in @env{AWKLIBPATH}, another
+If the extension is not initially found in @env{AWKLIBPATH}, another
 search is conducted after appending the platform's default shared library
-suffix to the filename.  For example, on GNU/Linux systems, the suffix
+suffix to the @value{FN}.  For example, on GNU/Linux systems, the suffix
 @samp{.so} is used.
 
 @example
@@ -4102,16 +4462,17 @@ $ @kbd{gawk -lordchr 'BEGIN @{print chr(65)@}'}
 
 @noindent
 For command-line usage, the @option{-l} option is more convenient,
-but @samp{@@load} is useful for embedding inside an @command{awk} source file
-that requires access to a shared library.
+but @code{@@load} is useful for embedding inside an @command{awk} source file
+that requires access to an extension.
 
 @ref{Dynamic Extensions}, describes how to write extensions (in C or C++)
-that can be loaded with either @samp{@@load} or the @option{-l} option.
+that can be loaded with either @code{@@load} or the @option{-l} option.
 
 @node Obsolete
 @section Obsolete Options and/or Features
 
-@cindex features, advanced, See advanced features
+@c update this section for each release!
+
 @cindex options, deprecated
 @cindex features, deprecated
 @cindex obsolete features
@@ -4120,12 +4481,9 @@ previous releases of @command{gawk} that are either not available in the
 current version or that are still supported but deprecated (meaning that
 they will @emph{not} be in the next release).
 
-@c update this section for each release!
-
-@cindex @code{PROCINFO} array
 The process-related special files @file{/dev/pid}, @file{/dev/ppid},
 @file{/dev/pgrpid}, and @file{/dev/user} were deprecated in @command{gawk}
-3.1, but still worked.  As of version 4.0, they are no longer
+3.1, but still worked.  As of @value{PVERSION} 4.0, they are no longer
 interpreted specially by @command{gawk}.  (Use @code{PROCINFO} instead;
 see @ref{Auto-set}.)
 
@@ -4148,6 +4506,7 @@ in case some option becomes obsolete in a future version of @command{gawk}.
 @author Obi-Wan
 @end quotation
 
+@cindex shells, sea
 This @value{SECTION} intentionally left
 blank.
 
@@ -4160,7 +4519,7 @@ blank.
 @table @code
 @item -W nostalgia
 @itemx --nostalgia
-Print the message @code{"awk: bailing out near line 1"} and dump core.
+Print the message @samp{awk: bailing out near line 1} and dump core.
 This option was inspired by the common behavior of very early versions of
 Unix @command{awk} and by a t--shirt.
 The message is @emph{not} subject to translation in non-English locales.
@@ -4204,9 +4563,61 @@ long-undocumented ``feature'' of Unix @code{awk}.
 
 @end ignore
 
+@node Invoking Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Use either
+@samp{awk '@var{program}' @var{files}}
+or
+@samp{awk -f @var{program-file} @var{files}}
+to run @command{awk}.
+
+@item
+The three standard @command{awk} options are @option{-f}, @option{-F}
+and @option{-v}.  @command{gawk} supplies these and many others, as well
+as corresponding GNU-style long options.
+
+@item
+Non-option command-line arguments are usually treated as @value{FN}s,
+unless they have the form @samp{@var{var}=@var{value}}, in which case
+they are taken as variable assignments to be performed at that point
+in processing the input.
+
+@item
+All non-option command-line arguments, excluding the program text,
+are placed in the @code{ARGV} array.  Adjusting @code{ARGC} and @code{ARGV}
+affects how @command{awk} processes input.
+
+@item
+You can use a single minus sign (@samp{-}) to refer to standard input
+on the command line.
+
+@item
+@command{gawk} pays attention to a number of environment variables.
+@env{AWKPATH}, @env{AWKLIBPATH}, and @env{POSIXLY_CORRECT} are the
+most important ones.
+
+@item
+@command{gawk}'s exit status conveys information to the program
+that invoked it. Use the @code{exit} statement from within
+an @command{awk} program to set the exit status.
+
+@item
+@command{gawk} allows you to include other @command{awk} source files into
+your program using the @code{@@include} statement and/or the @option{-i}
+and @option{-f} command-line options.
+
+@item
+@command{gawk} allows you to load additional functions written in C
+or C++ using the @code{@@load} statement and/or the @option{-l} option.
+(This advanced feature is described later on in @ref{Dynamic Extensions}.)
+@end itemize
+
 @node Regexp
 @chapter Regular Expressions
-@cindex regexp, See regular expressions
+@cindex regexp
 @c STARTOFRANGE regexp
 @cindex regular expressions
 
@@ -4215,8 +4626,8 @@ set of strings.
 Because regular expressions are such a fundamental part of @command{awk}
 programming, their format and use deserve a separate @value{CHAPTER}.
 
-@cindex forward slash (@code{/})
-@cindex @code{/} (forward slash)
+@cindex forward slash (@code{/}) to enclose regular expressions
+@cindex @code{/} (forward slash) to enclose regular expressions
 A regular expression enclosed in slashes (@samp{/})
 is an @command{awk} pattern that matches every input record whose text
 belongs to that set.
@@ -4242,6 +4653,7 @@ regular expressions work, we present more complicated instances.
 * Case-sensitivity::            How to do case-insensitive matching.
 * Leftmost Longest::            How much text matches.
 * Computed Regexps::            Using Dynamic Regexps.
+* Regexp Summary::              Regular expressions summary.
 @end menu
 
 @node Regexp Usage
@@ -4252,15 +4664,15 @@ A regular expression can be used as a pattern by enclosing it in
 slashes.  Then the regular expression is tested against the
 entire text of each record.  (Normally, it only needs
 to match some part of the text in order to succeed.)  For example, the
-following prints the second field of each record that contains the string
-@samp{foo} anywhere in it:
+following prints the second field of each record where the string
+@samp{li} appears anywhere in the record:
 
 @example
-$ @kbd{awk '/foo/ @{ print $2 @}' BBS-list}
-@print{} 555-1234
+$ @kbd{awk '/li/ @{ print $2 @}' mail-list}
+@print{} 555-5553
+@print{} 555-0542
 @print{} 555-6699
-@print{} 555-6480
-@print{} 555-2127
+@print{} 555-3430
 @end example
 
 @cindex regular expressions, operators
@@ -4272,9 +4684,9 @@ $ @kbd{awk '/foo/ @{ print $2 @}' BBS-list}
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
 @c @cindex operators, @code{!~}
-@cindex @code{if} statement
-@cindex @code{while} statement
-@cindex @code{do}-@code{while} statement
+@cindex @code{if} statement, use of regexps in
+@cindex @code{while} statement, use of regexps in
+@cindex @code{do}-@code{while} statement, use of regexps in
 @c @cindex statements, @code{if}
 @c @cindex statements, @code{while}
 @c @cindex statements, @code{do}
@@ -4333,6 +4745,7 @@ $ @kbd{awk '$1 !~ /J/' inventory-shipped}
 @end example
 
 @cindex regexp constants
+@cindex constant regexps
 @cindex regular expressions, constants, See regexp constants
 When a regexp is enclosed in slashes, such as @code{/foo/}, we call it
 a @dfn{regexp constant}, much like @code{5.27} is a numeric constant and
@@ -4341,7 +4754,7 @@ a @dfn{regexp constant}, much like @code{5.27} is a numeric constant and
 @node Escape Sequences
 @section Escape Sequences
 
-@cindex escape sequences
+@cindex escape sequences, in strings
 @cindex backslash (@code{\}), in escape sequences
 @cindex @code{\} (backslash), in escape sequences
 Some characters cannot be included literally in string constants
@@ -4382,7 +4795,7 @@ A literal backslash, @samp{\}.
 @cindex backslash (@code{\}), @code{\a} escape sequence
 @item \a
 The ``alert'' character, @kbd{Ctrl-g}, ASCII code 7 (BEL).
-(This usually makes some sort of audible noise.)
+(This often makes some sort of audible noise.)
 
 @cindex @code{\} (backslash), @code{\b} escape sequence
 @cindex backslash (@code{\}), @code{\b} escape sequence
@@ -4476,7 +4889,7 @@ shown in the previous list.
 
 To summarize:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The escape sequences in the table above are always processed first,
 for both string constants and regexp constants. This happens very early,
@@ -4506,6 +4919,7 @@ leaves what happens as undefined.  There are two choices:
 
 @c @cindex automatic warnings
 @c @cindex warnings, automatic
+@cindex Brian Kernighan's @command{awk}
 @table @asis
 @item Strip the backslash out
 This is what Brian Kernighan's @command{awk} and @command{gawk} both do.
@@ -4519,6 +4933,7 @@ two backslashes in the string: @samp{FS = @w{"[ \t]+\\|[ \t]+"}}.)
 
 @cindex @command{gawk}, escape sequences
 @cindex Unix @command{awk}, backslashes in escape sequences
+@cindex @command{mawk} utility
 @item Leave the backslash alone
 Some other @command{awk} implementations do this.
 In such implementations, typing @code{"a\qc"} is the same as typing
@@ -4550,6 +4965,7 @@ escape sequences literally when used in regexp constants. Thus,
 @section Regular Expression Operators
 @c STARTOFRANGE regexpo
 @cindex regular expressions, operators
+@cindex metacharacters in regular expressions
 
 You can combine regular expressions with special characters,
 called @dfn{regular expression operators} or @dfn{metacharacters}, to
@@ -4567,10 +4983,11 @@ the very first step in processing regexps.
 Here is a list of metacharacters.  All characters that are not escape
 sequences and that are not listed in the table stand for themselves:
 
-@table @code
-@cindex backslash (@code{\})
-@cindex @code{\} (backslash)
-@item \
+@c Use @asis so the docbook comes out ok. Sigh.
+@table @asis
+@cindex backslash (@code{\}), regexp operator
+@cindex @code{\} (backslash), regexp operator
+@item @code{\}
 This is used to suppress the special meaning of a character when
 matching.  For example, @samp{\$}
 matches the character @samp{$}.
@@ -4579,7 +4996,7 @@ matches the character @samp{$}.
 @cindex Texinfo, chapter beginnings in files
 @cindex @code{^} (caret), regexp operator
 @cindex caret (@code{^}), regexp operator
-@item ^
+@item @code{^}
 This matches the beginning of a string.  For example, @samp{^@@chapter}
 matches @samp{@@chapter} at the beginning of a string and can be used
 to identify chapter beginnings in Texinfo source files.
@@ -4587,29 +5004,31 @@ The @samp{^} is known as an @dfn{anchor}, because it anchors the pattern to
 match only at the beginning of the string.
 
 It is important to realize that @samp{^} does not match the beginning of
-a line embedded in a string.
+a line (the point right after a @samp{\n} newline character) embedded in a string.
 The condition is not true in the following example:
 
 @example
 if ("line1\nLINE 2" ~ /^L/) @dots{}
 @end example
 
-@cindex @code{$} (dollar sign)
-@cindex dollar sign (@code{$})
-@item $
+@cindex @code{$} (dollar sign), regexp operator
+@cindex dollar sign (@code{$}), regexp operator
+@item @code{$}
 This is similar to @samp{^}, but it matches only at the end of a string.
 For example, @samp{p$}
 matches a record that ends with a @samp{p}.  The @samp{$} is an anchor
-and does not match the end of a line embedded in a string.
+and does not match the end of a line
+(the point right before a @samp{\n} newline character)
+embedded in a string.
 The condition in the following example is not true:
 
 @example
 if ("line1\nLINE 2" ~ /1$/) @dots{}
 @end example
 
-@cindex @code{.} (period)
-@cindex period (@code{.})
-@item . @r{(period)}
+@cindex @code{.} (period), regexp operator
+@cindex period (@code{.}), regexp operator
+@item @code{.} (period)
 This matches any single character,
 @emph{including} the newline character.  For example, @samp{.P}
 matches any single character followed by a @samp{P} in a string.  Using
@@ -4624,12 +5043,13 @@ character, which is a character with all bits equal to zero.
 Otherwise, @sc{nul} is just another character. Other versions of @command{awk}
 may not be able to match the @sc{nul} character.
 
-@cindex @code{[]} (square brackets)
-@cindex square brackets (@code{[]})
+@cindex @code{[]} (square brackets), regexp operator
+@cindex square brackets (@code{[]}), regexp operator
 @cindex bracket expressions
 @cindex character sets, See Also bracket expressions
 @cindex character lists, See bracket expressions
-@item [@dots{}]
+@cindex character classes, See bracket expressions
+@item @code{[}@dots{}@code{]}
 This is called a @dfn{bracket expression}.@footnote{In other literature,
 you may see a bracket expression referred to as either a
 @dfn{character set}, a @dfn{character class}, or a @dfn{character list}.}
@@ -4641,7 +5061,7 @@ is given in
 @ref{Bracket Expressions}.
 
 @cindex bracket expressions, complemented
-@item [^ @dots{}]
+@item @code{[^}@dots{}@code{]}
 This is a @dfn{complemented bracket expression}.  The first character after
 the @samp{[} @emph{must} be a @samp{^}.  It matches any characters
 @emph{except} those in the square brackets.  For example, @samp{[^awk]}
@@ -4650,7 +5070,7 @@ or @samp{k}.
 
 @cindex @code{|} (vertical bar)
 @cindex vertical bar (@code{|})
-@item |
+@item @code{|}
 This is the @dfn{alternation operator} and it is used to specify
 alternatives.
 The @samp{|} has the lowest precedence of all the regular
@@ -4661,9 +5081,9 @@ means it matches any string that starts with @samp{P} or contains a digit.
 
 The alternation applies to the largest possible regexps on either side.
 
-@cindex @code{()} (parentheses)
-@cindex parentheses @code{()}
-@item (@dots{})
+@cindex @code{()} (parentheses), regexp operator
+@cindex parentheses @code{()}, regexp operator
+@item @code{(}@dots{}@code{)}
 Parentheses are used for grouping in regular expressions, as in
 arithmetic.  They can be used to concatenate regular expressions
 containing the alternation operator, @samp{|}.  For example,
@@ -4674,7 +5094,7 @@ explained further on in this list.)
 
 @cindex @code{*} (asterisk), @code{*} operator, as regexp operator
 @cindex asterisk (@code{*}), @code{*} operator, as regexp operator
-@item *
+@item @code{*}
 This symbol means that the preceding regular expression should be
 repeated as many times as necessary to find a match.  For example, @samp{ph*}
 applies the @samp{*} symbol to the preceding @samp{h} and looks for matches
@@ -4690,13 +5110,13 @@ prints every record in @file{sample} containing a string of the form
 Notice the escaping of the parentheses by preceding them
 with backslashes.
 
-@cindex @code{+} (plus sign)
-@cindex plus sign (@code{+})
-@item +
+@cindex @code{+} (plus sign), regexp operator
+@cindex plus sign (@code{+}), regexp operator
+@item @code{+}
 This symbol is similar to @samp{*}, except that the preceding expression must be
 matched at least once.  This means that @samp{wh+y}
 would match @samp{why} and @samp{whhy}, but not @samp{wy}, whereas
-@samp{wh*y} would match all three of these strings.
+@samp{wh*y} would match all three.
 The following is a simpler
 way of writing the last @samp{*} example:
 
@@ -4704,17 +5124,17 @@ way of writing the last @samp{*} example:
 awk '/\(c[ad]+r x\)/ @{ print @}' sample
 @end example
 
-@cindex @code{?} (question mark) regexp operator
-@cindex question mark (@code{?}) regexp operator
-@item ?
+@cindex @code{?} (question mark), regexp operator
+@cindex question mark (@code{?}), regexp operator
+@item @code{?}
 This symbol is similar to @samp{*}, except that the preceding expression can be
 matched either once or not at all.  For example, @samp{fe?d}
 matches @samp{fed} and @samp{fd}, but nothing else.
 
-@cindex interval expressions
-@item @{@var{n}@}
-@itemx @{@var{n},@}
-@itemx @{@var{n},@var{m}@}
+@cindex interval expressions, regexp operator
+@item @code{@{}@var{n}@code{@}}
+@itemx @code{@{}@var{n}@code{,@}}
+@itemx @code{@{}@var{n}@code{,}@var{m}@code{@}}
 One or two numbers inside braces denote an @dfn{interval expression}.
 If there is one number in the braces, the preceding regexp is repeated
 @var{n} times.
@@ -4745,7 +5165,7 @@ constants,
 @command{gawk} did @emph{not} match interval expressions
 in regexps.
 
-However, beginning with version 4.0,
+However, beginning with @value{PVERSION} 4.0,
 @command{gawk} does match interval expressions by default.
 This is because compatibility with POSIX has become more
 important to most @command{gawk} users than compatibility with
@@ -4788,6 +5208,7 @@ expressions are not available in regular expressions.
 @cindex bracket expressions
 @cindex bracket expressions, range expressions
 @cindex range expressions (regexps)
+@cindex character lists in regular expression
 
 As mentioned earlier, a bracket expression matches any character amongst
 those listed between the opening and closing square brackets.
@@ -4889,8 +5310,8 @@ These sequences are:
 @item Collating symbols
 Multicharacter collating elements enclosed between
 @samp{[.} and @samp{.]}.  For example, if @samp{ch} is a collating element,
-then @code{[[.ch.]]} is a regexp that matches this collating element, whereas
-@code{[ch]} is a regexp that matches either @samp{c} or @samp{h}.
+then @samp{[[.ch.]]} is a regexp that matches this collating element, whereas
+@samp{[ch]} is a regexp that matches either @samp{c} or @samp{h}.
 
 @cindex bracket expressions, equivalence classes
 @item Equivalence classes
@@ -4898,7 +5319,7 @@ Locale-specific names for a list of
 characters that are equal. The name is enclosed between
 @samp{[=} and @samp{=]}.
 For example, the name @samp{e} might be used to represent all of
-``e,'' ``@`e,'' and ``@'e.'' In this case, @code{[[=e=]]} is a regexp
+``e,'' ``@`e,'' and ``@'e.'' In this case, @samp{[[=e=]]} is a regexp
 that matches any of @samp{e}, @samp{@'e}, or @samp{@`e}.
 @end table
 
@@ -4942,7 +5363,7 @@ or underscores (@samp{_}):
 @item \s
 Matches any whitespace character.
 Think of it as shorthand for
-@w{@code{[[:space:]]}}.
+@w{@samp{[[:space:]]}}.
 
 @c @cindex operators, @code{\S} (@command{gawk})
 @cindex backslash (@code{\}), @code{\S} operator (@command{gawk})
@@ -4950,7 +5371,7 @@ Think of it as shorthand for
 @item \S
 Matches any character that is not whitespace.
 Think of it as shorthand for
-@w{@code{[^[:space:]]}}.
+@w{@samp{[^[:space:]]}}.
 
 @c @cindex operators, @code{\w} (@command{gawk})
 @cindex backslash (@code{\}), @code{\w} operator (@command{gawk})
@@ -4958,7 +5379,7 @@ Think of it as shorthand for
 @item \w
 Matches any word-constituent character---that is, it matches any
 letter, digit, or underscore. Think of it as shorthand for
-@w{@code{[[:alnum:]_]}}.
+@w{@samp{[[:alnum:]_]}}.
 
 @c @cindex operators, @code{\W} (@command{gawk})
 @cindex backslash (@code{\}), @code{\W} operator (@command{gawk})
@@ -4966,7 +5387,7 @@ letter, digit, or underscore. Think of it as shorthand for
 @item \W
 Matches any character that is not word-constituent.
 Think of it as shorthand for
-@w{@code{[^[:alnum:]_]}}.
+@w{@samp{[^[:alnum:]_]}}.
 
 @c @cindex operators, @code{\<} (@command{gawk})
 @cindex backslash (@code{\}), @code{\<} operator (@command{gawk})
@@ -5027,10 +5448,10 @@ Matches the empty string at the
 end of a buffer (string).
 @end table
 
-@cindex @code{^} (caret)
-@cindex caret (@code{^})
-@cindex @code{?} (question mark) regexp operator
-@cindex question mark (@code{?}) regexp operator
+@cindex @code{^} (caret), regexp operator
+@cindex caret (@code{^}), regexp operator
+@cindex @code{?} (question mark), regexp operator
+@cindex question mark (@code{?}), regexp operator
 Because @samp{^} and @samp{$} always work in terms of the beginning
 and end of strings, these operators don't add any new capabilities
 for @command{awk}.  They are provided for compatibility with other
@@ -5047,11 +5468,8 @@ GNU operators, but this was deemed too confusing. The current
 method of using @samp{\y} for the GNU @samp{\b} appears to be the
 lesser of two evils.
 
-@c NOTE!!! Keep this in sync with the same table in the summary appendix!
-@c
-@c Should really do this with file inclusion.
 @cindex regular expressions, @command{gawk}, command-line options
-@cindex @command{gawk}, command-line options
+@cindex @command{gawk}, command-line options, and regular expressions
 The various command-line options
 (@pxref{Options})
 control how @command{gawk} interprets characters in regexps:
@@ -5065,8 +5483,10 @@ previously described
 GNU regexp operators.
 @end ifnotinfo
 @ifnottex
+@ifnotdocbook
 GNU regexp operators described
 in @ref{Regexp Operators}.
+@end ifnotdocbook
 @end ifnottex
 
 @item @code{--posix}
@@ -5074,10 +5494,11 @@ Only POSIX regexps are supported; the GNU operators are not special
 (e.g., @samp{\w} matches a literal @samp{w}).  Interval expressions
 are allowed.
 
+@cindex Brian Kernighan's @command{awk}
 @item @code{--traditional}
 Traditional Unix @command{awk} regexps are matched. The GNU operators
 are not special, and interval expressions are not available.
-The POSIX character classes (@code{[[:alnum:]]}, etc.) are supported,
+The POSIX character classes (@samp{[[:alnum:]]}, etc.) are supported,
 as Brian Kernighan's @command{awk} does support them.
 Characters described by octal and hexadecimal escape sequences are
 treated literally, even if they represent regexp metacharacters.
@@ -5129,16 +5550,18 @@ This works in any POSIX-compliant @command{awk}.
 @cindex tilde (@code{~}), @code{~} operator
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
-@cindex @code{IGNORECASE} variable
+@cindex @code{IGNORECASE} variable, with @code{~} and @code{!~} operators
 @cindex @command{gawk}, @code{IGNORECASE} variable in
 @c @cindex variables, @code{IGNORECASE}
 Another method, specific to @command{gawk}, is to set the variable
 @code{IGNORECASE} to a nonzero value (@pxref{Built-in Variables}).
 When @code{IGNORECASE} is not zero, @emph{all} regexp and string
-operations ignore case.  Changing the value of
-@code{IGNORECASE} dynamically controls the case-sensitivity of the
-program as it runs.  Case is significant by default because
-@code{IGNORECASE} (like most variables) is initialized to zero:
+operations ignore case.
+
+Changing the value of @code{IGNORECASE} dynamically controls the
+case-sensitivity of the program as it runs.  Case is significant by
+default because @code{IGNORECASE} (like most variables) is initialized
+to zero:
 
 @example
 x = "aB"
@@ -5168,9 +5591,6 @@ case-sensitivity on or off for all the rules at once.
 Setting @code{IGNORECASE} from the command line is a way to make
 a program case-insensitive without having to edit it.
 
-Both regexp and string comparison
-operations are affected by @code{IGNORECASE}.
-
 @c @cindex ISO 8859-1
 @c @cindex ISO Latin-1
 In multibyte locales,
@@ -5248,7 +5668,7 @@ regexp constant (i.e., a string of characters between slashes).  It may
 be any expression.  The expression is evaluated and converted to a string
 if necessary; the contents of the string are then used as the
 regexp.  A regexp computed in this way is called a @dfn{dynamic
-regexp}:
+regexp} or a @dfn{computed regexp}:
 
 @example
 BEGIN @{ digits_regexp = "[[:digit:]]+" @}
@@ -5294,7 +5714,7 @@ Given that you can use both regexp and string constants to describe
 regular expressions, which should you use?  The answer is ``regexp
 constants,'' for several reasons:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 String constants are more complicated to write and
 more difficult to read. Using regexp constants makes your programs
@@ -5317,7 +5737,7 @@ intend a regexp match.
 @cindex regular expressions, dynamic, with embedded newlines
 @cindex newlines, in dynamic regexps
 
-Some commercial versions of @command{awk} do not allow the newline
+Some versions of @command{awk} do not allow the newline
 character to be used inside a bracket expression for a dynamic regexp:
 
 @example
@@ -5344,12 +5764,59 @@ occur often in practice, but it's worth noting for future reference.
 @end sidebar
 @c ENDOFRANGE dregexp
 @c ENDOFRANGE regexpd
+
+@node Regexp Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Regular expressions describe sets of strings to be matched.
+In @command{awk}, regular expression constants are written enclosed
+between slashes: @code{/}@dots{}@code{/}.
+
+@item
+Regexp constants may be used by standalone in patterns and
+in conditional expressions, or as part of matching expressions
+using the @samp{~} and @samp{!~} operators.
+
+@item
+Escape sequences let you represent non-printable characters and
+also let you represent regexp metacharacters as literal characters
+to be matched.
+
+@item
+Regexp operators provide grouping, alternation and repetition.
+
+@item
+Bracket expressions give you a shorthand for specifying sets
+of characters that can match at a particular point in a regexp.
+Within bracket expressions, POSIX character classes let you specify
+certain groups of characters in a locale-independent fashion.
+
+@item
+@command{gawk}'s @code{IGNORECASE} variable lets you control the
+case sensitivity of regexp matching.  In other @command{awk}
+versions, use @code{tolower()} or @code{toupper()}.
+
+@item
+Regular expressions match the leftmost longest text in the string being
+matched.  This matters for cases where you need to know the extent of
+the match, such as for text substitution and when the record separator
+is a regexp.
+
+@item
+Matching expressions may use dynamic regexps; that is string values
+treated as regular expressions.
+
+@end itemize
+
 @c ENDOFRANGE regexp
 
 @node Reading Files
 @chapter Reading Input Files
 
 @c STARTOFRANGE infir
+@cindex reading input files
 @cindex input files, reading
 @cindex input files
 @cindex @code{FILENAME} variable
@@ -5392,6 +5859,8 @@ used with it do not have to be named on the @command{awk} command line
 * Read Timeout::                Reading input with a timeout.
 * Command line directories::    What happens if you put a directory on the
                                 command line.
+* Input Summary::               Input summary.
+* Input Exercises::             Exercises.
 @end menu
 
 @node Records
@@ -5411,9 +5880,17 @@ so far
 from the current input file.  This value is stored in a
 built-in variable called @code{FNR}.  It is reset to zero when a new
 file is started.  Another built-in variable, @code{NR}, records the total
-number of input records read so far from all data files.  It starts at zero,
+number of input records read so far from all @value{DF}s.  It starts at zero,
 but is never automatically reset to zero.
 
+@menu
+* awk split records::           How standard @command{awk} splits records.
+* gawk split records::          How @command{gawk} splits records.
+@end menu
+
+@node awk split records
+@subsection Record Splitting With Standard @command{awk}
+
 @cindex separators, for records
 @cindex record separators
 Records are separated by a character called the @dfn{record separator}.
@@ -5436,69 +5913,80 @@ To do this, use the special @code{BEGIN} pattern
 (@pxref{BEGIN/END}).
 For example:
 
-@cindex @code{BEGIN} pattern
 @example
-awk 'BEGIN @{ RS = "/" @}
-     @{ print $0 @}' BBS-list
+awk 'BEGIN @{ RS = "u" @}
+     @{ print $0 @}' mail-list
 @end example
 
 @noindent
-changes the value of @code{RS} to @code{"/"}, before reading any input.
-This is a string whose first character is a slash; as a result, records
-are separated by slashes.  Then the input file is read, and the second
+changes the value of @code{RS} to @samp{u}, before reading any input.
+This is a string whose first character is the letter ``u;'' as a result, records
+are separated by the letter ``u.''  Then the input file is read, and the second
 rule in the @command{awk} program (the action with no pattern) prints each
 record.  Because each @code{print} statement adds a newline at the end of
 its output, this @command{awk} program copies the input
-with each slash changed to a newline.  Here are the results of running
-the program on @file{BBS-list}:
-
-@example
-$ @kbd{awk 'BEGIN @{ RS = "/" @}}
->      @kbd{@{ print $0 @}' BBS-list}
-@print{} aardvark     555-5553     1200
-@print{} 300          B
-@print{} alpo-net     555-3412     2400
-@print{} 1200
-@print{} 300     A
-@print{} barfly       555-7685     1200
-@print{} 300          A
-@print{} bites        555-1675     2400
-@print{} 1200
-@print{} 300     A
-@print{} camelot      555-0542     300               C
-@print{} core         555-2912     1200
-@print{} 300          C
-@print{} fooey        555-1234     2400
-@print{} 1200
-@print{} 300     B
-@print{} foot         555-6699     1200
-@print{} 300          B
-@print{} macfoo       555-6480     1200
-@print{} 300          A
-@print{} sdace        555-3430     2400
-@print{} 1200
-@print{} 300     A
-@print{} sabafoo      555-2127     1200
-@print{} 300          C
-@print{}
+with each @samp{u} changed to a newline.  Here are the results of running
+the program on @file{mail-list}:
+
+@example
+$ @kbd{awk 'BEGIN @{ RS = "u" @}}
+>      @kbd{@{ print $0 @}' mail-list}
+@print{} Amelia       555-5553     amelia.zodiac
+@print{} sq
+@print{} e@@gmail.com    F
+@print{} Anthony      555-3412     anthony.assert
+@print{} ro@@hotmail.com   A
+@print{} Becky        555-7685     becky.algebrar
+@print{} m@@gmail.com      A
+@print{} Bill         555-1675     bill.drowning@@hotmail.com       A
+@print{} Broderick    555-0542     broderick.aliq
+@print{} otiens@@yahoo.com R
+@print{} Camilla      555-2912     camilla.inf
+@print{} sar
+@print{} m@@skynet.be     R
+@print{} Fabi
+@print{} s       555-1234     fabi
+@print{} s.
+@print{} ndevicesim
+@print{} s@@
+@print{} cb.ed
+@print{}     F
+@print{} J
+@print{} lie        555-6699     j
+@print{} lie.perscr
+@print{} tabor@@skeeve.com   F
+@print{} Martin       555-6480     martin.codicib
+@print{} s@@hotmail.com    A
+@print{} Sam
+@print{} el       555-3430     sam
+@print{} el.lanceolis@@sh
+@print{} .ed
+@print{}         A
+@print{} Jean-Pa
+@print{} l    555-2127     jeanpa
+@print{} l.campanor
+@print{} m@@ny
+@print{} .ed
+@print{}      R
+@print{} 
 @end example
 
 @noindent
-Note that the entry for the @samp{camelot} BBS is not split.
-In the original data file
+Note that the entry for the name @samp{Bill} is not split.
+In the original @value{DF}
 (@pxref{Sample Data Files}),
 the line looks like this:
 
 @example
-camelot      555-0542     300               C
+Bill         555-1675     bill.drowning@@hotmail.com       A
 @end example
 
 @noindent
-It has one baud rate only, so there are no slashes in the record,
-unlike the others which have two or more baud rates.
-In fact, this record is treated as part of the record
-for the @samp{core} BBS; the newline separating them in the output
-is the original newline in the data file, not the one added by
+It contains no @samp{u} so there is no reason to split the record,
+unlike the others which have one or more occurrences of the @samp{u}.
+In fact, this record is treated as part of the previous record;
+the newline separating them in the output
+is the original newline in the @value{DF}, not the one added by
 @command{awk} when it printed the record!
 
 @cindex record separators, changing
@@ -5508,14 +5996,17 @@ using the variable-assignment feature
 (@pxref{Other Arguments}):
 
 @example
-awk '@{ print $0 @}' RS="/" BBS-list
+awk '@{ print $0 @}' RS="u" mail-list
 @end example
 
 @noindent
-This sets @code{RS} to @samp{/} before processing @file{BBS-list}.
+This sets @code{RS} to @samp{u} before processing @file{mail-list}.
 
-Using an unusual character such as @samp{/} for the record separator
-produces correct behavior in the vast majority of cases.
+Using an alphabetic character such as @samp{u} for the record separator
+is highly likely to produce strange results.
+Using an unusual character such as @samp{/} is more likely to
+produce correct behavior in the majority of cases, but there
+are no guarantees. The moral is: Know Your Data.
 
 There is one unusual case, that occurs when @command{gawk} is
 being fully POSIX-compliant (@pxref{Options}).
@@ -5537,6 +6028,7 @@ Reaching the end of an input file terminates the current input record,
 even if the last character in the file is not the character in @code{RS}.
 @value{DARKCORNER}
 
+@cindex empty strings
 @cindex null strings
 @cindex strings, empty, See null strings
 The empty string @code{""} (a string without any characters)
@@ -5562,6 +6054,9 @@ After the end of the record has been determined, @command{gawk}
 sets the variable @code{RT} to the text in the input that matched
 @code{RS}.
 
+@node gawk split records
+@subsection Record Splitting With @command{gawk}
+
 @cindex common extensions, @code{RS} as a regexp
 @cindex extensions, common@comma{} @code{RS} as a regexp
 When using @command{gawk},
@@ -5635,12 +6130,11 @@ In compatibility mode, only the first character of the value of
 
 @sidebar @code{RS = "\0"} Is Not Portable
 @cindex portability, data files as single record
-There are times when you might want to treat an entire data file as a
+There are times when you might want to treat an entire @value{DF} as a
 single record.  The only way to make this happen is to give @code{RS}
 a value that you know doesn't occur in the input file.  This is hard
 to do in a general way, such that a program always works for arbitrary
 input files.
-@c can you say `understatement' boys and girls?
 
 You might think that for text files, the @sc{nul} character, which
 consists of a character with all bits equal to zero, is a good
@@ -5653,21 +6147,27 @@ BEGIN @{ RS = "\0" @}  # whole file becomes one record?
 @cindex differences in @command{awk} and @command{gawk}, strings, storing
 @command{gawk} in fact accepts this, and uses the @sc{nul}
 character for the record separator.
+This works for certain special files, such as @file{/proc/environ} on
+GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
 However, this usage is @emph{not} portable
-to other @command{awk} implementations.
+to most other @command{awk} implementations.
 
 @cindex dark corner, strings, storing
-All other @command{awk} implementations@footnote{At least that we know
+Almost all other @command{awk} implementations@footnote{At least that we know
 about.} store strings internally as C-style strings.  C strings use the
 @sc{nul} character as the string terminator.  In effect, this means that
 @samp{RS = "\0"} is the same as @samp{RS = ""}.
 @value{DARKCORNER}
 
+It happens that recent versions of @command{mawk} can use the @sc{nul}
+character as a record separator. However, this is a special case:
+@command{mawk} does not allow embedded @sc{nul} characters in strings.
+
 @cindex records, treating files as
-@cindex files, as single records
-The best way to treat a whole file as a single record is to
-simply read the file in, one record at a time, concatenating each
-record onto the end of the previous ones.
+@cindex treating files, as single records
+@xref{Readfile Function}, for an interesting, portable way to read
+whole files.  If you are using @command{gawk}, see @ref{Extension Sample
+Readfile}, for another option.
 @end sidebar
 @c ENDOFRANGE inspl
 @c ENDOFRANGE recspl
@@ -5703,7 +6203,7 @@ simple @command{awk} programs so powerful.
 @cindex @code{$} (dollar sign), @code{$} field operator
 @cindex dollar sign (@code{$}), @code{$} field operator
 @cindex field operators@comma{} dollar sign as
-A dollar-sign (@samp{$}) is used
+You use a dollar-sign (@samp{$})
 to refer to a field in an @command{awk} program,
 followed by the number of the field you want.  Thus, @code{$1}
 refers to the first field, @code{$2} to the second, and so on.
@@ -5734,36 +6234,34 @@ one (such as @code{$8} when the record has only seven fields), you get
 the empty string.  (If used in a numeric operation, you get zero.)
 
 The use of @code{$0}, which looks like a reference to the ``zero-th'' field, is
-a special case: it represents the whole input record
+a special case: it represents the whole input record. Use it
 when you are not interested in specific fields.
 Here are some more examples:
 
 @example
-$ @kbd{awk '$1 ~ /foo/ @{ print $0 @}' BBS-list}
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sabafoo      555-2127     1200/300          C
+$ @kbd{awk '$1 ~ /li/ @{ print $0 @}' mail-list}
+@print{} Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+@print{} Julie        555-6699     julie.perscrutabor@@skeeve.com   F
 @end example
 
 @noindent
-This example prints each record in the file @file{BBS-list} whose first
-field contains the string @samp{foo}.  The operator @samp{~} is called a
+This example prints each record in the file @file{mail-list} whose first
+field contains the string @samp{li}.  The operator @samp{~} is called a
 @dfn{matching operator}
 (@pxref{Regexp Usage});
 it tests whether a string (here, the field @code{$1}) matches a given regular
 expression.
 
 By contrast, the following example
-looks for @samp{foo} in @emph{the entire record} and prints the first
+looks for @samp{li} in @emph{the entire record} and prints the first
 field and the last field for each matching input record:
 
 @example
-$ @kbd{awk '/foo/ @{ print $1, $NF @}' BBS-list}
-@print{} fooey B
-@print{} foot B
-@print{} macfoo A
-@print{} sabafoo C
+$ @kbd{awk '/li/ @{ print $1, $NF @}' mail-list}
+@print{} Amelia F
+@print{} Broderick R
+@print{} Julie F
+@print{} Samuel A
 @end example
 @c ENDOFRANGE fiex
 
@@ -5772,7 +6270,7 @@ $ @kbd{awk '/foo/ @{ print $1, $NF @}' BBS-list}
 @cindex fields, numbers
 @cindex field numbers
 
-The number of a field does not need to be a constant.  Any expression in
+A field number need not be a constant.  Any expression in
 the @command{awk} language can be used after a @samp{$} to refer to a
 field.  The value of the expression specifies the field number.  If the
 value is a string, rather than a number, it is converted to a number.
@@ -5791,7 +6289,7 @@ the record has fewer than 20 fields, so this prints a blank line.
 Here is another example of using expressions as field numbers:
 
 @example
-awk '@{ print $(2*2) @}' BBS-list
+awk '@{ print $(2*2) @}' mail-list
 @end example
 
 @command{awk} evaluates the expression @samp{(2*2)} and uses
@@ -5799,9 +6297,13 @@ its value as the number of the field to print.  The @samp{*} sign
 represents multiplication, so the expression @samp{2*2} evaluates to four.
 The parentheses are used so that the multiplication is done before the
 @samp{$} operation; they are necessary whenever there is a binary
-operator in the field-number expression.  This example, then, prints the
-hours of operation (the fourth field) for every line of the file
-@file{BBS-list}.  (All of the @command{awk} operators are listed, in
+operator@footnote{A @dfn{binary operator}, such as @samp{*} for
+multiplication, is one that takes two operands. The distinction
+is required, since @command{awk} also has unary (one-operand)
+and ternary (three-operand) operators.}
+in the field-number expression.  This example, then, prints the
+type of relationship (the fourth field) for every line of the file
+@file{mail-list}.  (All of the @command{awk} operators are listed, in
 order of decreasing precedence, in
 @ref{Precedence}.)
 
@@ -5849,7 +6351,7 @@ Then it prints the original and new values for field three.
 (Someone in the warehouse made a consistent mistake while inventorying
 the red boxes.)
 
-For this to work, the text in field @code{$3} must make sense
+For this to work, the text in @code{$3} must make sense
 as a number; the string of characters must be converted to a number
 for the computer to do arithmetic on it.  The number resulting
 from the subtraction is converted back to a string of characters that
@@ -5940,7 +6442,7 @@ $ @kbd{echo a b c d | awk '@{ OFS = ":"; $2 = ""}
 @end example
 
 @noindent
-The field is still there; it just has an empty value, denoted by
+The field is still there; it just has an empty value, delimited by
 the two colons between @samp{a} and @samp{c}.
 This example shows what happens if you create a new field:
 
@@ -6024,6 +6526,7 @@ with a statement such as @samp{$1 = $1}, as described earlier.
 * Regexp Field Splitting::       Using regexps as the field separator.
 * Single Character Fields::      Making each character a separate field.
 * Command Line Field Separator:: Setting @code{FS} from the command-line.
+* Full Line Fields::             Making the full line be a single field.
 * Field Splitting Summary::      Some final points and a summary table.
 @end menu
 
@@ -6191,7 +6694,7 @@ $ @kbd{echo ' a  b  c  d ' | awk 'BEGIN @{ FS = "[ \t\n]+" @}}
 @cindex null strings
 @cindex strings, null
 @cindex empty strings, See null strings
-In this case, the first field is @dfn{null} or empty.
+In this case, the first field is null, or empty.
 
 The stripping of leading and trailing whitespace also comes into
 play whenever @code{$0} is recomputed.  For instance, study this pipeline:
@@ -6211,7 +6714,7 @@ was ignored when finding @code{$1}, it is not part of the new @code{$0}.
 Finally, the last @code{print} statement prints the new @code{$0}.
 
 @cindex @code{FS}, containing @code{^}
-@cindex @code{^}, in @code{FS}
+@cindex @code{^} (caret), in @code{FS}
 @cindex dark corner, @code{^}, in @code{FS}
 There is an additional subtlety to be aware of when using regular expressions
 for field splitting.
@@ -6222,6 +6725,7 @@ different @command{awk} versions answer this question differently, and you
 should not rely on any specific behavior in your programs.
 @value{DARKCORNER}
 
+@cindex Brian Kernighan's @command{awk}
 As a point of information, Brian Kernighan's @command{awk} allows @samp{^}
 to match only at the beginning of the record. @command{gawk}
 also works this way. For example:
@@ -6265,7 +6769,7 @@ $ @kbd{echo a b | gawk 'BEGIN @{ FS = "" @}}
 @end example
 
 @cindex dark corner, @code{FS} as null string
-@cindex FS variable, as null string
+@cindex @code{FS} variable, as null string
 Traditionally, the behavior of @code{FS} equal to @code{""} was not defined.
 In this case, most versions of Unix @command{awk} simply treat the entire record
 as only having one field.
@@ -6277,10 +6781,8 @@ behaves this way.
 
 @node Command Line Field Separator
 @subsection Setting @code{FS} from the Command Line
-@cindex @code{-F} option
-@cindex options, command-line
-@cindex command line, options
-@cindex field separators, on command line
+@cindex @option{-F} option, command line
+@cindex field separator, on command line
 @cindex command line, @code{FS} on@comma{} setting
 @cindex @code{FS} variable, setting from command line
 
@@ -6330,68 +6832,75 @@ figures that you really want your fields to be separated with TABs and
 not @samp{t}s.  Use @samp{-v FS="t"} or @samp{-F"[t]"} on the command line
 if you really do want to separate your fields with @samp{t}s.
 
-As an example, let's use an @command{awk} program file called @file{baud.awk}
-that contains the pattern @code{/300/} and the action @samp{print $1}:
+As an example, let's use an @command{awk} program file called @file{edu.awk}
+that contains the pattern @code{/edu/} and the action @samp{print $1}:
 
 @example
-/300/   @{ print $1 @}
+/edu/   @{ print $1 @}
 @end example
 
 Let's also set @code{FS} to be the @samp{-} character and run the
-program on the file @file{BBS-list}.  The following command prints a
-list of the names of the bulletin boards that operate at 300 baud and
+program on the file @file{mail-list}.  The following command prints a
+list of the names of the people that work at or attend a university, and
 the first three digits of their phone numbers:
 
-@c tweaked to make the tex output look better in @smallbook
 @example
-$ @kbd{awk -F- -f baud.awk BBS-list}
-@print{} aardvark     555
-@print{} alpo
-@print{} barfly       555
-@print{} bites        555
-@print{} camelot      555
-@print{} core         555
-@print{} fooey        555
-@print{} foot         555
-@print{} macfoo       555
-@print{} sdace        555
-@print{} sabafoo      555
+$ @kbd{awk -F- -f edu.awk mail-list}
+@print{} Fabius       555
+@print{} Samuel       555
+@print{} Jean
 @end example
 
 @noindent
-Note the second line of output.  The second line
+Note the third line of output.  The third line
 in the original file looked like this:
 
 @example
-alpo-net     555-3412     2400/1200/300     A
+Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @end example
 
-The @samp{-} as part of the system's name was used as the field
+The @samp{-} as part of the person's name was used as the field
 separator, instead of the @samp{-} in the phone number that was
 originally intended.  This demonstrates why you have to be careful in
 choosing your field and record separators.
 
 @cindex Unix @command{awk}, password files@comma{} field separators and
-Perhaps the most common use of a single character as the field
-separator occurs when processing the Unix system password file.
-On many Unix systems, each user has a separate entry in the system password
-file, one line per user.  The information in these lines is separated
-by colons.  The first field is the user's login name and the second is
-the user's (encrypted or shadow) password.  A password file entry might look
-like this:
+Perhaps the most common use of a single character as the field separator
+occurs when processing the Unix system password file.  On many Unix
+systems, each user has a separate entry in the system password file, one
+line per user.  The information in these lines is separated by colons.
+The first field is the user's login name and the second is the user's
+encrypted or shadow password.  (A shadow password is indicated by the
+presence of a single @samp{x} in the second field.)  A password file
+entry might look like this:
 
 @cindex Robbins, Arnold
 @example
-arnold:xyzzy:2076:10:Arnold Robbins:/home/arnold:/bin/bash
+arnold:x:2076:10:Arnold Robbins:/home/arnold:/bin/bash
 @end example
 
 The following program searches the system password file and prints
-the entries for users who have no password:
+the entries for users whose full name is not indicated:
 
 @example
-awk -F: '$2 == ""' /etc/passwd
+awk -F: '$5 == ""' /etc/passwd
 @end example
 
+@node Full Line Fields
+@subsection Making The Full Line Be A Single Field
+
+Occasionally, it's useful to treat the whole input line as a
+single field.  This can be done easily and portably simply by
+setting @code{FS} to @code{"\n"} (a newline).@footnote{Thanks to
+Andrew Schorr for this tip.}
+
+@example
+awk -F'\n' '@var{program}' @var{files @dots{}}
+@end example
+
+@noindent
+When you do this, @code{$1} is the same as @code{$0}.
+
 @node Field Splitting Summary
 @subsection Field-Splitting Summary
 
@@ -6432,7 +6941,7 @@ POSIX standard.)
 @sidebar Changing @code{FS} Does Not Affect the Fields
 
 @cindex POSIX @command{awk}, field separators and
-@cindex field separators, POSIX and
+@cindex field separator, POSIX and
 According to the POSIX standard, @command{awk} is supposed to behave
 as if each record is split into fields at the time it is read.
 In particular, this means that if you change the value of @code{FS}
@@ -6502,19 +7011,11 @@ will take effect.
 @node Constant Size
 @section Reading Fixed-Width Data
 
-@ifnotinfo
 @quotation NOTE
 This @value{SECTION} discusses an advanced
 feature of @command{gawk}.  If you are a novice @command{awk} user,
 you might want to skip it on the first reading.
 @end quotation
-@end ifnotinfo
-
-@ifinfo
-(This @value{SECTION} discusses an advanced feature of @command{awk}.
-If you are a novice @command{awk} user, you might want to skip it on
-the first reading.)
-@end ifinfo
 
 @cindex data, fixed-width
 @cindex fixed-width data
@@ -6612,10 +7113,6 @@ program for processing such data could use the @code{FIELDWIDTHS} feature
 to simplify reading the data.  (Of course, getting @command{gawk} to run on
 a system with card readers is another story!)
 
-@ignore
-Exercise: Write a ballot card reading program
-@end ignore
-
 @cindex @command{gawk}, splitting fields and
 Assigning a value to @code{FS} causes @command{gawk} to use
 @code{FS} for field splitting again.  Use @samp{FS = FS} to make this happen,
@@ -6632,7 +7129,7 @@ if (PROCINFO["FS"] == "FS")
 else if  (PROCINFO["FS"] == "FIELDWIDTHS")
     @var{fixed-width field splitting} @dots{}
 else
-    @var{content-based field splitting} @dots{} (see next @value{SECTION})
+    @var{content-based field splitting} @dots{} @ii{(see next @value{SECTION})}
 @end example
 
 This information is useful when writing a function
@@ -6644,19 +7141,11 @@ for an example of such a function).
 @node Splitting By Content
 @section Defining Fields By Content
 
-@ifnotinfo
 @quotation NOTE
 This @value{SECTION} discusses an advanced
 feature of @command{gawk}.  If you are a novice @command{awk} user,
 you might want to skip it on the first reading.
 @end quotation
-@end ifnotinfo
-
-@ifinfo
-(This @value{SECTION} discusses an advanced feature of @command{awk}.
-If you are a novice @command{awk} user, you might want to skip it on
-the first reading.)
-@end ifinfo
 
 @cindex advanced features, specifying field content
 Normally, when using @code{FS}, @command{gawk} defines the fields as the
@@ -6754,7 +7243,7 @@ the double quotes.  @command{gawk} provides no way to deal with this.
 Since there is no formal specification for CSV data, there isn't much
 more to be done;
 the @code{FPAT} mechanism provides an elegant solution for the majority
-of cases, and the @command{gawk} maintainer is satisfied with that. 
+of cases, and the @command{gawk} developers are satisfied with that. 
 @end quotation
 
 As written, the regexp used for @code{FPAT} requires that each field
@@ -6771,6 +7260,7 @@ available for splitting regular strings (@pxref{String Functions}).
 @node Multiple Line
 @section Multiple-Line Records
 
+@cindex multiple-line records
 @c STARTOFRANGE recm
 @cindex records, multiline
 @c STARTOFRANGE imr
@@ -6815,14 +7305,15 @@ the first nonblank line that follows---no matter how many blank lines
 appear in a row, they are considered one record separator.
 
 @cindex dark corner, multiline records
-There is an important difference between @samp{RS = ""} and
+However, there is an important difference between @samp{RS = ""} and
 @samp{RS = "\n\n+"}. In the first case, leading newlines in the input
-data file are ignored, and if a file ends without extra blank lines
+@value{DF} are ignored, and if a file ends without extra blank lines
 after the last record, the final newline is removed from the record.
 In the second case, this special processing is not done.
 @value{DARKCORNER}
 
-@cindex field separators, in multiline records
+@cindex field separator, in multiline records
+@cindex @code{FS}, in multiline records
 Now that the input is separated into records, the second step is to
 separate the fields in the record.  One way to do this is to divide each
 of the lines into fields in the normal manner.  This happens by default
@@ -6852,7 +7343,7 @@ Another way to separate fields is to
 put each field on a separate line: to do this, just set the
 variable @code{FS} to the string @code{"\n"}.  (This single
 character separator matches a single newline.)
-A practical example of a data file organized this way might be a mailing
+A practical example of a @value{DF} organized this way might be a mailing
 list, where each entry is separated by blank lines.  Consider a mailing
 list in a file named @file{addresses}, which looks like this:
 
@@ -6917,7 +7408,7 @@ value of
 @table @code
 @item RS == "\n"
 Records are separated by the newline character (@samp{\n}).  In effect,
-every line in the data file is a separate record, including blank lines.
+every line in the @value{DF} is a separate record, including blank lines.
 This is the default.
 
 @item RS == @var{any single character}
@@ -6953,9 +7444,10 @@ then @command{gawk} sets @code{RT} to the null string.
 
 @c STARTOFRANGE getl
 @cindex @code{getline} command, explicit input with
+@c STARTOFRANGE inex
 @cindex input, explicit
 So far we have been getting our input data from @command{awk}'s main
-input stream---either the standard input (usually your terminal, sometimes
+input stream---either the standard input (usually your keyboard, sometimes
 the output from another program) or from the
 files specified on the command line.  The @command{awk} language has a
 special built-in command called @code{getline} that
@@ -6966,13 +7458,25 @@ The @code{getline} command is used in several different ways and should
 The examples that follow the explanation of the @code{getline} command
 include material that has not been covered yet.  Therefore, come back
 and study the @code{getline} command @emph{after} you have reviewed the
-rest of this @value{DOCUMENT} and have a good knowledge of how @command{awk} works.
+rest of
+@ifinfo
+this @value{DOCUMENT}
+@end ifinfo
+@ifhtml
+this @value{DOCUMENT}
+@end ifhtml
+@ifnotinfo
+@ifnothtml
+Parts I and II
+@end ifnothtml
+@end ifnotinfo
+and have a good knowledge of how @command{awk} works.
 
 @cindex @command{gawk}, @code{ERRNO} variable in
-@cindex @code{ERRNO} variable
+@cindex @code{ERRNO} variable, with @command{getline} command
 @cindex differences in @command{awk} and @command{gawk}, @code{getline} command
 @cindex @code{getline} command, return values
-@cindex @code{--sandbox} option, input redirection with @command{getline}
+@cindex @option{--sandbox} option, input redirection with @code{getline}
 
 The @code{getline} command returns one if it finds a record and zero if
 it encounters the end of the file.  If there is some error in getting
@@ -7045,11 +7549,6 @@ decommented input, such as searching for matches of a regular
 expression.  (This program has a subtle problem---it does not work if one
 comment ends and another begins on the same line.)
 
-@ignore
-Exercise,
-write a program that does handle multiple comments on the line.
-@end ignore
-
 This form of the @code{getline} command sets @code{NF},
 @code{NR}, @code{FNR}, @code{RT}, and the value of @code{$0}.
 
@@ -7065,6 +7564,7 @@ rule in the program.  @xref{Next Statement}.
 
 @node Getline/Variable
 @subsection Using @code{getline} into a Variable
+@cindex @code{getline} into a variable
 @cindex variables, @code{getline} command into@comma{} using
 
 You can use @samp{getline @var{var}} to read the next record from
@@ -7116,6 +7616,7 @@ the value of @code{NF} do not change.
 @node Getline/File
 @subsection Using @code{getline} from a File
 
+@cindex @code{getline} from a file
 @cindex input redirection
 @cindex redirection of input
 @cindex @code{<} (left angle bracket), @code{<} operator (I/O)
@@ -7123,7 +7624,7 @@ the value of @code{NF} do not change.
 @cindex operators, input/output
 Use @samp{getline < @var{file}} to read the next record from @var{file}.
 Here @var{file} is a string-valued expression that
-specifies the file name.  @samp{< @var{file}} is called a @dfn{redirection}
+specifies the @value{FN}.  @samp{< @var{file}} is called a @dfn{redirection}
 because it directs input to come from a different place.
 For example, the following
 program reads its input record from the file @file{secondary.input} when it
@@ -7151,9 +7652,9 @@ changed, resulting in a new value of @code{NF}.
 According to POSIX, @samp{getline < @var{expression}} is ambiguous if
 @var{expression} contains unparenthesized operators other than
 @samp{$}; for example, @samp{getline < dir "/" file} is ambiguous
-because the concatenation operator is not parenthesized.  You should
-write it as @samp{getline < (dir "/" file)} if you want your program
-to be portable to all @command{awk} implementations.
+because the concatenation operator (not discussed yet; @pxref{Concatenation})
+is not parenthesized.  You should write it as @samp{getline < (dir "/" file)} if
+you want your program to be portable to all @command{awk} implementations.
 
 @node Getline/Variable/File
 @subsection Using @code{getline} into a Variable from a File
@@ -7164,8 +7665,6 @@ from the file
 @var{file}, and put it in the variable @var{var}.  As above, @var{file}
 is a string-valued expression that specifies the file from which to read.
 
-@cindex @command{gawk}, @code{RT} variable in
-@cindex @code{RT} variable
 In this version of @code{getline}, none of the built-in variables are
 changed and the record is not split into fields.  The only variable
 changed is @var{var}.@footnote{This is not quite true. @code{RT} could
@@ -7188,25 +7687,25 @@ Such a record is replaced by the contents of the file
 
 Note here how the name of the extra input file is not built into
 the program; it is taken directly from the data, specifically from the second field on
-the @samp{@@include} line.
+the @code{@@include} line.
 
-@cindex @code{close()} function
 The @code{close()} function is called to ensure that if two identical
-@samp{@@include} lines appear in the input, the entire specified file is
+@code{@@include} lines appear in the input, the entire specified file is
 included twice.
 @xref{Close Files And Pipes}.
 
 One deficiency of this program is that it does not process nested
-@samp{@@include} statements
-(i.e., @samp{@@include} statements in included files)
+@code{@@include} statements
+(i.e., @code{@@include} statements in included files)
 the way a true macro preprocessor would.
 @xref{Igawk Program}, for a program
-that does handle nested @samp{@@include} statements.
+that does handle nested @code{@@include} statements.
 
 @node Getline/Pipe
 @subsection Using @code{getline} from a Pipe
 
 @c From private email, dated October 2, 1988. Used by permission, March 2013.
+@cindex Kernighan, Brian
 @quotation
 @i{Omniscience has much to recommend it.
 Failing that, attention to details would be useful.}
@@ -7216,7 +7715,7 @@ Failing that, attention to details would be useful.}
 @cindex @code{|} (vertical bar), @code{|} operator (I/O)
 @cindex vertical bar (@code{|}), @code{|} operator (I/O)
 @cindex input pipeline
-@cindex pipes, input
+@cindex pipe, input
 @cindex operators, input/output
 The output of a command can also be piped into @code{getline}, using
 @samp{@var{command} | getline}.  In
@@ -7240,14 +7739,14 @@ produced by running the rest of the line as a shell command:
 @end example
 
 @noindent
-@cindex @code{close()} function
 The @code{close()} function is called to ensure that if two identical
 @samp{@@execute} lines appear in the input, the command is run for
 each one.
 @ifnottex
+@ifnotdocbook
 @xref{Close Files And Pipes}.
+@end ifnotdocbook
 @end ifnottex
-@c Exercise!!
 @c This example is unrealistic, since you could just use system
 Given the input:
 
@@ -7294,6 +7793,8 @@ because the concatenation operator is not parenthesized.  You should
 write it as @samp{(@w{"echo "} "date") | getline} if you want your program
 to be portable to all @command{awk} implementations.
 
+@cindex Brian Kernighan's @command{awk}
+@cindex @command{mawk} utility
 @quotation NOTE
 Unfortunately, @command{gawk} has not been consistent in its treatment
 of a construct like @samp{@w{"echo "} "date" | getline}.
@@ -7405,7 +7906,7 @@ where coprocesses are discussed in more detail.
 Here are some miscellaneous points about @code{getline} that
 you should bear in mind:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 When @code{getline} changes the value of @code{$0} and @code{NF},
 @command{awk} does @emph{not} automatically jump to the start of the
@@ -7417,7 +7918,7 @@ However, the new record is tested against any subsequent rules.
 @cindex @command{awk}, implementations, limits
 @cindex @command{gawk}, implementation issues, limits
 @item
-Many @command{awk} implementations limit the number of pipelines that an @command{awk}
+Some very old @command{awk} implementations limit the number of pipelines that an @command{awk}
 program may have open to just one.  In @command{gawk}, there is no such limit.
 You can open as many pipelines (and coprocesses) as the underlying operating
 system permits.
@@ -7430,10 +7931,10 @@ system permits.
 @item
 An interesting side effect occurs if you use @code{getline} without a
 redirection inside a @code{BEGIN} rule. Because an unredirected @code{getline}
-reads from the command-line data files, the first @code{getline} command
+reads from the command-line @value{DF}s, the first @code{getline} command
 causes @command{awk} to set the value of @code{FILENAME}. Normally,
 @code{FILENAME} does not have a value inside @code{BEGIN} rules, because you
-have not yet started to process the command-line data files.
+have not yet started to process the command-line @value{DF}s.
 @value{DARKCORNER}
 (@xref{BEGIN/END},
 also @pxref{Auto-set}.)
@@ -7456,6 +7957,7 @@ can cause @code{FILENAME} to be updated if they cause
 @command{awk} to start reading a new input file.
 
 @item
+@cindex Moore, Duncan
 If the variable being assigned is an expression with side effects,
 different versions of @command{awk} behave differently upon encountering
 end-of-file.  Some versions don't evaluate the expression; many versions
@@ -7480,7 +7982,7 @@ end of file is encountered, before the element in @code{a} is assigned?
 
 @command{gawk} treats @code{getline} like a function call, and evaluates
 the expression @samp{a[++c]} before attempting to read from @file{f}.
-Other versions of @command{awk} only evaluate the expression once they
+However, some versions of @command{awk} only evaluate the expression once they
 know that there is a string value to be assigned.  Caveat Emptor.
 @end itemize
 
@@ -7516,10 +8018,13 @@ Note: for each variant, @command{gawk} sets the @code{RT} built-in variable.
 @section Reading Input With A Timeout
 @cindex timeout, reading input
 
-You may specify a timeout in milliseconds for reading input from a terminal,
-pipe or two-way communication including, TCP/IP sockets. This can be done
+@cindex differences in @command{awk} and @command{gawk}, read timeouts
+This @value{SECTION} describes a feature that is specific to @command{gawk}.
+
+You may specify a timeout in milliseconds for reading input from the keyboard,
+a pipe, or two-way communication, including TCP/IP sockets. This can be done
 on a per input, command or connection basis, by setting a special element
-in the @code{PROCINFO} array:
+in the @code{PROCINFO} (@pxref{Auto-set}) array:
 
 @example
 PROCINFO["input_name", "READ_TIMEOUT"] = @var{timeout in milliseconds}
@@ -7539,8 +8044,8 @@ else if (ERRNO != "")
     print ERRNO
 @end example
 
-Here is how to read interactively from the terminal@footnote{This assumes
-that standard input is the keyboard} without waiting
+Here is how to read interactively from the user@footnote{This assumes
+that standard input is the keyboard.} without waiting
 for more than five seconds:
 
 @example
@@ -7549,13 +8054,13 @@ while ((getline < "/dev/stdin") > 0)
     print $0
 @end example
 
-@command{gawk} will terminate the read operation if input does not
-arrive after waiting for the timeout period, return failure
-and set the @code{ERRNO} variable to an appropriate string value.
+@command{gawk} terminates the read operation if input does not
+arrive after waiting for the timeout period, returns failure
+and sets the @code{ERRNO} variable to an appropriate string value.
 A negative or zero value for the timeout is the same as specifying
 no timeout at all.
 
-A timeout can also be set for reading from the terminal in the implicit
+A timeout can also be set for reading from the keyboard in the implicit
 loop that reads input records and matches them against patterns,
 like so:
 
@@ -7618,19 +8123,120 @@ indefinitely until some other process opens it for writing.
 
 @node Command line directories
 @section Directories On The Command Line
+@cindex differences in @command{awk} and @command{gawk}, command line directories
 @cindex directories, command line
 @cindex command line, directories on
 
 According to the POSIX standard, files named on the @command{awk}
-command line must be text files.  It is a fatal error if they are not.
+command line must be text files; it is a fatal error if they are not.
 Most versions of @command{awk} treat a directory on the command line as
 a fatal error.
 
 By default, @command{gawk} produces a warning for a directory on the
-command line, but otherwise ignores it.  If either of the @option{--posix}
+command line, but otherwise ignores it.  This makes it easier to use
+shell wildcards with your @command{awk} program:
+
+@example
+$ @kbd{gawk -f whizprog.awk *}        @ii{Directories could kill this progam}
+@end example
+
+If either of the @option{--posix}
 or @option{--traditional} options is given, then @command{gawk} reverts
 to treating a directory on the command line as a fatal error.
 
+@xref{Extension Sample Readdir}, for a way to treat directories
+as usable data from an @command{awk} program.
+
+@node Input Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Input is split into records based on the value of @code{RS}.
+The possibilities are as follows:
+
+@multitable @columnfractions .25 .35 .40
+@headitem Value of @code{RS} @tab Records are split on @tab @command{awk} / @command{gawk}
+@item Any single character @tab That character @tab @command{awk}
+@item The empty string (@code{""}) @tab Runs of two or more newlines @tab @command{awk}
+@item A regexp @tab Text that matches the regexp @tab @command{gawk}
+@end multitable
+
+@item
+@command{gawk} sets @code{RT} to the text matched by @code{RS}.
+
+@item
+After splitting the input into records, @command{awk} further splits
+the record into individual fields, named @code{$1}, @code{$2} and so
+on. @code{$0} is the whole record, and @code{NF} indicates how many
+fields there are.  The default way to split fields is between whitespace
+characters.
+
+@item
+Fields may be referenced using a variable, as in @samp{$NF}.  Fields
+may also be assigned values, which causes the value of @code{$0} to be
+recomputed when it is later referenced. Assigning to a field with a number
+greater than @code{NF} creates the field and rebuilds the record, using
+@code{OFS} to separate the fields.  Incrementing @code{NF} does the same
+thing. Decrementing @code{NF} throws away fields and rebuilds the record.
+
+@item
+Field splitting is more complicated than record splitting.
+
+@multitable @columnfractions .40 .40 .20
+@headitem Field separator value @tab Fields are split @dots{} @tab @command{awk} / @command{gawk}
+@item @code{FS == " "} @tab On runs of whitespace @tab @command{awk}
+@item @code{FS == @var{any single character}} @tab On that character @tab @command{awk}
+@item @code{FS == @var{regexp}} @tab On text matching the regexp @tab @command{awk}
+@item @code{FS == ""}  @tab Each individual character is a separate field @tab @command{gawk}
+@item @code{FIELDWIDTHS == @var{list of columns}} @tab Based on character position @tab @command{gawk}
+@item @code{FPAT == @var{regexp}} @tab On text around text matching the regexp @tab @command{gawk}
+@end multitable
+
+Using @samp{FS = "\n"} causes the entire record to be a single field
+(assuming that newlines separate records).
+
+@item
+@code{FS} may be set from the command line using the @option{-F} option.
+This can also be done using command-line variable assignment.
+
+@item
+@code{PROCINFO["FS"]} can be used to see how fields are being split.
+
+@item
+Use @code{getline} in its various forms to read additional records,
+from the default input stream, from a file, or from a pipe or co-process.
+
+@item
+Use @code{PROCINFO[@var{file}, "READ_TIMEOUT"]} to cause reads to timeout
+for @var{file}.
+
+@item
+Directories on the command line are fatal for standard @command{awk};
+@command{gawk} ignores them if not in POSIX mode.
+
+@end itemize
+
+@node Input Exercises
+@section Exercises
+
+@enumerate
+@item
+Using the @code{FIELDWIDTHS} variable (@pxref{Constant Size}),
+write a program to read election data, where each record represents
+one voter's votes.  Come up with a way to define which columns are
+associated with each ballot item, and print the total votes,
+including abstentions, for each item.
+
+@item
+@ref{Plain Getline}, presented a program to remove C-style
+comments (@samp{/* @dots{} */}) from the input.  That program
+does not work if one comment ends on one line and another one
+starts later on the same line.
+Write a program that does handle multiple comments on the line.
+
+@end enumerate
+
 @node Printing
 @chapter Printing Output
 
@@ -7655,7 +8261,7 @@ For printing with specifications, you need the @code{printf} statement
 @cindex @code{printf} statement
 Besides basic and formatted printing, this @value{CHAPTER}
 also covers I/O redirections to files and pipes, introduces
-the special file names that @command{gawk} processes internally,
+the special @value{FN}s that @command{gawk} processes internally,
 and discusses the @code{close()} built-in function.
 
 @menu
@@ -7670,13 +8276,15 @@ and discusses the @code{close()} built-in function.
                                 @command{gawk} allows access to inherited file
                                 descriptors.
 * Close Files And Pipes::       Closing Input and Output Files and Pipes.
+* Output Summary::              Output summary.
+* Output exercises::            Exercises.
 @end menu
 
 @node Print
 @section The @code{print} Statement
 
 The @code{print} statement is used for producing output with simple, standardized
-formatting.  Specify only the strings or numbers to print, in a
+formatting.  You specify only the strings or numbers to print, in a
 list separated by commas.  They are output, separated by single spaces,
 followed by a newline.  The statement looks like this:
 
@@ -7759,10 +8367,9 @@ $ @kbd{awk '@{ print $1 $2 @}' inventory-shipped}
 To someone unfamiliar with the @file{inventory-shipped} file, neither
 example's output makes much sense.  A heading line at the beginning
 would make it clearer.  Let's add some headings to our table of months
-(@code{$1}) and green crates shipped (@code{$2}).  We do this using the
-@code{BEGIN} pattern
-(@pxref{BEGIN/END})
-so that the headings are only printed once:
+(@code{$1}) and green crates shipped (@code{$2}).  We do this using
+a @code{BEGIN} rule (@pxref{BEGIN/END}) so that the headings are only
+printed once:
 
 @example
 awk 'BEGIN @{  print "Month Crates"
@@ -7848,26 +8455,32 @@ The following example prints the first and second fields of each input
 record, separated by a semicolon, with a blank line added after each
 newline:
 
-@ignore
-Exercise,
-Rewrite the
-@example
-awk 'BEGIN @{ print "Month Crates"
-             print "----- ------" @}
-           @{ print $1, "     ", $2 @}' inventory-shipped
-@end example
-program by using a new value of @code{OFS}.
-@end ignore
 
 @example
 $ @kbd{awk 'BEGIN @{ OFS = ";"; ORS = "\n\n" @}}
->            @kbd{@{ print $1, $2 @}' BBS-list}
-@print{} aardvark;555-5553
-@print{}
-@print{} alpo-net;555-3412
-@print{}
-@print{} barfly;555-7685
-@dots{}
+>            @kbd{@{ print $1, $2 @}' mail-list}
+@print{} Amelia;555-5553
+@print{} 
+@print{} Anthony;555-3412
+@print{} 
+@print{} Becky;555-7685
+@print{} 
+@print{} Bill;555-1675
+@print{} 
+@print{} Broderick;555-0542
+@print{} 
+@print{} Camilla;555-2912
+@print{} 
+@print{} Fabius;555-1234
+@print{} 
+@print{} Julie;555-6699
+@print{} 
+@print{} Martin;555-6480
+@print{} 
+@print{} Samuel;555-3430
+@print{} 
+@print{} Jean-Paul;555-2127
+@print{} 
 @end example
 
 If the value of @code{ORS} does not contain a newline, the program's output
@@ -7889,7 +8502,7 @@ numbers can be formatted.  The different format specifications are discussed
 more fully in
 @ref{Control Letters}.
 
-@cindex @code{sprintf()} function
+@cindexawkfunc{sprintf}
 @cindex @code{OFMT} variable
 @cindex output, format specifier@comma{} @code{OFMT}
 The built-in variable @code{OFMT} contains the default format specification
@@ -7955,7 +8568,7 @@ parentheses are necessary if any of the item expressions use the @samp{>}
 relational operator; otherwise, it can be confused with an output redirection
 (@pxref{Redirection}).
 
-@cindex format strings
+@cindex format specifiers
 The difference between @code{printf} and @code{print} is the @var{format}
 argument.  This is an expression whose value is taken as a string; it
 specifies how to output each of the other arguments.  It is called the
@@ -7998,8 +8611,9 @@ of value to print.  The rest of the format specifier is made up of
 optional @dfn{modifiers} that control @emph{how} to print the value, such as
 the field width.  Here is a list of the format-control letters:
 
-@table @code
-@item %c
+@c @asis for docbook to come out right
+@table @asis
+@item @code{%c}
 Print a number as an ASCII character; thus, @samp{printf "%c",
 65} outputs the letter @samp{A}. The output for a string value is
 the first character of the string.
@@ -8007,16 +8621,6 @@ the first character of the string.
 @cindex dark corner, format-control characters
 @cindex @command{gawk}, format-control characters
 @quotation NOTE
-@ignore
-The @samp{%c} format does @emph{not} handle values outside the range
-0--255.  On most systems, values from 0--127 are within the range of
-ASCII and will yield an ASCII character.  Values in the range 128--255
-may format as characters in some extended character set, or they may not.
-System 390 (IBM architecture mainframe) systems use 8-bit characters,
-and thus values from 0--255 yield the corresponding EBCDIC character.
-Any value above 255 is treated as modulo 255; i.e., the lowest eight bits
-of the value are used.  The locale and character set are always ignored.
-@end ignore
 The POSIX standard says the first character of a string is printed.
 In locales with multibyte characters, @command{gawk} attempts to
 convert the leading bytes of the string into a valid wide character
@@ -8031,12 +8635,12 @@ a single byte (0--255).
 @end quotation
 
 
-@item %d@r{,} %i
+@item @code{%d}, @code{%i}
 Print a decimal integer.
 The two control letters are equivalent.
 (The @samp{%i} specification is for compatibility with ISO C.)
 
-@item %e@r{,} %E
+@item @code{%e}, @code{%E}
 Print a number in scientific (exponential) notation;
 for example:
 
@@ -8051,7 +8655,7 @@ which follow the decimal point.
 discussed in the next @value{SUBSECTION}.)
 @samp{%E} uses @samp{E} instead of @samp{e} in the output.
 
-@item %f
+@item @code{%f}
 Print a number in floating-point notation.
 For example:
 
@@ -8071,39 +8675,40 @@ infinity are formatted as
 @samp{-inf} or @samp{-infinity},
 and positive infinity as
 @samp{inf} and @samp{infinity}.
-The special ``not a number'' value formats as @samp{-nan} or @samp{nan}.
+The special ``not a number'' value formats as @samp{-nan} or @samp{nan}
+(@pxref{Math Definitions}).
 
-@item %F
+@item @code{%F}
 Like @samp{%f} but the infinity and ``not a number'' values are spelled
 using uppercase letters.
 
 The @samp{%F} format is a POSIX extension to ISO C; not all systems
 support it.  On those that don't, @command{gawk} uses @samp{%f} instead.
 
-@item %g@r{,} %G
+@item @code{%g}, @code{%G}
 Print a number in either scientific notation or in floating-point
 notation, whichever uses fewer characters; if the result is printed in
 scientific notation, @samp{%G} uses @samp{E} instead of @samp{e}.
 
-@item %o
+@item @code{%o}
 Print an unsigned octal integer
 (@pxref{Nondecimal-numbers}).
 
-@item %s
+@item @code{%s}
 Print a string.
 
-@item %u
+@item @code{%u}
 Print an unsigned decimal integer.
 (This format is of marginal use, because all numbers in @command{awk}
 are floating-point; it is provided primarily for compatibility with C.)
 
-@item %x@r{,} %X
+@item @code{%x}, @code{%X}
 Print an unsigned hexadecimal integer;
 @samp{%X} uses the letters @samp{A} through @samp{F}
 instead of @samp{a} through @samp{f}
 (@pxref{Nondecimal-numbers}).
 
-@item %%
+@item @code{%%}
 Print a single @samp{%}.
 This does not consume an
 argument and it ignores any modifiers.
@@ -8138,7 +8743,7 @@ which they may appear:
 @table @code
 @cindex differences in @command{awk} and @command{gawk}, @code{print}/@code{printf} statements
 @cindex @code{printf} statement, positional specifiers
-@c the command does NOT start a secondary
+@c the code{} does NOT start a secondary
 @cindex positional specifiers, @code{printf} statement
 @item @var{N}$
 An integer constant followed by a @samp{$} is a @dfn{positional specifier}.
@@ -8214,7 +8819,7 @@ For example:
 $ @kbd{cat thousands.awk}          @ii{Show source program}
 @print{} BEGIN @{ printf "%'d\n", 1234567 @}
 $ @kbd{LC_ALL=C gawk -f thousands.awk}
-@print{} 1234567                   @ii{Results in "C" locale}
+@print{} 1234567                   @ii{Results in} "C" @ii{locale}
 $ @kbd{LC_ALL=en_US.UTF-8 gawk -f thousands.awk}
 @print{} 1,234,567                 @ii{Results in US English UTF locale}
 @end example
@@ -8324,14 +8929,12 @@ This is not particularly easy to read but it does work.
 @c @cindex lint checks
 @cindex troubleshooting, fatal errors, @code{printf} format strings
 @cindex POSIX @command{awk}, @code{printf} format strings and
-C programmers may be used to supplying additional
-@samp{l}, @samp{L}, and @samp{h}
-modifiers in @code{printf} format strings. These are not valid in @command{awk}.
-Most @command{awk} implementations silently ignore them.
-If @option{--lint} is provided on the command line
-(@pxref{Options}),
-@command{gawk} warns about their use. If @option{--posix} is supplied,
-their use is a fatal error.
+C programmers may be used to supplying additional modifiers (@samp{h},
+@samp{j}, @samp{l}, @samp{L}, @samp{t}, and @samp{z}) in @code{printf}
+format strings. These are not valid in @command{awk}.  Most @command{awk}
+implementations silently ignore them.  If @option{--lint} is provided
+on the command line (@pxref{Options}), @command{gawk} warns about their
+use. If @option{--posix} is supplied, their use is a fatal error.
 @c ENDOFRANGE pfm
 
 @node Printf Examples
@@ -8341,30 +8944,30 @@ The following simple example shows
 how to use @code{printf} to make an aligned table:
 
 @example
-awk '@{ printf "%-10s %s\n", $1, $2 @}' BBS-list
+awk '@{ printf "%-10s %s\n", $1, $2 @}' mail-list
 @end example
 
 @noindent
 This command
-prints the names of the bulletin boards (@code{$1}) in the file
-@file{BBS-list} as a string of 10 characters that are left-justified.  It also
+prints the names of the people (@code{$1}) in the file
+@file{mail-list} as a string of 10 characters that are left-justified.  It also
 prints the phone numbers (@code{$2}) next on the line.  This
 produces an aligned two-column table of names and phone numbers,
 as shown here:
 
 @example
-$ @kbd{awk '@{ printf "%-10s %s\n", $1, $2 @}' BBS-list}
-@print{} aardvark   555-5553
-@print{} alpo-net   555-3412
-@print{} barfly     555-7685
-@print{} bites      555-1675
-@print{} camelot    555-0542
-@print{} core       555-2912
-@print{} fooey      555-1234
-@print{} foot       555-6699
-@print{} macfoo     555-6480
-@print{} sdace      555-3430
-@print{} sabafoo    555-2127
+$ @kbd{awk '@{ printf "%-10s %s\n", $1, $2 @}' mail-list}
+@print{} Amelia     555-5553
+@print{} Anthony    555-3412
+@print{} Becky      555-7685
+@print{} Bill       555-1675
+@print{} Broderick  555-0542
+@print{} Camilla    555-2912
+@print{} Fabius     555-1234
+@print{} Julie      555-6699
+@print{} Martin     555-6480
+@print{} Samuel     555-3430
+@print{} Jean-Paul  555-2127
 @end example
 
 In this case, the phone numbers had to be printed as strings because
@@ -8377,7 +8980,7 @@ they are last on their lines.  They don't need to have spaces
 after them.
 
 The table could be made to look even nicer by adding headings to the
-tops of the columns.  This is done using the @code{BEGIN} pattern
+tops of the columns.  This is done using a @code{BEGIN} rule
 (@pxref{BEGIN/END})
 so that the headers are only printed once, at the beginning of
 the @command{awk} program:
@@ -8385,7 +8988,7 @@ the @command{awk} program:
 @example
 awk 'BEGIN @{ print "Name      Number"
              print "----      ------" @}
-     @{ printf "%-10s %s\n", $1, $2 @}' BBS-list
+     @{ printf "%-10s %s\n", $1, $2 @}' mail-list
 @end example
 
 The above example mixes @code{print} and @code{printf} statements in
@@ -8395,7 +8998,7 @@ same results:
 @example
 awk 'BEGIN @{ printf "%-10s %s\n", "Name", "Number"
              printf "%-10s %s\n", "----", "------" @}
-     @{ printf "%-10s %s\n", $1, $2 @}' BBS-list
+     @{ printf "%-10s %s\n", $1, $2 @}' mail-list
 @end example
 
 @noindent
@@ -8410,23 +9013,19 @@ emphasized by storing it in a variable, like this:
 awk 'BEGIN @{ format = "%-10s %s\n"
              printf format, "Name", "Number"
              printf format, "----", "------" @}
-     @{ printf format, $1, $2 @}' BBS-list
+     @{ printf format, $1, $2 @}' mail-list
 @end example
 
-@c !!! exercise
-At this point, it would be a worthwhile exercise to use the
-@code{printf} statement to line up the headings and table data for the
-@file{inventory-shipped} example that was covered earlier in the @value{SECTION}
-on the @code{print} statement
-(@pxref{Print}).
 @c ENDOFRANGE printfs
 
 @node Redirection
 @section Redirecting Output of @code{print} and @code{printf}
 
+@c STARTOFRANGE outre
 @cindex output redirection
+@c STARTOFRANGE reout
 @cindex redirection of output
-@cindex @code{--sandbox} option, output redirection with @code{print}, @code{printf}
+@cindex @option{--sandbox} option, output redirection with @code{print}, @code{printf}
 So far, the output from @code{print} and @code{printf} has gone
 to the standard
 output, usually the screen.  Both @code{print} and @code{printf} can
@@ -8443,11 +9042,11 @@ Redirections in @command{awk} are written just like redirections in shell
 commands, except that they are written inside the @command{awk} program.
 
 @c the commas here are part of the see also
-@cindex @code{print} statement, See Also redirection, of output
-@cindex @code{printf} statement, See Also redirection, of output
+@cindex @code{print} statement, See Also redirection@comma{} of output
+@cindex @code{printf} statement, See Also redirection@comma{} of output
 There are four forms of output redirection: output to a file, output
 appended to a file, output through a pipe to another command, and output
-to a coprocess.  They are all shown for the @code{print} statement,
+to a coprocess.  We show them all for the @code{print} statement,
 but they work identically for @code{printf}:
 
 @table @code
@@ -8456,29 +9055,29 @@ but they work identically for @code{printf}:
 @cindex operators, input/output
 @item print @var{items} > @var{output-file}
 This redirection prints the items into the output file named
-@var{output-file}.  The file name @var{output-file} can be any
+@var{output-file}.  The @value{FN} @var{output-file} can be any
 expression.  Its value is changed to a string and then used as a
-file name (@pxref{Expressions}).
+@value{FN} (@pxref{Expressions}).
 
 When this type of redirection is used, the @var{output-file} is erased
 before the first output is written to it.  Subsequent writes to the same
 @var{output-file} do not erase @var{output-file}, but append to it.
 (This is different from how you use redirections in shell scripts.)
 If @var{output-file} does not exist, it is created.  For example, here
-is how an @command{awk} program can write a list of BBS names to one
+is how an @command{awk} program can write a list of peoples' names to one
 file named @file{name-list}, and a list of phone numbers to another file
 named @file{phone-list}:
 
 @example
 $ @kbd{awk '@{ print $2 > "phone-list"}
->        @kbd{print $1 > "name-list" @}' BBS-list}
+>        @kbd{print $1 > "name-list" @}' mail-list}
 $ @kbd{cat phone-list}
 @print{} 555-5553
 @print{} 555-3412
 @dots{}
 $ @kbd{cat name-list}
-@print{} aardvark
-@print{} alpo-net
+@print{} Amelia
+@print{} Anthony
 @dots{}
 @end example
 
@@ -8496,7 +9095,7 @@ appended to the file.
 If @var{output-file} does not exist, then it is created.
 
 @cindex @code{|} (vertical bar), @code{|} operator (I/O)
-@cindex pipes, output
+@cindex pipe, output
 @cindex output, pipes
 @item print @var{items} | @var{command}
 It is possible to send output to another program through a pipe
@@ -8507,7 +9106,7 @@ to another process created to execute @var{command}.
 The redirection argument @var{command} is actually an @command{awk}
 expression.  Its value is converted to a string whose contents give
 the shell command to be run.  For example, the following produces two
-files, one unsorted list of BBS names, and one list sorted in reverse
+files, one unsorted list of peoples' names, and one list sorted in reverse
 alphabetical order:
 
 @ignore
@@ -8520,7 +9119,7 @@ alone for now and let's hope no-one notices.
 @example
 awk '@{ print $1 > "names.unsorted"
        command = "sort -r > names.sorted"
-       print $1 | command @}' BBS-list
+       print $1 | command @}' mail-list
 @end example
 
 The unsorted list is written with an ordinary redirection, while
@@ -8552,7 +9151,7 @@ This example also illustrates the use of a variable to represent
 a @var{file} or @var{command}---it is not necessary to always
 use a string constant.  Using a variable is generally a good idea,
 because (if you mean to refer to that same file or command)
-@command{awk} requires that the string value be spelled identically
+@command{awk} requires that the string value be written identically
 every time.
 
 @cindex coprocesses
@@ -8611,7 +9210,9 @@ As mentioned earlier
 many
 @end ifnotinfo
 @ifnottex
+@ifnotdocbook
 Many
+@end ifnotdocbook
 @end ifnottex
 older
 @command{awk} implementations limit the number of pipelines that an @command{awk}
@@ -8624,7 +9225,7 @@ open as many pipelines as the underlying operating system permits.
 
 A particularly powerful way to use redirection is to build command lines
 and pipe them into the shell, @command{sh}.  For example, suppose you
-have a list of files brought over from a system where all the file names
+have a list of files brought over from a system where all the @value{FN}s
 are stored in uppercase, and you wish to rename them to have names in
 all lowercase.  The following program is both simple and efficient:
 
@@ -8646,12 +9247,12 @@ It then sends the list to the shell for execution.
 @c ENDOFRANGE reout
 
 @node Special Files
-@section Special File Names in @command{gawk}
+@section Special @value{FFN} in @command{gawk}
 @c STARTOFRANGE gfn
 @cindex @command{gawk}, file names in
 
-@command{gawk} provides a number of special file names that it interprets
-internally.  These file names provide access to standard file descriptors
+@command{gawk} provides a number of special @value{FN}s that it interprets
+internally.  These @value{FN}s provide access to standard file descriptors
 and TCP/IP networking.
 
 @menu
@@ -8715,12 +9316,12 @@ that happens, writing to the screen is not correct.  In fact, if
 terminal at all.
 Then opening @file{/dev/tty} fails.
 
-@command{gawk} provides special file names for accessing the three standard
-streams. @value{COMMONEXT}. It also provides syntax for accessing
-any other inherited open files.  If the file name matches
+@command{gawk} provides special @value{FN}s for accessing the three standard
+streams. @value{COMMONEXT} It also provides syntax for accessing
+any other inherited open files.  If the @value{FN} matches
 one of these special names when @command{gawk} redirects input or output,
-then it directly uses the stream that the file name stands for.
-These special file names work for all operating systems that @command{gawk}
+then it directly uses the stream that the @value{FN} stands for.
+These special @value{FN}s work for all operating systems that @command{gawk}
 has been ported to, not just those that are POSIX-compliant:
 
 @cindex common extensions, @code{/dev/stdin} special file
@@ -8730,9 +9331,9 @@ has been ported to, not just those that are POSIX-compliant:
 @cindex extensions, common@comma{} @code{/dev/stdout} special file
 @cindex extensions, common@comma{} @code{/dev/stderr} special file
 @cindex file names, standard streams in @command{gawk}
-@cindex @code{/dev/@dots{}} special files (@command{gawk})
+@cindex @code{/dev/@dots{}} special files
 @cindex files, @code{/dev/@dots{}} special files
-@cindex @code{/dev/fd/@var{N}} special files
+@cindex @code{/dev/fd/@var{N}} special files (@command{gawk})
 @table @file
 @item /dev/stdin
 The standard input (file descriptor 0).
@@ -8750,7 +9351,7 @@ the shell).  Unless special pains are taken in the shell from which
 @command{gawk} is invoked, only descriptors 0, 1, and 2 are available.
 @end table
 
-The file names @file{/dev/stdin}, @file{/dev/stdout}, and @file{/dev/stderr}
+The @value{FN}s @file{/dev/stdin}, @file{/dev/stdout}, and @file{/dev/stderr}
 are aliases for @file{/dev/fd/0}, @file{/dev/fd/1}, and @file{/dev/fd/2},
 respectively. However, they are more self-explanatory.
 The proper way to write an error message in a @command{gawk} program
@@ -8761,13 +9362,12 @@ print "Serious error detected!" > "/dev/stderr"
 @end example
 
 @cindex troubleshooting, quotes with file names
-Note the use of quotes around the file name.
+Note the use of quotes around the @value{FN}.
 Like any other redirection, the value must be a string.
 It is a common error to omit the quotes, which leads
 to confusing results.
-@c Exercise: What does it do?  :-)
 
-Finally, using the @code{close()} function on a file name of the
+Finally, using the @code{close()} function on a @value{FN} of the
 form @code{"/dev/fd/@var{N}"}, for file descriptor numbers
 above two, does actually close the given file descriptor.
 
@@ -8783,7 +9383,7 @@ versions of @command{awk}.
 @command{gawk} programs
 can open a two-way
 TCP/IP connection, acting as either a client or a server.
-This is done using a special file name of the form:
+This is done using a special @value{FN} of the form:
 
 @example
 @file{/@var{net-type}/@var{protocol}/@var{local-port}/@var{remote-host}/@var{remote-port}}
@@ -8793,7 +9393,7 @@ The @var{net-type} is one of @samp{inet}, @samp{inet4} or @samp{inet6}.
 The @var{protocol} is one of @samp{tcp} or @samp{udp},
 and the other fields represent the other essential pieces of information
 for making a networking connection.
-These file names are used with the @samp{|&} operator for communicating
+These @value{FN}s are used with the @samp{|&} operator for communicating
 with a coprocess
 (@pxref{Two-way I/O}).
 This is an advanced feature, mentioned here only for completeness.
@@ -8801,21 +9401,21 @@ Full discussion is delayed until
 @ref{TCP/IP Networking}.
 
 @node Special Caveats
-@subsection Special File Name Caveats
+@subsection Special @value{FFN} Caveats
 
 Here is a list of things to bear in mind when using the
-special file names that @command{gawk} provides:
+special @value{FN}s that @command{gawk} provides:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @cindex compatibility mode (@command{gawk}), file names
 @cindex file names, in compatibility mode
 @item
-Recognition of these special file names is disabled if @command{gawk} is in
+Recognition of these special @value{FN}s is disabled if @command{gawk} is in
 compatibility mode (@pxref{Options}).
 
 @item
 @command{gawk} @emph{always}
-interprets these special file names.
+interprets these special @value{FN}s.
 For example, using @samp{/dev/fd/4}
 for output actually writes on file descriptor 4, and not on a new
 file descriptor that is @code{dup()}'ed from file descriptor 4.  Most of
@@ -8833,12 +9433,12 @@ Doing so results in unpredictable behavior.
 @c STARTOFRANGE ofc
 @cindex output, files@comma{} closing
 @c STARTOFRANGE pc
-@cindex pipes, closing
+@cindex pipe, closing
 @c STARTOFRANGE cc
 @cindex coprocesses, closing
 @cindex @code{getline} command, coprocesses@comma{} using from
 
-If the same file name or the same shell command is used with @code{getline}
+If the same @value{FN} or the same shell command is used with @code{getline}
 more than once during the execution of an @command{awk} program
 (@pxref{Getline}),
 the file is opened (or the command is executed) the first time only.
@@ -8847,11 +9447,11 @@ The next time the same file or command is used with @code{getline},
 another record is read from it, and so on.
 
 Similarly, when a file or pipe is opened for output, @command{awk} remembers
-the file name or command associated with it, and subsequent
+the @value{FN} or command associated with it, and subsequent
 writes to the same file or command are appended to the previous writes.
 The file or pipe stays open until @command{awk} exits.
 
-@cindex @code{close()} function
+@cindexawkfunc{close}
 This implies that special steps are necessary in order to read the same
 file again from the beginning, or to rerun a shell command (rather than
 reading more output from the same command).  The @code{close()} function
@@ -8889,7 +9489,7 @@ file or command, or the next @code{print} or @code{printf} to that
 file or command, reopens the file or reruns the command.
 Because the expression that you use to close a file or pipeline must
 exactly match the expression used to open the file or run the command,
-it is good practice to use a variable to store the file name or command.
+it is good practice to use a variable to store the @value{FN} or command.
 The previous example becomes the following:
 
 @example
@@ -8903,7 +9503,7 @@ close(sortcom)
 This helps avoid hard-to-find typographical errors in your @command{awk}
 programs.  Here are some of the reasons for closing an output file:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 To write a file and read it back later on in the same @command{awk}
 program.  Close the file after writing it, then
@@ -8936,9 +9536,10 @@ a separate message.
 
 @cindex differences in @command{awk} and @command{gawk}, @code{close()} function
 @cindex portability, @code{close()} function and
+@cindex @code{close()} function, portability
 If you use more files than the system allows you to have open,
 @command{gawk} attempts to multiplex the available open files among
-your data files.  @command{gawk}'s ability to do this depends upon the
+your @value{DF}s.  @command{gawk}'s ability to do this depends upon the
 facilities of your operating system, so it may not always work.  It is
 therefore both good practice and good portability advice to always
 use @code{close()} on your files when you are done with them.
@@ -8971,15 +9572,16 @@ more importantly, the file descriptor for the pipe
 is not closed and released until @code{close()} is called or
 @command{awk} exits.
 
-@code{close()} will silently do nothing if given an argument that
+@code{close()} silently does nothing if given an argument that
 does not represent a file, pipe or coprocess that was opened with
-a redirection.
+a redirection.  In such a case, it returns a negative value,
+indicating an error. In addition, @command{gawk} sets @code{ERRNO}
+to a string indicating the error.
 
-Note also that @samp{close(FILENAME)} has no
-``magic'' effects on the implicit loop that reads through the
-files named on the command line.  It is, more likely, a close
-of a file that was never opened, so @command{awk} silently
-does nothing.
+Note also that @samp{close(FILENAME)} has no ``magic'' effects on the
+implicit loop that reads through the files named on the command line.
+It is, more likely, a close of a file that was never opened with a
+redirection, so @command{awk} silently does nothing.
 
 @cindex @code{|} (vertical bar), @code{|&} operator (I/O), pipes@comma{} closing
 When using the @samp{|&} operator to communicate with a coprocess,
@@ -9003,7 +9605,7 @@ which discusses it in more detail and gives an example.
 @cindex differences in @command{awk} and @command{gawk}, @code{close()} function
 @cindex Unix @command{awk}, @code{close()} function and
 
-In many versions of Unix @command{awk}, the @code{close()} function
+In many older versions of Unix @command{awk}, the @code{close()} function
 is actually a statement.  It is a syntax error to try and use the return
 value from @code{close()}:
 @value{DARKCORNER}
@@ -9015,7 +9617,7 @@ retval = close(command)  # syntax error in many Unix awks
 @end example
 
 @cindex @command{gawk}, @code{ERRNO} variable in
-@cindex @code{ERRNO} variable
+@cindex @code{ERRNO} variable, with @command{close()} function
 @command{gawk} treats @code{close()} as a function.
 The return value is @minus{}1 if the argument names something
 that was never opened with a redirection, or if there is
@@ -9048,6 +9650,67 @@ when closing a pipe.
 @c ENDOFRANGE ofc
 @c ENDOFRANGE pc
 @c ENDOFRANGE cc
+
+@node Output Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+The @code{print} statement prints comma-separated expressions. Each
+expression is separated by the value of @code{OFS} and terminated by
+the value of @code{ORS}.  @code{OFMT} provides the conversion format
+for numeric values for the @code{print} statement.
+
+@item
+The @code{printf} statement provides finer-grained control over output,
+with format control letters for different data types and various flags
+that modify the behavior of the format control letters.
+
+@item
+Output from both @code{print} and @code{printf} may be redirected to
+files, pipes, and co-processes.
+
+@item
+@command{gawk} provides special file names for access to standard input,
+output and error, and for network communications.
+
+@item
+Use @code{close()} to close open file, pipe and co-process redirections.
+For co-processes, it is possible to close only one direction of the
+communications.
+
+@end itemize
+
+@node Output exercises
+@section Exercises
+
+@enumerate
+@item
+Rewrite the program:
+
+@example
+awk 'BEGIN @{ print "Month Crates"
+             print "----- ------" @}
+           @{ print $1, "     ", $2 @}' inventory-shipped
+@end example
+
+@noindent
+from @ref{Output Separators}, by using a new value of @code{OFS}.
+
+@item
+Use the @code{printf} statement to line up the headings and table data
+for the @file{inventory-shipped} example that was covered in @ref{Print}.
+
+@item
+What happens if you forget the double quotes when redirecting
+output, as follows:
+
+@example
+BEGIN @{ print "Serious error detected!" > /dev/stderr @}
+@end example
+
+@end enumerate
+
 @c ENDOFRANGE prnt
 
 @node Expressions
@@ -9074,6 +9737,7 @@ combinations of these with various operators.
 * Function Calls::              A function call is an expression.
 * Precedence::                  How various operators nest.
 * Locales::                     How the locale affects things.
+* Expressions Summary::         Expressions summary.
 @end menu
 
 @node Values
@@ -9093,6 +9757,8 @@ which provide the values used in expressions.
 
 @node Constants
 @subsection Constant Expressions
+
+@c STARTOFRANGE cnst
 @cindex constants, types of
 
 The simplest type of expression is the @dfn{constant}, which always has
@@ -9112,13 +9778,14 @@ have different forms, but are stored identically internally.
 @node Scalar Constants
 @subsubsection Numeric and String Constants
 
-@cindex numeric, constants
+@cindex constants, numeric
+@cindex numeric constants
 A @dfn{numeric constant} stands for a number.  This number can be an
 integer, a decimal fraction, or a number in scientific (exponential)
 notation.@footnote{The internal representation of all numbers,
-including integers, uses double precision
-floating-point numbers.
-On most modern systems, these are in IEEE 754 standard format.}
+including integers, uses double precision floating-point numbers.
+On most modern systems, these are in IEEE 754 standard format.
+@xref{Arbitrary Precision Arithmetic}, for much more information.}
 Here are some examples of numeric constants that all
 have the same value:
 
@@ -9138,7 +9805,7 @@ double-quotation marks.  For example:
 
 @noindent
 @cindex differences in @command{awk} and @command{gawk}, strings
-@cindex strings, length of
+@cindex strings, length limitations
 represents the string whose contents are @samp{parrot}.  Strings in
 @command{gawk} can be of any length, and they can contain any of the possible
 eight-bit ASCII characters including ASCII @sc{nul} (character code zero).
@@ -9325,13 +9992,13 @@ upon the contents of the current input record.
 
 @cindex differences in @command{awk} and @command{gawk}, regexp constants
 @cindex dark corner, regexp constants, as arguments to user-defined functions
-@cindex @code{gensub()} function (@command{gawk})
-@cindex @code{sub()} function
-@cindex @code{gsub()} function
+@cindexgawkfunc{gensub}
+@cindexawkfunc{sub}
+@cindexawkfunc{gsub}
 Constant regular expressions are also used as the first argument for
 the @code{gensub()}, @code{sub()}, and @code{gsub()} functions, as the
 second argument of the @code{match()} function,
-and as the third argument of the @code{patsplit()} function
+and as the third argument of the @code{split()} and @code{patsplit()} functions
 (@pxref{String Functions}).
 Modern implementations of @command{awk}, including @command{gawk}, allow
 the third argument of @code{split()} to be a regexp constant, but some
@@ -9438,7 +10105,7 @@ Such an assignment has the following form:
 @var{variable}=@var{text}
 @end example
 
-@cindex @code{-v} option
+@cindex @option{-v} option
 @noindent
 With it, a variable is set either at the beginning of the
 @command{awk} run or in between input files.
@@ -9452,7 +10119,7 @@ as in the following:
 @noindent
 the variable is set at the very beginning, even before the
 @code{BEGIN} rules execute.  The @option{-v} option and its assignment
-must precede all the file name arguments, as well as the program text.
+must precede all the @value{FN} arguments, as well as the program text.
 (@xref{Options}, for more information about
 the @option{-v} option.)
 Otherwise, the variable assignment is performed at a time determined by
@@ -9460,7 +10127,7 @@ its position among the input file arguments---after the processing of the
 preceding input file argument.  For example:
 
 @example
-awk '@{ print $n @}' n=4 inventory-shipped n=2 BBS-list
+awk '@{ print $n @}' n=4 inventory-shipped n=2 mail-list
 @end example
 
 @noindent
@@ -9469,10 +10136,10 @@ the first file is read, the command line sets the variable @code{n}
 equal to four.  This causes the fourth field to be printed in lines from
 @file{inventory-shipped}.  After the first file has finished,
 but before the second file is started, @code{n} is set to two, so that the
-second field is printed in lines from @file{BBS-list}:
+second field is printed in lines from @file{mail-list}:
 
 @example
-$ @kbd{awk '@{ print $n @}' n=4 inventory-shipped n=2 BBS-list}
+$ @kbd{awk '@{ print $n @}' n=4 inventory-shipped n=2 mail-list}
 @print{} 15
 @print{} 24
 @dots{}
@@ -9493,6 +10160,19 @@ sequences
 @node Conversion
 @subsection Conversion of Strings and Numbers
 
+Number to string and string to number conversion are generally
+straightforward.  There can be subtleties to be aware of;
+this @value{SECTION} discusses this important facet of @command{awk}.
+
+@menu
+* Strings And Numbers::         How @command{awk} Converts Between Strings And
+                                Numbers.
+* Locale influences conversions:: How the locale may affect conversions.
+@end menu
+
+@node Strings And Numbers
+@subsubsection How @command{awk} Converts Between Strings And Numbers
+
 @cindex converting, strings to numbers
 @cindex strings, converting
 @cindex numbers, converting
@@ -9562,6 +10242,7 @@ b = a ""
 @code{b} has the value @code{"12"}, not @code{"12.00"}.
 @value{DARKCORNER}
 
+@sidebar Pre-POSIX @command{awk} Used @code{OFMT} For String Conversion
 @cindex POSIX @command{awk}, @code{OFMT} variable and
 @cindex @code{OFMT} variable
 @cindex portability, new @command{awk} vs.@: old @command{awk}
@@ -9573,32 +10254,32 @@ specifies the output format to use when printing numbers with @code{print}.
 conversion from the semantics of printing.  Both @code{CONVFMT} and
 @code{OFMT} have the same default value: @code{"%.6g"}.  In the vast majority
 of cases, old @command{awk} programs do not change their behavior.
-However, these semantics for @code{OFMT} are something to keep in mind if you must
-port your new-style program to older implementations of @command{awk}.
-We recommend
-that instead of changing your programs, just port @command{gawk} itself.
-@xref{Print},
-for more information on the @code{print} statement.
-
-And, once again, where you are can matter when it comes to converting
-between numbers and strings.  In @ref{Locales}, we mentioned that
-the local character set and language (the locale) can affect how
-@command{gawk} matches characters.  The locale also affects numeric
-formats.  In particular, for @command{awk} programs, it affects the
-decimal point character.  The @code{"C"} locale, and most English-language
-locales, use the period character (@samp{.}) as the decimal point.
-However, many (if not most) European and non-English locales use the comma
-(@samp{,}) as the decimal point character.
+@xref{Print}, for more information on the @code{print} statement.
+@end sidebar
+
+@node Locale influences conversions
+@subsubsection Locales Can Influence Conversion
+
+Where you are can matter when it comes to converting between numbers and
+strings.  The local character set and language---the @dfn{locale}---can
+affect numeric formats.  In particular, for @command{awk} programs,
+it affects the decimal point character and the thousands-separator
+character.  The @code{"C"} locale, and most English-language locales,
+use the period character (@samp{.}) as the decimal point and don't
+have a thousands separator.  However, many (if not most) European and
+non-English locales use the comma (@samp{,}) as the decimal point
+character. European locales often use either a space or a period as
+the thousands separator, if they have one.
 
 @cindex dark corner, locale's decimal point character
 The POSIX standard says that @command{awk} always uses the period as the decimal
-point when reading the @command{awk} program source code, and for command-line
-variable assignments (@pxref{Other Arguments}).
-However, when interpreting input data, for @code{print} and @code{printf} output,
-and for number to string conversion, the local decimal point character is used.
-@value{DARKCORNER}.
-Here are some examples indicating the difference in behavior,
-on a GNU/Linux system:
+point when reading the @command{awk} program source code, and for
+command-line variable assignments (@pxref{Other Arguments}).  However,
+when interpreting input data, for @code{print} and @code{printf} output,
+and for number to string conversion, the local decimal point character
+is used.  @value{DARKCORNER} In all cases, numbers in source code and
+in input data cannot have a thousands separator.  Here are some examples
+indicating the difference in behavior, on a GNU/Linux system:
 
 @example
 $ @kbd{export POSIXLY_CORRECT=1}                        @ii{Force POSIX behavior}
@@ -9613,7 +10294,7 @@ $ @kbd{echo 4,321 | LC_ALL=en_DK.utf-8 gawk '@{ print $1 + 1 @}'}
 @end example
 
 @noindent
-The @samp{en_DK.utf-8} locale is for English in Denmark, where the comma acts as
+The @code{en_DK.utf-8} locale is for English in Denmark, where the comma acts as
 the decimal point separator.  In the normal @code{"C"} locale, @command{gawk}
 treats @samp{4,321} as @samp{4}, while in the Danish locale, it's treated
 as the full number, 4.321.
@@ -9760,7 +10441,7 @@ b * int(a / b) + (a % b) == a
 @end example
 
 One possibly undesirable effect of this definition of remainder is that
-@code{@var{x} % @var{y}} is negative if @var{x} is negative.  Thus:
+@samp{@var{x} % @var{y}} is negative if @var{x} is negative.  Thus:
 
 @example
 -17 % 8 = -1
@@ -9768,7 +10449,7 @@ One possibly undesirable effect of this definition of remainder is that
 
 In other @command{awk} implementations, the signedness of the remainder
 may be machine-dependent.
-@c !!! what does posix say?
+@c FIXME !!! what does posix say?
 
 @cindex portability, @code{**} operator and
 @cindex @code{*} (asterisk), @code{**} operator
@@ -9795,9 +10476,9 @@ specific operator to represent it.  Instead, concatenation is performed by
 writing expressions next to one another, with no operator.  For example:
 
 @example
-$ @kbd{awk '@{ print "Field number one: " $1 @}' BBS-list}
-@print{} Field number one: aardvark
-@print{} Field number one: alpo-net
+$ @kbd{awk '@{ print "Field number one: " $1 @}' mail-list}
+@print{} Field number one: Amelia
+@print{} Field number one: Anthony
 @dots{}
 @end example
 
@@ -9805,9 +10486,9 @@ Without the space in the string constant after the @samp{:}, the line
 runs together.  For example:
 
 @example
-$ @kbd{awk '@{ print "Field number one:" $1 @}' BBS-list}
-@print{} Field number one:aardvark
-@print{} Field number one:alpo-net
+$ @kbd{awk '@{ print "Field number one:" $1 @}' mail-list}
+@print{} Field number one:Amelia
+@print{} Field number one:Anthony
 @dots{}
 @end example
 
@@ -9824,6 +10505,8 @@ name = "name"
 print "something meaningful" > file name
 @end example
 
+@cindex Brian Kernighan's @command{awk}
+@cindex @command{mawk} utility
 @noindent
 This produces a syntax error with some versions of Unix
 @command{awk}.@footnote{It happens that Brian Kernighan's
@@ -9852,7 +10535,7 @@ BEGIN @{
 @end example
 
 @noindent
-It is not defined whether the assignment to @code{a} happens
+It is not defined whether the second assignment to @code{a} happens
 before or after the value of @code{a} is retrieved for producing the
 concatenated value.  The result could be either @samp{don't panic},
 or @samp{panic panic}.
@@ -9974,8 +10657,8 @@ element. (Such values are called @dfn{rvalues}.)
 
 @cindex variables, types of
 It is important to note that variables do @emph{not} have permanent types.
-A variable's type is simply the type of whatever value it happens
-to hold at the moment.  In the following program fragment, the variable
+A variable's type is simply the type of whatever value was last assigned
+to it.  In the following program fragment, the variable
 @code{foo} has a numeric value at first, and a string value later on:
 
 @example
@@ -10076,6 +10759,7 @@ The indices of @code{bar} are practically guaranteed to be different, because
 and see @ref{Numeric Functions}, for more information).
 This example illustrates an important fact about assignment
 operators: the lefthand expression is only evaluated @emph{once}.
+
 It is up to the implementation as to which expression is evaluated
 first, the lefthand or the righthand.
 Consider this example:
@@ -10108,17 +10792,17 @@ to a number.
 @caption{Arithmetic Assignment Operators}
 @multitable @columnfractions .30 .70
 @headitem Operator @tab Effect
-@item @var{lvalue} @code{+=} @var{increment} @tab Adds @var{increment} to the value of @var{lvalue}.
-@item @var{lvalue} @code{-=} @var{decrement} @tab Subtracts @var{decrement} from the value of @var{lvalue}.
-@item @var{lvalue} @code{*=} @var{coefficient} @tab Multiplies the value of @var{lvalue} by @var{coefficient}.
-@item @var{lvalue} @code{/=} @var{divisor} @tab Divides the value of @var{lvalue} by @var{divisor}.
-@item @var{lvalue} @code{%=} @var{modulus} @tab Sets @var{lvalue} to its remainder by @var{modulus}.
+@item @var{lvalue} @code{+=} @var{increment} @tab Add @var{increment} to the value of @var{lvalue}.
+@item @var{lvalue} @code{-=} @var{decrement} @tab Subtract @var{decrement} from the value of @var{lvalue}.
+@item @var{lvalue} @code{*=} @var{coefficient} @tab Multiply the value of @var{lvalue} by @var{coefficient}.
+@item @var{lvalue} @code{/=} @var{divisor} @tab Divide the value of @var{lvalue} by @var{divisor}.
+@item @var{lvalue} @code{%=} @var{modulus} @tab Set @var{lvalue} to its remainder by @var{modulus}.
 @cindex common extensions, @code{**=} operator
 @cindex extensions, common@comma{} @code{**=} operator
 @cindex @command{awk} language, POSIX version
 @cindex POSIX @command{awk}
 @item @var{lvalue} @code{^=} @var{power} @tab
-@item @var{lvalue} @code{**=} @var{power} @tab Raises @var{lvalue} to the power @var{power}. @value{COMMONEXT}
+@item @var{lvalue} @code{**=} @var{power} @tab Raise @var{lvalue} to the power @var{power}. @value{COMMONEXT}
 @end multitable
 @end float
 
@@ -10163,10 +10847,8 @@ A workaround is:
 awk '/[=]=/' /dev/null
 @end example
 
-@command{gawk} does not have this problem,
-nor do the other
-freely available versions described in
-@ref{Other Versions}.
+@command{gawk} does not have this problem; Brian Kernighan's @command{awk}
+and @command{mawk} also do not (@pxref{Other Versions}).
 @end sidebar
 @c ENDOFRANGE exas
 @c ENDOFRANGE opas
@@ -10190,11 +10872,10 @@ are convenient abbreviations for very common operations.
 @cindex side effects, decrement/increment operators
 The operator used for adding one is written @samp{++}.  It can be used to increment
 a variable either before or after taking its value.
-To pre-increment a variable @code{v}, write @samp{++v}.  This adds
+To @dfn{pre-increment} a variable @code{v}, write @samp{++v}.  This adds
 one to the value of @code{v}---that new value is also the value of the
-expression. (The assignment expression @samp{v += 1} is completely
-equivalent.)
-Writing the @samp{++} after the variable specifies post-increment.  This
+expression. (The assignment expression @samp{v += 1} is completely equivalent.)
+Writing the @samp{++} after the variable specifies @dfn{post-increment}.  This
 increments the variable value just the same; the difference is that the
 value of the increment expression itself is the variable's @emph{old}
 value.  Thus, if @code{foo} has the value four, then the expression @samp{foo++}
@@ -10206,7 +10887,18 @@ The post-increment @samp{foo++} is nearly the same as writing @samp{(foo
 += 1) - 1}.  It is not perfectly equivalent because all numbers in
 @command{awk} are floating-point---in floating-point, @samp{foo + 1 - 1} does
 not necessarily equal @code{foo}.  But the difference is minute as
-long as you stick to numbers that are fairly small (less than 10e12).
+long as you stick to numbers that are fairly small (less than
+@iftex
+@math{10^12}).
+@end iftex
+@ifnottex
+@ifnotdocbook
+10e12).
+@end ifnotdocbook
+@end ifnottex
+@docbook
+10<superscript>12</superscript>). @c
+@end docbook
 
 @cindex @code{$} (dollar sign), incrementing fields and arrays
 @cindex dollar sign (@code{$}), incrementing fields and arrays
@@ -10215,6 +10907,7 @@ just like variables.  (Use @samp{$(i++)} when you want to do a field reference
 and a variable increment at the same time.  The parentheses are necessary
 because of the precedence of the field reference operator @samp{$}.)
 
+@c STARTOFRANGE deop
 @cindex decrement operators
 The decrement operator @samp{--} works just like @samp{++}, except that
 it subtracts one instead of adding it.  As with @samp{++}, it can be used before
@@ -10393,6 +11086,7 @@ like a number---for example, @code{@w{" +2"}}.  This concept is used
 for determining the type of a variable.
 The type of the variable is important because the types of two variables
 determine how they are compared.
+
 The various versions of the POSIX standard did not get the rules
 quite right for several editions.  Fortunately, as of at least the
 2008 standard (and possibly earlier), the standard has been fixed,
@@ -10400,7 +11094,7 @@ and variable typing follows these rules:@footnote{@command{gawk} has
 followed these rules for many years,
 and it is gratifying that the POSIX standard is also now correct.}
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 A numeric constant or the result of a numeric operation has the @var{numeric}
 attribute.
@@ -10486,6 +11180,7 @@ STRNUM  &&string	&numeric	&numeric\cr
 }}}
 @end tex
 @ifnottex
+@ifnotdocbook
 @display
         +----------------------------------------------
         |       STRING          NUMERIC         STRNUM
@@ -10498,7 +11193,51 @@ NUMERIC |       string          numeric         numeric
 STRNUM  |       string          numeric         numeric
 --------+----------------------------------------------
 @end display
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<informaltable>
+<tgroup cols="4">
+<colspec colname="1" align="left"/>
+<colspec colname="2" align="left"/>
+<colspec colname="3" align="left"/>
+<colspec colname="4" align="left"/>
+<thead>
+<row>
+<entry/>
+<entry>STRING</entry>
+<entry>NUMERIC</entry>
+<entry>STRNUM</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+<entry><emphasis role="bold">STRING</emphasis></entry>
+<entry>string</entry>
+<entry>string</entry>
+<entry>string</entry>
+</row>
+
+<row>
+<entry><emphasis role="bold">NUMERIC</emphasis></entry>
+<entry>string</entry>
+<entry>numeric</entry>
+<entry>numeric</entry>
+</row>
+
+<row>
+<entry><emphasis role="bold">STRNUM</emphasis></entry>
+<entry>string</entry>
+<entry>numeric</entry>
+<entry>numeric</entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 The basic idea is that user input that looks numeric---and @emph{only}
 user input---should be treated as numeric, even though it is actually
@@ -10517,8 +11256,8 @@ This point bears additional emphasis: All user input is made of characters,
 and so is first and foremost of @var{string} type; input strings
 that look numeric are additionally given the @var{strnum} attribute.
 Thus, the six-character input string @w{@samp{ +3.14}} receives the
-@var{strnum} attribute. In contrast, the eight-character literal
-@w{@code{" +3.14"}} appearing in program text is a string constant.
+@var{strnum} attribute. In contrast, the eight characters
+@w{@code{" +3.14"}} appearing in program text comprise a string constant.
 The following examples print @samp{1} when the comparison between
 the two different constants is true, @samp{0} otherwise:
 
@@ -10633,7 +11372,7 @@ string comparison (true)
 string comparison (true)
 
 @item a = 2; b = " +2"
-@item a == b
+@itemx a == b
 string comparison (false)
 @end table
 
@@ -10679,7 +11418,7 @@ has the value one if @code{x} contains @samp{foo}, such as
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
 The righthand operand of the @samp{~} and @samp{!~} operators may be
-either a regexp constant (@code{/@dots{}/}) or an ordinary
+either a regexp constant (@code{/}@dots{}@code{/}) or an ordinary
 expression. In the latter case, the value of the expression as a string is used as a
 dynamic regexp (@pxref{Regexp Usage}; also
 @pxref{Computed Regexps}).
@@ -10704,7 +11443,9 @@ where this is discussed in more detail.
 @subsubsection String Comparison With POSIX Rules
 
 The POSIX standard says that string comparison is performed based
-on the locale's collating order.  This is usually very different
+on the locale's @dfn{collating order}. This is the order in which
+characters sort, as defined by the locale (for more discussion,
+@pxref{Ranges and Locales}).  This order is usually very different
 from the results obtained when doing straight character-by-character
 comparison.@footnote{Technically, string comparison is supposed
 to behave the same way as if the strings are compared with the C
@@ -10712,7 +11453,7 @@ to behave the same way as if the strings are compared with the C
 
 Because this behavior differs considerably from existing practice,
 @command{gawk} only implements it when in POSIX mode (@pxref{Options}).
-Here is an example to illustrate the difference, in an @samp{en_US.UTF-8}
+Here is an example to illustrate the difference, in an @code{en_US.UTF-8}
 locale:
 
 @example
@@ -10767,10 +11508,10 @@ The Boolean operators are:
 @item @var{boolean1} && @var{boolean2}
 True if both @var{boolean1} and @var{boolean2} are true.  For example,
 the following statement prints the current input record if it contains
-both @samp{2400} and @samp{foo}:
+both @samp{edu} and @samp{li}:
 
 @example
-if ($0 ~ /2400/ && $0 ~ /foo/) print
+if ($0 ~ /edu/ && $0 ~ /li/) print
 @end example
 
 @cindex side effects, Boolean operators
@@ -10783,11 +11524,11 @@ no substring @samp{foo} in the record.
 @item @var{boolean1} || @var{boolean2}
 True if at least one of @var{boolean1} or @var{boolean2} is true.
 For example, the following statement prints all records in the input
-that contain @emph{either} @samp{2400} or
-@samp{foo} or both:
+that contain @emph{either} @samp{edu} or
+@samp{li} or both:
 
 @example
-if ($0 ~ /2400/ || $0 ~ /foo/) print
+if ($0 ~ /edu/ || $0 ~ /li/) print
 @end example
 
 The subexpression @var{boolean2} is evaluated only if @var{boolean1}
@@ -10928,7 +11669,7 @@ However, putting a newline in front
 of either character does not work without using backslash continuation
 (@pxref{Statements/Lines}).
 If @option{--posix} is specified
-(@pxref{Options}), then this extension is disabled.
+(@pxref{Options}), this extension is disabled.
 
 @node Function Calls
 @section Function Calls
@@ -10947,6 +11688,8 @@ functions and their descriptions.  In addition, you can define
 functions for use in your program.
 @xref{User-defined},
 for instructions on how to do this.
+Finally, @command{gawk} lets you write functions in C or C++
+that may be called from your program: see @ref{Dynamic Extensions}.
 
 @cindex arguments, in function calls
 The way to use a function is with a @dfn{function call} expression,
@@ -10988,7 +11731,9 @@ If those arguments are not supplied, the functions
 use a reasonable default value.
 @xref{Built-in}, for full details.  If arguments
 are omitted in calls to user-defined functions, then those arguments are
-treated as local variables and initialized to the empty string
+treated as local variables. Such local variables act like the
+empty string if referenced where a string value is required,
+and like zero if referenced where a numeric value is required
 (@pxref{User-defined}).
 
 As an advanced feature, @command{gawk} provides indirect function calls,
@@ -10997,12 +11742,12 @@ when you write the source code to your program. We defer discussion of
 this feature until later; see @ref{Indirect Calls}.
 
 @cindex side effects, function calls
-Like every other expression, the function call has a value, which is
-computed by the function based on the arguments you give it.  In this
-example, the value of @samp{sqrt(@var{argument})} is the square root of
-@var{argument}.
-The following program reads numbers, one number per line, and prints the
-square root of each one:
+Like every other expression, the function call has a value, often
+called the @dfn{return value}, which is computed by the function
+based on the arguments you give it.  In this example, the return value
+of @samp{sqrt(@var{argument})} is the square root of @var{argument}.
+The following program reads numbers, one number per line, and prints
+the square root of each one:
 
 @example
 $ @kbd{awk '@{ print "The square root of", $1, "is", sqrt($1) @}'}
@@ -11090,28 +11835,28 @@ expression because the first @samp{$} has higher precedence than the
 This table presents @command{awk}'s operators, in order of highest
 to lowest precedence:
 
-@c use @code in the items, looks better in TeX w/o all the quotes
-@table @code
-@item (@dots{})
+@c @asis for docbook to come out right
+@table @asis
+@item @code{(}@dots{}@code{)}
 Grouping.
 
 @cindex @code{$} (dollar sign), @code{$} field operator
 @cindex dollar sign (@code{$}), @code{$} field operator
-@item $
+@item @code{$}
 Field reference.
 
 @cindex @code{+} (plus sign), @code{++} operator
 @cindex plus sign (@code{+}), @code{++} operator
 @cindex @code{-} (hyphen), @code{--} operator
 @cindex hyphen (@code{-}), @code{--} operator
-@item ++ --
+@item @code{++ --}
 Increment, decrement.
 
 @cindex @code{^} (caret), @code{^} operator
 @cindex caret (@code{^}), @code{^} operator
 @cindex @code{*} (asterisk), @code{**} operator
 @cindex asterisk (@code{*}), @code{**} operator
-@item ^ **
+@item @code{^ **}
 Exponentiation.  These operators group right-to-left.
 
 @cindex @code{+} (plus sign), @code{+} operator
@@ -11120,7 +11865,7 @@ Exponentiation.  These operators group right-to-left.
 @cindex hyphen (@code{-}), @code{-} operator
 @cindex @code{!} (exclamation point), @code{!} operator
 @cindex exclamation point (@code{!}), @code{!} operator
-@item + - !
+@item @code{+ - !}
 Unary plus, minus, logical ``not.''
 
 @cindex @code{*} (asterisk), @code{*} operator, as multiplication operator
@@ -11129,17 +11874,17 @@ Unary plus, minus, logical ``not.''
 @cindex forward slash (@code{/}), @code{/} operator
 @cindex @code{%} (percent sign), @code{%} operator
 @cindex percent sign (@code{%}), @code{%} operator
-@item * / %
+@item @code{* / %}
 Multiplication, division, remainder.
 
 @cindex @code{+} (plus sign), @code{+} operator
 @cindex plus sign (@code{+}), @code{+} operator
 @cindex @code{-} (hyphen), @code{-} operator
 @cindex hyphen (@code{-}), @code{-} operator
-@item + -
+@item @code{+ -}
 Addition, subtraction.
 
-@item @r{String Concatenation}
+@item String Concatenation
 There is no special symbol for concatenation.
 The operands are simply written side by side
 (@pxref{Concatenation}).
@@ -11165,7 +11910,7 @@ The operands are simply written side by side
 @cindex @code{|} (vertical bar), @code{|&} operator (I/O)
 @cindex vertical bar (@code{|}), @code{|&} operator (I/O)
 @cindex operators, input/output
-@item < <= == != > >= >> | |&
+@item @code{< <= == != > >= >> | |&}
 Relational and redirection.
 The relational operators and the redirections have the same precedence
 level.  Characters such as @samp{>} serve both as relationals and as
@@ -11186,26 +11931,26 @@ The correct way to write this statement is @samp{print foo > (a ? b : c)}.
 @cindex tilde (@code{~}), @code{~} operator
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
-@item ~ !~
+@item @code{~ !~}
 Matching, nonmatching.
 
 @cindex @code{in} operator
-@item in
+@item @code{in}
 Array membership.
 
 @cindex @code{&} (ampersand), @code{&&} operator
 @cindex ampersand (@code{&}), @code{&&} operator
-@item &&
+@item @code{&&}
 Logical ``and''.
 
 @cindex @code{|} (vertical bar), @code{||} operator
 @cindex vertical bar (@code{|}), @code{||} operator
-@item ||
+@item @code{||}
 Logical ``or''.
 
 @cindex @code{?} (question mark), @code{?:} operator
 @cindex question mark (@code{?}), @code{?:} operator
-@item ?:
+@item @code{?:}
 Conditional.  This operator groups right-to-left.
 
 @cindex @code{+} (plus sign), @code{+=} operator
@@ -11222,7 +11967,7 @@ Conditional.  This operator groups right-to-left.
 @cindex percent sign (@code{%}), @code{%=} operator
 @cindex @code{^} (caret), @code{^=} operator
 @cindex caret (@code{^}), @code{^=} operator
-@item = += -= *= /= %= ^= **=
+@item @code{= += -= *= /= %= ^= **=}
 Assignment.  These operators group right-to-left.
 @end table
 
@@ -11239,27 +11984,102 @@ For maximum portability, do not use them.
 @section Where You Are Makes A Difference
 @cindex locale, definition of
 
-Modern systems support the notion of @dfn{locales}: a way to tell
-the system about the local character set and language.
+Modern systems support the notion of @dfn{locales}: a way to tell the
+system about the local character set and language.  The ISO C standard
+defines a default @code{"C"} locale, which is an environment that is
+typical of what many C programmers are used to.
 
 Once upon a time, the locale setting used to affect regexp matching
 (@pxref{Ranges and Locales}), but this is no longer true.
 
-Locales can affect record splitting.
-For the normal case of @samp{RS = "\n"}, the locale is largely irrelevant.
-For other single-character record separators, setting @samp{LC_ALL=C}
-in the environment
-will give you much better performance when reading records.  Otherwise,
+Locales can affect record splitting.  For the normal case of @samp{RS =
+"\n"}, the locale is largely irrelevant.  For other single-character
+record separators, setting @samp{LC_ALL=C} in the environment will
+give you much better performance when reading records.  Otherwise,
 @command{gawk} has to make several function calls, @emph{per input
 character}, to find the record terminator.
 
-According to POSIX, string comparison is also affected by locales
-(similar to regular expressions).  The details are presented in
-@ref{POSIX String Comparison}.
+Locales can affect how dates and times are formatted (@pxref{Time
+Functions}).  For example, a common way to abbreviate the date September
+4, 2015 in the United States is ``9/4/15.''  In many countries in
+Europe, however, it is abbreviated ``4.9.15.''  Thus, the @samp{%x}
+specification in a @code{"US"} locale might produce @samp{9/4/15},
+while in a @code{"EUROPE"} locale, it might produce @samp{4.9.15}.
+
+According to POSIX, string comparison is also affected by locales (similar
+to regular expressions).  The details are presented in @ref{POSIX String
+Comparison}.
 
 Finally, the locale affects the value of the decimal point character
-used when @command{gawk} parses input data.  This is discussed in
-detail in @ref{Conversion}.
+used when @command{gawk} parses input data.  This is discussed in detail
+in @ref{Conversion}.
+
+@node Expressions Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Expressions are the basic elements of computation in programs.  They are
+built from constants, variables, function calls and combinations of the
+various kinds of values with operators.
+
+@item
+@command{awk} supplies three kinds of constants: numeric, string, and
+regexp.  @command{gawk} lets you specify numeric constants in octal
+and hexadecimal (bases 8 and 16) in addition to decimal (base 10).
+In certain contexts, a standalone regexp constant such as @code{/foo/}
+has the same meaning as @samp{$0 ~ /foo/}.
+
+@item
+Variables hold values between uses in computations. A number of built-in
+variables provide information to your @command{awk} program, and a number
+of others let you control how @command{awk} behaves.
+
+@item
+Numbers are automatically converted to strings, and strings to numbers,
+as needed by @command{awk}. Numeric values are converted as if they were
+formatted with @code{sprintf()} using the format in @code{CONVFMT}.
+Locales can influence the conversions.
+
+@item
+@command{awk} provides the usual arithmetic operators (addition,
+subtraction, multiplication, division, modulus), and unary plus and minus.
+It also provides comparison operators, boolean operators, and regexp
+matching operators.  String concatenation is accomplished by placing
+two expressions next to each other; there is no explicit operator.
+The three-operand @samp{?:} operator provides an ``if-else'' test within
+expressions.
+
+@item
+Assignment operators provide convenient shorthands for common arithmetic
+operations.
+
+@item
+In @command{awk}, a value is considered to be true if it is non-zero
+@emph{or} non-null. Otherwise, the value is false.
+
+@item
+A value's type is set upon each assignment and may change over its
+lifetime.  The type determines how it behaves in comparisons (string
+or numeric).
+
+@item
+Function calls return a value which may be used as part of a larger
+expression.  Expressions used to pass parameter values are fully
+evaluated before the function is called.  @command{awk} provides
+built-in and user-defined functions; this is described later on in this
+@value{DOCUMENT}.
+
+@item
+Operator precedence specifies the order in which operations are performed,
+unless explicitly overridden by parentheses.  @command{awk}'s operator
+precedence is compatible with that of C.
+
+@item
+Locales can affect the format of data as output by an @command{awk}
+program, and occasionally the format for data read as input.
+
+@end itemize
 
 @c ENDOFRANGE exps
 
@@ -11287,6 +12107,7 @@ building something useful.
 * Statements::                  Describes the various control statements in
                                 detail.
 * Built-in Variables::          Summarizes the built-in variables.
+* Pattern Action Summary::      Patterns and Actions summary.
 @end menu
 
 @node Pattern Overview
@@ -11317,10 +12138,10 @@ A single expression.  It matches when its value
 is nonzero (if a number) or non-null (if a string).
 (@xref{Expression Patterns}.)
 
-@item @var{pat1}, @var{pat2}
+@item @var{begpat}, @var{endpat}
 A pair of patterns separated by a comma, specifying a range of records.
-The range includes both the initial record that matches @var{pat1} and
-the final record that matches @var{pat2}.
+The range includes both the initial record that matches @var{begpat} and
+the final record that matches @var{endpat}.
 (@xref{Ranges}.)
 
 @item BEGIN
@@ -11332,7 +12153,7 @@ Special patterns for you to supply startup or cleanup actions for your
 @item BEGINFILE
 @itemx ENDFILE
 Special patterns for you to supply startup or cleanup actions to be
-done on a per file basis.
+done on a per-file basis.
 (@xref{BEGINFILE/ENDFILE}.)
 
 @item @var{empty}
@@ -11382,7 +12203,7 @@ slashes (@code{/@var{regexp}/}), or any expression whose string value
 is used as a dynamic regular expression
 (@pxref{Computed Regexps}).
 The following example prints the second field of each input record
-whose first field is precisely @samp{foo}:
+whose first field is precisely @samp{li}:
 
 @cindex @code{/} (forward slash), patterns and
 @cindex forward slash (@code{/}), patterns and
@@ -11391,68 +12212,65 @@ whose first field is precisely @samp{foo}:
 @cindex @code{!} (exclamation point), @code{!~} operator
 @cindex exclamation point (@code{!}), @code{!~} operator
 @example
-$ @kbd{awk '$1 == "foo" @{ print $2 @}' BBS-list}
+$ @kbd{awk '$1 == "li" @{ print $2 @}' mail-list}
 @end example
 
 @noindent
-(There is no output, because there is no BBS site with the exact name @samp{foo}.)
+(There is no output, because there is no person with the exact name @samp{li}.)
 Contrast this with the following regular expression match, which
-accepts any record with a first field that contains @samp{foo}:
+accepts any record with a first field that contains @samp{li}:
 
 @example
-$ @kbd{awk '$1 ~ /foo/ @{ print $2 @}' BBS-list}
-@print{} 555-1234
+$ @kbd{awk '$1 ~ /foo/ @{ print $2 @}' mail-list}
+@print{} 555-5553
 @print{} 555-6699
-@print{} 555-6480
-@print{} 555-2127
 @end example
 
 @cindex regexp constants, as patterns
 @cindex patterns, regexp constants as
 A regexp constant as a pattern is also a special case of an expression
-pattern.  The expression @code{/foo/} has the value one if @samp{foo}
-appears in the current input record. Thus, as a pattern, @code{/foo/}
-matches any record containing @samp{foo}.
+pattern.  The expression @code{/li/} has the value one if @samp{li}
+appears in the current input record. Thus, as a pattern, @code{/li/}
+matches any record containing @samp{li}.
 
 @cindex Boolean expressions, as patterns
 Boolean expressions are also commonly used as patterns.
 Whether the pattern
 matches an input record depends on whether its subexpressions match.
 For example, the following command prints all the records in
-@file{BBS-list} that contain both @samp{2400} and @samp{foo}:
+@file{mail-list} that contain both @samp{edu} and @samp{li}:
 
 @example
-$ @kbd{awk '/2400/ && /foo/' BBS-list}
-@print{} fooey        555-1234     2400/1200/300     B
+$ @kbd{awk '/edu/ && /li/' mail-list}
+@print{} Samuel       555-3430     samuel.lanceolis@@shu.edu        A
 @end example
 
 The following command prints all records in
-@file{BBS-list} that contain @emph{either} @samp{2400} or @samp{foo}
+@file{mail-list} that contain @emph{either} @samp{edu} or @samp{li}
 (or both, of course):
 
 @example
-$ @kbd{awk '/2400/ || /foo/' BBS-list}
-@print{} alpo-net     555-3412     2400/1200/300     A
-@print{} bites        555-1675     2400/1200/300     A
-@print{} fooey        555-1234     2400/1200/300     B
-@print{} foot         555-6699     1200/300          B
-@print{} macfoo       555-6480     1200/300          A
-@print{} sdace        555-3430     2400/1200/300     A
-@print{} sabafoo      555-2127     1200/300          C
+$ @kbd{awk '/edu/ || /li/' mail-list}
+@print{} Amelia       555-5553     amelia.zodiacusque@@gmail.com    F
+@print{} Broderick    555-0542     broderick.aliquotiens@@yahoo.com R
+@print{} Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+@print{} Julie        555-6699     julie.perscrutabor@@skeeve.com   F
+@print{} Samuel       555-3430     samuel.lanceolis@@shu.edu        A
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @end example
 
 The following command prints all records in
-@file{BBS-list} that do @emph{not} contain the string @samp{foo}:
+@file{mail-list} that do @emph{not} contain the string @samp{li}:
 
 @example
-$ @kbd{awk '! /foo/' BBS-list}
-@print{} aardvark     555-5553     1200/300          B
-@print{} alpo-net     555-3412     2400/1200/300     A
-@print{} barfly       555-7685     1200/300          A
-@print{} bites        555-1675     2400/1200/300     A
-@print{} camelot      555-0542     300               C
-@print{} core         555-2912     1200/300          C
-@print{} sdace        555-3430     2400/1200/300     A
+$ @kbd{awk '! /li/' mail-list}
+@print{} Anthony      555-3412     anthony.asserturo@@hotmail.com   A
+@print{} Becky        555-7685     becky.algebrarum@@gmail.com      A
+@print{} Bill         555-1675     bill.drowning@@hotmail.com       A
+@print{} Camilla      555-2912     camilla.infusarum@@skynet.be     R
+@print{} Fabius       555-1234     fabius.undevicesimus@@ucb.edu    F
+@print{} Martin       555-6480     martin.codicibus@@hotmail.com    A
+@print{} Jean-Paul    555-2127     jeanpaul.campanorum@@nyu.edu     R
 @end example
 
 @cindex @code{BEGIN} pattern, Boolean patterns and
@@ -11496,7 +12314,7 @@ input record.  When a record matches @var{begpat}, the range pattern is
 @dfn{turned on} and the range pattern matches this record as well.  As long as
 the range pattern stays turned on, it automatically matches every input
 record read.  The range pattern also matches @var{endpat} against every
-input record; when this succeeds, the range pattern is turned off again
+input record; when this succeeds, the range pattern is @dfn{turned off} again
 for the following record.  Then the range pattern goes back to checking
 @var{begpat} against each record.
 
@@ -11556,6 +12374,11 @@ $ @kbd{echo Yes | gawk '(/1/,/2/) || /Yes/'}
 @error{} gawk: cmd. line:1:           ^ syntax error
 @end example
 
+@cindex range patterns, line continuation and
+As a minor point of interest, although it is poor style,
+POSIX allows you to put a newline after the comma in
+a range pattern.  @value{DARKCORNER}
+
 @node BEGIN/END
 @subsection The @code{BEGIN} and @code{END} Special Patterns
 
@@ -11580,28 +12403,30 @@ programmers.
 @node Using BEGIN/END
 @subsubsection Startup and Cleanup Actions
 
+@cindex @code{BEGIN} pattern
+@cindex @code{END} pattern
 A @code{BEGIN} rule is executed once only, before the first input record
 is read. Likewise, an @code{END} rule is executed once only, after all the
 input is read.  For example:
 
 @example
 $ @kbd{awk '}
-> @kbd{BEGIN @{ print "Analysis of \"foo\"" @}}
-> @kbd{/foo/ @{ ++n @}}
-> @kbd{END   @{ print "\"foo\" appears", n, "times." @}' BBS-list}
-@print{} Analysis of "foo"
-@print{} "foo" appears 4 times.
+> @kbd{BEGIN @{ print "Analysis of \"li\"" @}}
+> @kbd{/li/ @{ ++n @}}
+> @kbd{END   @{ print "\"li\" appears in", n, "records." @}' mail-list}
+@print{} Analysis of "li"
+@print{} "li" appears in 4 records.
 @end example
 
 @cindex @code{BEGIN} pattern, operators and
 @cindex @code{END} pattern, operators and
-This program finds the number of records in the input file @file{BBS-list}
-that contain the string @samp{foo}.  The @code{BEGIN} rule prints a title
+This program finds the number of records in the input file @file{mail-list}
+that contain the string @samp{li}.  The @code{BEGIN} rule prints a title
 for the report.  There is no need to use the @code{BEGIN} rule to
 initialize the counter @code{n} to zero, since @command{awk} does this
 automatically (@pxref{Variables}).
 The second rule increments the variable @code{n} every time a
-record containing the pattern @samp{foo} is read.  The @code{END} rule
+record containing the pattern @samp{li} is read.  The @code{END} rule
 prints the value of @code{n} at the end of the run.
 
 The special patterns @code{BEGIN} and @code{END} cannot be used in ranges
@@ -11643,7 +12468,7 @@ rule checks the @code{FNR} and @code{NR} variables.
 @subsubsection Input/Output from @code{BEGIN} and @code{END} Rules
 
 @cindex input/output, from @code{BEGIN} and @code{END}
-There are several (sometimes subtle) points to remember when doing I/O
+There are several (sometimes subtle) points to be aware of when doing I/O
 from a @code{BEGIN} or @code{END} rule.
 The first has to do with the value of @code{$0} in a @code{BEGIN}
 rule.  Because @code{BEGIN} rules are executed before any input is read,
@@ -11654,6 +12479,7 @@ to give @code{$0} a real value is to execute a @code{getline} command
 without a variable (@pxref{Getline}).
 Another way is simply to assign a value to @code{$0}.
 
+@cindex Brian Kernighan's @command{awk}
 @cindex differences in @command{awk} and @command{gawk}, @code{BEGIN}/@code{END} patterns
 @cindex POSIX @command{awk}, @code{BEGIN}/@code{END} patterns
 @cindex @code{print} statement, @code{BEGIN}/@code{END} patterns and
@@ -11703,8 +12529,19 @@ This @value{SECTION} describes a @command{gawk}-specific feature.
 
 Two special kinds of rule, @code{BEGINFILE} and @code{ENDFILE}, give
 you ``hooks'' into @command{gawk}'s command-line file processing loop.
-As with the @code{BEGIN} and @code{END} rules (@pxref{BEGIN/END}), all
-@code{BEGINFILE} rules in a program are merged, in the order they are
+As with the @code{BEGIN} and @code{END} rules
+@ifnottex
+@ifnotdocbook
+(@pxref{BEGIN/END}),
+@end ifnotdocbook
+@end ifnottex
+@iftex
+(see the previous section),
+@end iftex
+@ifdocbook
+(see the previous section),
+@end ifdocbook
+all @code{BEGINFILE} rules in a program are merged, in the order they are
 read by @command{gawk}, and all @code{ENDFILE} rules are merged as well.
 
 The body of the @code{BEGINFILE} rules is executed just before
@@ -11714,7 +12551,7 @@ is set to the name of the current file, and @code{FNR} is set to zero.
 The @code{BEGINFILE} rule provides you the opportunity to accomplish two tasks
 that would otherwise be difficult or impossible to perform:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 You can test if the file is readable.  Normally, it is a fatal error if a
 file named on the command line cannot be opened for reading.  However,
@@ -11722,7 +12559,7 @@ you can bypass the fatal error and move on to the next file on the
 command line.
 
 @cindex @command{gawk}, @code{ERRNO} variable in
-@cindex @code{ERRNO} variable
+@cindex @code{ERRNO} variable, with @code{BEGINFILE} pattern
 @cindex @code{nextfile} statement, @code{BEGINFILE}/@code{ENDFILE} patterns and
 You do this by checking if the @code{ERRNO} variable is not the empty
 string; if so, then @command{gawk} was not able to open the file. In
@@ -11732,10 +12569,11 @@ the file entirely.  Otherwise, @command{gawk} exits with the usual
 fatal error.
 
 @item
-If you have written extensions that modify the record handling (by inserting
-an ``input parser''), you can invoke them at this point, before @command{gawk}
-has started processing the file.  (This is a @emph{very} advanced feature,
-currently used only by the @uref{http://gawkextlib.sourceforge.net, @code{gawkextlib} project}.)
+If you have written extensions that modify the record handling (by
+inserting an ``input parser,'' @pxref{Input Parsers}), you can invoke
+them at this point, before @command{gawk} has started processing the file.
+(This is a @emph{very} advanced feature, currently used only by the
+@uref{http://gawkextlib.sourceforge.net, @code{gawkextlib} project}.)
 @end itemize
 
 The @code{ENDFILE} rule is called when @command{gawk} has finished processing
@@ -11757,14 +12595,14 @@ statement (@pxref{Nextfile Statement}) is allowed only inside a
 
 @cindex @code{getline} statement, @code{BEGINFILE}/@code{ENDFILE} patterns and
 The @code{getline} statement (@pxref{Getline}) is restricted inside
-both @code{BEGINFILE} and @code{ENDFILE}.  Only the @samp{getline
-@var{variable} < @var{file}} form is allowed.
+both @code{BEGINFILE} and @code{ENDFILE}: only redirected
+forms of @code{getline} are allowed.
 
 @code{BEGINFILE} and @code{ENDFILE} are @command{gawk} extensions.
 In most other @command{awk} implementations, or if @command{gawk} is in
 compatibility mode (@pxref{Options}), they are not special.
 
-@c FIXME: For 4.1 maybe deal with this?
+@c FIXME: For 4.2 maybe deal with this?
 @ignore
 Date:     Tue, 17 May 2011 02:06:10 PDT
 From:     rankin@pactechdata.com (Pat Rankin)
@@ -11795,7 +12633,7 @@ An empty (i.e., nonexistent) pattern is considered to match @emph{every}
 input record.  For example, the program:
 
 @example
-awk '@{ print $1 @}' BBS-list
+awk '@{ print $1 @}' mail-list
 @end example
 
 @noindent
@@ -11818,7 +12656,7 @@ into the body of the @command{awk} program.
 @cindex shells, quoting
 The most common method is to use shell quoting to substitute
 the variable's value into the program inside the script.
-For example, in the following program:
+For example, consider the following program:
 
 @example
 printf "Enter search pattern: "
@@ -11828,7 +12666,7 @@ awk "/$pattern/ "'@{ nmatches++ @}
 @end example
 
 @noindent
-the @command{awk} program consists of two pieces of quoted text
+The @command{awk} program consists of two pieces of quoted text
 that are concatenated together to form the program.
 The first part is double-quoted, which allows substitution of
 the @code{pattern} shell variable inside the quotes.
@@ -11842,8 +12680,8 @@ match up the quotes when reading the program.
 
 A better method is to use @command{awk}'s variable assignment feature
 (@pxref{Assignment Options})
-to assign the shell variable's value to an @command{awk} variable's
-value.  Then use dynamic regexps to match the pattern
+to assign the shell variable's value to an @command{awk} variable.
+Then use dynamic regexps to match the pattern
 (@pxref{Computed Regexps}).
 The following shows how to redo the
 previous example using this technique:
@@ -11881,13 +12719,13 @@ both) may be omitted.  The purpose of the @dfn{action} is to tell
 @command{awk} what to do once a match for the pattern is found.  Thus,
 in outline, an @command{awk} program generally looks like this:
 
-@example
-@r{[}@var{pattern}@r{]}  @{ @var{action} @}
- @var{pattern}  @r{[}@{ @var{action} @}@r{]}
+@display
+[@var{pattern}]  @code{@{ @var{action} @}}
+ @var{pattern}  [@code{@{ @var{action} @}}]
 @dots{}
-function @var{name}(@var{args}) @{ @dots{} @}
+@code{function @var{name}(@var{args}) @{ @dots{} @}}
 @dots{}
-@end example
+@end display
 
 @cindex @code{@{@}} (braces), actions and
 @cindex braces (@code{@{@}}), actions and
@@ -11896,11 +12734,11 @@ function @var{name}(@var{args}) @{ @dots{} @}
 @cindex @code{;} (semicolon), separating statements in actions
 @cindex semicolon (@code{;}), separating statements in actions
 An action consists of one or more @command{awk} @dfn{statements}, enclosed
-in curly braces (@samp{@{@dots{}@}}).  Each statement specifies one
+in braces (@samp{@{@r{@dots{}}@}}).  Each statement specifies one
 thing to do.  The statements are separated by newlines or semicolons.
-The curly braces around an action must be used even if the action
+The braces around an action must be used even if the action
 contains only one statement, or if it contains no statements at
-all.  However, if you omit the action entirely, omit the curly braces as
+all.  However, if you omit the action entirely, omit the braces as
 well.  An omitted action is equivalent to @samp{@{ print $0 @}}:
 
 @example
@@ -11926,10 +12764,9 @@ programs.  The @command{awk} language gives you C-like constructs
 special ones (@pxref{Statements}).
 
 @item Compound statements
-Consist of one or more statements enclosed in
-curly braces.  A compound statement is used in order to put several
-statements together in the body of an @code{if}, @code{while}, @code{do},
-or @code{for} statement.
+Enclose one or more statements in braces.  A compound statement
+is used in order to put several statements together in the body of an
+@code{if}, @code{while}, @code{do}, or @code{for} statement.
 
 @item Input statements
 Use the @code{getline} command
@@ -11975,7 +12812,7 @@ Many control statements contain other statements.  For example, the
 @code{if} statement contains another statement that may or may not be
 executed.  The contained statement is called the @dfn{body}.
 To include more than one statement in the body, group them into a
-single @dfn{compound statement} with curly braces, separating them with
+single @dfn{compound statement} with braces, separating them with
 newlines or semicolons.
 
 @menu
@@ -12003,9 +12840,9 @@ newlines or semicolons.
 The @code{if}-@code{else} statement is @command{awk}'s decision-making
 statement.  It looks like this:
 
-@example
-if (@var{condition}) @var{then-body} @r{[}else @var{else-body}@r{]}
-@end example
+@display
+@code{if (@var{condition}) @var{then-body}} [@code{else @var{else-body}}]
+@end display
 
 @noindent
 The @var{condition} is an expression that controls what the rest of the
@@ -12029,7 +12866,7 @@ if the value of @code{x} is evenly divisible by two), then the first
 statement is executed.
 If the @code{else} keyword appears on the same line as @var{then-body} and
 @var{then-body} is not a compound statement (i.e., not surrounded by
-curly braces), then a semicolon must separate @var{then-body} from
+braces), then a semicolon must separate @var{then-body} from
 the @code{else}.
 To illustrate this, the previous example can be rewritten as:
 
@@ -12048,6 +12885,7 @@ the first thing on its line.
 @subsection The @code{while} Statement
 @cindex @code{while} statement
 @cindex loops
+@cindex loops, @code{while}
 @cindex loops, See Also @code{while} statement
 
 In programming, a @dfn{loop} is a part of a program that can
@@ -12108,6 +12946,7 @@ program is harder to read without it.
 @node Do Statement
 @subsection The @code{do}-@code{while} Statement
 @cindex @code{do}-@code{while} statement
+@cindex loops, @code{do}-@code{while}
 
 The @code{do} loop is a variation of the @code{while} looping statement.
 The @code{do} loop executes the @var{body} once and then repeats the
@@ -12153,6 +12992,7 @@ occasionally is there a real use for a @code{do} statement.
 @node For Statement
 @subsection The @code{for} Statement
 @cindex @code{for} statement
+@cindex loops, @code{for}, iterative
 
 The @code{for} statement makes it more convenient to count iterations of a
 loop.  The general form of the @code{for} statement looks like this:
@@ -12259,6 +13099,10 @@ for more information on this version of the @code{for} loop.
 @cindex @code{case} keyword
 @cindex @code{default} keyword
 
+This @value{SECTION} describes a @command{gawk}-specific feature.
+If @command{gawk} is in compatibility mode (@pxref{Options}),
+it is not available.
+
 The @code{switch} statement allows the evaluation of an expression and
 the execution of statements based on a @code{case} match. Case statements
 are checked for a match in the order they are defined.  If no suitable
@@ -12314,15 +13158,11 @@ the @code{print} statement is executed and then falls through into the
 the @minus{}1 case will also be executed since the @code{default} does
 not halt execution.
 
-This @code{switch} statement is a @command{gawk} extension.
-If @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not available.
-
 @node Break Statement
 @subsection The @code{break} Statement
 @cindex @code{break} statement
 @cindex loops, exiting
+@cindex loops, @code{break} statement and
 
 The @code{break} statement jumps out of the innermost @code{for},
 @code{while}, or @code{do} loop that encloses it.  The following example
@@ -12332,15 +13172,15 @@ numbers:
 @example
 # find smallest divisor of num
 @{
-   num = $1
-   for (div = 2; div * div <= num; div++) @{
-     if (num % div == 0)
-       break
-   @}
-   if (num % div == 0)
-     printf "Smallest divisor of %d is %d\n", num, div
-   else
-     printf "%d is prime\n", num
+    num = $1
+    for (div = 2; div * div <= num; div++) @{
+        if (num % div == 0)
+            break
+    @}
+    if (num % div == 0)
+        printf "Smallest divisor of %d is %d\n", num, div
+    else
+        printf "%d is prime\n", num
 @}
 @end example
 
@@ -12358,17 +13198,17 @@ an @code{if}:
 @example
 # find smallest divisor of num
 @{
-  num = $1
-  for (div = 2; ; div++) @{
-    if (num % div == 0) @{
-      printf "Smallest divisor of %d is %d\n", num, div
-      break
-    @}
-    if (div * div > num) @{
-      printf "%d is prime\n", num
-      break
+    num = $1
+    for (div = 2; ; div++) @{
+        if (num % div == 0) @{
+            printf "Smallest divisor of %d is %d\n", num, div
+            break
+        @}
+        if (div * div > num) @{
+            printf "%d is prime\n", num
+            break
+        @}
     @}
-  @}
 @}
 @end example
 
@@ -12382,6 +13222,7 @@ This is discussed in @ref{Switch Statement}.
 @cindex POSIX @command{awk}, @code{break} statement and
 @cindex dark corner, @code{break} statement
 @cindex @command{gawk}, @code{break} statement in
+@cindex Brian Kernighan's @command{awk}
 The @code{break} statement has no meaning when
 used outside the body of a loop or @code{switch}.
 However, although it was never documented,
@@ -12446,6 +13287,7 @@ This program loops forever once @code{x} reaches 5.
 @cindex POSIX @command{awk}, @code{continue} statement and
 @cindex dark corner, @code{continue} statement
 @cindex @command{gawk}, @code{continue} statement in
+@cindex Brian Kernighan's @command{awk}
 The @code{continue} statement has no special meaning with respect to the
 @code{switch} statement, nor does it have any meaning when used outside the
 body of a loop.  Historical versions of @command{awk} treated a @code{continue}
@@ -12515,16 +13357,14 @@ The @code{next} statement is not allowed inside @code{BEGINFILE} and
 @cindex POSIX @command{awk}, @code{next}/@code{nextfile} statements and
 @cindex @code{next} statement, user-defined functions and
 @cindex functions, user-defined, @code{next}/@code{nextfile} statements and
-According to the POSIX standard, the behavior is undefined if
-the @code{next} statement is used in a @code{BEGIN} or @code{END} rule.
-@command{gawk} treats it as a syntax error.
-Although POSIX permits it,
-some other @command{awk} implementations don't allow the @code{next}
-statement inside function bodies
-(@pxref{User-defined}).
-Just as with any other @code{next} statement, a @code{next} statement inside a
-function body reads the next record and starts processing it with the
-first rule in the program.
+According to the POSIX standard, the behavior is undefined if the
+@code{next} statement is used in a @code{BEGIN} or @code{END} rule.
+@command{gawk} treats it as a syntax error.  Although POSIX permits it,
+most other @command{awk} implementations don't allow the @code{next}
+statement inside function bodies (@pxref{User-defined}).  Just as with any
+other @code{next} statement, a @code{next} statement inside a function
+body reads the next record and starts processing it with the first rule
+in the program.
 
 @node Nextfile Statement
 @subsection The @code{nextfile} Statement
@@ -12534,11 +13374,11 @@ The @code{nextfile} statement
 is similar to the @code{next} statement.
 However, instead of abandoning processing of the current record, the
 @code{nextfile} statement instructs @command{awk} to stop processing the
-current data file.
+current @value{DF}.
 
 Upon execution of the @code{nextfile} statement,
 @code{FILENAME} is
-updated to the name of the next data file listed on the command line,
+updated to the name of the next @value{DF} listed on the command line,
 @code{FNR} is reset to one,
 and processing
 starts over with the first rule in the program.
@@ -12547,10 +13387,10 @@ then the code in any @code{END} rules is executed. An exception to this is
 when @code{nextfile} is invoked during execution of any statement in an
 @code{END} rule; In this case, it causes the program to stop immediately. @xref{BEGIN/END}.
 
-The @code{nextfile} statement is useful when there are many data files
+The @code{nextfile} statement is useful when there are many @value{DF}s
 to process but it isn't necessary to process every record in every file.
 Without @code{nextfile},
-in order to move on to the next data file, a program
+in order to move on to the next @value{DF}, a program
 would have to continue scanning the unwanted records.  The @code{nextfile}
 statement accomplishes this much more efficiently.
 
@@ -12583,8 +13423,10 @@ See @uref{http://austingroupbugs.net/view.php?id=607, the Austin Group website}.
 
 @cindex functions, user-defined, @code{next}/@code{nextfile} statements and
 @cindex @code{nextfile} statement, user-defined functions and
-The current version of the Brian Kernighan's @command{awk} (@pxref{Other
-Versions}) also supports @code{nextfile}.  However, it doesn't allow the
+@cindex Brian Kernighan's @command{awk}
+@cindex @command{mawk} utility
+The current version of the Brian Kernighan's @command{awk}, and @command{mawk} (@pxref{Other
+Versions}) also support @code{nextfile}.  However, they don't allow the
 @code{nextfile} statement inside function bodies (@pxref{User-defined}).
 @command{gawk} does; a @code{nextfile} inside a function body reads the
 next record and starts processing it with the first rule in the program,
@@ -12598,9 +13440,9 @@ The @code{exit} statement causes @command{awk} to immediately stop
 executing the current rule and to stop processing input; any remaining input
 is ignored.  The @code{exit} statement is written as follows:
 
-@example
-exit @r{[}@var{return code}@r{]}
-@end example
+@display
+@code{exit} [@var{return code}]
+@end display
 
 @cindex @code{BEGIN} pattern, @code{exit} statement and
 @cindex @code{END} pattern, @code{exit} statement and
@@ -12633,8 +13475,7 @@ status code for the @command{awk} process.  If no argument is supplied,
 In the case where an argument
 is supplied to a first @code{exit} statement, and then @code{exit} is
 called a second time from an @code{END} rule with no argument,
-@command{awk} uses the previously supplied exit value.
-@value{DARKCORNER}
+@command{awk} uses the previously supplied exit value.  @value{DARKCORNER}
 @xref{Exit Status}, for more information.
 
 @cindex programming conventions, @code{exit} statement
@@ -12646,12 +13487,12 @@ in the following example:
 
 @example
 BEGIN @{
-       if (("date" | getline date_now) <= 0) @{
-         print "Can't get system date" > "/dev/stderr"
-         exit 1
-       @}
-       print "current date is", date_now
-       close("date")
+    if (("date" | getline date_now) <= 0) @{
+        print "Can't get system date" > "/dev/stderr"
+        exit 1
+    @}
+    print "current date is", date_now
+    close("date")
 @}
 @end example
 
@@ -12682,9 +13523,9 @@ automatically by @command{awk}, so that they carry information from the
 internal workings of @command{awk} to your program.
 
 @cindex @command{gawk}, built-in variables and
-This @value{SECTION} documents all the built-in variables of
-@command{gawk}, most of which are also documented in the chapters
-describing their areas of activity.
+This @value{SECTION} documents all of @command{gawk}'s built-in variables,
+most of which are also documented in the @value{CHAPTER}s describing
+their areas of activity.
 
 @menu
 * User-modified::               Built-in variables that you change to control
@@ -12702,44 +13543,38 @@ describing their areas of activity.
 @cindex user-modifiable variables
 
 The following is an alphabetical list of variables that you can change to
-control how @command{awk} does certain things. The variables that are
-specific to @command{gawk} are marked with a pound sign@w{ (@samp{#}).}
+control how @command{awk} does certain things.
+
+The variables that are specific to @command{gawk} are marked with a pound
+sign (@samp{#}).  These variables are @command{gawk} extensions.  In other
+@command{awk} implementations or if @command{gawk} is in compatibility
+mode (@pxref{Options}), they are not special.  (Any exceptions are noted
+in the description of each variable.)
 
 @table @code
 @cindex @code{BINMODE} variable
 @cindex binary input/output
 @cindex input/output, binary
-@item BINMODE #
-On non-POSIX systems, this variable specifies use of binary mode for all I/O.
-Numeric values of one, two, or three specify that input files, output files, or
-all files, respectively, should use binary I/O.
-A numeric value less than zero is treated as zero, and a numeric value greater than
-three is treated as three.
-Alternatively,
-string values of @code{"r"} or @code{"w"} specify that input files and
-output files, respectively, should use binary I/O.
-A string value of @code{"rw"} or @code{"wr"} indicates that all
-files should use binary I/O.
-Any other string value is treated the same as @code{"rw"},
-but causes @command{gawk}
-to generate a warning message.
-@code{BINMODE} is described in more detail in
-@ref{PC Using}.
-
 @cindex differences in @command{awk} and @command{gawk}, @code{BINMODE} variable
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations
-(except @command{mawk},
-@pxref{Other Versions}),
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
+@item BINMODE #
+On non-POSIX systems, this variable specifies use of binary mode
+for all I/O.  Numeric values of one, two, or three specify that input
+files, output files, or all files, respectively, should use binary I/O.
+A numeric value less than zero is treated as zero, and a numeric value
+greater than three is treated as three.  Alternatively, string values
+of @code{"r"} or @code{"w"} specify that input files and output files,
+respectively, should use binary I/O.  A string value of @code{"rw"} or
+@code{"wr"} indicates that all files should use binary I/O.  Any other
+string value is treated the same as @code{"rw"}, but causes @command{gawk}
+to generate a warning message.  @code{BINMODE} is described in more
+detail in @ref{PC Using}.  @command{mawk} @pxref{Other Versions}),
+also supports this variable, but only using numeric values.
 
 @cindex @code{CONVFMT} variable
 @cindex POSIX @command{awk}, @code{CONVFMT} variable and
 @cindex numbers, converting, to strings
 @cindex strings, converting, numbers to
-@item CONVFMT
+@item @code{CONVFMT}
 This string controls conversion of numbers to
 strings (@pxref{Conversion}).
 It works by being passed, in effect, as the first argument to the
@@ -12754,40 +13589,29 @@ Its default value is @code{"%.6g"}.
 @cindex field separators, @code{FIELDWIDTHS} variable and
 @cindex separators, field, @code{FIELDWIDTHS} variable and
 @item FIELDWIDTHS #
-This is a space-separated list of columns that tells @command{gawk}
+A space-separated list of columns that tells @command{gawk}
 how to split input with fixed columnar boundaries.
 Assigning a value to @code{FIELDWIDTHS}
 overrides the use of @code{FS} and @code{FPAT} for field splitting.
 @xref{Constant Size}, for more information.
 
-If @command{gawk} is in compatibility mode
-(@pxref{Options}), then @code{FIELDWIDTHS}
-has no special meaning, and field-splitting operations occur based
-exclusively on the value of @code{FS}.
-
 @cindex @command{gawk}, @code{FPAT} variable in
 @cindex @code{FPAT} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{FPAT} variable
 @cindex field separators, @code{FPAT} variable and
 @cindex separators, field, @code{FPAT} variable and
 @item FPAT #
-This is a regular expression (as a string) that tells @command{gawk}
+A regular expression (as a string) that tells @command{gawk}
 to create the fields based on text that matches the regular expression.
 Assigning a value to @code{FPAT}
 overrides the use of @code{FS} and @code{FIELDWIDTHS} for field splitting.
 @xref{Splitting By Content}, for more information.
 
-If @command{gawk} is in compatibility mode
-(@pxref{Options}), then @code{FPAT}
-has no special meaning, and field-splitting operations occur based
-exclusively on the value of @code{FS}.
-
 @cindex @code{FS} variable
 @cindex separators, field
 @cindex field separators
 @item FS
-This is the input field separator
-(@pxref{Field Separators}).
+The input field separator (@pxref{Field Separators}).
 The value is a single-character string or a multicharacter regular
 expression that matches the separations between fields in an input
 record.  If the value is the null string (@code{""}), then each
@@ -12821,8 +13645,8 @@ is to simply say @samp{FS = FS}, perhaps with an explanatory comment.
 @cindex @command{gawk}, @code{IGNORECASE} variable in
 @cindex @code{IGNORECASE} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{IGNORECASE} variable
-@cindex case sensitivity, string comparisons and
-@cindex case sensitivity, regexps and
+@cindex case sensitivity, and string comparisons
+@cindex case sensitivity, and regexps
 @cindex regular expressions, case sensitivity
 @item IGNORECASE #
 If @code{IGNORECASE} is nonzero or non-null, then all string comparisons
@@ -12837,18 +13661,13 @@ and it does not affect field splitting when using a single-character
 field separator.
 @xref{Case-sensitivity}.
 
-If @command{gawk} is in compatibility mode
-(@pxref{Options}),
-then @code{IGNORECASE} has no special meaning.  Thus, string
-and regexp operations are always case-sensitive.
-
 @cindex @command{gawk}, @code{LINT} variable in
 @cindex @code{LINT} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{LINT} variable
 @cindex lint checking
 @item LINT #
 When this variable is true (nonzero or non-null), @command{gawk}
-behaves as if the @option{--lint} command-line option is in effect.
+behaves as if the @option{--lint} command-line option is in effect
 (@pxref{Options}).
 With a value of @code{"fatal"}, lint warnings become fatal errors.
 With a value of @code{"invalid"}, only warnings about things that are
@@ -12869,7 +13688,7 @@ of @command{awk} being executed.
 @cindex numbers, converting, to strings
 @cindex strings, converting, numbers to
 @item OFMT
-This string controls conversion of numbers to
+Controls conversion of numbers to
 strings (@pxref{Conversion}) for
 printing with the @code{print} statement.  It works by being passed
 as the first argument to the @code{sprintf()} function
@@ -12890,27 +13709,26 @@ default value is @w{@code{" "}}, a string consisting of a single space.
 
 @cindex @code{ORS} variable
 @item ORS
-This is the output record separator.  It is output at the end of every
+The output record separator.  It is output at the end of every
 @code{print} statement.  Its default value is @code{"\n"}, the newline
 character.  (@xref{Output Separators}.)
 
 @cindex @code{PREC} variable
 @item PREC #
 The working precision of arbitrary precision floating-point numbers,
-53 bits by default (@pxref{Setting Precision}).
+53 bits by default (@pxref{Setting precision}).
 
 @cindex @code{ROUNDMODE} variable
 @item ROUNDMODE #
 The rounding mode to use for arbitrary precision arithmetic on
 numbers, by default @code{"N"} (@samp{roundTiesToEven} in
-the IEEE-754 standard)
-(@pxref{Setting Rounding Mode}).
+the IEEE 754 standard; @pxref{Setting the rounding mode}).
 
 @cindex @code{RS} variable
 @cindex separators, for records
 @cindex record separators
-@item RS
-This is @command{awk}'s input record separator.  Its default value is a string
+@item @code{RS}
+The input record separator.  Its default value is a string
 containing a single newline character, which means that an input record
 consists of a single line of text.
 It can also be the null string, in which case records are separated by
@@ -12929,8 +13747,8 @@ just the first character of @code{RS}'s value is used.
 @cindex @code{SUBSEP} variable
 @cindex separators, subscript
 @cindex subscript separators
-@item SUBSEP
-This is the subscript separator.  It has the default value of
+@item @code{SUBSEP}
+The subscript separator.  It has the default value of
 @code{"\034"} and is used to separate the parts of the indices of a
 multidimensional array.  Thus, the expression @code{@w{foo["A", "B"]}}
 really accesses @code{foo["A\034B"]}
@@ -12941,18 +13759,12 @@ really accesses @code{foo["A\034B"]}
 @cindex differences in @command{awk} and @command{gawk}, @code{TEXTDOMAIN} variable
 @cindex internationalization, localization
 @item TEXTDOMAIN #
-This variable is used for internationalization of programs at the
+Used for internationalization of programs at the
 @command{awk} level.  It sets the default text domain for specially
 marked string constants in the source text, as well as for the
 @code{dcgettext()}, @code{dcngettext()} and @code{bindtextdomain()} functions
 (@pxref{Internationalization}).
 The default value of @code{TEXTDOMAIN} is @code{"messages"}.
-
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
 @end table
 @c ENDOFRANGE bvar
 @c ENDOFRANGE varb
@@ -12968,14 +13780,19 @@ it is not special.
 @cindex variables, built-in, conveying information
 The following is an alphabetical list of variables that @command{awk}
 sets automatically on certain occasions in order to provide
-information to your program.  The variables that are specific to
-@command{gawk} are marked with a pound sign@w{ (@samp{#}).}
+information to your program.
 
-@table @code
+The variables that are specific to @command{gawk} are marked with a pound
+sign (@samp{#}).  These variables are @command{gawk} extensions.  In other
+@command{awk} implementations or if @command{gawk} is in compatibility
+mode (@pxref{Options}), they are not special.
+
+@c @asis for docbook
+@table @asis
 @cindex @code{ARGC}/@code{ARGV} variables
 @cindex arguments, command-line
 @cindex command line, arguments
-@item ARGC@r{,} ARGV
+@item @code{ARGC}, @code{ARGV}
 The command-line arguments available to @command{awk} programs are stored in
 an array called @code{ARGV}.  @code{ARGC} is the number of command-line
 arguments present.  @xref{Other Arguments}.
@@ -12987,16 +13804,16 @@ In the following example:
 $ @kbd{awk 'BEGIN @{}
 >         @kbd{for (i = 0; i < ARGC; i++)}
 >             @kbd{print ARGV[i]}
->      @kbd{@}' inventory-shipped BBS-list}
+>      @kbd{@}' inventory-shipped mail-list}
 @print{} awk
 @print{} inventory-shipped
-@print{} BBS-list
+@print{} mail-list
 @end example
 
 @noindent
 @code{ARGV[0]} contains @samp{awk}, @code{ARGV[1]}
 contains @samp{inventory-shipped}, and @code{ARGV[2]} contains
-@samp{BBS-list}.  The value of @code{ARGC} is three, one more than the
+@samp{mail-list}.  The value of @code{ARGC} is three, one more than the
 index of the last element in @code{ARGV}, because the elements are numbered
 from zero.
 
@@ -13015,36 +13832,30 @@ about how @command{awk} uses these variables.
 
 @cindex @code{ARGIND} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{ARGIND} variable
-@item ARGIND #
+@item @code{ARGIND #}
 The index in @code{ARGV} of the current file being processed.
-Every time @command{gawk} opens a new data file for processing, it sets
-@code{ARGIND} to the index in @code{ARGV} of the file name.
+Every time @command{gawk} opens a new @value{DF} for processing, it sets
+@code{ARGIND} to the index in @code{ARGV} of the @value{FN}.
 When @command{gawk} is processing the input files,
 @samp{FILENAME == ARGV[ARGIND]} is always true.
 
 @cindex files, processing@comma{} @code{ARGIND} variable and
 This variable is useful in file processing; it allows you to tell how far
-along you are in the list of data files as well as to distinguish between
-successive instances of the same file name on the command line.
+along you are in the list of @value{DF}s as well as to distinguish between
+successive instances of the same @value{FN} on the command line.
 
 @cindex file names, distinguishing
 While you can change the value of @code{ARGIND} within your @command{awk}
 program, @command{gawk} automatically sets it to a new value when the
 next file is opened.
 
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
-
 @cindex @code{ENVIRON} array
-@cindex environment variables
-@item ENVIRON
+@cindex environment variables, in @code{ENVIRON} array
+@item @code{ENVIRON}
 An associative array containing the values of the environment.  The array
 indices are the environment variable names; the elements are the values of
 the particular environment variables.  For example,
-@code{ENVIRON["HOME"]} might be @file{/home/arnold}.
+@code{ENVIRON["HOME"]} might be @code{/home/arnold}.
 
 For POSIX @command{awk}, changing this array does not affect the
 environment passed on to any programs that @command{awk} may spawn via
@@ -13059,80 +13870,60 @@ executable programs.
 
 Some operating systems may not have environment variables.
 On such systems, the @code{ENVIRON} array is empty (except for
-@w{@code{ENVIRON["AWKPATH"]}},
-@pxref{AWKPATH Variable} and
-@w{@code{ENVIRON["AWKLIBPATH"]}},
+@w{@code{ENVIRON["AWKPATH"]}} and
+@w{@code{ENVIRON["AWKLIBPATH"]}};
+@pxref{AWKPATH Variable}, and
 @pxref{AWKLIBPATH Variable}).
 
 @cindex @command{gawk}, @code{ERRNO} variable in
 @cindex @code{ERRNO} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{ERRNO} variable
 @cindex error handling, @code{ERRNO} variable and
-@item ERRNO #
-If a system error occurs during a redirection for @code{getline},
-during a read for @code{getline}, or during a @code{close()} operation,
-then @code{ERRNO} contains a string describing the error.
-
-In addition, @command{gawk} clears @code{ERRNO}
-before opening each command-line input file. This enables checking if
-the file is readable inside a @code{BEGINFILE} pattern (@pxref{BEGINFILE/ENDFILE}).
-
-Otherwise,
-@code{ERRNO} works similarly to the C variable @code{errno}.
-Except for the case just mentioned,
-@command{gawk} @emph{never} clears it (sets it
-to zero or @code{""}).  Thus, you should only expect its value
-to be meaningful when an I/O operation returns a failure
-value, such as @code{getline} returning @minus{}1.
-You are, of course, free to clear it yourself before doing an
-I/O operation.
-
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
+@item @code{ERRNO #}
+If a system error occurs during a redirection for @code{getline}, during
+a read for @code{getline}, or during a @code{close()} operation, then
+@code{ERRNO} contains a string describing the error.
+
+In addition, @command{gawk} clears @code{ERRNO} before opening each
+command-line input file. This enables checking if the file is readable
+inside a @code{BEGINFILE} pattern (@pxref{BEGINFILE/ENDFILE}).
+
+Otherwise, @code{ERRNO} works similarly to the C variable @code{errno}.
+Except for the case just mentioned, @command{gawk} @emph{never} clears
+it (sets it to zero or @code{""}).  Thus, you should only expect its
+value to be meaningful when an I/O operation returns a failure value,
+such as @code{getline} returning @minus{}1.  You are, of course, free
+to clear it yourself before doing an I/O operation.
 
 @cindex @code{FILENAME} variable
 @cindex dark corner, @code{FILENAME} variable
-@item FILENAME
-The name of the file that @command{awk} is currently reading.
-When no data files are listed on the command line, @command{awk} reads
-from the standard input and @code{FILENAME} is set to @code{"-"}.
-@code{FILENAME} is changed each time a new file is read
-(@pxref{Reading Files}).
-Inside a @code{BEGIN} rule, the value of @code{FILENAME} is
-@code{""}, since there are no input files being processed
-yet.@footnote{Some early implementations of Unix @command{awk} initialized
-@code{FILENAME} to @code{"-"}, even if there were data files to be
-processed. This behavior was incorrect and should not be relied
-upon in your programs.}
-@value{DARKCORNER}
-Note, though, that using @code{getline}
-(@pxref{Getline})
-inside a @code{BEGIN} rule can give
-@code{FILENAME} a value.
+@item @code{FILENAME}
+The name of the current input file.  When no @value{DF}s are listed
+on the command line, @command{awk} reads from the standard input and
+@code{FILENAME} is set to @code{"-"}.  @code{FILENAME} changes each
+time a new file is read (@pxref{Reading Files}).  Inside a @code{BEGIN}
+rule, the value of @code{FILENAME} is @code{""}, since there are no input
+files being processed yet.@footnote{Some early implementations of Unix
+@command{awk} initialized @code{FILENAME} to @code{"-"}, even if there
+were @value{DF}s to be processed. This behavior was incorrect and should
+not be relied upon in your programs.} @value{DARKCORNER} Note, though,
+that using @code{getline} (@pxref{Getline}) inside a @code{BEGIN} rule
+can give @code{FILENAME} a value.
 
 @cindex @code{FNR} variable
-@item FNR
+@item @code{FNR}
 The current record number in the current file.  @code{FNR} is
 incremented each time a new record is read
 (@pxref{Records}).  It is reinitialized
 to zero each time a new input file is started.
 
 @cindex @code{NF} variable
-@item NF
+@item @code{NF}
 The number of fields in the current input record.
 @code{NF} is set each time a new record is read, when a new field is
 created or when @code{$0} changes (@pxref{Fields}).
 
-Unlike most of the variables described in this
-@ifnotinfo
-section,
-@end ifnotinfo
-@ifinfo
-node,
-@end ifinfo
+Unlike most of the variables described in this @value{SUBSECTION},
 assigning a value to @code{NF} has the potential to affect
 @command{awk}'s internal workings.  In particular, assignments
 to @code{NF} can be used to create or remove fields from the
@@ -13141,18 +13932,18 @@ current record. @xref{Changing Fields}.
 @cindex @code{FUNCTAB} array
 @cindex @command{gawk}, @code{FUNCTAB} array in
 @cindex differences in @command{awk} and @command{gawk}, @code{FUNCTAB} variable
-@item FUNCTAB #
+@item @code{FUNCTAB #}
 An array whose indices and corresponding values are the names of all
 the user-defined or extension functions in the program.
 
 @quotation NOTE
 Attempting to use the @code{delete} statement with the @code{FUNCTAB}
-array will cause a fatal error.  Any attempt to assign to an element of
-the @code{FUNCTAB} array will also cause a fatal error.
+array causes a fatal error.  Any attempt to assign to an element of
+@code{FUNCTAB} also causes a fatal error.
 @end quotation
 
 @cindex @code{NR} variable
-@item NR
+@item @code{NR}
 The number of input records @command{awk} has processed since
 the beginning of the program's execution
 (@pxref{Records}).
@@ -13161,17 +13952,19 @@ the beginning of the program's execution
 @cindex @command{gawk}, @code{PROCINFO} array in
 @cindex @code{PROCINFO} array
 @cindex differences in @command{awk} and @command{gawk}, @code{PROCINFO} array
-@item PROCINFO #
+@item @code{PROCINFO #}
 The elements of this array provide access to information about the
 running @command{awk} program.
 The following elements (listed alphabetically)
 are guaranteed to be available:
 
 @table @code
+@cindex effective group ID of @command{gawk} user
 @item PROCINFO["egid"]
 The value of the @code{getegid()} system call.
 
 @item PROCINFO["euid"]
+@cindex effective user ID of @command{gawk} user
 The value of the @code{geteuid()} system call.
 
 @item PROCINFO["FS"]
@@ -13181,6 +13974,7 @@ This is
 or @code{"FPAT"} if field matching with @code{FPAT} is in effect.
 
 @item PROCINFO["identifiers"]
+@cindex program identifiers
 A subarray, indexed by the names of all identifiers used in the
 text of the AWK program.  For each identifier, the value of the element is one of the following:
 
@@ -13209,21 +14003,25 @@ after it has finished parsing the program; they are @emph{not} updated
 while the program runs.
 
 @item PROCINFO["gid"]
+@cindex group ID of @command{gawk} user
 The value of the @code{getgid()} system call.
 
 @item PROCINFO["pgrpid"]
+@cindex process group idIDof @command{gawk} process
 The process group ID of the current process.
 
 @item PROCINFO["pid"]
+@cindex process ID of @command{gawk} process
 The process ID of the current process.
 
 @item PROCINFO["ppid"]
+@cindex parent process ID of @command{gawk} process
 The parent process ID of the current process.
 
 @item PROCINFO["sorted_in"]
 If this element exists in @code{PROCINFO}, its value controls the
 order in which array indices will be processed by
-@samp{for (index in array) @dots{}} loops.
+@samp{for (@var{index} in @var{array})} loops.
 Since this is an advanced feature, we defer the
 full description until later; see
 @ref{Scanning an Array}.
@@ -13237,6 +14035,8 @@ Assigning a new value to this element changes the default.
 The value of the @code{getuid()} system call.
 
 @item PROCINFO["version"]
+@cindex version of @command{gawk}
+@cindex @command{gawk} version
 The version of @command{gawk}.
 @end table
 
@@ -13246,16 +14046,20 @@ if your version of @command{gawk} supports arbitrary precision numbers
 (@pxref{Arbitrary Precision Arithmetic}): 
 
 @table @code 
+@cindex version of GNU MPFR library
 @item PROCINFO["mpfr_version"]
 The version of the GNU MPFR library.
 
 @item PROCINFO["gmp_version"]
+@cindex version of GNU MP library
 The version of the GNU MP library.
 
 @item PROCINFO["prec_max"]
+@cindex maximum precision supported by MPFR library
 The maximum precision supported by MPFR.
 
 @item PROCINFO["prec_min"]
+@cindex minimum precision supported by MPFR library
 The minimum precision required by MPFR.
 @end table
 
@@ -13266,12 +14070,15 @@ of @command{gawk} supports dynamic loading of extension functions
 
 @table @code
 @item PROCINFO["api_major"]
+@cindex version of @command{gawk} extension API
+@cindex extension API, version number
 The major version of the extension API.
 
 @item PROCINFO["api_minor"]
 The minor version of the extension API.
 @end table
 
+@cindex supplementary groups of @command{gawk} process
 On some systems, there may be elements in the array, @code{"group1"}
 through @code{"group@var{N}"} for some @var{N}. @var{N} is the number of
 supplementary groups that the process has.  Use the @code{in} operator
@@ -13279,15 +14086,14 @@ to test for these elements
 (@pxref{Reference to Elements}).
 
 @cindex @command{gawk}, @code{PROCINFO} array in
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, uses
 The @code{PROCINFO} array has the following additional uses:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-It may be
-used to cause coprocesses
-to communicate over pseudo-ttys instead of through two-way pipes;
-this is discussed further in @ref{Two-way I/O}.
+It may be used to cause coprocesses to communicate over pseudo-ttys
+instead of through two-way pipes; this is discussed further in
+@ref{Two-way I/O}.
 
 @item
 It may be used to provide a timeout when reading from any
@@ -13295,14 +14101,8 @@ open input file, pipe, or coprocess.
 @xref{Read Timeout}, for more information.
 @end itemize
 
-This array is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
-
 @cindex @code{RLENGTH} variable
-@item RLENGTH
+@item @code{RLENGTH}
 The length of the substring matched by the
 @code{match()} function
 (@pxref{String Functions}).
@@ -13310,7 +14110,7 @@ The length of the substring matched by the
 is the length of the matched string, or @minus{}1 if no match is found.
 
 @cindex @code{RSTART} variable
-@item RSTART
+@item @code{RSTART}
 The start-index in characters of the substring that is matched by the
 @code{match()} function
 (@pxref{String Functions}).
@@ -13321,20 +14121,14 @@ if no match was found.
 @cindex @command{gawk}, @code{RT} variable in
 @cindex @code{RT} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{RT} variable
-@item RT #
-This is set each time a record is read. It contains the input text
-that matched the text denoted by @code{RS}, the record separator.
-
-This variable is a @command{gawk} extension.
-In other @command{awk} implementations,
-or if @command{gawk} is in compatibility mode
-(@pxref{Options}),
-it is not special.
+@item @code{RT #}
+The input text that matched the text denoted by @code{RS},
+the record separator.  It is set every time a record is read.
 
 @cindex @command{gawk}, @code{SYMTAB} array in
 @cindex @code{SYMTAB} array
 @cindex differences in @command{awk} and @command{gawk}, @code{SYMTAB} variable
-@item SYMTAB #
+@item @code{SYMTAB #}
 An array whose indices are the names of all currently defined
 global variables and arrays in the program.  The array may be used
 for indirect access to read or write the value of a variable:
@@ -13351,7 +14145,7 @@ if an element in @code{SYMTAB} is an array.
 Also, you may not use the @code{delete} statement with the
 @code{SYMTAB} array.
 
-You may use an index for @code{SYMTAB} that is not a predefined identifer:
+You may use an index for @code{SYMTAB} that is not a predefined identifier:
 
 @example
 SYMTAB["xxx"] = 5
@@ -13363,6 +14157,7 @@ This works as expected: in this case @code{SYMTAB} acts just like
 a regular array.  The only difference is that you can't then delete
 @code{SYMTAB["xxx"]}.
 
+@cindex Schorr, Andrew
 The @code{SYMTAB} array is more interesting than it looks. Andrew Schorr
 points out that it effectively gives @command{awk} data pointers. Consider his
 example:
@@ -13377,8 +14172,8 @@ function multiply(variable, amount)
 @end example
 
 @quotation NOTE
-In order to avoid severe time-travel paradoxes@footnote{Not to mention difficult
-implementation issues.}, neither @code{FUNCTAB} nor @code{SYMTAB}
+In order to avoid severe time-travel paradoxes,@footnote{Not to mention difficult
+implementation issues.} neither @code{FUNCTAB} nor @code{SYMTAB}
 are available as elements within the @code{SYMTAB} array.
 @end quotation
 @end table
@@ -13419,7 +14214,7 @@ changed.
 
 @node ARGC and ARGV
 @subsection Using @code{ARGC} and @code{ARGV}
-@cindex @code{ARGC}/@code{ARGV} variables
+@cindex @code{ARGC}/@code{ARGV} variables, how to use
 @cindex arguments, command-line
 @cindex command line, arguments
 
@@ -13431,16 +14226,16 @@ and @code{ARGV}:
 $ @kbd{awk 'BEGIN @{}
 >        @kbd{for (i = 0; i < ARGC; i++)}
 >            @kbd{print ARGV[i]}
->      @kbd{@}' inventory-shipped BBS-list}
+>      @kbd{@}' inventory-shipped mail-list}
 @print{} awk
 @print{} inventory-shipped
-@print{} BBS-list
+@print{} mail-list
 @end example
 
 @noindent
 In this example, @code{ARGV[0]} contains @samp{awk}, @code{ARGV[1]}
 contains @samp{inventory-shipped}, and @code{ARGV[2]} contains
-@samp{BBS-list}.
+@samp{mail-list}.
 Notice that the @command{awk} program is not entered in @code{ARGV}.  The
 other command-line options, with their arguments, are also not
 entered.  This includes variable assignments done with the @option{-v}
@@ -13481,11 +14276,11 @@ additional files to be read.
 If the value of @code{ARGC} is decreased, that eliminates input files
 from the end of the list.  By recording the old value of @code{ARGC}
 elsewhere, a program can treat the eliminated arguments as
-something other than file names.
+something other than @value{FN}s.
 
 To eliminate a file from the middle of the list, store the null string
 (@code{""}) into @code{ARGV} in place of the file's name.  As a
-special feature, @command{awk} ignores file names that have been
+special feature, @command{awk} ignores @value{FN}s that have been
 replaced with the null string.
 Another option is to
 use the @code{delete} statement to remove elements from
@@ -13544,6 +14339,65 @@ are passed on to the @command{awk} program.
 (@xref{Getopt Function}, for an @command{awk} library function
 that parses command-line options.)
 
+@node Pattern Action Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Pattern-action pairs make up the basic elements of an @command{awk}
+program.  Patterns are either normal expressions, range expressions,
+regexp constants, one of the special keywords @code{BEGIN}, @code{END},
+@code{BEGINFILE}, @code{ENDFILE}, or empty.  The action executes if
+the current record matches the pattern.  Empty (missing) patterns match
+all records.
+
+@item
+I/O from @code{BEGIN} and @code{END} rules have certain constraints.
+This is also true, only more so, for @code{BEGINFILE} and @code{ENDFILE}
+rules.  The latter two give you ``hooks'' into @command{gawk}'s file
+processing, allowing you to recover from a file that otherwise would
+cause a fatal error (such as a file that cannot be opened).
+
+@item
+Shell variables can be used in @command{awk} programs by careful
+use of shell quoting.  It is easier to pass a shell variable into
+@command{awk} by using the @option{-v} option and an @command{awk}
+variable.
+
+@item
+Actions consist of statements enclosed in curly braces. Statements
+are built up from expressions, control statements, compound statements,
+input and output statements, and deletion statements.
+
+@item
+The control statements in @command{awk} are @code{if}-@code{else},
+@code{while}, @code{for}, and @code{do}-@code{while}.  @command{gawk}
+adds the @code{switch} statement.  There are two flavors of @code{for}
+statement: one for for performing general looping, and the other iterating
+through an array.
+
+@item
+@code{break} and @code{continue} let you exit early or start the next
+iteration of a loop (or get out of a @code{switch}).
+
+@item
+@code{next} and @code{nextfile} let you read the next record and start
+over at the top of your program, or skip to the next input file and
+start over, respectively.
+
+@item
+The @code{exit} statement terminates your program. When executed
+from an action (or function body) it transfers control to the
+@code{END} statements. From an @code{END} statement body, it exits
+immediately.  You may pass an optional numeric value to be used
+at @command{awk}'s exit status.
+
+@item
+Some built-in variables provide control over @command{awk}, mainly for I/O.
+Other variables convey information from @command{awk} to your program.
+
+@end itemize
+
 @node Arrays
 @chapter Arrays in @command{awk}
 @c STARTOFRANGE arrs
@@ -13560,11 +14414,11 @@ It also describes how @command{awk} simulates multidimensional
 arrays, as well as some of the less obvious points about array usage.
 The @value{CHAPTER} moves on to discuss @command{gawk}'s facility
 for sorting arrays, and ends with a brief description of @command{gawk}'s
-ability to support true multidimensional arrays.
+ability to support true arrays of arrays.
 
 @cindex variables, names of
 @cindex functions, names of
-@cindex arrays, names of
+@cindex arrays, names of, and names of functions/variables
 @cindex names, arrays/variables
 @cindex namespace issues
 @command{awk} maintains a single set
@@ -13583,6 +14437,7 @@ same @command{awk} program.
 * Multidimensional::            Emulating multidimensional arrays in
                                 @command{awk}.
 * Arrays of Arrays::            True multidimensional arrays.
+* Arrays Summary::              Summary of arrays.
 @end menu
 
 @node Array Basics
@@ -13644,35 +14499,34 @@ the array is declared.)
 
 A contiguous array of four elements might look like the following example,
 conceptually, if the element values are 8, @code{"foo"},
-@code{""}, and 30:
+@code{""}, and 30
+@ifnotdocbook
+as shown in @ref{figure-array-elements}:
+@end ifnotdocbook
+@ifdocbook
+as shown in @inlineraw{docbook, <xref linkend="figure-array-elements"/>}:
+@end ifdocbook
 
-@c @strong{FIXME: NEXT ED:} Use real images here, and an @float
-@iftex
-@c from Karl Berry, much thanks for the help.
-@tex
-\bigskip % space above the table (about 1 linespace)
-\offinterlineskip
-\newdimen\width \width = 1.5cm
-\newdimen\hwidth \hwidth = 4\width \advance\hwidth by 2pt % 5 * 0.4pt
-\centerline{\vbox{
-\halign{\strut\hfil\ignorespaces#&&\vrule#&\hbox to\width{\hfil#\unskip\hfil}\cr
-\noalign{\hrule width\hwidth}
-	&&{\tt 8} &&{\tt "foo"} &&{\tt ""} &&{\tt 30} &&\quad Value\cr
-\noalign{\hrule width\hwidth}
-\noalign{\smallskip}
-	&\omit&0&\omit &1   &\omit&2 &\omit&3 &\omit&\quad Index\cr
-}
-}}
-@end tex
-@end iftex
-@ifnottex
-@example
-+---------+---------+--------+---------+
-|    8    |  "foo"  |   ""   |    30   |    @r{Value}
-+---------+---------+--------+---------+
-     0         1         2         3        @r{Index}
-@end example
-@end ifnottex
+@ifnotdocbook
+@float Figure,figure-array-elements
+@caption{A Contiguous Array}
+@ifinfo
+@center @image{array-elements, , , Basic Program Stages, txt}
+@end ifinfo
+@ifnotinfo
+@center @image{array-elements, , , Basic Program Stages}
+@end ifnotinfo
+@end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-array-elements" float="0">
+<title>A Contiguous Array</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="array-elements.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 @noindent
 Only the values are stored; the indices are implicit from the order of
@@ -13689,12 +14543,53 @@ Arrays in @command{awk} are different---they are @dfn{associative}.  This means
 that each array is a collection of pairs: an index and its corresponding
 array element value:
 
+@ifnotdocbook
 @example
 @r{Index} 3     @r{Value} 30
 @r{Index} 1     @r{Value} "foo"
 @r{Index} 0     @r{Value} 8
 @r{Index} 2     @r{Value} ""
 @end example
+@end ifnotdocbook
+
+@docbook
+<informaltable>
+<tgroup cols="2">
+<colspec colname="1" align="center"/>
+<colspec colname="2" align="center"/>
+<thead>
+<row>
+<entry>Index</entry>
+<entry>Value</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+<entry><literal>3</literal></entry>
+<entry><literal>30</literal></entry>
+</row>
+
+<row>
+<entry><literal>1</literal></entry>
+<entry><literal>"foo"</literal></entry>
+</row>
+
+<row>
+<entry><literal>0</literal></entry>
+<entry><literal>8</literal></entry>
+</row>
+
+<row>
+<entry><literal>2</literal></entry>
+<entry><literal>""</literal></entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 @noindent
 The pairs are shown in jumbled order because their order is irrelevant.
@@ -13703,6 +14598,7 @@ One advantage of associative arrays is that new pairs can be added
 at any time.  For example, suppose a tenth element is added to the array
 whose value is @w{@code{"number ten"}}.  The result is:
 
+@ifnotdocbook
 @example
 @r{Index} 10    @r{Value} "number ten"
 @r{Index} 3     @r{Value} 30
@@ -13710,6 +14606,51 @@ whose value is @w{@code{"number ten"}}.  The result is:
 @r{Index} 0     @r{Value} 8
 @r{Index} 2     @r{Value} ""
 @end example
+@end ifnotdocbook
+
+@docbook
+<informaltable>
+<tgroup cols="2">
+<colspec colname="1" align="center"/>
+<colspec colname="2" align="center"/>
+<thead>
+<row>
+<entry>Index</entry>
+<entry>Value</entry>
+</row>
+</thead>
+<tbody>
+
+<row>
+<entry><literal>10</literal></entry>
+<entry><literal>"number ten"</literal></entry>
+</row>
+
+<row>
+<entry><literal>3</literal></entry>
+<entry><literal>30</literal></entry>
+</row>
+
+<row>
+<entry><literal>1</literal></entry>
+<entry><literal>"foo"</literal></entry>
+</row>
+
+<row>
+<entry><literal>0</literal></entry>
+<entry><literal>8</literal></entry>
+</row>
+
+<row>
+<entry><literal>2</literal></entry>
+<entry><literal>""</literal></entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 @noindent
 @cindex sparse arrays
@@ -13722,28 +14663,67 @@ have to be positive integers.  Any number, or even a string, can be
 an index.  For example, the following is an array that translates words from
 English to French:
 
+@ifnotdocbook
 @example
 @r{Index} "dog" @r{Value} "chien"
 @r{Index} "cat" @r{Value} "chat"
 @r{Index} "one" @r{Value} "un"
 @r{Index} 1     @r{Value} "un"
 @end example
+@end ifnotdocbook
+
+@docbook
+<informaltable>
+<tgroup cols="2">
+<colspec colname="1" align="center"/>
+<colspec colname="2" align="center"/>
+<thead>
+<row>
+<entry>Index</entry>
+<entry>Value</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry><literal>"dog"</literal></entry>
+<entry><literal>"chien"</literal></entry>
+</row>
+
+<row>
+<entry><literal>"cat"</literal></entry>
+<entry><literal>"chat"</literal></entry>
+</row>
+
+<row>
+<entry><literal>"one"</literal></entry>
+<entry><literal>"un"</literal></entry>
+</row>
+
+<row>
+<entry><literal>1</literal></entry>
+<entry><literal>"un"</literal></entry>
+</row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+@end docbook
 
 @noindent
 Here we decided to translate the number one in both spelled-out and
 numeric form---thus illustrating that a single array can have both
 numbers and strings as indices.
-In fact, array subscripts are always strings; this is discussed
+(In fact, array subscripts are always strings; this is discussed
 in more detail in
-@ref{Numeric Array Subscripts}.
+@ref{Numeric Array Subscripts}.)
 Here, the number @code{1} isn't double-quoted, since @command{awk}
 automatically converts it to a string.
 
 @cindex @command{gawk}, @code{IGNORECASE} variable in
-@cindex @code{IGNORECASE} variable
 @cindex case sensitivity, array indices and
-@cindex arrays, @code{IGNORECASE} variable and
-@cindex @code{IGNORECASE} variable, array subscripts and
+@cindex arrays, and @code{IGNORECASE} variable
+@cindex @code{IGNORECASE} variable, and array indices
 The value of @code{IGNORECASE} has no effect upon array subscripting.
 The identical string value used to store an array element must be used
 to retrieve it.
@@ -13759,8 +14739,9 @@ is independent of the number of elements in the array.
 
 @node Reference to Elements
 @subsection Referring to an Array Element
-@cindex arrays, elements, referencing
-@cindex elements in arrays
+@cindex arrays, referencing elements
+@cindex array members
+@cindex elements of arrays
 
 The principal way to use an array is to refer to one of its elements.
 An array reference is an expression as follows:
@@ -13777,11 +14758,16 @@ The value of the array reference is the current value of that array
 element.  For example, @code{foo[4.3]} is an expression for the element
 of array @code{foo} at index @samp{4.3}.
 
+@cindex arrays, unassigned elements
+@cindex unassigned array elements
+@cindex empty array elements
 A reference to an array element that has no recorded value yields a value of
 @code{""}, the null string.  This includes elements
 that have not been assigned any value as well as elements that have been
 deleted (@pxref{Delete}).
 
+@cindex non-existent array elements
+@cindex arrays, elements that don't exist
 @quotation NOTE
 A reference to an element that does not exist @emph{automatically} creates
 that array element, with the null string as its value.  (In some cases,
@@ -13801,19 +14787,19 @@ if it didn't exist before!
 @end quotation
 
 @c @cindex arrays, @code{in} operator and
-@cindex @code{in} operator
+@cindex @code{in} operator, testing if array element exists
 To determine whether an element exists in an array at a certain index, use
 the following expression:
 
 @example
-@var{ind} in @var{array}
+@var{indx} in @var{array}
 @end example
 
 @cindex side effects, array indexing
 @noindent
-This expression tests whether the particular index @var{ind} exists,
+This expression tests whether the particular index @var{indx} exists,
 without the side effect of creating that element if it is not present.
-The expression has the value one (true) if @code{@var{array}[@var{ind}]}
+The expression has the value one (true) if @code{@var{array}[@var{indx}]}
 exists and zero (false) if it does not exist.
 For example, this statement tests whether the array @code{frequencies}
 contains the index @samp{2}:
@@ -13836,8 +14822,8 @@ if (frequencies[2] != "")
 
 @node Assigning Elements
 @subsection Assigning Array Elements
-@cindex arrays, elements, assigning
-@cindex elements in arrays, assigning
+@cindex arrays, elements, assigning values
+@cindex elements in arrays, assigning values
 
 Array elements can be assigned values just like
 @command{awk} variables:
@@ -13854,6 +14840,7 @@ assign to that element of the array.
 
 @node Array Example
 @subsection Basic Array Example
+@cindex arrays, an example of using
 
 The following program takes a list of lines, each beginning with a line
 number, and prints them out in order of line number.  The line numbers
@@ -13923,7 +14910,9 @@ END @{
 @node Scanning an Array
 @subsection Scanning All Elements of an Array
 @cindex elements in arrays, scanning
+@cindex scanning arrays
 @cindex arrays, scanning
+@cindex loops, @code{for}, array scanning
 
 In programs that use arrays, it is often necessary to use a loop that
 executes once for each element of an array.  In other languages, where
@@ -13940,7 +14929,7 @@ for (@var{var} in @var{array})
 @end example
 
 @noindent
-@cindex @code{in} operator
+@cindex @code{in} operator, use in loops
 This loop executes @var{body} once for each index in @var{array} that the
 program has previously used, with the variable @var{var} set to that index.
 
@@ -13979,18 +14968,61 @@ END @{
 @xref{Word Sorting},
 for a more detailed example of this type.
 
-@cindex arrays, elements, order of
-@cindex elements in arrays, order of
+@cindex arrays, elements, order of access by @code{in} operator
+@cindex elements in arrays, order of access by @code{in} operator
+@cindex @code{in} operator, order of array access
 The order in which elements of the array are accessed by this statement
 is determined by the internal arrangement of the array elements within
-@command{awk} and normally cannot be controlled or changed.  This can lead to
-problems if new elements are added to @var{array} by statements in
-the loop body; it is not predictable whether the @code{for} loop will
-reach them.  Similarly, changing @var{var} inside the loop may produce
-strange results.  It is best to avoid such things.
+@command{awk} and in standard @command{awk} cannot be controlled
+or changed.  This can lead to problems if new elements are added to
+@var{array} by statements in the loop body; it is not predictable whether
+the @code{for} loop will reach them.  Similarly, changing @var{var} inside
+the loop may produce strange results.  It is best to avoid such things.
+
+As a point of information, @command{gawk} sets up the list of elements
+to be iterated over before the loop starts, and does not change it.
+But not all @command{awk} versions do so. Consider this program, named
+@file{loopcheck.awk}:
+
+@example
+BEGIN @{
+    a["here"] = "here"
+    a["is"] = "is"
+    a["a"] = "a"
+    a["loop"] = "loop"
+    for (i in a) @{
+        j++
+        a[j] = j
+        print i
+    @}
+@}
+@end example
+
+Here is what happens when run with @command{gawk}:
+
+@example
+$ @kbd{gawk -f loopcheck.awk}
+@print{} here
+@print{} loop
+@print{} a
+@print{} is
+@end example
+
+Contrast this to Brian Kernighan's @command{awk}:
+
+@example
+$ @kbd{nawk -f loopcheck.awk}
+@print{} loop
+@print{} here
+@print{} is
+@print{} a
+@print{} 1
+@end example
 
 @node Controlling Scanning
-@subsection Using Predefined Array Scanning Orders
+@subsection Using Predefined Array Scanning Orders With @command{gawk}
+
+This @value{SUBSECTION} describes a feature that is specific to @command{gawk}.
 
 By default, when a @code{for} loop traverses an array, the order
 is undefined, meaning that the @command{awk} implementation
@@ -13998,12 +15030,14 @@ determines the order in which the array is traversed.
 This order is usually based on the internal implementation of arrays
 and will vary from one version of @command{awk} to the next.
 
+@cindex array scanning order, controlling
+@cindex controlling array scanning order
 Often, though, you may wish to do something simple, such as
 ``traverse the array by comparing the indices in ascending order,''
 or ``traverse the array by comparing the values in descending order.''
 @command{gawk} provides two mechanisms which give you this control.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Set @code{PROCINFO["sorted_in"]} to one of a set of predefined values.
 We describe this now.
@@ -14014,6 +15048,7 @@ to use for comparison of array elements. This advanced feature
 is described later, in @ref{Array Sorting}.
 @end itemize
 
+@cindex @code{PROCINFO}, values of @code{sorted_in}
 The following special values for @code{PROCINFO["sorted_in"]} are available:
 
 @table @code
@@ -14109,7 +15144,7 @@ order relative to each other is determined by their index strings.
 Here are some additional things to bear in mind about sorted
 array traversal.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The value of @code{PROCINFO["sorted_in"]} is global. That is, it affects
 all array traversal @code{for} loops.  If you need to change it within your
@@ -14174,7 +15209,7 @@ if (4 in foo)
     print "This will never be printed"
 @end example
 
-@cindex null strings, array elements and
+@cindex null strings, and deleting array elements
 It is important to note that deleting an element is @emph{not} the
 same as assigning it a null value (the empty string, @code{""}).
 For example:
@@ -14196,6 +15231,7 @@ is not in the array is deleted.
 @cindex extensions, common@comma{} @code{delete} to delete entire arrays
 @cindex arrays, deleting entire contents
 @cindex deleting entire arrays
+@cindex @code{delete} @var{array}
 @cindex differences in @command{awk} and @command{gawk}, array elements, deleting
 All the elements of an array may be deleted with a single statement
 by leaving off the subscript in the @code{delete} statement,
@@ -14210,6 +15246,7 @@ Using this version of the @code{delete} statement is about three times
 more efficient than the equivalent loop that deletes each element one
 at a time.
 
+@cindex Brian Kernighan's @command{awk}
 @quotation NOTE
 For many years,
 using @code{delete} without a subscript was a @command{gawk} extension.
@@ -14252,9 +15289,9 @@ a = 3
 @section Using Numbers to Subscript Arrays
 
 @cindex numbers, as array subscripts
-@cindex arrays, subscripts
+@cindex arrays, numeric subscripts
 @cindex subscripts in arrays, numbers as
-@cindex @code{CONVFMT} variable, array subscripts and
+@cindex @code{CONVFMT} variable, and array subscripts
 An important aspect to remember about arrays is that @emph{array subscripts
 are always strings}.  When a numeric value is used as a subscript,
 it is converted to a string value before being used for subscripting
@@ -14284,7 +15321,8 @@ string value from @code{xyz}---this time @code{"12.15"}---because the value of
 @code{CONVFMT} only allows two significant digits.  This test fails,
 since @code{"12.15"} is different from @code{"12.153"}.
 
-@cindex converting, during subscripting
+@cindex converting integer array subscripts
+@cindex integer array indices
 According to the rules for conversions
 (@pxref{Conversion}), integer
 values are always converted to strings as integers, no matter what the
@@ -14338,7 +15376,7 @@ $ @kbd{echo 'line 1}
 @print{} line 2
 @end example
 
-Unfortunately, the very first line of input data did not come out in the
+Unfortunately, the very first line of input data did not appear in the
 output!
 
 Upon first glance, we would think that this program should have worked.
@@ -14378,7 +15416,7 @@ on the command line (@pxref{Options}).
 @section Multidimensional Arrays
 
 @menu
-* Multiscanning::              Scanning multidimensional arrays.
+* Multiscanning::               Scanning multidimensional arrays.
 @end menu
 
 @cindex subscripts in arrays, multidimensional
@@ -14390,7 +15428,7 @@ languages, including @command{awk}) to refer to an element of a
 two-dimensional array named @code{grid} is with
 @code{grid[@var{x},@var{y}]}.
 
-@cindex @code{SUBSEP} variable, multidimensional arrays
+@cindex @code{SUBSEP} variable, and multidimensional arrays
 Multidimensional arrays are supported in @command{awk} through
 concatenation of indices into one string.
 @command{awk} converts the indices into strings
@@ -14422,6 +15460,7 @@ combined strings that are ambiguous.  Suppose that @code{SUBSEP} is
 "b@@c"]}} are indistinguishable because both are actually
 stored as @samp{foo["a@@b@@c"]}.
 
+@cindex @code{in} operator, index existence in multidimensional arrays
 To test whether a particular index sequence exists in a
 multidimensional array, use the same operator (@code{in}) that is
 used for single dimensional arrays.  Write the whole sequence of indices
@@ -14487,6 +15526,7 @@ multidimensional @emph{way of accessing} an array.
 
 @cindex subscripts in arrays, multidimensional, scanning
 @cindex arrays, multidimensional, scanning
+@cindex scanning multidimensional arrays
 However, if your program has an array that is always accessed as
 multidimensional, you can get the effect of scanning it by combining
 the scanning @code{for} statement
@@ -14528,12 +15568,13 @@ separate indices is recovered.
 
 @node Arrays of Arrays
 @section Arrays of Arrays
+@cindex arrays of arrays
 
 @command{gawk} goes beyond standard @command{awk}'s multidimensional
 array access and provides true arrays of
 arrays. Elements of a subarray are referred to by their own indices
 enclosed in square brackets, just like the elements of the main array.
-For example, the following creates a two-element subarray at index @samp{1}
+For example, the following creates a two-element subarray at index @code{1}
 of the main array @code{a}:
 
 @example
@@ -14557,7 +15598,7 @@ Each subarray and the main array can be of different length. In fact, the
 elements of an array or its subarray do not all have to have the same
 type. This means that the main array and any of its subarrays can be
 non-rectangular, or jagged in structure. One can assign a scalar value to
-the index @samp{4} of the main array @code{a}:
+the index @code{4} of the main array @code{a}:
 
 @example
 a[4] = "An element in a jagged array"
@@ -14578,7 +15619,7 @@ a[4][5][6][7] = "An element in a four-dimensional array"
 @end example
 
 @noindent
-This removes the scalar value from index @samp{4} and then inserts a
+This removes the scalar value from index @code{4} and then inserts a
 subarray of subarray of subarray containing a scalar. You can also
 delete an entire subarray or subarray of subarrays:
 
@@ -14679,6 +15720,63 @@ creating an arbitrary index:
 $ @kbd{gawk 'BEGIN @{ b[1][1] = ""; split("a b c d", b[1]); print b[1][1] @}'}
 @print{} a
 @end example
+
+@node Arrays Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Standard @command{awk} provides one-dimensional associative arrays
+(arrays indexed by string values).  All arrays are associative; numeric
+indices are converted automatically to strings.
+
+@item
+Array elements are referenced as @code{@var{array}[@var{indx}]}.
+Referencing an element creates it if it did not exist previously.
+
+@item
+The proper way to see if an array has an element with a given index
+is to use the @code{in} operator: @samp{@var{indx} in @var{array}}.
+
+@item
+Use @samp{for (@var{indx} in @var{array}) @dots{}} to scan through all the
+individual elements of an array. In the body of the loop, @var{indx} takes
+on the value of each element's index in turn.
+
+@item
+The order in which a @samp{for (@var{indx} in @var{array})} loop
+traverses an array is undefined in POSIX @command{awk} and varies among
+implementations.  @command{gawk} lets you control the order by assigning
+special predefined values to @code{PROCINFO["sorted_in"]}.
+
+@item
+Use @samp{delete @var{array}[@var{indx}]} to delete an individual element.
+You may also use @samp{delete @var{array}} to delete all of the elements
+in the array.  This latter feature has been a common extension for many
+years and is now standard, but may not be supported by all commercial
+versions of @command{awk}.
+
+@item
+Standard @command{awk} simulates multidimensional arrays by separating
+subscript values with a comma.  The values are concatenated into a
+single string, separated by the value of @code{SUBSEP}.  The fact
+that such a subscript was created in this way is not retained; thus
+changing @code{SUBSEP} may have unexpected consequences.  You can use
+@samp{(@var{sub1}, @var{sub2}, @dots{}) in @var{array}} to see if such
+a multidimensional subscript exists in @var{array}.
+
+@item
+@command{gawk} provides true arrays of arrays. You use a separate
+set of square brackets for each dimension in such an array:
+@code{data[row][col]}, for example. Array elements may thus be either
+scalar values (number or string) or another array.
+
+@item
+Use the @code{isarray()} built-in function to determine if an array
+element is itself a subarray.
+
+@end itemize
+
 @c ENDOFRANGE arrs
 
 @node Functions
@@ -14703,6 +15801,7 @@ The second half of this @value{CHAPTER} describes these
 * Built-in::                    Summarizes the built-in functions.
 * User-defined::                Describes User-defined functions in detail.
 * Indirect Calls::              Choosing the function to call at runtime.
+* Functions Summary::           Summary of functions.
 @end menu
 
 @node Built-in
@@ -14787,42 +15886,50 @@ two arguments 11 and 10.
 
 @node Numeric Functions
 @subsection Numeric Functions
+@cindex numeric functions
 
 The following list describes all of
 the built-in functions that work with numbers.
 Optional parameters are enclosed in square brackets@w{ ([ ]):}
 
-@table @code
-@item atan2(@var{y}, @var{x})
-@cindex @code{atan2()} function
+@c @asis for docbook
+@table @asis
+@item @code{atan2(@var{y}, @var{x})}
+@cindexawkfunc{atan2}
+@cindex arctangent
 Return the arctangent of @code{@var{y} / @var{x}} in radians.
-You can use @samp{pi = atan2(0, -1)} to retrieve the value of @value{PI}.
+You can use @samp{pi = atan2(0, -1)} to retrieve the value of
+@value{PI}.
 
-@item cos(@var{x})
-@cindex @code{cos()} function
+@item @code{cos(@var{x})}
+@cindexawkfunc{cos}
+@cindex cosine
 Return the cosine of @var{x}, with @var{x} in radians.
 
-@item exp(@var{x})
-@cindex @code{exp()} function
+@item @code{exp(@var{x})}
+@cindexawkfunc{exp}
+@cindex exponent
 Return the exponential of @var{x} (@code{e ^ @var{x}}) or report
 an error if @var{x} is out of range.  The range of values @var{x} can have
 depends on your machine's floating-point representation.
 
-@item int(@var{x})
-@cindex @code{int()} function
+@item @code{int(@var{x})}
+@cindexawkfunc{int}
+@cindex round to nearest integer
 Return the nearest integer to @var{x}, located between @var{x} and zero and
 truncated toward zero.
 
 For example, @code{int(3)} is 3, @code{int(3.9)} is 3, @code{int(-3.9)}
 is @minus{}3, and @code{int(-3)} is @minus{}3 as well.
 
-@item log(@var{x})
-@cindex @code{log()} function
+@item @code{log(@var{x})}
+@cindexawkfunc{log}
+@cindex logarithm
 Return the natural logarithm of @var{x}, if @var{x} is positive;
 otherwise, report an error.
 
-@item rand()
-@cindex @code{rand()} function
+@item @code{rand()}
+@cindexawkfunc{rand}
 @cindex random numbers, @code{rand()}/@code{srand()} functions
 Return a random number.  The values of @code{rand()} are
 uniformly distributed between zero and one.
@@ -14864,7 +15971,7 @@ function roll(n) @{ return 1 + int(rand() * n) @}
 @}
 @end example
 
-@cindex numbers, random
+@cindex seeding random number generator
 @cindex random numbers, seed of
 @quotation CAUTION
 In most @command{awk} implementations, including @command{gawk},
@@ -14879,18 +15986,20 @@ the seed to a value that is different in each run.  To do this,
 use @code{srand()}.
 @end quotation
 
-@item sin(@var{x})
-@cindex @code{sin()} function
+@item @code{sin(@var{x})}
+@cindexawkfunc{sin}
+@cindex sine
 Return the sine of @var{x}, with @var{x} in radians.
 
-@item sqrt(@var{x})
-@cindex @code{sqrt()} function
+@item @code{sqrt(@var{x})}
+@cindexawkfunc{sqrt}
+@cindex square root
 Return the positive square root of @var{x}.
 @command{gawk} prints a warning message
 if @var{x} is negative.  Thus, @code{sqrt(4)} is 2.
 
-@item srand(@r{[}@var{x}@r{]})
-@cindex @code{srand()} function
+@item @code{srand(}[@var{x}]@code{)}
+@cindexawkfunc{srand}
 Set the starting point, or seed,
 for generating random numbers to the value @var{x}.
 
@@ -14920,6 +16029,7 @@ sequences of random numbers.
 
 @node String Functions
 @subsection String-Manipulation Functions
+@cindex string-manipulation functions
 
 The functions in this @value{SECTION} look at or change the text of one
 or more strings.
@@ -14932,12 +16042,23 @@ example, @code{length()} returns the number of characters in a string,
 and not the number of bytes used to represent those characters. Similarly,
 @code{index()} works with character indices, and not byte indices.
 
+@quotation CAUTION
+A number of functions deal with indices into strings.  For these
+functions, the first character of a string is at position (index) one.
+This is different from C and the languages descended from it, where the
+first character is at position zero.  You need to remember this when
+doing index calculations, particularly if you are used to C.
+@end quotation
+
 In the following list, optional parameters are enclosed in square brackets@w{ ([ ]).}
 Several functions perform string substitution; the full discussion is
 provided in the description of the @code{sub()} function, which comes
 towards the end since the list is presented in alphabetic order.
+
 Those functions that are specific to @command{gawk} are marked with a
-pound sign@w{ (@samp{#}):}
+pound sign (@samp{#}).  They are not available in compatibility mode
+(@pxref{Options}):
+
 
 @menu
 * Gory Details::                More than you want to know about @samp{\} and
@@ -14945,14 +16066,15 @@ pound sign@w{ (@samp{#}):}
                                 @code{gensub()}.
 @end menu
 
-@table @code
-@item asort(@var{source} @r{[}, @var{dest} @r{[}, @var{how}  @r{]} @r{]}) #
-@itemx asorti(@var{source} @r{[}, @var{dest} @r{[}, @var{how}  @r{]} @r{]}) #
-@cindex @code{asorti()} function (@command{gawk})
+@c @asis for docbook
+@table @asis
+@item @code{asort(}@var{source} [@code{,} @var{dest} [@code{,} @var{how} ] ]@code{) #}
+@itemx @code{asorti(}@var{source} [@code{,} @var{dest} [@code{,} @var{how} ] ]@code{) #}
+@cindexgawkfunc{asorti}
+@cindex sort array
 @cindex arrays, elements, retrieving number of
-@cindex @code{asort()} function (@command{gawk})
-@cindex @command{gawk}, @code{IGNORECASE} variable in
-@cindex @code{IGNORECASE} variable
+@cindexgawkfunc{asort}
+@cindex sort array indices
 These two functions are similar in behavior, so they are described
 together.
 
@@ -14970,7 +16092,9 @@ sequential integers starting with one.  If the optional array @var{dest}
 is specified, then @var{source} is duplicated into @var{dest}.  @var{dest}
 is then sorted, leaving the indices of @var{source} unchanged.
 
-When comparing strings, @code{IGNORECASE} affects the sorting.  If the
+@cindex @command{gawk}, @code{IGNORECASE} variable in
+When comparing strings, @code{IGNORECASE} affects the sorting
+(@pxref{Array Sorting Functions}).  If the
 @var{source} array contains subarrays as values (@pxref{Arrays of
 Arrays}), they will come last, after all scalar values.
 
@@ -15009,11 +16133,10 @@ a[2] = "last"
 a[3] = "middle"
 @end example
 
-@code{asort()} and @code{asorti()} are @command{gawk} extensions; they
-are not available in compatibility mode (@pxref{Options}).
-
-@item gensub(@var{regexp}, @var{replacement}, @var{how} @r{[}, @var{target}@r{]}) #
-@cindex @code{gensub()} function (@command{gawk})
+@item @code{gensub(@var{regexp}, @var{replacement}, @var{how}} [@code{, @var{target}}]@code{) #}
+@cindexgawkfunc{gensub}
+@cindex search and replace in strings
+@cindex substitute in string
 Search the target string @var{target} for matches of the regular
 expression @var{regexp}.  If @var{how} is a string beginning with
 @samp{g} or @samp{G} (short for ``global''), then replace all matches of @var{regexp} with
@@ -15022,7 +16145,7 @@ which match of @var{regexp} to replace. If no @var{target} is supplied,
 use @code{$0}.  It returns the modified string as the result
 of the function and the original target string is @emph{not} changed.
 
-@code{gensub()} is a general substitution function.  It's purpose is
+@code{gensub()} is a general substitution function.  Its purpose is
 to provide more features than the standard @code{sub()} and @code{gsub()}
 functions.
 
@@ -15072,11 +16195,8 @@ a warning message.
 If @var{regexp} does not match @var{target}, @code{gensub()}'s return value
 is the original unchanged value of @var{target}.
 
-@code{gensub()} is a @command{gawk} extension; it is not available
-in compatibility mode (@pxref{Options}).
-
-@item gsub(@var{regexp}, @var{replacement} @r{[}, @var{target}@r{]})
-@cindex @code{gsub()} function
+@item @code{gsub(@var{regexp}, @var{replacement}} [@code{, @var{target}}]@code{)}
+@cindexawkfunc{gsub}
 Search @var{target} for
 @emph{all} of the longest, leftmost, @emph{nonoverlapping} matching
 substrings it can find and replace them with @var{replacement}.
@@ -15097,9 +16217,10 @@ omitted, then the entire input record (@code{$0}) is used.
 As in @code{sub()}, the characters @samp{&} and @samp{\} are special,
 and the third argument must be assignable.
 
-@item index(@var{in}, @var{find})
-@cindex @code{index()} function
-@cindex searching
+@item @code{index(@var{in}, @var{find})}
+@cindexawkfunc{index}
+@cindex search in string
+@cindex find substring in string
 Search the string @var{in} for the first occurrence of the string
 @var{find}, and return the position in characters where that occurrence
 begins in the string @var{in}.  Consider the following example:
@@ -15111,19 +16232,33 @@ $ @kbd{awk 'BEGIN @{ print index("peanut", "an") @}'}
 
 @noindent
 If @var{find} is not found, @code{index()} returns zero.
-(Remember that string indices in @command{awk} start at one.)
 
 It is a fatal error to use a regexp constant for @var{find}.
 
-@item length(@r{[}@var{string}@r{]})
-@cindex @code{length()} function
+@item @code{length(}[@var{string}]@code{)}
+@cindexawkfunc{length}
+@cindex string length
+@cindex length of string
 Return the number of characters in @var{string}.  If
 @var{string} is a number, the length of the digit string representing
 that number is returned.  For example, @code{length("abcde")} is five.  By
-contrast, @code{length(15 * 35)} works out to three. In this example, 15 * 35 =
-525, and 525 is then converted to the string @code{"525"}, which has
+contrast, @code{length(15 * 35)} works out to three. In this example,
+@iftex
+@math{15 @cdot 35 = 525},
+@end iftex
+@ifnottex
+@ifnotdocbook
+15 * 35 = 525,
+@end ifnotdocbook
+@end ifnottex
+@docbook
+15 &sdot; 35 = 525, @c
+@end docbook
+and 525 is then converted to the string @code{"525"}, which has
 three characters.
 
+@cindex length of input record
+@cindex input record, length of
 If no argument is supplied, @code{length()} returns the length of @code{$0}.
 
 @c @cindex historical features
@@ -15162,6 +16297,8 @@ warning about this.
 @cindex common extensions, @code{length()} applied to an array
 @cindex extensions, common@comma{} @code{length()} applied to an array
 @cindex differences between @command{gawk} and @command{awk}
+@cindex number of array elements
+@cindex array, number of elements
 With @command{gawk} and several other @command{awk} implementations, when given an
 array argument, the @code{length()} function returns the number of elements
 in the array. @value{COMMONEXT}
@@ -15174,16 +16311,18 @@ If @option{--lint} is provided on the command line
 If @option{--posix} is supplied, using an array argument is a fatal error
 (@pxref{Arrays}).
 
-@item match(@var{string}, @var{regexp} @r{[}, @var{array}@r{]})
-@cindex @code{match()} function
+@item @code{match(@var{string}, @var{regexp}} [@code{, @var{array}}]@code{)}
+@cindexawkfunc{match}
+@cindex string, regular expression match
+@cindex match regexp in string
 Search @var{string} for the
 longest, leftmost substring matched by the regular expression,
-@var{regexp} and return the character position, or @dfn{index},
+@var{regexp} and return the character position (index)
 at which that substring begins (one, if it starts at the beginning of
 @var{string}).  If no match is found, return zero.
 
 The @var{regexp} argument may be either a regexp constant
-(@code{/@dots{}/}) or a string constant (@code{"@dots{}"}).
+(@code{/}@dots{}@code{/}) or a string constant (@code{"}@dots{}@code{"}).
 In the latter case, the string is treated as a regexp to be matched.
 @xref{Computed Regexps}, for a
 discussion of the difference between the two forms, and the
@@ -15289,8 +16428,9 @@ The @var{array} argument to @code{match()} is a
 (@pxref{Options}),
 using a third argument is a fatal error.
 
-@item patsplit(@var{string}, @var{array} @r{[}, @var{fieldpat} @r{[}, @var{seps} @r{]} @r{]}) #
-@cindex @code{patsplit()} function (@command{gawk})
+@item @code{patsplit(@var{string}, @var{array}} [@code{, @var{fieldpat}} [@code{, @var{seps}} ] ]@code{) #}
+@cindexgawkfunc{patsplit}
+@cindex split string into array
 Divide
 @var{string} into pieces defined by @var{fieldpat}
 and store the pieces in @var{array} and the separator strings in the
@@ -15314,14 +16454,8 @@ manner similar to the way input lines are split into fields using @code{FPAT}
 Before splitting the string, @code{patsplit()} deletes any previously existing
 elements in the arrays @var{array} and @var{seps}.
 
-@cindex troubleshooting, @code{patsplit()} function
-The @code{patsplit()} function is a
-@command{gawk} extension.  In compatibility mode
-(@pxref{Options}),
-it is not available.
-
-@item split(@var{string}, @var{array} @r{[}, @var{fieldsep} @r{[}, @var{seps} @r{]} @r{]})
-@cindex @code{split()} function
+@item @code{split(@var{string}, @var{array}} [@code{, @var{fieldsep}} [@code{, @var{seps}} ] ]@code{)}
+@cindexawkfunc{split}
 Divide @var{string} into pieces separated by @var{fieldsep}
 and store the pieces in @var{array} and the separator strings in the
 @var{seps} array.  The first piece is stored in
@@ -15350,7 +16484,7 @@ split("cul-de-sac", a, "-", seps)
 @end example
 
 @noindent
-@cindex strings, splitting
+@cindex strings splitting, example
 splits the string @samp{cul-de-sac} into three fields using @samp{-} as the
 separator.  It sets the contents of the array @code{a} as follows:
 
@@ -15405,8 +16539,11 @@ If @var{string} does not match @var{fieldsep} at all (but is not null),
 @var{array} has one element only. The value of that element is the original
 @var{string}.
 
-@item sprintf(@var{format}, @var{expression1}, @dots{})
-@cindex @code{sprintf()} function
+In POSIX mode (@pxref{Options}), the fourth argument is not allowed.
+
+@item @code{sprintf(@var{format}, @var{expression1}, @dots{})}
+@cindexawkfunc{sprintf}
+@cindex formatting strings
 Return (without printing) the string that @code{printf} would
 have printed out with the same arguments
 (@pxref{Printf}).
@@ -15419,8 +16556,9 @@ pival = sprintf("pi = %.2f (approx.)", 22/7)
 @noindent
 assigns the string @w{@samp{pi = 3.14 (approx.)}} to the variable @code{pival}.
 
-@cindex @code{strtonum()} function (@command{gawk})
-@item strtonum(@var{str}) #
+@cindexgawkfunc{strtonum}
+@cindex convert string to number
+@item @code{strtonum(@var{str}) #}
 Examine @var{str} and return its numeric value.  If @var{str}
 begins with a leading @samp{0}, @code{strtonum()} assumes that @var{str}
 is an octal number.  If @var{str} begins with a leading @samp{0x} or
@@ -15442,12 +16580,9 @@ you use the @option{--non-decimal-data} option, which isn't recommended.
 Note also that @code{strtonum()} uses the current locale's decimal point
 for recognizing numbers (@pxref{Locales}).
 
-@cindex differences in @command{awk} and @command{gawk}, @code{strtonum()} function (@command{gawk})
-@code{strtonum()} is a @command{gawk} extension; it is not available
-in compatibility mode (@pxref{Options}).
-
-@item sub(@var{regexp}, @var{replacement} @r{[}, @var{target}@r{]})
-@cindex @code{sub()} function
+@item @code{sub(@var{regexp}, @var{replacement}} [@code{, @var{target}}]@code{)}
+@cindexawkfunc{sub}
+@cindex replace in string
 Search @var{target}, which is treated as a string, for the
 leftmost, longest substring matched by the regular expression @var{regexp}.
 Modify the entire string
@@ -15456,7 +16591,7 @@ The modified string becomes the new value of @var{target}.
 Return the number of substitutions made (zero or one).
 
 The @var{regexp} argument may be either a regexp constant
-(@code{/@dots{}/}) or a string constant (@code{"@dots{}"}).
+(@code{/}@dots{}@code{/}) or a string constant (@code{"}@dots{}@code{"}).
 In the latter case, the string is treated as a regexp to be matched.
 @xref{Computed Regexps}, for a
 discussion of the difference between the two forms, and the
@@ -15546,8 +16681,9 @@ will not run.
 Finally, if the @var{regexp} is not a regexp constant, it is converted into a
 string, and then the value of that string is treated as the regexp to match.
 
-@item substr(@var{string}, @var{start} @r{[}, @var{length}@r{]})
-@cindex @code{substr()} function
+@item @code{substr(@var{string}, @var{start}} [@code{, @var{length}} ]@code{)}
+@cindexawkfunc{substr}
+@cindex substring
 Return a @var{length}-character-long substring of @var{string},
 starting at character number @var{start}.  The first character of a
 string is character number one.@footnote{This is different from
@@ -15561,6 +16697,7 @@ suffix is also returned
 if @var{length} is greater than the number of characters remaining
 in the string, counting from character @var{start}.
 
+@cindex Brian Kernighan's @command{awk}
 If @var{start} is less than one, @code{substr()} treats it as
 if it was one. (POSIX doesn't specify what to do in this case:
 Brian Kernighan's @command{awk} acts this way, and therefore @command{gawk}
@@ -15603,16 +16740,18 @@ string = substr(string, 1, 2) "CDE" substr(string, 6)
 @end example
 
 @cindex case sensitivity, converting case
-@cindex converting, case
-@item tolower(@var{string})
-@cindex @code{tolower()} function
+@cindex strings, converting letter case
+@item @code{tolower(@var{string})}
+@cindexawkfunc{tolower}
+@cindex convert string to lower case
 Return a copy of @var{string}, with each uppercase character
 in the string replaced with its corresponding lowercase character.
 Nonalphabetic characters are left unchanged.  For example,
 @code{tolower("MiXeD cAsE 123")} returns @code{"mixed case 123"}.
 
-@item toupper(@var{string})
-@cindex @code{toupper()} function
+@item @code{toupper(@var{string})}
+@cindexawkfunc{toupper}
+@cindex convert string to upper case
 Return a copy of @var{string}, with each lowercase character
 in the string replaced with its corresponding uppercase character.
 Nonalphabetic characters are left unchanged.  For example,
@@ -15636,10 +16775,11 @@ that there are several levels of @dfn{escape processing} going on.
 
 First, there is the @dfn{lexical} level, which is when @command{awk} reads
 your program
-and builds an internal copy of it that can be executed.
+and builds an internal copy of it to execute.
 Then there is the runtime level, which is when @command{awk} actually scans the
 replacement string to determine what to generate.
 
+@cindex Brian Kernighan's @command{awk}
 At both levels, @command{awk} looks for a defined set of characters that
 can come after a backslash.  At the lexical level, it looks for the
 escape sequences listed in @ref{Escape Sequences}.
@@ -15778,7 +16918,7 @@ says, in effect, that @samp{\} turns off the special meaning of any
 following character, but for anything other than @samp{\} and @samp{&},
 such special meaning is undefined.  This wording leads to two problems:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Backslashes must now be doubled in the @var{replacement} string, breaking
 historical @command{awk} programs.
@@ -15909,17 +17049,17 @@ _bigskip}
 The only case where the difference is noticeable is the last one: @samp{\\\\}
 is seen as @samp{\\} and produces @samp{\} instead of @samp{\\}.
 
-Starting with version 3.1.4, @command{gawk} followed the POSIX rules
+Starting with @value{PVERSION} 3.1.4, @command{gawk} followed the POSIX rules
 when @option{--posix} is specified (@pxref{Options}). Otherwise,
 it continued to follow the 1996 proposed rules, since
 that had been its behavior for many years.
 
-When version 4.0.0 was released, the @command{gawk} maintainer
+When @value{PVERSION} 4.0.0 was released, the @command{gawk} maintainer
 made the POSIX rules the default, breaking well over a decade's worth
 of backwards compatibility.@footnote{This was rather naive of him, despite
 there being a note in this section indicating that the next major version
 would move to the POSIX rules.} Needless to say, this was a bad idea,
-and as of version 4.0.1, @command{gawk} resumed its historical
+and as of @value{PVERSION} 4.0.1, @command{gawk} resumed its historical
 behavior, and only follows the POSIX rules when @option{--posix} is given.
 
 The rules for @code{gensub()} are considerably simpler. At the runtime
@@ -16004,14 +17144,16 @@ Although this makes a certain amount of sense, it can be surprising.
 
 @node I/O Functions
 @subsection Input/Output Functions
+@cindex input/output functions
 
 The following functions relate to input/output (I/O).
 Optional parameters are enclosed in square brackets ([ ]):
 
-@table @code
-@item close(@var{filename} @r{[}, @var{how}@r{]})
-@cindex @code{close()} function
+@table @asis
+@item @code{close(}@var{filename} [@code{,} @var{how}]@code{)}
+@cindexawkfunc{close}
 @cindex files, closing
+@cindex close file or coprocess
 Close the file @var{filename} for input or output. Alternatively, the
 argument may be a shell command that was used for creating a coprocess, or
 for redirecting to or from a pipe; then the coprocess or pipe is closed.
@@ -16027,8 +17169,12 @@ not matter.
 @xref{Two-way I/O},
 which discusses this feature in more detail and gives an example.
 
-@item fflush(@r{[}@var{filename}@r{]})
-@cindex @code{fflush()} function
+Note that the second argument to @code{close()} is a @command{gawk}
+extension; it is not available in compatibility mode (@pxref{Options}).
+
+@item @code{fflush(}[@var{filename}]@code{)}
+@cindexawkfunc{fflush}
+@cindex flush buffered output
 Flush any buffered output associated with @var{filename}, which is either a
 file opened for writing or a shell command for redirecting output to
 a pipe or coprocess.
@@ -16046,11 +17192,12 @@ This is the purpose of the @code{fflush()} function---@command{gawk} also
 buffers its output and the @code{fflush()} function forces
 @command{gawk} to flush its buffers.
 
-@code{fflush()} was added to Brian Kernighan's
-version of @command{awk} in 1994.
-For over two decades, it was not part of the POSIX standard.
-As of December, 2012, it was accepted for
-inclusion into the POSIX standard.
+@cindex extensions, common@comma{} @code{fflush()} function
+@cindex Brian Kernighan's @command{awk}
+@code{fflush()} was added to Brian Kernighan's @command{awk} in
+April of 1992.  For two decades, it was not part of the POSIX standard.
+As of December, 2012, it was accepted for inclusion into the POSIX
+standard.
 See @uref{http://austingroupbugs.net/view.php?id=634, the Austin Group website}.
 
 POSIX standardizes @code{fflush()} as follows: If there
@@ -16059,7 +17206,7 @@ then @command{awk} flushes the buffers for @emph{all} open output files
 and pipes.
 
 @quotation NOTE
-Prior to version 4.0.2, @command{gawk}
+Prior to @value{PVERSION} 4.0.2, @command{gawk}
 would flush only the standard output if there was no argument,
 and flush all output files and pipes if the argument was the null
 string. This was changed in order to be compatible with Brian
@@ -16075,7 +17222,7 @@ only the standard output.
 @c @cindex warnings, automatic
 @cindex troubleshooting, @code{fflush()} function
 @code{fflush()} returns zero if the buffer is successfully flushed;
-otherwise, it returns non-zero (@command{gawk} returns @minus{}1).
+otherwise, it returns non-zero. (@command{gawk} returns @minus{}1.)
 In the case where all buffers are flushed, the return value is zero
 only if all buffers were flushed successfully.  Otherwise, it is
 @minus{}1, and @command{gawk} warns about the problem @var{filename}.
@@ -16085,8 +17232,9 @@ a file or pipe that was opened for reading (such as with @code{getline}),
 or if @var{filename} is not an open file, pipe, or coprocess.
 In such a case, @code{fflush()} returns @minus{}1, as well.
 
-@item system(@var{command})
-@cindex @code{system()} function
+@item @code{system(@var{command})}
+@cindexawkfunc{system}
+@cindex invoke shell command
 @cindex interacting with other programs
 Execute the operating-system
 command @var{command} and then return to the @command{awk} program.
@@ -16117,7 +17265,7 @@ close("/bin/sh")
 
 @noindent
 @cindex troubleshooting, @code{system()} function
-@cindex @code{--sandbox} option, disabling @code{system()} function
+@cindex @option{--sandbox} option, disabling @code{system()} function
 However, if your @command{awk}
 program is interactive, @code{system()} is useful for running large
 self-contained programs, such as a shell or an editor.
@@ -16233,6 +17381,7 @@ you would see the latter (undesirable) output.
 
 @node Time Functions
 @subsection Time Functions
+@cindex time functions
 
 @c STARTOFRANGE tst
 @cindex timestamps
@@ -16249,10 +17398,26 @@ particular log record was written.  Many programs log their timestamp
 in the form returned by the @code{time()} system call, which is the
 number of seconds since a particular epoch.  On POSIX-compliant systems,
 it is the number of seconds since
-1970-01-01 00:00:00 UTC, not counting leap seconds.@footnote{@xref{Glossary},
-especially the entries ``Epoch'' and ``UTC.''}
+1970-01-01 00:00:00 UTC, not counting leap
+@ifclear FOR_PRINT
+seconds.@footnote{@xref{Glossary}, especially the entries ``Epoch'' and ``UTC.''}
+@end ifclear
+@ifset FOR_PRINT
+seconds.
+@end ifset
 All known POSIX-compliant systems support timestamps from 0 through
-@math{2^{31} - 1}, which is sufficient to represent times through
+@iftex
+@math{2^{31} - 1},
+@end iftex
+@ifnottex
+@ifnotdocbook
+2^31 - 1,
+@end ifnotdocbook
+@end ifnottex
+@docbook
+2<superscript>31</superscript> &minus; 1, @c
+@end docbook
+which is sufficient to represent times through
 2038-01-19 03:14:07 UTC.  Many systems support a wider range of timestamps,
 including negative timestamps that represent times before the
 epoch.
@@ -16269,9 +17434,11 @@ However, recent versions
 of @command{mawk} (@pxref{Other Versions}) also support these functions.
 Optional parameters are enclosed in square brackets ([ ]):
 
-@table @code
-@item mktime(@var{datespec})
-@cindex @code{mktime()} function (@command{gawk})
+@c @asis for docbook
+@table @asis
+@item @code{mktime(@var{datespec})}
+@cindexgawkfunc{mktime}
+@cindex generate time values
 Turn @var{datespec} into a timestamp in the same form
 as is returned by @code{systime()}.  It is similar to the function of the
 same name in ISO C.  The argument, @var{datespec}, is a string of the form
@@ -16299,9 +17466,10 @@ is out of range, @code{mktime()} returns @minus{}1.
 
 @cindex @command{gawk}, @code{PROCINFO} array in
 @cindex @code{PROCINFO} array
-@item strftime(@r{[}@var{format} @r{[}, @var{timestamp} @r{[}, @var{utc-flag}@r{]]]})
+@item @code{strftime(} [@var{format} [@code{,} @var{timestamp} [@code{,} @var{utc-flag}] ] ]@code{)}
 @c STARTOFRANGE strf
-@cindex @code{strftime()} function (@command{gawk})
+@cindexgawkfunc{strftime}
+@cindex format time string
 Format the time specified by @var{timestamp}
 based on the contents of the @var{format} string and return the result.
 It is similar to the function of the same name in ISO C.
@@ -16318,11 +17486,12 @@ The default string value is
 @code{@w{"%a %b %e %H:%M:%S %Z %Y"}}.  This format string produces
 output that is equivalent to that of the @command{date} utility.
 You can assign a new value to @code{PROCINFO["strftime"]} to
-change the default format.
+change the default format; see below for the various format directives.
 
-@item systime()
-@cindex @code{systime()} function (@command{gawk})
+@item @code{systime()}
+@cindexgawkfunc{systime}
 @cindex timestamps
+@cindex current system time
 Return the current time as the number of seconds since
 the system epoch.  On POSIX systems, this is the number of seconds
 since 1970-01-01 00:00:00 UTC, not counting leap seconds.
@@ -16394,10 +17563,10 @@ This is the ISO 8601 date format.
 
 @item %g
 The year modulo 100 of the ISO 8601 week number, as a decimal number (00--99).
-For example, January 1, 1993 is in week 53 of 1992. Thus, the year
-of its ISO 8601 week number is 1992, even though its year is 1993.
-Similarly, December 31, 1973 is in week 1 of 1974. Thus, the year
-of its ISO week number is 1974, even though its year is 1973.
+For example, January 1, 2012 is in week 53 of 2011. Thus, the year
+of its ISO 8601 week number is 2011, even though its year is 2012.
+Similarly, December 31, 2012 is in week 1 of 2013. Thus, the year
+of its ISO week number is 2013, even though its year is 2012.
 
 @item %G
 The full year of the ISO week number, as a decimal number.
@@ -16478,7 +17647,7 @@ The locale's ``appropriate'' time representation.
 The year modulo 100 as a decimal number (00--99).
 
 @item %Y
-The full year as a decimal number (e.g., 2011).
+The full year as a decimal number (e.g., 2015).
 
 @c @cindex RFC 822
 @c @cindex RFC 1036
@@ -16512,17 +17681,6 @@ uses the system's version of @code{strftime()} if it's there.
 Typically, the conversion specifier either does not appear in the
 returned string or appears literally.}
 
-@c @cindex locale, definition of
-Informally, a @dfn{locale} is the geographic place in which a program
-is meant to run.  For example, a common way to abbreviate the date
-September 4, 2012 in the United States is ``9/4/12.''
-In many countries in Europe, however, it is abbreviated ``4.9.12.''
-Thus, the @samp{%x} specification in a @code{"US"} locale might produce
-@samp{9/4/12}, while in a @code{"EUROPE"} locale, it might produce
-@samp{4.9.12}.  The ISO C standard defines a default @code{"C"}
-locale, which is an environment that is typical of what many C programmers
-are used to.
-
 For systems that are not yet fully standards-compliant,
 @command{gawk} supplies a copy of
 @code{strftime()} from the GNU C Library.
@@ -16575,7 +17733,7 @@ the string.  For example:
 
 @example
 $ date '+Today is %A, %B %d, %Y.'
-@print{} Today is Wednesday, March 30, 2011.
+@print{} Today is Monday, May 05, 2014.
 @end example
 
 Here is the @command{gawk} version of the @command{date} utility.
@@ -16595,7 +17753,7 @@ case $1 in
 esac
 
 gawk 'BEGIN  @{
-    format = "%a %b %e %H:%M:%S %Z %Y"
+    format = PROCINFO["strftime"]
     exitval = 0
 
     if (ARGC > 2)
@@ -16616,6 +17774,7 @@ gawk 'BEGIN  @{
 
 @node Bitwise Functions
 @subsection Bit-Manipulation Functions
+@cindex bit-manipulation functions
 @c STARTOFRANGE bit
 @cindex bitwise, operations
 @c STARTOFRANGE and
@@ -16682,9 +17841,7 @@ Operands  | 0 | 1 | 0 | 1 | 0 | 1
 @end tex
 
 @docbook
-<!-- FIXME: Fix ID and add xref in text. -->
-<table id="table-bitwise-ops">
-<title>Bitwise Operations</title>
+<informaltable>
 
 <tgroup cols="7" colsep="1">
 <colspec colname="c1"/>
@@ -16744,7 +17901,7 @@ Operands  | 0 | 1 | 0 | 1 | 0 | 1
 
 </tbody>
 </tgroup>
-</table>
+</informaltable>
 @end docbook
 @end float
 
@@ -16778,28 +17935,34 @@ bitwise operations just described. They are:
 
 @cindex @command{gawk}, bitwise operations in
 @table @code
-@cindex @code{and()} function (@command{gawk})
-@item and(@var{v1}, @var{v2} @r{[}, @r{@dots{}]})
+@cindexgawkfunc{and}
+@cindex bitwise AND
+@item @code{and(@var{v1}, @var{v2}} [@code{,} @dots{}]@code{)}
 Return the bitwise AND of the arguments. There must be at least two.
 
-@cindex @code{compl()} function (@command{gawk})
-@item compl(@var{val})
+@cindexgawkfunc{compl}
+@cindex bitwise complement
+@item @code{compl(@var{val})}
 Return the bitwise complement of @var{val}.
 
-@cindex @code{lshift()} function (@command{gawk})
-@item lshift(@var{val}, @var{count})
+@cindexgawkfunc{lshift}
+@cindex left shift
+@item @code{lshift(@var{val}, @var{count})}
 Return the value of @var{val}, shifted left by @var{count} bits.
 
-@cindex @code{or()} function (@command{gawk})
-@item or(@var{v1}, @var{v2} @r{[}, @r{@dots{}]})
+@cindexgawkfunc{or}
+@cindex bitwise OR
+@item @code{or(@var{v1}, @var{v2}} [@code{,} @dots{}]@code{)}
 Return the bitwise OR of the arguments. There must be at least two.
 
-@cindex @code{rshift()} function (@command{gawk})
-@item rshift(@var{val}, @var{count})
+@cindexgawkfunc{rshift}
+@cindex right shift
+@item @code{rshift(@var{val}, @var{count})}
 Return the value of @var{val}, shifted right by @var{count} bits.
 
-@cindex @code{xor()} function (@command{gawk})
-@item xor(@var{v1}, @var{v2} @r{[}, @r{@dots{}]})
+@cindexgawkfunc{xor}
+@cindex bitwise XOR
+@item @code{xor(@var{v1}, @var{v2}} [@code{,} @dots{}]@code{)}
 Return the bitwise XOR of the arguments. There must be at least two.
 @end table
 
@@ -16890,6 +18053,7 @@ $ @kbd{gawk -f testbits.awk}
 @cindex strings, converting
 @cindex numbers, converting
 @cindex converting, numbers to strings
+@cindex number as string of bits
 The @code{bits2str()} function turns a binary number into a string.
 The number @code{1} represents a binary value where the rightmost bit
 is set to 1.  Using this mask,
@@ -16921,11 +18085,12 @@ results of the @code{compl()}, @code{lshift()}, and @code{rshift()} functions.
 
 @command{gawk} provides a single function that lets you distinguish
 an array from a scalar variable.  This is necessary for writing code
-that traverses every element of a true multidimensional array
+that traverses every element of an array of arrays.
 (@pxref{Arrays of Arrays}).
 
 @table @code
-@cindex @code{isarray()} function (@command{gawk})
+@cindexgawkfunc{isarray}
+@cindex scalar or array
 @item isarray(@var{x})
 Return a true value if @var{x} is an array. Otherwise return false.
 @end table
@@ -16933,7 +18098,7 @@ Return a true value if @var{x} is an array. Otherwise return false.
 @code{isarray()} is meant for use in two circumstances. The first is when
 traversing a multidimensional array: you can test if an element is itself
 an array or not.  The second is inside the body of a user-defined function
-(not discussed yet; @pxref{User-defined}), to test if a paramater is an
+(not discussed yet; @pxref{User-defined}), to test if a parameter is an
 array or not.
 
 Note, however, that using @code{isarray()} at the global level to test 
@@ -16947,6 +18112,7 @@ will end up turning it into a scalar.
 @subsection String-Translation Functions
 @cindex @command{gawk}, string-translation functions
 @cindex functions, string-translation
+@cindex string-translation functions
 @cindex internationalization
 @cindex @command{awk} programs, internationalizing
 
@@ -16957,9 +18123,10 @@ The descriptions here are purposely brief.
 for the full story.
 Optional parameters are enclosed in square brackets ([ ]):
 
-@table @code
-@cindex @code{bindtextdomain()} function (@command{gawk})
-@item bindtextdomain(@var{directory} @r{[}, @var{domain}@r{]})
+@table @asis
+@cindexgawkfunc{bindtextdomain}
+@cindex set directory of message catalogs
+@item @code{bindtextdomain(@var{directory}} [@code{,} @var{domain}]@code{)}
 Set the directory in which
 @command{gawk} will look for message translation files, in case they
 will not or cannot be placed in the ``standard'' locations
@@ -16971,15 +18138,16 @@ If @var{directory} is the null string (@code{""}), then
 @code{bindtextdomain()} returns the current binding for the
 given @var{domain}.
 
-@cindex @code{dcgettext()} function (@command{gawk})
-@item dcgettext(@var{string} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcgettext}
+@cindex translate string
+@item @code{dcgettext(@var{string}} [@code{,} @var{domain} [@code{,} @var{category}] ]@code{)}
 Return the translation of @var{string} in
 text domain @var{domain} for locale category @var{category}.
 The default value for @var{domain} is the current value of @code{TEXTDOMAIN}.
 The default value for @var{category} is @code{"LC_MESSAGES"}.
 
-@cindex @code{dcngettext()} function (@command{gawk})
-@item dcngettext(@var{string1}, @var{string2}, @var{number} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcngettext}
+@item @code{dcngettext(@var{string1}, @var{string2}, @var{number}} [@code{,} @var{domain} [@code{,} @var{category}] ]@code{)}
 Return the plural form used for @var{number} of the
 translation of @var{string1} and @var{string2} in text domain
 @var{domain} for locale category @var{category}. @var{string1} is the
@@ -16995,7 +18163,7 @@ The default value for @var{category} is @code{"LC_MESSAGES"}.
 @section User-Defined Functions
 
 @c STARTOFRANGE udfunc
-@cindex user-defined, functions
+@cindex user-defined functions
 @c STARTOFRANGE funcud
 @cindex functions, user-defined
 Complicated @command{awk} programs can often be simplified by defining
@@ -17027,12 +18195,12 @@ entire program before starting to execute any of it.
 
 The definition of a function named @var{name} looks like this:
 
-@example
-function @var{name}(@r{[}@var{parameter-list}@r{]})
-@{
+@display
+@code{function} @var{name}@code{(}[@var{parameter-list}]@code{)}
+@code{@{}
      @var{body-of-function}
-@}
-@end example
+@code{@}}
+@end display
 
 @cindex names, functions
 @cindex functions, names of
@@ -17047,14 +18215,20 @@ used as a variable, array, or function.
 @var{parameter-list} is an optional list of the function's arguments and local
 variable names, separated by commas.  When the function is called,
 the argument names are used to hold the argument values given in
-the call.  The local variables are initialized to the empty string.
+the call.
+
 A function cannot have two parameters with the same name, nor may it
 have a parameter with the same name as the function itself.
+In addition, according to the POSIX standard, function parameters
+cannot have the same name as one of the special built-in variables
+(@pxref{Built-in Variables}).  Not all versions of @command{awk} enforce
+this restriction.)
 
-In addition, according to the POSIX standard, function parameters cannot have the same
-name as one of the special built-in variables
-(@pxref{Built-in Variables}.  Not all versions of @command{awk}
-enforce this restriction.
+Local variables act like the empty string if referenced where a string
+value is required, and like zero if referenced where a numeric value
+is required. This is the same as regular variables that have never been
+assigned a value.  (There is more to understand about local variables;
+@pxref{Dynamic Typing}.)
 
 The @var{body-of-function} consists of @command{awk} statements.  It is the
 most important part of the definition, because it says what the function
@@ -17081,6 +18255,7 @@ conventional to place some extra space between the arguments and
 the local variables, in order to document how your function is supposed to be used.
 
 @cindex variables, shadowing
+@cindex shadowing of variable values
 During execution of the function body, the arguments and local variable
 values hide, or @dfn{shadow}, any variables of the same names used in the
 rest of the program.  The shadowed variables are not accessible in the
@@ -17101,7 +18276,7 @@ function.  When this happens, we say the function is @dfn{recursive}.
 The act of a function calling itself is called @dfn{recursion}.
 
 All the built-in functions return a value to their caller.
-User-defined functions can do also, using the @code{return} statement,
+User-defined functions can do so also, using the @code{return} statement,
 which is described in detail in @ref{Return Statement}.
 Many of the subsequent examples in this @value{SECTION} use
 the @code{return} statement.
@@ -17139,6 +18314,7 @@ keyword @code{function} when defining a function.
 
 @node Function Example
 @subsection Function Definition Examples
+@cindex function definition example
 
 Here is an example of a user-defined function, called @code{myprint()}, that
 takes a number and prints it in a specific format:
@@ -17193,7 +18369,8 @@ Instead of having
 to repeat this loop everywhere that you need to clear out
 an array, your program can just call @code{delarray}.
 (This guarantees portability.  The use of @samp{delete @var{array}} to delete
-the contents of an entire array is a nonstandard extension.)
+the contents of an entire array is a recent@footnote{Late in 2012.}
+addition to the POSIX standard.)
 
 The following is an example of a recursive function.  It takes a string
 as an input parameter and returns the string in backwards order.
@@ -17236,7 +18413,7 @@ to create an @command{awk} version of @code{ctime()}:
 
 function ctime(ts,    format)
 @{
-    format = "%a %b %e %H:%M:%S %Z %Y"
+    format = PROCINFO["strftime"]
     if (ts == 0)
         ts = systime()       # use current time as default
     return strftime(format, ts)
@@ -17249,7 +18426,10 @@ function ctime(ts,    format)
 @subsection Calling User-Defined Functions
 
 @c STARTOFRANGE fudc
-This section describes how to call a user-defined function.
+@cindex functions, user-defined, calling
+@dfn{Calling a function} means causing the function to run and do its job.
+A function call is an expression and its value is the value returned by
+the function.
 
 @menu
 * Calling A Function::          Don't use spaces.
@@ -17260,11 +18440,6 @@ This section describes how to call a user-defined function.
 @node Calling A Function
 @subsubsection Writing A Function Call
 
-@cindex functions, user-defined, calling
-@dfn{Calling a function} means causing the function to run and do its job.
-A function call is an expression and its value is the value returned by
-the function.
-
 A function call consists of the function name followed by the arguments
 in parentheses.  @command{awk} expressions are what you write in the
 call for the arguments.  Each time the call is executed, these
@@ -17288,9 +18463,10 @@ an error.
 @node Variable Scope
 @subsubsection Controlling Variable Scope
 
-@cindex local variables
-@cindex variables, local
-There is no way to make a variable local to a @code{@{ @dots{} @}} block in
+@cindex local variables, in a function
+@cindex variables, local to a function
+Unlike many languages,
+there is no way to make a variable local to a @code{@{} @dots{} @code{@}} block in
 @command{awk}, but you can make a variable local to a function. It is
 good practice to do so whenever a variable is needed only in that
 function.
@@ -17552,14 +18728,14 @@ This statement returns control to the calling part of the @command{awk} program.
 can also be used to return a value for use in the rest of the @command{awk}
 program.  It looks like this:
 
-@example
-return @r{[}@var{expression}@r{]}
-@end example
+@display
+@code{return} [@var{expression}]
+@end display
 
 The @var{expression} part is optional.
 Due most likely to an oversight, POSIX does not define what the return
 value is if you omit the @var{expression}.  Technically speaking, this
-make the returned value undefined, and therefore, unpredictable.
+makes the returned value undefined, and therefore, unpredictable.
 In practice, though, all versions of @command{awk} simply return the
 null string, which acts like zero if used in a numeric context.
 
@@ -17662,9 +18838,9 @@ BEGIN @{
 @end example
 
 In this example, the first call to @code{foo()} generates
-a fatal error, so @command{gawk} will not report the second
-error. If you comment out that call, though, then @command{gawk}
-will report the second error.
+a fatal error, so @command{awk} will not report the second
+error. If you comment out that call, though, then @command{awk}
+does report the second error.
 
 Usually, such things aren't a big issue, but it's worth
 being aware of them.
@@ -17734,7 +18910,7 @@ character:
 
 @example
 the_func = "sum"
-result = @@the_func()   # calls the `sum' function
+result = @@the_func()   # calls the sum() function
 @end example
 
 Here is a full program that processes the previously shown data,
@@ -17855,8 +19031,9 @@ We can do something similar using @command{gawk}, like this:
 @ignore
 @c file eg/lib/quicksort.awk
 #
-# Arnold Robbins, arnold@skeeve.com, Public Domain
+# Arnold Robbins, arnold@@skeeve.com, Public Domain
 # January 2009
+
 @c endfile
 
 @end ignore
@@ -17929,7 +19106,7 @@ or equal to), which yields data sorted in descending order.
 
 Next comes a sorting function.  It is parameterized with the starting and
 ending field numbers and the comparison function. It builds an array with
-the data and calls @code{quicksort} appropriately, and then formats the
+the data and calls @code{quicksort()} appropriately, and then formats the
 results as a single string:
 
 @example
@@ -17977,7 +19154,7 @@ function rsort(first, last)
 @c endfile
 @end example
 
-Here is an extended version of the data file:
+Here is an extended version of the @value{DF}:
 
 @example
 @c file eg/data/class_data2
@@ -18028,21 +19205,80 @@ for (i = 1; i <= n; i++)
 @noindent
 @code{gawk} will look up the actual function to call only once.
 
+@node Functions Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+@command{awk} provides built-in functions and lets you define your own
+functions.
+
+@item
+POSIX @command{awk} provides three kinds of built-in functions: numeric,
+string, and I/O.  @command{gawk} provides functions that work with values
+representing time, do bit manipulation, sort arrays, and internationalize
+and localize programs.  @command{gawk} also provides several extensions to
+some of standard functions, typically in the form of additional arguments.
+
+@item
+Functions accept zero or more arguments and return a value.  The
+expressions that provide the argument values are completely evaluated
+before the function is called. Order of evaluation is not defined.
+The return value can be ignored.
+
+@item
+The handling of backslash in @code{sub()} and @code{gsub()} is not simple.
+It is more straightforward in @command{gawk}'s @code{gensub()} function,
+but that function still requires care in its use.
+
+@item
+User-defined functions provide important capabilities but come with
+some syntactic inelegancies. In a function call, there cannot be any
+space between the function name and the opening left parenthesis of the
+argument list.  Also, there is no provision for local variables, so the
+convention is to add extra parameters, and to separate them visually
+from the real parameters by extra whitespace.
+
+@item
+User-defined functions may call other user-defined (and built-in)
+functions and may call themselves recursively. Function parameters
+``hide'' any global variables of the same names.
+
+@item
+Scalar values are passed to user-defined functions by value. Array
+parameters are passed by reference; any changes made by the function to
+array parameters are thus visible after the function has returned.
+
+@item
+Use the @code{return} statement to return from a user-defined function.
+An optional expression becomes the function's return value.  Only scalar
+values may be returned by a function.
+
+@item
+If a variable that has never been used is passed to a user-defined
+function, how that function treats the variable can set its nature:
+either scalar or array.
+
+@item
+@command{gawk} provides indirect function calls using a special syntax.
+By setting a variable to the name of a user-defined function, you can
+determine at runtime what function will be called at that point in the
+program. This is equivalent to function pointers in C and C++.
+
+@end itemize
+
 @c ENDOFRANGE funcud
 
-@iftex
-@part Part II:@* Problem Solving With @command{awk}
-@end iftex
+@ifnotinfo
+@part @value{PART2}Problem Solving With @command{awk}
+@end ifnotinfo
 
-@ignore
 @ifdocbook
-@part Part II:@* Problem Solving With @command{awk}
-
 Part II shows how to use @command{awk} and @command{gawk} for problem solving.
 There is lots of code here for you to read and learn from.
 It contains the following chapters:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Library Functions}.
 
@@ -18050,7 +19286,6 @@ It contains the following chapters:
 @ref{Sample Programs}.
 @end itemize
 @end ifdocbook
-@end ignore
 
 @node Library Functions
 @chapter A Library of @command{awk} Functions
@@ -18067,6 +19302,8 @@ it allows you to encapsulate algorithms and program tasks in a single
 place.  It simplifies programming, making program development more
 manageable, and making programs more readable.
 
+@cindex Kernighan, Brian
+@cindex Plauger, P.J.@:
 In their seminal 1976 book, @cite{Software Tools},@footnote{Sadly, over 35
 years later, many of the lessons taught by this book have yet to be
 learned by a vast number of practicing programmers.} Brian Kernighan
@@ -18086,7 +19323,6 @@ that their statement is correct, this @value{CHAPTER} and @ref{Sample
 Programs}, provide a good-sized body of code for you to read, and we hope,
 to learn from.
 
-@c 2e: USE TEXINFO-2 FUNCTION DEFINITION STUFF!!!!!!!!!!!!!
 This @value{CHAPTER} presents a library of useful @command{awk} functions.
 Many of the sample programs presented later in this @value{DOCUMENT}
 use these functions.
@@ -18099,9 +19335,11 @@ these example library functions and programs from the Texinfo source
 for this @value{DOCUMENT}.
 (This has already been done as part of the @command{gawk} distribution.)
 
+@ifclear FOR_PRINT
 If you have written one or more useful, general-purpose @command{awk} functions
 and would like to contribute them to the @command{awk} user community, see
 @ref{How To Contribute}, for more information.
+@end ifclear
 
 @cindex portability, example programs
 The programs in this @value{CHAPTER} and in
@@ -18110,7 +19348,7 @@ freely use features that are @command{gawk}-specific.
 Rewriting these programs for different implementations of @command{awk}
 is pretty straightforward.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Diagnostic error messages are sent to @file{/dev/stderr}.
 Use @samp{| "cat 1>&2"} instead of @samp{> "/dev/stderr"} if your system
@@ -18154,6 +19392,8 @@ comparisons use only lowercase letters.
 * Passwd Functions::            Functions for getting user information.
 * Group Functions::             Functions for getting group information.
 * Walking Arrays::              A function to walk arrays of arrays.
+* Library Functions Summary::   Summary of library functions.
+* Library exercises::           Exercises.
 @end menu
 
 @node Library Names
@@ -18196,7 +19436,7 @@ with the user's program.
 @cindex underscore (@code{_}), in names of private variables
 In addition, several of the library functions use a prefix that helps
 indicate what function or set of functions use the variables---for example,
-@code{_pw_byname} in the user database routines
+@code{_pw_byname()} in the user database routines
 (@pxref{Passwd Functions}).
 This convention is recommended, since it even further decreases the
 chance of inadvertent conflict among variable names.  Note that this
@@ -18215,7 +19455,7 @@ The leading capital letter indicates that it is global, while the fact that
 the variable name is not all capital letters indicates that the variable is
 not one of @command{awk}'s built-in variables, such as @code{FS}.
 
-@cindex @code{--dump-variables} option
+@cindex @option{--dump-variables} option, using for library functions
 It is also important that @emph{all} variables in library
 functions that do not need to save state are, in fact, declared
 local.@footnote{@command{gawk}'s @option{--dump-variables} command-line
@@ -18288,11 +19528,12 @@ provides an implementation for other versions of @command{awk}:
 #
 # Arnold Robbins, arnold@@skeeve.com, Public Domain
 # February, 2004
+# Revised June, 2014
 
 @c endfile
 @end ignore
 @c file eg/lib/strtonum.awk
-function mystrtonum(str,        ret, chars, n, i, k, c)
+function mystrtonum(str,        ret, n, i, k, c)
 @{
     if (str ~ /^0[0-7]*$/) @{
         # octal
@@ -18305,7 +19546,7 @@ function mystrtonum(str,        ret, chars, n, i, k, c)
 
             ret = ret * 8 + k
         @}
-    @} else if (str ~ /^0[xX][[:xdigit:]]+/) @{
+    @} else if (str ~ /^0[xX][[:xdigit:]]+$/) @{
         # hexadecimal
         str = substr(str, 3)    # lop off leading 0x
         n = length(str)
@@ -18313,10 +19554,7 @@ function mystrtonum(str,        ret, chars, n, i, k, c)
         for (i = 1; i <= n; i++) @{
             c = substr(str, i, 1)
             c = tolower(c)
-            if ((k = index("0123456789", c)) > 0)
-                k-- # adjust for 1-basing in awk
-            else if ((k = index("abcdef", c)) > 0)
-                k += 9
+            k = index("123456789abcdef", c)
 
             ret = ret * 16 + k
         @}
@@ -18484,7 +19722,7 @@ An @code{END} rule is automatically added
 to the program calling @code{assert()}.  Normally, if a program consists
 of just a @code{BEGIN} rule, the input files and/or standard input are
 not read. However, now that the program has an @code{END} rule, @command{awk}
-attempts to read the input data files or standard input
+attempts to read the input @value{DF}s or standard input
 (@pxref{Using BEGIN/END}),
 most likely causing the program to hang as it waits for input.
 
@@ -18510,9 +19748,9 @@ with an @code{exit} statement.
 The way @code{printf} and @code{sprintf()}
 (@pxref{Printf})
 perform rounding often depends upon the system's C @code{sprintf()}
-subroutine.  On many machines, @code{sprintf()} rounding is ``unbiased,''
-which means it doesn't always round a trailing @samp{.5} up, contrary
-to naive expectations.  In unbiased rounding, @samp{.5} rounds to even,
+subroutine.  On many machines, @code{sprintf()} rounding is @dfn{unbiased},
+which means it doesn't always round a trailing .5 up, contrary
+to naive expectations.  In unbiased rounding, .5 rounds to even,
 rather than always up, so 1.5 rounds to 2 but 4.5 rounds to 4.  This means
 that if you are using a format that does rounding (e.g., @code{"%.0f"}),
 you should check what your system does.  The following function does
@@ -18561,7 +19799,7 @@ function round(x,   ival, aval, fraction)
 @c don't include test harness in the file that gets installed
 
 # test harness
-@{ print $0, round($0) @}
+# @{ print $0, round($0) @}
 @end example
 
 @node Cliff Random Function
@@ -18628,6 +19866,7 @@ reason to build them into the @command{awk} interpreter:
 
 @cindex @code{ord()} user-defined function
 @cindex @code{chr()} user-defined function
+@cindex @code{_ord_init()} user-defined function
 @example
 @c file eg/lib/ord.awk
 # ord.awk --- do ord and chr
@@ -18674,8 +19913,9 @@ function _ord_init(    low, high, i, t)
 @cindex character sets (machine character encodings)
 @cindex ASCII
 @cindex EBCDIC
+@cindex Unicode
 @cindex mark parity
-Some explanation of the numbers used by @code{chr} is worthwhile.
+Some explanation of the numbers used by @code{_ord_init()} is worthwhile.
 The most prominent character set in use today is ASCII.@footnote{This
 is changing; many systems use Unicode, a very large character set
 that includes ASCII as a subset.  On systems with full Unicode support,
@@ -18686,7 +19926,7 @@ Although an
 defines characters that use the values from 0 to 127.@footnote{ASCII
 has been extended in many countries to use the values from 128 to 255
 for country-specific characters.  If your  system uses these extensions,
-you can simplify @code{_ord_init} to loop from 0 to 255.}
+you can simplify @code{_ord_init()} to loop from 0 to 255.}
 In the now distant past,
 at least one minicomputer manufacturer
 @c Pr1me, blech
@@ -18853,7 +20093,7 @@ function getlocaltime(time,    ret, now, i)
     now = systime()
 
     # return date(1)-style output
-    ret = strftime("%a %b %e %H:%M:%S %Z %Y", now)
+    ret = strftime(PROCINFO["strftime"], now)
 
     # clear out target array
     delete time
@@ -18969,7 +20209,7 @@ This tests the result to see if it is empty or not. An equivalent
 test would be @samp{contents == ""}.
 
 @node Data File Management
-@section Data File Management
+@section @value{DDF} Management
 
 @c STARTOFRANGE dataf
 @cindex files, managing
@@ -18978,7 +20218,7 @@ test would be @samp{contents == ""}.
 @c STARTOFRANGE flibdataf
 @cindex functions, library, managing data files
 This @value{SECTION} presents functions that are useful for managing
-command-line data files.
+command-line @value{DF}s.
 
 @menu
 * Filetrans Function::          A function for handling data file transitions.
@@ -18989,7 +20229,7 @@ command-line data files.
 @end menu
 
 @node Filetrans Function
-@subsection Noting Data File Boundaries
+@subsection Noting @value{DDF} Boundaries
 
 @cindex files, managing, data file boundaries
 @cindex files, initialization and cleanup
@@ -18997,8 +20237,8 @@ The @code{BEGIN} and @code{END} rules are each executed exactly once at
 the beginning and end of your @command{awk} program, respectively
 (@pxref{BEGIN/END}).
 We (the @command{gawk} authors) once had a user who mistakenly thought that the
-@code{BEGIN} rule is executed at the beginning of each data file and the
-@code{END} rule is executed at the end of each data file.
+@code{BEGIN} rule is executed at the beginning of each @value{DF} and the
+@code{END} rule is executed at the end of each @value{DF}.
 
 When informed
 that this was not the case, the user requested that we add new special
@@ -19009,7 +20249,7 @@ Adding these special patterns to @command{gawk} wasn't necessary;
 the job can be done cleanly in @command{awk} itself, as illustrated
 by the following library program.
 It arranges to call two user-supplied functions, @code{beginfile()} and
-@code{endfile()}, at the beginning and end of each data file.
+@code{endfile()}, at the beginning and end of each @value{DF}.
 Besides solving the problem in only nine(!) lines of code, it does so
 @emph{portably}; this works with any implementation of @command{awk}:
 
@@ -19040,17 +20280,17 @@ This file must be loaded before the user's ``main'' program, so that the
 rule it supplies is executed first.
 
 This rule relies on @command{awk}'s @code{FILENAME} variable that
-automatically changes for each new data file.  The current file name is
+automatically changes for each new @value{DF}.  The current @value{FN} is
 saved in a private variable, @code{_oldfilename}.  If @code{FILENAME} does
-not equal @code{_oldfilename}, then a new data file is being processed and
+not equal @code{_oldfilename}, then a new @value{DF} is being processed and
 it is necessary to call @code{endfile()} for the old file.  Because
 @code{endfile()} should only be called if a file has been processed, the
 program first checks to make sure that @code{_oldfilename} is not the null
-string.  The program then assigns the current file name to
+string.  The program then assigns the current @value{FN} to
 @code{_oldfilename} and calls @code{beginfile()} for the file.
 Because, like all @command{awk} variables, @code{_oldfilename} is
 initialized to the null string, this rule executes correctly even for the
-first data file.
+first @value{DF}.
 
 The program also supplies an @code{END} rule to do the final processing for
 the last file.  Because this @code{END} rule comes before any @code{END} rules
@@ -19059,7 +20299,7 @@ again the value of multiple @code{BEGIN} and @code{END} rules should be clear.
 
 @cindex @code{beginfile()} user-defined function
 @cindex @code{endfile()} user-defined function
-If the same data file occurs twice in a row on the command line, then
+If the same @value{DF} occurs twice in a row on the command line, then
 @code{endfile()} and @code{beginfile()} are not executed at the end of the
 first pass and at the beginning of the second pass.
 The following version solves the problem:
@@ -19174,16 +20414,18 @@ The @code{rewind()} function also relies on the @code{nextfile} keyword
 (@pxref{Nextfile Statement}).
 
 @node File Checking
-@subsection Checking for Readable Data Files
+@subsection Checking for Readable @value{DDF}s
 
 @cindex troubleshooting, readable data files
 @cindex readable data files@comma{} checking
 @cindex files, skipping
-Normally, if you give @command{awk} a data file that isn't readable,
-it stops with a fatal error.  There are times when you
-might want to just ignore such files and keep going.  You can
-do this by prepending the following program to your @command{awk}
-program:
+Normally, if you give @command{awk} a @value{DF} that isn't readable,
+it stops with a fatal error.  There are times when you might want to
+just ignore such files and keep going.@footnote{The @code{BEGINFILE}
+special pattern (@pxref{BEGINFILE/ENDFILE}) provides an alternative
+mechanism for dealing with files that can't be opened.  However, the
+code here provides a portable solution.} You can do this by prepending
+the following program to your @command{awk} program:
 
 @cindex @code{readable.awk} program
 @example
@@ -19221,22 +20463,22 @@ skips the file (since it's no longer in the list).
 See also @ref{ARGC and ARGV}.
 
 @node Empty Files
-@subsection Checking For Zero-length Files
+@subsection Checking for Zero-length Files
 
 All known @command{awk} implementations silently skip over zero-length files.
 This is a by-product of @command{awk}'s implicit 
 read-a-record-and-match-against-the-rules loop: when @command{awk}
 tries to read a record from an empty file, it immediately receives an
 end of file indication, closes the file, and proceeds on to the next
-command-line data file, @emph{without} executing any user-level
+command-line @value{DF}, @emph{without} executing any user-level
 @command{awk} program code.
 
 Using @command{gawk}'s @code{ARGIND} variable
 (@pxref{Built-in Variables}), it is possible to detect when an empty
-data file has been skipped.  Similar to the library file presented
+@value{DF} has been skipped.  Similar to the library file presented
 in @ref{Filetrans Function}, the following library file calls a function named
 @code{zerofile()} that the user must provide.  The arguments passed are
-the file name and the position in @code{ARGV} where it was found:
+the @value{FN} and the position in @code{ARGV} where it was found:
 
 @cindex @code{zerofile.awk} program
 @example
@@ -19283,56 +20525,16 @@ the end of the command-line arguments.  Note that the test in the
 condition of the @code{for} loop uses the @samp{<=} operator,
 not @samp{<}.
 
-As an exercise, you might consider whether this same problem can
-be solved without relying on @command{gawk}'s @code{ARGIND} variable.
-
-As a second exercise, revise this code to handle the case where
-an intervening value in @code{ARGV} is a variable assignment.
-
-@ignore
-# zerofile2.awk --- same thing, portably
-
-BEGIN @{
-    ARGIND = Argind = 0
-    for (i = 1; i < ARGC; i++)
-        Fnames[ARGV[i]]++
-
-@}
-FNR == 1 @{
-    while (ARGV[ARGIND] != FILENAME)
-        ARGIND++
-    Seen[FILENAME]++
-    if (Seen[FILENAME] == Fnames[FILENAME])
-        do
-            ARGIND++
-        while (ARGV[ARGIND] != FILENAME)
-@}
-ARGIND > Argind + 1 @{
-    for (Argind++; Argind < ARGIND; Argind++)
-        zerofile(ARGV[Argind], Argind)
-@}
-ARGIND != Argind @{
-    Argind = ARGIND
-@}
-END @{
-    if (ARGIND < ARGC - 1)
-        ARGIND = ARGC - 1 
-    if (ARGIND > Argind)
-        for (Argind++; Argind <= ARGIND; Argind++)
-            zerofile(ARGV[Argind], Argind)
-@}
-@end ignore
-
 @node Ignoring Assigns
-@subsection Treating Assignments as File Names
+@subsection Treating Assignments as @value{FFN}s
 
 @cindex assignments as filenames
 @cindex filenames, assignments as
 Occasionally, you might not want @command{awk} to process command-line
 variable assignments
 (@pxref{Assignment Options}).
-In particular, if you have a file name that contain an @samp{=} character,
-@command{awk} treats the file name as an assignment, and does not process it.
+In particular, if you have a @value{FN} that contains an @samp{=} character,
+@command{awk} treats the @value{FN} as an assignment, and does not process it.
 
 Some users have suggested an additional command-line option for @command{gawk}
 to disable command-line assignments.  However, some simple programming with
@@ -19376,7 +20578,7 @@ awk -v No_command_assign=1 -f noassign.awk -f yourprog.awk *
 The function works by looping through the arguments.
 It prepends @samp{./} to
 any argument that matches the form
-of a variable assignment, turning that argument into a file name.
+of a variable assignment, turning that argument into a @value{FN}.
 
 The use of @code{No_command_assign} allows you to disable command-line
 assignments at invocation time, by giving the variable a true value.
@@ -19460,7 +20662,6 @@ application might want to print its own error message.)
 
 @item optopt
 The letter representing the command-line option.
-@c While not usually documented, most versions supply this variable.
 @end table
 
 The following C fragment shows how @code{getopt()} might process command-line
@@ -19511,7 +20712,6 @@ necessary for accessing individual characters
 function was written before @command{gawk} acquired the ability to
 split strings into single characters using @code{""} as the separator.
 We have left it alone, since using @code{substr()} is more portable.}
-@c FIXME: could use split(str, a, "") to do it more easily.
 
 The discussion that follows walks through the code a bit at a time:
 
@@ -19694,7 +20894,7 @@ BEGIN @{
     # test program
     if (_getopt_test) @{
         while ((_go_c = getopt(ARGC, ARGV, "ab:cd")) != -1)
-            printf("c = <%c>, optarg = <%s>\n",
+            printf("c = <%c>, Optarg = <%s>\n",
                                        _go_c, Optarg)
         printf("non-option arguments:\n")
         for (; Optind < ARGC; Optind++)
@@ -19710,32 +20910,31 @@ result of two sample runs of the test program:
 
 @example
 $ @kbd{awk -f getopt.awk -v _getopt_test=1 -- -a -cbARG bax -x}
-@print{} c = <a>, optarg = <>
-@print{} c = <c>, optarg = <>
-@print{} c = <b>, optarg = <ARG>
+@print{} c = <a>, Optarg = <>
+@print{} c = <c>, Optarg = <>
+@print{} c = <b>, Optarg = <ARG>
 @print{} non-option arguments:
 @print{}         ARGV[3] = <bax>
 @print{}         ARGV[4] = <-x>
 
 $ @kbd{awk -f getopt.awk -v _getopt_test=1 -- -a -x -- xyz abc}
-@print{} c = <a>, optarg = <>
+@print{} c = <a>, Optarg = <>
 @error{} x -- invalid option
-@print{} c = <?>, optarg = <>
+@print{} c = <?>, Optarg = <>
 @print{} non-option arguments:
 @print{}         ARGV[4] = <xyz>
 @print{}         ARGV[5] = <abc>
 @end example
 
-In both runs,
-the first @option{--} terminates the arguments to @command{awk}, so that it does
-not try to interpret the @option{-a}, etc., as its own options.
+In both runs, the first @option{--} terminates the arguments to
+@command{awk}, so that it does not try to interpret the @option{-a},
+etc., as its own options.
 
 @quotation NOTE
-After @code{getopt()} is through, it is the responsibility of the user level
-code to
-clear out all the elements of @code{ARGV} from 1 to @code{Optind},
-so that @command{awk} does not try to process the command-line options
-as file names.
+After @code{getopt()} is through, it is the responsibility of the
+user level code to clear out all the elements of @code{ARGV} from 1
+to @code{Optind}, so that @command{awk} does not try to process the
+command-line options as @value{FN}s.
 @end quotation
 
 Several of the sample programs presented in
@@ -19752,7 +20951,7 @@ use @code{getopt()} to process their arguments.
 @c STARTOFRANGE libfudata
 @cindex libraries of @command{awk} functions, user database, reading
 @c STARTOFRANGE flibudata
-@cindex functions, library, user database, reading
+@cindex functions, library, user database@comma{} reading
 @c STARTOFRANGE udatar
 @cindex user database@comma{} reading
 @c STARTOFRANGE dataur
@@ -19797,14 +20996,12 @@ no more entries, it returns @code{NULL}, the null pointer.  When this
 happens, the C program should call @code{endpwent()} to close the database.
 Following is @command{pwcat}, a C program that ``cats'' the password database:
 
-@c Use old style function header for portability to old systems (SunOS, HP/UX).
-
 @example
 @c file eg/lib/pwcat.c
 /*
  * pwcat.c
  *
- * Generate a printable version of the password database
+ * Generate a printable version of the password database.
  */
 @c endfile
 @ignore
@@ -20001,7 +21198,7 @@ from anywhere within a user's program, and the user may have his
 or her
 own way of splitting records and fields.
 
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, testing the field splitting
 The @code{using_fw} variable checks @code{PROCINFO["FS"]}, which
 is @code{"FIELDWIDTHS"} if field splitting is being done with
 @code{FIELDWIDTHS}.  This makes it possible to restore the correct
@@ -20010,7 +21207,7 @@ field-splitting mechanism later.  The test can only be true for
 or on some other @command{awk} implementation.
 
 The code that checks for using @code{FPAT}, using @code{using_fpat}
-and @code{PROCINFO["FS"]} is similar.
+and @code{PROCINFO["FS"]}, is similar.
 
 The main part of the function uses a loop to read database lines, split
 the line into fields, and then store the line into each array as necessary.
@@ -20040,10 +21237,9 @@ function getpwnam(name)
 @end example
 
 @cindex @code{getpwuid()} function (C library)
-Similarly,
-the @code{getpwuid} function takes a user ID number argument. If that
-user number is in the database, it returns the appropriate line. Otherwise, it
-returns the null string:
+Similarly, the @code{getpwuid()} function takes a user ID number
+argument. If that user number is in the database, it returns the
+appropriate line. Otherwise, it returns the null string:
 
 @cindex @code{getpwuid()} user-defined function
 @example
@@ -20120,12 +21316,12 @@ uses these functions.
 @c STARTOFRANGE libfgdata
 @cindex libraries of @command{awk} functions, group database, reading
 @c STARTOFRANGE flibgdata
-@cindex functions, library, group database, reading
+@cindex functions, library, group database@comma{} reading
 @c STARTOFRANGE gdatar
 @cindex group database, reading
 @c STARTOFRANGE datagr
 @cindex database, group, reading
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, and group membership
 @cindex @code{getgrent()} function (C library)
 @cindex @code{getgrent()} user-defined function
 @cindex groups@comma{} information about
@@ -20151,7 +21347,7 @@ is as follows:
 /*
  * grcat.c
  *
- * Generate a printable version of the group database
+ * Generate a printable version of the group database.
  */
 @c endfile
 @ignore
@@ -20238,7 +21434,7 @@ it is usually empty or set to @samp{*}.
 
 @item Group ID Number
 The group's numeric group ID number;
-this number must be unique within the file.
+the association of name to number must be unique within the file.
 (On some systems it's a C @code{long}, and not an @code{int}.  Thus
 we cast it to @code{long} for all cases.)
 
@@ -20368,16 +21564,16 @@ database for the same group.  This is common when a group has a large number
 of members.  A pair of such entries might look like the following:
 
 @example
-tvpeople:*:101:johnny,jay,arsenio
+tvpeople:*:101:johny,jay,arsenio
 tvpeople:*:101:david,conan,tom,joan
 @end example
 
 For this reason, @code{_gr_init()} looks to see if a group name or
 group ID number is already seen.  If it is, then the user names are
-simply concatenated onto the previous list of users.  (There is actually a
+simply concatenated onto the previous list of users.@footnote{There is actually a
 subtle problem with the code just presented.  Suppose that
 the first time there were no names. This code adds the names with
-a leading comma. It also doesn't check that there is a @code{$4}.)
+a leading comma. It also doesn't check that there is a @code{$4}.}
 
 Finally, @code{_gr_init()} closes the pipeline to @command{grcat}, restores
 @code{FS} (and @code{FIELDWIDTHS} or @code{FPAT} if necessary), @code{RS}, and @code{$0},
@@ -20537,24 +21733,121 @@ $ @kbd{gawk -f walk_array.awk}
 @print{} a[3] = 3
 @end example
 
-Walking an array and processing each element is a general-purpose
-operation.  You might want to consider generalizing the @code{walk_array()}
-function by adding an additional parameter named @code{process}.
-
-Then, inside the loop, instead of simply printing the array element's
-index and value, use the indirect function call syntax
-(@pxref{Indirect Calls}) on @code{process}, passing it the index
-and the value.
-
-When calling @code{walk_array()}, you would pass the name of a user-defined
-function that expects to receive and index and a value, and then processes
-the element.
-
-
 @c ENDOFRANGE libfgdata
 @c ENDOFRANGE flibgdata
 @c ENDOFRANGE gdatar
 @c ENDOFRANGE libf
+
+@node Library Functions Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Reading programs is an excellent way to learn Good Programming.
+The functions provided in this @value{CHAPTER} and the next are intended
+to serve that purpose.
+
+@item
+When writing general-purpose library functions, put some thought into how
+to name any global variables so that they won't conflict with variables
+from a user's program.
+
+@item
+The functions presented here fit into the following categories:
+
+@c nested list
+@table @asis
+@item General problems
+Number to string conversion, assertions, rounding, random number
+generation, converting characters to numbers, joining strings, getting
+easily usable time-of-day information, and reading a whole file in
+one shot.
+
+@item Managing @value{DF}s
+Noting @value{DF} boundaries, rereading the current file, checking for
+readable files, checking for zero-length files, and treating assignments
+as @value{FN}s.
+
+@item Processing command-line options
+An @command{awk} version of the standard C @code{getopt()} function.
+
+@item Reading the user and group databases
+Two sets of routines that parallel the C library versions.
+
+@item Traversing arrays of arrays
+A simple function to traverse an array of arrays to any depth.
+@end table
+@c end nested list
+
+@end itemize
+
+@node Library exercises
+@section Exercises
+
+@enumerate
+@item
+In @ref{Empty Files}, we presented the @file{zerofile.awk} program,
+which made use of @command{gawk}'s @code{ARGIND} variable.  Can this
+problem be solved without relying on @code{ARGIND}?  If so, how?
+
+@ignore
+# zerofile2.awk --- same thing, portably
+
+BEGIN @{
+    ARGIND = Argind = 0
+    for (i = 1; i < ARGC; i++)
+        Fnames[ARGV[i]]++
+
+@}
+FNR == 1 @{
+    while (ARGV[ARGIND] != FILENAME)
+        ARGIND++
+    Seen[FILENAME]++
+    if (Seen[FILENAME] == Fnames[FILENAME])
+        do
+            ARGIND++
+        while (ARGV[ARGIND] != FILENAME)
+@}
+ARGIND > Argind + 1 @{
+    for (Argind++; Argind < ARGIND; Argind++)
+        zerofile(ARGV[Argind], Argind)
+@}
+ARGIND != Argind @{
+    Argind = ARGIND
+@}
+END @{
+    if (ARGIND < ARGC - 1)
+        ARGIND = ARGC - 1 
+    if (ARGIND > Argind)
+        for (Argind++; Argind <= ARGIND; Argind++)
+            zerofile(ARGV[Argind], Argind)
+@}
+@end ignore
+
+@item
+As a related challenge, revise that code to handle the case where
+an intervening value in @code{ARGV} is a variable assignment.
+
+@item
+@ref{Walking Arrays}, presented a function that walked a multidimensional
+array to print it out.  However, walking an array and processing
+each element is a general-purpose operation.  Generalize the
+@code{walk_array()} function by adding an additional parameter named
+@code{process}.
+
+Then, inside the loop, instead of printing the array element's index and
+value, use the indirect function call syntax (@pxref{Indirect Calls})
+on @code{process}, passing it the index and the value.
+
+When calling @code{walk_array()}, you would pass the name of a
+user-defined function that expects to receive an index and a value,
+and then processes the element.
+
+Test your new version by printing the array; you should end up with
+output identical to that of the original version.
+
+@end enumerate
+
 @c ENDOFRANGE flib
 @c ENDOFRANGE fudlib
 @c ENDOFRANGE datagr
@@ -20564,11 +21857,13 @@ the element.
 @c STARTOFRANGE awkpex
 @cindex @command{awk} programs, examples of
 
+@c FULLXREF ON
 @ref{Library Functions},
 presents the idea that reading programs in a language contributes to
 learning that language.  This @value{CHAPTER} continues that theme,
 presenting a potpourri of @command{awk} programs for your reading
 enjoyment.
+@c FULLXREF OFF
 @ifnotinfo
 There are three sections.
 The first describes how to run the programs presented
@@ -20595,6 +21890,8 @@ Many of these programs use library functions presented in
 * Running Examples::            How to run these examples.
 * Clones::                      Clones of common utilities.
 * Miscellaneous Programs::      Some interesting @command{awk} programs.
+* Programs Summary::            Summary of programs.
+* Programs Exercises::          Exercises.
 @end menu
 
 @node Running Examples
@@ -20609,7 +21906,7 @@ awk -f @var{program} -- @var{options} @var{files}
 @noindent
 Here, @var{program} is the name of the @command{awk} program (such as
 @file{cut.awk}), @var{options} are any command-line options for the
-program that start with a @samp{-}, and @var{files} are the actual data files.
+program that start with a @samp{-}, and @var{files} are the actual @value{DF}s.
 
 If your system supports the @samp{#!} executable interpreter mechanism
 (@pxref{Executable Scripts}),
@@ -20747,13 +22044,7 @@ function usage(    e1, e2)
 
 @noindent
 The variables @code{e1} and @code{e2} are used so that the function
-fits nicely on the
-@ifnotinfo
-page.
-@end ifnotinfo
-@ifnottex
-screen.
-@end ifnottex
+fits nicely on the @value{PAGE}.
 
 @cindex @code{BEGIN} pattern, running @command{awk} programs and
 @cindex @code{FS} variable, running @command{awk} programs and
@@ -20783,7 +22074,7 @@ BEGIN    \
             OFS = ""
         @} else if (c == "d") @{
             if (length(Optarg) > 1) @{
-                printf("Using first character of %s" \
+                printf("cut: using first character of %s" \
                        " for delimiter\n", Optarg) > "/dev/stderr"
                 Optarg = substr(Optarg, 1, 1)
             @}
@@ -20792,7 +22083,7 @@ BEGIN    \
             if (FS == " ")    # defeat awk semantics
                 FS = "[ ]"
         @} else if (c == "s")
-            suppress++
+            suppress = 1
         else
             usage()
     @}
@@ -20814,7 +22105,7 @@ spaces.  Also remember that after @code{getopt()} is through
 we have to
 clear out all the elements of @code{ARGV} from 1 to @code{Optind},
 so that @command{awk} does not try to process the command-line options
-as file names.
+as @value{FN}s.
 
 After dealing with the command-line options, the program verifies that the
 options make sense.  Only one or the other of @option{-c} and @option{-f}
@@ -20864,7 +22155,7 @@ function set_fieldlist(        n, m, i, j, k, f, g)
             m = split(f[i], g, "-")
 @group
             if (m != 2 || g[1] >= g[2]) @{
-                printf("bad field list: %s\n",
+                printf("cut: bad field list: %s\n",
                                   f[i]) > "/dev/stderr"
                 exit 1
             @}
@@ -20901,7 +22192,7 @@ complete field list, including filler fields:
 
 @example
 @c file eg/prog/cut.awk
-function set_charlist(    field, i, j, f, g, t,
+function set_charlist(    field, i, j, f, g, n, m, t,
                           filler, last, len)
 @{
     field = 1   # count total fields
@@ -20911,7 +22202,7 @@ function set_charlist(    field, i, j, f, g, t,
         if (index(f[i], "-") != 0) @{ # range
             m = split(f[i], g, "-")
             if (m != 2 || g[1] >= g[2]) @{
-                printf("bad character list: %s\n",
+                printf("cut: bad character list: %s\n",
                                f[i]) > "/dev/stderr"
                 exit 1
             @}
@@ -20987,7 +22278,6 @@ of picking the input line apart by characters.
 @c ENDOFRANGE ficut
 @c ENDOFRANGE colcut
 
-@c Exercise: Rewrite using split with "".
 
 @node Egrep Program
 @subsection Searching for Regular Expressions in Files
@@ -20998,20 +22288,21 @@ of picking the input line apart by characters.
 @cindex searching, files for regular expressions
 @c STARTOFRANGE fsregexp
 @cindex files, searching for regular expressions
+@c STARTOFRANGE egrep
 @cindex @command{egrep} utility
 The @command{egrep} utility searches files for patterns.  It uses regular
 expressions that are almost identical to those available in @command{awk}
 (@pxref{Regexp}).
 You invoke it as follows:
 
-@example
-egrep @r{[} @var{options} @r{]} '@var{pattern}' @var{files} @dots{}
-@end example
+@display
+@command{egrep} [@var{options}] @code{'@var{pattern}'} @var{files} @dots{}
+@end display
 
 The @var{pattern} is a regular expression.  In typical usage, the regular
 expression is quoted to prevent the shell from expanding any of the
-special characters as file name wildcards.  Normally, @command{egrep}
-prints the lines that matched.  If multiple file names are provided on
+special characters as @value{FN} wildcards.  Normally, @command{egrep}
+prints the lines that matched.  If multiple @value{FN}s are provided on
 the command line, each output line is preceded by the name of the file
 and a colon.
 
@@ -21102,7 +22393,7 @@ pattern is supplied with @option{-e}, the first nonoption on the
 command line is used.  The @command{awk} command-line arguments up to @code{ARGV[Optind]}
 are cleared, so that @command{awk} won't try to process them as files.  If no
 files are specified, the standard input is used, and if multiple files are
-specified, we make sure to note this so that the file names can precede the
+specified, we make sure to note this so that the @value{FN}s can precede the
 matched lines in the output:
 
 @example
@@ -21136,8 +22427,6 @@ if a match happens, we output the translated line, not the original.}
 The rule is
 commented out since it is not necessary with @command{gawk}:
 
-@c Exercise: Fix this, w/array and new line as key to original line
-
 @example
 @c file eg/prog/egrep.awk
 #@{
@@ -21188,6 +22477,11 @@ function endfile(file)
 @c endfile
 @end example
 
+The @code{BEGINFILE} and @code{ENDFILE} special patterns
+(@pxref{BEGINFILE/ENDFILE}) could be used, but then the program would be
+@command{gawk}-specific. Additionally, this example was written before
+@command{gawk} acquired @code{BEGINFILE} and @code{ENDFILE}.
+
 The following rule does most of the work of matching lines. The variable
 @code{matches} is true if the line matched the pattern. If the user
 wants lines that did not match, the sense of @code{matches} is inverted
@@ -21200,9 +22494,9 @@ A number of additional tests are made, but they are only done if we
 are not counting lines.  First, if the user only wants exit status
 (@code{no_print} is true), then it is enough to know that @emph{one}
 line in this file matched, and we can skip on to the next file with
-@code{nextfile}.  Similarly, if we are only printing file names, we can
-print the file name, and then skip to the next file with @code{nextfile}.
-Finally, each line is printed, with a leading file name and colon
+@code{nextfile}.  Similarly, if we are only printing @value{FN}s, we can
+print the @value{FN}, and then skip to the next file with @code{nextfile}.
+Finally, each line is printed, with a leading @value{FN} and colon
 if necessary:
 
 @cindex @code{!} (exclamation point), @code{!} operator
@@ -21244,9 +22538,7 @@ there are no matches, the exit status is one; otherwise it is zero:
 @c file eg/prog/egrep.awk
 END    \
 @{
-    if (total == 0)
-        exit 1
-    exit 0
+    exit (total == 0)
 @}
 @c endfile
 @end example
@@ -21283,12 +22575,14 @@ or not.
 @c ENDOFRANGE regexps
 @c ENDOFRANGE sfregexp
 @c ENDOFRANGE fsregexp
+@c ENDOFRANGE egrep
 
 @node Id Program
 @subsection Printing out User Information
 
 @cindex printing, user information
 @cindex users, information about, printing
+@c STARTOFRANGE id
 @cindex @command{id} utility
 The @command{id} utility lists a user's real and effective user ID numbers,
 real and effective group ID numbers, and the user's group set, if any.
@@ -21298,10 +22592,10 @@ corresponding user and group names.  The output might look like this:
 
 @example
 $ @kbd{id}
-@print{} uid=500(arnold) gid=500(arnold) groups=6(disk),7(lp),19(floppy)
+@print{} uid=1000(arnold) gid=1000(arnold) groups=1000(arnold),4(adm),7(lp),27(sudo)
 @end example
 
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, and user and group ID numbers
 This information is part of what is provided by @command{gawk}'s
 @code{PROCINFO} array (@pxref{Built-in Variables}).
 However, the @command{id} utility provides a more palatable output than just
@@ -21334,6 +22628,7 @@ numbers:
 # Arnold Robbins, arnold@@skeeve.com, Public Domain
 # May 1993
 # Revised February 1996
+# Revised May 2014
 
 @c endfile
 @end ignore
@@ -21353,34 +22648,26 @@ BEGIN    \
 
     printf("uid=%d", uid)
     pw = getpwuid(uid)
-    if (pw != "") @{
-        split(pw, a, ":")
-        printf("(%s)", a[1])
-    @}
+    if (pw != "")
+        pr_first_field(pw)
 
     if (euid != uid) @{
         printf(" euid=%d", euid)
         pw = getpwuid(euid)
-        if (pw != "") @{
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        @}
+        if (pw != "")
+            pr_first_field(pw)
     @}
 
     printf(" gid=%d", gid)
     pw = getgrgid(gid)
-    if (pw != "") @{
-        split(pw, a, ":")
-        printf("(%s)", a[1])
-    @}
+    if (pw != "")
+        pr_first_field(pw)
 
     if (egid != gid) @{
         printf(" egid=%d", egid)
         pw = getgrgid(egid)
-        if (pw != "") @{
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        @}
+        if (pw != "")
+            pr_first_field(pw)
     @}
 
     for (i = 1; ("group" i) in PROCINFO; i++) @{
@@ -21389,20 +22676,23 @@ BEGIN    \
         group = PROCINFO["group" i]
         printf("%d", group)
         pw = getgrgid(group)
-        if (pw != "") @{
-            split(pw, a, ":")
-            printf("(%s)", a[1])
-        @}
+        if (pw != "")
+            pr_first_field(pw)
         if (("group" (i+1)) in PROCINFO)
             printf(",")
     @}
 
     print ""
 @}
+
+function pr_first_field(str,  a)
+@{
+    split(str, a, ":")
+    printf("(%s)", a[1])
+@}
 @c endfile
 @end example
 
-@cindex @code{in} operator
 The test in the @code{for} loop is worth noting.
 Any supplementary groups in the @code{PROCINFO} array have the
 indices @code{"group1"} through @code{"group@var{N}"} for some
@@ -21412,19 +22702,18 @@ there are.
 
 This loop works by starting at one, concatenating the value with
 @code{"group"}, and then using @code{in} to see if that value is
-in the array.  Eventually, @code{i} is incremented past
+in the array (@pxref{Reference to Elements}).  Eventually, @code{i} is incremented past
 the last group in the array and the loop exits.
 
 The loop is also correct if there are @emph{no} supplementary
 groups; then the condition is false the first time it's
 tested, and the loop body never executes.
 
-@c exercise!!!
-@ignore
-The POSIX version of @command{id} takes arguments that control which
-information is printed.  Modify this version to accept the same
-arguments and perform in the same way.
-@end ignore
+The @code{pr_first_field()} function simply isolates out some
+code that is used repeatedly, making the whole program
+slightly shorter and cleaner.
+
+@c ENDOFRANGE id
 
 @node Split Program
 @subsection Splitting a Large File into Pieces
@@ -21433,15 +22722,16 @@ arguments and perform in the same way.
 
 @c STARTOFRANGE filspl
 @cindex files, splitting
+@c STARTOFRANGE split
 @cindex @code{split} utility
 The @command{split} program splits large text files into smaller pieces.
 Usage is as follows:@footnote{This is the traditional usage. The
 POSIX usage is different, but not relevant for what the program
 aims to demonstrate.}
 
-@example
-split @r{[}-@var{count}@r{]} file @r{[} @var{prefix} @r{]}
-@end example
+@display
+@command{split} [@code{-@var{count}}] [@var{file}] [@var{prefix}]
+@end display
 
 By default,
 the output files are named @file{xaa}, @file{xab}, and so on. Each file has
@@ -21450,7 +22740,7 @@ number of lines in each file, supply a number on the command line
 preceded with a minus; e.g., @samp{-500} for files with 500 lines in them
 instead of 1000.  To change the name of the output files to something like
 @file{myfileaa}, @file{myfileab}, and so on, supply an additional
-argument that specifies the file name prefix.
+argument that specifies the @value{FN} prefix.
 
 Here is a version of @command{split} in @command{awk}. It uses the
 @code{ord()} and @code{chr()} functions presented in
@@ -21460,8 +22750,8 @@ The program first sets its defaults, and then tests to make sure there are
 not too many arguments.  It then looks at each argument in turn.  The
 first argument could be a minus sign followed by a number. If it is, this happens
 to look like a negative number, so it is made positive, and that is the
-count of lines.  The data file name is skipped over and the final argument
-is used as the prefix for the output file names:
+count of lines.  The @value{DF} name is skipped over and the final argument
+is used as the prefix for the output @value{FN}s:
 
 @cindex @code{split.awk} program
 @example
@@ -21475,11 +22765,12 @@ is used as the prefix for the output file names:
 #
 # Arnold Robbins, arnold@@skeeve.com, Public Domain
 # May 1993
+# Revised slightly, May 2014
 
 @c endfile
 @end ignore
 @c file eg/prog/split.awk
-# usage: split [-num] [file] [outname]
+# usage: split [-count] [file] [outname]
 
 BEGIN @{
     outfile = "x"    # default
@@ -21488,7 +22779,7 @@ BEGIN @{
         usage()
 
     i = 1
-    if (ARGV[i] ~ /^-[[:digit:]]+$/) @{
+    if (i in ARGV && ARGV[i] ~ /^-[[:digit:]]+$/) @{
         count = -ARGV[i]
         ARGV[i] = ""
         i++
@@ -21510,7 +22801,7 @@ BEGIN @{
 The next rule does most of the work. @code{tcount} (temporary count) tracks
 how many lines have been printed to the output file so far. If it is greater
 than @code{count}, it is time to close the current file and start a new one.
-@code{s1} and @code{s2} track the current suffixes for the file name. If
+@code{s1} and @code{s2} track the current suffixes for the @value{FN}. If
 they are both @samp{z}, the file is just too big.  Otherwise, @code{s1}
 moves to the next letter in the alphabet and @code{s2} starts over again at
 @samp{a}:
@@ -21542,8 +22833,6 @@ moves to the next letter in the alphabet and @code{s2} starts over again at
 @c endfile
 @end example
 
-@c Exercise: do this with just awk builtin functions, index("abc..."), substr, etc.
-
 @noindent
 The @code{usage()} function simply prints an error message and exits:
 
@@ -21560,36 +22849,30 @@ function usage(   e)
 
 @noindent
 The variable @code{e} is used so that the function
-fits nicely on the
-@ifinfo
-screen.
-@end ifinfo
-@ifnotinfo
-page.
-@end ifnotinfo
+fits nicely on the @value{PAGE}.
 
 This program is a bit sloppy; it relies on @command{awk} to automatically close the last file
 instead of doing it in an @code{END} rule.
 It also assumes that letters are contiguous in the character set,
 which isn't true for EBCDIC systems.
 
-@c Exercise: Fix these problems.
-@c BFD...
 @c ENDOFRANGE filspl
+@c ENDOFRANGE split
 
 @node Tee Program
 @subsection Duplicating Output into Multiple Files
 
 @cindex files, multiple@comma{} duplicating output into
 @cindex output, duplicating into files
+@c STARTOFRANGE tee
 @cindex @code{tee} utility
 The @code{tee} program is known as a ``pipe fitting.''  @code{tee} copies
 its standard input to its standard output and also duplicates it to the
 files named on the command line.  Its usage is as follows:
 
-@example
-tee @r{[}-a@r{]} file @dots{}
-@end example
+@display
+@command{tee} [@option{-a}] @var{file} @dots{}
+@end display
 
 The @option{-a} option tells @code{tee} to append to the named files, instead of
 truncating them and starting over.
@@ -21598,13 +22881,13 @@ The @code{BEGIN} rule first makes a copy of all the command-line arguments
 into an array named @code{copy}.
 @code{ARGV[0]} is not copied, since it is not needed.
 @code{tee} cannot use @code{ARGV} directly, since @command{awk} attempts to
-process each file name in @code{ARGV} as input data.
+process each @value{FN} in @code{ARGV} as input data.
 
 @cindex flag variables
 If the first argument is @option{-a}, then the flag variable
 @code{append} is set to true, and both @code{ARGV[1]} and
 @code{copy[1]} are deleted. If @code{ARGC} is less than two, then no
-file names were supplied and @code{tee} prints a usage message and exits.
+@value{FN}s were supplied and @code{tee} prints a usage message and exits.
 Finally, @command{awk} is forced to read the standard input by setting
 @code{ARGV[1]} to @code{"-"} and @code{ARGC} to two:
 
@@ -21696,6 +22979,7 @@ END    \
 @}
 @c endfile
 @end example
+@c ENDOFRANGE tee
 
 @node Uniq Program
 @subsection Printing Nonduplicated Lines of Text
@@ -21706,15 +22990,16 @@ END    \
 @cindex printing, unduplicated lines of text
 @c STARTOFRANGE tpul
 @cindex text@comma{} printing, unduplicated lines of
+@c STARTOFRANGE uniq
 @cindex @command{uniq} utility
 The @command{uniq} utility reads sorted lines of data on its standard
 input, and by default removes duplicate lines.  In other words, it only
 prints unique lines---hence the name.  @command{uniq} has a number of
 options. The usage is as follows:
 
-@example
-uniq @r{[}-udc @r{[}-@var{n}@r{]]} @r{[}+@var{n}@r{]} @r{[} @var{input file} @r{[} @var{output file} @r{]]}
-@end example
+@display
+@command{uniq} [@option{-udc} [@code{-@var{n}}]] [@code{+@var{n}}] [@var{inputfile} [@var{outputfile}]]
+@end display
 
 The options for @command{uniq} are:
 
@@ -21738,11 +23023,11 @@ by runs of spaces and/or TABs.
 Skip @var{n} characters before comparing lines.  Any fields specified with
 @samp{-@var{n}} are skipped first.
 
-@item @var{input file}
+@item @var{inputfile}
 Data is read from the input file named on the command line, instead of from
 the standard input.
 
-@item @var{output file}
+@item @var{outputfile}
 The generated output is sent to the named output file, instead of to the
 standard output.
 @end table
@@ -21957,6 +23242,7 @@ END @{
 @end example
 @c ENDOFRANGE prunt
 @c ENDOFRANGE tpul
+@c ENDOFRANGE uniq
 
 @node Wc Program
 @subsection Counting Things
@@ -21973,13 +23259,14 @@ END @{
 @cindex characters, counting
 @c STARTOFRANGE lico
 @cindex lines, counting
+@c STARTOFRANGE wc
 @cindex @command{wc} utility
 The @command{wc} (word count) utility counts lines, words, and characters in
 one or more input files. Its usage is as follows:
 
-@example
-wc @r{[}-lwc@r{]} @r{[} @var{files} @dots{} @r{]}
-@end example
+@display
+@command{wc} [@option{-lwc}] [@var{files} @dots{}]
+@end display
 
 If no files are specified on the command line, @command{wc} reads its standard
 input. If there are multiple files, it also prints total counts for all
@@ -22066,7 +23353,7 @@ BEGIN @{
 @end example
 
 The @code{beginfile()} function is simple; it just resets the counts of lines,
-words, and characters to zero, and saves the current file name in
+words, and characters to zero, and saves the current @value{FN} in
 @code{fname}:
 
 @example
@@ -22079,18 +23366,10 @@ function beginfile(file)
 @c endfile
 @end example
 
-The @code{endfile()} function adds the current file's numbers to the running
-totals of lines, words, and characters.@footnote{@command{wc} can't just use the value of
-@code{FNR} in @code{endfile()}. If you examine
-the code in
-@ref{Filetrans Function},
-you will see that
-@code{FNR} has already been reset by the time
-@code{endfile()} is called.}  It then prints out those numbers
-for the file that was just read. It relies on @code{beginfile()} to reset the
-numbers for the following data file:
-@c FIXME: ONE DAY: make the above footnote an exercise,
-@c instead of giving away the answer.
+The @code{endfile()} function adds the current file's numbers to the
+running totals of lines, words, and characters.  It then prints out those
+numbers for the file that was just read. It relies on @code{beginfile()}
+to reset the numbers for the following @value{DF}:
 
 @example
 @c file eg/prog/wc.awk
@@ -22155,6 +23434,7 @@ END @{
 @c ENDOFRANGE lico
 @c ENDOFRANGE woco
 @c ENDOFRANGE chco
+@c ENDOFRANGE wc
 @c ENDOFRANGE posimawk
 
 @node Miscellaneous Programs
@@ -22259,6 +23539,32 @@ word, comparing it to the previous one:
 @i{Nothing cures insomnia like a ringing alarm clock.}
 @author Arnold Robbins
 @end quotation
+@cindex Quanstrom, Erik
+@ignore
+Date: Sat, 15 Feb 2014 16:47:09 -0500
+Subject: Re: 9atom install question
+Message-ID: <l2jcvx6j6mey60xnrkb0hhob.1392500829294@email.android.com>
+From: Erik Quanstrom <quanstro@quanstro.net>
+To: Aharon Robbins <arnold@skeeve.com>
+
+yes.
+
+- erik
+
+Aharon Robbins <arnold@skeeve.com> wrote:
+
+>> sleep is for web developers.
+>
+>Can I quote you, in the gawk manual?
+>
+>Thanks,
+>
+>Arnold
+@end ignore
+@quotation
+@i{Sleep is for web developers.}
+@author Erik Quanstrom
+@end quotation
 
 @c STARTOFRANGE tialarm
 @cindex time, alarm clock example program
@@ -22380,7 +23686,7 @@ is how long to wait before setting off the alarm:
     # how long to sleep for
     naptime = target - current
     if (naptime <= 0) @{
-        print "time is in the past!" > "/dev/stderr"
+        print "alarm: time is in the past!" > "/dev/stderr"
         exit 1
     @}
 @c endfile
@@ -22423,6 +23729,7 @@ seconds are necessary:
 
 @c STARTOFRANGE chtra
 @cindex characters, transliterating
+@c STARTOFRANGE tr
 @cindex @command{tr} utility
 The system @command{tr} utility transliterates characters.  For example, it is
 often used to map uppercase letters into lowercase for further processing:
@@ -22432,19 +23739,18 @@ often used to map uppercase letters into lowercase for further processing:
 @end example
 
 @command{tr} requires two lists of characters.@footnote{On some older
-systems,
-including Solaris,
-@command{tr} may require that the lists be written as
-range expressions enclosed in square brackets (@samp{[a-z]}) and quoted,
-to prevent the shell from attempting a file name expansion.  This is
-not a feature.}  When processing the input, the first character in the
-first list is replaced with the first character in the second list,
-the second character in the first list is replaced with the second
-character in the second list, and so on.  If there are more characters
-in the ``from'' list than in the ``to'' list, the last character of the
-``to'' list is used for the remaining characters in the ``from'' list.
-
-Some time ago,
+systems, including Solaris, the system version of @command{tr} may require
+that the lists be written as range expressions enclosed in square brackets
+(@samp{[a-z]}) and quoted, to prevent the shell from attempting a file
+name expansion.  This is not a feature.}  When processing the input, the
+first character in the first list is replaced with the first character
+in the second list, the second character in the first list is replaced
+with the second character in the second list, and so on.  If there are
+more characters in the ``from'' list than in the ``to'' list, the last
+character of the ``to'' list is used for the remaining characters in the
+``from'' list.
+
+Once upon a time,
 @c early or mid-1989!
 a user proposed that a transliteration function should
 be added to @command{gawk}.
@@ -22462,7 +23768,6 @@ and @code{gsub()} built-in functions
 (@pxref{String Functions}).@footnote{This
 program was written before @command{gawk} acquired the ability to
 split each character in a string into separate array elements.}
-@c Exercise: How might you use this new feature to simplify the program?
 There are two functions.  The first, @code{stranslate()}, takes three
 arguments:
 
@@ -22558,19 +23863,19 @@ BEGIN @{
 While it is possible to do character transliteration in a user-level
 function, it is not necessarily efficient, and we (the @command{gawk}
 authors) started to consider adding a built-in function.  However,
-shortly after writing this program, we learned that the System V Release 4
-@command{awk} had added the @code{toupper()} and @code{tolower()} functions
-(@pxref{String Functions}).
-These functions handle the vast majority of the
-cases where character transliteration is necessary, and so we chose to
-simply add those functions to @command{gawk} as well and then leave well
-enough alone.
+shortly after writing this program, we learned that Brian Kernighan
+had added the @code{toupper()} and @code{tolower()} functions to his
+@command{awk} (@pxref{String Functions}).  These functions handle the
+vast majority of the cases where character transliteration is necessary,
+and so we chose to simply add those functions to @command{gawk} as well
+and then leave well enough alone.
 
 An obvious improvement to this program would be to set up the
 @code{t_ar} array only once, in a @code{BEGIN} rule. However, this
 assumes that the ``from'' and ``to'' lists
 will never change throughout the lifetime of the program.
 @c ENDOFRANGE chtra
+@c ENDOFRANGE tr
 
 @node Labels Program
 @subsection Printing Mailing Labels
@@ -22596,7 +23901,18 @@ The @code{BEGIN} rule simply sets @code{RS} to the empty string, so that
 @command{awk} splits records at blank lines
 (@pxref{Records}).
 It sets @code{MAXLINES} to 100, since 100 is the maximum number
-of lines on the page (20 * 5 = 100).
+of lines on the page
+@iftex
+(@math{20 @cdot 5 = 100}).
+@end iftex
+@ifnottex
+@ifnotdocbook
+(20 * 5 = 100).
+@end ifnotdocbook
+@end ifnottex
+@docbook
+(20 &sdot; 5 = 100). @c
+@end docbook
 
 Most of the work is done in the @code{printpage()} function.
 The label lines are stored sequentially in the @code{line} array.  But they
@@ -22630,6 +23946,7 @@ that there are two blank lines at the top and two blank lines at the bottom.
 The @code{END} rule arranges to flush the final page of labels; there may
 not have been an even multiple of 20 labels in the data:
 
+@c STARTOFRANGE labels
 @cindex @code{labels.awk} program
 @example
 @c file eg/prog/labels.awk
@@ -22697,6 +24014,7 @@ END    \
 @end example
 @c ENDOFRANGE prml
 @c ENDOFRANGE mlprint
+@c ENDOFRANGE labels
 
 @node Word Sorting
 @subsection Generating Word-Usage Counts
@@ -22706,7 +24024,7 @@ END    \
 
 When working with large amounts of text, it can be interesting to know
 how often different words appear.  For example, an author may overuse
-certain words, in which case she might wish to find synonyms to substitute
+certain words, in which case he or she might wish to find synonyms to substitute
 for words that appear too often. This @value{SUBSECTION} develops a
 program for counting words and presenting the frequency information
 in a useful format.
@@ -22736,7 +24054,7 @@ it prints the counts.
 This program has several problems that prevent it from being
 useful on real text files:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @command{awk} language considers upper- and lowercase characters to be
 distinct.  Therefore, ``bartender'' and ``Bartender'' are not treated
@@ -22763,6 +24081,7 @@ to remove punctuation characters.  Finally, we solve the third problem
 by using the system @command{sort} utility to process the output of the
 @command{awk} script.  Here is the new version of the program:
 
+@c STARTOFRANGE wordfreq
 @cindex @code{wordfreq.awk} program
 @example
 @c file eg/prog/wordfreq.awk
@@ -22783,6 +24102,10 @@ END @{
 @}
 @end example
 
+The regexp @samp{/[^[:alnum:]_[:blank:]]/} might have been written
+@samp{/[[:punct:]]/}, but then underscores would also be removed,
+and we want to keep them.
+
 Assuming we have saved this program in a file named @file{wordfreq.awk},
 and that the data is in @file{file1}, the following pipeline:
 
@@ -22824,6 +24147,7 @@ have true pipes at the command-line (or batch-file) level.
 See the general operating system documentation for more information on how
 to use the @command{sort} program.
 @c ENDOFRANGE worus
+@c ENDOFRANGE wordfreq
 
 @node History Sorting
 @subsection Removing Duplicates from Unsorted Text
@@ -22834,7 +24158,7 @@ The @command{uniq} program
 (@pxref{Uniq Program}),
 removes duplicate lines from @emph{sorted} data.
 
-Suppose, however, you need to remove duplicate lines from a data file but
+Suppose, however, you need to remove duplicate lines from a @value{DF} but
 that you want to preserve the order the lines are in.  A good example of
 this might be a shell history file.  The history file keeps a copy of all
 the commands you have entered, and it is not unusual to repeat a command
@@ -22853,6 +24177,7 @@ Each element of @code{lines} is a unique command, and the indices of
 The @code{END} rule simply prints out the lines, in order:
 
 @cindex Rakitzis, Byron
+@c STARTOFRANGE histsort
 @cindex @code{histsort.awk} program
 @example
 @c file eg/prog/histsort.awk
@@ -22892,9 +24217,11 @@ information.  For example, using the following @code{print} statement in the
 print data[lines[i]], lines[i]
 @end example
 
+@noindent
 This works because @code{data[$0]} is incremented each time a line is
 seen.
 @c ENDOFRANGE lidu
+@c ENDOFRANGE histsort
 
 @node Extract Program
 @subsection Extracting Programs from Texinfo Source Files
@@ -22926,7 +24253,8 @@ printed and online documentation.
 @ifnotinfo
 Texinfo is fully documented in the book
 @cite{Texinfo---The GNU Documentation Format},
-available from the Free Software Foundation.
+available from the Free Software Foundation,
+and also available @uref{http://www.gnu.org/software/texinfo/manual/texinfo/, online}.
 @end ifnotinfo
 @ifinfo
 The Texinfo language is described fully, starting with
@@ -22936,7 +24264,7 @@ The Texinfo language is described fully, starting with
 For our purposes, it is enough to know three things about Texinfo input
 files:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The ``at'' symbol (@samp{@@}) is special in Texinfo, much as
 the backslash (@samp{\}) is in C
@@ -23004,6 +24332,7 @@ The first rule handles calling @code{system()}, checking that a command is
 given (@code{NF} is at least three) and also checking that the command
 exits with a zero exit status, signifying OK:
 
+@c STARTOFRANGE extract
 @cindex @code{extract.awk} program
 @example
 @c file eg/prog/extract.awk
@@ -23025,7 +24354,7 @@ BEGIN    @{ IGNORECASE = 1 @}
 /^@@c(omment)?[ \t]+system/    \
 @{
     if (NF < 3) @{
-        e = (FILENAME ":" FNR)
+        e = ("extract: " FILENAME ":" FNR)
         e = (e  ": badly formed `system' line")
         print e > "/dev/stderr"
         next
@@ -23034,7 +24363,7 @@ BEGIN    @{ IGNORECASE = 1 @}
     $2 = ""
     stat = system($0)
     if (stat != 0) @{
-        e = (FILENAME ":" FNR)
+        e = ("extract: " FILENAME ":" FNR)
         e = (e ": warning: system returned " stat)
         print e > "/dev/stderr"
     @}
@@ -23044,16 +24373,10 @@ BEGIN    @{ IGNORECASE = 1 @}
 
 @noindent
 The variable @code{e} is used so that the rule
-fits nicely on the
-@ifnotinfo
-page.
-@end ifnotinfo
-@ifnottex
-screen.
-@end ifnottex
+fits nicely on the @value{PAGE}.
 
 The second rule handles moving data into files.  It verifies that a
-file name is given in the directive.  If the file named is not the
+@value{FN} is given in the directive.  If the file named is not the
 current file, then the current file is closed.  Keeping the current file
 open until a new file is encountered allows the use of the @samp{>}
 redirection for printing the contents, keeping open file management
@@ -23077,12 +24400,11 @@ the array @code{a}, using the @code{split()} function
 The @samp{@@} symbol is used as the separator character.
 Each element of @code{a} that is empty indicates two successive @samp{@@}
 symbols in the original line.  For each two empty elements (@samp{@@@@} in
-the original file), we have to add a single @samp{@@} symbol back
-in.@footnote{This program was written before @command{gawk} had the
-@code{gensub()} function. Consider how you might use it to simplify the code.}
+the original file), we have to add a single @samp{@@} symbol back in.
 
 When the processing of the array is finished, @code{join()} is called with the
-value of @code{SUBSEP}, to rejoin the pieces back into a single
+value of @code{SUBSEP} (@pxref{Multidimensional}),
+to rejoin the pieces back into a single
 line.  That line is then printed to the output file:
 
 @example
@@ -23090,7 +24412,7 @@ line.  That line is then printed to the output file:
 /^@@c(omment)?[ \t]+file/    \
 @{
     if (NF != 3) @{
-        e = (FILENAME ":" FNR ": badly formed `file' line")
+        e = ("extract: " FILENAME ":" FNR ": badly formed `file' line")
         print e > "/dev/stderr"
         next
     @}
@@ -23135,20 +24457,19 @@ subsequent output is appended to the file
 (@pxref{Redirection}).
 This makes it easy to mix program text and explanatory prose for the same
 sample source file (as has been done here!) without any hassle.  The file is
-only closed when a new data file name is encountered or at the end of the
+only closed when a new @value{DF} name is encountered or at the end of the
 input file.
 
 Finally, the function @code{@w{unexpected_eof()}} prints an appropriate
 error message and then exits.
 The @code{END} rule handles the final cleanup, closing the open file:
 
-@c function lb put on same line for page breaking. sigh
 @example
 @c file eg/prog/extract.awk
 @group
 function unexpected_eof()
 @{
-    printf("%s:%d: unexpected EOF or error\n",
+    printf("extract: %s:%d: unexpected EOF or error\n",
         FILENAME, FNR) > "/dev/stderr"
     exit 1
 @}
@@ -23162,6 +24483,7 @@ END @{
 @end example
 @c ENDOFRANGE texse
 @c ENDOFRANGE fitex
+@c ENDOFRANGE extract
 
 @node Simple Sed
 @subsection A Simple Stream Editor
@@ -23187,10 +24509,11 @@ Here, @samp{s/old/new/g} tells @command{sed} to look for the regexp
 
 The following program, @file{awksed.awk}, accepts at least two command-line
 arguments: the pattern to look for and the text to replace it with. Any
-additional arguments are treated as data file names to process. If none
+additional arguments are treated as @value{DF} names to process. If none
 are provided, the standard input is used:
 
 @cindex Brennan, Michael
+@c STARTOFRANGE awksed
 @cindex @command{awksed.awk} program
 @c @cindex simple stream editor
 @c @cindex stream editor, simple
@@ -23260,33 +24583,14 @@ The @code{BEGIN} rule handles the setup, checking for the right number
 of arguments and calling @code{usage()} if there is a problem. Then it sets
 @code{RS} and @code{ORS} from the command-line arguments and sets
 @code{ARGV[1]} and @code{ARGV[2]} to the null string, so that they are
-not treated as file names
+not treated as @value{FN}s
 (@pxref{ARGC and ARGV}).
 
 The @code{usage()} function prints an error message and exits.
 Finally, the single rule handles the printing scheme outlined above,
 using @code{print} or @code{printf} as appropriate, depending upon the
 value of @code{RT}.
-
-@ignore
-Exercise, compare the performance of this version with the more
-straightforward:
-
-BEGIN {
-    pat = ARGV[1]
-    repl = ARGV[2]
-    ARGV[1] = ARGV[2] = ""
-}
-
-{ gsub(pat, repl); print }
-
-Exercise: what are the advantages and disadvantages of this version versus sed?
-  Advantage: egrep regexps
-             speed (?)
-  Disadvantage: no & in replacement text
-
-Others?
-@end ignore
+@c ENDOFRANGE awksed
 
 @node Igawk Program
 @subsection An Easy Way to Use Library Functions
@@ -23328,7 +24632,7 @@ BEGIN @{
 The following program, @file{igawk.sh}, provides this service.
 It simulates @command{gawk}'s searching of the @env{AWKPATH} variable
 and also allows @dfn{nested} includes; i.e., a file that is included
-with @samp{@@include} can contain further @samp{@@include} statements.
+with @code{@@include} can contain further @code{@@include} statements.
 @command{igawk} makes an effort to only include files once, so that nested
 includes don't accidentally include a library function twice.
 
@@ -23358,7 +24662,7 @@ Literal text, provided with @option{--source} or @option{--source=}.  This
 text is just appended directly.
 
 @item
-Source file names, provided with @option{-f}.  We use a neat trick and append
+Source @value{FN}s, provided with @option{-f}.  We use a neat trick and append
 @samp{@@include @var{filename}} to the shell variable's contents.  Since the file-inclusion
 program works the way @command{gawk} does, this gets the text
 of the file included into the program at the correct point.
@@ -23366,12 +24670,12 @@ of the file included into the program at the correct point.
 
 @item
 Run an @command{awk} program (naturally) over the shell variable's contents to expand
-@samp{@@include} statements.  The expanded program is placed in a second
+@code{@@include} statements.  The expanded program is placed in a second
 shell variable.
 
 @item
 Run the expanded program with @command{gawk} and any other original command-line
-arguments that the user supplied (such as the data file names).
+arguments that the user supplied (such as the @value{DF} names).
 @end enumerate
 
 This program uses shell variables extensively: for storing command-line arguments,
@@ -23386,24 +24690,25 @@ argument is @samp{debug}.
 The next part loops through all the command-line arguments.
 There are several cases of interest:
 
-@table @code
-@item --
+@c @asis for docbook
+@table @asis
+@item @option{--}
 This ends the arguments to @command{igawk}.  Anything else should be passed on
 to the user's @command{awk} program without being evaluated.
 
-@item -W
+@item @option{-W}
 This indicates that the next option is specific to @command{gawk}.  To make
 argument processing easier, the @option{-W} is appended to the front of the
 remaining arguments and the loop continues.  (This is an @command{sh}
 programming trick.  Don't worry about it if you are not familiar with
 @command{sh}.)
 
-@item -v@r{,} -F
+@item @option{-v}, @option{-F}
 These are saved and passed on to @command{gawk}.
 
-@item -f@r{,} --file@r{,} --file=@r{,} -Wfile=
-The file name is appended to the shell variable @code{program} with an
-@samp{@@include} statement.
+@item @option{-f}, @option{--file}, @option{--file=}, @option{-Wfile=}
+The @value{FN} is appended to the shell variable @code{program} with an
+@code{@@include} statement.
 The @command{expr} utility is used to remove the leading option part of the
 argument (e.g., @samp{--file=}).
 (Typical @command{sh} usage would be to use the @command{echo} and @command{sed}
@@ -23411,10 +24716,10 @@ utilities to do this work.  Unfortunately, some versions of @command{echo} evalu
 escape sequences in their arguments, possibly mangling the program text.
 Using @command{expr} avoids this problem.)
 
-@item --source@r{,} --source=@r{,} -Wsource=
+@item @option{--source}, @option{--source=}, @option{-Wsource=}
 The source text is appended to @code{program}.
 
-@item --version@r{,} -Wversion
+@item @option{--version}, @option{-Wversion}
 @command{igawk} prints its version number, runs @samp{gawk --version}
 to get the @command{gawk} version information, and then exits.
 @end table
@@ -23430,6 +24735,7 @@ program.
 
 The program is as follows:
 
+@c STARTOFRANGE igawk
 @cindex @code{igawk.sh} program
 @example
 @c file eg/prog/igawk.sh
@@ -23521,15 +24827,15 @@ fi
 @c endfile
 @end example
 
-The @command{awk} program to process @samp{@@include} directives
+The @command{awk} program to process @code{@@include} directives
 is stored in the shell variable @code{expand_prog}.  Doing this keeps
 the shell script readable.  The @command{awk} program
 reads through the user's program, one line at a time, using @code{getline}
 (@pxref{Getline}).  The input
-file names and @samp{@@include} statements are managed using a stack.
-As each @samp{@@include} is encountered, the current file name is
-``pushed'' onto the stack and the file named in the @samp{@@include}
-directive becomes the current file name.  As each file is finished,
+@value{FN}s and @code{@@include} statements are managed using a stack.
+As each @code{@@include} is encountered, the current @value{FN} is
+``pushed'' onto the stack and the file named in the @code{@@include}
+directive becomes the current @value{FN}.  As each file is finished,
 the stack is ``popped,'' and the previous input file becomes the current
 input file again.  The process is started by making the original file
 the first one on the stack.
@@ -23538,16 +24844,16 @@ The @code{pathto()} function does the work of finding the full path to
 a file.  It simulates @command{gawk}'s behavior when searching the
 @env{AWKPATH} environment variable
 (@pxref{AWKPATH Variable}).
-If a file name has a @samp{/} in it, no path search is done.
-Similarly, if the file name is @code{"-"}, then that string is
+If a @value{FN} has a @samp{/} in it, no path search is done.
+Similarly, if the @value{FN} is @code{"-"}, then that string is
 used as-is.  Otherwise,
-the file name is concatenated with the name of each directory in
-the path, and an attempt is made to open the generated file name.
+the @value{FN} is concatenated with the name of each directory in
+the path, and an attempt is made to open the generated @value{FN}.
 The only way to test if a file can be read in @command{awk} is to go
 ahead and try to read it with @code{getline}; this is what @code{pathto()}
 does.@footnote{On some very old versions of @command{awk}, the test
 @samp{getline junk < t} can loop forever if the file exists but is empty.
-Caveat emptor.} If the file can be read, it is closed and the file name
+Caveat emptor.} If the file can be read, it is closed and the @value{FN}
 is returned:
 
 @ignore
@@ -23602,17 +24908,17 @@ BEGIN @{
 @c endfile
 @end example
 
-The stack is initialized with @code{ARGV[1]}, which will be @file{/dev/stdin}.
+The stack is initialized with @code{ARGV[1]}, which will be @code{"/dev/stdin"}.
 The main loop comes next.  Input lines are read in succession. Lines that
-do not start with @samp{@@include} are printed verbatim.
-If the line does start with @samp{@@include}, the file name is in @code{$2}.
+do not start with @code{@@include} are printed verbatim.
+If the line does start with @code{@@include}, the @value{FN} is in @code{$2}.
 @code{pathto()} is called to generate the full path.  If it cannot, then the program
 prints an error message and continues.
 
 The next thing to check is if the file is included already.  The
-@code{processed} array is indexed by the full file name of each included
+@code{processed} array is indexed by the full @value{FN} of each included
 file and it tracks this information for us.  If the file is
-seen again, a warning message is printed. Otherwise, the new file name is
+seen again, a warning message is printed. Otherwise, the new @value{FN} is
 pushed onto the stack and processing continues.
 
 Finally, when @code{getline} encounters the end of the input file, the file
@@ -23633,7 +24939,7 @@ the program is done:
             fpath = pathto($2)
 @group
             if (fpath == "") @{
-                printf("igawk:%s:%d: cannot find %s\n",
+                printf("igawk: %s:%d: cannot find %s\n",
                     input[stackptr], FNR, $2) > "/dev/stderr"
                 continue
             @}
@@ -23673,7 +24979,7 @@ It's done in these steps:
 
 @enumerate
 @item
-Run @command{gawk} with the @samp{@@include}-processing program (the
+Run @command{gawk} with the @code{@@include}-processing program (the
 value of the @code{expand_prog} shell variable) on standard input.
 
 @item
@@ -23690,10 +24996,10 @@ options and command-line arguments that the user supplied.
 
 @c this causes more problems than it solves, so leave it out.
 @ignore
-The special file @file{/dev/null} is passed as a data file to @command{gawk}
+The special file @file{/dev/null} is passed as a @value{DF} to @command{gawk}
 to handle an interesting case. Suppose that the user's program only has
-a @code{BEGIN} rule and there are no data files to read.
-The program should exit without reading any data files.
+a @code{BEGIN} rule and there are no @value{DF}s to read.
+The program should exit without reading any @value{DF}s.
 However, suppose that an included library file defines an @code{END}
 rule of its own. In this case, @command{gawk} will hang, reading standard
 input. In order to avoid this, @file{/dev/null} is explicitly added to the
@@ -23712,27 +25018,25 @@ eval gawk $opts -- '"$processed_program"' '"$@@"'
 The @command{eval} command is a shell construct that reruns the shell's parsing
 process.  This keeps things properly quoted.
 
-This version of @command{igawk} represents my fifth version of this program.
+This version of @command{igawk} represents the fifth version of this program.
 There are four key simplifications that make the program work better:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-Using @samp{@@include} even for the files named with @option{-f} makes building
+Using @code{@@include} even for the files named with @option{-f} makes building
 the initial collected @command{awk} program much simpler; all the
-@samp{@@include} processing can be done once.
+@code{@@include} processing can be done once.
 
 @item
 Not trying to save the line read with @code{getline}
 in the @code{pathto()} function when testing for the
 file's accessibility for use with the main program simplifies things
 considerably.
-@c what problem does this engender though - exercise
-@c answer, reading from "-" or /dev/stdin
 
 @item
 Using a @code{getline} loop in the @code{BEGIN} rule does it all in one
 place.  It is not necessary to call out to a separate loop for processing
-nested @samp{@@include} statements.
+nested @code{@@include} statements.
 
 @item
 Instead of saving the expanded program in a temporary file, putting it in a shell variable
@@ -23752,47 +25056,18 @@ Finally, @command{igawk} shows that it is not always necessary to add new
 features to a program; they can often be layered on top.
 @ignore
 With @command{igawk},
-there is no real reason to build @samp{@@include} processing into
+there is no real reason to build @code{@@include} processing into
 @command{gawk} itself.
 @end ignore
-
-@cindex search paths
-@cindex search paths, for source files
-@cindex source files@comma{} search path for
-@cindex files, source@comma{} search path for
-@cindex directories, searching
-As an additional example of this, consider the idea of having two
-files in a directory in the search path:
-
-@table @file
-@item default.awk
-This file contains a set of default library functions, such
-as @code{getopt()} and @code{assert()}.
-
-@item site.awk
-This file contains library functions that are specific to a site or
-installation; i.e., locally developed functions.
-Having a separate file allows @file{default.awk} to change with
-new @command{gawk} releases, without requiring the system administrator to
-update it each time by adding the local functions.
-@end table
-
-One user
-@c Karl Berry, karl@ileaf.com, 10/95
-suggested that @command{gawk} be modified to automatically read these files
-upon startup.  Instead, it would be very simple to modify @command{igawk}
-to do this. Since @command{igawk} can process nested @samp{@@include}
-directives, @file{default.awk} could simply contain @samp{@@include}
-statements for the desired library functions.
-
-@c Exercise: make this change
 @c ENDOFRANGE libfex
 @c ENDOFRANGE flibex
 @c ENDOFRANGE awkpex
+@c ENDOFRANGE igawk
 
 @node Anagram Program
 @subsection Finding Anagrams From A Dictionary
 
+@cindex anagrams, finding
 An interesting programming challenge is to
 search for @dfn{anagrams} in a
 word list (such as
@@ -23812,6 +25087,7 @@ The following program uses arrays of arrays to bring together
 words with the same signature and array sorting to print the words
 in sorted order.
 
+@c STARTOFRANGE anagram
 @cindex @code{anagram.awk} program
 @example
 @c file eg/prog/anagram.awk
@@ -23920,9 +25196,13 @@ babery yabber
 @dots{}
 @end example
 
+@c ENDOFRANGE anagram
+
 @node Signature Program
 @subsection And Now For Something Completely Different
 
+@cindex signature program
+@cindex Brini, Davide
 The following program was written by Davide Brini
 @c (@email{dave_br@@gmx.com})
 and is published on @uref{http://backreference.org/2011/02/03/obfuscated-awk/,
@@ -23947,7 +25227,10 @@ X*(X-x)-o*o,(x+X)*o*o+o,x*(X-x)-O-O,x-O+(O+o+X+x)*(o+O),X*X-X*(x-O)-x+O,
 O+X*(o*(o+O)+O),+x+O+X*o,x*(x-o),(o+X+x)*o*o-(x-O-O),O+(X-x)*(X+O),x-O@}'
 @end example
 
-We leave it to you to determine what the program does.
+@cindex Johansen, Chris
+We leave it to you to determine what the program does.  (If you are
+truly desperate to understand it, see Chris Johansen's explanation,
+which is embedded in the Texinfo source file for this @value{DOCUMENT}.)
 
 @ignore
 To: "Arnold Robbins" <arnold@skeeve.com>
@@ -24027,19 +25310,181 @@ BEGIN {
 }
 @end ignore
 
-@iftex
-@part Part III:@* Moving Beyond Standard @command{awk} With @command{gawk}
-@end iftex
+@node Programs Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+The functions provided in this @value{CHAPTER} and the previous one
+continue on the theme that reading programs is an excellent way to learn
+Good Programming.
+
+@item
+Using @samp{#!} to make @command{awk} programs directly runnable makes
+them easier to use.  Otherwise, invoke the program using @samp{awk
+-f @dots{}}.
+
+@item
+Reimplementing standard POSIX programs in @command{awk} is a pleasant
+exercise; @command{awk}'s expressive power lets you write such programs
+in relatively few lines of code, yet they are functionally complete
+and usable.
+
+@item
+One of standard @command{awk}'s weaknesses is working with individual
+characters.  The ability to use @code{split()} with the empty string as
+the separator can considerably simplify such tasks.
+
+@item
+The library functions from @ref{Library Functions}, proved their
+usefulness for a number of real (if small) programs.
+
+@item
+Besides reinventing POSIX wheels, other programs solved a selection of
+interesting problems, such as finding duplicates words in text, printing
+mailing labels, and finding anagrams.
+
+@end itemize
+
+@node Programs Exercises
+@section Exercises
+
+@enumerate
+@item
+Rewrite @file{cut.awk} (@pxref{Cut Program})
+using @code{split()} with @code{""} as the seperator.
+
+@item
+In @ref{Egrep Program}, we mentioned that @samp{egrep -i} could be
+simulated in versions of @command{awk} without @code{IGNORECASE} by
+using @code{tolower()} on the line and the pattern. In a footnote there,
+we also mentioned that this solution has a bug: the translated line is
+output, and not the original one.  Fix this problem.
+@c Exercise: Fix this, w/array and new line as key to original line
+
+@item
+The POSIX version of @command{id} takes options that control which
+information is printed.  Modify the @command{awk} version
+(@pxref{Id Program}) to accept the same arguments and perform in the
+same way.
+
+@item
+The @code{split.awk} program (@pxref{Split Program}) uses
+the @code{chr()} and @code{ord()} functions to move through the
+letters of the alphabet.
+Modify the program to instead use only the @command{awk}
+built-in functions, such as @code{index()} and @code{substr()}.
+
+@item
+The @code{split.awk} program (@pxref{Split Program}) assumes
+that letters are contiguous in the character set,
+which isn't true for EBCDIC systems.
+Fix this problem.
+
+@item
+Why can't the @file{wc.awk} program (@pxref{Wc Program}) just
+use the value of @code{FNR} in @code{endfile()}?
+Hint: Examine the code in @ref{Filetrans Function}.
 
 @ignore
-@ifdocbook
+@command{wc} can't just use the value of @code{FNR} in
+@code{endfile()}. If you examine the code in @ref{Filetrans Function},
+you will see that @code{FNR} has already been reset by the time
+@code{endfile()} is called.
+@end ignore
+
+@item
+Manipulation of individual characters in the @command{translate} program
+(@pxref{Translate Program}) is painful using standard @command{awk}
+functions.  Given that @command{gawk} can split strings into individual
+characters using @code{""} as the separator, how might you use this
+feature to simplify the program?
+
+@item
+The @file{extract.awk} program (@pxref{Extract Program}) was written
+before @command{gawk} had the @code{gensub()} function.  Use it
+to simplify the code.
+
+@item
+Compare the performance of the @file{awksed.awk} program
+(@pxref{Simple Sed}) with the more straightforward:
+
+@example
+BEGIN @{
+    pat = ARGV[1]
+    repl = ARGV[2]
+    ARGV[1] = ARGV[2] = ""
+@}
+
+@{ gsub(pat, repl); print @}
+@end example
+
+@item
+What are the advantages and disadvantages of @file{awksed.awk} versus
+the real @command{sed} utility?
+
+@ignore
+  Advantage: egrep regexps
+             speed (?)
+  Disadvantage: no & in replacement text
+
+Others?
+@end ignore
+
+@item
+In @ref{Igawk Program}, we mentioned that not trying to save the line
+read with @code{getline} in the @code{pathto()} function when testing
+for the file's accessibility for use with the main program simplifies
+things considerably.  What problem does this engender though?
+@c answer, reading from "-" or /dev/stdin
+
+@cindex search paths
+@cindex search paths, for source files
+@cindex source files@comma{} search path for
+@cindex files, source@comma{} search path for
+@cindex directories, searching
+@item
+As an additional example of the idea that it is not always necessary to
+add new features to a program, consider the idea of having two files in
+a directory in the search path:
+
+@table @file
+@item default.awk
+This file contains a set of default library functions, such
+as @code{getopt()} and @code{assert()}.
+
+@item site.awk
+This file contains library functions that are specific to a site or
+installation; i.e., locally developed functions.
+Having a separate file allows @file{default.awk} to change with
+new @command{gawk} releases, without requiring the system administrator to
+update it each time by adding the local functions.
+@end table
+
+One user
+@c Karl Berry, karl@ileaf.com, 10/95
+suggested that @command{gawk} be modified to automatically read these files
+upon startup.  Instead, it would be very simple to modify @command{igawk}
+to do this. Since @command{igawk} can process nested @code{@@include}
+directives, @file{default.awk} could simply contain @code{@@include}
+statements for the desired library functions.
+Make this change.
+
+@item
+Modify @file{anagram.awk} (@pxref{Anagram Program}), to avoid
+the use of the external @command{sort} utility.
 
-@part Part III:@* Moving Beyond Standard @command{awk} With @command{gawk}
+@end enumerate
 
+@ifnotinfo
+@part @value{PART3}Moving Beyond Standard @command{awk} With @command{gawk}
+@end ifnotinfo
+
+@ifdocbook
 Part III focuses on features specific to @command{gawk}.
 It contains the following chapters:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Advanced Features}.
 
@@ -24054,12 +25499,11 @@ It contains the following chapters:
 
 @item
 @ref{Dynamic Extensions}.
+@end itemize
 @end ifdocbook
-@end ignore
 
 @node Advanced Features
 @chapter Advanced Features of @command{gawk}
-@cindex advanced features, network connections, See Also networks, connections
 @c STARTOFRANGE gawadv
 @cindex @command{gawk}, features, advanced
 @c STARTOFRANGE advgaw
@@ -24072,6 +25516,8 @@ Contributed by: Peter Langston <pud!psl@bellcore.bellcore.com>
 "Write documentation as if whoever reads it is a violent psychopath
 who knows where you live."
 @end ignore
+@cindex Langston, Peter
+@cindex English, Steve
 @quotation
 @i{Write documentation as if whoever reads it is
 a violent psychopath who knows where you live.}
@@ -24091,10 +25537,11 @@ of TCP/IP networking.  Finally, @command{gawk}
 can @dfn{profile} an @command{awk} program, making it possible to tune
 it for performance.
 
+@c FULLXREF ON
 A number of advanced features require separate @value{CHAPTER}s of their
 own:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Internationalization}, discusses how to internationalize
 your @command{awk} programs, so that they can speak multiple
@@ -24113,6 +25560,7 @@ debugger for debugging @command{awk} programs.
 discusses the ability to dynamically add new built-in functions to
 @command{gawk}.
 @end itemize
+@c FULLXREF OFF
 
 @menu
 * Nondecimal Data::             Allowing nondecimal input data.
@@ -24121,11 +25569,12 @@ discusses the ability to dynamically add new built-in functions to
 * Two-way I/O::                 Two-way communications with another process.
 * TCP/IP Networking::           Using @command{gawk} for network programming.
 * Profiling::                   Profiling your @command{awk} programs.
+* Advanced Features Summary::   Summary of advanced features.
 @end menu
 
 @node Nondecimal Data
 @section Allowing Nondecimal Input Data
-@cindex @code{--non-decimal-data} option
+@cindex @option{--non-decimal-data} option
 @cindex advanced features, nondecimal input data
 @cindex input, data@comma{} nondecimal
 @cindex constants, nondecimal
@@ -24153,7 +25602,7 @@ $ @kbd{echo 0123 123 0x123 | gawk '@{ print $1, $2, $3 @}'}
 The @code{print} statement treats its expressions as strings.
 Although the fields can act as numbers when necessary,
 they are still strings, so @code{print} does not try to treat them
-numerically.  You may need to add zero to a field to force it to
+numerically.  You need to add zero to a field to force it to
 be treated as a number.  For example:
 
 @example
@@ -24169,13 +25618,13 @@ using this facility could lead to surprising results, the default is to leave it
 disabled.  If you want it, you must explicitly request it.
 
 @cindex programming conventions, @code{--non-decimal-data} option
-@cindex @code{--non-decimal-data} option, @code{strtonum()} function and
+@cindex @option{--non-decimal-data} option, @code{strtonum()} function and
 @cindex @code{strtonum()} function (@command{gawk}), @code{--non-decimal-data} option and
 @quotation CAUTION
 @emph{Use of this option is not recommended.}
 It can break old programs very badly.
 Instead, use the @code{strtonum()} function to convert your data
-(@pxref{Nondecimal-numbers}).
+(@pxref{String Functions}).
 This makes your programs easier to write and easier to read, and
 leads to less surprising results.
 @end quotation
@@ -24209,7 +25658,7 @@ lets you do this.
 
 @ref{Controlling Scanning}, describes how you can assign special,
 pre-defined values to @code{PROCINFO["sorted_in"]} in order to
-control the order in which @command{gawk} will traverse an array
+control the order in which @command{gawk} traverses an array
 during a @code{for} loop.
 
 In addition, the value of @code{PROCINFO["sorted_in"]} can be a function name.
@@ -24466,9 +25915,9 @@ sorted array traversal is not the default.
 @subsection Sorting Array Values and Indices with @command{gawk}
 
 @cindex arrays, sorting
-@cindex @code{asort()} function (@command{gawk})
+@cindexgawkfunc{asort}
 @cindex @code{asort()} function (@command{gawk}), arrays@comma{} sorting
-@cindex @code{asorti()} function (@command{gawk})
+@cindexgawkfunc{asorti}
 @cindex @code{asorti()} function (@command{gawk}), arrays@comma{} sorting
 @cindex sort function, arrays, sorting
 In most @command{awk} implementations, sorting an array requires writing
@@ -24533,9 +25982,9 @@ END @{
 
 So far, so good. Now it starts to get interesting.  Both @code{asort()}
 and @code{asorti()} accept a third string argument to control comparison
-of array elements.  In @ref{String Functions}, we ignored this third
-argument; however, the time has now come to describe how this argument
-affects these two functions.
+of array elements.  When we introduced @code{asort()} and @code{asorti()}
+in @ref{String Functions}, we ignored this third argument; however,
+now is the time to describe how this argument affects these two functions.
 
 Basically, the third argument specifies how the array is to be sorted.
 There are two possibilities.  As with @code{PROCINFO["sorted_in"]},
@@ -24563,9 +26012,8 @@ both arrays use the values.
 
 @c Document It And Call It A Feature. Sigh.
 @cindex @command{gawk}, @code{IGNORECASE} variable in
-@cindex @code{IGNORECASE} variable
-@cindex arrays, sorting, @code{IGNORECASE} variable and
-@cindex @code{IGNORECASE} variable, array sorting and
+@cindex arrays, sorting, and @code{IGNORECASE} variable
+@cindex @code{IGNORECASE} variable, and array sorting functions
 Because @code{IGNORECASE} affects string comparisons, the value
 of @code{IGNORECASE} also affects sorting for both @code{asort()} and @code{asorti()}.
 Note also that the locale's sorting order does @emph{not}
@@ -24644,7 +26092,7 @@ open a @emph{two-way} pipe to another process.  The second process is
 termed a @dfn{coprocess}, since it runs in parallel with @command{gawk}.
 The two-way connection is created using the @samp{|&} operator
 (borrowed from the Korn shell, @command{ksh}):@footnote{This is very
-different from the same operator in the C shell.}
+different from the same operator in the C shell and in Bash.}
 
 @example
 do @{
@@ -24666,7 +26114,7 @@ the shell.
 
 There are some cautionary items to be aware of:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 As the code inside @command{gawk} currently stands, the coprocess's
 standard error goes to the same place that the parent @command{gawk}'s
@@ -24732,9 +26180,10 @@ has been read, @command{gawk} terminates the coprocess and exits.
 
 As a side note, the assignment @samp{LC_ALL=C} in the @command{sort}
 command ensures traditional Unix (ASCII) sorting from @command{sort}.
+This is not strictly necessary here, but it's good to know how to do this.
 
 @cindex @command{gawk}, @code{PROCINFO} array in
-@cindex @code{PROCINFO} array
+@cindex @code{PROCINFO} array, and communications via ptys
 You may also use pseudo-ttys (ptys) for
 two-way communication instead of pipes, if your system supports them.
 This is done on a per-command basis, by setting a special element
@@ -24750,7 +26199,7 @@ print @dots{} |& command       # start two-way pipe
 @end example
 
 @noindent
-Using ptys avoids the buffer deadlock issues described earlier, at some
+Using ptys usually avoids the buffer deadlock issues described earlier, at some
 loss in performance.  If your system does not have ptys, or if all the
 system's ptys are in use, @command{gawk} automatically falls back to
 using regular pipes.
@@ -24785,10 +26234,10 @@ another process on another system across an IP network connection.
 You can think of this as just a @emph{very long} two-way pipeline to
 a coprocess.
 The way @command{gawk} decides that you want to use TCP/IP networking is
-by recognizing special file names that begin with one of @samp{/inet/},
+by recognizing special @value{FN}s that begin with one of @samp{/inet/},
 @samp{/inet4/} or @samp{/inet6}.
 
-The full syntax of the special file name is
+The full syntax of the special @value{FN} is
 @file{/@var{net-type}/@var{protocol}/@var{local-port}/@var{remote-host}/@var{remote-port}}.
 The components are:
 
@@ -24854,7 +26303,9 @@ See
 @inforef{Top, , General Introduction, gawkinet, TCP/IP Internetworking with @command{gawk}},
 @end ifinfo
 @ifnotinfo
-See @cite{TCP/IP Internetworking with @command{gawk}},
+See
+@uref{http://www.gnu.org/software/gawk/manual/gawkinet/,
+@cite{TCP/IP Internetworking with @command{gawk}}},
 which comes as part of the @command{gawk} distribution,
 @end ifnotinfo
 for a much more complete introduction and discussion, as well as
@@ -24877,7 +26328,7 @@ When @command{gawk} has finished running, it creates a profile of your program i
 named @file{awkprof.out}. Because it is profiling, it also executes up to 45% slower than
 @command{gawk} normally does.
 
-@cindex @code{--profile} option
+@cindex @option{--profile} option
 As shown in the following example,
 the @option{--profile} option can be used to change the name of the file
 where @command{gawk} will write the profile:
@@ -24932,68 +26383,77 @@ foo
 junk
 @end example
 
-Here is the @file{awkprof.out} that results from running the @command{gawk}
-profiler on this program and data (this example also illustrates that @command{awk}
-programmers sometimes have to work late):
+Here is the @file{awkprof.out} that results from running the
+@command{gawk} profiler on this program and data. (This example also
+illustrates that @command{awk} programmers sometimes get up very early
+in the morning to work.)
 
-@cindex @code{BEGIN} pattern
-@cindex @code{END} pattern
+@cindex @code{BEGIN} pattern, and profiling
+@cindex @code{END} pattern, and profiling
 @example
-        # gawk profile, created Sun Aug 13 00:00:15 2000
+    # gawk profile, created Thu Feb 27 05:16:21 2014
 
-        # BEGIN block(s)
+    # BEGIN block(s)
 
-        BEGIN @{
-     1          print "First BEGIN rule"
-     1          print "Second BEGIN rule"
-        @}
+    BEGIN @{
+ 1          print "First BEGIN rule"
+    @}
 
-        # Rule(s)
+    BEGIN @{
+ 1          print "Second BEGIN rule"
+    @}
 
-     5  /foo/   @{ # 2
-     2          print "matched /foo/, gosh"
-     6          for (i = 1; i <= 3; i++) @{
-     6                  sing()
-                @}
-        @}
+    # Rule(s)
 
-     5  @{
-     5          if (/foo/) @{ # 2
-     2                  print "if is true"
-     3          @} else @{
-     3                  print "else is true"
-                @}
-        @}
+ 5  /foo/ @{ # 2
+ 2          print "matched /foo/, gosh"
+ 6          for (i = 1; i <= 3; i++) @{
+ 6                  sing()
+            @}
+    @}
 
-        # END block(s)
+ 5  @{
+ 5          if (/foo/) @{ # 2
+ 2                  print "if is true"
+ 3          @} else @{
+ 3                  print "else is true"
+            @}
+    @}
 
-        END @{
-     1          print "First END rule"
-     1          print "Second END rule"
-        @}
+    # END block(s)
 
-        # Functions, listed alphabetically
+    END @{
+ 1          print "First END rule"
+    @}
 
-     6  function sing(dummy)
-        @{
-     6          print "I gotta be me!"
-        @}
+    END @{
+ 1          print "Second END rule"
+    @}
+
+
+    # Functions, listed alphabetically
+
+ 6  function sing(dummy)
+    @{
+ 6          print "I gotta be me!"
+    @}
 @end example
 
 This example illustrates many of the basic features of profiling output.
 They are as follows:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-The program is printed in the order @code{BEGIN} rule,
-@code{BEGINFILE} rule,
+The program is printed in the order @code{BEGIN} rules,
+@code{BEGINFILE} rules,
 pattern/action rules,
-@code{ENDFILE} rule, @code{END} rule and functions, listed
+@code{ENDFILE} rules, @code{END} rules and functions, listed
 alphabetically.
-Multiple @code{BEGIN} and @code{END} rules are merged together,
-as are multiple @code{BEGINFILE} and @code{ENDFILE} rules.
+Multiple @code{BEGIN} and @code{END} rules retain their
+separate identities, as do
+multiple @code{BEGINFILE} and @code{ENDFILE} rules.
 
-@cindex patterns, counts
+@cindex patterns, counts, in a profile
 @item
 Pattern-action rules have two counts.
 The first count, to the left of the rule, shows how many times
@@ -25013,7 +26473,7 @@ is a count showing how many times the condition was true.
 The count for the @code{else}
 indicates how many times the test failed.
 
-@cindex loops, count for header
+@cindex loops, count for header, in a profile
 @item
 The count for a loop header (such as @code{for}
 or @code{while}) shows how many times the loop test was executed.
@@ -25021,8 +26481,8 @@ or @code{while}) shows how many times the loop test was executed.
 statement in a rule to determine how many times the rule was executed.
 If the first statement is a loop, the count is misleading.)
 
-@cindex functions, user-defined, counts
-@cindex user-defined, functions, counts
+@cindex functions, user-defined, counts, in a profile
+@cindex user-defined, functions, counts, in a profile
 @item
 For user-defined functions, the count next to the @code{function}
 keyword indicates how many times the function was called.
@@ -25036,12 +26496,11 @@ The layout uses ``K&R'' style with TABs.
 Braces are used everywhere, even when
 the body of an @code{if}, @code{else}, or loop is only a single statement.
 
-@cindex @code{()} (parentheses)
-@cindex parentheses @code{()}
+@cindex @code{()} (parentheses), in a profile
+@cindex parentheses @code{()}, in a profile
 @item
 Parentheses are used only where needed, as indicated by the structure
 of the program and the precedence rules.
-@c extra verbiage here satisfies the copyeditor. ugh.
 For example, @samp{(3 + 5) * 4} means add three plus five, then multiply
 the total by four.  However, @samp{3 + 5 * 4} has no parentheses, and
 means @samp{3 + (5 * 4)}.
@@ -25072,8 +26531,8 @@ typed when you wrote it.  This is because @command{gawk} creates the
 profiled version by ``pretty printing'' its internal representation of
 the program.  The advantage to this is that @command{gawk} can produce
 a standard representation.  The disadvantage is that all source-code
-comments are lost, as are the distinctions among multiple @code{BEGIN},
-@code{END}, @code{BEGINFILE}, and @code{ENDFILE} rules.  Also, things such as:
+comments are lost.
+Also, things such as:
 
 @example
 /foo/
@@ -25093,6 +26552,7 @@ which is correct, but possibly surprising.
 
 @cindex profiling @command{awk} programs, dynamically
 @cindex @command{gawk} program, dynamic profiling
+@cindex dynamic profiling
 Besides creating profiles when a program has completed,
 @command{gawk} can produce a profile while it is running.
 This is useful if your @command{awk} program goes into an
@@ -25106,9 +26566,9 @@ $ @kbd{gawk --profile -f myprog &}
 @end example
 
 @cindex @command{kill} command@comma{} dynamic profiling
-@cindex @code{USR1} signal
-@cindex @code{SIGUSR1} signal
-@cindex signals, @code{USR1}/@code{SIGUSR1}
+@cindex @code{USR1} signal, for dynamic profiling
+@cindex @code{SIGUSR1} signal, for dynamic profiling
+@cindex signals, @code{USR1}/@code{SIGUSR1}, for profiling
 @noindent
 The shell prints a job number and process ID number; in this case, 13992.
 Use the @command{kill} command to send the @code{USR1} signal
@@ -25123,7 +26583,7 @@ As usual, the profiled version of the program is written to
 @file{awkprof.out}, or to a different file if one specified with
 the @option{--profile} option.
 
-Along with the regular profile, as shown earlier, the profile
+Along with the regular profile, as shown earlier, the profile file
 includes a trace of any active functions:
 
 @example
@@ -25139,9 +26599,9 @@ You may send @command{gawk} the @code{USR1} signal as many times as you like.
 Each time, the profile and function call trace are appended to the output
 profile file.
 
-@cindex @code{HUP} signal
-@cindex @code{SIGHUP} signal
-@cindex signals, @code{HUP}/@code{SIGHUP}
+@cindex @code{HUP} signal, for dynamic profiling
+@cindex @code{SIGHUP} signal, for dynamic profiling
+@cindex signals, @code{HUP}/@code{SIGHUP}, for profiling
 If you use the @code{HUP} signal instead of the @code{USR1} signal,
 @command{gawk} produces the profile and the function call trace and then exits.
 
@@ -25163,11 +26623,61 @@ keyboard.  The @code{INT} signal is generated by the
 Finally, @command{gawk} also accepts another option, @option{--pretty-print}.
 When called this way, @command{gawk} ``pretty prints'' the program into
 @file{awkprof.out}, without any execution counts.
-@c ENDOFRANGE advgaw
-@c ENDOFRANGE gawadv
+
+@quotation NOTE
+The @option{--pretty-print} option still runs your program.
+This will change in the next major release.
+@end quotation
 @c ENDOFRANGE awkp
 @c ENDOFRANGE proawk
 
+@node Advanced Features Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+The @option{--non-decimal-data} option causes @command{gawk} to treat
+octal- and hexadecimal-looking input data as octal and hexadecimal.
+This option should be used with caution or not at all; use of @code{strtonum()}
+is preferable.
+
+@item
+You can take over complete control of sorting in @samp{for (@var{indx} in @var{array})}
+array traversal by setting @code{PROCINFO["sorted_in"]} to the name of a user-defined
+function that does the comparison of array elements based on index and value.
+
+@item
+Similarly, you can supply the name of a user-defined comparison function as the
+third argument to either @code{asort()} or @command{asorti()} to control how
+those functions sort arrays. Or you may provide one of the predefined control
+strings that work for @code{PROCINFO["sorted_in"]}.
+
+@item
+You can use the @samp{|&} operator to create a two-way pipe to a co-process.
+You read from the co-process with @code{getline} and write to it with @code{print}
+or @code{printf}. Use @code{close()} to close off the co-process completely, or
+optionally, close off one side of the two-way communications.
+
+@item
+By using special ``@value{FN}s'' with the @samp{|&} operator, you can open a
+TCP/IP (or UDP/IP) connection to remote hosts in the Internet. @command{gawk}
+supports both IPv4 an IPv6.
+
+@item
+You can generate statement count profiles of your program. This can help you
+determine which parts of your program may be taking the most time and let
+you tune them more easily.  Sending the @code{USR1} signal while profiling causes
+@command{gawk} to dump the profile and keep going, including a function call stack.
+
+@item
+You can also just ``pretty print'' the program. This currently also runs
+the program, but that will change in the next major release.
+
+@end itemize
+
+@c ENDOFRANGE advgaw
+@c ENDOFRANGE gawadv
+
 @node Internationalization
 @chapter Internationalization with @command{gawk}
 
@@ -25196,11 +26706,12 @@ a requirement.
 
 @menu
 * I18N and L10N::               Internationalization and Localization.
-* Explaining gettext::          How GNU @code{gettext} works.
+* Explaining gettext::          How GNU @command{gettext} works.
 * Programmer i18n::             Features for the programmer.
 * Translator i18n::             Features for the translator.
 * I18N Example::                A simple i18n example.
 * Gawk I18N::                   @command{gawk} is also internationalized.
+* I18N Summary::                Summary of I18N stuff.
 @end menu
 
 @node I18N and L10N
@@ -25220,20 +26731,22 @@ responses, and information related to how numerical and
 monetary values are printed and read.
 
 @node Explaining gettext
-@section GNU @code{gettext}
+@section GNU @command{gettext}
 
 @cindex internationalizing a program
 @c STARTOFRANGE gettex
-@cindex @code{gettext} library
-The facilities in GNU @code{gettext} focus on messages; strings printed
+@cindex @command{gettext} library
+@command{gawk} uses GNU @command{gettext} to provide its internationalization
+features.
+The facilities in GNU @command{gettext} focus on messages; strings printed
 by a program, either directly or via formatting with @code{printf} or
 @code{sprintf()}.@footnote{For some operating systems, the @command{gawk}
-port doesn't support GNU @code{gettext}.
+port doesn't support GNU @command{gettext}.
 Therefore, these features are not available
 if you are using one of those operating systems. Sorry.}
 
-@cindex portability, @code{gettext} library and
-When using GNU @code{gettext}, each application has its own
+@cindex portability, @command{gettext} library and
+When using GNU @command{gettext}, each application has its own
 @dfn{text domain}.  This is a unique name, such as @samp{kpilot} or @samp{gawk},
 that identifies the application.
 A complete application may have multiple components---programs written
@@ -25257,7 +26770,7 @@ language).
 @cindex @code{textdomain()} function (C library)
 @item
 The programmer indicates the application's text domain
-(@code{"guide"}) to the @code{gettext} library,
+(@command{"guide"}) to the @command{gettext} library,
 by calling the @code{textdomain()} function.
 
 @cindex @code{.pot} files
@@ -25274,6 +26787,7 @@ lookup of the translations.
 
 @cindex @code{.po} files
 @cindex files, @code{.po}
+@c STARTOFRANGE portobfi
 @cindex portable object files
 @cindex files, portable object
 @item
@@ -25285,6 +26799,7 @@ For example, there might be a @file{fr.po} for a French translation.
 @cindex @code{.gmo} files
 @cindex files, @code{.gmo}
 @cindex message object files
+@c STARTOFRANGE portmsgfi
 @cindex files, message object
 @item
 Each language's @file{.po} file is converted into a binary
@@ -25299,7 +26814,7 @@ are installed in a standard place.
 
 @cindex @code{bindtextdomain()} function (C library)
 @item
-For testing and development, it is possible to tell @code{gettext}
+For testing and development, it is possible to tell @command{gettext}
 to use @file{.gmo} files in a different directory than the standard
 one by using the @code{bindtextdomain()} function.
 
@@ -25332,7 +26847,7 @@ strings enclosed in calls to @code{gettext()}.
 
 @cindex @code{_} (underscore), C macro
 @cindex underscore (@code{_}), C macro
-The GNU @code{gettext} developers, recognizing that typing
+The GNU @command{gettext} developers, recognizing that typing
 @samp{gettext(@dots{})} over and over again is both painful and ugly to look
 at, use the macro @samp{_} (an underscore) to make things easier:
 
@@ -25345,7 +26860,7 @@ printf("%s", _("Don't Panic!\n"));
 @end example
 
 @cindex internationalization, localization, locale categories
-@cindex @code{gettext} library, locale categories
+@cindex @command{gettext} library, locale categories
 @cindex locale categories
 @noindent
 This reduces the typing overhead to just three extra characters per string
@@ -25353,12 +26868,12 @@ and is considerably easier to read as well.
 
 There are locale @dfn{categories}
 for different types of locale-related information.
-The defined locale categories that @code{gettext} knows about are:
+The defined locale categories that @command{gettext} knows about are:
 
 @table @code
 @cindex @code{LC_MESSAGES} locale category
 @item LC_MESSAGES
-Text messages.  This is the default category for @code{gettext}
+Text messages.  This is the default category for @command{gettext}
 operations, but it is possible to supply a different one explicitly,
 if necessary.  (It is almost never necessary to supply a different category.)
 
@@ -25406,7 +26921,7 @@ before or after the day in a date, local month abbreviations, and so on.
 
 @cindex @code{LC_ALL} locale category
 @item LC_ALL
-All of the above.  (Not too useful in the context of @code{gettext}.)
+All of the above.  (Not too useful in the context of @command{gettext}.)
 @end table
 @c ENDOFRANGE gettex
 
@@ -25422,7 +26937,7 @@ internationalization:
 @cindex @code{TEXTDOMAIN} variable
 @item TEXTDOMAIN
 This variable indicates the application's text domain.
-For compatibility with GNU @code{gettext}, the default
+For compatibility with GNU @command{gettext}, the default
 value is @code{"messages"}.
 
 @cindex internationalization, localization, marked strings
@@ -25432,8 +26947,8 @@ String constants marked with a leading underscore
 are candidates for translation at runtime.
 String constants without a leading underscore are not translated.
 
-@cindex @code{dcgettext()} function (@command{gawk})
-@item dcgettext(@var{string} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcgettext}
+@item @code{dcgettext(@var{string}} [@code{,} @var{domain} [@code{,} @var{category}]]@code{)}
 Return the translation of @var{string} in
 text domain @var{domain} for locale category @var{category}.
 The default value for @var{domain} is the current value of @code{TEXTDOMAIN}.
@@ -25458,8 +26973,8 @@ chosen to be simple and to allow for reasonable @command{awk}-style
 default arguments.
 @end quotation
 
-@cindex @code{dcngettext()} function (@command{gawk})
-@item dcngettext(@var{string1}, @var{string2}, @var{number} @r{[}, @var{domain} @r{[}, @var{category}@r{]]})
+@cindexgawkfunc{dcngettext}
+@item @code{dcngettext(@var{string1}, @var{string2}, @var{number}} [@code{,} @var{domain} [@code{,} @var{category}]]@code{)}
 Return the plural form used for @var{number} of the
 translation of @var{string1} and @var{string2} in text domain
 @var{domain} for locale category @var{category}. @var{string1} is the
@@ -25474,10 +26989,10 @@ The same remarks about argument order as for the @code{dcgettext()} function app
 @cindex files, @code{.gmo}, specifying directory of
 @cindex message object files, specifying directory of
 @cindex files, message object, specifying directory of
-@cindex @code{bindtextdomain()} function (@command{gawk})
-@item bindtextdomain(@var{directory} @r{[}, @var{domain}@r{]})
+@cindexgawkfunc{bindtextdomain}
+@item @code{bindtextdomain(@var{directory}} [@code{,} @var{domain} ]@code{)}
 Change the directory in which
-@code{gettext} looks for @file{.gmo} files, in case they
+@command{gettext} looks for @file{.gmo} files, in case they
 will not or cannot be placed in the standard locations
 (e.g., during testing).
 Return the directory in which @var{domain} is ``bound.''
@@ -25576,7 +27091,7 @@ and use translations from @command{awk}.
 @cindex portable object files
 @cindex files, portable object
 Once a program's translatable strings have been marked, they must
-be extracted to create the initial @file{.po} file.
+be extracted to create the initial @file{.pot} file.
 As part of translation, it is often helpful to rearrange the order
 in which arguments to @code{printf} are output.
 
@@ -25596,13 +27111,13 @@ is covered.
 @subsection Extracting Marked Strings
 @cindex strings, extracting
 @cindex marked strings@comma{} extracting
-@cindex @code{--gen-pot} option
+@cindex @option{--gen-pot} option
 @cindex command-line options, string extraction
 @cindex string extraction (internationalization)
 @cindex marked string extraction (internationalization)
 @cindex extraction, of marked strings (internationalization)
 
-@cindex @code{--gen-pot} option
+@cindex @option{--gen-pot} option
 Once your @command{awk} program is working, and all the strings have
 been marked and you've set (and perhaps bound) the text domain,
 it is time to produce translations.
@@ -25616,15 +27131,17 @@ $ @kbd{gawk --gen-pot -f guide.awk > guide.pot}
 @cindex @code{xgettext} utility
 When run with @option{--gen-pot}, @command{gawk} does not execute your
 program.  Instead, it parses it as usual and prints all marked strings
-to standard output in the format of a GNU @code{gettext} Portable Object
+to standard output in the format of a GNU @command{gettext} Portable Object
 file.  Also included in the output are any constant strings that
 appear as the first argument to @code{dcgettext()} or as the first and
 second argument to @code{dcngettext()}.@footnote{The
 @command{xgettext} utility that comes with GNU
-@code{gettext} can handle @file{.awk} files.}
+@command{gettext} can handle @file{.awk} files.}
 @xref{I18N Example},
 for the full list of steps to go through to create and test
 translations for @command{guide}.
+@c ENDOFRANGE portobfi
+@c ENDOFRANGE portmsgfi
 
 @node Printf Ordering
 @subsection Rearranging @code{printf} Arguments
@@ -25635,9 +27152,8 @@ Format strings for @code{printf} and @code{sprintf()}
 (@pxref{Printf})
 present a special problem for translation.
 Consider the following:@footnote{This example is borrowed
-from the GNU @code{gettext} manual.}
+from the GNU @command{gettext} manual.}
 
-@c line broken here only for smallbook format
 @example
 printf(_"String `%s' has %d characters\n",
           string, length(string)))
@@ -25671,7 +27187,7 @@ example, @samp{string} is the first argument and @samp{length(string)} is the se
 @example
 $ @kbd{gawk 'BEGIN @{}
 >     @kbd{string = "Dont Panic"}
->     @kbd{printf _"%2$d characters live in \"%1$s\"\n",}
+>     @kbd{printf "%2$d characters live in \"%1$s\"\n",}
 >                         @kbd{string, length(string)}
 > @kbd{@}'}
 @print{} 10 characters live in "Dont Panic"
@@ -25705,7 +27221,7 @@ This is somewhat counterintuitive.
 and those with positional specifiers in the same string:
 
 @example
-$ @kbd{gawk 'BEGIN @{ printf _"%d %3$s\n", 1, 2, "hi" @}'}
+$ @kbd{gawk 'BEGIN @{ printf "%d %3$s\n", 1, 2, "hi" @}'}
 @error{} gawk: cmd. line:1: fatal: must use `count$' on all formats or none
 @end example
 
@@ -25745,7 +27261,7 @@ As written, it won't work on other versions of @command{awk}.
 However, it is actually almost portable, requiring very little
 change:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @cindex @code{TEXTDOMAIN} variable, portability and
 @item
 Assignments to @code{TEXTDOMAIN} won't have any effect,
@@ -25885,33 +27401,34 @@ msgstr "Like, the scoop is"
 @cindex Linux
 @cindex GNU/Linux
 The next step is to make the directory to hold the binary message object
-file and then to create the @file{guide.gmo} file.
-The directory layout shown here is standard for GNU @code{gettext} on
-GNU/Linux systems.  Other versions of @code{gettext} may use a different
+file and then to create the @file{guide.mo} file.
+We pretend that our file is to be used in the @code{en_US.UTF-8} locale.
+The directory layout shown here is standard for GNU @command{gettext} on
+GNU/Linux systems.  Other versions of @command{gettext} may use a different
 layout:
 
 @example
-$ @kbd{mkdir en_US en_US/LC_MESSAGES}
+$ @kbd{mkdir en_US.UTF-8 en_US.UTF-8/LC_MESSAGES}
 @end example
 
-@cindex @code{.po} files, converting to @code{.gmo}
-@cindex files, @code{.po}, converting to @code{.gmo}
-@cindex @code{.gmo} files, converting from @code{.po}
-@cindex files, @code{.gmo}, converting from @code{.po}
+@cindex @code{.po} files, converting to @code{.mo}
+@cindex files, @code{.po}, converting to @code{.mo}
+@cindex @code{.mo} files, converting from @code{.po}
+@cindex files, @code{.mo}, converting from @code{.po}
 @cindex portable object files, converting to message object files
 @cindex files, portable object, converting to message object files
 @cindex message object files, converting from portable object files
 @cindex files, message object, converting from portable object files
 @cindex @command{msgfmt} utility
 The @command{msgfmt} utility does the conversion from human-readable
-@file{.po} file to machine-readable @file{.gmo} file.
+@file{.po} file to machine-readable @file{.mo} file.
 By default, @command{msgfmt} creates a file named @file{messages}.
 This file must be renamed and placed in the proper directory so that
 @command{gawk} can find it:
 
 @example
 $ @kbd{msgfmt guide-mellow.po}
-$ @kbd{mv messages en_US/LC_MESSAGES/guide.gmo}
+$ @kbd{mv messages en_US.UTF-8/LC_MESSAGES/guide.mo}
 @end example
 
 Finally, we run the program to test it:
@@ -25940,30 +27457,71 @@ $ @kbd{gawk --posix -f guide.awk -f libintl.awk}
 @section @command{gawk} Can Speak Your Language
 
 @command{gawk} itself has been internationalized
-using the GNU @code{gettext} package.
-(GNU @code{gettext} is described in
+using the GNU @command{gettext} package.
+(GNU @command{gettext} is described in
 complete detail in
 @ifinfo
-@inforef{Top, , GNU @code{gettext} utilities, gettext, GNU gettext tools}.)
+@inforef{Top, , GNU @command{gettext} utilities, gettext, GNU gettext tools}.)
 @end ifinfo
 @ifnotinfo
-@cite{GNU gettext tools}.)
+@uref{http://www.gnu.org/software/gettext/manual/,
+@cite{GNU gettext tools}}.)
 @end ifnotinfo
-As of this writing, the latest version of GNU @code{gettext} is
-@uref{ftp://ftp.gnu.org/gnu/gettext/gettext-0.18.2.1.tar.gz, version 0.18.2.1}.
+As of this writing, the latest version of GNU @command{gettext} is
+@uref{ftp://ftp.gnu.org/gnu/gettext/gettext-0.19.1.tar.gz,
+@value{PVERSION} 0.19.1}.
 
 If a translation of @command{gawk}'s messages exists,
 then @command{gawk} produces usage messages, warnings,
 and fatal errors in the local language.
-@c ENDOFRANGE inloc
 
-@c The original text for this chapter was contributed by Efraim Yawitz.
-@c FIXME: Add more indexing.
+@node I18N Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Internationalization means writing a program such that it can use multiple
+languages without requiring source-code changes.  Localization means
+providing the data necessary for an internationalized program to work
+in a particular language.
+
+@item
+@command{gawk} uses GNU @command{gettext} to let you internationalize
+and localize @command{awk} programs.  A program's text domain identifies
+the program for grouping all messages and other data together.
+
+@item
+You mark a program's strings for translation by preceding them with
+an underscore. Once that is done, the strings are extracted into a
+@file{.pot} file.  This file is copied for each language into a @file{.po}
+file, and the @file{.po} files are compiled into @file{.gmo} files for
+use at runtime.
+
+@item
+You can use position specifications with @code{sprintf()} and
+@code{printf} to rearrange the placement of argument values in formatted
+strings and output. This is useful for the translations of format
+control strings.
+
+@item
+The internationalization features have been designed so that they
+can be easily worked around in a standard @command{awk}.
+
+@item
+@command{gawk} itself has been internationalized and ships with
+a number of translations for its messages.
+
+@end itemize
+
+@c ENDOFRANGE inloc
 
 @node Debugger
 @chapter Debugging @command{awk} Programs
 @cindex debugging @command{awk} programs
 
+@c The original text for this chapter was contributed by Efraim Yawitz.
+@c FIXME: Add more indexing.
+
 It would be nice if computer programs worked perfectly the first time they
 were run, but in real life, this rarely happens for programs of
 any complexity.  Thus, most programming languages have facilities available
@@ -25980,10 +27538,11 @@ how to use @command{gawk} for debugging your program is easy.
 * List of Debugger Commands::   Main debugger commands.
 * Readline Support::            Readline support.
 * Limitations::                 Limitations and future plans.
+* Debugging Summary::           Debugging summary.
 @end menu
 
 @node Debugging
-@section Introduction to @command{gawk} Debugger
+@section Introduction to The @command{gawk} Debugger
 
 This @value{SECTION} introduces debugging in general and begins
 the discussion of debugging in @command{gawk}.
@@ -26008,7 +27567,7 @@ In that case, what can you expect from such a tool?  The answer to that
 depends on the language being debugged, but in general, you can expect at
 least the following:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The ability to watch a program execute its instructions one by one,
 giving you, the programmer, the opportunity to think about what is happening
@@ -26046,6 +27605,7 @@ The following list defines terms used throughout the rest of
 this @value{CHAPTER}.
 
 @table @dfn
+@cindex stack frame
 @item Stack Frame
 Programs generally call functions during the course of their execution.
 One function can call another, or a function can call itself (recursion).
@@ -26067,6 +27627,7 @@ invoked. Commands that print the call stack print information about
 each stack frame (as detailed later on).
 
 @item Breakpoint
+@cindex breakpoint
 During debugging, you often wish to let the program run until it
 reaches a certain point, and then continue execution from there one
 statement (or instruction) at a time.  The way to do this is to set
@@ -26076,6 +27637,7 @@ take over control of the program's execution.  You can add and remove
 as many breakpoints as you like.
 
 @item Watchpoint
+@cindex watchpoint
 A watchpoint is similar to a breakpoint.  The difference is that
 breakpoints are oriented around the code: stop when a certain point in the
 code is reached.  A watchpoint, however, specifies that program execution
@@ -26107,6 +27669,7 @@ by the higher-level @command{awk} commands.
 
 @node Sample Debugging Session
 @section Sample Debugging Session
+@cindex sample debugging session
 
 In order to illustrate the use of @command{gawk} as a debugger, let's look at a sample
 debugging session.  We will use the @command{awk} implementation of the
@@ -26120,13 +27683,16 @@ as our example.
 
 @node Debugger Invocation
 @subsection How to Start the Debugger
+@cindex starting the debugger
+@cindex debugger, how to start
 
-Starting the debugger is almost exactly like running @command{awk}, except you have to
-pass an additional option @option{--debug} or the corresponding short option @option{-D}.
-The file(s) containing the program and any supporting code are given on the command
-line as arguments to one or more @option{-f} options. (@command{gawk} is not designed
-to debug command-line programs, only programs contained in files.)  In our case,
-we invoke the debugger like this:
+Starting the debugger is almost exactly like running @command{gawk},
+except you have to pass an additional option @option{--debug} or the
+corresponding short option @option{-D}.  The file(s) containing the
+program and any supporting code are given on the command line as arguments
+to one or more @option{-f} options. (@command{gawk} is not designed
+to debug command-line programs, only programs contained in files.)
+In our case, we invoke the debugger like this:
 
 @example
 $ @kbd{gawk -D -f getopt.awk -f join.awk -f uniq.awk inputfile}
@@ -26259,7 +27825,7 @@ gawk> @kbd{p NR}
 
 @noindent
 So we can see that @code{are_equal()} was only called for the second record
-of the file.  Of course, this is because our program contained a rule for
+of the file.  Of course, this is because our program contains a rule for
 @samp{NR == 1}:
 
 @example
@@ -26291,13 +27857,7 @@ This tells us that @command{gawk} is now ready to execute line 67, which
 decides whether to give the lines the special ``field skipping'' treatment
 indicated by the @option{-f} command-line option.  (Notice that we skipped
 from where we were before at line 64 to here, since the condition in line 64
-
-@example
-if (fcount == 0 && charcount == 0)
-@end example
-
-@noindent
-was false.)
+@samp{if (fcount == 0 && charcount == 0)} was false.)
 
 Continuing to step, we now get to the splitting of the current and
 last records:
@@ -26406,7 +27966,7 @@ and problem solved!
 The @command{gawk} debugger command set can be divided into the
 following categories:
 
-@itemize @bullet{}
+@itemize @value{BULLET}
 
 @item
 Breakpoint control
@@ -26432,7 +27992,7 @@ In the following descriptions, commands which may be abbreviated
 show the abbreviation on a second description line.
 A debugger command name may also be truncated if that partial
 name is unambiguous. The debugger has the built-in capability to
-automatically repeat the previous command when just hitting @key{Enter}.
+automatically repeat the previous command just by hitting @key{Enter}.
 This works for the commands @code{list}, @code{next}, @code{nexti}, @code{step}, @code{stepi}
 and @code{continue} executed without any argument.
 
@@ -26459,21 +28019,24 @@ controlling breakpoints are:
 @cindex debugger commands, @code{break}
 @cindex @code{break} debugger command
 @cindex @code{b} debugger command (alias for @code{break})
+@cindex set breakpoint
+@cindex breakpoint, setting
 @item @code{break} [[@var{filename}@code{:}]@var{n} | @var{function}] [@code{"@var{expression}"}]
 @itemx @code{b} [[@var{filename}@code{:}]@var{n} | @var{function}] [@code{"@var{expression}"}]
 Without any argument, set a breakpoint at the next instruction
 to be executed in the selected stack frame.
 Arguments can be one of the following:
 
+@c @asis for docbook
 @c nested table
-@table @var
-@item n
+@table @asis
+@item @var{n}
 Set a breakpoint at line number @var{n} in the current source file.
 
-@item filename@code{:}n
+@item @var{filename}@code{:}@var{n}
 Set a breakpoint at line number @var{n} in source file @var{filename}.
 
-@item function
+@item @var{function}
 Set a breakpoint at entry to (the first instruction of)
 function @var{function}.
 @end table
@@ -26489,6 +28052,8 @@ it continues executing the program.
 
 @cindex debugger commands, @code{clear}
 @cindex @code{clear} debugger command
+@cindex delete breakpoint at location
+@cindex breakpoint at location, how to delete
 @item @code{clear} [[@var{filename}@code{:}]@var{n} | @var{function}]
 Without any argument, delete any breakpoint at the next instruction
 to be executed in the selected stack frame. If the program stops at
@@ -26496,19 +28061,20 @@ a breakpoint, this deletes that breakpoint so that the program
 does not stop at that location again.  Arguments can be one of the following:
 
 @c nested table
-@table @var
-@item n
+@table @asis
+@item @var{n}
 Delete breakpoint(s) set at line number @var{n} in the current source file.
 
-@item filename@code{:}n
+@item @var{filename}@code{:}@var{n}
 Delete breakpoint(s) set at line number @var{n} in source file @var{filename}.
 
-@item function
+@item @var{function}
 Delete breakpoint(s) set at entry to function @var{function}.
 @end table
 
 @cindex debugger commands, @code{condition}
 @cindex @code{condition} debugger command
+@cindex breakpoint condition
 @item @code{condition} @var{n} @code{"@var{expression}"}
 Add a condition to existing breakpoint or watchpoint @var{n}. The
 condition is an @command{awk} expression that the debugger evaluates
@@ -26522,6 +28088,8 @@ watchpoint is made unconditional.
 @cindex debugger commands, @code{delete}
 @cindex @code{delete} debugger command
 @cindex @code{d} debugger command (alias for @code{delete})
+@cindex delete breakpoint by number
+@cindex breakpoint, delete by number
 @item @code{delete} [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 @itemx @code{d} [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 Delete specified breakpoints or a range of breakpoints. Deletes
@@ -26529,6 +28097,8 @@ all defined breakpoints if no argument is supplied.
 
 @cindex debugger commands, @code{disable}
 @cindex @code{disable} debugger command
+@cindex disable breakpoint
+@cindex breakpoint, how to disable or enable
 @item @code{disable} [@var{n1 n2} @dots{} | @var{n}--@var{m}]
 Disable specified breakpoints or a range of breakpoints. Without
 any argument, disables all breakpoints.
@@ -26537,6 +28107,7 @@ any argument, disables all breakpoints.
 @cindex debugger commands, @code{enable}
 @cindex @code{enable} debugger command
 @cindex @code{e} debugger command (alias for @code{enable})
+@cindex enable breakpoint
 @item @code{enable} [@code{del} | @code{once}] [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 @itemx @code{e} [@code{del} | @code{once}] [@var{n1 n2} @dots{}] [@var{n}--@var{m}]
 Enable specified breakpoints or a range of breakpoints. Without
@@ -26556,6 +28127,7 @@ the program stops at the breakpoint.
 
 @cindex debugger commands, @code{ignore}
 @cindex @code{ignore} debugger command
+@cindex ignore breakpoint
 @item @code{ignore} @var{n} @var{count}
 Ignore breakpoint number @var{n} the next @var{count} times it is
 hit.
@@ -26564,6 +28136,7 @@ hit.
 @cindex debugger commands, @code{tbreak}
 @cindex @code{tbreak} debugger command
 @cindex @code{t} debugger command (alias for @code{tbreak})
+@cindex temporary breakpoint
 @item @code{tbreak} [[@var{filename}@code{:}]@var{n} | @var{function}]
 @itemx @code{t} [[@var{filename}@code{:}]@var{n} | @var{function}]
 Set a temporary breakpoint (enabled for only one stop).
@@ -26584,6 +28157,8 @@ execution of the program than we saw in our earlier example:
 @cindex @code{silent} debugger command
 @cindex debugger commands, @code{end}
 @cindex @code{end} debugger command
+@cindex breakpoint commands
+@cindex commands to execute at breakpoint
 @item @code{commands} [@var{n}]
 @itemx @code{silent}
 @itemx @dots{}
@@ -26611,6 +28186,7 @@ gawk>
 
 @cindex debugger commands, @code{c} (@code{continue})
 @cindex debugger commands, @code{continue}
+@cindex continue program, in debugger
 @item @code{continue} [@var{count}]
 @itemx @code{c} [@var{count}]
 Resume program execution. If continued from a breakpoint and @var{count} is
@@ -26627,6 +28203,7 @@ Print the returned value.
 @cindex debugger commands, @code{next}
 @cindex @code{next} debugger command
 @cindex @code{n} debugger command (alias for @code{next})
+@cindex single-step execution, in the debugger
 @item @code{next} [@var{count}]
 @itemx @code{n} [@var{count}]
 Continue execution to the next source line, stepping over function calls.
@@ -26721,6 +28298,7 @@ items on the list.
 
 @cindex debugger commands, @code{eval}
 @cindex @code{eval} debugger command
+@cindex evaluate expressions, in debugger
 @item @code{eval "@var{awk statements}"}
 Evaluate @var{awk statements} in the context of the running program.
 You can do anything that an @command{awk} program would do: assign
@@ -26738,6 +28316,7 @@ parameters defined by the program.
 @cindex debugger commands, @code{print}
 @cindex @code{print} debugger command
 @cindex @code{p} debugger command (alias for @code{print})
+@cindex print variables, in debugger
 @item @code{print} @var{var1}[@code{,} @var{var2} @dots{}]
 @itemx @code{p} @var{var1}[@code{,} @var{var2} @dots{}]
 Print the value of a @command{gawk} variable or field.
@@ -26771,10 +28350,11 @@ No newline is printed unless one is specified.
 
 @cindex debugger commands, @code{set}
 @cindex @code{set} debugger command
+@cindex assign values to variables, in debugger
 @item @code{set} @var{var}@code{=}@var{value}
 Assign a constant (number or string) value to an @command{awk} variable
 or field.
-String values must be enclosed between double quotes (@code{"@dots{}"}).
+String values must be enclosed between double quotes (@code{"}@dots{}@code{"}).
 
 You can also set special @command{awk} variables, such as @code{FS},
 @code{NF}, @code{NR}, etc.
@@ -26783,6 +28363,7 @@ You can also set special @command{awk} variables, such as @code{FS},
 @cindex debugger commands, @code{watch}
 @cindex @code{watch} debugger command
 @cindex @code{w} debugger command (alias for @code{watch})
+@cindex set watchpoint
 @item @code{watch} @var{var} | @code{$}@var{n} [@code{"@var{expression}"}]
 @itemx @code{w} @var{var} | @code{$}@var{n} [@code{"@var{expression}"}]
 Add variable @var{var} (or field @code{$@var{n}}) to the watch list.
@@ -26799,12 +28380,14 @@ then the debugger stops execution and prompts for a command. Otherwise,
 
 @cindex debugger commands, @code{undisplay}
 @cindex @code{undisplay} debugger command
+@cindex stop automatic display, in debugger
 @item @code{undisplay} [@var{n}]
 Remove item number @var{n} (or all items, if no argument) from the
 automatic display list.
 
 @cindex debugger commands, @code{unwatch}
 @cindex @code{unwatch} debugger command
+@cindex delete watchpoint
 @item @code{unwatch} [@var{n}]
 Remove item number @var{n} (or all items, if no argument) from the
 watch list.
@@ -26825,12 +28408,14 @@ functions which called the one you are in.  The commands for doing this are:
 @cindex debugger commands, @code{backtrace}
 @cindex @code{backtrace} debugger command
 @cindex @code{bt} debugger command (alias for @code{backtrace})
+@cindex call stack, display in debugger
+@cindex traceback, display in debugger
 @item @code{backtrace} [@var{count}]
 @itemx @code{bt} [@var{count}]
 Print a backtrace of all function calls (stack frames), or innermost @var{count}
 frames if @var{count} > 0. Print the outermost @var{count} frames if
 @var{count} < 0.  The backtrace displays the name and arguments to each
-function, the source file name, and the line number.
+function, the source @value{FN}, and the line number.
 
 @cindex debugger commands, @code{down}
 @cindex @code{down} debugger command
@@ -26844,10 +28429,11 @@ Then select and print the frame.
 @cindex @code{f} debugger command (alias for @code{frame})
 @item @code{frame} [@var{n}]
 @itemx @code{f} [@var{n}]
-Select and print (frame number, function and argument names, source file,
-and the source line) stack frame @var{n}. Frame 0 is the currently executing,
-or @dfn{innermost}, frame (function call), frame 1 is the frame that called the
-innermost one. The highest numbered frame is the one for the main program.
+Select and print stack frame @var{n}.  Frame 0 is the currently executing,
+or @dfn{innermost}, frame (function call), frame 1 is the frame that
+called the innermost one. The highest numbered frame is the one for the
+main program.  The printed information consists of the frame number,
+function and argument names, source file, and the source line.
 
 @cindex debugger commands, @code{up}
 @cindex @code{up} debugger command
@@ -26878,25 +28464,32 @@ The value for @var{what} should be one of the following:
 @c nested table
 @table @code
 @item args
+@cindex show function arguments, in debugger
 Arguments of the selected frame.
 
 @item break
+@cindex show breakpoints
 List all currently set breakpoints.
 
 @item display
+@cindex automatic displays, in debugger
 List all items in the automatic display list.
 
 @item frame
+@cindex describe call stack frame, in debugger
 Description of the selected stack frame.
 
 @item functions
-List all function definitions including source file names and
+@cindex list function definitions, in debugger
+List all function definitions including source @value{FN}s and
 line numbers.
 
 @item locals
+@cindex show local variables, in debugger
 Local variables of the selected frame.
 
 @item source
+@cindex show name of current source file, in debugger
 The name of the current source file. Each time the program stops, the
 current source file is the file containing the current instruction.
 When the debugger first starts, the current source file is the first file
@@ -26905,12 +28498,15 @@ included via the @option{-f} option. The
 be used at any time to change the current source.
 
 @item sources
+@cindex show all source files, in debugger
 List all program sources.
 
 @item variables
+@cindex list all global variables, in debugger
 List all global variables.
 
 @item watch
+@cindex show watchpoints
 List all items in the watch list.
 @end table
 @end table
@@ -26924,6 +28520,8 @@ from a file.  The commands are:
 @cindex debugger commands, @code{option}
 @cindex @code{option} debugger command
 @cindex @code{o} debugger command (alias for @code{option})
+@cindex display debugger options
+@cindex debugger options
 @item @code{option} [@var{name}[@code{=}@var{value}]]
 @itemx @code{o} [@var{name}[@code{=}@var{value}]]
 Without an argument, display the available debugger options
@@ -26933,40 +28531,49 @@ a new value to the named option.
 The available options are:
 
 @c nested table
-@table @code
-@item history_size
+@c asis for docbook
+@table @asis
+@item @code{history_size}
+@cindex debugger history size
 The maximum number of lines to keep in the history file @file{./.gawk_history}.
 The default is 100.
 
-@item listsize
+@item @code{listsize}
+@cindex debugger default list amount
 The number of lines that @code{list} prints. The default is 15.
 
-@item outfile
+@item @code{outfile}
+@cindex redirect @command{gawk} output, in debugger
 Send @command{gawk} output to a file; debugger output still goes
 to standard output. An empty string (@code{""}) resets output to
 standard output.
 
-@item prompt
+@item @code{prompt}
+@cindex debugger prompt
 The debugger prompt. The default is @samp{@w{gawk> }}.
 
-@item save_history @r{[}on @r{|} off@r{]}
+@item @code{save_history} [@code{on} | @code{off}]
+@cindex debugger history file
 Save command history to file @file{./.gawk_history}.
 The default is @code{on}.
 
-@item save_options @r{[}on @r{|} off@r{]}
+@item @code{save_options} [@code{on} | @code{off}]
+@cindex save debugger options
 Save current options to file @file{./.gawkrc} upon exit.
 The default is @code{on}.
 Options are read back in to the next session upon startup.
 
-@item trace @r{[}on @r{|} off@r{]}
+@item @code{trace} [@code{on} | @code{off}]
+@cindex instruction tracing, in debugger
 Turn instruction tracing on or off. The default is @code{off}.
 @end table
 
 @item @code{save} @var{filename}
-Save the commands from the current session to the given file name,
+Save the commands from the current session to the given @value{FN},
 so that they can be replayed using the @command{source} command.
 
 @item @code{source} @var{filename}
+@cindex debugger, read commands from a file
 Run command(s) from a file; an error in any command does not
 terminate execution of subsequent commands. Comments (lines starting
 with @samp{#}) are allowed in a command file.
@@ -27002,7 +28609,7 @@ partial dump of Davide Brini's obfuscated code
 
 @smallexample
 gawk> @kbd{dump}
-@print{} 	# BEGIN
+@print{}        # BEGIN
 @print{} 
 @print{} [     1:0xfcd340] Op_rule             : [in_rule = BEGIN] [source_file = brini.awk]
 @print{} [     1:0xfcc240] Op_push_i           : "~" [MALLOC|STRING|STRCUR]
@@ -27065,8 +28672,8 @@ about the command @var{command}.
 @cindex debugger commands, @code{list}
 @cindex @code{list} debugger command
 @cindex @code{l} debugger command (alias for @code{list})
-@item @code{list} [@code{-} | @code{+} | @var{n} | @var{filename@code{:}n} | @var{n}--@var{m} | @var{function}]
-@itemx @code{l} [@code{-} | @code{+} | @var{n} | @var{filename@code{:}n} | @var{n}--@var{m} | @var{function}]
+@item @code{list} [@code{-} | @code{+} | @var{n} | @var{filename}@code{:}@var{n} | @var{n}--@var{m} | @var{function}]
+@itemx @code{l} [@code{-} | @code{+} | @var{n} | @var{filename}@code{:}@var{n} | @var{n}--@var{m} | @var{function}]
 Print the specified lines (default 15) from the current source file
 or the file named @var{filename}. The possible arguments to @code{list}
 are as follows:
@@ -27086,7 +28693,7 @@ Print lines centered around line number @var{n}.
 @item  @var{n}--@var{m}
 Print lines from @var{n} to @var{m}.
 
-@item @var{filename@code{:}n}
+@item @var{filename}@code{:}@var{n}
 Print lines centered around line number @var{n} in
 source file @var{filename}. This command may change the current source file.
 
@@ -27099,6 +28706,7 @@ function @var{function}. This command may change the current source file.
 @cindex debugger commands, @code{quit}
 @cindex @code{quit} debugger command
 @cindex @code{q} debugger command (alias for @code{quit})
+@cindex exit the debugger
 @item @code{quit}
 @itemx @code{q}
 Exit the debugger.  Debugging is great fun, but sometimes we all have
@@ -27109,7 +28717,7 @@ running a program, the debugger warns you if you accidentally type
 
 @cindex debugger commands, @code{trace}
 @cindex @code{trace} debugger command
-@item @code{trace} @code{on} @r{|} @code{off}
+@item @code{trace} [@code{on} | @code{off}]
 Turn on or off a continuous printing of instructions which are about to
 be executed, along with printing the @command{awk} line which they
 implement.  The default is @code{off}.
@@ -27122,17 +28730,21 @@ fairly self-explanatory, and using @code{stepi} and @code{nexti} while
 
 @node Readline Support
 @section Readline Support
+@cindex command completion, in debugger
+@cindex history expansion, in debugger
 
-If @command{gawk} is compiled with the @code{readline} library, you
-can take advantage of that library's command completion and history expansion
-features. The following types of completion are available:
+If @command{gawk} is compiled with
+@uref{http://cnswww.cns.cwru.edu/php/chet/readline/readline.html,
+the @code{readline} library}, you can take advantage of that library's
+command completion and history expansion features. The following types
+of completion are available:
 
 @table @asis
 @item Command completion
 Command names.
 
-@item Source file name completion
-Source file names. Relevant commands are
+@item Source @value{FN} completion
+Source @value{FN}s. Relevant commands are
 @code{break},
 @code{clear},
 @code{list},
@@ -27162,7 +28774,7 @@ We hope you find the @command{gawk} debugger useful and enjoyable to work with,
 but as with any program, especially in its early releases, it still has
 some limitations.  A few which are worth being aware of are:
 
-@itemize @bullet{}
+@itemize @value{BULLET}
 @item
 At this point, the debugger does not give a detailed explanation of
 what you did wrong when you type in something it doesn't like. Rather, it just
@@ -27175,9 +28787,10 @@ If you perused the dump of opcodes in @ref{Miscellaneous Debugger Commands},
 you will realize that much of the internal manipulation of data
 in @command{gawk}, as in many interpreters, is done on a stack.
 @code{Op_push}, @code{Op_pop}, etc., are the ``bread and butter'' of
-most @command{gawk} code.  Unfortunately, as of now, the @command{gawk}
-debugger does not allow you to examine the stack's contents.
+most @command{gawk} code.
 
+Unfortunately, as of now, the @command{gawk}
+debugger does not allow you to examine the stack's contents.
 That is, the intermediate results of expression evaluation are on the
 stack, but cannot be printed.  Rather, only variables which are defined
 in the program can be printed.  Of course, a workaround for
@@ -27204,433 +28817,329 @@ The @command{gawk} debugger only accepts source supplied with the @option{-f} op
 Look forward to a future release when these and other missing features may
 be added, and of course feel free to try to add them yourself!
 
+@node Debugging Summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Programs rarely work correctly the first time.  Finding bugs
+is @dfn{debugging} and a program that helps you find bugs is a
+@dfn{debugger}.  @command{gawk} has a built-in debugger that works very
+similarly to the GNU Debugger, GDB.
+
+@item
+Debuggers let you step through your program one statement at a time,
+examine and change variable and array values, and do a number of other
+things that let understand what your program is actually doing (as
+opposed to what it is supposed to do).
+
+@item
+Like most debuggers, the @command{gawk} debugger works in terms of stack
+frames, and lets you set both breakpoints (stop at a point in the code)
+and watchpoints (stop when a data value changes).
+
+@item
+The debugger command set is fairly complete, providing control over
+breakpoints, execution, viewing and changing data, working with the stack,
+getting information, and other tasks.
+
+@item
+If the @code{readline} library is available when @command{gawk} is
+compiled, it is used by the debugger to provide command-line history
+and editing.
+
+@end itemize
+
 @node Arbitrary Precision Arithmetic
 @chapter Arithmetic and Arbitrary Precision Arithmetic with @command{gawk}
 @cindex arbitrary precision
 @cindex multiple precision
 @cindex infinite precision
-@cindex floating-point numbers, arbitrary precision
-@cindex MPFR
-@cindex GMP
-
-@cindex Knuth, Donald
-@quotation
-@i{There's a credibility gap: We don't know how much of the computer's answers
-to believe. Novice computer users solve this problem by implicitly trusting
-in the computer as an infallible authority; they tend to believe that all
-digits of a printed answer are significant. Disillusioned computer users have
-just the opposite approach; they are constantly afraid that their answers
-are almost meaningless.}@footnote{Donald E.@: Knuth.
-@cite{The Art of Computer Programming}. Volume 2,
-@cite{Seminumerical Algorithms}, third edition,
-1998, ISBN 0-201-89683-4, p.@: 229.}
-@author Donald Knuth
-@end quotation
-
-This @value{CHAPTER} discusses issues that you may encounter
-when performing arithmetic.  It begins by discussing some of
-the general attributes of computer arithmetic, along with how
-this can influence what you see when running @command{awk} programs.
-This discussion applies to all versions of @command{awk}.
-
-The @value{CHAPTER} then moves on to describe @dfn{arbitrary precision
-arithmetic}, a feature which is specific to @command{gawk}.
+@cindex floating-point, numbers@comma{} arbitrary precision
+
+This @value{CHAPTER} introduces some basic concepts relating to
+how computers do arithmetic and briefly lists the features in
+@command{gawk} for performing arbitrary precision floating point
+computations.  It then proceeds to describe floating-point arithmetic,
+which is what @command{awk} uses for all its computations, including a
+discussion of arbitrary precision floating point arithmetic, which is
+a feature available only in @command{gawk}. It continues on to present
+arbitrary precision integers, and concludes with a description of some
+points where @command{gawk} and the POSIX standard are not quite in
+agreement.
 
 @menu
-* General Arithmetic::          An introduction to computer arithmetic.
-* Floating-point Programming::  Effective Floating-point Programming.
-* Gawk and MPFR::               How @command{gawk} provides
-                                arbitrary-precision arithmetic.
-* Arbitrary Precision Floats::  Arbitrary Precision Floating-point Arithmetic
-                                with @command{gawk}.
-* Arbitrary Precision Integers:: Arbitrary Precision Integer Arithmetic with
-                                @command{gawk}.
+* Computer Arithmetic::           A quick intro to computer math.
+* Math Definitions::              Defining terms used.
+* MPFR features::                 The MPFR features in @command{gawk}.
+* FP Math Caution::               Things to know.
+* Arbitrary Precision Integers::  Arbitrary Precision Integer Arithmetic with
+                                  @command{gawk}.
+* POSIX Floating Point Problems:: Standards Versus Existing Practice.
+* Floating point summary::        Summary of floating point discussion.
 @end menu
 
-@node General Arithmetic
+@node Computer Arithmetic
 @section A General Description of Computer Arithmetic
 
-@cindex integers
-@cindex floating-point, numbers
-@cindex numbers, floating-point
-Within computers, there are two kinds of numeric values: @dfn{integers}
-and @dfn{floating-point}.
-In school, integer values were referred to as ``whole'' numbers---that is,
-numbers without any fractional part, such as 1, 42, or @minus{}17.
+Until now, we have worked with data as either numbers or
+strings.  Ultimately, however, computers represent everything in terms
+of @dfn{binary digits}, or @dfn{bits}.  A decimal digit can take on any
+of 10 values: zero through nine.  A binary digit can take on any of two
+values, zero or one.  Using binary, computers (and computer software)
+can represent and manipulate numerical and character data.  In general,
+the more bits you can use to represent a particular thing, the greater
+the range of possible values it can take on.
+
+Modern computers support at least two, and often more, ways to do
+arithmetic.  Each kind of arithmetic uses a different representation
+(organization of the bits) for the numbers.  The kinds of arithmetic
+that interest us are:
+
+@table @asis
+@item Decimal arithmetic
+This is the kind of arithmetic you learned in elementary school, using
+paper and pencil (and/or a calculator). In theory, numbers can have an
+arbitrary number of digits on either side (or both sides) of the decimal
+point, and the results of a computation are always exact.
+
+Some modern system can do decimal arithmetic in hardware, but usually you
+need a special software library to provide access to these instructions.
+There are also libraries that do decimal arithmetic entirely in software.
+
+Despite the fact that some users expect @command{gawk} to be performing
+decimal arithmetic,@footnote{We don't know why they expect this, but
+they do.} it does not do so.
+
+@item Integer arithmetic
+In school, integer values were referred to as ``whole'' numbers---that
+is, numbers without any fractional part, such as 1, 42, or @minus{}17.
 The advantage to integer numbers is that they represent values exactly.
-The disadvantage is that their range is limited.  On most systems,
-this range is @minus{}2,147,483,648 to 2,147,483,647.
-However, many systems now support a range from
-@minus{}9,223,372,036,854,775,808 to 9,223,372,036,854,775,807.
+The disadvantage is that their range is limited.
 
 @cindex unsigned integers
 @cindex integers, unsigned
-Integer values come in two flavors: @dfn{signed} and @dfn{unsigned}.
-Signed values may be negative or positive, with the range of values just
-described.
-Unsigned values are always positive.  On most systems,
-the range is from 0 to 4,294,967,295.
-However, many systems now support a range from
-0 to 18,446,744,073,709,551,615.
-
-@cindex double precision floating-point
-@cindex single precision floating-point
-Floating-point numbers represent what are called ``real'' numbers; i.e.,
-those that do have a fractional part, such as 3.1415927.
-The advantage to floating-point numbers is that they
-can represent a much larger range of values.
-The disadvantage is that there are numbers that they cannot represent
-exactly.
-@command{awk} uses @dfn{double precision} floating-point numbers, which
-can hold more digits than @dfn{single precision}
-floating-point numbers.
-@c Floating-point issues are discussed more fully in
-@c @ref{Floating Point Issues}.
-
-There a several important issues to be aware of, described next.
+In computers, integer values come in two flavors: @dfn{signed} and
+@dfn{unsigned}.  Signed values may be negative or positive, whereas
+unsigned values are always positive (that is, greater than or equal
+to zero).
+
+In computer systems, integer arithmetic is exact, but the possible
+range of values is limited.  Integer arithmetic is generally faster than
+floating point arithmetic.
+
+@item Floating point arithmetic
+Floating-point numbers represent what were called in school ``real''
+numbers; i.e., those that have a fractional part, such as 3.1415927.
+The advantage to floating-point numbers is that they can represent a
+much larger range of values than can integers.  The disadvantage is that
+there are numbers that they cannot represent exactly.
+
+Modern systems support floating point arithmetic in hardware, with a
+limited range of values.  There are software libraries that allow
+the use of arbitrary precision floating point calculations.
+
+POSIX @command{awk} uses @dfn{double precision} floating-point numbers, which
+can hold more digits than @dfn{single precision} floating-point numbers.
+@command{gawk} has facilities for performing arbitrary precision floating
+point arithmetic, which we describe in more detail shortly.
+@end table
 
-@menu
-* Floating Point Issues::       Stuff to know about floating-point numbers.
-* Integer Programming::         Effective integer programming.
-@end menu
+Computers work with integer and floating point values of different
+ranges. Integer values are usually either 32 or 64 bits in size.  Single
+precision floating point values occupy 32 bits, whereas double precision
+floating point values occupy 64 bits.  Floating point values are always
+signed. The possible ranges of values are shown in the following table.
+
+@multitable @columnfractions .34 .33 .33
+@headitem Numeric representation @tab Miniumum value @tab Maximum value
+@item 32-bit signed integer @tab @minus{}2,147,483,648 @tab 2,147,483,647
+@item 32-bit unsigned integer @tab 0 @tab 4,294,967,295
+@item 64-bit signed integer @tab @minus{}9,223,372,036,854,775,808 @tab 9,223,372,036,854,775,807
+@item 64-bit unsigned integer @tab 0 @tab 18,446,744,073,709,551,615
+@item Single precision floating point (approximate) @tab @code{1.175494e-38} @tab @code{3.402823e+38}
+@item Double precision floating point (approximate) @tab @code{2.225074e-308} @tab @code{1.797693e+308}
+@end multitable
 
-@node Floating Point Issues
-@subsection Floating-Point Number Caveats
+@node Math Definitions
+@section Other Stuff To Know
 
-This @value{SECTION} describes some of the issues
-involved in using floating-point numbers.
+The rest of this @value{CHAPTER} uses a number of terms. Here are some
+informal definitions that should help you work your way through the material
+here.
 
-There is a very nice
-@uref{http://www.validlab.com/goldberg/paper.pdf, paper on floating-point arithmetic}
-by David Goldberg,
-``What Every Computer Scientist Should Know About Floating-point Arithmetic,''
-@cite{ACM Computing Surveys} @strong{23}, 1 (1991-03), 5-48.
-This is worth reading if you are interested in the details,
-but it does require a background in computer science.
+@table @dfn
+@item Accuracy
+A floating-point calculation's accuracy is how close it comes
+to the real (paper and pencil) value.
 
-@menu
-* String Conversion Precision:: The String Value Can Lie.
-* Unexpected Results::          Floating Point Numbers Are Not Abstract
-                                Numbers.
-* POSIX Floating Point Problems:: Standards Versus Existing Practice.
-@end menu
+@item Error
+The difference between what the result of a computation ``should be''
+and what it actually is.  It is best to minimize error as much
+as possible.
 
-@node String Conversion Precision
-@subsubsection The String Value Can Lie
+@item Exponent
+The order of magnitude of a value;
+some number of bits in a floating-point value store the exponent.
 
-Internally, @command{awk} keeps both the numeric value
-(double precision floating-point) and the string value for a variable.
-Separately, @command{awk} keeps
-track of what type the variable has
-(@pxref{Typing and Comparison}),
-which plays a role in how variables are used in comparisons.
+@item Inf
+A special value representing infinity. Operations involving another
+number and infinity produce infinity.
 
-It is important to note that the string value for a number may not
-reflect the full value (all the digits) that the numeric value
-actually contains.
-The following program, @file{values.awk}, illustrates this:
+@item NaN
+``Not A Number.'' A special value indicating a result that can't
+happen in real math, but that can happen in floating-point computations.
 
-@example
-@{
-   sum = $1 + $2
-   # see it for what it is
-   printf("sum = %.12g\n", sum)
-   # use CONVFMT
-   a = "<" sum ">"
-   print "a =", a
-   # use OFMT
-   print "sum =", sum
-@}
-@end example
+@item Normalized
+How the significand (see later in this list) is usually stored. The
+value is adjusted so that the first bit is one, and then that leading
+one is assumed instead of physically stored.  This provides one
+extra bit of precision.
 
-@noindent
-This program shows the full value of the sum of @code{$1} and @code{$2}
-using @code{printf}, and then prints the string values obtained
-from both automatic conversion (via @code{CONVFMT}) and
-from printing (via @code{OFMT}).
+@item Precision
+The number of bits used to represent a floating-point number.
+The more bits, the more digits you can represent.
+Binary and decimal precisions are related approximately, according to the
+formula:
 
-Here is what happens when the program is run:
+@display
+@iftex
+@math{prec = 3.322 @cdot dps}
+@end iftex
+@ifnottex
+@ifnotdocbook
+@var{prec} = 3.322 * @var{dps}
+@end ifnotdocbook
+@end ifnottex
+@docbook
+<emphasis>prec</emphasis> = 3.322 &sdot; <emphasis>dps</emphasis> @c
+@end docbook
+@end display
 
-@example
-$ @kbd{echo 3.654321 1.2345678 | awk -f values.awk}
-@print{} sum = 4.8888888
-@print{} a = <4.88889>
-@print{} sum = 4.88889
-@end example
+@noindent
+Here, @var{prec} denotes the binary precision
+(measured in bits) and @var{dps} (short for decimal places)
+is the decimal digits.
+
+@item Rounding mode
+How numbers are rounded up or down when necessary.
+More details are provided later.
+
+@item Significand
+A floating point value consists the significand multiplied by 10
+to the power of the exponent. For example, in @code{1.2345e67},
+the significand is @code{1.2345}.
+
+@item Stability
+From @uref{http://en.wikipedia.org/wiki/Numerical_stability,
+the Wikipedia article on numerical stability}:
+``Calculations that can be proven not to magnify approximation errors
+are called @dfn{numerically stable}.''
+@end table
 
-This makes it clear that the full numeric value is different from
-what the default string representations show.
+See @uref{http://en.wikipedia.org/wiki/Accuracy_and_precision,
+the Wikipedia article on accuracy and precision} for more information
+on some of those terms.
 
-@code{CONVFMT}'s default value is @code{"%.6g"}, which yields a value with
-at most six significant digits.  For some applications, you might want to
-change it to specify more precision.
-On most modern machines, most of the time,
-17 digits is enough to capture a floating-point number's
-value exactly.@footnote{Pathological cases can require up to
-752 digits (!), but we doubt that you need to worry about this.}
+On modern systems, floating-point hardware uses the representation and
+operations defined by the IEEE 754 standard.
+Three of the standard IEEE 754 types are 32-bit single precision,
+64-bit double precision and 128-bit quadruple precision.
+The standard also specifies extended precision formats
+to allow greater precisions and larger exponent ranges.
+(@command{awk} uses only the 64-bit double precision format.)
 
-@node Unexpected Results
-@subsubsection Floating Point Numbers Are Not Abstract Numbers
-
-@cindex floating-point, numbers
-Unlike numbers in the abstract sense (such as what you studied in high school
-or college arithmetic), numbers stored in computers are limited in certain ways.
-They cannot represent an infinite number of digits, nor can they always
-represent things exactly.
-In particular,
-floating-point numbers cannot
-always represent values exactly.  Here is an example:
-
-@example
-$ @kbd{awk '@{ printf("%010d\n", $1 * 100) @}'}
-515.79
-@print{} 0000051579
-515.80
-@print{} 0000051579
-515.81
-@print{} 0000051580
-515.82
-@print{} 0000051582
-@kbd{Ctrl-d}
-@end example
+@ref{table-ieee-formats} lists the precision and exponent
+field values for the basic IEEE 754 binary formats:
 
-@noindent
-This shows that some values can be represented exactly,
-whereas others are only approximated.  This is not a ``bug''
-in @command{awk}, but simply an artifact of how computers
-represent numbers.
+@float Table,table-ieee-formats
+@caption{Basic IEEE Format Context Values}
+@multitable @columnfractions .20 .20 .20 .20 .20
+@headitem Name @tab Total bits @tab Precision @tab emin @tab emax
+@item Single @tab 32 @tab 24 @tab @minus{}126 @tab +127 
+@item Double @tab 64 @tab 53 @tab @minus{}1022 @tab +1023
+@item Quadruple @tab 128 @tab 113 @tab @minus{}16382 @tab +16383
+@end multitable
+@end float
 
 @quotation NOTE
-It cannot be emphasized enough that the behavior just
-described is fundamental to modern computers. You will
-see this kind of thing happen in @emph{any} programming
-language using hardware floating-point numbers. It is @emph{not}
-a bug in @command{gawk}, nor is it something that can be ``just
-fixed.''
+The precision numbers include the implied leading one that gives them
+one extra bit of significand.
 @end quotation
 
-@cindex negative zero
-@cindex positive zero
-@cindex zero@comma{} negative vs.@: positive
-Another peculiarity of floating-point numbers on modern systems
-is that they often have more than one representation for the number zero!
-In particular, it is possible to represent ``minus zero'' as well as
-regular, or ``positive'' zero.
-
-This example shows that negative and positive zero are distinct values
-when stored internally, but that they are in fact equal to each other,
-as well as to ``regular'' zero:
-
-@example
-$ @kbd{gawk 'BEGIN @{ mz = -0 ; pz = 0}
-> @kbd{printf "-0 = %g, +0 = %g, (-0 == +0) -> %d\n", mz, pz, mz == pz}
-> @kbd{printf "mz == 0 -> %d, pz == 0 -> %d\n", mz == 0, pz == 0}
-> @kbd{@}'}
-@print{} -0 = -0, +0 = 0, (-0 == +0) -> 1
-@print{} mz == 0 -> 1, pz == 0 -> 1
-@end example
-
-It helps to keep this in mind should you process numeric data
-that contains negative zero values; the fact that the zero is negative
-is noted and can affect comparisons.
-
-@node POSIX Floating Point Problems
-@subsubsection Standards Versus Existing Practice
-
-Historically, @command{awk} has converted any non-numeric looking string
-to the numeric value zero, when required.  Furthermore, the original
-definition of the language and the original POSIX standards specified that
-@command{awk} only understands decimal numbers (base 10), and not octal
-(base 8) or hexadecimal numbers (base 16).
-
-Changes in the language of the
-2001 and 2004 POSIX standards can be interpreted to imply that @command{awk}
-should support additional features.  These features are:
-
-@itemize @bullet
-@item
-Interpretation of floating point data values specified in hexadecimal
-notation (@samp{0xDEADBEEF}). (Note: data values, @emph{not}
-source code constants.)
+@node MPFR features
+@section Arbitrary Precison Arithmetic Features In @command{gawk}
 
-@item
-Support for the special IEEE 754 floating point values ``Not A Number''
-(NaN), positive Infinity (``inf'') and negative Infinity (``@minus{}inf'').
-In particular, the format for these values is as specified by the ISO 1999
-C standard, which ignores case and can allow machine-dependent additional
-characters after the @samp{nan} and allow either @samp{inf} or @samp{infinity}.
-@end itemize
-
-The first problem is that both of these are clear changes to historical
-practice:
-
-@itemize @bullet
-@item
-The @command{gawk} maintainer feels that supporting hexadecimal floating
-point values, in particular, is ugly, and was never intended by the
-original designers to be part of the language.
-
-@item
-Allowing completely alphabetic strings to have valid numeric
-values is also a very severe departure from historical practice.
-@end itemize
-
-The second problem is that the @code{gawk} maintainer feels that this
-interpretation of the standard, which requires a certain amount of
-``language lawyering'' to arrive at in the first place, was not even
-intended by the standard developers.  In other words, ``we see how you
-got where you are, but we don't think that that's where you want to be.''
-
-Recognizing the above issues, but attempting to provide compatibility
-with the earlier versions of the standard,
-the 2008 POSIX standard added explicit wording to allow, but not require,
-that @command{awk} support hexadecimal floating point values and
-special values for ``Not A Number'' and infinity.
-
-Although the @command{gawk} maintainer continues to feel that
-providing those features is inadvisable,
-nevertheless, on systems that support IEEE floating point, it seems
-reasonable to provide @emph{some} way to support NaN and Infinity values.
-The solution implemented in @command{gawk} is as follows:
-
-@itemize @bullet
-@item
-With the @option{--posix} command-line option, @command{gawk} becomes
-``hands off.'' String values are passed directly to the system library's
-@code{strtod()} function, and if it successfully returns a numeric value,
-that is what's used.@footnote{You asked for it, you got it.}
-By definition, the results are not portable across
-different systems.  They are also a little surprising:
+By default, @command{gawk} uses the double precision floating point values
+supplied by the hardware of the system it runs on.  However, if it was
+compiled to do, @command{gawk} uses the @uref{http://www.mpfr.org, GNU
+MPFR} and @uref{http://gmplib.org, GNU MP} (GMP) libraries for arbitrary
+precision arithmetic on numbers.  You can see if MPFR support is available
+like so:
 
 @example
-$ @kbd{echo nanny | gawk --posix '@{ print $1 + 0 @}'}
-@print{} nan
-$ @kbd{echo 0xDeadBeef | gawk --posix '@{ print $1 + 0 @}'}
-@print{} 3735928559
+$ @kbd{gawk --version}
+@print{} GNU Awk 4.1.1, API: 1.1 (GNU MPFR 3.1.0-p3, GNU MP 5.0.2)
+@print{} Copyright (C) 1989, 1991-2014 Free Software Foundation.
+@dots{}
 @end example
 
-@item
-Without @option{--posix}, @command{gawk} interprets the four strings
-@samp{+inf},
-@samp{-inf},
-@samp{+nan},
-and
-@samp{-nan}
-specially, producing the corresponding special numeric values.
-The leading sign acts a signal to @command{gawk} (and the user)
-that the value is really numeric.  Hexadecimal floating point is
-not supported (unless you also use @option{--non-decimal-data},
-which is @emph{not} recommended). For example:
-
-@example
-$ @kbd{echo nanny | gawk '@{ print $1 + 0 @}'}
-@print{} 0
-$ @kbd{echo +nan | gawk '@{ print $1 + 0 @}'}
-@print{} nan
-$ @kbd{echo 0xDeadBeef | gawk '@{ print $1 + 0 @}'}
-@print{} 0
-@end example
+@noindent
+(You may see different version numbers than what's shown here. That's OK;
+what's important is to see that GNU MPFR and GNU MP are listed in
+the output.)
 
-@command{gawk} does ignore case in the four special values.
-Thus @samp{+nan} and @samp{+NaN} are the same.
-@end itemize
+Additionally, there are a few elements available in the @code{PROCINFO}
+array to provide information about the MPFR and GMP libraries
+(@pxref{Auto-set}).
 
-@node Integer Programming
-@subsection Mixing Integers And Floating-point
-
-As has been mentioned already, @command{awk} uses hardware double
-precision with 64-bit IEEE binary floating-point representation
-for numbers on most systems. A large integer like 9,007,199,254,740,997
-has a binary representation that, although finite, is more than 53 bits long;
-it must also be rounded to 53 bits.
-The biggest integer that can be stored in a C @code{double} is usually the same
-as the largest possible value of a @code{double}. If your system @code{double}
-is an IEEE 64-bit @code{double}, this largest possible value is an integer and
-can be represented precisely.  What more should one know about integers?
-
-If you want to know what is the largest integer, such that it and
-all smaller integers can be stored in 64-bit doubles without losing precision,
-then the answer is
-@iftex
-@math{2^{53}}.
-@end iftex
-@ifnottex
-2^53.
-@end ifnottex
-The next representable number is the even number
-@iftex
-@math{2^{53} + 2},
-@end iftex
-@ifnottex
-2^53 + 2,
-@end ifnottex
-meaning it is unlikely that you will be able to make
-@command{gawk} print
-@iftex
-@math{2^{53} + 1}
-@end iftex
-@ifnottex
-2^53 + 1
-@end ifnottex
-in integer format.
-The range of integers exactly representable by a 64-bit double
-is
-@iftex
-@math{[-2^{53}, 2^{53}]}.
-@end iftex
-@ifnottex
-[@minus{}2^53, 2^53].
-@end ifnottex
-If you ever see an integer outside this range in @command{awk}
-using 64-bit doubles, you have reason to be very suspicious about
-the accuracy of the output. Here is a simple program with erroneous output:
+The MPFR library provides precise control over precisions and rounding
+modes, and gives correctly rounded, reproducible, platform-independent
+results.  With either of the command-line options @option{--bignum} or
+@option{-M}, all floating-point arithmetic operators and numeric functions
+can yield results to any desired precision level supported by MPFR.
 
-@example
-$ @kbd{gawk 'BEGIN @{ i = 2^53 - 1; for (j = 0; j < 4; j++) print i + j @}'}
-@print{} 9007199254740991
-@print{} 9007199254740992
-@print{} 9007199254740992
-@print{} 9007199254740994
-@end example
+Two built-in variables, @code{PREC} and @code{ROUNDMODE},
+provide control over the working precision and the rounding mode.
+The precision and the rounding mode are set globally for every operation
+to follow.
+@xref{Auto-set}, for more information.
 
-The lesson is to not assume that any large integer printed by @command{awk}
-represents an exact result from your computation, especially if it wraps
-around on your screen.
+@node FP Math Caution
+@section Floating Point Arithmetic: Caveat Emptor!
 
-@node Floating-point Programming
-@section Understanding Floating-point Programming
+@quotation
+Math class is tough!
+@author Late 1980's Barbie
+@end quotation
 
-Numerical programming is an extensive area; if you need to develop
-sophisticated numerical algorithms then @command{gawk} may not be
-the ideal tool, and this documentation may not be sufficient.
-It might require digesting a book or two@footnote{One recommended title is
-@cite{Numerical Computing with IEEE Floating Point Arithmetic}, Michael L.@:
-Overton, Society for Industrial and Applied Mathematics, 2004.
-ISBN: 0-89871-482-6, ISBN-13: 978-0-89871-482-1. See
-@uref{http://www.cs.nyu.edu/cs/faculty/overton/book}.}
-to really internalize how to compute
-with ideal accuracy and precision,
-and the result often depends on the particular application.
+This @value{SECTION} provides a high level overview of the issues
+involved when doing lots of floating-point arithmetic.@footnote{There
+is a very nice @uref{http://www.validlab.com/goldberg/paper.pdf,
+paper on floating-point arithmetic} by David Goldberg, ``What Every
+Computer Scientist Should Know About Floating-point Arithmetic,''
+@cite{ACM Computing Surveys} @strong{23}, 1 (1991-03), 5-48.  This is
+worth reading if you are interested in the details, but it does require
+a background in computer science.}
+The discussion applies to both hardware and arbitrary-precision
+floating-point arithmetic.
 
-@quotation NOTE
-A floating-point calculation's @dfn{accuracy} is how close it comes
-to the real value.  This is as opposed to the @dfn{precision}, which
-usually refers to the number of bits used to represent the number
-(see @uref{http://en.wikipedia.org/wiki/Accuracy_and_precision,
-the Wikipedia article} for more information).
+@quotation CAUTION
+The material here is purposely general. If you need to do serious
+computer arithmetic, you should do some research first, and not
+rely just on what we tell you.
 @end quotation
 
-There are two options for doing floating-point calculations:
-hardware floating-point (as used by standard @command{awk} and
-the default for @command{gawk}), and @dfn{arbitrary-precision}
-floating-point, which is software based.
-From this point forward, this @value{CHAPTER}
-aims to provide enough information to understand both, and then
-will focus on @command{gawk}'s facilities for the latter.@footnote{If you
-are interested in other tools that perform arbitrary precision arithmetic,
-you may want to investigate the POSIX @command{bc} tool. See
-@uref{http://pubs.opengroup.org/onlinepubs/009695399/utilities/bc.html,
-the POSIX specification for it}, for more information.}
+@menu
+* Inexactness of computations:: Floating point math is not exact.
+* Getting Accuracy::            Getting more accuracy takes some work.
+* Try To Round::                Add digits and round.
+* Setting precision::           How to set the precision.
+* Setting the rounding mode::   How to set the rounding mode.
+@end menu
+
+@node Inexactness of computations
+@subsection Floating Point Arithmetic Is Not Exact
 
 Binary floating-point representations and arithmetic are inexact.
 Simple values like 0.1 cannot be precisely represented using
@@ -27642,7 +29151,16 @@ floating-point, you can set the precision before starting a computation,
 but then you cannot be sure of the number of significant decimal places
 in the final result.
 
-Sometimes, before you start to write any code, you should think more
+@menu
+* Inexact representation::      Numbers are not exactly represented.
+* Comparing FP Values::         How to compare floating point values.
+* Errors accumulate::           Errors get bigger as they go.
+@end menu
+
+@node Inexact representation
+@subsubsection Many Numbers Cannot Be Represented Exactly
+
+So, before you start to write any code, you should think
 about what you really want and what's really happening. Consider the
 two numbers in the following example:
 
@@ -27672,21 +29190,42 @@ you can always specify how much precision you would like in your output.
 Usually this is a format string like @code{"%.15g"}, which when
 used in the previous example, produces an output identical to the input.
 
+@node Comparing FP Values
+@subsubsection Be Careful Comparing Values
+
 Because the underlying representation can be a little bit off from the exact value,
-comparing floating-point values to see if they are equal is generally not a good idea.
-Here is an example where it does not work like you expect:
+comparing floating-point values to see if they are exactly equal is generally a bad idea.
+Here is an example where it does not work like you would expect:
 
 @example 
 $ @kbd{gawk 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
 @print{} 0
 @end example
 
-The loss of accuracy during a single computation with floating-point numbers
-usually isn't enough to worry about. However, if you compute a value
-which is the result of a sequence of floating point operations,
+The general wisdom when comparing floating-point values is to see if
+they are within some small range of each other (called a @dfn{delta},
+or @dfn{tolerance}).
+You have to decide how small a delta is important to you. Code to do
+this looks something like this:
+
+@example
+delta = 0.00001                 # for example
+difference = abs(a) - abs(b)    # subtract the two values
+if (difference < delta)
+    # all ok
+else
+    # not ok
+@end example
+
+@node Errors accumulate
+@subsubsection Errors Accumulate
+
+The loss of accuracy during a single computation with floating-point
+numbers usually isn't enough to worry about. However, if you compute a
+value which is the result of a sequence of floating point operations,
 the error can accumulate and greatly affect the computation itself.
-Here is an attempt to compute the value of the constant
-@value{PI} using one of its many series representations:
+Here is an attempt to compute the value of @value{PI} using one of its
+many series representations:
 
 @example
 BEGIN @{
@@ -27700,8 +29239,8 @@ BEGIN @{
 @}
 @end example
 
-When run, the early errors propagating through later computations
-cause the loop to terminate prematurely after an attempt to divide by zero.
+When run, the early errors propagate through later computations,
+causing the loop to terminate prematurely after attempting to divide by zero:
 
 @example
 $ @kbd{gawk -f pi.awk}
@@ -27728,23 +29267,88 @@ $ @kbd{gawk 'BEGIN @{}
 @print{} 4
 @end example
 
-Can computation using arbitrary precision help with the previous examples?
-If you are impatient to know, see
-@ref{Exact Arithmetic}.
+@node Getting Accuracy
+@subsection Getting The Accuracy You Need
+
+Can arbitrary precision arithmetic give exact results? There are
+no easy answers. The standard rules of algebra often do not apply
+when using floating-point arithmetic.
+Among other things, the distributive and associative laws
+do not hold completely, and order of operation may be important
+for your computation. Rounding error, cumulative precision loss
+and underflow are often troublesome.
+
+When @command{gawk} tests the expressions @samp{0.1 + 12.2} and
+@samp{12.3} for equality using the machine double precision arithmetic,
+it decides that they are not equal!  (@xref{Comparing FP Values}.)
+You can get the result you want by increasing the precision; 56 bits in
+this case does the job:
+
+@example 
+$ @kbd{gawk -M -v PREC=56 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
+@print{} 1
+@end example
+
+If adding more bits is good, perhaps adding even more bits of
+precision is better?
+Here is what happens if we use an even larger value of @code{PREC}:
+
+@example 
+$ @kbd{gawk -M -v PREC=201 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
+@print{} 0
+@end example
+
+This is not a bug in @command{gawk} or in the MPFR library.
+It is easy to forget that the finite number of bits used to store the value
+is often just an approximation after proper rounding.
+The test for equality succeeds if and only if @emph{all} bits in the two operands
+are exactly the same. Since this is not necessarily true after floating-point
+computations with a particular precision and effective rounding rule,
+a straight test for equality may not work. Instead, compare the
+two numbers to see if they are within the desirable delta of each other.
+
+In applications where 15 or fewer decimal places suffice,
+hardware double precision arithmetic can be adequate, and is usually much faster.
+But you need to keep in mind that every floating-point operation
+can suffer a new rounding error with catastrophic consequences as illustrated
+by our earlier attempt to compute the value of @value{PI}.
+Extra precision can greatly enhance the stability and the accuracy
+of your computation in such cases.
+
+Repeated addition is not necessarily equivalent to multiplication
+in floating-point arithmetic. In the example in
+@ref{Errors accumulate}:
+
+@example
+$ @kbd{gawk 'BEGIN @{}
+>   @kbd{for (d = 1.1; d <= 1.5; d += 0.1)    # loop five times (?)}
+>       @kbd{i++}
+>   @kbd{print i}
+> @kbd{@}'}
+@print{} 4
+@end example
+
+@noindent
+you may or may not succeed in getting the correct result by choosing
+an arbitrarily large value for @code{PREC}. Reformulation of
+the problem at hand is often the correct approach in such situations.
+
+@node Try To Round
+@subsection Try A Few Extra Bits of Precision and Rounding
 
 Instead of arbitrary precision floating-point arithmetic,
 often all you need is an adjustment of your logic
 or a different order for the operations in your calculation.
-The stability and the accuracy of the computation of the constant @value{PI}
+The stability and the accuracy of the computation of @value{PI}
 in the earlier example can be enhanced by using the following
 simple algebraic transformation:
 
 @example
-(sqrt(x * x + 1) - 1) / x = x / (sqrt(x * x + 1) + 1)
+(sqrt(x * x + 1) - 1) / x @equiv{} x / (sqrt(x * x + 1) + 1)
 @end example
 
 @noindent
-After making this, change the program does converge to
+After making this, change the program converges to
 @value{PI} in under 30 iterations:
 
 @example
@@ -27759,340 +29363,22 @@ $ @kbd{gawk -f pi2.awk}
 @print{} 3.141592653589797
 @end example
 
-There is no need to be unduly suspicious about the results from
-floating-point arithmetic. The lesson to remember is that
-floating-point arithmetic is always more complex than arithmetic using
-pencil and paper. In order to take advantage of the power
-of computer floating-point, you need to know its limitations
-and work within them. For most casual use of floating-point arithmetic,
-you will often get the expected result in the end if you simply round
-the display of your final results to the correct number of significant
-decimal digits.
-
-As general advice, avoid presenting numerical data in a manner that
-implies better precision than is actually the case.
-
-@menu
-* Floating-point Representation:: Binary floating-point representation.
-* Floating-point Context::        Floating-point context.
-* Rounding Mode::                 Floating-point rounding mode.
-@end menu
-
-@node Floating-point Representation
-@subsection Binary Floating-point Representation
-@cindex IEEE-754 format
-
-Although floating-point representations vary from machine to machine,
-the most commonly encountered representation is that defined by the
-IEEE 754 Standard. An IEEE-754 format value has three components:
-
-@itemize @bullet
-@item
-A sign bit telling whether the number is positive or negative.
-
-@item
-An @dfn{exponent}, @var{e}, giving its order of magnitude.
-
-@item
-A @dfn{significand}, @var{s},
-specifying the actual digits of the number.
-@end itemize
-
-The value of the
-number is then
-@iftex
-@math{s @cdot 2^e}.
-@end iftex
-@ifnottex
-@var{s * 2^e}.
-@end ifnottex
-The first bit of a non-zero binary significand
-is always one, so the significand in an IEEE-754 format only includes the
-fractional part, leaving the leading one implicit.
-The significand is stored in @dfn{normalized} format,
-which means that the first bit is always a one.
-
-Three of the standard IEEE-754 types are 32-bit single precision,
-64-bit double precision and 128-bit quadruple precision.
-The standard also specifies extended precision formats
-to allow greater precisions and larger exponent ranges.
-
-@node Floating-point Context
-@subsection Floating-point Context
-@cindex context, floating-point
-
-A floating-point @dfn{context} defines the environment for arithmetic operations.
-It governs precision, sets rules for rounding, and limits the range for exponents.
-The context has the following primary components:
-
-@table @dfn
-@item Precision
-Precision of the floating-point format in bits.
-
-@item emax
-Maximum exponent allowed for the format.
-
-@item emin
-Minimum exponent allowed for the format.
-
-@item Underflow behavior
-The format may or may not support gradual underflow.
-
-@item Rounding
-The rounding mode of the context.
-@end table
-
-@ref{table-ieee-formats} lists the precision and exponent
-field values for the basic IEEE-754 binary formats:
-
-@float Table,table-ieee-formats
-@caption{Basic IEEE Format Context Values}
-@multitable @columnfractions .20 .20 .20 .20 .20
-@headitem Name @tab Total bits @tab Precision @tab emin @tab emax
-@item Single @tab 32 @tab 24 @tab @minus{}126 @tab +127 
-@item Double @tab 64 @tab 53 @tab @minus{}1022 @tab +1023
-@item Quadruple @tab 128 @tab 113 @tab @minus{}16382 @tab +16383
-@end multitable
-@end float
-
-@quotation NOTE
-The precision numbers include the implied leading one that gives them
-one extra bit of significand.
-@end quotation
-
-A floating-point context can also determine which signals are treated
-as exceptions, and can set rules for arithmetic with special values.
-Please consult the IEEE-754 standard or other resources for details.
-
-@command{gawk} ordinarily uses the hardware double precision
-representation for numbers.  On most systems, this is IEEE-754
-floating-point format, corresponding to 64-bit binary with 53 bits
-of precision.
-
-@quotation NOTE
-In case an underflow occurs, the standard allows, but does not require,
-the result from an arithmetic operation to be a number smaller than
-the smallest nonzero normalized number. Such numbers do
-not have as many significant digits as normal numbers, and are called
-@dfn{denormals} or @dfn{subnormals}. The alternative, simply returning a zero,
-is called @dfn{flush to zero}. The basic IEEE-754 binary formats
-support subnormal numbers.
-@end quotation
-
-@node Rounding Mode
-@subsection Floating-point Rounding Mode
-@cindex rounding mode, floating-point
-
-The @dfn{rounding mode} specifies the behavior for the results of numerical
-operations when discarding extra precision. Each rounding mode indicates
-how the least significant returned digit of a rounded result is to
-be calculated.
-@ref{table-rounding-modes} lists the IEEE-754 defined
-rounding modes:
-
-@float Table,table-rounding-modes
-@caption{IEEE 754 Rounding Modes}
-@multitable @columnfractions .45 .55
-@headitem Rounding Mode @tab IEEE Name
-@item Round to nearest, ties to even @tab @code{roundTiesToEven}
-@item Round toward plus Infinity @tab @code{roundTowardPositive}
-@item Round toward negative Infinity @tab @code{roundTowardNegative}
-@item Round toward zero @tab @code{roundTowardZero}
-@item Round to nearest, ties away from zero @tab @code{roundTiesToAway}
-@end multitable
-@end float
-
-The default mode @code{roundTiesToEven} is the most preferred,
-but the least intuitive. This method does the obvious thing for most values,
-by rounding them up or down to the nearest digit.
-For example, rounding 1.132 to two digits yields 1.13,
-and rounding 1.157 yields 1.16.
-
-However, when it comes to rounding a value that is exactly halfway between,
-things do not work the way you probably learned in school.
-In this case, the number is rounded to the nearest even digit.
-So rounding 0.125 to two digits rounds down to 0.12,
-but rounding 0.6875 to three digits rounds up to 0.688.
-You probably have already encountered this rounding mode when
-using @code{printf} to format floating-point numbers.
-For example:
-
-@example
-BEGIN @{
-    x = -4.5
-    for (i = 1; i < 10; i++) @{
-        x += 1.0
-        printf("%4.1f => %2.0f\n", x, x)
-    @}
-@}
-@end example
-
-@noindent
-produces the following output when run on the author's system:@footnote{It
-is possible for the output to be completely different if the
-C library in your system does not use the IEEE-754 even-rounding
-rule to round halfway cases for @code{printf}.}
-
-@example
--3.5 => -4
--2.5 => -2
--1.5 => -2
--0.5 => 0
- 0.5 => 0
- 1.5 => 2
- 2.5 => 2
- 3.5 => 4
- 4.5 => 4
-@end example
-
-The theory behind the rounding mode @code{roundTiesToEven} is that
-it more or less evenly distributes upward and downward rounds
-of exact halves, which might cause any round-off error
-to cancel itself out. This is the default rounding mode used
-in IEEE-754 computing functions and operators.
-
-The other rounding modes are rarely used.
-Round toward positive infinity (@code{roundTowardPositive})
-and round toward negative infinity (@code{roundTowardNegative})
-are often used to implement interval arithmetic,
-where you adjust the rounding mode to calculate upper and lower bounds
-for the range of output. The @code{roundTowardZero}
-mode can be used for converting floating-point numbers to integers.
-The rounding mode @code{roundTiesToAway} rounds the result to the
-nearest number and selects the number with the larger magnitude
-if a tie occurs.
-
-Some numerical analysts will tell you that your choice of rounding style
-has tremendous impact on the final outcome, and advise you to wait until
-final output for any rounding. Instead, you can often avoid round-off error problems by
-setting the precision initially to some value sufficiently larger than
-the final desired precision, so that the accumulation of round-off error
-does not influence the outcome.
-If you suspect that results from your computation are
-sensitive to accumulation of round-off error,
-one way to be sure is to look for a significant difference in output
-when you change the rounding mode.
-
-@node Gawk and MPFR
-@section @command{gawk} + MPFR = Powerful Arithmetic
-
-The rest of this @value{CHAPTER} describes how to use the arbitrary precision
-(also known as @dfn{multiple precision} or @dfn{infinite precision}) numeric
-capabilities in @command{gawk} to produce maximally accurate results
-when you need it.
-
-But first you should check if your version of
-@command{gawk} supports arbitrary precision arithmetic.
-The easiest way to find out is to look at the output of
-the following command:
-
-@example
-$ @kbd{gawk --version}
-@print{} GNU Awk 4.1.0, API: 1.0 (GNU MPFR 3.1.0-p3, GNU MP 5.0.2)
-@print{} Copyright (C) 1989, 1991-2013 Free Software Foundation.
-@dots{}
-@end example
-
-@command{gawk} uses the
-@uref{http://www.mpfr.org, GNU MPFR}
-and
-@uref{http://gmplib.org, GNU MP} (GMP)
-libraries for arbitrary precision
-arithmetic on numbers. So if you do not see the names of these libraries
-in the output, then your version of @command{gawk} does not support
-arbitrary precision arithmetic.
-
-Additionally,
-there are a few elements available in the @code{PROCINFO} array
-to provide information about the MPFR and GMP libraries.
-@xref{Auto-set}, for more information.
-
-@ignore
-Even if you aren't interested in arbitrary precision arithmetic, you
-may still benefit from knowing about how @command{gawk} handles numbers
-in general, and the limitations of doing arithmetic with ordinary
-@command{gawk} numbers.
-@end ignore
-
-
-@node Arbitrary Precision Floats
-@section Arbitrary Precision Floating-point Arithmetic with @command{gawk}
-
-@command{gawk} uses the GNU MPFR library
-for arbitrary precision floating-point arithmetic.  The MPFR library
-provides precise control over precisions and rounding modes, and gives
-correctly rounded, reproducible, platform-independent results.  With one
-of the command-line options @option{--bignum} or @option{-M},
-all floating-point arithmetic operators and numeric functions can yield
-results to any desired precision level supported by MPFR.
-Two built-in variables, @code{PREC} and @code{ROUNDMODE},
-provide control over the working precision and the rounding mode
-(@pxref{Setting Precision}, and
-@pxref{Setting Rounding Mode}).
-The precision and the rounding mode are set globally for every operation
-to follow.
-
-The default working precision for arbitrary precision floating-point values is
-53 bits, and the default value for @code{ROUNDMODE} is @code{"N"},
-which selects the IEEE-754 @code{roundTiesToEven} rounding mode
-(@pxref{Rounding Mode}).@footnote{The
-default precision is 53 bits, since according to the MPFR documentation,
-the library should be able to exactly reproduce all computations with
-double-precision machine floating-point numbers (@code{double} type
-in C), except the default exponent range is much wider and subnormal
-numbers are not implemented.}
-@command{gawk} uses the default exponent range in MPFR
-@iftex
-(@math{emax = 2^{30} - 1, emin = -emax})
-@end iftex
-@ifnottex
-(@var{emax} = 2^30 @minus{} 1, @var{emin} = @minus{}@var{emax})
-@end ifnottex
-for all floating-point contexts.
-There is no explicit mechanism to adjust the exponent range.
-MPFR does not implement subnormal numbers by default,
-and this behavior cannot be changed in @command{gawk}.
-
-@quotation NOTE
-When emulating an IEEE-754 format (@pxref{Setting Precision}),
-@command{gawk} internally adjusts the exponent range
-to the value defined for the format and also performs computations needed for
-gradual underflow (subnormal numbers).
-@end quotation
-
-@quotation NOTE
-MPFR numbers are variable-size entities, consuming only as much space as
-needed to store the significant digits. Since the performance using MPFR
-numbers pales in comparison to doing arithmetic using the underlying machine
-types, you should consider using only as much precision as needed by
-your program.
-@end quotation
-
-@menu
-* Setting Precision::           Setting the working precision.
-* Setting Rounding Mode::       Setting the rounding mode.
-* Floating-point Constants::    Representing floating-point constants.
-* Changing Precision::          Changing the precision of a number.
-* Exact Arithmetic::            Exact arithmetic with floating-point numbers.
-@end menu
-
-@node Setting Precision
-@subsection Setting the Working Precision
-@cindex @code{PREC} variable
+@node Setting precision
+@subsection Setting The Precision
 
 @command{gawk} uses a global working precision; it does not keep track of
 the precision or accuracy of individual numbers. Performing an arithmetic
 operation or calling a built-in function rounds the result to the current
-working precision. The default working precision is 53 bits, which can be
-modified using the built-in variable @code{PREC}. You can also set the
-value to one of the pre-defined case-insensitive strings
+working precision. The default working precision is 53 bits, which you can
+modify using the built-in variable @code{PREC}. You can also set the
+value to one of the predefined case-insensitive strings
 shown in @ref{table-predefined-precision-strings},
-to emulate an IEEE-754 binary format.
+to emulate an IEEE 754 binary format.
 
 @float Table,table-predefined-precision-strings
-@caption{Predefined precision strings for @code{PREC}}
+@caption{Predefined Precision Strings For @code{PREC}}
 @multitable {@code{"double"}} {12345678901234567890123456789012345}
-@headitem @code{PREC} @tab IEEE-754 Binary Format
+@headitem @code{PREC} @tab IEEE 754 Binary Format
 @item @code{"half"} @tab 16-bit half-precision.
 @item @code{"single"} @tab Basic 32-bit single precision.
 @item @code{"double"} @tab Basic 64-bit double precision.
@@ -28111,49 +29397,34 @@ $ @kbd{gawk -M -v PREC=100 'BEGIN @{ x = 1.0e-400; print x + 0}
 @print{} 0
 @end example
 
-Binary and decimal precisions are related approximately, according to the
-formula:
+@quotation CAUTION
+Be wary of floating-point constants! When reading a floating-point
+constant from program source code, @command{gawk} uses the default
+precision (that of a C @code{double}), unless overridden by an assignment
+to the special variable @code{PREC} on the command line, to store it
+internally as a MPFR number.  Changing the precision using @code{PREC}
+in the program text does @emph{not} change the precision of a constant.
+
+If you need to represent a floating-point constant at a higher precision
+than the default and cannot use a command line assignment to @code{PREC},
+you should either specify the constant as a string, or as a rational
+number, whenever possible. The following example illustrates the
+differences among various ways to print a floating-point constant:
+@end quotation
 
-@iftex
-@math{prec = 3.322 @cdot dps}
-@end iftex
-@ifnottex
-@var{prec} = 3.322 * @var{dps}
-@end ifnottex
+@example
+$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 0.1) @}'}
+@print{} 0.1000000000000000055511151 
+$ @kbd{gawk -M -v PREC=113 'BEGIN @{ printf("%0.25f\n", 0.1) @}'}
+@print{} 0.1000000000000000000000000
+$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", "0.1") @}'}
+@print{} 0.1000000000000000000000000
+$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 1/10) @}'}
+@print{} 0.1000000000000000000000000
+@end example
 
-@noindent
-Here, @var{prec} denotes the binary precision
-(measured in bits) and @var{dps} (short for decimal places)
-is the decimal digits. We can easily calculate how many decimal
-digits the 53-bit significand of an IEEE double is equivalent to:
-53 / 3.322 which is equal to about 15.95.
-But what does 15.95 digits actually mean? It depends whether you are
-concerned about how many digits you can rely on, or how many digits
-you need.
-
-It is important to know how many bits it takes to uniquely identify
-a double-precision value (the C type @code{double}).  If you want to
-convert from @code{double} to decimal and back to @code{double} (e.g.,
-saving a @code{double} representing an intermediate result to a file, and
-later reading it back to restart the computation), then a few more decimal
-digits are required. 17 digits is generally enough for a @code{double}.
-
-It can also be important to know what decimal numbers can be uniquely
-represented with a @code{double}. If you want to convert
-from decimal to @code{double} and back again, 15 digits is the most that
-you can get. Stated differently, you should not present
-the numbers from your floating-point computations with more than 15
-significant digits in them.
-
-Conversely, it takes a precision of 332 bits to hold an approximation
-of the constant @value{PI} that is accurate to 100 decimal places.
-
-You should always add some extra bits in order to avoid the confusing round-off
-issues that occur because numbers are stored internally in binary.
-
-@node Setting Rounding Mode
-@subsection Setting the Rounding Mode
-@cindex @code{ROUNDMODE} variable
+@node Setting the rounding mode
+@subsection Setting The Rounding Mode
 
 The @code{ROUNDMODE} variable provides
 program level control over the rounding mode.
@@ -28172,190 +29443,104 @@ rounding modes is shown in @ref{table-gawk-rounding-modes}.
 @end multitable
 @end float
 
-@code{ROUNDMODE} has the default value @code{"N"},
-which selects the IEEE-754 rounding mode @code{roundTiesToEven}.
-In @ref{table-gawk-rounding-modes}, @code{"A"} is listed to select the IEEE-754 mode
-@code{roundTiesToAway}.  This is only available
-if your version of the MPFR library supports it; otherwise setting
-@code{ROUNDMODE} to this value has no effect. @xref{Rounding Mode},
-for the meanings of the various rounding modes.
-
-Here is an example of how to change the default rounding behavior of
-@code{printf}'s output:
-
-@example
-$ @kbd{gawk -M -v ROUNDMODE="Z" 'BEGIN @{ printf("%.2f\n", 1.378) @}'}
-@print{} 1.37
-@end example
-
-@node Floating-point Constants
-@subsection Representing Floating-point Constants
-@cindex constants, floating-point
-
-Be wary of floating-point constants! When reading a floating-point constant
-from program source code, @command{gawk} uses the default precision,
-unless overridden
-by an assignment to the special variable @code{PREC} on the command
-line, to store it internally as a MPFR number.
-Changing the precision using @code{PREC} in the program text does
-@emph{not} change the precision of a constant. If you need to
-represent a floating-point constant at a higher precision than the
-default and cannot use a command line assignment to @code{PREC},
-you should either specify the constant as a string, or 
-as a rational number, whenever possible. The following example
-illustrates the differences among various ways to
-print a floating-point constant:
-
-@example
-$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 0.1) @}'}
-@print{} 0.1000000000000000055511151 
-$ @kbd{gawk -M -v PREC=113 'BEGIN @{ printf("%0.25f\n", 0.1) @}'}
-@print{} 0.1000000000000000000000000
-$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", "0.1") @}'}
-@print{} 0.1000000000000000000000000
-$ @kbd{gawk -M 'BEGIN @{ PREC = 113; printf("%0.25f\n", 1/10) @}'}
-@print{} 0.1000000000000000000000000
-@end example
-
-In the first case, the number is stored with the default precision of 53 bits.
+@code{ROUNDMODE} has the default value @code{"N"}, which
+selects the IEEE 754 rounding mode @code{roundTiesToEven}.
+In @ref{table-gawk-rounding-modes}, the value @code{"A"} selects
+@code{roundTiesToAway}.  This is only available if your version of the
+MPFR library supports it; otherwise setting @code{ROUNDMODE} to @code{"A"}
+has no effect.
 
-@node Changing Precision
-@subsection Changing the Precision of a Number
-
-@cindex Laurie, Dirk
-@quotation
-@i{The point is that in any variable-precision package,
-a decision is made on how to treat numbers given as data,
-or arising in intermediate results, which are represented in
-floating-point format to a precision lower than working precision.
-Do we promote them to full membership of the high-precision club,
-or do we treat them and all their associates as second-class citizens?
-Sometimes the first course is proper, sometimes the second, and it takes
-careful analysis to tell which.}@footnote{Dirk Laurie.
-@cite{Variable-precision Arithmetic Considered Perilous --- A Detective Story}.
-Electronic Transactions on Numerical Analysis. Volume 28, pp. 168-173, 2008.}
-@author Dirk Laurie
-@end quotation
+The default mode @code{roundTiesToEven} is the most preferred,
+but the least intuitive. This method does the obvious thing for most values,
+by rounding them up or down to the nearest digit.
+For example, rounding 1.132 to two digits yields 1.13,
+and rounding 1.157 yields 1.16.
 
-@command{gawk} does not implicitly modify the precision of any previously
-computed results when the working precision is changed with an assignment
-to @code{PREC}.  The precision of a number is always the one that was
-used at the time of its creation, and there is no way for the user
-to explicitly change it afterwards. However, since the result of a
-floating-point arithmetic operation is always an arbitrary precision
-floating-point value---with a precision set by the value of @code{PREC}---one of the
-following workarounds effectively accomplishes the desired behavior:
+However, when it comes to rounding a value that is exactly halfway between,
+things do not work the way you probably learned in school.
+In this case, the number is rounded to the nearest even digit.
+So rounding 0.125 to two digits rounds down to 0.12,
+but rounding 0.6875 to three digits rounds up to 0.688.
+You probably have already encountered this rounding mode when
+using @code{printf} to format floating-point numbers.
+For example:
 
 @example
-x = x + 0.0
+BEGIN @{
+    x = -4.5
+    for (i = 1; i < 10; i++) @{
+        x += 1.0
+        printf("%4.1f => %2.0f\n", x, x)
+    @}
+@}
 @end example
 
 @noindent
-or:
-
-@example
-x += 0.0
-@end example
-
-@node Exact Arithmetic
-@subsection Exact Arithmetic with Floating-point Numbers
-
-@quotation CAUTION
-Never depend on the exactness of floating-point arithmetic,
-even for apparently simple expressions!
-@end quotation
-
-Can arbitrary precision arithmetic give exact results? There are
-no easy answers. The standard rules of algebra often do not apply
-when using floating-point arithmetic.
-Among other things, the distributive and associative laws
-do not hold completely, and order of operation may be important
-for your computation. Rounding error, cumulative precision loss
-and underflow are often troublesome.
-
-When @command{gawk} tests the expressions @samp{0.1 + 12.2} and @samp{12.3}
-for equality
-using the machine double precision arithmetic, it decides that they
-are not equal!
-(@xref{Floating-point Programming}.)
-You can get the result you want by increasing the precision;
-56 bits in this case will get the job done:
-
-@example 
-$ @kbd{gawk -M -v PREC=56 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
-@print{} 1
-@end example
-
-If adding more bits is good, perhaps adding even more bits of
-precision is better?
-Here is what happens if we use an even larger value of @code{PREC}:
-
-@example 
-$ @kbd{gawk -M -v PREC=201 'BEGIN @{ print (0.1 + 12.2 == 12.3) @}'}
-@print{} 0
-@end example
-
-This is not a bug in @command{gawk} or in the MPFR library.
-It is easy to forget that the finite number of bits used to store the value
-is often just an approximation after proper rounding.
-The test for equality succeeds if and only if @emph{all} bits in the two operands
-are exactly the same. Since this is not necessarily true after floating-point
-computations with a particular precision and effective rounding rule,
-a straight test for equality may not work. 
-
-So, don't assume that floating-point values can be compared for equality.
-You should also exercise caution when using other forms of comparisons.
-The standard way to compare between floating-point numbers is to determine
-how much error (or @dfn{tolerance}) you will allow in a comparison and
-check to see if one value is within this error range of the other.
-
-In applications where 15 or fewer decimal places suffice,
-hardware double precision arithmetic can be adequate, and is usually much faster.
-But you do need to keep in mind that every floating-point operation
-can suffer a new rounding error with catastrophic consequences as illustrated
-by our earlier attempt to compute the value of the constant @value{PI}
-(@pxref{Floating-point Programming}).
-Extra precision can greatly enhance the stability and the accuracy
-of your computation in such cases.
-
-Repeated addition is not necessarily equivalent to multiplication
-in floating-point arithmetic. In the example in
-@ref{Floating-point Programming}:
+produces the following output when run on the author's system:@footnote{It
+is possible for the output to be completely different if the
+C library in your system does not use the IEEE 754 even-rounding
+rule to round halfway cases for @code{printf}.}
 
 @example
-$ @kbd{gawk 'BEGIN @{}
->   @kbd{for (d = 1.1; d <= 1.5; d += 0.1)    # loop five times (?)}
->       @kbd{i++}
->   @kbd{print i}
-> @kbd{@}'}
-@print{} 4
+-3.5 => -4
+-2.5 => -2
+-1.5 => -2
+-0.5 => 0
+ 0.5 => 0
+ 1.5 => 2
+ 2.5 => 2
+ 3.5 => 4
+ 4.5 => 4
 @end example
 
-@noindent
-you may or may not succeed in getting the correct result by choosing
-an arbitrarily large value for @code{PREC}. Reformulation of
-the problem at hand is often the correct approach in such situations.
+The theory behind @code{roundTiesToEven} is that it more or less evenly
+distributes upward and downward rounds of exact halves, which might
+cause any accumulating round-off error to cancel itself out. This is the
+default rounding mode for IEEE 754 computing functions and operators.
+
+The other rounding modes are rarely used.  Round toward positive infinity
+(@code{roundTowardPositive}) and round toward negative infinity
+(@code{roundTowardNegative}) are often used to implement interval
+arithmetic, where you adjust the rounding mode to calculate upper and
+lower bounds for the range of output. The @code{roundTowardZero} mode can
+be used for converting floating-point numbers to integers.  The rounding
+mode @code{roundTiesToAway} rounds the result to the nearest number and
+selects the number with the larger magnitude if a tie occurs.
+
+Some numerical analysts will tell you that your choice of rounding
+style has tremendous impact on the final outcome, and advise you to
+wait until final output for any rounding. Instead, you can often avoid
+round-off error problems by setting the precision initially to some
+value sufficiently larger than the final desired precision, so that
+the accumulation of round-off error does not influence the outcome.
+If you suspect that results from your computation are sensitive to
+accumulation of round-off error, look for a significant difference in
+output when you change the rounding mode to be sure.
 
 @node Arbitrary Precision Integers
 @section Arbitrary Precision Integer Arithmetic with @command{gawk}
-@cindex integer, arbitrary precision
-
-If one of the options @option{--bignum} or @option{-M} is specified,
-@command{gawk} performs all
-integer arithmetic using GMP arbitrary precision integers.
-Any number that looks like an integer in a program source or data file
-is stored as an arbitrary precision integer.
-The size of the integer is limited only by your computer's memory.
-The current floating-point context has no effect on operations involving integers.
-For example, the following computes
+@cindex integers, arbitrary precision
+@cindex arbitrary precision integers
+
+When given one of the options @option{--bignum} or @option{-M},
+@command{gawk} performs all integer arithmetic using GMP arbitrary
+precision integers.  Any number that looks like an integer in a source
+or @value{DF} is stored as an arbitrary precision integer.  The size
+of the integer is limited only by the available memory.  For example,
+the following computes
 @iftex
 @math{5^{4^{3^{2}}}},
 @end iftex
 @ifnottex
+@ifnotdocbook
 5^4^3^2,
+@end ifnotdocbook
 @end ifnottex
+@docbook
+5<superscript>4<superscript>3<superscript>2</superscript></superscript></superscript>, @c
+@end docbook
 the result of which is beyond the
-limits of ordinary @command{gawk} numbers:
+limits of ordinary hardware double-precision floating point values:
 
 @example
 $ @kbd{gawk -M 'BEGIN @{}
@@ -28367,25 +29552,32 @@ $ @kbd{gawk -M 'BEGIN @{}
 @print{} 62060698786608744707 ... 92256259918212890625
 @end example
 
-If you were to compute the same value using arbitrary precision
-floating-point values instead, the precision needed for correct output
-(using the formula
+If instead you were to compute the same value using arbitrary precision
+floating-point values, the precision needed for correct output (using
+the formula
 @iftex
 @math{prec = 3.322 @cdot dps}),
 would be @math{3.322 @cdot 183231},
 @end iftex
 @ifnottex
+@ifnotdocbook
 @samp{prec = 3.322 * dps}),
 would be 3.322 x 183231,
+@end ifnotdocbook
 @end ifnottex
+@docbook
+<emphasis>prec</emphasis> = 3.322 &sdot; <emphasis>dps</emphasis>),
+would be
+<emphasis>prec</emphasis> = 3.322 &sdot; 183231, @c
+@end docbook
 or 608693.
 
 The result from an arithmetic operation with an integer and a floating-point value
 is a floating-point value with a precision equal to the working precision.
 The following program calculates the eighth term in
 Sylvester's sequence@footnote{Weisstein, Eric W.
-@cite{Sylvester's Sequence}. From MathWorld---A Wolfram Web Resource.
-@url{http://mathworld.wolfram.com/SylvestersSequence.html}}
+@cite{Sylvester's Sequence}. From MathWorld---A Wolfram Web Resource
+@w{(@url{http://mathworld.wolfram.com/SylvestersSequence.html}).}}
 using a recurrence:
 
 @example
@@ -28405,15 +29597,15 @@ floating-point results exactly. You can either increase the precision
 @samp{2.0} with an integer, to perform all computations using integer
 arithmetic to get the correct output.
 
-It will sometimes be necessary for @command{gawk} to implicitly convert an
-arbitrary precision integer into an arbitrary precision floating-point value.
-This is primarily because the MPFR library does not always provide the
-relevant interface to process arbitrary precision integers or mixed-mode
-numbers as needed by an operation or function.
-In such a case, the precision is set to the minimum value necessary
-for exact conversion, and the working precision is not used for this purpose.
-If this is not what you need or want, you can employ a subterfuge
-like this:
+Sometimes @command{gawk} must implicitly convert an arbitrary precision
+integer into an arbitrary precision floating-point value.  This is
+primarily because the MPFR library does not always provide the relevant
+interface to process arbitrary precision integers or mixed-mode numbers
+as needed by an operation or function.  In such a case, the precision is
+set to the minimum value necessary for exact conversion, and the working
+precision is not used for this purpose.  If this is not what you need or
+want, you can employ a subterfuge, and convert the integer to floating
+point first, like this:
 
 @example
 gawk -M 'BEGIN @{ n = 13; print (n + 0.0) % 2.0 @}'
@@ -28426,15 +29618,186 @@ to begin with:
 gawk -M 'BEGIN @{ n = 13.0; print n % 2.0 @}'
 @end example
 
-Note that for the particular example above, there is likely best
+Note that for the particular example above, it is likely best
 to just use the following:
 
 @example
 gawk -M 'BEGIN @{ n = 13; print n % 2 @}'
 @end example
 
+@node POSIX Floating Point Problems
+@section Standards Versus Existing Practice
+
+Historically, @command{awk} has converted any non-numeric looking string
+to the numeric value zero, when required.  Furthermore, the original
+definition of the language and the original POSIX standards specified that
+@command{awk} only understands decimal numbers (base 10), and not octal
+(base 8) or hexadecimal numbers (base 16).
+
+Changes in the language of the
+2001 and 2004 POSIX standards can be interpreted to imply that @command{awk}
+should support additional features.  These features are:
+
+@itemize @value{BULLET}
+@item
+Interpretation of floating point data values specified in hexadecimal
+notation (e.g., @code{0xDEADBEEF}). (Note: data values, @emph{not}
+source code constants.)
+
+@item
+Support for the special IEEE 754 floating point values ``Not A Number''
+(NaN), positive Infinity (``inf'') and negative Infinity (``@minus{}inf'').
+In particular, the format for these values is as specified by the ISO 1999
+C standard, which ignores case and can allow implementation-dependent additional
+characters after the @samp{nan} and allow either @samp{inf} or @samp{infinity}.
+@end itemize
+
+The first problem is that both of these are clear changes to historical
+practice:
+
+@itemize @value{BULLET}
+@item
+The @command{gawk} maintainer feels that supporting hexadecimal floating
+point values, in particular, is ugly, and was never intended by the
+original designers to be part of the language.
+
+@item
+Allowing completely alphabetic strings to have valid numeric
+values is also a very severe departure from historical practice.
+@end itemize
+
+The second problem is that the @code{gawk} maintainer feels that this
+interpretation of the standard, which requires a certain amount of
+``language lawyering'' to arrive at in the first place, was not even
+intended by the standard developers.  In other words, ``we see how you
+got where you are, but we don't think that that's where you want to be.''
+
+Recognizing the above issues, but attempting to provide compatibility
+with the earlier versions of the standard,
+the 2008 POSIX standard added explicit wording to allow, but not require,
+that @command{awk} support hexadecimal floating point values and
+special values for ``Not A Number'' and infinity.
+
+Although the @command{gawk} maintainer continues to feel that
+providing those features is inadvisable,
+nevertheless, on systems that support IEEE floating point, it seems
+reasonable to provide @emph{some} way to support NaN and Infinity values.
+The solution implemented in @command{gawk} is as follows:
+
+@itemize @value{BULLET}
+@item
+With the @option{--posix} command-line option, @command{gawk} becomes
+``hands off.'' String values are passed directly to the system library's
+@code{strtod()} function, and if it successfully returns a numeric value,
+that is what's used.@footnote{You asked for it, you got it.}
+By definition, the results are not portable across
+different systems.  They are also a little surprising:
+
+@example
+$ @kbd{echo nanny | gawk --posix '@{ print $1 + 0 @}'}
+@print{} nan
+$ @kbd{echo 0xDeadBeef | gawk --posix '@{ print $1 + 0 @}'}
+@print{} 3735928559
+@end example
+
+@item
+Without @option{--posix}, @command{gawk} interprets the four strings
+@samp{+inf},
+@samp{-inf},
+@samp{+nan},
+and
+@samp{-nan}
+specially, producing the corresponding special numeric values.
+The leading sign acts a signal to @command{gawk} (and the user)
+that the value is really numeric.  Hexadecimal floating point is
+not supported (unless you also use @option{--non-decimal-data},
+which is @emph{not} recommended). For example:
+
+@example
+$ @kbd{echo nanny | gawk '@{ print $1 + 0 @}'}
+@print{} 0
+$ @kbd{echo +nan | gawk '@{ print $1 + 0 @}'}
+@print{} nan
+$ @kbd{echo 0xDeadBeef | gawk '@{ print $1 + 0 @}'}
+@print{} 0
+@end example
+
+@command{gawk} ignores case in the four special values.
+Thus @samp{+nan} and @samp{+NaN} are the same.
+@end itemize
+
+@node Floating point summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+Most computer arithmetic is done using either integers or floating-point
+values.  The default for @command{awk} is to use double-precision
+floating-point values.
+
+@item
+In the 1980's, Barbie mistakenly said ``Math class is tough!''
+While math isn't tough, floating-point arithmetic isn't the same
+as pencil and paper math, and care must be taken:
+
+@c nested list
+@itemize @value{MINUS}
+@item
+Not all numbers can be represented exactly.
+
+@item
+Comparing values should use a delta, instead of being done directly
+with @samp{==} and @samp{!=}.
+
+@item
+Errors accumulate.
+
+@item
+Operations are not always truly associative or distributive.
+@end itemize
+
+@item
+Increasing the accuracy can help, but it is not a panacea.
+
+@item
+Often, increasing the accuracy and then rounding to the desired
+number of digits produces reasonable results.
+
+@item
+Use either @option{-M} or @option{--bignum} to enable MPFR
+arithmetic. Use @code{PREC} to set the precision in bits, and
+@code{ROUNDMODE} to set the IEEE 754 rounding mode.
+
+@item
+With @option{-M} or @option{--bignum}, @command{gawk} performs
+arbitrary precision integer arithmetic using the GMP library.
+This is faster and more space efficient than using MPFR for
+the same calculations.
+
+@item
+There are several ``dark corners'' with respect to floating-point
+numbers where @command{gawk} disagrees with the POSIX standard.
+It pays to be aware of them.
+
+@item
+Overall, there is no need to be unduly suspicious about the results from
+floating-point arithmetic. The lesson to remember is that floating-point
+arithmetic is always more complex than arithmetic using pencil and
+paper. In order to take advantage of the power of computer floating-point,
+you need to know its limitations and work within them. For most casual
+use of floating-point arithmetic, you will often get the expected result
+if you simply round the display of your final results to the correct number
+of significant decimal digits.
+
+@item
+As general advice, avoid presenting numerical data in a manner that
+implies better precision than is actually the case.
+
+@end itemize
+
 @node Dynamic Extensions
 @chapter Writing Extensions for @command{gawk}
+@cindex dynamically loaded extensions
 
 It is possible to add new functions written in C or C++ to @command{gawk} using
 dynamically loaded libraries. This facility is available on systems
@@ -28464,11 +29827,14 @@ When @option{--sandbox} is specified, extensions are disabled
 * Extension Samples::           The sample extensions that ship with
                                 @code{gawk}.
 * gawkextlib::                  The @code{gawkextlib} project.
+* Extension summary::           Extension summary.
+* Extension Exercises::         Exercises.
 @end menu
 
 @node Extension Intro
 @section Introduction
 
+@cindex plug-in
 An @dfn{extension} (sometimes called a @dfn{plug-in}) is a piece of
 external compiled code that @command{gawk} can load at runtime to
 provide additional functionality, over and above the built-in capabilities
@@ -28488,8 +29854,15 @@ the facilities that the API provides and how to use
 them, and presents a small sample extension.  In addition, it documents
 the sample extensions included in the @command{gawk} distribution,
 and describes the @code{gawkextlib} project.
+@ifclear FOR_PRINT
 @xref{Extension Design}, for a discussion of the extension mechanism
 goals and design.
+@end ifclear
+@ifset FOR_PRINT
+See @uref{http://www.gnu.org/software/gawk/manual/html_node/Extension-Design.html}
+for a discussion of the extension mechanism
+goals and design.
+@end ifset
 
 @node Plugin License
 @section Extension Licensing
@@ -28514,45 +29887,83 @@ Communication between
 @command{gawk} and an extension is two-way.  First, when an extension
 is loaded, it is passed a pointer to a @code{struct} whose fields are
 function pointers.
-This is shown in @ref{load-extension}.
+@ifnotdocbook
+This is shown in @ref{figure-load-extension}.
+@end ifnotdocbook
+@ifdocbook
+This is shown in @inlineraw{docbook, <xref linkend="figure-load-extension"/>}.
+@end ifdocbook
 
-@float Figure,load-extension
+@ifnotdocbook
+@float Figure,figure-load-extension
 @caption{Loading The Extension}
 @c FIXME: One day, it should not be necessary to have two cases,
 @c but rather just the one without the "txt" final argument.
 @c This applies to the other figures as well.
 @ifinfo
-@center @image{api-figure1, , , Loading the extension, txt}
+@center @image{api-figure1, , , Loading The Extension, txt}
 @end ifinfo
 @ifnotinfo
-@center @image{api-figure1, , , Loading the extension}
+@center @image{api-figure1, , , Loading The Extension}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-load-extension" float="0">
+<title>Loading The Extension</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="api-figure1.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 The extension can call functions inside @command{gawk} through these
 function pointers, at runtime, without needing (link-time) access
 to @command{gawk}'s symbols.  One of these function pointers is to a
 function for ``registering'' new built-in functions.
-This is shown in @ref{load-new-function}.
+@ifnotdocbook
+This is shown in @ref{figure-load-new-function}.
+@end ifnotdocbook
+@ifdocbook
+This is shown in @inlineraw{docbook, <xref linkend="figure-load-new-function"/>}.
+@end ifdocbook
 
-@float Figure,load-new-function
+@ifnotdocbook
+@float Figure,figure-load-new-function
 @caption{Loading The New Function}
 @ifinfo
-@center @image{api-figure2, , , Loading the new function, txt}
+@center @image{api-figure2, , , Loading The New Function, txt}
 @end ifinfo
 @ifnotinfo
-@center @image{api-figure2, , , Loading the new function}
+@center @image{api-figure2, , , Loading The New Function}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-load-new-function" float="0">
+<title>Loading The New Function</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="api-figure2.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 In the other direction, the extension registers its new functions
 with @command{gawk} by passing function pointers to the functions that
 provide the new feature (@code{do_chdir()}, for example).  @command{gawk}
 associates the function pointer with a name and can then call it, using a
 defined calling convention.
-This is shown in @ref{call-new-function}.
+@ifnotdocbook
+This is shown in @ref{figure-call-new-function}.
+@end ifnotdocbook
+@ifdocbook
+This is shown in @inlineraw{docbook, <xref linkend="figure-call-new-function"/>}.
+@end ifdocbook
 
-@float Figure,call-new-function
+@ifnotdocbook
+@float Figure,figure-call-new-function
 @caption{Calling The New Function}
 @ifinfo
 @center @image{api-figure3, , , Calling the new function, txt}
@@ -28561,14 +29972,24 @@ This is shown in @ref{call-new-function}.
 @center @image{api-figure3, , , Calling the new function}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-call-new-function" float="0">
+<title>Calling The New Function</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="api-figure3.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 The @code{do_@var{xxx}()} function, in turn, then uses the function
 pointers in the API @code{struct} to do its work, such as updating
 variables or arrays, printing messages, setting @code{ERRNO}, and so on.
 
-Convenience macros in the @file{gawkapi.h} header file make calling
-through the function pointers look like regular function calls so that
-extension code is quite readable and understandable.
+Convenience macros make calling through the function pointers look
+like regular function calls so that extension code is quite readable
+and understandable.
 
 Although all of this sounds somewhat complicated, the result is that
 extension code is quite straightforward to write and to read. You can
@@ -28577,7 +29998,7 @@ Example}) and also the @file{testext.c} code for testing the APIs.
 
 Some other bits and pieces:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The API provides access to @command{gawk}'s @code{do_@var{xxx}} values,
 reflecting command line options, like @code{do_lint}, @code{do_profiling}
@@ -28597,13 +30018,18 @@ happen, but we all know how @emph{that} goes.)
 
 @node Extension API Description
 @section API Description
+@cindex extension API
 
+C or C++ code for an extension must include the header file
+@file{gawkapi.h}, which declares the functions and defines the data
+types used to communicate with @command{gawk}.
 This (rather large) @value{SECTION} describes the API in detail.
 
 @menu
 * Extension API Functions Introduction:: Introduction to the API functions.
 * General Data Types::                   The data types.
 * Requesting Values::                    How to get a value.
+* Memory Allocation Functions::          Functions for allocating memory.
 * Constructor Functions::                Functions for creating values.
 * Registration Functions::               Functions to register things with
                                          @command{gawk}.
@@ -28625,10 +30051,10 @@ by calling through function pointers passed into your extension.
 
 API function pointers are provided for the following kinds of operations:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
-Registrations functions. You may register:
-@itemize @minus
+Registration functions. You may register:
+@itemize @value{MINUS}
 @item
 extension functions,
 @item
@@ -28659,6 +30085,9 @@ Symbol table access: retrieving a global variable, creating one,
 or changing one.
 
 @item
+Allocating, reallocating, and releasing memory.
+
+@item
 Creating and releasing cached values; this provides an
 efficient way to use values for multiple variables and
 can be a big performance win.
@@ -28666,7 +30095,7 @@ can be a big performance win.
 @item
 Manipulating arrays:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 Retrieving, adding, deleting, and modifying elements
 
@@ -28686,7 +30115,7 @@ Flattening an array for easy C style looping over all its indices and elements
 
 Some points about using the API:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The following types and/or macros and/or functions are referenced
 in @file{gawkapi.h}.  For correct use, you must therefore include the
@@ -28695,12 +30124,11 @@ corresponding standard header file @emph{before} including @file{gawkapi.h}:
 @multitable {@code{memset()}, @code{memcpy()}} {@code{<sys/types.h>}}
 @headitem C Entity @tab Header File
 @item @code{EOF} @tab @code{<stdio.h>}
+@item Values for @code{errno} @tab @code{<errno.h>}
 @item @code{FILE} @tab @code{<stdio.h>}
 @item @code{NULL} @tab @code{<stddef.h>}
-@item @code{malloc()} @tab @code{<stdlib.h>}
 @item @code{memcpy()} @tab @code{<string.h>}
 @item @code{memset()} @tab @code{<string.h>}
-@item @code{realloc()} @tab @code{<stdlib.h>}
 @item @code{size_t} @tab @code{<sys/types.h>}
 @item @code{struct stat} @tab @code{<sys/stat.h>}
 @end multitable 
@@ -28712,9 +30140,6 @@ is necessary in order to keep @file{gawkapi.h} clean, instead of becoming
 a portability hodge-podge as can be seen in some parts of
 the @command{gawk} source code.
 
-To pass reasonable integer values for @code{ERRNO}, you will also need to
-include @code{<errno.h>}.
-
 @item
 The @file{gawkapi.h} file may be included more than once without ill effect.
 Doing so, however, is poor coding practice.
@@ -28730,14 +30155,15 @@ does not support this keyword, you should either place
 All pointers filled in by @command{gawk} are to memory
 managed by @command{gawk} and should be treated by the extension as
 read-only.  Memory for @emph{all} strings passed into @command{gawk}
-from the extension @emph{must} come from @code{malloc()} and is managed
-by @command{gawk} from then on.
+from the extension @emph{must} come from calling the API-provided function
+pointers @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()},
+and is managed by @command{gawk} from then on.
 
 @item
 The API defines several simple @code{struct}s that map values as seen
 from @command{awk}.  A value can be a @code{double}, a string, or an
 array (as in multidimensional arrays, or when creating a new array).
-String values maintain both pointer and length since embedded @code{NUL}
+String values maintain both pointer and length since embedded @sc{nul}
 characters are allowed.
 
 @quotation NOTE
@@ -28771,10 +30197,14 @@ the macros as if they were functions.
 @node General Data Types
 @subsection General Purpose Data Types
 
+@cindex Robbins, Arnold
+@cindex Ramey, Chet
 @quotation
 @i{I have a true love/hate relationship with unions.}
 @author Arnold Robbins
+@end quotation
 
+@quotation
 @i{That's the thing about unions: the compiler will arrange things so they
 can accommodate both love and hate.}
 @author Chet Ramey
@@ -28797,9 +30227,9 @@ certain fields in the API data structures unwritable from extension code,
 while allowing @command{gawk} to use them as it needs to.
 
 @item typedef enum awk_bool @{
-@item @ @ @ @ awk_false = 0,
-@item @ @ @ @ awk_true
-@item @} awk_bool_t;
+@itemx @ @ @ @ awk_false = 0,
+@itemx @ @ @ @ awk_true
+@itemx @} awk_bool_t;
 A simple boolean type.
 
 @item typedef struct awk_string @{
@@ -28809,7 +30239,8 @@ A simple boolean type.
 This represents a mutable string. @command{gawk}
 owns the memory pointed to if it supplied
 the value. Otherwise, it takes ownership of the memory pointed to.
-@strong{Such memory must come from @code{malloc()}!}
+@strong{Such memory must come from calling the API-provided function
+pointers @code{api_malloc()}, @code{api_calloc()}, or @code{api_realloc()}!}
 
 As mentioned earlier, strings are maintained using the current
 multibyte encoding.
@@ -28864,7 +30295,7 @@ Scalar values in @command{awk} are either numbers or strings. The
 indicates what is in the @code{union}.
 
 Representing numbers is easy---the API uses a C @code{double}.  Strings
-require more work. Since @command{gawk} allows embedded @code{NUL} bytes
+require more work. Since @command{gawk} allows embedded @sc{nul} bytes
 in string values, a string must be represented as a pair containing a
 data-pointer and length. This is the @code{awk_string_t} type.
 
@@ -28894,8 +30325,11 @@ reading and/or changing the value of one or more scalar variables, you
 can obtain a @dfn{scalar cookie}@footnote{See
 @uref{http://catb.org/jargon/html/C/cookie.html, the ``cookie'' entry in the Jargon file} for a
 definition of @dfn{cookie}, and @uref{http://catb.org/jargon/html/M/magic-cookie.html,
-the ``magic cookie'' entry in the Jargon file} for a nice example. See
-also the entry for ``Cookie'' in the @ref{Glossary}.}
+the ``magic cookie'' entry in the Jargon file} for a nice example.
+@ifclear FOR_PRINT
+See also the entry for ``Cookie'' in the @ref{Glossary}.
+@end ifclear
+}
 object for that variable, and then use
 the cookie for getting the variable's value or for changing the variable's
 value.
@@ -28925,9 +30359,94 @@ print an error message, or reissue the request for the actual
 value type, as appropriate.  This behavior is summarized in
 @ref{table-value-types-returned}.
 
-@ifnotplaintext
+@c FIXME: Try to do this with spans...
+
 @float Table,table-value-types-returned
-@caption{Value Types Returned}
+@caption{API Value Types Returned}
+@docbook
+<informaltable>
+<tgroup cols="2">
+  <colspec colwidth="50*"/><colspec colwidth="50*"/>
+  <thead>
+    <row><entry></entry><entry><para>Type of Actual Value:</para></entry></row>
+  </thead>
+  <tbody>
+    <row><entry></entry><entry></entry></row>
+  </tbody>
+</tgroup>
+<tgroup cols="6">
+  <colspec colwidth="16.6*"/>
+  <colspec colwidth="16.6*"/>
+  <colspec colwidth="19.8*"/>
+  <colspec colwidth="15*"/>
+  <colspec colwidth="15*"/>
+  <colspec colwidth="16.6*"/>
+  <thead>
+    <row>
+      <entry></entry>
+      <entry></entry>
+      <entry><para>String</para></entry>
+      <entry><para>Number</para></entry>
+      <entry><para>Array</para></entry>
+      <entry><para>Undefined</para></entry>
+    </row>
+  </thead>
+  <tbody>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">String</emphasis></para></entry>
+      <entry><para>String</para></entry>
+      <entry><para>String</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">Number</emphasis></para></entry>
+      <entry><para>Number if can be converted, else false</para></entry>
+      <entry><para>Number</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry><para><emphasis role="bold">Type</emphasis></para></entry>
+      <entry><para><emphasis role="bold">Array</emphasis></para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>Array</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry><para><emphasis role="bold">Requested:</emphasis></para></entry>
+      <entry><para><emphasis role="bold">Scalar</emphasis></para></entry>
+      <entry><para>Scalar</para></entry>
+      <entry><para>Scalar</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+    </row>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">Undefined</emphasis></para></entry>
+      <entry><para>String</para></entry>
+      <entry><para>Number</para></entry>
+      <entry><para>Array</para></entry>
+      <entry><para>Undefined</para></entry>
+    </row>
+    <row>
+      <entry></entry>
+      <entry><para><emphasis role="bold">Value Cookie</emphasis></para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para></entry>
+      <entry><para>false</para>
+      </entry><entry><para>false</para></entry>
+    </row>
+  </tbody>
+</tgroup>
+</informaltable>
+@end docbook
+
+@ifnotplaintext
+@ifnotdocbook
 @multitable @columnfractions .50 .50
 @headitem @tab Type of Actual Value:
 @end multitable
@@ -28940,11 +30459,9 @@ value type, as appropriate.  This behavior is summarized in
 @item @tab @b{Undefined} @tab String @tab Number @tab Array @tab Undefined
 @item @tab @b{Value Cookie} @tab false @tab false @tab false @tab false
 @end multitable
-@end float
+@end ifnotdocbook
 @end ifnotplaintext
 @ifplaintext
-@float Table,table-value-types-returned
-@caption{Value Types Returned}
 @example
                         +-------------------------------------------------+
                         |                Type of Actual Value:            |
@@ -28968,60 +30485,62 @@ value type, as appropriate.  This behavior is summarized in
 |           | Cookie    |            |            |           |           |
 +-----------+-----------+------------+------------+-----------+-----------+
 @end example
-@end float
 @end ifplaintext
+@end float
 
-@node Constructor Functions
-@subsection Constructor Functions and Convenience Macros
+@node Memory Allocation Functions
+@subsection Memory Allocation Functions and Convenience Macros
+@cindex allocating memory for extensions
+@cindex extensions, allocating memory
 
-The API provides a number of @dfn{constructor} functions for creating
-string and numeric values, as well as a number of convenience macros.
-This @value{SUBSECTION} presents them all as function prototypes, in
-the way that extension code would use them.
+The API provides a number of @dfn{memory allocation} functions for
+allocating memory that can be passed to @command{gawk}, as well as a number of
+convenience macros.
 
 @table @code
-@item static inline awk_value_t *
-@itemx make_const_string(const char *string, size_t length, awk_value_t *result)
-This function creates a string value in the @code{awk_value_t} variable
-pointed to by @code{result}. It expects @code{string} to be a C string constant
-(or other string data), and automatically creates a @emph{copy} of the data
-for storage in @code{result}. It returns @code{result}.
+@item void *gawk_malloc(size_t size);
+Call @command{gawk}-provided @code{api_malloc()} to allocate storage that may
+be passed to @command{gawk}.
 
-@item static inline awk_value_t *
-@itemx make_malloced_string(const char *string, size_t length, awk_value_t *result)
-This function creates a string value in the @code{awk_value_t} variable
-pointed to by @code{result}. It expects @code{string} to be a @samp{char *}
-value pointing to data previously obtained from @code{malloc()}. The idea here
-is that the data is passed directly to @command{gawk}, which assumes
-responsibility for it. It returns @code{result}.
+@item void *gawk_calloc(size_t nmemb, size_t size);
+Call @command{gawk}-provided @code{api_calloc()} to allocate storage that may
+be passed to @command{gawk}.
 
-@item static inline awk_value_t *
-@itemx make_null_string(awk_value_t *result)
-This specialized function creates a null string (the ``undefined'' value)
-in the @code{awk_value_t} variable pointed to by @code{result}.
-It returns @code{result}.
+@item void *gawk_realloc(void *ptr, size_t size);
+Call @command{gawk}-provided @code{api_realloc()} to allocate storage that may
+be passed to @command{gawk}.
 
-@item static inline awk_value_t *
-@itemx make_number(double num, awk_value_t *result)
-This function simply creates a numeric value in the @code{awk_value_t} variable
-pointed to by @code{result}.
+@item void gawk_free(void *ptr);
+Call @command{gawk}-provided @code{api_free()} to release storage that was
+allocated with @code{gawk_malloc()}, @code{gawk_calloc()} or @code{gawk_realloc()}.
 @end table
 
-Two convenience macros may be used for allocating storage from @code{malloc()}
-and @code{realloc()}. If the allocation fails, they cause @command{gawk} to
-exit with a fatal error message.  They should be used as if they were
+The API has to provide these functions because it is possible
+for an extension to be compiled and linked against a different
+version of the C library than was used for the @command{gawk}
+executable.@footnote{This is more common on MS-Windows systems, but
+can happen on Unix-like systems as well.} If @command{gawk} were
+to use its version of @code{free()} when the memory came from an
+unrelated version of @code{malloc()}, unexpected behavior would
+likely result.
+
+Two convenience macros may be used for allocating storage
+from the API-provided function pointers @code{api_malloc()} and
+@code{api_realloc()}. If the allocation fails, they cause @command{gawk}
+to exit with a fatal error message.  They should be used as if they were
 procedure calls that do not return a value.
 
 @table @code
 @item #define emalloc(pointer, type, size, message) @dots{}
 The arguments to this macro are as follows:
+
 @c nested table
 @table @code
 @item pointer
 The pointer variable to point at the allocated storage.
 
 @item type
-The type of the pointer variable, used to create a cast for the call to @code{malloc()}.
+The type of the pointer variable, used to create a cast for the call to @code{api_malloc()}.
 
 @item size
 The total number of bytes to be allocated.
@@ -29045,13 +30564,51 @@ make_malloced_string(message, strlen(message), & result);
 @end example
 
 @item #define erealloc(pointer, type, size, message) @dots{}
-This is like @code{emalloc()}, but it calls @code{realloc()},
-instead of @code{malloc()}.
+This is like @code{emalloc()}, but it calls @code{api_realloc()},
+instead of @code{api_malloc()}.
 The arguments are the same as for the @code{emalloc()} macro.
 @end table
 
+@node Constructor Functions
+@subsection Constructor Functions
+
+The API provides a number of @dfn{constructor} functions for creating
+string and numeric values, as well as a number of convenience macros.
+This @value{SUBSECTION} presents them all as function prototypes, in
+the way that extension code would use them.
+
+@table @code
+@item static inline awk_value_t *
+@itemx make_const_string(const char *string, size_t length, awk_value_t *result)
+This function creates a string value in the @code{awk_value_t} variable
+pointed to by @code{result}. It expects @code{string} to be a C string constant
+(or other string data), and automatically creates a @emph{copy} of the data
+for storage in @code{result}. It returns @code{result}.
+
+@item static inline awk_value_t *
+@itemx make_malloced_string(const char *string, size_t length, awk_value_t *result)
+This function creates a string value in the @code{awk_value_t} variable
+pointed to by @code{result}. It expects @code{string} to be a @samp{char *}
+value pointing to data previously obtained from the api-provided functions @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()}. The idea here
+is that the data is passed directly to @command{gawk}, which assumes
+responsibility for it. It returns @code{result}.
+
+@item static inline awk_value_t *
+@itemx make_null_string(awk_value_t *result)
+This specialized function creates a null string (the ``undefined'' value)
+in the @code{awk_value_t} variable pointed to by @code{result}.
+It returns @code{result}.
+
+@item static inline awk_value_t *
+@itemx make_number(double num, awk_value_t *result)
+This function simply creates a numeric value in the @code{awk_value_t} variable
+pointed to by @code{result}.
+@end table
+
 @node Registration Functions
 @subsection Registration Functions
+@cindex register extension
+@cindex extension registration
 
 This @value{SECTION} describes the API functions for
 registering parts of your extension with @command{gawk}.
@@ -29096,8 +30653,8 @@ Letter case in function names is significant.
 This is a pointer to the C function that provides the desired
 functionality.
 The function must fill in the result with either a number
-or a string. @command{awk} takes ownership of any string memory.
-As mentioned earlier, string memory @strong{must} come from @code{malloc()}.
+or a string. @command{gawk} takes ownership of any string memory.
+As mentioned earlier, string memory @strong{must} come from the api-provided functions @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()}.
 
 The @code{num_actual_args} argument tells the C function how many
 actual parameters were passed from the calling @command{awk} code.
@@ -29128,7 +30685,7 @@ empty string (@code{""}).  The @code{func} pointer is the address of a
 
 An @dfn{exit callback} function is a function that
 @command{gawk} calls before it exits.
-Such functions are useful if you have general ``clean up'' tasks
+Such functions are useful if you have general ``cleanup'' tasks
 that should be performed in your extension (such as closing data
 base connections or other resource deallocations).
 You can register such
@@ -29138,6 +30695,7 @@ a function with @command{gawk} using the following function.
 @item void awk_atexit(void (*funcp)(void *data, int exit_status),
 @itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ void *arg0);
 The parameters are:
+
 @c nested table
 @table @code
 @item funcp
@@ -29173,6 +30731,7 @@ is invoked with the @option{--version} option.
 
 @node Input Parsers
 @subsubsection Customized Input Parsers
+@cindex customized input parser
 
 By default, @command{gawk} reads text files as its input. It uses the value
 of @code{RS} to find the end of the record, and then uses @code{FS}
@@ -29230,8 +30789,9 @@ A pointer to your @code{@var{XXX}_can_take_file()} function.
 A pointer to your @code{@var{XXX}_take_control_of()} function.
 
 @item awk_const struct input_parser *awk_const next;
-This pointer is used by @command{gawk}.
-The extension cannot modify it.
+This is for use by @command{gawk};
+therefore it is marked @code{awk_const} so that the extension cannot
+modify it.
 @end table
 
 The steps are as follows:
@@ -29278,7 +30838,7 @@ open the file, then @code{fd} will @emph{not} be equal to
 @code{INVALID_HANDLE}. Otherwise, it will.
 
 @item struct stat sbuf;
-If file descriptor is valid, then @command{gawk} will have filled
+If the file descriptor is valid, then @command{gawk} will have filled
 in this structure via a call to the @code{fstat()} system call.
 @end table
 
@@ -29420,7 +30980,9 @@ Register the input parser pointed to by @code{input_parser} with
 
 @node Output Wrappers
 @subsubsection Customized Output Wrappers
+@cindex customized output wrapper
 
+@cindex output wrapper
 An @dfn{output wrapper} is the mirror image of an input parser.
 It allows an extension to take over the output to a file opened
 with the @samp{>} or @samp{>>} I/O redirection operators (@pxref{Redirection}).
@@ -29457,8 +31019,8 @@ as described below, and return true if successful, false otherwise.
 
 @item awk_const struct output_wrapper *awk_const next;
 This is for use by @command{gawk};
-therefore they are marked @code{awk_const} so that the extension cannot
-modify them.
+therefore it is marked @code{awk_const} so that the extension cannot
+modify it.
 @end table
 
 The @code{awk_output_buf_t} structure looks like this:
@@ -29520,7 +31082,7 @@ The @code{@var{XXX}_can_take_file()} function should make a decision based
 upon the @code{name} and @code{mode} fields, and any additional state
 (such as @command{awk} variable values) that is appropriate.
 
-When @command{gawk} calls @code{@var{XXX}_take_control_of()}, it should fill
+When @command{gawk} calls @code{@var{XXX}_take_control_of()}, that function should fill
 in the other fields, as appropriate, except for @code{fp}, which it should just
 use normally.
 
@@ -29534,6 +31096,7 @@ Register the output wrapper pointed to by @code{output_wrapper} with
 
 @node Two-way processors
 @subsubsection Customized Two-way Processors
+@cindex customized two-way processor
 
 A @dfn{two-way processor} combines an input parser and an output wrapper for
 two-way I/O with the @samp{|&} operator (@pxref{Redirection}).  It makes identical
@@ -29560,7 +31123,7 @@ The fields are as follows:
 The name of the two-way processor.
 
 @item awk_bool_t (*can_take_two_way)(const char *name);
-This function returns true if it wants to take over two-way I/O for this filename.
+This function returns true if it wants to take over two-way I/O for this @value{FN}.
 It should not change any state (variable
 values, etc.) within @command{gawk}.
 
@@ -29573,8 +31136,8 @@ This function should fill in the @code{awk_input_buf_t} and
 
 @item awk_const struct two_way_processor *awk_const next;
 This is for use by @command{gawk};
-therefore they are marked @code{awk_const} so that the extension cannot
-modify them.
+therefore it is marked @code{awk_const} so that the extension cannot
+modify it.
 @end table
 
 As with the input parser and output processor, you provide
@@ -29591,6 +31154,8 @@ Register the two-way processor pointed to by @code{two_way_processor} with
 
 @node Printing Messages
 @subsection Printing Messages
+@cindex printing messages from extensions
+@cindex messages from extensions
 
 You can print different kinds of warning messages from your
 extension, as described below.  Note that for these functions,
@@ -29664,6 +31229,7 @@ for more information on creating arrays.
 
 @node Symbol Table Access
 @subsection Symbol Table Access
+@cindex accessing global variables from extensions
 
 Two sets of routines provide access to global variables, and one set
 allows you to create and release cached values.
@@ -29709,6 +31275,13 @@ An extension can look up the value of @command{gawk}'s special variables.
 However, with the exception of the @code{PROCINFO} array, an extension
 cannot change any of those variables.
 
+@quotation NOTE
+It is possible for the lookup of @code{PROCINFO} to fail. This happens if
+the @command{awk} program being run does not reference @code{PROCINFO};
+in this case @command{gawk} doesn't bother to create the array and
+populate it.
+@end quotation
+
 @node Symbol table by cookie
 @subsubsection Variable Access and Update by Cookie
 
@@ -29730,7 +31303,7 @@ Return false if the value cannot be retrieved.
 
 @item awk_bool_t sym_update_scalar(awk_scalar_t cookie, awk_value_t *value);
 Update the value associated with a scalar cookie.  Return false if
-the new value is not one of @code{AWK_STRING} or @code{AWK_NUMBER}.
+the new value is not of type @code{AWK_STRING} or @code{AWK_NUMBER}.
 Here too, the built-in variables may not be updated.
 @end table
 
@@ -29835,7 +31408,7 @@ assign those values to variables using @code{sym_update()}
 or @code{sym_update_scalar()}, as you like.
 
 However, you can understand the point of cached values if you remember that
-@emph{every} string value's storage @emph{must} come from @code{malloc()}.
+@emph{every} string value's storage @emph{must} come from @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()}.
 If you have 20 variables, all of which have the same string value, you
 must create 20 identical copies of the string.@footnote{Numeric values
 are clearly less problematic, requiring only a C @code{double} to store.}
@@ -29848,7 +31421,7 @@ is what the routines in this section let you do.  The functions are as follows:
 @item awk_bool_t create_value(awk_value_t *value, awk_value_cookie_t *result);
 Create a cached string or numeric value from @code{value} for efficient later
 assignment.
-Only @code{AWK_NUMBER} and @code{AWK_STRING} values are allowed.  Any other type
+Only values of type @code{AWK_NUMBER} and @code{AWK_STRING} are allowed.  Any other type
 is rejected.  While @code{AWK_UNDEFINED} could be allowed, doing so would
 result in inferior performance.
 
@@ -29909,18 +31482,19 @@ What happens if @command{awk} code assigns a new value to @code{VAR1},
 are all the others be changed too?''
 
 That's a great question. The answer is that no, it's not a problem.
-Internally, @command{gawk} uses reference-counted strings. This means
+Internally, @command{gawk} uses @dfn{reference-counted strings}. This means
 that many variables can share the same string value, and @command{gawk}
 keeps track of the usage.  When a variable's value changes, @command{gawk}
 simply decrements the reference count on the old value and updates
 the variable to use the new value.
 
-Finally, as part of your clean up action (@pxref{Exit Callback Functions})
+Finally, as part of your cleanup action (@pxref{Exit Callback Functions})
 you should release any cached values that you created, using
 @code{release_value()}.
 
 @node Array Manipulation
 @subsection Array Manipulation
+@cindex array manipulation in extensions
 
 The primary data structure@footnote{Okay, the only data structure.} in @command{awk}
 is the associative array (@pxref{Arrays}).
@@ -30032,7 +31606,7 @@ requires that you understand how such values are converted to strings
 (@pxref{Conversion}); thus using integral values is safest.
 
 As with @emph{all} strings passed into @code{gawk} from an extension,
-the string value of @code{index} must come from @code{malloc()}, and
+the string value of @code{index} must come from the API-provided functions @code{api_malloc()}, @code{api_calloc()} or @code{api_realloc()} and
 @command{gawk} releases the storage.
 
 @item awk_bool_t set_array_element(awk_array_t a_cookie,
@@ -30040,7 +31614,8 @@ the string value of @code{index} must come from @code{malloc()}, and
 @itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ const@ awk_value_t *const value);
 In the array represented by @code{a_cookie}, create or modify
 the element whose index is given by @code{index}.
-The @code{ARGV} and @code{ENVIRON} arrays may not be changed.
+The @code{ARGV} and @code{ENVIRON} arrays may not be changed,
+although the @code{PROCINFO} array can be.
 
 @item awk_bool_t set_array_element_by_elem(awk_array_t a_cookie,
 @itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ awk_element_t element);
@@ -30311,7 +31886,7 @@ you must add the new array to its parent before adding any elements to it.
 Thus, the correct way to build an array is to work ``top down.''  Create
 the array, and immediately install it in @command{gawk}'s symbol table
 using @code{sym_update()}, or install it as an element in a previously
-existing array using @code{set_element()}.  We show example code shortly.
+existing array using @code{set_array_element()}.  We show example code shortly.
 
 @item
 Due to gawk internals, after using @code{sym_update()} to install an array
@@ -30337,7 +31912,7 @@ of the array cookie after the call to @code{set_element()}.
 @end enumerate
 
 The following C code is a simple test extension to create an array
-with two regular elements and with a subarray. The leading @samp{#include}
+with two regular elements and with a subarray. The leading @code{#include}
 directives and boilerplate variable declarations are omitted for brevity.
 The first step is to create a new array and then install it
 in the symbol table:
@@ -30500,6 +32075,8 @@ information about how @command{gawk} was invoked.
 
 @node Extension Versioning
 @subsubsection API Version Constants and Variables
+@cindex API version
+@cindex extension API version
 
 The API provides both a ``major'' and a ``minor'' version number.
 The API versions are available at compile time as constants:
@@ -30553,18 +32130,23 @@ provided in @file{gawkapi.h} (discussed later, in
 
 @node Extension API Informational Variables
 @subsubsection Informational Variables
+@cindex API informational variables
+@cindex extension API informational variables
 
 The API provides access to several variables that describe
 whether the corresponding command-line options were enabled when
 @command{gawk} was invoked.  The variables are:
 
 @table @code
+@item do_debug
+This variable is true if @command{gawk} was invoked with @option{--debug} option.
+
 @item do_lint
 This variable is true if @command{gawk} was invoked with @option{--lint} option
 (@pxref{Options}).
 
-@item do_traditional
-This variable is true if @command{gawk} was invoked with @option{--traditional} option.
+@item do_mpfr
+This variable is true if @command{gawk} was invoked with @option{--bignum} option.
 
 @item do_profile
 This variable is true if @command{gawk} was invoked with @option{--profile} option.
@@ -30572,11 +32154,8 @@ This variable is true if @command{gawk} was invoked with @option{--profile} opti
 @item do_sandbox
 This variable is true if @command{gawk} was invoked with @option{--sandbox} option.
 
-@item do_debug
-This variable is true if @command{gawk} was invoked with @option{--debug} option.
-
-@item do_mpfr
-This variable is true if @command{gawk} was invoked with @option{--bignum} option.
+@item do_traditional
+This variable is true if @command{gawk} was invoked with @option{--traditional} option.
 @end table
 
 The value of @code{do_lint} can change if @command{awk} code
@@ -30627,8 +32206,14 @@ These variables and functions are as follows:
 
 @table @code
 @item int plugin_is_GPL_compatible;
-This asserts that the extension is compatible with the GNU GPL
-(@pxref{Copying}).  If your extension does not have this, @command{gawk}
+This asserts that the extension is compatible with
+@ifclear FOR_PRINT
+the GNU GPL (@pxref{Copying}).
+@end ifclear
+@ifset FOR_PRINT
+the GNU GPL.
+@end ifset
+If your extension does not have this, @command{gawk}
 will not load it (@pxref{Plugin License}).
 
 @item static gawk_api_t *const api;
@@ -30652,8 +32237,9 @@ as described earlier (@pxref{Extension Functions}).
 It can then be looped over for multiple calls to
 @code{add_ext_func()}.
 
+@c Use @var{OR} for docbook
 @item static awk_bool_t (*init_func)(void) = NULL;
-@itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @r{OR}
+@itemx @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @var{OR}
 @itemx static awk_bool_t init_my_module(void) @{ @dots{} @}
 @itemx static awk_bool_t (*init_func)(void) = init_my_module;
 If you need to do some initialization work, you should define a
@@ -30698,6 +32284,8 @@ the version string with @command{gawk}.
 
 @node Finding Extensions
 @section How @command{gawk} Finds Extensions
+@cindex extension search path
+@cindex finding extensions
 
 Compiled extensions have to be installed in a directory where
 @command{gawk} can find them.  If @command{gawk} is configured and
@@ -30708,6 +32296,7 @@ path with a list of directories to search for compiled extensions.
 
 @node Extension Example
 @section Example: Some File Functions
+@cindex extension example
 
 @quotation
 @i{No matter where you go, there you are.}
@@ -30889,7 +32478,6 @@ Those are followed by the necessary variable declarations
 to make use of the API macros and boilerplate code
 (@pxref{Extension API Boilerplate}).
 
-@c break line for page breaking
 @example
 #ifdef HAVE_CONFIG_H
 #include <config.h>
@@ -30976,7 +32564,6 @@ The @code{stat()} extension is more involved.  First comes a function
 that turns a numeric mode into a printable representation
 (e.g., 644 becomes @samp{-rw-r--r--}). This is omitted here for brevity:
 
-@c break line for page breaking
 @example
 /* format_mode --- turn a stat mode field into something readable */
 
@@ -31166,7 +32753,7 @@ do_stat(int nargs, awk_value_t *result)
     awk_array_t array;
     int ret;
     struct stat sbuf;
-    /* default is stat() */
+    /* default is lstat() */
     int (*statfunc)(const char *path, struct stat *sbuf) = lstat;
 
     assert(result != NULL);
@@ -31250,7 +32837,9 @@ structures for loading each function into @command{gawk}:
 static awk_ext_func_t func_table[] = @{
     @{ "chdir", do_chdir, 1 @},
     @{ "stat",  do_stat, 2 @},
+#ifndef __MINGW32__
     @{ "fts",   do_fts, 3 @},
+#endif
 @};
 @end example
 
@@ -31264,9 +32853,7 @@ everything that needs to be loaded.  It is simplest to use the
 dl_load_func(func_table, filefuncs, "")
 @end example
 
-And that's it!  As an exercise, consider adding functions to
-implement system calls such as @code{chown()}, @code{chmod()},
-and @code{umask()}.
+And that's it!
 
 @node Using Internal File Ops
 @subsection Integrating The Extensions
@@ -31278,7 +32865,7 @@ code must be compiled.  Assuming that the functions are in
 a file named @file{filefuncs.c}, and @var{idir} is the location
 of the @file{gawkapi.h} header file,
 the following steps@footnote{In practice, you would probably want to
-use the GNU Autotools---Automake, Autoconf, Libtool, and Gettext---to
+use the GNU Autotools---Automake, Autoconf, Libtool, and @command{gettext}---to
 configure and build your libraries. Instructions for doing so are beyond
 the scope of this @value{DOCUMENT}. @xref{gawkextlib}, for WWW links to
 the tools.} create a GNU/Linux shared library:
@@ -31320,7 +32907,7 @@ BEGIN @{
 @end example
 
 The @env{AWKLIBPATH} environment variable tells
-@command{gawk} where to find shared libraries (@pxref{Finding Extensions}).
+@command{gawk} where to find extensions (@pxref{Finding Extensions}).
 We set it to the current directory and run the program:
 
 @example
@@ -31352,6 +32939,7 @@ $ @kbd{AWKLIBPATH=$PWD gawk -f testff.awk}
 
 @node Extension Samples
 @section The Sample Extensions In The @command{gawk} Distribution
+@cindex extensions distributed with @command{gawk}
 
 This @value{SECTION} provides brief overviews of the sample extensions
 that come in the @command{gawk} distribution. Some of them are intended
@@ -31382,19 +32970,19 @@ Others mainly provide example code that shows how to use the extension API.
 The @code{filefuncs} extension provides three different functions, as follows:
 The usage is:
 
-@table @code
+@table @asis
 @item @@load "filefuncs"
 This is how you load the extension.
 
-@cindex @code{chdir} extension function
-@item result = chdir("/some/directory")
+@cindex @code{chdir()} extension function
+@item @code{result = chdir("/some/directory")}
 The @code{chdir()} function is a direct hook to the @code{chdir()}
 system call to change the current directory.  It returns zero
 upon success or less than zero upon error.  In the latter case it updates
 @code{ERRNO}.
 
-@cindex @code{stat} extension function
-@item result = stat("/some/path", statdata [, follow])
+@cindex @code{stat()} extension function
+@item @code{result = stat("/some/path", statdata} [@code{, follow}]@code{)}
 The @code{stat()} function provides a hook into the
 @code{stat()} system call.
 It returns zero upon success or less than zero upon error.
@@ -31407,69 +32995,27 @@ In all cases, it clears the @code{statdata} array.
 When the call is successful, @code{stat()} fills the @code{statdata}
 array with information retrieved from the filesystem, as follows:
 
-@c nested table
-@multitable @columnfractions .25 .60
-@item @code{statdata["name"]} @tab
-The name of the file.
-
-@item @code{statdata["dev"]} @tab
-Corresponds to the @code{st_dev} field in the @code{struct stat}.
-
-@item @code{statdata["ino"]} @tab
-Corresponds to the @code{st_ino} field in the @code{struct stat}.
-
-@item @code{statdata["mode"]} @tab
-Corresponds to the @code{st_mode} field in the @code{struct stat}.
-
-@item @code{statdata["nlink"]} @tab
-Corresponds to the @code{st_nlink} field in the @code{struct stat}.
-
-@item @code{statdata["uid"]} @tab
-Corresponds to the @code{st_uid} field in the @code{struct stat}.
-
-@item @code{statdata["gid"]} @tab
-Corresponds to the @code{st_gid} field in the @code{struct stat}.
-
-@item @code{statdata["size"]} @tab
-Corresponds to the @code{st_size} field in the @code{struct stat}.
-
-@item @code{statdata["atime"]} @tab
-Corresponds to the @code{st_atime} field in the @code{struct stat}.
-
-@item @code{statdata["mtime"]} @tab
-Corresponds to the @code{st_mtime} field in the @code{struct stat}.
-
-@item @code{statdata["ctime"]} @tab
-Corresponds to the @code{st_ctime} field in the @code{struct stat}.
-
-@item @code{statdata["rdev"]} @tab
-Corresponds to the @code{st_rdev} field in the @code{struct stat}.
-This element is only present for device files.
-
-@item @code{statdata["major"]} @tab
-Corresponds to the @code{st_major} field in the @code{struct stat}.
-This element is only present for device files.
-
-@item @code{statdata["minor"]} @tab
-Corresponds to the @code{st_minor} field in the @code{struct stat}.
-This element is only present for device files.
-
-@item @code{statdata["blksize"]} @tab
-Corresponds to the @code{st_blksize} field in the @code{struct stat},
-if this field is present on your system.
-(It is present on all modern systems that we know of.)
-
-@item @code{statdata["pmode"]} @tab
-A human-readable version of the mode value, such as printed by
-@command{ls}.  For example, @code{"-rwxr-xr-x"}.
-
-@item @code{statdata["linkval"]} @tab
-If the named file is a symbolic link, this element will exist
-and its value is the value of the symbolic link (where the
-symbolic link points to).
-
-@item @code{statdata["type"]} @tab
-The type of the file as a string. One of
+@multitable @columnfractions .15 .50 .20
+@headitem Subscript @tab Field in @code{struct stat} @tab File type
+@item @code{"name"} @tab The @value{FN} @tab All
+@item @code{"dev"} @tab @code{st_dev} @tab All
+@item @code{"ino"} @tab @code{st_ino} @tab All
+@item @code{"mode"} @tab @code{st_mode} @tab All
+@item @code{"nlink"} @tab @code{st_nlink} @tab All
+@item @code{"uid"} @tab @code{st_uid} @tab All
+@item @code{"gid"} @tab @code{st_gid} @tab All
+@item @code{"size"} @tab @code{st_size} @tab All
+@item @code{"atime"} @tab @code{st_atime} @tab All
+@item @code{"mtime"} @tab @code{st_mtime} @tab All
+@item @code{"ctime"} @tab @code{st_ctime} @tab All
+@item @code{"rdev"} @tab @code{st_rdev} @tab Device files
+@item @code{"major"} @tab @code{st_major} @tab Device files
+@item @code{"minor"} @tab @code{st_minor} @tab Device files
+@item @code{"blksize"} @tab @code{st_blksize} @tab All
+@item @code{"pmode"} @tab A human-readable version of the mode value, such as printed by
+@command{ls}.  For example, @code{"-rwxr-xr-x"} @tab All
+@item @code{"linkval"} @tab The value of the symbolic link @tab Symbolic links
+@item @code{"type"} @tab The type of the file as a string. One of
 @code{"file"},
 @code{"blockdev"},
 @code{"chardev"},
@@ -31480,12 +33026,12 @@ The type of the file as a string. One of
 @code{"door"},
 or
 @code{"unknown"}.
-Not all systems support all file types.
+Not all systems support all file types. @tab All
 @end multitable
 
-@cindex @code{fts} extension function
-@item flags = or(FTS_PHYSICAL, ...)
-@itemx result = fts(pathlist, flags, filedata)
+@cindex @code{fts()} extension function
+@item @code{flags = or(FTS_PHYSICAL, ...)}
+@itemx @code{result = fts(pathlist, flags, filedata)}
 Walk the file trees provided in @code{pathlist} and fill in the
 @code{filedata} array as described below.  @code{flags} is the bitwise
 OR of several predefined constant values, also described below.
@@ -31502,7 +33048,7 @@ The arguments are as follows:
 
 @table @code
 @item pathlist
-An array of filenames.  The element values are used; the index values are ignored.
+An array of @value{FN}s.  The element values are used; the index values are ignored.
 
 @item flags
 This should be the bitwise OR of one or more of the following
@@ -31604,58 +33150,48 @@ See @file{test/fts.awk} in the @command{gawk} distribution for an example.
 @node Extension Sample Fnmatch
 @subsection Interface To @code{fnmatch()}
 
-@cindex @code{fnmatch} extension function
 This extension provides an interface to the C library
 @code{fnmatch()} function.  The usage is:
 
-@example
-@@load "fnmatch"
+@table @code
+@item @@load "fnmatch"
+This is how you load the extension.
 
-result = fnmatch(pattern, string, flags)
-@end example
+@cindex @code{fnmatch()} extension function
+@item result = fnmatch(pattern, string, flags)
+The return value is zero on success, @code{FNM_NOMATCH}
+if the string did not match the pattern, or
+a different non-zero value if an error occurred.
+@end table
 
-The @code{fnmatch} extension adds a single function named
-@code{fnmatch()}, one constant (@code{FNM_NOMATCH}), and an array of
-flag values named @code{FNM}.
+Besides the @code{fnmatch()} function, the @code{fnmatch} extension
+adds one constant (@code{FNM_NOMATCH}), and an array of flag values
+named @code{FNM}.
 
 The arguments to @code{fnmatch()} are:
 
 @table @code
 @item pattern
-The filename wildcard to match.
+The @value{FN} wildcard to match.
 
 @item string
-The filename string.
+The @value{FN} string.
 
 @item flag
 Either zero, or the bitwise OR of one or more of the
 flags in the @code{FNM} array.
 @end table
 
-The return value is zero on success, @code{FNM_NOMATCH}
-if the string did not match the pattern, or
-a different non-zero value if an error occurred.
-
 The flags are follows:
 
 @multitable @columnfractions .25 .75
-@item @code{FNM["CASEFOLD"]} @tab
-Corresponds to the @code{FNM_CASEFOLD} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["FILE_NAME"]} @tab
-Corresponds to the @code{FNM_FILE_NAME} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["LEADING_DIR"]} @tab
-Corresponds to the @code{FNM_LEADING_DIR} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["NOESCAPE"]} @tab
-Corresponds to the @code{FNM_NOESCAPE} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["PATHNAME"]} @tab
-Corresponds to the @code{FNM_PATHNAME} flag as defined in @code{fnmatch()}.
-
-@item @code{FNM["PERIOD"]} @tab
-Corresponds to the @code{FNM_PERIOD} flag as defined in @code{fnmatch()}.
+@headitem Array element @tab Corresponding flag defined by @code{fnmatch()}
+@item @code{FNM["CASEFOLD"]} @tab @code{FNM_CASEFOLD}
+@item @code{FNM["FILE_NAME"]} @tab @code{FNM_FILE_NAME}
+@item @code{FNM["LEADING_DIR"]} @tab @code{FNM_LEADING_DIR}
+@item @code{FNM["NOESCAPE"]} @tab @code{FNM_NOESCAPE}
+@item @code{FNM["PATHNAME"]} @tab @code{FNM_PATHNAME}
+@item @code{FNM["PERIOD"]} @tab @code{FNM_PERIOD}
 @end multitable
 
 Here is an example:
@@ -31677,21 +33213,21 @@ The @code{fork} extension adds three functions, as follows.
 @item @@load "fork"
 This is how you load the extension.
 
-@cindex @code{fork} extension function
+@cindex @code{fork()} extension function
 @item pid = fork()
-This function creates a new process. The return value is the zero in the
-child and the process-id number of the child in the parent, or @minus{}1
+This function creates a new process. The return value is zero in the
+child and the process-ID number of the child in the parent, or @minus{}1
 upon error. In the latter case, @code{ERRNO} indicates the problem.
 In the child, @code{PROCINFO["pid"]} and @code{PROCINFO["ppid"]} are
 updated to reflect the correct values.
 
-@cindex @code{waitpid} extension function
+@cindex @code{waitpid()} extension function
 @item ret = waitpid(pid)
-This function takes a numeric argument, which is the process-id to
+This function takes a numeric argument, which is the process-ID to
 wait for. The return value is that of the
 @code{waitpid()} system call.
 
-@cindex @code{wait} extension function
+@cindex @code{wait()} extension function
 @item ret = wait()
 This function waits for the first child to die.
 The return value is that of the
@@ -31746,8 +33282,8 @@ standard output to a temporary file configured to have the same owner
 and permissions as the original.  After the file has been processed,
 the extension restores standard output to its original destination.
 If @code{INPLACE_SUFFIX} is not an empty string, the original file is
-linked to a backup filename created by appending that suffix.  Finally,
-the temporary file is renamed to the original filename.
+linked to a backup @value{FN} created by appending that suffix.  Finally,
+the temporary file is renamed to the original @value{FN}.
 
 If any error occurs, the extension issues a fatal error to terminate
 processing immediately without damaging the original file.
@@ -31765,9 +33301,6 @@ $ @kbd{gawk -i inplace -v INPLACE_SUFFIX=.bak '@{ gsub(/foo/, "bar") @}}
 > @kbd{@{ print @}' file1 file2 file3}
 @end example
 
-We leave it as an exercise to write a wrapper script that presents an
-interface similar to @samp{sed -i}.
-
 @node Extension Sample Ord
 @subsection Character and Numeric values: @code{ord()} and @code{chr()}
 
@@ -31778,11 +33311,11 @@ The @code{ordchr} extension adds two functions, named
 @item @@load "ordchr"
 This is how you load the extension.
 
-@cindex @code{ord} extension function
+@cindex @code{ord()} extension function
 @item number = ord(string)
 Return the numeric value of the first character in @code{string}.
 
-@cindex @code{chr} extension function
+@cindex @code{chr()} extension function
 @item char = chr(number)
 Return a string whose first character is that represented by @code{number}.
 @end table
@@ -31813,11 +33346,14 @@ on the command line (or with @code{getline}),
 they are read, with each entry returned as a record.
 
 The record consists of three fields. The first two are the inode number and the
-filename, separated by a forward slash character.
+@value{FN}, separated by a forward slash character.
 On systems where the directory entry contains the file type, the record
 has a third field (also separated by a slash) which is a single letter
-indicating the type of the file:
+indicating the type of the file. The letters are file types are shown
+in @ref{table-readdir-file-types}.
 
+@float Table,table-readdir-file-types
+@caption{File Types Returned By @code{readdir()}}
 @multitable @columnfractions .1 .9
 @headitem Letter @tab File Type
 @item @code{b} @tab Block device
@@ -31829,6 +33365,7 @@ indicating the type of the file:
 @item @code{s} @tab Socket
 @item @code{u} @tab Anything else (unknown)
 @end multitable
+@end float
 
 On systems without the file type information, the third field is always
 @samp{u}.
@@ -31863,12 +33400,12 @@ Here is an example:
 
 BEGIN @{
     REVOUT = 1
-    print "hello, world" > "/dev/stdout"
+    print "don't panic" > "/dev/stdout"
 @}
 @end example
 
 The output from this program is:
-@samp{dlrow ,olleh}.
+@samp{cinap t'nod}.
 
 @node Extension Sample Rev2way
 @subsection Two-Way I/O Example
@@ -31885,13 +33422,22 @@ The following example shows how to use it:
 
 BEGIN @{
     cmd = "/magic/mirror"
-    print "hello, world" |& cmd
+    print "don't panic" |& cmd
     cmd |& getline result
     print result
     close(cmd)
 @}
 @end example
 
+The output from this program
+@ifnotinfo
+also is:
+@end ifnotinfo
+@ifinfo
+is:
+@end ifinfo
+@samp{cinap t'nod}.
+
 @node Extension Sample Read write array
 @subsection Dumping and Restoring An Array
 
@@ -31899,14 +33445,14 @@ The @code{rwarray} extension adds two functions,
 named @code{writea()} and @code{reada()}, as follows:
 
 @table @code
-@cindex @code{writea} extension function
+@cindex @code{writea()} extension function
 @item ret = writea(file, array)
 This function takes a string argument, which is the name of the file
-to which dump the array, and the array itself as the second argument.
-@code{writea()} understands multidimensional arrays.  It returns one on
+to which to dump the array, and the array itself as the second argument.
+@code{writea()} understands arrays of arrays.  It returns one on
 success, or zero upon failure.
 
-@cindex @code{reada} extension function
+@cindex @code{reada()} extension function
 @item ret = reada(file, array)
 @code{reada()} is the inverse of @code{writea()};
 it reads the file named as its first argument, filling in
@@ -31943,17 +33489,23 @@ ret = reada("arraydump.bin", array)
 @subsection Reading An Entire File
 
 The @code{readfile} extension adds a single function
-named @code{readfile()}:
+named @code{readfile()}, and an input parser:
 
 @table @code
 @item @@load "readfile"
 This is how you load the extension.
 
-@cindex @code{readfile} extension function
+@cindex @code{readfile()} extension function
 @item result = readfile("/some/path")
 The argument is the name of the file to read.  The return value is a
 string containing the entire contents of the requested file.  Upon error,
 the function returns the empty string and sets @code{ERRNO}.
+
+@item BEGIN @{ PROCINFO["readfile"] = 1 @}
+In addition, the extension adds an input parser that is activated if
+@code{PROCINFO["readfile"]} exists.
+When activated, each input file is returned in its entirety as @code{$0}.
+@code{RT} is set to the null string.
 @end table
 
 Here is an example:
@@ -31982,25 +33534,24 @@ for more information.
 @node Extension Sample Time
 @subsection Extension Time Functions
 
-These functions can be used either by invoking @command{gawk}
-with a command-line argument of @samp{-l time} or by
-inserting @samp{@@load "time"} in your script.
+The @code{time} extension adds two functions, named @code{gettimeofday()}
+and @code{sleep()}, as follows:
 
 @table @code
 @item @@load "time"
 This is how you load the extension.
 
-@cindex @code{gettimeofday} extension function
+@cindex @code{gettimeofday()} extension function
 @item the_time = gettimeofday()
 Return the time in seconds that has elapsed since 1970-01-01 UTC as a
 floating point value.  If the time is unavailable on this platform, return
 @minus{}1 and set @code{ERRNO}.  The returned time should have sub-second
 precision, but the actual precision may vary based on the platform.
 If the standard C @code{gettimeofday()} system call is available on this
-platform, then it simply returns the value.  Otherwise, if on Windows,
+platform, then it simply returns the value.  Otherwise, if on MS-Windows,
 it tries to use @code{GetSystemTimeAsFileTime()}.
 
-@cindex @code{sleep} extension function
+@cindex @code{sleep()} extension function
 @item result = sleep(@var{seconds})
 Attempt to sleep for @var{seconds} seconds.  If @var{seconds} is negative,
 or the attempt to sleep fails, return @minus{}1 and set @code{ERRNO}.
@@ -32012,6 +33563,8 @@ tries to use @code{nanosleep()} or @code{select()} to implement the delay.
 
 @node gawkextlib
 @section The @code{gawkextlib} Project
+@cindex @code{gawkextlib}
+@cindex extensions, where to find
 
 @cindex @code{gawkextlib} project
 The @uref{http://sourceforge.net/projects/gawkextlib/, @code{gawkextlib}}
@@ -32019,14 +33572,17 @@ project provides a number of @command{gawk} extensions, including one for
 processing XML files.  This is the evolution of the original @command{xgawk}
 (XML @command{gawk}) project.
 
-As of this writing, there are four extensions:
+As of this writing, there are five extensions:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 XML parser extension, using the @uref{http://expat.sourceforge.net, Expat}
 XML parsing library.
 
 @item
+PDF extension.
+
+@item
 PostgreSQL extension.
 
 @item
@@ -32042,8 +33598,9 @@ The @code{time} extension described earlier (@pxref{Extension Sample
 Time}) was originally from this project but has been moved in to the
 main @command{gawk} distribution.
 
+@cindex @command{git} utility
 You can check out the code for the @code{gawkextlib} project
-using the @uref{http://git-scm.com, GIT} distributed source
+using the @uref{http://git-scm.com, Git} distributed source
 code control system.  The command is as follows:
 
 @example
@@ -32059,7 +33616,7 @@ In addition, you must have the GNU Autotools installed
 @uref{http://www.gnu.org/software/automake, Automake},
 @uref{http://www.gnu.org/software/libtool, Libtool},
 and
-@uref{http://www.gnu.org/software/gettext, Gettext}).
+@uref{http://www.gnu.org/software/gettext, GNU @command{gettext}}).
 
 The simple recipe for building and testing @code{gawkextlib} is as follows.
 First, build and install @command{gawk}:
@@ -32093,26 +33650,168 @@ If you write an extension that you wish to share with other
 @code{gawkextlib} project.
 See the project's web site for more information.
 
-@iftex
-@part Part IV:@* Appendices
-@end iftex
+@node Extension summary
+@section Summary
+
+@itemize @value{BULLET}
+@item
+You can write extensions (sometimes called plug-ins) for @command{gawk}
+in C or C++ using the Application Programming Interface (API) defined
+by the @command{gawk} developers.
+
+@item
+Extensions must have a license compatible with the GNU General Public
+License (GPL), and they must assert that fact by declaring a variable
+named @code{plugin_is_GPL_compatible}.
+
+@item
+Communication between @command{gawk} and an extension is two-way.
+@command{gawk} passes a @code{struct} to the extension which contains
+various data fields and function pointers.  The extension can then call
+into @command{gawk} via the supplied function pointers to accomplish
+certain tasks.
+
+@item
+One of these tasks is to ``register'' the name and implementation of
+a new @command{awk}-level function with @command{gawk}.  The implementation
+takes the form of a C function pointer with a defined signature.
+By convention, implementation functions are named @code{do_@var{XXXX}()}
+for some @command{awk}-level function @code{@var{XXXX}()}.
+
+@item
+The API is defined in a header file named @file{gawkpi.h}. You must include
+a number of standard header files @emph{before} including it in your source file.
+
+@item
+API function pointers are provided for the following kinds of operations:
+
+@itemize @value{BULLET}
+@item
+Registration functions. You may register
+extension functions,
+exit callbacks,
+a version string,
+input parsers,
+output wrappers,
+and two-way processors.
+
+@item
+Printing fatal, warning, and ``lint'' warning messages.
+
+@item
+Updating @code{ERRNO}, or unsetting it.
+
+@item
+Accessing parameters, including converting an undefined parameter into
+an array.
+
+@item
+Symbol table access: retrieving a global variable, creating one,
+or changing one.
+
+@item
+Allocating, reallocating, and releasing memory.
+
+@item
+Creating and releasing cached values; this provides an
+efficient way to use values for multiple variables and
+can be a big performance win.
+
+@item
+Manipulating arrays:
+retrieving, adding, deleting, and modifying elements;
+getting the count of elements in an array;
+creating a new array;
+clearing an array;
+and
+flattening an array for easy C style looping over all its indices and elements
+@end itemize
+
+@item
+The API defines a number of standard data types for representing
+@command{awk} values, array elements, and arrays.
+
+@item
+The API provide convenience functions for constructing values.
+It also provides memory management functions to ensure compatibility
+between memory allocated by @command{gawk} and memory allocated by an
+extension.
+
+@item
+@emph{All} memory passed from @command{gawk} to an extension must be
+treated as read-only by the extension.
+
+@item
+@emph{All} memory passed from an extension to @command{gawk} must come from
+the API's memory allocation functions. @command{gawk} takes responsibility for
+the memory and will release it when appropriate.
+
+@item
+The API provides information about the running version of @command{gawk} so
+that an extension can make sure it is compatible with the @command{gawk}
+that loaded it.
+
+@item
+It is easiest to start a new extension by copying the boilerplate code
+described in this @value{CHAPTER}.  Macros in the @file{gawkapi.h} make
+this easier to do.
+
+@item
+The @command{gawk} distribution includes a number of small but useful
+sample extensions. The @code{gawkextlib} project includes several more,
+larger, extensions.  If you wish to write an extension and contribute it
+to the community of @command{gawk} users, the @code{gawkextlib} project
+should be the place to do so.
+
+@end itemize
+
+@node Extension Exercises
+@section Exercises
+
+@enumerate
+@item
+Add functions to implement system calls such as @code{chown()},
+@code{chmod()}, and @code{umask()} to the file operations extension
+presented in @ref{Internal File Ops}.
+
+@item
+(Hard.)
+How would you provide namespaces in @command{gawk}, so that the
+names of functions in different extensions don't conflict with each other?
+If you come up with a really good scheme, contact the @command{gawk}
+maintainer to tell him about it.
+
+@item
+Write a wrapper script that provides an interface similar to
+@samp{sed -i} for the ``inplace'' extension presented in
+@ref{Extension Sample Inplace}.
+
+@end enumerate
+
+@ifnotinfo
+@part @value{PART4}Appendices
+@end ifnotinfo
 
-@ignore
 @ifdocbook
 
-@part Part IV:@* Appendices
+@ifclear FOR_PRINT
+Part IV contains the appendixes (including the two licenses that cover
+the @command{gawk} source code and this @value{DOCUMENT}, respectively)
+and the Glossary:
+@end ifclear
 
-Part IV provides the appendices, the Glossary, and two licenses that cover
-the @command{gawk} source code and this @value{DOCUMENT}, respectively.
-It contains the following appendices:
+@ifset FOR_PRINT
+Part IV contains two appendixes:
+@end ifset
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @ref{Language History}.
 
 @item
 @ref{Installation}.
 
+@ifclear FOR_PRINT
 @item
 @ref{Notes}.
 
@@ -32127,24 +33826,31 @@ It contains the following appendices:
 
 @item
 @ref{GNU Free Documentation License}.
+@end ifclear
 @end itemize
 @end ifdocbook
-@end ignore
 
 @node Language History
 @appendix The Evolution of the @command{awk} Language
 
-This @value{DOCUMENT} describes the GNU implementation of @command{awk}, which follows
-the POSIX specification.
-Many long-time @command{awk} users learned @command{awk} programming
-with the original @command{awk} implementation in Version 7 Unix.
-(This implementation was the basis for @command{awk} in Berkeley Unix,
-through 4.3-Reno.  Subsequent versions of Berkeley Unix, and some systems
-derived from 4.4BSD-Lite, use various versions of @command{gawk}
-for their @command{awk}.)
-This @value{CHAPTER} briefly describes the
-evolution of the @command{awk} language, with cross-references to other parts
-of the @value{DOCUMENT} where you can find more information.
+This @value{DOCUMENT} describes the GNU implementation of @command{awk},
+which follows the POSIX specification.  Many long-time @command{awk}
+users learned @command{awk} programming with the original @command{awk}
+implementation in Version 7 Unix.  (This implementation was the basis for
+@command{awk} in Berkeley Unix, through 4.3-Reno.  Subsequent versions
+of Berkeley Unix, and some systems derived from 4.4BSD-Lite, used various
+versions of @command{gawk} for their @command{awk}.)  This @value{CHAPTER}
+briefly describes the evolution of the @command{awk} language, with
+cross-references to other parts of the @value{DOCUMENT} where you can
+find more information.
+
+@ifset FOR_PRINT
+To save space, we have omitted
+information on the history of features in @command{gawk} from this
+edition. You can find it in the
+@uref{http://www.gnu.org/software/gawk/manual/html_node/Feature-History.html,
+online documentation}.
+@end ifset
 
 @menu
 * V7/SVR3.1::                   The major changes between V7 and System V
@@ -32156,9 +33862,11 @@ of the @value{DOCUMENT} where you can find more information.
                                 @command{awk}.
 * POSIX/GNU::                   The extensions in @command{gawk} not in POSIX
                                 @command{awk}.
+* Feature History::             The history of the features in @command{gawk}.
 * Common Extensions::           Common Extensions Summary.
 * Ranges and Locales::          How locales used to affect regexp ranges.
 * Contributors::                The major contributors to @command{gawk}.
+* History summary::             History summary.
 @end menu
 
 @node V7/SVR3.1
@@ -32173,7 +33881,7 @@ Version 7 Unix (1978) and the new version that was first made generally availabl
 System V Release 3.1 (1987).  This @value{SECTION} summarizes the changes, with
 cross-references to further details:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The requirement for @samp{;} to separate rules on a line
 (@pxref{Statements/Lines}).
@@ -32264,7 +33972,7 @@ Multidimensional arrays
 The System V Release 4 (1989) version of Unix @command{awk} added these features
 (some of which originated in @command{gawk}):
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @code{ENVIRON} array (@pxref{Built-in Variables}).
 @c gawk and MKS awk
@@ -32324,7 +34032,7 @@ Processing of escape sequences inside command-line variable assignments
 The POSIX Command Language and Utilities standard for @command{awk} (1992)
 introduced the following changes into the language:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The use of @option{-W} for implementation-specific options
 (@pxref{Options}).
@@ -32349,7 +34057,7 @@ features of the language.
 In 2012, a number of extensions that had been commonly available for
 many years were finally added to POSIX. They are:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @code{fflush()} built-in function for flushing buffered output
 (@pxref{I/O Functions}).
@@ -32386,7 +34094,7 @@ has made his version available via his home page
 This @value{SECTION} describes common extensions that
 originally appeared in his version of @command{awk}.
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The @samp{**} and @samp{**=} operators
 (@pxref{Arithmetic Ops}
@@ -32404,7 +34112,7 @@ The @code{fflush()} built-in function for flushing buffered output
 @ignore
 @item
 The @code{SYMTAB} array, that allows access to @command{awk}'s internal symbol
-table. This feature is not documented, largely because
+table. This feature was never documented for his @command{awk}, largely because
 it is somewhat shakily implemented. For instance, you cannot access arrays
 or array elements through it.
 @end ignore
@@ -32431,12 +34139,12 @@ A number of features have come and gone over the years. This @value{SECTION}
 summarizes the additional features over POSIX @command{awk} that are
 in the current version of @command{gawk}.
 
-@itemize @bullet
+@itemize @value{BULLET}
 
 @item
 Additional built-in variables:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The
 @code{ARGIND}
@@ -32457,10 +34165,10 @@ variables
 @item
 Special files in I/O redirections:
 
-@itemize @minus{}
+@itemize @value{MINUS}
 @item
 The @file{/dev/stdin}, @file{/dev/stdout}, @file{/dev/stderr} and
-@file{/dev/fd/@var{N}} special file names
+@file{/dev/fd/@var{N}} special @value{FN}s
 (@pxref{Special Files}).
 
 @item
@@ -32473,7 +34181,7 @@ IP protocol to use.
 @item
 Changes and/or additions to the language:
 
-@itemize @minus{}
+@itemize @value{MINUS}
 @item
 The @samp{\x} escape sequence
 (@pxref{Escape Sequences}).
@@ -32512,7 +34220,7 @@ Directories on the command line produce a warning and are skipped
 @item
 New keywords:
 
-@itemize @minus{}
+@itemize @value{MINUS}
 @item
 The @code{BEGINFILE} and @code{ENDFILE} special patterns.
 (@pxref{BEGINFILE/ENDFILE}).
@@ -32533,7 +34241,7 @@ The @code{switch} statement
 @item
 Changes to standard @command{awk} functions:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The optional second argument to @code{close()} that allows closing one end
 of a two-way pipe to a coprocess
@@ -32566,7 +34274,7 @@ argument which is an array to hold the text of the field separators.
 @item
 Additional functions only in @command{gawk}:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The
 @code{and()},
@@ -32609,7 +34317,7 @@ functions for working with timestamps
 @item
 Changes and/or additions in the command-line options:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The @env{AWKPATH} environment variable for specifying a path search for
 the @option{-f} command-line option
@@ -32684,10 +34392,10 @@ long options
 
 @item
 Support for the following obsolete systems was removed from the code
-and the documentation for @command{gawk} version 4.0:
+and the documentation for @command{gawk} @value{PVERSION} 4.0:
 
 @c nested table
-@itemize @minus
+@itemize @value{MINUS}
 @item
 Amiga
 
@@ -32721,6 +34429,9 @@ Tandem (non-POSIX)
 @item
 Prestandard VAX C compiler for VAX/VMS
 
+@item
+GCC for VAX and Alpha has not been tested for a while.
+
 @end itemize
 
 @end itemize
@@ -32731,6 +34442,618 @@ Prestandard VAX C compiler for VAX/VMS
 @c ENDOFRANGE exgnot
 @c ENDOFRANGE posnot
 
+@c This does not need to be in the formal book.
+@ifclear FOR_PRINT
+@node Feature History
+@appendixsec History of @command{gawk} Features
+
+@ignore
+See the thread:
+https://groups.google.com/forum/#!topic/comp.lang.awk/SAUiRuff30c
+This motivated me to add this section.
+@end ignore
+
+@ignore
+I've tried to follow this general order, esp.@: for the 3.0 and 3.1 sections:
+       variables
+       special files
+       language changes (e.g., hex constants)
+       differences in standard awk functions
+       new gawk functions
+       new keywords
+       new command-line options
+       behavioral changes
+       new ports
+Within each category, be alphabetical.
+@end ignore
+
+This @value{SECTION} describes the features in @command{gawk}
+over and above those in POSIX @command{awk},
+in the order they were added to @command{gawk}.
+
+Version 2.10 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+The @env{AWKPATH} environment variable for specifying a path search for
+the @option{-f} command-line option
+(@pxref{Options}).
+
+@item
+The @code{IGNORECASE} variable and its effects
+(@pxref{Case-sensitivity}).
+
+@item
+The @file{/dev/stdin}, @file{/dev/stdout}, @file{/dev/stderr} and
+@file{/dev/fd/@var{N}} special @value{FN}s
+(@pxref{Special Files}).
+@end itemize
+
+Version 2.13 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+The @code{FIELDWIDTHS} variable and its effects
+(@pxref{Constant Size}).
+
+@item
+The @code{systime()} and @code{strftime()} built-in functions for obtaining
+and printing timestamps
+(@pxref{Time Functions}).
+
+@item
+Additional command-line options
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{-W lint} option to provide error and portability checking
+for both the source code and at runtime.
+
+@item
+The @option{-W compat} option to turn off the GNU extensions.
+
+@item
+The @option{-W posix} option for full POSIX compliance.
+@end itemize
+@end itemize
+
+Version 2.14 of @command{gawk} introduced the following feature:
+
+@itemize @value{BULLET}
+@item
+The @code{next file} statement for skipping to the next @value{DF}
+(@pxref{Nextfile Statement}).
+@end itemize
+
+Version 2.15 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+New variables (@pxref{Built-in Variables}):
+
+@itemize @value{MINUS}
+@item
+@code{ARGIND}, which tracks the movement of @code{FILENAME}
+through @code{ARGV}.
+
+@item
+@code{ERRNO}, which contains the system error message when
+@code{getline} returns @minus{}1 or @code{close()} fails.
+@end itemize
+
+@item
+The @file{/dev/pid}, @file{/dev/ppid}, @file{/dev/pgrpid}, and
+@file{/dev/user} special @value{FN}s. These have since been removed.
+
+@item
+The ability to delete all of an array at once with @samp{delete @var{array}}
+(@pxref{Delete}).
+
+@item
+Command line option changes
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The ability to use GNU-style long-named options that start with @option{--}.
+
+@item
+The @option{--source} option for mixing command-line and library-file
+source code.
+@end itemize
+@end itemize
+
+Version 3.0 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+New or changed variables:
+
+@itemize @value{MINUS}
+@item
+@code{IGNORECASE} changed, now applying to string comparison as well
+as regexp operations
+(@pxref{Case-sensitivity}).
+
+@item
+@code{RT}, which contains the input text that matched @code{RS}
+(@pxref{Records}).
+@end itemize
+
+@item
+Full support for both POSIX and GNU regexps
+(@pxref{Regexp}).
+
+@item
+The @code{gensub()} function for more powerful text manipulation
+(@pxref{String Functions}).
+
+@item
+The @code{strftime()} function acquired a default time format,
+allowing it to be called with no arguments
+(@pxref{Time Functions}).
+
+@item
+The ability for @code{FS} and for the third
+argument to @code{split()} to be null strings
+(@pxref{Single Character Fields}).
+
+@item
+The ability for @code{RS} to be a regexp
+(@pxref{Records}).
+
+@item
+The @code{next file} statement became @code{nextfile}
+(@pxref{Nextfile Statement}).
+
+@item
+The @code{fflush()} function from
+Brian Kernighan's @command{awk}
+(then at Bell Laboratories;
+@pxref{I/O Functions}).
+
+@item
+New command line options:
+
+@itemize @value{MINUS}
+@item
+The @option{--lint-old} option to
+warn about constructs that are not available in
+the original Version 7 Unix version of @command{awk}
+(@pxref{V7/SVR3.1}).
+
+@item
+The @option{-m} option from Brian Kernighan's @command{awk}.  (He was
+still at Bell Laboratories at the time.)  This was later removed from
+both his @command{awk} and from @command{gawk}.
+
+@item
+The @option{--re-interval} option to provide interval expressions in regexps
+(@pxref{Regexp Operators}).
+
+@item
+The @option{--traditional} option was added as a better name for
+@option{--compat} (@pxref{Options}).
+@end itemize
+
+@item
+The use of GNU Autoconf to control the configuration process
+(@pxref{Quick Installation}).
+
+@item
+Amiga support.
+This has since been removed.
+
+@end itemize
+
+Version 3.1 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+@item
+New variables
+(@pxref{Built-in Variables}):
+
+@itemize @value{MINUS}
+@item
+@code{BINMODE}, for non-POSIX systems,
+which allows binary I/O for input and/or output files
+(@pxref{PC Using}).
+
+@item
+@code{LINT}, which dynamically controls lint warnings.
+
+@item
+@code{PROCINFO}, an array for providing process-related information.
+
+@item
+@code{TEXTDOMAIN}, for setting an application's internationalization text domain
+(@pxref{Internationalization}).
+@end itemize
+
+@item
+The ability to use octal and hexadecimal constants in @command{awk}
+program source code
+(@pxref{Nondecimal-numbers}).
+
+@item
+The @samp{|&} operator for two-way I/O to a coprocess
+(@pxref{Two-way I/O}).
+
+@item
+The @file{/inet} special files for TCP/IP networking using @samp{|&}
+(@pxref{TCP/IP Networking}).
+
+@item
+The optional second argument to @code{close()} that allows closing one end
+of a two-way pipe to a coprocess
+(@pxref{Two-way I/O}).
+
+@item
+The optional third argument to the @code{match()} function
+for capturing text-matching subexpressions within a regexp
+(@pxref{String Functions}).
+
+@item
+Positional specifiers in @code{printf} formats for
+making translations easier
+(@pxref{Printf Ordering}).
+
+@item
+A number of new built-in functions:
+
+@itemize @value{MINUS}
+@item
+The @code{asort()} and @code{asorti()} functions for sorting arrays
+(@pxref{Array Sorting}).
+
+@item
+The @code{bindtextdomain()}, @code{dcgettext()} and @code{dcngettext()} functions
+for internationalization
+(@pxref{Programmer i18n}).
+
+@item
+The @code{extension()} function and the ability to add
+new built-in functions dynamically
+(@pxref{Dynamic Extensions}).
+
+@item
+The @code{mktime()} function for creating timestamps
+(@pxref{Time Functions}).
+
+@item
+The @code{and()}, @code{or()}, @code{xor()}, @code{compl()},
+@code{lshift()}, @code{rshift()}, and @code{strtonum()} functions
+(@pxref{Bitwise Functions}).
+@end itemize
+
+@item
+@cindex @code{next file} statement
+The support for @samp{next file} as two words was removed completely
+(@pxref{Nextfile Statement}).
+
+@item
+Additional command-line options
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{--dump-variables} option to print a list of all global variables.
+
+@item
+The @option{--exec} option, for use in CGI scripts.
+
+@item
+The @option{--gen-po} command-line option and the use of a leading
+underscore to mark strings that should be translated
+(@pxref{String Extraction}).
+
+@item
+The @option{--non-decimal-data} option to allow non-decimal
+input data
+(@pxref{Nondecimal Data}).
+
+@item
+The @option{--profile} option and @command{pgawk}, the
+profiling version of @command{gawk}, for producing execution
+profiles of @command{awk} programs
+(@pxref{Profiling}).
+
+@item
+The @option{--use-lc-numeric} option to force @command{gawk}
+to use the locale's decimal point for parsing input data
+(@pxref{Conversion}).
+@end itemize
+
+@item
+The use of GNU Automake to help in standardizing the configuration process
+(@pxref{Quick Installation}).
+
+@item
+The use of GNU @command{gettext} for @command{gawk}'s own message output
+(@pxref{Gawk I18N}).
+
+@item
+BeOS support. This was later removed.
+
+@item
+Tandem support. This was later removed.
+
+@item
+The Atari port became officially unsupported and was
+later removed entirely.
+
+@item
+The source code changed to use ISO C standard-style function definitions.
+
+@item
+POSIX compliance for @code{sub()} and @code{gsub()}
+(@pxref{Gory Details}).
+
+@item
+The @code{length()} function was extended to accept an array argument
+and return the number of elements in the array
+(@pxref{String Functions}).
+
+@item
+The @code{strftime()} function acquired a third argument to
+enable printing times as UTC
+(@pxref{Time Functions}).
+@end itemize
+
+Version 4.0 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+
+@item
+Variable additions:
+
+@itemize @value{MINUS}
+@item
+@code{FPAT}, which allows you to specify a regexp that matches
+the fields, instead of matching the field separator
+(@pxref{Splitting By Content}).
+
+@item
+If @code{PROCINFO["sorted_in"]} exists, @samp{for(iggy in foo)} loops sort the
+indices before looping over them.  The value of this element
+provides control over how the indices are sorted before the loop
+traversal starts
+(@pxref{Controlling Scanning}).
+
+@item
+@code{PROCINFO["strftime"]}, which holds
+the default format for @code{strftime()}
+(@pxref{Time Functions}).
+@end itemize
+
+@item
+The special files @file{/dev/pid}, @file{/dev/ppid}, @file{/dev/pgrpid}
+and @file{/dev/user} were removed.
+
+@item
+Support for IPv6 was added via the @file{/inet6} special file.
+@file{/inet4} forces IPv4 and @file{/inet} chooses the system
+default, which is probably IPv4
+(@pxref{TCP/IP Networking}).
+
+@item
+The use of @samp{\s} and @samp{\S} escape sequences in regular expressions
+(@pxref{GNU Regexp Operators}).
+
+@item
+Interval expressions became part of default regular expressions
+(@pxref{Regexp Operators}).
+
+@item
+POSIX character classes work even with @option{--traditional}
+(@pxref{Regexp Operators}).
+
+@item
+@code{break} and @code{continue} became invalid outside a loop,
+even with @option{--traditional}
+(@pxref{Break Statement}, and also see
+@ref{Continue Statement}).
+
+@item
+@code{fflush()}, @code{nextfile}, and @samp{delete @var{array}}
+are allowed if @option{--posix} or @option{--traditional}, since they
+are all now part of POSIX.
+
+@item
+An optional third argument to
+@code{asort()} and @code{asorti()}, specifying how to sort
+(@pxref{String Functions}).
+
+@item
+The behavior of @code{fflush()} changed to match Brian Kernighan's @command{awk}
+and for POSIX; now both @samp{fflush()} and @samp{fflush("")}
+flush all open output redirections
+(@pxref{I/O Functions}).
+
+@item
+The @code{isarray()}
+function which distinguishes if an item is an array
+or not, to make it possible to traverse arrays of arrays
+(@pxref{Type Functions}).
+
+@item
+The @code{patsplit()}
+function which gives the same capability as @code{FPAT}, for splitting
+(@pxref{String Functions}).
+
+@item
+An optional fourth argument to the @code{split()} function,
+which is an array to hold the values of the separators
+(@pxref{String Functions}).
+
+@item
+Arrays of arrays
+(@pxref{Arrays of Arrays}).
+
+@item
+The @code{BEGINFILE} and @code{ENDFILE} special patterns
+(@pxref{BEGINFILE/ENDFILE}).
+
+@item
+Indirect function calls
+(@pxref{Indirect Calls}).
+
+@item
+@code{switch} / @code{case} are enabled by default
+(@pxref{Switch Statement}).
+
+@item
+Command line option changes
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{-b} and @option{--characters-as-bytes} options
+which prevent @command{gawk} from treating input as a multibyte string.
+
+@item
+The redundant @option{--compat}, @option{--copyleft}, and @option{--usage}
+long options were removed.
+
+@item
+The @option{--gen-po} option was finally renamed to the correct @option{--gen-pot}.
+
+@item
+The @option{--sandbox} option which disables certain features.
+
+@item
+All long options acquired corresponding short options, for use in @samp{#!} scripts.
+@end itemize
+
+@item
+Directories named on the command line now produce a warning, not a fatal
+error, unless @option{--posix} or @option{--traditional} are used
+(@pxref{Command line directories}).
+
+@item
+The @command{gawk} internals were rewritten, bringing the @command{dgawk}
+debugger and possibly improved performance
+(@pxref{Debugger}).
+
+@item
+Per the GNU Coding Standards, dynamic extensions must now define
+a global symbol indicating that they are GPL-compatible
+(@pxref{Plugin License}).
+
+@item
+In POSIX mode, string comparisons use @code{strcoll()} / @code{wcscoll()}
+(@pxref{POSIX String Comparison}).
+
+@item
+The option for raw sockets was removed, since it was never implemented
+(@pxref{TCP/IP Networking}).
+
+@item
+Ranges of the form @samp{[d-h]} are treated as if they were in the
+C locale, no matter what kind of regexp is being used, and even if
+@option{--posix}
+(@pxref{Ranges and Locales}).
+
+@item
+Support was removed for the following systems:
+
+@itemize @value{MINUS}
+@item
+Atari
+
+@item
+Amiga
+
+@item
+BeOS
+
+@item
+Cray
+
+@item
+MIPS RiscOS
+
+@item
+MS-DOS with Microsoft Compiler
+
+@item
+MS-Windows with Microsoft Compiler
+
+@item
+NeXT
+
+@item
+SunOS 3.x, Sun 386 (Road Runner)
+
+@item
+Tandem (non-POSIX)
+
+@item
+Prestandard VAX C compiler for VAX/VMS
+@end itemize
+@end itemize
+
+Version 4.1 of @command{gawk} introduced the following features:
+
+@itemize @value{BULLET}
+
+@item
+Three new arrays:
+@code{SYMTAB}, @code{FUNCTAB}, and @code{PROCINFO["identifiers"]}
+(@pxref{Auto-set}).
+
+@item
+The three executables @command{gawk}, @command{pgawk}, and @command{dgawk}, were merged into
+one, named just @command{gawk}.  As a result the command line options changed.
+
+@item
+Command line option changes
+(@pxref{Options}):
+
+@itemize @value{MINUS}
+@item
+The @option{-D} option invokes the debugger.
+
+@item
+The @option{-i} and @option{--include} options
+load @command{awk} library files.
+
+@item
+The @option{-l} and @option{--load} options load compiled dynamic extensions.
+
+@item 
+The @option{-M} and @option{--bignum} options enable MPFR.
+
+@item
+The @option{-o} only does pretty-printing.
+
+@item
+The @option{-p} option is used for profiling.
+
+@item
+The @option{-R} option was removed.
+@end itemize
+
+@item
+Support for high precision arithmetic with MPFR.
+(@pxref{Arbitrary Precision Arithmetic}).
+
+@item
+The @code{and()}, @code{or()} and @code{xor()} functions
+changed to allow any number of arguments,
+with a minimum of two
+(@pxref{Bitwise Functions}).
+
+@item
+The dynamic extension interface was completely redone
+(@pxref{Dynamic Extensions}).
+
+@end itemize
+
+@c XXX ADD MORE STUFF HERE
+@end ifclear
+
 @node Common Extensions
 @appendixsec Common Extensions Summary
 
@@ -32744,18 +35067,18 @@ the three most widely-used freely available versions of @command{awk}
 @multitable {@file{/dev/stderr} special file} {BWK Awk} {Mawk} {GNU Awk}
 @headitem Feature @tab BWK Awk @tab Mawk @tab GNU Awk
 @item @samp{\x} Escape sequence @tab X @tab X @tab X
-@item @code{RS} as regexp @tab @tab X @tab X
 @item @code{FS} as null string @tab X @tab X @tab X
-@item @file{/dev/stdin} special file @tab X @tab @tab X
+@item @file{/dev/stdin} special file @tab X @tab X @tab X
 @item @file{/dev/stdout} special file @tab X @tab X @tab X
 @item @file{/dev/stderr} special file @tab X @tab X @tab X
-@item @code{**} and @code{**=} operators @tab X @tab @tab X
+@item @code{delete} without subscript @tab X @tab X @tab X
 @item @code{fflush()} function @tab X @tab X @tab X
-@item @code{func} keyword @tab X @tab @tab X
+@item @code{length()} of an array @tab X @tab X @tab X
 @item @code{nextfile} statement @tab X @tab X @tab X
-@item @code{delete} without subscript @tab X @tab X @tab X
-@item @code{length()} of an array @tab X @tab @tab X
+@item @code{**} and @code{**=} operators @tab X @tab @tab X
+@item @code{func} keyword @tab X @tab @tab X
 @item @code{BINMODE} variable @tab @tab X @tab X
+@item @code{RS} as regexp @tab @tab X @tab X
 @item Time related functions @tab @tab X @tab X
 @end multitable
 
@@ -32775,7 +35098,7 @@ character ranges (such as @samp{[a-z]}) to match any character between
 the first character in the range and the last character in the range,
 inclusive.  Ordering was based on the numeric value of each character
 in the machine's native character set.  Thus, on ASCII-based systems,
-@code{[a-z]} matched all the lowercase letters, and only the lowercase
+@samp{[a-z]} matched all the lowercase letters, and only the lowercase
 letters, since the numeric values for the letters from @samp{a} through
 @samp{z} were contiguous.  (On an EBCDIC system, the range @samp{[a-z]}
 includes additional, non-alphabetic characters as well.)
@@ -32786,7 +35109,7 @@ as working in this fashion, and in particular, would teach that the
 that @samp{[A-Z]} was the ``correct'' way to match uppercase letters.
 And indeed, this was true.@footnote{And Life was good.}
 
-The 1993 POSIX standard introduced the idea of locales (@pxref{Locales}).
+The 1992 POSIX standard introduced the idea of locales (@pxref{Locales}).
 Since many locales include other letters besides the plain twenty-six
 letters of the American English alphabet, the POSIX standard added
 character classes (@pxref{Bracket Expressions}) as a way to match
@@ -32825,9 +35148,10 @@ This output is unexpected, since the @samp{bc} at the end of
 This result is due to the locale setting (and thus you may not see
 it on your system).
 
+@cindex Unicode
 Similar considerations apply to other ranges.  For example, @samp{["-/]}
 is perfectly valid in ASCII, but is not valid in many Unicode locales,
-such as @samp{en_US.UTF-8}.
+such as @code{en_US.UTF-8}.
 
 Early versions of @command{gawk} used regexp matching code that was not
 locale aware, so ranges had their traditional interpretation.
@@ -32836,18 +35160,19 @@ When @command{gawk} switched to using locale-aware regexp matchers,
 the problems began; especially as both GNU/Linux and commercial Unix
 vendors started implementing non-ASCII locales, @emph{and making them
 the default}.  Perhaps the most frequently asked question became something
-like ``why does @code{[A-Z]} match lowercase letters?!?''
+like ``why does @samp{[A-Z]} match lowercase letters?!?''
 
+@cindex Berry, Karl
 This situation existed for close to 10 years, if not more, and
 the @command{gawk} maintainer grew weary of trying to explain that
 @command{gawk} was being nicely standards-compliant, and that the issue
-was in the user's locale.  During the development of version 4.0,
+was in the user's locale.  During the development of @value{PVERSION} 4.0,
 he modified @command{gawk} to always treat ranges in the original,
 pre-POSIX fashion, unless @option{--posix} was used (@pxref{Options}).@footnote{And
-thus was born the Campain for Rational Range Interpretation (or RRI). A number
-of GNU tools, such as @command{grep} and @command{sed}, have either
-implemented this change, or will soon.  Thanks to Karl Berry for coining the phrase
-``Rational Range Interpretation.''}
+thus was born the Campaign for Rational Range Interpretation (or
+RRI). A number of GNU tools have either implemented this change,
+or will soon.  Thanks to Karl Berry for coining the phrase ``Rational
+Range Interpretation.''}
 
 Fortunately, shortly before the final release of @command{gawk} 4.0,
 the maintainer learned that the 2008 standard had changed the
@@ -32860,7 +35185,7 @@ and
 By using this lovely technical term, the standard gives license
 to implementors to implement ranges in whatever way they choose.
 The @command{gawk} maintainer chose to apply the pre-POSIX meaning in all
-cases: the default regexp matching; with @option{--traditional}, and with
+cases: the default regexp matching; with @option{--traditional} and with
 @option{--posix}; in all cases, @command{gawk} remains POSIX compliant.
 
 @node Contributors
@@ -32874,7 +35199,7 @@ cases: the default regexp matching; with @option{--traditional}, and with
 This @value{SECTION} names the major contributors to @command{gawk}
 and/or this @value{DOCUMENT}, in approximate chronological order:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @cindex Aho, Alfred
 @cindex Weinberger, Peter
@@ -32954,8 +35279,8 @@ provided the initial port to OS/2 and its documentation.
 Michal Jaegermann
 provided the port to Atari systems and its documentation.
 (This port is no longer supported.)
-He continues to provide portability checking with DEC Alpha
-systems, and has done a lot of work to make sure @command{gawk}
+He continues to provide portability checking,
+and has done a lot of work to make sure @command{gawk}
 works on non-32-bit systems.
 
 @item
@@ -33026,7 +35351,7 @@ provided the port to BeOS and its documentation.
 @cindex Peters, Arno
 Arno Peters
 did the initial work to convert @command{gawk} to use
-GNU Automake and GNU @code{gettext}.
+GNU Automake and GNU @command{gettext}.
 
 @item
 @cindex Broder, Alan J.@:
@@ -33056,17 +35381,25 @@ environments.
 (This is no longer supported)
 
 @item
+@cindex Wallin, Anders
+Anders Wallin helped keep the VMS port going for several years.
+
+@item
+@cindex Gordon, Assaf
+Assaf Gordon contributed the code to implement the
+@option{--sandbox} option.
+
+@item
 @cindex Haque, John
 John Haque made the following contributions:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The modifications to convert @command{gawk}
 into a byte-code interpreter, including the debugger.
 
 @item
-The addition of true multidimensional arrays.
-@ref{Arrays of Arrays}.
+The addition of true arrays of arrays.
 
 @item
 The additional modifications for support of arbitrary precision arithmetic.
@@ -33087,6 +35420,10 @@ The improved array sorting features were driven by John together
 with Pat Rankin.
 @end itemize
 
+@cindex Papadopoulos, Panos
+@item
+Panos Papadopoulos contributed the original text for @ref{Include Files}.
+
 @item
 @cindex Yawitz, Efraim
 Efraim Yawitz contributed the original text for @ref{Debugger}.
@@ -33099,17 +35436,57 @@ Arnold Robbins and Andrew Schorr, with notable contributions from
 the rest of the development team.
 
 @item
+@cindex Colombo, Antonio
+Antonio Giovanni Colombo rewrote a number of examples in the early
+chapters that were severely dated, for which I am incredibly grateful.
+
+@item
 @cindex Robbins, Arnold
 Arnold Robbins
 has been working on @command{gawk} since 1988, at first
 helping David Trueman, and as the primary maintainer since around 1994.
 @end itemize
 
+@node History summary
+@appendixsec Summary
+
+@itemize @value{BULLET}
+@item
+The @command{awk} language has evolved over time. The first release
+was with V7 Unix circa 1978.  In 1987 for System V Release 3.1,
+major additions, including user-defined functions, were made to the language.
+Additional changes were made for System V Release 4, in 1989.
+Since then, further minor changes happen under the auspices of the
+POSIX standard.
+
+@item
+Brian Kernighan's @command{awk} provides a small number of extensions
+that are implemented in common with other versions of @command{awk}.
+
+@item
+@command{gawk} provides a large number of extensions over POSIX @command{awk}.
+They can be disabled with either the @option{--traditional} or @option{--posix}
+options.
+
+@item
+The interaction of POSIX locales and regexp matching in @command{gawk} has been confusing over
+the years. Today, @command{gawk} implements Rational Range Interpretation, where
+ranges of the form @samp{[a-z]} match @emph{only} the characters numerically between
+@samp{a} through @samp{z} in the machine's native character set.  Usually this is ASCII
+but it can be EBCDIC on IBM S/390 systems.
+
+@item
+Many people have contributed to @command{gawk} development over the years.
+We hope that the list provided in this @value{CHAPTER} is complete and gives
+the appropriate credit where credit is due.
+
+@end itemize
+
 @node Installation
 @appendix Installing @command{gawk}
 
 @c last two commas are part of see also
-@cindex operating systems, See Also GNU/Linux, PC operating systems, Unix
+@cindex operating systems, See Also GNU/Linux@comma{} PC operating systems@comma{} Unix
 @c STARTOFRANGE gligawk
 @cindex @command{gawk}, installing
 @c STARTOFRANGE ingawk
@@ -33130,6 +35507,7 @@ the respective ports.
 * Bugs::                        Reporting Problems and Bugs.
 * Other Versions::              Other freely available @command{awk}
                                 implementations.
+* Installation summary::        Summary of installation.
 @end menu
 
 @node Gawk Distribution
@@ -33149,9 +35527,9 @@ subdirectories.
 @node Getting
 @appendixsubsec Getting the @command{gawk} Distribution
 @cindex @command{gawk}, source code@comma{} obtaining
-There are three ways to get GNU software:
+There are two ways to get GNU software:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Copy it from someone else who already has it.
 
@@ -33190,7 +35568,6 @@ file and then use @code{tar} to extract it.  You can use the following
 pipeline to produce the @command{gawk} distribution:
 
 @example
-# Under System V, add 'o' to the tar options
 gzip -d -c gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz | tar -xvpf -
 @end example
 
@@ -33206,7 +35583,7 @@ Extracting the archive
 creates a directory named @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}
 in the current directory.
 
-The distribution file name is of the form
+The distribution @value{FN} is of the form
 @file{gawk-@var{V}.@var{R}.@var{P}.tar.gz}.
 The @var{V} represents the major version of @command{gawk},
 the @var{R} represents the current release of version @var{V}, and
@@ -33345,8 +35722,8 @@ actual @file{Makefile} for creating the documentation.
 
 @item Makefile.am
 @itemx */Makefile.am
-Files used by the GNU @command{automake} software for generating
-the @file{Makefile.in} files used by @command{autoconf} and
+Files used by the GNU Automake software for generating
+the @file{Makefile.in} files used by Autoconf and
 @command{configure}.
 
 @item Makefile.in
@@ -33389,15 +35766,23 @@ They are installed as part of the installation process.
 The rest of the programs in this @value{DOCUMENT} are available in appropriate
 subdirectories of @file{awklib/eg}.
 
+@item extension/*
+The source code, manual pages, and infrastructure files for
+the sample extensions included with @command{gawk}.
+@xref{Dynamic Extensions}, for more information.
+
 @item posix/*
 Files needed for building @command{gawk} on POSIX-compliant systems.
 
 @item pc/*
-Files needed for building @command{gawk} under MS-Windows and OS/2
+Files needed for building @command{gawk} under MS-Windows
+@ifclear FOR_PRINT
+and OS/2
+@end ifclear
 (@pxref{PC Installation}, for details).
 
 @item vms/*
-Files needed for building @command{gawk} under VMS
+Files needed for building @command{gawk} under Vax/VMS and OpenVMS
 (@pxref{VMS Installation}, for details).
 
 @item test/*
@@ -33434,9 +35819,9 @@ to @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}.  Like most GNU software,
 @command{gawk} is configured
 automatically for your system by running the @command{configure} program.
 This program is a Bourne shell script that is generated automatically using
-GNU @command{autoconf}.
+GNU Autoconf.
 @ifnotinfo
-(The @command{autoconf} software is
+(The Autoconf software is
 described fully in
 @cite{Autoconf---Generating Automatic Configuration Scripts},
 which can be found online at
@@ -33444,7 +35829,7 @@ which can be found online at
 the Free Software Foundation's web site}.)
 @end ifnotinfo
 @ifinfo
-(The @command{autoconf} software is described fully starting with
+(The Autoconf software is described fully starting with
 @inforef{Top, , Autoconf, autoconf,Autoconf---Generating Automatic Configuration Scripts}.)
 @end ifinfo
 
@@ -33492,7 +35877,7 @@ please send in a bug report (@pxref{Bugs}).
 
 Of course, once you've built @command{gawk}, it is likely that you will
 wish to install it.  To do so, you need to run the command @samp{make
-check}, as a user with the appropriate permissions.  How to do this
+install}, as a user with the appropriate permissions.  How to do this
 varies by system, but on many systems you can use the @command{sudo}
 command to do so.  The command then becomes @samp{sudo make install}. It
 is likely that you will be asked for your password, and you will have
@@ -33509,7 +35894,7 @@ command line when compiling @command{gawk} from scratch, including:
 
 @table @code
 
-@cindex @code{--disable-extensions} configuration option
+@cindex @option{--disable-extensions} configuration option
 @cindex configuration option, @code{--disable-extensions}
 @item --disable-extensions
 Disable configuring and building the sample extensions in the
@@ -33517,7 +35902,7 @@ Disable configuring and building the sample extensions in the
 The default action is to dynamically check if the extensions
 can be configured and compiled.
 
-@cindex @code{--disable-lint} configuration option
+@cindex @option{--disable-lint} configuration option
 @cindex configuration option, @code{--disable-lint}
 @item --disable-lint
 Disable all lint checking within @code{gawk}.  The
@@ -33537,17 +35922,17 @@ Using this option may bring you some slight performance improvement.
 Using this option will cause some of the tests in the test suite
 to fail.  This option may be removed at a later date.
 
-@cindex @code{--disable-nls} configuration option
+@cindex @option{--disable-nls} configuration option
 @cindex configuration option, @code{--disable-nls}
 @item --disable-nls
 Disable all message-translation facilities.
 This is usually not desirable, but it may bring you some slight performance
 improvement.
 
-@cindex @code{--with-whiny-user-strftime} configuration option
+@cindex @option{--with-whiny-user-strftime} configuration option
 @cindex configuration option, @code{--with-whiny-user-strftime}
 @item  --with-whiny-user-strftime
-Force use of the included version of the @code{strftime()}
+Force use of the included version of the C @code{strftime()}
 function for deficient systems.
 @end table
 
@@ -33594,9 +35979,9 @@ should not have.  @file{custom.h} is automatically included by
 @file{config.h}.
 
 It is also possible that the @command{configure} program generated by
-@command{autoconf} will not work on your system in some other fashion.
+Autoconf will not work on your system in some other fashion.
 If you do have a problem, the file @file{configure.ac} is the input for
-@command{autoconf}.  You may be able to change this file and generate a
+Autoconf.  You may be able to change this file and generate a
 new version of @command{configure} that works on your system
 (@pxref{Bugs},
 for information on how to report problems in configuring @command{gawk}).
@@ -33624,16 +36009,21 @@ various non-Unix systems.
 @cindex PC operating systems@comma{} @command{gawk} on, installing
 @cindex operating systems, PC@comma{} @command{gawk} on, installing
 This @value{SECTION} covers installation and usage of @command{gawk} on x86 machines
+@ifclear FOR_PRINT
 running MS-DOS, any version of MS-Windows, or OS/2.
+@end ifclear
+@ifset FOR_PRINT
+running MS-DOS and any version of MS-Windows.
+@end ifset
 In this @value{SECTION}, the term ``Windows32''
-refers to any of Microsoft Windows-95/98/ME/NT/2000/XP/Vista/7.
+refers to any of Microsoft Windows-95/98/ME/NT/2000/XP/Vista/7/8.
 
-The limitations of MS-DOS (and MS-DOS shells under Windows32 or OS/2) has meant
-that various ``DOS extenders'' are often used with programs such as
-@command{gawk}.  The varying capabilities of Microsoft Windows 3.1
-and Windows32 can add to the confusion.  For an overview of the
-considerations, please refer to @file{README_d/README.pc} in the
-distribution.
+The limitations of MS-DOS (and MS-DOS shells under the other operating
+systems) has meant that various ``DOS extenders'' are often used with
+programs such as @command{gawk}.  The varying capabilities of Microsoft
+Windows 3.1 and Windows32 can add to the confusion.  For an overview
+of the considerations, please refer to @file{README_d/README.pc} in
+the distribution.
 
 @menu
 * PC Binary Installation::      Installing a prepared distribution.
@@ -33647,6 +36037,7 @@ distribution.
 * MSYS::                        Using @command{gawk} In The MSYS Environment.
 @end menu
 
+@ifclear FOR_PRINT
 @node PC Binary Installation
 @appendixsubsubsec Installing a Prepared Distribution for PC Systems
 
@@ -33685,13 +36076,21 @@ install-info --info-dir=x:/usr/info x:/usr/info/gawkinet.info
 
 The binary distribution may contain a separate file containing additional
 or more detailed installation instructions.
+@end ifclear
 
 @node PC Compiling
 @appendixsubsubsec Compiling @command{gawk} for PC Operating Systems
 
+@ifclear FOR_PRINT
 @command{gawk} can be compiled for MS-DOS, Windows32, and OS/2 using the GNU
-development tools from DJ Delorie (DJGPP: MS-DOS only) or Eberhard
-Mattes (EMX: MS-DOS, Windows32 and OS/2).  The file
+development tools from DJ Delorie (DJGPP: MS-DOS only), MinGW (Windows32) or Eberhard
+Mattes (EMX: MS-DOS, Windows32 and OS/2).
+@end ifclear
+@ifset FOR_PRINT
+@command{gawk} can be compiled for MS-DOS and Windows32 using the GNU
+development tools from DJ Delorie (DJGPP: MS-DOS only) or MinGW (Windows32).
+@end ifset
+The file
 @file{README_d/README.pc} in the @command{gawk} distribution contains
 additional notes, and @file{pc/Makefile} contains important information on
 compilation options.
@@ -33713,6 +36112,7 @@ build @command{gawk} using the DJGPP tools, enter @samp{make djgpp}.
 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/}.)  To build a
 native MS-Windows binary of @command{gawk}, type @samp{make mingw32}.
 
+@ifclear FOR_PRINT
 @cindex compiling @command{gawk} with EMX for OS/2
 The 32 bit EMX version of @command{gawk} works ``out of the box'' under OS/2.
 However, it is highly recommended to use GCC 2.95.3 for the compilation.
@@ -33747,7 +36147,7 @@ and @option{--libexecdir=c:/usr/lib}.
 @end ignore
 
 @ignore
-The internal @code{gettext} library tends to be problematic. It is therefore recommended
+The internal @command{gettext} library tends to be problematic. It is therefore recommended
 to use either an external one (@option{--without-included-gettext}) or to disable
 NLS entirely (@option{--disable-nls}).
 @end ignore
@@ -33784,8 +36184,11 @@ Ancient OS/2 ports of GNU @command{make} are not able to handle
 the Makefiles of this package.  If you encounter any problems with
 @command{make}, try GNU Make 3.79.1 or later versions.  You should
 find the latest version on
-@uref{ftp://hobbes.nmsu.edu/pub/os2/}.
+@uref{ftp://hobbes.nmsu.edu/pub/os2/}.@footnote{As of May, 2014,
+this site is still there, but the author could not find a package
+for GNU Make.}
 @end quotation
+@end ifclear
 
 @node PC Testing
 @appendixsubsubsec Testing @command{gawk} on PC Operating Systems
@@ -33797,6 +36200,7 @@ be converted so that they have the usual MS-DOS-style end-of-line markers.
 Alternatively, run @command{make check CMP="diff -a"} to use GNU @command{diff}
 in text mode instead of @command{cmp} to compare the resulting files.
 
+@ifclear FOR_PRINT
 Most
 of the tests work properly with Stewartson's shell along with the
 companion utilities or appropriate GNU utilities.  However, some editing of
@@ -33809,7 +36213,7 @@ On OS/2 the @code{pid} test fails because @code{spawnl()} is used instead of
 @code{fork()}/@code{execl()} to start child processes.
 Also the @code{mbfw1} and @code{mbprintf1} tests fail because the needed
 multibyte functionality is not available.
-
+@end ifclear
 
 @node PC Using
 @appendixsubsubsec Using @command{gawk} on PC Operating Systems
@@ -33818,15 +36222,15 @@ multibyte functionality is not available.
 @c STARTOFRANGE pcgawon
 @cindex PC operating systems, @command{gawk} on
 
-With the exception of the Cygwin environment,
-the @samp{|&} operator and TCP/IP networking
-(@pxref{TCP/IP Networking})
-are not supported for MS-DOS or MS-Windows.  EMX (OS/2 only) does support
-at least the @samp{|&} operator.
+Under MS-DOS and MS-Windows, the Cygwin and MinGW environments support
+both the @samp{|&} operator and TCP/IP networking
+(@pxref{TCP/IP Networking}).
+@ifclear FOR_PRINT
+EMX (OS/2 only) supports at least the @samp{|&} operator.
+@end ifclear
 
 @cindex search paths
 @cindex search paths, for source files
-@cindex @command{gawk}, OS/2 version of
 @cindex @command{gawk}, MS-DOS version of
 @cindex @command{gawk}, MS-Windows version of
 @cindex @code{;} (semicolon), @code{AWKPATH} variable and
@@ -33837,36 +36241,50 @@ program files as described in @ref{AWKPATH Variable}.  However,
 semicolons (rather than colons) separate elements in the @env{AWKPATH}
 variable.  If @env{AWKPATH} is not set or is empty, then the default
 search path for MS-Windows and MS-DOS versions is
-@code{@w{".;c:/lib/awk;c:/gnu/lib/awk"}}.
+@samp{@w{.;c:/lib/awk;c:/gnu/lib/awk}}.
 
+@ifclear FOR_PRINT
+@cindex @command{gawk}, OS/2 version of
 @cindex @code{UNIXROOT} variable, on OS/2 systems
 The search path for OS/2 (32 bit, EMX) is determined by the prefix directory
 (most likely @file{/usr} or @file{c:/usr}) that has been specified as an option of
-the @command{configure} script like it is the case for the Unix versions.
+the @command{configure} script as is the case for the Unix versions.
 If @file{c:/usr} is the prefix directory then the default search path contains @file{.}
 and @file{c:/usr/share/awk}.
 Additionally, to support binary distributions of @command{gawk} for OS/2
-systems whose drive @samp{c:} might not support long file names or might not exist
+systems whose drive @samp{c:} might not support long @value{FN}s or might not exist
 at all, there is a special environment variable.  If @env{UNIXROOT} specifies
 a drive then this specific drive is also searched for program files.
 E.g., if @env{UNIXROOT} is set to @file{e:} the complete default search path is
-@code{@w{".;c:/usr/share/awk;e:/usr/share/awk"}}.
+@samp{@w{.;c:/usr/share/awk;e:/usr/share/awk}}.
 
 An @command{sh}-like shell (as opposed to @command{command.com} under MS-DOS
 or @command{cmd.exe} under MS-Windows or OS/2) may be useful for @command{awk} programming.
 The DJGPP collection of tools includes an MS-DOS port of Bash,
 and several shells are available for OS/2, including @command{ksh}.
+@end ifclear
+@ifset FOR_PRINT
+An @command{sh}-like shell (as opposed to @command{command.com} under MS-DOS
+or @command{cmd.exe} under MS-Windows) may be useful for @command{awk} programming.
+The DJGPP collection of tools includes an MS-DOS port of Bash.
+@end ifset
 
 @cindex common extensions, @code{BINMODE} variable
 @cindex extensions, common@comma{} @code{BINMODE} variable
 @cindex differences in @command{awk} and @command{gawk}, @code{BINMODE} variable
 @cindex @code{BINMODE} variable
-Under MS-Windows, OS/2 and MS-DOS, @command{gawk} (and many other text programs) silently
-translate end-of-line @code{"\r\n"} to @code{"\n"} on input and @code{"\n"}
-to @code{"\r\n"} on output.  A special @code{BINMODE} variable @value{COMMONEXT}
+@ifclear FOR_PRINT
+Under MS-Windows, OS/2 and MS-DOS,
+@end ifclear
+@ifset FOR_PRINT
+Under MS-Windows and MS-DOS,
+@end ifset
+@command{gawk} (and many other text programs) silently
+translate end-of-line @samp{\r\n} to @samp{\n} on input and @samp{\n}
+to @samp{\r\n} on output.  A special @code{BINMODE} variable @value{COMMONEXT}
 allows control over these translations and is interpreted as follows:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 If @code{BINMODE} is @code{"r"}, or one,
 then
@@ -33904,7 +36322,7 @@ The name @code{BINMODE} was chosen to match @command{mawk}
 @command{mawk} adds a @samp{-W BINMODE=@var{N}} option and an environment
 variable that can set @code{BINMODE}, @code{RS}, and @code{ORS}.  The
 files @file{binmode[1-3].awk} (under @file{gnu/lib/awk} in some of the
-prepared distributions) have been chosen to match @command{mawk}'s @samp{-W
+prepared binary distributions) have been chosen to match @command{mawk}'s @samp{-W
 BINMODE=@var{N}} option.  These can be changed or discarded; in particular,
 the setting of @code{RS} giving the fewest ``surprises'' is open to debate.
 @command{mawk} uses @samp{RS = "\r\n"} if binary mode is set on read, which is
@@ -33952,7 +36370,7 @@ moved into the @code{BEGIN} rule.
 
 @command{gawk} can be built and used ``out of the box'' under MS-Windows
 if you are using the @uref{http://www.cygwin.com, Cygwin environment}.
-This environment provides an excellent simulation of Unix, using the
+This environment provides an excellent simulation of GNU/Linux, using the
 GNU tools, such as Bash, the GNU Compiler Collection (GCC), GNU Make,
 and other GNU programs.  Compilation and installation for Cygwin is the
 same as for a Unix system:
@@ -33968,13 +36386,6 @@ When compared to GNU/Linux on the same system, the @samp{configure}
 step on Cygwin takes considerably longer.  However, it does finish,
 and then the @samp{make} proceeds as usual.
 
-@quotation NOTE
-The @samp{|&} operator and TCP/IP networking
-(@pxref{TCP/IP Networking})
-are fully supported in the Cygwin environment.  This is not true
-for any other environment on MS-Windows.
-@end quotation
-
 @node MSYS
 @appendixsubsubsec Using @command{gawk} In The MSYS Environment
 
@@ -33987,7 +36398,7 @@ been ported to MS-Windows that expect @command{gawk} to do automatic
 translation of @code{"\r\n"}, since it won't.  Caveat Emptor!
 
 @node VMS Installation
-@appendixsubsec How to Compile and Install @command{gawk} on VMS
+@appendixsubsec How to Compile and Install @command{gawk} on Vax/VMS and OpenVMS
 
 @c based on material from Pat Rankin <rankin@eql.caltech.edu>
 @c now rankin@pactechdata.com
@@ -34000,8 +36411,11 @@ The older designation ``VMS'' is used throughout to refer to OpenVMS.
 
 @menu
 * VMS Compilation::             How to compile @command{gawk} under VMS.
+* VMS Dynamic Extensions::      Compiling @command{gawk} dynamic extensions on
+                                VMS.
 * VMS Installation Details::    How to install @command{gawk} under VMS.
 * VMS Running::                 How to run @command{gawk} under VMS.
+* VMS GNV::                     The VMS GNV Project.
 * VMS Old Gawk::                An old version comes with some VMS systems.
 @end menu
 
@@ -34009,41 +36423,110 @@ The older designation ``VMS'' is used throughout to refer to OpenVMS.
 @appendixsubsubsec Compiling @command{gawk} on VMS
 @cindex compiling @command{gawk} for VMS
 
-To compile @command{gawk} under VMS, there is a @code{DCL} command procedure that
-issues all the necessary @code{CC} and @code{LINK} commands. There is
-also a @file{Makefile} for use with the @code{MMS} utility.  From the source
-directory, use either:
+To compile @command{gawk} under VMS, there is a @code{DCL} command procedure
+that issues all the necessary @code{CC} and @code{LINK} commands. There is
+also a @file{Makefile} for use with the @code{MMS} and @code{MMK} utilities.
+From the source directory, use either:
 
 @example
-$ @kbd{@@[.VMS]VMSBUILD.COM}
+$ @kbd{@@[.vms]vmsbuild.com}
 @end example
 
 @noindent
 or:
 
 @example
-$ @kbd{MMS/DESCRIPTION=[.VMS]DESCRIP.MMS GAWK}
+$ @kbd{MMS/DESCRIPTION=[.vms]descrip.mms gawk}
 @end example
 
-Older versions of @command{gawk} could be built with VAX C or
-GNU C on VAX/VMS, as well as with DEC C, but that is no longer
-supported.  DEC C (also briefly known as ``Compaq C'' and now known
-as ``HP C,'' but referred to here as ``DEC C'') is required.  Both
-@code{VMSBUILD.COM} and @code{DESCRIP.MMS} contain some obsolete support
-for the older compilers but are set up to use DEC C by default.
+@noindent
+or:
+
+@example
+$ @kbd{MMK/DESCRIPTION=[.vms]descrip.mms gawk}
+@end example
+
+@command{MMK} is an open source, free, near-clone of @command{MMS} and
+can better handle ODS-5 volumes with upper- and lowercase @value{FN}s.
+@command{MMK} is available from @uref{https://github.com/endlesssoftware/mmk}.
+
+With ODS-5 volumes and extended parsing enabled, the case of the target
+parameter may need to be exact.
 
-@command{gawk} has been tested under Alpha/VMS 7.3-1 using Compaq C V6.4,
-and on Alpha/VMS 7.3, Alpha/VMS 7.3-2, and IA64/VMS 8.3.@footnote{The IA64
-architecture is also known as ``Itanium.''}
+@command{gawk} has been tested under VAX/VMS 7.3 and Alpha/VMS 7.3-1
+using Compaq C V6.4, and Alpha/VMS 7.3, Alpha/VMS 7.3-2, and IA64/VMS 8.3.
+The most recent builds used HP C V7.3 on Alpha VMS 8.3 and both
+Alpha and IA64 VMS 8.4 used HP C 7.3.@footnote{The IA64 architecture
+is also known as ``Itanium.''}
+
+@xref{VMS GNV}, for information on building
+@command{gawk} as a PCSI kit that is compatible with the GNV product.
+
+@node VMS Dynamic Extensions
+@appendixsubsubsec Compiling @command{gawk} Dynamic Extensions on VMS
+
+The extensions that have been ported to VMS can be built using one of
+the following commands.
+
+@example
+$ @kbd{MMS/DESCRIPTION=[.vms]descrip.mms extensions}
+@end example
+
+@noindent
+or:
+
+@example
+$ @kbd{MMK/DESCRIPTION=[.vms]descrip.mms extensions}
+@end example
+
+@command{gawk} uses @code{AWKLIBPATH} as either an environment variable
+or a logical name to find the dynamic extensions.
+
+Dynamic extensions need to be compiled with the same compiler options for
+floating point, pointer size, and symbol name handling as were used
+to compile @command{gawk} itself.
+Alpha and Itanium should use IEEE floating point.  The pointer size is 32 bits,
+and the symbol name handling should be exact case with CRC shortening for
+symbols longer than 32 bits.
+
+For Alpha and Itanium:
+
+@example
+/name=(as_is,short)
+/float=ieee/ieee_mode=denorm_results
+@end example
+
+For VAX:
+
+@example
+/name=(as_is,short)
+@end example
+
+Compile time macros need to be defined before the first VMS-supplied
+header file is included.
+
+@example
+#if (__CRTL_VER >= 70200000) && !defined (__VAX)
+#define _LARGEFILE 1
+#endif
+
+#ifndef __VAX
+#ifdef __CRTL_VER
+#if __CRTL_VER >= 80200000
+#define _USE_STD_STAT 1
+#endif
+#endif
+#endif
+@end example
 
 @node VMS Installation Details
 @appendixsubsubsec Installing @command{gawk} on VMS
 
-To install @command{gawk}, all you need is a ``foreign'' command, which is
-a @code{DCL} symbol whose value begins with a dollar sign. For example:
+To use @command{gawk}, all you need is a ``foreign'' command, which is a
+@code{DCL} symbol whose value begins with a dollar sign. For example:
 
 @example
-$ @kbd{GAWK :== $disk1:[gnubin]GAWK}
+$ @kbd{GAWK :== $disk1:[gnubin]gawk}
 @end example
 
 @noindent
@@ -34055,10 +36538,29 @@ Alternatively, the symbol may be placed in the system-wide
 @file{sylogin.com} procedure, which allows all users
 to run @command{gawk}.
 
-Optionally, the help entry can be loaded into a VMS help library:
+If your @command{gawk} was installed by a PCSI kit into the
+@file{GNV$GNU:} directory tree, the program will be known as
+@file{GNV$GNU:[bin]gnv$gawk.exe} and the help file will be
+@file{GNV$GNU:[vms_help]gawk.hlp}.
+
+The PCSI kit also installs a @file{GNV$GNU:[vms_bin]gawk_verb.cld} file
+which can be used to add @command{gawk} and @command{awk} as DCL commands.
+
+For just the current process you can use:
+
+@example
+$ @kbd{set command gnv$gnu:[vms_bin]gawk_verb.cld}
+@end example
+
+Or the system manager can use @file{GNV$GNU:[vms_bin]gawk_verb.cld} to
+add the @command{gawk} and @command{awk} to the system wide @samp{DCLTABLES}.
+
+The DCL syntax is documented in the @file{gawk.hlp} file.
+
+Optionally, the @file{gawk.hlp} entry can be loaded into a VMS help library:
 
 @example
-$ @kbd{LIBRARY/HELP SYS$HELP:HELPLIB [.VMS]GAWK.HLP}
+$ @kbd{LIBRARY/HELP sys$help:helplib [.vms]gawk.hlp}
 @end example
 
 @noindent
@@ -34076,11 +36578,11 @@ provides information about both the @command{gawk} implementation and the
 
 The logical name @samp{AWK_LIBRARY} can designate a default location
 for @command{awk} program files.  For the @option{-f} option, if the specified
-file name has no device or directory path information in it, @command{gawk}
+@value{FN} has no device or directory path information in it, @command{gawk}
 looks in the current directory first, then in the directory specified
 by the translation of @samp{AWK_LIBRARY} if the file is not found.
 If, after searching in both directories, the file still is not found,
-@command{gawk} appends the suffix @samp{.awk} to the filename and retries
+@command{gawk} appends the suffix @samp{.awk} to the @value{FN} and retries
 the file search.  If @samp{AWK_LIBRARY} has no definition, a default value
 of @samp{SYS$LIBRARY:} is used for it.
 
@@ -34109,9 +36611,42 @@ One side effect of dual command-line parsing is that if there is only a
 single parameter (as in the quoted string program above), the command
 becomes ambiguous.  To work around this, the normally optional @option{--}
 flag is required to force Unix-style parsing rather than @code{DCL} parsing.  If any
-other dash-type options (or multiple parameters such as data files to
+other dash-type options (or multiple parameters such as @value{DF}s to
 process) are present, there is no ambiguity and @option{--} can be omitted.
 
+@cindex exit status, of VMS
+The @code{exit} value is a Unix-style value and is encoded to a VMS exit
+status value when the program exits.
+
+The VMS severity bits will be set based on the @code{exit} value.
+A failure is indicated by 1 and VMS sets the @code{ERROR} status.
+A fatal error is indicated by 2 and VMS will set the @code{FATAL} status.
+All other values will have the @code{SUCCESS} status.  The exit value is
+encoded to comply with VMS coding standards and will have the
+@code{C_FACILITY_NO} of @code{0x350000} with the constant @code{0xA000}
+added to the number shifted over by 3 bits to make room for the severity codes.
+
+To extract the actual @command{gawk} exit code from the VMS status use:
+
+@example
+unix_status = (vms_status .and. &x7f8) / 8
+@end example
+
+@noindent
+A C program that uses @code{exec()} to call @command{gawk} will get the original
+Unix-style exit value.
+
+Older versions of @command{gawk} treated a Unix exit code 0 as 1, a failure
+as 2, a fatal error as 4, and passed all the other numbers through.
+This violated the VMS exit status coding requirements.
+
+@cindex floating-point, VAX/VMS
+VAX/VMS floating point uses unbiased rounding. @xref{Round Function}.
+
+VMS reports time values in GMT unless one of the @code{SYS$TIMEZONE_RULE}
+or @code{TZ} logical names is set.  Older versions of VMS, such as VAX/VMS
+7.3 do not set these logical names.
+
 @c @cindex directory search
 @c @cindex path, search
 @cindex search paths
@@ -34123,6 +36658,21 @@ of @env{AWKPATH} is a comma-separated list of directory specifications.
 When defining it, the value should be quoted so that it retains a single
 translation and not a multitranslation @code{RMS} searchlist.
 
+@node VMS GNV
+@appendixsubsubsec The VMS GNV Project
+
+The VMS GNV package provides a build environment similar to POSIX with ports
+of a collection of open source tools.  The @command{gawk} found in the GNV
+base kit is an older port.  Currently the GNV project is being reorganized
+to supply individual PCSI packages for each component.
+See @w{@uref{https://sourceforge.net/p/gnv/wiki/InstallingGNVPackages/}.}
+
+The normal build procedure for @command{gawk} produces a program that
+is suitable for use with GNV.
+
+The @file{vms/gawk_build_steps.txt} in the source documents the procedure
+for building a VMS PCSI kit that is compatible with GNV.
+
 @ignore
 @c The VMS POSIX product, also known as POSIX for OpenVMS, is long defunct
 @c and building gawk for it has not been tested in many years, but these
@@ -34170,7 +36720,7 @@ define a symbol, as follows:
 $ @kbd{gawk :== $sys$common:[syshlp.examples.tcpip.snmp]gawk.exe}
 @end example
 
-This is apparently version 2.15.6, which is extremely old. We
+This is apparently @value{PVERSION} 2.15.6, which is extremely old. We
 recommend compiling and using the current version.
 
 @c ENDOFRANGE opgawx
@@ -34199,8 +36749,8 @@ what you're trying to do.  If it's not clear whether you should be able
 to do something or not, report that too; it's a bug in the documentation!
 
 Before reporting a bug or trying to fix it yourself, try to isolate it
-to the smallest possible @command{awk} program and input data file that
-reproduces the problem.  Then send us the program and data file,
+to the smallest possible @command{awk} program and input @value{DF} that
+reproduces the problem.  Then send us the program and @value{DF},
 some idea of what kind of Unix system you're using,
 the compiler you used to compile @command{gawk}, and the exact results
 @command{gawk} gave you.  Also say what you expected to occur; this helps
@@ -34216,12 +36766,14 @@ Once you have a precise problem, send email to
 @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}.
 
 @cindex Robbins, Arnold
-Using this address automatically sends a copy of your
-mail to me.  If necessary, I can be reached directly at
+The @command{gawk} maintainers subscribe to this address and
+thus they will receive your bug report.
+If necessary, the primary maintainer can be reached directly at
 @EMAIL{arnold@@skeeve.com,arnold at skeeve dot com}.
 The bug reporting address is preferred since the
 email list is archived at the GNU Project.
-@emph{All email should be in English, since that is my native language.}
+@emph{All email should be in English. This is the only language
+understood in common by all the maintainers.}
 
 @cindex @code{comp.lang.awk} newsgroup
 @quotation CAUTION
@@ -34254,32 +36806,39 @@ mail at the Internet address noted previously.
 
 If you find bugs in one of the non-Unix ports of @command{gawk}, please send
 an electronic mail message to the person who maintains that port.  They
-are named in the following list, as well as in the @file{README} file in the @command{gawk}
-distribution.  Information in the @file{README} file should be considered
-authoritative if it conflicts with this @value{DOCUMENT}.
+are named in the following list, as well as in the @file{README} file
+in the @command{gawk} distribution.  Information in the @file{README}
+file should be considered authoritative if it conflicts with this
+@value{DOCUMENT}.
 
 The people maintaining the non-Unix ports of @command{gawk} are
 as follows:
 
-@multitable {MS-Windows with MINGW} {123456789012345678901234567890123456789001234567890}
+@c put the index entries outside the table, for docbook
 @cindex Deifik, Scott
+@cindex Zaretskii, Eli
+@cindex Buening, Andreas
+@cindex Rankin, Pat
+@cindex Malmberg, John
+@cindex Pitts, Dave
+@multitable {MS-Windows with MinGW} {123456789012345678901234567890123456789001234567890}
 @item MS-DOS with DJGPP @tab Scott Deifik, @EMAIL{scottd.mail@@sbcglobal.net,scottd dot mail at sbcglobal dot net}.
 
-@cindex Zaretskii, Eli
-@item MS-Windows with MINGW @tab Eli Zaretskii, @EMAIL{eliz@@gnu.org,eliz at gnu dot org}.
+@item MS-Windows with MinGW @tab Eli Zaretskii, @EMAIL{eliz@@gnu.org,eliz at gnu dot org}.
 
-@cindex Buening, Andreas
+@c Leave this in the print version on purpose.
+@c OS/2 is not mentioned anywhere else in the print version though.
 @item OS/2 @tab Andreas Buening, @EMAIL{andreas.buening@@nexgo.de,andreas dot buening at nexgo dot de}.
 
-@cindex Rankin, Pat
-@item VMS @tab Pat Rankin, @EMAIL{r.pat.rankin@@gmail.com,r.pat.rankin at gmail.com}
+@item VMS @tab Pat Rankin, @EMAIL{r.pat.rankin@@gmail.com,r.pat.rankin at gmail.com}, and
+John Malmberg, @EMAIL{wb8tyw@@qsl.net,wb8tyw at qsl.net}.
 
-@cindex Pitts, Dave
 @item z/OS (OS/390) @tab Dave Pitts, @EMAIL{dpitts@@cozx.com,dpitts at cozx dot com}.
 @end multitable
 
 If your bug is also reproducible under Unix, please send a copy of your
-report to the @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org} email list as well.
+report to the @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org} email
+list as well.
 @c ENDOFRANGE dbugg
 @c ENDOFRANGE tblgawb
 
@@ -34308,7 +36867,7 @@ This @value{SECTION} briefly describes where to get them:
 @cindex Kernighan, Brian
 @cindex source code, Brian Kernighan's @command{awk}
 @cindex @command{awk}, versions of, See Also Brian Kernighan's @command{awk}
-@cindex Brian Kernighan's @command{awk}
+@cindex Brian Kernighan's @command{awk}, source code
 @item Unix @command{awk}
 Brian Kernighan, one of the original designers of Unix @command{awk},
 has made his implementation of
@@ -34328,6 +36887,7 @@ It is available in several archive formats:
 @uref{http://www.cs.princeton.edu/~bwk/btl.mirror/awk.zip}
 @end table
 
+@cindex @command{git} utility
 You can also retrieve it from Git Hub:
 
 @example
@@ -34347,12 +36907,17 @@ from GCC (the GNU Compiler Collection) works quite nicely.
 for a list of extensions in this @command{awk} that are not in POSIX @command{awk}.
 
 @cindex Brennan, Michael
-@cindex @command{mawk} program
+@cindex @command{mawk} utility
 @cindex source code, @command{mawk}
 @item @command{mawk}
 Michael Brennan wrote an independent implementation of @command{awk},
-called @command{mawk}.  It is available under the GPL
-(@pxref{Copying}),
+called @command{mawk}.  It is available under the
+@ifclear FOR_PRINT
+GPL (@pxref{Copying}),
+@end ifclear
+@ifset FOR_PRINT
+GPL,
+@end ifset
 just as @command{gawk} is.
 
 The original distribution site for the @command{mawk} source code
@@ -34393,7 +36958,7 @@ To get @command{awka}, go to @url{http://sourceforge.net/projects/awka}.
 The project seems to be frozen; no new code changes have been made
 since approximately 2003.
 
-@cindex Beebe, Nelson
+@cindex Beebe, Nelson H.F.@:
 @cindex @command{pawk} (profiling version of Brian Kernighan's @command{awk})
 @cindex source code, @command{pawk}
 @item @command{pawk}
@@ -34421,10 +36986,10 @@ information, see the @uref{http://busybox.net, project's home page}.
 @cindex Solaris, POSIX-compliant @command{awk}
 @cindex source code, Solaris @command{awk}
 @item The OpenSolaris POSIX @command{awk}
-The version of @command{awk} in @file{/usr/xpg4/bin} on Solaris is
-more-or-less POSIX-compliant. It is based on the @command{awk} from
-Mortice Kern Systems for PCs.
-This author was able to make it compile and work under GNU/Linux
+The versions of @command{awk} in @file{/usr/xpg4/bin} and
+@file{/usr/xpg6/bin} on Solaris are more-or-less POSIX-compliant.
+They are based on the @command{awk} from Mortice Kern Systems for PCs.
+This author was able to make this code compile and work under GNU/Linux
 with 1--2 hours of work.  Making it more generally portable (using
 GNU Autoconf and/or Automake) would take more work, and this
 has not been done, at least to our knowledge.
@@ -34456,6 +37021,7 @@ This is an embeddable @command{awk} interpreter derived from
 @uref{http://repo.hu/projects/libmawk/}.
 
 @item @code{pawk}
+@cindex source code, @command{pawk} (Python version)
 @cindex @code{pawk}, @command{awk}-like facilities for Python
 This is a Python module that claims to bring @command{awk}-like
 features to Python. See @uref{https://github.com/alecthomas/pawk}
@@ -34478,15 +37044,56 @@ under the GPL. It has a large number of extensions over standard
 See @uref{http://www.quiktrim.org/QTawk.html} for more information,
 including the manual and a download link.
 
+The project may also be frozen; no new code changes have been made
+since approximately 2008.
+
 @item Other Versions
 See also the @uref{http://en.wikipedia.org/wiki/Awk_language#Versions_and_implementations,
 Wikipedia article}, for information on additional versions.
 
 @end table
+@c ENDOFRANGE awkim
+
+@node Installation summary
+@appendixsec Summary
+
+@itemize @value{BULLET}
+@item
+The @command{gawk} distribution is available from GNU project's main
+distribution site, @code{ftp.gnu.org}.  The canonical build recipe is:
+
+@example
+wget http://ftp.gnu.org/gnu/gawk/gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz
+tar -xvpzf gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz
+cd gawk-@value{VERSION}.@value{PATCHLEVEL}
+./configure && make && make check
+@end example
+
+@item
+@command{gawk} may be built on non-POSIX systems as well. The currently
+supported systems are MS-Windows using DJGPP, MSYS, MinGW and Cygwin,
+@ifclear FOR_PRINT
+OS/2 using EMX,
+@end ifclear
+and both Vax/VMS and OpenVMS.
+Instructions for each system are included in this @value{CHAPTER}.
+
+@item
+Bug reports should be sent via email to @email{bug-gawk@@gnu.org}.
+Bug reports should be in English, and should include the version of @command{gawk},
+how it was compiled, and a short program and @value{DF} which demonstrate
+the problem.
+
+@item
+There are a number of other freely available @command{awk}
+implementations.  Many are POSIX compliant; others are less so.
+
+@end itemize
+
 @c ENDOFRANGE gligawk
 @c ENDOFRANGE ingawk
-@c ENDOFRANGE awkim
 
+@ifclear FOR_PRINT
 @node Notes
 @appendix Implementation Notes
 @c STARTOFRANGE gawii
@@ -34506,6 +37113,7 @@ maintainers of @command{gawk}.  Everything in it applies specifically to
 * Implementation Limitations::  Some limitations of the implementation.
 * Extension Design::            Design notes about the extension API.
 * Old Extension Mechanism::     Some compatibility for old extensions.
+* Notes summary::               Summary of implementation notes.
 @end menu
 
 @node Compatibility Mode
@@ -34526,7 +37134,7 @@ is one more option available on the command line:
 @table @code
 @item -Y
 @itemx --parsedebug
-Prints out the parse stack information as the program is being parsed.
+Print out the parse stack information as the program is being parsed.
 @end table
 
 This option is intended only for serious @command{gawk} developers
@@ -34550,8 +37158,8 @@ as well as any considerations you should bear in mind.
                                 @command{gawk}.
 * New Ports::                   Porting @command{gawk} to a new operating
                                 system.
-* Derived Files::               Why derived files are kept in the
-                                @command{git} repository.
+* Derived Files::               Why derived files are kept in the Git
+                                repository.
 @end menu
 
 @node Accessing The Source
@@ -34561,6 +37169,7 @@ As @command{gawk} is Free Software, the source code is always available.
 @ref{Gawk Distribution}, describes how to get and build the formal,
 released versions of @command{gawk}.
 
+@cindex @command{git} utility
 However, if you want to modify @command{gawk} and contribute back your
 changes, you will probably wish to work with the development version.
 To do so, you will need to access the @command{gawk} source code
@@ -34574,8 +37183,8 @@ git clone git://git.savannah.gnu.org/gawk.git
 @end example
 
 @noindent
-This will clone the @command{gawk} repository.  If you are behind a
-firewall that will not allow you to use the Git native protocol, you
+This clones the @command{gawk} repository.  If you are behind a
+firewall that does not allow you to use the Git native protocol, you
 can still access the repository using:
 
 @example
@@ -34603,7 +37212,7 @@ that has a Git plug-in for working with Git repositories.
 You are free to add any new features you like to @command{gawk}.
 However, if you want your changes to be incorporated into the @command{gawk}
 distribution, there are several steps that you need to take in order to
-make it possible to include your changes:
+make it possible to include them:
 
 @enumerate 1
 @item
@@ -34625,14 +37234,15 @@ or @EMAIL{assign@@gnu.org,assign at gnu dot org}.
 @item
 Get the latest version.
 It is much easier for me to integrate changes if they are relative to
-the most recent distributed version of @command{gawk}.  If your version of
-@command{gawk} is very old, I may not be able to integrate them at all.
+the most recent distributed version of @command{gawk}, or better yet,
+relative to the latest code in the Git repository.  If your version of
+@command{gawk} is very old, I may not be able to integrate your changes at all.
 (@xref{Getting},
 for information on getting the latest version of @command{gawk}.)
 
 @item
 @ifnotinfo
-Follow the @cite{GNU Coding Standards}.
+Follow the @uref{http://www.gnu.org/prep/standards/, @cite{GNU Coding Standards}}.
 @end ifnotinfo
 @ifinfo
 See @inforef{Top, , Version, standards, GNU Coding Standards}.
@@ -34653,7 +37263,7 @@ using the traditional ``K&R'' style, particularly as regards to the placement
 of braces and the use of TABs.  In brief, the coding rules for @command{gawk}
 are as follows:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Use ANSI/ISO style (prototype) function headers when defining functions.
 
@@ -34736,6 +37346,7 @@ If possible, please update the @command{man} page as well.
 
 You will also have to sign paperwork for your documentation changes.
 
+@cindex @command{git} utility
 @item
 Submit changes as unified diffs.
 Use @samp{diff -u -r -N} to compare
@@ -34756,6 +37367,7 @@ not do so, particularly if there are lots of changes.
 Include an entry for the @file{ChangeLog} file with your submission.
 This helps further minimize the amount of work I have to do,
 making it easier for me to accept patches.
+It is simplest if you just make this part of your diff.
 @end enumerate
 
 Although this sounds like a lot of work, please remember that while you
@@ -34791,11 +37403,9 @@ Be prepared to sign the appropriate paperwork.
 In order for the FSF to distribute your code, you must either place
 your code in the public domain and submit a signed statement to that
 effect, or assign the copyright in your code to the FSF.
-@ifinfo
 Both of these actions are easy to do and @emph{many} people have done so
 already. If you have questions, please contact me, or
 @email{gnu@@gnu.org}.
-@end ifinfo
 
 @item
 When doing a port, bear in mind that your code must coexist peacefully
@@ -34815,10 +37425,39 @@ A number of the files that come with @command{gawk} are maintained by other
 people.  Thus, you should not change them
 unless it is for a very good reason; i.e., changes are not out of the
 question, but changes to these files are scrutinized extra carefully.
-The files are @file{dfa.c}, @file{dfa.h}, @file{getopt1.c}, @file{getopt.c},
-@file{getopt.h}, @file{install-sh}, @file{mkinstalldirs}, @file{regcomp.c},
-@file{regex.c}, @file{regexec.c}, @file{regexex.c}, @file{regex.h},
-@file{regex_internal.c}, and @file{regex_internal.h}.
+The files are
+@file{dfa.c},
+@file{dfa.h},
+@file{getopt.c},
+@file{getopt.h},
+@file{getopt1.c},
+@file{getopt_int.h},
+@file{gettext.h},
+@file{regcomp.c},
+@file{regex.c},
+@file{regex.h},
+@file{regex_internal.c},
+@file{regex_internal.h},
+and
+@file{regexec.c}.
+
+@item
+A number of other files are provided by the GNU
+Autotools (Autoconf, Automake, and GNU @command{gettext}).
+You should not change them either, unless it is for a very
+good reason. The files are
+@file{ABOUT-NLS},
+@file{config.guess},
+@file{config.rpath},
+@file{config.sub},
+@file{depcomp},
+@file{INSTALL},
+@file{install-sh},
+@file{missing},
+@file{mkinstalldirs},
+@file{xalloc.h},
+and
+@file{ylwrap}.
 
 @item
 Be willing to continue to maintain the port.
@@ -34869,14 +37508,16 @@ In the code that you supply and maintain, feel free to use a
 coding style and brace layout that suits your taste.
 
 @node Derived Files
-@appendixsubsec Why Generated Files Are Kept In @command{git}
+@appendixsubsec Why Generated Files Are Kept In Git
 
+@c STARTOFRANGE gawkgit
+@cindex Git, use of for @command{gawk} source code
 @c From emails written March 22, 2012, to the gawk developers list.
 
-If you look at the @command{gawk} source in the @command{git}
+If you look at the @command{gawk} source in the Git
 repository, you will notice that it includes files that are automatically
 generated by GNU infrastructure tools, such as @file{Makefile.in} from
-@command{automake} and even @file{configure} from @command{autoconf}.
+Automake and even @file{configure} from Autoconf.
 
 This is different from many Free Software projects that do not store
 the derived files, because that keeps the repository less cluttered,
@@ -34902,11 +37543,10 @@ there a guarantee that we could find that @command{bison} version? Or that
 @emph{it} would build?)
 
 If the repository has all the generated files, then it's easy to just check
-them out and build. (Or @emph{easier}, depending upon how far back we go.
-@code{:-)})
+them out and build. (Or @emph{easier}, depending upon how far back we go.)
 
 And that brings us to the second (and stronger) reason why all the files
-really need to be in @command{git}.  It boils down to who do you cater
+really need to be in Git.  It boils down to who do you cater
 to---the @command{gawk} developer(s), or the user who just wants to check
 out a version and try it out?
 
@@ -34915,10 +37555,10 @@ wants it to be possible for any interested @command{awk} user in the
 world to just clone the repository, check out the branch of interest and
 build it. Without their having to have the correct version(s) of the
 autotools.@footnote{There is one GNU program that is (in our opinion)
-severely difficult to bootstrap from the @command{git} repository. For
-example, on the author's old (but still working) PowerPC macintosh with
+severely difficult to bootstrap from the Git repository. For
+example, on the author's old (but still working) PowerPC Macintosh with
 Mac OS X 10.5, it was necessary to bootstrap a ton of software, starting
-with @command{git} itself, in order to try to work with the latest code.
+with Git itself, in order to try to work with the latest code.
 It's not pleasant, and especially on older systems, it's a big waste
 of time.
 
@@ -34941,14 +37581,14 @@ This is extremely important for the @code{master} and
 
 Further, the @command{gawk} maintainer would argue that it's also
 important for the @command{gawk} developers. When he tried to check out
-the @code{xgawk} branch@footnote{A branch created by one of the other
+the @code{xgawk} branch@footnote{A branch (since removed) created by one of the other
 developers that did not include the generated files.} to build it, he
 couldn't. (No @file{ltmain.sh} file, and he had no idea how to create it,
 and that was not the only problem.)
 
 He felt @emph{extremely} frustrated.  With respect to that branch,
 the maintainer is no different than Jane User who wants to try to build
-@code{gawk-4.0-stable} or @code{master} from the repository.
+@code{gawk-4.1-stable} or @code{master} from the repository.
 
 Thus, the maintainer thinks that it's not just important, but critical,
 that for any given branch, the above incantation @emph{just works}.
@@ -34968,29 +37608,29 @@ It's the maintainer's job to merge them and he will deal with it.
 
 @item
 He is really good at @samp{git diff x y > /tmp/diff1 ; gvim /tmp/diff1} to
-remove the diffs that aren't of interest in order to review code. @code{:-)}
+remove the diffs that aren't of interest in order to review code.
 @end enumerate
 
 @item
 It would certainly help if everyone used the same versions of the GNU tools
 as he does, which in general are the latest released versions of
-@command{automake},
-@command{autoconf},
+Automake,
+Autoconf,
 @command{bison},
 and
-@command{gettext}.
+GNU @command{gettext}.
 
 @ignore
-If it would help if I sent out an "I just upgraded to version x.y
-of tool Z" kind of message to this list, I can do that.  Up until
+If it would help if I sent out an ``I just upgraded to version x.y
+of tool Z'' kind of message to this list, I can do that.  Up until
 now it hasn't been a real issue since I'm the only one who's been
 dorking with the configuration machinery.
 @end ignore
 
-@enumerate A
-@item
+@c @enumerate A
+@c @item
 Installing from source is quite easy. It's how the maintainer worked for years
-under Fedora.
+(and still works).
 He had @file{/usr/local/bin} at the front of his @env{PATH} and just did:
 
 @example
@@ -35001,10 +37641,11 @@ cd @var{package}-@var{x}.@var{y}.@var{z}
 make install    # as root
 @end example
 
-@item
+@c @item
+@ignore
 These days the maintainer uses Ubuntu 12.04 which is medium current, but
-he is already doing the above for @command{autoconf}, @command{automake}
-and @command{bison}.
+he is already doing the above for Automake, Autoconf, and @command{bison}.
+@end ignore
 
 @ignore
 (C. Rant: Recent Linux versions with GNOME 3 really suck. What
@@ -35012,7 +37653,7 @@ and @command{bison}.
     me to Ubuntu, but Ubuntu 11.04 and 11.10 are totally unusable from
     a UI perspective. Bleah.)
 @end ignore
-@end enumerate
+@c @end enumerate
 
 @ignore
 @item
@@ -35028,7 +37669,7 @@ the "real" changes and the second with "everything else needed for
 Most of the above was originally written by the maintainer to other
 @command{gawk} developers.  It raised the objection from one of
 the developers ``@dots{} that anybody pulling down the source from
-@command{git} is not an end user.''
+Git is not an end user.''
 
 However, this is not true. There are ``power @command{awk} users''
 who can build @command{gawk} (using the magic incantation shown previously)
@@ -35038,10 +37679,10 @@ kept buildable all the time.
 It was then suggested that there be a @command{cron} job to create
 nightly tarballs of ``the source.''  Here, the problem is that there
 are source trees, corresponding to the various branches! So,
-nightly tar balls aren't the answer, especially as the repository can go
+nightly tarballs aren't the answer, especially as the repository can go
 for weeks without significant change being introduced.
 
-Fortunately, the @command{git} server can meet this need. For any given
+Fortunately, the Git server can meet this need. For any given
 branch named @var{branchname}, use:
 
 @example
@@ -35050,7 +37691,7 @@ wget http://git.savannah.gnu.org/cgit/gawk.git/snapshot/gawk-@var{branchname}.ta
 
 @noindent
 to retrieve a snapshot of the given branch.
-
+@c ENDOFRANGE gawkgit
 
 @node Future Extensions
 @appendixsec Probable Future Extensions
@@ -35094,14 +37735,17 @@ Larry
 @quotation
 @i{AWK is a language similar to PERL, only considerably more elegant.}
 @author Arnold Robbins
+@end quotation
 
+@quotation
 @i{Hey!}
 @author Larry Wall
 @end quotation
 
-The @file{TODO} file in the @command{gawk} Git repository lists possible
-future enhancements.  Some of these relate to the source code, and others
-to possible new features.  Please see that file for the list.
+The @file{TODO} file in the @code{master} branch of the @command{gawk}
+Git repository lists possible future enhancements.  Some of these relate
+to the source code, and others to possible new features.  Please see
+that file for the list.
 @xref{Additions},
 if you are interested in tackling any of the projects listed there.
 
@@ -35115,7 +37759,7 @@ different limits.
 @multitable @columnfractions .40 .60
 @headitem Item @tab Limit
 @item Characters in a character class @tab 2^(number of bits per byte)
-@item Length of input record @tab @code{MAX_INT }
+@item Length of input record @tab @code{MAX_INT}
 @item Length of output record @tab Unlimited
 @item Length of source line @tab Unlimited
 @item Number of fields in a record @tab @code{MAX_LONG}
@@ -35124,9 +37768,9 @@ different limits.
 @item Number of input records total @tab @code{MAX_LONG}
 @item Number of pipe redirections @tab min(number of processes per user, number of open files)
 @item Numeric values @tab Double-precision floating point (if not using MPFR)
-@item Size of a field @tab @code{MAX_INT }
-@item Size of a literal string @tab @code{MAX_INT }
-@item Size of a printf string @tab @code{MAX_INT }
+@item Size of a field @tab @code{MAX_INT}
+@item Size of a literal string @tab @code{MAX_INT}
+@item Size of a printf string @tab @code{MAX_INT}
 @end multitable
 
 @node Extension Design
@@ -35161,7 +37805,7 @@ mechanism was bolted onto the side and was not really well thought out.
 
 The old extension mechanism had several problems:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 It depended heavily upon @command{gawk} internals.  Any time the
 @code{NODE} structure@footnote{A critical central data structure
@@ -35173,8 +37817,8 @@ documentation in this @value{DOCUMENT}, but it was quite minimal.
 @item
 Being able to call into @command{gawk} from an extension required linker
 facilities that are common on Unix-derived systems but that did
-not work on Windows systems; users wanting extensions on Windows
-had to statically link them into @command{gawk}, even though Windows supports
+not work on MS-Windows systems; users wanting extensions on MS-Windows
+had to statically link them into @command{gawk}, even though MS-Windows supports
 dynamic loading of shared objects.
 
 @item
@@ -35197,7 +37841,7 @@ project is provided in @ref{gawkextlib}.
 
 Some goals for the new API were:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The API should be independent of @command{gawk} internals.  Changes in
 @command{gawk} internals should not be visible to the writer of an
@@ -35212,7 +37856,7 @@ The API should enable extensions written in C or C++ to have roughly the
 same ``appearance'' to @command{awk}-level code as @command{awk}
 functions do. This means that extensions should have:
 
-@itemize @minus
+@itemize @value{MINUS}
 @item
 The ability to access function parameters.
 
@@ -35228,13 +37872,13 @@ in order to loop over all the element in an easy fashion for C code.
 
 @item
 The ability to create arrays (including @command{gawk}'s true
-multidimensional arrays).
+arrays of arrays).
 @end itemize
 @end itemize
 
 Some additional important goals were:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 The API should use only features in ISO C 90, so that extensions
 can be written using the widest range of C and C++ compilers. The header
@@ -35249,15 +37893,15 @@ The API mechanism should not require access to @command{gawk}'s
 symbols@footnote{The @dfn{symbols} are the variables and functions
 defined inside @command{gawk}.  Access to these symbols by code
 external to @command{gawk} loaded dynamically at runtime is
-problematic on Windows.} by the compile-time or dynamic linker,
-in order to enable creation of extensions that also work on Windows.
+problematic on MS-Windows.} by the compile-time or dynamic linker,
+in order to enable creation of extensions that also work on MS-Windows.
 @end itemize
 
 During development, it became clear that there were other features
 that should be available to extensions, which were also subsequently
 provided:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 Extensions should have the ability to hook into @command{gawk}'s
 I/O redirection mechanism.  In particular, the @command{xgawk}
@@ -35268,7 +37912,7 @@ two-way I/O.
 
 @item
 An extension should be able to provide a ``call back'' function
-to perform clean up actions when @command{gawk} exits.
+to perform cleanup actions when @command{gawk} exits.
 
 @item
 An extension should be able to provide a version string so that
@@ -35338,7 +37982,7 @@ to provide a minimal yet powerful set of features for creating extensions.
 
 The API can later be expanded, in two ways:
 
-@itemize @bullet
+@itemize @value{BULLET}
 @item
 @command{gawk} passes an ``extension id'' into the extension when it
 first loads the extension.  The extension then passes this id back
@@ -35361,12 +38005,12 @@ to any of the above.
 
 @ref{Dynamic Extensions}, describes the supported API and mechanisms
 for writing extensions for @command{gawk}.  This API was introduced
-in version 4.1.  However, for many years @command{gawk}
+in @value{PVERSION} 4.1.  However, for many years @command{gawk}
 provided an extension mechanism that required knowledge of @command{gawk}
 internals and that was not as well designed.
 
-In order to provide a transition period, @command{gawk} version
-4.1 continues to support the original extension mechanism.
+In order to provide a transition period, @command{gawk} @value{PVERSION} 4.1
+continues to support the original extension mechanism.
 This will be true for the life of exactly one major release.  This support
 will be withdrawn, and removed from the source code, at the next major
 release.
@@ -35392,6 +38036,42 @@ The @command{gawk} development team strongly recommends that you
 convert any old extensions that you may have to use the new API
 described in @ref{Dynamic Extensions}.
 
+@node Notes summary
+@appendixsec Summary
+
+@itemize @value{BULLET}
+@item
+@command{gawk}'s extensions can be disabled with either the
+@option{--traditional} option or with the @option{--posix} option.
+The @option{--parsedebug} option is available if @command{gawk} is
+compiled with @samp{-DDEBUG}.
+
+@item
+The source code for @command{gawk} is maintained in a publicly
+accessable Git repository. Anyone may check it out and view the source.
+
+@item
+Contributions to @command{gawk} are welcome. Following the steps
+outlined in this @value{CHAPTER} will make it easier to integrate
+your contributions into the code base.
+This applies both to new feature contributions and to ports to
+additional operating systems.
+
+@item
+@command{gawk} has some limits---generally those that are imposed by
+the machine architecture.
+
+@item
+The extension API design was intended to solve a number of problems
+with the previous extension mechanism, enable features needed by
+the @code{xgawk} project, and provide binary compatibility going forward.
+
+@item
+The previous extension mechanism is still supported in @value{PVERSION} 4.1
+of @command{gawk}, but it @emph{will} be removed in the next major release.
+
+@end itemize
+
 @c ENDOFRANGE impis
 @c ENDOFRANGE gawii
 
@@ -35419,8 +38099,15 @@ other introductory texts that you should refer to instead.)
 
 @cindex processing data
 At the most basic level, the job of a program is to process
-some input data and produce results. See @ref{figure-general-flow}.
+some input data and produce results.
+@ifnotdocbook
+See @ref{figure-general-flow}.
+@end ifnotdocbook
+@ifdocbook
+See @inlineraw{docbook, <xref linkend="figure-general-flow"/>}.
+@end ifdocbook
 
+@ifnotdocbook
 @float Figure,figure-general-flow
 @caption{General Program Flow}
 @ifinfo
@@ -35430,6 +38117,16 @@ some input data and produce results. See @ref{figure-general-flow}.
 @center @image{general-program, , , General program flow}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-general-flow" float="0">
+<title>General Program Flow</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="general-program.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 @cindex compiled programs
 @cindex interpreted programs
@@ -35445,9 +38142,15 @@ instructions in your program to process the data.
 
 @cindex programming, basic steps
 When you write a program, it usually consists
-of the following, very basic set of steps, as shown
-in @ref{figure-process-flow}:
+of the following, very basic set of steps,
+@ifnotdocbook
+as shown in @ref{figure-process-flow}:
+@end ifnotdocbook
+@ifdocbook
+as shown in @inlineraw{docbook, <xref linkend="figure-process-flow"/>}:
+@end ifdocbook
 
+@ifnotdocbook
 @float Figure,figure-process-flow
 @caption{Basic Program Steps}
 @ifinfo
@@ -35457,6 +38160,16 @@ in @ref{figure-process-flow}:
 @center @image{process-flow, , , Basic Program Stages}
 @end ifnotinfo
 @end float
+@end ifnotdocbook
+
+@docbook
+<figure id="figure-process-flow" float="0">
+<title>Basic Program Stages</title>
+<mediaobject>
+<imageobject role="web"><imagedata fileref="process-flow.png" format="PNG"/></imageobject>
+</mediaobject>
+</figure>
+@end docbook
 
 @table @asis
 @item Initialization
@@ -35552,7 +38265,7 @@ Individual variables, as well as numeric and string variables, are
 referred to as @dfn{scalar} values.
 Groups of values, such as arrays, are not scalars.
 
-@ref{General Arithmetic}, provided a basic introduction to numeric
+@ref{Computer Arithmetic}, provided a basic introduction to numeric
 types (integer and floating-point) and how they are used in a computer.
 Please review that information, including a number of caveats that
 were presented.
@@ -35568,14 +38281,14 @@ like this: @code{""}.
 
 Humans are used to working in decimal; i.e., base 10.  In base 10,
 numbers go from 0 to 9, and then ``roll over'' into the next
-column.  (Remember grade school? 42 is 4 times 10 plus 2.)
+column.  (Remember grade school? 42 = 4 x 10 + 2.)
 
 There are other number bases though.  Computers commonly use base 2
 or @dfn{binary}, base 8 or @dfn{octal}, and base 16 or @dfn{hexadecimal}.
 In binary, each column represents two times the value in the column to
 its right. Each column may contain either a 0 or a 1.
-Thus, binary 1010 represents 1 times 8, plus 0 times 4, plus 1 times 2,
-plus 0 times 1, or decimal 10.
+Thus, binary 1010 represents (1 x 8) + (0 x 4) + (1 x 2)
++ (0 x 1), or decimal 10.
 Octal and hexadecimal are discussed more in
 @ref{Nondecimal-numbers}.
 
@@ -35612,7 +38325,7 @@ Where it makes sense, POSIX @command{awk} is compatible with 1999 ISO C.
 @item Action
 A series of @command{awk} statements attached to a rule.  If the rule's
 pattern matches an input record, @command{awk} executes the
-rule's action.  Actions are always enclosed in curly braces.
+rule's action.  Actions are always enclosed in braces.
 (@xref{Action Overview}.)
 
 @cindex Spencer, Henry
@@ -35627,7 +38340,7 @@ better written in another language.
 You can get it from @uref{http://awk.info/?awk100/aaa}.
 
 @cindex Ada programming language
-@cindex Programming languages, Ada
+@cindex programming languages, Ada
 @item Ada
 A programming language originally defined by the U.S.@: Department of
 Defense for embedded programming. It was designed to enforce good
@@ -35695,9 +38408,6 @@ The GNU version of the standard shell
 @end ifinfo
 See also ``Bourne Shell.''
 
-@item BBS
-See ``Bulletin Board System.''
-
 @item Bit
 Short for ``Binary Digit.''
 All values in computer memory ultimately reduce to binary digits: values
@@ -35720,7 +38430,7 @@ Named after the English mathematician Boole. See also ``Logical Expression.''
 
 @item Bourne Shell
 The standard shell (@file{/bin/sh}) on Unix and Unix-like systems,
-originally written by Steven R.@: Bourne.
+originally written by Steven R.@: Bourne at Bell Laboratories.
 Many shells (Bash, @command{ksh}, @command{pdksh}, @command{zsh}) are
 generally upwardly compatible with the Bourne shell.
 
@@ -35770,12 +38480,9 @@ Changing some of them affects @command{awk}'s running environment.
 (@xref{Built-in Variables}.)
 
 @item Braces
-See ``Curly Braces.''
-
-@item Bulletin Board System
-A computer system allowing users to log in and read and/or leave messages
-for other users of the system, much like leaving paper notes on a bulletin
-board.
+The characters @samp{@{} and @samp{@}}.  Braces are used in
+@command{awk} for delimiting actions, compound statements, and function
+bodies.
 
 @item C
 The system programming language that most GNU software is written in.  The
@@ -35800,9 +38507,11 @@ or place. The most common character set in use today is ASCII (American
 Standard Code for Information Interchange).  Many European
 countries use an extension of ASCII known as ISO-8859-1 (ISO Latin-1).
 The @uref{http://www.unicode.org, Unicode character set} is
-becoming increasingly popular and standard, and is particularly
+increasingly popular and standard, and is particularly
 widely used on GNU/Linux systems.
 
+@cindex Kernighan, Brian
+@cindex Bentley, Jon
 @cindex @command{chem} utility
 @item CHEM
 A preprocessor for @command{pic} that reads descriptions of molecules
@@ -35811,10 +38520,11 @@ It was written in @command{awk}
 by Brian Kernighan and Jon Bentley, and is available from
 @uref{http://netlib.sandia.gov/netlib/typesetting/chem.gz}.
 
+@cindex McIlroy, Doug
 @cindex cookie
 @item Cookie
 A peculiar goodie, token, saying or remembrance
-produced by or presented to a program. (With thanks to Doug McIlroy.)
+produced by or presented to a program. (With thanks to Professor Doug McIlroy.)
 @ignore
 From: Doug McIlroy <doug@cs.dartmouth.edu>
 Date: Sat, 13 Oct 2012 19:55:25 -0400
@@ -35892,9 +38602,7 @@ statements, and in patterns to select which input records to process.
 (@xref{Typing and Comparison}.)
 
 @item Curly Braces
-The characters @samp{@{} and @samp{@}}.  Curly braces are used in
-@command{awk} for delimiting actions, compound statements, and function
-bodies.
+See ``Braces.''
 
 @cindex dark corner
 @item Dark Corner
@@ -35939,7 +38647,7 @@ ordinary expression.  It could be a string constant, such as
 (@xref{Computed Regexps}.)
 
 @item Environment
-A collection of strings, of the form @var{name@code{=}val}, that each
+A collection of strings, of the form @samp{@var{name}=@var{val}}, that each
 program has available to it. Users generally place values into the
 environment in order to provide information to various programs. Typical
 examples are the environment variables @env{HOME} and @env{PATH}.
@@ -35993,8 +38701,8 @@ this is just a number that can have a fractional part.
 See also ``Double Precision'' and ``Single Precision.''
 
 @item Format
-Format strings are used to control the appearance of output in the
-@code{strftime()} and @code{sprintf()} functions, and are used in the
+Format strings control the appearance of output in the
+@code{strftime()} and @code{sprintf()} functions, and in the
 @code{printf} statement as well.  Also, data conversions from numbers to strings
 are controlled by the format strings contained in the built-in variables
 @code{CONVFMT} and @code{OFMT}. (@xref{Control Letters}.)
@@ -36063,7 +38771,7 @@ Base 16 notation, where the digits are @code{0}--@code{9} and
 @code{A}--@code{F}, with @samp{A}
 representing 10, @samp{B} representing 11, and so on, up to @samp{F} for 15.
 Hexadecimal numbers are written in C using a leading @samp{0x},
-to indicate their base.  Thus, @code{0x12} is 18 (1 times 16 plus 2).
+to indicate their base.  Thus, @code{0x12} is 18 ((1 x 16) + 2).
 @xref{Nondecimal-numbers}.
 
 @item I/O
@@ -36108,7 +38816,7 @@ information about the name of the organization and its language-independent
 three-letter acronym.
 
 @cindex Java programming language
-@cindex Programming languages, Java
+@cindex programming languages, Java
 @item Java
 A modern programming language originally developed by Sun Microsystems
 (now Oracle) supporting Object-Oriented programming.  Although usually
@@ -36137,8 +38845,8 @@ meaning.  Keywords are reserved and may not be used as variable names.
 @code{function},
 @code{func},
 @code{if},
-@code{nextfile},
 @code{next},
+@code{nextfile},
 @code{switch},
 and
 @code{while}.
@@ -36199,13 +38907,9 @@ Ancient @command{awk} implementations used single precision floating-point.
 @item Octal
 Base-eight notation, where the digits are @code{0}--@code{7}.
 Octal numbers are written in C using a leading @samp{0},
-to indicate their base.  Thus, @code{013} is 11 (one times 8 plus 3).
+to indicate their base.  Thus, @code{013} is 11 ((1 x 8) + 3).
 @xref{Nondecimal-numbers}.
 
-@cindex P1003.1 POSIX standard
-@item P1003.1
-See ``POSIX.''
-
 @item Pattern
 Patterns tell @command{awk} which input records are interesting to which
 rules.
@@ -36246,8 +38950,8 @@ specify single lines. (@xref{Pattern Overview}.)
 
 @item Recursion
 When a function calls itself, either directly or indirectly.
-As long as this is not clear, refer to the entry for ``recursion.''
 If this is clear, stop, and proceed to the next entry.
+Otherwise, refer to the entry for ``recursion.''
 
 @item Redirection
 Redirection means performing input from something other than the standard input
@@ -36326,14 +39030,14 @@ expressions, and function calls have side effects.
 An internal representation of numbers that can have fractional parts.
 Single precision numbers keep track of fewer digits than do double precision
 numbers, but operations on them are sometimes less expensive in terms of CPU time.
-This is the type used by some very old versions of @command{awk} to store
+This is the type used by some ancient versions of @command{awk} to store
 numeric values.  It is the C type @code{float}.
 
 @item Space
 The character generated by hitting the space bar on the keyboard.
 
 @item Special File
-A file name interpreted internally by @command{gawk}, instead of being handed
+A @value{FN} interpreted internally by @command{gawk}, instead of being handed
 directly to the underlying operating system---for example, @file{/dev/stderr}.
 (@xref{Special Files}.)
 
@@ -36363,7 +39067,7 @@ into the local language.
 A value in the ``seconds since the epoch'' format used by Unix
 and POSIX systems.  Used for the @command{gawk} functions
 @code{mktime()}, @code{strftime()}, and @code{systime()}.
-See also ``Epoch'' and ``UTC.''
+See also ``Epoch,'' ``GMT,'' and ``UTC.''
 
 @cindex Linux
 @cindex GNU/Linux
@@ -36395,7 +39099,12 @@ record or a string.
 @c The GNU General Public License.
 @node Copying
 @unnumbered GNU General Public License
+@ifnotdocbook
 @center Version 3, 29 June 2007
+@end ifnotdocbook
+@docbook
+<subtitle>Version 3, 29 June 2007</subtitle>
+@end docbook
 
 @c This file is intended to be included within another document,
 @c hence no sectioning command or @node.  
@@ -37120,10 +39829,17 @@ first, please read @url{http://www.gnu.org/philosophy/why-not-lgpl.html}.
 @c The GNU Free Documentation License.
 @node GNU Free Documentation License
 @unnumbered GNU Free Documentation License
+@ifnotdocbook
+@center Version 1.3, 3 November 2008
+@end ifnotdocbook
+
+@docbook
+<subtitle>Version 1.3, 3 November 2008</subtitle>
+@end docbook
+
 @cindex FDL (Free Documentation License)
 @cindex Free Documentation License (FDL)
 @cindex GNU Free Documentation License
-@center Version 1.3, 3 November 2008
 
 @c This file is intended to be included within another document,
 @c hence no sectioning command or @node.
@@ -37624,12 +40340,12 @@ recommend releasing these examples in parallel under your choice of
 free software license, such as the GNU General Public License,
 to permit their use in free software.
 
-@c Local Variables:
-@c ispell-local-pdict: "ispell-dict"
-@c End:
+@end ifclear
 
+@ifnotdocbook
 @node Index
 @unnumbered Index
+@end ifnotdocbook
 @printindex cp
 
 @bye
@@ -37737,11 +40453,6 @@ ORA uses filename, thus the macro.
 
 Suggestions:
 ------------
-% Next edition:
-%	1. Standardize the error messages from the functions and programs
-%	   in the two sample code chapters.
-%	2. Nuke the BBS stuff and use something that won't be obsolete
-%	3. Turn the advanced notes into sidebars by using @cartouche
 
 Better sidebars can almost sort of be done with:
 
@@ -37774,3 +40485,5 @@ But to use it you have to say
 
 which sorta sucks.
 
+TODO:
+-----
diff --git a/doc/texinfo.tex b/doc/texinfo.tex
index 9cf29f2e..7506dffb 100644
--- a/doc/texinfo.tex
+++ b/doc/texinfo.tex
@@ -3,11 +3,11 @@
 % Load plain if necessary, i.e., if running under initex.
 \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi
 %
-\def\texinfoversion{2013-06-21.17}
+\def\texinfoversion{2014-03-18.17}
 %
 % Copyright 1985, 1986, 1988, 1990, 1991, 1992, 1993, 1994, 1995,
 % 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006,
-% 2007, 2008, 2009, 2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+% 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Free Software Foundation, Inc.
 %
 % This texinfo.tex file is free software: you can redistribute it and/or
 % modify it under the terms of the GNU General Public License as
@@ -281,9 +281,9 @@
   \toks6=\expandafter{\prevsectiondefs}%
   \toks8=\expandafter{\lastcolordefs}%
   \mark{%
-                   \the\toks0 \the\toks2
-      \noexpand\or \the\toks4 \the\toks6
-    \noexpand\else \the\toks8
+                   \the\toks0 \the\toks2  % 0: top marks (\last...)
+      \noexpand\or \the\toks4 \the\toks6  % 1: bottom marks (default, \prev...)
+    \noexpand\else \the\toks8             % 2: color marks
   }%
 }
 % \topmark doesn't work for the very first chapter (after the title
@@ -322,10 +322,13 @@
   %
   % Do this outside of the \shipout so @code etc. will be expanded in
   % the headline as they should be, not taken literally (outputting ''code).
+  \def\commmonheadfootline{\let\hsize=\pagewidth \texinfochars}
+  %
   \ifodd\pageno \getoddheadingmarks \else \getevenheadingmarks \fi
-  \setbox\headlinebox = \vbox{\let\hsize=\pagewidth \makeheadline}%
+  \global\setbox\headlinebox = \vbox{\commmonheadfootline \makeheadline}%
+  %
   \ifodd\pageno \getoddfootingmarks \else \getevenfootingmarks \fi
-  \setbox\footlinebox = \vbox{\let\hsize=\pagewidth \makefootline}%
+  \global\setbox\footlinebox = \vbox{\commmonheadfootline \makefootline}%
   %
   {%
     % Have to do this stuff outside the \shipout because we want it to
@@ -1135,10 +1138,12 @@ output) for that.)}
 
 \ifpdf
   %
-  % Color manipulation macros based on pdfcolor.tex,
+  % Color manipulation macros using ideas from pdfcolor.tex,
   % except using rgb instead of cmyk; the latter is said to render as a
   % very dark gray on-screen and a very dark halftone in print, instead
-  % of actual black.
+  % of actual black. The dark red here is dark enough to print on paper as
+  % nearly black, but still distinguishable for online viewing.  We use
+  % black by default, though.
   \def\rgbDarkRed{0.50 0.09 0.12}
   \def\rgbBlack{0 0 0}
   %
@@ -1248,10 +1253,9 @@ output) for that.)}
   % used to mark target names; must be expandable.
   \def\pdfmkpgn#1{#1}
   %
-  % by default, use a color that is dark enough to print on paper as
-  % nearly black, but still distinguishable for online viewing.
-  \def\urlcolor{\rgbDarkRed}
-  \def\linkcolor{\rgbDarkRed}
+  % by default, use black for everything.
+  \def\urlcolor{\rgbBlack}
+  \def\linkcolor{\rgbBlack}
   \def\endlink{\setcolor{\maincolor}\pdfendlink}
   %
   % Adding outlines to PDF; macros for calculating structure of outlines
@@ -2377,8 +2381,10 @@ end
   \ifx\next,%
   \else\ifx\next-%
   \else\ifx\next.%
+  \else\ifx\next\.%
+  \else\ifx\next\comma%
   \else\ptexslash
-  \fi\fi\fi
+  \fi\fi\fi\fi\fi
   \aftersmartic
 }
 
@@ -2519,7 +2525,9 @@ end
       \ifx\codedashprev\codedash 
       \else \discretionary{}{}{}\fi
     \fi
-    \global\let\codedashprev=\next
+    % we need the space after the = for the case when \next itself is a
+    % space token; it would get swallowed otherwise.  As in @code{- a}.
+    \global\let\codedashprev= \next
   }
 }
 \def\normaldash{-}
@@ -2567,37 +2575,21 @@ end
 \let\file=\code
 \let\option=\code
 
-% @uref (abbreviation for `urlref') takes an optional (comma-separated)
-% second argument specifying the text to display and an optional third
-% arg as text to display instead of (rather than in addition to) the url
-% itself.  First (mandatory) arg is the url.
-% (This \urefnobreak definition isn't used now, leaving it for a while
-% for comparison.)
-\def\urefnobreak#1{\dourefnobreak #1,,,\finish}
-\def\dourefnobreak#1,#2,#3,#4\finish{\begingroup
-  \unsepspaces
-  \pdfurl{#1}%
-  \setbox0 = \hbox{\ignorespaces #3}%
-  \ifdim\wd0 > 0pt
-    \unhbox0 % third arg given, show only that
-  \else
-    \setbox0 = \hbox{\ignorespaces #2}%
-    \ifdim\wd0 > 0pt
-      \ifpdf
-        \unhbox0             % PDF: 2nd arg given, show only it
-      \else
-        \unhbox0\ (\code{#1})% DVI: 2nd arg given, show both it and url
-      \fi
-    \else
-      \code{#1}% only url given, so show it
-    \fi
-  \fi
-  \endlink
-\endgroup}
+% @uref (abbreviation for `urlref') aka @url takes an optional
+% (comma-separated) second argument specifying the text to display and
+% an optional third arg as text to display instead of (rather than in
+% addition to) the url itself.  First (mandatory) arg is the url.
+
+% TeX-only option to allow changing PDF output to show only the second
+% arg (if given), and not the url (which is then just the link target).
+\newif\ifurefurlonlylink
 
-% This \urefbreak definition is the active one.
+% The main macro is \urefbreak, which allows breaking at expected
+% places within the url.  (There used to be another version, which
+% didn't support automatic breaking.)
 \def\urefbreak{\begingroup \urefcatcodes \dourefbreak}
 \let\uref=\urefbreak
+%
 \def\dourefbreak#1{\urefbreakfinish #1,,,\finish}
 \def\urefbreakfinish#1,#2,#3,#4\finish{% doesn't work in @example
   \unsepspaces
@@ -2606,12 +2598,19 @@ end
   \ifdim\wd0 > 0pt
     \unhbox0 % third arg given, show only that
   \else
-    \setbox0 = \hbox{\ignorespaces #2}%
+    \setbox0 = \hbox{\ignorespaces #2}% look for second arg
     \ifdim\wd0 > 0pt
       \ifpdf
-        \unhbox0             % PDF: 2nd arg given, show only it
+        \ifurefurlonlylink
+          % PDF plus option to not display url, show just arg
+          \unhbox0             
+        \else
+          % PDF, normally display both arg and url for consistency,
+          % visibility, if the pdf is eventually used to print, etc.
+          \unhbox0\ (\urefcode{#1})%
+        \fi
       \else
-        \unhbox0\ (\urefcode{#1})% DVI: 2nd arg given, show both it and url
+        \unhbox0\ (\urefcode{#1})% DVI, always show arg and url
       \fi
     \else
       \urefcode{#1}% only url given, so show it
@@ -2651,8 +2650,10 @@ end
 % we put a little stretch before and after the breakable chars, to help
 % line breaking of long url's.  The unequal skips make look better in
 % cmtt at least, especially for dots.
-\def\urefprestretch{\urefprebreak \hskip0pt plus.13em }
-\def\urefpoststretch{\urefpostbreak \hskip0pt plus.1em }
+\def\urefprestretchamount{.13em}
+\def\urefpoststretchamount{.1em}
+\def\urefprestretch{\urefprebreak \hskip0pt plus\urefprestretchamount\relax}
+\def\urefpoststretch{\urefpostbreak \hskip0pt plus\urefprestretchamount\relax}
 %
 \def\urefcodeamp{\urefprestretch \&\urefpoststretch}
 \def\urefcodedot{\urefprestretch .\urefpoststretch}
@@ -2887,6 +2888,15 @@ end
   \def\inlinefmtname{#1}%
   \ifx\inlinefmtname\outfmtnametex \ignorespaces #2\fi
 }
+% 
+% @inlinefmtifelse{FMTNAME,THEN-TEXT,ELSE-TEXT} expands THEN-TEXT if
+% FMTNAME is tex, else ELSE-TEXT.
+\long\def\inlinefmtifelse#1{\doinlinefmtifelse #1,,,\finish}
+\long\def\doinlinefmtifelse#1,#2,#3,#4,\finish{%
+  \def\inlinefmtname{#1}%
+  \ifx\inlinefmtname\outfmtnametex \ignorespaces #2\else \ignorespaces #3\fi
+}
+%
 % For raw, must switch into @tex before parsing the argument, to avoid
 % setting catcodes prematurely.  Doing it this way means that, for
 % example, @inlineraw{html, foo{bar} gets a parse error instead of being
@@ -2903,6 +2913,23 @@ end
   \endgroup % close group opened by \tex.
 }
 
+% @inlineifset{VAR, TEXT} expands TEXT if VAR is @set.
+%
+\long\def\inlineifset#1{\doinlineifset #1,\finish}
+\long\def\doinlineifset#1,#2,\finish{%
+  \def\inlinevarname{#1}%
+  \expandafter\ifx\csname SET\inlinevarname\endcsname\relax
+  \else\ignorespaces#2\fi
+}
+
+% @inlineifclear{VAR, TEXT} expands TEXT if VAR is not @set.
+%
+\long\def\inlineifclear#1{\doinlineifclear #1,\finish}
+\long\def\doinlineifclear#1,#2,\finish{%
+  \def\inlinevarname{#1}%
+  \expandafter\ifx\csname SET\inlinevarname\endcsname\relax \ignorespaces#2\fi
+}
+
 
 \message{glyphs,}
 % and logos.
@@ -3658,7 +3685,7 @@ end
   \parskip=\smallskipamount
   \ifdim\parskip=0pt \parskip=2pt \fi
   %
-  % Try typesetting the item mark that if the document erroneously says
+  % Try typesetting the item mark so that if the document erroneously says
   % something like @itemize @samp (intending @table), there's an error
   % right away at the @itemize.  It's not the best error message in the
   % world, but it's better than leaving it to the @item.  This means if
@@ -3908,19 +3935,23 @@ end
 }
 
 % multitable-only commands.
-%
-% @headitem starts a heading row, which we typeset in bold.
-% Assignments have to be global since we are inside the implicit group
-% of an alignment entry.  \everycr resets \everytab so we don't have to
+% 
+% @headitem starts a heading row, which we typeset in bold.  Assignments
+% have to be global since we are inside the implicit group of an
+% alignment entry.  \everycr below resets \everytab so we don't have to
 % undo it ourselves.
 \def\headitemfont{\b}% for people to use in the template row; not changeable
 \def\headitem{%
   \checkenv\multitable
   \crcr
+  \gdef\headitemcrhook{\nobreak}% attempt to avoid page break after headings
   \global\everytab={\bf}% can't use \headitemfont since the parsing differs
   \the\everytab % for the first item
 }%
 %
+% default for tables with no headings.
+\let\headitemcrhook=\relax
+%
 % A \tab used to include \hskip1sp.  But then the space in a template
 % line is not enough.  That is bad.  So let's go back to just `&' until
 % we again encounter the problem the 1sp was intended to solve.
@@ -3951,15 +3982,15 @@ end
   %
   \everycr = {%
     \noalign{%
-      \global\everytab={}%
+      \global\everytab={}% Reset from possible headitem.
       \global\colcount=0 % Reset the column counter.
-      % Check for saved footnotes, etc.
+      %
+      % Check for saved footnotes, etc.:
       \checkinserts
-      % Keeps underfull box messages off when table breaks over pages.
-      %\filbreak
-	% Maybe so, but it also creates really weird page breaks when the
-	% table breaks over pages. Wouldn't \vfil be better?  Wait until the
-	% problem manifests itself, so it can be fixed for real --karl.
+      %
+      % Perhaps a \nobreak, then reset:
+      \headitemcrhook
+      \global\let\headitemcrhook=\relax
     }%
   }%
   %
@@ -4198,7 +4229,7 @@ end
 \def\value{\begingroup\makevalueexpandable\valuexxx}
 \def\valuexxx#1{\expandablevalue{#1}\endgroup}
 {
-  \catcode`\- = \active \catcode`\_ = \active
+  \catcode`\-=\active \catcode`\_=\active
   %
   \gdef\makevalueexpandable{%
     \let\value = \expandablevalue
@@ -4218,7 +4249,12 @@ end
 % variable's value contains other Texinfo commands, it's almost certain
 % it will fail (although perhaps we could fix that with sufficient work
 % to do a one-level expansion on the result, instead of complete).
-%
+% 
+% Unfortunately, this has the consequence that when _ is in the *value*
+% of an @set, it does not print properly in the roman fonts (get the cmr
+% dot accent at position 126 instead).  No fix comes to mind, and it's
+% been this way since 2003 or earlier, so just ignore it.
+% 
 \def\expandablevalue#1{%
   \expandafter\ifx\csname SET#1\endcsname\relax
     {[No value for ``#1'']}%
@@ -4396,7 +4432,7 @@ end
   % complicated, when \tex is in effect and \{ is a \delimiter again.
   % We can't use \lbracecmd and \rbracecmd because texindex assumes
   % braces and backslashes are used only as delimiters.  Perhaps we
-  % should define @lbrace and @rbrace commands a la @comma.
+  % should use @lbracechar and @rbracechar?
   \def\{{{\tt\char123}}%
   \def\}{{\tt\char125}}%
   %
@@ -4417,8 +4453,7 @@ end
   % @end macro
   % ...
   % @funindex commtest
-  %
-  % The above is not enough to reproduce the bug, but it gives the flavor.
+  % This is not enough to reproduce the bug, but it gives the flavor.
   %
   % Sample whatsit resulting:
   % .@write3{\entry{xyz}{@folio }{@code {xyz@endinput }}}
@@ -4619,8 +4654,21 @@ end
   \definedummyword\verb
   \definedummyword\w
   \definedummyword\xref
+  %
+  % Consider:
+  %   @macro mkind{arg1,arg2}
+  %   @cindex \arg2\
+  %   @end macro
+  %   @mkind{foo, bar}
+  % The space after the comma will end up in the temporary definition
+  % that we make for arg2 (see \parsemargdef ff.).  We want all this to be
+  % expanded for the sake of the index, so we end up just seeing "bar".
+  \let\xeatspaces = \eatspaces
 }
 
+% For testing: output @{ and @} in index sort strings as \{ and \}.
+\newif\ifusebracesinindexes
+
 % \indexnofonts is used when outputting the strings to sort the index
 % by, and when constructing control sequence names.  It eliminates all
 % control sequences and just writes whatever the best ASCII sort string
@@ -4649,11 +4697,16 @@ end
   % Unfortunately, texindex is not prepared to handle braces in the
   % content at all.  So for index sorting, we map @{ and @} to strings
   % starting with |, since that ASCII character is between ASCII { and }.
-  \def\{{|a}%
-  \def\lbracechar{|a}%
+  \ifusebracesinindexes
+    \def\lbracechar{\lbracecmd}%
+    \def\rbracechar{\rbracecmd}%
+  \else
+    \def\lbracechar{|a}%
+    \def\rbracechar{|b}%
+  \fi
+  \let\{=\lbracechar
+  \let\}=\rbracechar
   %
-  \def\}{|b}%
-  \def\rbracechar{|b}%
   %
   % Non-English letters.
   \def\AA{AA}%
@@ -5905,7 +5958,7 @@ end
     %
     % Now the second mark, after the heading break.  No break points
     % between here and the heading.
-    \let\prevsectiondefs=\lastsectiondefs
+    \global\let\prevsectiondefs=\lastsectiondefs
     \domark
     %
     % Only insert the space after the number if we have a section number.
@@ -6272,8 +6325,8 @@ end
   \catcode `\|=\other
   \catcode `\<=\other
   \catcode `\>=\other
-  \catcode`\`=\other
-  \catcode`\'=\other
+  \catcode `\`=\other
+  \catcode `\'=\other
   \escapechar=`\\
   %
   % ' is active in math mode (mathcode"8000).  So reset it, and all our
@@ -6297,7 +6350,7 @@ end
   \let\/=\ptexslash
   \let\*=\ptexstar
   \let\t=\ptext
-  \expandafter \let\csname top\endcsname=\ptextop  % outer
+  \expandafter \let\csname top\endcsname=\ptextop  % we've made it outer
   \let\frenchspacing=\plainfrenchspacing
   %
   \def\endldots{\mathinner{\ldots\ldots\ldots\ldots}}%
@@ -6381,8 +6434,6 @@ end
 				% side, and for 6pt waste from
 				% each corner char, and rule thickness
   \normbskip=\baselineskip \normpskip=\parskip \normlskip=\lineskip
-  % Flag to tell @lisp, etc., not to narrow margin.
-  \let\nonarrowing = t%
   %
   % If this cartouche directly follows a sectioning command, we need the
   % \parskip glue (backspaced over by default) or the cartouche can
@@ -6549,9 +6600,13 @@ end
 
 
 % @raggedright does more-or-less normal line breaking but no right
-% justification.  From plain.tex.
+% justification.  From plain.tex.  Don't stretch around special
+% characters in urls in this environment, since the stretch at the right
+% should be enough.
 \envdef\raggedright{%
-  \rightskip0pt plus2em \spaceskip.3333em \xspaceskip.5em\relax
+  \rightskip0pt plus2.4em \spaceskip.3333em \xspaceskip.5em\relax
+  \def\urefprestretchamount{0pt}%
+  \def\urefpoststretchamount{0pt}%
 }
 \let\Eraggedright\par
 
@@ -7444,7 +7499,7 @@ end
 
 % Parse the optional {params} list.  Set up \paramno and \paramlist
 % so \defmacro knows what to do.  Define \macarg.BLAH for each BLAH
-% in the params list to some hook where the argument si to be expanded.  If
+% in the params list to some hook where the argument is to be expanded.  If
 % there are less than 10 arguments that hook is to be replaced by ##N where N
 % is the position in that list, that is to say the macro arguments are to be
 % defined `a la TeX in the macro body.  
@@ -8306,6 +8361,7 @@ end
 \gdef\footnote{%
   \let\indent=\ptexindent
   \let\noindent=\ptexnoindent
+  %
   \global\advance\footnoteno by \@ne
   \edef\thisfootno{$^{\the\footnoteno}$}%
   %
@@ -8329,6 +8385,11 @@ end
 %
 \gdef\dofootnote{%
   \insert\footins\bgroup
+  %
+  % Nested footnotes are not supported in TeX, that would take a lot
+  % more work.  (\startsavinginserts does not suffice.)
+  \let\footnote=\errfootnote
+  %
   % We want to typeset this text as a normal paragraph, even if the
   % footnote reference occurs in (for example) a display environment.
   % So reset some parameters.
@@ -8366,13 +8427,19 @@ end
 }
 }%end \catcode `\@=11
 
+\def\errfootnote{%
+  \errhelp=\EMsimple
+  \errmessage{Nested footnotes not supported in texinfo.tex,
+    even though they work in makeinfo; sorry}
+}
+
 % In case a @footnote appears in a vbox, save the footnote text and create
 % the real \insert just after the vbox finished.  Otherwise, the insertion
 % would be lost.
 % Similarly, if a @footnote appears inside an alignment, save the footnote
 % text to a box and make the \insert when a row of the table is finished.
 % And the same can be done for other insert classes.  --kasal, 16nov03.
-
+%
 % Replace the \insert primitive by a cheating macro.
 % Deeper inside, just make sure that the saved insertions are not spilled
 % out prematurely.
@@ -9940,11 +10007,9 @@ directory should work if nowhere else does.}
 \catcode`\"=\active
 \def\activedoublequote{{\tt\char34}}
 \let"=\activedoublequote
-\catcode`\~=\active
-\def~{{\tt\char126}}
+\catcode`\~=\active \def\activetilde{{\tt\char126}} \let~ = \activetilde
 \chardef\hat=`\^
-\catcode`\^=\active
-\def^{{\tt \hat}}
+\catcode`\^=\active \def\activehat{{\tt \hat}} \let^ = \activehat
 
 \catcode`\_=\active
 \def_{\ifusingtt\normalunderscore\_}
@@ -9954,16 +10019,26 @@ directory should work if nowhere else does.}
 
 \catcode`\|=\active
 \def|{{\tt\char124}}
+
 \chardef \less=`\<
-\catcode`\<=\active
-\def<{{\tt \less}}
+\catcode`\<=\active \def\activeless{{\tt \less}}\let< = \activeless
 \chardef \gtr=`\>
-\catcode`\>=\active
-\def>{{\tt \gtr}}
-\catcode`\+=\active
-\def+{{\tt \char 43}}
-\catcode`\$=\active
-\def${\ifusingit{{\sl\$}}\normaldollar}%$ font-lock fix
+\catcode`\>=\active \def\activegtr{{\tt \gtr}}\let> = \activegtr
+\catcode`\+=\active \def+{{\tt \char 43}}
+\catcode`\$=\active \def${\ifusingit{{\sl\$}}\normaldollar}%$ font-lock fix
+
+% used for headline/footline in the output routine, in case the page
+% breaks in the middle of an @tex block.
+\def\texinfochars{%
+  \let< = \activeless
+  \let> = \activegtr
+  \let~ = \activetilde 
+  \let^ = \activehat
+  \markupsetuplqdefault \markupsetuprqdefault 
+  \let\b = \strong
+  \let\i = \smartitalic
+  % in principle, all other definitions in \tex have to be undone too.
+}
 
 % If a .fmt file is being used, characters that might appear in a file
 % name cannot be active until we have parsed the command line.
diff --git a/ext.c b/ext.c
index 9e17761a..09e10164 100644
--- a/ext.c
+++ b/ext.c
@@ -7,7 +7,7 @@
  */
 
 /*
- * Copyright (C) 1995 - 2001, 2003-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1995 - 2001, 2003-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -174,9 +174,9 @@ load_old_ext(SRCFILE *s, const char *init_func, const char *fini_func, NODE *obj
 		fatal(_("`extension' is a gawk extension"));
 
 	if (lib_name == NULL)
-		fatal(_("load_ext: received NULL lib_name"));
+		fatal(_("extension: received NULL lib_name"));
 
-	if ((dl = dlopen(s->fullpath, flags)) == NULL)
+	if ((dl = dlopen(lib_name, flags)) == NULL)
 		fatal(_("extension: cannot open library `%s' (%s)"), lib_name,
 		      dlerror());
 
@@ -221,13 +221,11 @@ make_builtin(const awk_ext_func_t *funcinfo)
 		fatal(_("make_builtin: missing function name"));
 
 	if (! is_letter(*sp))
-		return false;
-
-	sp++;
+		return awk_false;
 
-	while ((c = *sp++) != '\0') {
+	for (sp++; (c = *sp++) != '\0';) {
 		if (! is_identifier_char(c))
-			return false;
+			return awk_false;
 	}
 
 	f = lookup(name);
@@ -240,7 +238,7 @@ make_builtin(const awk_ext_func_t *funcinfo)
 			/* multiple extension() calls etc. */ 
 			if (do_lint)
 				lintwarn(_("make_builtin: function `%s' already defined"), name);
-			return false;
+			return awk_false;
 		} else
 			/* variable name etc. */ 
 			fatal(_("make_builtin: function name `%s' previously defined"), name);
@@ -260,7 +258,7 @@ make_builtin(const awk_ext_func_t *funcinfo)
        	symbol = install_symbol(estrdup(name, strlen(name)), Node_ext_func);
 	symbol->code_ptr = b;
 	track_ext_func(name);
-	return true;
+	return awk_true;
 }
 
 /* make_old_builtin --- register name to be called as func with a builtin body */
@@ -277,9 +275,11 @@ make_old_builtin(const char *name, NODE *(*func)(int), int count)	/* temporary *
 	if (sp == NULL || *sp == '\0')
 		fatal(_("extension: missing function name"));
 
-	while ((c = *sp++) != '\0') {
-		if ((sp == & name[1] && c != '_' && ! isalpha((unsigned char) c))
-				|| (sp > &name[1] && ! is_identifier_char((unsigned char) c)))
+	if (! is_letter(*sp))
+		fatal(_("extension: illegal character `%c' in function name `%s'"), *sp, name);
+
+	for (sp++; (c = *sp++) != '\0';) {
+		if (! is_identifier_char(c))
 			fatal(_("extension: illegal character `%c' in function name `%s'"), c, name);
 	}
 
@@ -312,6 +312,7 @@ make_old_builtin(const char *name, NODE *(*func)(int), int count)	/* temporary *
 
        	symbol = install_symbol(estrdup(name, strlen(name)), Node_old_ext_func);
 	symbol->code_ptr = b;
+	track_ext_func(name);
 }
 
 
diff --git a/extension/ChangeLog b/extension/ChangeLog
index 328d58ba..f3a1c7a8 100644
--- a/extension/ChangeLog
+++ b/extension/ChangeLog
@@ -1,3 +1,78 @@
+2014-04-11         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (install-data-hook): Use $(DESTDIR) when removing
+	the .la files. Thanks to Lars Wendler <polynomial-c@gentoo.org>
+	for the report and fix.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac: Bump version before release.
+
+2014-04-04         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* time.c: Include <time.h> unconditionally to get declaration
+	of nanosleep on Linux. Avoids a warning. Thanks to Michal
+	Jaegermann.
+
+2014-03-31         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac: Remove -Wextra to avoid killing compilations
+	on older versions of gcc. Thanks to Antonio Diaz Diaz for
+	the report.
+
+2014-03-28         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* configure.ac: Add AC_HEADER_TIME and AC_HEADER_DIRENT, and
+	rearrange order of macros some. May help on older systems.
+
+2014-03-27         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* readfile.c: Add an input parser that works off of
+	PROCINFO["readfile"].
+	* readfile.3am: Document same.
+
+2014-03-23         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawkfts.c (MAXPATHLEN): Add a default definition. Thanks to
+	Antonio Diaz Dian and Nelson H.F. Beebe.
+	* readdir.c (PATH_MAX): Add a default definition. Thanks to
+	Nelson H.F. Beebe.
+
+2014-03-08         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* filefuncs.c (read_symlink, do_fts): Replace free with gawk_free.
+	* inplace.c (at_exit, do_inplace_end): Ditto.
+	* readdir.c (dir_close): Ditto.
+	* readfile.c (do_readfile): Ditto.
+	* revtwoway.c (close_two_proc_data): Ditto.
+	* rwarray.c (read_elem): Replace realloc with gawk_realloc.
+	(read_value): Replace malloc and free with gawk_malloc and gawk_free.
+	* testext.c (try_modify_environ): Replace free with gawk_free.
+
+2014-02-12         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* time.c: Better hack for nanosleep bug based on feedback from HP.
+
+2013-12-29         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* filefuncs.c: Fix compile on VMS.
+	* time.c: Fix compile on VMS.
+
+2013-12-29         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawkfts.c: Wrap include of <sys/param.h> in HAVE_SYS_PARAM_H,
+	as I should have done to start with.  For VMS.
+
+2013-12-29         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawkdirfd.h: Adjust include for VMS.
+	* filefuncs.c: Make it compile on VMS.
+	* fnmatch.c: Make it compile on VMS.
+
 2013-12-21         Mike Frysinger        <vapier@gentoo.org>
 
 	* configure.ac: Remove MirBSD and OS/390 hack to create
diff --git a/extension/Makefile.am b/extension/Makefile.am
index 9c49bb81..11826e2b 100644
--- a/extension/Makefile.am
+++ b/extension/Makefile.am
@@ -100,7 +100,7 @@ testext_la_LIBADD     = $(MY_LIBS)
 
 install-data-hook:
 	for i in $(pkgextension_LTLIBRARIES) ; do \
-		$(RM) $(pkgextensiondir)/$$i ; \
+		$(RM) $(DESTDIR)$(pkgextensiondir)/$$i ; \
 	done
 
 # Keep the uninstall check working:
diff --git a/extension/Makefile.in b/extension/Makefile.in
index 040cdb8f..d81b1696 100644
--- a/extension/Makefile.in
+++ b/extension/Makefile.in
@@ -1231,7 +1231,7 @@ uninstall-man: uninstall-man3
 
 install-data-hook:
 	for i in $(pkgextension_LTLIBRARIES) ; do \
-		$(RM) $(pkgextensiondir)/$$i ; \
+		$(RM) $(DESTDIR)$(pkgextensiondir)/$$i ; \
 	done
 
 # Keep the uninstall check working:
diff --git a/extension/build-aux/ChangeLog b/extension/build-aux/ChangeLog
index bf00e289..697db607 100644
--- a/extension/build-aux/ChangeLog
+++ b/extension/build-aux/ChangeLog
@@ -1,3 +1,16 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-01-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* config.guess, config.rpath, config.sub, depcomp,
+	install-sh: Updated.
+
+2013-12-24         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* config.guess: Updated.
+
 2013-12-21         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* ltmain.sh: Updated to libtool 2.4.2.418.
diff --git a/extension/build-aux/config.guess b/extension/build-aux/config.guess
index aa04f04b..4438cd70 100755
--- a/extension/build-aux/config.guess
+++ b/extension/build-aux/config.guess
@@ -1,14 +1,12 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
-#   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-#   2011, 2012 Free Software Foundation, Inc.
+#   Copyright 1992-2014 Free Software Foundation, Inc.
 
-timestamp='2012-06-17'
+timestamp='2014-01-01'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
+# the Free Software Foundation; either version 3 of the License, or
 # (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful, but
@@ -22,19 +20,17 @@ timestamp='2012-06-17'
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-
-# Originally written by Per Bothner.  Please send patches (context
-# diff format) to <config-patches@gnu.org> and include a ChangeLog
-# entry.
+# the same distribution terms that you use for the rest of that
+# program.  This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
 #
-# This script attempts to guess a canonical system name similar to
-# config.sub.  If it succeeds, it prints the system name on stdout, and
-# exits with 0.  Otherwise, it exits with 1.
+# Originally written by Per Bothner.
 #
 # You can get the latest version of this script from:
 # http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
+#
+# Please send patches with a ChangeLog entry to config-patches@gnu.org.
+
 
 me=`echo "$0" | sed -e 's,.*/,,'`
 
@@ -54,9 +50,7 @@ version="\
 GNU config.guess ($timestamp)
 
 Originally written by Per Bothner.
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012
-Free Software Foundation, Inc.
+Copyright 1992-2014 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -138,6 +132,27 @@ UNAME_RELEASE=`(uname -r) 2>/dev/null` || UNAME_RELEASE=unknown
 UNAME_SYSTEM=`(uname -s) 2>/dev/null`  || UNAME_SYSTEM=unknown
 UNAME_VERSION=`(uname -v) 2>/dev/null` || UNAME_VERSION=unknown
 
+case "${UNAME_SYSTEM}" in
+Linux|GNU|GNU/*)
+	# If the system lacks a compiler, then just pick glibc.
+	# We could probably try harder.
+	LIBC=gnu
+
+	eval $set_cc_for_build
+	cat <<-EOF > $dummy.c
+	#include <features.h>
+	#if defined(__UCLIBC__)
+	LIBC=uclibc
+	#elif defined(__dietlibc__)
+	LIBC=dietlibc
+	#else
+	LIBC=gnu
+	#endif
+	EOF
+	eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'`
+	;;
+esac
+
 # Note: order is significant - the case branches are not exclusive.
 
 case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
@@ -306,7 +321,7 @@ case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
     arm:RISC*:1.[012]*:*|arm:riscix:1.[012]*:*)
 	echo arm-acorn-riscix${UNAME_RELEASE}
 	exit ;;
-    arm:riscos:*:*|arm:RISCOS:*:*)
+    arm*:riscos:*:*|arm*:RISCOS:*:*)
 	echo arm-unknown-riscos
 	exit ;;
     SR2?01:HI-UX/MPP:*:* | SR8000:HI-UX/MPP:*:*)
@@ -805,6 +820,9 @@ EOF
     i*:CYGWIN*:*)
 	echo ${UNAME_MACHINE}-pc-cygwin
 	exit ;;
+    *:MINGW64*:*)
+	echo ${UNAME_MACHINE}-pc-mingw64
+	exit ;;
     *:MINGW*:*)
 	echo ${UNAME_MACHINE}-pc-mingw32
 	exit ;;
@@ -856,21 +874,21 @@ EOF
 	exit ;;
     *:GNU:*:*)
 	# the GNU system
-	echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-gnu`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'`
+	echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-${LIBC}`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'`
 	exit ;;
     *:GNU/*:*:*)
 	# other systems with GNU libc and userland
-	echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-gnu
+	echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-${LIBC}
 	exit ;;
     i*86:Minix:*:*)
 	echo ${UNAME_MACHINE}-pc-minix
 	exit ;;
     aarch64:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     aarch64_be:Linux:*:*)
 	UNAME_MACHINE=aarch64_be
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     alpha:Linux:*:*)
 	case `sed -n '/^cpu model/s/^.*: \(.*\)/\1/p' < /proc/cpuinfo` in
@@ -883,59 +901,54 @@ EOF
 	  EV68*) UNAME_MACHINE=alphaev68 ;;
 	esac
 	objdump --private-headers /bin/sh | grep -q ld.so.1
-	if test "$?" = 0 ; then LIBC="libc1" ; else LIBC="" ; fi
-	echo ${UNAME_MACHINE}-unknown-linux-gnu${LIBC}
+	if test "$?" = 0 ; then LIBC="gnulibc1" ; fi
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
+	exit ;;
+    arc:Linux:*:* | arceb:Linux:*:*)
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     arm*:Linux:*:*)
 	eval $set_cc_for_build
 	if echo __ARM_EABI__ | $CC_FOR_BUILD -E - 2>/dev/null \
 	    | grep -q __ARM_EABI__
 	then
-	    echo ${UNAME_MACHINE}-unknown-linux-gnu
+	    echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	else
 	    if echo __ARM_PCS_VFP | $CC_FOR_BUILD -E - 2>/dev/null \
 		| grep -q __ARM_PCS_VFP
 	    then
-		echo ${UNAME_MACHINE}-unknown-linux-gnueabi
+		echo ${UNAME_MACHINE}-unknown-linux-${LIBC}eabi
 	    else
-		echo ${UNAME_MACHINE}-unknown-linux-gnueabihf
+		echo ${UNAME_MACHINE}-unknown-linux-${LIBC}eabihf
 	    fi
 	fi
 	exit ;;
     avr32*:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     cris:Linux:*:*)
-	echo ${UNAME_MACHINE}-axis-linux-gnu
+	echo ${UNAME_MACHINE}-axis-linux-${LIBC}
 	exit ;;
     crisv32:Linux:*:*)
-	echo ${UNAME_MACHINE}-axis-linux-gnu
+	echo ${UNAME_MACHINE}-axis-linux-${LIBC}
 	exit ;;
     frv:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     hexagon:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     i*86:Linux:*:*)
-	LIBC=gnu
-	eval $set_cc_for_build
-	sed 's/^	//' << EOF >$dummy.c
-	#ifdef __dietlibc__
-	LIBC=dietlibc
-	#endif
-EOF
-	eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'`
-	echo "${UNAME_MACHINE}-pc-linux-${LIBC}"
+	echo ${UNAME_MACHINE}-pc-linux-${LIBC}
 	exit ;;
     ia64:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     m32r*:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     m68*:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     mips:Linux:*:* | mips64:Linux:*:*)
 	eval $set_cc_for_build
@@ -954,54 +967,63 @@ EOF
 	#endif
 EOF
 	eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^CPU'`
-	test x"${CPU}" != x && { echo "${CPU}-unknown-linux-gnu"; exit; }
+	test x"${CPU}" != x && { echo "${CPU}-unknown-linux-${LIBC}"; exit; }
 	;;
+    or1k:Linux:*:*)
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
+	exit ;;
     or32:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     padre:Linux:*:*)
-	echo sparc-unknown-linux-gnu
+	echo sparc-unknown-linux-${LIBC}
 	exit ;;
     parisc64:Linux:*:* | hppa64:Linux:*:*)
-	echo hppa64-unknown-linux-gnu
+	echo hppa64-unknown-linux-${LIBC}
 	exit ;;
     parisc:Linux:*:* | hppa:Linux:*:*)
 	# Look for CPU level
 	case `grep '^cpu[^a-z]*:' /proc/cpuinfo 2>/dev/null | cut -d' ' -f2` in
-	  PA7*) echo hppa1.1-unknown-linux-gnu ;;
-	  PA8*) echo hppa2.0-unknown-linux-gnu ;;
-	  *)    echo hppa-unknown-linux-gnu ;;
+	  PA7*) echo hppa1.1-unknown-linux-${LIBC} ;;
+	  PA8*) echo hppa2.0-unknown-linux-${LIBC} ;;
+	  *)    echo hppa-unknown-linux-${LIBC} ;;
 	esac
 	exit ;;
     ppc64:Linux:*:*)
-	echo powerpc64-unknown-linux-gnu
+	echo powerpc64-unknown-linux-${LIBC}
 	exit ;;
     ppc:Linux:*:*)
-	echo powerpc-unknown-linux-gnu
+	echo powerpc-unknown-linux-${LIBC}
+	exit ;;
+    ppc64le:Linux:*:*)
+	echo powerpc64le-unknown-linux-${LIBC}
+	exit ;;
+    ppcle:Linux:*:*)
+	echo powerpcle-unknown-linux-${LIBC}
 	exit ;;
     s390:Linux:*:* | s390x:Linux:*:*)
-	echo ${UNAME_MACHINE}-ibm-linux
+	echo ${UNAME_MACHINE}-ibm-linux-${LIBC}
 	exit ;;
     sh64*:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     sh*:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     sparc:Linux:*:* | sparc64:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     tile*:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     vax:Linux:*:*)
-	echo ${UNAME_MACHINE}-dec-linux-gnu
+	echo ${UNAME_MACHINE}-dec-linux-${LIBC}
 	exit ;;
     x86_64:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     xtensa*:Linux:*:*)
-	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
 	exit ;;
     i*86:DYNIX/ptx:4*:*)
 	# ptx 4.0 does uname -s correctly, with DYNIX/ptx in there.
@@ -1205,6 +1227,9 @@ EOF
     BePC:Haiku:*:*)	# Haiku running on Intel PC compatible.
 	echo i586-pc-haiku
 	exit ;;
+    x86_64:Haiku:*:*)
+	echo x86_64-unknown-haiku
+	exit ;;
     SX-4:SUPER-UX:*:*)
 	echo sx4-nec-superux${UNAME_RELEASE}
 	exit ;;
@@ -1231,19 +1256,31 @@ EOF
 	exit ;;
     *:Darwin:*:*)
 	UNAME_PROCESSOR=`uname -p` || UNAME_PROCESSOR=unknown
-	case $UNAME_PROCESSOR in
-	    i386)
-		eval $set_cc_for_build
-		if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then
-		  if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \
-		      (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \
-		      grep IS_64BIT_ARCH >/dev/null
-		  then
-		      UNAME_PROCESSOR="x86_64"
-		  fi
-		fi ;;
-	    unknown) UNAME_PROCESSOR=powerpc ;;
-	esac
+	eval $set_cc_for_build
+	if test "$UNAME_PROCESSOR" = unknown ; then
+	    UNAME_PROCESSOR=powerpc
+	fi
+	if test `echo "$UNAME_RELEASE" | sed -e 's/\..*//'` -le 10 ; then
+	    if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then
+		if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \
+		    (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \
+		    grep IS_64BIT_ARCH >/dev/null
+		then
+		    case $UNAME_PROCESSOR in
+			i386) UNAME_PROCESSOR=x86_64 ;;
+			powerpc) UNAME_PROCESSOR=powerpc64 ;;
+		    esac
+		fi
+	    fi
+	elif test "$UNAME_PROCESSOR" = i386 ; then
+	    # Avoid executing cc on OS X 10.9, as it ships with a stub
+	    # that puts up a graphical alert prompting to install
+	    # developer tools.  Any system running Mac OS X 10.7 or
+	    # later (Darwin 11 and later) is required to have a 64-bit
+	    # processor. This is not true of the ARM version of Darwin
+	    # that Apple uses in portable devices.
+	    UNAME_PROCESSOR=x86_64
+	fi
 	echo ${UNAME_PROCESSOR}-apple-darwin${UNAME_RELEASE}
 	exit ;;
     *:procnto*:*:* | *:QNX:[0123456789]*:*)
@@ -1334,9 +1371,6 @@ EOF
 	exit ;;
 esac
 
-#echo '(No uname command or uname output not recognized.)' 1>&2
-#echo "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" 1>&2
-
 eval $set_cc_for_build
 cat >$dummy.c <<EOF
 #ifdef _SEQUENT_
diff --git a/extension/build-aux/config.rpath b/extension/build-aux/config.rpath
index 17298f23..ab6fd995 100755
--- a/extension/build-aux/config.rpath
+++ b/extension/build-aux/config.rpath
@@ -2,7 +2,7 @@
 # Output a system dependent set of variables, describing how to set the
 # run time search path of shared libraries in an executable.
 #
-#   Copyright 1996-2010 Free Software Foundation, Inc.
+#   Copyright 1996-2014 Free Software Foundation, Inc.
 #   Taken from GNU libtool, 2001
 #   Originally by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
 #
@@ -25,7 +25,7 @@
 #   known workaround is to choose shorter directory names for the build
 #   directory and/or the installation directory.
 
-# All known linkers require a `.a' archive for static linking (except MSVC,
+# All known linkers require a '.a' archive for static linking (except MSVC,
 # which needs '.lib').
 libext=a
 shrext=.so
@@ -57,13 +57,6 @@ else
     aix*)
       wl='-Wl,'
       ;;
-    darwin*)
-      case $cc_basename in
-        xlc*)
-          wl='-Wl,'
-          ;;
-      esac
-      ;;
     mingw* | cygwin* | pw32* | os2* | cegcc*)
       ;;
     hpux9* | hpux10* | hpux11*)
@@ -72,9 +65,7 @@ else
     irix5* | irix6* | nonstopux*)
       wl='-Wl,'
       ;;
-    newsos6)
-      ;;
-    linux* | k*bsd*-gnu)
+    linux* | k*bsd*-gnu | kopensolaris*-gnu)
       case $cc_basename in
         ecc*)
           wl='-Wl,'
@@ -85,17 +76,26 @@ else
         lf95*)
           wl='-Wl,'
           ;;
-        pgcc | pgf77 | pgf90)
+        nagfor*)
+          wl='-Wl,-Wl,,'
+          ;;
+        pgcc* | pgf77* | pgf90* | pgf95* | pgfortran*)
           wl='-Wl,'
           ;;
         ccc*)
           wl='-Wl,'
           ;;
+        xl* | bgxl* | bgf* | mpixl*)
+          wl='-Wl,'
+          ;;
         como)
           wl='-lopt='
           ;;
         *)
           case `$CC -V 2>&1 | sed 5q` in
+            *Sun\ F* | *Sun*Fortran*)
+              wl=
+              ;;
             *Sun\ C*)
               wl='-Wl,'
               ;;
@@ -103,13 +103,24 @@ else
           ;;
       esac
       ;;
+    newsos6)
+      ;;
+    *nto* | *qnx*)
+      ;;
     osf3* | osf4* | osf5*)
       wl='-Wl,'
       ;;
     rdos*)
       ;;
     solaris*)
-      wl='-Wl,'
+      case $cc_basename in
+        f77* | f90* | f95* | sunf77* | sunf90* | sunf95*)
+          wl='-Qoption ld '
+          ;;
+        *)
+          wl='-Wl,'
+          ;;
+      esac
       ;;
     sunos4*)
       wl='-Qoption ld '
@@ -171,15 +182,14 @@ if test "$with_gnu_ld" = yes; then
       fi
       ;;
     amigaos*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_minus_L=yes
-      # Samuel A. Falvo II <kc5tja@dolphin.openprojects.net> reports
-      # that the semantics of dynamic libraries on AmigaOS, at least up
-      # to version 4, is to share data among multiple programs linked
-      # with the same dynamic library.  Since this doesn't match the
-      # behavior of shared libraries on other platforms, we cannot use
-      # them.
-      ld_shlibs=no
+      case "$host_cpu" in
+        powerpc)
+          ;;
+        m68k)
+          hardcode_libdir_flag_spec='-L$libdir'
+          hardcode_minus_L=yes
+          ;;
+      esac
       ;;
     beos*)
       if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
@@ -198,11 +208,13 @@ if test "$with_gnu_ld" = yes; then
         ld_shlibs=no
       fi
       ;;
+    haiku*)
+      ;;
     interix[3-9]*)
       hardcode_direct=no
       hardcode_libdir_flag_spec='${wl}-rpath,$libdir'
       ;;
-    gnu* | linux* | k*bsd*-gnu)
+    gnu* | linux* | tpf* | k*bsd*-gnu | kopensolaris*-gnu)
       if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
         :
       else
@@ -325,10 +337,14 @@ else
       fi
       ;;
     amigaos*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_minus_L=yes
-      # see comment about different semantics on the GNU ld section
-      ld_shlibs=no
+      case "$host_cpu" in
+        powerpc)
+          ;;
+        m68k)
+          hardcode_libdir_flag_spec='-L$libdir'
+          hardcode_minus_L=yes
+          ;;
+      esac
       ;;
     bsdi[45]*)
       ;;
@@ -342,24 +358,15 @@ else
       ;;
     darwin* | rhapsody*)
       hardcode_direct=no
-      if test "$GCC" = yes ; then
+      if { case $cc_basename in ifort*) true;; *) test "$GCC" = yes;; esac; }; then
         :
       else
-        case $cc_basename in
-          xlc*)
-            ;;
-          *)
-            ld_shlibs=no
-            ;;
-        esac
+        ld_shlibs=no
       fi
       ;;
     dgux*)
       hardcode_libdir_flag_spec='-L$libdir'
       ;;
-    freebsd1*)
-      ld_shlibs=no
-      ;;
     freebsd2.2*)
       hardcode_libdir_flag_spec='-R$libdir'
       hardcode_direct=yes
@@ -420,6 +427,8 @@ else
       hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir'
       hardcode_libdir_separator=:
       ;;
+    *nto* | *qnx*)
+      ;;
     openbsd*)
       if test -f /usr/libexec/ld.so; then
         hardcode_direct=yes
@@ -515,7 +524,12 @@ case "$host_os" in
     library_names_spec='$libname$shrext'
     ;;
   amigaos*)
-    library_names_spec='$libname.a'
+    case "$host_cpu" in
+      powerpc*)
+        library_names_spec='$libname$shrext' ;;
+      m68k)
+        library_names_spec='$libname.a' ;;
+    esac
     ;;
   beos*)
     library_names_spec='$libname$shrext'
@@ -534,8 +548,6 @@ case "$host_os" in
   dgux*)
     library_names_spec='$libname$shrext'
     ;;
-  freebsd1*)
-    ;;
   freebsd* | dragonfly*)
     case "$host_os" in
       freebsd[123]*)
@@ -547,6 +559,9 @@ case "$host_os" in
   gnu*)
     library_names_spec='$libname$shrext'
     ;;
+  haiku*)
+    library_names_spec='$libname$shrext'
+    ;;
   hpux9* | hpux10* | hpux11*)
     case $host_cpu in
       ia64*)
@@ -582,7 +597,7 @@ case "$host_os" in
     ;;
   linux*oldld* | linux*aout* | linux*coff*)
     ;;
-  linux* | k*bsd*-gnu)
+  linux* | k*bsd*-gnu | kopensolaris*-gnu)
     library_names_spec='$libname$shrext'
     ;;
   knetbsd*-gnu)
@@ -594,7 +609,7 @@ case "$host_os" in
   newsos6)
     library_names_spec='$libname$shrext'
     ;;
-  nto-qnx*)
+  *nto* | *qnx*)
     library_names_spec='$libname$shrext'
     ;;
   openbsd*)
@@ -625,6 +640,9 @@ case "$host_os" in
   sysv5* | sco3.2v5* | sco5v6* | unixware* | OpenUNIX* | sysv4*uw2*)
     library_names_spec='$libname$shrext'
     ;;
+  tpf*)
+    library_names_spec='$libname$shrext'
+    ;;
   uts4*)
     library_names_spec='$libname$shrext'
     ;;
diff --git a/extension/build-aux/config.sub b/extension/build-aux/config.sub
index aa2cf19b..092cff00 100755
--- a/extension/build-aux/config.sub
+++ b/extension/build-aux/config.sub
@@ -1,24 +1,18 @@
 #! /bin/sh
 # Configuration validation subroutine script.
-#   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-#   2011, 2012 Free Software Foundation, Inc.
+#   Copyright 1992-2014 Free Software Foundation, Inc.
 
-timestamp='2012-06-17'
+timestamp='2014-01-01'
 
-# This file is (in principle) common to ALL GNU software.
-# The presence of a machine in this file suggests that SOME GNU software
-# can handle that machine.  It does not imply ALL GNU software can.
-#
-# This file is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
+# This file is free software; you can redistribute it and/or modify it
+# under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
 # (at your option) any later version.
 #
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, see <http://www.gnu.org/licenses/>.
@@ -26,11 +20,12 @@ timestamp='2012-06-17'
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
+# the same distribution terms that you use for the rest of that
+# program.  This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
 
 
-# Please send patches to <config-patches@gnu.org>.  Submit a context
-# diff and a properly formatted GNU ChangeLog entry.
+# Please send patches with a ChangeLog entry to config-patches@gnu.org.
 #
 # Configuration subroutine to validate and canonicalize a configuration type.
 # Supply the specified configuration type as an argument.
@@ -73,9 +68,7 @@ Report bugs and patches to <config-patches@gnu.org>."
 version="\
 GNU config.sub ($timestamp)
 
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012
-Free Software Foundation, Inc.
+Copyright 1992-2014 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -123,7 +116,7 @@ esac
 maybe_os=`echo $1 | sed 's/^\(.*\)-\([^-]*-[^-]*\)$/\2/'`
 case $maybe_os in
   nto-qnx* | linux-gnu* | linux-android* | linux-dietlibc | linux-newlib* | \
-  linux-uclibc* | uclinux-uclibc* | uclinux-gnu* | kfreebsd*-gnu* | \
+  linux-musl* | linux-uclibc* | uclinux-uclibc* | uclinux-gnu* | kfreebsd*-gnu* | \
   knetbsd*-gnu* | netbsd*-gnu* | \
   kopensolaris*-gnu* | \
   storm-chaos* | os2-emx* | rtmk-nova*)
@@ -156,7 +149,7 @@ case $os in
 	-convergent* | -ncr* | -news | -32* | -3600* | -3100* | -hitachi* |\
 	-c[123]* | -convex* | -sun | -crds | -omron* | -dg | -ultra | -tti* | \
 	-harris | -dolphin | -highlevel | -gould | -cbm | -ns | -masscomp | \
-	-apple | -axis | -knuth | -cray | -microblaze)
+	-apple | -axis | -knuth | -cray | -microblaze*)
 		os=
 		basic_machine=$1
 		;;
@@ -259,10 +252,12 @@ case $basic_machine in
 	| alpha | alphaev[4-8] | alphaev56 | alphaev6[78] | alphapca5[67] \
 	| alpha64 | alpha64ev[4-8] | alpha64ev56 | alpha64ev6[78] | alpha64pca5[67] \
 	| am33_2.0 \
-	| arc | arm | arm[bl]e | arme[lb] | armv[2345] | armv[345][lb] | avr | avr32 \
-        | be32 | be64 \
+	| arc | arceb \
+	| arm | arm[bl]e | arme[lb] | armv[2-8] | armv[3-8][lb] | armv7[arm] \
+	| avr | avr32 \
+	| be32 | be64 \
 	| bfin \
-	| c4x | clipper \
+	| c4x | c8051 | clipper \
 	| d10v | d30v | dlx | dsp16xx \
 	| epiphany \
 	| fido | fr30 | frv \
@@ -270,10 +265,11 @@ case $basic_machine in
 	| hexagon \
 	| i370 | i860 | i960 | ia64 \
 	| ip2k | iq2000 \
+	| k1om \
 	| le32 | le64 \
 	| lm32 \
 	| m32c | m32r | m32rle | m68000 | m68k | m88k \
-	| maxq | mb | microblaze | mcore | mep | metag \
+	| maxq | mb | microblaze | microblazeel | mcore | mep | metag \
 	| mips | mipsbe | mipseb | mipsel | mipsle \
 	| mips16 \
 	| mips64 | mips64el \
@@ -291,16 +287,17 @@ case $basic_machine in
 	| mipsisa64r2 | mipsisa64r2el \
 	| mipsisa64sb1 | mipsisa64sb1el \
 	| mipsisa64sr71k | mipsisa64sr71kel \
+	| mipsr5900 | mipsr5900el \
 	| mipstx39 | mipstx39el \
 	| mn10200 | mn10300 \
 	| moxie \
 	| mt \
 	| msp430 \
 	| nds32 | nds32le | nds32be \
-	| nios | nios2 \
+	| nios | nios2 | nios2eb | nios2el \
 	| ns16k | ns32k \
 	| open8 \
-	| or32 \
+	| or1k | or32 \
 	| pdp10 | pdp11 | pj | pjl \
 	| powerpc | powerpc64 | powerpc64le | powerpcle \
 	| pyramid \
@@ -328,7 +325,7 @@ case $basic_machine in
 	c6x)
 		basic_machine=tic6x-unknown
 		;;
-	m6811 | m68hc11 | m6812 | m68hc12 | m68hcs12x | picochip)
+	m6811 | m68hc11 | m6812 | m68hc12 | m68hcs12x | nvptx | picochip)
 		basic_machine=$basic_machine-unknown
 		os=-none
 		;;
@@ -370,13 +367,13 @@ case $basic_machine in
 	| aarch64-* | aarch64_be-* \
 	| alpha-* | alphaev[4-8]-* | alphaev56-* | alphaev6[78]-* \
 	| alpha64-* | alpha64ev[4-8]-* | alpha64ev56-* | alpha64ev6[78]-* \
-	| alphapca5[67]-* | alpha64pca5[67]-* | arc-* \
+	| alphapca5[67]-* | alpha64pca5[67]-* | arc-* | arceb-* \
 	| arm-*  | armbe-* | armle-* | armeb-* | armv*-* \
 	| avr-* | avr32-* \
 	| be32-* | be64-* \
 	| bfin-* | bs2000-* \
 	| c[123]* | c30-* | [cjt]90-* | c4x-* \
-	| clipper-* | craynv-* | cydra-* \
+	| c8051-* | clipper-* | craynv-* | cydra-* \
 	| d10v-* | d30v-* | dlx-* \
 	| elxsi-* \
 	| f30[01]-* | f700-* | fido-* | fr30-* | frv-* | fx80-* \
@@ -385,11 +382,13 @@ case $basic_machine in
 	| hexagon-* \
 	| i*86-* | i860-* | i960-* | ia64-* \
 	| ip2k-* | iq2000-* \
+	| k1om-* \
 	| le32-* | le64-* \
 	| lm32-* \
 	| m32c-* | m32r-* | m32rle-* \
 	| m68000-* | m680[012346]0-* | m68360-* | m683?2-* | m68k-* \
-	| m88110-* | m88k-* | maxq-* | mcore-* | metag-* | microblaze-* \
+	| m88110-* | m88k-* | maxq-* | mcore-* | metag-* \
+	| microblaze-* | microblazeel-* \
 	| mips-* | mipsbe-* | mipseb-* | mipsel-* | mipsle-* \
 	| mips16-* \
 	| mips64-* | mips64el-* \
@@ -407,12 +406,13 @@ case $basic_machine in
 	| mipsisa64r2-* | mipsisa64r2el-* \
 	| mipsisa64sb1-* | mipsisa64sb1el-* \
 	| mipsisa64sr71k-* | mipsisa64sr71kel-* \
+	| mipsr5900-* | mipsr5900el-* \
 	| mipstx39-* | mipstx39el-* \
 	| mmix-* \
 	| mt-* \
 	| msp430-* \
 	| nds32-* | nds32le-* | nds32be-* \
-	| nios-* | nios2-* \
+	| nios-* | nios2-* | nios2eb-* | nios2el-* \
 	| none-* | np1-* | ns16k-* | ns32k-* \
 	| open8-* \
 	| orion-* \
@@ -788,11 +788,15 @@ case $basic_machine in
 		basic_machine=ns32k-utek
 		os=-sysv
 		;;
-	microblaze)
+	microblaze*)
 		basic_machine=microblaze-xilinx
 		;;
+	mingw64)
+		basic_machine=x86_64-pc
+		os=-mingw64
+		;;
 	mingw32)
-		basic_machine=i386-pc
+		basic_machine=i686-pc
 		os=-mingw32
 		;;
 	mingw32ce)
@@ -828,7 +832,7 @@ case $basic_machine in
 		basic_machine=`echo $basic_machine | sed -e 's/ms1-/mt-/'`
 		;;
 	msys)
-		basic_machine=i386-pc
+		basic_machine=i686-pc
 		os=-msys
 		;;
 	mvs)
@@ -1019,7 +1023,11 @@ case $basic_machine in
 		basic_machine=i586-unknown
 		os=-pw32
 		;;
-	rdos)
+	rdos | rdos64)
+		basic_machine=x86_64-pc
+		os=-rdos
+		;;
+	rdos32)
 		basic_machine=i386-pc
 		os=-rdos
 		;;
@@ -1346,7 +1354,7 @@ case $os in
 	-gnu* | -bsd* | -mach* | -minix* | -genix* | -ultrix* | -irix* \
 	      | -*vms* | -sco* | -esix* | -isc* | -aix* | -cnk* | -sunos | -sunos[34]*\
 	      | -hpux* | -unos* | -osf* | -luna* | -dgux* | -auroraux* | -solaris* \
-	      | -sym* | -kopensolaris* \
+	      | -sym* | -kopensolaris* | -plan9* \
 	      | -amigaos* | -amigados* | -msdos* | -newsos* | -unicos* | -aof* \
 	      | -aos* | -aros* \
 	      | -nindy* | -vxsim* | -vxworks* | -ebmon* | -hms* | -mvs* \
@@ -1359,8 +1367,8 @@ case $os in
 	      | -udi* | -eabi* | -lites* | -ieee* | -go32* | -aux* \
 	      | -chorusos* | -chorusrdb* | -cegcc* \
 	      | -cygwin* | -msys* | -pe* | -psos* | -moss* | -proelf* | -rtems* \
-	      | -mingw32* | -linux-gnu* | -linux-android* \
-	      | -linux-newlib* | -linux-uclibc* \
+	      | -mingw32* | -mingw64* | -linux-gnu* | -linux-android* \
+	      | -linux-newlib* | -linux-musl* | -linux-uclibc* \
 	      | -uxpv* | -beos* | -mpeix* | -udk* \
 	      | -interix* | -uwin* | -mks* | -rhapsody* | -darwin* | -opened* \
 	      | -openstep* | -oskit* | -conix* | -pw32* | -nonstopux* \
@@ -1492,9 +1500,6 @@ case $os in
 	-aros*)
 		os=-aros
 		;;
-	-kaos*)
-		os=-kaos
-		;;
 	-zvmoe)
 		os=-zvmoe
 		;;
@@ -1543,6 +1548,9 @@ case $basic_machine in
 	c4x-* | tic4x-*)
 		os=-coff
 		;;
+	c8051-*)
+		os=-elf
+		;;
 	hexagon-*)
 		os=-elf
 		;;
@@ -1586,6 +1594,9 @@ case $basic_machine in
 	mips*-*)
 		os=-elf
 		;;
+	or1k-*)
+		os=-elf
+		;;
 	or32-*)
 		os=-coff
 		;;
diff --git a/extension/build-aux/depcomp b/extension/build-aux/depcomp
index 0544c683..31788017 100755
--- a/extension/build-aux/depcomp
+++ b/extension/build-aux/depcomp
@@ -1,9 +1,9 @@
 #! /bin/sh
 # depcomp - compile a program generating dependencies as side-effects
 
-scriptversion=2012-07-12.20; # UTC
+scriptversion=2013-05-30.07; # UTC
 
-# Copyright (C) 1999-2012 Free Software Foundation, Inc.
+# Copyright (C) 1999-2013 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -27,9 +27,9 @@ scriptversion=2012-07-12.20; # UTC
 
 case $1 in
   '')
-     echo "$0: No command.  Try '$0 --help' for more information." 1>&2
-     exit 1;
-     ;;
+    echo "$0: No command.  Try '$0 --help' for more information." 1>&2
+    exit 1;
+    ;;
   -h | --h*)
     cat <<\EOF
 Usage: depcomp [--help] [--version] PROGRAM [ARGS]
@@ -56,11 +56,65 @@ EOF
     ;;
 esac
 
+# Get the directory component of the given path, and save it in the
+# global variables '$dir'.  Note that this directory component will
+# be either empty or ending with a '/' character.  This is deliberate.
+set_dir_from ()
+{
+  case $1 in
+    */*) dir=`echo "$1" | sed -e 's|/[^/]*$|/|'`;;
+      *) dir=;;
+  esac
+}
+
+# Get the suffix-stripped basename of the given path, and save it the
+# global variable '$base'.
+set_base_from ()
+{
+  base=`echo "$1" | sed -e 's|^.*/||' -e 's/\.[^.]*$//'`
+}
+
+# If no dependency file was actually created by the compiler invocation,
+# we still have to create a dummy depfile, to avoid errors with the
+# Makefile "include basename.Plo" scheme.
+make_dummy_depfile ()
+{
+  echo "#dummy" > "$depfile"
+}
+
+# Factor out some common post-processing of the generated depfile.
+# Requires the auxiliary global variable '$tmpdepfile' to be set.
+aix_post_process_depfile ()
+{
+  # If the compiler actually managed to produce a dependency file,
+  # post-process it.
+  if test -f "$tmpdepfile"; then
+    # Each line is of the form 'foo.o: dependency.h'.
+    # Do two passes, one to just change these to
+    #   $object: dependency.h
+    # and one to simply output
+    #   dependency.h:
+    # which is needed to avoid the deleted-header problem.
+    { sed -e "s,^.*\.[$lower]*:,$object:," < "$tmpdepfile"
+      sed -e "s,^.*\.[$lower]*:[$tab ]*,," -e 's,$,:,' < "$tmpdepfile"
+    } > "$depfile"
+    rm -f "$tmpdepfile"
+  else
+    make_dummy_depfile
+  fi
+}
+
 # A tabulation character.
 tab='	'
 # A newline character.
 nl='
 '
+# Character ranges might be problematic outside the C locale.
+# These definitions help.
+upper=ABCDEFGHIJKLMNOPQRSTUVWXYZ
+lower=abcdefghijklmnopqrstuvwxyz
+digits=0123456789
+alpha=${upper}${lower}
 
 if test -z "$depmode" || test -z "$source" || test -z "$object"; then
   echo "depcomp: Variables source, object and depmode must be set" 1>&2
@@ -74,6 +128,9 @@ tmpdepfile=${tmpdepfile-`echo "$depfile" | sed 's/\.\([^.]*\)$/.T\1/'`}
 
 rm -f "$tmpdepfile"
 
+# Avoid interferences from the environment.
+gccflag= dashmflag=
+
 # Some modes work just like other modes, but use different flags.  We
 # parameterize here, but still list the modes in the big case below,
 # to make depend.m4 easier to write.  Note that we *cannot* use a case
@@ -85,32 +142,32 @@ if test "$depmode" = hp; then
 fi
 
 if test "$depmode" = dashXmstdout; then
-   # This is just like dashmstdout with a different argument.
-   dashmflag=-xM
-   depmode=dashmstdout
+  # This is just like dashmstdout with a different argument.
+  dashmflag=-xM
+  depmode=dashmstdout
 fi
 
 cygpath_u="cygpath -u -f -"
 if test "$depmode" = msvcmsys; then
-   # This is just like msvisualcpp but w/o cygpath translation.
-   # Just convert the backslash-escaped backslashes to single forward
-   # slashes to satisfy depend.m4
-   cygpath_u='sed s,\\\\,/,g'
-   depmode=msvisualcpp
+  # This is just like msvisualcpp but w/o cygpath translation.
+  # Just convert the backslash-escaped backslashes to single forward
+  # slashes to satisfy depend.m4
+  cygpath_u='sed s,\\\\,/,g'
+  depmode=msvisualcpp
 fi
 
 if test "$depmode" = msvc7msys; then
-   # This is just like msvc7 but w/o cygpath translation.
-   # Just convert the backslash-escaped backslashes to single forward
-   # slashes to satisfy depend.m4
-   cygpath_u='sed s,\\\\,/,g'
-   depmode=msvc7
+  # This is just like msvc7 but w/o cygpath translation.
+  # Just convert the backslash-escaped backslashes to single forward
+  # slashes to satisfy depend.m4
+  cygpath_u='sed s,\\\\,/,g'
+  depmode=msvc7
 fi
 
 if test "$depmode" = xlc; then
-   # IBM C/C++ Compilers xlc/xlC can output gcc-like dependency informations.
-   gccflag=-qmakedep=gcc,-MF
-   depmode=gcc
+  # IBM C/C++ Compilers xlc/xlC can output gcc-like dependency information.
+  gccflag=-qmakedep=gcc,-MF
+  depmode=gcc
 fi
 
 case "$depmode" in
@@ -133,8 +190,7 @@ gcc3)
   done
   "$@"
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
@@ -142,13 +198,17 @@ gcc3)
   ;;
 
 gcc)
+## Note that this doesn't just cater to obsosete pre-3.x GCC compilers.
+## but also to in-use compilers like IMB xlc/xlC and the HP C compiler.
+## (see the conditional assignment to $gccflag above).
 ## There are various ways to get dependency output from gcc.  Here's
 ## why we pick this rather obscure method:
 ## - Don't want to use -MD because we'd like the dependencies to end
 ##   up in a subdir.  Having to rename by hand is ugly.
 ##   (We might end up doing this anyway to support other compilers.)
 ## - The DEPENDENCIES_OUTPUT environment variable makes gcc act like
-##   -MM, not -M (despite what the docs say).
+##   -MM, not -M (despite what the docs say).  Also, it might not be
+##   supported by the other compilers which use the 'gcc' depmode.
 ## - Using -M directly means running the compiler twice (even worse
 ##   than renaming).
   if test -z "$gccflag"; then
@@ -156,15 +216,14 @@ gcc)
   fi
   "$@" -Wp,"$gccflag$tmpdepfile"
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
   rm -f "$depfile"
   echo "$object : \\" > "$depfile"
-  alpha=ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
-## The second -e expression handles DOS-style file names with drive letters.
+  # The second -e expression handles DOS-style file names with drive
+  # letters.
   sed -e 's/^[^:]*: / /' \
       -e 's/^['$alpha']:\/[^:]*: / /' < "$tmpdepfile" >> "$depfile"
 ## This next piece of magic avoids the "deleted header file" problem.
@@ -173,15 +232,15 @@ gcc)
 ## typically no way to rebuild the header).  We avoid this by adding
 ## dummy dependencies for each header file.  Too bad gcc doesn't do
 ## this for us directly.
-  tr ' ' "$nl" < "$tmpdepfile" |
 ## Some versions of gcc put a space before the ':'.  On the theory
 ## that the space means something, we add a space to the output as
 ## well.  hp depmode also adds that space, but also prefixes the VPATH
 ## to the object.  Take care to not repeat it in the output.
 ## Some versions of the HPUX 10.20 sed can't process this invocation
 ## correctly.  Breaking it into two sed invocations is a workaround.
-    sed -e 's/^\\$//' -e '/^$/d' -e "s|.*$object$||" -e '/:$/d' \
-      | sed -e 's/$/ :/' >> "$depfile"
+  tr ' ' "$nl" < "$tmpdepfile" \
+    | sed -e 's/^\\$//' -e '/^$/d' -e "s|.*$object$||" -e '/:$/d' \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -192,47 +251,6 @@ hp)
   exit 1
   ;;
 
-sgi)
-  if test "$libtool" = yes; then
-    "$@" "-Wp,-MDupdate,$tmpdepfile"
-  else
-    "$@" -MDupdate "$tmpdepfile"
-  fi
-  stat=$?
-  if test $stat -eq 0; then :
-  else
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  rm -f "$depfile"
-
-  if test -f "$tmpdepfile"; then  # yes, the sourcefile depend on other files
-    echo "$object : \\" > "$depfile"
-
-    # Clip off the initial element (the dependent).  Don't try to be
-    # clever and replace this with sed code, as IRIX sed won't handle
-    # lines with more than a fixed number of characters (4096 in
-    # IRIX 6.2 sed, 8192 in IRIX 6.5).  We also remove comment lines;
-    # the IRIX cc adds comments like '#:fec' to the end of the
-    # dependency line.
-    tr ' ' "$nl" < "$tmpdepfile" \
-    | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' | \
-    tr "$nl" ' ' >> "$depfile"
-    echo >> "$depfile"
-
-    # The second pass generates a dummy entry for each header file.
-    tr ' ' "$nl" < "$tmpdepfile" \
-   | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' -e 's/$/:/' \
-   >> "$depfile"
-  else
-    # The sourcefile does not contain any dependencies, so just
-    # store a dummy comment line, to avoid errors with the Makefile
-    # "include basename.Plo" scheme.
-    echo "#dummy" > "$depfile"
-  fi
-  rm -f "$tmpdepfile"
-  ;;
-
 xlc)
   # This case exists only to let depend.m4 do its work.  It works by
   # looking at the text of this script.  This case will never be run,
@@ -246,9 +264,8 @@ aix)
   # current directory.  Also, the AIX compiler puts '$object:' at the
   # start of each line; $object doesn't have directory information.
   # Version 6 uses the directory in both cases.
-  dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-  test "x$dir" = "x$object" && dir=
-  base=`echo "$object" | sed -e 's|^.*/||' -e 's/\.o$//' -e 's/\.lo$//'`
+  set_dir_from "$object"
+  set_base_from "$object"
   if test "$libtool" = yes; then
     tmpdepfile1=$dir$base.u
     tmpdepfile2=$base.u
@@ -261,9 +278,7 @@ aix)
     "$@" -M
   fi
   stat=$?
-
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
     exit $stat
   fi
@@ -272,65 +287,37 @@ aix)
   do
     test -f "$tmpdepfile" && break
   done
-  if test -f "$tmpdepfile"; then
-    # Each line is of the form 'foo.o: dependent.h'.
-    # Do two passes, one to just change these to
-    # '$object: dependent.h' and one to simply 'dependent.h:'.
-    sed -e "s,^.*\.[a-z]*:,$object:," < "$tmpdepfile" > "$depfile"
-    sed -e 's,^.*\.[a-z]*:['"$tab"' ]*,,' -e 's,$,:,' < "$tmpdepfile" >> "$depfile"
-  else
-    # The sourcefile does not contain any dependencies, so just
-    # store a dummy comment line, to avoid errors with the Makefile
-    # "include basename.Plo" scheme.
-    echo "#dummy" > "$depfile"
-  fi
-  rm -f "$tmpdepfile"
+  aix_post_process_depfile
   ;;
 
-icc)
-  # Intel's C compiler anf tcc (Tiny C Compiler) understand '-MD -MF file'.
-  # However on
-  #    $CC -MD -MF foo.d -c -o sub/foo.o sub/foo.c
-  # ICC 7.0 will fill foo.d with something like
-  #    foo.o: sub/foo.c
-  #    foo.o: sub/foo.h
-  # which is wrong.  We want
-  #    sub/foo.o: sub/foo.c
-  #    sub/foo.o: sub/foo.h
-  #    sub/foo.c:
-  #    sub/foo.h:
-  # ICC 7.1 will output
-  #    foo.o: sub/foo.c sub/foo.h
-  # and will wrap long lines using '\':
-  #    foo.o: sub/foo.c ... \
-  #     sub/foo.h ... \
-  #     ...
-  # tcc 0.9.26 (FIXME still under development at the moment of writing)
-  # will emit a similar output, but also prepend the continuation lines
-  # with horizontal tabulation characters.
+tcc)
+  # tcc (Tiny C Compiler) understand '-MD -MF file' since version 0.9.26
+  # FIXME: That version still under development at the moment of writing.
+  #        Make that this statement remains true also for stable, released
+  #        versions.
+  # It will wrap lines (doesn't matter whether long or short) with a
+  # trailing '\', as in:
+  #
+  #   foo.o : \
+  #    foo.c \
+  #    foo.h \
+  #
+  # It will put a trailing '\' even on the last line, and will use leading
+  # spaces rather than leading tabs (at least since its commit 0394caf7
+  # "Emit spaces for -MD").
   "$@" -MD -MF "$tmpdepfile"
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
   rm -f "$depfile"
-  # Each line is of the form 'foo.o: dependent.h',
-  # or 'foo.o: dep1.h dep2.h \', or ' dep3.h dep4.h \'.
-  # Do two passes, one to just change these to
-  # '$object: dependent.h' and one to simply 'dependent.h:'.
-  sed -e "s/^[ $tab][ $tab]*/  /" -e "s,^[^:]*:,$object :," \
-    < "$tmpdepfile" > "$depfile"
-  sed '
-    s/[ '"$tab"'][ '"$tab"']*/ /g
-    s/^ *//
-    s/ *\\*$//
-    s/^[^:]*: *//
-    /^$/d
-    /:$/d
-    s/$/ :/
-  ' < "$tmpdepfile" >> "$depfile"
+  # Each non-empty line is of the form 'foo.o : \' or ' dep.h \'.
+  # We have to change lines of the first kind to '$object: \'.
+  sed -e "s|.*:|$object :|" < "$tmpdepfile" > "$depfile"
+  # And for each line of the second kind, we have to emit a 'dep.h:'
+  # dummy dependency, to avoid the deleted-header problem.
+  sed -n -e 's|^  *\(.*\) *\\$|\1:|p' < "$tmpdepfile" >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -349,34 +336,37 @@ pgcc)
   #    foo.o: sub/foo.c ... \
   #     sub/foo.h ... \
   #     ...
-  dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-  test "x$dir" = "x$object" && dir=
+  set_dir_from "$object"
   # Use the source, not the object, to determine the base name, since
   # that's sadly what pgcc will do too.
-  base=`echo "$source" | sed -e 's|^.*/||' -e 's/\.[-_a-zA-Z0-9]*$//'`
-  tmpdepfile="$base.d"
+  set_base_from "$source"
+  tmpdepfile=$base.d
 
   # For projects that build the same source file twice into different object
   # files, the pgcc approach of using the *source* file root name can cause
   # problems in parallel builds.  Use a locking strategy to avoid stomping on
   # the same $tmpdepfile.
-  lockdir="$base.d-lock"
-  trap "echo '$0: caught signal, cleaning up...' >&2; rm -rf $lockdir" 1 2 13 15
+  lockdir=$base.d-lock
+  trap "
+    echo '$0: caught signal, cleaning up...' >&2
+    rmdir '$lockdir'
+    exit 1
+  " 1 2 13 15
   numtries=100
   i=$numtries
-  while test $i -gt 0 ; do
+  while test $i -gt 0; do
     # mkdir is a portable test-and-set.
-    if mkdir $lockdir 2>/dev/null; then
+    if mkdir "$lockdir" 2>/dev/null; then
       # This process acquired the lock.
       "$@" -MD
       stat=$?
       # Release the lock.
-      rm -rf $lockdir
+      rmdir "$lockdir"
       break
     else
-      ## the lock is being held by a different process,
-      ## wait until the winning process is done or we timeout
-      while test -d $lockdir && test $i -gt 0; do
+      # If the lock is being held by a different process, wait
+      # until the winning process is done or we timeout.
+      while test -d "$lockdir" && test $i -gt 0; do
         sleep 1
         i=`expr $i - 1`
       done
@@ -402,8 +392,8 @@ pgcc)
   sed "s,^[^:]*:,$object :," < "$tmpdepfile" > "$depfile"
   # Some versions of the HPUX 10.20 sed can't process this invocation
   # correctly.  Breaking it into two sed invocations is a workaround.
-  sed 's,^[^:]*: \(.*\)$,\1,;s/^\\$//;/^$/d;/:$/d' < "$tmpdepfile" |
-    sed -e 's/$/ :/' >> "$depfile"
+  sed 's,^[^:]*: \(.*\)$,\1,;s/^\\$//;/^$/d;/:$/d' < "$tmpdepfile" \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -414,9 +404,8 @@ hp2)
   # 'foo.d', which lands next to the object file, wherever that
   # happens to be.
   # Much of this is similar to the tru64 case; see comments there.
-  dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-  test "x$dir" = "x$object" && dir=
-  base=`echo "$object" | sed -e 's|^.*/||' -e 's/\.o$//' -e 's/\.lo$//'`
+  set_dir_from  "$object"
+  set_base_from "$object"
   if test "$libtool" = yes; then
     tmpdepfile1=$dir$base.d
     tmpdepfile2=$dir.libs/$base.d
@@ -427,8 +416,7 @@ hp2)
     "$@" +Maked
   fi
   stat=$?
-  if test $stat -eq 0; then :
-  else
+  if test $stat -ne 0; then
      rm -f "$tmpdepfile1" "$tmpdepfile2"
      exit $stat
   fi
@@ -438,76 +426,61 @@ hp2)
     test -f "$tmpdepfile" && break
   done
   if test -f "$tmpdepfile"; then
-    sed -e "s,^.*\.[a-z]*:,$object:," "$tmpdepfile" > "$depfile"
+    sed -e "s,^.*\.[$lower]*:,$object:," "$tmpdepfile" > "$depfile"
     # Add 'dependent.h:' lines.
     sed -ne '2,${
-	       s/^ *//
-	       s/ \\*$//
-	       s/$/:/
-	       p
-	     }' "$tmpdepfile" >> "$depfile"
+               s/^ *//
+               s/ \\*$//
+               s/$/:/
+               p
+             }' "$tmpdepfile" >> "$depfile"
   else
-    echo "#dummy" > "$depfile"
+    make_dummy_depfile
   fi
   rm -f "$tmpdepfile" "$tmpdepfile2"
   ;;
 
 tru64)
-   # The Tru64 compiler uses -MD to generate dependencies as a side
-   # effect.  'cc -MD -o foo.o ...' puts the dependencies into 'foo.o.d'.
-   # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put
-   # dependencies in 'foo.d' instead, so we check for that too.
-   # Subdirectories are respected.
-   dir=`echo "$object" | sed -e 's|/[^/]*$|/|'`
-   test "x$dir" = "x$object" && dir=
-   base=`echo "$object" | sed -e 's|^.*/||' -e 's/\.o$//' -e 's/\.lo$//'`
-
-   if test "$libtool" = yes; then
-      # With Tru64 cc, shared objects can also be used to make a
-      # static library.  This mechanism is used in libtool 1.4 series to
-      # handle both shared and static libraries in a single compilation.
-      # With libtool 1.4, dependencies were output in $dir.libs/$base.lo.d.
-      #
-      # With libtool 1.5 this exception was removed, and libtool now
-      # generates 2 separate objects for the 2 libraries.  These two
-      # compilations output dependencies in $dir.libs/$base.o.d and
-      # in $dir$base.o.d.  We have to check for both files, because
-      # one of the two compilations can be disabled.  We should prefer
-      # $dir$base.o.d over $dir.libs/$base.o.d because the latter is
-      # automatically cleaned when .libs/ is deleted, while ignoring
-      # the former would cause a distcleancheck panic.
-      tmpdepfile1=$dir.libs/$base.lo.d   # libtool 1.4
-      tmpdepfile2=$dir$base.o.d          # libtool 1.5
-      tmpdepfile3=$dir.libs/$base.o.d    # libtool 1.5
-      tmpdepfile4=$dir.libs/$base.d      # Compaq CCC V6.2-504
-      "$@" -Wc,-MD
-   else
-      tmpdepfile1=$dir$base.o.d
-      tmpdepfile2=$dir$base.d
-      tmpdepfile3=$dir$base.d
-      tmpdepfile4=$dir$base.d
-      "$@" -MD
-   fi
-
-   stat=$?
-   if test $stat -eq 0; then :
-   else
-      rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" "$tmpdepfile4"
-      exit $stat
-   fi
-
-   for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" "$tmpdepfile4"
-   do
-     test -f "$tmpdepfile" && break
-   done
-   if test -f "$tmpdepfile"; then
-      sed -e "s,^.*\.[a-z]*:,$object:," < "$tmpdepfile" > "$depfile"
-      sed -e 's,^.*\.[a-z]*:['"$tab"' ]*,,' -e 's,$,:,' < "$tmpdepfile" >> "$depfile"
-   else
-      echo "#dummy" > "$depfile"
-   fi
-   rm -f "$tmpdepfile"
-   ;;
+  # The Tru64 compiler uses -MD to generate dependencies as a side
+  # effect.  'cc -MD -o foo.o ...' puts the dependencies into 'foo.o.d'.
+  # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put
+  # dependencies in 'foo.d' instead, so we check for that too.
+  # Subdirectories are respected.
+  set_dir_from  "$object"
+  set_base_from "$object"
+
+  if test "$libtool" = yes; then
+    # Libtool generates 2 separate objects for the 2 libraries.  These
+    # two compilations output dependencies in $dir.libs/$base.o.d and
+    # in $dir$base.o.d.  We have to check for both files, because
+    # one of the two compilations can be disabled.  We should prefer
+    # $dir$base.o.d over $dir.libs/$base.o.d because the latter is
+    # automatically cleaned when .libs/ is deleted, while ignoring
+    # the former would cause a distcleancheck panic.
+    tmpdepfile1=$dir$base.o.d          # libtool 1.5
+    tmpdepfile2=$dir.libs/$base.o.d    # Likewise.
+    tmpdepfile3=$dir.libs/$base.d      # Compaq CCC V6.2-504
+    "$@" -Wc,-MD
+  else
+    tmpdepfile1=$dir$base.d
+    tmpdepfile2=$dir$base.d
+    tmpdepfile3=$dir$base.d
+    "$@" -MD
+  fi
+
+  stat=$?
+  if test $stat -ne 0; then
+    rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
+    exit $stat
+  fi
+
+  for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
+  do
+    test -f "$tmpdepfile" && break
+  done
+  # Same post-processing that is required for AIX mode.
+  aix_post_process_depfile
+  ;;
 
 msvc7)
   if test "$libtool" = yes; then
@@ -518,8 +491,7 @@ msvc7)
   "$@" $showIncludes > "$tmpdepfile"
   stat=$?
   grep -v '^Note: including file: ' "$tmpdepfile"
-  if test "$stat" = 0; then :
-  else
+  if test $stat -ne 0; then
     rm -f "$tmpdepfile"
     exit $stat
   fi
@@ -545,6 +517,7 @@ $ {
   G
   p
 }' >> "$depfile"
+  echo >> "$depfile" # make sure the fragment doesn't end with a backslash
   rm -f "$tmpdepfile"
   ;;
 
@@ -596,13 +569,14 @@ dashmstdout)
   # in the target name.  This is to cope with DOS-style filenames:
   # a dependency such as 'c:/foo/bar' could be seen as target 'c' otherwise.
   "$@" $dashmflag |
-    sed 's:^['"$tab"' ]*[^:'"$tab"' ][^:][^:]*\:['"$tab"' ]*:'"$object"'\: :' > "$tmpdepfile"
+    sed "s|^[$tab ]*[^:$tab ][^:][^:]*:[$tab ]*|$object: |" > "$tmpdepfile"
   rm -f "$depfile"
   cat < "$tmpdepfile" > "$depfile"
-  tr ' ' "$nl" < "$tmpdepfile" | \
-## Some versions of the HPUX 10.20 sed can't process this invocation
-## correctly.  Breaking it into two sed invocations is a workaround.
-    sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' | sed -e 's/$/ :/' >> "$depfile"
+  # Some versions of the HPUX 10.20 sed can't process this sed invocation
+  # correctly.  Breaking it into two sed invocations is a workaround.
+  tr ' ' "$nl" < "$tmpdepfile" \
+    | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile"
   ;;
 
@@ -655,10 +629,12 @@ makedepend)
   # makedepend may prepend the VPATH from the source file name to the object.
   # No need to regex-escape $object, excess matching of '.' is harmless.
   sed "s|^.*\($object *:\)|\1|" "$tmpdepfile" > "$depfile"
-  sed '1,2d' "$tmpdepfile" | tr ' ' "$nl" | \
-## Some versions of the HPUX 10.20 sed can't process this invocation
-## correctly.  Breaking it into two sed invocations is a workaround.
-    sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' | sed -e 's/$/ :/' >> "$depfile"
+  # Some versions of the HPUX 10.20 sed can't process the last invocation
+  # correctly.  Breaking it into two sed invocations is a workaround.
+  sed '1,2d' "$tmpdepfile" \
+    | tr ' ' "$nl" \
+    | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \
+    | sed -e 's/$/ :/' >> "$depfile"
   rm -f "$tmpdepfile" "$tmpdepfile".bak
   ;;
 
@@ -694,10 +670,10 @@ cpp)
     esac
   done
 
-  "$@" -E |
-    sed -n -e '/^# [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
-       -e '/^#line [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' |
-    sed '$ s: \\$::' > "$tmpdepfile"
+  "$@" -E \
+    | sed -n -e '/^# [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
+             -e '/^#line [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
+    | sed '$ s: \\$::' > "$tmpdepfile"
   rm -f "$depfile"
   echo "$object : \\" > "$depfile"
   cat < "$tmpdepfile" >> "$depfile"
@@ -729,15 +705,15 @@ msvisualcpp)
       shift
       ;;
     "-Gm"|"/Gm"|"-Gi"|"/Gi"|"-ZI"|"/ZI")
-	set fnord "$@"
-	shift
-	shift
-	;;
+        set fnord "$@"
+        shift
+        shift
+        ;;
     *)
-	set fnord "$@" "$arg"
-	shift
-	shift
-	;;
+        set fnord "$@" "$arg"
+        shift
+        shift
+        ;;
     esac
   done
   "$@" -E 2>/dev/null |
diff --git a/extension/build-aux/install-sh b/extension/build-aux/install-sh
index 377bb868..04367377 100755
--- a/extension/build-aux/install-sh
+++ b/extension/build-aux/install-sh
@@ -1,7 +1,7 @@
 #!/bin/sh
 # install - install a program, script, or datafile
 
-scriptversion=2011-11-20.07; # UTC
+scriptversion=2013-10-30.23; # UTC
 
 # This originates from X11R5 (mit/util/scripts/install.sh), which was
 # later released in X11R6 (xc/config/util/install.sh) with the
@@ -41,19 +41,15 @@ scriptversion=2011-11-20.07; # UTC
 # This script is compatible with the BSD install script, but was written
 # from scratch.
 
+tab='	'
 nl='
 '
-IFS=" ""	$nl"
+IFS=" $tab$nl"
 
-# set DOITPROG to echo to test this script
+# Set DOITPROG to "echo" to test this script.
 
-# Don't use :- since 4.3BSD and earlier shells don't like it.
 doit=${DOITPROG-}
-if test -z "$doit"; then
-  doit_exec=exec
-else
-  doit_exec=$doit
-fi
+doit_exec=${doit:-exec}
 
 # Put in absolute file names if you don't have them in your path;
 # or use environment vars.
@@ -68,17 +64,6 @@ mvprog=${MVPROG-mv}
 rmprog=${RMPROG-rm}
 stripprog=${STRIPPROG-strip}
 
-posix_glob='?'
-initialize_posix_glob='
-  test "$posix_glob" != "?" || {
-    if (set -f) 2>/dev/null; then
-      posix_glob=
-    else
-      posix_glob=:
-    fi
-  }
-'
-
 posix_mkdir=
 
 # Desired mode of installed file.
@@ -137,40 +122,39 @@ while test $# -ne 0; do
     -d) dir_arg=true;;
 
     -g) chgrpcmd="$chgrpprog $2"
-	shift;;
+        shift;;
 
     --help) echo "$usage"; exit $?;;
 
     -m) mode=$2
-	case $mode in
-	  *' '* | *'	'* | *'
-'*	  | *'*'* | *'?'* | *'['*)
-	    echo "$0: invalid mode: $mode" >&2
-	    exit 1;;
-	esac
-	shift;;
+        case $mode in
+          *' '* | *"$tab"* | *"$nl"* | *'*'* | *'?'* | *'['*)
+            echo "$0: invalid mode: $mode" >&2
+            exit 1;;
+        esac
+        shift;;
 
     -o) chowncmd="$chownprog $2"
-	shift;;
+        shift;;
 
     -s) stripcmd=$stripprog;;
 
     -t) dst_arg=$2
-	# Protect names problematic for 'test' and other utilities.
-	case $dst_arg in
-	  -* | [=\(\)!]) dst_arg=./$dst_arg;;
-	esac
-	shift;;
+        # Protect names problematic for 'test' and other utilities.
+        case $dst_arg in
+          -* | [=\(\)!]) dst_arg=./$dst_arg;;
+        esac
+        shift;;
 
     -T) no_target_directory=true;;
 
     --version) echo "$0 $scriptversion"; exit $?;;
 
-    --)	shift
-	break;;
+    --) shift
+        break;;
 
-    -*)	echo "$0: invalid option: $1" >&2
-	exit 1;;
+    -*) echo "$0: invalid option: $1" >&2
+        exit 1;;
 
     *)  break;;
   esac
@@ -223,16 +207,16 @@ if test -z "$dir_arg"; then
 
     *[0-7])
       if test -z "$stripcmd"; then
-	u_plus_rw=
+        u_plus_rw=
       else
-	u_plus_rw='% 200'
+        u_plus_rw='% 200'
       fi
       cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;;
     *)
       if test -z "$stripcmd"; then
-	u_plus_rw=
+        u_plus_rw=
       else
-	u_plus_rw=,u+rw
+        u_plus_rw=,u+rw
       fi
       cp_umask=$mode$u_plus_rw;;
   esac
@@ -270,40 +254,14 @@ do
     # if double slashes aren't ignored.
     if test -d "$dst"; then
       if test -n "$no_target_directory"; then
-	echo "$0: $dst_arg: Is a directory" >&2
-	exit 1
+        echo "$0: $dst_arg: Is a directory" >&2
+        exit 1
       fi
       dstdir=$dst
       dst=$dstdir/`basename "$src"`
       dstdir_status=0
     else
-      # Prefer dirname, but fall back on a substitute if dirname fails.
-      dstdir=`
-	(dirname "$dst") 2>/dev/null ||
-	expr X"$dst" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
-	     X"$dst" : 'X\(//\)[^/]' \| \
-	     X"$dst" : 'X\(//\)$' \| \
-	     X"$dst" : 'X\(/\)' \| . 2>/dev/null ||
-	echo X"$dst" |
-	    sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
-		   s//\1/
-		   q
-		 }
-		 /^X\(\/\/\)[^/].*/{
-		   s//\1/
-		   q
-		 }
-		 /^X\(\/\/\)$/{
-		   s//\1/
-		   q
-		 }
-		 /^X\(\/\).*/{
-		   s//\1/
-		   q
-		 }
-		 s/.*/./; q'
-      `
-
+      dstdir=`dirname "$dst"`
       test -d "$dstdir"
       dstdir_status=$?
     fi
@@ -314,74 +272,74 @@ do
   if test $dstdir_status != 0; then
     case $posix_mkdir in
       '')
-	# Create intermediate dirs using mode 755 as modified by the umask.
-	# This is like FreeBSD 'install' as of 1997-10-28.
-	umask=`umask`
-	case $stripcmd.$umask in
-	  # Optimize common cases.
-	  *[2367][2367]) mkdir_umask=$umask;;
-	  .*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
-
-	  *[0-7])
-	    mkdir_umask=`expr $umask + 22 \
-	      - $umask % 100 % 40 + $umask % 20 \
-	      - $umask % 10 % 4 + $umask % 2
-	    `;;
-	  *) mkdir_umask=$umask,go-w;;
-	esac
-
-	# With -d, create the new directory with the user-specified mode.
-	# Otherwise, rely on $mkdir_umask.
-	if test -n "$dir_arg"; then
-	  mkdir_mode=-m$mode
-	else
-	  mkdir_mode=
-	fi
-
-	posix_mkdir=false
-	case $umask in
-	  *[123567][0-7][0-7])
-	    # POSIX mkdir -p sets u+wx bits regardless of umask, which
-	    # is incompatible with FreeBSD 'install' when (umask & 300) != 0.
-	    ;;
-	  *)
-	    tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
-	    trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
-
-	    if (umask $mkdir_umask &&
-		exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
-	    then
-	      if test -z "$dir_arg" || {
-		   # Check for POSIX incompatibilities with -m.
-		   # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
-		   # other-writable bit of parent directory when it shouldn't.
-		   # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
-		   ls_ld_tmpdir=`ls -ld "$tmpdir"`
-		   case $ls_ld_tmpdir in
-		     d????-?r-*) different_mode=700;;
-		     d????-?--*) different_mode=755;;
-		     *) false;;
-		   esac &&
-		   $mkdirprog -m$different_mode -p -- "$tmpdir" && {
-		     ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
-		     test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
-		   }
-		 }
-	      then posix_mkdir=:
-	      fi
-	      rmdir "$tmpdir/d" "$tmpdir"
-	    else
-	      # Remove any dirs left behind by ancient mkdir implementations.
-	      rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
-	    fi
-	    trap '' 0;;
-	esac;;
+        # Create intermediate dirs using mode 755 as modified by the umask.
+        # This is like FreeBSD 'install' as of 1997-10-28.
+        umask=`umask`
+        case $stripcmd.$umask in
+          # Optimize common cases.
+          *[2367][2367]) mkdir_umask=$umask;;
+          .*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
+
+          *[0-7])
+            mkdir_umask=`expr $umask + 22 \
+              - $umask % 100 % 40 + $umask % 20 \
+              - $umask % 10 % 4 + $umask % 2
+            `;;
+          *) mkdir_umask=$umask,go-w;;
+        esac
+
+        # With -d, create the new directory with the user-specified mode.
+        # Otherwise, rely on $mkdir_umask.
+        if test -n "$dir_arg"; then
+          mkdir_mode=-m$mode
+        else
+          mkdir_mode=
+        fi
+
+        posix_mkdir=false
+        case $umask in
+          *[123567][0-7][0-7])
+            # POSIX mkdir -p sets u+wx bits regardless of umask, which
+            # is incompatible with FreeBSD 'install' when (umask & 300) != 0.
+            ;;
+          *)
+            tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
+            trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
+
+            if (umask $mkdir_umask &&
+                exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
+            then
+              if test -z "$dir_arg" || {
+                   # Check for POSIX incompatibilities with -m.
+                   # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
+                   # other-writable bit of parent directory when it shouldn't.
+                   # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
+                   ls_ld_tmpdir=`ls -ld "$tmpdir"`
+                   case $ls_ld_tmpdir in
+                     d????-?r-*) different_mode=700;;
+                     d????-?--*) different_mode=755;;
+                     *) false;;
+                   esac &&
+                   $mkdirprog -m$different_mode -p -- "$tmpdir" && {
+                     ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
+                     test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
+                   }
+                 }
+              then posix_mkdir=:
+              fi
+              rmdir "$tmpdir/d" "$tmpdir"
+            else
+              # Remove any dirs left behind by ancient mkdir implementations.
+              rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
+            fi
+            trap '' 0;;
+        esac;;
     esac
 
     if
       $posix_mkdir && (
-	umask $mkdir_umask &&
-	$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
+        umask $mkdir_umask &&
+        $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
       )
     then :
     else
@@ -391,53 +349,51 @@ do
       # directory the slow way, step by step, checking for races as we go.
 
       case $dstdir in
-	/*) prefix='/';;
-	[-=\(\)!]*) prefix='./';;
-	*)  prefix='';;
+        /*) prefix='/';;
+        [-=\(\)!]*) prefix='./';;
+        *)  prefix='';;
       esac
 
-      eval "$initialize_posix_glob"
-
       oIFS=$IFS
       IFS=/
-      $posix_glob set -f
+      set -f
       set fnord $dstdir
       shift
-      $posix_glob set +f
+      set +f
       IFS=$oIFS
 
       prefixes=
 
       for d
       do
-	test X"$d" = X && continue
-
-	prefix=$prefix$d
-	if test -d "$prefix"; then
-	  prefixes=
-	else
-	  if $posix_mkdir; then
-	    (umask=$mkdir_umask &&
-	     $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
-	    # Don't fail if two instances are running concurrently.
-	    test -d "$prefix" || exit 1
-	  else
-	    case $prefix in
-	      *\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
-	      *) qprefix=$prefix;;
-	    esac
-	    prefixes="$prefixes '$qprefix'"
-	  fi
-	fi
-	prefix=$prefix/
+        test X"$d" = X && continue
+
+        prefix=$prefix$d
+        if test -d "$prefix"; then
+          prefixes=
+        else
+          if $posix_mkdir; then
+            (umask=$mkdir_umask &&
+             $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
+            # Don't fail if two instances are running concurrently.
+            test -d "$prefix" || exit 1
+          else
+            case $prefix in
+              *\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
+              *) qprefix=$prefix;;
+            esac
+            prefixes="$prefixes '$qprefix'"
+          fi
+        fi
+        prefix=$prefix/
       done
 
       if test -n "$prefixes"; then
-	# Don't fail if two instances are running concurrently.
-	(umask $mkdir_umask &&
-	 eval "\$doit_exec \$mkdirprog $prefixes") ||
-	  test -d "$dstdir" || exit 1
-	obsolete_mkdir_used=true
+        # Don't fail if two instances are running concurrently.
+        (umask $mkdir_umask &&
+         eval "\$doit_exec \$mkdirprog $prefixes") ||
+          test -d "$dstdir" || exit 1
+        obsolete_mkdir_used=true
       fi
     fi
   fi
@@ -472,15 +428,12 @@ do
 
     # If -C, don't bother to copy if it wouldn't change the file.
     if $copy_on_change &&
-       old=`LC_ALL=C ls -dlL "$dst"	2>/dev/null` &&
-       new=`LC_ALL=C ls -dlL "$dsttmp"	2>/dev/null` &&
-
-       eval "$initialize_posix_glob" &&
-       $posix_glob set -f &&
+       old=`LC_ALL=C ls -dlL "$dst"     2>/dev/null` &&
+       new=`LC_ALL=C ls -dlL "$dsttmp"  2>/dev/null` &&
+       set -f &&
        set X $old && old=:$2:$4:$5:$6 &&
        set X $new && new=:$2:$4:$5:$6 &&
-       $posix_glob set +f &&
-
+       set +f &&
        test "$old" = "$new" &&
        $cmpprog "$dst" "$dsttmp" >/dev/null 2>&1
     then
@@ -493,24 +446,24 @@ do
       # to itself, or perhaps because mv is so ancient that it does not
       # support -f.
       {
-	# Now remove or move aside any old file at destination location.
-	# We try this two ways since rm can't unlink itself on some
-	# systems and the destination file might be busy for other
-	# reasons.  In this case, the final cleanup might fail but the new
-	# file should still install successfully.
-	{
-	  test ! -f "$dst" ||
-	  $doit $rmcmd -f "$dst" 2>/dev/null ||
-	  { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
-	    { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
-	  } ||
-	  { echo "$0: cannot unlink or rename $dst" >&2
-	    (exit 1); exit 1
-	  }
-	} &&
-
-	# Now rename the file to the real destination.
-	$doit $mvcmd "$dsttmp" "$dst"
+        # Now remove or move aside any old file at destination location.
+        # We try this two ways since rm can't unlink itself on some
+        # systems and the destination file might be busy for other
+        # reasons.  In this case, the final cleanup might fail but the new
+        # file should still install successfully.
+        {
+          test ! -f "$dst" ||
+          $doit $rmcmd -f "$dst" 2>/dev/null ||
+          { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
+            { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
+          } ||
+          { echo "$0: cannot unlink or rename $dst" >&2
+            (exit 1); exit 1
+          }
+        } &&
+
+        # Now rename the file to the real destination.
+        $doit $mvcmd "$dsttmp" "$dst"
       }
     fi || exit 1
 
diff --git a/extension/configh.in b/extension/configh.in
index 8add211a..5842f2f4 100644
--- a/extension/configh.in
+++ b/extension/configh.in
@@ -30,7 +30,8 @@
    */
 #undef HAVE_DECL_DIRFD
 
-/* Define to 1 if you have the <dirent.h> header file. */
+/* Define to 1 if you have the <dirent.h> header file, and it defines `DIR'.
+   */
 #undef HAVE_DIRENT_H
 
 /* Define to 1 if you have the `dirfd' function. */
@@ -75,6 +76,9 @@
 /* Define to 1 if you have the `nanosleep' function. */
 #undef HAVE_NANOSLEEP
 
+/* Define to 1 if you have the <ndir.h> header file, and it defines `DIR'. */
+#undef HAVE_NDIR_H
+
 /* Define to 1 if you have the `select' function. */
 #undef HAVE_SELECT
 
@@ -93,6 +97,14 @@
 /* Define to 1 if `st_blksize' is a member of `struct stat'. */
 #undef HAVE_STRUCT_STAT_ST_BLKSIZE
 
+/* Define to 1 if you have the <sys/dir.h> header file, and it defines `DIR'.
+   */
+#undef HAVE_SYS_DIR_H
+
+/* Define to 1 if you have the <sys/ndir.h> header file, and it defines `DIR'.
+   */
+#undef HAVE_SYS_NDIR_H
+
 /* Define to 1 if you have the <sys/param.h> header file. */
 #undef HAVE_SYS_PARAM_H
 
@@ -108,9 +120,6 @@
 /* Define to 1 if you have the <sys/types.h> header file. */
 #undef HAVE_SYS_TYPES_H
 
-/* Define to 1 if you have the <time.h> header file. */
-#undef HAVE_TIME_H
-
 /* Define to 1 if you have the <unistd.h> header file. */
 #undef HAVE_UNISTD_H
 
@@ -149,6 +158,9 @@
 /* Define to 1 if you have the ANSI C header files. */
 #undef STDC_HEADERS
 
+/* Define to 1 if you can safely include both <sys/time.h> and <time.h>. */
+#undef TIME_WITH_SYS_TIME
+
 /* Enable extensions on AIX 3, Interix.  */
 #ifndef _ALL_SOURCE
 # undef _ALL_SOURCE
diff --git a/extension/configure b/extension/configure
index 025e2723..2105648d 100755
--- a/extension/configure
+++ b/extension/configure
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for GNU Awk Bundled Extensions 4.1.0.
+# Generated by GNU Autoconf 2.69 for GNU Awk Bundled Extensions 4.1.1.
 #
 # Report bugs to <bug-gawk@gnu.org>.
 #
@@ -590,8 +590,8 @@ MAKEFLAGS=
 # Identity of this package.
 PACKAGE_NAME='GNU Awk Bundled Extensions'
 PACKAGE_TARNAME='gawk-extensions'
-PACKAGE_VERSION='4.1.0'
-PACKAGE_STRING='GNU Awk Bundled Extensions 4.1.0'
+PACKAGE_VERSION='4.1.1'
+PACKAGE_STRING='GNU Awk Bundled Extensions 4.1.1'
 PACKAGE_BUGREPORT='bug-gawk@gnu.org'
 PACKAGE_URL='http://www.gnu.org/software/gawk-extensions/'
 
@@ -1333,7 +1333,7 @@ if test "$ac_init_help" = "long"; then
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures GNU Awk Bundled Extensions 4.1.0 to adapt to many kinds of systems.
+\`configure' configures GNU Awk Bundled Extensions 4.1.1 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1403,7 +1403,7 @@ fi
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
-     short | recursive ) echo "Configuration of GNU Awk Bundled Extensions 4.1.0:";;
+     short | recursive ) echo "Configuration of GNU Awk Bundled Extensions 4.1.1:";;
    esac
   cat <<\_ACEOF
 
@@ -1518,7 +1518,7 @@ fi
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-GNU Awk Bundled Extensions configure 4.1.0
+GNU Awk Bundled Extensions configure 4.1.1
 generated by GNU Autoconf 2.69
 
 Copyright (C) 2012 Free Software Foundation, Inc.
@@ -1990,7 +1990,7 @@ cat >config.log <<_ACEOF
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by GNU Awk Bundled Extensions $as_me 4.1.0, which was
+It was created by GNU Awk Bundled Extensions $as_me 4.1.1, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   $ $0 $@
@@ -4172,7 +4172,7 @@ fi
 
 # Define the identity of the package.
  PACKAGE='gawk-extensions'
- VERSION='4.1.0'
+ VERSION='4.1.1'
 
 
 cat >>confdefs.h <<_ACEOF
@@ -14034,7 +14034,7 @@ pkgextensiondir='${libdir}/gawk'
 
 if test "$GCC" = yes
 then
-	CFLAGS="$CFLAGS -Wall -Wextra"
+	CFLAGS="$CFLAGS -Wall"	# Don't add -Wextra, hurts older gcc
 fi
 
 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for special development options" >&5
@@ -14052,6 +14052,177 @@ else
 $as_echo "no" >&6; }
 fi
 
+for ac_header in fnmatch.h limits.h sys/time.h sys/select.h sys/param.h
+do :
+  as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
+ac_fn_c_check_header_mongrel "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default"
+if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
+  cat >>confdefs.h <<_ACEOF
+#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
+_ACEOF
+
+fi
+
+done
+
+ac_header_dirent=no
+for ac_hdr in dirent.h sys/ndir.h sys/dir.h ndir.h; do
+  as_ac_Header=`$as_echo "ac_cv_header_dirent_$ac_hdr" | $as_tr_sh`
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_hdr that defines DIR" >&5
+$as_echo_n "checking for $ac_hdr that defines DIR... " >&6; }
+if eval \${$as_ac_Header+:} false; then :
+  $as_echo_n "(cached) " >&6
+else
+  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+#include <sys/types.h>
+#include <$ac_hdr>
+
+int
+main ()
+{
+if ((DIR *) 0)
+return 0;
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+  eval "$as_ac_Header=yes"
+else
+  eval "$as_ac_Header=no"
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+fi
+eval ac_res=\$$as_ac_Header
+	       { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
+$as_echo "$ac_res" >&6; }
+if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
+  cat >>confdefs.h <<_ACEOF
+#define `$as_echo "HAVE_$ac_hdr" | $as_tr_cpp` 1
+_ACEOF
+
+ac_header_dirent=$ac_hdr; break
+fi
+
+done
+# Two versions of opendir et al. are in -ldir and -lx on SCO Xenix.
+if test $ac_header_dirent = dirent.h; then
+  { $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing opendir" >&5
+$as_echo_n "checking for library containing opendir... " >&6; }
+if ${ac_cv_search_opendir+:} false; then :
+  $as_echo_n "(cached) " >&6
+else
+  ac_func_search_save_LIBS=$LIBS
+cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+
+/* Override any GCC internal prototype to avoid an error.
+   Use char because int might match the return type of a GCC
+   builtin and then its argument prototype would still apply.  */
+#ifdef __cplusplus
+extern "C"
+#endif
+char opendir ();
+int
+main ()
+{
+return opendir ();
+  ;
+  return 0;
+}
+_ACEOF
+for ac_lib in '' dir; do
+  if test -z "$ac_lib"; then
+    ac_res="none required"
+  else
+    ac_res=-l$ac_lib
+    LIBS="-l$ac_lib  $ac_func_search_save_LIBS"
+  fi
+  if ac_fn_c_try_link "$LINENO"; then :
+  ac_cv_search_opendir=$ac_res
+fi
+rm -f core conftest.err conftest.$ac_objext \
+    conftest$ac_exeext
+  if ${ac_cv_search_opendir+:} false; then :
+  break
+fi
+done
+if ${ac_cv_search_opendir+:} false; then :
+
+else
+  ac_cv_search_opendir=no
+fi
+rm conftest.$ac_ext
+LIBS=$ac_func_search_save_LIBS
+fi
+{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_opendir" >&5
+$as_echo "$ac_cv_search_opendir" >&6; }
+ac_res=$ac_cv_search_opendir
+if test "$ac_res" != no; then :
+  test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
+
+fi
+
+else
+  { $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing opendir" >&5
+$as_echo_n "checking for library containing opendir... " >&6; }
+if ${ac_cv_search_opendir+:} false; then :
+  $as_echo_n "(cached) " >&6
+else
+  ac_func_search_save_LIBS=$LIBS
+cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+
+/* Override any GCC internal prototype to avoid an error.
+   Use char because int might match the return type of a GCC
+   builtin and then its argument prototype would still apply.  */
+#ifdef __cplusplus
+extern "C"
+#endif
+char opendir ();
+int
+main ()
+{
+return opendir ();
+  ;
+  return 0;
+}
+_ACEOF
+for ac_lib in '' x; do
+  if test -z "$ac_lib"; then
+    ac_res="none required"
+  else
+    ac_res=-l$ac_lib
+    LIBS="-l$ac_lib  $ac_func_search_save_LIBS"
+  fi
+  if ac_fn_c_try_link "$LINENO"; then :
+  ac_cv_search_opendir=$ac_res
+fi
+rm -f core conftest.err conftest.$ac_objext \
+    conftest$ac_exeext
+  if ${ac_cv_search_opendir+:} false; then :
+  break
+fi
+done
+if ${ac_cv_search_opendir+:} false; then :
+
+else
+  ac_cv_search_opendir=no
+fi
+rm conftest.$ac_ext
+LIBS=$ac_func_search_save_LIBS
+fi
+{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_opendir" >&5
+$as_echo "$ac_cv_search_opendir" >&6; }
+ac_res=$ac_cv_search_opendir
+if test "$ac_res" != no; then :
+  test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
+
+fi
+
+fi
+
 { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether sys/types.h defines makedev" >&5
 $as_echo_n "checking whether sys/types.h defines makedev... " >&6; }
 if ${ac_cv_header_sys_types_h_makedev+:} false; then :
@@ -14102,18 +14273,40 @@ fi
   fi
 fi
 
-for ac_header in dirent.h fnmatch.h limits.h time.h sys/time.h sys/select.h sys/param.h
-do :
-  as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
-ac_fn_c_check_header_mongrel "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default"
-if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
-  cat >>confdefs.h <<_ACEOF
-#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
-_ACEOF
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether time.h and sys/time.h may both be included" >&5
+$as_echo_n "checking whether time.h and sys/time.h may both be included... " >&6; }
+if ${ac_cv_header_time+:} false; then :
+  $as_echo_n "(cached) " >&6
+else
+  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+#include <sys/types.h>
+#include <sys/time.h>
+#include <time.h>
 
+int
+main ()
+{
+if ((struct tm *) 0)
+return 0;
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+  ac_cv_header_time=yes
+else
+  ac_cv_header_time=no
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
 fi
+{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_time" >&5
+$as_echo "$ac_cv_header_time" >&6; }
+if test $ac_cv_header_time = yes; then
 
-done
+$as_echo "#define TIME_WITH_SYS_TIME 1" >>confdefs.h
+
+fi
 
 
 for ac_func in fdopendir fnmatch gettimeofday \
@@ -14824,7 +15017,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by GNU Awk Bundled Extensions $as_me 4.1.0, which was
+This file was extended by GNU Awk Bundled Extensions $as_me 4.1.1, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   CONFIG_FILES    = $CONFIG_FILES
@@ -14892,7 +15085,7 @@ _ACEOF
 cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
 ac_cs_version="\\
-GNU Awk Bundled Extensions config.status 4.1.0
+GNU Awk Bundled Extensions config.status 4.1.1
 configured by $0, generated by GNU Autoconf 2.69,
   with options \\"\$ac_cs_config\\"
 
diff --git a/extension/configure.ac b/extension/configure.ac
index 412fec09..1f876a0e 100644
--- a/extension/configure.ac
+++ b/extension/configure.ac
@@ -1,7 +1,7 @@
 dnl
 dnl configure.ac --- autoconf input file for gawk
 dnl
-dnl Copyright (C) 2012, 2013 the Free Software Foundation, Inc.
+dnl Copyright (C) 2012-2014 the Free Software Foundation, Inc.
 dnl
 dnl This file is part of GAWK, the GNU implementation of the
 dnl AWK Programming Language.
@@ -23,7 +23,7 @@ dnl
 
 dnl Process this file with autoconf to produce a configure script.
 
-AC_INIT([GNU Awk Bundled Extensions], 4.1.0, bug-gawk@gnu.org, gawk-extensions)
+AC_INIT([GNU Awk Bundled Extensions], 4.1.1, bug-gawk@gnu.org, gawk-extensions)
 
 AC_CONFIG_MACRO_DIR([m4])
 AC_CONFIG_AUX_DIR([build-aux])
@@ -51,7 +51,7 @@ AC_SUBST([pkgextensiondir], ['${libdir}/gawk'])
 
 if test "$GCC" = yes
 then
-	CFLAGS="$CFLAGS -Wall -Wextra"
+	CFLAGS="$CFLAGS -Wall"	# Don't add -Wextra, hurts older gcc
 fi
 
 AC_MSG_CHECKING([for special development options])
@@ -66,8 +66,10 @@ else
 	AC_MSG_RESULT([no])
 fi
 
+AC_CHECK_HEADERS(fnmatch.h limits.h sys/time.h sys/select.h sys/param.h)
+AC_HEADER_DIRENT
 AC_HEADER_MAJOR
-AC_CHECK_HEADERS(dirent.h fnmatch.h limits.h time.h sys/time.h sys/select.h sys/param.h)
+AC_HEADER_TIME
 
 AC_CHECK_FUNCS(fdopendir fnmatch gettimeofday \
 		getdtablesize nanosleep select GetSystemTimeAsFileTime)
diff --git a/extension/filefuncs.c b/extension/filefuncs.c
index 61cadfec..d5249a4e 100644
--- a/extension/filefuncs.c
+++ b/extension/filefuncs.c
@@ -9,7 +9,7 @@
  */
 
 /*
- * Copyright (C) 2001, 2004, 2005, 2010, 2011, 2012, 2013
+ * Copyright (C) 2001, 2004, 2005, 2010, 2011, 2012, 2013, 2014
  * the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
@@ -36,6 +36,34 @@
 
 #define _BSD_SOURCE
 
+#ifdef __VMS
+#if (__CRTL_VER >= 70200000) && !defined (__VAX)
+#define _LARGEFILE 1
+#endif
+
+#ifndef __VAX
+#ifdef __CRTL_VER
+#if __CRTL_VER >= 80200000
+#define _USE_STD_STAT 1
+#endif
+#endif
+#endif
+#define _POSIX_C_SOURCE 1
+#define _XOPEN_SOURCE 1
+#include <stat.h>
+#ifndef S_ISVTX
+#define S_ISVTX (0)
+#endif
+#ifndef major
+#define major(s) (s)
+#endif
+#ifndef minor
+#define minor(s) (0)
+#endif
+#include <unixlib.h>
+#endif
+
+
 #include <stdio.h>
 #include <assert.h>
 #include <errno.h>
@@ -256,7 +284,7 @@ read_symlink(const char *fname, size_t bufsize, ssize_t *linksize)
 			   returns -1 with errno == ERANGE if the buffer is
 			   too small.  */
 			if (errno != ERANGE) {
-				free(buf);
+				gawk_free(buf);
 				return NULL;
 			}
 		}
@@ -265,7 +293,7 @@ read_symlink(const char *fname, size_t bufsize, ssize_t *linksize)
 			buf[*linksize] = '\0';
 			return buf;
 		}
-		free(buf);
+		gawk_free(buf);
 		if (bufsize <= MAXSIZE/2)
 			bufsize *= 2;
 		else if (bufsize < MAXSIZE)
@@ -826,7 +854,7 @@ do_fts(int nargs, awk_value_t *result)
 
 out:
 	if (pathvector != NULL)
-		free(pathvector);
+		gawk_free(pathvector);
 	if (path_array != NULL)
 		(void) release_flattened_array(pathlist.array_cookie, path_array);
 
diff --git a/extension/fnmatch.c b/extension/fnmatch.c
index a67bc25f..a85bcc78 100644
--- a/extension/fnmatch.c
+++ b/extension/fnmatch.c
@@ -45,15 +45,29 @@
 #define _(msgid)  gettext(msgid)
 #define N_(msgid) msgid
 
+#ifdef __VMS
+#define __iswctype iswctype
+#define __btowc btowc
+#endif
+
 #define _GNU_SOURCE	1	/* use GNU extensions if they're there */
 #ifdef HAVE_FNMATCH_H
 #include <fnmatch.h>
 #else
+#ifdef __VMS
+#include "fnmatch.h"	/* version that comes with gawk */
+#else
 #include "../missing_d/fnmatch.h"	/* version that comes with gawk */
 #endif
+#define HAVE_FNMATCH_H
+#endif
 
 #ifndef HAVE_FNMATCH
+#ifdef __VMS
+#include "fnmatch.c"	/* ditto */
+#else
 #include "../missing_d/fnmatch.c"	/* ditto */
+#endif
 #define HAVE_FNMATCH
 #endif
 
diff --git a/extension/gawkdirfd.h b/extension/gawkdirfd.h
index a3a2b6a6..d1edf65f 100644
--- a/extension/gawkdirfd.h
+++ b/extension/gawkdirfd.h
@@ -35,7 +35,11 @@
  * Unlike the main gawk code base, this include is NOT dependant
  * upon MinGW or EMX.
  */
+#ifndef __VMS
 #include "../nonposix.h"
+#else
+#include "nonposix.h"
+#endif
 
 #ifndef DIR_TO_FD
 # define DIR_TO_FD(d) (FAKE_FD_VALUE)
diff --git a/extension/gawkfts.c b/extension/gawkfts.c
index 81803b88..4a712153 100644
--- a/extension/gawkfts.c
+++ b/extension/gawkfts.c
@@ -43,11 +43,11 @@ static char sccsid[] = "@(#)fts.c	8.6 (Berkeley) 8/14/94";
 
 #include <limits.h>
 /* #include "namespace.h" */
-#ifndef ZOS_USS
+#ifdef HAVE_SYS_PARAM_H
 #include <sys/param.h>
 #else
 #include <stdio.h>
-#endif /* ZOS_USS */
+#endif
 #include <sys/stat.h>
 
 #include <assert.h>
@@ -139,6 +139,10 @@ static int	 fts_safe_changedir(const FTS *, const FTSENT *, int,
 
 #define _DIAGASSERT(expression)
 
+#ifndef MAXPATHLEN
+#define MAXPATHLEN	1024	/* a guess */
+#endif
+
 FTS *
 fts_open(char * const *argv, int options,
     int (*compar)(const FTSENT **, const FTSENT **))
diff --git a/extension/inplace.c b/extension/inplace.c
index 91b1a229..e2f8b73f 100644
--- a/extension/inplace.c
+++ b/extension/inplace.c
@@ -3,7 +3,7 @@
  */
 
 /*
- * Copyright (C) 2013 the Free Software Foundation, Inc.
+ * Copyright (C) 2013, 2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -96,7 +96,7 @@ at_exit(void *data, int exit_status)
 	(void) exit_status;	/* silence warnings */
 	if (state.tname) {
 		unlink(state.tname);
-		free(state.tname);
+		gawk_free(state.tname);
 		state.tname = NULL;
 	}
 }
@@ -242,7 +242,7 @@ do_inplace_end(int nargs, awk_value_t *result)
 		if (link(filename.str_value.str, bakname) < 0)
 			fatal(ext_id, _("inplace_end: link(`%s', `%s') failed (%s)"),
 				filename.str_value.str, bakname, strerror(errno));
-		free(bakname);
+		gawk_free(bakname);
 	}
 
 #ifdef __MINGW32__
@@ -252,7 +252,7 @@ do_inplace_end(int nargs, awk_value_t *result)
 	if (rename(state.tname, filename.str_value.str) < 0)
 		fatal(ext_id, _("inplace_end: rename(`%s', `%s') failed (%s)"),
 			state.tname, filename.str_value.str, strerror(errno));
-	free(state.tname);
+	gawk_free(state.tname);
 	state.tname = NULL;
 	return make_number(0, result);
 }
diff --git a/extension/m4/ChangeLog b/extension/m4/ChangeLog
index 821ef9ed..349bbcc8 100644
--- a/extension/m4/ChangeLog
+++ b/extension/m4/ChangeLog
@@ -1,3 +1,7 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
 2013-12-21         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* libtool.m4, ltoptions.m4, ltversion.m4: Update to
diff --git a/extension/readdir.c b/extension/readdir.c
index 91296801..7bcabcb0 100644
--- a/extension/readdir.c
+++ b/extension/readdir.c
@@ -10,7 +10,7 @@
  */
 
 /*
- * Copyright (C) 2012, 2013 the Free Software Foundation, Inc.
+ * Copyright (C) 2012-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -67,6 +67,10 @@
 #define _(msgid)  gettext(msgid)
 #define N_(msgid) msgid
 
+#ifndef PATH_MAX
+#define PATH_MAX	1024	/* a good guess */
+#endif
+
 static const gawk_api_t *api;	/* for convenience macros to work */
 static awk_ext_id_t *ext_id;
 static const char *ext_version = "readdir extension: version 1.0";
@@ -235,8 +239,8 @@ dir_close(awk_input_buf_t *iobuf)
 	the_dir = (open_directory_t *) iobuf->opaque;
 
 	closedir(the_dir->dp);
-	free(the_dir->buf);
-	free(the_dir);
+	gawk_free(the_dir->buf);
+	gawk_free(the_dir);
 
 	iobuf->fd = -1;
 }
diff --git a/extension/readfile.3am b/extension/readfile.3am
index 688d9cd5..0cb2eb5b 100644
--- a/extension/readfile.3am
+++ b/extension/readfile.3am
@@ -1,4 +1,4 @@
-.TH READFILE 3am "Jan 15 2013" "Free Software Foundation" "GNU Awk Extension Modules"
+.TH READFILE 3am "Mar 24 2013" "Free Software Foundation" "GNU Awk Extension Modules"
 .SH NAME
 readfile \- return the entire contents of a file as a string
 .SH SYNOPSIS
@@ -6,6 +6,14 @@ readfile \- return the entire contents of a file as a string
 @load "readfile"
 .sp
 result = readfile("/some/path")
+.sp
+.ft R
+For making whole files be single records:
+.sp
+.ft CW
+@load "readfile"
+.br
+BEGIN { PROCINFO["readfile"] = 1 }
 .ft R
 .SH DESCRIPTION
 The
@@ -18,6 +26,14 @@ the requested file.
 .PP
 Upon error, the function returns the empty string and sets
 .BR ERRNO .
+.PP
+In addition, it adds an input parser that is activated if
+.ft CW
+PROCINFO["readfile"]
+.ft R
+exists.
+When activated, each input file is returned in its entirety as \f(CW$0\fR.
+\f(CWRT\fP is set to the null string.
 ... .SH NOTES
 ... .SH BUGS
 .SH EXAMPLE
@@ -47,7 +63,7 @@ if (contents == "" && ERRNO != "") {
 Arnold Robbins,
 .BR arnold@skeeve.com .
 .SH COPYING PERMISSIONS
-Copyright \(co 2012, 2013,
+Copyright \(co 2012, 2013, 2014,
 Free Software Foundation, Inc.
 .PP
 Permission is granted to make and distribute verbatim copies of
diff --git a/extension/readfile.c b/extension/readfile.c
index 06889c3d..d4b4aef9 100644
--- a/extension/readfile.c
+++ b/extension/readfile.c
@@ -8,10 +8,11 @@
  * Revised for new dynamic function facilities
  * Mon Jun 14 14:53:07 IDT 2004
  * Revised for formal API May 2012
+ * Added input parser March 2014
  */
 
 /*
- * Copyright (C) 2002, 2003, 2004, 2011, 2012, 2013
+ * Copyright (C) 2002, 2003, 2004, 2011, 2012, 2013, 2014
  * the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
@@ -61,11 +62,39 @@
 
 static const gawk_api_t *api;	/* for convenience macros to work */
 static awk_ext_id_t *ext_id;
-static const char *ext_version = "readfile extension: version 1.0";
-static awk_bool_t (*init_func)(void) = NULL;
+static const char *ext_version = "readfile extension: version 2.0";
+static awk_bool_t init_readfile();
+static awk_bool_t (*init_func)(void) = init_readfile;
 
 int plugin_is_GPL_compatible;
 
+/* read_file_to_buffer --- handle the mechanics of reading the file */
+
+static char *
+read_file_to_buffer(int fd, const struct stat *sbuf)
+{
+	char *text = NULL;
+	int ret;
+
+	if ((sbuf->st_mode & S_IFMT) != S_IFREG) {
+		errno = EINVAL;
+		update_ERRNO_int(errno);
+		goto done;
+	}
+
+	emalloc(text, char *, sbuf->st_size + 2, "do_readfile");
+	memset(text, '\0', sbuf->st_size + 2);
+
+	if ((ret = read(fd, text, sbuf->st_size)) != sbuf->st_size) {
+		update_ERRNO_int(errno);
+		gawk_free(text);
+		text = NULL;
+		/* fall through to return */
+	}
+done:
+	return text;
+}
+
 /* do_readfile --- read a file into memory */
 
 static awk_value_t *
@@ -90,10 +119,6 @@ do_readfile(int nargs, awk_value_t *result)
 		if (ret < 0) {
 			update_ERRNO_int(errno);
 			goto done;
-		} else if ((sbuf.st_mode & S_IFMT) != S_IFREG) {
-			errno = EINVAL;
-			update_ERRNO_int(errno);
-			goto done;
 		}
 
 		if ((fd = open(filename.str_value.str, O_RDONLY|O_BINARY)) < 0) {
@@ -101,15 +126,9 @@ do_readfile(int nargs, awk_value_t *result)
 			goto done;
 		}
 
-		emalloc(text, char *, sbuf.st_size + 2, "do_readfile");
-		memset(text, '\0', sbuf.st_size + 2);
-
-		if ((ret = read(fd, text, sbuf.st_size)) != sbuf.st_size) {
-			(void) close(fd);
-			update_ERRNO_int(errno);
-			free(text);
-			goto done;
-		}
+		text = read_file_to_buffer(fd, & sbuf);
+		if (text == NULL)
+			goto done;	/* ERRNO already updated */
 
 		close(fd);
 		make_malloced_string(text, sbuf.st_size, result);
@@ -117,12 +136,110 @@ do_readfile(int nargs, awk_value_t *result)
 	} else if (do_lint)
 		lintwarn(ext_id, _("readfile: called with no arguments"));
 
-
 done:
 	/* Set the return value */
 	return result;
 }
 
+/* readfile_get_record --- read the whole file as one record */
+
+static int
+readfile_get_record(char **out, awk_input_buf_t *iobuf, int *errcode,
+			char **rt_start, size_t *rt_len)
+{
+	char *text;
+
+	/*
+	 * The caller sets *errcode to 0, so we should set it only if an
+	 * error occurs.
+	 */
+
+	if (out == NULL || iobuf == NULL)
+		return EOF;
+
+	if (iobuf->opaque != NULL) {
+		/*
+		 * Already read the whole file,
+		 * free up stuff and return EOF
+		 */
+		gawk_free(iobuf->opaque);
+		iobuf->opaque = NULL;
+		return EOF;
+	}
+
+	/* read file */
+	text = read_file_to_buffer(iobuf->fd, & iobuf->sbuf);
+	if (text == NULL)
+		return EOF;
+
+	/* set up the iobuf for next time */
+	iobuf->opaque = text;
+
+	/* set return values */
+	*rt_start = NULL;
+	*rt_len = 0;
+	*out = text;
+
+	/* return count */
+	return iobuf->sbuf.st_size;
+}
+
+/* readfile_can_take_file --- return true if we want the file */
+
+static awk_bool_t
+readfile_can_take_file(const awk_input_buf_t *iobuf)
+{
+	awk_value_t array, index, value;
+
+	if (iobuf == NULL)
+		return awk_false;
+
+	/*
+	 * This could fail if PROCINFO isn't referenced from
+	 * the awk program. It's not a "can't happen" error.
+	 */
+	if (! sym_lookup("PROCINFO", AWK_ARRAY, & array)) {
+		return awk_false;
+	}
+
+	(void) make_const_string("readfile", 8, & index);
+
+	if (! get_array_element(array.array_cookie, & index, AWK_UNDEFINED, & value)) {
+		return awk_false;
+	}
+
+	return awk_true;
+}
+
+/* readfile_take_control_of --- take over the file */
+
+static awk_bool_t
+readfile_take_control_of(awk_input_buf_t *iobuf)
+{
+	if (iobuf == NULL)
+		return awk_false;
+
+	iobuf->get_record = readfile_get_record;
+	return awk_true;
+}
+
+static awk_input_parser_t readfile_parser = {
+	"readfile",
+	readfile_can_take_file,
+	readfile_take_control_of,
+	NULL
+};
+
+/* init_readfile --- set things up */
+
+static awk_bool_t
+init_readfile()
+{
+	register_input_parser(& readfile_parser);
+
+	return awk_true;
+}
+
 static awk_ext_func_t func_table[] = {
 	{ "readfile", do_readfile, 1 },
 };
diff --git a/extension/revtwoway.c b/extension/revtwoway.c
index 5f490825..c0d9381a 100644
--- a/extension/revtwoway.c
+++ b/extension/revtwoway.c
@@ -7,7 +7,7 @@
  */
 
 /*
- * Copyright (C) 2012, 2013 the Free Software Foundation, Inc.
+ * Copyright (C) 2012-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -119,8 +119,8 @@ close_two_proc_data(two_way_proc_data_t *proc_data)
 		return;
 	}
 
-	free(proc_data->data);
-	free(proc_data);
+	gawk_free(proc_data->data);
+	gawk_free(proc_data);
 }
 
 /*
diff --git a/extension/rwarray.c b/extension/rwarray.c
index 6185000b..aa05a0d5 100644
--- a/extension/rwarray.c
+++ b/extension/rwarray.c
@@ -7,7 +7,7 @@
  */
 
 /*
- * Copyright (C) 2009, 2010, 2011, 2012, 2013 the Free Software Foundation, Inc.
+ * Copyright (C) 2009-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -408,7 +408,7 @@ read_elem(FILE *fp, awk_element_t *element)
 			buflen = index_len;
 		} else if (buflen < index_len) {
 			/* reallocate buffer */
-			char *cp = realloc(buffer, index_len);
+			char *cp = gawk_realloc(buffer, index_len);
 
 			if (cp == NULL)
 				return awk_false;
@@ -468,11 +468,11 @@ read_value(FILE *fp, awk_value_t *value)
 		len = ntohl(len);
 		value->val_type = AWK_STRING;
 		value->str_value.len = len;
-		value->str_value.str = malloc(len + 2);
+		value->str_value.str = gawk_malloc(len + 2);
 		memset(value->str_value.str, '\0', len + 2);
 
 		if (fread(value->str_value.str, 1, len, fp) != (ssize_t) len) {
-			free(value->str_value.str);
+			gawk_free(value->str_value.str);
 			return awk_false;
 		}
 	}
diff --git a/extension/testext.c b/extension/testext.c
index d11272b8..2dda339f 100644
--- a/extension/testext.c
+++ b/extension/testext.c
@@ -3,7 +3,7 @@
  */
 
 /*
- * Copyright (C) 2012, 2013
+ * Copyright (C) 2012, 2013, 2014
  * the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
@@ -237,8 +237,8 @@ try_modify_environ(int nargs, awk_value_t *result)
 		printf("try_modify_environ: set_array_element of ENVIRON passed\n");
 	} else {
 		printf("try_modify_environ: set_array_element of ENVIRON failed\n");
-		free(index.str_value.str);
-		free(value.str_value.str);
+		gawk_free(index.str_value.str);
+		gawk_free(value.str_value.str);
 	}
 
 	if (! flatten_array(environ_array, & flat_array)) {
diff --git a/extension/time.c b/extension/time.c
index 9fadfe54..e6b2b39f 100644
--- a/extension/time.c
+++ b/extension/time.c
@@ -1,25 +1,24 @@
 /*
  * time.c - Builtin functions that provide time-related functions.
- *
  */
 
 /*
- * Copyright (C) 2012, 2013
+ * Copyright (C) 2012, 2013, 2014
  * the Free Software Foundation, Inc.
- * 
+ *
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
- * 
+ *
  * GAWK is free software; you can redistribute it and/or modify
  * it under the terms of the GNU General Public License as published by
  * the Free Software Foundation; either version 3 of the License, or
  * (at your option) any later version.
- * 
+ *
  * GAWK is distributed in the hope that it will be useful,
  * but WITHOUT ANY WARRANTY; without even the implied warranty of
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  * GNU General Public License for more details.
- * 
+ *
  * You should have received a copy of the GNU General Public License
  * along with this program; if not, write to the Free Software
  * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
@@ -39,6 +38,40 @@
 #include <sys/types.h>
 #include <sys/stat.h>
 
+#ifdef __VMS
+#define HAVE_NANOSLEEP
+#define HAVE_GETTIMEOFDAY
+#ifdef gettimeofday
+#undef gettimeofday
+#endif
+#ifdef __ia64__
+/* nanosleep not working correctly on IA64 */
+static int
+vms_fake_nanosleep(struct timespec *rqdly, struct timespec *rmdly)
+{
+	int result;
+	struct timespec mtime1, mtime2;
+
+	result = nanosleep(rqdly, &mtime1);
+	if (result == 0)
+		return 0;
+
+	/* On IA64 it returns 100 nanoseconds early with an error */
+	if ((mtime1.tv_sec == 0) && (mtime1.tv_nsec <= 100)) {
+		mtime1.tv_nsec += 100;
+		result = nanosleep(&mtime1, &mtime2);
+		if (result == 0)
+			return 0;
+		if ((mtime2.tv_sec == 0) && (mtime2.tv_nsec <= 100)) {
+			return 0;
+		}
+	}
+	return result;
+}
+#define nanosleep(x,y) vms_fake_nanosleep(x, y)
+#endif
+#endif
+
 #include "gawkapi.h"
 
 #include "gettext.h"
@@ -52,15 +85,13 @@ static awk_bool_t (*init_func)(void) = NULL;
 
 int plugin_is_GPL_compatible;
 
+#include <time.h>
 #if defined(HAVE_GETTIMEOFDAY) && defined(HAVE_SYS_TIME_H)
 #include <sys/time.h>
 #endif
 #if defined(HAVE_SELECT) && defined(HAVE_SYS_SELECT_H)
 #include <sys/select.h>
 #endif
-#if defined(HAVE_NANOSLEEP) && defined(HAVE_TIME_H)
-#include <time.h>
-#endif
 #if defined(HAVE_GETSYSTEMTIMEASFILETIME)
 #define WIN32_LEAN_AND_MEAN
 #include <windows.h>
diff --git a/field.c b/field.c
index 0a7cee8f..64ee1f02 100644
--- a/field.c
+++ b/field.c
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -1013,7 +1013,9 @@ do_split(int nargs)
 		return make_number((AWKNUM) 0);
 	}
 
-	if ((sep->re_flags & FS_DFLT) != 0 && current_field_sep() != Using_FIELDWIDTHS && ! RS_is_null) {
+	if (   (sep->re_flags & FS_DFLT) != 0
+	    && current_field_sep() == Using_FS
+	    && ! RS_is_null) {
 		parseit = parse_field;
 		fs = force_string(FS_node->var_value);
 		rp = FS_regexp;
diff --git a/gawkapi.c b/gawkapi.c
index 9936d530..bcf8d90a 100644
--- a/gawkapi.c
+++ b/gawkapi.c
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 2012, 2013 the Free Software Foundation, Inc.
+ * Copyright (C) 2012-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -43,7 +43,7 @@ api_get_argument(awk_ext_id_t id, size_t count,
 	NODE *arg;
 
 	if (result == NULL)
-		return false;
+		return awk_false;
 
 	(void) id;
 
@@ -59,7 +59,7 @@ api_get_argument(awk_ext_id_t id, size_t count,
 	 */
 	arg = get_argument(count);
 	if (arg == NULL)
-		return false;
+		return awk_false;
 
 	/* if type is undefined */
 	if (arg->type == Node_var_new) {
@@ -84,7 +84,7 @@ array:
 	/* get the array here */
 	arg = get_array_argument(count, false);
 	if (arg == NULL)
-		return false;
+		return awk_false;
 
 	return node_to_awk_value(arg, result, wanted);
 
@@ -92,11 +92,11 @@ scalar:
 	/* at this point we have a real type that is not an array */
 	arg = get_scalar_argument(count, false);
 	if (arg == NULL)
-		return false;
+		return awk_false;
 
 	return node_to_awk_value(arg, result, wanted);
 #else
-	return false;
+	return awk_false;
 #endif
 }
 
@@ -114,23 +114,23 @@ api_set_argument(awk_ext_id_t id,
 	(void) id;
 
 	if (array == NULL || array->type != Node_var_array)
-		return false;
+		return awk_false;
 
 	if (   (arg = get_argument(count)) == NULL
 	    || arg->type != Node_var_new)
-		return false;
+		return awk_false;
 
 	arg = get_array_argument(count, false);
 	if (arg == NULL)
-		return false;
+		return awk_false;
 
 	array->vname = arg->vname;
 	*arg = *array;
 	freenode(array);
 
-	return true;
+	return awk_true;
 #else
-	return false;
+	return awk_false;
 #endif
 }
 
@@ -314,12 +314,12 @@ api_add_ext_func(awk_ext_id_t id,
 	(void) namespace;
 
 	if (func == NULL)
-		return false;
+		return awk_false;
 
 #ifdef DYNAMIC
 	return make_builtin(func);
 #else
-	return false;
+	return awk_false;
 #endif
 }
 
@@ -378,7 +378,7 @@ api_awk_atexit(awk_ext_id_t id,
 static awk_bool_t
 node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 {
-	awk_bool_t ret = false;
+	awk_bool_t ret = awk_false;
 
 	if (node == NULL)
 		fatal(_("node_to_awk_value: received null node"));
@@ -390,7 +390,7 @@ node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 	case Node_var_new:	/* undefined variable */
 		val->val_type = AWK_UNDEFINED;
 		if (wanted == AWK_UNDEFINED) {
-			ret = true;
+			ret = awk_true;
 		}
 		break;
 
@@ -399,7 +399,7 @@ node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 		if (wanted == AWK_SCALAR) {
 			val->val_type = AWK_SCALAR;
 			val->scalar_cookie = (void *) node;
-			ret = true;
+			ret = awk_true;
 			break;
 		}
 
@@ -414,7 +414,7 @@ node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 			(void) force_number(node);
 			if ((node->flags & NUMCUR) != 0) {
 				val->num_value = get_number_d(node);
-				ret = true;
+				ret = awk_true;
 			}
 			break;
 
@@ -425,7 +425,7 @@ node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 			if ((node->flags & STRCUR) != 0) {
 				val->str_value.str = node->stptr;
 				val->str_value.len = node->stlen;
-				ret = true;
+				ret = awk_true;
 			}
 			break;
 
@@ -436,7 +436,7 @@ node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 				val->val_type = AWK_STRING;
 			} else
 				val->val_type = AWK_UNDEFINED;
-			ret = false;
+			ret = awk_false;
 			break;
 
 		case AWK_UNDEFINED:
@@ -444,12 +444,12 @@ node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 			if ((node->flags & NUMBER) != 0) {
 				val->val_type = AWK_NUMBER;
 				val->num_value = get_number_d(node);
-				ret = true;
+				ret = awk_true;
 			} else if ((node->flags & STRING) != 0) {
 				val->val_type = AWK_STRING;
 				val->str_value.str = node->stptr;
 				val->str_value.len = node->stlen;
-				ret = true;
+				ret = awk_true;
 			} else
 				val->val_type = AWK_UNDEFINED;
 			break;
@@ -464,15 +464,14 @@ node_to_awk_value(NODE *node, awk_value_t *val, awk_valtype_t wanted)
 		val->val_type = AWK_ARRAY;
 		if (wanted == AWK_ARRAY || wanted == AWK_UNDEFINED) {
 			val->array_cookie = node;
-			ret = true;
-		} else {
-			ret = false;
-		}
+			ret = awk_true;
+		} else
+			ret = awk_false;
 		break;
 
 	default:
 		val->val_type = AWK_UNDEFINED;
-		ret = false;
+		ret = awk_false;
 		break;
 	}
 
@@ -510,7 +509,7 @@ api_sym_lookup(awk_ext_id_t id,
 	    || *name == '\0'
 	    || result == NULL
 	    || (node = lookup(name)) == NULL)
-		return false;
+		return awk_false;
 
 	if (is_off_limits_var(name))	/* a built-in variable */
 		node->flags |= NO_EXT_SET;
@@ -531,7 +530,7 @@ api_sym_lookup_scalar(awk_ext_id_t id,
 	if (node == NULL
 	    || result == NULL
 	    || node->type != Node_var)
-		return false;
+		return awk_false;
 
 	update_global_values();	/* make sure stuff like NF, NR, are up to date */
 
@@ -551,7 +550,7 @@ api_sym_update(awk_ext_id_t id,
 	if (   name == NULL
 	    || *name == '\0'
 	    || value == NULL)
-		return false;
+		return awk_false;
 
 	switch (value->val_type) {
 	case AWK_NUMBER:
@@ -564,7 +563,7 @@ api_sym_update(awk_ext_id_t id,
 
 	default:
 		/* fatal(_("api_sym_update: invalid value for type of new value (%d)"), value->val_type); */
-		return false;
+		return awk_false;
 	}
 
 	node = lookup(name);
@@ -586,7 +585,7 @@ api_sym_update(awk_ext_id_t id,
 			node->var_value = awk_value_to_node(value);
 		}
 
-		return true;
+		return awk_true;
 	}
 
 	/*
@@ -596,7 +595,7 @@ api_sym_update(awk_ext_id_t id,
 	if (   (node->flags & NO_EXT_SET) != 0
 	    || is_off_limits_var(name)) {	/* most built-in vars not allowed */
 		node->flags |= NO_EXT_SET;
-		return false;
+		return awk_false;
 	}
 
 	if (    value->val_type != AWK_ARRAY
@@ -606,10 +605,10 @@ api_sym_update(awk_ext_id_t id,
 		if (node->type == Node_var_new && value->val_type != AWK_UNDEFINED)
 			node->type = Node_var;
 
-		return true;
+		return awk_true;
 	}
 
-	return false;
+	return awk_false;
 }
 
 /* api_sym_update_scalar --- update a scalar cookie */
@@ -625,7 +624,7 @@ api_sym_update_scalar(awk_ext_id_t id,
 	    || node == NULL
 	    || node->type != Node_var
 	    || (node->flags & NO_EXT_SET) != 0)
-		return false;
+		return awk_false;
 
 	/*
 	 * Optimization: if valref is 1, and the new value is a string or
@@ -650,7 +649,7 @@ api_sym_update_scalar(awk_ext_id_t id,
 			r->flags = MALLOC|NUMBER|NUMCUR;
 			r->stptr = NULL;
 			r->stlen = 0;
-			return true;
+			return awk_true;
 		}
 		break;
 	case AWK_STRING:
@@ -670,7 +669,7 @@ api_sym_update_scalar(awk_ext_id_t id,
 			r->stfmt = -1;
 			r->stptr = value->str_value.str;
 			r->stlen = value->str_value.len;
-			return true;
+			return awk_true;
 		}
 		break;
 	case AWK_UNDEFINED:
@@ -679,13 +678,13 @@ api_sym_update_scalar(awk_ext_id_t id,
 		break;
 
 	default:	/* AWK_ARRAY or invalid type */
-		return false;
+		return awk_false;
 	}
 
 	/* do it the hard (slow) way */
 	unref(node->var_value);
 	node->var_value = awk_value_to_node(value);
-	return true;
+	return awk_true;
 }
 
 /*
@@ -694,7 +693,7 @@ api_sym_update_scalar(awk_ext_id_t id,
  * Any scalar value is fine, so only AWK_ARRAY (or an invalid type) is illegal.
  */
 
-static inline int
+static inline bool
 valid_subscript_type(awk_valtype_t valtype)
 {
 	switch (valtype) {
@@ -733,21 +732,21 @@ api_get_array_element(awk_ext_id_t id,
 	    || result == NULL
 	    || index == NULL
 	    || ! valid_subscript_type(index->val_type))
-		return false;
+		return awk_false;
 
 	subscript = awk_value_to_node(index);
 
 	/* if it doesn't exist, return false */
 	if (in_array(array, subscript) == NULL) {
 		unref(subscript);
-		return false;
+		return awk_false;
 	}
 
 	aptr = assoc_lookup(array, subscript);
 
 	if (aptr == NULL) {	/* can't happen */
 		unref(subscript);
-		return false;
+		return awk_false;
 	}
 
 	unref(subscript);
@@ -777,7 +776,7 @@ api_set_array_element(awk_ext_id_t id, awk_array_t a_cookie,
 	    || index == NULL
 	    || value == NULL
 	    || ! valid_subscript_type(index->val_type))
-		return false;
+		return awk_false;
 
 	tmp = awk_value_to_node(index);
 	aptr = assoc_lookup(array, tmp);
@@ -791,7 +790,7 @@ api_set_array_element(awk_ext_id_t id, awk_array_t a_cookie,
 		make_aname(elem);
 	}
 
-	return true;
+	return awk_true;
 }
 
 /*
@@ -843,13 +842,13 @@ api_del_array_element(awk_ext_id_t id,
 	    || (array->flags & NO_EXT_SET) != 0
 	    || index == NULL
 	    || ! valid_subscript_type(index->val_type))
-		return false;
+		return awk_false;
 
 	sub = awk_value_to_node(index);
 	remove_element(array, sub);
 	unref(sub);
 
-	return true;
+	return awk_true;
 }
 
 /*
@@ -864,10 +863,10 @@ api_get_element_count(awk_ext_id_t id,
 	NODE *node = (NODE *) a_cookie;
 
 	if (count == NULL || node == NULL || node->type != Node_var_array)
-		return false;
+		return awk_false;
 
 	*count = node->table_size;
-	return true;
+	return awk_true;
 }
 
 /* api_create_array --- create a new array cookie to which elements may be added */
@@ -894,10 +893,10 @@ api_clear_array(awk_ext_id_t id, awk_array_t a_cookie)
 	if (   node == NULL
 	    || node->type != Node_var_array
 	    || (node->flags & NO_EXT_SET) != 0)
-		return false;
+		return awk_false;
 
 	assoc_clear(node);
-	return true;
+	return awk_true;
 }
 
 /* api_flatten_array --- flatten out an array so that it can be looped over easily. */
@@ -916,7 +915,7 @@ api_flatten_array(awk_ext_id_t id,
 	    || array->type != Node_var_array
 	    || array->table_size == 0
 	    || data == NULL)
-		return false;
+		return awk_false;
 
 	alloc_size = sizeof(awk_flat_array_t) +
 			(array->table_size - 1) * sizeof(awk_element_t);
@@ -954,7 +953,7 @@ api_flatten_array(awk_ext_id_t id,
 						(int) i);
 		}
 	}
-	return true;
+	return awk_true;
 }
 
 /*
@@ -978,7 +977,7 @@ api_release_flattened_array(awk_ext_id_t id,
 	    || array != (NODE *) data->opaque1
 	    || data->count != array->table_size
 	    || data->opaque2 == NULL)
-		return false;
+		return awk_false;
 
 	list = (NODE **) data->opaque2;
 
@@ -995,7 +994,7 @@ api_release_flattened_array(awk_ext_id_t id,
 	efree(list);
 	efree(data);
 
-	return true;
+	return awk_true;
 }
 
 /* api_create_value --- create a cached value */
@@ -1005,7 +1004,7 @@ api_create_value(awk_ext_id_t id, awk_value_t *value,
 		awk_value_cookie_t *result)
 {
 	if (value == NULL || result == NULL)
-		return false;
+		return awk_false;
 
 	switch (value->val_type) {
 	case AWK_NUMBER:
@@ -1013,10 +1012,10 @@ api_create_value(awk_ext_id_t id, awk_value_t *value,
 		break;
 	default:
 		/* reject anything other than a simple scalar */
-		return false;
+		return awk_false;
 	}
 
-	return (*result = awk_value_to_node(value)) != NULL;
+	return (awk_bool_t) ((*result = awk_value_to_node(value)) != NULL);
 }
 
 /* api_release_value --- release a cached value */
@@ -1027,10 +1026,10 @@ api_release_value(awk_ext_id_t id, awk_value_cookie_t value)
 	NODE *val = (NODE *) value;
 
 	if (val == NULL)
-		return false;
+		return awk_false;
 
 	unref(val);
-	return true;
+	return awk_true;
 }
 
 /*
@@ -1112,6 +1111,12 @@ gawk_api_t api_impl = {
 	api_clear_array,
 	api_flatten_array,
 	api_release_flattened_array,
+
+	/* Memory allocation */
+	malloc,
+	calloc,
+	realloc,
+	free,
 };
 
 /* init_ext_api --- init the extension API */
diff --git a/gawkapi.h b/gawkapi.h
index b26ee24c..5ccadc21 100644
--- a/gawkapi.h
+++ b/gawkapi.h
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 2012, 2013 the Free Software Foundation, Inc.
+ * Copyright (C) 2012-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -30,7 +30,6 @@
  *
  * FILE			- <stdio.h>
  * NULL			- <stddef.h>
- * malloc()		- <stdlib.h>
  * memset(), memcpy()	- <string.h>
  * size_t		- <sys/types.h>
  * struct stat		- <sys/stat.h>
@@ -62,7 +61,7 @@
  *
  * Additional important information:
  *
- * 1. ALL string values in awk_value_t objects need to come from malloc().
+ * 1. ALL string values in awk_value_t objects need to come from api_malloc().
  * Gawk will handle releasing the storage if necessary.  This is slightly
  * awkward, in that you can't take an awk_value_t that you got from gawk
  * and reuse it directly, even for something that is conceptually pass
@@ -264,7 +263,7 @@ typedef struct awk_two_way_processor {
 /* Current version of the API. */
 enum {
 	GAWK_API_MAJOR_VERSION = 1,
-	GAWK_API_MINOR_VERSION = 0
+	GAWK_API_MINOR_VERSION = 1
 };
 
 /* A number of typedefs related to different types of values. */
@@ -665,6 +664,16 @@ typedef struct gawk_api {
 	awk_bool_t (*api_release_flattened_array)(awk_ext_id_t id,
 			awk_array_t a_cookie,
 			awk_flat_array_t *data);
+
+	/*
+	 * Hooks to provide access to gawk's memory allocation functions.
+	 * This ensures that memory passed between gawk and the extension
+	 * is allocated and released by the same library.
+	 */
+	void *(*api_malloc)(size_t size);
+	void *(*api_calloc)(size_t nmemb, size_t size);
+	void *(*api_realloc)(void *ptr, size_t size);
+	void (*api_free)(void *ptr);
 } gawk_api_t;
 
 #ifndef GAWK	/* these are not for the gawk code itself! */
@@ -736,6 +745,11 @@ typedef struct gawk_api {
 #define release_flattened_array(array, data) \
 	(api->api_release_flattened_array(ext_id, array, data))
 
+#define gawk_malloc(size)		(api->api_malloc(size))
+#define gawk_calloc(nmemb, size)	(api->api_calloc(nmemb, size))
+#define gawk_realloc(ptr, size)		(api->api_realloc(ptr, size))
+#define gawk_free(ptr)			(api->api_free(ptr))
+
 #define create_value(value, result) \
 	(api->api_create_value(ext_id, value,result))
 
@@ -747,13 +761,13 @@ typedef struct gawk_api {
 
 #define emalloc(pointer, type, size, message) \
 	do { \
-		if ((pointer = (type) malloc(size)) == 0) \
+		if ((pointer = (type) gawk_malloc(size)) == 0) \
 			fatal(ext_id, "%s: malloc of %d bytes failed\n", message, size); \
 	} while(0)
 
 #define erealloc(pointer, type, size, message) \
 	do { \
-		if ((pointer = (type) realloc(pointer, size)) == 0) \
+		if ((pointer = (type) gawk_realloc(pointer, size)) == 0) \
 			fatal(ext_id, "%s: realloc of %d bytes failed\n", message, size); \
 	} while(0)
 
diff --git a/getopt.c b/getopt.c
index fa258382..7bd42bb6 100644
--- a/getopt.c
+++ b/getopt.c
@@ -2,7 +2,7 @@
    NOTE: getopt is part of the C library, so if you don't know what
    "Keep this file name-space clean" means, talk to drepper@gnu.org
    before changing it!
-   Copyright (C) 1987-2013 Free Software Foundation, Inc.
+   Copyright (C) 1987-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
 
    The GNU C Library is free software; you can redistribute it and/or
@@ -57,7 +57,7 @@
 
 /* This needs to come after some library #include
    to get __GNU_LIBRARY__ defined.  */
-#if defined (__GNU_LIBRARY__) || defined (__CYGWIN__) || defined(__DJGPP__) || defined(__APPLE__) || defined(__MINGW32__)
+#if defined (__GNU_LIBRARY__) || defined (__CYGWIN__) || defined(__DJGPP__) || defined(__APPLE__) || defined(__MINGW32__) || defined(__sun) /* Illumos */
 /* Don't include stdlib.h for
  * non-GNU C libraries
  * non-Cygwin
diff --git a/getopt.h b/getopt.h
index 5d19cb3d..da1a01ff 100644
--- a/getopt.h
+++ b/getopt.h
@@ -1,5 +1,5 @@
 /* Declarations for getopt.
-   Copyright (C) 1989-2013 Free Software Foundation, Inc.
+   Copyright (C) 1989-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
 
    The GNU C Library is free software; you can redistribute it and/or
diff --git a/getopt1.c b/getopt1.c
index 8be96571..32f2f6a6 100644
--- a/getopt1.c
+++ b/getopt1.c
@@ -1,5 +1,5 @@
 /* getopt_long and getopt_long_only entry points for GNU getopt.
-   Copyright (C) 1987-2013 Free Software Foundation, Inc.
+   Copyright (C) 1987-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
 
    The GNU C Library is free software; you can redistribute it and/or
diff --git a/getopt_int.h b/getopt_int.h
index 92f3871e..d255c8ee 100644
--- a/getopt_int.h
+++ b/getopt_int.h
@@ -1,5 +1,5 @@
 /* Internal declarations for getopt.
-   Copyright (C) 1989-2013 Free Software Foundation, Inc.
+   Copyright (C) 1989-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
 
    The GNU C Library is free software; you can redistribute it and/or
diff --git a/helpers/ChangeLog b/helpers/ChangeLog
index 91d43464..c9121403 100644
--- a/helpers/ChangeLog
+++ b/helpers/ChangeLog
@@ -1,3 +1,20 @@
+2014-06-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* testdfa.c: Minor improvements.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-03-10         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* quoteconvert2.sh: Use .UTF-8 locales per request from
+	Michal Jaegermann.
+
+2014-03-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* quoteconvert2.sh, tryfmt.c, scanfmt.c: New files.
+
 2013-12-21         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* testdfa.c: Fix some bugs and compiler warnings.
diff --git a/helpers/quoteconvert2.sh b/helpers/quoteconvert2.sh
new file mode 100755
index 00000000..63750a37
--- /dev/null
+++ b/helpers/quoteconvert2.sh
@@ -0,0 +1,49 @@
+#!/bin/sh
+
+# quoteconvert2.sh --- test locale dependent output of numbers
+# Michal Jaegermann, michal@harddata.com, 2014/Mar/1
+
+#AWK="../gawk"
+SCRIPT=`basename $0`
+
+if [ "$AWK" = "" ]
+then
+        echo $0: You must set AWK >&2
+        exit 1
+fi
+
+# The last entry on this list represents "a locale with a typo".
+
+llist="
+C
+en_US
+en_US.UTF-8
+de_DE
+de_DE.UTF-8
+fr_FR
+fr_FR.UTF-8
+pt_PT
+pt_PT.UTF-8
+pt_BR
+pt_BR.UTF-8
+ru_RU
+ru_RU.UTF-8
+pl_PX
+"
+
+error=0
+for lc in $llist ; do
+    wanted=`LC_ALL=$lc locale -c LC_NUMERIC 2>/dev/null | \
+	$AWK 'NR == 2 { decimal_point = $0 }
+	      NR == 3 { thousands_sep = $0 }
+	      END  { printf("123%s456%s789%s15\n",
+		       thousands_sep, thousands_sep, decimal_point)}'`
+    got=`LC_ALL=$lc $AWK "BEGIN {printf(\"%'.2f\n\",123456789.15)}"`
+    if [ "$wanted" != "$got" ] ; then
+	echo "$lc - unexpected output $got instead of $wanted"
+	error=1
+    fi
+done
+
+[ "$error" = 0 ] && echo ok || echo bummer
+exit $error
diff --git a/helpers/scanfmt.c b/helpers/scanfmt.c
new file mode 100644
index 00000000..2d7bd73a
--- /dev/null
+++ b/helpers/scanfmt.c
@@ -0,0 +1,22 @@
+/*
+ * Test out ' flag in different locales.
+ * Michal Jaegermann
+ * March, 2014
+ */
+
+#include <stdio.h>
+#include <locale.h>
+#include <stdlib.h>
+int
+main(int argc, char **argv)
+{
+        double t;
+
+        if (argc == 1)
+                return 1;
+
+	setlocale(LC_ALL, getenv("LC_ALL"));
+	sscanf(argv[1], "%lf", &t);
+        printf("%.2f\n", t);
+        return 0;
+}
diff --git a/helpers/testdfa.c b/helpers/testdfa.c
index 813acaab..25a229a2 100644
--- a/helpers/testdfa.c
+++ b/helpers/testdfa.c
@@ -40,14 +40,16 @@
 #include <sys/stat.h>
 
 
+#undef _Noreturn
 #define _Noreturn
+#define _GL_ATTRIBUTE_PURE
 #include "dfa.h"
 
 const char *regexflags2str(int flags);
 char *databuf(int fd);
 const char * reflags2str(int flagval);
 int parse_escape(const char **string_ptr);
-char *setup_pattern(const char *pattern, size_t len);
+char *setup_pattern(const char *pattern, size_t *len);
 char casetable[];
 
 reg_syntax_t syn;
@@ -126,10 +128,10 @@ int main(int argc, char **argv)
 	printf("Ignorecase: %s\nSyntax: %s\n",
 			(ignorecase ? "true" : "false"),
 			reflags2str(syn));
-	printf("Pattern: /%s/\n", pattern);
+	printf("Pattern: /%s/, len = %d\n", pattern, len);
 
-	pattern = setup_pattern(pattern, len);
-	len = strlen(pattern);
+	pattern = setup_pattern(pattern, & len);
+	printf("After setup_pattern(), len = %d\n", len);
 
 	pat.fastmap = (char *) malloc(256);
 	if (pat.fastmap == NULL) {
@@ -191,7 +193,10 @@ int main(int argc, char **argv)
 				&count, &try_backref);
 	data[len] = save;
 
-	printf("dfaexec returned %p (%.3s)\n", place, place);
+	if (place == NULL)
+		printf("dfaexec returned NULL\n");
+	else
+		printf("dfaexec returned %d (%.3s)\n", place - data, place);
 
 	/* release storage */
 	regfree(& pat);
@@ -363,7 +368,7 @@ r_fatal(const char *mesg, ...)
 /* setup_pattern --- do what gawk does with the pattern string */
 
 char *
-setup_pattern(const char *pattern, size_t len)
+setup_pattern(const char *pattern, size_t *len)
 {
 	size_t is_multibyte = 0;
 	int c, c2;
@@ -377,7 +382,7 @@ setup_pattern(const char *pattern, size_t len)
 	memset(& mbs, 0, sizeof(mbs));
 
 	src = pattern;
-	end = pattern + len;
+	end = pattern + *len;
 
 	/* Handle escaped characters first. */
 
@@ -387,19 +392,19 @@ setup_pattern(const char *pattern, size_t len)
 	 * from that. 
 	 */
 	if (buf == NULL) {
-		buf = (char *) malloc(len + 2);
+		buf = (char *) malloc(*len + 2);
 		if (buf == NULL) {
 			fprintf(stderr, "%s: malloc failed\n", __func__);
 			exit(EXIT_FAILURE);
 		}
-		buflen = len;
-	} else if (len > buflen) {
-		buf = (char *) realloc(buf, len + 2);
+		buflen = *len;
+	} else if (*len > buflen) {
+		buf = (char *) realloc(buf, *len + 2);
 		if (buf == NULL) {
 			fprintf(stderr, "%s: realloc failed\n", __func__);
 			exit(EXIT_FAILURE);
 		}
-		buflen = len;
+		buflen = *len;
 	}
 	dest = buf;
 
@@ -487,7 +492,7 @@ setup_pattern(const char *pattern, size_t len)
 	} /* while */
 
 	*dest = '\0';
-	len = dest - buf;
+	*len = dest - buf;
 
 	return buf;
 }
diff --git a/helpers/tryfmt.c b/helpers/tryfmt.c
new file mode 100644
index 00000000..8166d3f1
--- /dev/null
+++ b/helpers/tryfmt.c
@@ -0,0 +1,23 @@
+/*
+ * Test out ' flag in different locales.
+ * Michal Jaegermann
+ * March, 2014
+ */
+
+#include <locale.h>
+#include <stdio.h>
+#include <stdlib.h>
+int
+main(int argc, char **argv)
+{
+	const char *fmt;
+	if (argc == 1)
+		fmt = "%'.2f";
+	else
+		fmt = argv[1];
+
+        setlocale(LC_ALL, getenv("LC_ALL"));
+       	printf(fmt, 12456789.01);
+	printf("\n");
+	return 0;
+}
diff --git a/install-sh b/install-sh
index 377bb868..04367377 100755
--- a/install-sh
+++ b/install-sh
@@ -1,7 +1,7 @@
 #!/bin/sh
 # install - install a program, script, or datafile
 
-scriptversion=2011-11-20.07; # UTC
+scriptversion=2013-10-30.23; # UTC
 
 # This originates from X11R5 (mit/util/scripts/install.sh), which was
 # later released in X11R6 (xc/config/util/install.sh) with the
@@ -41,19 +41,15 @@ scriptversion=2011-11-20.07; # UTC
 # This script is compatible with the BSD install script, but was written
 # from scratch.
 
+tab='	'
 nl='
 '
-IFS=" ""	$nl"
+IFS=" $tab$nl"
 
-# set DOITPROG to echo to test this script
+# Set DOITPROG to "echo" to test this script.
 
-# Don't use :- since 4.3BSD and earlier shells don't like it.
 doit=${DOITPROG-}
-if test -z "$doit"; then
-  doit_exec=exec
-else
-  doit_exec=$doit
-fi
+doit_exec=${doit:-exec}
 
 # Put in absolute file names if you don't have them in your path;
 # or use environment vars.
@@ -68,17 +64,6 @@ mvprog=${MVPROG-mv}
 rmprog=${RMPROG-rm}
 stripprog=${STRIPPROG-strip}
 
-posix_glob='?'
-initialize_posix_glob='
-  test "$posix_glob" != "?" || {
-    if (set -f) 2>/dev/null; then
-      posix_glob=
-    else
-      posix_glob=:
-    fi
-  }
-'
-
 posix_mkdir=
 
 # Desired mode of installed file.
@@ -137,40 +122,39 @@ while test $# -ne 0; do
     -d) dir_arg=true;;
 
     -g) chgrpcmd="$chgrpprog $2"
-	shift;;
+        shift;;
 
     --help) echo "$usage"; exit $?;;
 
     -m) mode=$2
-	case $mode in
-	  *' '* | *'	'* | *'
-'*	  | *'*'* | *'?'* | *'['*)
-	    echo "$0: invalid mode: $mode" >&2
-	    exit 1;;
-	esac
-	shift;;
+        case $mode in
+          *' '* | *"$tab"* | *"$nl"* | *'*'* | *'?'* | *'['*)
+            echo "$0: invalid mode: $mode" >&2
+            exit 1;;
+        esac
+        shift;;
 
     -o) chowncmd="$chownprog $2"
-	shift;;
+        shift;;
 
     -s) stripcmd=$stripprog;;
 
     -t) dst_arg=$2
-	# Protect names problematic for 'test' and other utilities.
-	case $dst_arg in
-	  -* | [=\(\)!]) dst_arg=./$dst_arg;;
-	esac
-	shift;;
+        # Protect names problematic for 'test' and other utilities.
+        case $dst_arg in
+          -* | [=\(\)!]) dst_arg=./$dst_arg;;
+        esac
+        shift;;
 
     -T) no_target_directory=true;;
 
     --version) echo "$0 $scriptversion"; exit $?;;
 
-    --)	shift
-	break;;
+    --) shift
+        break;;
 
-    -*)	echo "$0: invalid option: $1" >&2
-	exit 1;;
+    -*) echo "$0: invalid option: $1" >&2
+        exit 1;;
 
     *)  break;;
   esac
@@ -223,16 +207,16 @@ if test -z "$dir_arg"; then
 
     *[0-7])
       if test -z "$stripcmd"; then
-	u_plus_rw=
+        u_plus_rw=
       else
-	u_plus_rw='% 200'
+        u_plus_rw='% 200'
       fi
       cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;;
     *)
       if test -z "$stripcmd"; then
-	u_plus_rw=
+        u_plus_rw=
       else
-	u_plus_rw=,u+rw
+        u_plus_rw=,u+rw
       fi
       cp_umask=$mode$u_plus_rw;;
   esac
@@ -270,40 +254,14 @@ do
     # if double slashes aren't ignored.
     if test -d "$dst"; then
       if test -n "$no_target_directory"; then
-	echo "$0: $dst_arg: Is a directory" >&2
-	exit 1
+        echo "$0: $dst_arg: Is a directory" >&2
+        exit 1
       fi
       dstdir=$dst
       dst=$dstdir/`basename "$src"`
       dstdir_status=0
     else
-      # Prefer dirname, but fall back on a substitute if dirname fails.
-      dstdir=`
-	(dirname "$dst") 2>/dev/null ||
-	expr X"$dst" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
-	     X"$dst" : 'X\(//\)[^/]' \| \
-	     X"$dst" : 'X\(//\)$' \| \
-	     X"$dst" : 'X\(/\)' \| . 2>/dev/null ||
-	echo X"$dst" |
-	    sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
-		   s//\1/
-		   q
-		 }
-		 /^X\(\/\/\)[^/].*/{
-		   s//\1/
-		   q
-		 }
-		 /^X\(\/\/\)$/{
-		   s//\1/
-		   q
-		 }
-		 /^X\(\/\).*/{
-		   s//\1/
-		   q
-		 }
-		 s/.*/./; q'
-      `
-
+      dstdir=`dirname "$dst"`
       test -d "$dstdir"
       dstdir_status=$?
     fi
@@ -314,74 +272,74 @@ do
   if test $dstdir_status != 0; then
     case $posix_mkdir in
       '')
-	# Create intermediate dirs using mode 755 as modified by the umask.
-	# This is like FreeBSD 'install' as of 1997-10-28.
-	umask=`umask`
-	case $stripcmd.$umask in
-	  # Optimize common cases.
-	  *[2367][2367]) mkdir_umask=$umask;;
-	  .*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
-
-	  *[0-7])
-	    mkdir_umask=`expr $umask + 22 \
-	      - $umask % 100 % 40 + $umask % 20 \
-	      - $umask % 10 % 4 + $umask % 2
-	    `;;
-	  *) mkdir_umask=$umask,go-w;;
-	esac
-
-	# With -d, create the new directory with the user-specified mode.
-	# Otherwise, rely on $mkdir_umask.
-	if test -n "$dir_arg"; then
-	  mkdir_mode=-m$mode
-	else
-	  mkdir_mode=
-	fi
-
-	posix_mkdir=false
-	case $umask in
-	  *[123567][0-7][0-7])
-	    # POSIX mkdir -p sets u+wx bits regardless of umask, which
-	    # is incompatible with FreeBSD 'install' when (umask & 300) != 0.
-	    ;;
-	  *)
-	    tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
-	    trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
-
-	    if (umask $mkdir_umask &&
-		exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
-	    then
-	      if test -z "$dir_arg" || {
-		   # Check for POSIX incompatibilities with -m.
-		   # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
-		   # other-writable bit of parent directory when it shouldn't.
-		   # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
-		   ls_ld_tmpdir=`ls -ld "$tmpdir"`
-		   case $ls_ld_tmpdir in
-		     d????-?r-*) different_mode=700;;
-		     d????-?--*) different_mode=755;;
-		     *) false;;
-		   esac &&
-		   $mkdirprog -m$different_mode -p -- "$tmpdir" && {
-		     ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
-		     test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
-		   }
-		 }
-	      then posix_mkdir=:
-	      fi
-	      rmdir "$tmpdir/d" "$tmpdir"
-	    else
-	      # Remove any dirs left behind by ancient mkdir implementations.
-	      rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
-	    fi
-	    trap '' 0;;
-	esac;;
+        # Create intermediate dirs using mode 755 as modified by the umask.
+        # This is like FreeBSD 'install' as of 1997-10-28.
+        umask=`umask`
+        case $stripcmd.$umask in
+          # Optimize common cases.
+          *[2367][2367]) mkdir_umask=$umask;;
+          .*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
+
+          *[0-7])
+            mkdir_umask=`expr $umask + 22 \
+              - $umask % 100 % 40 + $umask % 20 \
+              - $umask % 10 % 4 + $umask % 2
+            `;;
+          *) mkdir_umask=$umask,go-w;;
+        esac
+
+        # With -d, create the new directory with the user-specified mode.
+        # Otherwise, rely on $mkdir_umask.
+        if test -n "$dir_arg"; then
+          mkdir_mode=-m$mode
+        else
+          mkdir_mode=
+        fi
+
+        posix_mkdir=false
+        case $umask in
+          *[123567][0-7][0-7])
+            # POSIX mkdir -p sets u+wx bits regardless of umask, which
+            # is incompatible with FreeBSD 'install' when (umask & 300) != 0.
+            ;;
+          *)
+            tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
+            trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
+
+            if (umask $mkdir_umask &&
+                exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
+            then
+              if test -z "$dir_arg" || {
+                   # Check for POSIX incompatibilities with -m.
+                   # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
+                   # other-writable bit of parent directory when it shouldn't.
+                   # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
+                   ls_ld_tmpdir=`ls -ld "$tmpdir"`
+                   case $ls_ld_tmpdir in
+                     d????-?r-*) different_mode=700;;
+                     d????-?--*) different_mode=755;;
+                     *) false;;
+                   esac &&
+                   $mkdirprog -m$different_mode -p -- "$tmpdir" && {
+                     ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
+                     test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
+                   }
+                 }
+              then posix_mkdir=:
+              fi
+              rmdir "$tmpdir/d" "$tmpdir"
+            else
+              # Remove any dirs left behind by ancient mkdir implementations.
+              rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
+            fi
+            trap '' 0;;
+        esac;;
     esac
 
     if
       $posix_mkdir && (
-	umask $mkdir_umask &&
-	$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
+        umask $mkdir_umask &&
+        $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
       )
     then :
     else
@@ -391,53 +349,51 @@ do
       # directory the slow way, step by step, checking for races as we go.
 
       case $dstdir in
-	/*) prefix='/';;
-	[-=\(\)!]*) prefix='./';;
-	*)  prefix='';;
+        /*) prefix='/';;
+        [-=\(\)!]*) prefix='./';;
+        *)  prefix='';;
       esac
 
-      eval "$initialize_posix_glob"
-
       oIFS=$IFS
       IFS=/
-      $posix_glob set -f
+      set -f
       set fnord $dstdir
       shift
-      $posix_glob set +f
+      set +f
       IFS=$oIFS
 
       prefixes=
 
       for d
       do
-	test X"$d" = X && continue
-
-	prefix=$prefix$d
-	if test -d "$prefix"; then
-	  prefixes=
-	else
-	  if $posix_mkdir; then
-	    (umask=$mkdir_umask &&
-	     $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
-	    # Don't fail if two instances are running concurrently.
-	    test -d "$prefix" || exit 1
-	  else
-	    case $prefix in
-	      *\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
-	      *) qprefix=$prefix;;
-	    esac
-	    prefixes="$prefixes '$qprefix'"
-	  fi
-	fi
-	prefix=$prefix/
+        test X"$d" = X && continue
+
+        prefix=$prefix$d
+        if test -d "$prefix"; then
+          prefixes=
+        else
+          if $posix_mkdir; then
+            (umask=$mkdir_umask &&
+             $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
+            # Don't fail if two instances are running concurrently.
+            test -d "$prefix" || exit 1
+          else
+            case $prefix in
+              *\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
+              *) qprefix=$prefix;;
+            esac
+            prefixes="$prefixes '$qprefix'"
+          fi
+        fi
+        prefix=$prefix/
       done
 
       if test -n "$prefixes"; then
-	# Don't fail if two instances are running concurrently.
-	(umask $mkdir_umask &&
-	 eval "\$doit_exec \$mkdirprog $prefixes") ||
-	  test -d "$dstdir" || exit 1
-	obsolete_mkdir_used=true
+        # Don't fail if two instances are running concurrently.
+        (umask $mkdir_umask &&
+         eval "\$doit_exec \$mkdirprog $prefixes") ||
+          test -d "$dstdir" || exit 1
+        obsolete_mkdir_used=true
       fi
     fi
   fi
@@ -472,15 +428,12 @@ do
 
     # If -C, don't bother to copy if it wouldn't change the file.
     if $copy_on_change &&
-       old=`LC_ALL=C ls -dlL "$dst"	2>/dev/null` &&
-       new=`LC_ALL=C ls -dlL "$dsttmp"	2>/dev/null` &&
-
-       eval "$initialize_posix_glob" &&
-       $posix_glob set -f &&
+       old=`LC_ALL=C ls -dlL "$dst"     2>/dev/null` &&
+       new=`LC_ALL=C ls -dlL "$dsttmp"  2>/dev/null` &&
+       set -f &&
        set X $old && old=:$2:$4:$5:$6 &&
        set X $new && new=:$2:$4:$5:$6 &&
-       $posix_glob set +f &&
-
+       set +f &&
        test "$old" = "$new" &&
        $cmpprog "$dst" "$dsttmp" >/dev/null 2>&1
     then
@@ -493,24 +446,24 @@ do
       # to itself, or perhaps because mv is so ancient that it does not
       # support -f.
       {
-	# Now remove or move aside any old file at destination location.
-	# We try this two ways since rm can't unlink itself on some
-	# systems and the destination file might be busy for other
-	# reasons.  In this case, the final cleanup might fail but the new
-	# file should still install successfully.
-	{
-	  test ! -f "$dst" ||
-	  $doit $rmcmd -f "$dst" 2>/dev/null ||
-	  { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
-	    { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
-	  } ||
-	  { echo "$0: cannot unlink or rename $dst" >&2
-	    (exit 1); exit 1
-	  }
-	} &&
-
-	# Now rename the file to the real destination.
-	$doit $mvcmd "$dsttmp" "$dst"
+        # Now remove or move aside any old file at destination location.
+        # We try this two ways since rm can't unlink itself on some
+        # systems and the destination file might be busy for other
+        # reasons.  In this case, the final cleanup might fail but the new
+        # file should still install successfully.
+        {
+          test ! -f "$dst" ||
+          $doit $rmcmd -f "$dst" 2>/dev/null ||
+          { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
+            { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
+          } ||
+          { echo "$0: cannot unlink or rename $dst" >&2
+            (exit 1); exit 1
+          }
+        } &&
+
+        # Now rename the file to the real destination.
+        $doit $mvcmd "$dsttmp" "$dst"
       }
     fi || exit 1
 
diff --git a/interpret.h b/interpret.h
index ba70cf08..27f194ae 100644
--- a/interpret.h
+++ b/interpret.h
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -1098,10 +1098,6 @@ match_re:
 			JUMPTO(ni);
 
 		case Op_K_getline_redir:
-			if ((currule == BEGINFILE || currule == ENDFILE)
-					&& pc->into_var == false
-					&& pc->redir_type == redirect_input)
-				fatal(_("`getline' invalid inside `%s' rule"), ruletab[currule]);
 			r = do_getline_redir(pc->into_var, pc->redir_type);
 			PUSH(r);
 			break;
@@ -1217,7 +1213,7 @@ match_re:
 			ret = nextfile(& curfile, true);	/* skip current file */
 
 			if (currule == BEGINFILE) {
-				long stack_size;
+				long stack_size = 0;
 
 				ni = pop_exec_state(& currule, & source, & stack_size);
 
diff --git a/io.c b/io.c
index 4f244532..57d4af22 100644
--- a/io.c
+++ b/io.c
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -121,6 +121,11 @@
 #endif
 
 #if defined(VMS)
+#include <ssdef.h>
+#ifndef SS$_EXBYTLM
+#define SS$_EXBYTLM 0x2a14  /* VMS 8.4 seen */
+#endif
+#include <rmsdef.h>
 #define closemaybesocket(fd)	close(fd)
 #endif
 
@@ -161,6 +166,12 @@
 # define SOCKET			int
 #endif
 
+#else /* HAVE_SOCKETS */
+
+#ifndef closemaybesocket
+# define closemaybesocket(fd)	close(fd)
+#endif
+
 #endif /* HAVE_SOCKETS */
 
 #ifndef HAVE_SETSID
@@ -195,6 +206,7 @@ typedef enum { CLOSE_ALL, CLOSE_TO, CLOSE_FROM } two_way_close_type;
 #define at_eof(iop)     (((iop)->flag & IOP_AT_EOF) != 0)
 #define has_no_data(iop)        ((iop)->dataend == NULL)
 #define no_data_left(iop)	((iop)->off >= (iop)->dataend)
+#define buffer_has_all_data(iop) ((iop)->dataend - (iop)->off == (iop)->public.sbuf.st_size)
 
 /*
  * The key point to the design is to split out the code that searches through
@@ -268,7 +280,23 @@ static RECVALUE (*matchrec)(IOBUF *iop, struct recmatch *recm, SCANSTATE *state)
 static int get_a_record(char **out, IOBUF *iop, int *errcode);
 
 static void free_rp(struct redirect *rp);
-static int inetfile(const char *str, int *length, int *family);
+
+struct inet_socket_info {
+	int family;		/* AF_UNSPEC, AF_INET, or AF_INET6 */
+	int protocol;		/* SOCK_STREAM or SOCK_DGRAM */
+	/*
+	 * N.B. If we used 'char *' or 'const char *' pointers to the
+	 * substrings, it would trigger compiler warnings about the casts
+	 * in either inetfile() or devopen().  So we use offset/len to
+	 * avoid that.
+	 */
+	struct {
+		int offset;
+		int len;
+	} localport, remotehost, remoteport;
+};
+
+static bool inetfile(const char *str, struct inet_socket_info *isn);
 
 static NODE *in_PROCINFO(const char *pidx1, const char *pidx2, NODE **full_idx);
 static long get_read_timeout(IOBUF *iop);
@@ -462,6 +490,11 @@ nextfile(IOBUF **curfile, bool skipping)
 			/* IOBUF management: */
 			errno = 0;
 			fd = devopen(fname, binmode("r"));
+			if (fd == INVALID_HANDLE && errno == EMFILE) {
+				close_one();
+				close_one();
+				fd = devopen(fname, binmode("r"));
+			}
 			errcode = errno;
 			if (! do_traditional)
 				update_ERRNO_int(errno);
@@ -697,7 +730,9 @@ redirect(NODE *redir_exp, int redirtype, int *errflg)
 	int fd;
 	const char *what = NULL;
 	bool new_rp = false;
-	int len;	/* used with /inet */
+#ifdef HAVE_SOCKETS
+	struct inet_socket_info isi;
+#endif
 	static struct redirect *save_rp = NULL;	/* hold onto rp that should
 	                                         * be freed for reuse
 	                                         */
@@ -756,9 +791,9 @@ redirect(NODE *redir_exp, int redirtype, int *errflg)
 	 * Use /inet4 to force IPv4, /inet6 to force IPv6, and plain
 	 * /inet will be whatever we get back from the system.
 	 */
-	if (inetfile(str, & len, NULL)) {
+	if (inetfile(str, & isi)) {
 		tflag |= RED_SOCKET;
-		if (strncmp(str + len, "tcp/", 4) == 0)
+		if (isi.protocol == SOCK_STREAM)
 			tflag |= RED_TCP;	/* use shutdown when closing */
 	}
 #endif /* HAVE_SOCKETS */
@@ -885,7 +920,7 @@ redirect(NODE *redir_exp, int redirtype, int *errflg)
 			direction = "to/from";
 			if (! two_way_open(str, rp)) {
 #ifdef HAVE_SOCKETS
-				if (inetfile(str, NULL, NULL)) {
+				if (inetfile(str, NULL)) {
 					*errflg = errno;
 					/* do not free rp, saving it for reuse (save_rp = rp) */
 					return NULL;
@@ -948,13 +983,13 @@ redirect(NODE *redir_exp, int redirtype, int *errflg)
 			if (errno == EMFILE || errno == ENFILE)
 				close_one();
 #ifdef VMS
-			/* Alpha/VMS V7.1's C RTL is returning this instead
+			/* Alpha/VMS V7.1+ C RTL is returning these instead
 			   of EMFILE (haven't tried other post-V6.2 systems) */
-#define SS$_EXQUOTA 0x001C
-#define SS$_EXBYTLM 0x2a14  /* VMS 8.4 seen */
-			else if (errno == EIO && 
+			else if ((errno == EIO || errno == EVMSERR) && 
                                  (vaxc$errno == SS$_EXQUOTA ||
-                                  vaxc$errno == SS$_EXBYTLM))
+                                  vaxc$errno == SS$_EXBYTLM ||
+                                  vaxc$errno == RMS$_ACC ||
+				  vaxc$errno == RMS$_SYN))
 				close_one();
 #endif
 			else {
@@ -1522,8 +1557,7 @@ devopen(const char *name, const char *mode)
 	char *cp;
 	char *ptr;
 	int flag = 0;
-	int len;
-	int family;
+	struct inet_socket_info isi;
 
 	if (strcmp(name, "-") == 0)
 		return fileno(stdin);
@@ -1560,74 +1594,14 @@ devopen(const char *name, const char *mode)
 		/* do not set close-on-exec for inherited fd's */
 		if (openfd != INVALID_HANDLE)
 			return openfd;
-	} else if (inetfile(name, & len, & family)) {
+	} else if (inetfile(name, & isi)) {
 #ifdef HAVE_SOCKETS
-		/* /inet/protocol/localport/hostname/remoteport */
-		int protocol;
-		char *hostname;
-		char *hostnameslastcharp;
-		char *localpname;
-		char *localpnamelastcharp;
-
-		cp = (char *) name + len;
-		/* which protocol? */
-		if (strncmp(cp, "tcp/", 4) == 0)
-			protocol = SOCK_STREAM;
-		else if (strncmp(cp, "udp/", 4) == 0)
-			protocol = SOCK_DGRAM;
-		else {
-			protocol = SOCK_STREAM;	/* shut up the compiler */
-			fatal(_("no (known) protocol supplied in special filename `%s'"),
-						name);
-		}
-		cp += 4;
-
-		/* which localport? */
-		localpname = cp;
-		while (*cp != '/' && *cp != '\0')
-			cp++;
-		/*                    
-		 * Require a port, let them explicitly put 0 if
-		 * they don't care.  
-		 */
-		if (*cp != '/' || cp == localpname)
-			fatal(_("special file name `%s' is incomplete"), name);
+		cp = (char *) name;
 
-		/*
-		 * We change the special file name temporarily because we
-		 * need a 0-terminated string here for conversion with atoi().
-		 * By using atoi() the use of decimal numbers is enforced.
-		 */
-		*cp = '\0';
-		localpnamelastcharp = cp;
-
-		/* which hostname? */
-		cp++;
-		hostname = cp;
-		while (*cp != '/' && *cp != '\0')
-			cp++; 
-		if (*cp != '/' || cp == hostname) {
-			*localpnamelastcharp = '/';
-			fatal(_("must supply a remote hostname to `/inet'"));
-		}
-		*cp = '\0';
-		hostnameslastcharp = cp;
-
-		/* which remoteport? */
-		cp++;
-		/*
-		 * The remote port ends the special file name.
-		 * This means there already is a '\0' at the end of the string.
-		 * Therefore no need to patch any string ending.
-		 *
-		 * Here too, require a port, let them explicitly put 0 if
-		 * they don't care.
-		 */
-		if (*cp == '\0') {
-			*localpnamelastcharp = '/';
-			*hostnameslastcharp = '/';
-			fatal(_("must supply a remote port to `/inet'"));
-		}
+		/* socketopen requires NUL-terminated strings */
+		cp[isi.localport.offset+isi.localport.len] = '\0';
+		cp[isi.remotehost.offset+isi.remotehost.len] = '\0';
+		/* remoteport comes last, so already NUL-terminated */
 
 		{
 #define DEFAULT_RETRIES 20
@@ -1664,13 +1638,14 @@ devopen(const char *name, const char *mode)
 		retries = def_retries;
 
 		do {
-			openfd = socketopen(family, protocol, localpname, cp, hostname);
+			openfd = socketopen(isi.family, isi.protocol, name+isi.localport.offset, name+isi.remoteport.offset, name+isi.remotehost.offset);
 			retries--;
 		} while (openfd == INVALID_HANDLE && retries > 0 && usleep(msleep) == 0);
 	}
 
-	*localpnamelastcharp = '/';
-	*hostnameslastcharp = '/';
+	/* restore original name string */
+	cp[isi.localport.offset+isi.localport.len] = '/';
+	cp[isi.remotehost.offset+isi.remotehost.len] = '/';
 #else /* ! HAVE_SOCKETS */
 	fatal(_("TCP/IP communications are not supported"));
 #endif /* HAVE_SOCKETS */
@@ -1684,9 +1659,8 @@ strictopen:
 		/* On OS/2 and Windows directory access via open() is
 		   not permitted.  */
 		struct stat buf;
-		int l, f;
 
-		if (!inetfile(name, &l, &f)
+		if (!inetfile(name, NULL)
 		    && stat(name, & buf) == 0 && S_ISDIR(buf.st_mode))
 			errno = EISDIR;
 	}
@@ -1708,7 +1682,7 @@ two_way_open(const char *str, struct redirect *rp)
 
 #ifdef HAVE_SOCKETS
 	/* case 1: socket */
-	if (inetfile(str, NULL, NULL)) {
+	if (inetfile(str, NULL)) {
 		int fd, newfd;
 
 		fd = devopen(str, "rw");
@@ -2105,6 +2079,7 @@ use_pipes:
 		    || close(ctop[0]) == -1 || close(ctop[1]) == -1)
 			fatal(_("close of pipe failed (%s)"), strerror(errno));
 		/* stderr does NOT get dup'ed onto child's stdout */
+		signal(SIGPIPE, SIG_DFL);
 		execl("/bin/sh", "sh", "-c", str, NULL);
 		_exit(errno == ENOENT ? 127 : 126);
 	}
@@ -2298,6 +2273,7 @@ gawk_popen(const char *cmd, struct redirect *rp)
 			fatal(_("moving pipe to stdout in child failed (dup: %s)"), strerror(errno));
 		if (close(p[0]) == -1 || close(p[1]) == -1)
 			fatal(_("close of pipe failed (%s)"), strerror(errno));
+		signal(SIGPIPE, SIG_DFL);
 		execl("/bin/sh", "sh", "-c", cmd, NULL);
 		_exit(errno == ENOENT ? 127 : 126);
 	}
@@ -3497,9 +3473,18 @@ get_a_record(char **out,        /* pointer to pointer to data */
 
 		ret = (*matchrec)(iop, & recm, & state);
 		iop->flag &= ~IOP_AT_START;
+		/* found the record, we're done, break the loop */
 		if (ret == REC_OK)
 			break;
 
+		/*
+		 * Likely found the record; if there's no more data
+		 * to be had (like from a tiny regular file), break the
+		 * loop. Otherwise, see if we can read more.
+		 */
+		if (ret == TERMNEAREND && buffer_has_all_data(iop))
+			break;
+
 		/* need to add more data to buffer */
 		/* shift data down in buffer */
 		dataend_off = iop->dataend - iop->off;
@@ -3549,10 +3534,14 @@ get_a_record(char **out,        /* pointer to pointer to data */
 			break;
 		} else if (iop->count == 0) {
 			/*
-			 * hit EOF before matching RS, so end
-			 * the record and set RT to ""
+			 * Hit EOF before being certain that we've matched
+			 * the end of the record. If ret is TERMNEAREND,
+			 * we need to pull out what we've got in the buffer.
+			 * Eventually we'll come back here and see the EOF,
+			 * end the record and set RT to "".
 			 */
-			iop->flag |= IOP_AT_EOF;
+			if (ret != TERMNEAREND)
+				iop->flag |= IOP_AT_EOF;
 			break;
 		} else
 			iop->dataend += iop->count;
@@ -3734,35 +3723,92 @@ free_rp(struct redirect *rp)
 
 /* inetfile --- return true for a /inet special file, set other values */
 
-static int
-inetfile(const char *str, int *length, int *family)
+static bool
+inetfile(const char *str, struct inet_socket_info *isi)
 {
-	bool ret = false;
-
-	if (strncmp(str, "/inet/", 6) == 0) {
-		ret = true;
-		if (length != NULL)
-			*length = 6;
-		if (family != NULL)
-			*family = AF_UNSPEC;
-	} else if (strncmp(str, "/inet4/", 7) == 0) {
-		ret = true;
-		if (length != NULL)
-			*length = 7;
-		if (family != NULL)
-			*family = AF_INET;
-	} else if (strncmp(str, "/inet6/", 7) == 0) {
-		ret = true;
-		if (length != NULL)
-			*length = 7;
-		if (family != NULL)
-			*family = AF_INET6;
+#ifndef HAVE_SOCKETS
+	return false;
+#else
+	const char *cp = str;
+	struct inet_socket_info buf;
+
+	/* syntax: /inet/protocol/localport/hostname/remoteport */
+	if (strncmp(cp, "/inet", 5) != 0)
+		/* quick exit */
+		return false;
+	if (! isi)
+		isi = & buf;
+	cp += 5;
+	switch (*cp) {
+	case '/':
+		isi->family = AF_UNSPEC;
+		break;
+	case '4':
+		if (*++cp != '/')
+			return false;
+		isi->family = AF_INET;
+		break;
+	case '6':
+		if (*++cp != '/')
+			return false;
+		isi->family = AF_INET6;
+		break;
+	default:
+		return false;
+	}
+	cp++;	/* skip past '/' */
+
+	/* which protocol? */
+	if (strncmp(cp, "tcp/", 4) == 0)
+		isi->protocol = SOCK_STREAM;
+	else if (strncmp(cp, "udp/", 4) == 0)
+		isi->protocol = SOCK_DGRAM;
+	else
+		return false;
+	cp += 4;
+
+	/* which localport? */
+	isi->localport.offset = cp-str;
+	while (*cp != '/' && *cp != '\0')
+		cp++;
+	/*                    
+	 * Require a port, let them explicitly put 0 if
+	 * they don't care.  
+	 */
+	if (*cp != '/' || ((isi->localport.len = (cp-str)-isi->localport.offset) == 0))
+		return false;
+
+	/* which hostname? */
+	cp++;
+	isi->remotehost.offset = cp-str;
+	while (*cp != '/' && *cp != '\0')
+		cp++; 
+	if (*cp != '/' || ((isi->remotehost.len = (cp-str)-isi->remotehost.offset) == 0))
+		return false;
+
+	/* which remoteport? */
+	cp++;
+	/*
+	 * The remote port ends the special file name.
+	 * This means there already is a '\0' at the end of the string.
+	 * Therefore no need to patch any string ending.
+	 *
+	 * Here too, require a port, let them explicitly put 0 if
+	 * they don't care.
+	 */
+	isi->remoteport.offset = cp-str;
+	while (*cp != '/' && *cp != '\0')
+		cp++; 
+	if (*cp != '\0' || ((isi->remoteport.len = (cp-str)-isi->remoteport.offset) == 0))
+		return false;
+
 #ifndef HAVE_GETADDRINFO
+	/* final check for IPv6: */
+	if (isi->family == AF_INET6)
 		fatal(_("IPv6 communication is not supported"));
 #endif
-	}
-
-	return ret;
+	return true;
+#endif /* HAVE_SOCKETS */
 }
 
 /*
@@ -3958,7 +4004,7 @@ init_output_wrapper(awk_output_buf_t *outbuf)
 	outbuf->mode = NULL;
 	outbuf->fp = NULL;
 	outbuf->opaque = NULL;
-	outbuf->redirected = false;
+	outbuf->redirected = awk_false;
 	outbuf->gawk_fwrite = gawk_fwrite;
 	outbuf->gawk_fflush = gawk_fflush;
 	outbuf->gawk_ferror = gawk_ferror;
diff --git a/m4/ChangeLog b/m4/ChangeLog
index 9e2c279b..81fdcec0 100644
--- a/m4/ChangeLog
+++ b/m4/ChangeLog
@@ -1,3 +1,13 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-03-11         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* readline.m4: Add manual check for *bsd* OS and add -ltermcap
+	if so.  Hack, slash. Can you say "quick and dirty" boys and girls?
+	I knew you could.
+
 2013-10-16         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* readline.m4: Add check for NULL return from readline() in
diff --git a/m4/readline.m4 b/m4/readline.m4
index af2745db..77ed8b25 100644
--- a/m4/readline.m4
+++ b/m4/readline.m4
@@ -1,5 +1,5 @@
 dnl Check for readline and dependencies
-dnl Copyright (C) 2004, 2005, 2013 Free Software Foundation, Inc.
+dnl Copyright (C) 2004, 2005, 2013, 2014 Free Software Foundation, Inc.
 dnl
 dnl This file is free software, distributed under the terms of the GNU
 dnl General Public License.  As a special exception to the GNU General
@@ -70,6 +70,10 @@ dnl action if cross compiling:
         LIBS=$_readline_save_libs
 
         if test $_found_readline = yes ; then
+	   case $host_os in
+	   *bsd* )	_combo="$_combo -ltermcap"
+	  	 ;;
+	   esac
            AC_DEFINE(HAVE_LIBREADLINE,1,
 	      [Define to 1 if you have a fully functional readline library.])
            AC_SUBST(LIBREADLINE,$_combo)
diff --git a/main.c b/main.c
index 4f8a397d..c6fef2f1 100644
--- a/main.c
+++ b/main.c
@@ -3,7 +3,7 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-2013 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -24,7 +24,7 @@
  */
 
 /* FIX THIS BEFORE EVERY RELEASE: */
-#define UPDATE_YEAR	2013
+#define UPDATE_YEAR	2014
 
 #include "awk.h"
 #include "getopt.h"
@@ -194,7 +194,6 @@ static const struct option optab[] = {
 	{ NULL, 0, NULL, '\0' }
 };
 
-
 /* main --- process args, parse program, run it, clean up */
 
 int
diff --git a/missing_d/ChangeLog b/missing_d/ChangeLog
index f94c070d..70fbde64 100644
--- a/missing_d/ChangeLog
+++ b/missing_d/ChangeLog
@@ -1,3 +1,7 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
 2013-05-09         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* 4.1.0: Release tar ball made.
diff --git a/old-extension/ChangeLog b/old-extension/ChangeLog
index a25295a6..55c8d31d 100644
--- a/old-extension/ChangeLog
+++ b/old-extension/ChangeLog
@@ -1,3 +1,10 @@
+2014-01-07         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* dbarray.awk: Use full name for lib to load in extenstion() call.
+	* record.awk: Ditto.
+	* testsparr.awk: Ditto.
+	* spec_array.c [SUPER]: Fix so that it will compile.
+
 2013-01-06         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* bindarr.c, dbarray.awk, fileop.c, record.awk, sparr.c,
diff --git a/old-extension/dbarray.awk b/old-extension/dbarray.awk
index e0a3c093..1e31f58f 100644
--- a/old-extension/dbarray.awk
+++ b/old-extension/dbarray.awk
@@ -3,7 +3,7 @@
 # @load "bindarr"
 
 BEGIN {
-	extension("bindarr")
+	extension("./bindarr.so")
 }
 
 function _db_count(symbol, sq,
diff --git a/old-extension/record.awk b/old-extension/record.awk
index 18a3ce48..ff89110d 100644
--- a/old-extension/record.awk
+++ b/old-extension/record.awk
@@ -30,8 +30,8 @@
 #
 
 BEGIN {
-	extension("fileop.so")
-	extension("bindarr.so")
+	extension("./fileop.so")
+	extension("./bindarr.so")
 }
 
 # _record_count --- return the number of records in file
diff --git a/old-extension/spec_array.c b/old-extension/spec_array.c
index 78b24018..34d15fc5 100644
--- a/old-extension/spec_array.c
+++ b/old-extension/spec_array.c
@@ -3,7 +3,7 @@
  */
 
 /*
- * Copyright (C) 2012 the Free Software Foundation, Inc.
+ * Copyright (C) 2012, 2014 the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Programming Language.
@@ -40,7 +40,7 @@ typedef struct spec_array {
  * the base array is str_array.
  */
 
-#define	SUPER(F)	(*str_array_func[AFUNC(F)])
+#define	SUPER(F)	(*str_array_func[F ## _ind])
 
 
 /*
diff --git a/old-extension/testsparr.awk b/old-extension/testsparr.awk
index 648a21a2..a9e3119d 100644
--- a/old-extension/testsparr.awk
+++ b/old-extension/testsparr.awk
@@ -1,6 +1,6 @@
 # ../gawk -lsparr -f testsparr.awk
 BEGIN {
-	extension("sparr")
+	extension("./sparr.so")
 	print SYS["time"]
 	SYS["readline"] = "sparr.c";
 	printf("File %s has %d lines\n", SYS["readline"], length(READLINE)) 
diff --git a/pc/ChangeLog b/pc/ChangeLog
index eb5636e9..a66edae9 100644
--- a/pc/ChangeLog
+++ b/pc/ChangeLog
@@ -1,3 +1,50 @@
+2014-04-17         Scott Deifik  <scottd.mail@sbcglobal.net>
+
+	* Makefile.tst: Add readfile2 test.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-02-03   Scott Deifik  <scottd.mail@sbcglobal.net>
+
+	* Makefile.tst: Include original test/Makefile.in lines as
+	comments.
+
+2014-01-28  Eli Zaretskii  <eliz@gnu.org>
+
+	* Makefile.tst (strftime): Pass the value of 'date' command
+	through the DATECMD variable.
+	(readdir): Adapt to changes in test/readdir0.awk.
+
+2014-01-20         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.tst (mbprintf4, backbigs1, backsmalls1): Add warning
+	that the tests are expected to fail with DJGPP.
+
+2014-01-24   Scott Deifik  <scottd.mail@sbcglobal.net>
+
+	* Makefile.tst: Sync with mainline.
+
+2014-01-20         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.tst (split_after_fpat, mpfrnegzero): Added, to
+	sync with main test Makefile.
+
+2014-01-15  Eli Zaretskii  <eliz@gnu.org>
+
+	* Makefile.tst (mbprintf4, profile5, backbigs1, backsmalls1):
+	Announce expected failures.
+	(fts): Fail gracefully, to avoid bailing out of the test suite too
+	early.
+
+	* popen.c (os_system): Use spawnl, and quote the command line, to
+	be consistent with what gawk_popen does.
+	(os_popen) [__MINGW32__]: Don't scriptify the command, to be
+	consistent with gawk_popen.
+	(os_pclose) [__MINGW32__]: Update to match os_open: no need to
+	unlink the script file.
+
 2013-12-10   Scott Deifik  <scottd.mail@sbcglobal.net>
 
 	* gawkmisc.c (init_sockets): Move into the right part of the
diff --git a/pc/Makefile b/pc/Makefile
index 9d98cb1c..d1c08069 100644
--- a/pc/Makefile
+++ b/pc/Makefile
@@ -6,6 +6,17 @@
 
 # Tested with GNU make on Windows, OS/2 and DOS.
 
+# Copyright (C) 1989-2014 Free Software Foundation, Inc.
+
+# This Makefile is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
 default:
 	@echo "Enter $(MAK) target "
 	@echo " where 'target' is chosen from                          "
diff --git a/pc/Makefile.tst b/pc/Makefile.tst
index 6a2216a0..610704e4 100644
--- a/pc/Makefile.tst
+++ b/pc/Makefile.tst
@@ -1,6 +1,6 @@
 # Makefile for GNU Awk test suite.
 #
-# Copyright (C) 1988-2013 the Free Software Foundation, Inc.
+# Copyright (C) 1988-2014 the Free Software Foundation, Inc.
 # 
 # This file is part of GAWK, the GNU implementation of the
 # AWK Programming Language.
@@ -141,8 +141,7 @@ BASIC_TESTS = \
 	arrayref arrymem1 arryref2 arryref3 arryref4 arryref5 arynasty \
 	arynocls aryprm1 aryprm2 aryprm3 aryprm4 aryprm5 aryprm6 aryprm7 \
 	aryprm8 arysubnm asgext awkpath \
-	back89 backgsub \
-	badassign1 \
+	back89 backgsub badassign1 \
 	childin clobber closebad clsflnam compare compare2 concat1 concat2 \
 	concat3 concat4 convfmt \
 	datanonl defref delargv delarpm2 delarprm delfunc dfamb1 dfastress dynlj \
@@ -194,14 +193,16 @@ GAWK_EXT_TESTS = \
 	patsplit posix printfbad1 printfbad2 printfbad3 procinfs \
 	profile1 profile2 profile3 profile4 profile5 pty1 \
 	rebuf regx8bit reginttrad reint reint2 rsstart1 \
-	rsstart2 rsstart3 rstest6 shadow sortfor sortu splitarg4 strftime \
+	rsstart2 rsstart3 rstest6 shadow sortfor sortu split_after_fpat \
+	splitarg4 strftime \
 	strtonum switch2 symtab1 symtab2 symtab3 symtab4 symtab5 symtab6 \
 	symtab7 symtab8 symtab9
 
 EXTRA_TESTS = inftest regtest
 INET_TESTS = inetdayu inetdayt inetechu inetecht
 MACHINE_TESTS = double1 double2 fmtspcl intformat
-MPFR_TESTS = mpfrnr mpfrrnd mpfrieee mpfrexprange mpfrsort mpfrbigint
+MPFR_TESTS = mpfrnr mpfrnegzero mpfrrnd mpfrieee mpfrexprange \
+	mpfrsort mpfrbigint
 LOCALE_CHARSET_TESTS = \
 	asort asorti backbigs1 backsmalls1 backsmalls2 \
 	fmttest fnarydel fnparydl jarebug lc_num1 mbfw1 \
@@ -209,7 +210,7 @@ LOCALE_CHARSET_TESTS = \
 
 SHLIB_TESTS = \
 	fnmatch filefuncs fork fork2 fts functab4 inplace1 inplace2 inplace3 \
-	ordchr ordchr2 readdir readfile revout revtwoway rwarray testext time
+	ordchr ordchr2 readdir readfile readfile2 revout revtwoway rwarray testext time
 
 # List of the tests which should be run with --lint option:
 NEED_LINT = \
@@ -410,7 +411,7 @@ getline2::
 
 awkpath::
 	@echo $@
-	@AWKPATH=""$(srcdir)"$(PATH_SEPARATOR)"$(srcdir)"/lib" $(AWK) -f awkpath.awk >_$@
+	@AWKPATH="$(srcdir)$(PATH_SEPARATOR)$(srcdir)/lib" $(AWK) -f awkpath.awk >_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 argtest::
@@ -429,15 +430,13 @@ nonl::
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 strftime::
-	@echo This test could fail on slow machines or on a minute boundary,
-	@echo so if it does, double check the actual results:
 	@echo $@
 #	@GAWKLOCALE=C; export GAWKLOCALE; \
 #	TZ=GMT0; export TZ; \
-#	(LC_ALL=C date) | $(AWK) -v OUTPUT=_$@ -f "$(srcdir)"/strftime.awk
+#	$(AWK) -v OUTPUT=_$@ -f "$(srcdir)"/strftime.awk
 	@GAWKLOCALE=C; export GAWKLOCALE; \
 	TZ=GMT0; export TZ; \
-	(LC_ALL=C $(DATE)) | $(AWK) -v OUTPUT=_$@ -f "$(srcdir)"/strftime.awk
+	$(AWK) -v OUTPUT=_$@ -v DATECMD="$(DATE)" -f "$(srcdir)"/strftime.awk
 	@-$(CMP) strftime.ok _$@ && rm -f _$@ strftime.ok || exit 0
 
 litoct::
@@ -494,7 +493,7 @@ nors::
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 fmtspcl.ok: fmtspcl.tok
-	@$(AWK) -v "sd="$(srcdir)"" 'BEGIN {pnan = sprintf("%g",sqrt(-1)); nnan = sprintf("%g",-sqrt(-1)); pinf = sprintf("%g",-log(0)); ninf = sprintf("%g",log(0))} {sub(/positive_nan/,pnan); sub(/negative_nan/,nnan); sub(/positive_infinity/,pinf); sub(/negative_infinity/,ninf); sub(/fmtspcl/,(sd"/fmtspcl")); print}' < "$(srcdir)"/fmtspcl.tok > $@ 2>/dev/null
+	@$(AWK) -v "sd=$(srcdir)" 'BEGIN {pnan = sprintf("%g",sqrt(-1)); nnan = sprintf("%g",-sqrt(-1)); pinf = sprintf("%g",-log(0)); ninf = sprintf("%g",log(0))} {sub(/positive_nan/,pnan); sub(/negative_nan/,nnan); sub(/positive_infinity/,pinf); sub(/negative_infinity/,ninf); sub(/fmtspcl/,(sd"/fmtspcl")); print}' < "$(srcdir)"/fmtspcl.tok > $@ 2>/dev/null
 
 fmtspcl: fmtspcl.ok
 	@echo $@
@@ -660,7 +659,7 @@ widesub4::
 
 ignrcas2::
 	@echo $@
-	@GAWKLOCALE=en_US ; export GAWKLOCALE ; \
+	@GAWKLOCALE=en_US.UTF-8 ; export GAWKLOCALE ; \
 	$(AWK) -f "$(srcdir)"/$@.awk >_$@ 2>&1 || echo EXIT CODE: $$? >> _$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
@@ -797,6 +796,7 @@ mbprintf3::
 
 mbprintf4::
 	@echo $@
+	@echo Expect mbprintf4 to fail with MinGW and DJGPP
 	@GAWKLOCALE=en_US.UTF-8 ; export GAWKLOCALE ; \
 	$(AWK) -f "$(srcdir)"/$@.awk "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >> _$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
@@ -870,6 +870,7 @@ profile4:
 
 profile5:
 	@echo $@
+	@echo Expect profile5 to fail with MinGW due to 3 digits in %e output
 	@GAWK_NO_PP_RUN=1 $(AWK) --profile=ap-$@.out -f "$(srcdir)"/$@.awk > /dev/null
 	@sed 1,2d < ap-$@.out > _$@; rm ap-$@.out
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
@@ -911,6 +912,11 @@ mpfrrnd:
 	@$(AWK) -M -vPREC=53 -f "$(srcdir)"/$@.awk > _$@ 2>&1
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+mpfrnegzero:
+	@echo $@
+	@$(AWK) -M -f "$(srcdir)"/$@.awk > _$@ 2>&1
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 mpfrnr:
 	@echo $@
 	@$(AWK) -M -vPREC=113 -f "$(srcdir)"/$@.awk "$(srcdir)"/$@.in > _$@
@@ -929,7 +935,7 @@ mpfrbigint:
 jarebug::
 	@echo $@
 	@echo Expect jarebug to fail with DJGPP and MinGW.
-	@"$(srcdir)"/$@.sh "$(AWKPROG)" ""$(srcdir)"/$@.awk" ""$(srcdir)"/$@.in" "_$@"
+	@"$(srcdir)"/$@.sh "$(AWKPROG)" "$(srcdir)"/$@.awk "$(srcdir)"/$@.in "_$@"
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 ordchr2::
@@ -943,6 +949,11 @@ readfile::
 	@$(AWK) -l readfile 'BEGIN {printf "%s", readfile("Makefile")}' >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) Makefile _$@ && rm -f _$@ || cp -p Makefile $@.ok
 
+readfile2::
+	@echo $@
+	@$(AWK) -f "$(srcdir)"/$@.awk "$(srcdir)"/$@.awk "$(srcdir)"/readdir.awk > _$@ || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 include2::
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) --include inclib 'BEGIN {print sandwich("a", "b", "c")}' >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
@@ -1017,8 +1028,8 @@ inplace3::
 
 testext::
 	@echo $@
-#	@$(AWK) '/^(@load|BEGIN)/,/^}/' $(top_srcdir)/extension/testext.c > testext.awk
-	@$(AWK) ' /^(@load|BEGIN)/,/^}/' $(top_srcdir)/extension/testext.c > testext.awk
+#	@$(AWK) '/^(@load|BEGIN)/,/^}/' "$(top_srcdir)"/extension/testext.c > testext.awk
+	@$(AWK) ' /^(@load|BEGIN)/,/^}/' "$(top_srcdir)"/extension/testext.c > testext.awk
 	@$(AWK) -f testext.awk >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@ testext.awk
 
@@ -1029,19 +1040,28 @@ readdir:
 	fi
 	@echo $@
 	@echo This test may fail on MinGW if $(LS) does not report full Windows file index as the inode
-	@$(AWK) -f "$(srcdir)"/readdir.awk $(top_srcdir) > _$@
-#	@ls -afli $(top_srcdir) | sed 1d | $(AWK) -f "$(srcdir)"/readdir0.awk -v extout=_$@ $(top_srcdir) > $@.ok
-	@$(LS) -afli $(top_srcdir) | sed 1d | $(AWK) -f "$(srcdir)"/readdir0.awk -v extout=_$@ $(top_srcdir) > $@.ok
-	@-$(CMP) $@.ok _$@ && rm -f $@.ok _$@
+	@$(AWK) -f "$(srcdir)"/readdir.awk "$(top_srcdir)" > _$@
+#	@ls -afi "$(top_srcdir)" > _dirlist
+	@$(LS) -afi "$(top_srcdir)" > _dirlist
+#	@ls -lna "$(top_srcdir)" | sed 1d > _longlist
+	@$(LS) -lna "$(top_srcdir)" | sed 1d > _longlist
+	@$(AWK) -f "$(srcdir)"/readdir0.awk -v extout=_$@  \
+		-v dirlist=_dirlist -v longlist=_longlist > $@.ok
+	@-$(CMP) $@.ok _$@ && rm -f $@.ok _$@ _dirlist _longlist
 
 fts:
-	@if [ "`uname`" = IRIX ];  then \
+	@case `uname` in \
+	IRIX) \
 	echo This test may fail on IRIX systems when run on an NFS filesystem.; \
-	echo If it does, try rerunning on an xfs filesystem. ; \
-	fi
+	echo If it does, try rerunning on an xfs filesystem. ;; \
+	CYGWIN*) \
+	echo This test may fail on CYGWIN systems when run on an NFS filesystem.; \
+	echo If it does, try rerunning on an ntfs filesystem. ;; \
+	esac
 	@echo $@
 	@echo Expect $@ to fail with MinGW because function 'fts' is not defined.
-	@$(AWK) -f "$(srcdir)"/fts.awk
+#	@$(AWK) -f "$(srcdir)"/fts.awk
+	@$(AWK) -f "$(srcdir)"/fts.awk || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) $@.ok _$@ && rm -f $@.ok _$@
 
 charasbytes:
@@ -1098,12 +1118,14 @@ dfamb1:
 
 backbigs1:
 	@echo $@
+	@echo Expect backbigs1 to fail with MinGW and DJGPP
 	@[ -z "$$GAWKLOCALE" ] && GAWKLOCALE=en_US.UTF-8; \
 	AWKPATH="$(srcdir)" $(AWK) -f $@.awk "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 backsmalls1:
 	@echo $@
+	@echo Expect backsmalls1 to fail with MinGW and DJGPP
 	@[ -z "$$GAWKLOCALE" ] && GAWKLOCALE=en_US.UTF-8; \
 	AWKPATH="$(srcdir)" $(AWK) -f $@.awk "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
@@ -1113,7 +1135,6 @@ backsmalls2:
 	@[ -z "$$GAWKLOCALE" ] && GAWKLOCALE=en_US.UTF-8; \
 	AWKPATH="$(srcdir)" $(AWK) -f $@.awk "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
-
 Gt-dummy:
 # file Maketests, generated from Makefile.am by the Gentests program
 addcomma:
@@ -2308,6 +2329,11 @@ sortu:
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+split_after_fpat:
+	@echo $@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 splitarg4:
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
@@ -2471,8 +2497,8 @@ time:
 # Targets generated for other tests:
 
 $(srcdir)/Maketests: $(srcdir)/Makefile.am $(srcdir)/Gentests
-	files=`cd ""$(srcdir)"" && echo *.awk *.in`; \
-	$(AWK) -f "$(srcdir)"/Gentests ""$(srcdir)"/Makefile.am" $$files > "$(srcdir)"/Maketests
+	files=`cd "$(srcdir)" && echo *.awk *.in`; \
+	$(AWK) -f "$(srcdir)"/Gentests "$(srcdir)"/Makefile.am $$files > "$(srcdir)"/Maketests
 
 clean:
 	rm -fr _* core core.* fmtspcl.ok junk strftime.ok test1 test2 \
diff --git a/pc/config.h b/pc/config.h
index a07228c9..c5d78a96 100644
--- a/pc/config.h
+++ b/pc/config.h
@@ -49,9 +49,6 @@
 #define HAVE_DECL_TZNAME 1
 #endif
 
-/* Define to 1 if you don't have `vprintf' but do have `_doprnt.' */
-#undef HAVE_DOPRNT
-
 /* Define to 1 if you have the <fcntl.h> header file. */
 #define HAVE_FCNTL_H 1
 
@@ -372,9 +369,6 @@
 #define HAVE_USLEEP 1
 #endif
 
-/* Define to 1 if you have the `vprintf' function. */
-#define HAVE_VPRINTF 1
-
 /* Define to 1 if you have the <wchar.h> header file. */
 #ifdef __MINGW32__
 #define HAVE_WCHAR_H 1
@@ -429,7 +423,7 @@
 #define PACKAGE_NAME "GNU Awk"
 
 /* Define to the full name and version of this package. */
-#define PACKAGE_STRING "GNU Awk 4.1.0a"
+#define PACKAGE_STRING "GNU Awk 4.1.60"
 
 /* Define to the one symbol short name of this package. */
 #define PACKAGE_TARNAME "gawk"
@@ -438,7 +432,7 @@
 #define PACKAGE_URL "http://www.gnu.org/software/gawk/"
 
 /* Define to the version of this package. */
-#define PACKAGE_VERSION "4.1.0a"
+#define PACKAGE_VERSION "4.1.60"
 
 /* Define to 1 if *printf supports %F format */
 #undef PRINTF_HAS_F_FORMAT
@@ -500,7 +494,7 @@
 
 
 /* Version number of package */
-#define VERSION "4.1.0a"
+#define VERSION "4.1.60"
 
 /* Enable large inode numbers on Mac OS X 10.5.  */
 #ifndef _DARWIN_USE_64_BIT_INODE
diff --git a/pc/popen.c b/pc/popen.c
index 399e250a..73770d98 100644
--- a/pc/popen.c
+++ b/pc/popen.c
@@ -13,7 +13,6 @@
 #define _NFILE 40
 #endif
 
-static char template[] = "piXXXXXX";
 static struct {
   char *command;
   char *name;
@@ -34,6 +33,7 @@ static struct {
 #define WIN32_LEAN_AND_MEAN
 #include <windows.h>
 
+#if 0
 static int
 unixshell(char *p)
 {
@@ -119,20 +119,16 @@ unlink_and_free(char *cmd)
     s = cmd;
   unlink(s); free(cmd);
 }
+#endif
 
 int
 os_system(const char *cmd)
 {
-  char *s;
-  int i;
-  char *cmd1;
+  char *cmdexe = getenv("ComSpec");
+  char *cmd1 = quote_cmd(cmd);
+  int i = spawnl(P_WAIT, cmdexe, "cmd.exe", "/c", cmd1, NULL);
 
-  if ((cmd1 = scriptify(cmd)) == NULL) return(1);
-  if (s = getenv("SHELL"))
-    i = spawnlp(P_WAIT, s, s, cmd1 + strlen(s), NULL);
-  else
-    i = system(cmd1);
-  unlink_and_free(cmd1);
+  free(cmd1);
   return(i);
 }
 
@@ -209,19 +205,15 @@ os_popen(const char *command, const char *mode )
     char *name;
     int cur;
     char curmode[4];
-#if defined(__MINGW32__)
-    char *cmd;
-#endif
 
     if (*mode != 'r' && *mode != 'w')
       return NULL;
     strncpy(curmode, mode, 3); curmode[3] = '\0';
 
 #if defined(__MINGW32__)
-    current = popen(cmd = scriptify(command), mode);
+    current = popen(command, mode);
     cur = fileno(current);
     strcpy(pipes[cur].pmode, curmode);
-    pipes[cur].command = cmd;
     return(current);
 #endif
 
@@ -268,7 +260,6 @@ os_pclose( FILE * current)
 #if defined(__MINGW32__)
     rval = pclose(current);
     *pipes[cur].pmode = '\0';
-    unlink_and_free(pipes[cur].command);
     return rval;
 #endif
 
diff --git a/po/ChangeLog b/po/ChangeLog
index 31d9fa1d..a9cca765 100644
--- a/po/ChangeLog
+++ b/po/ChangeLog
@@ -1,3 +1,7 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
 2013-05-09         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* 4.1.0: Release tar ball made.
diff --git a/po/LINGUAS b/po/LINGUAS
index 3ec9de9d..d00794ef 100644
--- a/po/LINGUAS
+++ b/po/LINGUAS
@@ -1,3 +1,4 @@
+ca
 da
 de
 es
diff --git a/po/ca.gmo b/po/ca.gmo
new file mode 100644
index 00000000..465f05a5
--- /dev/null
+++ b/po/ca.gmo
diff --git a/po/ca.po b/po/ca.po
index d7b6e552..444f09c4 100644
--- a/po/ca.po
+++ b/po/ca.po
@@ -1,14 +1,15 @@
 # translation of gawk.po to Catalan
 # Copyright (C) 2003 Free Software Foundation, Inc.
+# This file is distributed under the same license as the gawk package.
 # Antoni Bella Perez <bella5@teleline.es>, 2003.
-#
+# Walter Garcia-Fontes <walter.garcia@upf.edu>, 2014.
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk 3.1.31\n"
+"Project-Id-Version: gawk 4.1.0b\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2011-03-18 12:00+0200\n"
-"PO-Revision-Date: 2003-05-07 21:13+0100\n"
-"Last-Translator: Antoni Bella Perez <bella5@teleline.es>\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-02-26 20:18+0100\n"
+"Last-Translator: Walter Garcia-Fontes <walter.garcia@upf.edu>\n"
 "Language-Team: Catalan <ca@dodds.net>\n"
 "Language: ca\n"
 "MIME-Version: 1.0\n"
@@ -16,880 +17,1897 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: KBabel 1.0.1\n"
 
-#: array.c:103
-#, fuzzy, c-format
+#: array.c:256
+#, c-format
 msgid "from %s"
-msgstr "%s (de %s)"
+msgstr "de %s"
 
-#: array.c:267
-#, fuzzy
+#: array.c:357
 msgid "attempt to use a scalar value as array"
-msgstr "s'ha intentat usar la dada escalar �%s� com a una matriu"
-
-#: array.c:270
-#, fuzzy, c-format
-msgid "attempt to use function `%s' as an array"
-msgstr "s'ha intentat usar la funci� �%s� com a una matriu"
+msgstr "s'ha intentat usar un valor escalar com a una matriu"
 
-#: array.c:273
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
-msgstr "s'ha intentat usar un par�metre escalar �%s� com a una matriu"
+msgstr "s'ha intentat usar un par�metre escalar `%s' com a una matriu"
 
-#: array.c:276 eval.c:2013
-#, fuzzy, c-format
+#: array.c:362
+#, c-format
 msgid "attempt to use scalar `%s' as an array"
-msgstr "s'ha intentat usar la dada escalar �%s� com a una matriu"
+msgstr "s'ha intentat usar la dada escalar `%s' com a una matriu"
 
-#: array.c:321 array.c:648 builtin.c:75 builtin.c:555 builtin.c:597
-#: builtin.c:610 builtin.c:1016 builtin.c:1028 eval.c:1381 eval.c:1385
-#: eval.c:1710 eval.c:1958 eval.c:2026 eval.c:2274
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
-msgstr "s'ha intentat usar la matriu �%s� en un context escalar"
-
-#: array.c:570
-#, fuzzy, c-format
-msgid "reference to uninitialized element `%s[\"%.*s\"]'"
-msgstr "refer�ncia a un element sense valor inicial �%s[\"%s\"]�"
+msgstr "s'ha intentat usar la matriu `%s' en un context escalar"
 
-#: array.c:576
-#, c-format
-msgid "subscript of array `%s' is null string"
-msgstr "el subscript de la matriu �%s� �s una cadena nul�la"
-
-#: array.c:684
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
-msgstr "delete: l'�ndex �%s� no est� en la matriu �%s�"
-
-#: array.c:708
-#, fuzzy, c-format
-msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
-msgstr "s'ha intentat usar la dada escalar �%s� com a una matriu"
+msgstr "delete: l'�ndex `%s' no est� en la matriu `%s'"
 
-#: array.c:871
+#: array.c:597
 #, c-format
-msgid "%s: empty (null)\n"
-msgstr "%s: buit (nul)\n"
-
-#: array.c:876
-#, c-format
-msgid "%s: empty (zero)\n"
-msgstr "%s: buit (zero)\n"
-
-#: array.c:880
-#, c-format
-msgid "%s: table_size = %d, array_size = %d\n"
-msgstr "%s: mida_taula = %d, mida_matriu = %d\n"
-
-#: array.c:915
-#, fuzzy, c-format
-msgid "%s: is parameter\n"
-msgstr "%s: �s un par�metre\n"
-
-#: array.c:919
-#, c-format
-msgid "%s: array_ref to %s\n"
-msgstr "%s: ref_matriu a %s\n"
-
-#: array.c:924
-#, fuzzy
-msgid "adump: argument not an array"
-msgstr "asort: el primer argument no �s una matriu"
+msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
+msgstr "s'ha intentat usar la dada escalar `%s[\"%.*s\"]' com a una matriu"
 
-#: array.c:1142
-#, fuzzy
-msgid "attempt to use array in a scalar context"
-msgstr "s'ha intentat usar la matriu �%s� en un context escalar"
+#: array.c:776
+msgid "adump: first argument not an array"
+msgstr "adump: el primer argument no �s una matriu"
 
-#: array.c:1239
-#, fuzzy
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: el segon argument no �s una matriu"
 
-#: array.c:1240
-#, fuzzy
+#: array.c:816
 msgid "asorti: second argument not an array"
-msgstr "asort: el segon argument no �s una matriu"
+msgstr "asorti: el segon argument no �s una matriu"
 
-#: array.c:1247
-#, fuzzy
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: el primer argument no �s una matriu"
 
-#: array.c:1248
-#, fuzzy
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asort: el primer argument no �s una matriu"
 
-#: awkgram.y:249
-#, fuzzy, c-format
+#: array.c:831
+msgid "asort: cannot use a subarray of first arg for second arg"
+msgstr ""
+"asort: no es pot usar una submatriu com a primer argument per al segon "
+"argument"
+
+#: array.c:832
+msgid "asorti: cannot use a subarray of first arg for second arg"
+msgstr ""
+"asorti: no es pot usar una submatriu com a primer argument per al segon "
+"argument"
+
+#: array.c:837
+msgid "asort: cannot use a subarray of second arg for first arg"
+msgstr ""
+"asort: no es pot usar una submatriu com a segon argument per al primer "
+"argument"
+
+#: array.c:838
+msgid "asorti: cannot use a subarray of second arg for first arg"
+msgstr ""
+"asorti: no es pot usar una submatriu com a segon argument per al primer "
+"argument"
+
+#: array.c:1314
+#, c-format
+msgid "`%s' is invalid as a function name"
+msgstr "`%s' no �s v�lid com a nom de funci�"
+
+#: array.c:1318
+#, c-format
+msgid "sort comparison function `%s' is not defined"
+msgstr "la funci� de comparaci� d'ordenaci� `%s' no est� definida"
+
+#: awkgram.y:233
+#, c-format
 msgid "%s blocks must have an action part"
-msgstr "Els blocs FINAL han de tindre una part d'acci�"
+msgstr "%s blocs han de tenir una part d'acci�"
 
-#: awkgram.y:252
-#, fuzzy
+#: awkgram.y:236
 msgid "each rule must have a pattern or an action part"
-msgstr "Els blocs FINAL han de tindre una part d'acci�"
+msgstr "cada regla ha de tenir un patr� o una part d'acci�"
 
-#: awkgram.y:323 awkgram.y:334
-#, fuzzy
+#: awkgram.y:325 awkgram.y:336
 msgid "old awk does not support multiple `BEGIN' or `END' rules"
-msgstr "l'antic awk no suporta l'operador �**=�"
+msgstr "l'antic awk no suporta m�ltiples regles `BEGIN' i `END'"
 
-#: awkgram.y:371
+#: awkgram.y:373
 #, c-format
 msgid "`%s' is a built-in function, it cannot be redefined"
-msgstr "�%s� �s una funci� interna, no pot ser redefinida"
+msgstr "`%s' �s una funci� interna, no pot ser redefinida"
 
-#: awkgram.y:432
-#, fuzzy
+#: awkgram.y:419
 msgid "regexp constant `//' looks like a C++ comment, but is not"
 msgstr ""
-"la constant d'expressi� regular �/%s/� sembla un comentari en C, per� no ho "
+"la constant d'expressi� regular `//' sembla un comentari en C++, per� no ho "
 "�s"
 
-#: awkgram.y:436
+#: awkgram.y:423
 #, c-format
 msgid "regexp constant `/%s/' looks like a C comment, but is not"
 msgstr ""
-"la constant d'expressi� regular �/%s/� sembla un comentari en C, per� no ho "
+"la constant d'expressi� regular `/%s/' sembla un comentari en C, per� no ho "
 "�s"
 
-#: awkgram.y:528
+#: awkgram.y:515
 #, c-format
 msgid "duplicate case values in switch body: %s"
-msgstr ""
+msgstr "valors duplicats de casos al cos de l'expressi� switch: %s"
 
-#: awkgram.y:549
+#: awkgram.y:536
 msgid "duplicate `default' detected in switch body"
 msgstr ""
+"s'ha detectat el cas predeterminat `default' duplicat a l'expressi� switch "
 
-#: awkgram.y:811
-#, fuzzy
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
-msgstr "no es permet �break� a fora d'un bucle"
+msgstr "no es permet `break' a fora d'un bucle o bifurcaci�"
 
-#: awkgram.y:820
-#, fuzzy
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
-msgstr "no es permet �continue� a fora d'un bucle"
+msgstr "no es permet `continue' a fora d'un bucle"
 
-#: awkgram.y:829
-#, fuzzy, c-format
+#: awkgram.y:815
+#, c-format
 msgid "`next' used in %s action"
-msgstr "�next� �s usat dintre de l'acci� BEGIN o END"
-
-#: awkgram.y:837
-msgid "`nextfile' is a gawk extension"
-msgstr "�nextfile� �s una extensi� de gawk"
+msgstr "`next' usat a l'acci� %s"
 
-#: awkgram.y:840
-#, fuzzy, c-format
+#: awkgram.y:824
+#, c-format
 msgid "`nextfile' used in %s action"
-msgstr "�next� �s usat dintre de l'acci� BEGIN o END"
+msgstr "`nextfile' usat a l'acci� %s"
 
-#: awkgram.y:863
+#: awkgram.y:848
 msgid "`return' used outside function context"
-msgstr "�return� �s usat fora del context d'una funci�"
+msgstr "`return' �s usat fora del context d'una funci�"
 
-#: awkgram.y:923
+#: awkgram.y:922
 msgid "plain `print' in BEGIN or END rule should probably be `print \"\"'"
 msgstr ""
-"el �print� simple en la regla BEGIN o END probablement ha de ser �print \"\"�"
+"el `print'� simple en la regla BEGIN o END probablement ha de ser `print "
+"\"\"'"
+
+#: awkgram.y:988 awkgram.y:1037
+msgid "`delete' is not allowed with SYMTAB"
+msgstr "no es permet `delete' amb SYMTAB"
 
-#: awkgram.y:993 awkgram.y:997 awkgram.y:1021
-msgid "`delete array' is a gawk extension"
-msgstr "�delete array� �s una extensi� de gawk"
+#: awkgram.y:990 awkgram.y:1039
+msgid "`delete' is not allowed with FUNCTAB"
+msgstr "no es permet `delete' a FUNCTAB"
 
-#: awkgram.y:1017
-#, fuzzy
+#: awkgram.y:1024 awkgram.y:1028
 msgid "`delete(array)' is a non-portable tawk extension"
-msgstr "�delete array� �s una extensi� de gawk"
+msgstr "`delete(array)' �s una extensi� tawk no portable"
 
-#: awkgram.y:1133
+#: awkgram.y:1149
 msgid "multistage two-way pipelines don't work"
 msgstr "les canonades bidireccionals multi-etapes no funcionen"
 
-#: awkgram.y:1236
+#: awkgram.y:1264
 msgid "regular expression on right of assignment"
 msgstr "expressi� regular a la dreta d'una assignaci�"
 
-#: awkgram.y:1247
+#: awkgram.y:1275
 msgid "regular expression on left of `~' or `!~' operator"
-msgstr "expressi� regular a l'esquerra de l'operador �~� o �!~�"
+msgstr "expressi� regular a l'esquerra de l'operador `~' o `!~'"
 
-#: awkgram.y:1263 awkgram.y:1417
-#, fuzzy
+#: awkgram.y:1291 awkgram.y:1442
 msgid "old awk does not support the keyword `in' except after `for'"
-msgstr "l'antic awk no suporta l'operador �**=�"
+msgstr ""
+"l'antic awk no d�na suport a la paraula clau `in' excepte despr�s de `for'"
 
-#: awkgram.y:1273
+#: awkgram.y:1301
 msgid "regular expression on right of comparison"
-msgstr "expressi� regular a la derta de la comparaci�"
+msgstr "expressi� regular a la dreta de la comparaci�"
 
-#: awkgram.y:1392
-#, fuzzy, c-format
+#: awkgram.y:1417
+#, c-format
 msgid "`getline var' invalid inside `%s' rule"
-msgstr "port remot no v�lid en �%s�"
+msgstr "`getline var' no �s v�lid a dins de la regla `%s'"
 
-#: awkgram.y:1395 eval.c:2649
-#, fuzzy, c-format
+#: awkgram.y:1420
+#, c-format
 msgid "`getline' invalid inside `%s' rule"
-msgstr "port remot no v�lid en �%s�"
+msgstr "`getline' no �s v�lid a dins de la regla `%s'"
 
-#: awkgram.y:1400
+#: awkgram.y:1425
 msgid "non-redirected `getline' undefined inside END action"
-msgstr "�getline� no redirigit sense definir dintre de l'acci� FINAL"
+msgstr "`getline' no redirigit sense definir dintre de l'acci� FINAL"
 
-#: awkgram.y:1419
-#, fuzzy
+#: awkgram.y:1444
 msgid "old awk does not support multidimensional arrays"
-msgstr "l'antic awk no suporta l'operador �**=�"
+msgstr "l'antic awk no suporta matrius multidimensionals"
 
-#: awkgram.y:1515
+#: awkgram.y:1541
 msgid "call of `length' without parentheses is not portable"
-msgstr "la crida de �length� sense par�ntesis no �s portable"
+msgstr "la crida de `length' sense par�ntesis no �s portable"
 
-#: awkgram.y:1578
-#, fuzzy
+#: awkgram.y:1607
 msgid "indirect function calls are a gawk extension"
-msgstr "�nextfile� �s una extensi� de gawk"
+msgstr "les crides a funcions indirectes s�n una extensi� gawk"
 
-#: awkgram.y:1591
-#, fuzzy, c-format
+#: awkgram.y:1620
+#, c-format
 msgid "can not use special variable `%s' for indirect function call"
-msgstr "funci� �%s�: no pot usar el nom de la funci� com a par�metre"
+msgstr ""
+"no es pot usar la variable especial `%s' per a una crida indirecta de funci�"
 
-#: awkgram.y:1669
+#: awkgram.y:1698
 msgid "invalid subscript expression"
-msgstr "expressi� de subscript no v�lida"
+msgstr "expressi� de sub�ndex no v�lida"
 
-#: awkgram.y:1709
-msgid "use of non-array as array"
-msgstr ""
-
-#: awkgram.y:1973 awkgram.y:1993 msg.c:98
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
-msgstr "ADVERTIMENT: "
+msgstr "advertiment: "
 
-#: awkgram.y:1991 msg.c:130
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
-msgstr "Fatal: "
+msgstr "fatal: "
 
-#: awkgram.y:2041
-#, fuzzy
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
-msgstr "nova l�nia inesperada"
+msgstr "nova l�nia inesperada o final d'una cadena de car�cters"
 
-#: awkgram.y:2297 awkgram.y:2355 awkgram.y:2539
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
-msgstr "no es pot obrir el fitxer font �%s� per a lectura (%s)"
+msgstr "no es pot obrir el fitxer font `%s' per a lectura (%s)"
+
+#: awkgram.y:2384 awkgram.y:2509
+#, c-format
+msgid "can't open shared library `%s' for reading (%s)"
+msgstr "no es pot obrir la llibreria compartida `%s' per a lectura (%s)"
 
-#: awkgram.y:2298 awkgram.y:2356 builtin.c:119
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "motiu desconegut"
 
-#: awkgram.y:2314
-#, fuzzy, c-format
+#: awkgram.y:2395 awkgram.y:2419
+#, c-format
+msgid "can't include `%s' and use it as a program file"
+msgstr "no es pot incloure `%s' i usar-lo com un fitxer de programa"
+
+#: awkgram.y:2408
+#, c-format
 msgid "already included source file `%s'"
-msgstr "no es pot llegir el fitxer font �%s� (%s)"
+msgstr "ja s'ha incl�s el fitxer font `%s'"
+
+#: awkgram.y:2409
+#, c-format
+msgid "already loaded shared library `%s'"
+msgstr "ja s'ha carregat la biblioteca compartida `%s'"
 
-#: awkgram.y:2340
-#, fuzzy
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
-msgstr "�nextfile� �s una extensi� de gawk"
+msgstr "@include �s una extensi� de gawk"
 
-#: awkgram.y:2346
+#: awkgram.y:2450
 msgid "empty filename after @include"
-msgstr ""
+msgstr "nom de fitxer buit despr�s de @include"
+
+#: awkgram.y:2494
+msgid "@load is a gawk extension"
+msgstr "@load �s una extensi� de gawk"
+
+#: awkgram.y:2500
+msgid "empty filename after @load"
+msgstr "fitxer buit despr�s de @load"
 
-#: awkgram.y:2491
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "el text del programa en la l�nia de comandaments est� buit"
 
-#: awkgram.y:2606
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
-msgstr "no es pot llegir el fitxer font �%s� (%s)"
+msgstr "no es pot llegir el fitxer font `%s' (%s)"
 
-#: awkgram.y:2617
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
-msgstr "el fitxer font �%s� est� buit"
+msgstr "el fitxer font `%s' est� buit"
 
-#: awkgram.y:2802
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "el fitxer font no finalitza amb un retorn de carro"
 
-#: awkgram.y:2879
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
-msgstr "expressi� regular sense finalitzar acaba amb �\\� al final del fitxer"
+msgstr "expressi� regular sense finalitzar acaba amb `\\' al final del fitxer"
 
-#: awkgram.y:2903
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
-msgstr ""
+msgstr "%s: %d: el modificador regex tawk `/.../%c' no funciona a gawk"
 
-#: awkgram.y:2907
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
-msgstr ""
+msgstr "el modificador regex tawk `/.../%c' no funciona a gawk"
 
-#: awkgram.y:2914
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "expressi� regular sense finalitzar"
 
-#: awkgram.y:2918
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "expressi� regular sense finalitzar al final del fitxer"
 
-#: awkgram.y:2977
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
-msgstr "l'�s de �\\ #...� com a continuaci� de l�nia no �s portable"
+msgstr "l'�s de `\\ #...' com a continuaci� de l�nia no �s portable"
 
-#: awkgram.y:2993
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "la barra invertida no �s l'�ltim car�cter en la l�nia"
 
-#: awkgram.y:3054
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
-msgstr "POSIX no permet l'operador �**=�"
+msgstr "POSIX no permet l'operador `**='"
 
-#: awkgram.y:3056
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
-msgstr "l'antic awk no suporta l'operador �**=�"
+msgstr "l'antic awk no suporta l'operador `**='"
 
-#: awkgram.y:3065
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
-msgstr "POSIX no permet l'operador �**�"
+msgstr "POSIX no permet l'operador `**'"
 
-#: awkgram.y:3067
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
-msgstr "l'antic awk no suporta l'operador �**=�"
+msgstr "l'antic awk no suporta l'operador `**='"
 
-#: awkgram.y:3102
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
-msgstr "l'operador �^=� no est� suportat en l'antic awk"
+msgstr "l'operador `^=' no est� suportat en l'antic awk"
 
-#: awkgram.y:3110
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
-msgstr "l'operador �^� no est� suportat en l'antic awk"
+msgstr "l'operador `^' no est� suportat en l'antic awk"
 
-#: awkgram.y:3203 awkgram.y:3219
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "cadena sense finalitzar"
 
-#: awkgram.y:3415
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
-msgstr "car�cter �%c� no v�lid en l'expressi�"
+msgstr "car�cter `%c' no v�lid en l'expressi�"
 
-#: awkgram.y:3462
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
-msgstr "�%s� �s una extensi� de gawk"
-
-#: awkgram.y:3467
-#, c-format
-msgid "`%s' is a Bell Labs extension"
-msgstr "�%s� �s una extensi� de Bell Labs"
+msgstr "`%s' �s una extensi� de gawk"
 
-#: awkgram.y:3472
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX no permet �%s�"
 
-#: awkgram.y:3480
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
-msgstr "�%s� no est� suportat en l'antic awk"
+msgstr "`%s' no est� suportat en l'antic awk"
 
-#: awkgram.y:3550
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
-msgstr "�goto� se considera nefast!\n"
+msgstr "`goto' es considera perjudicial!\n"
 
-#: awkgram.y:3602
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d no �s v�lid com a nombre d'arguments per a %s"
 
-#: awkgram.y:3637 awkgram.y:3640
-msgid "match: third argument is a gawk extension"
-msgstr "match: el tercer argument �s una extensi� de gawk"
-
-#: awkgram.y:3668
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr "%s: la cadena literal com a �ltim argument de substituci� no t� efecte"
 
-#: awkgram.y:3673
-#, fuzzy, c-format
+#: awkgram.y:3827
+#, c-format
 msgid "%s third parameter is not a changeable object"
-msgstr "sub: el tercer argument no �s un objecte intercanviable"
+msgstr "%s el tercer par�metre no �s un objecte intercanviable"
+
+#: awkgram.y:3910 awkgram.y:3913
+msgid "match: third argument is a gawk extension"
+msgstr "match: el tercer argument �s una extensi� de gawk"
 
-#: awkgram.y:3759 awkgram.y:3762
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: el segon argument �s una extensi� de gawk"
 
-#: awkgram.y:3774
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "l'�s de dcgettext(_\"...\") no �s correcte: elimineu el gui� baix inicial"
 
-#: awkgram.y:3789
-#, fuzzy
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "l'�s de dcgettext(_\"...\") no �s correcte: elimineu el gui� baix inicial"
 
-#: awkgram.y:3881
-#, c-format
-msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
-msgstr "funci� �%s�: par�metre #%d, �%s�, duplica al par�metre #%d"
+#: awkgram.y:4016
+msgid "index: regexp constant as second argument is not allowed"
+msgstr "�ndex: no es permet una constant regexp com a segon argument"
 
-#: awkgram.y:3923
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
-msgstr "funci� �%s�: par�metre �%s� ofusca la variable global"
+msgstr "funci� `%s': par�metre `%s' ofusca la variable global"
 
-#: awkgram.y:4081
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
-msgstr "no es pot obrir �%s� per a escriptura (%s)"
+msgstr "no es pot obrir `%s' per a escriptura (%s)"
 
-#: awkgram.y:4082 profile.c:85
-msgid "sending profile to standard error"
-msgstr "enviant el perfil a l'eixida d'error est�ndard"
+#: awkgram.y:4127
+msgid "sending variable list to standard error"
+msgstr "s'est� enviant la llista de variables a l'eixida d'error est�ndard"
 
-#: awkgram.y:4088
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: tancament erroni (%s)"
 
-#: awkgram.y:4140
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
-msgstr "shadow_funcs() crida dos vegades!"
+msgstr "shadow_funcs() s'ha cridat dues vegades!"
 
-#: awkgram.y:4146
+#: awkgram.y:4168
 msgid "there were shadowed variables."
-msgstr ""
+msgstr "hi ha hagut variables a l'ombra"
+
+#: awkgram.y:4239
+#, c-format
+msgid "function name `%s' previously defined"
+msgstr "nom de la funci� `%s' definida pr�viament"
 
-#: awkgram.y:4176
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
-msgstr "funci� �%s�: no pot usar el nom de la funci� com a par�metre"
+msgstr "funci� `%s�: no pot usar el nom de la funci� com a par�metre"
 
-#: awkgram.y:4180
-#, fuzzy, c-format
+#: awkgram.y:4288
+#, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
-msgstr "funci� �%s�: no pot usar el nom de la funci� com a par�metre"
+msgstr ""
+"funci� `%s': no es pot usar la variable especial `%s' com a un par�metre de "
+"funci�"
 
-#: awkgram.y:4196
+#: awkgram.y:4296
 #, c-format
-msgid "function name `%s' previously defined"
-msgstr "nom de la funci� �%s� definida pr�viament"
+msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
+msgstr "funci� `%s': par�metre #%d, `%s', duplica al par�metre #%d"
 
-#: awkgram.y:4364 awkgram.y:4370
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
-msgstr "es crida a la funci� �%s� per� no s'ha definit"
+msgstr "es crida a la funci� `%s' per� no s'ha definit"
 
-#: awkgram.y:4373
-#, fuzzy, c-format
+#: awkgram.y:4393
+#, c-format
 msgid "function `%s' defined but never called directly"
-msgstr "es defineix la funci� �%s� per� no s'ha cridat mai"
+msgstr "la funci� `%s' est� definida per� no s'ha cridat mai directament"
 
-#: awkgram.y:4405
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr ""
 "l'expressi� regular constant per al par�metre #%d condueix a un valor boole�"
 
-#: awkgram.y:4514
-#, fuzzy, c-format
+#: awkgram.y:4484
+#, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
 "or used as a variable or an array"
 msgstr ""
-"s'ha cridat a la funci� �%s� amb espai entre el nom i el �(�,\n"
-"%s"
+"s'ha cridat a la funci� `%s' amb espai entre el nom i el '(',\n"
+"o s'ha usat com a variable o matriu"
 
-#: awkgram.y:4761 eval.c:2206
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "s'ha intentat una divisi� per zero"
 
-#: awkgram.y:4770 eval.c:2222
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
-msgstr "s'ha intentat una divisi� per zero en �%%�"
+msgstr "s'ha intentat una divisi� per zero en `%%'"
+
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+"no es pot assignar un valor al resultat d'una expressi� post-increment de "
+"camp"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "dest� no v�lid d'assignaci� (opcode %s)"
 
-#: builtin.c:117
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s a \"%s\" ha fallat (%s)"
 
-#: builtin.c:118
+#: builtin.c:134
 msgid "standard output"
-msgstr "eixida est�ndard"
+msgstr "sortida est�ndard"
 
-#: builtin.c:132
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: s'ha rebut un argument que no �s un n�mero"
 
-#: builtin.c:138
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: l'argument %g est� fora de rang"
 
-#: builtin.c:197
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
-"fflush: no es pot netejar: la canonada �%s� s'ha obert per a lectura, no per "
+"fflush: no es pot netejar: la canonada `%s' s'ha obert per a lectura, no per "
 "a escriptura"
 
-#: builtin.c:200
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
-"fflush: no es pot netejar: el fitxer �%s� s'ha obert per a lectura, no per a "
+"fflush: no es pot netejar: el fitxer `%s' s'ha obert per a lectura, no per a "
 "escriptura"
 
-#: builtin.c:212
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
-msgstr "fflush: �%s� no �s un fitxer obert, canonada o co-proc�s"
+msgstr "fflush: `%s' no �s un fitxer obert, canonada o co-proc�s"
 
-#: builtin.c:330
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "�ndex: el primer argument rebut no �s una cadena"
 
-#: builtin.c:332
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "�ndex: el segon argument rebut no �s una cadena"
 
-#: builtin.c:454
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: s'ha rebut un argument no num�ric"
 
-#: builtin.c:490
-#, fuzzy
+#: builtin.c:525
 msgid "length: received array argument"
-msgstr "length: s'ha rebut un argument que no �s una cadena"
+msgstr "length: s'ha rebut un argument de matriu"
 
-#: builtin.c:493
-#, fuzzy
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
-msgstr "�delete array� �s una extensi� de gawk"
+msgstr "`length(array)' �s una extensi� de gawk"
 
-#: builtin.c:501
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: s'ha rebut un argument que no �s una cadena"
 
-#: builtin.c:532
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: s'ha rebut un argument no num�ric"
 
-#: builtin.c:535
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: s'ha rebut l'argument negatiu %g"
 
-#: builtin.c:593 builtin.c:604
+#: builtin.c:776 builtin.c:781
+msgid "fatal: must use `count$' on all formats or none"
+msgstr "fatal: s'ha d'usar `count$' a tots els format o a cap"
+
+#: builtin.c:851
+#, c-format
+msgid "field width is ignored for `%%' specifier"
+msgstr "l'amplada de camp s'ignorar� per a l'especificador `%%'"
+
+#: builtin.c:853
+#, c-format
+msgid "precision is ignored for `%%' specifier"
+msgstr "la precisi� s'ignorar� per a l'especificador `%%'"
+
+#: builtin.c:855
+#, c-format
+msgid "field width and precision are ignored for `%%' specifier"
+msgstr "l'amplada de camp i la precisi� s'ignoraran per a l'especificador `%%'"
+
+#: builtin.c:906
+msgid "fatal: `$' is not permitted in awk formats"
+msgstr "fatal: no es permeten `$' en els formats awk"
+
+#: builtin.c:915
+msgid "fatal: arg count with `$' must be > 0"
+msgstr "fatal: el recompte d'arguments amb `$' ha de ser > 0"
+
+#: builtin.c:919
+#, c-format
+msgid "fatal: arg count %ld greater than total number of supplied arguments"
+msgstr ""
+"fatal: el recompte d'arguments %ld �s major que el nombre total d'arguments "
+"proporcionats"
+
+#: builtin.c:923
+msgid "fatal: `$' not permitted after period in format"
+msgstr "fatal: no es permet `$' despr�s d'un punt en el format"
+
+#: builtin.c:939
+msgid "fatal: no `$' supplied for positional field width or precision"
+msgstr ""
+"fatal: no es proporciona `$' per a l'ample o precisi� del camp de posici�"
+
+#: builtin.c:1009
+msgid "`l' is meaningless in awk formats; ignored"
+msgstr "`l' manca de significat en els formats awk; ser� ignorat"
+
+#: builtin.c:1013
+msgid "fatal: `l' is not permitted in POSIX awk formats"
+msgstr "fatal: `l' no est� perm�s en els formats POSIX de awk"
+
+#: builtin.c:1026
+msgid "`L' is meaningless in awk formats; ignored"
+msgstr "`L' manca de significat en els formats awk; ser� ignorat"
+
+#: builtin.c:1030
+msgid "fatal: `L' is not permitted in POSIX awk formats"
+msgstr "fatal: `L' no est� perm�s en els formats POSIX de awk"
+
+#: builtin.c:1043
+msgid "`h' is meaningless in awk formats; ignored"
+msgstr "`h' manca de significat en els formats awk; ser� ignorat"
+
+#: builtin.c:1047
+msgid "fatal: `h' is not permitted in POSIX awk formats"
+msgstr "fatal: `h' no est� perm�s en els formats POSIX de awk"
+
+#: builtin.c:1463
+#, c-format
+msgid "[s]printf: value %g is out of range for `%%%c' format"
+msgstr "[s]printf: el valor %g est� fora de rang per al format `%%%c'"
+
+#: builtin.c:1561
+#, c-format
+msgid "ignoring unknown format specifier character `%c': no argument converted"
+msgstr ""
+"s'ignorar� el car�cter especificador de format `%c': no s'ha convertit cap "
+"argument"
+
+#: builtin.c:1566
+msgid "fatal: not enough arguments to satisfy format string"
+msgstr "fatal: no hi ha prou arguments per a satisfer el format d'una cadena"
+
+#: builtin.c:1568
+msgid "^ ran out for this one"
+msgstr "^ desbordament per a aquest"
+
+#: builtin.c:1575
+msgid "[s]printf: format specifier does not have control letter"
+msgstr "[s]printf: l'especificador de format no cont� lletra de control"
+
+#: builtin.c:1578
+msgid "too many arguments supplied for format string"
+msgstr "s'han proporcionat masses arguments per a la cadena de format"
+
+#: builtin.c:1634
+msgid "sprintf: no arguments"
+msgstr "sprintf: sense arguments"
+
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: sense arguments"
 
-#: builtin.c:645
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: s'ha rebut un argument no num�ric"
 
-#: builtin.c:649
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: cridat amb l'argument negatiu %g"
 
-#: builtin.c:673
-#, fuzzy, c-format
+#: builtin.c:1746
+#, c-format
 msgid "substr: length %g is not >= 1"
-msgstr "substr: la longitud %g �s <= 0"
+msgstr "substr: la longitud %g no �s >= 1"
 
-#: builtin.c:675
-#, fuzzy, c-format
+#: builtin.c:1748
+#, c-format
 msgid "substr: length %g is not >= 0"
-msgstr "substr: la longitud %g �s <= 0"
+msgstr "substr: la longitud %g no �s >= 0"
 
-#: builtin.c:682
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: la longitud sobre un nombre no enter %g ser� truncada"
 
-#: builtin.c:687
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr ""
+"substr: la llargada %g �s massa gran per a la indexaci� de cadenes de "
+"car�cters, es truncar� a %g"
 
-#: builtin.c:699
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: l'�ndex d'inici %g no �s v�lid, usant 1"
 
-#: builtin.c:704
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: l'�ndex d'inici no enter %g ser� truncat"
 
-#: builtin.c:729
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: la cadena font �s de longitud zero"
 
-#: builtin.c:745
-#, fuzzy, c-format
+#: builtin.c:1818
+#, c-format
 msgid "substr: start index %g is past end of string"
-msgstr "substr: l'�ndex d'inici %d sobrepassa l'acabament de la cadena"
+msgstr "substr: l'�ndex d'inici %g sobrepassa l'acabament de la cadena"
 
-#: builtin.c:753
-#, fuzzy, c-format
+#: builtin.c:1826
+#, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
 msgstr ""
-"substr: la longitud %d a l'�ndex d'inici %d excedeix la longitud del 1er "
-"argument (%d)"
+"substr: la longitud %g a l'�ndex d'inici %g excedeix la longitud del primer "
+"argument (%lu)"
 
-#: builtin.c:826
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
-msgstr ""
+msgstr "strftime: el valor de format a PROCINFO[\"strftime\"] t� tipus num�ric"
 
-#: builtin.c:840
-#, fuzzy
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
-msgstr "strftime: el segon argument rebut no �s num�ric"
+msgstr "strftime: s'ha rebut un segon argument no num�ric"
+
+#: builtin.c:1927
+msgid "strftime: second argument less than 0 or too big for time_t"
+msgstr ""
+"strftime: el segon argument �s m�s petit que 0 o massa gran per a time_t"
 
-#: builtin.c:847
-#, fuzzy
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: el primer argument rebut no �s una cadena"
 
-#: builtin.c:853
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: s'ha rebut una cadena de format buida"
 
-#: builtin.c:919
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: s'ha rebut un argument que no �s una cadena"
 
-#: builtin.c:936
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
-msgstr ""
+msgstr "mktime: almenys un dels valors est� forra del rang predeterminat"
 
-#: builtin.c:971
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
-msgstr ""
+msgstr "la funci� 'system' no es permet fora del mode entorn de proves"
 
-#: builtin.c:976
-#, fuzzy
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: s'ha rebut un argument que no �s una cadena"
 
-#: builtin.c:1031 eval.c:1411 eval.c:1936 eval.c:1949
+#: builtin.c:2184
 #, c-format
-msgid "reference to uninitialized variable `%s'"
-msgstr "refer�ncia a una variable sense inicialitzar �%s�"
-
-#: builtin.c:1098
-#, fuzzy, c-format
 msgid "reference to uninitialized field `$%d'"
-msgstr "refer�ncia a una variable sense inicialitzar �%s�"
+msgstr "refer�ncia a una variable sense inicialitzar `$%d'"
 
-#: builtin.c:1185
-#, fuzzy
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: s'ha rebut un argument que no �s una cadena"
 
-#: builtin.c:1219
-#, fuzzy
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: s'ha rebut un argument que no �s una cadena"
 
-#: builtin.c:1255
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: el primer argument rebut no �s num�ric"
 
-#: builtin.c:1257
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: el segon argument rebut no �s num�ric"
 
-#: builtin.c:1276
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: s'ha rebut un argument que no �s num�ric"
 
-#: builtin.c:1292
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: s'ha rebut un argument que no �s num�ric"
 
-#: builtin.c:1345
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: s'ha rebut un argument que no �s num�ric"
 
-#: builtin.c:1376
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: el tercer argument no �s una matriu"
 
-#: builtin.c:1883
-#, fuzzy
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: el tercer argument de 0 �s tractat com a 1"
 
-#: builtin.c:1923
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: el primer argument rebut no �s num�ric"
 
-#: builtin.c:1925
-#, fuzzy
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
-msgstr "atan2: el segon argument rebut no �s num�ric"
+msgstr "lshift: el segon argument rebut no �s num�ric"
 
-#: builtin.c:1931
+#: builtin.c:3038
 #, c-format
-msgid "lshift(%lf, %lf): negative values will give strange results"
-msgstr "lshift(%lf, %lf): els valors negatius donaran resultats estranys"
+msgid "lshift(%f, %f): negative values will give strange results"
+msgstr "lshift(%f, %f): els valors negatius donaran resultats estranys"
 
-#: builtin.c:1933
+#: builtin.c:3040
 #, c-format
-msgid "lshift(%lf, %lf): fractional values will be truncated"
-msgstr "lshift(%lf, %lf): els valors fraccionaris sernn truncats"
+msgid "lshift(%f, %f): fractional values will be truncated"
+msgstr "lshift(%f, %f): els valors fraccionaris sernn truncats"
 
-#: builtin.c:1935
+#: builtin.c:3042
 #, c-format
-msgid "lshift(%lf, %lf): too large shift value will give strange results"
+msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr ""
-"lshift(%lf, %lf): un valor de despla�ament massa gran donar� resultats "
-"estranys"
+"lshift(%f, %f): un valor de despla�ament massa gran donar� resultats estranys"
 
-#: builtin.c:1960
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: el primer argument rebut no �s num�ric"
 
-#: builtin.c:1962
-#, fuzzy
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
-msgstr "atan2: el segon argument rebut no �s num�ric"
+msgstr "rshift: el segon argument rebut no �s num�ric"
 
-#: builtin.c:1968
+#: builtin.c:3075
 #, c-format
-msgid "rshift(%lf, %lf): negative values will give strange results"
-msgstr "rshift(%lf, %lf): els valors negatius donaran resultats estranys"
+msgid "rshift(%f, %f): negative values will give strange results"
+msgstr "rshift(%f, %f): els valors negatius donaran resultats estranys"
 
-#: builtin.c:1970
+#: builtin.c:3077
 #, c-format
-msgid "rshift(%lf, %lf): fractional values will be truncated"
-msgstr "rshift(%lf, %lf): els valors fraccionaris seran truncats"
+msgid "rshift(%f, %f): fractional values will be truncated"
+msgstr "rshift(%f, %f): els valors fraccionaris seran truncats"
 
-#: builtin.c:1972
+#: builtin.c:3079
 #, c-format
-msgid "rshift(%lf, %lf): too large shift value will give strange results"
+msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
-"rshift(%lf, %lf): un valor de despla�ament massa gran donar� resultats "
-"estranys"
+"rshift(%f, %f): un valor de despla�ament massa gran donar� resultats estranys"
 
-#: builtin.c:1997
-msgid "and: received non-numeric first argument"
-msgstr "and: el primer argument rebut no �s num�ric"
-
-#: builtin.c:1999
-#, fuzzy
-msgid "and: received non-numeric second argument"
-msgstr "atan2: el segon argument rebut no �s num�ric"
+#: builtin.c:3104 mpfr.c:968
+msgid "and: called with less than two arguments"
+msgstr "and: cridat amb menys de dos arguments"
 
-#: builtin.c:2005
+#: builtin.c:3109
 #, c-format
-msgid "and(%lf, %lf): negative values will give strange results"
-msgstr "and(%lf, %lf): els valors negatius donaran resultats estranys"
+msgid "and: argument %d is non-numeric"
+msgstr "exp: l'argument %d no �s num�ric"
 
-#: builtin.c:2007
+#: builtin.c:3113
 #, c-format
-msgid "and(%lf, %lf): fractional values will be truncated"
-msgstr "and(%lf, %lf): els valors fraccionaris seran truncats"
-
-#: builtin.c:2032
-msgid "or: received non-numeric first argument"
-msgstr "or: el primer argument rebut no �s num�ric"
+msgid "and: argument %d negative value %g will give strange results"
+msgstr "and: l'argument %d amb valor negatiu %g donar� resultats estranys"
 
-#: builtin.c:2034
-#, fuzzy
-msgid "or: received non-numeric second argument"
-msgstr "atan2: el segon argument rebut no �s num�ric"
+#: builtin.c:3136 mpfr.c:1000
+msgid "or: called with less than two arguments"
+msgstr "or: cridat amb menys de dos arguments"
 
-#: builtin.c:2040
+#: builtin.c:3141
 #, c-format
-msgid "or(%lf, %lf): negative values will give strange results"
-msgstr "or(%lf, %lf): els valors negatius donaran resultats estranys"
+msgid "or: argument %d is non-numeric"
+msgstr "or: l'argument %d no �s num�ric"
 
-#: builtin.c:2042
+#: builtin.c:3145
 #, c-format
-msgid "or(%lf, %lf): fractional values will be truncated"
-msgstr "or(%lf, %lf): els valors fraccionaris seran truncats"
-
-#: builtin.c:2070
-msgid "xor: received non-numeric first argument"
-msgstr "xor: el primer argument rebut no �s num�ric"
+msgid "or: argument %d negative value %g will give strange results"
+msgstr "or: l'argument %d amb valor negatiu %g donar� resultats estranys"
 
-#: builtin.c:2072
-#, fuzzy
-msgid "xor: received non-numeric second argument"
-msgstr "atan2: el segon argument rebut no �s num�ric"
+#: builtin.c:3167 mpfr.c:1031
+msgid "xor: called with less than two arguments"
+msgstr "xort: cridat amb menys de dos arguments"
 
-#: builtin.c:2078
+#: builtin.c:3173
 #, c-format
-msgid "xor(%lf, %lf): negative values will give strange results"
-msgstr "xor(%lf, %lf): els valors negatius donaran resultats estranys"
+msgid "xor: argument %d is non-numeric"
+msgstr "xor: l'argument %d no �s num�ric"
 
-#: builtin.c:2080
+#: builtin.c:3177
 #, c-format
-msgid "xor(%lf, %lf): fractional values will be truncated"
-msgstr "xor(%lf, %lf): els valors fraccionaris seran truncats"
+msgid "xor: argument %d negative value %g will give strange results"
+msgstr "xor: l'argument %d del valor negatiu %g donar� resultats estranys"
 
-#: builtin.c:2104 builtin.c:2110
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: s'ha rebut un argument que no �s num�ric"
 
-#: builtin.c:2112
+#: builtin.c:3208
 #, c-format
-msgid "compl(%lf): negative value will give strange results"
-msgstr "compl(%lf): el valor negatiu donar� resultats estranys"
+msgid "compl(%f): negative value will give strange results"
+msgstr "compl(%f): el valor negatiu donar� resultats estranys"
 
-#: builtin.c:2114
+#: builtin.c:3210
 #, c-format
-msgid "compl(%lf): fractional value will be truncated"
-msgstr "compl(%lf): el valor fraccionari ser� truncat"
+msgid "compl(%f): fractional value will be truncated"
+msgstr "compl(%f): el valor fraccionari ser� truncat"
 
-#: builtin.c:2283
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
-msgstr "dcgettext: �%s� no �s una categoria local v�lida"
+msgstr "dcgettext: `%s' no �s una categoria local v�lida"
+
+#: command.y:225
+#, c-format
+msgid "Type (g)awk statement(s). End with the command \"end\"\n"
+msgstr "Escriviu proposici�(ns) g(awk). Termineu amb la instrucci� \"end\"\n"
+
+#: command.y:289
+#, c-format
+msgid "invalid frame number: %d"
+msgstr "n�mero inv�lid de marc: %d"
+
+#: command.y:295
+#, c-format
+msgid "info: invalid option - \"%s\""
+msgstr "info: opci� no v�lida - \"%s\""
+
+#: command.y:321
+#, c-format
+msgid "source \"%s\": already sourced."
+msgstr "source \"%s\": ja s'ha utilitzat."
+
+#: command.y:326
+#, c-format
+msgid "save \"%s\": command not permitted."
+msgstr "save \"%s\": ordre no permesa."
+
+#: command.y:339
+msgid "Can't use command `commands' for breakpoint/watchpoint commands"
+msgstr ""
+"No es pot usar l'ordre `commands' per a ordres de punt d'interrupci�/"
+"inspecci�"
+
+#: command.y:341
+msgid "no breakpoint/watchpoint has been set yet"
+msgstr "no s'ha establert encara cap punt d'interrupci�/verificaci�"
+
+#: command.y:343
+msgid "invalid breakpoint/watchpoint number"
+msgstr "n�mero de punt d'interrupci�/inspecci� no v�lid"
+
+#: command.y:348
+#, c-format
+msgid "Type commands for when %s %d is hit, one per line.\n"
+msgstr "Escriviu les ordres per a quan s'assoleix %s %d, una per l�nia.\n"
+
+#: command.y:350
+#, c-format
+msgid "End with the command \"end\"\n"
+msgstr "Termineu amb l'ordre \"end\"\n"
+
+#: command.y:357
+msgid "`end' valid only in command `commands' or `eval'"
+msgstr "`end' �s v�lid sols a les ordres `commands' o `eval'"
+
+#: command.y:367
+msgid "`silent' valid only in command `commands'"
+msgstr "`silent' �s v�lid sols a l'ordre `commands'"
+
+#: command.y:373
+#, c-format
+msgid "trace: invalid option - \"%s\""
+msgstr "tra�: opci� no v�lida - \"%s\""
+
+#: command.y:387
+msgid "condition: invalid breakpoint/watchpoint number"
+msgstr "condici�: n�mero de punt d'interrupci�/inspecci� no v�lid"
+
+#: command.y:449
+msgid "argument not a string"
+msgstr "l'argument no �s una cadena de car�cters"
+
+#: command.y:459 command.y:464
+#, c-format
+msgid "option: invalid parameter - \"%s\""
+msgstr "opci�: par�metre no v�lid - \"%s\""
+
+#: command.y:474
+#, c-format
+msgid "no such function - \"%s\""
+msgstr "no existeix aquesta funci� - \"%s\""
+
+#: command.y:531
+#, c-format
+msgid "enable: invalid option - \"%s\""
+msgstr "enable: opci� no v�lida - \"%s\""
+
+#: command.y:597
+#, c-format
+msgid "invalid range specification: %d - %d"
+msgstr "especificaci� no v�lida de rang: %d - %d"
+
+#: command.y:659
+msgid "non-numeric value for field number"
+msgstr "valor no num�ric per al n�mero de camp"
+
+#: command.y:680 command.y:687
+msgid "non-numeric value found, numeric expected"
+msgstr "s'ha trobat un valor no num�ric, s'esperava un valor num�ric"
+
+#: command.y:712 command.y:718
+msgid "non-zero integer value"
+msgstr "valor enter no zero"
+
+#: command.y:817
+msgid ""
+"backtrace [N] - print trace of all or N innermost (outermost if N < 0) "
+"frames."
+msgstr ""
+"backtrace [N] - imprimeix la tra�a de tot els N marcs interiors (exteriors "
+"si N < 0)."
+
+#: command.y:819
+msgid ""
+"break [[filename:]N|function] - set breakpoint at the specified location."
+msgstr ""
+"break [[fitxer:]N|funci�] - estableix el punt d'interrupci� a la ubicaci� "
+"especificada."
+
+#: command.y:821
+msgid "clear [[filename:]N|function] - delete breakpoints previously set."
+msgstr ""
+"clear [[fitxer:]N|funci�] - suprimeix els punts  establerts pr�viament."
+
+#: command.y:823
+msgid ""
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
+msgstr ""
+"commands [num] - inicia una llista d'ordres a executar quan s'arribi a un "
+"punt d'interrupci�/inspecci�."
+
+#: command.y:825
+msgid "condition num [expr] - set or clear breakpoint or watchpoint condition."
+msgstr ""
+"condition num [expr] - estableix o neteja una condici� de punt d'interrupci� "
+"o d'inspecci�."
+
+#: command.y:827
+msgid "continue [COUNT] - continue program being debugged."
+msgstr "continue [RECOMPTE] - continua el programa que s'est� depurant."
+
+#: command.y:829
+msgid "delete [breakpoints] [range] - delete specified breakpoints."
+msgstr ""
+"delete [punts d'interrupci�] [rang] - esborra els punts d'interrupci� "
+"especificats."
+
+#: command.y:831
+msgid "disable [breakpoints] [range] - disable specified breakpoints."
+msgstr ""
+"disable [punts d'interrupci�] [rang] - deshabilita els punts d'interrupci� "
+"especificats."
+
+#: command.y:833
+msgid "display [var] - print value of variable each time the program stops."
+msgstr ""
+"display [var] - imprimeix el valor de la variable cada cop que el programa "
+"s'atura"
+
+#: command.y:835
+msgid "down [N] - move N frames down the stack."
+msgstr "down [N] - mou N marcs cap a baix a la pila."
+
+#: command.y:837
+msgid "dump [filename] - dump instructions to file or stdout."
+msgstr ""
+"dump [filename] - aboca les instruccions a un fitxer o a la sortida "
+"est�ndard."
+
+#: command.y:839
+msgid "enable [once|del] [breakpoints] [range] - enable specified breakpoints."
+msgstr ""
+"enable [once|del] [punts d'interrupci�] [rang] - habilita els punts "
+"d'interrupci� especificats."
+
+#: command.y:841
+msgid "end - end a list of commands or awk statements."
+msgstr "end - finalitza una llista de ordres o declaracions awk."
+
+#: command.y:843
+msgid "eval stmt|[p1, p2, ...] - evaluate awk statement(s)."
+msgstr "eval stmt|[p1, p2, ...] - avalua la(es) declaraci�(ns) awk."
+
+#: command.y:845
+msgid "finish - execute until selected stack frame returns."
+msgstr ""
+"finish - executa fins que hi hagi un retorn del marc de pila seleccionat."
+
+#: command.y:847
+msgid "frame [N] - select and print stack frame number N."
+msgstr "frame [N] - selecciona i imprimeix el  marc de pila amb n�mero N."
+
+#: command.y:849
+msgid "help [command] - print list of commands or explanation of command."
+msgstr "help [ordre] - imprimeix una llista d'ordres o una explica de l'ordre."
+
+#: command.y:851
+msgid "ignore N COUNT - set ignore-count of breakpoint number N to COUNT."
+msgstr ""
+"ignore N RECOMPTE - estableix ignore-count del punt d'interrupci� n�mero N "
+"fins RECOMPTE."
+
+#: command.y:853
+msgid ""
+"info topic - source|sources|variables|functions|break|frame|args|locals|"
+"display|watch."
+msgstr ""
+"info topic - source|sources|variables|functions|break|frame|args|locals|"
+"display|watch."
+
+#: command.y:855
+msgid "list [-|+|[filename:]lineno|function|range] - list specified line(s)."
+msgstr ""
+"list [-|+|[fitxer:]n�mero-de-l�nia|funci�|rang] - fes una llista la(es) "
+"l�nia(es) especificada(es)."
+
+#: command.y:857
+msgid "next [COUNT] - step program, proceeding through subroutine calls."
+msgstr ""
+"next [RECOMPTE] - avan�a el programa pas per pas, tot procedint a trav�s de "
+"les crides de subrutines."
+
+#: command.y:859
+msgid ""
+"nexti [COUNT] - step one instruction, but proceed through subroutine calls."
+msgstr ""
+"nexti [RECOMPTE] - avan�a una instrucci�, per� procedeix a trav�s de crides "
+"de subrutines."
+
+#: command.y:861
+msgid "option [name[=value]] - set or display debugger option(s)."
+msgstr ""
+"option [nom[=valor]] - estableix o mostra la(es) opci�(ns) del depurador."
+
+#: command.y:863
+msgid "print var [var] - print value of a variable or array."
+msgstr "print var [var] - imprimeix el valor de la variable o matriu."
+
+#: command.y:865
+msgid "printf format, [arg], ... - formatted output."
+msgstr "printf format, [arg], ... - sortida amb format."
+
+#: command.y:867
+msgid "quit - exit debugger."
+msgstr "quit - surt del depurador."
+
+#: command.y:869
+msgid "return [value] - make selected stack frame return to its caller."
+msgstr ""
+"return [valor] - fes que el marc seleccionat de pila retorni a l'element que "
+"l'ha cridat."
+
+#: command.y:871
+msgid "run - start or restart executing program."
+msgstr "run - inicia o reinicia el programa que s'est� executant."
+
+#: command.y:874
+msgid "save filename - save commands from the session to file."
+msgstr "save filename - desa les ordres de la sessi� a un fitxer."
+
+#: command.y:877
+msgid "set var = value - assign value to a scalar variable."
+msgstr "set var = valor - assigna un valor a una variable escalar."
+
+#: command.y:879
+msgid ""
+"silent - suspends usual message when stopped at a breakpoint/watchpoint."
+msgstr ""
+"silent - susp�n els missatges habituals quan s'autra a un punt d'interrupci�/"
+"inspecci�."
+
+#: command.y:881
+msgid "source file - execute commands from file."
+msgstr "source file - executa una ordre des d'un fitxer."
+
+#: command.y:883
+msgid "step [COUNT] - step program until it reaches a different source line."
+msgstr ""
+"step [RECOMPTE] - avan�a pas per pas pel programa fins que arribi a una "
+"l�nia diferent de la font."
+
+#: command.y:885
+msgid "stepi [COUNT] - step one instruction exactly."
+msgstr "stepi [RECOMPTE] - avan�a exactament una instrucci�."
+
+#: command.y:887
+msgid "tbreak [[filename:]N|function] - set a temporary breakpoint."
+msgstr ""
+"tbreak [[fitxer:]N|funci�] - estableix un punt temporari d'interrupci�."
+
+#: command.y:889
+msgid "trace on|off - print instruction before executing."
+msgstr "trace on|off - imprimeix la instrucci� abans d'executar-la."
+
+#: command.y:891
+msgid "undisplay [N] - remove variable(s) from automatic display list."
+msgstr ""
+"undisplay [N] - remou la(es) variable(s) de la llista autom�tica  "
+"visualitzaci�."
+
+#: command.y:893
+msgid ""
+"until [[filename:]N|function] - execute until program reaches a different "
+"line or line N within current frame."
+msgstr ""
+"until [[fitxer:]N|funci�] - executa fins que el programa arribi a una l�nia "
+"diferent a la l�nia N dins del marc actual."
+
+#: command.y:895
+msgid "unwatch [N] - remove variable(s) from watch list."
+msgstr "unwatch [N] - remou la(es) variable(s) de la llista d'inspecci�."
+
+#: command.y:897
+msgid "up [N] - move N frames up the stack."
+msgstr "up [N] - mou-te N marcs cap a dalt de la pila."
+
+#: command.y:899
+msgid "watch var - set a watchpoint for a variable."
+msgstr "watch var - estableix un punt d'inspecci� per a una variable."
+
+#: command.y:1011 debug.c:401 msg.c:135
+#, c-format
+msgid "error: "
+msgstr "error: "
+
+#: command.y:1051
+#, c-format
+msgid "can't read command (%s)\n"
+msgstr "no es pot llegir l'ordre (%s)\n"
+
+#: command.y:1065
+#, c-format
+msgid "can't read command (%s)"
+msgstr "no es pot llegir l'ordre (%s)"
+
+#: command.y:1116
+msgid "invalid character in command"
+msgstr "car�cter no v�lida en la instucci�"
+
+#: command.y:1152
+#, c-format
+msgid "unknown command - \"%.*s\", try help"
+msgstr "ordre desconeguda - \"%.*s\", prova l'ajuda"
+
+#: command.y:1222
+#, c-format
+msgid "%s"
+msgstr "%s"
+
+#: command.y:1284
+msgid "invalid character"
+msgstr "car�cter no v�lid"
+
+#: command.y:1455
+#, c-format
+msgid "undefined command: %s\n"
+msgstr "ordre no definida: %s\n"
+
+#: debug.c:252
+msgid "set or show the number of lines to keep in history file."
+msgstr ""
+"estableix o mostra el n�mero de l�nies a mantenir al fitxer d'hist�ria."
+
+#: debug.c:254
+msgid "set or show the list command window size."
+msgstr "estableix o mostra la mida de la finestra de llista d'ordres."
+
+#: debug.c:256
+msgid "set or show gawk output file."
+msgstr "estableix o mostra el fitxer de sortida gawk."
+
+#: debug.c:258
+msgid "set or show debugger prompt."
+msgstr "estableix o mostra l'indicador del depurador."
+
+#: debug.c:260
+msgid "(un)set or show saving of command history (value=on|off)."
+msgstr ""
+"estableix(anul�la) o mostra el desament de la hist�ria d'ordres (valor=on|"
+"off)."
+
+#: debug.c:262
+msgid "(un)set or show saving of options (value=on|off)."
+msgstr "estableix(anul�la) o mostra el desament d'opcions (valor=on|off)."
+
+#: debug.c:264
+msgid "(un)set or show instruction tracing (value=on|off)."
+msgstr ""
+"estableix(anul�la) o mostra el seguiment d'instruccions (valor=on|off)."
+
+#: debug.c:345
+msgid "program not running."
+msgstr "el programa no s'est� executant."
+
+#: debug.c:448 debug.c:606
+#, c-format
+msgid "can't read source file `%s' (%s)"
+msgstr "no es pot llegir el fitxer font `%s' (%s)"
+
+#: debug.c:453
+#, c-format
+msgid "source file `%s' is empty.\n"
+msgstr "el fitxer font `%s' est� buit\n"
+
+#: debug.c:480
+msgid "no current source file."
+msgstr "no hi ha un fitxer font."
+
+#: debug.c:505
+#, c-format
+msgid "cannot find source file named `%s' (%s)"
+msgstr "no es pot trobar el fitxer font `%s' (%s)"
+
+#: debug.c:529
+#, c-format
+msgid "WARNING: source file `%s' modified since program compilation.\n"
+msgstr ""
+"ADVERTIMENT: el fitxer font `%s' s'ha modificat des de la compilaci� del "
+"programa.\n"
+
+#: debug.c:551
+#, c-format
+msgid "line number %d out of range; `%s' has %d lines"
+msgstr "l�nia n�mero %d fora de rang; `%s' t� %d l�nies"
+
+#: debug.c:611
+#, c-format
+msgid "unexpected eof while reading file `%s', line %d"
+msgstr ""
+"final de fitxer no esperat quan s'estava llegint el fitxer `%s', l�nia %d"
+
+#: debug.c:620
+#, c-format
+msgid "source file `%s' modified since start of program execution"
+msgstr ""
+"el fitxer font `%s' s'ha modificat des de l'inici de l'execuci� del programa"
+
+#: debug.c:732
+#, c-format
+msgid "Current source file: %s\n"
+msgstr "Fitxer font actual: %s\n"
+
+#: debug.c:733
+#, c-format
+msgid "Number of lines: %d\n"
+msgstr "Nombre de l�nies: %d\n"
+
+#: debug.c:740
+#, c-format
+msgid "Source file (lines): %s (%d)\n"
+msgstr "Fitxer font (l�nies): %s (%d)\n"
+
+#: debug.c:754
+msgid ""
+"Number  Disp  Enabled  Location\n"
+"\n"
+msgstr ""
+"Ubicaci� habilitada per n�mero disp\n"
+"\n"
+
+#: debug.c:765
+#, c-format
+msgid "\tno of hits = %ld\n"
+msgstr "\tn�mero de accessos = %ld\n"
+
+#: debug.c:767
+#, c-format
+msgid "\tignore next %ld hit(s)\n"
+msgstr "\tignora el(s) pr�xim(s) %ld acc�s(sos)\n"
+
+#: debug.c:769 debug.c:909
+#, c-format
+msgid "\tstop condition: %s\n"
+msgstr "\tcondici� d'aturada: %s\n"
+
+#: debug.c:771 debug.c:911
+msgid "\tcommands:\n"
+msgstr "\tordres:\n"
+
+#: debug.c:793
+#, c-format
+msgid "Current frame: "
+msgstr "Marc actual: "
+
+#: debug.c:796
+#, c-format
+msgid "Called by frame: "
+msgstr "Cridat per marc: "
+
+#: debug.c:800
+#, c-format
+msgid "Caller of frame: "
+msgstr "Cridador de marc: "
+
+#: debug.c:818
+#, c-format
+msgid "None in main().\n"
+msgstr "Cap a main().\n"
+
+#: debug.c:848
+msgid "No arguments.\n"
+msgstr "Sense arguments.\n"
+
+#: debug.c:849
+msgid "No locals.\n"
+msgstr "No hi ha locals.\n"
+
+#: debug.c:857
+msgid ""
+"All defined variables:\n"
+"\n"
+msgstr ""
+"Totes les variables definides:\n"
+"\n"
+
+#: debug.c:867
+msgid ""
+"All defined functions:\n"
+"\n"
+msgstr ""
+"Totes les funcions definides:\n"
+"\n"
+
+#: debug.c:886
+msgid ""
+"Auto-display variables:\n"
+"\n"
+msgstr ""
+"Mostra autom�ticament les variables:\n"
+"\n"
+
+#: debug.c:889
+msgid ""
+"Watch variables:\n"
+"\n"
+msgstr ""
+"Inspecciona les variables:\n"
+"\n"
+
+#: debug.c:1029
+#, c-format
+msgid "no symbol `%s' in current context\n"
+msgstr "no hi ha el s�mbol `%s' al context actual\n"
+
+#: debug.c:1041 debug.c:1427
+#, c-format
+msgid "`%s' is not an array\n"
+msgstr "`%s' no �s una matriu\n"
+
+#: debug.c:1055
+#, c-format
+msgid "$%ld = uninitialized field\n"
+msgstr "$%ld = camp sense inicialitzar\n"
+
+#: debug.c:1076
+#, c-format
+msgid "array `%s' is empty\n"
+msgstr "la matriu `%s' est� buida\n"
+
+#: debug.c:1119 debug.c:1171
+#, c-format
+msgid "[\"%s\"] not in array `%s'\n"
+msgstr "[\"%s\"] no est� a la matriu `%s'\n"
+
+#: debug.c:1175
+#, c-format
+msgid "`%s[\"%s\"]' is not an array\n"
+msgstr "`%s[\"%s\"]' no �s una matriu\n"
+
+#: debug.c:1236 debug.c:4964
+#, c-format
+msgid "`%s' is not a scalar variable"
+msgstr "`%s' no �s una variable escalar"
+
+#: debug.c:1258 debug.c:4994
+#, c-format
+msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
+msgstr "s'ha intentat usar la matriu `%s[\"%s\"]' en un context escalar"
+
+#: debug.c:1280 debug.c:5005
+#, c-format
+msgid "attempt to use scalar `%s[\"%s\"]' as array"
+msgstr "s'ha intentat usar la dada escalar `%s[\"%s\"]' com a una matriu"
+
+#: debug.c:1423
+#, c-format
+msgid "`%s' is a function"
+msgstr "`%s' �s una funci�"
+
+#: debug.c:1465
+#, c-format
+msgid "watchpoint %d is unconditional\n"
+msgstr "el punt d'inspecci� %d �s incondicional\n"
+
+#: debug.c:1499
+#, c-format
+msgid "No display item numbered %ld"
+msgstr "No hi ha un element de visualitzaci� numerat %ld"
+
+#: debug.c:1502
+#, c-format
+msgid "No watch item numbered %ld"
+msgstr "No hi ha un element d'inspecci� numerat %ld"
+
+#: debug.c:1528
+#, c-format
+msgid "%d: [\"%s\"] not in array `%s'\n"
+msgstr "%d: [\"%s\"] no est� a la matriu `%s'\n"
+
+#: debug.c:1767
+msgid "attempt to use scalar value as array"
+msgstr "s'ha intentat usar una dada escalar com a una matriu"
+
+#: debug.c:1856
+#, c-format
+msgid "Watchpoint %d deleted because parameter is out of scope.\n"
+msgstr ""
+"El punt d'inspecci� %d s'ha esborrat perqu� el par�metre est� fora d'abast.\n"
+
+#: debug.c:1867
+#, c-format
+msgid "Display %d deleted because parameter is out of scope.\n"
+msgstr "La vista %d s'ha suprimit perqu� el par�metre est� fora de l'abast.\n"
+
+#: debug.c:1900
+#, c-format
+msgid " in file `%s', line %d\n"
+msgstr "al fitxer `%s', l�nia %d\n"
+
+#: debug.c:1921
+#, c-format
+msgid " at `%s':%d"
+msgstr " a `%s':%d"
+
+#: debug.c:1937 debug.c:2000
+#, c-format
+msgid "#%ld\tin "
+msgstr "#%ld\ten "
+
+#: debug.c:1974
+#, c-format
+msgid "More stack frames follow ...\n"
+msgstr "Segueixen m�s marcs de pila ...\n"
+
+#: debug.c:2017
+msgid "invalid frame number"
+msgstr "n�mero no v�lid de rang"
+
+#: debug.c:2200
+#, c-format
+msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
+msgstr ""
+"Nota: el punt d'interrupci� %d (habilitat, ignora els %ld accessos "
+"seg�ents), tamb� s'ha establert a %s:%d"
+
+#: debug.c:2207
+#, c-format
+msgid "Note: breakpoint %d (enabled), also set at %s:%d"
+msgstr ""
+"Nota: el punt d'interrupci� %d (habilitat), tamb� s'ha establert a %s:%d"
+
+#: debug.c:2214
+#, c-format
+msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
+msgstr ""
+"Nota: el punt d'interrupci� %d (deshabilitat, ignora els %ld accessos "
+"seg�ents), tamb� s'ha establert a %s:%d"
+
+#: debug.c:2221
+#, c-format
+msgid "Note: breakpoint %d (disabled), also set at %s:%d"
+msgstr ""
+"Nota: el punt d'interrupci� %d (deshabilitat), tamb� s'ha establert a %s:%d"
+
+#: debug.c:2238
+#, c-format
+msgid "Breakpoint %d set at file `%s', line %d\n"
+msgstr "Punt d'interrupci�  %d establert al fitxer `%s', l�nia %d\n"
+
+#: debug.c:2340
+#, c-format
+msgid "Can't set breakpoint in file `%s'\n"
+msgstr "No es pot establir el punt d'interrupci� al fitxer `%s'\n"
+
+#: debug.c:2369 debug.c:2492 debug.c:3350
+#, c-format
+msgid "line number %d in file `%s' out of range"
+msgstr "el n�mero de l�nia %d al fitxer `%s' est� fora de rang"
+
+#: debug.c:2373
+#, c-format
+msgid "Can't find rule!!!\n"
+msgstr "No es pot trobar la regla!!!\n"
+
+#: debug.c:2375
+#, c-format
+msgid "Can't set breakpoint at `%s':%d\n"
+msgstr "No es pot establir el punt d'interrupci� a `%s':%d\n"
+
+#: debug.c:2387
+#, c-format
+msgid "Can't set breakpoint in function `%s'\n"
+msgstr "No est pot establir el punt d'interrupci� a la funci� `%s'\n"
+
+#: debug.c:2403
+#, c-format
+msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
+msgstr ""
+"el punt d'interrupci� %d establert al fitxer `%s', l�nia %d �s "
+"incondicional\n"
+
+#: debug.c:2508 debug.c:2530
+#, c-format
+msgid "Deleted breakpoint %d"
+msgstr "Punt interrupci� suprimit %d"
+
+#: debug.c:2514
+#, c-format
+msgid "No breakpoint(s) at entry to function `%s'\n"
+msgstr "No hi ha punt(s) d'interrupci� a l'entrada a la funci� `%s'\n"
+
+#: debug.c:2541
+#, c-format
+msgid "No breakpoint at file `%s', line #%d\n"
+msgstr "No hi ha un punt d'interrupci� al fitxer `%s', l�nia #%d\n"
+
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
+msgid "invalid breakpoint number"
+msgstr "n�mero no v�lid de punt d'interrupci�"
+
+#: debug.c:2612
+msgid "Delete all breakpoints? (y or n) "
+msgstr "Suprimir tots els punts d'interrupci� (s o n) "
+
+#: debug.c:2613 debug.c:2923 debug.c:2976
+msgid "y"
+msgstr "s"
+
+#: debug.c:2662
+#, c-format
+msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
+msgstr ""
+"S'ignoraran el(s) %ld creuament(s) seg�ent(s) del punt d'interrupci� %d.\n"
+
+#: debug.c:2666
+#, c-format
+msgid "Will stop next time breakpoint %d is reached.\n"
+msgstr ""
+"S'aturar� la pr�xima vegada que s'assoleixi el punt d'interrupci� %d.\n"
+
+#: debug.c:2783
+#, c-format
+msgid "Can only debug programs provided with the `-f' option.\n"
+msgstr "Sols es poden depurar programes que tenen l'opci� `-f'.\n"
+
+#: debug.c:2908
+#, c-format
+msgid "Failed to restart debugger"
+msgstr "No s'ha pogut reiniciar el depurador."
+
+#: debug.c:2922
+msgid "Program already running. Restart from beginning (y/n)? "
+msgstr "El programa ja est� corrent. S'ha de reiniciar des del principi (s/n)?"
+
+#: debug.c:2926
+#, c-format
+msgid "Program not restarted\n"
+msgstr "No s'ha reiniciat el programa\n"
+
+#: debug.c:2936
+#, c-format
+msgid "error: cannot restart, operation not allowed\n"
+msgstr "error: no es pot reiniciar, l'operaci� no est� permesa\n"
+
+#: debug.c:2942
+#, c-format
+msgid "error (%s): cannot restart, ignoring rest of the commands\n"
+msgstr "error (%s): no es pot reiniciar, s'ignoraran la resta de les ordres\n"
+
+#: debug.c:2950
+#, c-format
+msgid "Starting program: \n"
+msgstr "S'est� iniciant el programa: \n"
+
+#: debug.c:2959
+#, c-format
+msgid "Program exited %s with exit value: %d\n"
+msgstr "El programa ha tingut la sortida %s amb el valor de sortida: %d\n"
+
+#: debug.c:2975
+msgid "The program is running. Exit anyway (y/n)? "
+msgstr "El programa s'est� executant. Voleu sortir tot i aix� (s/n)? "
+
+#: debug.c:3010
+#, c-format
+msgid "Not stopped at any breakpoint; argument ignored.\n"
+msgstr "No s'ha detingut a cap punt d'interrupci�; s'ignorar� l'argument.\n"
+
+#: debug.c:3015
+#, c-format
+msgid "invalid breakpoint number %d."
+msgstr "n�mero no v�lid de punt d'interrupci� %d."
+
+#: debug.c:3020
+#, c-format
+msgid "Will ignore next %ld crossings of breakpoint %d.\n"
+msgstr "S'ignoraran els pr�xims %ld creuaments de punt d'interrupci� %d.\n"
+
+#: debug.c:3207
+#, c-format
+msgid "'finish' not meaningful in the outermost frame main()\n"
+msgstr "'finish' no t� significat al marc m�s extern main()\n"
+
+#: debug.c:3212
+#, c-format
+msgid "Run till return from "
+msgstr "Executa fins retornar de "
+
+#: debug.c:3255
+#, c-format
+msgid "'return' not meaningful in the outermost frame main()\n"
+msgstr "'return' no t� significat al marc m�s extern main()\n"
+
+#: debug.c:3369
+#, c-format
+msgid "Can't find specified location in function `%s'\n"
+msgstr "No es pot trobar la ubicaci� especificada a la funci� `%s'\n"
+
+#: debug.c:3377
+#, c-format
+msgid "invalid source line %d in file `%s'"
+msgstr "l�nia %d no v�lida de font al fitxer `%s'"
+
+#: debug.c:3392
+#, c-format
+msgid "Can't find specified location %d in file `%s'\n"
+msgstr "No es pot trobar la ubicaci� especificada %d al fitxer `%s'\n"
+
+#: debug.c:3424
+#, c-format
+msgid "element not in array\n"
+msgstr "l'element no est� a la matriu\n"
+
+#: debug.c:3424
+#, c-format
+msgid "untyped variable\n"
+msgstr "variable sense tipus\n"
+
+#: debug.c:3466
+#, c-format
+msgid "Stopping in %s ...\n"
+msgstr "S'est� aturant a %s ...\n"
+
+#: debug.c:3543
+#, c-format
+msgid "'finish' not meaningful with non-local jump '%s'\n"
+msgstr "'finish' no t� significat amb salt no local '%s'\n"
+
+#: debug.c:3550
+#, c-format
+msgid "'until' not meaningful with non-local jump '%s'\n"
+msgstr "'until' no t� significat amb salt no local '%s'\n"
+
+#: debug.c:4185
+msgid "\t------[Enter] to continue or q [Enter] to quit------"
+msgstr "\t------[Intro] per continuar o q [Intro] per sortir------"
+
+#: debug.c:4186
+msgid "q"
+msgstr "q"
+
+#: debug.c:5001
+#, c-format
+msgid "[\"%s\"] not in array `%s'"
+msgstr "[\"%s\"] no est� a la matriu `%s'"
+
+#: debug.c:5207
+#, c-format
+msgid "sending output to stdout\n"
+msgstr "s'est� enviant la sortida a la sortida est�ndard\n"
+
+#: debug.c:5247
+msgid "invalid number"
+msgstr "n�mero no v�lid"
+
+#: debug.c:5381
+#, c-format
+msgid "`%s' not allowed in current context; statement ignored"
+msgstr "`%s' no est� perm�s al context actual; s'ignorar� la declaraci�"
+
+#: debug.c:5389
+msgid "`return' not allowed in current context; statement ignored"
+msgstr "`return' no est� perm�s al context actual; s'ignorar� la declaraci�"
+
+#: debug.c:5590
+#, c-format
+msgid "No symbol `%s' in current context"
+msgstr "No hi ha un s�mbol `%s' al context actual"
+
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
+msgid "unbalanced ["
+msgstr "[ sense aparellar"
+
+#: dfa.c:1174
+msgid "invalid character class"
+msgstr "classe no v�lida de car�cters"
+
+#: dfa.c:1316
+msgid "character class syntax is [[:space:]], not [:space:]"
+msgstr "la sintaxi de la classe de car�cters �s [[:espai:]], no [:espai:]"
 
-#: eval.c:410
+#: dfa.c:1366
+msgid "unfinished \\ escape"
+msgstr "seq��ncia d'escapada \\ sense finalitzar"
+
+#: dfa.c:1513 regcomp.c:161
+msgid "Invalid content of \\{\\}"
+msgstr "Contingut no v�lid de \\{\\}"
+
+#: dfa.c:1516 regcomp.c:176
+msgid "Regular expression too big"
+msgstr "L'expressi� regular �s massa gran"
+
+#: dfa.c:1936
+msgid "unbalanced ("
+msgstr "( sense aparellar"
+
+#: dfa.c:2062
+msgid "no syntax specified"
+msgstr "no s'ha especificat una sintaxi"
+
+#: dfa.c:2070
+msgid "unbalanced )"
+msgstr ") sense aparellar"
+
+#: eval.c:394
 #, c-format
 msgid "unknown nodetype %d"
-msgstr "tipo de node %d desconegut"
+msgstr "tipus de node %d desconegut"
 
-#: eval.c:421 eval.c:435
-#, fuzzy, c-format
+#: eval.c:405 eval.c:419
+#, c-format
 msgid "unknown opcode %d"
-msgstr "tipo de node %d desconegut"
+msgstr "opcode %d desconegut"
 
-#: eval.c:432
+#: eval.c:416
 #, c-format
 msgid "opcode %s not an operator or keyword"
-msgstr ""
+msgstr "l'opcode %s no �s un operador o una paraula clau"
 
-#: eval.c:485
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "desbordament del cau temporal en genflags2str"
 
-#: eval.c:696
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -897,870 +1915,1292 @@ msgid ""
 "\n"
 msgstr ""
 "\n"
-"\t# Pila de Crides a les Funcions:\n"
+"\t# Pila de crida a les funcions:\n"
 "\n"
 
-#: eval.c:723
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
-msgstr "�IGNORECASE� �s una extensi� de gawk"
+msgstr "`IGNORECASE' �s una extensi� de gawk"
 
-#: eval.c:752
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
-msgstr "�BINMODE� �s una extensi� de gawk"
+msgstr "`BINMODE' �s una extensi� de gawk"
 
-#: eval.c:810
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
-msgstr ""
+msgstr "El valor BINMODE `%s' no �s v�lid, es tractar� com 3"
 
-#: eval.c:900
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
-msgstr "�%sFMT� especificaci� err�nia �%s�"
+msgstr "`%sFMT' especificaci� err�nia `%s'"
 
-#: eval.c:978
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
-msgstr "desactivant �--lint� degut a una assignaci� a �LINT�"
-
-#: eval.c:1247
-#, fuzzy
-msgid "sorted array traversal is a gawk extension"
-msgstr "�delete array� �s una extensi� de gawk"
-
-#: eval.c:1291
-msgid "`PROCINFO[\"sorted_in\"]' value is not recognized"
-msgstr ""
+msgstr "desactivant `--lint' degut a una assignaci� a `LINT'"
 
-#: eval.c:1373 eval.c:1923
+#: eval.c:1147
 #, c-format
-msgid "can't use function name `%s' as variable or array"
-msgstr "no es pot usar el nom de la funci� �%s� com a variable o matriu"
-
-#: eval.c:1401
-msgid "assignment is not allowed to result of builtin function"
-msgstr ""
-"no es permet l'assignaci� per a obtindre un resultat d'una funci� interna"
+msgid "reference to uninitialized argument `%s'"
+msgstr "refer�ncia a un argument sense inicialitzar `%s'"
 
-#: eval.c:1410 eval.c:1935 eval.c:1948
+#: eval.c:1148
 #, c-format
-msgid "reference to uninitialized argument `%s'"
-msgstr "refer�ncia a un argument sense inicialitzar �%s�"
+msgid "reference to uninitialized variable `%s'"
+msgstr "refer�ncia a una variable sense inicialitzar `%s'"
 
-#: eval.c:1429
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "s'ha intentat una refer�ncia de camp a partir d'un valor no num�ric"
 
-#: eval.c:1431
-#, fuzzy
+#: eval.c:1168
 msgid "attempt to field reference from null string"
-msgstr "s'ha intentat una refer�ncia a partir d'una cadena nul�la"
+msgstr "s'ha intentat entrar una refer�ncia a partir d'una cadena nul�la"
 
-#: eval.c:1437
-#, fuzzy, c-format
+#: eval.c:1176
+#, c-format
 msgid "attempt to access field %ld"
-msgstr "s'ha intentat accedir al camp %d"
+msgstr "s'ha intentat accedir al camp %ld"
 
-#: eval.c:1446
-#, fuzzy, c-format
+#: eval.c:1185
+#, c-format
 msgid "reference to uninitialized field `$%ld'"
-msgstr "refer�ncia a una variable sense inicialitzar �%s�"
+msgstr "refer�ncia a una variable sense inicialitzar `$%ld'"
 
-#: eval.c:1508
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
-msgstr "s'ha cridat a la funci� �%s� amb m�s arguments dels declarats"
+msgstr "s'ha cridat a la funci� `%s' amb m�s arguments dels declarats"
 
-#: eval.c:1663
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
-msgstr ""
+msgstr "unwind_stack: tipus no esperat `%s'"
 
-#: eval.c:1747
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
-msgstr "s'ha intentat una divisi� per zero en �/=�"
+msgstr "s'ha intentat una divisi� per zero en `/='"
 
-#: eval.c:1754
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
-msgstr "s'ha intentat una divisi� per zero en �%%=�"
+msgstr "s'ha intentat una divisi� per zero en `%%='"
 
-#: eval.c:2057
-msgid "assignment used in conditional context"
-msgstr "assignaci� usada en un context condicional"
+#: ext.c:89 ext.c:171
+msgid "extensions are not allowed in sandbox mode"
+msgstr "les extensions no estan permeses en mode de proves"
 
-#: eval.c:2061
-msgid "statement has no effect"
-msgstr "la sent�ncia no t� efecte"
+#: ext.c:92
+msgid "-l / @load are gawk extensions"
+msgstr "-l / @load s�n extensions gawk"
 
-#: eval.c:2473
-#, fuzzy, c-format
-msgid "for loop: array `%s' changed size from %ld to %ld during loop execution"
-msgstr ""
-"bucle for: la matriu �%s� ha canviat de mida de %d a %d durant l'execuci� "
-"del bucle"
+#: ext.c:95
+msgid "load_ext: received NULL lib_name"
+msgstr "load_ext: s'ha rebut lib_name nul"
+
+#: ext.c:98
+#, c-format
+msgid "load_ext: cannot open library `%s' (%s)\n"
+msgstr "load_ext: no es pot obrir la llibreria `%s' (%s)\n"
 
-#: eval.c:2583
+#: ext.c:104
 #, c-format
-msgid "function called indirectly through `%s' does not exist"
+msgid ""
+"load_ext: library `%s': does not define `plugin_is_GPL_compatible' (%s)\n"
 msgstr ""
+"load_ext: biblioteca `%s': no defineix `plugin_is_GPL_compatible' (%s)\n"
 
-#: eval.c:2595
+#: ext.c:110
 #, c-format
-msgid "function `%s' not defined"
-msgstr "la funci� �%s� no est� definida"
+msgid "load_ext: library `%s': cannot call function `%s' (%s)\n"
+msgstr "load_ext: biblioteca `%s': no es pot cridar a la funci� `%s' (%s)\n"
 
-#: eval.c:2656
-#, fuzzy, c-format
-msgid "non-redirected `getline' invalid inside `%s' rule"
-msgstr "port remot no v�lid en �%s�"
+#: ext.c:114
+#, c-format
+msgid "load_ext: library `%s' initialization routine `%s' failed\n"
+msgstr ""
+"load_ext: la biblioteca `%s' amb rutina d'inicialitzaci� `%s' ha fallat\n"
 
-#: eval.c:2717
-#, fuzzy, c-format
-msgid "`nextfile' cannot be called from a `%s' rule"
-msgstr "�nextfile� no es pot cridar des d'una regla FINAL"
+#: ext.c:174
+msgid "`extension' is a gawk extension"
+msgstr "`extension' �s una extensi� gawk"
 
-#: eval.c:2767
-#, fuzzy, c-format
-msgid "`next' cannot be called from a `%s' rule"
-msgstr "�next� no es pot cridar des d'una regla FINAL"
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "extension: s'ha rebut lib_name nul"
 
-#: eval.c:2834
+#: ext.c:180
 #, c-format
-msgid "Sorry, don't know how to interpret `%s'"
-msgstr ""
+msgid "extension: cannot open library `%s' (%s)"
+msgstr "extension: no es pot obrir la biblioteca `%s' (%s)"
 
-#: ext.c:64
-msgid "extensions are not allowed in sandbox mode"
+#: ext.c:186
+#, c-format
+msgid ""
+"extension: library `%s': does not define `plugin_is_GPL_compatible' (%s)"
 msgstr ""
+"extension: biblioteca `%s': no defineix `plugin_is_GPL_compatible' (%s)"
 
-#: ext.c:70 ext.c:75
-msgid "`extension' is a gawk extension"
-msgstr "�extension� �s una extensi� gawk"
+#: ext.c:190
+#, c-format
+msgid "extension: library `%s': cannot call function `%s' (%s)"
+msgstr "extension: biblioteca `%s': no es pot cridar a la funci� `%s' (%s)"
 
-#: ext.c:85
-#, fuzzy, c-format
-msgid "fatal: extension: cannot open `%s' (%s)\n"
-msgstr "extension: no es pot obrir �%s� (%s)\n"
+#: ext.c:221
+msgid "make_builtin: missing function name"
+msgstr "make_builtin: nom absent de funci�"
 
-#: ext.c:94
-#, fuzzy, c-format
-msgid ""
-"fatal: extension: library `%s': does not define "
-"`plugin_is_GPL_compatible' (%s)\n"
-msgstr "extension: biblioteca �%s�: no es pot cridar a la funci� �%s� (%s)\n"
+#: ext.c:236
+#, c-format
+msgid "make_builtin: can't redefine function `%s'"
+msgstr "make_builtin: no es pot redefinir la funci� `%s'"
+
+#: ext.c:240
+#, c-format
+msgid "make_builtin: function `%s' already defined"
+msgstr "make_builtin: la funci� `%s' ja est� definida"
+
+#: ext.c:244
+#, c-format
+msgid "make_builtin: function name `%s' previously defined"
+msgstr "make_builtin: nom de la funci� `%s' definida pr�viament"
+
+#: ext.c:246
+#, c-format
+msgid "make_builtin: can't use gawk built-in `%s' as function name"
+msgstr "make_builtin: no es pot usar el nom intern `%s' com a nom de funci�"
 
-#: ext.c:103
-#, fuzzy, c-format
-msgid "fatal: extension: library `%s': cannot call function `%s' (%s)\n"
-msgstr "extension: biblioteca �%s�: no es pot cridar a la funci� �%s� (%s)\n"
+#: ext.c:249 ext.c:304
+#, c-format
+msgid "make_builtin: negative argument count for function `%s'"
+msgstr "make_builtin: recompte negatiu d'arguments per a la funci� `%s'"
 
-#: ext.c:137
+#: ext.c:276
 msgid "extension: missing function name"
-msgstr ""
+msgstr "extension: nom absent de funci�"
 
-#: ext.c:142
-#, fuzzy, c-format
+#: ext.c:279 ext.c:283
+#, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
-msgstr "extension: biblioteca �%s�: no es pot cridar a la funci� �%s� (%s)\n"
+msgstr "extension: car�cter `%c' il�legal al nom de funci� `%s'"
 
-#: ext.c:151
-#, fuzzy, c-format
+#: ext.c:291
+#, c-format
 msgid "extension: can't redefine function `%s'"
-msgstr "extension: no es pot obrir �%s� (%s)\n"
+msgstr "extension: no es pot redefinir la funci� `%s'"
 
-#: ext.c:155
-#, fuzzy, c-format
+#: ext.c:295
+#, c-format
 msgid "extension: function `%s' already defined"
-msgstr "la funci� �%s� no est� definida"
+msgstr "extension: la funci� `%s' ja est� definida"
 
-#: ext.c:160
-#, fuzzy, c-format
+#: ext.c:299
+#, c-format
 msgid "extension: function name `%s' previously defined"
-msgstr "nom de la funci� �%s� definida pr�viament"
+msgstr "extension: nom de la funci� `%s' definida pr�viament"
 
-#: ext.c:162
-#, fuzzy, c-format
+#: ext.c:301
+#, c-format
 msgid "extension: can't use gawk built-in `%s' as function name"
-msgstr "funci� �%s�: no pot usar el nom de la funci� com a par�metre"
+msgstr "extension: no es pot usar el nom intern `%s' com a nom de funci�"
 
-#: ext.c:166
+#: ext.c:375
 #, c-format
-msgid "make_builtin: negative argument count for function `%s'"
-msgstr ""
-
-#: ext.c:269
-#, fuzzy, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
-msgstr "es defineix la funci� �%s� per� no s'ha cridat mai"
+msgstr "la funci� `%s' est� definida per agafar no m�s de %d argument(s)"
 
-#: ext.c:272
-#, fuzzy, c-format
+#: ext.c:378
+#, c-format
 msgid "function `%s': missing argument #%d"
-msgstr "la funci� �%s� no est� definida"
+msgstr "funci� `%s': falta l'argument  #%d"
 
-#: ext.c:282
-#, fuzzy, c-format
+#: ext.c:395
+#, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
-msgstr "s'ha intentat usar la dada escalar �%s� com a una matriu"
+msgstr ""
+"funci� `%s': argument #%d: s'ha intentat usar una dada escalar com a una "
+"matriu"
 
-#: ext.c:286
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr ""
+"funci� `%s': argument #%d: s'ha intentat usar una matriu com a un escalar"
 
-#: ext.c:299
-msgid "Operation Not Supported"
-msgstr "Operaci� No Suportada"
+#: ext.c:413
+msgid "dynamic loading of library not supported"
+msgstr "no est� suportada la c�rrega din�mica de la biblioteca"
+
+#: extension/filefuncs.c:159
+msgid "chdir: called with incorrect number of arguments, expecting 1"
+msgstr "chdir: cridat amb un nombre incorrecte d'arguments, s'esperava 1"
+
+#: extension/filefuncs.c:439
+#, c-format
+msgid "stat: unable to read symbolic link `%s'"
+msgstr "stat: no s'ha pogut llegir l'enlla� simb�lic `%s'"
+
+#: extension/filefuncs.c:472
+msgid "stat: called with wrong number of arguments"
+msgstr "stat: cridat amb un nombre incorrecte d'arguments"
+
+#: extension/filefuncs.c:479
+msgid "stat: bad parameters"
+msgstr "stata: arguments dolents"
+
+#: extension/filefuncs.c:533
+#, c-format
+msgid "fts init: could not create variable %s"
+msgstr "fts init: no s'ha pogut crear la variable %s"
+
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "fts no est� suportat en aquest sistema"
+
+#: extension/filefuncs.c:573
+msgid "fill_stat_element: could not create array"
+msgstr "fill_stat_element: no s'ha pogut crear la matriu"
+
+#: extension/filefuncs.c:582
+msgid "fill_stat_element: could not set element"
+msgstr "fill_stat_element: no s'ha pogut establir l'element"
+
+#: extension/filefuncs.c:597
+msgid "fill_path_element: could not set element"
+msgstr "fill_path_element: no s'ha pogut establir l'element"
+
+#: extension/filefuncs.c:613
+msgid "fill_error_element: could not set element"
+msgstr "fill_error_element: no s'ha pogut establir l'element"
+
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
+msgid "fts-process: could not create array"
+msgstr "fts-process: no s'ha pogut crear la matriu"
+
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
+msgid "fts-process: could not set element"
+msgstr "fts-process: no s'ha pogut establir l'element"
+
+#: extension/filefuncs.c:784
+msgid "fts: called with incorrect number of arguments, expecting 3"
+msgstr "fts: cridat amb un nombre incorrecte d'arguments, s'esperaven 3"
+
+#: extension/filefuncs.c:787
+msgid "fts: bad first parameter"
+msgstr "fts: el segon argument �s dolent"
+
+#: extension/filefuncs.c:793
+msgid "fts: bad second parameter"
+msgstr "fts: el segon argument �s dolent"
+
+#: extension/filefuncs.c:799
+msgid "fts: bad third parameter"
+msgstr "fts: el tercer par�meter es dolent"
+
+#: extension/filefuncs.c:806
+msgid "fts: could not flatten array\n"
+msgstr "fts: no s'ha pogut aplanar la matriu\n"
+
+#: extension/filefuncs.c:824
+msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
+msgstr "fts: s'ignorar� l'indicador FTS_NOSTAT furtiu. T'he enxampat!"
+
+#: extension/filefuncs.c:841
+msgid "fts: clear_array() failed\n"
+msgstr "fts: clear_array() ha fallat\n"
+
+#: extension/fnmatch.c:112
+msgid "fnmatch: called with less than three arguments"
+msgstr "fnmatch: s'ha cridat amb menys de tres arguments"
+
+#: extension/fnmatch.c:115
+msgid "fnmatch: called with more than three arguments"
+msgstr "fnmatch: s'ha cridat amb m�s de tres arguments"
+
+#: extension/fnmatch.c:118
+msgid "fnmatch: could not get first argument"
+msgstr "fnmatch: no s'ha pogut obtenir el segon argument"
+
+#: extension/fnmatch.c:123
+msgid "fnmatch: could not get second argument"
+msgstr "fnmatch: no s'ha pogut obtenir el segon argument"
+
+#: extension/fnmatch.c:128
+msgid "fnmatch: could not get third argument"
+msgstr "fnmatch: no s'ha pogut obtenir el tercer argument"
+
+#: extension/fnmatch.c:141
+msgid "fnmatch is not implemented on this system\n"
+msgstr "fnmatch no est� implementat en aquest sistema\n"
+
+#: extension/fnmatch.c:173
+msgid "fnmatch init: could not add FNM_NOMATCH variable"
+msgstr "fnmatch init: no s'ha pogut afegir la variable FNM_NOMATCH"
+
+#: extension/fnmatch.c:183
+#, c-format
+msgid "fnmatch init: could not set array element %s"
+msgstr "fnmatch init: no s'ha pogut establir l'element de matriu %s"
+
+#: extension/fnmatch.c:193
+msgid "fnmatch init: could not install FNM array"
+msgstr "fnmatch init: no s'ha pogut instal�lar la matriu FNM"
+
+#: extension/fork.c:81
+msgid "fork: called with too many arguments"
+msgstr "fork: s'ha cridat amb massa arguments"
+
+#: extension/fork.c:94
+msgid "fork: PROCINFO is not an array!"
+msgstr "fork: PROCINFO no �s una matriu!"
+
+#: extension/fork.c:118
+msgid "waitpid: called with too many arguments"
+msgstr "waitpid: s'ha cridat amb massa arguments"
+
+#: extension/fork.c:126
+msgid "wait: called with no arguments"
+msgstr "wait: s'ha cridat amb cap argument"
+
+#: extension/fork.c:143
+msgid "wait: called with too many arguments"
+msgstr "wait: s'ha cridat amb massa arguments"
+
+#: extension/inplace.c:130
+msgid "inplace_begin: in-place editing already active"
+msgstr "inplace_begin: l'edici� in situ ja est� activa"
+
+#: extension/inplace.c:133 extension/inplace.c:207
+#, c-format
+msgid "inplace_begin: expects 2 arguments but called with %d"
+msgstr "inplace_begin: s'esperaven 2 arguments per� s'ha cridat amb %d"
+
+#: extension/inplace.c:136
+msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
+msgstr ""
+"inplace_begin: no es pot obtenir el primer argument com nom de fitxer cadena "
+"de car�cters"
+
+#: extension/inplace.c:144
+#, c-format
+msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
+msgstr ""
+"inplace_begin: s'est� deshabilitant l'edici� in situ per al nom de fitxer no "
+"v�lid `%s'"
+
+#: extension/inplace.c:151
+#, c-format
+msgid "inplace_begin: Cannot stat `%s' (%s)"
+msgstr "implace_begin: No es pot obrir `%s' (%s)"
+
+#: extension/inplace.c:158
+#, c-format
+msgid "inplace_begin: `%s' is not a regular file"
+msgstr "inplace_begin: `%s' no �s un fitxer regular"
+
+#: extension/inplace.c:169
+#, c-format
+msgid "inplace_begin: mkstemp(`%s') failed (%s)"
+msgstr "inplace_begin: mkstemp(`%s') ha fallat (%s)"
+
+#: extension/inplace.c:178
+#, c-format
+msgid "inplace_begin: chmod failed (%s)"
+msgstr "inplace_begin: ha fallat chmod (%s)"
+
+#: extension/inplace.c:185
+#, c-format
+msgid "inplace_begin: dup(stdout) failed (%s)"
+msgstr "inplace_begin: dup(stdout) ha fallat(%s)"
+
+#: extension/inplace.c:188
+#, c-format
+msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
+msgstr "inplace_begin: dup2(%d, stdout) ha fallat (%s)"
+
+#: extension/inplace.c:191
+#, c-format
+msgid "inplace_begin: close(%d) failed (%s)"
+msgstr "inplace begin: close(%d) ha fallat (%s)"
+
+#: extension/inplace.c:210
+msgid "inplace_end: cannot retrieve 1st argument as a string filename"
+msgstr ""
+"inplace_end: no es pot obtenir el primer argument com un nom de fitxer "
+"cadena de car�cters"
 
-#: field.c:328
+#: extension/inplace.c:217
+msgid "inplace_end: in-place editing not active"
+msgstr "inplace_end: no est� activa l'edici� in situ"
+
+#: extension/inplace.c:223
+#, c-format
+msgid "inplace_end: dup2(%d, stdout) failed (%s)"
+msgstr "inplace_end: dup2(%d, stdout) ha fallat (%s)"
+
+#: extension/inplace.c:226
+#, c-format
+msgid "inplace_end: close(%d) failed (%s)"
+msgstr "inplace_end: close(%d) ha fallat (%s)"
+
+#: extension/inplace.c:230
+#, c-format
+msgid "inplace_end: fsetpos(stdout) failed (%s)"
+msgstr "inplace_end: fsetpos(stdout) ha fallat (%s)"
+
+#: extension/inplace.c:243
+#, c-format
+msgid "inplace_end: link(`%s', `%s') failed (%s)"
+msgstr "inplace_end: link(`%s', `%s') ha fallat (%s)"
+
+#: extension/inplace.c:253
+#, c-format
+msgid "inplace_end: rename(`%s', `%s') failed (%s)"
+msgstr "inplace_end: rename(`%s', `%s') ha fallat (%s)"
+
+#: extension/ordchr.c:69
+msgid "ord: called with too many arguments"
+msgstr "ord: s'ha cridat amb massa arguments"
+
+#: extension/ordchr.c:75
+msgid "ord: called with no arguments"
+msgstr "ord: s'ha cridat amb cap argument"
+
+#: extension/ordchr.c:77
+msgid "ord: called with inappropriate argument(s)"
+msgstr "ord: s'ha cridat amb argument(s) no apropiat(s)"
+
+#: extension/ordchr.c:99
+msgid "chr: called with too many arguments"
+msgstr "chr: s'ha cridat amb massa arguments"
+
+#: extension/ordchr.c:109
+msgid "chr: called with no arguments"
+msgstr "chr: s'ha cridat amb cap argument"
+
+#: extension/ordchr.c:111
+msgid "chr: called with inappropriate argument(s)"
+msgstr "chr: s'ha cridat amb argument(s) no apropiat(s)"
+
+#: extension/readdir.c:281
+#, c-format
+msgid "dir_take_control_of: opendir/fdopendir failed: %s"
+msgstr "dir_take_control_of: opendir/fdopendir ha fallat: %s"
+
+#: extension/readfile.c:113
+msgid "readfile: called with too many arguments"
+msgstr "readfile: s'ha cridat amb massa arguments"
+
+#: extension/readfile.c:137
+msgid "readfile: called with no arguments"
+msgstr "readfile: s'ha cridat amb cap argument"
+
+#: extension/rwarray.c:124
+msgid "writea: called with too many arguments"
+msgstr "writea: s'ha cridat amb massa arguments"
+
+#: extension/rwarray.c:131
+#, c-format
+msgid "do_writea: argument 0 is not a string\n"
+msgstr "do_writea: l'argument 0 no �s una cadena de car�cters\n"
+
+#: extension/rwarray.c:137
+#, c-format
+msgid "do_writea: argument 1 is not an array\n"
+msgstr "do_writea: l'argument 1 no �s una matriu\n"
+
+#: extension/rwarray.c:184
+#, c-format
+msgid "write_array: could not flatten array\n"
+msgstr "write_array: no s'ha pogut aplanar la matriu\n"
+
+#: extension/rwarray.c:198
+#, c-format
+msgid "write_array: could not release flattened array\n"
+msgstr "write_array: no s'ha pogut alliberar la matriu aplanada\n"
+
+#: extension/rwarray.c:280
+msgid "reada: called with too many arguments"
+msgstr "reada: s'ha cridat amb massa arguments"
+
+#: extension/rwarray.c:287
+#, c-format
+msgid "do_reada: argument 0 is not a string\n"
+msgstr "do_reada: l'argument 0 no �s una cadena de car�cters\n"
+
+#: extension/rwarray.c:293
+#, c-format
+msgid "do_reada: argument 1 is not an array\n"
+msgstr "do_reada: l'argument 1 no �s una matriu\n"
+
+#: extension/rwarray.c:337
+#, c-format
+msgid "do_reada: clear_array failed\n"
+msgstr "do_reada: clear_array ha fallat\n"
+
+#: extension/rwarray.c:374
+#, c-format
+msgid "read_array: set_array_element failed\n"
+msgstr "read_array: set_array_element ha fallat\n"
+
+#: extension/time.c:113
+msgid "gettimeofday: ignoring arguments"
+msgstr "gettimeofday: s'estan ignorant els arguments"
+
+#: extension/time.c:144
+msgid "gettimeofday: not supported on this platform"
+msgstr "gettimeofday: no est� suportat en aquesta plataforma"
+
+#: extension/time.c:165
+msgid "sleep: called with too many arguments"
+msgstr "sleep: s'ha cridat amb massa arguments"
+
+#: extension/time.c:168
+msgid "sleep: missing required numeric argument"
+msgstr "sleep: no hi ha un argument num�ric requerit"
+
+#: extension/time.c:174
+msgid "sleep: argument is negative"
+msgstr "sleep: l'argument �s negatiu"
+
+#: extension/time.c:208
+msgid "sleep: not supported on this platform"
+msgstr "sleep: no est� suportat en aquesta plataforma"
+
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF s'inicialitza sobre un valor negatiu"
 
-#: field.c:939 field.c:946 field.c:950
-#, fuzzy
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
-msgstr "match: el tercer argument �s una extensi� de gawk"
+msgstr "split: el quart argument �s una extensi� gawk"
 
-#: field.c:943
-#, fuzzy
+#: field.c:975
 msgid "split: fourth argument is not an array"
-msgstr "split: el segon argument no �s una matriu"
+msgstr "split: el quart argument no �s una matriu"
 
-#: field.c:957
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: el segon argument no �s una matriu"
 
-#: field.c:962
-msgid "split: can not use the same array for second and fourth args"
+#: field.c:993
+msgid "split: cannot use the same array for second and fourth args"
+msgstr ""
+"split: no es pot usar una submatriu de segon argument per a quart argument"
+
+#: field.c:998
+msgid "split: cannot use a subarray of second arg for fourth arg"
+msgstr ""
+"split: no es pot usar una submatriu de segon argument per a quart argument"
+
+#: field.c:1001
+msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
+"split: no est pot usar una submatriu de quart argument per a segon argument"
 
-#: field.c:990
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: la cadena nul�la per al tercer argument �s una extensi� de gawk"
 
-#: field.c:1031
-#, fuzzy
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
-msgstr "split: el segon argument no �s una matriu"
+msgstr "patsplit: el quart argument no �s una matriu"
 
-#: field.c:1036
-#, fuzzy
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
-msgstr "split: el segon argument no �s una matriu"
+msgstr "patsplit: el tercer argument no �s una matriu"
 
-#: field.c:1054
-#, fuzzy
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
-msgstr "match: el tercer argument no �s una matriu"
+msgstr "patsplit: el segon argument no �s una matriu"
 
-#: field.c:1059
-msgid "patsplit: can not use the same array for second and fourth args"
+#: field.c:1087
+msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
+"patsplit: no es pot usar la mateixa matriu per a segon i quart argument"
 
-#: field.c:1089
+#: field.c:1092
+msgid "patsplit: cannot use a subarray of second arg for fourth arg"
+msgstr ""
+"patsplit: no es pot usar una submatriu de segon argument per a quart argument"
+
+#: field.c:1095
+msgid "patsplit: cannot use a subarray of fourth arg for second arg"
+msgstr ""
+"patsplit: no es pot usar una submatriu de quart argument per a segon argument"
+
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
-msgstr "�FIELDWIDTHS� �s una extensi� de gawk"
+msgstr "`FIELDWIDTHS' �s una extensi� de gawk"
 
-#: field.c:1152
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
-msgstr ""
+msgstr "valor FIELDWIDTHS no v�lid, a prop de `%s'"
 
-#: field.c:1225
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
-msgstr "la cadena nul�la per a �FS� �s una extensi� de gawk"
+msgstr "la cadena nul�la per a `FS' �s una extensi� de gawk"
 
-#: field.c:1229
-#, fuzzy
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
-msgstr "l'antic awk no suporta l'operador �**=�"
+msgstr "l'antic awk no suporta expressions regulars com a valor de `FS'"
 
-#: field.c:1348
-#, fuzzy
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
-msgstr "�%s� �s una extensi� de gawk"
+msgstr "`FPAT' �s una extensi� gawk"
+
+#: gawkapi.c:146
+msgid "awk_value_to_node: received null retval"
+msgstr "awk_value_to_node: s'ha rebut retval nul"
+
+#: gawkapi.c:384
+msgid "node_to_awk_value: received null node"
+msgstr "node_to_awk_value: s'ha rebut un node nul"
 
-#: getopt.c:574 getopt.c:590
-#, fuzzy, c-format
-msgid "%s: option '%s' is ambiguous\n"
-msgstr "%s: l'opci� �%s� �s ambigua\n"
+#: gawkapi.c:387
+msgid "node_to_awk_value: received null val"
+msgstr "node_to_awk_value: s'ha rebut un valor nul"
 
-#: getopt.c:623 getopt.c:627
-#, fuzzy, c-format
+#: gawkapi.c:807
+msgid "remove_element: received null array"
+msgstr "remove_element: s'ha rebut una matriu nul�la"
+
+#: gawkapi.c:810
+msgid "remove_element: received null subscript"
+msgstr "remove_element: s'ha rebut un sub�ndex nul"
+
+#: gawkapi.c:947
+#, c-format
+msgid "api_flatten_array: could not convert index %d\n"
+msgstr "api_flatten_array: no s'ha pogut convertir l'�ndex %d\n"
+
+#: gawkapi.c:952
+#, c-format
+msgid "api_flatten_array: could not convert value %d\n"
+msgstr "api_flatten_array: no s'ha pogut convertir el valor %d\n"
+
+#: getopt.c:604 getopt.c:633
+#, c-format
+msgid "%s: option '%s' is ambiguous; possibilities:"
+msgstr "%s: l'opci� `%s' �s ambigua<b: possibilitats:"
+
+#: getopt.c:679 getopt.c:683
+#, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
-msgstr "%s: l'opci� �--%s� no admet cap argument\n"
+msgstr "%s: l'opci� `--%s' no admet cap argument\n"
 
-#: getopt.c:636 getopt.c:641
-#, fuzzy, c-format
+#: getopt.c:692 getopt.c:697
+#, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
-msgstr "%s: l'opci� �%c%s� no admet cap argument\n"
+msgstr "%s: l'opci� `%c%s' no admet cap argument\n"
 
-#: getopt.c:684 getopt.c:703
-#, fuzzy, c-format
+#: getopt.c:740 getopt.c:759
+#, c-format
 msgid "%s: option '--%s' requires an argument\n"
-msgstr "%s: l'opci� �%s� requereix un argument\n"
+msgstr "%s: l'opci� `--%s' requereix un argument\n"
 
-#: getopt.c:741 getopt.c:744
-#, fuzzy, c-format
+#: getopt.c:797 getopt.c:800
+#, c-format
 msgid "%s: unrecognized option '--%s'\n"
-msgstr "%s: no es reconeix l'opci� �--%s�\n"
+msgstr "%s: no es reconeix l'opci� `--%s'\n"
 
-#: getopt.c:752 getopt.c:755
-#, fuzzy, c-format
+#: getopt.c:808 getopt.c:811
+#, c-format
 msgid "%s: unrecognized option '%c%s'\n"
-msgstr "%s: no es reconeix l'opci� �%c%s�\n"
+msgstr "%s: no es reconeix l'opci� `%c%s'\n"
 
-#: getopt.c:804 getopt.c:807
-#, fuzzy, c-format
+#: getopt.c:860 getopt.c:863
+#, c-format
 msgid "%s: invalid option -- '%c'\n"
-msgstr "%s: opci� no v�lida -- %c\n"
+msgstr "%s: opci� no v�lida -- '%c'\n"
 
-#: getopt.c:857 getopt.c:874 getopt.c:1082 getopt.c:1100
-#, fuzzy, c-format
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
+#, c-format
 msgid "%s: option requires an argument -- '%c'\n"
-msgstr "%s: l'opci� requereix un argument -- %c\n"
+msgstr "%s: l'opci� requereix un argument -- '%c'\n"
 
-#: getopt.c:930 getopt.c:946
-#, fuzzy, c-format
+#: getopt.c:989 getopt.c:1005
+#, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
-msgstr "%s: l'opci� �-W %s� �s ambigua\n"
+msgstr "%s: l'opci� `-W %s' �s ambigua\n"
 
-#: getopt.c:970 getopt.c:988
-#, fuzzy, c-format
+#: getopt.c:1029 getopt.c:1047
+#, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
-msgstr "%s: l'opci� �-W %s� no admet cap argument\n"
+msgstr "%s: l'opci� `-W %s' no admet cap argument\n"
 
-#: getopt.c:1009 getopt.c:1027
-#, fuzzy, c-format
+#: getopt.c:1068 getopt.c:1086
+#, c-format
 msgid "%s: option '-W %s' requires an argument\n"
-msgstr "%s: l'opci� �%s� requereix un argument\n"
+msgstr "%s: l'opci� `-W %s' requereix un argument\n"
 
-#: io.c:282
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
-msgstr ""
+msgstr "l'argument `%s' de l�nia d'ordres �s un directori: s'ignorar�"
 
-#: io.c:285 io.c:382
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
-msgstr "no es pot obrir el fitxer �%s� per a lectura (%s)"
-
-#: io.c:429
-#, c-format
-msgid "error reading input file `%s': %s"
-msgstr "error en llegir el fitxer d'entrada �%s�: %s"
+msgstr "no es pot obrir el fitxer `%s' per a lectura (%s)"
 
-#: io.c:498
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
-msgstr "la finalitzaci� del descriptor fd %d (�%s�) ha fallat  (%s)"
+msgstr "la finalitzaci� del descriptor fd %d (`%s') ha fallat  (%s)"
 
-#: io.c:575
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
-msgstr ""
+msgstr "no est permeten redireccions en mode de proves"
 
-#: io.c:609
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
-msgstr "l'expressi� en la redirecci� �%s� solt t� un valor num�ric"
+msgstr "l'expressi� en la redirecci� `%s' solt t� un valor num�ric"
 
-#: io.c:615
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
-msgstr "l'expressi� per a la redirecci� �%s� t� un valor de cadena nul�la"
+msgstr "l'expressi� per a la redirecci� `%s' t� un valor de cadena nul�la"
 
-#: io.c:621
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
-"el fitxer �%s� per a la redirecci� �%s� pot ser resultat d'una expressi� "
+"el fitxer `%s' per a la redirecci� `%s' pot ser resultat d'una expressi� "
 "l�gica"
 
-#: io.c:664
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
-msgstr "mescla innecess�ria de �>� i �>>� per al fitxer �%.*s�"
+msgstr "mescla innecess�ria de `>' i `>>' per al fitxer `%.*s'"
 
-#: io.c:717
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
-msgstr "no es pot obrir la canonada �%s� per a l'eixida (%s)"
+msgstr "no es pot obrir la canonada `%s' per a l'eixida (%s)"
 
-#: io.c:727
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
-msgstr "no es pot obrir la canonada �%s� per a l'entrada (%s)"
+msgstr "no es pot obrir la canonada `%s' per a l'entrada (%s)"
 
-#: io.c:749
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr ""
-"no es pot obrir una canonada bidireccional �%s� per a les entrades/eixides "
+"no es pot obrir una canonada bidireccional `%s' per a les entrades/eixides "
 "(%s)"
 
-#: io.c:831
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
-msgstr "no es pot redirigir des de �%s� (%s)"
+msgstr "no es pot redirigir des de `%s' (%s)"
 
-#: io.c:834
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
-msgstr "no es pot redirigir cap a �%s� (%s)"
+msgstr "no es pot redirigir cap a `%s' (%s)"
 
-#: io.c:883
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "s'ha arribat al l�mit del sistema per a fitxers oberts: es comen�ar� a "
 "multiplexar els descriptors de fitxer"
 
-#: io.c:899
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
-msgstr "la finalitzaci� de �%s� ha fallat  (%s)"
+msgstr "la finalitzaci� de `%s' ha fallat  (%s)"
 
-#: io.c:907
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "masses canonades o fitxers d'entrada oberts"
 
-#: io.c:929
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
-msgstr "close: el segon argument hauria de ser �to� o �from�"
+msgstr "close: el segon argument hauria de ser `to' o `from'"
 
-#: io.c:946
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
-msgstr "close: �%.*s� no �s un fitxer obert, canonada o co-proc�s"
+msgstr "close: `%.*s' no �s un fitxer obert, canonada o co-proc�s"
 
-#: io.c:951
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "finalitzaci� d'una redirecci� que no s'ha obert"
 
-#: io.c:1048
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
-"close: la redirecci� �%s� no s'obre amb �|&�, s'ignora el segon argument"
+"close: la redirecci� `%s' no s'obre amb `|&', s'ignora el segon argument"
 
-#: io.c:1064
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
-msgstr "estaus de falla (%d) en la finalitzaci� de la canonada �%s� (%s)"
+msgstr "estat de fallada (%d) en la finalitzaci� de la canonada `%s' (%s)"
 
-#: io.c:1067
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
-msgstr "estatus de falla (%d) en la finalitzaci� del fitxer �%s� (%s)"
+msgstr "estat de falla (%d) en la finalitzaci� del fitxer `%s' (%s)"
 
-#: io.c:1087
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
-msgstr "no s'aporta la finalitzaci� expl�cita del socket �%s�"
+msgstr "no s'aporta la finalitzaci� expl�cita del socket `%s'"
 
-#: io.c:1090
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
-msgstr "no s'aporta la finalitzaci� expl�cita del co-proc�s �%s�"
+msgstr "no s'aporta la finalitzaci� expl�cita del co-proc�s `%s'"
 
-#: io.c:1093
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
-msgstr "no s'aporta la finalitzaci� expl�cita de la canonada �%s�"
+msgstr "no s'aporta la finalitzaci� expl�cita de la canonada `%s'"
 
-#: io.c:1096
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
-msgstr "no s'aporta la finalitzaci� expl�cita del fitxer �%s�"
+msgstr "no s'aporta la finalitzaci� expl�cita del fitxer `%s'"
 
-#: io.c:1124 io.c:1179 main.c:809 main.c:851
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
-msgstr "error a l'escriure en l'eixida est�ndard (%s)"
+msgstr "error en escriure a la sortida est�ndard (%s)"
 
-#: io.c:1128 io.c:1184
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
-msgstr "error a l'escriure en l'eixida d'error est�ndard (%s)"
+msgstr "error en escriure a la sortida d'error est�ndard (%s)"
 
-#: io.c:1136
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
-msgstr "la neteja de la canonada de �%sx� ha fallat (%s)."
+msgstr "la neteja de la canonada de `%sx' ha fallat (%s)."
 
-#: io.c:1139
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
-msgstr "la neteja de la canonada per al co-proc�s de �%sx� ha fallat (%s)."
+msgstr "la neteja de la canonada per al co-proc�s de `%sx' ha fallat (%s)."
 
-#: io.c:1142
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
-msgstr "la neteja del fitxer �%sx� ha fallat (%s)."
+msgstr "la neteja del fitxer `%s' ha fallat (%s)."
 
-#: io.c:1257
-#, fuzzy, c-format
+#: io.c:1420
+#, c-format
 msgid "local port %s invalid in `/inet'"
-msgstr "port local no v�lid en �%s�"
+msgstr "port local %s no v�lid a `/inet'"
 
-#: io.c:1274
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
-msgstr ""
+msgstr "amfitri� remot i informaci� de port (%s, %s) no v�lids"
 
-#: io.c:1426
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
-msgstr "no s'aporta cap protocol (conegut) en el nom del fitxer especial �%s�"
+msgstr "no s'aporta cap protocol (conegut) en el nom del fitxer especial `%s'"
 
-#: io.c:1440
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
-msgstr "el nom del fitxer especial �%s� est� incomplet"
+msgstr "el nom del fitxer especial `%s' est� incomplet"
 
-#: io.c:1457
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
-msgstr "s'ha de subministrar un nom de sistema remot a �/inet�"
+msgstr "s'ha de subministrar un nom de sistema remot a `/inet'"
 
-#: io.c:1475
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
-msgstr "s'ha de subministrar un port remot a �/inet�"
+msgstr "s'ha de subministrar un port remot a `/inet'"
 
-#: io.c:1521
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "les comunicacions TCP/IP no estan suportades"
 
-#: io.c:1688
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
-msgstr "no es pot obrir �%s�, mode �%s�"
+msgstr "no es pot obrir `%s', mode `%s'"
 
-#: io.c:1739
-#, fuzzy, c-format
+#: io.c:1917
+#, c-format
 msgid "close of master pty failed (%s)"
-msgstr "ha fallat la finalitzaci� de la canonada (%s)"
+msgstr "ha fallat el tancament del pty mestre (%s)"
 
-#: io.c:1741 io.c:1909 io.c:2066
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr ""
-"ha fallat la finalitzaci� de l'eixida est�ndard en els processos fills (%s)"
+"ha fallat la finalitzaci� de la sortida est�ndard en els processos fills (%s)"
 
-#: io.c:1744
-#, fuzzy, c-format
+#: io.c:1922
+#, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
-"ha fallat la redirecci� cap a l'eixida est�ndard dels processos fills (dup: "
-"%s)"
+"ha fallat el trasllat del pty esclau cap a l'eixida est�ndard dels processos "
+"fills (dup: %s)"
 
-#: io.c:1746 io.c:1914
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr ""
 "ha fallat la finalitzaci� de l'entrada est�ndard en els processos fills (%s)"
 
-#: io.c:1749
-#, fuzzy, c-format
+#: io.c:1927
+#, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
-"ha fallat la redirecci� cap a l'entrada est�ndard dels processos fills (dup: "
-"%s)"
+"ha fallat el trasllat del pty esclau cap a l'entrada est�ndard dels "
+"processos fills (dup: %s)"
 
-#: io.c:1751 io.c:1772
-#, fuzzy, c-format
+#: io.c:1929 io.c:1951
+#, c-format
 msgid "close of slave pty failed (%s)"
-msgstr "ha fallat la finalitzaci� de la canonada (%s)"
+msgstr "ha fallat el tancament del pty esclau (%s)"
 
-#: io.c:1850 io.c:1912 io.c:2044 io.c:2069
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 "ha fallat la redirecci� cap a l'eixida est�ndard dels processos fills (dup: "
 "%s)"
 
-#: io.c:1857 io.c:1917
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "ha fallat la redirecci� cap a l'entrada est�ndard dels processos fills (dup: "
 "%s)"
 
-#: io.c:1877 io.c:2059
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "ha fallat la restauraci� de l'eixida est�ndard en el proc�s pare\n"
 
-#: io.c:1885
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "ha fallat la restauraci� de l'entrada est�ndard en el proc�s pare\n"
 
-#: io.c:1920 io.c:2071 io.c:2085
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "ha fallat la finalitzaci� de la canonada (%s)"
 
-#: io.c:1965
+#: io.c:2174
 msgid "`|&' not supported"
-msgstr "�|&� no est� suportat"
+msgstr "`|&' no est� suportat"
 
-#: io.c:2031
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
-msgstr "no es pot obrir la canonada �%s� (%s)"
+msgstr "no es pot obrir la canonada `%s' (%s)"
 
-#: io.c:2079
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
-msgstr "no es pot crear el proc�s fill per a �%s� (fork: %s)"
+msgstr "no es pot crear el proc�s fill per a `%s' (fork: %s)"
+
+#: io.c:2790
+msgid "register_input_parser: received NULL pointer"
+msgstr "register_input_parser: s'ha rebut un punter nul"
 
-#: io.c:2569
+#: io.c:2818
 #, c-format
-msgid "data file `%s' is empty"
-msgstr "el fitxer de dades �%s� est� buit"
+msgid "input parser `%s' conflicts with previously installed input parser `%s'"
+msgstr ""
+"l'analitzador d'entrades `%s' est� en conflicte amb analitzador d'entrades `"
+"%s' instal�lat pr�viament"
 
-#: io.c:2610 io.c:2618
-msgid "could not allocate more input memory"
+#: io.c:2825
+#, c-format
+msgid "input parser `%s' failed to open `%s'"
+msgstr "l'analitzador d'entrada `%s' no ha pogut obrir `%s'"
+
+#: io.c:2845
+msgid "register_output_wrapper: received NULL pointer"
+msgstr "register_output_wrapper: s'ha rebut un punter nul"
+
+#: io.c:2873
+#, c-format
+msgid ""
+"output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
+"l'embolcall de sortida `%s' est� en conflicte amb l'embolcall de sortida `"
+"%s' instal�lat pr�viament"
 
-#: io.c:3171
-msgid "multicharacter value of `RS' is a gawk extension"
-msgstr "el valor multicar�cter de �RS� �s una extensi� de gawk"
+#: io.c:2880
+#, c-format
+msgid "output wrapper `%s' failed to open `%s'"
+msgstr "l'embolcall de sortida `%s' no ha pogut obrir `%s'"
 
-#: io.c:3276
-#, fuzzy
-msgid "IPv6 communication is not supported"
-msgstr "les comunicacions TCP/IP no estan suportades"
+#: io.c:2901
+msgid "register_output_processor: received NULL pointer"
+msgstr "register_output_processor: s'ha rebut un punter nul"
 
-#: main.c:307
-msgid "out of memory"
-msgstr "mem�ria esgotada"
+#: io.c:2930
+#, c-format
+msgid ""
+"two-way processor `%s' conflicts with previously installed two-way processor "
+"`%s'"
+msgstr ""
+"el processsador de dues vies `%s' est� en conflicte amb el processador de "
+"dues vies `%s' instal�lat pr�viament"
 
-#: main.c:384
-msgid "`-m[fr]' option irrelevant in gawk"
-msgstr "l'opci�n �-m[fr]� �s irrellevant en gawk"
+#: io.c:2939
+#, c-format
+msgid "two way processor `%s' failed to open `%s'"
+msgstr "el processador de dues vies `%s' no ha pogut obrir `%s'"
+
+#: io.c:3064
+#, c-format
+msgid "data file `%s' is empty"
+msgstr "el fitxer de dades `%s' est� buit"
 
-#: main.c:386
-msgid "-m option usage: `-m[fr] nnn'"
-msgstr "�s de l'opci� -m: �-m[fr] nnn�"
+#: io.c:3106 io.c:3114
+msgid "could not allocate more input memory"
+msgstr "no s'ha pogut assignar m�s mem�ria d'entrada"
+
+#: io.c:3682
+msgid "multicharacter value of `RS' is a gawk extension"
+msgstr "el valor multicar�cter de `RS' �s una extensi� de gawk"
 
-#: main.c:409
-#, fuzzy
+#: io.c:3771
+msgid "IPv6 communication is not supported"
+msgstr "la comunicaci� IPv6 no est� suportada"
+
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
-msgstr "s'igonar� l'argument buit per a l'opci� �--source�"
+msgstr "s'ignonar� l'argument buit de `-e/--source'"
 
-#: main.c:475
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
-msgstr "%s: no es reconeix l'opci� �-W %s�, ser� ignorada\n"
+msgstr "%s: no es reconeix l'opci� `-W %s', ser� ignorada\n"
 
-#: main.c:528
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: l'opci� requereix un argument -- %c\n"
 
-#: main.c:549
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
-"la variable d'entorn �POSIXLY_CORRECT� est� establerta: usant �--posix�"
+"la variable d'entorn `POSIXLY_CORRECT' est� establerta: usant `--posix'"
 
-#: main.c:555
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
-msgstr "�--posix� solapa a �--traditional�"
+msgstr "`--posix' solapa a `--traditional'"
 
-#: main.c:566
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
-msgstr "�--posix� i �--traditional� solapen a �--non-decimal-data�"
+msgstr "`--posix' i `--traditional' solapen a `--non-decimal-data'"
 
-#: main.c:570
-#, fuzzy, c-format
+#: main.c:583
+#, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "executar %s com a setuid root pot ser un problema de seguretat"
 
-#: main.c:575
-#, fuzzy
-msgid "`--posix' overrides `--binary'"
-msgstr "�--posix� solapa a �--traditional�"
+#: main.c:588
+msgid "`--posix' overrides `--characters-as-bytes'"
+msgstr "`--posix' anul�la a `--characters-as-bytes'"
 
-#: main.c:626
-#, fuzzy, c-format
+#: main.c:647
+#, c-format
 msgid "can't set binary mode on stdin (%s)"
-msgstr "no es pot establir el mode en l'entrada est�ndard (%s)"
+msgstr "no es pot establir el mode binari en l'entrada est�ndard (%s)"
 
-#: main.c:629
-#, fuzzy, c-format
+#: main.c:650
+#, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "no es pot establir el mode en l'eixida est�ndard (%s)"
 
-#: main.c:631
-#, fuzzy, c-format
+#: main.c:652
+#, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "no es pot establir el mode en l'eixida d'error est�ndard (%s)"
 
-#: main.c:670
+#: main.c:710
 msgid "no program text at all!"
 msgstr "no hi ha cap text per al programa!"
 
-#: main.c:749
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr "�s: %s [opcions d'estil POSIX o GNU] -f fitx_prog [--] fitxer ...\n"
 
-#: main.c:751
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr "�s: %s [opcions d'estil POSIX o GNU] [--] %cprograma%c fitxer ...\n"
 
-#: main.c:756
-#, fuzzy
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
-msgstr "Opcions POSIX:\t\tOpcions llargues GNU:\n"
+msgstr "Opcions POSIX:\t\tOpcions llargues GNU: (est�ndard)\n"
 
-#: main.c:757
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f fitx_prog\t\t--file=fitx_prog\n"
 
-#: main.c:758
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs (fs=sep_camp)\n"
 
-#: main.c:759
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=valor\t\t--assign=var=valor\n"
 
-#: main.c:760
-#, fuzzy
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
-msgstr "Opcions POSIX:\t\tOpcions llargues GNU:\n"
+msgstr "Opcions curtes:\t\tOpcions llargues GNU: (extensions)\n"
 
-#: main.c:761
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
-msgstr ""
+msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:762
-#, fuzzy
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
-msgstr "\t-W traditional\t\t--traditional\n"
+msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:763
-#, fuzzy
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
-msgstr "\t-W copyright\t\t--copyright\n"
+msgstr "\t-C\t\t\t--copyright\n"
+
+#: main.c:814
+msgid "\t-d[file]\t\t--dump-variables[=file]\n"
+msgstr "\t-d[file]\t\t--dump-variables[=file]\n"
 
-#: main.c:764
-#, fuzzy
-msgid "\t-d [file]\t\t--dump-variables[=file]\n"
-msgstr "\t-W dump-variables[=fitxer] --dump-variables[=fitxer]\n"
+#: main.c:815
+msgid "\t-D[file]\t\t--debug[=file]\n"
+msgstr "\t-D[file]\t\t--debug[=file]\n"
 
-#: main.c:765
-#, fuzzy
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
-msgstr "\t-W source=text_prog\t--source=text_prog\n"
+msgstr "\t-e 'program-text'\t--source='program-text'\n"
 
-#: main.c:766
-#, fuzzy
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
-msgstr "\t-W profile[=fitxer]\t--profile[=fitxer]\n"
+msgstr "\t-E file\t\t\t--exec=file\n"
 
-#: main.c:767
-#, fuzzy
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
-msgstr "\t-W gen-po\t\t--gen-po\n"
+msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:768
-#, fuzzy
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
-msgstr "\t-W help\t\t\t--help\n"
+msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:769
-#, fuzzy
+#: main.c:820
+msgid "\t-i includefile\t\t--include=includefile\n"
+msgstr "\t-i includefile\t\t--include=fitxer a incloure\n"
+
+#: main.c:821
+msgid "\t-l library\t\t--load=library\n"
+msgstr "\t-l library\t\t--load=biblioteca\n"
+
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
-msgstr "\t-W lint[=fatal]\t\t--lint[=fatal]\n"
+msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:770
-#, fuzzy
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
-msgstr "\t-W non-decimal-data\t--non-decimal-data\n"
+msgstr "\t-n\t\t\t--non-decimal-data\n"
+
+#: main.c:824
+msgid "\t-M\t\t\t--bignum\n"
+msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:771
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
-msgstr ""
+msgstr "\t-N\t\t\t--use-lc-numeric\n"
+
+#: main.c:826
+msgid "\t-o[file]\t\t--pretty-print[=file]\n"
+msgstr "\t-o[file]\t\t--pretty-print[=file]\n"
 
-#: main.c:772
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
-msgstr ""
+msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:773
-#, fuzzy
-msgid "\t-p [file]\t\t--profile[=file]\n"
-msgstr "\t-W profile[=fitxer]\t--profile[=fitxer]\n"
+#: main.c:828
+msgid "\t-p[file]\t\t--profile[=file]\n"
+msgstr "\t-p[file]\t\t--profile[=file]\n"
 
-#: main.c:774
-#, fuzzy
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
-msgstr "\t-W posix\t\t--posix\n"
+msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:775
-#, fuzzy
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
-msgstr "\t-W re-interval\t\t--re-interval\n"
+msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:777
-#, fuzzy
-msgid "\t-R file\t\t\t--command=file\n"
-msgstr "\t-W profile[=fitxer]\t--profile[=fitxer]\n"
-
-#: main.c:778
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
-msgstr ""
+msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:779
-#, fuzzy
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
-msgstr "\t-W lint-old\t\t--lint-old\n"
+msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:780
-#, fuzzy
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
-msgstr "\t-W version\t\t--version\n"
+msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:782
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:785
-#, fuzzy
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
-msgstr "\t-W parsedebug\t\t--parsedebug\n"
+msgstr "\t-Y\t\t--parsedebug\n"
 
 #. TRANSLATORS: --help output 5 (end)
 #. TRANSLATORS: the placeholder indicates the bug-reporting address
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:794
-#, fuzzy
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
 "section `Reporting Problems and Bugs' in the printed version.\n"
 "\n"
-msgstr "a la secci� �Reporting Problems and Bugs� de la versi� impresa.\n"
+msgstr ""
+"\n"
+"Per informar d'errors, vegeu el node `Bugs' a `gawk.info', que\n"
+"�s la secci� `Informant sobre problemes i errors' a la versi� impresa.\n"
+"Informeu dels errors de traducci� a <ca@li.org>\n"
 
-#: main.c:798
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
 "\n"
 msgstr ""
+"gawk �s un llenguatge d'an�lisi i processament de patrons.\n"
+"De forma predeterminada llegeix l'entrada est�ndard i escriu a la sortida "
+"est�ndar.\n"
 
-#: main.c:802
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 msgstr ""
+"Exemples:\n"
+"\tgawk '{ sum += $1 }; END { print sum }' fitxer\n"
+"\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:822
-#, fuzzy, c-format
+#: main.c:880
+#, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
 "\n"
@@ -1774,11 +3214,11 @@ msgstr ""
 "\n"
 "Aquest programa �s programari lliure; pot redistribuir-se i/o modificar-se\n"
 "sota els termes de la Llic�ncia P�blica General de GNU tal i como est�\n"
-"publicada per la Free Software Foundation; ja siga en la versi� 2 de la\n"
+"publicada per la Free Software Foundation; ja siga en la versi� 3 de la\n"
 "Llic�ncia, o (a la vostra elecci�) qualsevol versi� posterior.\n"
 "\n"
 
-#: main.c:830
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -1792,145 +3232,204 @@ msgstr ""
 "Per a m�s detalls consulteu la Llic�ncia P�blica General de GNU.\n"
 "\n"
 
-#: main.c:841
-#, fuzzy
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
 msgstr ""
-"Junt amb aquest programa haur�eu d'haber rebut una c�pia de la Llic�ncia\n"
-"P�blica General de GNU; si no �s aix�, escriviu a la Free Software\n"
-"Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.\n"
+"Junt amb aquest programa haur�eu d'haver rebut una c�pia de la Llic�ncia\n"
+"P�blica General de GNU; si no �s aix�, vegeu http://www.gnu.org/licenses/.\n"
 
-#: main.c:876
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft no permet inicialitzar FS a un tabulador en la versi� POSIX de awk"
 
-#: main.c:1110
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
-msgstr ""
+msgstr "valor desconegut per a l'especificaci� de camp: %d\n"
 
-#: main.c:1170
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
 "\n"
 msgstr ""
+"%s: `%s' l'argument per a `-v' no est� en forma `var=valor'\n"
+"\n"
 
-#: main.c:1190
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
-msgstr ""
+msgstr "`%s' no �s nom legal de variable"
 
-#: main.c:1193
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
+msgstr "`%s' no �s un valor de variable, s'esperava fitxer `%s=%s'"
+
+#: main.c:1339
+#, c-format
+msgid "cannot use gawk builtin `%s' as variable name"
 msgstr ""
+"no es pot usar el nom de la funci� integrada `%s' com a nom de variable"
+
+#: main.c:1344
+#, c-format
+msgid "cannot use function `%s' as variable name"
+msgstr "no es pot usar el nom de la funci� interna `%s' com nom de variable"
 
-#: main.c:1246
+#: main.c:1397
 msgid "floating point exception"
 msgstr "excepci� de coma flotant"
 
-#: main.c:1253
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "error fatal: error intern"
 
-#: main.c:1268
-#, fuzzy
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
-msgstr "error fatal: error intern"
+msgstr "error fatal: error intern: segfault"
 
-#: main.c:1280
-#, fuzzy
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
-msgstr "error fatal: error intern"
+msgstr "error fatal: error intern: sobreeiximent de pila"
 
-#: main.c:1330
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "no s'ha pre-obert el descriptor fd per a %d"
 
-#: main.c:1337
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "no es pot pre-obrir /dev/null per al descriptor fd %d"
 
-#: main.c:1360 main.c:1369
+#: mpfr.c:550
+#, c-format
+msgid "PREC value `%.*s' is invalid"
+msgstr "Valor PREC `%.*s' no �s v�lid"
+
+#: mpfr.c:608
+#, c-format
+msgid "RNDMODE value `%.*s' is invalid"
+msgstr "Valor RNDMODE `%.*s' no �s v�lid"
+
+#: mpfr.c:698
+#, c-format
+msgid "%s: received non-numeric argument"
+msgstr "%s: s'ha rebut un argument que no �s num�ric"
+
+#: mpfr.c:800
+msgid "compl(%Rg): negative value will give strange results"
+msgstr "compl(%Rg): el valor negatiu donar� resultats estranys"
+
+#: mpfr.c:804
+msgid "comp(%Rg): fractional value will be truncated"
+msgstr "compl(%Rg): el valor fraccionari ser� truncat"
+
+#: mpfr.c:816
+#, c-format
+msgid "cmpl(%Zd): negative values will give strange results"
+msgstr "cmpl(%Zd): els valors negatius donaran resultats estranys"
+
+#: mpfr.c:835
+#, c-format
+msgid "%s: received non-numeric argument #%d"
+msgstr "%s: s'ha rebut un argument no num�ric #%d"
+
+#: mpfr.c:845
+msgid "%s: argument #%d has invalid value %Rg, using 0"
+msgstr "%s: l'argument #%d t� valor no v�lid %Rg, s'usar� 0"
+
+#: mpfr.c:857
+msgid "%s: argument #%d negative value %Rg will give strange results"
+msgstr "%s: l'argument #%d amb valor negatiu %Rg donar� resultats estranys"
+
+#: mpfr.c:863
+msgid "%s: argument #%d fractional value %Rg will be truncated"
+msgstr "%s: l'argument #%d amb valor fraccional %Rg ser� truncat"
+
+#: mpfr.c:878
 #, c-format
-msgid "could not find groups: %s"
-msgstr "no es poden trobar els grups: %s"
+msgid "%s: argument #%d negative value %Zd will give strange results"
+msgstr "%s: l'argument #%d amb valor negatiu %Zd donar� resultats estranys"
 
-#: msg.c:63
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "l�nia cmd.:"
 
-#: msg.c:107
-msgid "error: "
-msgstr "Error: "
-
-#: node.c:401
+#: node.c:421
 msgid "backslash at end of string"
 msgstr "barra invertida al final de la cadena"
 
-#: node.c:502
-#, fuzzy, c-format
+#: node.c:500
+#, c-format
 msgid "old awk does not support the `\\%c' escape sequence"
-msgstr "l'antic awk no suporta l'operador �**=�"
+msgstr "l'antic awk no d�na suport a la seq�encia d'escapada `\\%c'"
 
-#: node.c:553
+#: node.c:551
 msgid "POSIX does not allow `\\x' escapes"
-msgstr "POSIX no permet seq��ncies d'escapada �\\x�"
+msgstr "POSIX no permet seq��ncies d'escapada `\\x'"
 
-#: node.c:559
+#: node.c:557
 msgid "no hex digits in `\\x' escape sequence"
-msgstr "no hi ha d�gits hexadecimals en la seq��ncia d'escapada �\\x�"
+msgstr "no hi ha d�gits hexadecimals en la seq��ncia d'escapada `\\x'"
 
-#: node.c:581
+#: node.c:579
 #, c-format
 msgid ""
 "hex escape \\x%.*s of %d characters probably not interpreted the way you "
 "expect"
 msgstr ""
+"probablement no s'han interpretat els car�cters hex escape \\x%.*s of %d de "
+"la manera que esper�veu"
 
-#: node.c:596
+#: node.c:594
 #, c-format
 msgid "escape sequence `\\%c' treated as plain `%c'"
-msgstr "la seq��ncia d'escapada �\\%c� �s tractada com a una simple �%c�"
+msgstr "la seq��ncia d'escapada `\\%c' �s tractada com a una simple `%c'"
 
-#: node.c:735
+#: node.c:739
 msgid ""
 "Invalid multibyte data detected. There may be a mismatch between your data "
 "and your locale."
 msgstr ""
+"S'han detectat dades multibyte no v�lides. Pot haver-hi una discordan�a "
+"entre les vostres dades i la vostra configuraci� local"
 
-#: posix/gawkmisc.c:175
-#, fuzzy, c-format
+#: posix/gawkmisc.c:177
+#, c-format
 msgid "%s %s `%s': could not get fd flags: (fcntl F_GETFD: %s)"
-msgstr "%s %s �%s�: no es pot inicialitzar close-on-exec: (fcntl: %s)"
+msgstr ""
+"%s %s `%s': no s'han pogut obtenir els indicadors fd: (fcntl F_GETFD: %s)"
 
-#: posix/gawkmisc.c:187
-#, fuzzy, c-format
+#: posix/gawkmisc.c:189
+#, c-format
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
-msgstr "%s %s �%s�: no es pot inicialitzar close-on-exec: (fcntl: %s)"
+msgstr "%s %s `%s': no s'ha pogut establir close-on-exec: (fcntl F_SETFD: %s)"
 
-#: profile.c:83
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
-msgstr "no es pot obrir �%s� per a escriptura: %s"
+msgstr "no es pot obrir `%s' per a escriptura: %s"
 
-#: profile.c:203
-#, fuzzy, c-format
+#: profile.c:73
+msgid "sending profile to standard error"
+msgstr "enviant el perfil a l'eixida d'error est�ndard"
+
+#: profile.c:193
+#, c-format
 msgid ""
 "\t# %s block(s)\n"
 "\n"
 msgstr ""
-"\t# Bloc(s) FINAL\n"
+"\t# %s bloc(s)\n"
 "\n"
 
-#: profile.c:208
-#, fuzzy, c-format
+#: profile.c:198
+#, c-format
 msgid ""
 "\t# Rule(s)\n"
 "\n"
@@ -1938,17 +3437,30 @@ msgstr ""
 "\t# Regla(es)\n"
 "\n"
 
-#: profile.c:279
-#, fuzzy, c-format
+#: profile.c:272
+#, c-format
 msgid "internal error: %s with null vname"
-msgstr "error intern: Node_var amb vname nul"
+msgstr "error intern: %s amb vname nul"
+
+#: profile.c:537
+msgid "internal error: builtin with null fname"
+msgstr "error intern: funci� integrada amb fname nul"
 
-#: profile.c:938
+#: profile.c:949
+#, c-format
+msgid ""
+"\t# Loaded extensions (-l and/or @load)\n"
+"\n"
+msgstr ""
+"\t# Extensions carregades (-l i/o @load)\n"
+"\n"
+
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# perfil gawk, creat %s\n"
 
-#: profile.c:1317
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -1957,152 +3469,137 @@ msgstr ""
 "\n"
 "\t# Funcions, llistades alfab�ticament\n"
 
-#: profile.c:1356
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
-msgstr ""
+msgstr "redir2str: tipus desconegut de redireccionament %d"
 
-#: re.c:589
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependant"
-msgstr ""
-
-#: re.c:611
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
-msgstr ""
+msgstr "el component regexp `%.*s' probablement hauria de ser `[%.*s]'"
 
-#: regcomp.c:132
+#: regcomp.c:131
 msgid "Success"
 msgstr "�xit"
 
-#: regcomp.c:135
+#: regcomp.c:134
 msgid "No match"
 msgstr "No hi ha concordan�a"
 
-#: regcomp.c:138
+#: regcomp.c:137
 msgid "Invalid regular expression"
 msgstr "Expressi� regular no v�lida"
 
-#: regcomp.c:141
+#: regcomp.c:140
 msgid "Invalid collation character"
 msgstr "Car�cter de comparaci� no v�lid"
 
-#: regcomp.c:144
+#: regcomp.c:143
 msgid "Invalid character class name"
 msgstr "Nom de classe de car�cters no v�lid"
 
-#: regcomp.c:147
+#: regcomp.c:146
 msgid "Trailing backslash"
 msgstr "Barra invertida extra al final"
 
-#: regcomp.c:150
+#: regcomp.c:149
 msgid "Invalid back reference"
-msgstr "Refer�ncia cap enradera no v�lida"
+msgstr "Refer�ncia cap endarrere no v�lida"
 
-#: regcomp.c:153
+#: regcomp.c:152
 msgid "Unmatched [ or [^"
 msgstr "[ o [^ desemparellats"
 
-#: regcomp.c:156
+#: regcomp.c:155
 msgid "Unmatched ( or \\("
 msgstr "( o \\( desemparellats"
 
-#: regcomp.c:159
+#: regcomp.c:158
 msgid "Unmatched \\{"
 msgstr "\\{ desemparellat"
 
-#: regcomp.c:162
-msgid "Invalid content of \\{\\}"
-msgstr "Contingut no v�lid de \\{\\}"
-
-#: regcomp.c:165
+#: regcomp.c:164
 msgid "Invalid range end"
 msgstr "Final de rang no v�lid"
 
-#: regcomp.c:168
+#: regcomp.c:167
 msgid "Memory exhausted"
 msgstr "Mem�ria exhaurida"
 
-#: regcomp.c:171
+#: regcomp.c:170
 msgid "Invalid preceding regular expression"
 msgstr "Expressi� regular precedent no v�lida"
 
-#: regcomp.c:174
+#: regcomp.c:173
 msgid "Premature end of regular expression"
 msgstr "F� prematura de l'expressi� regular"
 
-#: regcomp.c:177
-msgid "Regular expression too big"
-msgstr "L'expressi� regular �s massa gran"
-
-#: regcomp.c:180
+#: regcomp.c:179
 msgid "Unmatched ) or \\)"
 msgstr ") o \\) desemparellats"
 
-#: regcomp.c:701
+#: regcomp.c:704
 msgid "No previous regular expression"
 msgstr "No hi ha una expressi� regular pr�via"
 
-#~ msgid "statement may have no effect"
-#~ msgstr "la declaraci� podria no tindre efecte"
+#: symbol.c:741
+msgid "can not pop main context"
+msgstr "no es pot mostrar el context principal"
 
-#~ msgid "attempt to use scalar `%s' as array"
-#~ msgstr "s'ha intentat usar la dada escalar �%s� com a una matriu"
+#~ msgid "reference to uninitialized element `%s[\"%s\"]'"
+#~ msgstr "refer�ncia a un element sense valor inicial `%s[\"%s\"]'"
 
-#, fuzzy
-#~ msgid "attempt to use array `%s' in scalar context"
-#~ msgstr "s'ha intentat usar la matriu �%s� en un context escalar"
+#~ msgid "subscript of array `%s' is null string"
+#~ msgstr "el subscript de la matriu `%s' �s una cadena nul�la"
 
-#~ msgid "`continue' outside a loop is not allowed"
-#~ msgstr "no es permet �continue� a fora d'un bucle"
+#~ msgid "delete: illegal use of variable `%s' as array"
+#~ msgstr "delete: �s il�legal de la variable `%s' com a una matriu"
 
-#, fuzzy
-#~ msgid "`break' outside a loop is not allowed"
-#~ msgstr "no es permet �break� a fora d'un bucle"
+#~ msgid "%s: empty (null)\n"
+#~ msgstr "%s: buit (nul)\n"
 
-#~ msgid "/inet/raw client not ready yet, sorry"
-#~ msgstr "el client /inet/raw encara no est� a punt, ho sento"
+#~ msgid "%s: empty (zero)\n"
+#~ msgstr "%s: buit (zero)\n"
 
-#~ msgid "only root may use `/inet/raw'."
-#~ msgstr "sols el root pot usar �/inet/raw�."
+#~ msgid "%s: table_size = %d, array_size = %d\n"
+#~ msgstr "%s: mida_taula = %d, mida_matriu = %d\n"
 
-#~ msgid "/inet/raw server not ready yet, sorry"
-#~ msgstr "el servidor /inet/raw encara no est� a punt, ho sento"
+#~ msgid "%s: array_ref to %s\n"
+#~ msgstr "%s: ref_matriu a %s\n"
 
-#~ msgid "\t-m[fr] val\n"
-#~ msgstr "\t-m[fr] valor\n"
+#~ msgid "and: received non-numeric first argument"
+#~ msgstr "and: el primer argument rebut no �s num�ric"
 
-#~ msgid "call of `length' without parentheses is deprecated by POSIX"
-#~ msgstr "la crida de �length� sense par�ntesis est� desaprovada per POSIX"
+#~ msgid "or: received non-numeric first argument"
+#~ msgstr "or: el primer argument rebut no �s num�ric"
 
-#, fuzzy
-#~ msgid "reference to uninitialized field `$%s'"
-#~ msgstr "refer�ncia a una variable sense inicialitzar �%s�"
+#~ msgid "or(%lf, %lf): negative values will give strange results"
+#~ msgstr "or(%lf, %lf): els valors negatius donaran resultats estranys"
 
-#~ msgid "can't convert string to float"
-#~ msgstr "no es pot convertir la cadena a coma flotant"
+#~ msgid "or(%lf, %lf): fractional values will be truncated"
+#~ msgstr "or(%lf, %lf): els valors fraccionaris seran truncats"
 
-#~ msgid "`continue' outside a loop is not portable"
-#~ msgstr "�continue� fora d'un bucle no �s portable"
+#~ msgid "xor: received non-numeric first argument"
+#~ msgstr "xor: el primer argument rebut no �s num�ric"
 
-#~ msgid "`break' outside a loop is not portable"
-#~ msgstr "�break� a fora d'un bucle no �s portable"
+#~ msgid "xor(%lf, %lf): fractional values will be truncated"
+#~ msgstr "xor(%lf, %lf): els valors fraccionaris seran truncats"
 
-#~ msgid "`nextfile' cannot be called from a BEGIN rule"
-#~ msgstr "�nextfile� no es pot cridar des d'una regla BEGIN"
+#~ msgid "Operation Not Supported"
+#~ msgstr "Operaci� No Suportada"
 
-#~ msgid "`next' cannot be called from a BEGIN rule"
-#~ msgstr "�next� no es pot cridar des d'una regla BEGIN"
+#~ msgid "%s: illegal option -- %c\n"
+#~ msgstr "%s: opci� il�legal -- %c\n"
 
-#~ msgid "file `%s' is a directory"
-#~ msgstr "el fitxer �%s� �s un directori"
+#~ msgid "`-m[fr]' option irrelevant in gawk"
+#~ msgstr "l'opci�n `-m[fr]' �s irrellevant en gawk"
 
-#~ msgid "use `PROCINFO[\"%s\"]' instead of `%s'"
-#~ msgstr "useu �PROCINFO[\"%s\"]� en comptes de �%s�"
+#~ msgid "-m option usage: `-m[fr] nnn'"
+#~ msgstr "�s de l'opci� -m: `-m[fr] nnn'"
 
-#~ msgid "use `PROCINFO[...]' instead of `/dev/user'"
-#~ msgstr "useu �PROCINFO[...]� en comptes de �/dev/user�"
+#~ msgid "\t-m[fr] val\n"
+#~ msgstr "\t-m[fr] valor\n"
 
 #~ msgid "\t-W compat\t\t--compat\n"
 #~ msgstr "\t-W compat\t\t--compat\n"
@@ -2114,159 +3611,152 @@ msgstr "No hi ha una expressi� regular pr�via"
 #~ msgstr "\t-W usage\t\t--usage\n"
 
 #~ msgid ""
-#~ "\t# BEGIN block(s)\n"
 #~ "\n"
+#~ "To report bugs, see node `Bugs' in `gawk.info', which is\n"
 #~ msgstr ""
-#~ "\t# Bloc(s) INICI\n"
 #~ "\n"
+#~ "Per a informar d'errors, consulteu el node �Bugs' en �gawk.info', que "
+#~ "est�\n"
 
-#~ msgid "`$' is not permitted in awk formats"
-#~ msgstr "no es permeten �$� en els formats awk"
-
-#~ msgid "arg count with `$' must be > 0"
-#~ msgstr "el compte d'arguments amb �$� ha de ser > 0"
-
-#, fuzzy
-#~ msgid "arg count %ld greater than total number of supplied arguments"
-#~ msgstr ""
-#~ "el comte d'arguments %d �s major que el nombre total d'arguments "
-#~ "proporcionats"
-
-#~ msgid "`$' not permitted after period in format"
-#~ msgstr "no es permet �$� despr�s d'un punt en el format"
-
-#~ msgid "no `$' supplied for positional field width or precision"
-#~ msgstr "no es proporciona �$� per a l'ample o precisi� del camp de posici�"
-
-#~ msgid "`l' is meaningless in awk formats; ignored"
-#~ msgstr "�l� manca de significat en els formats awk; ser� ignorat"
-
-#~ msgid "`l' is not permitted in POSIX awk formats"
-#~ msgstr "�l� no est� perm�s en els formats POSIX de awk"
-
-#~ msgid "`L' is meaningless in awk formats; ignored"
-#~ msgstr "�L� manca de significat en els formats awk; ser� ignorat"
-
-#~ msgid "`L' is not permitted in POSIX awk formats"
-#~ msgstr "�L� no est� perm�s en els formats POSIX de awk"
-
-#~ msgid "`h' is meaningless in awk formats; ignored"
-#~ msgstr "�h� manca de significat en els formats awk; ser� ignorat"
-
-#~ msgid "`h' is not permitted in POSIX awk formats"
-#~ msgstr "�h� no est� perm�s en els formats POSIX de awk"
-
-#~ msgid "not enough arguments to satisfy format string"
-#~ msgstr "no hi ha prou arguments per a satisfer el format d'una cadena"
-
-#~ msgid "^ ran out for this one"
-#~ msgstr "^ desbordament per a aquest"
-
-#~ msgid "[s]printf: format specifier does not have control letter"
-#~ msgstr "[s]printf: l'especificador de format no cont� lletra de control"
-
-#~ msgid "too many arguments supplied for format string"
-#~ msgstr "s'han proporcionat masses arguments per a la cadena de format"
-
-#, fuzzy
-#~ msgid "attempt to use array parameter `%s' in a scalar context"
-#~ msgstr "s'ha intentat usar la matriu �%s� en un context escalar"
+#~ msgid "invalid syntax in name `%s' for variable assignment"
+#~ msgstr "sintaxi no v�lida en el nom �%s' per a l'asignaci� de la variable"
 
-#~ msgid "can't open two way socket `%s' for input/output (%s)"
-#~ msgstr ""
-#~ "no es pot obrir un socket bidireccional �%s� per a les entrades/eixides "
-#~ "(%s)"
+#~ msgid "could not find groups: %s"
+#~ msgstr "no es poden trobar els grups: %s"
 
-#~ msgid "%s: illegal option -- %c\n"
-#~ msgstr "%s: opci� il�legal -- %c\n"
+#~ msgid "internal error: Node_var_array with null vname"
+#~ msgstr "error intern: Node_var_array amb vname nul"
 
-#~ msgid ""
-#~ "concatenation: side effects in one expression have changed the length of "
-#~ "another!"
-#~ msgstr ""
-#~ "concatenaci�: els efectes colaterals en una expressi� han canviat la "
-#~ "longitud d'una altra!"
+#~ msgid "or used in other expression context"
+#~ msgstr "o s'ha emprat en un altre context de l'expressi�"
 
 #~ msgid "illegal type (%s) in tree_eval"
 #~ msgstr "tipus il�legal (%s) en tree_eval"
 
-#~ msgid "\t# -- main --\n"
-#~ msgstr "\t# -- principal --\n"
+#~ msgid "attempt to use function `%s' as array"
+#~ msgstr "s'ha intentat usar la funci� �%s� com a una matriu"
 
-#~ msgid "invalid tree type %s in redirect()"
-#~ msgstr "tipus d'arbre %s no v�lid dintre de redirect()"
-
-#~ msgid "unexpected type %s in prec_level"
-#~ msgstr "tipus %s inesperat en prec_level"
-
-#, fuzzy
-#~ msgid "Unknown node type %s in pp_var"
-#~ msgstr "tipo de node %d desconegut"
+#~ msgid "`%s' is a function, assignment is not allowed"
+#~ msgstr "�%s� �s una funci�, l'assignaci� no �s permesa"
 
-#~ msgid "delete: illegal use of variable `%s' as array"
-#~ msgstr "delete: �s il�legal de la variable �%s� com a una matriu"
+#~ msgid "assignment is not allowed to result of builtin function"
+#~ msgstr ""
+#~ "no es permet l'assignaci� per a obtindre un resultat d'una funci� interna"
 
 #~ msgid ""
+#~ "\t# BEGIN block(s)\n"
 #~ "\n"
-#~ "To report bugs, see node `Bugs' in `gawk.info', which is\n"
 #~ msgstr ""
+#~ "\t# Bloc(s) INICI\n"
 #~ "\n"
-#~ "Per a informar d'errors, consulteu el node �Bugs� en �gawk.info�, que "
-#~ "est�\n"
-
-#~ msgid "invalid syntax in name `%s' for variable assignment"
-#~ msgstr "sintaxi no v�lida en el nom �%s� per a l'asignaci� de la variable"
-
-#~ msgid "internal error: Node_var_array with null vname"
-#~ msgstr "error intern: Node_var_array amb vname nul"
-
-#~ msgid "or used in other expression context"
-#~ msgstr "o s'ha emprat en un altre context de l'expressi�"
 
-#~ msgid "`%s' is a function, assignment is not allowed"
-#~ msgstr "�%s� �s una funci�, l'assignaci� no �s permesa"
+#~ msgid "unexpected type %s in prec_level"
+#~ msgstr "tipus %s inesperat en prec_level"
 
 #~ msgid "BEGIN blocks must have an action part"
 #~ msgstr "Els blocs INICI han de tindre una part d'acci�"
 
-#~ msgid "`nextfile' used in BEGIN or END action"
-#~ msgstr "�nextfile� �s usat dintre de l'acci� BEGIN o END"
+#~ msgid "statement may have no effect"
+#~ msgstr "la declaraci� podria no tindre efecte"
 
 #~ msgid "non-redirected `getline' undefined inside BEGIN or END action"
 #~ msgstr "�getline� no redirigit sense definir dintre de l'acci� BEGIN o END"
 
+#~ msgid "call of `length' without parentheses is deprecated by POSIX"
+#~ msgstr "la crida de �length� sense par�ntesis est� desaprovada per POSIX"
+
 #~ msgid "fptr %x not in tokentab\n"
 #~ msgstr "fptr %x no est� en la taula de refer�ncia\n"
 
+#~ msgid "`%s' is a Bell Labs extension"
+#~ msgstr "�%s� �s una extensi� de Bell Labs"
+
 #~ msgid "gsub third parameter is not a changeable object"
 #~ msgstr "gsub: el tercer argument no �s un objecte intercanviable"
 
-#~ msgid "Unfinished \\ escape"
-#~ msgstr "seq��ncia d'escapada \\ sense finalitzar"
-
 #~ msgid "unfinished repeat count"
 #~ msgstr "repetici� del comptador sense finalitzar"
 
 #~ msgid "malformed repeat count"
 #~ msgstr "repetici� del comptador malformada"
 
-#~ msgid "Unbalanced ["
-#~ msgstr "[ sense aparellar"
+#~ msgid "out of memory"
+#~ msgstr "mem�ria esgotada"
 
-#~ msgid "Unbalanced ("
-#~ msgstr "( sense aparellar"
+#~ msgid "field %d in FIELDWIDTHS, must be > 0"
+#~ msgstr "el camp %d en FIELDWIDTHS, hauria de ser > 0"
 
-#~ msgid "No regexp syntax bits specified"
-#~ msgstr "No s'especifiquen els bits de sintaxi de l'expressi� regular"
+#~ msgid ""
+#~ "for loop: array `%s' changed size from %d to %d during loop execution"
+#~ msgstr ""
+#~ "bucle for: la matriu �%s� ha canviat de mida de %d a %d durant l'execuci� "
+#~ "del bucle"
 
-#~ msgid "Unbalanced )"
-#~ msgstr ") sense aparellar"
+#~ msgid "`break' outside a loop is not portable"
+#~ msgstr "�break� a fora d'un bucle no �s portable"
 
-#~ msgid "field %d in FIELDWIDTHS, must be > 0"
-#~ msgstr "el camp %d en FIELDWIDTHS, hauria de ser > 0"
+#~ msgid "`continue' outside a loop is not portable"
+#~ msgstr "�continue� fora d'un bucle no �s portable"
+
+#~ msgid "`next' cannot be called from a BEGIN rule"
+#~ msgstr "�next� no es pot cridar des d'una regla BEGIN"
+
+#~ msgid "`next' cannot be called from an END rule"
+#~ msgstr "�next� no es pot cridar des d'una regla FINAL"
+
+#~ msgid "`nextfile' cannot be called from a BEGIN rule"
+#~ msgstr "�nextfile� no es pot cridar des d'una regla BEGIN"
+
+#~ msgid "`nextfile' cannot be called from an END rule"
+#~ msgstr "�nextfile� no es pot cridar des d'una regla FINAL"
+
+#~ msgid "statement has no effect"
+#~ msgstr "la sent�ncia no t� efecte"
+
+#~ msgid "assignment used in conditional context"
+#~ msgstr "assignaci� usada en un context condicional"
+
+#~ msgid ""
+#~ "concatenation: side effects in one expression have changed the length of "
+#~ "another!"
+#~ msgstr ""
+#~ "concatenaci�: els efectes colaterals en una expressi� han canviat la "
+#~ "longitud d'una altra!"
 
 #~ msgid "function %s called\n"
 #~ msgstr "s'ha cridat a la funci� %s\n"
 
-#~ msgid "internal error: file `%s', line %d\n"
-#~ msgstr "error intern: fitxer �%s�, l�nia %d\n"
+#~ msgid "\t# -- main --\n"
+#~ msgstr "\t# -- principal --\n"
+
+#~ msgid "invalid tree type %s in redirect()"
+#~ msgstr "tipus d'arbre %s no v�lid dintre de redirect()"
+
+#~ msgid "can't open two way socket `%s' for input/output (%s)"
+#~ msgstr ""
+#~ "no es pot obrir un socket bidireccional �%s� per a les entrades/eixides "
+#~ "(%s)"
+
+#~ msgid "/inet/raw client not ready yet, sorry"
+#~ msgstr "el client /inet/raw encara no est� a punt, ho sento"
+
+#~ msgid "only root may use `/inet/raw'."
+#~ msgstr "sols el root pot usar �/inet/raw�."
+
+#~ msgid "/inet/raw server not ready yet, sorry"
+#~ msgstr "el servidor /inet/raw encara no est� a punt, ho sento"
+
+#~ msgid "file `%s' is a directory"
+#~ msgstr "el fitxer �%s� �s un directori"
+
+#~ msgid "use `PROCINFO[\"%s\"]' instead of `%s'"
+#~ msgstr "useu �PROCINFO[\"%s\"]� en comptes de �%s�"
+
+#~ msgid "use `PROCINFO[...]' instead of `/dev/user'"
+#~ msgstr "useu �PROCINFO[...]� en comptes de �/dev/user�"
+
+#~ msgid "error reading input file `%s': %s"
+#~ msgstr "error en llegir el fitxer d'entrada �%s�: %s"
+
+#~ msgid "can't convert string to float"
+#~ msgstr "no es pot convertir la cadena a coma flotant"
diff --git a/po/da.gmo b/po/da.gmo
index 3655ffb5..0ba7ffc0 100644
--- a/po/da.gmo
+++ b/po/da.gmo
diff --git a/po/da.po b/po/da.po
index 2ce06bf8..f3840840 100644
--- a/po/da.po
+++ b/po/da.po
@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: gawk 4.0.0h\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
 "PO-Revision-Date: 2012-02-06 10:37+0100\n"
 "Last-Translator: Keld Simonsen <keld@keldix.com>\n"
 "Language-Team: Danish <dansk@dansk-gruppen.dk>\n"
@@ -21,89 +21,89 @@ msgstr ""
 "X-Generator: Lokalize 1.0\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "fra %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "fors�g p� at bruge en skalar som array"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "fors�g p� at bruge skalarparameteren '%s' som et array"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "fors�g p� at bruge skalar '%s' som et array"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "fors�g p� at bruge array '%s' i skalarsammenh�ng"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: indeks '%s' findes ikke i array '%s'"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "fors�g p� at bruge skalaren '%s[\"%.*s\"]' som array"
 
-#: array.c:773
+#: array.c:776
 #, fuzzy
 msgid "adump: first argument not an array"
 msgstr "adump: argument er ikke et array"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: andet argument er ikke et array"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: andet argument er ikke et array"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: f�rste argument er ikke et array"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: f�rste argument er ikke et array"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asort: kan ikke bruge et underarray af f�rste argument for andet argument"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asorti: kan ikke bruge et underarray af f�rste argument for andet argument"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asort: kan ikke bruge et underarray af andet argument for f�rste argument"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asorti: kan ikke bruge et underarray af andet argument for f�rste argument"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "'%s' er ugyldigt som funktionsnavn"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "funktionen for sorteringssammenligning '%s' er ikke defineret"
@@ -145,11 +145,11 @@ msgstr "dublet case-v�rdier i switch-krop %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "dublet 'default' opdaget i switch-krop"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "'break' uden for en l�kke eller switch er ikke tilladt"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "'continue' uden for en l�kke er ikke tilladt"
 
@@ -241,272 +241,272 @@ msgstr "kan ikke bruge specialvariabel '%s' til indirekte funktionskald"
 msgid "invalid subscript expression"
 msgstr "ugyldigt indeksudtryk"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "advarsel: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "fatal: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "uventet nylinjetegn eller strengafslutning"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "kan ikke �bne kildefilen '%s' for l�sning (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, fuzzy, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "kan ikke �bne kildefilen '%s' for l�sning (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "ukendt �rsag"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr ""
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "allerede inkluderet kildefil '%s'"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, fuzzy, c-format
 msgid "already loaded shared library `%s'"
 msgstr "allerede inkluderet kildefil '%s'"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include er en gawk-udvidelse"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "tomt filnavn efter @include"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 #, fuzzy
 msgid "@load is a gawk extension"
 msgstr "@include er en gawk-udvidelse"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 #, fuzzy
 msgid "empty filename after @load"
 msgstr "tomt filnavn efter @include"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "tom programtekst p� kommandolinjen"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "kan ikke l�se kildefilen '%s' (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "kildefilen '%s' er tom"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "kildefilen slutter ikke med en ny linje"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr "uafsluttet regul�rt udtryk slutter med '\\' i slutningen af filen"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "%s: %d: regex-�ndringstegn '/.../%c' fra tawk virker ikke i gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "regex-�ndringstegn '/.../%c' fra tawk virker ikke i gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "uafsluttet regul�rt udtryk"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "uafsluttet regul�rt udtryk i slutningen af filen"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "brug af '\\ #...' for linjeforts�ttelse er ikke portabelt"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "sidste tegn p� linjen er ikke en omvendt skr�streg"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX tillader ikke operatoren '**='"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "gamle versioner af awk underst�tter ikke operatoren '**='"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX tillader ikke operatoren '**'"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "gamle versioner af awk underst�tter ikke operatoren '**'"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "operatoren '^=' underst�ttes ikke i gamle versioner af awk"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "operatoren '^' underst�ttes ikke i gamle versioner af awk"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "uafsluttet streng"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "ugyldigt tegn '%c' i udtryk"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "'%s' er en gawk-udvidelse"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX tillader ikke '%s'"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "'%s' underst�ttes ikke i gamle versioner af awk"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "'goto' anses for skadelig!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d er et ugyldigt antal argumenter for %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 "%s: bogstavelig streng som sidste argument til erstatning har ingen effekt"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "%s: tredje argument er ikke et �ndringsbart objekt"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: tredje argument er en gawk-udvidelse"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: andet argument er en gawk-udvidelse"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "brug af dcgettext(_\"...\") er forkert: fjern det indledende "
 "understregningstegn"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "brug af dcgettext(_\"...\") er forkert: fjern det indledende "
 "understregningstegn"
 
-#: awkgram.y:3992
+#: awkgram.y:4016
 #, fuzzy
 msgid "index: regexp constant as second argument is not allowed"
 msgstr "indeks: andet argument er ikke en streng"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "funktionen '%s': parameteren '%s' overskygger en global variabel"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "kunne ikke �bne '%s' for skrivning (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "sender variabelliste til standard fejl"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: lukning mislykkedes (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() kaldt to gange!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "der var skyggede variable."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "funktionsnavnet '%s' er allerede defineret"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr "funktionen '%s': kan ikke bruge funktionsnavn som parameternavn"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "funktionen '%s': kan ikke bruge specialvariabel '%s' som en "
 "funktionsparameter"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "funktionen '%s': parameter %d, '%s', er samme som parameter %d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "funktionen '%s' kaldt, men aldrig defineret"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "funktionen '%s' defineret, men aldrig kaldt direkte"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "konstant regul�rt udtryk for parameter %d giver en boolesk v�rdi"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -515,232 +515,242 @@ msgstr ""
 "funktionen '%s' kaldt med blanktegn mellem navnet og '(',\n"
 "eller brugt som en variabel eller et array"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "fors�gte at dividere med nul"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "fors�gte at dividere med nul i '%%'"
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+
+#: awkgram.y:5052
+#, fuzzy, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "%d er et ugyldigt antal argumenter for %s"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s til '%s' mislykkedes (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "standard ud"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: fik et ikke-numerisk argument"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: kan ikke rense: datakanalen '%s' �bnet for l�sning, ikke skrivning"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr "fflush: kan ikke rense: filen '%s' �bnet for l�sning, ikke skrivning"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: '%s' er ikke en �ben fil, datakanal eller ko-proces"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "indeks: f�rste argument er ikke en streng"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "indeks: andet argument er ikke en streng"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: fik et ikke-numerisk argument"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: fik et array-argument"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "'length(array)' er en gawk-udvidelse"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: fik et argument som ikke er en streng"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: fik et ikke-numerisk argument"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: fik et negativt argument %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "fatal: skal bruge 'count$' p� alle formater eller ikke nogen"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "feltbredde ignoreret for '%%'-angivelse"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "pr�cision ignoreret for '%%'-angivelse"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "feltbredde og pr�cision ignoreret for '%%'-angivelse"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "fatal: '$' tillades ikke i awk-formater"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "fatal: argumentantallet med '$' skal v�re > 0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr "fatal: argumentantallet %ld er st�rre end antal givne argumenter"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "fatal: '$' tillades ikke efter et punktum i formatet"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
 "fatal: intet '$' angivet for bredde eller pr�cision af positionsangivet felt"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "'l' er meningsl�st i awk-formater, ignoreret"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "fatal: 'l' tillades ikke i POSIX awk-formater"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "'L' er meningsl�st i awk-formater, ignoreret"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "fatal: 'L' tillades ikke i POSIX awk-formater"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "'h' er meningsl�st i awk-formater, ignoreret"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "fatal: 'h' tillades ikke i POSIX awk-formater"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: v�rdi %g er uden for omr�de for '%%%c'-format"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "ignorerer ukendt formatspecificeringstegn '%c': intet argument konverteret"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr "fatal: for f� argumenter til formatstrengen"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "^ sluttede her"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: formatspecifikation har intet kommandobogstav"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "for mange argumenter til formatstrengen"
 
-#: builtin.c:1610
+#: builtin.c:1634
 #, fuzzy
 msgid "sprintf: no arguments"
 msgstr "printf: ingen argumenter"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: ingen argumenter"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: fik ikke-numerisk argument"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: l�ngden %g er ikke >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: l�ngden %g er ikke >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: l�ngden %g som ikke er et heltal vil blive trunkeret"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr "substr: l�ngden %g for stor til strengindeksering, trunkerer til %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: startindeks %g er ugyldigt, bruger 1"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: startindeks %g som ikke er et heltal vil blive trunkeret"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: kildestrengen er tom"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: startindeks %g er forbi slutningen p� strengen"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -748,191 +758,191 @@ msgstr ""
 "substr: l�ngden %g ved startindeks %g overskrider l�ngden af f�rste argument "
 "(%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr "strftime: formatv�rdi i PROCINFO[\"strftime\"] har numerisk type"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: fik et ikke-numerisk andet argument"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr "strftime: andet argument mindre end 0 eller for stort til time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: fik et f�rste argument som ikke er en streng"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: fik en tom formatstreng"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: fik et argument som ikke er en streng"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: mindst �n af v�rdierne er udenfor standardomr�det"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "'system'-funktion ikke tilladt i sandkasse-tilstand"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: fik et argument som ikke er en streng"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "reference til ikke-initieret felt '$%d'"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: fik et argument som ikke er en streng"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: fik et argument som ikke er en streng"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: fik et ikke-numerisk f�rste argument"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: fik et ikke-numerisk andet argument"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: fik et ikke-numerisk argument"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: fik et ikke-numerisk argument"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: fik et ikke-numerisk argument"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: tredje argument er ikke et array"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: 0 i tredje argument behandlet som 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: fik et ikke-numerisk f�rste argument"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: fik et ikke-numerisk andet argument"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, fuzzy, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%lf, %lf): negative v�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, fuzzy, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%lf, %lf): kommatalsv�rdier vil blive trunkeret"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, fuzzy, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "lshift(%lf, %lf): for store skiftev�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: fik et ikke-numerisk f�rste argument"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: fik et ikke-numerisk andet argument"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, fuzzy, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%lf, %lf): negative v�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, fuzzy, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%lf, %lf): kommatalsv�rdier vil blive trunkeret"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, fuzzy, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "rshift(%lf, %lf): for store skiftev�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 #, fuzzy
 msgid "and: called with less than two arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, fuzzy, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, fuzzy, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr "and(%lf, %lf): negative v�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 #, fuzzy
 msgid "or: called with less than two arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, fuzzy, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, fuzzy, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "compl(%lf): negative v�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 #, fuzzy
 msgid "xor: called with less than two arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, fuzzy, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, fuzzy, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor(%lf, %lf): negative v�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: fik et ikke-numerisk argument"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, fuzzy, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%lf): negative v�rdier vil give m�rkelige resultater"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, fuzzy, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%lf): kommatalsv�rdier vil blive trunkeret"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: '%s' er ikke en gyldig lokalitetskategori"
@@ -1056,8 +1066,8 @@ msgstr ""
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 
 #: command.y:825
@@ -1214,7 +1224,7 @@ msgstr ""
 msgid "watch var - set a watchpoint for a variable."
 msgstr ""
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "fejl: "
@@ -1254,557 +1264,557 @@ msgstr "Ugyldigt sorteringstegn"
 msgid "undefined command: %s\n"
 msgstr ""
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr ""
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr ""
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr ""
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr ""
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr ""
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr ""
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, fuzzy, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "kan ikke l�se kildefilen '%s' (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, fuzzy, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "kildefilen '%s' er tom"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr ""
 
-#: debug.c:499
+#: debug.c:505
 #, fuzzy, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "kan ikke l�se kildefilen '%s' (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr ""
 
-#: debug.c:602
+#: debug.c:611
 #, fuzzy, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "uventet nylinjetegn eller strengafslutning"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr ""
 
-#: debug.c:723
+#: debug.c:732
 #, fuzzy, c-format
 msgid "Current source file: %s\n"
 msgstr "allerede inkluderet kildefil '%s'"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr ""
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr ""
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr ""
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr ""
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr ""
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr ""
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr ""
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr ""
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr ""
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr ""
 
-#: debug.c:839
+#: debug.c:848
 #, fuzzy
 msgid "No arguments.\n"
 msgstr "printf: ingen argumenter"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr ""
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:1020
+#: debug.c:1029
 #, fuzzy, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "'exit' kan ikke kaldes i den aktuelle kontekst"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, fuzzy, c-format
 msgid "`%s' is not an array\n"
 msgstr "'%s' er ikke et gyldigt variabelnavn"
 
-#: debug.c:1046
+#: debug.c:1055
 #, fuzzy, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "reference til ikke-initieret felt '$%d'"
 
-#: debug.c:1067
+#: debug.c:1076
 #, fuzzy, c-format
 msgid "array `%s' is empty\n"
 msgstr "datafilen '%s' er tom"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "delete: indeks '%s' findes ikke i array '%s'"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr ""
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, fuzzy, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "'%s' er ikke et gyldigt variabelnavn"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, fuzzy, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "fors�g p� at bruge array '%s[\"%.*s\"]' i skalarsammenh�ng"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, fuzzy, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "fors�g p� at bruge skalaren '%s[\"%.*s\"]' som array"
 
-#: debug.c:1414
+#: debug.c:1423
 #, fuzzy, c-format
 msgid "`%s' is a function"
 msgstr "'%s' er ugyldigt som funktionsnavn"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr ""
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr ""
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr ""
 
-#: debug.c:1519
+#: debug.c:1528
 #, fuzzy, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "delete: indeks '%s' findes ikke i array '%s'"
 
-#: debug.c:1758
+#: debug.c:1767
 #, fuzzy
 msgid "attempt to use scalar value as array"
 msgstr "fors�g p� at bruge en skalar som array"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr ""
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr ""
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr ""
 
-#: debug.c:2008
+#: debug.c:2017
 #, fuzzy
 msgid "invalid frame number"
 msgstr "Ugyldig intervalslutning"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr ""
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, fuzzy, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr ""
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr ""
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr ""
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr ""
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr ""
 
-#: debug.c:2521
+#: debug.c:2541
 #, fuzzy, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "fejl ved l�sning af inddatafilen '%s': %s"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr ""
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr ""
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr ""
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr ""
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr ""
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr ""
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr ""
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr ""
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr ""
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr ""
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr ""
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr ""
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr ""
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr ""
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr ""
 
-#: debug.c:3357
+#: debug.c:3377
 #, fuzzy, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "allerede inkluderet kildefil '%s'"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, fuzzy, c-format
 msgid "element not in array\n"
 msgstr "delete: indeks '%s' findes ikke i array '%s'"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr ""
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr ""
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr ""
 
-#: debug.c:4986
+#: debug.c:5001
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "delete: indeks '%s' findes ikke i array '%s'"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr ""
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr ""
 
-#: debug.c:5366
+#: debug.c:5381
 #, fuzzy, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "'exit' kan ikke kaldes i den aktuelle kontekst"
 
-#: debug.c:5374
+#: debug.c:5389
 #, fuzzy
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "'exit' kan ikke kaldes i den aktuelle kontekst"
 
-#: debug.c:5575
+#: debug.c:5590
 #, fuzzy, c-format
 msgid "No symbol `%s' in current context"
 msgstr "fors�g p� at bruge array '%s' i skalarsammenh�ng"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr ""
 
-#: dfa.c:1052
+#: dfa.c:1174
 #, fuzzy
 msgid "invalid character class"
 msgstr "Ugyldigt tegnklassenavn"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr ""
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr ""
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Ugyldigt indhold i \\{\\}"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Regul�rt udtryk for stort"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr ""
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr ""
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ""
 
@@ -1823,11 +1833,11 @@ msgstr "ukendt opkode %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "opkode %s er ikke en operator eller et n�gleord"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "bufferoverl�b i genflags2str"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1838,71 +1848,71 @@ msgstr ""
 "\t# Funktionskaldsstak:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "'IGNORECASE' er en gawk-udvidelse"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "'BINMODE' er en gawk-udvidelse"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "BINMODE v�rdi '%s' er ugyldig, behandles som 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "forkert '%sFMT'-specifikation '%s'"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "deaktiverer '--lint' p� grund af en tildeling til 'LINT'"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "reference til ikke-initieret argument '%s'"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "reference til ikke-initieret variabel '%s'"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "fors�g p� at referere til et felt fra ikke-numerisk v�rdi"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "fors�g p� at referere til et felt fra tom streng"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "fors�g p� at f� adgang til felt %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "reference til ikke-initieret felt '$%ld'"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "funktionen '%s' kaldt med flere argumenter end deklareret"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: uventet type `%s'"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "fors�gte at dividere med nul i '/='"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "fors�gte at dividere med nul i '%%='"
@@ -1916,7 +1926,7 @@ msgstr "udvidelser er ikke tilladt i sandkasse-tilstand"
 msgid "-l / @load are gawk extensions"
 msgstr "@include er en gawk-udvidelse"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr ""
 
@@ -1948,6 +1958,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "'extension' er en gawk-udvidelse"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr ""
+
 #: ext.c:180
 #, fuzzy, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1972,37 +1986,37 @@ msgstr ""
 msgid "make_builtin: missing function name"
 msgstr "extension: mangler funktionsnavn"
 
-#: ext.c:238
+#: ext.c:236
 #, fuzzy, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "extension: kan ikke omdefinere funktion '%s'"
 
-#: ext.c:242
+#: ext.c:240
 #, fuzzy, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "extension: funktionen '%s' er allerede defineret"
 
-#: ext.c:246
+#: ext.c:244
 #, fuzzy, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "extension: funktionsnavnet '%s' er defineret tidligere"
 
-#: ext.c:248
+#: ext.c:246
 #, fuzzy, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr "extension: kan ikke bruge gawk's indbyggede '%s' som funktionsnavn"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: negativt argumentantal for funktion '%s'"
 
-#: ext.c:278
+#: ext.c:276
 #, fuzzy
 msgid "extension: missing function name"
 msgstr "extension: mangler funktionsnavn"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, fuzzy, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: ugyldigt tegn '%c' i funktionsnavn '%s'"
@@ -2027,155 +2041,160 @@ msgstr "funktionsnavnet '%s' er allerede defineret"
 msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr "extension: kan ikke bruge gawk's indbyggede '%s' som funktionsnavn"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "funktionen '%s' defineret til at tage ikke mere end %d argumenter"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "funktion '%s': mangler argument nummer %d"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr ""
 "funktion '%s': argument nummer %d: fors�g p� at bruge skalar som et array"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr ""
 "funktion '%s': argument nummer %d: fors�g p� at bruge array som en skalar"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr ""
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 #, fuzzy
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr ""
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 #, fuzzy
 msgid "stat: called with wrong number of arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 #, fuzzy
 msgid "stat: bad parameters"
 msgstr "%s: er parameter\n"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, fuzzy, c-format
 msgid "fts init: could not create variable %s"
 msgstr "indeks: andet argument er ikke en streng"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+#, fuzzy
+msgid "fts is not supported on this system"
+msgstr "'%s' underst�ttes ikke i gamle versioner af awk"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 #, fuzzy
 msgid "fill_path_element: could not set element"
 msgstr "indeks: andet argument er ikke en streng"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 #, fuzzy
 msgid "fts-process: could not set element"
 msgstr "indeks: andet argument er ikke en streng"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 #, fuzzy
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 #, fuzzy
 msgid "fts: bad first parameter"
 msgstr "%s: er parameter\n"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 #, fuzzy
 msgid "fts: bad second parameter"
 msgstr "%s: er parameter\n"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 #, fuzzy
 msgid "fts: bad third parameter"
 msgstr "%s: er parameter\n"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 #, fuzzy
 msgid "fts: could not flatten array\n"
 msgstr "'%s' er ikke et gyldigt variabelnavn"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr ""
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr ""
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 #, fuzzy
 msgid "fnmatch: called with less than three arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 #, fuzzy
 msgid "fnmatch: called with more than three arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 #, fuzzy
 msgid "fnmatch: could not get first argument"
 msgstr "strftime: fik et f�rste argument som ikke er en streng"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 #, fuzzy
 msgid "fnmatch: could not get second argument"
 msgstr "indeks: andet argument er ikke en streng"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr ""
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr ""
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr ""
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr ""
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr ""
 
@@ -2203,88 +2222,88 @@ msgstr "sqrt: kaldt med negativt argument %g"
 msgid "wait: called with too many arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr ""
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr ""
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, fuzzy, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "atalt: extension: kan ikke �bne '%s' (%s)\n"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, fuzzy, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "'%s' er ikke et gyldigt variabelnavn"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, fuzzy, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "%s: lukning mislykkedes (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, fuzzy, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "%s: lukning mislykkedes (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr ""
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, fuzzy, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "%s: lukning mislykkedes (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, fuzzy, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "datakanalsrensning af '%s' mislykkedes (%s)."
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, fuzzy, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "lukning af fd %d ('%s') mislykkedes (%s)"
@@ -2319,177 +2338,177 @@ msgstr "sqrt: kaldt med negativt argument %g"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr ""
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 #, fuzzy
 msgid "readfile: called with too many arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 #, fuzzy
 msgid "readfile: called with no arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 #, fuzzy
 msgid "writea: called with too many arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, fuzzy, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de\n"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, fuzzy, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "split: fjerde argument er ikke et array\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr ""
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr ""
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 #, fuzzy
 msgid "reada: called with too many arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, fuzzy, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, fuzzy, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "match: tredje argument er ikke et array"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr ""
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr ""
 
-#: extension/time.c:81
+#: extension/time.c:113
 #, fuzzy
 msgid "gettimeofday: ignoring arguments"
 msgstr "mktime: fik et argument som ikke er en streng"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr ""
 
-#: extension/time.c:133
+#: extension/time.c:165
 #, fuzzy
 msgid "sleep: called with too many arguments"
 msgstr "sqrt: kaldt med negativt argument %g"
 
-#: extension/time.c:136
+#: extension/time.c:168
 #, fuzzy
 msgid "sleep: missing required numeric argument"
 msgstr "exp: fik et ikke-numerisk argument"
 
-#: extension/time.c:142
+#: extension/time.c:174
 #, fuzzy
 msgid "sleep: argument is negative"
 msgstr "exp: argumentet %g er uden for det tilladte omr�de"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr ""
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF sat til en negativ v�rdi"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: fjerde argument er en gawk-udvidelse"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: fjerde argument er ikke et array"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: andet argument er ikke et array"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr "split: kan ikke bruge det samme array som andet og fjerde argument"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split: kan ikke bruge et underarray af andet argument som fjerde argument"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split: kan ikke bruge et underarray af fjerde argument som andet argument"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: tom streng som tredje argument er en gawk-udvidelse"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: fjerde argument er ikke et array"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: andet argument er ikke et array"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patmatch: tredje argument er ikke et array"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr "patsplit: kan ikke bruge det samme array som andet og fjerde argument"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit: kan ikke bruge et underarray af andet argument som fjerde argument"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit: kan ikke bruge et underarray af fjerde argument som andet argument"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "'FIELDWIDTHS' er en gawk-udvidelse"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "ugyldig FIELDWIDTHS v�rdi, n�r '%s"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "tom streng som 'FS' er en gawk-udvidelse"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "gamle versioner af awk underst�tter ikke regexp'er som v�rdi for 'FS'"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "'FPAT' er en gawk-udvidelse"
 
@@ -2505,590 +2524,590 @@ msgstr ""
 msgid "node_to_awk_value: received null val"
 msgstr ""
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 #, fuzzy
 msgid "remove_element: received null array"
 msgstr "length: fik et array-argument"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr ""
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr ""
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr ""
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, fuzzy, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: flaget '%s' er flertydigt\n"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: flaget '--%s' tillader ikke noget argument\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: flaget '%c%s' tillader ikke noget argument\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: flaget '--%s' kr�ver et argument\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: ukendt flag '--%s'\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: ukendt flag '%c%s'\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: ugyldigt flag - '%c'\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: flaget kr�ver et argument - '%c'\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: flaget '-W %s' er flertydigt\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: flaget '-W %s' tillader ikke noget argument\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: flaget '-W %s' kr�ver et argument\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "kommandolinjeargument '%s' er et katalog, oversprunget"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "kan ikke �bne filen '%s' for l�sning (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "lukning af fd %d ('%s') mislykkedes (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "omdirigering ikke tilladt i sandkasse-tilstand"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "udtrykket i '%s'-omdirigering har kun numerisk v�rdi"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "udtrykket for '%s'-omdirigering har en tom streng som v�rdi"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "filnavnet '%s' for '%s'-omdirigering kan v�re resultatet af et logisk udtryk"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "un�dig blanding af '>' og '>>' for filen '%.*s'"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "kan ikke �bne datakanalen '%s' for udskrivning (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "kan ikke �bne datakanalen '%s' for indtastning (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr "kan ikke �bne tovejsdatakanalen '%s' for ind-/uddata (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "kan ikke omdirigere fra '%s' (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "kan ikke omdirigere til '%s' (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "n�ede systembegr�nsningen for �bne filer: begynder at multiplekse "
 "fildeskriptorer"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "lukning af '%s' mislykkedes (%s)."
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "for mange datakanaler eller inddatafiler �bne"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: andet argument skal v�re 'to' eller 'from'"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: '%.*s' er ikke en �ben fil, datakanal eller ko-proces"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "lukning af omdirigering som aldrig blev �bnet"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: omdirigeringen '%s' blev ikke �bnet med '|&', andet argument ignoreret"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "fejlstatus (%d) fra lukning af datakanalen '%s' (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "fejlstatus (%d) fra fillukning af '%s' (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "ingen eksplicit lukning af soklen '%s' angivet"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "ingen eksplicit lukning af ko-processen '%s' angivet"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "ingen eksplicit lukning af datakanalen '%s' angivet"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "ingen eksplicit lukning af filen '%s' angivet"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "fejl ved skrivning til standard ud (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "fejl ved skrivning til standard fejl (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "datakanalsrensning af '%s' mislykkedes (%s)."
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "ko-procesrensning af datakanalen til '%s' mislykkedes (%s)."
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "filrensning af '%s' mislykkedes (%s)."
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "lokal port %s ugyldig i '/inet'"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "fjernv�rt og portinformation (%s, %s) ugyldige"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr "ingen (kendt) protokol opgivet i special-filnavn '%s'"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "special-filnavn '%s' er ufuldst�ndigt"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "fjernmaskinenavn til '/inet' skal angives"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "fjernport til '/inet' skal angives"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "TCP/IP-kommunikation underst�ttes ikke"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "kunne ikke �bne '%s', tilstand '%s'"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "lukning af master-pty mislykkedes (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "lukning af standard ud i underproces mislykkedes (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "flytning af slave-pty til standard ud i underproces mislykkedes (dup: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "lukning af standard ind i underproces mislykkedes (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "flytning af slave-pty til standard ind i underproces mislykkedes (dup: %s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "lukning af slave-pty mislykkedes (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 "flytning af datakanal til standard ud i underproces mislykkedes (dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "flytning af datakanalen til standard ind i underproces mislykkedes (dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "genskabelse af standard ud i for�lderprocessen mislykkedes\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "genskabelse af standard ind i for�lderprocessen mislykkedes\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "lukning af datakanalen mislykkedes (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "'|&' underst�ttes ikke"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "kan ikke �bne datakanalen '%s' (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "kan ikke oprette barneproces for '%s' (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr ""
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr ""
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr ""
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "datafilen '%s' er tom"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "kunne ikke allokere mere hukommelse til inddata"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "'RS' som flertegnsv�rdi er en gawk-udvidelse"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "IPv6-kommunikation underst�ttes ikke"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "tomt argument til '-e/--source' ignoreret"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: flaget '-W %s' ukendt, ignoreret\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: flaget kr�ver et argument -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr "milj�variablen 'POSIXLY_CORRECT' sat: aktiverer '--posix'"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "'--posix' tilsides�tter '--traditional'"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr "'--posix'/'--traditional' tilsides�tter '--non-decimal-data'"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "at k�re %s setuid root kan v�re et sikkerhedsproblem"
 
-#: main.c:571
+#: main.c:588
 #, fuzzy
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "'--posix' tilsides�tter '--binary'"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "kan ikke s�tte bin�r tilstand p� standard ind (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "kan ikke s�tte bin�r tilstand p� standard ud (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "kan ikke s�tte bin�r tilstand p� standard fejl (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "ingen programtekst overhovedet!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr "Brug: %s [flag i POSIX- eller GNU-stil] -f progfil [--] fil ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr "Brug: %s [flag i POSIX- eller GNU-stil] %cprogram%c fil ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "POSIX-flag:\t\tlange GNU-flag: (standard)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f progfil\t\t--file=progfil\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=v�rdi\t\t--assign=var=v�rdi\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "POSIX-flag:\t\tlange GNU-flag: (udvidelser)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[fil]\t\t--dump-variables[=fil]\n"
 
-#: main.c:795
+#: main.c:815
 #, fuzzy
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-p[fil]\t\t--profile[=fil]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'programtekst'\t--source='programtekst'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E fil\t\t\t--exec=fil\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr ""
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr ""
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 #, fuzzy
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 #, fuzzy
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-p[fil]\t\t--profile[=fil]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[fil]\t\t--profile[=fil]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3097,7 +3116,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3110,7 +3129,7 @@ msgstr ""
 "\n"
 "Rapport�r kommentarer til overs�ttelsen til <dansk@dansk-gruppen.dk>.\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3120,7 +3139,7 @@ msgstr ""
 "Almindeligvis l�ser gawk fra standard ind og skriver til standard ud.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3130,7 +3149,7 @@ msgstr ""
 "\tgawk '{ sum += $1 }; END { print sum }' fil\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3150,7 +3169,7 @@ msgstr ""
 "enhver senere version.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3164,7 +3183,7 @@ msgstr ""
 "General Public License for yderligere information.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3172,16 +3191,16 @@ msgstr ""
 "Du b�r have f�et en kopi af GNU General Public License sammen\n"
 "med dette program. Hvis ikke, s� se http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft s�tter ikke FS til tab i POSIX-awk"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "ukendt v�rdi for felt-spec: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3190,48 +3209,48 @@ msgstr ""
 "%s: '%s' argument til '-v' ikke p� formen 'var=v�rdi'\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "'%s' er ikke et gyldigt variabelnavn"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "'%s' er ikke et variabelnavn, leder efter fil '%s=%s'"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "kan ikke bruge gawk's indbyggede '%s' som variabelnavn"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "kan ikke bruge funktion '%s' som variabelnavn"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "flydendetalsundtagelse"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "fatal fejl: intern fejl"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "fatal fejl: intern fejl: segmentfejl"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "fatal fejl: intern fejl: stakoverl�b"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "ingen fd %d �bnet i forvejen"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "kunne ikke i forvejen �bne /dev/null for fd %d"
@@ -3290,7 +3309,7 @@ msgstr "or(%lf, %lf): kommatalsv�rdier vil blive trunkeret"
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "compl(%lf): negative v�rdier vil give m�rkelige resultater"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "kommandolinje:"
@@ -3344,16 +3363,16 @@ msgstr "%s %s '%s': kunne ikke f� fat p� fd flag: (fcntl F_GETFD: %s)"
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr "%s %s '%s': kunne ikke s�tte luk-ved-exec (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "kunne ikke �bne '%s' for skrivning: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "sender profilen til standard fejl"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3362,7 +3381,7 @@ msgstr ""
 "\t# %s blokke\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3371,29 +3390,29 @@ msgstr ""
 "\t# Regler\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "intern fejl: %s med null vname"
 
-#: profile.c:530
+#: profile.c:537
 #, fuzzy
 msgid "internal error: builtin with null fname"
 msgstr "intern fejl: %s med null vname"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# profil til gawk oprettet %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3402,17 +3421,12 @@ msgstr ""
 "\n"
 "\t# Funktioner, listede alfabetisk\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: uykendt omdirigeringstype %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "omr�de p� formen `[%c-%c]' er locale-afh�ngig"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr "regexp-komponent `%.*s' skulle nok v�re `[%.*s]'"
@@ -3481,10 +3495,13 @@ msgstr "Ubalanceret ) eller \\)"
 msgid "No previous regular expression"
 msgstr "Intet foreg�ende regul�rt udtryk"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr ""
 
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "omr�de p� formen `[%c-%c]' er locale-afh�ngig"
+
 #, fuzzy
 #~ msgid "[s]printf called with no arguments"
 #~ msgstr "sqrt: kaldt med negativt argument %g"
diff --git a/po/de.gmo b/po/de.gmo
index f8ae3a41..e46946bb 100644
--- a/po/de.gmo
+++ b/po/de.gmo
diff --git a/po/de.po b/po/de.po
index e5b8a93d..f92c3bb7 100644
--- a/po/de.po
+++ b/po/de.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: gawk 4.0.0h\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
 "PO-Revision-Date: 2012-01-30 16:21+0100\n"
 "Last-Translator: Philipp Thomas <pth@suse.de>\n"
 "Language-Team: German <translation-team-de@lists.sourceforge.net>\n"
@@ -17,93 +17,93 @@ msgstr ""
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "von %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "Es wird versucht, einen Skalar als Feld zu verwenden"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "Es wird versucht, den skalaren Parameter »%s« als Feld zu verwenden"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "Es wird versucht, den Skalar »%s« als Array zu verwenden"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "Es wird versucht, das Feld »%s« in einem Skalarkontext zu verwenden"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: Index »%s« ist in Feld »%s« nicht vorhanden"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "Es wird versucht, den Skalar »%s[\"%.*s\"]« als Feld zu verwenden"
 
-#: array.c:773
+#: array.c:776
 #, fuzzy
 msgid "adump: first argument not an array"
 msgstr "adump: Das Argument ist kein Feld"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: Das zweite Argument ist kein Feld"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: Das zweite Argument ist kein Feld"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: Das erste Argument ist kein Feld"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: Das erste Argument ist kein Feld"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asort: ein untergeordnetes Feld des ersten Arguments kann nicht als zweites "
 "Argument verwendet werden"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asorti: ein untergeordnetes Feld des ersten Arguments kann nicht als zweites "
 "Argument verwendet werden"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asort: ein untergeordnetes Feld des zweiten Arguments kann nicht als erstes "
 "Argument verwendet werden"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asorti: ein untergeordnetes Feld des zweiten Arguments kann nicht als erstes "
 "Argument verwendet werden"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "»%s« ist ein unzulässiger Funktionsname"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "Die Vergleichsfunktion »%s« für das Sortieren ist nicht definiert"
@@ -148,12 +148,12 @@ msgstr "doppelte Case-Werte im Switch-Block: %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "doppeltes »default« im Switch-Block gefunden"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr ""
 "»break« ist außerhalb einer Schleife oder eines Switch-Blocks nicht zulässig"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "»continue« ist außerhalb einer Schleife nicht zulässig"
 
@@ -246,279 +246,279 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr "Ungültiger Index-Ausdruck"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "Warnung: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "Fatal: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "Unerwarteter Zeilenumbruch oder Ende der Zeichenkette"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "Quelldatei »%s« kann nicht zum Lesen geöffnet werden (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, fuzzy, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "Quelldatei »%s« kann nicht zum Lesen geöffnet werden (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "Unbekannte Ursache"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr ""
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "Quelldatei »%s« wurde bereits eingebunden"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, fuzzy, c-format
 msgid "already loaded shared library `%s'"
 msgstr "Quelldatei »%s« wurde bereits eingebunden"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "»@include« ist eine gawk-Erweiterung"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "leerer Dateiname nach @include"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 #, fuzzy
 msgid "@load is a gawk extension"
 msgstr "»@include« ist eine gawk-Erweiterung"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 #, fuzzy
 msgid "empty filename after @load"
 msgstr "leerer Dateiname nach @include"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "Kein Programmtext auf der Kommandozeile"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "Die Quelldatei »%s« kann nicht gelesen werden (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "Die Quelldatei »%s« ist leer"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "Die Quelldatei hört nicht mit einem Zeilenende auf"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr ""
 "Nicht beendeter regulärer Ausdruck (hört mit '\\' auf) am Ende der Datei"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "%s: %d: der tawk-Modifizierer für reguläre Ausdrücke »/.../%c« funktioniert "
 "nicht in gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "Der tawk-Modifizierer für reguläre Ausdrücke »/.../%c« funktioniert nicht in "
 "gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "Nicht beendeter regulärer Ausdruck"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "Nicht beendeter regulärer Ausdruck am Dateiende"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr ""
 "Die Verwendung von »\\#...« zur Fortsetzung von Zeilen ist nicht portabel"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "das letzte Zeichen auf der Zeile ist kein Backslash (»\\«)"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX erlaubt den Operator »**=« nicht"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "Das alte awk unterstützt den Operator »**=« nicht"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX erlaubt den Operator »**« nicht"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "Das alte awk unterstützt den Operator »**« nicht"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "Das alte awk unterstützt den Operator »^=« nicht"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "Das alte awk unterstützt den Operator »^« nicht"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "Nicht beendete Zeichenkette"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "Ungültiges Zeichen »%c« in einem Ausdruck"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "»%s« ist eine gawk-Erweiterung"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX erlaubt »%s« nicht"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "»%s« wird im alten awk nicht unterstützt"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "»goto« gilt als schlechter Stil!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "Unzulässige Argumentzahl %d für %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr "%s: Ein String als letztes Argument von substitute hat keinen Effekt"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "Der dritte Parameter von %s ist ein unveränderliches Objekt"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: Das dritte Argument ist eine gawk-Erweiterung"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: Das zweite Argument ist eine gawk-Erweiterung"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "Fehlerhafte Verwendung von dcgettext(_\"...\"): \n"
 "Entfernen Sie den führenden Unterstrich"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "Fehlerhafte Verwendung von dcngettext(_\"...\"): \n"
 "Entfernen Sie den führenden Unterstrich"
 
-#: awkgram.y:3992
+#: awkgram.y:4016
 #, fuzzy
 msgid "index: regexp constant as second argument is not allowed"
 msgstr "index: Zweites Argument ist kein string"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "Funktion »%s«: Parameter »%s« verdeckt eine globale Variable"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "»%s« kann nicht zum Schreiben geöffne werden(%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "Die Liste der Variablen wird auf der Standardfehlerausgabe ausgegeben"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: close ist gescheitert (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() zweimal aufgerufen!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "es sind verdeckte Variablen vorhanden"
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "Funktion »%s« wurde bereits definiert"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr "Funktion »%s«: Funktionsnamen können nicht als Parameternamen benutzen"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "Funktion »%s«: die spezielle Variable »%s« kann nicht als Parameter "
 "verwendet werden"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "Funktion »%s«: Parameter #%d, »%s« wiederholt Parameter #%d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "Aufgerufene Funktion »%s« ist nirgends definiert"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "Funktion »%s« wurde definiert aber nirgends aufgerufen"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr ""
 "Regulärer-Ausdruck-Konstante für Parameter #%d ergibt einen \n"
 "logischen Wert"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -527,238 +527,248 @@ msgstr ""
 "Funktion »%s« wird mit Leerzeichen zwischen Name und »(« aufgerufen, \n"
 "oder als Variable oder Feld verwendet"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "Division durch Null wurde versucht"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "Division durch Null versucht in »%%«"
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+
+#: awkgram.y:5052
+#, fuzzy, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "Unzulässige Argumentzahl %d für %s"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s to \"%s\" fehlgeschlagen (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "Standardausgabe"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: das Argument ist keine Zahl"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: Leeren der Puffer nicht möglich, Pipe »%s« ist nur zum Lesen geöffnet"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: Leeren der Puffer nicht möglich, Datei »%s« ist nur zum Lesen "
 "geöffnet"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: »%s« ist keine geöffnete Datei, Pipe oder Prozess"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: Erstes Argument ist kein String"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: Zweites Argument ist kein string"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "Argument ist keine Zahl"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: Argument ist ein Feld"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "»length(array)« ist eine gawk-Erweiterung"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: Argument ist kein String"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: Argument ist keine Zahl"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: Negatives Argument %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "Fatal: »count$« muss auf alle Formate angewandt werden oder auf keines"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "Feldbreite wird für die »%%«-Angabe ignoriert"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "Genauigkeit wird für die »%%«-Angabe ignoriert"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "Feldbreite und Genauigkeit werden für die »%%«-Angabe ignoriert"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "Fatal: »$« ist in awk-Formaten nicht zulässig"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "Fatal: die Anzahl der Argumen bei »$« muss > 0 sein"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr ""
 "Fatal: Argumentenanzahl %ld ist größer als die Gesamtzahl angegebener "
 "Argumente"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "Fatal: »$« nach Punkt in Formatangabe nicht zulässig"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr "Fatal: »$« fehlt in positionsabhängiger Feldbreite oder Genauigkeit"
 
 #
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "»l« ist in awk-Formaten bedeutungslos, ignoriert"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "Fatal: »l« ist in POSIX-awk-Formaten nicht zulässig"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "»L« ist in awk-Formaten bedeutungslos, ignoriert"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "Fatal: »L« ist in POSIX-awk-Formaten nicht zulässig"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "»h« ist in awk-Formaten bedeutungslos, ignoriert"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "Fatal: »h« ist in POSIX-awk-Formaten nicht zulässig"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: Wert %g ist außerhalb des Bereichs für Format »%%%c«"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "das unbekannte Zeichen »%c« in der Formatspezifikation wird ignoriert: keine "
 "Argumente umgewandelt"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr "Fatal: Nicht genügend Argumente für die Formatangabe"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "^ hierfür fehlte es"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: Format-Spezifikation hat keinen Controlcode"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "Zu viele Argumente für den Formatstring"
 
-#: builtin.c:1610
+#: builtin.c:1634
 #, fuzzy
 msgid "sprintf: no arguments"
 msgstr "printf: Keine Argumente"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: Keine Argumente"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: das Argument ist keine Zahl"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: Länge %g ist nicht >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: Länge %g ist nicht >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: Nicht ganzzahlige Länge %g wird abgeschnitten"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr ""
 "substr: Länge %g ist zu groß für Stringindizierung, wird auf %g gekürzt"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: Start-Index %g ist ungültig, 1 wird verwendet"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: Nicht ganzzahliger Start-Wert %g wird abgeschnitten"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: Quellstring ist leer"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: Start-Wert %g liegt hinter dem Ende des Strings"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -766,197 +776,197 @@ msgstr ""
 "substr: Länge %g am Start-Wert %g überschreitet die Länge des ersten "
 "Arguments (%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr "strftime: Formatwert in PROCINFO[\"strftime\"] ist numerischen Typs"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: Das zweite Argument ist keine Zahl"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr ""
 "strftime: das zweite Argument ist kleiner als 0 oder zu groß für time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: Das erste Argument ist kein String"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: Der Format-String ist leer"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: Das Argument ist kein String"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: mindestens einer der Werte ist außerhalb des normalen Bereichs"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "Die Funktion »system« ist im Sandbox-Modus nicht erlaubt"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: Das Argument ist kein String"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "Referenz auf das nicht initialisierte Feld »$%d«"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: das Argument ist kein String"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: das Argument ist kein String"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: das erste Argument ist keine Zahl"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: das zweite Argument ist keine Zahl"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: das Argument ist keine Zahl"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: das Argument ist keine Zahl"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: das Argument ist keine Zahl"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: das dritte Argument ist kein Array"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: 0 als drittes Argument wird als 1 interpretiert"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: das erste Argument ist keine Zahl"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: das zweite Argument ist keine Zahl"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, fuzzy, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr ""
 "lshift(%lf, %lf): Negative Werte werden zu merkwürdigen Ergebnissen führen"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, fuzzy, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%lf, %lf): Dezimalteil wird abgeschnitten"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, fuzzy, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "lshift(%lf, %lf): Zu große Shift-Werte werden zu merkwürdigen Ergebnissen "
 "führen"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: das erste Argument ist keine Zahl"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: das zweite Argument ist keine Zahl"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, fuzzy, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr ""
 "rshift (%lf, %lf): Negative Werte werden zu merkwürdigen Ergebnissen führen"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, fuzzy, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%lf, %lf): Dezimalteil wird abgeschnitten"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, fuzzy, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "rshift(%lf, %lf): Zu große Shift-Werte werden zu merkwürdigen Ergebnissen "
 "führen"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 #, fuzzy
 msgid "and: called with less than two arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, fuzzy, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, fuzzy, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr ""
 "and(%lf, %lf): Negative Werte werden zu merkwürdigen Ergebnissen führen"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 #, fuzzy
 msgid "or: called with less than two arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, fuzzy, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, fuzzy, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "compl(%lf): Negativer Wert wird zu merkwürdigen Ergebnissen führen"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 #, fuzzy
 msgid "xor: called with less than two arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, fuzzy, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, fuzzy, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor(%lf, %lf: Negative Werte werden zu merkwürdigen Ergebnissen führen"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: das erste Argument ist keine Zahl"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, fuzzy, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%lf): Negativer Wert wird zu merkwürdigen Ergebnissen führen"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, fuzzy, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%lf): Dezimalteil wird abgeschnitten"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: »%s« ist keine gültige Locale-Kategorie"
@@ -1080,8 +1090,8 @@ msgstr ""
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 
 #: command.y:825
@@ -1238,7 +1248,7 @@ msgstr ""
 msgid "watch var - set a watchpoint for a variable."
 msgstr ""
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "Fehler: "
@@ -1278,558 +1288,558 @@ msgstr "Ungültiges Zeichen"
 msgid "undefined command: %s\n"
 msgstr ""
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr ""
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr ""
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr ""
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr ""
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr ""
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr ""
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, fuzzy, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "Die Quelldatei »%s« kann nicht gelesen werden (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, fuzzy, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "Die Quelldatei »%s« ist leer"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr ""
 
-#: debug.c:499
+#: debug.c:505
 #, fuzzy, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "Die Quelldatei »%s« kann nicht gelesen werden (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr ""
 
-#: debug.c:602
+#: debug.c:611
 #, fuzzy, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "Unerwarteter Zeilenumbruch oder Ende der Zeichenkette"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr ""
 
-#: debug.c:723
+#: debug.c:732
 #, fuzzy, c-format
 msgid "Current source file: %s\n"
 msgstr "Quelldatei »%s« wurde bereits eingebunden"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr ""
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr ""
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr ""
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr ""
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr ""
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr ""
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr ""
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr ""
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr ""
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr ""
 
-#: debug.c:839
+#: debug.c:848
 #, fuzzy
 msgid "No arguments.\n"
 msgstr "printf: Keine Argumente"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr ""
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:1020
+#: debug.c:1029
 #, fuzzy, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "»exit« kann im aktuellen Kontext nicht aufgerufen werden"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, fuzzy, c-format
 msgid "`%s' is not an array\n"
 msgstr "»%s« ist kein gültiger Variablenname"
 
-#: debug.c:1046
+#: debug.c:1055
 #, fuzzy, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "Referenz auf das nicht initialisierte Feld »$%d«"
 
-#: debug.c:1067
+#: debug.c:1076
 #, fuzzy, c-format
 msgid "array `%s' is empty\n"
 msgstr "Die Datei »%s« ist leer"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "delete: Index »%s« ist in Feld »%s« nicht vorhanden"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr ""
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, fuzzy, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "»%s« ist kein gültiger Variablenname"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, fuzzy, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr ""
 "Es wird versucht, das Feld »%s[\"%.*s\"]« in einem Skalarkontext zu verwenden"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, fuzzy, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "Es wird versucht, den Skalar »%s[\"%.*s\"]« als Feld zu verwenden"
 
-#: debug.c:1414
+#: debug.c:1423
 #, fuzzy, c-format
 msgid "`%s' is a function"
 msgstr "»%s« ist ein unzulässiger Funktionsname"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr ""
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr ""
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr ""
 
-#: debug.c:1519
+#: debug.c:1528
 #, fuzzy, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "delete: Index »%s« ist in Feld »%s« nicht vorhanden"
 
-#: debug.c:1758
+#: debug.c:1767
 #, fuzzy
 msgid "attempt to use scalar value as array"
 msgstr "Es wird versucht, einen Skalar als Feld zu verwenden"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr ""
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr ""
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr ""
 
-#: debug.c:2008
+#: debug.c:2017
 #, fuzzy
 msgid "invalid frame number"
 msgstr "Ungültiges Bereichsende"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr ""
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, fuzzy, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr ""
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr ""
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr ""
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr ""
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr ""
 
-#: debug.c:2521
+#: debug.c:2541
 #, fuzzy, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "Fehler beim Lesen der Eingabedatei »%s«: %s"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr ""
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr ""
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr ""
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr ""
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr ""
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr ""
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr ""
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr ""
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr ""
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr ""
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr ""
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr ""
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr ""
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr ""
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr ""
 
-#: debug.c:3357
+#: debug.c:3377
 #, fuzzy, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "Quelldatei »%s« wurde bereits eingebunden"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, fuzzy, c-format
 msgid "element not in array\n"
 msgstr "delete: Index »%s« ist in Feld »%s« nicht vorhanden"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr ""
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr ""
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr ""
 
-#: debug.c:4986
+#: debug.c:5001
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "delete: Index »%s« ist in Feld »%s« nicht vorhanden"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr ""
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr ""
 
-#: debug.c:5366
+#: debug.c:5381
 #, fuzzy, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "»exit« kann im aktuellen Kontext nicht aufgerufen werden"
 
-#: debug.c:5374
+#: debug.c:5389
 #, fuzzy
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "»exit« kann im aktuellen Kontext nicht aufgerufen werden"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr ""
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr ""
 
-#: dfa.c:1052
+#: dfa.c:1174
 #, fuzzy
 msgid "invalid character class"
 msgstr "Ungültiger Name für eine Zeichenklasse"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr ""
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr ""
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Ungültiger Inhalt von \\{\\}"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Regulärer Ausdruck ist zu groß"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr ""
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr ""
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ""
 
@@ -1848,11 +1858,11 @@ msgstr "Unbekannter Opcode %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "Opcode %s ist weder ein Operator noch ein Schlüsselwort"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "Pufferüberlauf in genflags2str"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1863,71 +1873,71 @@ msgstr ""
 "\t# Funktions-Aufruf-Stack\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "»IGNORECASE« ist eine gawk-Erweiterung"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "»BINMODE« ist eine gawk-Erweiterung"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "BINMODE Wert »%s« ist ungültig und wird als 3 behandelt"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "Falsche »%sFMT«-Angabe »%s«"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "»--lint« wird abgeschaltet, da an »LINT« zugewiesen wird"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "Referenz auf nicht initialisiertes Argument »%s«"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "Referenz auf die nicht initialisierte Variable »%s«"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "Nicht numerischer Wert für Feldreferenz verwendet"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "Referenz auf ein Feld von einem Null-String"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "Versuch des Zugriffs auf Feld %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "Referenz auf das nicht initialisierte Feld »$%ld«"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "Funktion »%s« mit zu vielen Argumenten aufgerufen"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: unerwarteter Typ »%s«"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "Division durch Null versucht in »/=«"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "Division durch Null versucht in »%%=«"
@@ -1941,7 +1951,7 @@ msgstr "Erweiterungen sind im Sandbox-Modus nicht erlaubt"
 msgid "-l / @load are gawk extensions"
 msgstr "»@include« ist eine gawk-Erweiterung"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr ""
 
@@ -1974,6 +1984,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "»extension« ist eine gawk-Erweiterung"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr ""
+
 #: ext.c:180
 #, fuzzy, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1999,39 +2013,39 @@ msgstr ""
 msgid "make_builtin: missing function name"
 msgstr "Erweiterung: Funktionsname fehlt"
 
-#: ext.c:238
+#: ext.c:236
 #, fuzzy, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "Erweiterung: Funktion »%s« kann nicht neu definiert werden"
 
-#: ext.c:242
+#: ext.c:240
 #, fuzzy, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "Erweiterung: Funktion »%s« wurde bereits definiert"
 
-#: ext.c:246
+#: ext.c:244
 #, fuzzy, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "Erweiterung: Funktion »%s« wurde bereits vorher definiert"
 
-#: ext.c:248
+#: ext.c:246
 #, fuzzy, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 "Erweiterung: die eingebaute Funktion »%s« kann nicht als Funktionsname "
 "verwendet werden"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: negative Anzahl von Argumenten für Funktion »%s«"
 
-#: ext.c:278
+#: ext.c:276
 #, fuzzy
 msgid "extension: missing function name"
 msgstr "Erweiterung: Funktionsname fehlt"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, fuzzy, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "Erweiterung: unzulässiges Zeichen »%c« in Funktionsname »%s«"
@@ -2058,159 +2072,164 @@ msgstr ""
 "Erweiterung: die eingebaute Funktion »%s« kann nicht als Funktionsname "
 "verwendet werden"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr ""
 "Funktion »%s« wird als Funktion definiert, die nie mehr als %d Argument(e) "
 "akzeptiert"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "Funktion »%s«: fehlendes Argument #%d"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr ""
 "Funktion »%s«: Argument #%d: Es wird versucht, einen Skalar als Feld zu "
 "verwenden"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr ""
 "Funktion »%s«: Argument #%d: Es wird versucht, ein Feld als Skalar zu "
 "verwenden"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr ""
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 #, fuzzy
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr ""
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 #, fuzzy
 msgid "stat: called with wrong number of arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 #, fuzzy
 msgid "stat: bad parameters"
 msgstr "%s: ist ein Parameter\n"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, fuzzy, c-format
 msgid "fts init: could not create variable %s"
 msgstr "index: Zweites Argument ist kein string"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+#, fuzzy
+msgid "fts is not supported on this system"
+msgstr "»%s« wird im alten awk nicht unterstützt"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 #, fuzzy
 msgid "fill_path_element: could not set element"
 msgstr "index: Zweites Argument ist kein string"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 #, fuzzy
 msgid "fts-process: could not set element"
 msgstr "index: Zweites Argument ist kein string"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 #, fuzzy
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 #, fuzzy
 msgid "fts: bad first parameter"
 msgstr "%s: ist ein Parameter\n"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 #, fuzzy
 msgid "fts: bad second parameter"
 msgstr "%s: ist ein Parameter\n"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 #, fuzzy
 msgid "fts: bad third parameter"
 msgstr "%s: ist ein Parameter\n"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 #, fuzzy
 msgid "fts: could not flatten array\n"
 msgstr "»%s« ist kein gültiger Variablenname"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr ""
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr ""
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 #, fuzzy
 msgid "fnmatch: called with less than three arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 #, fuzzy
 msgid "fnmatch: called with more than three arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 #, fuzzy
 msgid "fnmatch: could not get first argument"
 msgstr "strftime: Das erste Argument ist kein String"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 #, fuzzy
 msgid "fnmatch: could not get second argument"
 msgstr "index: Zweites Argument ist kein string"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr ""
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr ""
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr ""
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr ""
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr ""
 
@@ -2238,88 +2257,88 @@ msgstr "sqrt: das Argument %g ist negativ"
 msgid "wait: called with too many arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr ""
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr ""
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, fuzzy, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "Fatal: extension: »%s« kann nicht geöffnet werden (%s)\n"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, fuzzy, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "»%s« ist kein gültiger Variablenname"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, fuzzy, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "%s: close ist gescheitert (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, fuzzy, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "%s: close ist gescheitert (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr ""
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, fuzzy, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "%s: close ist gescheitert (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, fuzzy, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "Das Leeren der Pipe »%s« ist gescheitert (%s)"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, fuzzy, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "Das Schließen des Dateideskriptors %d (»%s«) ist gescheitert (%s)"
@@ -2354,185 +2373,185 @@ msgstr "sqrt: das Argument %g ist negativ"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr ""
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 #, fuzzy
 msgid "readfile: called with too many arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 #, fuzzy
 msgid "readfile: called with no arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 #, fuzzy
 msgid "writea: called with too many arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, fuzzy, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, fuzzy, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "split: das vierte Argument ist kein Feld"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr ""
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr ""
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 #, fuzzy
 msgid "reada: called with too many arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, fuzzy, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, fuzzy, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "match: das dritte Argument ist kein Array"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr ""
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr ""
 
-#: extension/time.c:81
+#: extension/time.c:113
 #, fuzzy
 msgid "gettimeofday: ignoring arguments"
 msgstr "mktime: Das Argument ist kein String"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr ""
 
-#: extension/time.c:133
+#: extension/time.c:165
 #, fuzzy
 msgid "sleep: called with too many arguments"
 msgstr "sqrt: das Argument %g ist negativ"
 
-#: extension/time.c:136
+#: extension/time.c:168
 #, fuzzy
 msgid "sleep: missing required numeric argument"
 msgstr "exp: das Argument ist keine Zahl"
 
-#: extension/time.c:142
+#: extension/time.c:174
 #, fuzzy
 msgid "sleep: argument is negative"
 msgstr "exp: das Argument %g liegt außerhalb des gültigen Bereichs"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr ""
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF wird ein negativer Wert zugewiesen"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: das vierte Argument ist eine gawk-Erweiterung"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: das vierte Argument ist kein Feld"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: das zweite Argument ist kein Feld"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 "split: als zweites und viertes Argument kann nicht das gleiche Feld "
 "verwendet werden"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split: Ein untergeordnetes Feld des zweiten Arguments kann nicht als viertes "
 "Argument verwendet werden"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split: Ein untergeordnetes Feld des vierten Arguments kann nicht als zweites "
 "Argument verwendet werden"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: Null-String als drittes Argument ist eine gawk-Erweiterung"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: Das vierte Argument ist kein Feld"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: Das zweite Argument ist kein Feld"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: Das dritte Argument darf nicht Null sein"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit: als zweites und viertes Argument kann nicht das gleiche Feld "
 "verwendet werden"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit: Ein untergeordnetes Feld des zweiten Arguments kann nicht als "
 "viertes Argument verwendet werden"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit: Ein untergeordnetes Feld des vierten Arguments kann nicht als "
 "zweites Argument verwendet werden"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "»FIELDWIDTHS« ist eine gawk-Erweiterung"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "ungültiger FIELDWIDTHS-Wert nah bei »%s«"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "Null-String für »FS« ist eine gawk-Erweiterung"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "Das alte awk unterstützt keine regulären Ausdrücke als Wert von »FS«"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "»FPAT« ist eine gawk-Erweiterung"
 
@@ -2548,610 +2567,610 @@ msgstr ""
 msgid "node_to_awk_value: received null val"
 msgstr ""
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 #, fuzzy
 msgid "remove_element: received null array"
 msgstr "length: Argument ist ein Feld"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr ""
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr ""
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr ""
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, fuzzy, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: Option »%s« ist mehrdeutig\n"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: Die Option »--%s« hat keine Argumente\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: Die Option »%c%s« hat keine Argument\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: Die Option »%s« erfordert ein Argument\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: Die Option »--%s« ist unbekannt\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: Die Option »%c%s« ist unbekannt\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: Ungültige Option -- »%c«\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s Die Option »%c« erfordert ein Argument\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: Die Option »-W %s« ist mehrdeutig\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: Die Option »-W %s« hat keine Argumente\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: Die Option »-W %s« erfordert ein Argument\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr ""
 "das Kommandozeilen-Argument »%s« ist ein Verzeichnis: wird übersprungen"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "Die Datei »%s« kann nicht zum Lesen geöffnet werden (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "Das Schließen des Dateideskriptors %d (»%s«) ist gescheitert (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "Umlenkungen sind im Sandbox-Modus nicht erlaubt"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr ""
 "Der Ausdruck in einer Umlenkung mittels »%s« hat nur einen numerischen Wert"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "Der Ausdruck für eine Umlenkung mittels »%s« ist ein leerer String"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "Der Dateiname »%s« für eine Umlenkung mittels »%s« kann das Ergebnis eines "
 "logischen Ausdrucks sein"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "Unnötige Kombination von »>« und »>>« für Datei »%.*s«"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "Die Pipe »%s« kann nicht für die Ausgabe geöffnet werden (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "Die Pipe »%s« kann nicht für die Eingabe geöffnet werden (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr ""
 "Die bidirektionale Pipe »%s« kann nicht für die Ein-/Ausgabe geöffnet werden "
 "(%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "Von »%s« kann nicht umgelenkt werden (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "Zu »%s« kann nicht umgelenkt werden (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "Die Systemgrenze offener Dateien ist erreicht, daher werden nun "
 "Dateideskriptoren mehrfach verwendet"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "Das Schließen von »%s« ist gescheitert (%s)."
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "Zu viele Pipes oder Eingabedateien offen"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: Das zweite Argument muss »to« oder »from« sein"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: »%.*s« ist weder offene Datei, noch Pipe oder Ko-Prozess"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "»close« für eine Umlenkung, die nie geöffnet wurde"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: Umlenkung »%s« wurde nicht mit »[&« geöffnet, das zweite Argument "
 "wird ignoriert"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "Fehlerstatus (%d) beim Schließen der Pipe »%s« (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "Fehlerstatus (%d) beim Schließen der Datei »%s« (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "Das explizite Schließen des Sockets »%s« fehlt"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "Das explizite Schließen des Ko-Prozesses »%s« fehlt"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "Das explizite Schließen der Pipe »%s« fehlt"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "Das explizite Schließen der Datei »%s« fehlt"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "Fehler beim Schreiben auf die Standardausgabe (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "Fehler beim Schreiben auf die Standardfehlerausgabe (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "Das Leeren der Pipe »%s« ist gescheitert (%s)"
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "Ko-Prozess: Das Leeren der Pipe zu »%s« ist gescheitert (%s)"
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "Das Leeren der Datei »%s« ist gescheitert (%s)"
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "Der lokale Port »%s« ist ungültig in »/inet«"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "Die Angaben zu entferntem Host und Port (%s, %s) sind ungültig"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr "Es wurde kein (bekanntes) Protokoll im Dateinamen »%s« angegeben"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "Der Dateiname »%s« ist unvollständig"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "Sie müssen in /inet einen Rechnernamen angeben"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "Sie müssen in »/inet« einen Port angeben"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "TCP/IP-Verbindungen werden nicht unterstützt"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "»%s« konnte nicht geöffnet werden, Modus »%s«"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr ""
 "Das Schließen der übergeordneten Terminal-Gerätedatei ist gescheitert (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "Das Schließen der Standardausgabe im Kindprozess ist gescheitert (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "Das Verschieben der untergeordneten Terminal-Gerätedatei zur Standardausgabe "
 "im Kindprozess ist gescheitert (dup: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "Schließen von stdin im Kindprozess gescheitert (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "Das Verschieben der untergeordneten Terminal-Gerätedatei zur Standardeingabe "
 "im Kindprozess ist gescheitert (dup: %s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr ""
 "Das Schließen der untergeordneten Terminal-Gerätedatei ist gescheitert (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 "Das Verschieben der Pipe zur Standardausgabe im Kindprozess ist gescheitert "
 "(dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "Das Verschieben der Pipe zur Standardeingabe im Kindprozess ist gescheitert "
 "(dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr ""
 "Das Wiederherstellen der Standardausgabe im Elternprozess ist gescheitert\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr ""
 "Das Wiederherstellen der Standardeingabe im Elternprozess ist gescheitert\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "Das Schließen der Pipe ist gescheitert (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "»|&« wird nicht unterstützt"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "Pipe »%s« kann nicht geöffnet werden (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "Kindprozess für »%s« kann nicht erzeugt werden (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr ""
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr ""
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr ""
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "Die Datei »%s« ist leer"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "Es konnte kein weiterer Speicher für die Eingabe beschafft werden"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "Multicharacter-Wert von »RS« ist eine gawk-Erweiterung"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "IPv6-Verbindungen werden nicht unterstützt"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "Das leere Argument für »--source« wird ignoriert"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: Die Option »-W %s« ist unbekannt und wird ignoriert\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: Die Option %c erfordert ein Argument\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 "Die Umgebungsvariable »POSIXLY_CORRECT« ist gesetzt: »--posix« wird "
 "eingeschaltet"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "»--posix« hat Vorrang vor »--traditional«"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr "»--posix« /»--traditional« hat Vorrang vor »--non-decimal-data«"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "%s als setuid root auszuführen kann zu Sicherheitsproblemen führen"
 
-#: main.c:571
+#: main.c:588
 #, fuzzy
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "»--posix« hat Vorrang vor »--binary«"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr ""
 "Das Setzen des Binärermodus für die Standardeingabe ist nicht möglich (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr ""
 "Das Setzen des Binärermodus für die Standardausgabe ist nicht möglich (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr ""
 "Das Setzen des Binärermodus für die Standardfehlerausgabe ist nicht möglich "
 "(%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "Es wurde überhaupt kein Programmtext angegeben!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr "Aufruf: %s [POSIX- oder GNU-Optionen] -f PROGRAMM [--] Datei ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr "Aufruf: %s [POSIX- oder GNU-Optionen] -- %cPROGRAMM%c Datei ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "POSIX-Optionen\t\tlange GNU-Optionen: (standard)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f PROGRAMM\t\t--file=PROGRAMM\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F Feldtrenner\t\t\t--field-separator=Feldtrenner\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=Wert\t\t--assign=var=Wert\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "POSIX-Optionen\t\tGNU-Optionen (lang): (Erweiterungen)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d [Datei]\t\t--dump-variables[=Datei]\n"
 
-#: main.c:795
+#: main.c:815
 #, fuzzy
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-p [Datei]\t\t--profile[=Datei]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'Programmtext'\t--source=Programmtext\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E Datei\t\t\t--exec=Datei\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr ""
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr ""
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 #, fuzzy
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 #, fuzzy
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-p [Datei]\t\t--profile[=Datei]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p [Datei]\t\t--profile[=Datei]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3160,7 +3179,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3176,7 +3195,7 @@ msgstr ""
 "an translation-team-de@lists.sourceforge.net\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3187,7 +3206,7 @@ msgstr ""
 "auf der Standardausgabe aus.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3197,7 +3216,7 @@ msgstr ""
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3217,7 +3236,7 @@ msgstr ""
 "spätere Version.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3230,7 +3249,7 @@ msgstr ""
 "leistung einer HANDELBARKEIT oder der EIGNUNG FÜR EINEN BESTIMMTEN ZWECK.\n"
 "Sehen Sie bitte die GNU General Public License für weitere Details.\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3239,16 +3258,16 @@ msgstr ""
 "diesem Programm erhalten haben. Wenn nicht, lesen Sie bitte\n"
 "http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft setzt FS im POSIX-awk nicht auf Tab"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "unbekannter Wert für eine Feldangabe: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3257,50 +3276,50 @@ msgstr ""
 "%s: Argument »%s« von »-v« ist nicht in der Form »Variable=Wert«\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "»%s« ist kein gültiger Variablenname"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "»%s« ist kein Variablenname, es wird nach der Datei »%s=%s« gesucht"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr ""
 "die eingebaute Funktion »%s« kann nicht als Variablenname verwendet werden"
 
 # c-format
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "Funktion »%s« kann nicht als Name einer Variablen verwendet werden"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "Fließkomma-Ausnahme"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "Fataler Fehler: interner Fehler"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "Fataler Fehler: interner Fehler: Speicherbegrenzungsfehler"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "Fataler Fehler: interner Fehler: Stapelüberlauf"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "Kein bereits geöffneter Dateideskriptor %d"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "/dev/null konnte nicht für Dateideskriptor %d geöffnet werden"
@@ -3359,7 +3378,7 @@ msgstr "or(%lf, %lf): Dezimalteil wird abgeschnitten"
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "compl(%lf): Negativer Wert wird zu merkwürdigen Ergebnissen führen"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "Kommandozeile:"
@@ -3416,16 +3435,16 @@ msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr ""
 "%s %s »%s«: close-on-exec konnte nicht gesetzt werden: (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "»%s« konnte nicht zum Schreiben geöffnet werden: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "Das Profil wird auf der Standardfehlerausgabe ausgegeben"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3434,7 +3453,7 @@ msgstr ""
 "\t# %s Blöcke\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3443,29 +3462,29 @@ msgstr ""
 "\t# Regeln(s)\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "Interner Fehler: %s mit null vname"
 
-#: profile.c:530
+#: profile.c:537
 #, fuzzy
 msgid "internal error: builtin with null fname"
 msgstr "Interner Fehler: %s mit null vname"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# gawk-Profil, erzeugt %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3474,18 +3493,12 @@ msgstr ""
 "\n"
 "\t# Funktionen in alphabetischer Reihenfolge\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: unbekannter Umlenkungstyp %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr ""
-"Ein Bereich in der Form »[%c-%c]« ist abhängig von der gesetzten Locale"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3555,10 +3568,14 @@ msgstr ") oder \\) werden nicht geöffnet"
 msgid "No previous regular expression"
 msgstr "Kein vorangehender regulärer Ausdruck"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr ""
 
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr ""
+#~ "Ein Bereich in der Form »[%c-%c]« ist abhängig von der gesetzten Locale"
+
 #, fuzzy
 #~ msgid "[s]printf called with no arguments"
 #~ msgstr "sqrt: das Argument %g ist negativ"
diff --git a/po/es.gmo b/po/es.gmo
index 53ace354..0bfebbae 100644
--- a/po/es.gmo
+++ b/po/es.gmo
diff --git a/po/es.po b/po/es.po
index 59b53afb..d16109a9 100644
--- a/po/es.po
+++ b/po/es.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: gawk 4.0.0h\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
 "PO-Revision-Date: 2012-01-30 07:42-0600\n"
 "Last-Translator: Cristian Othón Martínez Vera <cfuga@cfuga.mx>\n"
 "Language-Team: Spanish <es@li.org>\n"
@@ -16,93 +16,93 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "desde %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "se intentó usar un valor escalar como una matriz"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "se intentó usar el parámetro escalar `%s como una matriz'"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "se intentó usar el escalar `%s' como una matriz"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "se intentó usar la matriz `%s' en un contexto escalar"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: el índice `%s' no está en la matriz `%s'"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "se intentó usar el dato escalar `%s[\"%.*s\"]' como una matriz"
 
-#: array.c:773
+#: array.c:776
 #, fuzzy
 msgid "adump: first argument not an array"
 msgstr "adump: el argumento no es una matriz"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: el segundo argumento no es una matriz"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: el segundo argumento no es una matriz"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: el primer argumento no es una matriz"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: el primer argumento no es una matriz"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asort: no se puede usar una submatriz del primer argumento para el segundo "
 "argumento"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asorti: no se puede usar una submatriz del primer argumento para el segundo "
 "argumento"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asort: no se puede usar una submatriz del segundo argumento para el primer "
 "argumento"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asorti: no se puede usar una submatriz del segundo argumento para el primer "
 "argumento"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "`%s' es inválido como un nombre de función"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "la función de comparación de ordenamiento `%s' no está definida"
@@ -147,11 +147,11 @@ msgstr "valores case duplicados en el cuerpo de un switch: %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "se detectó un `default' duplicado en el cuerpo de un switch"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "no se permite `break' fuera de un bucle o switch"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "no se permite `continue' fuera de un bucle"
 
@@ -243,275 +243,275 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr "expresión de subíndice inválida"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "aviso: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "fatal: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "nueva línea o fin de la cadena inesperados"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "no se puede abrir el fichero fuente `%s' para lectura (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, fuzzy, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "no se puede abrir el fichero fuente `%s' para lectura (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "razón desconocida"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr ""
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "ya se incluyó el fichero fuente `%s'"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, fuzzy, c-format
 msgid "already loaded shared library `%s'"
 msgstr "ya se incluyó el fichero fuente `%s'"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include es una extensión de gawk"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "nombre de fichero vacío después de @include"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 #, fuzzy
 msgid "@load is a gawk extension"
 msgstr "@include es una extensión de gawk"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 #, fuzzy
 msgid "empty filename after @load"
 msgstr "nombre de fichero vacío después de @include"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "texto de programa vacío en la linea de órdenes"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "no se puede leer el fichero fuente `%s' (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "el fichero fuente `%s' está vacío"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "el fichero fuente no termina con línea nueva"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr "expresión regular sin terminar termina con `\\` al final del fichero"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "%s: %d: el modificador de expresión regular `/.../%c` de tawk no funciona en "
 "gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "el modificador de expresión regular `/.../%c` de tawk no funciona en gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "expresión regular sin terminar"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "expresión regular sin terminar al final del fichero"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "el uso de la continuación de línea `\\ #...' no es transportable"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "la barra invertida no es el último caracter en la línea"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX no permite el operador `**='"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "el awk antiguo no admite el operador `**='"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX no permite el operador `**'"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "el awk antiguo no admite el operador `**='"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "el operador `^=' no se admite en el awk antiguo"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "el operador `^' no se admite en el awk antiguo"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "cadena sin terminar"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "caracter '%c' inválido en la expresión"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "`%s' es una extensión de gawk"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX no permite `%s'"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "`%s' no se admite en el awk antiguo"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "¡`goto' se considera dañino!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d es inválido como número de argumentos para %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 "%s: la literal de cadena como último argumento de substitute no tiene efecto"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "el tercer argumento de %s no es un objecto modificable"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: el tercer argumento es una extensión de gawk"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: el segundo argumento es una extensión de gawk"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "el uso de dcgettext(_\"...\") es incorrecto: quite el subrayado inicial"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "el uso de dcngettext(_\"...\") es incorrecto: quite el subrayado inicial"
 
-#: awkgram.y:3992
+#: awkgram.y:4016
 #, fuzzy
 msgid "index: regexp constant as second argument is not allowed"
 msgstr "index: el segundo argumento recibido no es una cadena"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "función `%s': parámetro `%s' oscurece la variable global"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "no se puede abrir `%s' para escritura (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "se envía la lista de variables a la salida estándar de error"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: falló close (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "¡se llamó shadow_funcs() dos veces!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "hay variables opacadas."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "el nombre de función `%s' se definió previamente"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr ""
 "función `%s': no se puede usar un nombre de función como nombre de parámetro"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "función `%s': no se puede usar la variable especial `%s' como un parámetro "
 "de función"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "función `%s': parámetro #%d, `%s', duplica el parámetro #%d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "se llamó a la función `%s' pero nunca se definió"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "se definió la función `%s' pero nunca se llamó directamente"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr ""
 "la constante de expresión regular para el parámetro #%d da un valor booleano"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -520,243 +520,253 @@ msgstr ""
 "se llamó la función `%s' con espacio entre el nombre y el `(',\n"
 "o se usó como una variable o una matriz"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "se intentó una división por cero"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "se intentó una división por cero en `%%'"
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+
+#: awkgram.y:5052
+#, fuzzy, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "%d es inválido como número de argumentos para %s"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "falló %s a \"%s\" (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "salida estándar"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: se recibió un argumento que no es númerico"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: no se puede limpiar: se abrió la tubería `%s' para lectura, no para "
 "escritura"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: no se puede limpiar: se abrió el fichero `%s' para lectura, no para "
 "escritura"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: `%s' no es un fichero abierto, tubería o co-proceso"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: el primer argumento recibido no es una cadena"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: el segundo argumento recibido no es una cadena"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: se recibió un argumento que no es númerico"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: se recibió un argumento de matriz"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "`length(array)' es una extensión de gawk"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: se recibió un argumento que no es una cadena"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: se recibió un argumento que no es númerico"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: se recibió el argumento negativo %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "fatal: se debe utilizar `count$' en todos los formatos o en ninguno"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "se descarta la anchura del campo para el especificador `%%'"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "se descarta la precisión para el especificador `%%'"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr ""
 "se descartan la anchura del campo y la precisión para el especificador `%%'"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "fatal: no se permite `$' en los formatos de awk"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "fatal: la cuenta de argumentos con `$' debe ser > 0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr ""
 "fatal: la cuenta de argumentos %ld es mayor que el número total de "
 "argumentos proporcionados"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "fatal: no se permite `$' después de un punto en el formato"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
 "fatal: no se proporciona `$' para la anchura o la precisión del campo "
 "posicional"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "`l' no tiene significado en los formatos de awk; se descarta"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "fatal: no se permite `l' en los formatos POSIX de awk"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "`L' no tiene significado en los formatos de awk; se descarta"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "fatal: no se permite `L' en los formatos POSIX de awk"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "`h' no tiene significado en los formatos de awk; se descarta"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "fatal: no se permite `h' en los formatos POSIX de awk"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: el valor %g está fuera del rango para el formato `%%%c'"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "se descarta el carácter especificador de formato `%c' desconocido: no se "
 "convirtió ningún argumento"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr ""
 "fatal: no hay suficientes argumentos para satisfacer a la cadena de formato"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "se acabó ^ para éste"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: el especificador de formato no tiene letras de control"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "se proporcionaron demasiados argumentos para la cadena de formato"
 
-#: builtin.c:1610
+#: builtin.c:1634
 #, fuzzy
 msgid "sprintf: no arguments"
 msgstr "printf: sin argumentos"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: sin argumentos"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: se recibió un argumento que no es un númerico"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: la longitud %g no es >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: la longitud %g no es >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: se truncará la longitud no entera %g"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr ""
 "substr: la longitud %g es demasiado grande para ser índice de cadena, se "
 "trunca a %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: el índice de inicio %g es inválido, se usa 1"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: se truncará el índice de inicio no entero %g"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: la cadena de origen es de longitud cero"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: el índice de inicio %g está después del fin de la cadena"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -764,196 +774,196 @@ msgstr ""
 "substr: la cadena %g en el índice de inicio %g excede la longitud del primer "
 "argumento (%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 "strftime: el valor de formato en PROCINFO[\"strftime\"] tiene tipo numérico"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: el segundo argumento recibido no es númerico"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr ""
 "strftime: el segundo argumento es menor que 0 o demasiado grande para time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: el primer argumento recibido no es una cadena"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: se recibió una cadena de formato vacía"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: se recibió un argumento que no es una cadena"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr ""
 "mktime: por lo menos uno de los valores está fuera del rango por defecto"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "no se permite la función 'system' en modo sandbox"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: se recibió un argumento que no es una cadena"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "referencia al campo sin inicializar `$%d'"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: se recibió un argumento que no es una cadena"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: se recibió un argumento que no es una cadena"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: el primer argumento recibido no es númerico"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: el segundo argumento recibido no es númerico"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: se recibió un argumento que no es númerico"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: se recibió un argumento que no es númerico"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: se recibió un argumento que no es númerico"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: el tercer argumento no es una matriz"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: el tercer argumento de 0 se trata como 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: el primer argumento recibido no es númerico"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: el segundo argumento recibido no es númerico"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, fuzzy, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%lf, %lf): los valores negativos darán resultados extraños"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, fuzzy, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%lf, %lf): los valores fraccionarios se truncarán"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, fuzzy, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "lshift(%lf, %lf): un valor de desplazamiento muy grande dará resultados "
 "extraños"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: el primer argumento recibido no es númerico"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: el segundo argumento recibido no es númerico"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, fuzzy, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%lf, %lf): los valores negativos darán resultados extraños"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, fuzzy, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%lf, %lf): los valores fraccionarios serán truncados"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, fuzzy, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "rshift(%lf, %lf): un valor de desplazamiento muy grande dará resultados "
 "extraños"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 #, fuzzy
 msgid "and: called with less than two arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, fuzzy, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, fuzzy, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr "and(%lf, %lf): los valores negativos darán resultados extraños"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 #, fuzzy
 msgid "or: called with less than two arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, fuzzy, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, fuzzy, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "compl(%lf): el valor negativo dará resultados extraños"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 #, fuzzy
 msgid "xor: called with less than two arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, fuzzy, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, fuzzy, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor(%lf, %lf): los valores negativos darán resultados extraños"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: se recibió un argumento que no es númerico"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, fuzzy, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%lf): el valor negativo dará resultados extraños"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, fuzzy, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%lf): el valor fraccionario se truncará"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: `%s' no es una categoría local válida"
@@ -1077,8 +1087,8 @@ msgstr ""
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 
 #: command.y:825
@@ -1235,7 +1245,7 @@ msgstr ""
 msgid "watch var - set a watchpoint for a variable."
 msgstr ""
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "error: "
@@ -1275,561 +1285,561 @@ msgstr "Caracter de ordenación inválido"
 msgid "undefined command: %s\n"
 msgstr ""
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr ""
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr ""
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr ""
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr ""
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr ""
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr ""
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, fuzzy, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "no se puede leer el fichero fuente `%s' (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, fuzzy, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "el fichero fuente `%s' está vacío"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr ""
 
-#: debug.c:499
+#: debug.c:505
 #, fuzzy, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "no se puede leer el fichero fuente `%s' (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr ""
 
-#: debug.c:602
+#: debug.c:611
 #, fuzzy, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "error interno: fichero `%s', línea %d\n"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr ""
 
-#: debug.c:723
+#: debug.c:732
 #, fuzzy, c-format
 msgid "Current source file: %s\n"
 msgstr "ya se incluyó el fichero fuente `%s'"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr ""
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr ""
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr ""
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr ""
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr ""
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr ""
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr ""
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr ""
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr ""
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr ""
 
-#: debug.c:839
+#: debug.c:848
 #, fuzzy
 msgid "No arguments.\n"
 msgstr "printf: sin argumentos"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr ""
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:1020
+#: debug.c:1029
 #, fuzzy, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "`exit' no se puede llamar en el contexto actual"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, fuzzy, c-format
 msgid "`%s' is not an array\n"
 msgstr "`%s' no es un nombre de variable legal"
 
-#: debug.c:1046
+#: debug.c:1055
 #, fuzzy, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "referencia al campo sin inicializar `$%d'"
 
-#: debug.c:1067
+#: debug.c:1076
 #, fuzzy, c-format
 msgid "array `%s' is empty\n"
 msgstr "el fichero de datos `%s' está vacío"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "delete: el índice `%s' no está en la matriz `%s'"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr ""
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, fuzzy, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "`%s' no es un nombre de variable legal"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, fuzzy, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "se intentó usar la matriz `%s[\"%.*s\"]' en un contexto escalar"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, fuzzy, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "se intentó usar el dato escalar `%s[\"%.*s\"]' como una matriz"
 
-#: debug.c:1414
+#: debug.c:1423
 #, fuzzy, c-format
 msgid "`%s' is a function"
 msgstr "`%s' es inválido como un nombre de función"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr ""
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr ""
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr ""
 
-#: debug.c:1519
+#: debug.c:1528
 #, fuzzy, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "delete: el índice `%s' no está en la matriz `%s'"
 
-#: debug.c:1758
+#: debug.c:1767
 #, fuzzy
 msgid "attempt to use scalar value as array"
 msgstr "se intentó usar un valor escalar como una matriz"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1891
+#: debug.c:1900
 #, fuzzy, c-format
 msgid " in file `%s', line %d\n"
 msgstr "error interno: fichero `%s', línea %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr ""
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr ""
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr ""
 
-#: debug.c:2008
+#: debug.c:2017
 #, fuzzy
 msgid "invalid frame number"
 msgstr "Final de rango inválido"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2218
+#: debug.c:2238
 #, fuzzy, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr "error interno: fichero `%s', línea %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr ""
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, fuzzy, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr ""
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr ""
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr ""
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr ""
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr ""
 
-#: debug.c:2521
+#: debug.c:2541
 #, fuzzy, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "error interno: fichero `%s', línea %d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr ""
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr ""
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr ""
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr ""
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr ""
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr ""
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr ""
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr ""
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr ""
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr ""
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr ""
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr ""
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr ""
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr ""
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr ""
 
-#: debug.c:3357
+#: debug.c:3377
 #, fuzzy, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "ya se incluyó el fichero fuente `%s'"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, fuzzy, c-format
 msgid "element not in array\n"
 msgstr "delete: el índice `%s' no está en la matriz `%s'"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr ""
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr ""
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr ""
 
-#: debug.c:4986
+#: debug.c:5001
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "delete: el índice `%s' no está en la matriz `%s'"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr ""
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr ""
 
-#: debug.c:5366
+#: debug.c:5381
 #, fuzzy, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "`exit' no se puede llamar en el contexto actual"
 
-#: debug.c:5374
+#: debug.c:5389
 #, fuzzy
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "`exit' no se puede llamar en el contexto actual"
 
-#: debug.c:5575
+#: debug.c:5590
 #, fuzzy, c-format
 msgid "No symbol `%s' in current context"
 msgstr "se intentó usar la matriz `%s' en un contexto escalar"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 #, fuzzy
 msgid "unbalanced ["
 msgstr "[ desbalanceado"
 
-#: dfa.c:1052
+#: dfa.c:1174
 #, fuzzy
 msgid "invalid character class"
 msgstr "Nombre de clase de caracter inválido"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr ""
 
-#: dfa.c:1281
+#: dfa.c:1366
 #, fuzzy
 msgid "unfinished \\ escape"
 msgstr "Escape \\ sin terminar"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Contenido inválido de \\{\\}"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "La expresión regular es demasiado grande"
 
-#: dfa.c:1816
+#: dfa.c:1936
 #, fuzzy
 msgid "unbalanced ("
 msgstr "( desbalanceado"
 
-#: dfa.c:1943
+#: dfa.c:2062
 #, fuzzy
 msgid "no syntax specified"
 msgstr "No se especifican los bits de sintaxis de la expresión regular"
 
-#: dfa.c:1951
+#: dfa.c:2070
 #, fuzzy
 msgid "unbalanced )"
 msgstr ") desbalanceado"
@@ -1849,11 +1859,11 @@ msgstr "código de operación %d desconocido"
 msgid "opcode %s not an operator or keyword"
 msgstr "el código de operación %s no es un operador o una palabra clave"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "desbordamiento de almacenamiento temporal en genflags2str"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1864,71 +1874,71 @@ msgstr ""
 "\t# Pila de Llamadas de Funciones:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "`IGNORECASE' es una extensión de gawk"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "`BINMODE' es una extensión de gawk"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "el valor BINMODE `%s' es inválido; se trata como 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "especificación `%sFMT' `%s' errónea"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "se desactiva `--lint' debido a una asignación a `LINT'"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "referencia al argumento sin inicializar `%s'"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "referencia a la variable sin inicializar `%s'"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "se intentó una referencia de campo desde un valor que no es númerico"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "se intentó una referencia de campo desde una cadena nula"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "se intentó acceder al campo %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "referencia al campo sin inicializar `$%ld'"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "se llamó a la función `%s' con más argumentos de los declarados"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: tipo `%s' inesperado"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "se intentó una división por cero en `/='"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "se intentó una división por cero en `%%='"
@@ -1942,7 +1952,7 @@ msgstr "no se permiten las extensiones en modo sandbox"
 msgid "-l / @load are gawk extensions"
 msgstr "@include es una extensión de gawk"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr ""
 
@@ -1975,6 +1985,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "`extension' es una extensión de gawk"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr ""
+
 #: ext.c:180
 #, fuzzy, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -2000,39 +2014,39 @@ msgstr ""
 msgid "make_builtin: missing function name"
 msgstr "extension: falta el nombre de la función"
 
-#: ext.c:238
+#: ext.c:236
 #, fuzzy, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "extension: no se puede redefinir la función `%s'"
 
-#: ext.c:242
+#: ext.c:240
 #, fuzzy, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "extension: la función `%s' ya está definida"
 
-#: ext.c:246
+#: ext.c:244
 #, fuzzy, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "extension: el nombre de función `%s' se definió previamente"
 
-#: ext.c:248
+#: ext.c:246
 #, fuzzy, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 "extension: no se puede utilizar la orden interna de gawk `%s' como nombre de "
 "función"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: cuenta de argumento negativa para la función `%s'"
 
-#: ext.c:278
+#: ext.c:276
 #, fuzzy
 msgid "extension: missing function name"
 msgstr "extension: falta el nombre de la función"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, fuzzy, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: carácter ilegal `%c' en el nombre de la función `%s'"
@@ -2059,155 +2073,160 @@ msgstr ""
 "extension: no se puede utilizar la orden interna de gawk `%s' como nombre de "
 "función"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "la función `%s' se definió para tomar no más de %d argumento(s)"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "función `%s': falta el argumento #%d"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr ""
 "función `%s': argumento #%d: se intentó usar un escalar como una matriz"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr ""
 "función `%s': argumento #%d: se intentó usar una matriz como un escalar"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr ""
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 #, fuzzy
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr ""
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 #, fuzzy
 msgid "stat: called with wrong number of arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 #, fuzzy
 msgid "stat: bad parameters"
 msgstr "%s: es un parámetro\n"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, fuzzy, c-format
 msgid "fts init: could not create variable %s"
 msgstr "index: el segundo argumento recibido no es una cadena"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+#, fuzzy
+msgid "fts is not supported on this system"
+msgstr "`%s' no se admite en el awk antiguo"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 #, fuzzy
 msgid "fill_path_element: could not set element"
 msgstr "index: el segundo argumento recibido no es una cadena"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 #, fuzzy
 msgid "fts-process: could not set element"
 msgstr "index: el segundo argumento recibido no es una cadena"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 #, fuzzy
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 #, fuzzy
 msgid "fts: bad first parameter"
 msgstr "%s: es un parámetro\n"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 #, fuzzy
 msgid "fts: bad second parameter"
 msgstr "%s: es un parámetro\n"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 #, fuzzy
 msgid "fts: bad third parameter"
 msgstr "%s: es un parámetro\n"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 #, fuzzy
 msgid "fts: could not flatten array\n"
 msgstr "`%s' no es un nombre de variable legal"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr ""
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr ""
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 #, fuzzy
 msgid "fnmatch: called with less than three arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 #, fuzzy
 msgid "fnmatch: called with more than three arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 #, fuzzy
 msgid "fnmatch: could not get first argument"
 msgstr "strftime: el primer argumento recibido no es una cadena"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 #, fuzzy
 msgid "fnmatch: could not get second argument"
 msgstr "index: el segundo argumento recibido no es una cadena"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr ""
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr ""
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr ""
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr ""
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr ""
 
@@ -2235,88 +2254,88 @@ msgstr "sqrt: se llamó con el argumento negativo %g"
 msgid "wait: called with too many arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr ""
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr ""
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, fuzzy, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "fatal: extension: no se puede abrir `%s' (%s)\n"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, fuzzy, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "`%s' no es un nombre de variable legal"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, fuzzy, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "%s: falló close (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, fuzzy, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "%s: falló close (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr ""
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, fuzzy, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "%s: falló close (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, fuzzy, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "falló la limpieza de la tubería de `%s' (%s)."
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, fuzzy, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "falló al cerrar el df %d (`%s') (%s)"
@@ -2351,185 +2370,185 @@ msgstr "sqrt: se llamó con el argumento negativo %g"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr ""
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 #, fuzzy
 msgid "readfile: called with too many arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 #, fuzzy
 msgid "readfile: called with no arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 #, fuzzy
 msgid "writea: called with too many arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, fuzzy, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, fuzzy, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "split: el cuarto argumento no es una matriz"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr ""
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr ""
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 #, fuzzy
 msgid "reada: called with too many arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, fuzzy, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, fuzzy, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "match: el tercer argumento no es una matriz"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr ""
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr ""
 
-#: extension/time.c:81
+#: extension/time.c:113
 #, fuzzy
 msgid "gettimeofday: ignoring arguments"
 msgstr "mktime: se recibió un argumento que no es una cadena"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr ""
 
-#: extension/time.c:133
+#: extension/time.c:165
 #, fuzzy
 msgid "sleep: called with too many arguments"
 msgstr "sqrt: se llamó con el argumento negativo %g"
 
-#: extension/time.c:136
+#: extension/time.c:168
 #, fuzzy
 msgid "sleep: missing required numeric argument"
 msgstr "exp: se recibió un argumento que no es númerico"
 
-#: extension/time.c:142
+#: extension/time.c:174
 #, fuzzy
 msgid "sleep: argument is negative"
 msgstr "exp: el argumento %g está fuera de rango"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr ""
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "se definió NF con un valor negativo"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: el cuarto argumento es una extensión de gawk"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: el cuarto argumento no es una matriz"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: el segundo argumento no es una matriz"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 "split: no se puede usar la misma matriz para el segundo y cuarto argumentos"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split: no se puede usar una submatriz del segundo argumento para el cuarto "
 "argumento"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split: no se puede usar una submatriz del cuarto argumento para el segundo "
 "argumento"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr ""
 "split: la cadena nula para el tercer argumento es una extensión de gawk"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: el cuarto argumento no es una matriz"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: el segundo argumento no es una matriz"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: el tercer argumento no debe ser nulo"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit: no se puede usar la misma matriz para el segundo y cuarto "
 "argumentos"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit: no se puede usar una submatriz del segundo argumento para el "
 "cuarto argumento"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit: no se puede usar una submatriz del cuarto argumento para el "
 "segundo argumento"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "`FIELDWIDTHS' es una extensión gawk"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "valor de FIELDWIDTHS inválido, cerca de `%s'"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "la cadena nula para `FS' es una extensión de gawk"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "el awk antiguo no admite expresiones regulares como valor de `FS'"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "`FPAT' es una extensión de gawk"
 
@@ -2545,602 +2564,602 @@ msgstr ""
 msgid "node_to_awk_value: received null val"
 msgstr ""
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 #, fuzzy
 msgid "remove_element: received null array"
 msgstr "length: se recibió un argumento de matriz"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr ""
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr ""
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr ""
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, fuzzy, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: la opción '%s' es ambigua\n"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: la opción '--%s' no admite ningún argumento\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: la opción '%c%s' no admite ningún argumento\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: la opción '--%s' requiere un argumento\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: no se reconoce la opción '--%s'\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: no se reconoce la opción '%c%s'\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: opción inválida -- '%c'\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: la opción requiere un argumento -- '%c'\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: la opción '-W %s' es ambigua\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: la opción '-W %s' no admite ningún argumento\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: la opción '-W %s' requiere un argumento\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "el argumento de la línea de órdenes `%s' es un directorio: se salta"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "no se puede abrir el fichero `%s' para lectura (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "falló al cerrar el df %d (`%s') (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "no se permite la redirección en modo sandbox"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "la expresión en la redirección `%s' sólo tiene valor numérico"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "la expresión para la redirección `%s' tiene un valor de cadena nula"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "el fichero `%s' para la redirección `%s' puede ser resultado de una "
 "expresión lógica"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "mezcla innecesaria de `>' y `>>' para el fichero `%.*s'"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "no se puede abrir la tubería `%s' para la salida (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "no se puede abrir la tubería `%s' para la entrada (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr "no se puede abrir la tubería de dos vías `%s' para entrada/salida (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "no se puede redirigir desde `%s' (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "no se puede redirigir a `%s' (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "se alcanzó el límite del sistema para ficheros abiertos: comenzando a "
 "multiplexar los descriptores de fichero"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "falló al cerrar `%s' (%s)."
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "demasiadas tuberías o ficheros de entrada abiertos"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: el segundo argumento debe ser `to' o `from'"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: `%.*s' no es un fichero abierto, tubería o co-proceso"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "se cerró una redirección que nunca se abrió"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: la redirección `%s' no se abrió con `|&', se descarta el segundo "
 "argumento"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "estado de fallo (%d) al cerrar la tubería de `%s' (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "estado de fallo (%d) al cerrar el fichero de `%s' (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "no se provee el cerrado explícito del `socket' `%s'"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "no se provee el cerrado explícito del co-proceso `%s'"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "no se provee el cerrado explícito del la tubería `%s'"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "no se provee el cerrado explícito del fichero `%s'"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "error al escribir en la salida estándar (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "error al escribir en la salida estándar de error (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "falló la limpieza de la tubería de `%s' (%s)."
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "falló la limpieza del co-proceso de la tubería a `%s' (%s)."
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "falló la limpieza del fichero de `%s' (%s)."
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "puerto local %s inválido en `/inet'"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "anfitrión remoto e información de puerto (%s, %s) inválidos"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr ""
 "no se proporciona algún protocolo (conocido) en el nombre de fichero "
 "especial `%s'"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "el nombre de fichero especial `%s' está incompleto"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "se debe proporcionar a `/inet' un nombre de anfitrión remoto"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "se debe proporcionar a `/inet' un puerto remoto"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "no se admiten las comunicaciones TCP/IP"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "no se puede abrir `%s', modo `%s'"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "falló al cerrar el pty maestro (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "falló al cerrar la salida estándar en el hijo (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "falló el movimiento del pty esclavo a la salida estándar en el hijo (dup: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "falló al cerrar la entrada estándar en el hijo (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "falló el movimiento del pty esclavo a la entrada estándar en el hijo (dup: "
 "%s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "falló al cerrar el pty esclavo (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr "falló el movimiento a la salida estándar en el hijo (dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "falló el movimiento de la tubería a la entrada estándar en el hijo (dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "falló la restauración de la salida estándar en el proceso padre\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "falló la restauración de la entrada estándar en el proceso padre\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "falló al cerrar la tubería (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "no se admite `|&'"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "no se puede abrir la tubería `%s' (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "no se puede crear el proceso hijo para `%s' (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr ""
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr ""
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr ""
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "el fichero de datos `%s' está vacío"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "no se puede reservar más memoria de entrada"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "el valor multicaracter de `RS' es una extensión de gawk"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "no se admite la comunicación IPv6"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "se descarta el argumento vacío para `-e/--source'"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: no se reconoce la opción `-W %s', se descarta\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: la opción requiere un argumento -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 "la variable de ambiente `POSIXLY_CORRECT' está definida: se activa `--posix'"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "`--posix' se impone a `--traditional'"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr "`--posix'/`--traditional' se imponen a `--non-decimal-data'"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "ejecutar %s como setuid root puede ser un problema de seguridad"
 
-#: main.c:571
+#: main.c:588
 #, fuzzy
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "`--posix' se impone a `--binary'"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "no se puede establecer el modo binario en la entrada estándar (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "no se puede establecer el modo binario en la salida estándar (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr ""
 "no se puede establecer el modo binario en la salida estándar de error (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "¡No hay ningún programa de texto!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 "Modo de empleo: %s [opciones estilo POSIX o GNU] -f fichprog [--] "
 "fichero ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 "Modo de empleo: %s [opciones estilo POSIX o GNU] [--] %cprograma%c "
 "fichero ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "Opciones POSIX:\t\tOpciones largas GNU: (estándar)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f fichprog\t\t--file=fichprog\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F sc\t\t\t--field-separator=sc\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=valor\t\t--assign=var=valor\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "Opciones cortas:\t\tOpciones largas GNU: (extensiones)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[fichero]\t\t--dump-variables[=fichero]\n"
 
-#: main.c:795
+#: main.c:815
 #, fuzzy
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-p[fichero]\t\t--profile[=fichero]\n"
 
 # Esta es la línea más larga de la lista de argumentos.
 # Probar con gawk para revisar tabuladores. cfuga
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'texto-prog'\t--source='texto-prog'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E fichero\t\t--exec=fichero\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr ""
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr ""
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 #, fuzzy
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 #, fuzzy
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-p[fichero]\t\t--profile[=fichero]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[fichero]\t\t--profile[=fichero]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3149,7 +3168,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3163,7 +3182,7 @@ msgstr ""
 "Reporte los errores de los mensajes en español a <es@li.org>.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3173,7 +3192,7 @@ msgstr ""
 "Por defecto lee la entrada estándar y escribe en la salida estándar.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3183,7 +3202,7 @@ msgstr ""
 "\tgawk '{ sum += $1 }; END { print sum }' fichero\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3203,7 +3222,7 @@ msgstr ""
 "(a su elección) cualquier versión posterior.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3217,7 +3236,7 @@ msgstr ""
 "Licencia Pública General de GNU para más detalles.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3226,16 +3245,16 @@ msgstr ""
 "junto con este programa. Si no es así, consulte\n"
 "http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft no establece FS a tabulador en el awk de POSIX"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "valor desconocido para la especificación de campo: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3244,49 +3263,49 @@ msgstr ""
 "%s: el argumento `%s' para `-v' no es de la forma `var=valor'\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "`%s' no es un nombre de variable legal"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "`%s' no es un nombre de variable, se busca el fichero `%s=%s'"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr ""
 "no se puede utilizar la orden interna de gawk `%s' como nombre de variable"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "no se puede usar la función `%s' como nombre de variable"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "excepción de coma flotante"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "error fatal: error interno"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "error fatal: error interno: falla de segmentación"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "error fatal: error interno: desbordamiento de pila"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "no existe el df %d abierto previamente"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "no se puede abrir previamente /dev/null para el df %d"
@@ -3345,7 +3364,7 @@ msgstr "or(%lf, %lf): los valores fraccionarios serán truncados"
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "compl(%lf): el valor negativo dará resultados extraños"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "línea ord.:"
@@ -3400,16 +3419,16 @@ msgstr ""
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr "%s %s `%s': no se puede establecer close-on-exec: (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "no se puede abrir `%s' para escritura: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "se envía el perfil a la salida estándar de error"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3418,7 +3437,7 @@ msgstr ""
 "\t# bloque(s) %s\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3427,29 +3446,29 @@ msgstr ""
 "\t# Regla(s)\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "error interno: %s con vname nulo"
 
-#: profile.c:530
+#: profile.c:537
 #, fuzzy
 msgid "internal error: builtin with null fname"
 msgstr "error interno: %s con vname nulo"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# perfil de gawk, creado %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3458,17 +3477,12 @@ msgstr ""
 "\n"
 "\t# Funciones, enumeradas alfabéticamente\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: tipo de redirección %d desconocida"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "el rango de la forma `[%c-%c]' depende del local"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3538,10 +3552,13 @@ msgstr ") o \\) desemparejados"
 msgid "No previous regular expression"
 msgstr "No hay una expresión regular previa"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr ""
 
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "el rango de la forma `[%c-%c]' depende del local"
+
 #, fuzzy
 #~ msgid "[s]printf called with no arguments"
 #~ msgstr "sqrt: se llamó con el argumento negativo %g"
diff --git a/po/fi.gmo b/po/fi.gmo
index 18411e5b..478aa070 100644
--- a/po/fi.gmo
+++ b/po/fi.gmo
diff --git a/po/fi.po b/po/fi.po
index 37607553..49014233 100644
--- a/po/fi.po
+++ b/po/fi.po
@@ -1,14 +1,14 @@
 # Finnish messages for gawk.
-# Copyright © 2010, 2011, 2012 Free Software Foundation, Inc.
+# Copyright © 2010, 2011, 2012, 2013, 2014 Free Software Foundation, Inc.
 # This file is distributed under the same license as the gawk package.
-# Jorma Karvonen <karvonen.jorma@gmail.com>, 2010-2012.
+# Jorma Karvonen <karvonen.jorma@gmail.com>, 2010-2014.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk 4.0.0h\n"
+"Project-Id-Version: gawk 4.1.0b\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
-"PO-Revision-Date: 2012-03-13 18:00+0200\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-01-16 13:32+0200\n"
 "Last-Translator: Jorma Karvonen <karvonen.jorma@gmail.com>\n"
 "Language-Team: Finnish <translation-team-fi@lists.sourceforge.net>\n"
 "Language: fi\n"
@@ -16,94 +16,94 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Generator: Poedit 1.5.4\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "taulukosta %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "yritettiin käyttää skalaariarvoa taulukkona"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "yritettiin käyttää skalaariparametria ”%s” taulukkona"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "yritettiin käyttää skalaaria ”%s” taulukkona"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "yritettiin käyttää taulukkoa ”%s” skalaarikontekstissa"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: indeksi ”%s” ei ole taulukossa ”%s”"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "yritettiin käyttää skalaaria ”%s[\"%.*s\"]” taulukkona"
 
-#: array.c:773
-#, fuzzy
+#: array.c:776
 msgid "adump: first argument not an array"
-msgstr "adump: argumentti ei ole taulukko"
+msgstr "adump: ensimmäinen argumentti ei ole taulukko"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: toinen argumentti ei ole taulukko"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: toinen argumentti ei ole taulukko"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: ensimmäinen argumentti ei ole taulukko"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: ensimmäinen argumentti ei ole taulukko"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
-"asort: ei voida käyttää ensimmäisen argumentin alitaulukkoa toiselle "
-"argumentille"
+"asort: ensimmäisen argumentin alitaulukon käyttö toiselle argumentille "
+"epäonnistui"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
-"asorti: ei voida käyttää ensimmäisen argumentin alitaulukkoa toiselle "
-"argumentille"
+"asorti: ensimmäisen argumentin alitaulukon käyttö toiselle argumentille "
+"epäonnistui"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
-"asort: ei voida käyttää toisen argumentin alitaulukkoa ensimmäiselle "
-"argumentille"
+"asort: toisen argumentin alitaulukon käyttö ensimmäiselle argumentille "
+"epäonnistui"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
-"asorti: ei voida käyttää toisen argumentin alitaulukkoa ensimmäiselle "
-"argumentille"
+"asorti: toisen argumentin alitaulukon käyttö ensimmäiselle argumentille "
+"epäonnistui"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "”%s” on virheellinen funktionimenä"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "lajitteluvertailufunktiota ”%s” ei ole määritelty"
@@ -146,11 +146,11 @@ msgstr "kaksi samanlaista case-arvoa switch-rakenteen rungossa: %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "kaksoiskappale ”default” havaittu switch-rungossa"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "”break” ei ole sallittu silmukan tai switch-lauseen ulkopuolella"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "”continue” ei ole sallittu silmukan ulkopuolella"
 
@@ -175,11 +175,11 @@ msgstr ""
 
 #: awkgram.y:988 awkgram.y:1037
 msgid "`delete' is not allowed with SYMTAB"
-msgstr ""
+msgstr "”delete” ei ole sallittu kohteessa SYMTAB"
 
 #: awkgram.y:990 awkgram.y:1039
 msgid "`delete' is not allowed with FUNCTAB"
-msgstr ""
+msgstr "”delete” ei ole sallittu kohteessa FUNCTAB"
 
 #: awkgram.y:1024 awkgram.y:1028
 msgid "`delete(array)' is a non-portable tawk extension"
@@ -234,274 +234,272 @@ msgstr "epäsuorat funktiokutsut ovat gawk-laajennus"
 #: awkgram.y:1620
 #, c-format
 msgid "can not use special variable `%s' for indirect function call"
-msgstr "ei voi käyttää erikoismuuttujaa ”%s” epäsuoralle funktiokutsulle"
+msgstr "erikoismuuttujan ”%s” käyttö epäsuoralle funktiokutsulle epäonnistui"
 
 #: awkgram.y:1698
 msgid "invalid subscript expression"
 msgstr "virheellinen indeksointilauseke"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
-msgstr "varoitus:"
+msgstr "varoitus: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
-msgstr "tuhoisa:"
+msgstr "tuhoisa: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "odottamaton rivinvaihto tai merkkijonon loppu"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
-msgstr "ei voi avata lähdetiedostoa ”%s” lukemista varten (%s)"
+msgstr "lähdetiedoston ”%s” avaaminen lukemista varten (%s) epäonnistui"
 
-#: awkgram.y:2360 awkgram.y:2485
-#, fuzzy, c-format
+#: awkgram.y:2384 awkgram.y:2509
+#, c-format
 msgid "can't open shared library `%s' for reading (%s)"
-msgstr "ei voi avata lähdetiedostoa ”%s” lukemista varten (%s)"
+msgstr "jaetun kirjaston ”%s” avaaminen lukemista varten (%s) epäonnistui"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "syy tuntematon"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
-msgstr ""
+msgstr "kohteen ”%s” sisällyttäminen ja käyttö ohjelmatiedostona epäonnistui"
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "on jo sisällytetty lähdetiedostoon ”%s”"
 
-#: awkgram.y:2385
-#, fuzzy, c-format
+#: awkgram.y:2409
+#, c-format
 msgid "already loaded shared library `%s'"
-msgstr "on jo sisällytetty lähdetiedostoon ”%s”"
+msgstr "jaettu kirjasto ”%s” on jo ladattu"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include on gawk-laajennus"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "tyhjä tiedostonimi @include:n jälkeen"
 
-#: awkgram.y:2470
-#, fuzzy
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
-msgstr "@include on gawk-laajennus"
+msgstr "@load on gawk-laajennus"
 
-#: awkgram.y:2476
-#, fuzzy
+#: awkgram.y:2500
 msgid "empty filename after @load"
-msgstr "tyhjä tiedostonimi @include:n jälkeen"
+msgstr "tyhjä tiedostonimi @load:n jälkeen"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "tyhjä ohjelmateksti komentorivillä"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
-msgstr "ei voi lukea lähdetiedostoa ”%s” (%s)"
+msgstr "lähdetiedoston ”%s” (%s) lukeminen epäonnistui"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "lähdetiedosto ”%s” on tyhjä"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "lähdetiedoston lopussa ei ole rivinvaihtoa"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr ""
 "päättämätön säännöllinen lauseke loppuu ”\\”-merkkeihin tiedoston lopussa"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "%s: %d: tawk:n regex-määre ”/.../%c” ei toimi gawk:ssa"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "tawkin regex-määre ”/.../%c” ei toimi gawkissa"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "päättämätön säännöllinen lauseke"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "päättämätön säännöllinen lauseke tiedoston lopussa"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "”\\ #...”-rivijatkamisen käyttö ei ole siirrettävä"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "kenoviiva ei ole rivin viimeinen merkki"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX ei salli operaattoria ”**=”"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "vanha awk ei tue operaattoria ”**=”"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX ei salli operaattoria ”**”"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "vanha awk ei tue operaattoria ”**”"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "operaattoria ”^=” ei tueta vanhassa awk:ssa"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "operaattoria ”^” ei tueta vanhassa awk:ssa"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "päättämätön merkkijono"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "virheellinen merkki ’%c’ lausekkeessa"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "”%s” on gawk-laajennus"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
-msgstr "POSIX ei salli operaattori ”%s”"
+msgstr "POSIX ei salli operaattoria ”%s”"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "”%s” ei ole tuettu vanhassa awk-ohjelmassa"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "”goto”-käskyä pidetään haitallisena!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d on virheellinen argumenttilukumäärä operaattorille %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 "%s: merkkijonoliteraalilla ei ole vaikutusta korvauksen viimeisenä "
 "argumenttina"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "%s kolmas parametri ei ole vaihdettava objekti"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: kolmas argumentti on gawk-laajennus"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: toinen argumentti on gawk-laajennus"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "dcgettext(_\"...\")-käyttö on virheellinen: poista alaviiva alusta"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "dcngettext(_\"...\")-käyttö on virheellinen: poista alaviiva alusta"
 
-#: awkgram.y:3992
-#, fuzzy
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
-msgstr "index: toinen vastaanotettu argumentti ei ole merkkijono"
+msgstr "index: regexp-vakio toisena argumenttina ei ole sallittu"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "funktio ”%s”: parametri ”%s” varjostaa yleismuuttujaa"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
-msgstr "ei voitu avata tiedostoa ”%s” kirjoittamista varten (%s)"
+msgstr "tiedoston ”%s” avaaminen kirjoittamista varten (%s) epäonnistui"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "lähetetään muuttujaluettelo vakiovirheeseen"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: sulkeminen epäonnistui (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() kutsuttu kahdesti!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "siellä oli varjostettuja muuttujia."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "funktionimi ”%s” on jo aikaisemmin määritelty"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
-msgstr "funktio ”%s”: ei voi käyttää funktionimeä parametrinimenä"
+msgstr "funktio ”%s”: funktionimen käyttö parametrinimenä epäonnistui"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
-msgstr "funktio ”%s”: ei voi käyttää erikoismuuttujaa ”%s” funktioparametrina"
+msgstr ""
+"funktio ”%s”: erikoismuuttujan ”%s” käyttö funktioparametrina epäonnistui"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "funktio ”%s”: parametri #%d, ”%s”, samanlainen parametri #%d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "funktiota ”%s” kutsuttiin, mutta sitä ei ole koskaan määritelty"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "funktio ”%s” määriteltiin, mutta sitä ei ole koskaan kutsuttu suoraan"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "säännöllisen lausekkeen vakio parametrille #%d antaa boolean-arvon"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -510,240 +508,249 @@ msgstr ""
 "funktio ”%s” kutsuttu välilyönnillä nimen ja ”(”-merkin\n"
 "välillä, tai käytetty muuttujana tai taulukkona"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "nollalla jakoa yritettiin"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "jakoa nollalla yritettiin operaattorissa ”%%”"
 
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr "arvon liittäminen kenttäjälkiaskelkasvatuslausekkeeseen epäonnistui"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "virheellinen liittämiskohde (käskykoodi %s)"
+
 #  kohteena voi olla vakiotuloste tai joku muu
-#: builtin.c:128
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s kohteeseen ”%s” epäonnistui (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "vakiotuloste"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: argumentti %g on lukualueen ulkopuolella"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
-"fflush: ei voi tyhjentää: putki ”%s” avattu lukemista varten, ei "
+"fflush: tyhjentäminen epäonnistui: putki ”%s” avattu lukemista varten, ei "
 "kirjoittamiseen"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
-"fflush: ei voi tyhjentää: tiedosto ”%s” avattu lukemista varten, ei "
+"fflush: tyhjentäminen epäonnistui: tiedosto ”%s” avattu lukemista varten, ei "
 "kirjoittamiseen"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: ”%s” ei ole avoin tiedosto, putki tai apuprosessi"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: ensimmäinen vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: toinen vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: vastaanotettu taulukkoargumentti"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "”length(array)” on gawk-laajennus"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: vastaanotettu negatiivinen argumentti %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "kohtalokas: on käytettävä ”count$” kaikilla muodoilla tai ei missään"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "kenttäleveys ohitetaan ”%%%%”-määritteelle"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "tarkkuus ohitetaan ”%%%%”-määritteelle"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "kenttäleveys ja tarkkuus ohitetaan ”%%%%”-määritteelle"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "kohtalokas: ”$”-argumentti ei ole sallittu awk-muodoissa"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "kohtalokas: argumenttilukumäärän argumentilla ”$” on oltava > 0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr ""
 "kohtalokas: argumenttilukumäärä %ld on suurempi kuin toimitettujen "
 "argumenttien lukumäärä"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "kohtalokas: ”$”-argumentti ei ole sallittu pisteen jälkeen muodossa"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
 "kohtalokas: ei ”$”-argumenttia tarjottu sijantikenttäleveydelle tai "
 "tarkkuudelle"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "”l” on merkityksetön awk-muodoissa; ohitetaan"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "kohtalokas: ”l” ei ole sallittu POSIX awk -muodoissa"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "”L” on merkityksetön awk-muodoissa; ohitetaan"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "kohtalokas: ”L” ei ole sallittu POSIX awk -muodoissa"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "”h” on merkityksetön awk-muodoissa; ohitetaan"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "kohtalokas: ”h” ei ole sallittu POSIX awk -muodoissa"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: arvo %g on lukualueen ulkopuolella ”%%%c”-muodolle"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "ohitetaan tuntematon muotoargumenttimerkki ”%c”: ei muunnettu argumenttia"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr "kohtalokas: ei kylliksi argumentteja muotomerkkijonon tyydyttämiseksi"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "^ tällainen loppui kesken"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: muotoargumentilla ei ole ohjauskirjainta"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "muotomerkkijonoon toimitettu liian monta argumenttia"
 
-#: builtin.c:1610
-#, fuzzy
+#: builtin.c:1634
 msgid "sprintf: no arguments"
-msgstr "printf: ei argumentteja"
+msgstr "sprintf: ei argumentteja"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: ei argumentteja"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: pituus %g ei ole >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: pituus %g ei ole >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: typistetään pituus %g, joka ei ole kokonaisluku"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr ""
 "substr: pituus %g liian suuri merkkijononindeksointiin, typistetään arvoon %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: aloitusindeksi %g on virheellinen, käytetään 1:tä"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: typistetään aloitusindeksi %g, joka ei ole kokonaisluku"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: lähdemerkkijono on nollapituinen"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: aloitusindeksi %g on merkkijonon lopun jälkeen"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -751,192 +758,189 @@ msgstr ""
 "substr: pituus %g alkuindeksissä %g ylittää ensimmäisen argumentin pituuden "
 "(%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 "strftime: muotoarvolla kohteessa PROCINFO[\"strftime\"] on numerotyyppi"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: toinen vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr ""
 "strftime: toinen argumentti on pienempi kuin 0 tai liian suuri time_t-"
 "rakenteeseen"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: ensimmäinen vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: vastaanotettu tyhjä muotomerkkijono"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: vähintään yksi arvoista on oletuslukualueen ulkopuolella"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
-msgstr "”system”-funktio ei ole sallittu hiekkalaatikkotilassa"
+msgstr "’system’-funktio ei ole sallittu hiekkalaatikkotilassa"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "viite alustamattomaan kenttään ”$%d”"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: vastaanotettu argumentti ei ole merkkijono"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: ensimmäinen vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: toinen vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: kolmas argumentti ei ole taulukko"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: 0-arvoinen kolmas argumentti käsitellään kuin 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: ensimmäinen vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: toinen vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:3011
-#, fuzzy, c-format
+#: builtin.c:3038
+#, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
-msgstr "lshift(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "lshift(%f, %f): negatiiviset arvot antavat outoja tuloksia"
 
-#: builtin.c:3013
-#, fuzzy, c-format
+#: builtin.c:3040
+#, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
-msgstr "lshift(%lf, %lf): jaosarvot typistetään"
+msgstr "lshift(%f, %f): jaosarvot typistetään"
 
-#: builtin.c:3015
-#, fuzzy, c-format
+#: builtin.c:3042
+#, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
-msgstr "lshift(%lf, %lf): liian suuri siirrosarvo antaa outoja tuloksia"
+msgstr "lshift(%f, %f): liian suuri siirrosarvo antaa outoja tuloksia"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: ensimmäinen vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: toinen vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:3048
-#, fuzzy, c-format
+#: builtin.c:3075
+#, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
-msgstr "rshift(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "rshift(%f, %f): negatiiviset arvot antavat outoja tuloksia"
 
-#: builtin.c:3050
-#, fuzzy, c-format
+#: builtin.c:3077
+#, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
-msgstr "rshift(%lf, %lf): jaosarvot typistetään"
+msgstr "rshift(%f, %f): jaosarvot typistetään"
 
-#: builtin.c:3052
-#, fuzzy, c-format
+#: builtin.c:3079
+#, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
-msgstr "rshift(%lf, %lf): liian suuri siirrosarvo antaa outoja tuloksia"
+msgstr "rshift(%f, %f): liian suuri siirrosarvo antaa outoja tuloksia"
 
-#: builtin.c:3077 mpfr.c:968
-#, fuzzy
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "and: kutsuttu vähemmällä kuin kahdella argumentilla"
 
-#: builtin.c:3082
-#, fuzzy, c-format
+#: builtin.c:3109
+#, c-format
 msgid "and: argument %d is non-numeric"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "and: argumentti %d ei ole numeeraaliargumentti"
 
-#: builtin.c:3086
-#, fuzzy, c-format
+#: builtin.c:3113
+#, c-format
 msgid "and: argument %d negative value %g will give strange results"
-msgstr "and(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "and: argumentin %d negatiivinen arvo %g antaa outoja tuloksia"
 
-#: builtin.c:3109 mpfr.c:1000
-#, fuzzy
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "or: kutsuttu vähemmällä kuin kahdella argumentilla"
 
-#: builtin.c:3114
-#, fuzzy, c-format
+#: builtin.c:3141
+#, c-format
 msgid "or: argument %d is non-numeric"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "or: argumentti %d ei ole numeraaliargumentti"
 
-#: builtin.c:3118
-#, fuzzy, c-format
+#: builtin.c:3145
+#, c-format
 msgid "or: argument %d negative value %g will give strange results"
-msgstr "compl(%lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "or: argumentin %d negatiivinen arvo %g antaa outoja tuloksia"
 
-#: builtin.c:3140 mpfr.c:1031
-#, fuzzy
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "xor: kutsuttu vähemmällä kuin kahdella argumentilla"
 
-#: builtin.c:3146
-#, fuzzy, c-format
+#: builtin.c:3173
+#, c-format
 msgid "xor: argument %d is non-numeric"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "xor: argumentti %d ei ole numeraaliargumentti"
 
-#: builtin.c:3150
-#, fuzzy, c-format
+#: builtin.c:3177
+#, c-format
 msgid "xor: argument %d negative value %g will give strange results"
-msgstr "xor(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "xor: argumentin %d negatiivinen arvo %g antaa outoja tuloksia"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: vastaanotettu argumentti ei ole numeerinen"
 
-#: builtin.c:3181
-#, fuzzy, c-format
+#: builtin.c:3208
+#, c-format
 msgid "compl(%f): negative value will give strange results"
-msgstr "compl(%lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "compl(%f): negatiivinen arvo antaa outoja tuloksia"
 
-#: builtin.c:3183
-#, fuzzy, c-format
+#: builtin.c:3210
+#, c-format
 msgid "compl(%f): fractional value will be truncated"
-msgstr "compl(%lf): jaosarvo typistetään"
+msgstr "compl(%f): jaosarvo typistetään"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: ”%s” ei ole kelvollinen paikallinen kategoria"
@@ -944,873 +948,916 @@ msgstr "dcgettext: ”%s” ei ole kelvollinen paikallinen kategoria"
 #: command.y:225
 #, c-format
 msgid "Type (g)awk statement(s). End with the command \"end\"\n"
-msgstr ""
+msgstr "Kirjoita (g)awk-lause(et). Lopeta komennolla \"end\"\n"
 
 #: command.y:289
-#, fuzzy, c-format
+#, c-format
 msgid "invalid frame number: %d"
-msgstr "Virheellinen lukualueen loppu"
+msgstr "virheellinen kehysnumero: %d"
 
 #: command.y:295
-#, fuzzy, c-format
+#, c-format
 msgid "info: invalid option - \"%s\""
-msgstr "%s: virheellinen valitsin -- ’%c’\n"
+msgstr "info: virheellinen valitsin -- ”%s”"
 
 #: command.y:321
 #, c-format
 msgid "source \"%s\": already sourced."
-msgstr ""
+msgstr "source ”%s”: on jo merkitty lähteeksi."
 
 #: command.y:326
 #, c-format
 msgid "save \"%s\": command not permitted."
-msgstr ""
+msgstr "save ”%s”: komento ei ole sallittu."
 
 #: command.y:339
 msgid "Can't use command `commands' for breakpoint/watchpoint commands"
 msgstr ""
+"Komennon ”commands” käyttö breakpoint/watchpoint-komentoja varten epäonnistui"
 
 #: command.y:341
 msgid "no breakpoint/watchpoint has been set yet"
-msgstr ""
+msgstr "yhtään breakpoint/watchpoint -kohdetta ei ole vielä asetettu"
 
 #: command.y:343
 msgid "invalid breakpoint/watchpoint number"
-msgstr ""
+msgstr "virheellinen breakpoint/watchpoint-numero"
 
 #: command.y:348
 #, c-format
 msgid "Type commands for when %s %d is hit, one per line.\n"
-msgstr ""
+msgstr "Kirjoita komennot, kun %s %d osui, yksi per rivi.\n"
 
 #: command.y:350
 #, c-format
 msgid "End with the command \"end\"\n"
-msgstr ""
+msgstr "Lopeta komennolla ”end”\n"
 
 #: command.y:357
 msgid "`end' valid only in command `commands' or `eval'"
-msgstr ""
+msgstr "”end” on kelvollinen vain komennoissa ”commands” tai ”eval”"
 
 #: command.y:367
 msgid "`silent' valid only in command `commands'"
-msgstr ""
+msgstr "”silent” on kelvollinen vain komennossa ”commands”"
 
 #: command.y:373
-#, fuzzy, c-format
+#, c-format
 msgid "trace: invalid option - \"%s\""
-msgstr "%s: virheellinen valitsin -- ’%c’\n"
+msgstr "trace: virheellinen valitsin -- ”%s”"
 
 #: command.y:387
 msgid "condition: invalid breakpoint/watchpoint number"
-msgstr ""
+msgstr "condition: virheellinen breakpoint/watchpoint-numero"
 
 #: command.y:449
-#, fuzzy
 msgid "argument not a string"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "argumentti ei ole merkkijono"
 
 #: command.y:459 command.y:464
 #, c-format
 msgid "option: invalid parameter - \"%s\""
-msgstr ""
+msgstr "option: virheellinen parametri - ”%s”"
 
 #: command.y:474
 #, c-format
 msgid "no such function - \"%s\""
-msgstr ""
+msgstr "tuntematon funktio - ”%s”"
 
 #: command.y:531
-#, fuzzy, c-format
+#, c-format
 msgid "enable: invalid option - \"%s\""
-msgstr "%s: virheellinen valitsin -- ’%c’\n"
+msgstr "enable: virheellinen valitsin -- ”%s”"
 
 #: command.y:597
-#, fuzzy, c-format
+#, c-format
 msgid "invalid range specification: %d - %d"
-msgstr "Virheellinen lukualueen loppu"
+msgstr "virheellinen lukualuemäärittely: %d - %d"
 
 #: command.y:659
-#, fuzzy
 msgid "non-numeric value for field number"
-msgstr "tuntematon arvo kenttämääritteelle: %d\n"
+msgstr "ei-numeerinen arvo kenttänumerolle"
 
 #: command.y:680 command.y:687
 msgid "non-numeric value found, numeric expected"
-msgstr ""
+msgstr "löytyi ei-numeerinen arvo, odotettiin numeraalia"
 
 #: command.y:712 command.y:718
 msgid "non-zero integer value"
-msgstr ""
+msgstr "nollasta poikkeava kokonaislukuarvo"
 
 #: command.y:817
 msgid ""
 "backtrace [N] - print trace of all or N innermost (outermost if N < 0) "
 "frames."
 msgstr ""
+"backtrace [N] - tulosta kaikkien tai N:n sisimmäisen (ulommaisin, jos N < 0) "
+"kehyksen jäljet."
 
 #: command.y:819
 msgid ""
 "break [[filename:]N|function] - set breakpoint at the specified location."
 msgstr ""
+"break [[filename:]N|function] - aseta breakpoint määriteltyyn sijaintiin."
 
 #: command.y:821
 msgid "clear [[filename:]N|function] - delete breakpoints previously set."
 msgstr ""
+"clear [[filename:]N|function] - poista aiemmin asetetut breakpoint-kohdat."
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
+"commands [num] - aloittaa komentojen luettelon, joka suoritetaan "
+"keskeytyskohta(watchpoint)osumassa."
 
 #: command.y:825
 msgid "condition num [expr] - set or clear breakpoint or watchpoint condition."
 msgstr ""
+"condition num [expr] - aseta tai nollaa keskeytyskohta- tai vahtikohtaehdot."
 
 #: command.y:827
 msgid "continue [COUNT] - continue program being debugged."
-msgstr ""
+msgstr "continue [COUNT] - continue program being debugged."
 
 #: command.y:829
 msgid "delete [breakpoints] [range] - delete specified breakpoints."
 msgstr ""
+"delete [keskeytyskohdat] [lukualue] - poista määritellyt keskeytyskohdat."
 
 #: command.y:831
 msgid "disable [breakpoints] [range] - disable specified breakpoints."
 msgstr ""
+"disable [keskeytyskohdat] [lukualue] - ota pois käytöstä määritellyt "
+"keskeytyskohdat."
 
 #: command.y:833
 msgid "display [var] - print value of variable each time the program stops."
 msgstr ""
+"display [muuttuja] - tulosta muuttujan arvo joka kerta kun ohjelma pysähtyy."
 
 #: command.y:835
 msgid "down [N] - move N frames down the stack."
-msgstr ""
+msgstr "down [N] - siirrä N kehystä alaspäin pinossa."
 
 #: command.y:837
 msgid "dump [filename] - dump instructions to file or stdout."
-msgstr ""
+msgstr "dump [tiedostonimi] - vedosta käskyt tiedostoon tai vakiotulosteeseen."
 
 #: command.y:839
 msgid "enable [once|del] [breakpoints] [range] - enable specified breakpoints."
 msgstr ""
+"enable [once|del] [keskeytyskohdat] [lukualue] - ota käyttöön määritellyt "
+"keskeytyskohdat."
 
 #: command.y:841
 msgid "end - end a list of commands or awk statements."
-msgstr ""
+msgstr "end - lopeta komentojen tai awk-lauseiden luottelo."
 
 #: command.y:843
 msgid "eval stmt|[p1, p2, ...] - evaluate awk statement(s)."
-msgstr ""
+msgstr "eval stmt|[p1, p2, ...] - evaloi awk-lauseet."
 
 #: command.y:845
 msgid "finish - execute until selected stack frame returns."
-msgstr ""
+msgstr "finish - suorita kunnes palautetaan valittu pinokehys."
 
 #: command.y:847
 msgid "frame [N] - select and print stack frame number N."
-msgstr ""
+msgstr "frame [N] - valitse ja tulosta pinokehys numero N."
 
 #: command.y:849
 msgid "help [command] - print list of commands or explanation of command."
-msgstr ""
+msgstr "help [komento] - tulosta komentoluettelo tai komennon selitys."
 
 #: command.y:851
 msgid "ignore N COUNT - set ignore-count of breakpoint number N to COUNT."
 msgstr ""
+"ignore N COUNT - aseta keskeytyskohdan ignore-count numero N arvoon COUNT."
 
 #: command.y:853
 msgid ""
 "info topic - source|sources|variables|functions|break|frame|args|locals|"
 "display|watch."
 msgstr ""
+"info aihe - source|sources|variables|functions|break|frame|args|locals|"
+"display|watch."
 
 #: command.y:855
 msgid "list [-|+|[filename:]lineno|function|range] - list specified line(s)."
 msgstr ""
+"list [-|+|[tiedostonimi:]rivinumero|funktio|lukualue] - luettele määritellyt "
+"rivit."
 
 #: command.y:857
 msgid "next [COUNT] - step program, proceeding through subroutine calls."
-msgstr ""
+msgstr "next [COUNT] - askella ohjelmaa, etene alirutiinikutsujen kautta."
 
 #: command.y:859
 msgid ""
 "nexti [COUNT] - step one instruction, but proceed through subroutine calls."
 msgstr ""
+"nexti [COUNT] - askella yksi käsky, mutta etene alirutiinikutsujen kautta."
 
 #: command.y:861
 msgid "option [name[=value]] - set or display debugger option(s)."
-msgstr ""
+msgstr "option [nimi[=arvo]] - aseta tai näytä vianjäljittäjävalitsimet."
 
 #: command.y:863
 msgid "print var [var] - print value of a variable or array."
-msgstr ""
+msgstr "print var [muuttuja] - tulosta muutujan tai taulukon arvo."
 
 #: command.y:865
 msgid "printf format, [arg], ... - formatted output."
-msgstr ""
+msgstr "printf muoto, [argumentti], ... - muotoiltu tuloste."
 
 #: command.y:867
 msgid "quit - exit debugger."
-msgstr ""
+msgstr "quit - poistu vianjäljittäjästä."
 
 #: command.y:869
 msgid "return [value] - make selected stack frame return to its caller."
-msgstr ""
+msgstr "return [arvo] - tekee valitun pinokehyksen paluun sen kutsujalle."
 
 #: command.y:871
 msgid "run - start or restart executing program."
-msgstr ""
+msgstr "run - käynnistä tai uudelleenkäynnistä ohjelman suoritus."
 
 #: command.y:874
 msgid "save filename - save commands from the session to file."
-msgstr ""
+msgstr "save tiedostonimi - tallenna komennot istunnosta tiedostoon."
 
 #: command.y:877
 msgid "set var = value - assign value to a scalar variable."
-msgstr ""
+msgstr "set var = arvo - liitä arvo skalaarimuuttujaan."
 
 #: command.y:879
 msgid ""
 "silent - suspends usual message when stopped at a breakpoint/watchpoint."
 msgstr ""
+"silent - pysäyttää tavallisen viestin kun pysähdytään katkaisukohdassa/"
+"vahtipisteessä."
 
 #: command.y:881
 msgid "source file - execute commands from file."
-msgstr ""
+msgstr "source file - suorita komennot tiedostosta."
 
 #: command.y:883
 msgid "step [COUNT] - step program until it reaches a different source line."
 msgstr ""
+"step [COUNT] - askella ohjelmaa, kunnes se saavuttaa eri lähdekoodirivin."
 
 #: command.y:885
 msgid "stepi [COUNT] - step one instruction exactly."
-msgstr ""
+msgstr "stepi [COUNT] - askella tarkalleen yksi käsky."
 
 #: command.y:887
 msgid "tbreak [[filename:]N|function] - set a temporary breakpoint."
-msgstr ""
+msgstr "tbreak [[tiedostonimi:]N|funktio] - aseta tilapäinen keskeytyskohta."
 
 #: command.y:889
 msgid "trace on|off - print instruction before executing."
-msgstr ""
+msgstr "trace on|off - tulosta käsky ennen suoritusta."
 
 #: command.y:891
 msgid "undisplay [N] - remove variable(s) from automatic display list."
-msgstr ""
+msgstr "undisplay [N] - poista muuttuja(t) automaattisesta näyttöluettelosta."
 
 #: command.y:893
 msgid ""
 "until [[filename:]N|function] - execute until program reaches a different "
 "line or line N within current frame."
 msgstr ""
+"until [[tiedostonimi:]N|funktio] - suorita kunnes ohjelma tavoittaa eri "
+"rivin tai rivin N nykyisen kehyksen sisällä."
 
 #: command.y:895
 msgid "unwatch [N] - remove variable(s) from watch list."
-msgstr ""
+msgstr "unwatch [N] - poista muuttuja(t) vahtiluettelosta."
 
 #: command.y:897
 msgid "up [N] - move N frames up the stack."
-msgstr ""
+msgstr "up [N] - siirrä N kehystä ylöspäin pinossa."
 
 #: command.y:899
 msgid "watch var - set a watchpoint for a variable."
-msgstr ""
+msgstr "watch muuttuja - aseta vahtikohta muuttujalle."
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
-msgstr "virhe:"
+msgstr "virhe: "
 
 #: command.y:1051
-#, fuzzy, c-format
+#, c-format
 msgid "can't read command (%s)\n"
-msgstr "ei voi uudelleenohjata putkesta ”%s” (%s)"
+msgstr "komennon (%s) lukeminen epäonnistui\n"
 
 #: command.y:1065
-#, fuzzy, c-format
+#, c-format
 msgid "can't read command (%s)"
-msgstr "ei voi uudelleenohjata putkesta ”%s” (%s)"
+msgstr "komennon (%s) lukeminen epäonnistui"
 
 #: command.y:1116
-#, fuzzy
 msgid "invalid character in command"
-msgstr "Virheellinen merkkiluokkanimi"
+msgstr "virheellinen merkki komennossa"
 
 #: command.y:1152
 #, c-format
 msgid "unknown command - \"%.*s\", try help"
-msgstr ""
+msgstr "tuntematon komento - \"%.*s\", kokeile käskyä help"
 
 #: command.y:1222
 #, c-format
 msgid "%s"
-msgstr ""
+msgstr "%s"
 
 #: command.y:1284
-#, fuzzy
 msgid "invalid character"
-msgstr "Virheellinen vertailumerkki"
+msgstr "virheellinen merkki"
 
 #: command.y:1455
 #, c-format
 msgid "undefined command: %s\n"
-msgstr ""
+msgstr "määrittelemätön komento: %s\n"
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
-msgstr ""
+msgstr "aseta tai näytä historiatiedostossa säilytettävien rivien lukumäärä."
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
-msgstr ""
+msgstr "aseta tai näytä luettelokomentoikkunan koko."
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
-msgstr ""
+msgstr "aseta tai näytä gawk-tulostetiedosto."
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
-msgstr ""
+msgstr "aseta tai näytä vianjäljittäjäkehote."
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
+"aseta, poista asetus tai näytä komentohistoriatallennus (value=on|off)."
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
-msgstr ""
+msgstr "aseta, poista asetus tai näytä valitsintallennus (value=on|off)."
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
-msgstr ""
+msgstr "aseta, poista asetus tai näytä käskyjäljitys (value=on|off)."
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
-msgstr ""
+msgstr "ohjelma ei ole käynnissä."
 
-#: debug.c:442 debug.c:597
-#, fuzzy, c-format
+#: debug.c:448 debug.c:606
+#, c-format
 msgid "can't read source file `%s' (%s)"
-msgstr "ei voi lukea lähdetiedostoa ”%s” (%s)"
+msgstr "lähdetiedoston ”%s” (%s) lukeminen epäonnistui"
 
-#: debug.c:447
-#, fuzzy, c-format
+#: debug.c:453
+#, c-format
 msgid "source file `%s' is empty.\n"
-msgstr "lähdetiedosto ”%s” on tyhjä"
+msgstr "lähdetiedosto ”%s” on tyhjä.\n"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
-msgstr ""
+msgstr "ei nykyistä lähdekooditiedostoa."
 
-#: debug.c:499
-#, fuzzy, c-format
+#: debug.c:505
+#, c-format
 msgid "cannot find source file named `%s' (%s)"
-msgstr "ei voi lukea lähdetiedostoa ”%s” (%s)"
+msgstr "lähdetiedostoa nimeltä ”%s” (%s) ei kyetä lukemaan"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
+"VAROITUS: lähdekooditiedostoa ”%s” on muokattu ohjelman kääntämisen "
+"jälkeen.\n"
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
-msgstr ""
+msgstr "rivinumero %d lukualueen ulkopuolella; kohteessa ”%s” on %d riviä"
 
-#: debug.c:602
-#, fuzzy, c-format
+#: debug.c:611
+#, c-format
 msgid "unexpected eof while reading file `%s', line %d"
-msgstr "odottamaton rivinvaihto tai merkkijonon loppu"
+msgstr ""
+"odottamaton eof-tiedostonloppumerkki luettaessa tiedostoa ”%s”, rivi %d"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr ""
+"lähdekooditiedostoa ”%s” on muokattu ohjelman suorituksen aloituksen jälkeen"
 
-#: debug.c:723
-#, fuzzy, c-format
+#: debug.c:732
+#, c-format
 msgid "Current source file: %s\n"
-msgstr "on jo sisällytetty lähdetiedostoon ”%s”"
+msgstr "Nykyinen lähdetiedosto: %s\n"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
-msgstr ""
+msgstr "Rivien lukumäärä: %d\n"
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
-msgstr ""
+msgstr "Lähdetiedosto (riviä): %s (%d)\n"
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
+"Numero  Disp  Käytössä  Sijainti\n"
+"\n"
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
-msgstr ""
+msgstr "\tosumien lukumäärä = %ld\n"
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
-msgstr ""
+msgstr "\tohita seuraavat %ld osumaa\n"
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
-msgstr ""
+msgstr "\tpysähtymisehto: %s\n"
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
-msgstr ""
+msgstr "\tkomennot:\n"
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
-msgstr ""
+msgstr "Nykyinen kehys: "
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
-msgstr ""
+msgstr "Kehyksen kutsuma: "
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
-msgstr ""
+msgstr "Kehyksen kutsuja: "
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
-msgstr ""
+msgstr "Funktiossa main() ei ole mitään.\n"
 
-#: debug.c:839
-#, fuzzy
+#: debug.c:848
 msgid "No arguments.\n"
-msgstr "printf: ei argumentteja"
+msgstr "Ei argumentteja.\n"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
-msgstr ""
+msgstr "Ei paikallisia muuttujia.\n"
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
+"Kaikki määritellyt muuttujat:\n"
+"\n"
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
+"Kaikki määritellyt funktiot.\n"
+"\n"
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
+"Automaattisesti näytettävät muuttujat:\n"
+"\n"
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
+"Vahtimuuttujia:\n"
+"\n"
 
-#: debug.c:1020
-#, fuzzy, c-format
+#: debug.c:1029
+#, c-format
 msgid "no symbol `%s' in current context\n"
-msgstr "”exit” ei voida kutsua nykyisessä asiayhteydessä"
+msgstr "symbolia ”%s” ei löydy nykyisestä asiayhteydestä\n"
 
-#: debug.c:1032 debug.c:1418
-#, fuzzy, c-format
+#: debug.c:1041 debug.c:1427
+#, c-format
 msgid "`%s' is not an array\n"
-msgstr "”%s” ei ole laillinen muuttujanimi"
+msgstr "”%s” ei ole taulukko\n"
 
-#: debug.c:1046
-#, fuzzy, c-format
+#: debug.c:1055
+#, c-format
 msgid "$%ld = uninitialized field\n"
-msgstr "viite alustamattomaan kenttään ”$%d”"
+msgstr "$%ld = alustamaton kenttä\n"
 
-#: debug.c:1067
-#, fuzzy, c-format
+#: debug.c:1076
+#, c-format
 msgid "array `%s' is empty\n"
-msgstr "data-tiedosto ”%s” on tyhjä"
+msgstr "taulukko ”%s” on tyhjä\n"
 
-#: debug.c:1110 debug.c:1162
-#, fuzzy, c-format
+#: debug.c:1119 debug.c:1171
+#, c-format
 msgid "[\"%s\"] not in array `%s'\n"
-msgstr "delete: indeksi ”%s” ei ole taulukossa ”%s”"
+msgstr "[”%s”] ei ole taulukossa ”%s”\n"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
-msgstr ""
+msgstr "”%s[\"%s\"]” ei ole taulukko\n"
 
-#: debug.c:1227 debug.c:4949
-#, fuzzy, c-format
+#: debug.c:1236 debug.c:4964
+#, c-format
 msgid "`%s' is not a scalar variable"
-msgstr "”%s” ei ole laillinen muuttujanimi"
+msgstr "”%s” ei ole skalaarimuuttuja"
 
-#: debug.c:1249 debug.c:4979
-#, fuzzy, c-format
+#: debug.c:1258 debug.c:4994
+#, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
-msgstr "yritettiin käyttää taulukkoa ”%s[\"%.*s\"]” skalaarikontekstissa"
+msgstr "yritettiin käyttää taulukkoa ”%s[\"%s\"]” skalaarikontekstissa"
 
-#: debug.c:1271 debug.c:4990
-#, fuzzy, c-format
+#: debug.c:1280 debug.c:5005
+#, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
-msgstr "yritettiin käyttää skalaaria ”%s[\"%.*s\"]” taulukkona"
+msgstr "yritettiin käyttää skalaaria ”%s[\"%s\"]” taulukkona"
 
-#: debug.c:1414
-#, fuzzy, c-format
+#: debug.c:1423
+#, c-format
 msgid "`%s' is a function"
-msgstr "”%s” on virheellinen funktionimenä"
+msgstr "”%s” on funktio"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
-msgstr ""
+msgstr "watchpoint %d ei ole ehdollinen\n"
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
-msgstr ""
+msgstr "Yksikään näyttörivi ei ole numeroitu %ld"
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
-msgstr ""
+msgstr "Yksikään vahtirivi ei ole numeroitu %ld"
 
-#: debug.c:1519
-#, fuzzy, c-format
+#: debug.c:1528
+#, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
-msgstr "delete: indeksi ”%s” ei ole taulukossa ”%s”"
+msgstr "%d: [”%s”] ei ole taulukossa ”%s”\n"
 
-#: debug.c:1758
-#, fuzzy
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr "yritettiin käyttää skalaariarvoa taulukkona"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
+"Watchpoint %d poistettiin, koska parametri on lukualueen ulkopuolella.\n"
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
-msgstr ""
+msgstr "Display %d poistettiin, koska parametri on lukualueen ulkopuolella.\n"
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
-msgstr ""
+msgstr " tiedostossa ”%s”, rivi %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
-msgstr ""
+msgstr " osoitteessa ”%s”:%d"
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
-msgstr ""
+msgstr "#%ld\tkohteessa "
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
-msgstr ""
+msgstr "Lisää pinokehyksiä seuraa ...\n"
 
-#: debug.c:2008
-#, fuzzy
+#: debug.c:2017
 msgid "invalid frame number"
-msgstr "Virheellinen lukualueen loppu"
+msgstr "virheellinen kehysnumero"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
+"Huomaa: keskeytyskohta %d (otettu käyttöön, ohita seuraavat %ld osumaa), "
+"asetettu myös osoitteessa %s:%d"
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
+"Huomaa: keskeytyskohta %d (otettu käyttöön), asetettu myös kohdassa %s:%d"
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
+"Huomaa: keskeytyskohta %d (otettu pois käytöstä, ohita seuraavat %ld "
+"osumaa), asetettu myös kohdassa %s:%d"
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
+"Huomaa: keskeytyskohta %d (otettu pois käytöstä), asetettu myös kohdassa %s:"
+"%d"
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
-msgstr ""
+msgstr "Keskeytyskohta %d asetettu tiedostossa ”%s”, rivi %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
-msgstr ""
+msgstr "Keskeytyskohdan asetaminen tiedostossa ”%s” epäonnistui\n"
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
-#, fuzzy, c-format
+#: debug.c:2369 debug.c:2492 debug.c:3350
+#, c-format
 msgid "line number %d in file `%s' out of range"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "rivinumero %d tiedostossa ”%s” on lukualueen ulkopuolella"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
-msgstr ""
+msgstr "Säännön löytäminen epäonnistui!!!\n"
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
-msgstr ""
+msgstr "Keskeytykohdan asettaminen kohdassa ”%s”:%d epäonnistui\n"
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
-msgstr ""
+msgstr "Keskeytyskohdan asettaminen funktiossa ”%s” epäonnistui\n"
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
-msgstr ""
+msgstr "keskeytyskohta %d asetettu tiedostossa ”%s”, rivi %d on ehdoton\n"
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
-msgstr ""
+msgstr "Poistettu keskeytyskohta %d"
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
-msgstr ""
+msgstr "Ei keskeytyskohtaa funktion ”%s” sisääntulossa\n"
 
-#: debug.c:2521
-#, fuzzy, c-format
+#: debug.c:2541
+#, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
-msgstr "virhe luettaessa syötetiedostoa ”%s”: %s"
+msgstr "Tiedostossa ”%s” ei ole keskeytyskohtaa, rivi #%d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
-msgstr ""
+msgstr "virheellinen keskeytyskohtanumero"
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
-msgstr ""
+msgstr "Poistetaanko kaikki keskeytyskohdata? (y tai n) "
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
-msgstr ""
+msgstr "k"
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
-msgstr ""
+msgstr "Keskeytyskohta %2$d:n seuraavat %1$ld risteystä ohitetaan.\n"
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
-msgstr ""
+msgstr "Pysähtyy seuraavalla kerralla kun keskeytyskohta %d saavutetaan.\n"
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
+"Vain ohjelmia, jotka tarjoavat valitsimen ”-f”, voidaan vikajäljittää.\n"
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
-msgstr ""
+msgstr "Vianjäljittäjän uudelleenkäynnistys epäonnistui"
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
-msgstr ""
+msgstr "Ohjelma on jo käynnissä. Käynnistetäänkö uudelleen alusta (y/n)? "
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
-msgstr ""
+msgstr "Ohjelma ei käynnistynyt uudelleen\n"
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
-msgstr ""
+msgstr "virhe: uudelleenkäynnistys epäonnistui, toiminto ei ole sallittu\n"
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
+"virhe (%s): uudelleenkäynnistys epäonnistui, loput komennot ohitetaan\n"
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
-msgstr ""
+msgstr "Käynnistetään ohjelma: \n"
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
-msgstr ""
+msgstr "Ohjelma päättyi %s päättymisarvolla: %d\n"
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
-msgstr ""
+msgstr "Ohjelma on käynnissä. Poistutaanko silti (y/n)? "
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
-msgstr ""
+msgstr "Ei pysäytetty yhdessäkään keskeytyskohdassa; argumentti ohitetaan.\n"
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
-msgstr ""
+msgstr "virheellinen keskeytyskohtanumero %d."
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
-msgstr ""
+msgstr "Ohittaa seuraavat %ld keskeytyskohdan %d ylitystä.\n"
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
+"’finish’ ei ole merkityksellinen ulommaisen kehyksen main()-funktiossa\n"
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
-msgstr ""
+msgstr "Suorita kunnes paluu kohteesta "
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
+"’return’ ei ole merkityksellinen ulommaisen kehyksen main()-funktiossa\n"
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
-msgstr ""
+msgstr "Määritellyn sijainnin löytyminen funktiossa ”%s” epäonnistui\n"
 
-#: debug.c:3357
-#, fuzzy, c-format
+#: debug.c:3377
+#, c-format
 msgid "invalid source line %d in file `%s'"
-msgstr "on jo sisällytetty lähdetiedostoon ”%s”"
+msgstr "virheellinen lähdekoodirivi %d tiedostossa ”%s”"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
-msgstr ""
+msgstr "Määritellyn sijainnin %d löytyminen tiedostossa ”%s” epäonnistui\n"
 
-#: debug.c:3404
-#, fuzzy, c-format
+#: debug.c:3424
+#, c-format
 msgid "element not in array\n"
-msgstr "delete: indeksi ”%s” ei ole taulukossa ”%s”"
+msgstr "elementti ei ole taulukossa\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
-msgstr ""
+msgstr "tyypitön muuttuja\n"
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
-msgstr ""
+msgstr "Pysäytetään kohdassa %s ...\n"
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
-msgstr ""
+msgstr "’finish’ ei ole merkityksellinen ei-paikallisessa hypyssä ’%s’\n"
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
-msgstr ""
+msgstr "’until’ ei ole merkityksellinen ei-paikallisessa hypyssä ’%s’\n"
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
-msgstr ""
+msgstr "\t------Jatka painamalla [Enter] tai poistu painamalla q [Enter]------"
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
-msgstr ""
+msgstr "q"
 
-#: debug.c:4986
-#, fuzzy, c-format
+#: debug.c:5001
+#, c-format
 msgid "[\"%s\"] not in array `%s'"
-msgstr "delete: indeksi ”%s” ei ole taulukossa ”%s”"
+msgstr "[”%s”] ei ole taulukossa ”%s”"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
-msgstr ""
+msgstr "lähetetään tuloste vakiotulosteeseen\n"
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
-msgstr ""
+msgstr "virheellinen numero"
 
-#: debug.c:5366
-#, fuzzy, c-format
+#: debug.c:5381
+#, c-format
 msgid "`%s' not allowed in current context; statement ignored"
-msgstr "”exit” ei voida kutsua nykyisessä asiayhteydessä"
+msgstr "”%s” ei ole sallittu nykyisessä asiayhteydessä; lause ohitetaan"
 
-#: debug.c:5374
-#, fuzzy
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
-msgstr "”exit” ei voida kutsua nykyisessä asiayhteydessä"
+msgstr "”return” ei ole sallittu nykyisessä asiayhteydessä; lause ohitetaan"
 
-#: debug.c:5575
-#, fuzzy, c-format
+#: debug.c:5590
+#, c-format
 msgid "No symbol `%s' in current context"
-msgstr "yritettiin käyttää taulukkoa ”%s” skalaarikontekstissa"
+msgstr "Symbolia ”%s” ei ole nykyisesssä asiayhteydessä"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
-msgstr ""
+msgstr "pariton ["
 
-#: dfa.c:1052
-#, fuzzy
+#: dfa.c:1174
 msgid "invalid character class"
-msgstr "Virheellinen merkkiluokkanimi"
+msgstr "virheellinen merkkiluokka"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
-msgstr ""
+msgstr "merkkiluokkasyntaksi on [[:space:]], ei [:space:]"
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
-msgstr ""
+msgstr "päättymätön \\-koodinvaihtomerkki"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Virheellinen \\{\\}-sisältö"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Säännöllinen lauseke on liian iso"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
-msgstr ""
+msgstr "pariton ("
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
-msgstr ""
+msgstr "syntaksi ei ole määritelty"
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
-msgstr ""
+msgstr "pariton )"
 
 #: eval.c:394
 #, c-format
@@ -1827,11 +1874,11 @@ msgstr "tuntematon käskykoodi %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "käskykoodi %s ei ole operaattori tai avainsana"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "puskurin ylivuoto funktiossa genflags2str"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1842,71 +1889,71 @@ msgstr ""
 "\t# Funktiokutsupino:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "”IGNORECASE” on gawk-laajennus"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "”BINMODE” on gawk-laajennus"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "BINMODE-arvo ”%s” on virheellinen, käsiteltiin arvona 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "väärä ”%sFMT”-määritys ”%s”"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "käännetään pois ”--lint”-valitsin ”LINT”-sijoituksen vuoksi"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "viite alustamattomaan argumenttiin ”%s”"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "viite alustamattomaan muuttujaan ”%s”"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "yritettiin kenttäviitettä arvosta, joka ei ole numeerinen"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "yritettiin kenttäviitettä null-merkkijonosta"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "yritettiin saantia kenttään %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "viite alustamattomaan kenttään ”$%ld”"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "funktio ”%s” kutsuttiin useammalla argumentilla kuin esiteltiin"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: odottamaton tyyppi ”%s”"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "jakoa nollalla yritettiin operaatiossa ”/=”"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "jakoa nollalla yritettiin operaatiossa ”%%=”"
@@ -1916,1201 +1963,1181 @@ msgid "extensions are not allowed in sandbox mode"
 msgstr "laajennuksia ei sallita hiekkalaatikkotilassa"
 
 #: ext.c:92
-#, fuzzy
 msgid "-l / @load are gawk extensions"
-msgstr "@include on gawk-laajennus"
+msgstr "-l / @load ovat gawk-laajennuksia"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
-msgstr ""
+msgstr "load_ext: vastaanotettiin NULL lib_name"
 
 #: ext.c:98
-#, fuzzy, c-format
+#, c-format
 msgid "load_ext: cannot open library `%s' (%s)\n"
-msgstr "tuhoisa: extension: ei voi avata solmua ”%s” (%s)\n"
+msgstr "load_ext: kirjaston ”%s” (%s) avaus epäonnistui\n"
 
 #: ext.c:104
-#, fuzzy, c-format
+#, c-format
 msgid ""
 "load_ext: library `%s': does not define `plugin_is_GPL_compatible' (%s)\n"
 msgstr ""
-"tuhoisa: extension: kirjasto ”%s”: ei määrittele "
-"”plugin_is_GPL_compatible” (%s)\n"
+"load_ext: kirjasto ”%s”: ei määrittele ”plugin_is_GPL_compatible” (%s)\n"
 
 #: ext.c:110
-#, fuzzy, c-format
+#, c-format
 msgid "load_ext: library `%s': cannot call function `%s' (%s)\n"
-msgstr "tuhoisa: extension: kirjasto ”%s”: ei voi kutsua funktiota ”%s” (%s)\n"
+msgstr "load_ext: kirjasto ”%s”: funktion ”%s” (%s) kutsu epäonnistui\n"
 
 #: ext.c:114
 #, c-format
 msgid "load_ext: library `%s' initialization routine `%s' failed\n"
-msgstr ""
+msgstr "load_ext: kirjaston ”%s” alustusrutiini ”%s” epäonnistui\n"
 
 #: ext.c:174
 msgid "`extension' is a gawk extension"
 msgstr "”extension” on gawk-laajennus"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "extension: vastaanotettiin NULL lib_name"
+
 #: ext.c:180
-#, fuzzy, c-format
+#, c-format
 msgid "extension: cannot open library `%s' (%s)"
-msgstr "tuhoisa: extension: ei voi avata solmua ”%s” (%s)\n"
+msgstr "extension: kirjaston ”%s” (%s) avaus epäonnistui"
 
 #: ext.c:186
-#, fuzzy, c-format
+#, c-format
 msgid ""
 "extension: library `%s': does not define `plugin_is_GPL_compatible' (%s)"
 msgstr ""
-"tuhoisa: extension: kirjasto ”%s”: ei määrittele "
-"”plugin_is_GPL_compatible” (%s)\n"
+"extension: kirjasto ”%s”: ei määrittele ”plugin_is_GPL_compatible” (%s)"
 
 #: ext.c:190
-#, fuzzy, c-format
+#, c-format
 msgid "extension: library `%s': cannot call function `%s' (%s)"
-msgstr "tuhoisa: extension: kirjasto ”%s”: ei voi kutsua funktiota ”%s” (%s)\n"
+msgstr "extension: kirjasto ”%s”: funktion ”%s” (%s) kutsu epäonnistui"
 
 #: ext.c:221
-#, fuzzy
 msgid "make_builtin: missing function name"
-msgstr "extension: puuttuva funktionimi"
+msgstr "make_builtin: puuttuva funktionimi"
 
-#: ext.c:238
-#, fuzzy, c-format
+#: ext.c:236
+#, c-format
 msgid "make_builtin: can't redefine function `%s'"
-msgstr "extension: ei voi määritellä uudelleen funktiota ”%s”"
+msgstr "make_builtin: funktion ”%s” uudelleenmäärittely epäonnistui"
 
-#: ext.c:242
-#, fuzzy, c-format
+#: ext.c:240
+#, c-format
 msgid "make_builtin: function `%s' already defined"
-msgstr "extension: funktio ”%s” on jo määritelty"
+msgstr "make_builtin: funktio ”%s” on jo määritelty"
 
-#: ext.c:246
-#, fuzzy, c-format
+#: ext.c:244
+#, c-format
 msgid "make_builtin: function name `%s' previously defined"
-msgstr "extension: funktionimi ”%s” on määritelty jo aiemmin"
+msgstr "make_builtin: funktionimi ”%s” on määritelty jo aiemmin"
 
-#: ext.c:248
-#, fuzzy, c-format
+#: ext.c:246
+#, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
-"extension: ei voi käyttää gawk-ohjelman sisäistä muuttujanimeä ”%s” "
-"funktionimenä"
+"make_builtin: gawk-ohjelman sisäisen muuttujanimen ”%s” käyttö funktionimenä "
+"epäonnistui"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: negatiivinen argumenttilukumäärä funktiolle ”%s”"
 
-#: ext.c:278
-#, fuzzy
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr "extension: puuttuva funktionimi"
 
-#: ext.c:283
-#, fuzzy, c-format
+#: ext.c:279 ext.c:283
+#, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: virheellinen merkki ”%c” funktionimessä ”%s”"
 
 #: ext.c:291
-#, fuzzy, c-format
+#, c-format
 msgid "extension: can't redefine function `%s'"
-msgstr "extension: ei voi määritellä uudelleen funktiota ”%s”"
+msgstr "extension: funktion ”%s” uudelleenmäärittely epäonnistui"
 
 #: ext.c:295
-#, fuzzy, c-format
+#, c-format
 msgid "extension: function `%s' already defined"
 msgstr "extension: funktio ”%s” on jo määritelty"
 
 #: ext.c:299
-#, fuzzy, c-format
+#, c-format
 msgid "extension: function name `%s' previously defined"
-msgstr "funktionimi ”%s” on jo aikaisemmin määritelty"
+msgstr "extension: funktionimi ”%s” on määritelty jo aiemmin"
 
 #: ext.c:301
-#, fuzzy, c-format
+#, c-format
 msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr ""
-"extension: ei voi käyttää gawk-ohjelman sisäistä muuttujanimeä ”%s” "
-"funktionimenä"
+"extension: gawk-ohjelman sisäisen muuttujanimen käyttö ”%s” funktionimenä "
+"epäonnistui"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "funktio ”%s” on määritelty ottamaan enemmän kuin %d argumenttia"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "function ”%s”: puuttuva argumentti #%d"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr "funktio ”%s”: argumentti #%d: yritettiin käyttää skalaaria taulukkona"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr "funktio ”%s”: argumentti #%d: yritettiin käyttää taulukkoa skalaarina"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
-msgstr ""
+msgstr "kirjaston dynaamista latausta ei tueta"
 
-#: extension/filefuncs.c:97
-#, fuzzy
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "chdir: kutsuttu argumenttien väärällä lukumäärällä, odotettiin 1"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
-msgstr ""
+msgstr "stat: symbolisen linkin ”%s” lukeminen epäonnistui"
 
-#: extension/filefuncs.c:376
-#, fuzzy
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "stat: kutsuttu argumenttien väärällä lukumäärällä"
 
-#: extension/filefuncs.c:383
-#, fuzzy
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
-msgstr "%s: on parametri\n"
+msgstr "stat: väärät parametrit"
 
-#: extension/filefuncs.c:437
-#, fuzzy, c-format
+#: extension/filefuncs.c:533
+#, c-format
 msgid "fts init: could not create variable %s"
-msgstr "index: toinen vastaanotettu argumentti ei ole merkkijono"
+msgstr "fts init: muuttujan %s luominen epäonnistui"
+
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "fts ei ole tuettu tässä järjestelmässä"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
-msgstr ""
+msgstr "fill_stat_element: taulukon luominen epäonnistui"
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
-msgstr ""
+msgstr "fill_stat_element: elementin asettaminen epäonnistui"
 
-#: extension/filefuncs.c:484
-#, fuzzy
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
-msgstr "index: toinen vastaanotettu argumentti ei ole merkkijono"
+msgstr "fill_path_element: elementin asettaminen epäonnistui"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
-msgstr ""
+msgstr "fill_error_element: elementin asettaminen epäonnistui"
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
-msgstr ""
+msgstr "fts-process: taulukon luominen epäonnistui"
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
-#, fuzzy
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
-msgstr "index: toinen vastaanotettu argumentti ei ole merkkijono"
+msgstr "fts-process: elementin asettaminen epäonnistui"
 
-#: extension/filefuncs.c:671
-#, fuzzy
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "fts: kutsuttu argumenttien väärällä lukumäärällä, odotettiin 3"
 
-#: extension/filefuncs.c:674
-#, fuzzy
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
-msgstr "%s: on parametri\n"
+msgstr "fts: väärä ensimmäinen parametri"
 
-#: extension/filefuncs.c:680
-#, fuzzy
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
-msgstr "%s: on parametri\n"
+msgstr "fts: väärä toinen parametri"
 
-#: extension/filefuncs.c:686
-#, fuzzy
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
-msgstr "%s: on parametri\n"
+msgstr "fts: väärä kolmas parametri"
 
-#: extension/filefuncs.c:693
-#, fuzzy
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
-msgstr "”%s” ei ole laillinen muuttujanimi"
+msgstr "fts: taulukon litistäminen epäonnistui\n"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
-msgstr ""
+msgstr "fts: ohitetaan petollinen FTS_NOSTAT-lippu. nyyh, nyyh, nyyh."
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
-msgstr ""
+msgstr "fts: clear_array() epäonnistui\n"
 
-#: extension/fnmatch.c:98
-#, fuzzy
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "fnmatch: kutsuttu vähemmällä kuin kolmella argumentilla"
 
-#: extension/fnmatch.c:101
-#, fuzzy
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "fnmatch: kutsuttu useammalla kuin kolmella argumentilla"
 
-#: extension/fnmatch.c:104
-#, fuzzy
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
-msgstr "strftime: ensimmäinen vastaanotettu argumentti ei ole merkkijono"
+msgstr "fnmatch: ensimmäistä argumenttia ei saatu"
 
-#: extension/fnmatch.c:109
-#, fuzzy
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
-msgstr "index: toinen vastaanotettu argumentti ei ole merkkijono"
+msgstr "fnmatch: toista argumenttia ei saatu"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
-msgstr ""
+msgstr "fnmatch: kolmatta argumenttia ei saatu"
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
-msgstr ""
+msgstr "fnmatch ei ole toteutettu tässä järjestelmässä\n"
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
-msgstr ""
+msgstr "fnmatch init: muuttujan FNM_NOMATCH lisääminen epäonnistui"
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
-msgstr ""
+msgstr "fnmatch init: taulukkoelementin %s asettaminen epäonnistui"
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
-msgstr ""
+msgstr "fnmatch init: FNM-taulukon lisääminen epäonnistui"
 
 #: extension/fork.c:81
-#, fuzzy
 msgid "fork: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "fork: kutsuttu liian monella argumentilla"
 
 #: extension/fork.c:94
 msgid "fork: PROCINFO is not an array!"
-msgstr ""
+msgstr "fork: PROCINFO ei ole taulukko!"
 
 #: extension/fork.c:118
-#, fuzzy
 msgid "waitpid: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "waitpid: kutsuttu liian monella argumentilla"
 
 #: extension/fork.c:126
-#, fuzzy
 msgid "wait: called with no arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "wait: kutsuttu ilman argumentteja"
 
 #: extension/fork.c:143
-#, fuzzy
 msgid "wait: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "wait: kutsuttu liian monella argumentilla"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
-msgstr ""
+msgstr "inplace_begin: kohdallaanmuokkaus on jo aktivoitu"
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr ""
+"inplace_begin: odotetaan 2 argumenttia, mutta kutsussa oli %d argumenttia"
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
+"inplace_begin: ensimmäisen argumentin noutaminen merkkijonotiedostonimenä "
+"epäonnistui"
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
+"inplace_begin: ottaen pois käytöstä virheellisen TIEDOSTONIMI ”%s” "
+"muokkauksen"
 
-#: extension/inplace.c:131
-#, fuzzy, c-format
+#: extension/inplace.c:151
+#, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
-msgstr "tuhoisa: extension: ei voi avata solmua ”%s” (%s)\n"
+msgstr "inplace_begin: stat ”%s” (%s) epäonnistui"
 
-#: extension/inplace.c:138
-#, fuzzy, c-format
+#: extension/inplace.c:158
+#, c-format
 msgid "inplace_begin: `%s' is not a regular file"
-msgstr "”%s” ei ole laillinen muuttujanimi"
+msgstr "inplace_begin: ”%s” ei ole tavallinen tiedosto"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
-msgstr ""
+msgstr "inplace_begin: mkstemp(”%s”) epäonnistui (%s)"
 
-#: extension/inplace.c:158
-#, fuzzy, c-format
+#: extension/inplace.c:178
+#, c-format
 msgid "inplace_begin: chmod failed (%s)"
-msgstr "%s: sulkeminen epäonnistui (%s)"
+msgstr "inplace_begin: chmod epäonnistui (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
-msgstr ""
+msgstr "inplace_begin: dup(stdout) epäonnistui (%s)"
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
-msgstr ""
+msgstr "inplace_begin: dup2(%d, stdout) epäonnistui (%s)"
 
-#: extension/inplace.c:171
-#, fuzzy, c-format
+#: extension/inplace.c:191
+#, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
-msgstr "%s: sulkeminen epäonnistui (%s)"
+msgstr "inplace_begin: close(%d) epäonnistui (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
+"inplace_end: ensimmäisen argumentin noutaminen merkkijonotiedostonimenä "
+"epäonnistui"
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
-msgstr ""
+msgstr "inplace_end: kohdallaanmuokkaus ei ole aktiivinen"
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
-msgstr ""
+msgstr "inplace_end: dup2(%d, stdout) epäonnistui (%s)"
 
-#: extension/inplace.c:206
-#, fuzzy, c-format
+#: extension/inplace.c:226
+#, c-format
 msgid "inplace_end: close(%d) failed (%s)"
-msgstr "%s: sulkeminen epäonnistui (%s)"
+msgstr "inplace_end: close(%d) epäonnistui (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
-msgstr ""
+msgstr "inplace_end: fsetpos(stdout) epäonnistui (%s)"
 
-#: extension/inplace.c:223
-#, fuzzy, c-format
+#: extension/inplace.c:243
+#, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
-msgstr "uudelleenohjauksen ”%s” putken tyhjennys epäonnistui (%s)."
+msgstr "inplace_end: link(”%s”, ”%s”) epäonnistui (%s)."
 
-#: extension/inplace.c:229
-#, fuzzy, c-format
+#: extension/inplace.c:253
+#, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
-msgstr "tiedostomäärittelijän %d (”%s”) sulkeminen epäonnistui (%s)"
+msgstr "inplace_end: rename(”%s”, ”%s”) epäonnistui (%s)"
 
 #: extension/ordchr.c:69
-#, fuzzy
 msgid "ord: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "ord: kutsuttu liian monella argumentilla"
 
 #: extension/ordchr.c:75
-#, fuzzy
 msgid "ord: called with no arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "ord: kutsuttu ilman argumentteja"
 
 #: extension/ordchr.c:77
-#, fuzzy
 msgid "ord: called with inappropriate argument(s)"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "ord: kutsuttu sopimattomalla argumentilla"
 
 #: extension/ordchr.c:99
-#, fuzzy
 msgid "chr: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "chr: kutsuttu liian monella argumentilla"
 
 #: extension/ordchr.c:109
-#, fuzzy
 msgid "chr: called with no arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "chr: kutsuttu ilman argumentteja"
 
 #: extension/ordchr.c:111
-#, fuzzy
 msgid "chr: called with inappropriate argument(s)"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "chr: kutsuttu sopimattomalla argumentilla"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
-msgstr ""
+msgstr "dir_take_control_of: opendir/fdopendir epäonnistui: %s"
 
-#: extension/readfile.c:84
-#, fuzzy
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "readfile: kutsuttu liian monella argumentilla"
 
-#: extension/readfile.c:118
-#, fuzzy
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "readfile: kutsuttu ilman argumentteja"
 
-#: extension/rwarray.c:120
-#, fuzzy
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "writea: kutsuttu liian monella argumentilla"
 
-#: extension/rwarray.c:127
-#, fuzzy, c-format
+#: extension/rwarray.c:131
+#, c-format
 msgid "do_writea: argument 0 is not a string\n"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "do_writea: argumentti 0 ei ole merkkijono\n"
 
-#: extension/rwarray.c:133
-#, fuzzy, c-format
+#: extension/rwarray.c:137
+#, c-format
 msgid "do_writea: argument 1 is not an array\n"
-msgstr "split: neljäs argumentti ei ole taulukko"
+msgstr "do_writea: argumentti 1 ei ole taulukko\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
-msgstr ""
+msgstr "write_array: taulukon litistäminen epäonnistui\n"
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
-msgstr ""
+msgstr "write_array: litistettyä taulukon vapauttaminen epäonnistui\n"
 
-#: extension/rwarray.c:276
-#, fuzzy
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "reada: kutsuttu liian monilla argumenteilla"
 
-#: extension/rwarray.c:283
-#, fuzzy, c-format
+#: extension/rwarray.c:287
+#, c-format
 msgid "do_reada: argument 0 is not a string\n"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "do_reada: argumentti 0 ei ole merkkijono\n"
 
-#: extension/rwarray.c:289
-#, fuzzy, c-format
+#: extension/rwarray.c:293
+#, c-format
 msgid "do_reada: argument 1 is not an array\n"
-msgstr "match: kolmas argumentti ei ole taulukko"
+msgstr "do_reada: argumentti 1 ei ole taulukko\n"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
-msgstr ""
+msgstr "do_reada: clear_array epäonnistui\n"
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
-msgstr ""
+msgstr "read_array: set_array_element epäonnistui\n"
 
-#: extension/time.c:81
-#, fuzzy
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
-msgstr "mktime: vastaanotettu argumentti ei ole merkkijono"
+msgstr "gettimeofday: ohitetaan argumentit"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
-msgstr ""
+msgstr "gettimeofday: ei ole tuettu tällä alustalla"
 
-#: extension/time.c:133
-#, fuzzy
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
-msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+msgstr "sleep: kutsuttu liian monella argumentilla"
 
-#: extension/time.c:136
-#, fuzzy
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
-msgstr "exp: vastaanotettu argumentti ei ole numeerinen"
+msgstr "sleep: puuttuu vaadittu numeerinen argumentti"
 
-#: extension/time.c:142
-#, fuzzy
+#: extension/time.c:174
 msgid "sleep: argument is negative"
-msgstr "exp: argumentti %g on lukualueen ulkopuolella"
+msgstr "sleep: argumentti on negatiivinen"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
-msgstr ""
+msgstr "sleep: ei ole tuettu tällä alustalla"
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF asetettu negatiiviseen arvoon"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: neljäs argumentti on gawk-laajennus"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: neljäs argumentti ei ole taulukko"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: toinen argumentti ei ole taulukko"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
-"split: ei voida käyttää samaa taulukkoa toiselle ja neljännelle argumentille"
+"split: saman taulukon käyttö toiselle ja neljännelle argumentille epäonnistui"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
-"split: ei voida käyttää toisen argumentin alitaulukkoa neljännelle "
-"argumentille"
+"split: toisen argumentin käyttö alitaulukkoa neljännelle argumentille "
+"epäonnistui"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
-"split: ei voida käyttää neljännen argumentin alitaulukkoa toiselle "
-"argumentille"
+"split: neljännen argumentin käyttö alitaulukkoa toiselle argumentille "
+"epäonnistui"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: null-merkkijono kolmantena argumenttina on gawk-laajennus"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: neljäs argumentti ei ole taulukko"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: toinen argumentti ei ole taulukko"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: kolmas argumentti ei ole taulukko"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
-"patsplit: ei voida käyttää samaa taulukkoa toiselle ja neljännelle "
-"argumentille"
+"patsplit: saman taulukon käyttö toiselle ja neljännelle argumentille "
+"epäonnistui"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
-"patsplit: ei voida käyttää toisen argumentin alitaulukkkoa neljännelle "
-"argumentille"
+"patsplit: toisen argumentin käyttö alitaulukkkoa neljännelle argumentille "
+"epäonnistui"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
-"patsplit: ei voida käyttää neljännen argumentin alitaulukkoa toiselle "
-"argumentille"
+"patsplit: neljännen argumentin käyttö alitaulukkoa toiselle argumentille "
+"epäonnistui"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "”FIELDWIDTHS” on gawk-laajennus"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "virheellinen FIELDWIDTHS-arvo, lähellä ”%s”"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "null-merkkijono ”FS”-kenttäerotinmuuttujalle on gawk-laajennus"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "vanha awk ei tue regexp-arvoja ”FS”-kenttäerotinmuuttujana"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "”FPAT” on gawk-laajennus"
 
 #: gawkapi.c:146
 msgid "awk_value_to_node: received null retval"
-msgstr ""
+msgstr "awk_value_to_node: vastaanotti null retval-paluuarvon"
 
 #: gawkapi.c:384
 msgid "node_to_awk_value: received null node"
-msgstr ""
+msgstr "node_to_awk_value: vastaaotti null-solmun"
 
 #: gawkapi.c:387
 msgid "node_to_awk_value: received null val"
-msgstr ""
+msgstr "node_to_awk_value: vastaanotti null-arvon"
 
-#: gawkapi.c:808
-#, fuzzy
+#: gawkapi.c:807
 msgid "remove_element: received null array"
-msgstr "length: vastaanotettu taulukkoargumentti"
+msgstr "remove_element: vastaanotettu null-taulukko"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
-msgstr ""
+msgstr "remove_element: vastaanotti null-alaindeksin"
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
-msgstr ""
+msgstr "api_flatten_array: indeksin %d muuntaminen epäonnistui\n"
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
-msgstr ""
+msgstr "api_flatten_array: arvon %d muuntaminen epäonnistui\n"
 
-#: getopt.c:603 getopt.c:632
-#, fuzzy, c-format
+#: getopt.c:604 getopt.c:633
+#, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
-msgstr "%s: valitsin ’%s’ ei ole yksiselitteinen\n"
+msgstr "%s: valitsin ’%s’ ei ole yksiselitteinen; mahdollisuudet:"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: valitsin ’--%s’ ei salli argumenttia\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: valitsin ’%c%s’ ei salli argumenttia\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: valitsin ’--%s’ vaatii argumentin\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: tunnistamaton valitsin ’--%s’\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: tunnistamaton valitsin ’%c%s’\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: virheellinen valitsin -- ’%c’\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: valitsin vaatii argumentin -- ’%c’\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: valitsin ’-W %s’ ei ole yksiselitteinen\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: valitsin ’-W %s’ ei salli argumenttia\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: valitsin ’-W %s’ vaatii argumentin\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "komentoriviargumentti ”%s” on hakemisto: ohitettiin"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
-msgstr "ei voi avata tiedostoa ”%s” lukemista varten (%s)"
+msgstr "tiedoston ”%s” avaaminen lukemista varten (%s) epäonnistui"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "tiedostomäärittelijän %d (”%s”) sulkeminen epäonnistui (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "edelleenohjaus ei ole sallittua hiekkalaatikkotilassa"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "lausekkeella ”%s”-uudellenohjauksessa on vain numeerinen arvo"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "lausekkeella ”%s”-uudelleenohjauksessa on null-merkkijonoarvo"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "tiedostonimi ”%s” ”%s”-uudelleenohjaukselle saattaa olla loogisen lausekkeen "
 "tulos"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "turha merkkien ”>” ja ”>>” sekoittaminen tiedostolle ”%.*s”"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
-msgstr "ei voi avata putkea ”%s” tulosteelle (%s)"
+msgstr "putken ”%s” avaaminen tulosteelle (%s) epäonnistui"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
-msgstr "ei voi avata putkea ”%s” syötteelle (%s)"
+msgstr "putken ”%s” avaaminen syötteelle (%s) epäonnistui"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
-msgstr "ei voi avata kaksisuuntaista putkea ”%s” syötteelle/tulosteelle (%s)"
+msgstr ""
+"kaksisuuntaisen putken ”%s” avaaminen syötteelle/tulosteelle (%s) epäonnistui"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
-msgstr "ei voi uudelleenohjata putkesta ”%s” (%s)"
+msgstr "uudelleenohjaus putkesta ”%s” (%s) epäonnistui"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
-msgstr "ei voi uudelleenohjata putkeen ”%s” (%s)"
+msgstr "uudelleenohjaus putkeen ”%s” (%s) epäonnistui"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "saavutettiin avoimien tiedostojen järjestelmäraja: aloitetaan "
 "tiedostomäärittelijöiden lomittaminen"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "uudelleenohjauksen ”%s” sulkeminen epäonnistui (%s)."
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "avoinna liian monta putkea tai syötetiedostoa"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: toisen argumentin on oltava ”to” tai ”from”"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: ”%.*s” ei ole avoin tiedosto, putki tai apuprosessi"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "suljettiin uudelleenohjaus, jota ei avattu koskaan"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: uudelleenohjaus ”%s” ei ole avattu operaattoreilla ”|&”, toinen "
 "argumentti ohitettu"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "virhetila (%d) putken ”%s” sulkemisessa (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "virhetila (%d) tiedoston ”%s” sulkemisessa (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "pistokkeen ”%s” eksplisiittistä sulkemista ei tarjota"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "apuprosessin ”%s” eksplisiittistä sulkemista ei tarjota"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "putken ”%s” eksplisiittistä sulkemista ei tarjota"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "tiedoston ”%s” eksplisiittistä sulkemista ei tarjota"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "virhe kirjoitettaessa vakiotulosteeseen (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "virhe kirjoitettaessa vakiovirheeseen (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "uudelleenohjauksen ”%s” putken tyhjennys epäonnistui (%s)."
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "putken apuprosessityhjennys uudelleenohjaukseen ”%s” epäonnistui (%s)."
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "uudelleenohjauksen ”%s” tiedostontyhjennys epäonnistui (%s)."
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "paikallinen portti %s virheellinen pistokkeessa ”/inet”"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "etäkone- ja porttitiedot (%s, %s) ovat virheellisiä"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr "ei (tunnettua) yhteyskäytäntöä tarjottu erikoistiedostonimessä ”%s”"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "erikoistiedostonimi ”%s” on vaillinainen"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "on tarjottava etäkoneen nimi pistokkeeseen ”/inet”"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "on tarjottava etäportti pistokkeeseen ”/inet”"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "TCP/IP-viestintää ei tueta"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
-msgstr "ei voitu avata laitetta ”%s”, tila ”%s”"
+msgstr "laitteen ”%s” avaus epäonnistui, tila ”%s”"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "”master pty”-sulkeminen epäonnistui (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "vakiotulosteen sulkeminen lapsiprosessissa epäonnistui (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "”slave pty”:n siirtäminen vakiotulosteeseen lapsiprosessissa epäonnistui "
 "(dup: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "vakiosyötteen sulkeminen lapsiprosessissa epäonnistui (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "”slave pty”:n siirtäminen vakiosyötteeseen lapsiprosessissa epäonnistui "
 "(dup: %s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "”slave pty”:n sulkeminen epäonnistui (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 "putken siirtäminen vakiotulosteeseen lapsiprosessissa epäonnistui (dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "putken siirtäminen vakiosyötteeseen lapsiprosessissa epäonnistui (dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "vakiotulosteen palauttaminen äitiprosessissa epäonnistui\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "vakiosyötön palauttaminen äitiprosessissa epäonnistui\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "putken sulkeminen epäonnistui (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "”|&” ei tueta"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
-msgstr "ei voi avata putkea ”%s” (%s)"
+msgstr "putken ”%s” (%s) avaaminen epäonnistui"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
-msgstr "ei voida luoda lapsiprosessia komennolle ”%s” (fork: %s)"
+msgstr "lapsiprosessin luominen komennolle ”%s” (fork: %s) epäonnistui"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
-msgstr ""
+msgstr "register_input_parser: vastaanotettiin NULL-osoitin"
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
+"syötejäsennin ”%s” on ristiriidassa aiemmin asennetun syötejäsentimen ”%s” "
+"kanssa"
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
-msgstr ""
+msgstr "syötejäsentäjä ”%s” epäonnistui kohteen ”%s” avaamisessa"
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
-msgstr ""
+msgstr "register_output_wrapper: vastaanotti NULL-osoittimen"
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
+"tulostekäärin ”%s” on ristiriidassa aiemmin asennetun tulostekäärimen ”%s” "
+"kanssa"
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
-msgstr ""
+msgstr "tulostekäärin ”%s” epäonnistui avaamaan ”%s”"
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
-msgstr ""
+msgstr "register_output_processor: vastaanotti NULL-osoittimen"
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
+"kaksisuuntainen prosessori ”%s” on ristiriidassa aiemmin asennetun "
+"kaksisuuntaisen prosessorin ”%s” kanssa"
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
-msgstr ""
+msgstr "kaksisuuntainen prosessori ”%s” epäonnistui avaamaan ”%s”"
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "data-tiedosto ”%s” on tyhjä"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
-msgstr "ei voitu varata lisää syötemuistia"
+msgstr "lisäsyötemuistin varaus epäonnistui"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "”RS”-monimerkkiarvo on gawk-laajennus"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "IPv6-viestintää ei tueta"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "tyhjä argumentti valitsimelle ”-e/--source” ohitetaan"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: valitsin ”-W %s” on tunnistamaton, ohitetaan\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: valitsin vaatii argumentin -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 "ympäristömuuttuja ”POSIXLY_CORRECT” asetettu: käännetään päälle valitsin ”--"
 "posix”"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "valitsin ”--posix” korvaa valitsimen ”--traditional”"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr ""
 "valitsin ”--posix” tai ”--traditional” korvaa valitsimen ”--non-decimal-data”"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "suorittaminen ”%s setuid root”-käyttäjänä saattaa olla turvapulma"
 
-#: main.c:571
-#, fuzzy
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
-msgstr "valitsin ”--posix” korvaa valitsimen ”--binary”"
+msgstr "valitsin ”--posix” korvaa valitsimen ”--characters-as-bytes”"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
-msgstr "ei voi asettaa binaaritilaa vakiosyötteessä (%s)"
+msgstr "binaaritilan asettaminen vakiosyötteessä (%s) epäonnistui"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
-msgstr "ei voi asettaa binaaritilaa vakiotulosteessa (%s)"
+msgstr "binaaritilan asettaminen vakiotulosteessa (%s) epäonnistui"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
-msgstr "ei voi asettaa binaaritilaa vakiovirheessä (%s)"
+msgstr "binaaritilaa asettaminen vakiovirheessä (%s) epäonnistui"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "ei ohjelmatekstiä ollenkaan!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 "Käyttö: %s [POSIX- tai GNU-tyyliset valitsimet] -f ohjelmatiedosto [--] "
 "tiedosto ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 "Käyttö: %s [POSIX- tai GNU-tyyliset valitsimet] [--] %cohjelma%c "
 "tiedosto ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "POSIX-valitsimet:\t\tGNU-pitkät valitsimet: (vakio)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f ohjelmatiedosto\t\t--file=ohjelmatiedosto\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=arvo\t\t--assign=muuttuja=arvo\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "Lyhyet valitsimet:\t\tGNU-pitkät valitsimet: (laajennukset)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[tiedosto]\t\t--dump-variables[=tiedosto]\n"
 
-#: main.c:795
-#, fuzzy
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
-msgstr "\t-p[tiedosto]\t\t--profile[=tiedosto]\n"
+msgstr "\t-D[tiedosto]\t\t--debug[=tiedosto]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'program-text'\t--source='program-text'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E file\t\t\t--exec=tiedosto\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-po\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
-msgstr ""
+msgstr "\t-i include-tiedosto\t\t--include=include-tiedosto\n"
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
-msgstr ""
+msgstr "\t-l kirjasto\t\t--load=kirjasto\n"
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
-#, fuzzy
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
-msgstr "\t-g\t\t\t--gen-po\n"
+msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
-#, fuzzy
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
-msgstr "\t-p[tiedosto]\t\t--profile[=tiedosto]\n"
+msgstr "\t-o[tiedosto]\t\t--pretty-print[=tiedosto]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[tiedosto]\t\t--profile[=tiedosto]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3119,7 +3146,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3132,7 +3159,7 @@ msgstr ""
 "joka on kappale ”Reporting Problems and Bugs” painetussa versiossa.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3142,7 +3169,7 @@ msgstr ""
 "Oletuksena se lukee vakiosyötettä ja kirjoittaa vakiotulosteeseen.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3152,7 +3179,7 @@ msgstr ""
 "\tgawk '{ sum += $1 }; END { print sum }' tiedosto\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3171,7 +3198,7 @@ msgstr ""
 "ehtojen mukaisesti.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3185,7 +3212,7 @@ msgstr ""
 "GNU General Public License-ehdoista.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3193,16 +3220,16 @@ msgstr ""
 "Sinun pitäisi vastaanottaa kopion GNU General Public Licence-lisenssistä\n"
 "tämän ohjelman mukana. Jos näin ei ole, katso http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft ei aseta FS välilehteen POSIX awk:ssa"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "tuntematon arvo kenttämääritteelle: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3211,107 +3238,105 @@ msgstr ""
 "%s: ”%s” argumentti valitsimelle ”-v” ei ole ”var=arvo”-muodossa\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "”%s” ei ole laillinen muuttujanimi"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "”%s” ei ole muuttujanimi, etsitään tiedostoa ”%s=%s”"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
-msgstr "ei voi käyttää gawk-ohjelman sisäistä ”%s”-määrittelyä muuttujanimenä"
+msgstr ""
+"gawk-ohjelman sisäisen ”%s”-määrittelyn käyttö muuttujanimenä epäonnistui"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
-msgstr "funktionimeä ”%s” ei voi käyttää muuttujanimenä"
+msgstr "funktionimen ”%s” käyttö muuttujanimenä epäonnistui"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "liukulukupoikkeus"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "tuhoisa virhe: sisäinen virhe"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "tuhoisa virhe: sisäinen virhe: segmenttivirhe"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "tuhoisa virhe: sisäinen virhe: pinoylivuoto"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "ei avattu uudelleen tiedostomäärittelijää %d"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
-msgstr "ei voitu avata uudelleen laitetta /dev/null tiedostomäärittelijälle %d"
+msgstr ""
+"laitteen /dev/null avaaminen uudelleen tiedostomäärittelijälle %d epäonnistui"
 
 #: mpfr.c:550
-#, fuzzy, c-format
+#, c-format
 msgid "PREC value `%.*s' is invalid"
-msgstr "BINMODE-arvo ”%s” on virheellinen, käsiteltiin arvona 3"
+msgstr "PREC-arvo ”%.*s” on virheellinen"
 
 #: mpfr.c:608
-#, fuzzy, c-format
+#, c-format
 msgid "RNDMODE value `%.*s' is invalid"
-msgstr "BINMODE-arvo ”%s” on virheellinen, käsiteltiin arvona 3"
+msgstr "RNDMODE-arvo ”%.*s” on virheellinen"
 
 #: mpfr.c:698
-#, fuzzy, c-format
+#, c-format
 msgid "%s: received non-numeric argument"
-msgstr "cos: vastaanotettu argumentti ei ole numeerinen"
+msgstr "%s: vastaanotettu argumentti ei ole numeerinen"
 
 #: mpfr.c:800
-#, fuzzy
 msgid "compl(%Rg): negative value will give strange results"
-msgstr "compl(%lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "compl(%Rg): negatiivinen arvo antaa outoja tuloksia"
 
 #: mpfr.c:804
-#, fuzzy
 msgid "comp(%Rg): fractional value will be truncated"
-msgstr "compl(%lf): jaosarvo typistetään"
+msgstr "compl(%Rg): jaosarvo typistetään"
 
 #: mpfr.c:816
-#, fuzzy, c-format
+#, c-format
 msgid "cmpl(%Zd): negative values will give strange results"
-msgstr "compl(%lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "compl(%Zd): negatiiviset arvot antavat outoja tuloksia"
 
 #: mpfr.c:835
-#, fuzzy, c-format
+#, c-format
 msgid "%s: received non-numeric argument #%d"
-msgstr "cos: vastaanotettu argumentti ei ole numeerinen"
+msgstr "%s: vastaanotettu argumentti #%d ei ole numeerinen"
 
 #: mpfr.c:845
 msgid "%s: argument #%d has invalid value %Rg, using 0"
-msgstr ""
+msgstr "%s: argumentilla #%d on virheellinen arvo %Rg, käytetään 0"
 
 #: mpfr.c:857
-#, fuzzy
 msgid "%s: argument #%d negative value %Rg will give strange results"
-msgstr "compl(%lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "%s: argumentin #%d negatiivinen arvo %Rg antaa outoja tuloksia"
 
 #: mpfr.c:863
-#, fuzzy
 msgid "%s: argument #%d fractional value %Rg will be truncated"
-msgstr "or(%lf, %lf): jaosarvot typistetään"
+msgstr "%s: argumentin #%d jaosarvo %Rg typistetään"
 
 #: mpfr.c:878
-#, fuzzy, c-format
+#, c-format
 msgid "%s: argument #%d negative value %Zd will give strange results"
-msgstr "compl(%lf): negatiiviset arvot antavat outoja tuloksia"
+msgstr "%s: argumentin #%d negatiivinen arvo %Zd antaa outoja tuloksia"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "komentorivi:"
@@ -3358,23 +3383,24 @@ msgstr ""
 #: posix/gawkmisc.c:177
 #, c-format
 msgid "%s %s `%s': could not get fd flags: (fcntl F_GETFD: %s)"
-msgstr "%s %s ”%s”: ei voitu hakea fd-lippuja: (fcntl F_GETFD: %s)"
+msgstr "%s %s ”%s”: fd-lippujen hakeminen epäonnistui: (fcntl F_GETFD: %s)"
 
 #: posix/gawkmisc.c:189
 #, c-format
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
-msgstr "%s %s ”%s”: ei voitu asettaa close-on-exec: (fcntl F_SETFD: %s)"
+msgstr ""
+"%s %s ”%s”: close-on-exec -asettaminen epäonnistui: (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
-msgstr "ei voitu avata tiedostoa ”%s” kirjoittamista varten: %s"
+msgstr "tiedoston ”%s” avaaminen kirjoittamista varten epäonnistui: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "lähetetään profiili vakiovirheeseen"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3383,7 +3409,7 @@ msgstr ""
 "\t# %s-lohko(t)\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3392,29 +3418,30 @@ msgstr ""
 "\t# Säännöt\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "sisäinen virhe: %s null vname-arvolla"
 
-#: profile.c:530
-#, fuzzy
+#: profile.c:537
 msgid "internal error: builtin with null fname"
-msgstr "sisäinen virhe: %s null vname-arvolla"
+msgstr "sisäinen virhe: builtin null-funktionimellä"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
+"\t# Ladatut laajennukset (-l ja/tai @load)\n"
+"\n"
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# gawk-profiili, luotu %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3423,17 +3450,12 @@ msgstr ""
 "\n"
 "\t# Funktiot, luetteloitu aakkosjärjestyksessä\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: tuntematon edelleenohjaustyyppi %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "muodon ”[%c-%c]” lukualue on paikallisasetuksesta riippuvainen"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3503,50 +3525,33 @@ msgstr "Pariton ) tai \\)"
 msgid "No previous regular expression"
 msgstr "Ei edellistä säännöllistä lauseketta"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
-msgstr ""
+msgstr "pääsisällön pop-toiminto epäonnistui"
 
-#, fuzzy
-#~ msgid "[s]printf called with no arguments"
-#~ msgstr "sqrt: kutsuttu negatiivisella argumentilla %g"
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "muodon ”[%c-%c]” lukualue on paikallisasetuksesta riippuvainen"
 
-#~ msgid "`-m[fr]' option irrelevant in gawk"
-#~ msgstr "”-m[fr]”-valitsin asiaanliittymätön gawk:ssa"
-
-#~ msgid "-m option usage: `-m[fr] nnn'"
-#~ msgstr "-m valitsinkäyttö: ”-m[fr] nnn”"
-
-#, fuzzy
-#~ msgid "%s: received non-numeric first argument"
-#~ msgstr "or: ensimmäinen vastaanotettu argumentti ei ole numeerinen"
-
-#, fuzzy
-#~ msgid "%s: received non-numeric second argument"
-#~ msgstr "or: toinen vastaanotettu argumentti ei ole numeerinen"
+#~ msgid "attempt to use function `%s' as an array"
+#~ msgstr "yritettiin käyttää funktiota ”%s” taulukkona"
 
-#, fuzzy
-#~ msgid "%s(%Rg, ..): negative values will give strange results"
-#~ msgstr "or(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+#~ msgid "reference to uninitialized element `%s[\"%.*s\"]'"
+#~ msgstr "viite alustamattomaan elementtiin ”%s[\"%.*s\"]”"
 
-#, fuzzy
-#~ msgid "%s(%Rg, ..): fractional values will be truncated"
-#~ msgstr "or(%lf, %lf): jaosarvot typistetään"
+#~ msgid "subscript of array `%s' is null string"
+#~ msgstr "taulukon alaindeksi ”%s” on null-merkkijono"
 
-#, fuzzy
-#~ msgid "%s(%Zd, ..): negative values will give strange results"
-#~ msgstr "or(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+#~ msgid "%s: empty (null)\n"
+#~ msgstr "%s: tyhjä (null)\n"
 
-#, fuzzy
-#~ msgid "%s(.., %Rg): negative values will give strange results"
-#~ msgstr "or(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+#~ msgid "%s: empty (zero)\n"
+#~ msgstr "%s: tyhjä (nolla)\n"
 
-#, fuzzy
-#~ msgid "%s(.., %Zd): negative values will give strange results"
-#~ msgstr "or(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+#~ msgid "%s: table_size = %d, array_size = %d\n"
+#~ msgstr "%s: table_size = %d, array_size = %d\n"
 
-#~ msgid "`%s' is a Bell Labs extension"
-#~ msgstr "”%s” on Bell Labs -laajennus"
+#~ msgid "%s: array_ref to %s\n"
+#~ msgstr "%s: array_ref-viite taulukkoon %s\n"
 
 #~ msgid "`nextfile' is a gawk extension"
 #~ msgstr "”nextfile” on gawk-laajennus"
@@ -3554,14 +3559,29 @@ msgstr ""
 #~ msgid "`delete array' is a gawk extension"
 #~ msgstr "”delete array” on gawk-laajennus"
 
+#~ msgid "use of non-array as array"
+#~ msgstr "ei-taulukon käyttö taulukkona"
+
+#~ msgid "`%s' is a Bell Labs extension"
+#~ msgstr "”%s” on Bell Labs -laajennus"
+
 #~ msgid "and: received non-numeric first argument"
 #~ msgstr "and: ensimmäinen vastaanotettu argumentti ei ole numeerinen"
 
 #~ msgid "and: received non-numeric second argument"
 #~ msgstr "and: toinen vastaanotettu argumentti ei ole numeerinen"
 
-#~ msgid "and(%lf, %lf): fractional values will be truncated"
-#~ msgstr "and(%lf, %lf): jaosarvot typistetään"
+#~ msgid "or: received non-numeric first argument"
+#~ msgstr "or: ensimmäinen vastaanotettu argumentti ei ole numeerinen"
+
+#~ msgid "or: received non-numeric second argument"
+#~ msgstr "or: toinen vastaanotettu argumentti ei ole numeerinen"
+
+#~ msgid "or(%lf, %lf): negative values will give strange results"
+#~ msgstr "or(%lf, %lf): negatiiviset arvot antavat outoja tuloksia"
+
+#~ msgid "or(%lf, %lf): fractional values will be truncated"
+#~ msgstr "or(%lf, %lf): jaosarvot typistetään"
 
 #~ msgid "xor: received non-numeric first argument"
 #~ msgstr "xor: ensimmäinen vastaanotettu argumentti ei ole numeerinen"
@@ -3572,35 +3592,8 @@ msgstr ""
 #~ msgid "xor(%lf, %lf): fractional values will be truncated"
 #~ msgstr "xor(%lf, %lf): jaosarvot typistetään"
 
-#~ msgid "Operation Not Supported"
-#~ msgstr "Toimintoa ei tueta"
-
-#~ msgid "attempt to use function `%s' as an array"
-#~ msgstr "yritettiin käyttää funktiota ”%s” taulukkona"
-
-#~ msgid "reference to uninitialized element `%s[\"%.*s\"]'"
-#~ msgstr "viite alustamattomaan elementtiin ”%s[\"%.*s\"]”"
-
-#~ msgid "subscript of array `%s' is null string"
-#~ msgstr "taulukon alaindeksi ”%s” on null-merkkijono"
-
-#~ msgid "%s: empty (null)\n"
-#~ msgstr "%s: tyhjä (null)\n"
-
-#~ msgid "%s: empty (zero)\n"
-#~ msgstr "%s: tyhjä (nolla)\n"
-
-#~ msgid "%s: table_size = %d, array_size = %d\n"
-#~ msgstr "%s: table_size = %d, array_size = %d\n"
-
-#~ msgid "%s: array_ref to %s\n"
-#~ msgstr "%s: array_ref-viite taulukkoon %s\n"
-
-#~ msgid "use of non-array as array"
-#~ msgstr "ei-taulukon käyttö taulukkona"
-
 #~ msgid "can't use function name `%s' as variable or array"
-#~ msgstr "funktionimeä ”%s” ei voi käyttää muuttujana tai taulukkona"
+#~ msgstr "funktionimeä ”%s” käyttö muuttujana tai taulukkona epäonnistui"
 
 #~ msgid "assignment used in conditional context"
 #~ msgstr "sijoitusta käytetty ehdollisessa kontekstissa"
@@ -3632,11 +3625,20 @@ msgstr ""
 #~ msgid "Sorry, don't know how to interpret `%s'"
 #~ msgstr "Ei osata tulkita kohdetta ”%s”"
 
+#~ msgid "Operation Not Supported"
+#~ msgstr "Toimintoa ei tueta"
+
+#~ msgid "`-m[fr]' option irrelevant in gawk"
+#~ msgstr "”-m[fr]”-valitsin asiaanliittymätön gawk:ssa"
+
+#~ msgid "-m option usage: `-m[fr] nnn'"
+#~ msgstr "-m valitsinkäyttö: ”-m[fr] nnn”"
+
 #~ msgid "\t-R file\t\t\t--command=file\n"
 #~ msgstr "\t-R tiedosto\t\t\t--exec=tiedosto\n"
 
 #~ msgid "could not find groups: %s"
-#~ msgstr "ei voitu löytää ryhmiä: %s"
+#~ msgstr "ryhmien löytäminen epäonnistui: %s"
 
 #~ msgid "assignment is not allowed to result of builtin function"
 #~ msgstr "sijoitusta ei sallita sisäänrakennetun funktion tulokselle"
@@ -3701,7 +3703,7 @@ msgstr ""
 #~ msgstr "/inet/raw-palvelin ei ole vielä valitettavasti valmis"
 
 #~ msgid "file `%s' is a directory"
-#~ msgstr "tiedosto `%s' on hakemisto"
+#~ msgstr "tiedosto ”%s” on hakemisto"
 
 #~ msgid "use `PROCINFO[\"%s\"]' instead of `%s'"
 #~ msgstr "käytä ”PROCINFO[\"%s\"]” eikä ”%s”"
@@ -3722,7 +3724,7 @@ msgstr ""
 #~ msgstr "\t-W usage\t\t--usage\n"
 
 #~ msgid "can't convert string to float"
-#~ msgstr "ei voi muuntaa merkkijonoa liukuluvuksi"
+#~ msgstr "merkkijonon muuntaminen liukuluvuksi epäonnistui"
 
 #~ msgid "# treated internally as `delete'"
 #~ msgstr "# käsitelty sisäisesti kuin ”delete”"
@@ -3745,7 +3747,11 @@ msgstr ""
 
 #~ msgid "can't open two way socket `%s' for input/output (%s)"
 #~ msgstr ""
-#~ "ei voi avata kaksisuuntaista pistoketta ”%s” syötteelle/tulosteelle (%s)"
+#~ "kaksisuuntaisen vastakkeen ”%s” avaaminen syötteelle/tulosteelle (%s) "
+#~ "epäonnistui"
 
 #~ msgid "attempt to use scalar `%s' as array"
 #~ msgstr "yritettiin käyttää skalaaria ”%s” taulukkona"
+
+#~ msgid "cannot pop main context"
+#~ msgstr "pääsisällön pop-toiminto epäonnistui"
diff --git a/po/fr.gmo b/po/fr.gmo
index 2ed0420a..c962ab71 100644
--- a/po/fr.gmo
+++ b/po/fr.gmo
diff --git a/po/fr.po b/po/fr.po
index 5c1ef226..2a951b29 100644
--- a/po/fr.po
+++ b/po/fr.po
@@ -7,10 +7,10 @@
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk 4.0.75\n"
+"Project-Id-Version: gawk 4.1.0b\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
-"PO-Revision-Date: 2013-04-23 23:41+0200\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-01-16 00:31+0100\n"
 "Last-Translator: Jean-Philippe Guérard <jean-philippe.guerard@corbeaunoir."
 "org>\n"
 "Language-Team: French <traduc@traduc.org>\n"
@@ -20,84 +20,84 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n > 1);\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "de %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "tentative d'utiliser un scalaire comme tableau"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "tentative d'utiliser le paramètre scalaire « %s » comme tableau"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "tentative d'utiliser le scalaire « %s » comme tableau"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "tentative d'utilisation du tableau « %s » dans un contexte scalaire"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete : l'indice « %s » est absent du tableau « %s »"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "tentative d'utiliser le scalaire « %s[\"%.*s\"] » comme tableau"
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr "adump : le 1er argument n'est pas un tableau"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort : le 2e argument n'est pas un tableau"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti : le 2e argument n'est pas un tableau"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort : le 1er argument n'est pas un tableau"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti : le 1er argument n'est pas un tableau"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr "asort : le 2e argument ne doit pas être un sous-tableau du 1er"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr "asorti : le 2e argument ne doit pas être un sous-tableau du 1er"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr "asort : le 1er argument ne doit pas être un sous-tableau du 2e"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr "asorti : le 1er argument ne doit pas être un sous-tableau du 2e"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "« %s » n'est pas un nom de fonction valide"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "la fonction de comparaison « %s » du tri n'est pas définie"
@@ -138,11 +138,11 @@ msgstr "le corps du switch comporte des cas répétés : %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "plusieurs « default » ont été détectés dans le corps du switch"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "« break » est interdit en dehors d'une boucle ou d'un switch"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "« continue » est interdit en dehors d'une boucle ou d'un switch"
 
@@ -235,277 +235,277 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr "expression indice incorrecte"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "avertissement : "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "fatal : "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "fin de chaîne ou passage à la ligne inattendu"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "impossible d'ouvrir le fichier source « %s » en lecture (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "impossible d'ouvrir la bibliothèque partagée « %s » en lecture (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "raison inconnue"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr "impossible d'inclure « %s » et de l'utiliser comme extension"
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "le fichier source « %s » a déjà été intégré"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
 msgstr "la bibliothèque partagée « %s » est déjà chargée"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include est une extension gawk"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "Le nom de fichier après @include est vide"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr "@load est une extension gawk"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
 msgstr "Le nom de fichier après @load est vide"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "le programme indiqué en ligne de commande est vide"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "impossible de lire le fichier source « %s » (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "le fichier source « %s » est vide"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "le fichier source ne se termine pas par un passage à la ligne"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr ""
 "expression rationnelle non refermée terminée par un « \\ » en fin de fichier"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "%s : %d : le modificateur d'expressions rationnelles « /.../%c » de tawk ne "
 "marche pas dans gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "le modificateur d'expressions rationnelles « /.../%c » de tawk ne marche pas "
 "dans gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "expression rationnelle non refermée"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "expression rationnelle non refermée en fin de fichier"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr ""
 "l'utilisation de « \\ #... » pour prolonger une ligne n'est pas portable"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "la barre oblique inverse n'est pas le dernier caractère de la ligne"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX n'autorise pas l'opérateur « **= »"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "l'ancien awk ne dispose pas de l'opérateur « **= »"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX n'autorise pas l'opérateur « ** »"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "l'ancien awk ne dispose pas de l'opérateur « ** »"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "l'ancien awk ne dispose pas de l'opérateur « ^= »"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "l'ancien awk ne dispose pas de l'opérateur « ^ »"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "chaîne non refermée"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "caractère incorrect « %c » dans l'expression"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "« %s » est une extension gawk"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX n'autorise pas « %s »"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "l'ancien awk ne dispose pas de « %s »"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "« goto est jugé dangereux ! » (Edsger W. Dijkstra)\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d n'est pas un nombre d'arguments valide de %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 "%s : une chaîne littérale en dernier argument d'une substitution est sans "
 "effet"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "le 3e paramètre de %s n'est pas un objet modifiable"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match : le 3e argument est une extension gawk"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close : le 2e argument est une extension gawk"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "utilisation incorrecte de dcgettext(_\"...\") : enlevez le souligné de tête"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "utilisation incorrecte de dcngettext(_\"...\") : enlevez le souligné de tête"
 
-#: awkgram.y:3992
-#, fuzzy
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
-msgstr "index : le second argument n'est pas une chaîne"
+msgstr ""
+"index : le second argument ne peut être une expression rationnelle constante"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "fonction « %s » : le paramètre « %s » masque la variable globale"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "impossible d'ouvrir « %s » en écriture (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "envoi de la liste des variables vers la sortie d'erreur standard"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s : échec de la fermeture (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadows_funcs() a été appelé deux fois !"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "il y avait des variables masquées."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "nom de fonction « %s » déjà défini"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr ""
 "fonction « %s » : impossible d'utiliser un nom de fonction comme paramètre"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "fonction « %s » : impossible d'utiliser la variable spéciale « %s » comme "
 "paramètre d'une fonction"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr ""
 "fonction « %s » : paramètre #%d, « %s » est un doublon du paramètre #%d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "fonction « %s » appelée sans être définie"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "fonction « %s » définie mais jamais appelée directement"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "le paramètre #%d, une expr. rationnelle constante, fournit un booléen"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -514,236 +514,249 @@ msgstr ""
 "fonction « %s » appelée avec un espace entre son nom\n"
 "et « ( », ou utilisée comme variable ou tableau"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "tentative de division par zéro"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "tentative de division par zéro dans « %% »"
 
-#: builtin.c:128
+# gawk 'BEGIN { $1++ = 1 }'
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+"impossible d'assigner une valeur au résultat de la post-incrémentation d'un "
+"champ"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "cible de l'assignement incorrecte (opcode %s)"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "échec de %s vers « %s » (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "sortie standard"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp : l'argument n'est pas numérique"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp : l'argument %g est hors limite"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush : vidage impossible : le tube « %s » est ouvert en lecture et non en "
 "écriture"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush : vidage impossible : fichier « %s » ouvert en lecture, pas en "
 "écriture"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr ""
 "fflush : « %s » n'est ni un fichier ouvert, ni un tube, ni un co-processus"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index : le premier argument n'est pas une chaîne"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index : le second argument n'est pas une chaîne"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int : l'argument n'est pas numérique"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length : l'argument reçu est un tableau"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "« length(tableau) » est une extension gawk"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length : l'argument n'est pas une chaîne"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log : l'argument n'est pas numérique"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log : l'argument est négatif %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr ""
 "fatal : « numéro$ » doit être utilisé pour toutes les formats ou pour aucun"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "taille du champ de la spécification « %% » ignorée"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "précision de la spécification « %% » ignorée"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "taille du champ et précision de la spécification « %% » ignorées"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "fatal : « $ » n'est pas autorisé dans les formats awk"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "fatal : le numéro d'argument de « $ » doit être > 0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr ""
 "fatal : le numéro d'argument %ld est > au nombre total d'arguments fournis"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "fatal : dans un format, « $ » ne doit pas suivre un point"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
 "fatal : aucun « $ » fourni pour la taille ou la précision du champ positionné"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "« l » n'a aucun sens dans un format awk ; ignoré"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "fatal : « l » est interdit dans un format awk POSIX"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "« L » n'a aucun sens dans un format awk ; ignoré"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "fatal : « L » est interdit dans un format awk POSIX"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "« h » n'a aucun sens dans un format awk ; ignoré"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "fatal : « h » est interdit dans un format awk POSIX"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf : valeur %g hors limite pour le format « %%%c »"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr "caractère de format inconnu « %c » ignoré : aucun argument converti"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr "fatal : pas assez d'arguments pour satisfaire la chaîne de formatage"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "^ à court pour celui-ci"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf : spécification de format sans lettre de contrôle"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "trop d'arguments pour la chaîne de formatage"
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr "sprintf : aucun argument"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf : aucun argument"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt : l'argument n'est pas numérique"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt : appelé avec un argument négatif %g"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr : la longueur %g n'est pas >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr : la longueur %g n'est pas >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr : la longueur %g n'est pas entière, elle sera tronquée"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr "substr : la longueur %g est trop grande, tronquée à %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr : l'index de début %g n'est pas valide, utilisation de 1"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr : l'index de début %g n'est pas un entier, il sera tronqué"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr : la chaîne source est de longueur nulle"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr : l'index de début %g est au-delà de la fin de la chaîne"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -751,195 +764,195 @@ msgstr ""
 "substr : la longueur %g à partir de %g dépasse la fin du 1er argument (%lu)"
 
 # Exemple : gawk --lint 'BEGIN { PROCINFO["strftime"]=123 ;  print strftime() }'
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 "strftime : la valeur de formatage PROCINFO[\"strftime\"] est de type "
 "numérique"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime : le second argument n'est pas numérique"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr "strftime: second argument négatif ou trop grand pour time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftim : le premier argument n'est pas une chaîne"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime : la chaîne de formatage est vide"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime : l'argument n'est pas une chaîne"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr ""
 "mktime : au moins l'une des valeurs est en dehors de la plage par défaut"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "La fonction « system » est interdite en isolement (mode sandbox)"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system : l'argument n'est pas une chaîne"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "référence à un champ non initialisé « $%d »"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower : l'argument n'est pas une chaîne"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper : l'argument n'est pas une chaîne"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2 : le premier argument n'est pas numérique"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2 : le second argument n'est pas numérique"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin : l'argument n'est pas numérique"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos : l'argument n'est pas numérique"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand : l'argument n'est pas numérique"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match : le 3e argument n'est pas un tableau"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub : le 3e argument vaut 0, il sera traité comme un 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift : le premier argument n'est pas numérique"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift : le second argument reçu n'est pas numérique"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr ""
 "lshift(%f, %f) : les valeurs négatives donnent des résultats inattendus"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%f, %f) : les valeurs non entières seront tronquées"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr "lshift(%f, %f) : un décalage trop grand donne des résultats inattendus"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift : le premier argument n'est pas numérique"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift : le second argument reçu n'est pas numérique"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr ""
 "rshift(%f, %f) : les valeurs négatives donneront des résultats inattendus"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%f, %f) : les valeurs non entières seront tronquées"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "rshift(%f, %f) : un décalage trop grand donnera des résultats inattendus"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr "and : appelé avec moins de 2 arguments"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "and : l'argument %d n'est pas numérique"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr ""
 "and : l'argument %d est négatif (%g) ce qui aura des résultats inattendus"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
 msgstr "or : appelé avec moins de 2 arguments"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "or : l'argument %d n'est pas numérique"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr ""
 "or : l'argument %d est négatif (%g) ce qui aura des résultats inattendus"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr "xor : appelé avec moins de 2 arguments"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "xor : l'argument %d n'est pas numérique"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr ""
 "xor : l'argument %d est négatif (%g) ce qui aura des résultats inattendus"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl : l'argument n'est pas numérique"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%f) : les valeurs négatives donneront des résultats inattendus"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%f) : les valeurs non entières seront tronquées"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext : « %s » n'est pas dans un catégorie valide de la locale"
@@ -1066,8 +1079,8 @@ msgstr "clear [[fichier:]N|fonction] - détruit un point d'arrêt existant."
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 "commands [no] - débute une liste de commande à lancer aux points d'arrêt ou "
 "de surveillance."
@@ -1243,7 +1256,7 @@ msgstr "up [N] - remonte de N trames dans la pile."
 msgid "watch var - set a watchpoint for a variable."
 msgstr "watch var - définit un point de surveillance pour une variable."
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "erreur : "
@@ -1281,96 +1294,96 @@ msgstr "Caractère incorrect"
 msgid "undefined command: %s\n"
 msgstr "commande inconnue : %s\n"
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr "affiche ou définit le nombre de lignes du fichier d'historique."
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr "affiche ou définit la taille de fenêtre pour la commande list."
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr "affiche ou définit le fichier de sortie de gawk."
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr "affiche ou définit l'invite du débogueur."
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 "affiche ou (dés)active l'enregistrement de l'historique (valeur=on|off)."
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr "affiche ou (dés)active l'enregistrement des options (valeur=on|off)."
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr "affiche ou (dés)active le traçage des instructions (valeur=on|off)."
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr "le programme n'est pas en cours."
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "impossible de lire le fichier source « %s » (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "le fichier source « %s » est vide.\n"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr "pas de fichier source courant."
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "impossible de trouver le fichier source nommé « %s » (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 "ATTENTION : fichier source « %s » modifié après compilation du programme.\n"
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr "numéro de ligne %d hors limite ; « %s » a %d lignes"
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "fin de fichier inattendue lors de la lecture de « %s », ligne %d"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr "fichier source « %s » modifié depuis le début d'exécution du programme"
 
 # c-format
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr "Fichier source courant : %s\n"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr "Nombre de lignes : %d\n"
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr "Fichier source (lignes) : %s (%d)\n"
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
@@ -1378,54 +1391,54 @@ msgstr ""
 "Numéro  Post  Activé   Position\n"
 "\n"
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr "\tnb occurrences = %ld\n"
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr "\tignore %ld prochaines occurrences\n"
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr "\tcondition d'arrêt : %s\n"
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr "\tcommandes :\n"
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr "Trame courante : "
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr "Appelée par la trame : "
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr "Appelant de la trame : "
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr "Aucune dans main().\n"
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr "Aucun argument.\n"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr "Aucune variable locale.\n"
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
@@ -1433,7 +1446,7 @@ msgstr ""
 "Liste des variables définies :\n"
 "\n"
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
@@ -1441,7 +1454,7 @@ msgstr ""
 "Liste des fonctions définies :\n"
 "\n"
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
@@ -1449,7 +1462,7 @@ msgstr ""
 "Variables affichées automatiquement :\n"
 "\n"
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
@@ -1457,396 +1470,396 @@ msgstr ""
 "Variables inspectées :\n"
 "\n"
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "pas de symbole « %s » dans le contexte actuel\n"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr "« %s » n'est pas un tableau\n"
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "$%ld = champ non initialisé\n"
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr "le tableau « %s » est vide\n"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "[\"%s\"] n'est pas dans le tableau « %s »\n"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr "« %s[\"%s\"] » n'est pas un tableau\n"
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "« %s » n'est pas une variable scalaire"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "tentative d'utilisation du tableau « %s[\"%s\"] » en contexte scalaire"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "tentative d'utiliser le scalaire « %s[\"%s\"] » comme tableau"
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr "« %s » est une fonction"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr "le point de surveillance %d est inconditionnel\n"
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr "Aucune entrée d'affichage numéro %ld"
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr "Aucune entrée de surveillance numéro %ld"
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "%d: [\"%s\"] n'est pas dans le tableau « %s »\n"
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr "tentative d'utiliser un scalaire comme tableau"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 "Point de surveillance %d détruit, car son paramètre est hors contexte.\n"
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr "Affichage %d détruit, car son paramètre est hors contexte\n"
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr "dans le fichier « %s », ligne %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr " à « %s »:%d"
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr "#%ld\tdans "
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr "D'autres trames de la pile suivent...\n"
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr "Numéro de trame incorrect"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Note : point d'arrêt %d (activé, ignore %ld occurrences) déjà défini à %s:%d"
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr "Note : point d'arrêt %d (activé) déjà défini à %s:%d"
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Note : point d'arrêt %d (désactivé, ignore %ld occurrences) déjà défini à %s:"
 "%d"
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr "Note : point d'arrêt %d (désactivé) déjà défini à %s:%d"
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr "Point d'arrêt %d défini dans le fichier « %s » ligne %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr "Impossible de définir un point d'arrêt dans le fichier « %s »\n"
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "numéro de ligne %d dans le fichier « %s » hors limite"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr "Règle introuvable !!!\n"
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr "Impossible de définir un point d'arrêt à « %s »:%d\n"
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr "Impossible de définir un point d'arrêt dans la fonction « %s »\n"
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 "le point d'arrêt %d défini sur le fichier « %s », ligne %d est "
 "inconditionnel\n"
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr "Point d'arrêt %d supprimé"
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr "Aucun point d'arrêt à l'appel de la fonction « %s »\n"
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "Pas de point d'arrêt sur le fichier « %s », ligne #%d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr "Numéro de point d'arrêt incorrect"
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr "Supprimer tous les points d'arrêt (o ou n) "
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr "o"
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr "Ignorera les prochaines %ld occurrences du point d'arrêt %d.\n"
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr "S'arrêtera à la prochaine occurrence du point d'arrêt %d.\n"
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 "Seuls les programmes fournis via l'option « -f » peuvent être débogués.\n"
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr "Échec de redémarrage du débogueur"
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr "Programme en cours. Reprendre depuis le début (o/n) ? "
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr "Programme non redémarré\n"
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr "erreur : impossible de redémarrer, opération interdite\n"
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr "erreur (%s) : impossible de redémarrer, suite des commandes ignorées\n"
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr "Démarrage du programme :\n"
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr "Le programme s'est terminé %s avec le code de retour : %d\n"
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr "Le programme est en cours. Sortir quand même (o/n) ?"
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr "Auncun arrêt à un point d'arrêt : argument ignoré.\n"
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr "point d'arrêt %d incorrect."
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr "Les %ld prochaines occurrences du point d'arrêt %d seront ignorées.\n"
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr "« finish » n'a pas de sens dans la trame initiale main()\n"
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr "S'exécute jusqu'au retour de "
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr "« return » n'a pas de sens dans la trame initiale main()\n"
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr "Impossible de trouver la position indiquée dans la fonction « %s »\n"
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "ligne source %d incorrecte dans le fichier « %s »"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr "Position %d introuvable dans le fichier « %s »\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr "élément absent du tableau\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr "variable sans type\n"
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr "Arrêt dans %s...\n"
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr "« finish » n'a pas de sens avec un saut non local « %s »\n"
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr "« until » n'a pas de sens avec un saut non local « %s »\n"
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr "\t---« [Entrée] » continuer ; « q [Entrée] » quitter---"
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr "q"
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "[\"%s\"] est absent du tableau « %s »"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr "envoi de la sortie vers stdout\n"
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr "nombre incorrect"
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "« %s » interdit dans ce contexte ; instruction ignorée"
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "« return » interdit dans ce contexte ; instruction ignorée"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr "Pas de symbole « %s » dans le contexte actuel"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr "[ non apparié"
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr "classe de caractères incorrecte"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr "la syntaxe des classes de caractères est [[:space:]], et non [:space:]"
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr "échappement \\ non terminé"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Contenu de \\{\\} incorrect"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Expression rationnelle trop grande"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr "( non apparié"
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr "aucune syntaxe indiquée"
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ") non apparié"
 
@@ -1865,11 +1878,11 @@ msgstr "code opération %d inconnu"
 msgid "opcode %s not an operator or keyword"
 msgstr "le code opération %s n'est pas un opérateur ou un mot-clef"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "débordement de tampon dans genflag2str"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1880,71 +1893,71 @@ msgstr ""
 "\t# Pile des appels de fonctions :\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "« IGNORECASE » est une extension gawk"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "« BINMODE » est une extension gawk"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "la valeur « %s » de BINMODE n'est pas valide, 3 utilisé à la place"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "spécification de « %sFMT » erronée « %s »"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "désactivation de « --lint » en raison d'une affectation à « LINT »"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "référence à un argument non initialisé « %s »"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "référence à une variable non initialisée « %s »"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "tentative de référence à un champ via une valeur non numérique"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "tentative de référence à un champ via une chaîne nulle"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "tentative d'accès au champ %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "référence à un champ non initialisé « $%ld »"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "la fonction « %s » a été appelée avec trop d'arguments"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: type « %s » inattendu"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "tentative de division par zéro dans « /= »"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "tentative de division par zéro dans « %%= »"
@@ -1957,7 +1970,7 @@ msgstr "les extensions sont interdites en isolement (mode sandbox)"
 msgid "-l / @load are gawk extensions"
 msgstr "-l / @load est une extension gawk"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr "load_ext : lib_name reçu NULL"
 
@@ -1992,6 +2005,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "« extension » est une extension gawk"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "extension : lib_name reçu NULL"
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -2016,38 +2033,38 @@ msgstr ""
 msgid "make_builtin: missing function name"
 msgstr "make_builtin : nom de fonction manquant"
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "make_builtin : impossible de redéfinir la fonction « %s »"
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "make_builtin : fonction « %s » déjà définie"
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "make_builtin : nom de la fonction « %s » déjà défini"
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 "make_builtin : impossible d'utiliser la fonction gawk « %s » comme nom de "
 "fonction"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin : la fonction « %s » a un nombre négatif d'arguments"
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr "extension : nom de fonction manquant"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension : caractère illégal « %c » dans le nom de la fonction « %s »"
@@ -2074,143 +2091,147 @@ msgstr ""
 "extension : impossible d'utiliser la fonction interne gawk « %s » comme nom "
 "de fonction"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "fonction « %s »  définie comme ayant au maximum« %d » argument(s)"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "fonction « %s » : argument #%d manquant"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr ""
 "fonction « %s » : argument #%d : tentative d'utilisation d'un scalaire comme "
 "tableau"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr ""
 "fonction « %s » : argument #%d : tentative d'utiliser un tableau comme "
 "scalaire"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr "chargement dynamique des bibliothèques impossible"
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "chdir : appelé avec un nombre d'arguments incorrects, attendu : 1"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr "stat : impossible de lire le lien symbolique « %s »"
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr "stat : appelé avec un nombre d'arguments incorrect"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr "stat : paramètres incorrects"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr "fts init : impossible de créer la variable %s"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "fts n'est pas compatible avec ce système"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr "fill_stat_element : impossible de créer le tableau"
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr "fill_stat_element : impossible de définir l'élément"
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr "fill_path_element : impossible de définir l'élément"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr "fill_error_element : impossible de définir l'élément"
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr "fts-process : impossible de créer le tableau"
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr "fts-process : impossible de définir l'élément"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "fts : appelé avec un nombre d'arguments incorrects, attendu : 3"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr "fts : premier paramètre incorrect"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr "fts : deuxième paramètre incorrect"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr "fts : troisième paramètre incorrect"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr "fts : impossible d'aplatir le tableau\n"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr "fts : on ignore le drapeau sournois FTS_NOSTAT..."
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr "fts : échec de clear_array()\n"
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr "fnmatch : appelé avec moins de 3 arguments"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr "fnmatch : appelé avec plus de 3 arguments"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr "fnmatch : impossible d'obtenir le 1er argument"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr "fnmatch : impossible d'obtenir le 2e argument"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr "fnmatch : impossible d'obtenir le 3e argument"
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr "fnmatch n'est pas disponible sur ce système\n"
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr "fnmatch init : impossible d'ajouter la variable FNM_NOMATCH"
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr "fnmatch init : impossible de définir l'élément de tableau %s"
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr "fnmatch init : impossible d'installer le tableau FNM"
 
@@ -2234,92 +2255,92 @@ msgstr "wait : appelé sans argument"
 msgid "wait: called with too many arguments"
 msgstr "wait : appelé avec trop d'arguments"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr "inplace_begin : modification sur place déjà active"
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr "inplace_begin : 2 arguments attendu, appelé avec %d"
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 "inplace_begin : impossible de récupérer le 1er argument comme nom de fichier"
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 "inplace_begin : modification sur place annulée pour le fichier incorrect "
 "« %s »"
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "inplace_begin : stat impossible sur « %s » (%s)"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "inplace_begin : « %s » n'est pas un fichier ordinaire"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr "inplace_begin : échec de mkstemp('%s') (%s)"
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "inplace_begin : échec de la chmod (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr "inplace_begin : échec de dup(stdout) (%s)"
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_begin : échec de dup2(%d, stdout) (%s)"
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "inplace_begin : échec de close(%d) (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 "inplace_end : impossible de récupérer le 1er argument comme nom de fichier"
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr "inplace_end : modification sur place non active"
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr "ipnlace_end : échec de dup2(%d, stdout) (%s)"
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "inplace_end : échec de close(%d) (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr "inplace_end : échec de fsetpos(stdout) (%s)"
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "inplace_end : échec de link('%s', '%s') (%s)"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "inplace_end : échec de rename('%s', '%s') (%s)"
@@ -2348,173 +2369,173 @@ msgstr "chr : appelé sans argument"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "chr : appelé avec des arguments incorrects"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr "dir_take_control_of : échec de opendir/fdopendir : %s"
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr "readfile : appelé avec trop d'arguments"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr "readfile : appelé sans argument"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr "writea : appelé avec trop d'arguments"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "do_writea : l'argument 0 n'est pas une chaîne\n"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "do_writea : l'argument 1 n'est pas un tableau\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr "write_array : impossible d'aplatir le tableau\n"
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr "write_array : impossible de libérer le tableau aplati\n"
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr "reada : appelé avec trop d'arguments"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "do_reada : l'argument 0 n'est pas une chaîne\n"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "do_reada : l'argument 1 n'est pas un tableau\n"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr "do_reada : échec de clear_array\n"
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr "read_array : échec de set_array_element\n"
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr "gettimeofday : arguments ignorés"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr "gettimeofday : n'est pas disponible sur cette plateforme"
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr "sleep : appelé avec trop d'arguments"
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr "sleep : l'argument numérique requis est absent"
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr "sleep : l'argument est négatif"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr "sleep : n'est pas disponible sur cette plateforme"
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "une valeur négative a été assignée à NF"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split : le 4e argument est une extension gawk"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split : le 4e argument n'est pas un tableau"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split : le 2e argument n'est pas un tableau"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr "split : impossible d'utiliser le même tableau comme 2e et 4e argument"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split : impossible d'utiliser un sous-tableau du 2e argument en 4e argument"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split : impossible d'utiliser un sous-tableau du 4e argument en 2e argument"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split : utiliser une chaîne vide en 3e argument est une extension gawk"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit : le 4e argument n'est pas un tableau"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit : le 2e argument n'est pas un tableau"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit : le 3e argument n'est pas un tableau"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit : impossible d'utiliser le même tableau comme 2e et 4e argument"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit : impossible d'utiliser un sous-tableau du 2e argument en 4e "
 "argument"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit : impossible d'utiliser un sous-tableau du 4e argument en 2e "
 "argument"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "« FIELDWIDTHS » est une extension gawk"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "valeur de FIELDWIDTHS incorrecte, près de « %s »"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "utiliser une chaîne vide pour « FS » est une extension gawk"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr ""
 "l'ancien awk n'accepte pas les expr. rationnelles comme valeur de « FS »"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "« FPAT » est une extension gawk"
 
@@ -2530,385 +2551,385 @@ msgstr "node_to_awk_value : node nul reçu"
 msgid "node_to_awk_value: received null val"
 msgstr "node_to_awk_value : val nul reçu"
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr "remove_element : tableau nul reçu"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr "remove_element : indice nul reçu"
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr "api_flatten_array : impossible de convertir l'indice %d\n"
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr "api_flatten_array : impossible de convertir la valeur %d\n"
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s : l'option « %s » est ambiguë ; possibilités :"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s : l'option « --%s » n'accepte pas d'argument\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s : l'option « %c%s » n'accepte pas d'argument\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s : l'option « --%s » nécessite un argument\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s : option non reconnue « --%s »\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s : option non reconnue « %c%s »\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s : option incorrecte - « %c »\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s : l'option requiert un argument - « %c »\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s : l'option « -W %s » est ambiguë\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s : l'option « -W %s » n'accepte pas d'argument\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s : l'option « -W %s » nécessite un argument\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "L'argument « %s » de la ligne de commande est un répertoire : ignoré"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "impossible d'ouvrir le fichier « %s » en lecture (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "échec de la fermeture du fd %d (« %s ») : %s"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "les redirections sont interdites en isolement (mode sandbox)"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "l'expression dans la redirection « %s » n'a qu'une valeur numérique"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "l'expression dans la redirection « %s » donne une chaîne nulle"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "le fichier « %s » de la redirection « %s » pourrait être le résultat d'une "
 "expression booléenne"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "mélange non nécessaire de « > » et « >> » pour le fichier « %.*s »"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "impossible d'ouvrir le tube « %s » en sortie (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "impossible d'ouvrir le tube « %s » en entrée (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr ""
 "impossible d'ouvrir un tube bidirectionnel « %s » en entrées-sorties (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "impossible de rediriger depuis « %s » (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "impossible de rediriger vers « %s » (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "limite système du nombre de fichiers ouverts atteinte : début du "
 "multiplexage des descripteurs de fichiers"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "échec de la fermeture de « %s » (%s)."
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "trop de fichiers d'entrées ou de tubes ouverts"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close : le second argument doit être « to » ou « from »"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr ""
 "close : « %.*s » n'est ni un fichier ouvert, ni un tube ou un co-processus"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "fermeture d'une redirection qui n'a jamais été ouverte"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close : la redirection « %s » n'a pas été ouverte avec « |& », second "
 "argument ignoré"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "résultat d'échec (%d) sur la fermeture du tube « %s » (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "résultat d'échec (%d) sur la fermeture du fichier « %s » (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "aucune fermeture explicite du connecteur « %s » fournie"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "aucune fermeture explicite du co-processus « %s » fournie"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "aucune fermeture explicite du tube « %s » fournie"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "aucune fermeture explicite du fichier « %s » fournie"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "erreur lors de l'écriture vers la sortie standard (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "erreur lors de l'écriture vers l'erreur standard (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "échec du vidage du tube « %s » (%s)."
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "échec du vidage du tube vers « %s » par le co-processus (%s)."
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "échec du vidage vers le fichier « %s » (%s)."
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "le port local %s n'est pas valide dans « /inet »"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr ""
 "les informations sur l'hôte et le port distants (%s, %s) ne sont pas valides"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr ""
 "aucun protocole (connu) n'a été fourni dans le nom de fichier spécial « %s »"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "nom de fichier spécial « %s » incomplet"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "un nom d'hôte distant doit être fourni à « /inet »"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "un port distant doit être fourni à « /inet »"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "les communications TCP/IP ne sont pas disponibles"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "impossible d'ouvrir « %s », mode « %s »"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "échec de la fermeture du pty maître (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "échec de la fermeture de stdout du processus fils (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "échec du déplacement du pty esclave vers le stdout du processus fils (dup : "
 "%s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "échec de fermeture du stdin du processus fils (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "échec du déplacement du pty esclave vers le stdin du processus fils (dup : "
 "%s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "échec de la fermeture du pty esclave (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr "échec du déplacement du tube vers stdout du processus fils (dup : %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr "échec de déplacement du tube vers stdin du processus fils (dup : %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "échec de la restauration du stdout dans le processus parent\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "échec de la restauration du stdin dans le processus parent\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "échec de la fermeture du tube (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "« |& » non disponible"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "impossible d'ouvrir le tube « %s » (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "impossible de créer le processus fils pour « %s » (fork : %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr "register_input_parser : pointeur NULL reçu"
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 "l'analyseur d'entrée « %s » est en conflit avec l'analyseur « %s » déjà "
 "installé"
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr "l'analyseur d'entrée « %s » n'a pu ouvrir « %s »"
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr "register_output_wrapper : pointeur NULL reçu"
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 "le filtre de sortie « %s » est en conflit avec le filtre « %s » déjà installé"
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr "le filtre de sortie « %s » n'a pu ouvrir « %s »"
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr "register_output_processor : pointeur NULL reçu"
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
@@ -2917,216 +2938,216 @@ msgstr ""
 "le gestionnaire bidirectionnel « %s » est en conflit avec le gestionnaire "
 "« %s » déjà installé"
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr "le gestionnaire bidirectionnel « %s » n'a pu ouvrir « %s »"
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "le fichier de données « %s » est vide"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "impossible d'allouer plus de mémoire d'entrée"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr ""
 "l'utilisation d'un « RS » de plusieurs caractères est une extension gawk"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "les communications IPv6 ne sont pas disponibles"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "argument vide de l'option « -e / --source » ignoré"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s : option « -W %s » non reconnue, ignorée\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s : l'option requiert un argument - %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 "variable d'environnement « POSIXLY__CORRECT » définie : activation de « --"
 "posix »"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "« --posix » prend le pas sur « --traditional »"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr ""
 "« --posix » et « --traditional » prennent le pas sur « --non-decimal-data »"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr ""
 "l'exécution de %s en mode setuid root peut être un problème de sécurité"
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "« --posix » prend le pas sur « --characters-as-bytes »"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "impossible d'activer le mode binaire sur stdin (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "impossible d'activer le mode binaire sur stdout (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "impossible d'activer le mode binaire sur stderr (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "aucun programme !"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 "Utilisation : %s [options GNU ou POSIX] -f fichier_prog [--] fichier ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 "Utilisation : %s [options GNU ou POSIX] [--] %cprogramme%c fichier ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "Options POSIX :\t\tOptions longues GNU : (standard)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f fichier_prog\t\t--file=fichier_prog\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=valeur\t\t--assign=var=valeur\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "Options POSIX :\t\tOptions longues GNU : (extensions)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[fichier]\t\t--dump-variables[=fichier]\n"
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-D[fichier]\t\t--debug[=fichier]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'programme'\t\t--source='programme'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E fichier\t\t--exec=fichier\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr "\t-i fichier\t\t--include=fichier\n"
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr "\t-l bibliothèque\t\t--load=bibliothèque\n"
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-o[fichier]\t\t--pretty-print[=fichier]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[fichier]\t\t--profile[=fichier]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3135,7 +3156,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3150,7 +3171,7 @@ msgstr ""
 "<traduc CHEZ traduc POINT org>.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3160,7 +3181,7 @@ msgstr ""
 "Par défaut, il lit l'entrée standard et écrit sur la sortie standard.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3170,7 +3191,7 @@ msgstr ""
 "\tgawk '{ somme += $1 }; END { print somme }' fichier\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3190,7 +3211,7 @@ msgstr ""
 "version ultérieure de votre choix.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3205,7 +3226,7 @@ msgstr ""
 "General Public License).\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3214,16 +3235,16 @@ msgstr ""
 "(GNU General Public License) avec ce programme. Sinon, consultez\n"
 "http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft ne définit pas le FS comme étant une tabulation en awk POSIX"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "valeur inconnue pour la définition de champ : %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3232,48 +3253,48 @@ msgstr ""
 "%s : « %s » l'argument de « -v » ne respecte pas la forme « var=valeur »\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "« %s » n'est pas un nom de variable valide"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "« %s » n'est pas un nom de variable, recherche du fichier « %s=%s »"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "impossible d'utiliser le mot clef gawk « %s » comme variable"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "impossible d'utiliser la fonction « %s » comme variable"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "exception du traitement en virgule flottante"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "fatal : erreur interne"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "fatal : erreur interne : erreur de segmentation"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "fatal : erreur interne : débordement de la pile"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "aucun descripteur fd %d pré-ouvert"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "impossible de pré-ouvrir /dev/null pour le descripteur fd %d"
@@ -3330,7 +3351,7 @@ msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr ""
 "%s : argument #%d : la valeur négative %Zd donnera des résultats inattendus"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "ligne de commande:"
@@ -3386,16 +3407,16 @@ msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr ""
 "%s %s « %s »: impossible de positionner close-on-exec: (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "impossible d'ouvrir « %s » en écriture : %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "envoi du profil vers la sortie d'erreur standard"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3404,7 +3425,7 @@ msgstr ""
 "\t# Bloc(s) %s\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3413,16 +3434,16 @@ msgstr ""
 "\t# Règle(s)\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "erreur interne : %s avec un vname nul"
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr "erreur interne : fonction interne avec un fname nul"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
@@ -3431,12 +3452,12 @@ msgstr ""
 "\t# Extensions chargées (-l ou @load)\n"
 "\n"
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# profile gawk, créé %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3445,17 +3466,12 @@ msgstr ""
 "\n"
 "\t# Fonctions, par ordre alphabétique\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str : type de redirection %d inconnu"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "les plages « [%c-%c] » sont dépendantes des paramètres régionaux"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3526,6 +3542,9 @@ msgstr ") ou \\) sans correspondance"
 msgid "No previous regular expression"
 msgstr "Aucune expression rationnelle précédente"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr "impossible de rétablir (pop) le contexte principal (main)"
+
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "les plages « [%c-%c] » sont dépendantes des paramètres régionaux"
diff --git a/po/gawk.pot b/po/gawk.pot
index 6e4582f5..bb47fa9e 100644
--- a/po/gawk.pot
+++ b/po/gawk.pot
@@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk 4.1.0\n"
+"Project-Id-Version: gawk 4.1.1\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,84 +17,84 @@ msgstr ""
 "Content-Type: text/plain; charset=CHARSET\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr ""
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr ""
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr ""
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr ""
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr ""
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr ""
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr ""
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr ""
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr ""
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr ""
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr ""
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr ""
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr ""
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr ""
@@ -135,11 +135,11 @@ msgstr ""
 msgid "duplicate `default' detected in switch body"
 msgstr ""
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr ""
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr ""
 
@@ -228,675 +228,685 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr ""
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr ""
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr ""
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr ""
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr ""
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr ""
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr ""
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr ""
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr ""
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
 msgstr ""
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr ""
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr ""
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr ""
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
 msgstr ""
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr ""
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr ""
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr ""
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr ""
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr ""
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr ""
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr ""
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr ""
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr ""
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr ""
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr ""
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr ""
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr ""
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr ""
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr ""
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr ""
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr ""
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr ""
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr ""
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr ""
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr ""
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr ""
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr ""
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr ""
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr ""
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 
-#: awkgram.y:3992
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
 msgstr ""
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr ""
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr ""
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr ""
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr ""
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr ""
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr ""
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr ""
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr ""
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr ""
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr ""
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr ""
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr ""
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
 "or used as a variable or an array"
 msgstr ""
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr ""
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr ""
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr ""
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr ""
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr ""
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr ""
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr ""
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr ""
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr ""
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr ""
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr ""
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr ""
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr ""
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr ""
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr ""
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr ""
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr ""
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr ""
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr ""
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr ""
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr ""
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr ""
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr ""
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr ""
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr ""
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr ""
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr ""
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr ""
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr ""
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr ""
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr ""
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr ""
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr ""
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr ""
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr ""
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr ""
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr ""
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr ""
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr ""
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr ""
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr ""
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr ""
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr ""
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
 msgstr ""
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr ""
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr ""
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr ""
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr ""
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr ""
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr ""
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr ""
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr ""
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr ""
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr ""
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr ""
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr ""
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr ""
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr ""
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr ""
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr ""
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr ""
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr ""
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr ""
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr ""
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr ""
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr ""
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
 msgstr ""
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
 msgstr ""
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr ""
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr ""
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr ""
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr ""
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr ""
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr ""
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr ""
@@ -1018,8 +1028,8 @@ msgstr ""
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 
 #: command.y:825
@@ -1176,7 +1186,7 @@ msgstr ""
 msgid "watch var - set a watchpoint for a variable."
 msgstr ""
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr ""
@@ -1214,552 +1224,552 @@ msgstr ""
 msgid "undefined command: %s\n"
 msgstr ""
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr ""
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr ""
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr ""
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr ""
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr ""
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr ""
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr ""
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr ""
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr ""
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr ""
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr ""
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr ""
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr ""
 
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr ""
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr ""
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr ""
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr ""
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr ""
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr ""
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr ""
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr ""
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr ""
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr ""
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr ""
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr ""
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr ""
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr ""
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr ""
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr ""
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr ""
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr ""
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr ""
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr ""
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr ""
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr ""
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr ""
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr ""
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr ""
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr ""
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr ""
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr ""
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr ""
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr ""
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr ""
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr ""
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr ""
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr ""
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr ""
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr ""
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr ""
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr ""
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr ""
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr ""
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr ""
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr ""
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr ""
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr ""
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr ""
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr ""
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr ""
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr ""
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr ""
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr ""
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr ""
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr ""
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr ""
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr ""
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr ""
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr ""
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr ""
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr ""
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr ""
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr ""
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr ""
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr ""
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr ""
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr ""
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr ""
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr ""
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr ""
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr ""
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr ""
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr ""
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr ""
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr ""
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr ""
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ""
 
@@ -1778,11 +1788,11 @@ msgstr ""
 msgid "opcode %s not an operator or keyword"
 msgstr ""
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr ""
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1790,71 +1800,71 @@ msgid ""
 "\n"
 msgstr ""
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr ""
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr ""
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr ""
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr ""
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr ""
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr ""
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr ""
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr ""
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr ""
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr ""
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr ""
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr ""
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr ""
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr ""
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr ""
@@ -1867,7 +1877,7 @@ msgstr ""
 msgid "-l / @load are gawk extensions"
 msgstr ""
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr ""
 
@@ -1896,6 +1906,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr ""
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr ""
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1916,36 +1930,36 @@ msgstr ""
 msgid "make_builtin: missing function name"
 msgstr ""
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr ""
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr ""
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr ""
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr ""
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr ""
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr ""
@@ -1970,139 +1984,143 @@ msgstr ""
 msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr ""
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr ""
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr ""
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr ""
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr ""
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr ""
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr ""
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr ""
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr ""
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr ""
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr ""
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr ""
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr ""
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr ""
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr ""
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr ""
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr ""
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr ""
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr ""
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr ""
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr ""
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr ""
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr ""
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr ""
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr ""
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr ""
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr ""
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr ""
 
@@ -2126,88 +2144,88 @@ msgstr ""
 msgid "wait: called with too many arguments"
 msgstr ""
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr ""
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr ""
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr ""
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr ""
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr ""
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr ""
@@ -2236,165 +2254,165 @@ msgstr ""
 msgid "chr: called with inappropriate argument(s)"
 msgstr ""
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr ""
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr ""
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr ""
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr ""
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr ""
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr ""
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr ""
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr ""
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr ""
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr ""
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr ""
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr ""
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr ""
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr ""
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr ""
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr ""
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr ""
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr ""
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr ""
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr ""
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr ""
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr ""
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr ""
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr ""
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr ""
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr ""
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr ""
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr ""
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr ""
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr ""
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr ""
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr ""
 
@@ -2410,577 +2428,577 @@ msgstr ""
 msgid "node_to_awk_value: received null val"
 msgstr ""
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr ""
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr ""
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr ""
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr ""
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr ""
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr ""
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr ""
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr ""
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr ""
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr ""
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr ""
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr ""
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr ""
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr ""
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr ""
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr ""
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr ""
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr ""
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr ""
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr ""
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr ""
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr ""
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr ""
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr ""
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr ""
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr ""
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr ""
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr ""
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr ""
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr ""
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr ""
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr ""
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr ""
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr ""
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr ""
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr ""
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr ""
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr ""
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr ""
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr ""
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr ""
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr ""
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr ""
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr ""
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr ""
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr ""
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr ""
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr ""
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr ""
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr ""
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr ""
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr ""
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr ""
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr ""
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr ""
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr ""
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr ""
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr ""
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr ""
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr ""
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr ""
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr ""
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr ""
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr ""
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr ""
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr ""
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr ""
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr ""
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr ""
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr ""
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr ""
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr ""
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr ""
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr ""
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr ""
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr ""
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr ""
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr ""
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr ""
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr ""
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr ""
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr ""
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr ""
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr ""
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr ""
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr ""
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr ""
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr ""
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr ""
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr ""
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr ""
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr ""
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr ""
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr ""
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr ""
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr ""
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr ""
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr ""
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr ""
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr ""
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr ""
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr ""
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr ""
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr ""
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr ""
 
@@ -2989,7 +3007,7 @@ msgstr ""
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -2997,21 +3015,21 @@ msgid ""
 "\n"
 msgstr ""
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
 "\n"
 msgstr ""
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 msgstr ""
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3023,7 +3041,7 @@ msgid ""
 "\n"
 msgstr ""
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3032,70 +3050,70 @@ msgid ""
 "\n"
 msgstr ""
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
 msgstr ""
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr ""
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr ""
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
 "\n"
 msgstr ""
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr ""
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr ""
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr ""
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr ""
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr ""
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr ""
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr ""
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr ""
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr ""
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr ""
@@ -3150,7 +3168,7 @@ msgstr ""
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr ""
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr ""
@@ -3200,68 +3218,63 @@ msgstr ""
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr ""
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr ""
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr ""
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
 "\n"
 msgstr ""
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
 "\n"
 msgstr ""
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr ""
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr ""
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr ""
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
 "\t# Functions, listed alphabetically\n"
 msgstr ""
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr ""
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr ""
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3330,6 +3343,6 @@ msgstr ""
 msgid "No previous regular expression"
 msgstr ""
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr ""
diff --git a/po/it.gmo b/po/it.gmo
index 2cb0e347..73f46395 100644
--- a/po/it.gmo
+++ b/po/it.gmo
diff --git a/po/it.po b/po/it.po
index 5e2c5a1b..68f2d7f0 100644
--- a/po/it.po
+++ b/po/it.po
@@ -6,8 +6,8 @@ msgid ""
 msgstr ""
 "Project-Id-Version: GNU Awk 4.0.73, API: 0.0\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
-"PO-Revision-Date: 2013-05-10 11:52+0100\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-01-15 10:39+0100\n"
 "Last-Translator: Antonio Colombo <azc100@gmail.com>\n"
 "Language-Team: Italian <it@li.org>\n"
 "Language: it\n"
@@ -15,92 +15,92 @@ msgstr ""
 "Content-Type: text/plain; charset=ISO-8859-1\n"
 "Content-Transfer-Encoding: 8-bit\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "da %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "tentativo di usare valore scalare come vettore"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "tentativo di usare il parametro scalare `%s' come un vettore"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "tentativo di usare scalare '%s' come vettore"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "tentativo di usare vettore `%s' in un contesto scalare"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: indice `%s' non presente nel vettore `%s'"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "tentativo di usare scalare`%s[\"%.*s\"]' come vettore"
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr "adump: primo argomento non-vettoriale"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: secondo argomento non-vettoriale"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: secondo argomento non-vettoriale"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: primo argomento non-vettoriale"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: primo argomento non-vettoriale"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asort: non consentito un secondo argomento che sia un sottovettore del primo "
 "argomento"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asorti: non consentito un secondo argomento che sia un sottovettore del "
 "primo argomento"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asort: non consentito un primo argomento che sia un sottovettore del secondo "
 "argomento"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asorti: non consentito un primo argomento che sia un sottovettore del "
 "secondo argomento"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "`%s' non � un nome funzione valido"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "funzione di confronto del sort `%s' non definita"
@@ -141,11 +141,11 @@ msgstr "valori di `case' doppi all'interno di uno `switch': %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "valori di default doppi all'interno di uno `switch'"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "`break' non consentito fuori da un ciclo o da uno `switch'"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "`continue' non consentito fuori da un un ciclo"
 
@@ -236,271 +236,271 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr "espressione indice invalida"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "attenzione: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "fatale: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "carattere 'a capo' o fine stringa non previsti"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "non riesco ad aprire file sorgente `%s' in lettura (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "non riesco ad aprire shared library `%s' in lettura (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "ragione indeterminata"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr "non riesco a includere `%s' per usarlo come file di programma"
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "file sorgente `%s' gi� incluso"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
 msgstr "shared library `%s' gi� inclusa"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include � un'estensione gawk"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "nome-file mancante dopo @include"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr "@load � un'estensione gawk"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
 msgstr "nome-file mancante dopo @include"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "programma nullo sulla riga comandi"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "non riesco a leggere file sorgente `%s' (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "file sorgente `%s' vuoto"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "file sorgente non termina con carattere 'a capo'"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr "espressione regolare non completata termina con `\\' a fine file"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "%s: %d: modificatore di espressione regolare tawk `/.../%c' non valido in "
 "gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "modificatore di espressione regolare tawk `/.../%c' non valido in gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "espressione regolare non completata"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "espressione regolare non completata a fine file"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "uso di `\\ #...' continuazione riga non portabile"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "'\\' non � l'ultimo carattere della riga"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX non permette l'operatore `**='"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "il vecchio awk non supporta l'operatore `**='"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX non permette l'operatore `**'"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "il vecchio awk non supporta l'operatore `**'"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "l'operatore `^=' non � supportato nel vecchio awk"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "l'operatore `^' non � supportato nel vecchio awk"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "stringa non terminata"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "carattere '%c' non valido in un'espressione"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "`%s' � un'estensione gawk"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX non permette `%s'"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "`%s' non � supportato nel vecchio awk"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "`goto' considerato pericoloso!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d non valido come numero di argomenti per %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr "%s: una stringa come ultimo argomento di `substitute' non ha effetto"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "il terzo parametro di '%s'  non � un oggetto modificabile"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: il terzo argomento � un'estensione gawk"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: il secondo argomento � un'estensione gawk"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "uso scorretto di dcgettext(_\"...\"): togliere il carattere '_' iniziale"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "uso scorretto di dcngettext(_\"...\"): togliere il carattere '_' iniziale"
 
-#: awkgram.y:3992
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
 msgstr "index: espressione regolare come secondo argomento non consentita"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "funzione `%s': parametro `%s' nasconde variabile globale"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "non riesco ad aprire `%s' in scrittura (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "mando lista variabili a 'standard error'"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: `close' non riuscita (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() chiamata due volte!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "c'erano variabili nascoste."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "funzione di nome `%s' definita in precedenza"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr ""
 "funzione `%s': non � possibile usare nome della funzione come nome parametro"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "funzione `%s': non � possibile usare la variabile speciale `%s' come "
 "parametro di funzione"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "funzione `%s': parametro #%d, `%s', duplica parametro #%d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "funzione `%s' chiamata ma mai definita"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "funzione `%s' definita ma mai chiamata direttamente"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr ""
 "espressione regolare di valore costante per parametro #%d genera valore "
 "booleano"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -509,234 +509,246 @@ msgstr ""
 "funzione `%s' chiamata con spazio tra il nome e `(',\n"
 "o usata come variabile o vettore"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "tentativo di dividere per zero"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "tentativo di dividere per zero in `%%'"
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+"impossibile assegnare un valore al risultato di un'espressione di post-"
+"incremento di un campo"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "destinazione di assegnazione non valida (codice operativo %s)"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s a \"%s\" non riuscita (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "standard output"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: argomento non-numerico"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: argomento %g fuori intervallo"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: non riesco a scaricare: `pipe' `%s' aperta in lettura, non in "
 "scrittura"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: non riesco a scaricare: file `%s' aperto in lettura, non in scrittura"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: `%s' non � un file aperto, una `pipe' o un co-processo"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: il primo argomento non � una stringa"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: il secondo argomento non � una stringa"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: argomento non-numerico"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: l'argomento fornito � un vettore"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "`length(array)' � un'estensione gawk"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: l'argomento non � una stringa"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: argomento non-numerico"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: argomento negativo %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "fatale: `count$' va usato per ogni `format' o per nessuno"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "larghezza campo ignorata per la specifica `%%'"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "precisione ignorata per la specifica `%%'"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "larghezza campo e precisone ignorate per la specifica `%%'"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "fatale: operatore `$' non consentito nei `format' awk"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "fatale: numero argomenti con `$' dev'essere > 0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr "fatale: numero argomenti %ld > del numero totale argomenti specificati"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "fatale: `$' non consentito dopo il punto in un `format'"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr "fatale: manca `$' per i campi posizionali larghezza o precisione"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "`l' non ha senso nei `format' awk; ignorato"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "fatale: `l' non consentito nei `format' POSIX awk"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "`L' non ha senso nei `format' awk; ignorato"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "`L' non ha senso nei `format' awk; ignorato"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "`h' non ha senso nei `format' awk; ignorato"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "fatale: `h' non consentito nei `format' POSIX awk"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: valore %g fuori intervallo per il `format' `%%%c'"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "carattere di `format' sconosciuto `%c' ignorato: nessun argomento convertito"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr ""
 "fatale: argomenti in numero minore di quelli richiesti dalla stringa di "
 "`format'"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "^ esauriti a questo punto"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: specifica di `format' senza un carattere di controllo"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "troppi argomenti specificati per questa stringa di `format'"
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr "sprintf: nessun argomento"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: nessun argomento"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: argomento non-numerico"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: chiamata con argomento negativo %g"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: lunghezza %g non >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: lunghezza %g non >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: lunghezza non intera %g: sar� troncata"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr "substr: lunghezza %g troppo elevata per indice stringa, tronco a %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: indice di partenza %g non valido, uso 1"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: indice di partenza non intero %g: sar� troncato"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: stringa di partenza lunga zero"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: indice di partenza %g oltre la fine della stringa"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -744,187 +756,187 @@ msgstr ""
 "substr: lunghezza %g all'indice di partenza %g supera la lunghezza del primo "
 "argomento (%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 "strftime: il valore del `format' in PROCINFO[\"strftime\"] � di tipo numerico"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: secondo argomento non-numerico"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr "strftime: secondo argomento < 0 o troppo elevato per time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: il primo argomento non � una stringa"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: `format' � una stringa nulla"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: l'argomento non � una stringa"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: almeno un valore � fuori dall'intervallo di default"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "funzione 'system' non consentita in modo `sandbox'"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: l'argomento non � una stringa"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "riferimento a variabile non inizializzata `$%d'"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: l'argomento non � una stringa"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: l'argomento non � una stringa"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: primo argomento non-numerico"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: secondo argomento non-numerico"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: argomento non-numerico"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: argomento non-numerico"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: argomento non-numerico"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: terzo argomento non-vettoriale"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: il terzo argomento � 0, trattato come 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: primo argomento non-numerico"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: secondo argomento non-numerico"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%f, %f): valori negativi daranno risultati strani"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%f, %f): valori decimali saranno troncati"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr "lshift(%f, %f): valori troppo alti daranno risultati strani"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: primo argomento ricevuto non-numerico"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: secondo argomento non-numerico"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%f, %f): valori negativi daranno risultati strani"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%f, %f): valori decimali saranno troncati"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr "rshift(%f, %f): valori troppo alti daranno risultati strani"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr "and: chiamata con meno di due argomenti"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "and: argomento %d non-numerico"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr "and: argomento %d, valore negativo %g dar� risultati strani"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
 msgstr "or: chiamata con meno di due argomenti"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "or: argomento %d non-numerico"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "or: argomento %d, valore negativo %g dar� risultati strani"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr "xor: chiamata con meno di due argomenti"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "xor: argomento %d non-numerico"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor: argomento %d, valore negativo %g dar� risultati strani"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: argomento non-numerico"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%f): valore negativo, dar� risultati strani"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%f): valori decimali saranno troncati"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: `%s' non � una categoria `locale' valida"
@@ -1051,8 +1063,8 @@ msgstr "clear [[nome-file:]N|funzione] - togli breakpoint impostati prima."
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 "commands [num] - inizia una lista di comandi da eseguire se si raggiunge un "
 "breakpoint (watchpoint)."
@@ -1231,7 +1243,7 @@ msgstr "up [N] - spostati di N elementi dello stack verso l'alto."
 msgid "watch var - set a watchpoint for a variable."
 msgstr "watch var - imposta un watchpoint per una variabile."
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "errore: "
@@ -1269,97 +1281,97 @@ msgstr "carattere non valido"
 msgid "undefined command: %s\n"
 msgstr "comando non definito: %s\n"
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 "imposta o mostra il numero di righe da tenere nel file che contiene la "
 "storia comandi."
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr "imposta o mostra dimensioni finestra lista comandi"
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr "imposta o mostra file di outpu gawk"
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr "imposta o mostra prompt di debug"
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr "(dis)imposta o mostra salvataggio storia comandi (valore=on|off)."
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr "(dis)imposta o mostra salvataggio opzioni (valore=on|off)."
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr "(dis)imposta o mostra tracciamento istruzioni (valore=on|off)."
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr "programma non in esecuzione."
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "non riesco a leggere file sorgente `%s' (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "file sorgente `%s' vuoto.\n"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr "file sorgente non disponibile."
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "non riesco a leggere file di nome `%s' (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 "ATTENZIONE: file sorgente `%s' modificato dopo la compilazione del "
 "programma.\n"
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr "numero riga %d non ammesso; `%s' ha %d righe"
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "fine-file inattesa durante lettura file `%s', riga %d"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr "file sorgente `%s' modificato dopo l'inizio esecuzione del programma."
 
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr "File sorgente corrente: %s\n"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr "Numero di righe: %d\n"
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr "File sorgente (righe): %s (%d)\n"
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
@@ -1367,54 +1379,54 @@ msgstr ""
 "Numero  Disp  Abilit.  Posizione\n"
 "\n"
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr "\tn. di occorrenze = %ld\n"
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr "\tignora prossime %ld occorrenze\n"
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr "\tcondizione per stop: %s\n"
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr "\tcomandi:\n"
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr "Elemento corrente: "
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr "Chiamato da elemento: "
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr "Chiamante di elemento: "
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr "Assente in main().\n"
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr "Nessun argomento.\n"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr "Nessun `locale'.\n"
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
@@ -1422,7 +1434,7 @@ msgstr ""
 "Tutte le variabili definite:\n"
 "\n"
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
@@ -1430,7 +1442,7 @@ msgstr ""
 "Tutte le funzioni definite:\n"
 "\n"
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
@@ -1438,7 +1450,7 @@ msgstr ""
 "Auto-visualizzazione variabili:\n"
 "\n"
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
@@ -1446,394 +1458,394 @@ msgstr ""
 "Variabili Watch [da tenere sott'occhio]:\n"
 "\n"
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "nessun simbolo `%s' nel contesto corrente\n"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr "`%s' non � un vettore\n"
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "%ld = variabile non inizializzata\n"
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr "vettore `%s' vuoto\n"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "[\"%s\"] non presente nel vettore `%s\n"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr "`%s[\"%s\"]' non � un vettore\n"
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "`%s' non � una variabile scalare"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "tentativo di usare vettore `%s[\"%s\"]' in un contesto scalare"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "tentativo di usare scalare `%s[\"%s\"]' come vettore"
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr "`%s' � una funzione"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr "watchpoint %d non soggetto a condizioni\n"
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr "Nessun elemento numerato da visualizzare %ld"
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr "Nessun elemento numerato watch [da sorvegliare] da visualizzare %ld"
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "%d: [\"%s\"] non presente nel vettore `%s'\n"
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr "tentativo di usare valore scalare come vettore"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr "Watchpoint %d cancellato perch� il parametro � fuori intervallo.\n"
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 "Visualizzazione %d cancellata perch� il parametro � fuori intervallo.\n"
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr " nel file `%s', riga %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr " a `%s':%d"
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr "#%ld\tin "
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr "Ulteriori elementi stack seguono...\n"
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr "numero elemento non valido"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Nota: breakpoint %d (abilitato, ignora prossimi %ld passaggi), anche "
 "impostato a %s:%d"
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr "Nota: breakpoint %d (abilitato), anche impostato a %s:%d"
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Nota: breakpoint %d (disabilitato, ignora prossimi %ld passaggi), anche "
 "impostato a %s:%d"
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr "Nota: breakpoint %d (disabilitato), anche impostato a %s:%d"
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr "Breakpoint %d impostato al file `%s', riga %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr "Non riesco a impostare breakpoint nel file `%s'\n"
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "numero riga %d nel file `%s' fuori intervallo"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr "Non riesco a trovare la regola!!!\n"
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr "Non riesco a impostare breakpoint a `%s':%d\n"
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr "Non riesco a impostare breakpoint nella funzione `%s'\n"
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr "breakpoint %d impostato al file `%s', riga %d � senza condizioni\n"
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr "Cancellato breakpoint %d"
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr "No breakpoint all'entrata nella funzione `%s'\n"
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "No breakpoint al file `%s', riga #%d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr "numero breakpoint non valido"
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr "Cancello tutti i breakpoint? (y oppure n) "
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr "y"
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr "Prossimi %ld passaggi dal breakpoint %d ignorati.\n"
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr "Far� uno stop al prossimo passaggio dal breakpoint %d.\n"
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr "Debug possibile solo per programmi con opzione `-f' specificata.\n"
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr "Non sono riuscito a far ripartire il debugger"
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr "Programma gi� in esecuzione. Lo faccio ripartire dall'inizio (y/n)? "
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr "Programma non fatto ripartire\n"
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr "errore: non riesco a far ripartire, operazione non consentita\n"
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr "errore (%s): non riesco a far ripartire, ignoro i comandi rimanenti\n"
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr "Partenza del programma: \n"
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr "Programma %s eseguit, valore in uscita: %d\n"
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr "Il programma � in esecuzione. Esco comunque (y/n)? "
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr "Non interrotto ad alcun breakpoint: argomento ignorato.\n"
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr "numero di breakpoint non valido %d."
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr "Prossimi %ld passaggi dal breakpoint %d ignorati.\n"
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr "'finish' non significativo nell'elemento iniziale main()\n"
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr "Esegui fino al ritorno da "
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr "'return' non significativo nell'elemento iniziale main()\n"
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr "Non trovo la posizione specificata nella funzione `%s'\n"
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "riga sorgente invalida %d nel file `%s'"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr "Non trovo posizione specificata %d nel file `%s'\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr "elemento non presente nel vettore\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr "variabile di tipo sconosciuto\n"
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr "Mi fermo in %s ...\n"
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr "'finish' not significativo per salti non-locali '%s'\n"
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr "'until' not significativo per salti non-locali '%s'\n"
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr "\t------[Invio] per continuare o q [Invio] per uscire------"
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr "q"
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "[\"%s\"] non presente nel vettore `%s'"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr "output inviato a stdout\n"
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr "numero non valido"
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "`%s' non consentito nel contesto corrente; istruzione ignorata"
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "`return' non consentito nel contesto corrente; istruzione ignorata"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr "Simbolo `%s' non esiste nel contesto corrente"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr "[ non chiusa"
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr "character class non valida"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr "sintassi character class � [[:spazio:]], non [:spazio:]"
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr "sequenza escape \\ non completa"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Contenuto di \\{\\} non valido"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Espressione regolare troppo complessa"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr "( non chiusa"
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr "nessuna sintassi specificata"
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ") non aperta"
 
@@ -1852,11 +1864,11 @@ msgstr "codice operativo sconosciuto %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "codice operativo %s non � un operatore o una parola chiave"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "superamento limiti buffer in 'genflags2str'"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1867,71 +1879,71 @@ msgstr ""
 "\t# `Stack' (Pila) Chiamate Funzione:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "`IGNORECASE' � un'estensione gawk"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "`BINMODE' � un'estensione gawk"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "valore di BINMODE `%s' non valido, considerato come 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "specificazione invalida `%sFMT' `%s'"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "disabilito `--lint' a causa di assegnamento a `LINT'"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "riferimento ad argomento non inizializzato `%s'"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "riferimento a variabile non inizializzata `%s'"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "tentativo di riferimento a un campo da valore non-numerico"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "tentativo di riferimento a un campo da una stringa nulla"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "tentativo di accedere al campo %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "riferimento a campo non inizializzato `$%ld'"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "funzione `%s' chiamata con pi� argomenti di quelli previsti"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: tipo non previsto `%s'"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "divisione per zero tentata in `/='"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "divisione per zero tentata in `%%='"
@@ -1944,7 +1956,7 @@ msgstr "le estensioni non sono consentite in modo `sandbox'"
 msgid "-l / @load are gawk extensions"
 msgstr "-l / @load sono estensioni gawk"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr "load_ext: nome libreria ricevuto � NULL"
 
@@ -1975,6 +1987,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "`extension' � un'estensione gawk"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "extension: nome libreria ricevuto � NULL"
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1996,37 +2012,37 @@ msgstr "extension: libreria `%s': non riesco a chiamare funzione `%s' (%s)"
 msgid "make_builtin: missing function name"
 msgstr "make_builtin: manca nome di funzione"
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "make_builtin: non riesco a ridefinire funzione `%s'"
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "make_builtin: funzione `%s' gi� definita"
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "make_builtin: funzione di nome `%s' definita in precedenza"
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 "make_builtin: nome funzione interna gawk `%s' non ammesso come nome funzione"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: contatore argomenti negativo per la funzione `%s'"
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr "extension: manca nome di funzione"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: carattere non ammesso `%c' nel nome di funzione `%s'"
@@ -2052,139 +2068,143 @@ msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr ""
 "extension: nome funzione interna gawk `%s' non ammesso come nome funzione"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "funzione `%s' definita per avere al massimo %d argomenti(o)"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "funzione `%s': manca argomento #%d"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr "funzione `%s': argomento #%d: tentativo di usare scalare come vettore"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr "funzione `%s': argomento #%d: tentativo di usare vettore come scalare"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr "caricamento dinamico di libreria non supportato"
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "chdir: chiamata con numero di argomenti errato, 1 previsto"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr "stat: non riesco a leggere il link simbolico `%s'"
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr "stat: chiamata con numero di argomenti errato"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr "stat: parametri errati"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr "ftp init: non riesco a creare variabile %s"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "fts non disponibile su questo sistema"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr "fill_stat_element: non riesco a creare vettore"
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr "fill_stat_element: non riesco a impostare elemento"
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr "fill_path_element: non riesco a impostare elemento"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr "fill_error_element: non riesco a impostare elemento"
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr "fts-process: non riesco a creare vettore"
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr "fts-process: non riesco a impostare elemento"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "fts: chiamata con numero di argomenti errato, 3 previsti"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr "fts: primo parametro errato"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr "fts: secondo parametro errato"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr "fts: terzo parametro errato"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr "fts: non sono riuscito a appiattire un vettore\n"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr "fts: ignoro flag infido FTS_NOSTAT. nooo, nooo, nooo."
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr "fts: clear_array() non riuscita\n"
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr "fnmatch: chiamata con meno di tre argomenti"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr "fnmatch: chiamata con pi� di tre argomenti"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr "fnmatch: primo argomento non disponibile"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr "fnmatch: secondo argomento non disponibile"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr "fnmatch: terzo argomento non disponibile"
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr "fnmatch non disponibile su questo sistema\n"
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr "fnmatch init: non riesco ad aggiungere variabile FNM_NOMATCH"
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr "fnmatch init: non riesco a impostare elemento vettoriale %s"
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr "fnmatch init: non riesco a installare vettore FNM"
 
@@ -2208,91 +2228,91 @@ msgstr "wait: chiamata senza argomenti"
 msgid "wait: called with too many arguments"
 msgstr "wait: chiamata con troppi argomenti"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr "inplace_begin: modifica in-place gi� attiva"
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr "inplace_begin: 2 argumenti richiesti, ma chiamata con %d"
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 "inplace_begin: non riesco a trovare il 1� argomento come stringa nome-file"
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 "inplace_begin: modifica in-place disabilitato, FILENAME non valido `%s'"
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "inplace_begin: Non riesco a trovare `%s' (%s)"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "inplace_begin: `%s' non � un file regolare"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr "inplace_begin: mkstemp(`%s') non riuscita (%s)"
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "inplace_begin: chmod non riuscita (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr "inplace_begin: dup(stdout) non riuscita (%s)"
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_begin: dup2(%d, stdout) non riuscita (%s)"
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "inplace_begin: close(%d) non riuscita (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 "inplace_end: non riesco a trovare il 1� argomento come stringa nome-file"
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr "inplace_end: modifica in-place non attiva"
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_end: dup2(%d, stdout) non riuscita (%s)"
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "inplace_end: close(%d) non riuscita (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr "inplace_end: fsetpos(stdout) non riuscita (%s)"
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "inplace_end: link(`%s', `%s') non riuscita (%s)"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "inplace_end: rename(`%s', `%s') non riuscito (%s)"
@@ -2321,175 +2341,175 @@ msgstr "chr: chiamata senza argomenti"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "chr: chiamata con argomento/i non corretto/i"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr "dir_take_control_of: opendir/fdopendir non riuscita: %s"
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr "readfile: chiamata con troppi argomenti"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr "readfile: chiamata senza argomenti"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr "writea: chiamata con troppi argomenti"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "do_writea: argomento 0 non � una stringa\n"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "do_writea: argomento 1 non-vettoriale\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr "write_array: non sono riuscito a appiattire un vettore\n"
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr "write_array: non sono riuscito a rilasciare un vettore appiattito\n"
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr "reada: chiamata con troppi argomenti"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "do_reada: argomento 0 non � una stringa\n"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "do_reada: argomento 1 non-vettoriale\n"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr "do_reada: clear_array non riuscita\n"
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr "read_array: set_array_element non riuscita\n"
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr "gettimeofday: ignoro argomenti"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr "gettimeofday: non supportato in questa architettura"
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr "sleep: chiamata con troppi argomenti"
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr "sleep: manca necessario argomento numerico"
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr "sleep: l'argomento � negativo"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr "sleep: non supportato in questa architettura"
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF impostato a un valore negativo"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: il quarto argomento � un'estensione gawk"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: quarto argomento non-vettoriale"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: secondo argomento non-vettoriale"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 "split: non si pu� usare un unico vettore come secondo e quarto argomento"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split: non consentito un quarto argomento che sia un sottovettore del "
 "secondo argomento"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split: non consentito un secondo argomento che sia un sottovettore del "
 "quarto argomento"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: la stringa nulla come terzo arg. � un'estensione gawk"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: secondo argomento non-vettoriale"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: secondo argomento non-vettoriale"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: il terzo argomento non pu� essere nullo"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit: non si pu� usare un unico vettore come secondo e quarto argomento"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit: non consentito un quarto argomento che sia un sottovettore del "
 "secondo argomento"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit: non consentito un secondo argomento che sia un sottovettore del "
 "quarto argomento"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "`FIELDWIDTHS' � un'estensione gawk"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "valore di FIELDWIDTHS non valido, vicino a `%s'"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "la stringa nulla usata come `FS' � un'estensione gawk"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "il vecchio awk non supporta espressioni come valori di `FS'"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "`FPAT' � un'estensione gawk"
 
@@ -2505,366 +2525,366 @@ msgstr "node_to_awk_value: ricevuto nodo nullo"
 msgid "node_to_awk_value: received null val"
 msgstr "node_to_awk_value: ricevuto valore nullo"
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr "remove_element: ricevuto vettore nullo"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr "remove_element: ricevuto indice nullo"
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr "api_flatten_array: non sono riuscito a convertire l'indice %d\n"
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr "api_flatten_array: non sono riuscito a convertire il valore %d\n"
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: opzione '%s' ambigua; possibilit�:"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: l'opzione '--%s' non ammette un argomento\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: l'opzione '%c%s' non ammette un argomento\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: l'opzione '--%s' richiede un argomento\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: opzione sconosciuta '--%s'\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: opzione sconosciuta '%c%s'\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: opzione non valida -- '%c'\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: l'opzione richiede un argomento -- '%c'\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: l'opzione '-W %s' � ambigua\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: l'opzione '-W %s' non ammette un argomento\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: l'opzione '-W %s' richiede un argomento\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "l'argomento in linea comando `%s' � una directory: saltato"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "non riesco ad aprire file `%s' in lettura (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "chiusura di fd %d (`%s') non riuscita (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "re-direzione non consentita in modo `sandbox'"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "espressione nella re-direzione `%s' ha solo un valore numerico"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "espressione nella re-direzione `%s' ha per valore la stringa nulla"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "nome-file `%s' per la re-direzione `%s' pu� essere il risultato di una "
 "espressione logica"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "mistura non necessaria di `>' e `>>' per il file `%.*s'"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "non riesco ad aprire `pipe' `%s' in scrittura (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "non riesco ad aprire `pipe' `%s' in lettura (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr ""
 "non riesco ad aprire `pipe' bidirezionale `%s' in lettura/scrittura (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "non riesco a re-dirigere da `%s' (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "non riesco a re-dirigere a `%s' (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "numero massimo consentito di file aperti raggiunto: comincio a riutilizzare "
 "i descrittori di file"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "chiusura di `%s' non riuscita (%s)."
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "troppe `pipe' o file di input aperti"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: il secondo argomento deve essere `a' o `da'"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: `%.*s' non � un file aperto, una `pipe' o un co-processo"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "chiusura di una re-direzione mai aperta"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr "close: re-direzione `%s' non aperta con `|&', ignoro secondo argomento"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "errore ritornato (%d) dalla chiusura della `pipe' `%s' (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "errore ritornato (%d) dalla chiusura del file `%s' (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "nessuna chiusura esplicita richiesta per `socket' `%s'"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "nessuna chiusura esplicita richiesta per co-processo `%s'"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "nessuna chiusura esplicita richiesta per `pipe' `%s'"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "nessuna chiusura esplicita richiesta per file `%s'"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "errore scrivendo 'standard output' (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "errore scrivendo 'standard error' (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "scaricamento di `pipe' `%s' non riuscito (%s)."
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "scaricamento da co-processo di `pipe' a `%s' non riuscito (%s)."
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "scaricamento di file `%s' non riuscito (%s)."
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "porta locale %s invalida in `/inet'"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "host remoto e informazione di porta (%s, %s) invalidi"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr "nessuno protocollo (noto) specificato nel filename speciale `%s'"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "nome-file speciale `%s' incompleto"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "va fornito nome di `host' remoto a `/inet'"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "va fornita porta remota a `/inet'"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "comunicazioni TCP/IP non supportate"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "non riesco ad aprire `%s', modo `%s'"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "close di `pty' principale non riuscita (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "close di `stdout' nel processo-figlio non riuscita (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "trasferimento di `pty' secondaria a `stdout' nel processo-figlio non "
 "riuscita (dup: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "close di `stdin' nel processo-figlio non riuscita (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "trasferimento di 'pty' secondaria a 'stdin' nel processo-figlio non riuscito "
 "(dup: %s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "close di 'pty' secondaria non riuscita (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 "passaggio di `pipe' a `stdout' nel processo-figlio non riuscito (dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "passaggio di pipe a `stdin' nel processo-figlio  non riuscito (dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "ripristino di `stdout' nel processo-padre non riuscito\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "ripristino di `stdin' nel processo-padre non riuscito\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "close di 'pipe' non riuscita (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "`|&' non supportato"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "non riesco ad aprire `pipe' `%s' (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "non riesco a creare processo-figlio per `%s' (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr "register_input_parser: ricevuto puntatore NULL"
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 "input parser `%s' in conflitto con l'input parser `%s' installato in "
 "precedenza"
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr "l'input parser `%s' non � riuscito ad aprire `%s'"
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr "register_output_wrapper: ricevuto puntatore NULL"
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
@@ -2872,16 +2892,16 @@ msgstr ""
 "output wrapper `%s' in conflitto con l'output wrapper `%s' installato in "
 "precedenza"
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr "l'output wrapper `%s' non � riuscito ad aprire `%s'"
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr "register_output_processor: ricevuto puntatore NULL"
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
@@ -2890,209 +2910,209 @@ msgstr ""
 "processore doppio `%s' in conflitto con il processore doppio installato in "
 "precedenza `%s'"
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr "il processore doppio `%s' non � riuscito ad aprire `%s'"
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "file dati `%s' vuoto"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "non riesco ad allocare ulteriore memoria per l'input"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "valore multicarattere per `RS' � un'estensione gawk"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "comunicazioni IPv6 non supportate"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "argomento di `-e/--source' nullo, ignorato"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: opzione `-W %s' non riconosciuta, ignorata\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: l'opzione richiede un argomento -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr "variable d'ambiente `POSIXLY_CORRECT' impostata: attivo `--posix'"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "`--posix' annulla `--traditional'"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr "`--posix'/`--traditional' annulla `--non-decimal-data'"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "eseguire %s con `setuid' root pu� essere un rischio per la sicurezza"
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "`--posix' annulla `--characters-as-bytes'"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "non � possibile impostare modalit� binaria su `stdin'(%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "non � possibile impostare modalit� binaria su `stdout'(%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "non � possibile impostare modalit� binaria su `stderr'(%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "manca del tutto il testo del programma!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr "Uso: %s [opzioni in stile POSIX o GNU] -f file-prog. [--] file ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr "Usage: %s [opzioni in stile POSIX o GNU] [--] %cprogramma%c file ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "Opzioni POSIX:\t\topzioni lunghe GNU: (standard)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f fileprog\t\t--file=file-prog.\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=valore\t\t--assign=var=valore\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "Opzioni brevi:\t\topzioni lunghe GNU: (estensioni)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[file]\t\t--dump-variables[=file]\n"
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-D[file]\t\t--debug[=file]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'testo-del-programma'\t--source='testo-del-programma'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E file\t\t\t--exec=file\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr "\t-i include_file\t\t--include=include_file\n"
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr "\t-l libreria\t\t--load=libreria\n"
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-o[file]\t\t--pretty-print[=file]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[file]\t\t--profile[=file]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3101,7 +3121,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3114,7 +3134,7 @@ msgstr ""
 "Problemi di traduzione, segnalare ad: azc100@gmail.com.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3124,7 +3144,7 @@ msgstr ""
 "Senza parametri, legge da 'standard input' e scrive su 'standard output'.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3134,7 +3154,7 @@ msgstr ""
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3153,7 +3173,7 @@ msgstr ""
 "Licenza, o (a tua scelta) a una qualsiasi versione successiva.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3167,7 +3187,7 @@ msgstr ""
 "Vedi la 'GNU General Public License' per ulteriori dettagli.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3176,16 +3196,16 @@ msgstr ""
 "assieme a questo programma; se non � cos�, vedi http://www.gnu.org/"
 "licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft non imposta FS a `tab' nell'awk POSIX"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "valore non noto per specifica campo: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3194,48 +3214,48 @@ msgstr ""
 "%s: `%s' argomento di `-v' non in forma `var=valore'\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "`%s' non � un nome di variabile ammesso"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "`%s' non � un nome di variabile, cerco il file `%s=%s'"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "nome funzione interna gawk `%s' non ammesso come nome variabile"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "non � possibile usare nome di funzione `%s' come nome di variabile"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "eccezione floating point"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "errore fatale: errore interno"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "errore fatale: errore interno: segfault"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "errore fatale: errore interno: stack overflow"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "manca `fd' pre-aperta %d"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "non riesco a pre-aprire /dev/null per `fd' %d"
@@ -3290,7 +3310,7 @@ msgstr "%s: argomento #%d, valore decimale sar� troncato"
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "%s: argomento #%d con valore negativo %Zd, dar� risultati strani"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "linea com.:"
@@ -3345,16 +3365,16 @@ msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr ""
 "%s %s `%s': non riesco a impostare 'close-on-exec': (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "non riesco ad aprire `%s' in scrittura: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "mando profilo a 'standard error'"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3363,7 +3383,7 @@ msgstr ""
 "\t# blocco(hi) %s\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3372,16 +3392,16 @@ msgstr ""
 "\t# Regola(e)\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "errore interno: %s con `vname' nullo"
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr "errore interno: funzione interna con `fname' nullo"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
@@ -3390,12 +3410,12 @@ msgstr ""
 "\t# Estensioni caricate (-l e/o @load)\n"
 "\n"
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# profilo gawk, creato %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3404,17 +3424,12 @@ msgstr ""
 "\n"
 "\t# Funzioni, in ordine alfabetico\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: tipo di re-direzione non noto %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "intervallo della forma `[%c-%c]' dipende da `locale'"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3484,6 +3499,9 @@ msgstr ") o \\) non aperta"
 msgid "No previous regular expression"
 msgstr "Nessuna espressione regolare precedente"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr "non posso salire pi� in alto nello stack"
+
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "intervallo della forma `[%c-%c]' dipende da `locale'"
diff --git a/po/ja.gmo b/po/ja.gmo
index faca679e..d1ef30cc 100644
--- a/po/ja.gmo
+++ b/po/ja.gmo
diff --git a/po/ja.po b/po/ja.po
index 756f3548..ae5b61c8 100644
--- a/po/ja.po
+++ b/po/ja.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: gawk 4.0.0\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
 "PO-Revision-Date: 2011-07-17 08:28+0900\n"
 "Last-Translator: Yasuaki Taniguchi <yasuakit@gmail.com>\n"
 "Language-Team: Japanese <translation-team-ja@lists.sourceforge.net>\n"
@@ -18,85 +18,85 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "%s から"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "スカラー値を配列として使用する試みです"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "スカラー仮引数 `%s' を配列として使用する試みです"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "スカラー `%s' を配列として使用する試みです"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "スカラーコンテキストで配列 `%s' を使用する試みです"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: 配列 `%2$s' 内にインデックス `%1$s' がありません"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "スカラー `%s[\"%.*s\"]' を配列として使用する試みです"
 
-#: array.c:773
+#: array.c:776
 #, fuzzy
 msgid "adump: first argument not an array"
 msgstr "adump: 引数が配列ではありません"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: 第二引数が配列ではありません"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: 第二引数が配列ではありません"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: 第一引数が配列ではありません"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: 第一引数が配列ではありません"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr "asort: 第一引数の部分配列を第二引数用に使用することは出来ません"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr "asorti: 第一引数の部分配列を第二引数用に使用することは出来ません"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr "asort: 第二引数の部分配列を第一引数用に使用することは出来ません"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr "asorti: 第二引数の部分配列を第一引数用に使用することは出来ません"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "`%s' は関数名としては無効です"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "ソート比較関数 `%s' が定義されていません"
@@ -137,11 +137,11 @@ msgstr "switch 文の中で重複した case 値が使用されています: %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "switch 文の中で重複した `default' が検出されました"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "`break' はループまたは switch の外では許可されていません"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "`continue' はループの外では許可されていません"
 
@@ -231,269 +231,269 @@ msgstr "特別な変数 `%s' は間接関数呼び出し用には使用出来ま
 msgid "invalid subscript expression"
 msgstr "添字の式が無効です"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "警告: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "致命的: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "予期しない改行または文字列終端です"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "ソースファイル `%s' を読み込み用に開けません (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, fuzzy, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "ソースファイル `%s' を読み込み用に開けません (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "原因不明"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr ""
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "ソースファイル `%s' は既に読み込まれています"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, fuzzy, c-format
 msgid "already loaded shared library `%s'"
 msgstr "ソースファイル `%s' は既に読み込まれています"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include は gawk 拡張です"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "@include の後に空のファイル名があります"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 #, fuzzy
 msgid "@load is a gawk extension"
 msgstr "@include は gawk 拡張です"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 #, fuzzy
 msgid "empty filename after @load"
 msgstr "@include の後に空のファイル名があります"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "コマンド行のプログラム表記が空です"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "ソースファイル `%s' を読み込めません (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "ソースファイル `%s' は空です"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "ソースファイルが改行で終っていません"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr "終端されていない正規表現がファイル最後の `\\' で終っています。"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "%s: %d: tawk の正規表現修飾子 `/.../%c' は gawk で使用できません"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "tawk の正規表現修飾子 `/.../%c' は gawk で使用できません"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "正規表現が終端されていません"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "ファイルの中で正規表現が終端されていません"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "`\\ #...' 形式の行継続は移植性がありません"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "バックスラッシュが行最後の文字になっていません。"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX では演算子 `**=' は許可されていません"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "古い awk は演算子 `**=' をサポートしません"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX では演算子 `**' は許可されていません"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "古い awk は演算子 `**' をサポートしません"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "古い awk は演算子 `^=' をサポートしません"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "古い awk は演算子 `^' をサポートしません"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "文字列が終端されていません"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "式内に無効な文字 '%c' があります"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "`%s' は gawk 拡張です"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX では `%s' は許可されていません"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "古い awk は `%s' をサポートしません"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "`goto' は有害だと見なされています!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d は %s 用の引数の数としては無効です"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr "%s: 文字列リテラルを置き換え最後の引数に使用すると効果がありません"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "%s 第三仮引数は可変オブジェクトではありません"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: 第三引数は gawk 拡張です"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: 第二引数は gawk 拡張です"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "dcgettext(_\"...\")の使用法が間違っています: 先頭のアンダースコア(_)を削除し"
 "てください"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "dcngettext(_\"...\")の使用法が間違っています: 先頭のアンダースコア(_)を削除し"
 "てください"
 
-#: awkgram.y:3992
+#: awkgram.y:4016
 #, fuzzy
 msgid "index: regexp constant as second argument is not allowed"
 msgstr "index: 文字列では無い第二引数を受け取りました"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "関数 `%s': 仮引数 `%s' が大域変数を覆い隠しています"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "`%s' を書込み用に開けませんでした (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "変数リストを標準エラーに送っています"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: 閉じるのに失敗しました (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() を二回呼び出しています!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "覆い隠された変数がありました"
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "関数名 `%s' は前に定義されています"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr "関数 `%s': 関数名を仮引数名として使用出来ません"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr "関数 `%s': 特別な変数 `%s' は関数の仮引数として使用出来ません"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "関数 `%s': 仮引数 #%d, `%s' が仮引数 #%d と重複しています"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "未定義の関数 `%s' を呼び出しました"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "関数 `%s' は定義されていますが、一度も直接呼び出されていません"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "仮引数 #%d 用の正規表現定数は真偽値を出力します"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -502,235 +502,245 @@ msgstr ""
 "関数名と `(' の間にスペースを入れて関数 `%s' を呼び出しています。\n"
 "または、変数か配列として使われています。"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "ゼロによる除算が試みられました"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "`%%' 内でゼロによる除算が試みられました"
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+
+#: awkgram.y:5052
+#, fuzzy, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "%d は %s 用の引数の数としては無効です"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s から \"%s\" へ出力できません (%s)。"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "標準出力"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: 引数が数値ではありません"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: flush できません: パイプ `%s' は読み込み用に開かれています。書き込み"
 "用ではありません"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: flush できません: ファイル `%s' は読み込み用に開かれています。書き込"
 "み用ではありません"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: `%s' が開かれたファイル、パイプ、プロセス共有ではありません"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: 文字列では無い第一引数を受け取りました"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: 文字列では無い第二引数を受け取りました"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: 数値では無い引数を受け取りました"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: 配列引数を受け取りました"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "`length(array)' は gawk 拡張です"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: 文字列では無い引数を受け取りました"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: 数値では無い引数を受け取りました"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: 負の引数 %g を受け取りました"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr ""
 "致命的: `count$’ は全ての書式使用する、または全てに使用しないのいずれかでなけ"
 "ればいけません"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "`%%' 指定用のフィールド幅は無視されます"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "`%%' 指定用のフィールド幅は無視されます"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "`%%' 指定用のフィールド幅および精度は無視されます"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "致命的: `$' は awk 形式内では許可されていません"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "致命的: `$' で指定する引数の番号は正でなければいけません"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr "致命的: 引数の番号 %ld は引数として与えられた数より大きいです"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "致命的: `$' は書式指定内のピリオド `.' の後に使用できません"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr "致命的: フィールド幅、または精度の指定子に `$' が与えられていません"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "awk の書式指定では `l' は無意味です。無視します"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "致命的: POSIX awk 書式内では `l' は許可されていません"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "awk の書式指定では `L' は無意味です。無視します。"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "致命的: POSIX awk 書式内では `L' は許可されていません"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "awk の書式指定では `h' は無意味です。無視します。"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "致命的: POSIX awk 書式内では `h' は許可されていません"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: 値 %g は書式 `%%%c' の範囲外です"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr "不明な書式指定文字 `%c' を無視しています: 変換される引数はありません"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr "致命的: 書式文字列を満たす十分な数の引数がありません"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "^ ここから足りません"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: 書式指定子に制御文字がありません"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "書式文字列に与えられている引数が多すぎます"
 
-#: builtin.c:1610
+#: builtin.c:1634
 #, fuzzy
 msgid "sprintf: no arguments"
 msgstr "printf: 引数がありません"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: 引数がありません"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: 数値では無い引数を受け取りました"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: 長さ %g が 1 以上ではありません"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: 長さ %g が 0 以上ではありません"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: 文字数 %g の小数点以下は切り捨てます。"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr "substr: 文字数 %g は最大値を超えています。%g を使います。"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: 開始インデックス %g が無効です。1を使用します"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: 開始インデックス %g が非整数のため、値は切り捨てられます"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: 文字列の長さがゼロです。"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: 開始インデックス %g が文字列終端の後にあります"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -738,189 +748,189 @@ msgstr ""
 "substr: 開始インデックス %2$g からの長さ %1$g は第一引数の長さを超えています "
 "(%3$lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr "strftime: PROCINFO[\"strftime\"] の書式の値は数値型です"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: 非数値の第二引数を受け取りました"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr ""
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: 非文字列の第一引数を受け取りました"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: 空の書式文字列を受け取りました"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: 非文字列引数を受け取りました"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: 一つ以上の値がデフォルトの範囲を超えています"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "サンドボックスモードでは 'system' 関数は許可されていません"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: 文字列では無い引数を受け取りました"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "初期化されていないフィールド `$%d' への参照です"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: 非文字列引数を受け取りました"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: 非文字列引数を受け取りました"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: 非数値の第一引数を受け取りました"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: 非数値の第二引数を受け取りました"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: 非数値の引数を受け取りました"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: 非数値の引数を受け取りました"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: 非数値の引数を受け取りました"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: 第三引数が配列ではありません"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: 第三引数が 0 です。1 を代わりに使用します"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: 非数値の第一引数を受け取りました"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: 非数値の第二引数を受け取りました"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, fuzzy, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%lf, %lf): 負の数値を使用すると異常な結果になります"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, fuzzy, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%lf, %lf): 小数点以下は切り捨てられます"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, fuzzy, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr "lshift(%lf, %lf): シフト値が大き過ぎると異常な結果になります"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: 非数値の第一引数を受け取りました"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: 非数値の第二引数を受け取りました"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, fuzzy, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%lf, %lf): 負の数値を使用すると異常な結果になります"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, fuzzy, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%lf, %lf): 小数点以下は切り捨てられます"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, fuzzy, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr "rshift(%lf, %lf): シフト値が大き過ぎると異常な結果になります"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 #, fuzzy
 msgid "and: called with less than two arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, fuzzy, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, fuzzy, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr "and(%lf, %lf): 負の数値を使用すると異常な結果になります"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 #, fuzzy
 msgid "or: called with less than two arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, fuzzy, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, fuzzy, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "compl(%lf): 負の数値を使用すると異常な結果になります"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 #, fuzzy
 msgid "xor: called with less than two arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, fuzzy, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, fuzzy, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor(%lf, %lf): 負の数値を使用すると異常な結果になります"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: 非数値の引数を受け取りました"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, fuzzy, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%lf): 負の数値を使用すると異常な結果になります"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, fuzzy, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%lf): 小数点以下は切り捨てられます"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: `%s' は無効なロケール区分です"
@@ -1044,8 +1054,8 @@ msgstr ""
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 
 #: command.y:825
@@ -1202,7 +1212,7 @@ msgstr ""
 msgid "watch var - set a watchpoint for a variable."
 msgstr ""
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "エラー: "
@@ -1242,557 +1252,557 @@ msgstr "無効な照合文字です"
 msgid "undefined command: %s\n"
 msgstr ""
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr ""
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr ""
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr ""
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr ""
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr ""
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr ""
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, fuzzy, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "ソースファイル `%s' を読み込めません (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, fuzzy, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "ソースファイル `%s' は空です"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr ""
 
-#: debug.c:499
+#: debug.c:505
 #, fuzzy, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "ソースファイル `%s' を読み込めません (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr ""
 
-#: debug.c:602
+#: debug.c:611
 #, fuzzy, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "予期しない改行または文字列終端です"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr ""
 
-#: debug.c:723
+#: debug.c:732
 #, fuzzy, c-format
 msgid "Current source file: %s\n"
 msgstr "ソースファイル `%s' は既に読み込まれています"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr ""
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr ""
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr ""
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr ""
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr ""
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr ""
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr ""
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr ""
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr ""
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr ""
 
-#: debug.c:839
+#: debug.c:848
 #, fuzzy
 msgid "No arguments.\n"
 msgstr "printf: 引数がありません"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr ""
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:1020
+#: debug.c:1029
 #, fuzzy, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "`next' は `%s' から呼び出すことが出来ません"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, fuzzy, c-format
 msgid "`%s' is not an array\n"
 msgstr "`%s' は不正な変数名です"
 
-#: debug.c:1046
+#: debug.c:1055
 #, fuzzy, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "初期化されていないフィールド `$%d' への参照です"
 
-#: debug.c:1067
+#: debug.c:1076
 #, fuzzy, c-format
 msgid "array `%s' is empty\n"
 msgstr "データファイル `%s' は空です。"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "delete: 配列 `%2$s' 内にインデックス `%1$s' がありません"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr ""
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, fuzzy, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "`%s' は不正な変数名です"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, fuzzy, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "スカラーコンテキスト内で配列 `%s[\"%.*s\"]' の使用の試みです"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, fuzzy, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "スカラー `%s[\"%.*s\"]' を配列として使用する試みです"
 
-#: debug.c:1414
+#: debug.c:1423
 #, fuzzy, c-format
 msgid "`%s' is a function"
 msgstr "`%s' は関数名としては無効です"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr ""
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr ""
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr ""
 
-#: debug.c:1519
+#: debug.c:1528
 #, fuzzy, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "delete: 配列 `%2$s' 内にインデックス `%1$s' がありません"
 
-#: debug.c:1758
+#: debug.c:1767
 #, fuzzy
 msgid "attempt to use scalar value as array"
 msgstr "スカラー値を配列として使用する試みです"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr ""
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr ""
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr ""
 
-#: debug.c:2008
+#: debug.c:2017
 #, fuzzy
 msgid "invalid frame number"
 msgstr "無効な範囲終了です"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr ""
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, fuzzy, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr ""
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr ""
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr ""
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr ""
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr ""
 
-#: debug.c:2521
+#: debug.c:2541
 #, fuzzy, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "入力ファイル `%s' を読み込み中にエラーが発生しました: %s"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr ""
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr ""
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr ""
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr ""
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr ""
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr ""
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr ""
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr ""
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr ""
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr ""
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr ""
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr ""
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr ""
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr ""
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr ""
 
-#: debug.c:3357
+#: debug.c:3377
 #, fuzzy, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "ソースファイル `%s' は既に読み込まれています"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, fuzzy, c-format
 msgid "element not in array\n"
 msgstr "delete: 配列 `%2$s' 内にインデックス `%1$s' がありません"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr ""
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr ""
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr ""
 
-#: debug.c:4986
+#: debug.c:5001
 #, fuzzy, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "delete: 配列 `%2$s' 内にインデックス `%1$s' がありません"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr ""
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr ""
 
-#: debug.c:5366
+#: debug.c:5381
 #, fuzzy, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "`next' は `%s' から呼び出すことが出来ません"
 
-#: debug.c:5374
+#: debug.c:5389
 #, fuzzy
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "`next' は `%s' から呼び出すことが出来ません"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr ""
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr ""
 
-#: dfa.c:1052
+#: dfa.c:1174
 #, fuzzy
 msgid "invalid character class"
 msgstr "無効な文字クラス名です"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr ""
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr ""
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "\\{\\} の中身が無効です"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "正規表現が大きすぎます"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr ""
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr ""
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ""
 
@@ -1811,11 +1821,11 @@ msgstr "不明なオペコード %d です"
 msgid "opcode %s not an operator or keyword"
 msgstr "オペコード %s は演算子または予約語ではありません"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "genflags2str 内でバッファオーバーフローが発生しました"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1826,71 +1836,71 @@ msgstr ""
 "\t# 呼出関数スタック:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "`IGNORECASE' は gawk 拡張です"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "`BINMODE' は gawk 拡張です"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "BINMODE 値 `%s' は無効です。代わりに 3 を使用します"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "誤った `%sFMT' 指定 `%s' です"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "`LINT' への代入に従い `--lint' を無効にします"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "初期化されていない引数 `%s' への参照です"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "初期化されていない変数 `%s' への参照です"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "非数値を使用したフイールド参照の試みです"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "NULL 文字列を使用してフィールドの参照を試みています"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "フィールド %ld へのアクセスの試みです"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "初期化されていないフィールド `$%ld' への参照です"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "宣言されている数より多い引数を使って関数 `%s' を呼び出しました"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: 予期しない型 `%s' です"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "`/=' 内でゼロによる除算が行われました"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "`%%=' 内でゼロによる除算が行われました"
@@ -1904,7 +1914,7 @@ msgstr "サンドボックスモード内では拡張は許可されていませ
 msgid "-l / @load are gawk extensions"
 msgstr "@include は gawk 拡張です"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr ""
 
@@ -1937,6 +1947,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "`extension' は gawk 拡張です"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr ""
+
 #: ext.c:180
 #, fuzzy, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1962,37 +1976,37 @@ msgstr ""
 msgid "make_builtin: missing function name"
 msgstr "extension: 関数名がありません"
 
-#: ext.c:238
+#: ext.c:236
 #, fuzzy, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "extension: 関数 `%s' を再定義できません"
 
-#: ext.c:242
+#: ext.c:240
 #, fuzzy, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "extension: 関数 `%s' は既に定義されています"
 
-#: ext.c:246
+#: ext.c:244
 #, fuzzy, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "extension: 関数名 `%s' は前に定義されています"
 
-#: ext.c:248
+#: ext.c:246
 #, fuzzy, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr "extension: gawk に組み込まれている `%s' は関数名として使用出来ません"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: 関数 `%s' の引数の数が負です"
 
-#: ext.c:278
+#: ext.c:276
 #, fuzzy
 msgid "extension: missing function name"
 msgstr "extension: 関数名がありません"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, fuzzy, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: 関数名 `%2$s' の中で不正な文字 `%1$c' が使用されています"
@@ -2017,153 +2031,158 @@ msgstr "関数名 `%s' は前に定義されています"
 msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr "extension: gawk に組み込まれている `%s' は関数名として使用出来ません"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "関数 `%s' に使える引数の数は `%d' 以下と定義されています"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "関数 `%s': 引数 #%d がありません"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr "関数 `%s': 引数 #%d: スカラーを配列として使用する試みです"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr "関数 `%s': 引数 #%d: 配列をスカラーとして使用する試みです"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr ""
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 #, fuzzy
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr ""
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 #, fuzzy
 msgid "stat: called with wrong number of arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 #, fuzzy
 msgid "stat: bad parameters"
 msgstr "%s: 仮引数です\n"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, fuzzy, c-format
 msgid "fts init: could not create variable %s"
 msgstr "index: 文字列では無い第二引数を受け取りました"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+#, fuzzy
+msgid "fts is not supported on this system"
+msgstr "古い awk は `%s' をサポートしません"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 #, fuzzy
 msgid "fill_path_element: could not set element"
 msgstr "index: 文字列では無い第二引数を受け取りました"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 #, fuzzy
 msgid "fts-process: could not set element"
 msgstr "index: 文字列では無い第二引数を受け取りました"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 #, fuzzy
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 #, fuzzy
 msgid "fts: bad first parameter"
 msgstr "%s: 仮引数です\n"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 #, fuzzy
 msgid "fts: bad second parameter"
 msgstr "%s: 仮引数です\n"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 #, fuzzy
 msgid "fts: bad third parameter"
 msgstr "%s: 仮引数です\n"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 #, fuzzy
 msgid "fts: could not flatten array\n"
 msgstr "`%s' は不正な変数名です"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr ""
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr ""
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 #, fuzzy
 msgid "fnmatch: called with less than three arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 #, fuzzy
 msgid "fnmatch: called with more than three arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 #, fuzzy
 msgid "fnmatch: could not get first argument"
 msgstr "strftime: 非文字列の第一引数を受け取りました"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 #, fuzzy
 msgid "fnmatch: could not get second argument"
 msgstr "index: 文字列では無い第二引数を受け取りました"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr ""
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr ""
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr ""
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr ""
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr ""
 
@@ -2191,88 +2210,88 @@ msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 msgid "wait: called with too many arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr ""
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr ""
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, fuzzy, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "致命的: extension: `%s' を開くことが出来ません (%s)\n"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, fuzzy, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "`%s' は不正な変数名です"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, fuzzy, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "%s: 閉じるのに失敗しました (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, fuzzy, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "%s: 閉じるのに失敗しました (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr ""
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, fuzzy, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "%s: 閉じるのに失敗しました (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, fuzzy, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "パイプ `%s' をフラッシュできません (%s)。"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, fuzzy, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "fd %d (`%s') を閉じることができません (%s)"
@@ -2307,173 +2326,173 @@ msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr ""
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 #, fuzzy
 msgid "readfile: called with too many arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 #, fuzzy
 msgid "readfile: called with no arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 #, fuzzy
 msgid "writea: called with too many arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, fuzzy, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, fuzzy, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "split: 第四引数が配列ではありません"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr ""
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr ""
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 #, fuzzy
 msgid "reada: called with too many arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, fuzzy, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, fuzzy, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "match: 第三引数が配列ではありません"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr ""
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr ""
 
-#: extension/time.c:81
+#: extension/time.c:113
 #, fuzzy
 msgid "gettimeofday: ignoring arguments"
 msgstr "mktime: 非文字列引数を受け取りました"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr ""
 
-#: extension/time.c:133
+#: extension/time.c:165
 #, fuzzy
 msgid "sleep: called with too many arguments"
 msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
-#: extension/time.c:136
+#: extension/time.c:168
 #, fuzzy
 msgid "sleep: missing required numeric argument"
 msgstr "exp: 引数が数値ではありません"
 
-#: extension/time.c:142
+#: extension/time.c:174
 #, fuzzy
 msgid "sleep: argument is negative"
 msgstr "exp: 引数 %g が範囲外です"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr ""
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF が負の値に設定されています"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: 第四引数は gawk 拡張です"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: 第四引数が配列ではありません"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: 第二引数が配列ではありません"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr "split: 第二引数と第四引数に同じ配列を使用することは出来ません"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr "split: 第四引数に第二引数の部分配列を使用することは出来ません"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr "split: 第二引数に第四引数の部分配列を使用することは出来ません"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: 第三引数に NULL 文字列を使用することは gawk 拡張です"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: 第四引数が配列ではありません"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: 第二引数が配列ではありません"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: 第三引数は非 NULL でなければいけません"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr "patsplit: 第二引数と第四引数に同じ配列を使用することは出来ません"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr "patsplit: 第四引数に第二引数の部分配列を使用することは出来ません"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr "patsplit: 第二引数に第四引数の部分配列を使用することは出来ません"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "`FIELDWIDTHS' は gawk 拡張です"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "`%s' 付近の FIELDWIDTHS 値が無効です"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "`FS' に NULL 文字列を使用するのは gawk 拡張です"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "古い awk は `FS' の値として正規表現をサポートしません"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "`FPAT' は gawk 拡張です"
 
@@ -2489,596 +2508,596 @@ msgstr ""
 msgid "node_to_awk_value: received null val"
 msgstr ""
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 #, fuzzy
 msgid "remove_element: received null array"
 msgstr "length: 配列引数を受け取りました"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr ""
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr ""
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr ""
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, fuzzy, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: オプション '%s' は曖昧です\n"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: オプション '--%s' は引数を取ることができません\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: オプション '%c%s' は引数を取ることができません\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: オプション '--%s' には引数が必要です\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: オプション '--%s' を認識できません\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: オプション '%c%s' を認識できません\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: 無効なオプション -- '%c'\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: オプションには引数が必要です -- '%c'\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: オプション '-W %s' は曖昧です\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: オプション '-W %s' は引数を取ることができません\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: オプション '-W %s' には引数が必要です\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "コマンドライン引数 `%s' はディレクトリです: スキップされました"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "ファイル `%s' を読み込み用に開けません (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "fd %d (`%s') を閉じることができません (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "サンドボックスモード内ではリダイレクトは許可されていません"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "`%s' リダイレクトの命令式に数値しか記述されていません。"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "`%s' リダイレクトの命令式が空列です。"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "`%2$s' リダイレクトに論理演算の結果と思われるファイル名 `%1$s' が使われていま"
 "す。"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "ファイル `%.*s' で必要以上に `>' と `>>' を組合せています。"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "出力用にパイプ `%s' を開けません (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "入力用にパイプ `%s' を開けません (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr "入出力用の双方向パイプ `%s' が開けません (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "`%s' からリダイレクトできません (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "`%s' にリダイレクトできません (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "開いているファイルの数がシステム制限に達しました。ファイル記述子を多重化しま"
 "す。"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "`%s' を閉じるのに失敗しました (%s)"
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "開いているパイプまたは入力ファイルの数が多過ぎます。"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: 第二引数は `to' または `from' でなければいけません"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: `%.*s' は開いているファイル、パイプ、プロセス共有ではありません"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "開いてないリダイレクトを閉じようとしています"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: リダイレクト `%s' は `|&' を使用して開かれていません。第二引数は無視さ"
 "れました"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "パイプ `%2$s' を閉じたときの状態コードが失敗 (%1$d) でした (%3$s)。"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "ファイル `%2$s' を閉じたときの状態コードが失敗 (%1$d) でした (%3$s)。"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "ソケット `%s' を明示して閉じていません。"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "並行プロセス `%s' を明示して閉じていません。"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "パイプ `%s' を明示して閉じていません。"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "ファイル `%s' を明示して閉じていません。"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "標準出力への書込みエラー (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "標準エラーへの書込みエラー (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "パイプ `%s' をフラッシュできません (%s)。"
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "`%s' へ接続するパイプを並行プロセスからフラッシュできません (%s)。"
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "ファイル `%s' をフラッシュできません (%s)。"
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "`/inet' 内のローカルポート %s が無効です"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "リモートのホストおよびポート情報 (%s, %s) が無効です"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr ""
 "スペシャルファイル名 `%s' に（認識できる）プロトコルが指定されていません"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "スペシャルファイル名 `%s' は不完全です"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "`/inet' にはリモートホスト名を与えなければいけません"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "`/inet' にはリモートポート番号を与えなければいけません"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "TCP/IP 通信はサポートされていません"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "`%s' をモード `%s' で開けません"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "マスター pty を閉じるのに失敗しました (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "子プロセスが標準出力を閉じるのに失敗しました (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr "子プロセスがスレーブ pty を標準出力に移動できません (dup: %s)。"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "子プロセスが標準入力を閉じられません (%s)。"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr "子プロセスがスレーブ pty を標準入力に移動できません (dup: %s)。"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "スレーブ pty を閉じるのに失敗しました (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr "子プロセスがパイプを標準出力に移動できません (dup: %s)。"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr "子プロセスがパイプを標準入力に移動できません (dup: %s)。"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "親プロセスが標準出力を復旧できません。\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "親プロセスが標準入力を復旧できません。\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "パイプを閉じられません (%s)。"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "`|&' は使用できません。"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "パイプ `%s' が開けません (%s)。"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "`%s' 用の子プロセスを実行できません (fork: %s)。"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr ""
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr ""
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr ""
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "データファイル `%s' は空です。"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "入力用メモリーをこれ以上確保できません。"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "複数の文字を `RS' に使用するのは gawk 特有の拡張です。"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "IPv6 通信はサポートされていません"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "`-e/--source' への空の引数は無視されました"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: オプション `-W %s' は認識できません。無視されました\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: 引数が必要なオプション -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 "環境変数 `POSIXLY_CORRECT' が指定されています。オプション `--posix' を有効に"
 "します"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "オプション `--posix' は `--traditional' を無効にします。"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr ""
 "オプション `--posix'/`--traditional' は `--non-decimal-data' を無効にします。"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr ""
 "setuid root で %s を実行すると、セキュリティ上の問題が発生する場合がありま"
 "す。"
 
-#: main.c:571
+#: main.c:588
 #, fuzzy
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "`--posix' は `--binary' を上書きします"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "標準入力をバイナリモードに設定できません (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "標準出力をバイナリモードに設定できません (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "標準エラーをバイナリモードに設定できません (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "プログラム文が全くありません!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 "使用法: %s [POSIX または GNU 形式のオプション] -f progfile [--] file ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 "使用法: %s [POSIX または GNU 形式のオプション] [--] %cprogram%c file ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "POSIX オプション:\t\tGNU 長い形式のオプション: (標準)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f progfile\t\t--file=progfile\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=val\t\t--assign=var=val\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "短いオプション:\t\tGNU 長い形式のオプション: (拡張)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[file]\t\t--dump-variables[=file]\n"
 
-#: main.c:795
+#: main.c:815
 #, fuzzy
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-p[file]\t\t--profile[=file]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'program-text'\t--source='program-text'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E file\t\t\t--exec=file\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr ""
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr ""
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 #, fuzzy
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 #, fuzzy
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-p[file]\t\t--profile[=file]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[file]\t\t--profile[=file]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3087,7 +3106,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3102,7 +3121,7 @@ msgstr ""
 "翻訳に関するバグは<translation-team-ja@lists.sourceforge.net>に報告してくださ"
 "い。\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3112,7 +3131,7 @@ msgstr ""
 "デフォルト設定では、標準入力を読み込み、標準出力に書き出します。\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3122,7 +3141,7 @@ msgstr ""
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3141,7 +3160,7 @@ msgstr ""
 "(at your option) any later version.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3155,7 +3174,7 @@ msgstr ""
 "GNU General Public License for more details.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3163,16 +3182,16 @@ msgstr ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "POSIX awk では -Ft は FS をタブに設定しません"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "フィールド指定に不明な値があります: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3181,48 +3200,48 @@ msgstr ""
 "%s: オプション `-v' の引数 `%s' が `変数=代入値' の形式になっていません。\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "`%s' は不正な変数名です"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "`%s' は変数名ではありません。`%s=%s' のファイルを探します。"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "gawk に組み込みの `%s' は変数名として使用出来ません"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "関数 `%s' は変数名として使用出来ません"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "浮動小数点例外"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "致命的エラー: 内部エラー"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "致命的エラー: 内部エラー: セグメンテーション違反"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "致命的エラー: 内部エラー: スタックオーバーフロー"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "fd %d が事前に開いていません。"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "事前に fd %d 用に /dev/null を開けません。"
@@ -3281,7 +3300,7 @@ msgstr "or(%lf, %lf): 小数点以下は切り捨てられます"
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "compl(%lf): 負の数値を使用すると異常な結果になります"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "コマンドライン:"
@@ -3335,16 +3354,16 @@ msgstr "%s %s `%s': fd フラグを取得できません: (fcntl F_GETFD: %s)"
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr "%s %s `%s': close-on-exec を設定できません: (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "`%s' を書込み用に開けませんでした: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "プロファイルを標準エラーに送っています"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3353,7 +3372,7 @@ msgstr ""
 "\t# %s ブロック\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3362,29 +3381,29 @@ msgstr ""
 "\t# ルール\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "内部エラー: %s の vname が無効です。"
 
-#: profile.c:530
+#: profile.c:537
 #, fuzzy
 msgid "internal error: builtin with null fname"
 msgstr "内部エラー: %s の vname が無効です。"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# gawk プロファイル、作成日時 %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3393,17 +3412,12 @@ msgstr ""
 "\n"
 "\t# 関数一覧（アルファベット順）\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: 不明なリダイレクト型 %d です"
 
-#: re.c:583
-#, fuzzy, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "`[%c-%c]' 形式の範囲はロケール依存です"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr "正規表現の要素 `%.*s' はおそらく `[%.*s]' であるべきです"
@@ -3472,11 +3486,15 @@ msgstr ") または \\) が不一致です"
 msgid "No previous regular expression"
 msgstr "以前に正規表現がありません"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr ""
 
 #, fuzzy
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "`[%c-%c]' 形式の範囲はロケール依存です"
+
+#, fuzzy
 #~ msgid "[s]printf called with no arguments"
 #~ msgstr "sqrt: 負の値 %g を引数に使用して呼び出されました"
 
diff --git a/po/ms.gmo b/po/ms.gmo
index 0db272d3..6123c873 100644
--- a/po/ms.gmo
+++ b/po/ms.gmo
diff --git a/po/ms.po b/po/ms.po
index 70121298..09ec6472 100644
--- a/po/ms.po
+++ b/po/ms.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: gawk 4.0.75\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
 "PO-Revision-Date: 2013-04-19 10:45+0800\n"
 "Last-Translator: Sharuzzaman Ahmat Raslan <sharuzzaman@gmail.com>\n"
 "Language-Team: Malay <translation-team-ms@lists.sourceforge.net>\n"
@@ -19,84 +19,84 @@ msgstr ""
 "Plural-Forms: nplurals=1; plural=0;\n"
 "X-Poedit-SourceCharset: UTF-8\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "dari %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "cubaan untuk menggunakan nilai skalar sebagai tatasusunan"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "cubaan untuk menggunakan parameter skalar `%s' sebagai tatasusunan"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "cubaan untuk menggunakan skalar `%s' sebagai tatasusunan"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "cubaan untuk menggunakan tatasusunan `%s' dalam konteks skalar"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "padam: indeks `%s' tiada dalam tatasusunan `%s'"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr ""
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr ""
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr ""
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr ""
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr ""
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr ""
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr ""
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr ""
@@ -137,11 +137,11 @@ msgstr ""
 msgid "duplicate `default' detected in switch body"
 msgstr ""
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr ""
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr ""
 
@@ -230,675 +230,685 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr ""
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr ""
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr ""
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr ""
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr ""
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr ""
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr ""
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr ""
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr ""
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
 msgstr ""
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr ""
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr ""
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr ""
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
 msgstr ""
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr ""
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr ""
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr ""
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr ""
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr ""
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr ""
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr ""
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr ""
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr ""
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr ""
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr ""
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr ""
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr ""
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr ""
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr ""
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr ""
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr ""
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr ""
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr ""
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr ""
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr ""
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr ""
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr ""
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr ""
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr ""
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 
-#: awkgram.y:3992
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
 msgstr ""
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr ""
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr ""
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr ""
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr ""
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr ""
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr ""
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr ""
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr ""
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr ""
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr ""
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr ""
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr ""
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
 "or used as a variable or an array"
 msgstr ""
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr ""
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr ""
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr ""
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr ""
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr ""
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr ""
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr ""
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr ""
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr ""
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr ""
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr ""
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr ""
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr ""
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr ""
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr ""
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr ""
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr ""
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr ""
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr ""
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr ""
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr ""
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr ""
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr ""
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr ""
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr ""
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr ""
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr ""
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr ""
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr ""
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr ""
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr ""
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr ""
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr ""
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr ""
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr ""
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr ""
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr ""
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr ""
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr ""
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr ""
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr ""
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr ""
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr ""
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
 msgstr ""
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr ""
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr ""
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr ""
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr ""
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr ""
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr ""
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr ""
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr ""
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr ""
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr ""
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr ""
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr ""
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr ""
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr ""
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr ""
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr ""
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr ""
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr ""
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr ""
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr ""
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr ""
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr ""
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr ""
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
 msgstr ""
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
 msgstr ""
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr ""
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr ""
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr ""
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr ""
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr ""
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr ""
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr ""
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr ""
@@ -1020,8 +1030,8 @@ msgstr ""
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 
 #: command.y:825
@@ -1178,7 +1188,7 @@ msgstr ""
 msgid "watch var - set a watchpoint for a variable."
 msgstr ""
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr ""
@@ -1216,552 +1226,552 @@ msgstr ""
 msgid "undefined command: %s\n"
 msgstr ""
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr ""
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr ""
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr ""
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr ""
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr ""
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr ""
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr ""
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr ""
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr ""
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr ""
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr ""
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr ""
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr ""
 
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr ""
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr ""
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr ""
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr ""
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr ""
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr ""
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr ""
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr ""
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr ""
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr ""
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr ""
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr ""
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr ""
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr ""
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr ""
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr ""
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr ""
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr ""
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr ""
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr ""
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr ""
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr ""
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr ""
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr ""
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr ""
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr ""
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr ""
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr ""
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr ""
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr ""
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr ""
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr ""
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr ""
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr ""
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr ""
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr ""
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr ""
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr ""
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr ""
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr ""
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr ""
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr ""
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr ""
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr ""
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr ""
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr ""
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr ""
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr ""
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr ""
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr ""
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr ""
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr ""
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr ""
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr ""
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr ""
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr ""
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr ""
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr ""
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr ""
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr ""
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr ""
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr ""
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr ""
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr ""
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr ""
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr ""
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr ""
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr ""
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr ""
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr ""
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr ""
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr ""
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr ""
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr ""
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ""
 
@@ -1780,11 +1790,11 @@ msgstr ""
 msgid "opcode %s not an operator or keyword"
 msgstr ""
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr ""
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1792,71 +1802,71 @@ msgid ""
 "\n"
 msgstr ""
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr ""
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr ""
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr ""
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr ""
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr ""
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr ""
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr ""
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr ""
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr ""
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr ""
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr ""
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr ""
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr ""
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr ""
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr ""
@@ -1869,7 +1879,7 @@ msgstr ""
 msgid "-l / @load are gawk extensions"
 msgstr ""
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr ""
 
@@ -1898,6 +1908,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr ""
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr ""
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1918,36 +1932,36 @@ msgstr ""
 msgid "make_builtin: missing function name"
 msgstr ""
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr ""
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr ""
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr ""
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr ""
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr ""
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr ""
@@ -1972,139 +1986,143 @@ msgstr ""
 msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr ""
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr ""
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr ""
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr ""
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr ""
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr ""
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr ""
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr ""
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr ""
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr ""
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr ""
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr ""
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr ""
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr ""
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr ""
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr ""
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr ""
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr ""
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr ""
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr ""
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr ""
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr ""
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr ""
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr ""
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr ""
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr ""
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr ""
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr ""
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr ""
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr ""
 
@@ -2128,88 +2146,88 @@ msgstr ""
 msgid "wait: called with too many arguments"
 msgstr ""
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr ""
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr ""
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr ""
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr ""
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr ""
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr ""
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr ""
@@ -2238,165 +2256,165 @@ msgstr ""
 msgid "chr: called with inappropriate argument(s)"
 msgstr ""
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr ""
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr ""
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr ""
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr ""
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr ""
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr ""
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr ""
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr ""
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr ""
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr ""
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr ""
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr ""
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr ""
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr ""
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr ""
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr ""
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr ""
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr ""
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr ""
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr ""
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr ""
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr ""
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr ""
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr ""
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr ""
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr ""
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr ""
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr ""
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr ""
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr ""
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr ""
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr ""
 
@@ -2412,577 +2430,577 @@ msgstr ""
 msgid "node_to_awk_value: received null val"
 msgstr ""
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr ""
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr ""
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr ""
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr ""
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr ""
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr ""
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr ""
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr ""
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr ""
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr ""
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr ""
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr ""
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr ""
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr ""
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr ""
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr ""
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr ""
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr ""
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr ""
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr ""
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr ""
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr ""
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr ""
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr ""
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr ""
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr ""
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr ""
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr ""
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr ""
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr ""
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr ""
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr ""
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr ""
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr ""
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr ""
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr ""
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr ""
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr ""
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr ""
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr ""
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr ""
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr ""
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr ""
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr ""
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr ""
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr ""
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr ""
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr ""
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr ""
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr ""
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr ""
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr ""
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr ""
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr ""
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr ""
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr ""
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr ""
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr ""
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr ""
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr ""
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr ""
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr ""
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr ""
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr ""
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr ""
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr ""
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr ""
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr ""
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr ""
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr ""
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr ""
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr ""
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr ""
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr ""
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr ""
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr ""
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr ""
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr ""
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr ""
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr ""
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr ""
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr ""
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr ""
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr ""
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr ""
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr ""
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr ""
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr ""
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr ""
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr ""
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr ""
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr ""
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr ""
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr ""
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr ""
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr ""
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr ""
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr ""
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr ""
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr ""
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr ""
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr ""
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr ""
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr ""
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr ""
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr ""
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr ""
 
@@ -2991,7 +3009,7 @@ msgstr ""
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -2999,21 +3017,21 @@ msgid ""
 "\n"
 msgstr ""
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
 "\n"
 msgstr ""
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 msgstr ""
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3025,7 +3043,7 @@ msgid ""
 "\n"
 msgstr ""
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3034,70 +3052,70 @@ msgid ""
 "\n"
 msgstr ""
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
 msgstr ""
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr ""
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr ""
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
 "\n"
 msgstr ""
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr ""
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr ""
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr ""
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr ""
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr ""
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr ""
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr ""
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr ""
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr ""
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr ""
@@ -3152,7 +3170,7 @@ msgstr ""
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr ""
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr ""
@@ -3202,68 +3220,63 @@ msgstr ""
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr ""
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr ""
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr ""
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
 "\n"
 msgstr ""
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
 "\n"
 msgstr ""
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr ""
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr ""
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr ""
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
 "\t# Functions, listed alphabetically\n"
 msgstr ""
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr ""
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr ""
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3332,6 +3345,6 @@ msgstr ""
 msgid "No previous regular expression"
 msgstr ""
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr ""
diff --git a/po/nl.gmo b/po/nl.gmo
index 7801796c..76c57134 100644
--- a/po/nl.gmo
+++ b/po/nl.gmo
diff --git a/po/nl.po b/po/nl.po
index e15d9ff0..dc037a99 100644
--- a/po/nl.po
+++ b/po/nl.po
@@ -1,17 +1,17 @@
 # Dutch translations for GNU gawk.
-# Copyright (C) 2013 Free Software Foundation, Inc.
+# Copyright (C) 2014 Free Software Foundation, Inc.
 # This file is distributed under the same license as the gawk package.
 #
-# Bright red with teasing buttons.
+# “Flierefluiten!!”
 #
-# Benno Schulenberg <benno@vertaalt.nl>, 2005, 2007, 2010, 2011, 2012, 2013.
 # Erwin Poeze <erwin.poeze@gmail.com>, 2009.
+# Benno Schulenberg <benno@vertaalt.nl>, 2005, 2007, 2010, 2011, 2012, 2013, 2014.
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk 4.0.75\n"
+"Project-Id-Version: gawk 4.1.0b\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
-"PO-Revision-Date: 2013-04-25 21:49+0200\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-02-04 11:18+0100\n"
 "Last-Translator: Benno Schulenberg <benno@vertaalt.nl>\n"
 "Language-Team: Dutch <vertaling@vrijschrift.org>\n"
 "Language: nl\n"
@@ -21,92 +21,92 @@ msgstr ""
 "X-Generator: Lokalize 1.0\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "van %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "scalaire waarde wordt gebruikt als array"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "scalaire parameter '%s' wordt gebruikt als array"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "scalair '%s' wordt gebruikt als array"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "array '%s' wordt gebruikt in een scalaire context"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: index '%s' niet in array '%s'"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "scalair '%s[\"%.*s\"]' wordt gebruikt als array"
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr "adump: eerste argument is geen array"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: tweede argument is geen array"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: tweede argument is geen array"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: eerste argument is geen array"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: eerste argument is geen array"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asort: een subarray van het eerste argument kan niet als tweede argument "
 "gebruikt worden"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asorti: een subarray van het eerste argument kan niet als tweede argument "
 "gebruikt worden"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asort: een subarray van het tweede argument kan niet als eerste argument "
 "gebruikt worden"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asorti: een subarray van het tweede argument kan niet als eerste argument "
 "gebruikt worden"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "'%s' is ongeldig als functienaam"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "sorteervergelijkingsfunctie '%s' is niet gedefinieerd"
@@ -147,11 +147,11 @@ msgstr "dubbele 'case'-waarde in 'switch'-opdracht: %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "dubbele 'default' in 'switch'-opdracht"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "'break' buiten een lus of 'switch'-opdracht is niet toegestaan"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "'continue' buiten een lus is niet toegestaan"
 
@@ -242,264 +242,265 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr "ongeldige index-expressie"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "waarschuwing: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "fataal: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "onverwacht regeleinde of einde van string"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "kan bronbestand '%s' niet openen om te lezen (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "kan gedeelde bibliotheek '%s' niet openen om te lezen (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "reden onbekend"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr "kan '%s' niet invoegen en als programmabestand gebruiken"
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "bronbestand '%s' is reeds ingesloten"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
 msgstr "gedeelde bibliotheek '%s' is reeds geladen"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "'@include' is een gawk-uitbreiding"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "lege bestandsnaam na '@include'"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr "'@load' is een gawk-uitbreiding"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
 msgstr "lege bestandsnaam na '@load'"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
-msgstr "lege programmatekst op commandoregel"
+msgstr "lege programmatekst op opdrachtregel"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "kan bronbestand '%s' niet lezen (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "bronbestand '%s' is leeg"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "bronbestand eindigt niet met een regeleindeteken (LF)"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr "onafgesloten reguliere expressie eindigt met '\\' aan bestandseinde"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "%s: %d: regexp-optie '/.../%c' van 'tawk' werkt niet in gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "regexp-optie '/.../%c' van 'tawk' werkt niet in gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "onafgesloten reguliere expressie"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "onafgesloten reguliere expressie aan bestandseinde"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "gebruik van regelvoortzetting '\\ #...' is niet overdraagbaar"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "backslash is niet het laatste teken op de regel"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX staat operator '**=' niet toe"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "oude 'awk' kent de operator '**=' niet"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX staat operator '**' niet toe"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "oude 'awk' kent de operator '**' niet"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "oude 'awk' kent de operator '^=' niet"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "oude 'awk' kent de operator '^' niet"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "onafgesloten string"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "ongeldig teken '%c' in expressie"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "'%s' is een gawk-uitbreiding"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX staat '%s' niet toe"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "oude 'awk' kent '%s' niet"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "'goto' wordt als schadelijk beschouwd!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d is een ongeldig aantal argumenten voor %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr "%s: een stringwaarde als laatste vervangingsargument heeft geen effect"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "%s: derde parameter is geen veranderbaar object"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: derde argument is een gawk-uitbreiding"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: tweede argument is een gawk-uitbreiding"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "dcgettext(_\"...\") is onjuist: verwijder het liggende streepje"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "dcngettext(_\"...\") is onjuist: verwijder het liggende streepje"
 
-#: awkgram.y:3992
-#, fuzzy
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
-msgstr "index: tweede argument is geen string"
+msgstr ""
+"index: een reguliere-expressie-constante als tweede argument is niet "
+"toegestaan"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "functie '%s': parameter '%s' schaduwt een globale variabele"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "kan '%s' niet openen om te schrijven (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "variabelenlijst gaat naar standaardfoutuitvoer"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: sluiten is mislukt (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() twee keer aangeroepen!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "er waren geschaduwde variabelen."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "functienaam '%s' is al eerder gedefinieerd"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr "functie '%s': kan functienaam niet als parameternaam gebruiken"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "functie '%s': kan speciale variabele '%s' niet als functieparameter gebruiken"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "functie '%s': parameter #%d, '%s', dupliceert parameter #%d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "functie '%s' wordt aangeroepen maar is nergens gedefinieerd"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "functie '%s' is gedefinieerd maar wordt nergens direct aangeroepen"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "regexp-constante als parameter #%d levert booleanwaarde op"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -508,234 +509,246 @@ msgstr ""
 "functie '%s' wordt aangeroepen met een spatie tussen naam en '(',\n"
 "of wordt gebruikt als variabele of array"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "deling door nul"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "deling door nul in '%%'"
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+"kan geen waarde toewijzen aan het resultaat van een post-increment-expressie "
+"van een veld"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "ongeldig doel van toewijzing (opcode %s)"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s naar \"%s\" is mislukt (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "standaarduitvoer"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: argument is geen getal"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: argument %g ligt buiten toegestane bereik"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: kan pijp niet leegmaken: '%s' is geopend om te lezen, niet om te "
 "schrijven"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: kan bestand niet leegmaken: '%s' is geopend om te lezen, niet om te "
 "schrijven"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: '%s' is geen open bestand, pijp, of co-proces"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: eerste argument is geen string"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: tweede argument is geen string"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: argument is geen getal"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: argument is een array"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "'length(array)' is een gawk-uitbreiding"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: argument is geen string"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: argument is geen getal"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: argument %g is negatief"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "fataal: 'count$' hoort in alle opmaken gebruikt te worden, of in geen"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "veldbreedte wordt genegeerd voor opmaakaanduiding '%%'"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "veldprecisie wordt genegeerd voor opmaakaanduiding '%%'"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "veldbreedte en -precisie worden genegeerd voor opmaakaanduiding '%%'"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "fataal: '$' is niet toegestaan in awk-opmaak"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "fataal: het aantal argumenten met '$' moet > 0 zijn"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr "fataal: argumentental %ld is groter dan het gegeven aantal argumenten"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "fataal: '$' is niet toegestaan na een punt in de opmaak"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr "fataal: geen '$' opgegeven bij positionele veldbreedte of -precisie"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "'l' is betekenisloos in awk-opmaak; genegeerd"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "fataal: 'l' is niet toegestaan in POSIX awk-opmaak"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "'L' is betekenisloos in awk-opmaak; genegeerd"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "fataal: 'L' is niet toegestaan in POSIX awk-opmaak"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "'h' is betekenisloos in awk-opmaak; genegeerd"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "fataal: 'h' is niet toegestaan in POSIX awk-opmaak"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: waarde %g ligt buiten toegestaan bereik voor opmaak '%%%c'"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "onbekend opmaakteken '%c' wordt genegeerd: geen argument is geconverteerd"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr "fataal: niet genoeg argumenten voor opmaakstring"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "niet genoeg ^ voor deze"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: opmaakaanduiding mist een stuurletter"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "te veel argumenten voor opmaakstring"
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr "sprintf: geen argumenten"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: geen argumenten"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: argument is geen getal"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: argument %g is negatief"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: lengte %g is niet >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: lengte %g is niet >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: lengte %g is geen integer; wordt afgekapt"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr ""
 "substr: lengte %g is te groot voor stringindexering; wordt verkort tot %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: startindex %g is ongeldig; 1 wordt gebruikt"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: startindex %g is geen integer; wordt afgekapt"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: bronstring heeft lengte nul"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: startindex %g ligt voorbij het einde van de string"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -743,186 +756,186 @@ msgstr ""
 "substr: lengte %g bij startindex %g is groter dan de lengte van het eerste "
 "argument (%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr "strftime: opmaakwaarde in PROCINFO[\"strftime\"] is numeriek"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: tweede argument is geen getal"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr "strftime: tweede argument is kleiner dan nul of te groot voor 'time_t'"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: eerste argument is geen string"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: opmaakstring is leeg"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: argument is geen string"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: minstens één van waarden valt buiten het standaardbereik"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "'system'-functie is niet toegestaan in sandbox-modus"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: argument is geen string"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "verwijzing naar ongeïnitialiseerd veld '$%d'"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: argument is geen string"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: argument is geen string"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: eerste argument is geen getal"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: tweede argument is geen getal"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: argument is geen getal"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: argument is geen getal"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: argument is geen getal"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: derde argument is geen array"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: derde argument is 0; wordt beschouwd als 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: eerste argument is geen getal"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: tweede argument is geen getal"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%f, %f): negatieve waarden geven rare resultaten"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%f, %f): cijfers na de komma worden afgekapt"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr "lshift(%f, %f): te grote opschuifwaarden geven rare resultaten"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: eerste argument is geen getal"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: tweede argument is geen getal"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%f, %f): negatieve waarden geven rare resultaten"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%f, %f): cijfers na de komma worden afgekapt"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr "rshift(%f, %f): te grote opschuifwaarden geven rare resultaten"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr "and: aangeroepen met minder dan twee argumenten"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "and: argument %d is niet-numeriek"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr "and: negatieve waarde %2$g van argument %1$d geeft rare resultaten"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
 msgstr "or: aangeroepen met minder dan twee argumenten"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "or: argument %d is niet-numeriek"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "or: negatieve waarde %2$g van argument %1$d geeft rare resultaten"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr "xor: aangeroepen met minder dan twee argumenten"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "xor: argument %d is niet-numeriek"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor: negatieve waarde %2$g van argument %1$d geeft rare resultaten"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: argument is geen getal"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%f): negatieve waarden geven rare resultaten"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%f): cijfers na de komma worden afgekapt"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: '%s' is geen geldige taalregio-deelcategorie"
@@ -955,24 +968,25 @@ msgstr "save \"%s\": commando niet toegestaan."
 #: command.y:339
 msgid "Can't use command `commands' for breakpoint/watchpoint commands"
 msgstr ""
+"Kan commando 'commands' niet voor breekpunt-/kijkpunt-commando's gebruiken"
 
 #: command.y:341
 msgid "no breakpoint/watchpoint has been set yet"
-msgstr ""
+msgstr "er is nog geen breekpunt/kijkpunt gezet"
 
 #: command.y:343
 msgid "invalid breakpoint/watchpoint number"
-msgstr ""
+msgstr "ongeldig nummer van breekpunt/kijkpunt"
 
 #: command.y:348
 #, c-format
 msgid "Type commands for when %s %d is hit, one per line.\n"
-msgstr ""
+msgstr "Typ de commando's voor wanneer %s %d getroffen wordt, één per regel.\n"
 
 #: command.y:350
 #, c-format
 msgid "End with the command \"end\"\n"
-msgstr "Eindig met het commando \"end\".\n"
+msgstr "Eindig met het commando 'end'.\n"
 
 #: command.y:357
 msgid "`end' valid only in command `commands' or `eval'"
@@ -989,7 +1003,7 @@ msgstr "trace: ongeldige optie -- \"%s\""
 
 #: command.y:387
 msgid "condition: invalid breakpoint/watchpoint number"
-msgstr ""
+msgstr "condition: ongeldig nummer van breekpunt/kijkpunt"
 
 #: command.y:449
 msgid "argument not a string"
@@ -1032,101 +1046,122 @@ msgid ""
 "backtrace [N] - print trace of all or N innermost (outermost if N < 0) "
 "frames."
 msgstr ""
-"backtrace [N] - trace printen van alle of N binnenste frames (of buitenste "
-"als N < 0)"
+"backtrace [N] - een trace weergeven van alle of N binnenste frames (of "
+"buitenste als N < 0)"
 
 #: command.y:819
 msgid ""
 "break [[filename:]N|function] - set breakpoint at the specified location."
-msgstr "break [[BESTANDSNAAM:]N|FUNCTIE] - breekpunt zetten op gegeven positie"
+msgstr ""
+"break [[BESTANDSNAAM:]REGELNUMMER|FUNCTIE] - breekpunt zetten op gegeven "
+"positie"
 
 #: command.y:821
 msgid "clear [[filename:]N|function] - delete breakpoints previously set."
-msgstr "clear [[BESTANDSNAAM:]N|FUNCTIE] - eerder gezet breekpunt verwijderen"
+msgstr ""
+"clear [[BESTANDSNAAM:]REGELNUMMER|FUNCTIE] - eerder gezet breekpunt "
+"verwijderen"
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
+"commands [NUMMER] - een lijst van commando's beginnen die uitgevoerd moeten "
+"worden wanneer een breekpunt/kijkpunt getroffen wordt"
 
 #: command.y:825
 msgid "condition num [expr] - set or clear breakpoint or watchpoint condition."
 msgstr ""
+"condition NUMMER [EXPRESSIE] - de conditie van een breekpunt/kijkpunt zetten "
+"of wissen"
 
 #: command.y:827
 msgid "continue [COUNT] - continue program being debugged."
-msgstr ""
+msgstr "continue [AANTAL] - doorgaan met het programma in de debugger"
 
 #: command.y:829
 msgid "delete [breakpoints] [range] - delete specified breakpoints."
-msgstr ""
+msgstr "delete [BREEKPUNTEN] [BEREIK] - de gegeven breekpunten verwijderen"
 
 #: command.y:831
 msgid "disable [breakpoints] [range] - disable specified breakpoints."
-msgstr ""
+msgstr "disable [BREEKPUNTEN] [BEREIK] - de gegeven breekpunten uitschakelen"
 
 #: command.y:833
 msgid "display [var] - print value of variable each time the program stops."
 msgstr ""
-"display [VAR] - waarde van variabele printen elke keer dat het programma "
+"display [VAR] - waarde van variabele weergeven elke keer dat het programma "
 "stopt"
 
 #: command.y:835
 msgid "down [N] - move N frames down the stack."
-msgstr ""
+msgstr "down [AANTAL] - dit aantal frames naar beneden in de stack gaan"
 
 #: command.y:837
 msgid "dump [filename] - dump instructions to file or stdout."
 msgstr ""
-"dump [BESTANDSNAAM] - instructies dumpen op standaarduitvoer of naar bestand"
+"dump [BESTANDSNAAM] - instructies dumpen op standaarduitvoer (of naar "
+"bestand)"
 
 #: command.y:839
 msgid "enable [once|del] [breakpoints] [range] - enable specified breakpoints."
 msgstr ""
+"enable [once|del] [BREEKPUNTEN] [BEREIK] - de gegeven breekpunten inschakelen"
 
 #: command.y:841
 msgid "end - end a list of commands or awk statements."
-msgstr ""
+msgstr "end - een lijst van commando's of awk-statements beëindigen"
 
 #: command.y:843
 msgid "eval stmt|[p1, p2, ...] - evaluate awk statement(s)."
-msgstr ""
+msgstr "eval STATEMENT|[p1, p2, ...] - awk-statement(s) evalueren"
 
 #: command.y:845
 msgid "finish - execute until selected stack frame returns."
-msgstr ""
+msgstr "finish - uitvoeren totdat het geselecteerde stack-frame terugkeert"
 
 #: command.y:847
 msgid "frame [N] - select and print stack frame number N."
-msgstr ""
+msgstr "frame [NUMMER] - stack-frame met dit nummer selecteren en weergeven"
 
 #: command.y:849
 msgid "help [command] - print list of commands or explanation of command."
 msgstr ""
+"help [COMMANDO] - lijst van beschikbare commando's (of uitleg van commando) "
+"tonen"
 
 #: command.y:851
 msgid "ignore N COUNT - set ignore-count of breakpoint number N to COUNT."
 msgstr ""
+"ignore NUMMER AANTAL - het aantal keren dat dit breekpuntnummer genegeerd "
+"moet worden"
 
 #: command.y:853
 msgid ""
 "info topic - source|sources|variables|functions|break|frame|args|locals|"
 "display|watch."
 msgstr ""
+"info THEMA - source|sources|variables|functions|break|frame|args|locals|"
+"display|watch"
 
 #: command.y:855
 msgid "list [-|+|[filename:]lineno|function|range] - list specified line(s)."
 msgstr ""
+"list [-|+|[BESTANDSNAAM:]REGELNUMMER|FUNCTIE|BEREIK] - aangegeven regels "
+"tonen"
 
 #: command.y:857
 msgid "next [COUNT] - step program, proceeding through subroutine calls."
 msgstr ""
+"next [AANTAL] - programma uitvoeren tot de volgende bronregel bereikt is"
 
 #: command.y:859
 msgid ""
 "nexti [COUNT] - step one instruction, but proceed through subroutine calls."
 msgstr ""
+"nexti [AANTAL] - één instructie (of dit aantal) uitvoeren, waarbij een "
+"functie-aanroep als één telt"
 
 #: command.y:861
 msgid "option [name[=value]] - set or display debugger option(s)."
@@ -1134,7 +1169,7 @@ msgstr "option [NAAM[=WAARDE]] - opties van debugger tonen of instellen"
 
 #: command.y:863
 msgid "print var [var] - print value of a variable or array."
-msgstr "print VAR [VAR] - waarde van variabele of array printen"
+msgstr "print VAR [VAR] - waarde van variabele of array weergeven"
 
 #: command.y:865
 msgid "printf format, [arg], ... - formatted output."
@@ -1146,7 +1181,7 @@ msgstr "quit - de debugger verlaten"
 
 #: command.y:869
 msgid "return [value] - make selected stack frame return to its caller."
-msgstr "return [WAARDE] - gekozen stackframe terug laten keren naar aanroeper"
+msgstr "return [WAARDE] - gekozen stack-frame terug laten keren naar aanroeper"
 
 #: command.y:871
 msgid "run - start or restart executing program."
@@ -1164,6 +1199,8 @@ msgstr "set VAR = WAARDE - een waarde aan een scalaire variabele toekennen"
 msgid ""
 "silent - suspends usual message when stopped at a breakpoint/watchpoint."
 msgstr ""
+"silent - de gewone meldingen bij het stoppen bij een breekpunt/kijkpunt "
+"onderdrukken"
 
 #: command.y:881
 msgid "source file - execute commands from file."
@@ -1176,39 +1213,43 @@ msgstr ""
 
 #: command.y:885
 msgid "stepi [COUNT] - step one instruction exactly."
-msgstr "stepi [AANTAL] - precies één of dit aantal instructies uitvoeren"
+msgstr "stepi [AANTAL] - precies één (of dit aantal) instructies uitvoeren"
 
 #: command.y:887
 msgid "tbreak [[filename:]N|function] - set a temporary breakpoint."
 msgstr ""
+"tbreak [[BESTANDSNAAM:]REGELNUMMER|FUNCTIE] - een tijdelijk breekpunt zetten"
 
 #: command.y:889
 msgid "trace on|off - print instruction before executing."
-msgstr ""
+msgstr "trace on|off - instructie weergeven alvorens deze uit te voeren"
 
 #: command.y:891
 msgid "undisplay [N] - remove variable(s) from automatic display list."
 msgstr ""
+"undisplay [AANTAL] - variabele(n) van automatische weergavelijst verwijderen"
 
 #: command.y:893
 msgid ""
 "until [[filename:]N|function] - execute until program reaches a different "
 "line or line N within current frame."
 msgstr ""
+"until [[BESTANDSNAAM:]N|FUNCTIE] - programma uitvoeren totdat deze een "
+"andere regel bereikt of regel N binnen het huidige frame"
 
 #: command.y:895
 msgid "unwatch [N] - remove variable(s) from watch list."
-msgstr ""
+msgstr "unwatch [AANTAL] - variabele(n) van de kijklijst verwijderen"
 
 #: command.y:897
 msgid "up [N] - move N frames up the stack."
-msgstr ""
+msgstr "up [AANTAL] - dit aantal frames naar boven in de stack gaan"
 
 #: command.y:899
 msgid "watch var - set a watchpoint for a variable."
-msgstr ""
+msgstr "watch VAR - een kijkpunt voor een variabele zetten"
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "fout: "
@@ -1230,12 +1271,12 @@ msgstr "ongeldig teken in commando"
 #: command.y:1152
 #, c-format
 msgid "unknown command - \"%.*s\", try help"
-msgstr ""
+msgstr "onbekend commando - \"%.*s\", probeer help"
 
 #: command.y:1222
 #, c-format
 msgid "%s"
-msgstr ""
+msgstr "%s"
 
 #: command.y:1284
 msgid "invalid character"
@@ -1244,560 +1285,571 @@ msgstr "ongeldig teken"
 #: command.y:1455
 #, c-format
 msgid "undefined command: %s\n"
-msgstr ""
+msgstr "ongedefinieerd commando: %s\n"
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
-msgstr ""
+msgstr "zetten of tonen van maximum aantal regels in geschiedenisbestand"
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
-msgstr ""
+msgstr "zetten of tonen van venstergrootte van list-commando"
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
-msgstr ""
+msgstr "zetten of tonen van gawk-uitvoerbestand"
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
-msgstr ""
+msgstr "zetten of tonen van debugger-prompt"
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
-msgstr ""
+msgstr "zetten of tonen van opslaan van commandogeschiedenis (waarde=on|off)"
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
-msgstr ""
+msgstr "zetten of tonen van opslaan van opties (waarde=on|off)"
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
-msgstr ""
+msgstr "zetten of tonen van instructie-tracing (waarde=on|off)"
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
-msgstr ""
+msgstr "programma draait niet."
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "kan bronbestand '%s' niet lezen (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "bronbestand '%s' is leeg\n"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr "geen huidig bronbestand"
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "kan geen bronbestand met naam '%s' vinden (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr ""
+"Waarschuwing: bronbestand '%s' is gewijzigd sinds programmacompilatie.\n"
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
-msgstr ""
+msgstr "regelnummer %d valt buiten bereik;  '%s' heeft %d regels"
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "onverwacht einde-van-bestand tijdens lezen van bestand '%s', regel %d"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
-msgstr ""
+msgstr "bronbestand '%s' is gewijzigd sinds start van programma-uitvoering"
 
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr "Huidig bronbestand: %s\n"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
-msgstr ""
+msgstr "Aantal regels: %d\n"
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
-msgstr ""
+msgstr "Bronbestand (regels): %s (%d)\n"
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
+"Nummer  Toon  Actief   Locatie\n"
+"\n"
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
-msgstr ""
+msgstr "\taantal treffers = %ld\n"
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
-msgstr ""
+msgstr "\tvolgende %ld treffer(s) negeren\n"
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
-msgstr ""
+msgstr "\tstopconditie: %s\n"
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
-msgstr ""
+msgstr "\tcommando's:\n"
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
-msgstr ""
+msgstr "Huidig frame: "
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
-msgstr ""
+msgstr "Aangeroepen door frame: "
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
-msgstr ""
+msgstr "Aanroeper van frame: "
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
-msgstr ""
+msgstr "Geen in main().\n"
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr "Geen argumenten.\n"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
-msgstr ""
+msgstr "Geen lokalen.\n"
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
 msgstr ""
+"Alle gedefinieerde variabelen:\n"
+"\n"
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
 msgstr ""
+"Alle gedefinieerde functies:\n"
+"\n"
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
+"Automatisch weer te geven variabelen:\n"
+"\n"
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
 msgstr ""
+"Kijkvariabelen:\n"
+"\n"
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "geen symbool '%s' in huidige context\n"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr "'%s' is geen array\n"
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "$%ld = ongeïnitialiseerd veld\n"
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr "array '%s' is leeg\n"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "[\"%s\"] niet in array '%s'\n"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
-msgstr ""
+msgstr "'%s[\"%s\"]' is geen array\n"
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "'%s' is geen scalaire variabele"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "array '%s[\"%s\"]' wordt gebruikt in een scalaire context"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "scalair '%s[\"%s\"]' wordt gebruikt als array"
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr "'%s' is een functie"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
-msgstr ""
+msgstr "kijkpunt %d is zonder conditie\n"
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
-msgstr ""
+msgstr "Er is geen weergave-item met nummer %ld"
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
-msgstr ""
+msgstr "Er is geen kijk-item met nummer %ld"
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "%d: [\"%s\"] niet in array '%s'\n"
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr "scalaire waarde wordt gebruikt als array"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
-msgstr ""
+msgstr "Kijkpunt %d is verwijderd omdat parameter buiten bereik is.\n"
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
-msgstr ""
+msgstr "Weergave %d is verwijderd omdat parameter buiten bereik is.\n"
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr " in bestand '%s', regel %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr " op '%s':%d"
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
-msgstr ""
+msgstr "#%ld\tin "
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
-msgstr ""
+msgstr "Er volgen meer stack-frames...\n"
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr "ongeldig framenummer"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Opmerking: breekpunt %d (ingeschakeld, volgende %ld passages genegeerd), ook "
 "gezet op %s:%d"
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr "Opmerking: breekpunt %d (ingeschakeld), ook gezet op %s:%d"
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Opmerking: breekpunt %d (uitgeschakeld, volgende %ld passages genegeerd), "
 "ook gezet op %s:%d"
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr "Opmerking: breekpunt %d (uitgeschakeld), ook gezet op %s:%d"
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr "Breekpunt %d is gezet in bestand '%s', op regel %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr "Kan geen breekpunt zetten in bestand '%s'\n"
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "regelnummer %d in bestand '%s' valt buiten bereik"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr "Kan regel niet vinden!!!\n"
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr "Kan geen breekpunt zetten op '%s':%d\n"
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr "Kan geen breekpunt zetten in functie '%s'\n"
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr "breekpunt %d (gezet in bestand '%s', op regel %d) is onconditioneel\n"
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr "Breekpunt %d is verwijderd"
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr "Geen breekpunt(en) bij binnengaan van functie '%s'\n"
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "Geen breekpunt in bestand '%s', op regel #%d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr "ongeldig breekpuntnummer"
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr "Alle breekpunten verwijderen? (j of n) "
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr "j"
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr "Zal de volgende %ld passage(s) van breekpunt %d negeren.\n"
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr "Zal de volgende keer dat breekpunt %d wordt bereikt stoppen.\n"
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
-msgstr ""
+msgstr "Kan alleen programma's debuggen die met optie '-f' gegeven zijn.\n"
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr "Herstarten van debugger is mislukt"
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr "Programma draait al. Herstarten vanaf begin (j/n)? "
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr "Programma is niet herstart\n"
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr "fout: kan niet herstarten; operatie is niet toegestaan\n"
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 "fout(%s): kan niet herstarten; de resterende commando's worden genegeerd\n"
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr "Starten van programma: \n"
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr "Programma verliet %s met afsluitwaarde %d\n"
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr "Het programma draait. Toch afsluiten (j/n)? "
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr "Niet gestopt op een breekpunt; argument is genegeerd.\n"
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr "ongeldig breekpuntnummer %d."
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr "Zal de volgende %ld passages van breekpunt %d negeren.\n"
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
-msgstr ""
+msgstr "'finish' is niet zinvol in het buitenste frame van main()\n"
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr "Draaien tot terugkeer uit "
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
-msgstr ""
+msgstr "'return' is niet zinvol in het buitenste frame van main()\n"
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr "Kan gegeven locatie in functie '%s' niet vinden\n"
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "ongeldige bronregel %d in bestand '%s'"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr "Kan gegeven locatie %d in bestand '%s' niet vinden\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr "element niet in array\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr "ongetypeerde variabele\n"
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr "Stoppend in %s...\n"
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
-msgstr ""
+msgstr "'finish' is niet zinvol met een niet-lokale sprong '%s'\n"
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
-msgstr ""
+msgstr "'until' is niet zinvol met een niet-lokale sprong '%s'\n"
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 "\t------[Enter] om verder te gaan, of [q] [Enter] om af te sluiten------"
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr "q"
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "[\"%s\"] niet in array '%s'"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr "uitvoer wordt naar standaarduitvoer gestuurd\n"
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr "ongeldig nummer"
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "'%s' is niet toegestaan in huidige context; statement is genegeerd"
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "'return' is niet toegestaan in huidige context; statement is genegeerd"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr "Geen symbool '%s' in huidige context"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr "ongepaarde ["
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr "ongeldige tekenklasse"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr "syntax van tekenklasse is [[:space:]], niet [:space:]"
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr "onafgemaakte \\-stuurcode"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Ongeldige inhoud van \\{\\}"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Reguliere expressie is te groot"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr "ongepaarde ("
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr "geen syntax opgegeven"
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr "ongepaarde )"
 
@@ -1816,11 +1868,11 @@ msgstr "onbekende opcode %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "opcode %s is geen operator noch sleutelwoord"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "bufferoverloop in genflags2str()"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1831,71 +1883,71 @@ msgstr ""
 "\t# Functieaanroepen-stack:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "'IGNORECASE' is een gawk-uitbreiding"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "'BINMODE' is een gawk-uitbreiding"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "BINMODE-waarde '%s' is ongeldig, wordt behandeld als 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "onjuiste opgave van '%sFMT': '%s'"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "'--lint' wordt uitgeschakeld wegens toewijzing aan 'LINT'"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "verwijzing naar ongeïnitialiseerd argument '%s'"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "verwijzing naar ongeïnitialiseerde variabele '%s'"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "veldverwijzingspoging via een waarde die geen getal is"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "veldverwijzingspoging via een lege string"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "toegangspoging tot veld %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "verwijzing naar ongeïnitialiseerd veld '$%ld'"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "functie '%s' aangeroepen met meer argumenten dan gedeclareerd"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack(): onverwacht type '%s'"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "deling door nul in '/='"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "deling door nul in '%%='"
@@ -1908,7 +1960,7 @@ msgstr "uitbreidingen zijn niet toegestaan in sandbox-modus"
 msgid "-l / @load are gawk extensions"
 msgstr "-l / '@load' zijn gawk-uitbreidingen"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr "load_ext: lege bibliotheeknaam ontvangen"
 
@@ -1938,6 +1990,10 @@ msgstr "load_ext: bibliotheek '%s': initialisatiefunctie '%s' is mislukt\n"
 msgid "`extension' is a gawk extension"
 msgstr "'extension' is een gawk-uitbreiding"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "uitbreiding: lege bibliotheeknaam ontvangen"
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1959,37 +2015,37 @@ msgstr "extension: bibliotheek '%s' kan functie '%s' niet aanroepen (%s)"
 msgid "make_builtin: missing function name"
 msgstr "make_builtin: ontbrekende functienaam"
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "make_builtin: kan functie '%s' niet herdefiniëren"
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "make_builtin: functie '%s' is al gedefinieerd"
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "make_builtin: functienaam '%s' is al eerder gedefinieerd"
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 "make_builtin: kan in gawk ingebouwde '%s' niet als functienaam gebruiken"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: negatief aantal argumenten voor functie '%s'"
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr "extension: ontbrekende functienaam"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: ongeldig teken '%c' in functienaam '%s'"
@@ -2014,142 +2070,146 @@ msgstr "extension: functienaam '%s' is al eerder gedefinieerd"
 msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr "extension: kan in gawk ingebouwde '%s' niet als functienaam gebruiken"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr ""
 "functie '%s' is gedefinieerd om niet meer dan %d argument(en) te accepteren"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "functie '%s': ontbrekend argument #%d"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr "functie '%s': argument #%d: een scalair wordt gebruikt als array"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr "functie '%s': argument #%d: een array wordt gebruikt als scalair"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr "het dynamisch laden van de bibliotheek wordt niet ondersteund"
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr ""
 "chdir: aangeroepen met onjuist aantal argumenten; één wordt er verwacht"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr "stat: kan symbolische koppeling '%s' niet lezen"
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr "stat: aangeroepen met onjuist aantal argumenten"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr "stat: onjuiste parameters"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr "fts-initialisatie: kan variabele %s niet aanmaken"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "'fts' wordt op dit systeem niet ondersteund"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr "fill_stat_element: kan array niet aanmaken"
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr "fill_stat_element: kan element niet instellen"
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr "fill_path_element: kan element niet instellen"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr "fill_error_element: kan element niet instellen"
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr "fts-verwerking: kan array niet aanmaken"
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr "fts-verwerking: kan element niet instellen"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr ""
 "fts: aangeroepen met onjuist aantal argumenten; drie worden er verwacht"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr "fts: onjuiste eerste parameter"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr "fts: onjuiste tweede parameter"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr "fts: onjuiste derde parameter"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr "fts: kan array niet pletten\n"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
-msgstr ""
+msgstr "fts: listige FTS_NOSTAT-vlag wordt genegeerd -- lekker puh :)"
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr "fts: clear_array() is mislukt\n"
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr "fnmatch: aangeroepen met minder dan drie argumenten"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr "fnmatch: aangeroepen met meer dan drie argumenten"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr "fnmatch: kan eerste argument niet verkrijgen"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr "fnmatch: kan tweede argument niet verkrijgen"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr "fnmatch: kan derde argument niet verkrijgen"
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr "'fnmatch' is niet geïmplementeerd op dit systeem\n"
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr "fnmatch()-initialisatie: kan de variabele FNM_NOMATCH niet toevoegen"
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr "fnmatch()-initialisatie: kan array-element %s niet instellen"
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr "fnmatch()-initialisatie: kan array FNM niet installeren"
 
@@ -2173,94 +2233,92 @@ msgstr "wait: aangeroepen zonder argumenten"
 msgid "wait: called with too many arguments"
 msgstr "wait: aangeroepen met te veel argumenten"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr "inplace_begin(): in-situ-bewerken is al actief"
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr "inplace_begin(): verwachtte twee argumenten maar is aangeroepen met %d"
 
-#: extension/inplace.c:116
-#, fuzzy
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr ""
 "inplace_begin(): kan eerste argument niet als bestandsnaamstring oppakken"
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 "inplace_begin(): in-situ-bewerken wordt uitgeschakeld voor ongeldige "
 "bestandsnaam '%s'"
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "inplace_begin(): Kan status van '%s' niet bepalen (%s)"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "inplace_begin(): '%s' is geen normaal bestand"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr "inplace_begin(): mkstemp('%s') is mislukt (%s)"
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "inplace_begin(): chmod is mislukt (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr "inplace_begin(): dup(stdout) is mislukt (%s)"
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_begin(): dup2(%d, stdout) is mislukt (%s)"
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "inplace_begin(): close(%d) is mislukt (%s)"
 
-#: extension/inplace.c:190
-#, fuzzy
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr ""
 "inplace_end(): kan eerste argument niet als bestandsnaamstring oppakken"
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr "inplace_end(): in-situ-bewerken is niet actief"
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_end(): dup2(%d, stdout) is mislukt (%s)"
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "inplace_end(): close(%d) is mislukt (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr "inplace_end(): fsetpos(stdout) is mislukt (%s)"
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "inplace_end(): link('%s', '%s') is mislukt (%s)"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "inplace_end(): rename('%s', '%s') is mislukt (%s)"
@@ -2289,177 +2347,177 @@ msgstr "chr: aangeroepen zonder argumenten"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "chr: aangeroepen met onjuiste argumenten"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
-msgstr ""
+msgstr "dir_take_control_of(): opendir()/fdopendir() is mislukt: %s"
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr "readfile: aangeroepen met te veel argumenten"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr "readfile: aangeroepen zonder argumenten"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr "writea: aangeroepen met te veel argumenten"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "do_writea: argument 0 is geen string\n"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "do_writea: argument 1 is geen array\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr "write_array: kan array niet pletten\n"
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr "write_array: kan geplet array niet vrijgeven\n"
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr "reada: aangeroepen met te veel argumenten"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "do_reada: argument 0 is geen string\n"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "do_reada: argument 1 is geen array\n"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr "do_reada: clear_array() is mislukt\n"
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr "read_array: set_array_element() is mislukt\n"
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr "gettimeofday: argumenten worden genegeerd"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr "gettimeofday: wordt op dit platform niet ondersteund"
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr "sleep: aangeroepen met te veel argumenten"
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr "sleep: vereist numeriek argument ontbreekt"
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr "sleep: argument is negatief"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr "sleep: wordt op dit platform niet ondersteund"
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF is op een negatieve waarde gezet"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: vierde argument is een gawk-uitbreiding"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: vierde argument is geen array"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: tweede argument is geen array"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 "split: hetzelfde array kan niet zowel als tweede als als vierde argument "
 "gebruikt worden"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split: een subarray van het tweede argument kan niet als vierde argument "
 "gebruikt worden"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split: een subarray van het vierde argument kan niet als tweede argument "
 "gebruikt worden"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: lege string als derde argument is een gawk-uitbreiding"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: vierde argument is geen array"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: tweede argument is geen array"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: derde argument moet niet-nil zijn"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit: hetzelfde array kan niet zowel als tweede als als vierde argument "
 "gebruikt worden"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit: een subarray van het tweede argument kan niet als vierde argument "
 "gebruikt worden"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit: een subarray van het vierde argument kan niet als tweede argument "
 "gebruikt worden"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "'FIELDWIDTHS' is een gawk-uitbreiding"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "ongeldige waarde voor FIELDWIDTHS, nabij '%s'"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "een lege string als 'FS' is een gawk-uitbreiding"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "oude 'awk' staat geen reguliere expressies toe als waarde van 'FS'"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "'FPAT' is een gawk-uitbreiding"
 
@@ -2475,592 +2533,594 @@ msgstr "node_to_awk_value(): lege knoop ontvangen"
 msgid "node_to_awk_value: received null val"
 msgstr "node_to_awk_value(): lege waarde ontvangen"
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr "remove_element(): leeg array ontvangen"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr "remove_element(): lege index ontvangen"
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr "api_flatten_array(): kan index %d niet converteren\n"
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr "api_flatten_array(): kan waarde %d niet converteren\n"
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: optie '%s' is niet eenduidig; mogelijkheden zijn:"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: optie '--%s' staat geen argument toe\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: optie '%c%s' staat geen argument toe\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: optie '--%s' vereist een argument\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: onbekende optie '--%s'\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: onbekende optie '%c%s'\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: ongeldige optie -- '%c'\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: optie vereist een argument -- '%c'\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: optie '-W %s' is niet eenduidig\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: optie '-W %s' staat geen argument toe\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: optie '-W %s' vereist een argument\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "opdrachtregelargument '%s' is een map -- overgeslagen"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "kan bestand '%s' niet openen om te lezen (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "sluiten van bestandsdescriptor %d ('%s') is mislukt (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "omleiding is niet toegestaan in sandbox-modus"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "expressie in omleiding '%s' heeft alleen een getal als waarde"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "expressie voor omleiding '%s' heeft een lege string als waarde"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "bestandsnaam '%s' voor omleiding '%s' kan het resultaat zijn van een "
 "logische expressie"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "onnodige mix van '>' en '>>' voor bestand '%.*s'"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "kan pijp '%s' niet openen voor uitvoer (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "kan pijp '%s' niet openen voor invoer (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr "kan tweerichtings-pijp '%s' niet openen voor in- en uitvoer (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "kan niet omleiden van '%s' (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "kan niet omleiden naar '%s' (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "systeemgrens voor aantal open bestanden is bereikt: begonnen met multiplexen"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "sluiten van '%s' is mislukt (%s)"
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "te veel pijpen of invoerbestanden geopend"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: tweede argument moet 'to' of 'from' zijn"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: '%.*s' is geen open bestand, pijp, of co-proces"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "sluiten van een nooit-geopende omleiding"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: omleiding '%s' is niet geopend met '|&'; tweede argument wordt "
 "genegeerd"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "afsluitwaarde %d bij mislukte sluiting van pijp '%s' (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "afsluitwaarde %d bij mislukte sluiting van bestand '%s' (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "geen expliciete sluiting van socket '%s' aangegeven"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "geen expliciete sluiting van co-proces '%s' aangegeven"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "geen expliciete sluiting van pijp '%s' aangegeven"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "geen expliciete sluiting van bestand '%s' aangegeven"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "fout tijdens schrijven van standaarduitvoer (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "fout tijdens schrijven van standaardfoutuitvoer (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "leegmaken van pijp '%s' is mislukt (%s)"
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "leegmaken door co-proces van pijp naar '%s' is mislukt (%s)"
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "leegmaken van bestand '%s' is mislukt (%s)"
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "lokale poort %s is ongeldig in '/inet'"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "host- en poortinformatie (%s, %s) zijn ongeldig"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr "geen (bekend) protocol aangegeven in speciale bestandsnaam '%s'"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "speciale bestandsnaam '%s' is onvolledig"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "'/inet' heeft een gindse hostnaam nodig"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "'/inet' heeft een gindse poort nodig"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "TCP/IP-communicatie wordt niet ondersteund"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "kan '%s' niet openen -- modus '%s'"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "kan meester-pty van dochterproces niet sluiten (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "kan standaarduitvoer van dochterproces niet sluiten (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "kan slaaf-pty niet overzetten naar standaarduitvoer van dochterproces (dup: "
 "%s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "kan standaardinvoer van dochterproces niet sluiten (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "kan slaaf-pty niet overzetten naar standaardinvoer van dochterproces (dup: "
 "%s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "kan slaaf-pty niet sluiten (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 "kan pijp niet overzetten naar standaarduitvoer van dochterproces (dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "kan pijp niet overzetten naar standaardinvoer van dochterproces (dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "kan standaarduitvoer van ouderproces niet herstellen\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "kan standaardinvoer van ouderproces niet herstellen\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "kan pijp niet sluiten (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "'|&' wordt niet ondersteund"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "kan pijp '%s' niet openen (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "kan voor '%s' geen dochterproces starten (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr "register_input_parser(): NULL-pointer gekregen"
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
-msgstr ""
+msgstr "invoer-parser '%s' botst met eerder geïnstalleerde invoer-parser '%s'"
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
-msgstr ""
+msgstr "invoer-parser '%s' kan '%s' niet openen"
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr "register_output_wrapper(): NULL-pointer gekregen"
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
+"uitvoer-wrapper '%s' botst met eerder geïnstalleerde uitvoer-wrapper '%s'"
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
-msgstr ""
+msgstr "uitvoer-wrapper '%s' kan '%s' niet openen"
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr "register_output_processor(): NULL-pointer gekregen"
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
 "`%s'"
 msgstr ""
+"tweeweg-processor '%s' botst met eerder geïnstalleerde tweeweg-processor '%s'"
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
-msgstr ""
+msgstr "tweeweg-processor '%s' kan '%s' niet openen"
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "databestand '%s' is leeg"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "kan geen extra invoergeheugen meer toewijzen"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "een 'RS' van meerdere tekens is een gawk-uitbreiding"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "IPv6-communicatie wordt niet ondersteund"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "argument van '-e/--source' is leeg; genegeerd"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: optie '-W %s' is onbekend; genegeerd\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: optie vereist een argument -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr "omgevingsvariabele 'POSIXLY_CORRECT' is gezet: '--posix' ingeschakeld"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "'--posix' overstijgt '--traditional'"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr "'--posix'/'--traditional' overstijgen '--non-decimal-data'"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "het uitvoeren van %s als 'setuid root' kan een veiligheidsrisico zijn"
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "'--posix' overstijgt '--characters-as-bytes'"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "kan standaardinvoer niet in binaire modus zetten (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "kan standaarduitvoer niet in binaire modus zetten (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "kan standaardfoutuitvoer niet in binaire modus zetten (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "helemaal geen programmatekst!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr "Gebruik:  %s [opties] -f programmabestand [--]  bestand...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 "     of:  %s [opties] [--] %cprogrammatekst%c  bestand...\n"
 "\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "\tPOSIX-opties:\t\tEquivalente GNU-opties: (standaard)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f programmabestand\t--file=programmabestand\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F veldscheidingsteken\t--field-separator=veldscheidingsteken\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr ""
 "\t-v var=waarde\t\t--assign=var=waarde\n"
 "\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "\tKorte opties:\t\tEquivalente GNU-opties: (uitbreidingen)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[bestand]\t\t--dump-variables[=bestand]\n"
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-D[bestand]\t\t--debug[=bestand]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'programmatekst'\t--source='programmatekst'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E bestand\t\t--exec=bestand\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
-msgstr ""
+msgstr "\t-i include-bestand\t\t--include=include-bestand\n"
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
-msgstr ""
+msgstr "\t-l bibliotheek\t\t--load=bibliotheek\n"
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fataal]\t\t--lint[=fataal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-o[bestand]\t\t--pretty-print[=bestand]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[bestand]\t\t--profile[=bestand]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t\t--parsedebug\n"
 
@@ -3069,7 +3129,7 @@ msgstr "\t-Y\t\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3082,7 +3142,7 @@ msgstr ""
 "Meld fouten in de vertaling aan <vertaling@vrijschrift.org>.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3092,7 +3152,7 @@ msgstr ""
 "Standaard leest het van standaardinvoer en schrijft naar standaarduitvoer.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3102,7 +3162,7 @@ msgstr ""
 "\tgawk '{ som += $1 }; END { print som }' bestand\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3120,7 +3180,7 @@ msgstr ""
 "uitgegeven door de Free Software Foundation, naar keuze ofwel onder\n"
 "versie 3 of onder een nieuwere versie van die licentie.\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3134,7 +3194,7 @@ msgstr ""
 "Zie de GNU General Public License voor meer details.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3143,16 +3203,16 @@ msgstr ""
 "ontvangen te hebben; is dit niet het geval, dan kunt u deze licentie\n"
 "ook vinden op http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft maakt van FS geen tab in POSIX-awk"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "onbekende waarde voor veldspecificatie: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3161,48 +3221,48 @@ msgstr ""
 "%s: argument '%s' van '-v' is niet van de vorm 'var=waarde'\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "'%s' is geen geldige variabelenaam"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "'%s' is geen variabelenaam; zoekend naar bestand '%s=%s'"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "kan in gawk ingebouwde '%s' niet als variabelenaam gebruiken"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "kan functie '%s' niet als variabelenaam gebruiken"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "drijvendekomma-berekeningsfout"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "fatale fout: **interne fout**"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "fatale fout: **interne fout**: segmentatiefout"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "fatale fout: **interne fout**: stack is vol"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "geen reeds-geopende bestandsdescriptor %d"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "kan /dev/null niet openen voor bestandsdescriptor %d"
@@ -3242,7 +3302,7 @@ msgstr "%s: niet-numeriek argument #%d ontvangen"
 
 #: mpfr.c:845
 msgid "%s: argument #%d has invalid value %Rg, using 0"
-msgstr ""
+msgstr "%s: argument #%d heeft ongeldige waarde %Rg;  0 wordt gebruikt"
 
 #: mpfr.c:857
 msgid "%s: argument #%d negative value %Rg will give strange results"
@@ -3258,7 +3318,7 @@ msgstr ""
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "%1$s: negatieve waarde %3$Zd van argument #%2$d geeft rare resultaten"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "commandoregel:"
@@ -3314,16 +3374,16 @@ msgstr ""
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr "%s %s '%s': kan 'close-on-exec' niet activeren: (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "kan '%s' niet openen om te schrijven: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "profiel gaat naar standaardfoutuitvoer"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3332,7 +3392,7 @@ msgstr ""
 "\t# %s-blok(ken)\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3341,28 +3401,30 @@ msgstr ""
 "\t# Regel(s)\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "**interne fout**: %s met lege 'vname'"
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr "**interne fout**: ingebouwde functie met lege 'fname'"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
 "\n"
 msgstr ""
+"\t# Geladen uitbreidingen ('-l' en/of '@load')\n"
+"\n"
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# gawk-profiel, gemaakt op %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3371,19 +3433,12 @@ msgstr ""
 "\n"
 "\t# Functies, alfabetisch geordend\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str(): onbekend omleidingstype %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr ""
-"de betekenis van een bereik van de vorm '[%c-%c]' is afhankelijk van de "
-"taalregio"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3453,9 +3508,14 @@ msgstr "Ongepaarde ) of \\)"
 msgid "No previous regular expression"
 msgstr "Geen eerdere reguliere expressie"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
-msgstr ""
+msgstr "kan hoofdcontext niet poppen"
+
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr ""
+#~ "de betekenis van een bereik van de vorm '[%c-%c]' is afhankelijk van de "
+#~ "taalregio"
 
 #~ msgid "attempt to use function `%s' as an array"
 #~ msgstr "functie '%s' wordt gebruikt als array"
@@ -3642,15 +3702,6 @@ msgstr ""
 #~ msgid "\t-m[fr] val\n"
 #~ msgstr "\t-m[fr] waarde\n"
 
-#~ msgid "\t-W compat\t\t--compat\n"
-#~ msgstr "\t-W compat\t\t\t--compat\n"
-
-#~ msgid "\t-W copyleft\t\t--copyleft\n"
-#~ msgstr "\t-W copyleft\t\t\t--copyleft\n"
-
-#~ msgid "\t-W usage\t\t--usage\n"
-#~ msgstr "\t-W usage\t\t\t--usage\n"
-
 #~ msgid "can't convert string to float"
 #~ msgstr "kan string niet converteren naar drijvende-komma-getal"
 
diff --git a/po/pl.gmo b/po/pl.gmo
index 0683f658..b2c8e5fa 100644
--- a/po/pl.gmo
+++ b/po/pl.gmo
diff --git a/po/pl.po b/po/pl.po
index 6d647581..95ddbec2 100644
--- a/po/pl.po
+++ b/po/pl.po
@@ -1,16 +1,16 @@
 # Polish translations for GNU AWK package.
-# Copyright (C) 2003, 2004, 2005, 2007, 2008, 2009, 2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+# Copyright (C) 2003, 2004, 2005, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Free Software Foundation, Inc.
 # This file is distributed under the same license as the gawk package.
 #
-# Wojciech Polak <polak@gnu.org>, 2003, 2004, 2005, 2007, 2008, 2009, 2010, 2011, 2012, 2013.
+# Wojciech Polak <polak@gnu.org>, 2003, 2004, 2005, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014.
 # additional help by Sergey Poznyakoff <gray@gnu.org>, 2003.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk 4.0.75\n"
+"Project-Id-Version: gawk 4.1.0b\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
-"PO-Revision-Date: 2013-05-05 18:29+0200\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-03-22 17:49+0100\n"
 "Last-Translator: Wojciech Polak <polak@gnu.org>\n"
 "Language-Team: Polish <translation-team-pl@lists.sourceforge.net>\n"
 "Language: pl\n"
@@ -20,88 +20,88 @@ msgstr ""
 "Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 "
 "|| n%100>=20) ? 1 : 2);\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "od %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "próba użycia wartości skalarnej jako tablicy"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "próba użycia parametru `%s' skalaru jako tablicy"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "próba użycia skalaru `%s' jako tablicy"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "próba użycia tablicy `%s' w kontekście skalaru"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: indeks `%s' nie jest w tablicy `%s'"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "próba użycia skalaru `%s[\"%.*s\"]' jako tablicy"
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr "adump: pierwszy argument nie jest tablicą"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: drugi argument nie jest tablicą"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: drugi argument nie jest tablicą"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: pierwszy argument nie jest tablicą"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: pierwszy argument nie jest tablicą"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asort: nie można użyć podtablicy pierwszego argumentu dla drugiego argumentu"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asorti: nie można użyć podtablicy pierwszego argumentu dla drugiego argumentu"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asort: nie można użyć podtablicy drugiego argumentu dla pierwszego argumentu"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asorti: nie można użyć podtablicy drugiego argumentu dla pierwszego argumentu"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "nieprawidłowa nazwa funkcji `%s'"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "funkcja porównująca w sortowaniu `%s' nie została zdefiniowna"
@@ -145,11 +145,11 @@ msgstr "powielone wartości case w ciele switch: %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "wykryto powielony `default' w ciele switch"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "instrukcja `break' poza pętlą lub switch'em jest niedozwolona"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "instrukcja `continue' poza pętlą jest niedozwolona"
 
@@ -243,271 +243,270 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr "nieprawidłowe wyrażenie indeksowe"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "ostrzeżenie: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "fatalny błąd: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "niespodziewany znak nowego wiersza lub końca łańcucha"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "nie można otworzyć pliku źródłowego `%s' do czytania (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "nie można otworzyć współdzielonej biblioteki `%s' do czytania (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "nieznany powód"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr "nie można dołączyć `%s' i używać go jako pliku programu"
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "plik źródłowy `%s' jest już załączony"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
 msgstr "biblioteka współdzielona jest już załadowana `%s'"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include jest rozszerzeniem gawk"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "pusta nazwa pliku po @include"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr "@load jest rozszerzeniem gawk"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
 msgstr "pusta nazwa pliku po @load"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "pusty tekst programu w linii poleceń"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "nie można otworzyć pliku źródłowego `%s' (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "plik źródłowy `%s' jest pusty"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "plik źródłowy nie posiada na końcu znaku nowego wiersza"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr ""
 "niezakończone prawidłowo wyrażenie regularne kończy się znakiem `\\' na "
 "końcu pliku"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "%s: %d: modyfikator wyrażenia regularnego `/.../%c' tawk nie działa w gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr "modyfikator wyrażenia regularnego `/.../%c' tawk nie działa w gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "niezakończone wyrażenie regularne"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "niezakończone wyrażenie regularne na końcu pliku"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "użycie `\\ #...' kontynuacji linii nie jest przenośne"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "backslash nie jest ostatnim znakiem w wierszu"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX nie zezwala na operator `**='"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "stary awk nie wspiera operatora `**='"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX nie zezwala na operator `**'"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "stary awk nie wspiera operatora `**'"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "operator `^=' nie jest wspierany w starym awk"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "operator `^' nie jest wspierany w starym awk"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "niezakończony łańcuch"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "nieprawidłowy znak '%c' w wyrażeniu"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "`%s' jest rozszerzeniem gawk"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX nie zezwala na `%s'"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "`%s' nie jest wspierany w starym awk"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "`goto' uważane za szkodliwe!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d jest nieprawidłowe jako liczba argumentów dla %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 "%s: literał łańcuchowy jako ostatni argument podstawienia nie ma żadnego "
 "efektu"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "%s trzeci parametr nie jest zmiennym obiektem"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: trzeci argument jest rozszerzeniem gawk"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: drugi argument jest rozszerzeniem gawk"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "nieprawidłowe użycie dcgettext(_\"...\"): usuń znak podkreślenia"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "nieprawidłowe użycie dcngettext(_\"...\"): usuń znak podkreślenia"
 
-#: awkgram.y:3992
-#, fuzzy
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
-msgstr "index: otrzymano drugi argument, który nie jest łańcuchem"
+msgstr "index: stały regexp jako drugi argument nie jest dozwolony"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "funkcja `%s': parametr `%s' zasłania globalną zmienną"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "nie można otworzyć `%s' do zapisu (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "wysyłanie listy zmiennych na standardowe wyjście diagnostyczne"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: zamknięcie nie powiodło się (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() wywołana podwójnie!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "wystąpiły przykryte zmienne."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "nazwa funkcji `%s' została zdefiniowana poprzednio"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr "funkcja `%s': nie można użyć nazwy funkcji jako nazwy parametru"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "funkcja `%s': nie można użyć specjalnej zmiennej `%s' jako parametru funkcji"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "funkcja `%s': parametr #%d, `%s', powiela parametr #%d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "funkcja `%s' została wywołana, ale nigdy nie została zdefiniowana"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr ""
 "funkcja `%s' została zdefiniowana, ale nigdy nie została wywołana "
 "bezpośrednio"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "stałe wyrażenie regularne dla parametru #%d daje wartość logiczną"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -517,237 +516,247 @@ msgstr ""
 "`(',\n"
 "lub użyta jako zmienna lub jako tablica"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "próba dzielenia przez zero"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "próba dzielenia przez zero w `%%'"
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr "nie można przypisać wartości do wyniku tego wyrażenia"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "nieprawidłowy cel przypisania (opcode %s)"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s do \"%s\" nie powiódł się (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "standardowe wyjście"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: otrzymano argument nie będący liczbą"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: argument %g jest poza zasięgiem"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: nie można opróżnić: potok `%s' otwarty do czytania, a nie do zapisu"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: nie można opróżnić: plik `%s' otwarty do czytania, a nie do zapisu"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: `%s' nie jest ani otwartym plikiem, ani potokiem, ani procesem"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: otrzymano pierwszy argument, który nie jest łańcuchem"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: otrzymano drugi argument, który nie jest łańcuchem"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: otrzymano argument, który nie jest liczbą"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: otrzymano argument, który jest tablicą"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "`length(tablica)' jest rozszerzeniem gawk"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: otrzymano argument, który nie jest łańcuchem"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: otrzymano argument, który nie jest liczbą"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: otrzymano ujemny argument %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "fatal: należy użyć `count$' we wszystkich formatach lub nic"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "szerokość pola jest ignorowana dla specyfikatora `%%'"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "precyzja jest ignorowana dla specyfikatora `%%'"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "szerokość pola i precyzja są ignorowane dla specyfikatora `%%'"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "fatal: `$' jest niedozwolony w formatach awk"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "fatal: argument count z `$' musi być > 0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr ""
 "fatal: argument count %ld większy niż całkowita suma argumentów dostarczonych"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "fatal: `$' jest niedozwolony po kropce w formacie"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr "fatal: brak `$' dla pozycyjnej szerokości pola lub precyzji"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "`l' jest bezsensowny w formatach awk; zignorowany"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "fatal: `l' jest niedozwolony w formatach POSIX awk"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "`L' jest bezsensowny w formatach awk; zignorowany"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "fatal: `L' jest niedozwolony w formatach POSIX awk"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "`h' jest bezsensowny w formatach awk; zignorowany"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "fatal: `h' jest niedozwolony w formatach POSIX awk"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: wartość %g jest poza zasięgiem dla formatu `%%%c'"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "pominięcie nieznanego formatu specyfikatora znaku `%c': nie skonwertowano "
 "argumentu"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr ""
 "fatal: brak wystarczającej liczby argumentów, aby zaspokoić łańcuch "
 "formatujący"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "zabrakło ^"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: specyfikator formatu nie posiada kontrolnej litery"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "zbyt dużo podanych argumentów w łańcuchu formatującym"
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr "sprintf: brak argumentów"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: brak argumentów"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: otrzymano argument, który nie jest liczbą"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: wywołana z ujemnym argumentem %g"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: długość %g nie jest >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: długość %g nie jest >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: długość %g, która nie jest liczbą całkowitą, zostanie obcięta"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr "substr: długość %g zbyt duża dla indeksu łańcucha, obcinanie do %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: początkowy indeks %g jest nieprawidłowy, nastąpi użycie 1"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr ""
 "substr: początkowy indeks %g, który nie jest liczbą całkowitą, zostanie "
 "obcięty"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: łańcuch źródłowy ma zerową długość"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: początkowy indeks %g leży poza końcem łańcucha"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -755,187 +764,187 @@ msgstr ""
 "substr: długość %g zaczynając od %g przekracza długość pierwszego argumentu "
 "(%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 "strftime: wartość formatu w PROCINFO[\"strftime\"] posiada typ numeryczny"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: otrzymano drugi argument, który nie jest liczbą"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr "strftime: drugi argument mniejszy od 0 lub zbyt duży dla time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: otrzymano pierwszy argument, który nie jest łańcuchem"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: otrzymano pusty łańcuch formatujący"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: otrzymano argument, który nie jest łańcuchem"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: przynajmniej jedna z wartości jest poza domyślnym zakresem"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "funkcja 'system' nie jest dozwolona w trybie piaskownicy"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: otrzymano argument, który nie jest łańcuchem"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "odwołanie do niezainicjowanego pola `$%d'"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: otrzymano argument, który nie jest łańcuchem"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: otrzymano argument, który nie jest łańcuchem"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: otrzymano pierwszy argument, który nie jest liczbą"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: otrzymano drugi argument, który nie jest liczbą"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: otrzymano argument, który nie jest liczbą"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: otrzymano argument, który nie jest liczbą"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: otrzymano argument, który nie jest liczbą"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: otrzymano trzeci argument, który nie jest tablicą"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: trzeci argument 0 potraktowany jako 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: otrzymano pierwszy argument, który nie jest liczbą"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: otrzymano drugi argument, który nie jest liczbą"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%f, %f): ujemne wartości spowodują dziwne wyniki"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%f, %f): ułamkowe wartości zostaną obcięte"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr "lshift(%f, %f): zbyt duża wartość przesunięcia spowoduje dziwne wyniki"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: otrzymano pierwszy argument, który nie jest liczbą"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: otrzymano drugi argument, który nie jest liczbą"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%f, %f): ujemne wartości spowodują dziwne wyniki"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%f, %f): ułamkowe wartości zostaną obcięte"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr "rshift(%f, %f): zbyt duża wartość przesunięcia spowoduje dziwne wyniki"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr "and: wywołano z mniej niż dwoma argumentami"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "and: argument %d nie jest liczbą"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr "and: argument %d ujemna wartość %g spowoduje dziwne wyniki"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
 msgstr "or: wywołano z mniej niż dwoma argumentami"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "or: argument %d nie jest liczbą"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "or: argument %d ujemna wartość %g spowoduje dziwne wyniki"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr "xor: wywołano z mniej niż dwoma argumentami"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "xor: argument %d nie jest liczbą"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor: argument %d ujemna wartość %g spowoduje dziwne wyniki"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: otrzymano argument, który nie jest liczbą"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%f): ujemne wartości spowodują dziwne wyniki"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%f): ułamkowe wartości zostaną obcięte"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: `%s' nie jest prawidłową kategorią lokalizacji"
@@ -1057,8 +1066,8 @@ msgstr ""
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 
 #: command.y:825
@@ -1215,7 +1224,7 @@ msgstr ""
 msgid "watch var - set a watchpoint for a variable."
 msgstr ""
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "błąd: "
@@ -1253,93 +1262,93 @@ msgstr "nieprawidłowy znak"
 msgid "undefined command: %s\n"
 msgstr "niezdefiniowana komenda: %s\n"
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr ""
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr ""
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr ""
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr ""
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr ""
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr ""
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr ""
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr ""
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "nie można odczytać pliku źródłowego `%s' (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "plik źródłowy `%s' jest pusty.\n"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr "brak aktualnego pliku źródłowego."
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "nie można znaleźć pliku źródłowego `%s' (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr "UWAGA: plik źródłowy `%s' uległ zmianie od kompilacji programu.\n"
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr ""
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "niespodziewany koniec pliku podczas czytania `%s', linia %d"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr "plik źródłowy `%s' uległ zmianie od rozpoczęcia działania programu"
 
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr "Aktualny plik źródłowy: %s\n"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr "Ilość linii: %d\n"
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr "Plik źródłowy (linie): %s (%d)\n"
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
@@ -1347,54 +1356,54 @@ msgstr ""
 "Numer  Disp  Enabled  Lokacja\n"
 "\n"
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr ""
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr ""
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr "\tkoniec warunku: %s\n"
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr "\tkomendy:\n"
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr "Aktualna ramka: "
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr ""
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr ""
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr ""
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr "Brak argumentów.\n"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr ""
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
@@ -1402,7 +1411,7 @@ msgstr ""
 "Wszystkie zdefiniowane zmienne:\n"
 "\n"
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
@@ -1410,13 +1419,13 @@ msgstr ""
 "Wszystkie zdefiniowane funkcje:\n"
 "\n"
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
 msgstr ""
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
@@ -1424,390 +1433,390 @@ msgstr ""
 "Obserwowane zmienne:\n"
 "\n"
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "brak symbolu `%s' w bieżącym kontekście\n"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr "`%s' nie jest tablicą\n"
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "$%ld = niezainicjowane pole\n"
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr "tablica `%s' jest pusta\n"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "[\"%s\"] nie ma w tablicy `%s'\n"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr "`%s[\"%s\"]' nie jest tablicą\n"
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "`%s' nie jest zmienną skalarną"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "próba użycia tablicy `%s[\"%s\"]' w kontekście skalaru"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "próba użycia skalaru `%s[\"%s\"]' jako tablicy"
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr "`%s' jest funkcją"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr ""
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr ""
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr ""
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "%d: [\"%s\"] nie ma w tablicy `%s'\n"
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr "próba użycia wartości skalarnej jako tablicy"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr ""
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr " w pliku `%s', linia %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr " w `%s':%d"
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr "#%ld\tw "
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr ""
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr "nieprawidłowy numer ramki"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr ""
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr "Breakpoint %d ustawiony w pliku `%s', linia %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr ""
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "numer linii %d w pliku `%s' jest poza zasięgiem"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr "Nie można znaleźć reguły!!!\n"
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr ""
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr ""
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr ""
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr "Skasowany breakpoint %d"
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr ""
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "Brak breakpointa w pliku `%s', linii #%d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr ""
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr "Czy skasować wszystkie breakpointy? (y lub n) "
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr "t"
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr ""
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr ""
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr ""
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr ""
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr ""
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr ""
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr "Uruchamianie programu: \n"
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr ""
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr ""
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr ""
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr ""
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr ""
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr ""
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr ""
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr ""
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "nieprawidłowa linia źródłowa %d w pliku `%s'"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr ""
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr "brak elementu w tablicy\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr "zmienna bez typu\n"
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr ""
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr ""
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr "q"
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "[\"%s\"] nie ma w tablicy `%s'"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr "wysyłanie wyjścia na stdout\n"
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr "nieprawidłowa liczba"
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "polecenie `%s' nie może być wywołane w tym kontekście; zignorowano"
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr ""
 "instrukcja `return' nie może być wywołana w tym kontekście; zignorowano"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr "Brak symbolu `%s' w bieżącym kontekście"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr "[ nie do pary"
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr "nieprawidłowa klasa znaku"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr "składnia klasy znaku to [[:space:]], a nie [:space:]"
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr "niedokończona sekwencja ucieczki \\"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Nieprawidłowa zawartość \\{\\}"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Wyrażenie regularne jest zbyt duże"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr "( nie do pary"
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr "nie podano składni"
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr ") nie do pary"
 
@@ -1826,11 +1835,11 @@ msgstr "nieznany opcode %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "opcode %s nie jest operatorem ani słowem kluczowym"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "przepełnienie bufora w genflags2str"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1841,73 +1850,73 @@ msgstr ""
 "\t# Stos Wywoławczy Funkcji:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "`IGNORECASE' jest rozszerzeniem gawk"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "`BINMODE' jest rozszerzeniem gawk"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "wartość BINMODE `%s' jest nieprawidłowa, przyjęto ją jako 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "zła specyfikacja `%sFMT' `%s'"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "wyłączenie `--lint' z powodu przypisania do `LINT'"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "odwołanie do niezainicjowanego argumentu `%s'"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "odwołanie do niezainicjowanej zmiennej `%s'"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "próba odwołania do pola poprzez nienumeryczną wartość"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "próba odwołania z zerowego łańcucha"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "próba dostępu do pola %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "odwołanie do niezainicjowanego pola `$%ld'"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr ""
 "funkcja `%s' została wywołana z większą ilością argumentów niż zostało to "
 "zadeklarowane"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: niespodziewany typ `%s'"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "próba dzielenia przez zero w `/='"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "próba dzielenia przez zero w `%%='"
@@ -1920,7 +1929,7 @@ msgstr "rozszerzenia nie są dozwolone w trybie piaskownicy"
 msgid "-l / @load are gawk extensions"
 msgstr "-l / @load są rozszerzeniami gawk"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr "load_ext: otrzymano NULL lib_name"
 
@@ -1951,6 +1960,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "`extension' jest rozszerzeniem gawk"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "extension: otrzymano NULL lib_name"
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1972,36 +1985,36 @@ msgstr "extension: biblioteka `%s': nie można wywołać funkcji `%s' (%s)"
 msgid "make_builtin: missing function name"
 msgstr "make_builtin: brakująca nazwa funkcji"
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "make_builtin: nie można zredefiniować funkcji `%s'"
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "make_builtin: funkcja `%s' została już zdefiniowana"
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "make_builtin: nazwa funkcji `%s' została zdefiniowana wcześniej"
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr "make_builtin: nie można użyć wbudowanej w gawk `%s' jako nazwy funkcji"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: ujemny licznik argumentów dla funkcji `%s'"
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr "extension: brakująca nazwa funkcji"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: nieprawidłowy znak `%c' w nazwie funkcji `%s'"
@@ -2026,139 +2039,143 @@ msgstr "extension: nazwa funkcji `%s' została zdefiniowana wcześniej"
 msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr "extension: nie można użyć wbudowanej w gawk `%s' jako nazwy funkcji"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "funkcja `%s' zdefiniowana aby pobrać nie więcej niż %d argument(ów)"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "funkcja `%s': brakuje #%d argumentu"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr "funkcja `%s': argument #%d: próba użycia skalaru jako tablicy"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr "funkcja `%s': argument #%d: próba użycia tablicy jako skalaru"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr "dynamiczne ładowanie biblioteki nie jest wspierane"
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "chdir: wywołano z nieprawidłową ilością argumentów, spodziewano się 1"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr "stat: nie można odczytać dowiązania symbolicznego `%s'"
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr "stat: wywołano z nieprawidłową ilością argumentów"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr "stat: złe parametry"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr "fts init: nie można utworzyć zmiennej %s"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "funkcja fts nie jest wspierana w tym systemie"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr "fill_stat_element: nie można utworzyć tablicy"
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr "fill_stat_element: nie można ustawić elementu"
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr "fill_path_element: nie można ustawić elementu"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr "fill_error_element: nie można ustawić elementu"
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr "fts-process: nie można utworzyć tablicy"
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr "fts-process: nie można ustawić elementu"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "fts: wywołano z nieprawidłową ilością argumentów, powinny być 3"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr "fts: nieprawidłowy pierwszy parametr"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr "fts: nieprawidłowy drugi parametr"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr "fts: nieprawidłowy trzeci parametr"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr "fts: nie można spłaszczyć tablicy\n"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr "fts: zignorowano flagę FTS_NOSTAT. nyah, nyah, nyah."
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr "fts: clear_array() nie powiodła się\n"
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr "fnmatch: wywołano z mniej niż trzema argumentami"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr "fnmatch: wywołano z więcej niż trzema argumentami"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr "fnmatch: nie można pobrać pierwszego argumentu"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr "fnmatch: nie można pobrać drugiego argumentu"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr "fnmatch: nie można pobrać trzeciego argumentu"
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr "funkcja fnmatch nie została zaimplementowana w tym systemie\n"
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr "fnmatch init: nie można było dodać zmiennej FNM_NOMATCH"
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr "fnmatch init: nie można było ustawić elementu tablicy %s"
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr "fnmatch init: nie można było zainstalować tablicy FNM"
 
@@ -2182,90 +2199,90 @@ msgstr "wait: wywołano bez argumentów"
 msgid "wait: called with too many arguments"
 msgstr "wait: wywołana ze zbyt dużą ilością argumentów"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr "inplace_begin: edycja w miejscu jest już aktywna"
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr "inplace_begin: spodziewano się 2 argumentów, a otrzymano %d"
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr "inplace_begin: nie można pobrać pierwszego argumentu jako nazwy pliku"
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 "inplace_begin: wyłączenie edycji w miejscu dla nieprawidłowej nazwy pliku `"
 "%s'"
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "inplace_begin: nie można sprawdzić `%s' (%s)"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "inplace_begin: `%s' nie jest zwykłym plikiem"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr "inplace_begin: wywołanie mkstemp(`%s') nie powiodło się (%s)"
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "inplace_begin: funkcja chmod nie powiodła się (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr "inplace_begin: wywołanie dup(stdout) nie powiodło się (%s)"
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_begin: wywołanie dup2(%d, stdout) nie powiodło się (%s)"
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "inplace_begin: wywołanie close(%d) nie powiodło się (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr "inplace_end: nie można pobrać pierwszego argumentu jako nazwy pliku"
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr "inplace_end: edycja w miejscu nie jest aktywna"
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_end: wywołanie dup2(%d, stdout) nie powiodło się (%s)"
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "inplace_end: wywołanie close(%d) nie powiodło się (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr "inplace_end: wywołanie fsetpos(stdout) nie powiodło się (%s)"
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "inplace_end: wywołanie link(`%s', `%s') nie powiodło się (%s)"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "inplace_end: wywołanie rename(`%s', `%s') nie powiodło się (%s)"
@@ -2294,173 +2311,173 @@ msgstr "chr: wywołano bez argumentów"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "chr: wywołano z nieprawidłowymi argumentami"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr "dir_take_control_of: wywołanie opendir/fdopendir nie powiodło się: %s"
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr "readfile: wywołana ze zbyt dużą ilością argumentów"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr "readfile: wywołano bez argumentów"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr "writea: wywołana ze zbyt dużą ilością argumentów"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "do_writea: argument 0 nie jest tekstem\n"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "do_writea: argument 1 nie jest tablicą\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr "write_array: nie można spłaszczyć tablicy\n"
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr "write_array: nie można było zwolnić spłaszczonej tablicy\n"
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr "reada: wywołana ze zbyt dużą ilością argumentów"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "do_reada: argument 0 nie jest tekstem\n"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "do_reada: argument 1 nie jest tablicą\n"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr "do_reada: clear_array nie powiodła się\n"
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr "read_array: set_array_element nie powiodła się\n"
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr "gettimeofday: zignorowano argumenty"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr "gettimeofday: funkcja nie jest wspierana na tej platformie"
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr "sleep: wywołana ze zbyt dużą ilością argumentów"
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr "sleep: brakuje wymaganego argumentu numerycznego"
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr "sleep: argument jest ujemny"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr "sleep: funkcja nie jest wspierana na tej platformie"
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF ustawiony na wartość ujemną"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: czwarty argument jest rozszerzeniem gawk"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: czwarty argument nie jest tablicą"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: drugi argument nie jest tablicą"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 "split: nie można użyć tej samej tablicy dla drugiego i czwartego argumentu"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split: nie można użyć podtablicy drugiego argumentu dla czwartego argumentu"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split: nie można użyć podtablicy czwartego argumentu dla drugiego argumentu"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: zerowy łańcuch dla trzeciego argumentu jest rozszerzeniem gawk"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: czwarty argument nie jest tablicą"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: drugi argument nie jest tablicą"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: trzeci argument nie może być pusty"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit: nie można użyć tej samej tablicy dla drugiego i czwartego argumentu"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit: nie można użyć podtablicy drugiego argumentu dla czwartego "
 "argumentu"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit: nie można użyć podtablicy czwartego argumentu dla drugiego "
 "argumentu"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "`FIELDWIDTHS' jest rozszerzeniem gawk"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "nieprawidłowa wartość FIELDWIDTHS, w pobliżu `%s'"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "zerowy łańcuch dla `FS' jest rozszerzeniem gawk"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "stary awk nie wspiera wyrażeń regularnych jako wartości `FS'"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "`FPAT' jest rozszerzeniem gawk"
 
@@ -2476,391 +2493,391 @@ msgstr "node_to_awk_value: otrzymano null node"
 msgid "node_to_awk_value: received null val"
 msgstr "node_to_awk_value: otrzymano null val"
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr "remove_element: otrzymano tablicę null"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr "remove_element: otrzymano null subscript"
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr "api_flatten_array: nie można było skonwertować indeksu %d\n"
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr "api_flatten_array: nie można było skonwertować wartości %d\n"
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: opcja '%s' jest niejednoznaczna; możliwości:"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: opcja '--%s' nie może mieć argumentów\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: opcja '%c%s' nie może mieć argumentów\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: opcja '--%s' wymaga argumentu\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: nieznana opcja '--%s'\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: nieznana opcja '%c%s'\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: błędna opcja -- '%c'\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: opcja wymaga argumentu -- '%c'\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: opcja '-W %s' jest niejednoznaczna\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: opcja '-W %s' nie może mieć argumentów\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: opcja '-W %s' wymaga argumentu\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "argument linii poleceń `%s' jest katalogiem: pominięto"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "nie można otworzyć pliku `%s' do czytania (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "zamknięcie fd %d (`%s') nie powiodło się (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "przekierowanie nie jest dozwolone w trybie piaskownicy"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "wyrażenie w przekierowaniu `%s' ma tylko wartość numeryczną"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "wyrażenie dla przekierowania `%s' ma zerową wartość łańcucha"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "nazwa pliku `%s' dla przekierowania `%s' może być rezultatem logicznego "
 "wyrażenia"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "niepotrzebne mieszanie `>' i `>>' dla pliku `%.*s'"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "nie można otworzyć potoku `%s' jako wyjścia (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "nie można otworzyć potoku `%s' jako wejścia (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr ""
 "nie można otworzyć dwukierunkowego potoku `%s' jako wejścia/wyjścia (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "nie można przekierować z `%s' (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "nie można przekierować do `%s' (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "osiągnięto systemowy limit otwartych plików: rozpoczęcie multipleksowania "
 "deskryptorów plików"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "zamknięcie `%s' nie powiodło się (%s)."
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "zbyt dużo otwartych potoków lub plików wejściowych"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: drugim argumentem musi być `to' lub `from'"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr ""
 "close: `%.*s' nie jest ani otwartym plikiem, ani potokiem, ani procesem"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "zamknięcie przekierowania, które nigdy nie zostało otwarte"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: przekierowanie `%s' nie zostało otwarte z `|&', drugi argument "
 "zignorowany"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "status awarii (%d) podczas zamykania potoku `%s' (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "status awarii (%d) podczas zamykania pliku `%s' (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "brak jawnego zamknięcia gniazdka `%s'"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "brak jawnego zamknięcia procesu pomocniczego `%s'"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "brak jawnego zamknięcia potoku `%s'"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "brak jawnego zamknięcia pliku `%s'"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "błąd podczas zapisu na standardowe wyjście (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "błąd podczas zapisu na standardowe wyjście diagnostyczne (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "opróżnienie potoku `%s' nie powiodło się (%s)."
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr ""
 "opróżnienie potoku do `%s' przez proces pomocniczy nie powiodło się (%s)."
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "opróżnienie pliku `%s' nie powiodło się (%s)."
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "nieprawidłowy lokalny port %s w `/inet'"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "informacje o zdalnym hoście i porcie są nieprawidłowe (%s, %s)"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr "nie dostarczono (znanego) protokołu w specjalnym pliku `%s'"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "specjalna nazwa pliku `%s' jest niekompletna"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "należy dostarczyć nazwę zdalnego hosta do `/inet'"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "należy dostarczyć numer zdalnego portu do `/inet'"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "Komunikacja TCP/IP nie jest wspierana"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "nie można otworzyć `%s', tryb `%s'"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "zamknięcie nadrzędnego pty nie powiodło się (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr ""
 "zamknięcie standardowego wyjścia w procesie potomnym nie powiodło się (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
 "przesunięcie podległego pty na standardowe wyjście w procesie potomnym nie "
 "powiodło się (dup: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr ""
 "zamknięcie standardowego wejścia w procesie potomnym nie powiodło się (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
 "przesunięcie podległego pty na standardowe wejście w procesie potomnym nie "
 "powiodło się (dup: %s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "zamknięcie podległego pty nie powiodło się (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
 "przesunięcie potoku na standardowe wyjście w procesie potomnym nie powiodło "
 "się (dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
 "przesunięcie potoku na standardowe wejście w procesie potomnym nie powiodło "
 "się (dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr ""
 "odzyskanie standardowego wyjścia w procesie potomnym nie powiodło się\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr ""
 "odzyskanie standardowego wejścia w procesie potomnym nie powiodło się\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "zamknięcie potoku nie powiodło się (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "`|&' nie jest wspierany"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "nie można otworzyć potoku `%s' (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "nie można utworzyć procesu potomnego dla `%s' (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr "register_input_parser: otrzymano wskaźnik NULL"
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 "parser wejścia `%s' konfliktuje z poprzednio zainstalowanym parserem `%s'"
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr "parser wejścia `%s': nie powiodło się otwarcie `%s'"
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr "register_output_wrapper: otrzymano wskaźnik NULL"
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 "otoczka wyjścia `%s' konfliktuje z poprzednio zainstalowaną otoczką `%s'"
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr "otoczka wyjścia `%s': nie powiodło się otwarcie `%s'"
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr "register_output_processor: otrzymano wskaźnik NULL"
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
@@ -2869,212 +2886,212 @@ msgstr ""
 "dwukierunkowy procesor `%s' konfliktuje z poprzednio zainstalowanym "
 "procesorem `%s'"
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr "dwukierunkowy procesor `%s' zawiódł w otwarciu `%s'"
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "plik danych `%s' jest pusty"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "nie można zarezerwować więcej pamięci wejściowej"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "wieloznakowa wartość `RS' jest rozszerzeniem gawk"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "Komunikacja IPv6 nie jest wspierana"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "pusty argument dla opcji `-e/--source' został zignorowany"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: opcja `-W %s' nierozpoznana i zignorowana\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: opcja musi mieć argument -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 "zmienna środowiskowa `POSIXLY_CORRECT' ustawiona: `--posix' został włączony"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "opcja `--posix' zostanie użyta nad `--traditional'"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr "`--posix'/`--traditional' użyte nad opcją `--non-decimal-data'"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr ""
 "uruchamianie %s setuid root może być problemem pod względem bezpieczeństwa"
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "opcja `--posix' zostanie użyta nad `--characters-as-bytes'"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "nie można ustawić trybu binarnego na standardowym wejściu (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "nie można ustawić trybu binarnego na standardowym wyjściu (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "nie można ustawić trybu binarnego na wyjściu diagnostycznym (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "brak tekstu programu!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 "Użycie: %s [styl opcji POSIX lub GNU] -f plik_z_programem [--] plik ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr "Użycie: %s [styl opcji POSIX lub GNU] [--] %cprogram%c plik ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "Opcje POSIX:\t\tDługie opcje GNU (standard):\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f program\t\t--file=program\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v zmienna=wartość\t--assign=zmienna=wartość\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "Krótkie opcje:\t\tDługie opcje GNU: (rozszerzenia)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[plik]\t\t--dump-variables[=plik]\n"
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-D[plik]\t\t--debug[=plik]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'tekst-programu'\t--source='tekst-programu'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E plik\t\t\t--exec=plik\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr "\t-i plikinclude\t\t--include=plikinclude\n"
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr "\t-l biblioteka\t\t--load=biblioteka\n"
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-o[plik]\t\t--pretty-print[=plik]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[plik]\t\t--profile[=plik]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3083,7 +3100,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3096,7 +3113,7 @@ msgstr ""
 "dokumentacji.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3106,7 +3123,7 @@ msgstr ""
 "Program domyślnie czyta standardowe wejście i zapisuje standardowe wyjście.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3116,7 +3133,7 @@ msgstr ""
 "\tgawk '{ suma += $1 }; END { print suma }' plik\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3135,7 +3152,7 @@ msgstr ""
 "tej Licencji lub którejś z późniejszych wersji.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3150,7 +3167,7 @@ msgstr ""
 "Powszechną Licencję Publiczną GNU.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3159,16 +3176,16 @@ msgstr ""
 "Powszechnej Licencji Publicznej GNU (GNU General Public License);\n"
 "jeśli zaś nie - odwiedź stronę http://www.gnu.org/licenses/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft nie ustawia FS na znak tabulatora w POSIX awk"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "nieznana wartość dla specyfikacji pola: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
@@ -3177,48 +3194,48 @@ msgstr ""
 "%s: argument `%s' dla `-v' nie jest zgodny ze składnią `zmienna=wartość'\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "`%s' nie jest dozwoloną nazwą zmiennej"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "`%s' nie jest nazwą zmiennej, szukanie pliku `%s=%s'"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "nie można użyć wbudowanej w gawk `%s' jako nazwy zmiennej"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "nie można użyć funkcji `%s' jako nazwy zmiennej"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "wyjątek zmiennopozycyjny"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "fatalny błąd: wewnętrzny błąd"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "fatalny błąd: wewnętrzny błąd: błąd segmentacji"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "fatalny błąd: wewnętrzny błąd: przepełnienie stosu"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "brak już otwartego fd %d"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "nie można otworzyć zawczasu /dev/null dla fd %d"
@@ -3273,7 +3290,7 @@ msgstr "%s: argument #%d ułamkowa wartość %Rg zostanie obcięta"
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "%s: argument #%d ujemna wartość %Zd spowoduje dziwne wyniki"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "linia poleceń:"
@@ -3327,16 +3344,16 @@ msgstr "%s %s `%s': nie można uzyskać flag fd: (fcntl F_GETFD: %s)"
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr "%s %s `%s': nie można ustawić close-on-exec: (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "nie można otworzyć `%s' do zapisu: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "wysyłanie profilu na standardowe wyjście diagnostyczne"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3345,7 +3362,7 @@ msgstr ""
 "\t# %s blok(i)\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3354,16 +3371,16 @@ msgstr ""
 "\t# Reguła(i)\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "wewnętrzny błąd: %s z zerowym vname"
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr "wewnętrzny błąd: builtin z fname null"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
@@ -3372,12 +3389,12 @@ msgstr ""
 "\t# Załadowane rozszerzenia (-l i/lub @load)\n"
 "\n"
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# profil programu gawk, utworzony %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3386,17 +3403,12 @@ msgstr ""
 "\n"
 "\t# Funkcje, spis alfabetyczny\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: nieznany typ przekierowania %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "zasięg formy `[%c-%c]' jest zależny od lokalizacji"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr "komponent regexp `%.*s' powinien być prawdopodobnie `[%.*s]'"
@@ -3465,10 +3477,13 @@ msgstr "Niedopasowany znak ) lub \\)"
 msgid "No previous regular expression"
 msgstr "Brak poprzedniego wyrażenia regularnego"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr "nie można zdjąć głównego kontekstu"
 
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "zasięg formy `[%c-%c]' jest zależny od lokalizacji"
+
 #~ msgid "attempt to use function `%s' as an array"
 #~ msgstr "próba użycia funkcji `%s' jako tablicy"
 
diff --git a/po/sv.gmo b/po/sv.gmo
index a805642a..11006e58 100644
--- a/po/sv.gmo
+++ b/po/sv.gmo
diff --git a/po/sv.po b/po/sv.po
index 7168507f..79b0bca8 100644
--- a/po/sv.po
+++ b/po/sv.po
@@ -1,17 +1,17 @@
 # Swedish translation of gawk
-# Copyright © 2003, 2011, 2012, 2013 Free Software Foundation, Inc.
+# Copyright © 2003, 2011, 2012, 2013, 2014 Free Software Foundation, Inc.
 # This file is distributed under the same license as the gawk package.
 # Martin Sjögren <md9ms@mdstud.chalmers.se>, 2001-2002.
 # Christer Andersson <klamm@comhem.se>, 2007.
-# Göran Uddeborg <goeran@uddeborg.se>, 2011, 2012, 2013.
+# Göran Uddeborg <goeran@uddeborg.se>, 2011, 2012, 2013, 2014.
 #
-# $Revision: 1.12 $
+# $Revision: 1.14 $
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk 4.0.75\n"
+"Project-Id-Version: gawk 4.1.0b\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
-"PO-Revision-Date: 2013-04-18 22:46+0200\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-01-21 17:40+0100\n"
 "Last-Translator: Göran Uddeborg <goeran@uddeborg.se>\n"
 "Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n"
 "Language: sv\n"
@@ -19,92 +19,92 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "från %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "försök att använda ett skalärt värde som vektor"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "försök att använda skalärparametern ”%s” som en vektor"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "försök att använda skalären ”%s” som en vektor"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "försök att använda vektorn ”%s” i skalärsammanhang"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: index ”%s” finns inte i vektorn ”%s”"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
 msgstr "försök att använda skalären ”%s[\"%.*s\"]” som en vektor"
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr "adump: första argumentet är inte en vektor"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: andra argumentet är inte en vektor"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: andra argumentet är inte en vektor"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: första argumentet är inte en vektor"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: första argumentet är inte en vektor"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asort: det går inte att använda en delvektor av första argumentet som andra "
 "argument"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
 "asorti: det går inte att använda en delvektor av första argumentet som andra "
 "argument"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asort: det går inte att använda en delvektor av andra argumentet som första "
 "argument"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
 "asorti: det går inte att använda en delvektor av andra argumentet som första "
 "argument"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "”%s” är ogiltigt som ett funktionsnamn"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "jämförelsefunktionen ”%s” för sortering är inte definierad"
@@ -145,11 +145,11 @@ msgstr "upprepade case-värden i switch-sats: %s"
 msgid "duplicate `default' detected in switch body"
 msgstr "flera \"default\" upptäcktes i switch-sats"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr "\"break\" är inte tillåtet utanför en slinga eller switch"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "\"continue\" är inte tillåtet utanför en slinga"
 
@@ -240,273 +240,272 @@ msgstr ""
 msgid "invalid subscript expression"
 msgstr "ogiltig indexuttryck"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "varning: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
 msgstr "ödesdigert: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
 msgstr "oväntat nyradstecken eller slut på strängen"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "kan inte öppna källfilen \"%s\" för läsning (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "kan inte öppna det delade biblioteket ”%s” för läsning (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
 msgstr "okänd anledning"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr "kan inte inkludera ”%s” och använda den som en programfil"
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "inkluderade redan källfilen \"%s\""
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
 msgstr "inkluderade redan det delade biblioteket ”%s”"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include är en gawk-utökning"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
 msgstr "tomt filnamn efter @include"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr "@load är en gawk-utökning"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
 msgstr "tomt filnamn efter @load"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "tom programtext på kommandoraden"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "kan inte läsa källfilen \"%s\" (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "källfilen \"%s\" är tom"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "källfilen slutar inte med en ny rad"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr "oavslutat reguljärt uttryck slutar med \"\\\" i slutet av filen"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "%s: %d: tawk-modifierare för reguljära uttryck \"/.../%c\" fungerar inte i "
 "gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "tawk-modifierare för reguljära uttryck \"/.../%c\" fungerar inte i gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "oavslutat reguljärt uttryck"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "oavslutat reguljärt uttryck i slutet av filen"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "Användning av \"\\ #...\" för radfortsättning är inte portabelt"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
 msgstr "sista tecknet på raden är inte ett omvänt snedstreck"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX tillåter inte operatorn \"**=\""
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "gamla awk stöder inte operatorn \"**=\""
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX tillåter inte operatorn \"**\""
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "gamla awk stöder inte operatorn \"**\""
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "operatorn \"^=\" stöds inte i gamla awk"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "operatorn \"^\" stöds inte i gamla awk"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "oavslutad sträng"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "ogiltigt tecken \"%c\" i uttryck"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "\"%s\" är en gawk-utökning"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX tillåter inte \"%s\""
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "\"%s\" stöds inte i gamla awk"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "\"goto\" anses skadlig!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "%d är ett ogiltigt antal argument för %s"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 "%s: bokstavlig sträng som sista argument till ersättning har ingen effekt"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "%s: tredje argumentet är inte ett ändringsbart objekt"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: tredje argumentet är en gawk-utökning"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: andra argumentet är en gawk-utökning"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "användandet av dcgettext(_\"...\") är felaktigt: ta bort det inledande "
 "understrykningstecknet"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr ""
 "användandet av dcngettext(_\"...\") är felaktigt: ta bort det inledande "
 "understrykningstecknet"
 
-#: awkgram.y:3992
-#, fuzzy
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
-msgstr "index: andra argumentet är inte en sträng"
+msgstr "index: reguljäruttryck som andra argumentet är inte tillåtet"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "funktionen \"%s\": parametern \"%s\" överskuggar en global variabel"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "kunde inte öppna \"%s\" för skrivning (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "skickar variabellista till standard fel"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
 msgstr "%s: misslyckades att stänga (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() anropad två gånger!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "det fanns överskuggade variabler."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "funktionsnamnet \"%s\" är definierat sedan tidigare"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr "funktionen \"%s\": kan inte använda funktionsnamn som parameternamn"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr ""
 "funktionen \"%s\": det går inte att använda specialvariabeln \"%s\" som en "
 "funktionsparameter"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "funktionen \"%s\": parameter %d, \"%s\", är samma som parameter %d"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
 msgstr "funktionen \"%s\" anropad men aldrig definierad"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "funktionen \"%s\" definierad men aldrig anropad direkt"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "konstant reguljärt uttryck för parameter %d ger ett booleskt värde"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -515,233 +514,245 @@ msgstr ""
 "funktionen \"%s\" anropad med blanktecken mellan namnet och \"(\",\n"
 "eller använd som variabel eller vektor"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
 msgstr "försökte dividera med noll"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
 msgstr "försökte dividera med noll i \"%%\""
 
-#: builtin.c:128
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr ""
+"kan inte tilldela ett värde till uttryck som är en efterinkrementering av "
+"ett fält"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "ogiltigt mål för tilldelning (op-kod %s)"
+
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s till \"%s\" misslyckades (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "standard ut"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: fick ett ickenumeriskt argument"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: argumentet %g är inte inom tillåten gräns"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: kan inte spola: röret \"%s\" öppnat för läsning, inte skrivning"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: kan inte spola: filen \"%s\" öppnad för läsning, inte skrivning"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr "fflush: \"%s\" är inte en öppen fil, rör eller koprocess"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: första argumentet är inte en sträng"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
 msgstr "index: andra argumentet är inte en sträng"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: fick ett ickenumeriskt argument"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: fick ett vektorargument"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "\"length(array)\" är en gawk-utökning"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: fick ett argument som inte är en sträng"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
 msgstr "log: fick ett ickenumeriskt argument"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
 msgstr "log: fick ett negativt argumentet %g"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
 msgstr "ödesdigert: måste använda \"count$\" på alla eller inga format"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "fältbredd ignoreras för \"%%\"-specificerare"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "precision ignoreras för \"%%\"-specificerare"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "fältbredd och precision ignoreras för \"%%\"-specificerare"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
 msgstr "ödesdigert: \"$\" tillåts inte i awk-format"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
 msgstr "ödesdigert: argumentantalet med \"$\" måste vara > 0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
 msgstr "ödesdigert: argumentantalet %ld är större än antalet givna argument"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
 msgstr "ödesdigert: \"$\" tillåts inte efter en punkt i formatet"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
 "ödesdigert: inget \"$\" bifogat för positionsangiven fältbredd eller "
 "precision"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "\"l\" är meningslös i awk-format, ignorerad"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
 msgstr "ödesdigert: \"l\" tillåts inte i POSIX awk-format"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "\"L\" är meningslös i awk-format, ignorerad"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
 msgstr "ödesdigert: \"L\" tillåts inte i POSIX awk-format"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "\"h\" är meningslös i awk-format, ignorerad"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
 msgstr "ödesdigert: \"h\" tillåts inte i POSIX awk-format"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
 msgstr "[s]printf: värdet %g är utanför \"%%%c\"-formatets giltiga intervall"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "ignorerar okänt formatspecifikationstecken \"%c\": inget argument konverterat"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
 msgstr "ödesdigert: för få argument för formatsträngen"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "^ tog slut här"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: formatspecifieraren har ingen kommandobokstav"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "för många argument för formatsträngen"
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr "sprintf: inga argument"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: inga argument"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: fick ickenumeriskt argument"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: anropad med negativt argument %g"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
 msgstr "substr: längden %g är inte >= 1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
 msgstr "substr: längden %g är inte >= 0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
 msgstr "substr: längden %g som inte är ett heltal kommer huggas av"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
 msgstr "substr: längden %g är för stor för strängindexering, huggas av till %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
 msgstr "substr: startindex %g är ogiltigt, använder 1"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr "substr: startindex %g som inte är ett heltal kommer huggas av"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: källsträngen är tom"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
 msgstr "substr: startindex %g är bortom strängens slut"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
@@ -749,186 +760,186 @@ msgstr ""
 "substr: längden %g vid startindex %g överskrider det första argumentets "
 "längd (%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr "strftime: formatvärde i PROCINFO[\"strftime\"] har numerisk typ"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: fick ett ickenumeriskt andra argument"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr "strftime: andra argimentet mindre än 0 eller för stort för time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: fick ett första argument som inte är en sträng"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: fick en tom formatsträng"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: fick ett argument som inte är en sträng"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: åtminstone ett av värdena är utanför standardintervallet"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "funktionen \"system\" är inte tillåten i sandlådeläge"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: fick ett argument som inte är en sträng"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
 msgstr "referens till icke initierat fält \"$%d\""
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: fick ett argument som inte är en sträng"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: fick ett argument som inte är en sträng"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: fick ett ickenumeriskt första argument"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: fick ett ickenumeriskt andra argument"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: fick ett ickenumeriskt argument"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: fick ett ickenumeriskt argument"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: fick ett ickenumeriskt argument"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: tredje argumentet är inte en vektor"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: nollan i tredje argumentet behandlad som en etta"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: fick ett ickenumeriskt första argument"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: fick ett ickenumeriskt andra argument"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%f, %f): negativa värden kommer ge konstiga resultat"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%f, %f): flyttalsvärden kommer huggas av"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr "lshift(%f, %f): för stort skiftvärde kommer ge konstiga resultat"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: fick ett ickenumeriskt första argument"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
 msgstr "rshift: fick ett ickenumeriskt andra argument"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%f, %f): negativa värden kommer ge konstiga resultat"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%f, %f): flyttalsvärden kommer huggas av"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr "rshift(%f, %f): för stor skiftvärde kommer ge konstiga resultat"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr "and: anropad med mindre än två argument"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "and: argument %d är inte numeriskt"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
 msgstr "and: argument %d med negativt värde %g kommer ge konstiga resultat"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
 msgstr "or: anropad med färre än två argmuent"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
 msgstr "or: argument %d är inte numeriskt"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
 msgstr "or: argument %d med negativt värde %g kommer ge konstiga resultat"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr "xor: anropad med färre än två argument"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "xor: argument %d är inte numeriskt"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor: argument %d med negativt värde %g kommer ge konstiga resultat"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
 msgstr "compl: fick ett ickenumeriskt argument"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%f): negativt värde kommer ge konstiga resultat"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%f): flyttalsvärde kommer huggas av"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: \"%s\" är inte en giltig lokalkategori"
@@ -1054,11 +1065,11 @@ msgstr "clear [[filnamn:]N|funktion] - radera tidigare satta brytpunkter."
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
-"commands [num] - startar en lista av kommandon att köra när en brytpunkt"
-"(observationspunkt) träffas."
+"commands [num] - startar en lista av kommandon att köra när en "
+"brytpunkt(observationspunkt) träffas."
 
 #: command.y:825
 msgid "condition num [expr] - set or clear breakpoint or watchpoint condition."
@@ -1226,7 +1237,7 @@ msgstr "up [N] - flytta N ramar uppåt i stacken."
 msgid "watch var - set a watchpoint for a variable."
 msgstr "watch var - sätt en observationspunkt för en variabel."
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "fel: "
@@ -1264,93 +1275,93 @@ msgstr "ogiltigt tecken"
 msgid "undefined command: %s\n"
 msgstr "odefinierat kommando: %s\n"
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr "sätt eller visa antalet rader att behålla i historiefilen."
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr "sätt eller visa fönsterstorleken för listkommandot."
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr "sätt eller visa gawks utmatningsfil."
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr "sätt eller visa felsökningsprompten."
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr "slå av/på eller visa sparandet av kommandohisterik (värde=on|off)."
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr "slå av/på eller visa sparandet av flaggor (värde=on|off)."
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr "slå av/på eller visa instruktionsspårande (värde=on|off)."
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr "programmet kör inte."
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "kan inte läsa källfilen ”%s” (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "källfilen ”%s” är tom.\n"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr "ingen aktuell källkodsfil."
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "kan inte hitta någon källfil med namnet ”%s” (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr "VARNING: källfilen ”%s” ändrad sedan programmet kompilerades.\n"
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr "radnummer %d utanför intervallet; ”%s” har %d rader"
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "oväntat filslut när filen ”%s” lästes, rad %d"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr "källfilen ”%s” ändrad sedan början av programkörningen"
 
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr "Aktuell källfil: %s\n"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr "Antalet rader: %d\n"
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr "Källfilen (rader): %s (%d)\n"
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
@@ -1358,54 +1369,54 @@ msgstr ""
 "Nummer  Visa  Aktiv    Plats\n"
 "\n"
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr "\tantal träffar = %ld\n"
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr "\tignorera nästa %ld träffar\n"
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr "\tstoppvillkor: %s\n"
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr "\tkommandon:\n"
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr "Aktuell ram: "
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr "Anropad av ramen: "
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr "Anropare av ramen: "
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr "Ingen i main().\n"
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr "Inga argument.\n"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr "Inga lokala.\n"
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
@@ -1413,7 +1424,7 @@ msgstr ""
 "Alla definierade variabler:\n"
 "\n"
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
@@ -1421,7 +1432,7 @@ msgstr ""
 "Alla definierade funktioner:\n"
 "\n"
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
@@ -1429,7 +1440,7 @@ msgstr ""
 "Automatvisade variabler:\n"
 "\n"
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
@@ -1437,396 +1448,396 @@ msgstr ""
 "Observerade variabler:\n"
 "\n"
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "ingen symbol ”%s” i aktuellt sammanhang\n"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr "”%s” är inte en vektor\n"
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "$%ld = oinitierat fält\n"
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr "vektorn ”%s” är tom\n"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "[\"%s\"] finns inte i vektorn ”%s”\n"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr "”%s[\"%s\"]” är inte en vektor\n"
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "”%s” är inte en skalär variabel"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "försök att använda vektorn ”%s[\"%s\"]” i skalärt sammanhang"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "försök att använda skalären ”%s[\"%s\"]” som en vektor"
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr "”%s” är en funktion"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr "observationspunkt %d är ovillkorlig\n"
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr "Ingen visningspost med numret %ld"
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr "Ingen observationspost med numret %ld"
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "%d: [\"%s\"] finns inte i vektorn ”%s”\n"
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr "försök att använda ett skalärt värde som vektor"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr ""
 "Observationspunkt %d raderad för att parametern är utanför sin räckvidd.\n"
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr "Visning %d raderad för att parametern är utanför sin räckvidd.\n"
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr " i filen ”%s”, rad %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr " vid ”%s”:%d"
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr "#%ld\ti "
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
 msgstr "Fler stackramar följer …\n"
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr "Ogiltigt ramnummer"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Observera: brytpunkt %d (aktiverad, ingorera följande %ld träffar), är också "
 "satt vid %s:%d"
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr "Observera: brytpunkt %d (aktiverad), är också satt vid %s:%d"
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Observera: brytpunkt %d (avaktiverad, intorera följande %ld träffar), är "
 "också satt vid %s:%d"
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr "Observera: brytpunkt %d (avaktiverad), är också satt vid %s:%d"
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr "Brytpunkt %d satt vid filen ”%s”, rad %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr "Kan inte sätta en brytpunkt i filen ”%s”\n"
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "radnummer %d i filen ”%s” är utanför tillåtet intervall"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr "Kan inte hitta regeln!!!\n"
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr "Kan inte sätta än brytpunkt vid ”%s”:%d\n"
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr "Kan inte sätta en brytpunkt i funktionen ”%s”\n"
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr "brytpunkt %d satt i filen ”%s”, rad %d är ovillkorlig\n"
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr "Raderade brytpunkt %d"
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr "Inga brytpunkter vid ingången till funktionen ”%s”\n"
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "Ingen brytpunkt i filen ”%s”, rad nr. %d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr "ogiltigt brytpunktsnummer"
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr "Radera alla brytpunkter? (j eller n)"
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr "j"
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr "Kommer ignorera följande %ld passager av brytpunkt %d.\n"
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr "Kommer stanna nästa gång brytpunkt %d nås.\n"
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr "Kan bara felsöka program som getts flaggan ”-f”.\n"
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr "Misslyckades att starta om felsökaren"
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr "Programmet kör redan.  Starta om från början (j/n)? "
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr "Programmet inte omstartat\n"
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr "fel: kan inte starta om, åtgärden är inte tillåten\n"
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr "fel (%s): kan inte starta om, ingorerar resten av kommandona\n"
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr "Startar programmet: \n"
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr "Programmet avslutade %s med slutvärde: %d\n"
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr "Programmet kör.  Avsluta ändå (j/n)? "
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr "Inte stoppad vid någon brytpunkt, argumentet ignoreras.\n"
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr "ogiltigt brytpunktsnummer %d."
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr "Kommer ignorera de nästa %ld passagerna av brytpunkt %d.\n"
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr "”finish” är inte meningsfullt i den yttersta ramen main()\n"
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr "Kör till retur från "
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr "”return” är inte meningsfullt i den yttersta ramen main()\n"
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr "Kan inte hitta angiven plats i funktionen ”%s”\n"
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "ogiltig källrad %d i filen ”%s”"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr "Kan inte hitta angiven plats %d i filen ”%s”\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr "elementet finns inte i vektorn\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr "otypad variabel\n"
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr "Stannar i %s …\n"
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr "”finish” är inte meningsfullt med icke lokalt hopp ”%s”\n"
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr "”until” är inte meningsfullt med icke lokalt hopp ”%s”\n"
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
 msgstr ""
 "\t------[Retur] för att fortsätta eller a [Retur] för att avsluta------"
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr "a"
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
 msgstr "[\"%s\"] finns inte i vektorn ”%s”"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr "skickar utdata till standard ut\n"
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr "ogiltigt tal"
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "”%s” är inte tillåtet i det aktuella sammanhanget; satsen ignoreras"
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr ""
 "”return” är inte tillåtet i det aktuella sammanhanget; satsen ignoreras"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr "Ingen symbol ”%s” i aktuell omgivning"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr "obalanserad ["
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr "ogiltig teckenklass"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr "syntaxen för teckenklass är [[:space:]], inte [:space:]"
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr "oavslutad \\-följd"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
 msgstr "Ogiltigt innehåll i \\{\\}"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Reguljärt uttryck för stort"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
 msgstr "obalanserad ("
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr "ingen syntax angiven"
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
 msgstr "obalanserad )"
 
@@ -1845,11 +1856,11 @@ msgstr "okänd op-kod %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "op-kod %s är inte en operator eller ett nyckelord"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "buffertöverflöd i genflags2str"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1860,71 +1871,71 @@ msgstr ""
 "\t# Funktionsanropsstack:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
 msgstr "\"IGNORECASE\" är en gawk-utökning"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "\"BINMODE\" är en gawk-utökning"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
 msgstr "BINMODE-värde \"%s\" är ogiltigt, behandlas som 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "felaktig \"%sFMT\"-specifikation \"%s\""
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "slår av \"--lint\" på grund av en tilldelning till \"LINT\""
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
 msgstr "referens till icke initierat argument \"%s\""
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
 msgstr "referens till icke initierad variabel \"%s\""
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "försök att fältreferera från ickenumeriskt värde"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
 msgstr "försök till fältreferens från en tom sträng"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "försök att komma åt fält nummer %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "referens till icke initierat fält \"$%ld\""
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
 msgstr "funktionen \"%s\" anropad med fler argument än vad som deklarerats"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
 msgstr "unwind_stack: oväntad typ \"%s\""
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
 msgstr "försökte dividera med noll i \"/=\""
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
 msgstr "försökte dividera med noll i \"%%=\""
@@ -1937,7 +1948,7 @@ msgstr "utökningar är inte tillåtna i sandlådeläge"
 msgid "-l / @load are gawk extensions"
 msgstr "-l / @load är gawk-utökningar"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr "load_ext: mottog NULL-lib_name"
 
@@ -1968,6 +1979,10 @@ msgstr ""
 msgid "`extension' is a gawk extension"
 msgstr "\"extension\" är en gawk-utökning"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "utökning: mottog NULL-lib_name"
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -1989,37 +2004,37 @@ msgstr "extension: biblioteket ”%s”: kan inte anropa funktionen ”%s” (%s
 msgid "make_builtin: missing function name"
 msgstr "make_builtin: funktionsnamn saknas"
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "make_builtin: det går inte att definiera om funktionen ”%s”"
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "make_builtin: funktionen ”%s” är redan definierad"
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "make_builtin: funktionsnamnet ”%s” är definierat sedan tidigare"
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 "make_builtin: kan inte använda gawks inbyggda ”%s” som ett funktionsnamn"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: negativt argumentantal för funktionen \"%s\""
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr "extension: saknar funktionsnamn"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: ogiltigt tecken \"%c\" i funktionsnamnet \"%s\""
@@ -2045,139 +2060,143 @@ msgid "extension: can't use gawk built-in `%s' as function name"
 msgstr ""
 "extension: kan inte använda gawks inbyggda \"%s\" som ett funktionsnamn"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
 msgstr "funktionen \"%s\" definierades för att ta maximalt %d argument"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "funktionen \"%s\": argument %d saknas"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr "funktionen \"%s\": argument %d: försök att använda skalär som vektor"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr "funktionen \"%s\": argument %d: försök att använda vektor som skalär"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr "dynamisk laddning av bibliotek stödjs inte"
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "chdir: anropad med felaktigt antal argument, förväntade 1"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr "stat: kan inte läsa den symboliska länken ”%s”"
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr "stat: anropad med fel antal argument"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr "stat: felaktiga parametrar"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr "fts init: kunde inte skapa variabeln %s"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "fts stödjs inte på detta system"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr "fill_stat_element: kunde inte skapa en vektor"
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr "fill_stat_element: kunde inte sätta ett element"
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr "fill_path_element: kunde inte sätta ett element"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr "fill_error_element: kunde inte sätta ett element"
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr "fts-process: kunde inte skapa en vektor"
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr "fts-process: kunde inte sätta ett element"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "fts: anropad med felaktigt antal argument, förväntade 3"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr "fts: felaktig första parameter"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr "fts: felaktig andra parameter"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr "fts: felaktig tredje parameter"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr "fts: kunde inte platta till en vektor\n"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr "fts: ignorerar lömsk FTS_NOSTAT-flagga, nä, nä, nä."
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr "fts: clear_array() misslyckades\n"
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr "fnmatch: anropad färre an tre argument"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr "fnmatch: anropad med mer än tre argument"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr "fnmatch: kunde inte hämta första argumentet"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr "fnmatch: kunde inte hämta andra argumentet"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr "fnmatch: kunde inte hämta ett tredje argument"
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr "fnmatch är inte implementerat på detta system\n"
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr "fnmatch init: kunde inte lägga till en FNM_NOMATCH-variabel"
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr "fnmatch init: kunde inte sätta vektorelement %s"
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr "fnmatch init: kunde inte installera en FNM-vektor"
 
@@ -2201,89 +2220,89 @@ msgstr "wait: anropad utan argument"
 msgid "wait: called with too many arguments"
 msgstr "wait: anropad med för många argument"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr "inplace_begin: redigering på plats är redan aktivt"
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr "inplace_begin: förväntar sig 2 argument men anropad med %d"
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr "inplace_begin: kan inte hämta 1:a argumentet som en filnamnssträng"
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
 msgstr ""
 "inplace_begin: avaktiverar redigering på plats för ogiltigt FILNAMN ”%s”"
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
 msgstr "inplace_begin: kan inte ta status på ”%s” (%s)"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "inplace_begin: ”%s” är inte en vanlig fil"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr "inplace_begin: mkstemp(”%s”) misslyckades (%s)"
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "inplace_begin: chmod misslyckades (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr "inplace_begin: dup(standard ut) misslyckades (%s)"
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_begin: dup2(%d, standard ut) misslyckades (%s)"
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "inplace_begin: close(%d) misslyckades (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr "inplace_end: kan inte hämta 1:a argumentet som en filnamnssträng"
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr "inplace_end: redigering på plats är inte aktivt"
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_end: dup2(%d, standard ut) misslyckades (%s)"
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "inplace_end: close(%d) misslyckades (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr "inplace_end: fsetpos(standard ut) misslyckades (%s)"
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "inplace_end: link(”%s”, ”%s”) misslyckades (%s)"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "inplace_end: rename(”%s”, ”%s”) misslyckades (%s)"
@@ -2312,175 +2331,175 @@ msgstr "chr: anropad utan argument"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "chr: anropad med felaktiga argument"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr "dir_take_control_of: opendir/fdopendir misslyckades: %s"
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr "readfile: anropad med för många argument"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr "readfile: anropad utan argument"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr "writea: anropad med för många argument"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "do_writea: argument 0 är inte en sträng\n"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "do_writea: argument 1 är inte en vektor\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr "write_array: kunde inte platta till vektor\n"
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr "write_array: kunde inte släppa en tillplattad vektor\n"
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr "reada: anropad med för många argument"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "do_reada: argument 0 är inte en sträng\n"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "do_reada: argument 1 är inte en vektor\n"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr "do_reada: clear_array misslyckades\n"
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr "read_array: set_array_element misslyckades\n"
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr "gettimeofday: ignorerar argumenten"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr "gettimeofday: stödjs inte på denna plattform"
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr "sleep: anropad med för många argument"
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr "sleep: nödvändigt numeriskt argument saknas"
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr "sleep: argumentet är negativt"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr "sleep: stödjs inte på denna plattform"
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "NF satt till ett negativt värde"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split: fjärde argumentet är en gawk-utökning"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split: fjärde argumentet är inte en vektor"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: andra argumentet är inte en vektor"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 "split: det går inte att använda samma vektor som andra och fjärde argument"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split: det går inte att använda en delvektor av andra argumentet som fjärde "
 "argument"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split: det går inte att använda en delvektor av fjärde argumentet som andra "
 "argument"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr "split: tom sträng som tredje argument är en gawk-utökning"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: fjärde argumentet är inte en vektor"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: andra argumentet är inte en vektor"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: tredje argumentet får inte vara tomt"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit: det går inte att använda samma vektor som andra och fjärde argument"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit: det går inte att använda en delvektor av andra argumentet som "
 "fjärde argument"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit: det går inte att använda en delvektor av fjärde argumentet som "
 "andra argument"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "\"FIELDWIDTHS\" är en gawk-utökning"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "ogiltigt FIELDWITHS-värde i närheten av \"%s\""
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "tom sträng som \"FS\" är en gawk-utökning"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "gamla awk stöder inte reguljära uttryck som värden på \"FS\""
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "\"FPAT\" är en gawk-utökning"
 
@@ -2496,361 +2515,361 @@ msgstr "node_to_awk_value: mottog null-nod"
 msgid "node_to_awk_value: received null val"
 msgstr "node_to_awk_value: mottog null-värde"
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr "remove_element: fick en null-vektor"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr "remove_element: mottog null-index"
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr "api_flatten_array: kunde inte konvertera index %d\n"
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr "api_flatten_array: kunde inte konvertera värdet %d\n"
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: flaggan ”%s” är tvetydig; möjligheter:"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: flaggan \"--%s\" tillåter inte något argument\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: flaggan \"%c%s\" tillåter inte något argument\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: flaggan \"%s\" kräver ett argument\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: okänd flagga \"--%s\"\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: okänd flagga \"%c%s\"\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: ogiltig flagga -- \"%c\"\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: flaggan kräver ett argument -- \"%c\"\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: flaggan \"-W %s\" är tvetydig\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: flaggan \"-W %s\" tillåter inte något argument\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: flaggan \"-W %s\" kräver ett argument\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "kommandoradsargumentet \"%s\" är en katalog: hoppas över"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "kan inte öppna filen \"%s\" för läsning (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "stängning av fd %d (\"%s\") misslyckades (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "omdirigering är inte tillåten i sandlådeläge"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "uttrycket i \"%s\"-omdirigering har bara numeriskt värde"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "uttrycket för \"%s\"-omdirigering har en tom sträng som värde"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "filnamnet \"%s\" för \"%s\"-omdirigering kan vara resultatet av ett logiskt "
 "uttryck"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "onödig blandning av \">\" och \">>\" för filen \"%.*s\""
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "kan inte öppna röret \"%s\" för utmatning (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "kan inte öppna röret \"%s\" för inmatning (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr "kan inte öppna tvåvägsröret \"%s\" för in-/utmatning (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "kan inte dirigera om från \"%s\" (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "kan inte dirigera om till \"%s\" (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "nådde systembegränsningen för öppna filer: börjar multiplexa fildeskriptorer"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "stängning av \"%s\" misslyckades (%s)"
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "för många rör eller indatafiler öppna"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: andra argumentet måste vara \"to\" eller \"from\""
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr "close: \"%.*s\" är inte en öppen fil, rör eller koprocess"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "stängning av omdirigering som aldrig öppnades"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: omdirigeringen \"%s\" öppnades inte med \"|&\", andra argumentet "
 "ignorerat"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "felstatus (%d) från rörstängning av \"%s\" (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "felstatus (%d) från filstängning av \"%s\" (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "ingen explicit stängning av uttaget \"%s\" tillhandahållen"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "ingen explicit stängning av koprocessen \"%s\" tillhandahållen"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "ingen explicit stängning av röret \"%s\" tillhandahållen"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "ingen explicit stängning av filen \"%s\" tillhandahållen"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "fel vid skrivning till standard ut (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "fel vid skrivning till standard fel (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "rörspolning av \"%s\" misslyckades (%s)"
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "koprocesspolning av röret till \"%s\" misslyckades (%s)"
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "filspolning av \"%s\" misslyckades (%s)"
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "lokal port %s ogiltig i \"/inet\""
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "ogiltig information (%s, %s) för fjärrvärd och fjärrport"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr ""
 "inget (känt) protokoll tillhandahållet i det speciella filnamnet \"%s\""
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "speciellt filnamn \"%s\" är ofullständigt"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "måste tillhandahålla ett fjärrdatornamn till \"/inet\""
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "måste tillhandahålla en fjärrport till \"/inet\""
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "TCP/IP-kommunikation stöds inte"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "kunde inte öppna \"%s\", läge \"%s\""
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
 msgstr "stängning av huvudpty misslyckades (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
 msgstr "stängning av standard ut i barnet misslyckades (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr "flyttandet av slavpty till standard ut i barnet misslyckades (dup: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "stängning av standard in i barnet misslyckades (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr "flyttandet av slavpty till standard in i barnet misslyckades (dup: %s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
 msgstr "stängning av slavpty misslyckades (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr "flyttande av rör till standard ut i barnet misslyckades (dup: %s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr "flyttande av rör till standard in i barnet misslyckades (dup: %s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "återställande av standard ut i förälderprocessen misslyckades\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "återställande av standard in i förälderprocessen misslyckades\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "stängning av röret misslyckades (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "\"|&\" stöds inte"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "kan inte öppna röret \"%s\" (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "kan inte skapa barnprocess för \"%s\" (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr "register_input_parser: mottog NULL-pekare"
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 "inmatningstolken ”%s” står i konflikt med tidigare installerad "
 "inmatningstolk ”%s”"
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr "inmatningstolken ”%s” misslyckades att öppna ”%s”"
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr "register_output_wrapper: mottog NULL-pekare"
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
@@ -2858,16 +2877,16 @@ msgstr ""
 "utmatningsomslag ”%s” står i konflikt med tidigare installerat "
 "utmatningsomslag ”%s”"
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr "utmatningsomslag ”%s” misslyckades att öpnna ”%s”"
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr "register_output_processor: mottog NULL-pekare"
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
@@ -2876,210 +2895,210 @@ msgstr ""
 "tvåvägsprocessorn ”%s” står i konflikt med tidigare installerad "
 "tvåvägsprocessor ”%s”"
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr "tvåvägsprocessorn ”%s” misslyckades att öppna ”%s”"
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "datafilen \"%s\" är tom"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "kunde inte allokera mer indataminne"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "flerteckensvärdet av \"RS\" är en gawk-utökning"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "IPv6-kommunikation stöds inte"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "tomt argument till \"-e/--source\" ignorerat"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: flaggan \"-W %s\" okänd, ignorerad\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: flaggan kräver ett argument -- %c\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr "miljövariabeln \"POSIXLY_CORRECT\" satt: slår på \"--posix\""
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "\"--posix\" åsidosätter \"--traditional\""
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr "\"--posix\"/\"--traditional\" åsidosätter \"--non-decimal-data\""
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "att köra %s setuid root kan vara ett säkerhetsproblem"
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "”--posix” åsidosätter ”--character-as-bytes”"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
 msgstr "kan inte sätta binärläge på standard in (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
 msgstr "kan inte sätta binärläge på standard ut (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
 msgstr "kan inte sätta binärläge på standard fel (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
 msgstr "ingen programtext alls!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 "Användning: %s [POSIX- eller GNU-stilsflaggor] -f progfil [--] fil ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr "Användning: %s [POSIX- eller GNU-stilsflaggor] %cprogram%c fil ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
 msgstr "POSIX-flaggor:\t\tGNU långa flaggor: (standard)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
 msgstr "\t-f progfil\t\t--file=progfil\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
 msgstr "\t-F fs\t\t\t--field-separator=fs\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr "\t-v var=värde\t\t--assign=var=värde\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
 msgstr "Korta flaggor:\t\tGNU långa flaggor: (utökningar)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
 msgstr "\t-d[fil]\t\t\t--dump-variables[=fil]\n"
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-D[fil]\t\t\t--debug[=fil]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
 msgstr "\t-e 'programtext'\t--source='programtext'\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
 msgstr "\t-E fil\t\t\t--exec=fil\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr "\t-i inkluderingsfil\t--include=inkluderingsfil\n"
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr "\t-l bibliotek\t\t--load=bibliotek\n"
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-o[fil]\t\t\t--pretty-print[=fil]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
 msgstr "\t-O\t\t\t--optimize\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
 msgstr "\t-p[fil]\t\t\t--profile[=fil]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr "\t-W nostalgia\t\t--nostalgia\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3088,7 +3107,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3102,7 +3121,7 @@ msgstr ""
 "Rapportera synpunkter på översättningen till <tp-sv@listor.tp-sv.se>.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
@@ -3112,7 +3131,7 @@ msgstr ""
 "Normalt läser det från standard in och skriver till standard ut.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
@@ -3122,7 +3141,7 @@ msgstr ""
 "\tgawk '{ sum += $1 }; END { print sum }' fil\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3141,7 +3160,7 @@ msgstr ""
 "någon senare version.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3155,7 +3174,7 @@ msgstr ""
 "General Public License för ytterligare information.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
@@ -3163,64 +3182,64 @@ msgstr ""
 "Du bör ha fått en kopia av GNU General Public License tillsammans\n"
 "med detta program. Om inte, se http//www.gnu.org/liceences/.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft sätter inte FS till tab i POSIX-awk"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
 msgstr "okänt värde till fältspecifikation: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
 "\n"
 msgstr "%s: Argumentet \"%s\" till \"-v\" är inte på formatet \"var=värde\"\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "\"%s\" är inte ett giltigt variabelnamn"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "\"%s\" är inte ett variabelnamn, letar efter filen \"%s=%s\""
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "kan inte använda gawks inbyggda \"%s\" som ett funktionsnamn"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "kan inte använda funktionen \"%s\" som variabelnamn"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
 msgstr "flyttalsundantag"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "ödesdigert fel: internt fel"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
 msgstr "ödesdigert fel: internt fel: segmenteringsfel"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
 msgstr "ödesdigert fel: internt fel: stackspill"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "ingen föröppnad fd %d"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "kunde inte föröppna /dev/null för fd %d"
@@ -3275,7 +3294,7 @@ msgstr "%s: argument nr. %d flyttalsvärde %Rg kommer huggas av"
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "%s: argument nr. %d negativa värde %Zd kommer ge konstiga resultat"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "kommandorad:"
@@ -3329,16 +3348,16 @@ msgstr "%s %s \"%s\": kunde inte hämta fb-flaggor: (fcntl F_GETFD: %s)"
 msgid "%s %s `%s': could not set close-on-exec: (fcntl F_SETFD: %s)"
 msgstr "%s %s \"%s\": kunde inte sätta stäng-vid-exec (fcntl F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "kunde inte öppna \"%s\" för skrivning: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "skickar profilen till standard fel"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3347,7 +3366,7 @@ msgstr ""
 "\t# %s-block\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3356,16 +3375,16 @@ msgstr ""
 "\t# Regel/regler\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "internt fel: %s med null vname"
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr "internt fel: inbyggd med tomt fname"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
@@ -3374,12 +3393,12 @@ msgstr ""
 "\t# Laddade utvidgningar (-l och/eller @load)\n"
 "\n"
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# gawkprofil, skapad %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3388,17 +3407,12 @@ msgstr ""
 "\n"
 "\t# Funktioner, listade alfabetiskt\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: okänd omdirigeringstyp %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "intervall på formen \"[%c-%c]\" är lokalberoende"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
@@ -3468,6 +3482,6 @@ msgstr "Obalanserad ) eller \\)"
 msgid "No previous regular expression"
 msgstr "Inget föregående reguljärt uttryck"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
 msgstr "kan inte poppa huvudsammanhang"
diff --git a/po/vi.gmo b/po/vi.gmo
index debb0899..10c710dc 100644
--- a/po/vi.gmo
+++ b/po/vi.gmo
diff --git a/po/vi.po b/po/vi.po
index 400477b8..faa458a1 100644
--- a/po/vi.po
+++ b/po/vi.po
@@ -1,15 +1,16 @@
 # Vietnamese translation for Gawk.
-# Copyright © 2013 Free Software Foundation, Inc.
+# Bản dịch Tiếng Việt dành cho Gawk.
+# Copyright © 2014 Free Software Foundation, Inc.
 # This file is distributed under the same license as the gawk package.
 # Clytie Siddall <clytie@riverland.net.au>, 2005-2010.
-# Trần Ngọc Quân <vnwildman@gmail.com>, 2012-2013.
+# Trần Ngọc Quân <vnwildman@gmail.com>, 2012-2014.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: gawk-4.0.75\n"
+"Project-Id-Version: gawk-4.1.0b\n"
 "Report-Msgid-Bugs-To: arnold@skeeve.com\n"
-"POT-Creation-Date: 2013-05-09 16:05+0300\n"
-"PO-Revision-Date: 2013-04-24 08:11+0700\n"
+"POT-Creation-Date: 2014-04-08 19:23+0300\n"
+"PO-Revision-Date: 2014-01-16 14:52+0700\n"
 "Last-Translator: Trần Ngọc Quân <vnwildman@gmail.com>\n"
 "Language-Team: Vietnamese <translation-team-vi@lists.sourceforge.net>\n"
 "Language: vi\n"
@@ -20,92 +21,92 @@ msgstr ""
 "X-Generator: Poedit 1.5.5\n"
 "X-Poedit-SourceCharset: UTF-8\n"
 
-#: array.c:254
+#: array.c:256
 #, c-format
 msgid "from %s"
 msgstr "từ %s"
 
-#: array.c:354
+#: array.c:357
 msgid "attempt to use a scalar value as array"
 msgstr "cố dùng giá trị vô hướng như là một mảng"
 
-#: array.c:356
+#: array.c:359
 #, c-format
 msgid "attempt to use scalar parameter `%s' as an array"
 msgstr "cố dùng tham số vô hướng “%s” như là mảng"
 
-#: array.c:359
+#: array.c:362
 #, c-format
 msgid "attempt to use scalar `%s' as an array"
 msgstr "cố dùng “%s” vô hướng như là mảng"
 
-#: array.c:406 array.c:573 builtin.c:85 builtin.c:1591 builtin.c:1637
-#: builtin.c:1650 builtin.c:2078 builtin.c:2092 eval.c:1121 eval.c:1125
-#: eval.c:1524
+#: array.c:409 array.c:576 builtin.c:85 builtin.c:1615 builtin.c:1661
+#: builtin.c:1674 builtin.c:2102 builtin.c:2116 eval.c:1122 eval.c:1126
+#: eval.c:1531
 #, c-format
 msgid "attempt to use array `%s' in a scalar context"
 msgstr "cố gắng dùng mảng “%s” trong một ngữ cảnh vô hướng"
 
-#: array.c:580
+#: array.c:583
 #, c-format
 msgid "delete: index `%s' not in array `%s'"
 msgstr "delete: (xoá) chỉ số “%s” không nằm trong mảng “%s”"
 
-#: array.c:594
+#: array.c:597
 #, c-format
 msgid "attempt to use scalar `%s[\"%.*s\"]' as an array"
-msgstr "cố dùng “%s[”%.*s”]” vô hướng như là mảng"
+msgstr "cố dùng “%s[\"%.*s\"]” vô hướng như là mảng"
 
-#: array.c:773
+#: array.c:776
 msgid "adump: first argument not an array"
 msgstr "adump: đối số thứ nhất không phải là một mảng"
 
-#: array.c:812
+#: array.c:815
 msgid "asort: second argument not an array"
 msgstr "asort: đối số thứ hai không phải là một mảng"
 
-#: array.c:813
+#: array.c:816
 msgid "asorti: second argument not an array"
 msgstr "asorti: đối số thứ hai không phải là một mảng"
 
-#: array.c:820
+#: array.c:823
 msgid "asort: first argument not an array"
 msgstr "asort: đối số thứ nhất không phải là một mảng"
 
-#: array.c:821
+#: array.c:824
 msgid "asorti: first argument not an array"
 msgstr "asorti: đối số thứ nhất không phải là một mảng"
 
-#: array.c:828
+#: array.c:831
 msgid "asort: cannot use a subarray of first arg for second arg"
 msgstr ""
-"asort (một chương trính xắp xếp thứ tự): không thể sử dụng mảng con của tham "
+"asort (một chương trình xắp xếp thứ tự): không thể sử dụng mảng con của tham "
 "số thứ nhất cho tham số thứ hai"
 
-#: array.c:829
+#: array.c:832
 msgid "asorti: cannot use a subarray of first arg for second arg"
 msgstr ""
-"asorti (một chương trính xắp xếp thứ tự): không thể sử dụng mảng con của "
+"asorti (một chương trình xắp xếp thứ tự): không thể sử dụng mảng con của "
 "tham số thứ nhất cho tham số thứ hai"
 
-#: array.c:834
+#: array.c:837
 msgid "asort: cannot use a subarray of second arg for first arg"
 msgstr ""
-"asort (một chương trính xắp xếp thứ tự): không thể sử dụng mảng con của tham "
+"asort (một chương trình xắp xếp thứ tự): không thể sử dụng mảng con của tham "
 "số thứ hai cho tham số thứ nhất"
 
-#: array.c:835
+#: array.c:838
 msgid "asorti: cannot use a subarray of second arg for first arg"
 msgstr ""
-"asorti (một chương trính xắp xếp thứ tự): không thể sử dụng mảng con của "
+"asorti (một chương trình xắp xếp thứ tự): không thể sử dụng mảng con của "
 "tham số thứ hai cho tham số thứ nhất"
 
-#: array.c:1309
+#: array.c:1314
 #, c-format
 msgid "`%s' is invalid as a function name"
 msgstr "“%s” không phải là tên hàm hợp lệ"
 
-#: array.c:1313
+#: array.c:1318
 #, c-format
 msgid "sort comparison function `%s' is not defined"
 msgstr "chưa định nghĩa hàm so sánh xắp xếp “%s”"
@@ -152,12 +153,12 @@ msgid "duplicate `default' detected in switch body"
 msgstr ""
 "đã phát hiện trùng “default” trong thân cấu trúc điều khiển chọn lựa (switch)"
 
-#: awkgram.y:796 awkgram.y:3699
+#: awkgram.y:796 awkgram.y:3723
 msgid "`break' is not allowed outside a loop or switch"
 msgstr ""
 "không cho phép “break” (ngắt) nằm ở ngoại vòng lặp hay cấu trúc chọn lựa"
 
-#: awkgram.y:805 awkgram.y:3691
+#: awkgram.y:805 awkgram.y:3715
 msgid "`continue' is not allowed outside a loop"
 msgstr "không cho phép “continue” (tiếp tục) ở ngoài một vòng lặp"
 
@@ -169,7 +170,7 @@ msgstr "“next” (kế tiếp) được dùng trong hành động %s"
 #: awkgram.y:824
 #, c-format
 msgid "`nextfile' used in %s action"
-msgstr "“nextfile” (tệp tin kế tiếp) được dùng trong hành động %s"
+msgstr "“nextfile” (tập tin kế tiếp) được dùng trong hành động %s"
 
 #: awkgram.y:848
 msgid "`return' used outside function context"
@@ -227,7 +228,7 @@ msgstr "“getline” không hợp lệ trong quy tắc “%s”"
 msgid "non-redirected `getline' undefined inside END action"
 msgstr ""
 "trong hành động “END” (kết thúc) có “getline” (lấy dòng) không được chuyển "
-"hướng lại và chưa được xác định."
+"hướng lại và chưa được định nghĩa."
 
 #: awkgram.y:1444
 msgid "old awk does not support multidimensional arrays"
@@ -252,270 +253,270 @@ msgstr "không thể dùng biến đặc biệt “%s” cho cú gọi hàm giá
 msgid "invalid subscript expression"
 msgstr "biểu thức in thấp không hợp lệ"
 
-#: awkgram.y:2024 awkgram.y:2044 gawkapi.c:206 gawkapi.c:224 msg.c:119
+#: awkgram.y:2048 awkgram.y:2068 gawkapi.c:206 gawkapi.c:224 msg.c:126
 msgid "warning: "
 msgstr "cảnh báo: "
 
-#: awkgram.y:2042 gawkapi.c:192 gawkapi.c:221 msg.c:151
+#: awkgram.y:2066 gawkapi.c:192 gawkapi.c:221 msg.c:158
 msgid "fatal: "
-msgstr "nghiêm trọng: "
+msgstr "lỗi nghiêm trọng: "
 
-#: awkgram.y:2092
+#: awkgram.y:2116
 msgid "unexpected newline or end of string"
-msgstr "gặp dòng mới bất ngờ hay kết thúc của chuỗi"
+msgstr "gặp dòng mới hay kết thúc chuỗi bất ngờ"
 
-#: awkgram.y:2359 awkgram.y:2435 awkgram.y:2658 debug.c:517 debug.c:533
-#: debug.c:2792 debug.c:5040
+#: awkgram.y:2383 awkgram.y:2459 awkgram.y:2682 debug.c:523 debug.c:539
+#: debug.c:2812 debug.c:5055
 #, c-format
 msgid "can't open source file `%s' for reading (%s)"
 msgstr "không thể mở tập tin nguồn “%s” để đọc (%s)"
 
-#: awkgram.y:2360 awkgram.y:2485
+#: awkgram.y:2384 awkgram.y:2509
 #, c-format
 msgid "can't open shared library `%s' for reading (%s)"
 msgstr "không thể mở tập thư viện chia sẻ “%s” để đọc (%s)"
 
-#: awkgram.y:2362 awkgram.y:2436 awkgram.y:2486 builtin.c:130 debug.c:5191
+#: awkgram.y:2386 awkgram.y:2460 awkgram.y:2510 builtin.c:135 debug.c:5206
 msgid "reason unknown"
-msgstr "không biết sao"
+msgstr "không rõ lý do"
 
-#: awkgram.y:2371 awkgram.y:2395
+#: awkgram.y:2395 awkgram.y:2419
 #, c-format
 msgid "can't include `%s' and use it as a program file"
 msgstr "không thể bao gồm “%s” và dùng nó như là tập tin chương trình"
 
-#: awkgram.y:2384
+#: awkgram.y:2408
 #, c-format
 msgid "already included source file `%s'"
 msgstr "đã sẵn bao gồm tập tin nguồn “%s”"
 
-#: awkgram.y:2385
+#: awkgram.y:2409
 #, c-format
 msgid "already loaded shared library `%s'"
-msgstr "thư viện dùng chung “%s” đã được sẵn được tải rồi "
+msgstr "thư viện dùng chung “%s” đã được sẵn được tải rồi"
 
-#: awkgram.y:2420
+#: awkgram.y:2444
 msgid "@include is a gawk extension"
 msgstr "@include là phần mở rộng của gawk"
 
-#: awkgram.y:2426
+#: awkgram.y:2450
 msgid "empty filename after @include"
-msgstr "tệp tin trống sau @include"
+msgstr "tập tin trống sau @include"
 
-#: awkgram.y:2470
+#: awkgram.y:2494
 msgid "@load is a gawk extension"
 msgstr "@load là một phần mở rộng gawk"
 
-#: awkgram.y:2476
+#: awkgram.y:2500
 msgid "empty filename after @load"
-msgstr "tên tệp tin trống sau @load"
+msgstr "tên tập tin trống sau @load"
 
-#: awkgram.y:2610
+#: awkgram.y:2634
 msgid "empty program text on command line"
 msgstr "gặp đoạn chữ chương trình rỗng nằm trên dòng lệnh"
 
-#: awkgram.y:2725
+#: awkgram.y:2749
 #, c-format
 msgid "can't read sourcefile `%s' (%s)"
 msgstr "không thể đọc tập tin nguồn “%s” (%s)"
 
-#: awkgram.y:2736
+#: awkgram.y:2760
 #, c-format
 msgid "source file `%s' is empty"
 msgstr "tập tin nguồn “%s” là rỗng"
 
-#: awkgram.y:2913
+#: awkgram.y:2937
 msgid "source file does not end in newline"
 msgstr "tập tin nguồn không kết thúc với một dòng mới"
 
-#: awkgram.y:3018
+#: awkgram.y:3042
 msgid "unterminated regexp ends with `\\' at end of file"
 msgstr ""
 "biểu thức chính quy chưa được chấm dứt kết thúc với “\\” tại kết thúc của "
 "tập tin"
 
-#: awkgram.y:3042
+#: awkgram.y:3066
 #, c-format
 msgid "%s: %d: tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "%s: %d: bộ sửa đổi biểu thức chính quy tawk “/.../%c” không hoạt động được "
 "trong gawk"
 
-#: awkgram.y:3046
+#: awkgram.y:3070
 #, c-format
 msgid "tawk regex modifier `/.../%c' doesn't work in gawk"
 msgstr ""
 "bộ sửa đổi biểu thức chính quy tawk “/.../%c” không hoạt động được trong gawk"
 
-#: awkgram.y:3053
+#: awkgram.y:3077
 msgid "unterminated regexp"
 msgstr "biểu thức chính quy chưa được chấm dứt"
 
-#: awkgram.y:3057
+#: awkgram.y:3081
 msgid "unterminated regexp at end of file"
 msgstr "biểu thức chính quy chưa được chấm dứt nằm tại kết thúc của tập tin"
 
-#: awkgram.y:3116
+#: awkgram.y:3140
 msgid "use of `\\ #...' line continuation is not portable"
 msgstr "không thể mang khả năng dùng “\\#...” để tiếp tục dòng"
 
-#: awkgram.y:3132
+#: awkgram.y:3156
 msgid "backslash not last character on line"
-msgstr "xuyệc ngược không phải là ký tự cuối cùng nằm trên dòng"
+msgstr "dấu gạch ngược không phải là ký tự cuối cùng nằm trên dòng"
 
-#: awkgram.y:3193
+#: awkgram.y:3217
 msgid "POSIX does not allow operator `**='"
 msgstr "POSIX không cho phép toán tử “**=”"
 
-#: awkgram.y:3195
+#: awkgram.y:3219
 msgid "old awk does not support operator `**='"
 msgstr "awk cũ không hỗ trợ toán tử “**=”"
 
-#: awkgram.y:3204
+#: awkgram.y:3228
 msgid "POSIX does not allow operator `**'"
 msgstr "POSIX không cho phép toán tử “**”"
 
-#: awkgram.y:3206
+#: awkgram.y:3230
 msgid "old awk does not support operator `**'"
 msgstr "awk cũ không hỗ trợ toán tử “**”"
 
-#: awkgram.y:3241
+#: awkgram.y:3265
 msgid "operator `^=' is not supported in old awk"
 msgstr "awk cũ không hỗ trợ toán tử “^=”"
 
-#: awkgram.y:3249
+#: awkgram.y:3273
 msgid "operator `^' is not supported in old awk"
 msgstr "awk cũ không hỗ trợ toán tử “^”"
 
-#: awkgram.y:3342 awkgram.y:3358 command.y:1178
+#: awkgram.y:3366 awkgram.y:3382 command.y:1178
 msgid "unterminated string"
 msgstr "chuỗi không được chấm dứt"
 
-#: awkgram.y:3579
+#: awkgram.y:3603
 #, c-format
 msgid "invalid char '%c' in expression"
 msgstr "có ký tự không hợp lệ “%c” nằm trong biểu thức"
 
-#: awkgram.y:3626
+#: awkgram.y:3650
 #, c-format
 msgid "`%s' is a gawk extension"
 msgstr "“%s” là một phần mở rộng gawk"
 
-#: awkgram.y:3631
+#: awkgram.y:3655
 #, c-format
 msgid "POSIX does not allow `%s'"
 msgstr "POSIX không cho phép “%s”"
 
-#: awkgram.y:3639
+#: awkgram.y:3663
 #, c-format
 msgid "`%s' is not supported in old awk"
 msgstr "awk kiểu cũ không hỗ trợ “%s”"
 
-#: awkgram.y:3729
+#: awkgram.y:3753
 msgid "`goto' considered harmful!\n"
 msgstr "“goto” được xem là có hại!\n"
 
-#: awkgram.y:3763
+#: awkgram.y:3787
 #, c-format
 msgid "%d is invalid as number of arguments for %s"
 msgstr "“%d” không hợp lệ khi là số đối số cho “%s”"
 
-#: awkgram.y:3798
+#: awkgram.y:3822
 #, c-format
 msgid "%s: string literal as last arg of substitute has no effect"
 msgstr ""
 "%s: khi đối số cuối cùng của sự thay thế, hằng mã nguồn chuỗi không có tác "
 "dụng"
 
-#: awkgram.y:3803
+#: awkgram.y:3827
 #, c-format
 msgid "%s third parameter is not a changeable object"
 msgstr "tham số thứ ba %s không phải là một đối tượng có thể thay đổi"
 
-#: awkgram.y:3886 awkgram.y:3889
+#: awkgram.y:3910 awkgram.y:3913
 msgid "match: third argument is a gawk extension"
 msgstr "match: (khớp) đối số thứ ba là phần mở rộng gawk"
 
-#: awkgram.y:3943 awkgram.y:3946
+#: awkgram.y:3967 awkgram.y:3970
 msgid "close: second argument is a gawk extension"
 msgstr "close: (đóng) đối số thứ hai là phần mở rộng gawk"
 
-#: awkgram.y:3958
+#: awkgram.y:3982
 msgid "use of dcgettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "dùng “dcgettext(_\"...\")” không đúng: hãy gỡ bỏ gạch dưới nằm trước"
 
-#: awkgram.y:3973
+#: awkgram.y:3997
 msgid "use of dcngettext(_\"...\") is incorrect: remove leading underscore"
 msgstr "dùng “dcgettext(_\"...\")” không đúng: hãy gỡ bỏ gạch dưới nằm trước"
 
-#: awkgram.y:3992
-#, fuzzy
+#: awkgram.y:4016
 msgid "index: regexp constant as second argument is not allowed"
-msgstr "index: (chỉ mục) đã nhận đối số thứ hai không phải là chuỗi"
+msgstr ""
+"index: (chỉ mục) không cho phép hằng biểu thức chính quy làm đối số thứ hai"
 
-#: awkgram.y:4045
+#: awkgram.y:4069
 #, c-format
 msgid "function `%s': parameter `%s' shadows global variable"
 msgstr "hàm “%s”: tham số “%s” che biến toàn cục"
 
-#: awkgram.y:4102 debug.c:4021 debug.c:4064 debug.c:5189
+#: awkgram.y:4126 debug.c:4041 debug.c:4084 debug.c:5204
 #, c-format
 msgid "could not open `%s' for writing (%s)"
 msgstr "không mở được “%s” để ghi (%s)"
 
-#: awkgram.y:4103
+#: awkgram.y:4127
 msgid "sending variable list to standard error"
 msgstr "đang gởi danh sách biến tới thiết bị lỗi chuẩn"
 
-#: awkgram.y:4111
+#: awkgram.y:4135
 #, c-format
 msgid "%s: close failed (%s)"
-msgstr "%s: lỗi đóng (%s)"
+msgstr "%s: gặp lỗi khi đóng (%s)"
 
-#: awkgram.y:4136
+#: awkgram.y:4160
 msgid "shadow_funcs() called twice!"
 msgstr "shadow_funcs() (hàm bóng) được gọi hai lần!"
 
-#: awkgram.y:4144
+#: awkgram.y:4168
 msgid "there were shadowed variables."
 msgstr "có biến bị bóng."
 
-#: awkgram.y:4215
+#: awkgram.y:4239
 #, c-format
 msgid "function name `%s' previously defined"
 msgstr "tên hàm “%s” trước đây đã được định nghĩa rồi"
 
-#: awkgram.y:4261
+#: awkgram.y:4285
 #, c-format
 msgid "function `%s': can't use function name as parameter name"
 msgstr "hàm “%s”: không thể dùng tên hàm như là tên tham số"
 
-#: awkgram.y:4264
+#: awkgram.y:4288
 #, c-format
 msgid "function `%s': can't use special variable `%s' as a function parameter"
 msgstr "hàm “%s”: không thể dùng biến đặc biệt “%s” như là tham số hàm"
 
-#: awkgram.y:4272
+#: awkgram.y:4296
 #, c-format
 msgid "function `%s': parameter #%d, `%s', duplicates parameter #%d"
 msgstr "hàm “%s”: tham số “#%d”, “%s”, nhân đôi tham số “#%d”"
 
-#: awkgram.y:4366 awkgram.y:4372
+#: awkgram.y:4383 awkgram.y:4389
 #, c-format
 msgid "function `%s' called but never defined"
-msgstr "hàm “%s” được gọi nhưng mà chưa xác định"
+msgstr "hàm “%s” được gọi nhưng mà chưa định nghĩa"
 
-#: awkgram.y:4376
+#: awkgram.y:4393
 #, c-format
 msgid "function `%s' defined but never called directly"
 msgstr "hàm “%s” được định nghĩa nhưng mà chưa được gọi trực tiếp bao giờ"
 
-#: awkgram.y:4408
+#: awkgram.y:4425
 #, c-format
 msgid "regexp constant for parameter #%d yields boolean value"
 msgstr "hằng biểu thức chính quy cho tham số “#%d” làm giá trị luận lý (bun)"
 
-#: awkgram.y:4467
+#: awkgram.y:4484
 #, c-format
 msgid ""
 "function `%s' called with space between name and `(',\n"
@@ -524,428 +525,443 @@ msgstr ""
 "hàm “%s” được gọi với dấu cách nằm giữa tên và “(”\n"
 "hoặc được dùng như là biến hay mảng"
 
-#: awkgram.y:4703
+#: awkgram.y:4720
 msgid "division by zero attempted"
-msgstr "cố gắng chia cho số không"
+msgstr "gặp phép chia cho số không"
 
-#: awkgram.y:4712
+#: awkgram.y:4729
 #, c-format
 msgid "division by zero attempted in `%%'"
-msgstr "thử chia cho không trong “%%”"
+msgstr "gặp phép chia cho số không trong “%%”"
+
+#: awkgram.y:5049
+msgid ""
+"cannot assign a value to the result of a field post-increment expression"
+msgstr "không thể gán giá trị cho kết quả của biểu thức trường tăng-trước"
+
+#: awkgram.y:5052
+#, c-format
+msgid "invalid target of assignment (opcode %s)"
+msgstr "gán đich không hợp lệ (mã thi hành “%s”)"
 
-#: builtin.c:128
+#: builtin.c:133
 #, c-format
 msgid "%s to \"%s\" failed (%s)"
 msgstr "%s tới “%s” gặp lỗi (%s)"
 
-#: builtin.c:129
+#: builtin.c:134
 msgid "standard output"
 msgstr "đầu ra tiêu chuẩn"
 
-#: builtin.c:143
+#: builtin.c:148
 msgid "exp: received non-numeric argument"
 msgstr "exp: đã nhận đối số không phải thuộc số"
 
-#: builtin.c:149
+#: builtin.c:154
 #, c-format
 msgid "exp: argument %g is out of range"
 msgstr "exp: đối số “%g” nằm ngoài phạm vi"
 
-#: builtin.c:224
+#: builtin.c:229
 #, c-format
 msgid "fflush: cannot flush: pipe `%s' opened for reading, not writing"
 msgstr ""
 "fflush: không thể flush (đẩy dữ liệu lên đĩa): ống dẫn “%s” được mở để đọc, "
 "không phải để ghi"
 
-#: builtin.c:227
+#: builtin.c:232
 #, c-format
 msgid "fflush: cannot flush: file `%s' opened for reading, not writing"
 msgstr ""
 "fflush: không thể flush (đẩy dữ liệu vào đĩa): tập tin “%s” được mở để đọc, "
 "không phải để ghi"
 
-#: builtin.c:239
+#: builtin.c:244
 #, c-format
 msgid "fflush: `%s' is not an open file, pipe or co-process"
 msgstr ""
 "fflush: “%s” không phải là tập tin, ống dẫn hay đồng tiến trình được mở"
 
-#: builtin.c:357
+#: builtin.c:362
 msgid "index: received non-string first argument"
 msgstr "index: (chỉ số) đã nhận đối số thứ nhất không phải là chuỗi"
 
-#: builtin.c:359
+#: builtin.c:364
 msgid "index: received non-string second argument"
-msgstr "index: (chỉ mục) đã nhận đối số thứ hai không phải là chuỗi"
+msgstr "index: (chỉ số) đã nhận đối số thứ hai không phải là chuỗi"
 
-#: builtin.c:483 mpfr.c:757
+#: builtin.c:488 mpfr.c:757
 msgid "int: received non-numeric argument"
 msgstr "int: (số nguyên?) đã nhận đối số không phải thuộc số"
 
-#: builtin.c:520
+#: builtin.c:525
 msgid "length: received array argument"
 msgstr "length: (chiều dài) đã nhận mảng đối số"
 
-#: builtin.c:523
+#: builtin.c:528
 msgid "`length(array)' is a gawk extension"
 msgstr "“length(array)” (độ dài mảng) là một phần mở rộng gawk"
 
-#: builtin.c:539
+#: builtin.c:544
 msgid "length: received non-string argument"
 msgstr "length: (chiều dài) đã nhận đối số không phải chuỗi"
 
-#: builtin.c:570
+#: builtin.c:575
 msgid "log: received non-numeric argument"
-msgstr "log: (bản ghi) đã nhận đối số không phải thuộc số"
+msgstr "log: (nhật ký) đã nhận đối số không phải thuộc số"
 
-#: builtin.c:573
+#: builtin.c:578
 #, c-format
 msgid "log: received negative argument %g"
-msgstr "log: (bản ghi) đã nhận đối số âm “%g”"
+msgstr "log: (nhật ký) đã nhận đối số âm “%g”"
 
-#: builtin.c:771 builtin.c:776
+#: builtin.c:776 builtin.c:781
 msgid "fatal: must use `count$' on all formats or none"
-msgstr "nghiêm trọng: phải dùng “count$” với mọi dạng thức hay không gì cả"
+msgstr "lỗi nghiêm trọng: phải dùng “count$” với mọi dạng thức hay không gì cả"
 
-#: builtin.c:846
+#: builtin.c:851
 #, c-format
 msgid "field width is ignored for `%%' specifier"
 msgstr "chiều rộng trường bị bỏ qua đối với bộ chỉ định “%%”"
 
-#: builtin.c:848
+#: builtin.c:853
 #, c-format
 msgid "precision is ignored for `%%' specifier"
 msgstr "độ chính xác bị bỏ qua đối với bộ chỉ định “%%”"
 
-#: builtin.c:850
+#: builtin.c:855
 #, c-format
 msgid "field width and precision are ignored for `%%' specifier"
 msgstr "chiều rộng trường và độ chính xác bị bỏ qua đối với bộ chỉ định “%%”"
 
-#: builtin.c:901
+#: builtin.c:906
 msgid "fatal: `$' is not permitted in awk formats"
-msgstr "nghiêm trọng: không cho phép “$” trong định dạng awk"
+msgstr "lỗi nghiêm trọng: không cho phép “$” trong định dạng awk"
 
-#: builtin.c:910
+#: builtin.c:915
 msgid "fatal: arg count with `$' must be > 0"
-msgstr "nghiêm trọng: số lượng đối số với “$” phải >0"
+msgstr "lỗi nghiêm trọng: số lượng đối số với “$” phải >0"
 
-#: builtin.c:914
+#: builtin.c:919
 #, c-format
 msgid "fatal: arg count %ld greater than total number of supplied arguments"
-msgstr "nghiêm trọng: số lượng đối số %ld lớn hơn tổng số đối số được cung cấp"
+msgstr ""
+"lỗi nghiêm trọng: số lượng đối số %ld lớn hơn tổng số đối số được cung cấp"
 
-#: builtin.c:918
+#: builtin.c:923
 msgid "fatal: `$' not permitted after period in format"
-msgstr "nghiêm trọng: không cho phép “$” nằm sau dấu chấm trong định dạng"
+msgstr "lỗi nghiêm trọng: không cho phép “$” nằm sau dấu chấm trong định dạng"
 
-#: builtin.c:934
+#: builtin.c:939
 msgid "fatal: no `$' supplied for positional field width or precision"
 msgstr ""
-"nghiêm trọng: chưa cung cấp “$” cho độ rộng trường thuộc vị trí hay cho độ "
-"chính xác"
+"lỗi nghiêm trọng: chưa cung cấp “$” cho độ rộng trường thuộc vị trí hay cho "
+"độ chính xác"
 
-#: builtin.c:1006
+#: builtin.c:1009
 msgid "`l' is meaningless in awk formats; ignored"
 msgstr "chữ “l” không có nghĩa trong định dạng awk nên bị bỏ qua"
 
-#: builtin.c:1010
+#: builtin.c:1013
 msgid "fatal: `l' is not permitted in POSIX awk formats"
-msgstr "nghiêm trọng: không cho phép chữ “l” nằm trong định dạng awk POSIX"
+msgstr "lỗi nghiêm trọng: không cho phép chữ “l” nằm trong định dạng awk POSIX"
 
-#: builtin.c:1023
+#: builtin.c:1026
 msgid "`L' is meaningless in awk formats; ignored"
 msgstr "chữ “L” không có nghĩa trong định dạng awk nên bị bỏ qua"
 
-#: builtin.c:1027
+#: builtin.c:1030
 msgid "fatal: `L' is not permitted in POSIX awk formats"
-msgstr "nghiêm trọng: không cho phép chữ “L” nằm trong định dạng awk POSIX"
+msgstr "lỗi nghiêm trọng: không cho phép chữ “L” nằm trong định dạng awk POSIX"
 
-#: builtin.c:1040
+#: builtin.c:1043
 msgid "`h' is meaningless in awk formats; ignored"
 msgstr "chữ “h” không có nghĩa trong định dạng awk nên bị bỏ qua"
 
-#: builtin.c:1044
+#: builtin.c:1047
 msgid "fatal: `h' is not permitted in POSIX awk formats"
-msgstr "nghiêm trọng: không cho phép chữ “h” nằm trong định dạng awk POSIX"
+msgstr "lỗi nghiêm trọng: không cho phép chữ “h” nằm trong định dạng awk POSIX"
 
-#: builtin.c:1439
+#: builtin.c:1463
 #, c-format
 msgid "[s]printf: value %g is out of range for `%%%c' format"
-msgstr "[s]printf: giá trị %g ở ngoại phạm vị cho dạng thức “%%%c”"
+msgstr "[s]printf: giá trị %g ở ngoại phạm vi cho dạng thức “%%%c”"
 
-#: builtin.c:1537
+#: builtin.c:1561
 #, c-format
 msgid "ignoring unknown format specifier character `%c': no argument converted"
 msgstr ""
 "đang bỏ qua ký tự ghi rõ định dạng không rõ “%c”: không có đối số được "
 "chuyển đổi"
 
-#: builtin.c:1542
+#: builtin.c:1566
 msgid "fatal: not enough arguments to satisfy format string"
-msgstr "nghiêm trọng: chưa có đủ đối số để đáp ứng chuỗi định dạng"
+msgstr "lỗi nghiêm trọng: chưa có đủ đối số để đáp ứng chuỗi định dạng"
 
-#: builtin.c:1544
+#: builtin.c:1568
 msgid "^ ran out for this one"
 msgstr "bị hết “^” cho cái này"
 
-#: builtin.c:1551
+#: builtin.c:1575
 msgid "[s]printf: format specifier does not have control letter"
 msgstr "[s]printf: chỉ định định dạng không có ký hiệu điều khiển"
 
-#: builtin.c:1554
+#: builtin.c:1578
 msgid "too many arguments supplied for format string"
 msgstr "quá nhiều đối số được cung cấp cho chuỗi định dạng"
 
-#: builtin.c:1610
+#: builtin.c:1634
 msgid "sprintf: no arguments"
 msgstr "sprintf: không có đối số"
 
-#: builtin.c:1633 builtin.c:1644
+#: builtin.c:1657 builtin.c:1668
 msgid "printf: no arguments"
 msgstr "printf: không có đối số"
 
-#: builtin.c:1687
+#: builtin.c:1711
 msgid "sqrt: received non-numeric argument"
 msgstr "sqrt: (căn bậc hai) đã nhận đối số không phải thuộc số"
 
-#: builtin.c:1691
+#: builtin.c:1715
 #, c-format
 msgid "sqrt: called with negative argument %g"
 msgstr "sqrt: (căn bậc hai) đã gọi với đối số âm “%g”"
 
-#: builtin.c:1722
+#: builtin.c:1746
 #, c-format
 msgid "substr: length %g is not >= 1"
-msgstr "substr: (chuỗi phụ) độ dài %g không phải ≥1"
+msgstr "substr: (chuỗi con) độ dài %g không phải ≥1"
 
-#: builtin.c:1724
+#: builtin.c:1748
 #, c-format
 msgid "substr: length %g is not >= 0"
-msgstr "substr: (chuỗi phụ) độ dài %g không phải ≥0"
+msgstr "substr: (chuỗi con) độ dài %g không phải ≥0"
 
-#: builtin.c:1731
+#: builtin.c:1755
 #, c-format
 msgid "substr: non-integer length %g will be truncated"
-msgstr "substr: (chuỗi phụ) sẽ cắt xén độ dài không phải số nguyên “%g”"
+msgstr "substr: (chuỗi con) sẽ cắt xén độ dài không phải số nguyên “%g”"
 
-#: builtin.c:1736
+#: builtin.c:1760
 #, c-format
 msgid "substr: length %g too big for string indexing, truncating to %g"
-msgstr "substr: độ dài %g quá lớn để chỉ mục chuỗi nên xén ngắn thành %g"
+msgstr ""
+"substr: (chuỗi con) độ dài %g là quá lớn cho chỉ số chuỗi, nên xén ngắn "
+"thành %g"
 
-#: builtin.c:1748
+#: builtin.c:1772
 #, c-format
 msgid "substr: start index %g is invalid, using 1"
-msgstr "substr: (chuỗi phụ) số chỉ mục đầu “%g” không hợp lệ nên dùng 1"
+msgstr "substr: (chuỗi con) chỉ số đầu “%g” không hợp lệ nên dùng 1"
 
-#: builtin.c:1753
+#: builtin.c:1777
 #, c-format
 msgid "substr: non-integer start index %g will be truncated"
 msgstr ""
-"substr: (chuỗi phụ) số chỉ mục đầu không phải số nguyên “%g” sẽ bị cắt ngắn"
+"substr: (chuỗi con) chỉ số đầu không phải số nguyên “%g” sẽ bị cắt ngắn"
 
-#: builtin.c:1778
+#: builtin.c:1802
 msgid "substr: source string is zero length"
 msgstr "substr: (chuỗi con) chuỗi nguồn có độ dài số không"
 
-#: builtin.c:1794
+#: builtin.c:1818
 #, c-format
 msgid "substr: start index %g is past end of string"
-msgstr "substr: (chuỗi phụ) số chỉ mục đầu %g nằm sau kết thúc của chuỗi"
+msgstr "substr: (chuỗi con) chỉ số đầu %g nằm sau kết thúc của chuỗi"
 
-#: builtin.c:1802
+#: builtin.c:1826
 #, c-format
 msgid ""
 "substr: length %g at start index %g exceeds length of first argument (%lu)"
 msgstr ""
-"substr: (chuỗi phụ) độ dài %g tại số chỉ mục đầu %g vượt quá độ dài của đối "
-"số đầu (%lu)"
+"substr: (chuỗi con) độ dài %g chỉ số đầu %g vượt quá độ dài của đối số đầu "
+"(%lu)"
 
-#: builtin.c:1876
+#: builtin.c:1900
 msgid "strftime: format value in PROCINFO[\"strftime\"] has numeric type"
 msgstr ""
 "strftime: giá trị định dạng trong PROCINFO[”strftime”] phải thuộc kiểu số"
 
-#: builtin.c:1899
+#: builtin.c:1923
 msgid "strftime: received non-numeric second argument"
 msgstr "strftime: đã nhận đối số thứ hai khác thuộc số"
 
-#: builtin.c:1903
+#: builtin.c:1927
 msgid "strftime: second argument less than 0 or too big for time_t"
 msgstr "strftime: tham số thứ hai nhỏ hơn 0 hay quá lớn dành cho time_t"
 
-#: builtin.c:1910
+#: builtin.c:1934
 msgid "strftime: received non-string first argument"
 msgstr "strftime: đã nhận đối số thứ nhất khác chuỗi"
 
-#: builtin.c:1917
+#: builtin.c:1941
 msgid "strftime: received empty format string"
 msgstr "strftime: đã nhận chuỗi định dạng rỗng"
 
-#: builtin.c:1983
+#: builtin.c:2007
 msgid "mktime: received non-string argument"
 msgstr "mktime: đã nhận đối số khác chuỗi"
 
-#: builtin.c:2000
+#: builtin.c:2024
 msgid "mktime: at least one of the values is out of the default range"
 msgstr "mktime: ít nhất một của những giá trị nằm ở ngoại phạm vi mặc định"
 
-#: builtin.c:2035
+#: builtin.c:2059
 msgid "'system' function not allowed in sandbox mode"
 msgstr "hàm “system” không cho phép ở chế độ khuôn đúc"
 
-#: builtin.c:2040
+#: builtin.c:2064
 msgid "system: received non-string argument"
 msgstr "system: (hệ thống) đã nhận đối số khác chuỗi"
 
-#: builtin.c:2160
+#: builtin.c:2184
 #, c-format
 msgid "reference to uninitialized field `$%d'"
-msgstr "gặp tham chiếu đến trường chưa được sở khởi “$%d”"
+msgstr "gặp tham chiếu đến trường chưa được khởi tạo “$%d”"
 
-#: builtin.c:2247
+#: builtin.c:2271
 msgid "tolower: received non-string argument"
 msgstr "tolower: (đến thấp hơn) đã nhận đối số khác chuỗi"
 
-#: builtin.c:2281
+#: builtin.c:2305
 msgid "toupper: received non-string argument"
 msgstr "toupper: (đến cao hơn) đã nhận đối số khác chuỗi"
 
-#: builtin.c:2317 mpfr.c:672
+#: builtin.c:2341 mpfr.c:672
 msgid "atan2: received non-numeric first argument"
 msgstr "atan2: đã nhận đối số thứ nhất khác thuộc số"
 
-#: builtin.c:2319 mpfr.c:674
+#: builtin.c:2343 mpfr.c:674
 msgid "atan2: received non-numeric second argument"
 msgstr "atan2: đã nhận đối số thứ hai khác thuộc số"
 
-#: builtin.c:2338
+#: builtin.c:2362
 msgid "sin: received non-numeric argument"
 msgstr "sin: đã nhận đối số không phải thuộc số"
 
-#: builtin.c:2354
+#: builtin.c:2378
 msgid "cos: received non-numeric argument"
 msgstr "cos: đã nhận đối số không phải thuộc số"
 
-#: builtin.c:2407 mpfr.c:1156
+#: builtin.c:2431 mpfr.c:1156
 msgid "srand: received non-numeric argument"
 msgstr "srand: đã nhận đối số không phải thuộc số"
 
-#: builtin.c:2438
+#: builtin.c:2462
 msgid "match: third argument is not an array"
 msgstr "match: (khớp) đối số thứ ba không phải là mảng"
 
-#: builtin.c:2710
+#: builtin.c:2734
 msgid "gensub: third argument of 0 treated as 1"
 msgstr "gensub: đối số thứ ba của 0 được xử lý như 1"
 
-#: builtin.c:3003
+#: builtin.c:3030
 msgid "lshift: received non-numeric first argument"
 msgstr "lshift: đã nhận đối số đầu không phải thuộc số"
 
-#: builtin.c:3005
+#: builtin.c:3032
 msgid "lshift: received non-numeric second argument"
 msgstr "lshift: (dịch bên trái) đã nhận đối số thứ hai khác thuộc số"
 
-#: builtin.c:3011
+#: builtin.c:3038
 #, c-format
 msgid "lshift(%f, %f): negative values will give strange results"
 msgstr "lshift(%f, %f): giá trị âm sẽ gây ra kết quả không như mong muốn"
 
-#: builtin.c:3013
+#: builtin.c:3040
 #, c-format
 msgid "lshift(%f, %f): fractional values will be truncated"
 msgstr "lshift(%f, %f): giá trị thuộc phân số sẽ bị cắt ngắn"
 
-#: builtin.c:3015
+#: builtin.c:3042
 #, c-format
 msgid "lshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "lshift(%f, %f): giá trị dịch quá lớn sẽ gây ra kết quả không như mong muốn"
 
-#: builtin.c:3040
+#: builtin.c:3067
 msgid "rshift: received non-numeric first argument"
 msgstr "rshift: đã nhận đối số thứ nhất khác thuộc số"
 
-#: builtin.c:3042
+#: builtin.c:3069
 msgid "rshift: received non-numeric second argument"
-msgstr "rshift: (dịch bên phải) đã nhận đối số thứ hai khác thuộc số"
+msgstr "rshift: (dịch phải) đã nhận đối số thứ hai khác thuộc số"
 
-#: builtin.c:3048
+#: builtin.c:3075
 #, c-format
 msgid "rshift(%f, %f): negative values will give strange results"
 msgstr "rshift(%f, %f): giá trị âm sẽ gây ra kết quả không như mong muốn"
 
-#: builtin.c:3050
+#: builtin.c:3077
 #, c-format
 msgid "rshift(%f, %f): fractional values will be truncated"
 msgstr "rshift(%f, %f): giá trị thuộc kiểu phân số sẽ bị xén ngắn"
 
-#: builtin.c:3052
+#: builtin.c:3079
 #, c-format
 msgid "rshift(%f, %f): too large shift value will give strange results"
 msgstr ""
 "rshift(%f, %f): giá trị dịch quá lớn sẽ gây ra kết quả không như mong muốn"
 
-#: builtin.c:3077 mpfr.c:968
+#: builtin.c:3104 mpfr.c:968
 msgid "and: called with less than two arguments"
 msgstr "and: được gọi với ít hơn hai đối số"
 
-#: builtin.c:3082
+#: builtin.c:3109
 #, c-format
 msgid "and: argument %d is non-numeric"
 msgstr "and: đối số  %d không phải thuộc số"
 
-#: builtin.c:3086
+#: builtin.c:3113
 #, c-format
 msgid "and: argument %d negative value %g will give strange results"
-msgstr "and: đối số %d giá trị âm %g sẽ đưa lại kết quả không như mong muốn"
+msgstr ""
+"and: (và) đối số %d giá trị âm %g sẽ đưa lại kết quả không như mong muốn"
 
-#: builtin.c:3109 mpfr.c:1000
+#: builtin.c:3136 mpfr.c:1000
 msgid "or: called with less than two arguments"
-msgstr "or: được gọi với ít hơn hai đối số"
+msgstr "or: (hoặc) được gọi với ít hơn hai đối số"
 
-#: builtin.c:3114
+#: builtin.c:3141
 #, c-format
 msgid "or: argument %d is non-numeric"
-msgstr "or: đối số %d không thuộc kiểu số"
+msgstr "or: (hoặc) đối số %d không thuộc kiểu số"
 
-#: builtin.c:3118
+#: builtin.c:3145
 #, c-format
 msgid "or: argument %d negative value %g will give strange results"
-msgstr "or: đối số %d giá trị âm %g sẽ đưa lại kết quả không như mong muốn"
+msgstr ""
+"or: (hoặc) đối số %d giá trị âm %g sẽ đưa lại kết quả không như mong muốn"
 
-#: builtin.c:3140 mpfr.c:1031
+#: builtin.c:3167 mpfr.c:1031
 msgid "xor: called with less than two arguments"
 msgstr "xor: được gọi với ít hơn hai đối số"
 
-#: builtin.c:3146
+#: builtin.c:3173
 #, c-format
 msgid "xor: argument %d is non-numeric"
 msgstr "xor: đối số %d không thuộc kiểu số"
 
-#: builtin.c:3150
+#: builtin.c:3177
 #, c-format
 msgid "xor: argument %d negative value %g will give strange results"
 msgstr "xor: đối số %d giá trị âm %g sẽ đưa lại kết quả không như mong muốn"
 
-#: builtin.c:3175 mpfr.c:787
+#: builtin.c:3202 mpfr.c:787
 msgid "compl: received non-numeric argument"
-msgstr "compl: (biên dịch) đã nhận đối số khác thuộc số"
+msgstr "compl: (biên dịch) đã nhận được đối số không-phải-số"
 
-#: builtin.c:3181
+#: builtin.c:3208
 #, c-format
 msgid "compl(%f): negative value will give strange results"
 msgstr "compl(%f): giá trị âm sẽ gây ra kết quả không như mong đợi"
 
-#: builtin.c:3183
+#: builtin.c:3210
 #, c-format
 msgid "compl(%f): fractional value will be truncated"
 msgstr "compl(%f): giá trị thuộc phân số sẽ bị cắt ngắn"
 
-#: builtin.c:3352
+#: builtin.c:3379
 #, c-format
 msgid "dcgettext: `%s' is not a valid locale category"
 msgstr "dcgettext: “%s” không phải là một phân loại miền địa phương hợp lệ"
@@ -973,7 +989,7 @@ msgstr "nguồn “%s”: đã sẵn có trong nguồn rồi."
 #: command.y:326
 #, c-format
 msgid "save \"%s\": command not permitted."
-msgstr "ghi “%s”: không đủ thẩm quyền."
+msgstr "ghi “%s”: lệnh không đủ thẩm quyền."
 
 #: command.y:339
 msgid "Can't use command `commands' for breakpoint/watchpoint commands"
@@ -1012,7 +1028,7 @@ msgstr "trace: tùy chọn không hợp lệ - “%s”"
 
 #: command.y:387
 msgid "condition: invalid breakpoint/watchpoint number"
-msgstr "điều kiện: số hiệu điểm ngắt hay điểm theo dõi không hợp lệ"
+msgstr "condition: điều kiện: số hiệu điểm ngắt hay điểm theo dõi không hợp lệ"
 
 #: command.y:449
 msgid "argument not a string"
@@ -1061,16 +1077,17 @@ msgstr ""
 #: command.y:819
 msgid ""
 "break [[filename:]N|function] - set breakpoint at the specified location."
-msgstr "break [[TẬP-TIN:]N|hàm] - đặt điểm ngắt tại vị trí đã cho."
+msgstr "break [[tên_tập_tin:]N|hàm] - đặt điểm ngắt tại vị trí đã cho."
 
 #: command.y:821
 msgid "clear [[filename:]N|function] - delete breakpoints previously set."
-msgstr "clear [[filename:]N|function] - xóa các điểm ngắt được đặt trước đây."
+msgstr ""
+"clear [[tên_tập_tin:]N|function] - xóa các điểm ngắt được đặt trước đây."
 
 #: command.y:823
 msgid ""
-"commands [num] - starts a list of commands to be executed at a breakpoint"
-"(watchpoint) hit."
+"commands [num] - starts a list of commands to be executed at a "
+"breakpoint(watchpoint) hit."
 msgstr ""
 "commands [số] - chạy một danh sách các câu lệnh được thực thi tại điểm ngắt "
 "(hay điểm theo dõi) tìm được."
@@ -1086,11 +1103,11 @@ msgstr "continue [SỐ_LƯỢNG] - tiếp tục chương trình đang được g
 
 #: command.y:829
 msgid "delete [breakpoints] [range] - delete specified breakpoints."
-msgstr "delete [điểm ngắt] [vùng] - xóa các điểm ngắt đã chỉ ra."
+msgstr "delete [điểm_ngắt] [vùng] - xóa các điểm ngắt đã chỉ ra."
 
 #: command.y:831
 msgid "disable [breakpoints] [range] - disable specified breakpoints."
-msgstr "disable [điểm ngắt] [vùng] - tắt các điểm ngắt đã chỉ định."
+msgstr "disable [điểm_ngắt] [vùng] - tắt các điểm ngắt đã chỉ định."
 
 #: command.y:833
 msgid "display [var] - print value of variable each time the program stops."
@@ -1103,11 +1120,11 @@ msgstr "down [N] - chuyển xuống N khung stack."
 #: command.y:837
 msgid "dump [filename] - dump instructions to file or stdout."
 msgstr ""
-"dump [tên-tập-tin] - dump các chỉ lệnh ra tập tin hay đầu ra tiêu chuẩn."
+"dump [tên_tập_tin] - dump các chỉ lệnh ra tập tin hay đầu ra tiêu chuẩn."
 
 #: command.y:839
 msgid "enable [once|del] [breakpoints] [range] - enable specified breakpoints."
-msgstr "enable [once|del] [breakpoints] [range] - bật các điểm ngắt đã chỉ ra."
+msgstr "enable [once|del] [điểm_ngắt] [range] - bật các điểm ngắt đã chỉ ra."
 
 #: command.y:841
 msgid "end - end a list of commands or awk statements."
@@ -1131,7 +1148,7 @@ msgstr "help [lệnh] - hiển thị danh sách các lệnh hay giải thích c�
 
 #: command.y:851
 msgid "ignore N COUNT - set ignore-count of breakpoint number N to COUNT."
-msgstr "ignore N SÔ-LƯỢNG - đặt số lượng điểm ngắt bị bỏ qua."
+msgstr "ignore N SỐ-LƯỢNG - đặt số lượng điểm ngắt bị bỏ qua."
 
 #: command.y:853
 msgid ""
@@ -1142,7 +1159,7 @@ msgstr ""
 
 #: command.y:855
 msgid "list [-|+|[filename:]lineno|function|range] - list specified line(s)."
-msgstr "list [-|+|[TẬP-TIN:]số_dòng|hàm|vùng] - liệt kê các dòng đã chỉ định."
+msgstr "list [-|+|[tập_tin:]số_dòng|hàm|vùng] - liệt kê các dòng đã chỉ định."
 
 #: command.y:857
 msgid "next [COUNT] - step program, proceeding through subroutine calls."
@@ -1154,7 +1171,7 @@ msgstr ""
 msgid ""
 "nexti [COUNT] - step one instruction, but proceed through subroutine calls."
 msgstr ""
-"nexti [SỐ_LƯỢNG]   - nhảy từng chỉ lệnh, nhưng được xử lý thông qua gọi thủ "
+"nexti [SỐ_LƯỢNG]  - nhảy từng chỉ lệnh, nhưng được xử lý thông qua gọi thủ "
 "tục con."
 
 #: command.y:861
@@ -1189,7 +1206,7 @@ msgstr "save tên_tập_tin - ghi các câu lệnh từ phiên làm việc vào
 
 #: command.y:877
 msgid "set var = value - assign value to a scalar variable."
-msgstr "set biến = giá_trị - gán giá trị cho một biến scalar."
+msgstr "set biến = giá_trị - gán giá trị cho một biến vô hướng."
 
 #: command.y:879
 msgid ""
@@ -1214,7 +1231,7 @@ msgstr "stepi [SỐ_LƯỢNG] - chạy từng lệnh một."
 
 #: command.y:887
 msgid "tbreak [[filename:]N|function] - set a temporary breakpoint."
-msgstr "tbreak [[TẬP-TIN:]N|hàm] - đặt điểm ngắt tạm thời."
+msgstr "tbreak [[tên_tập_tin:]N|hàm] - đặt điểm ngắt tạm thời."
 
 #: command.y:889
 msgid "trace on|off - print instruction before executing."
@@ -1229,8 +1246,8 @@ msgid ""
 "until [[filename:]N|function] - execute until program reaches a different "
 "line or line N within current frame."
 msgstr ""
-"until [[TẬP-TIN:]N|hàm] - thực hiện cho đến khi chương trình đạt đến dòng "
-"khác hay dòng N trong khung hiện tại."
+"until [[tên_tập_tin:]N|hàm] - thực hiện cho đến khi chương trình đạt đến "
+"dòng khác hay dòng N trong khung hiện tại."
 
 #: command.y:895
 msgid "unwatch [N] - remove variable(s) from watch list."
@@ -1244,7 +1261,7 @@ msgstr "up [N] - chuyển xuống N khung stack."
 msgid "watch var - set a watchpoint for a variable."
 msgstr "watch var - đặt điểm theo dõi cho một biến."
 
-#: command.y:1011 debug.c:395 msg.c:128
+#: command.y:1011 debug.c:401 msg.c:135
 #, c-format
 msgid "error: "
 msgstr "lỗi: "
@@ -1282,148 +1299,148 @@ msgstr "ký tự không hợp lệ"
 msgid "undefined command: %s\n"
 msgstr "lệnh chưa định nghĩa: %s\n"
 
-#: debug.c:246
+#: debug.c:252
 msgid "set or show the number of lines to keep in history file."
 msgstr "đặt hay hiển thị số dòng được lưu giữ trong tập tin lịch sử."
 
-#: debug.c:248
+#: debug.c:254
 msgid "set or show the list command window size."
 msgstr "đặt hay hiển thị kích thước cửa sổ danh sách lệnh."
 
-#: debug.c:250
+#: debug.c:256
 msgid "set or show gawk output file."
 msgstr "đặt hay hiển thị tập tin kết xuất gawk."
 
-#: debug.c:252
+#: debug.c:258
 msgid "set or show debugger prompt."
 msgstr "đặt hay hiển thị dấu nhắc gỡ lỗi."
 
-#: debug.c:254
+#: debug.c:260
 msgid "(un)set or show saving of command history (value=on|off)."
 msgstr "(bỏ) đặt hay ghi lại lịch sử lệnh (giá trị=on|off)."
 
-#: debug.c:256
+#: debug.c:262
 msgid "(un)set or show saving of options (value=on|off)."
 msgstr "đặt/bỏ đặt hay hiển thị các tùy chọn được ghi lại (giá_trị=on|off)."
 
-#: debug.c:258
+#: debug.c:264
 msgid "(un)set or show instruction tracing (value=on|off)."
 msgstr "(bỏ) đặt hay hiển thị việc theo vết chỉ lệnh (giá trị=on|off)."
 
-#: debug.c:339
+#: debug.c:345
 msgid "program not running."
 msgstr "chương trình không chạy."
 
-#: debug.c:442 debug.c:597
+#: debug.c:448 debug.c:606
 #, c-format
 msgid "can't read source file `%s' (%s)"
 msgstr "không thể đọc tập tin nguồn “%s” (%s)"
 
-#: debug.c:447
+#: debug.c:453
 #, c-format
 msgid "source file `%s' is empty.\n"
 msgstr "tập tin nguồn “%s” bị trống rỗng.\n"
 
-#: debug.c:474
+#: debug.c:480
 msgid "no current source file."
 msgstr "không có tập tin nguồn hiện tại."
 
-#: debug.c:499
+#: debug.c:505
 #, c-format
 msgid "cannot find source file named `%s' (%s)"
 msgstr "không thể tìm thấy tập tin nguồn có tên “%s” (%s)"
 
-#: debug.c:523
+#: debug.c:529
 #, c-format
 msgid "WARNING: source file `%s' modified since program compilation.\n"
 msgstr "CẢNH BÁO: tập tin nguồn “%s” bị sửa đổi kể từ lúc nó được dịch.\n"
 
-#: debug.c:542
+#: debug.c:551
 #, c-format
 msgid "line number %d out of range; `%s' has %d lines"
 msgstr "số dòng %d nằm ngoài phạm vi; “%s” có %d dòng"
 
-#: debug.c:602
+#: debug.c:611
 #, c-format
 msgid "unexpected eof while reading file `%s', line %d"
 msgstr "gặp kết thúc tập tin bất ngờ khi đang đọc tập tin “%s”, dòng %d"
 
-#: debug.c:611
+#: debug.c:620
 #, c-format
 msgid "source file `%s' modified since start of program execution"
 msgstr "tập tin nguồn “%s” đã bị sửa đổi kể từ lúc chưong trình được khởi chạy"
 
-#: debug.c:723
+#: debug.c:732
 #, c-format
 msgid "Current source file: %s\n"
 msgstr "Tập tin nguồn hiện tại: %s\n"
 
-#: debug.c:724
+#: debug.c:733
 #, c-format
 msgid "Number of lines: %d\n"
 msgstr "Số dòng: %d\n"
 
-#: debug.c:731
+#: debug.c:740
 #, c-format
 msgid "Source file (lines): %s (%d)\n"
 msgstr "Tập tin nguồn (dòng): %s (%d)\n"
 
-#: debug.c:745
+#: debug.c:754
 msgid ""
 "Number  Disp  Enabled  Location\n"
 "\n"
 msgstr ""
-"Số    Hiển thị   Bật   Vị trí\n"
+"Số      Hthị  Bật      Vị trí\n"
 "\n"
 
-#: debug.c:756
+#: debug.c:765
 #, c-format
 msgid "\tno of hits = %ld\n"
 msgstr "\tkhông gợi ý = %ld\n"
 
-#: debug.c:758
+#: debug.c:767
 #, c-format
 msgid "\tignore next %ld hit(s)\n"
 msgstr "\tbỏ qua %ld gợi ý tiếp\n"
 
-#: debug.c:760 debug.c:900
+#: debug.c:769 debug.c:909
 #, c-format
 msgid "\tstop condition: %s\n"
 msgstr "\tdừng điều kiện: %s\n"
 
-#: debug.c:762 debug.c:902
+#: debug.c:771 debug.c:911
 msgid "\tcommands:\n"
 msgstr "\tlệnh:\n"
 
-#: debug.c:784
+#: debug.c:793
 #, c-format
 msgid "Current frame: "
 msgstr "Khung hiện tại:"
 
-#: debug.c:787
+#: debug.c:796
 #, c-format
 msgid "Called by frame: "
 msgstr "Được gọi bởi khung:"
 
-#: debug.c:791
+#: debug.c:800
 #, c-format
 msgid "Caller of frame: "
 msgstr "Bộ gọi của khung:"
 
-#: debug.c:809
+#: debug.c:818
 #, c-format
 msgid "None in main().\n"
 msgstr "Không có gì trong main().\n"
 
-#: debug.c:839
+#: debug.c:848
 msgid "No arguments.\n"
 msgstr "Không có đối số nào.\n"
 
-#: debug.c:840
+#: debug.c:849
 msgid "No locals.\n"
 msgstr "Không có nội bộ.\n"
 
-#: debug.c:848
+#: debug.c:857
 msgid ""
 "All defined variables:\n"
 "\n"
@@ -1431,7 +1448,7 @@ msgstr ""
 "Tất cả các biến đã định nghĩa:\n"
 "\n"
 
-#: debug.c:858
+#: debug.c:867
 msgid ""
 "All defined functions:\n"
 "\n"
@@ -1439,7 +1456,7 @@ msgstr ""
 "Tất cả các hàm đã định nghĩa:\n"
 "\n"
 
-#: debug.c:877
+#: debug.c:886
 msgid ""
 "Auto-display variables:\n"
 "\n"
@@ -1447,7 +1464,7 @@ msgstr ""
 "Các biến hiển thị tự động:\n"
 "\n"
 
-#: debug.c:880
+#: debug.c:889
 msgid ""
 "Watch variables:\n"
 "\n"
@@ -1455,396 +1472,396 @@ msgstr ""
 "Các biến theo dõi:\n"
 "\n"
 
-#: debug.c:1020
+#: debug.c:1029
 #, c-format
 msgid "no symbol `%s' in current context\n"
 msgstr "không có ký hiệu “%s” trong ngữ cảnh hiện tại\n"
 
-#: debug.c:1032 debug.c:1418
+#: debug.c:1041 debug.c:1427
 #, c-format
 msgid "`%s' is not an array\n"
 msgstr "“%s” không phải là một mảng\n"
 
-#: debug.c:1046
+#: debug.c:1055
 #, c-format
 msgid "$%ld = uninitialized field\n"
 msgstr "$%ld = trường chưa được khởi tạo\n"
 
-#: debug.c:1067
+#: debug.c:1076
 #, c-format
 msgid "array `%s' is empty\n"
 msgstr "mảng “%s” trống rỗng\n"
 
-#: debug.c:1110 debug.c:1162
+#: debug.c:1119 debug.c:1171
 #, c-format
 msgid "[\"%s\"] not in array `%s'\n"
 msgstr "[”%s”] không nằm trong mảng “%s”\n"
 
-#: debug.c:1166
+#: debug.c:1175
 #, c-format
 msgid "`%s[\"%s\"]' is not an array\n"
 msgstr "“%s[”%s”]” không phải là một mảng\n"
 
-#: debug.c:1227 debug.c:4949
+#: debug.c:1236 debug.c:4964
 #, c-format
 msgid "`%s' is not a scalar variable"
 msgstr "“%s” không phải là biến scalar"
 
-#: debug.c:1249 debug.c:4979
+#: debug.c:1258 debug.c:4994
 #, c-format
 msgid "attempt to use array `%s[\"%s\"]' in a scalar context"
 msgstr "cố dùng mảng “%s[”%s”]” trong một ngữ cảnh vô hướng"
 
-#: debug.c:1271 debug.c:4990
+#: debug.c:1280 debug.c:5005
 #, c-format
 msgid "attempt to use scalar `%s[\"%s\"]' as array"
 msgstr "cố dùng kiểu vô hướng “%s[”%s”]” như là mảng"
 
-#: debug.c:1414
+#: debug.c:1423
 #, c-format
 msgid "`%s' is a function"
 msgstr "“%s” là một hàm"
 
-#: debug.c:1456
+#: debug.c:1465
 #, c-format
 msgid "watchpoint %d is unconditional\n"
 msgstr "điểm kiểm tra %d là vô điều kiện\n"
 
-#: debug.c:1490
+#: debug.c:1499
 #, c-format
 msgid "No display item numbered %ld"
 msgstr "Không có mục tin hiển thị nào đánh số %ld"
 
-#: debug.c:1493
+#: debug.c:1502
 #, c-format
 msgid "No watch item numbered %ld"
 msgstr "Không có mục tin theo dõi nào đánh số %ld"
 
-#: debug.c:1519
+#: debug.c:1528
 #, c-format
 msgid "%d: [\"%s\"] not in array `%s'\n"
 msgstr "%d: [”%s”] không trong mảng “%s”\n"
 
-#: debug.c:1758
+#: debug.c:1767
 msgid "attempt to use scalar value as array"
 msgstr "cố dùng biến vô hướng như là một mảng"
 
-#: debug.c:1847
+#: debug.c:1856
 #, c-format
 msgid "Watchpoint %d deleted because parameter is out of scope.\n"
 msgstr "Điểm theo dõi %d bị xóa bởi vì đối số nằm ngoài phạm vi\n"
 
-#: debug.c:1858
+#: debug.c:1867
 #, c-format
 msgid "Display %d deleted because parameter is out of scope.\n"
 msgstr "Trình bày %d bị xóa bởi vì đối số nằm ngoài phạm vi\n"
 
-#: debug.c:1891
+#: debug.c:1900
 #, c-format
 msgid " in file `%s', line %d\n"
 msgstr " tại tập tin “%s”, dòng %d\n"
 
-#: debug.c:1912
+#: debug.c:1921
 #, c-format
 msgid " at `%s':%d"
 msgstr " tại “%s”:%d"
 
-#: debug.c:1928 debug.c:1991
+#: debug.c:1937 debug.c:2000
 #, c-format
 msgid "#%ld\tin "
 msgstr "#%ld\ttrong "
 
-#: debug.c:1965
+#: debug.c:1974
 #, c-format
 msgid "More stack frames follow ...\n"
-msgstr "Nhiều khung stack theo sau...\n"
+msgstr "Nhiều khung ngăn xếp theo sau...\n"
 
-#: debug.c:2008
+#: debug.c:2017
 msgid "invalid frame number"
 msgstr "số khung không hợp lệ"
 
-#: debug.c:2180
+#: debug.c:2200
 #, c-format
 msgid "Note: breakpoint %d (enabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Chú ý: điểm ngắt %d (được bật, bỏ qua %ld gợi ý tiếp), đồng thời được đặt "
 "tại %s:%d"
 
-#: debug.c:2187
+#: debug.c:2207
 #, c-format
 msgid "Note: breakpoint %d (enabled), also set at %s:%d"
 msgstr "Chú ý: điểm ngắt %d (được bật), đồng thời được đặt tại %s:%d"
 
-#: debug.c:2194
+#: debug.c:2214
 #, c-format
 msgid "Note: breakpoint %d (disabled, ignore next %ld hits), also set at %s:%d"
 msgstr ""
 "Chú ý: điểm ngắt %d (bị tắt, bỏ qua %ld gợi ý tiếp), đồng thời được đặt tại "
 "%s:%d"
 
-#: debug.c:2201
+#: debug.c:2221
 #, c-format
 msgid "Note: breakpoint %d (disabled), also set at %s:%d"
 msgstr "Chú ý: điểm ngắt %d (bị tắt), đồng thời được đặt tại %s:%d"
 
-#: debug.c:2218
+#: debug.c:2238
 #, c-format
 msgid "Breakpoint %d set at file `%s', line %d\n"
 msgstr "Điểm ngắt %d đặt tại tập tin “%s”, dòng %d\n"
 
-#: debug.c:2320
+#: debug.c:2340
 #, c-format
 msgid "Can't set breakpoint in file `%s'\n"
 msgstr "Không thể đặt điểm ngắt trong tập tin “%s”\n"
 
-#: debug.c:2349 debug.c:2472 debug.c:3330
+#: debug.c:2369 debug.c:2492 debug.c:3350
 #, c-format
 msgid "line number %d in file `%s' out of range"
 msgstr "số dòng %d trong tập tin “%s” nằm ngoài phạm vi"
 
-#: debug.c:2353
+#: debug.c:2373
 #, c-format
 msgid "Can't find rule!!!\n"
 msgstr "Không tìm thấy quy tắc!!!\n"
 
-#: debug.c:2355
+#: debug.c:2375
 #, c-format
 msgid "Can't set breakpoint at `%s':%d\n"
 msgstr "Không thể đặt điểm ngắt tại “%s”:%d\n"
 
-#: debug.c:2367
+#: debug.c:2387
 #, c-format
 msgid "Can't set breakpoint in function `%s'\n"
 msgstr "Không thể đặt điểm ngắt trong hàm “%s”\n"
 
-#: debug.c:2383
+#: debug.c:2403
 #, c-format
 msgid "breakpoint %d set at file `%s', line %d is unconditional\n"
 msgstr "điểm ngắt %d đặt tại tập tin “%s”, dòng %d là vô điều kiện\n"
 
-#: debug.c:2488 debug.c:2510
+#: debug.c:2508 debug.c:2530
 #, c-format
 msgid "Deleted breakpoint %d"
 msgstr "Xóa điểm dừng %d"
 
-#: debug.c:2494
+#: debug.c:2514
 #, c-format
 msgid "No breakpoint(s) at entry to function `%s'\n"
 msgstr "Không có điểm ngắt tại điểm vào của hàm “%s”\n"
 
-#: debug.c:2521
+#: debug.c:2541
 #, c-format
 msgid "No breakpoint at file `%s', line #%d\n"
 msgstr "Không có điểm ngắt tại tập tin “%s”, dòng #%d\n"
 
-#: debug.c:2576 debug.c:2617 debug.c:2637 debug.c:2680
+#: debug.c:2596 debug.c:2637 debug.c:2657 debug.c:2700
 msgid "invalid breakpoint number"
 msgstr "số điểm ngắt không hợp lệ"
 
-#: debug.c:2592
+#: debug.c:2612
 msgid "Delete all breakpoints? (y or n) "
 msgstr "Xóa tất cả các điểm ngắt? (c hay k) "
 
-#: debug.c:2593 debug.c:2903 debug.c:2956
+#: debug.c:2613 debug.c:2923 debug.c:2976
 msgid "y"
 msgstr "c"
 
-#: debug.c:2642
+#: debug.c:2662
 #, c-format
 msgid "Will ignore next %ld crossing(s) of breakpoint %d.\n"
 msgstr "Sẽ bỏ qua %ld điểm giao chéo của điểm ngắt %d.\n"
 
-#: debug.c:2646
+#: debug.c:2666
 #, c-format
 msgid "Will stop next time breakpoint %d is reached.\n"
 msgstr "Sẽ dừng lần gặp điểm ngắt %d tiếp theo.\n"
 
-#: debug.c:2763
+#: debug.c:2783
 #, c-format
 msgid "Can only debug programs provided with the `-f' option.\n"
 msgstr ""
 "Chỉ có thể gỡ lỗi các chương trình được cung cấp cùng với tùy chọn “-f”.\n"
 
-#: debug.c:2888
+#: debug.c:2908
 #, c-format
 msgid "Failed to restart debugger"
 msgstr "Gặp lỗi khi khởi động lại bộ gỡ lỗi"
 
-#: debug.c:2902
+#: debug.c:2922
 msgid "Program already running. Restart from beginning (y/n)? "
 msgstr "Chương trình đang chạy. Khởi động từ đầu (c/không)?"
 
-#: debug.c:2906
+#: debug.c:2926
 #, c-format
 msgid "Program not restarted\n"
 msgstr "Chương trình không khởi động lại\n"
 
-#: debug.c:2916
+#: debug.c:2936
 #, c-format
 msgid "error: cannot restart, operation not allowed\n"
 msgstr "lỗi: không thể khởi động lại, thao tác không được cho phép\n"
 
-#: debug.c:2922
+#: debug.c:2942
 #, c-format
 msgid "error (%s): cannot restart, ignoring rest of the commands\n"
 msgstr "lỗi (%s): không thể khởi động lại, bỏ qua các lệnh còn lại\n"
 
-#: debug.c:2930
+#: debug.c:2950
 #, c-format
 msgid "Starting program: \n"
 msgstr "Đang khởi động chương trình:\n"
 
-#: debug.c:2939
+#: debug.c:2959
 #, c-format
 msgid "Program exited %s with exit value: %d\n"
 msgstr "Chương trình %s được thoát ra với mã thoát là: %d\n"
 
-#: debug.c:2955
+#: debug.c:2975
 msgid "The program is running. Exit anyway (y/n)? "
 msgstr "Chương trình này đang chạy. Vẫn thoát (c/không)?"
 
-#: debug.c:2990
+#: debug.c:3010
 #, c-format
 msgid "Not stopped at any breakpoint; argument ignored.\n"
 msgstr "Không dừng tại bất ký điểm ngắt nào; đối số bị bỏ qua.\n"
 
-#: debug.c:2995
+#: debug.c:3015
 #, c-format
 msgid "invalid breakpoint number %d."
 msgstr "số điểm ngắt không hợp lệ %d."
 
-#: debug.c:3000
+#: debug.c:3020
 #, c-format
 msgid "Will ignore next %ld crossings of breakpoint %d.\n"
 msgstr "Sẽ bỏ qua %ld điểm ngắt xuyên chéo %d kế tiếp.\n"
 
-#: debug.c:3187
+#: debug.c:3207
 #, c-format
 msgid "'finish' not meaningful in the outermost frame main()\n"
 msgstr "“finish” không có nghĩa trong khung ngoài cùng nhất main()\n"
 
-#: debug.c:3192
+#: debug.c:3212
 #, c-format
 msgid "Run till return from "
 msgstr "Chạy cho đến khi có trả về từ đó"
 
-#: debug.c:3235
+#: debug.c:3255
 #, c-format
 msgid "'return' not meaningful in the outermost frame main()\n"
 msgstr "“return” không có nghĩa trong khung ngoài cùng nhất main()\n"
 
-#: debug.c:3349
+#: debug.c:3369
 #, c-format
 msgid "Can't find specified location in function `%s'\n"
 msgstr "Không tìm thấy vị trí đã cho trong hàm “%s”\n"
 
-#: debug.c:3357
+#: debug.c:3377
 #, c-format
 msgid "invalid source line %d in file `%s'"
 msgstr "dòng nguồn không hợp lệ %d trong tập tin “%s”"
 
-#: debug.c:3372
+#: debug.c:3392
 #, c-format
 msgid "Can't find specified location %d in file `%s'\n"
 msgstr "Không thể tìm thấy vị trí %d được chỉ ra trong tập tin “%s”\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "element not in array\n"
 msgstr "phần tử không trong mảng\n"
 
-#: debug.c:3404
+#: debug.c:3424
 #, c-format
 msgid "untyped variable\n"
 msgstr "biến chưa định kiểu\n"
 
-#: debug.c:3446
+#: debug.c:3466
 #, c-format
 msgid "Stopping in %s ...\n"
 msgstr "Dừng trong %s ...\n"
 
-#: debug.c:3523
+#: debug.c:3543
 #, c-format
 msgid "'finish' not meaningful with non-local jump '%s'\n"
 msgstr "“finish” không có nghĩa với lệnh nhảy non-local “%s”\n"
 
-#: debug.c:3530
+#: debug.c:3550
 #, c-format
 msgid "'until' not meaningful with non-local jump '%s'\n"
 msgstr "“until” không có nghĩa với cú nhảy non-local “%s”\n"
 
-#: debug.c:4165
+#: debug.c:4185
 msgid "\t------[Enter] to continue or q [Enter] to quit------"
-msgstr "\t------Nhấn [Enter] để tiếp tục hay  “q” [Enter] để thoát------"
+msgstr "\t-Nhấn [Enter] để tiếp tục hay  “q” [Enter] để thoát------"
 
-#: debug.c:4166
+#: debug.c:4186
 msgid "q"
 msgstr "t"
 
-#: debug.c:4986
+#: debug.c:5001
 #, c-format
 msgid "[\"%s\"] not in array `%s'"
-msgstr "[”%s”] không trong mảng “%s”"
+msgstr "[\"%s\"] không trong mảng “%s”"
 
-#: debug.c:5192
+#: debug.c:5207
 #, c-format
 msgid "sending output to stdout\n"
 msgstr "gửi kết xuất ra stdout\n"
 
-#: debug.c:5232
+#: debug.c:5247
 msgid "invalid number"
 msgstr "số không hợp lệ"
 
-#: debug.c:5366
+#: debug.c:5381
 #, c-format
 msgid "`%s' not allowed in current context; statement ignored"
 msgstr "“%s” không được phép trong ngữ cảnh hiện hành; câu lệnh bị bỏ qua"
 
-#: debug.c:5374
+#: debug.c:5389
 msgid "`return' not allowed in current context; statement ignored"
 msgstr "“return” không được phép trong ngữ cảnh hiện hành; câu lệnh bị bỏ qua"
 
-#: debug.c:5575
+#: debug.c:5590
 #, c-format
 msgid "No symbol `%s' in current context"
 msgstr "Không có ký hiệu “%s” trong ngữ cảnh hiện thời"
 
-#: dfa.c:998 dfa.c:1001 dfa.c:1021 dfa.c:1031 dfa.c:1043 dfa.c:1094 dfa.c:1103
-#: dfa.c:1106 dfa.c:1111 dfa.c:1124 dfa.c:1192
+#: dfa.c:1118 dfa.c:1121 dfa.c:1142 dfa.c:1150 dfa.c:1162 dfa.c:1197
+#: dfa.c:1206 dfa.c:1209 dfa.c:1214 dfa.c:1228 dfa.c:1275
 msgid "unbalanced ["
 msgstr "thiếu dấu ngoặc vuông mở ["
 
-#: dfa.c:1052
+#: dfa.c:1174
 msgid "invalid character class"
 msgstr "sai lớp ký tự"
 
-#: dfa.c:1229
+#: dfa.c:1316
 msgid "character class syntax is [[:space:]], not [:space:]"
 msgstr "cú pháp lớp ký tự là [[:dấu_cách:]], không phải [:dấu_cách:]"
 
-#: dfa.c:1281
+#: dfa.c:1366
 msgid "unfinished \\ escape"
 msgstr "chưa kết thúc dãy thoát \\"
 
-#: dfa.c:1428 regcomp.c:161
+#: dfa.c:1513 regcomp.c:161
 msgid "Invalid content of \\{\\}"
-msgstr "Nội dụng “\\{\\}” không hợp lệ"
+msgstr "Nội dung của “\\{\\}” không hợp lệ"
 
-#: dfa.c:1431 regcomp.c:176
+#: dfa.c:1516 regcomp.c:176
 msgid "Regular expression too big"
 msgstr "Biểu thức chính quy quá lớn"
 
-#: dfa.c:1816
+#: dfa.c:1936
 msgid "unbalanced ("
-msgstr "mất cân xứng ("
+msgstr "thiếu dấu ("
 
-#: dfa.c:1943
+#: dfa.c:2062
 msgid "no syntax specified"
 msgstr "chưa chỉ rõ cú pháp"
 
-#: dfa.c:1951
+#: dfa.c:2070
 msgid "unbalanced )"
-msgstr "mất cân xứng )"
+msgstr "thiếu dấu )"
 
 #: eval.c:394
 #, c-format
@@ -1861,11 +1878,11 @@ msgstr "gặp opcode (mã thao tác) không rõ %d"
 msgid "opcode %s not an operator or keyword"
 msgstr "mã lệnh %s không phải là một toán tử hoặc từ khoá"
 
-#: eval.c:471
+#: eval.c:472
 msgid "buffer overflow in genflags2str"
 msgstr "tràn bộ đệm trong “genflags2str” (tạo ra cờ đến chuỗi)"
 
-#: eval.c:674
+#: eval.c:675
 #, c-format
 msgid ""
 "\n"
@@ -1873,77 +1890,77 @@ msgid ""
 "\n"
 msgstr ""
 "\n"
-"\t# Đống gọi hàm:\n"
+"\t# Ngăn xếp gọi hàm:\n"
 "\n"
 
-#: eval.c:703
+#: eval.c:704
 msgid "`IGNORECASE' is a gawk extension"
-msgstr "“IGNORECASE” (bỏ qua chữ hoa/thường) là phần mở rộng gawk"
+msgstr "“IGNORECASE” (bỏ qua chữ HOA/thường) là phần mở rộng gawk"
 
-#: eval.c:735
+#: eval.c:736
 msgid "`BINMODE' is a gawk extension"
 msgstr "“BINMODE” (chế độ nhị phân) là phần mở rộng gawk"
 
-#: eval.c:793
+#: eval.c:794
 #, c-format
 msgid "BINMODE value `%s' is invalid, treated as 3"
-msgstr "Giá trị BINMODE (chế độ nhị phân) “%s” không hợp lệ nên thấy là 3"
+msgstr "Giá trị BINMODE (chế độ nhị phân) “%s” không hợp lệ nên đã coi là 3"
 
-#: eval.c:884
+#: eval.c:885
 #, c-format
 msgid "bad `%sFMT' specification `%s'"
 msgstr "đặc tả “%sFMT” sai “%s”"
 
-#: eval.c:968
+#: eval.c:969
 msgid "turning off `--lint' due to assignment to `LINT'"
 msgstr "đang tắt “--lint” do việc gán cho “LINT”"
 
-#: eval.c:1146
+#: eval.c:1147
 #, c-format
 msgid "reference to uninitialized argument `%s'"
-msgstr "gặp tham chiếu đến đối số chưa được sở khởi “%s”"
+msgstr "gặp tham chiếu đến đối số chưa được khởi tạo “%s”"
 
-#: eval.c:1147
+#: eval.c:1148
 #, c-format
 msgid "reference to uninitialized variable `%s'"
-msgstr "gặp tham chiếu đến biến chưa được sở khởi “%s”"
+msgstr "gặp tham chiếu đến biến chưa được khởi tạo “%s”"
 
-#: eval.c:1165
+#: eval.c:1166
 msgid "attempt to field reference from non-numeric value"
 msgstr "cố gắng tham chiếu trường từ giá trị khác thuộc số"
 
-#: eval.c:1167
+#: eval.c:1168
 msgid "attempt to field reference from null string"
-msgstr "cố gắng tham chiếu trường từ chỗi trống rỗng"
+msgstr "cố gắng tham chiếu trường từ chuỗi trống rỗng"
 
-#: eval.c:1175
+#: eval.c:1176
 #, c-format
 msgid "attempt to access field %ld"
 msgstr "cố gắng để truy cập trường %ld"
 
-#: eval.c:1184
+#: eval.c:1185
 #, c-format
 msgid "reference to uninitialized field `$%ld'"
 msgstr "tham chiếu đến trường chưa được khởi tạo “$%ld”"
 
-#: eval.c:1271
+#: eval.c:1272
 #, c-format
 msgid "function `%s' called with more arguments than declared"
-msgstr "hàm “%s” được gọi với số đối số hơn số được tuyên bố"
+msgstr "hàm “%s” được gọi với nhiều số đối số hơn số được khai báo"
 
-#: eval.c:1466
+#: eval.c:1473
 #, c-format
 msgid "unwind_stack: unexpected type `%s'"
-msgstr "unwind_stack: không mong đợi kiểu “%s”"
+msgstr "unwind_stack: không cần kiểu “%s”"
 
-#: eval.c:1562
+#: eval.c:1569
 msgid "division by zero attempted in `/='"
-msgstr "cố gắng chia cho số không trong “/=”"
+msgstr "gặp phép chia cho số không trong “/=”"
 
-#: eval.c:1569
+#: eval.c:1576
 #, c-format
 msgid "division by zero attempted in `%%='"
-msgstr "cố gắng chia cho số không trong “%%=”"
+msgstr "gặp phép chia cho số không trong “%%=”"
 
 #: ext.c:89 ext.c:171
 msgid "extensions are not allowed in sandbox mode"
@@ -1953,7 +1970,7 @@ msgstr "phần mở rộng không cho phép ở chế độ khuôn đúc"
 msgid "-l / @load are gawk extensions"
 msgstr "-l / @load là một phần mở rộng gawk"
 
-#: ext.c:95 ext.c:177
+#: ext.c:95
 msgid "load_ext: received NULL lib_name"
 msgstr "load_ext: nhận được NULL lib_name"
 
@@ -1983,6 +2000,10 @@ msgstr "load_ext: thư viện “%s” thủ tục khởi tạo “%s” gặp l
 msgid "`extension' is a gawk extension"
 msgstr "“extension” là một phần mở rộng gawk"
 
+#: ext.c:177
+msgid "extension: received NULL lib_name"
+msgstr "extension: nhận được NULL lib_name"
+
 #: ext.c:180
 #, c-format
 msgid "extension: cannot open library `%s' (%s)"
@@ -2004,38 +2025,38 @@ msgstr "phần mở rộng: thư viện “%s”: không thể gọi hàm “%s�
 msgid "make_builtin: missing function name"
 msgstr "make_builtin: thiếu tên hàm"
 
-#: ext.c:238
+#: ext.c:236
 #, c-format
 msgid "make_builtin: can't redefine function `%s'"
 msgstr "make_builtin: không thể định nghĩa lại hàm “%s”"
 
-#: ext.c:242
+#: ext.c:240
 #, c-format
 msgid "make_builtin: function `%s' already defined"
 msgstr "make_builtin: hàm “%s” đã được định nghĩa rồi"
 
-#: ext.c:246
+#: ext.c:244
 #, c-format
 msgid "make_builtin: function name `%s' previously defined"
 msgstr "make_builtin: hàm “%s” đã được định nghĩa trước đây rồi"
 
-#: ext.c:248
+#: ext.c:246
 #, c-format
 msgid "make_builtin: can't use gawk built-in `%s' as function name"
 msgstr ""
 "make_builtin: không thể sử dụng “%s” như là một hàm được xây dựng sẵn trong "
 "gawk"
 
-#: ext.c:251 ext.c:304
+#: ext.c:249 ext.c:304
 #, c-format
 msgid "make_builtin: negative argument count for function `%s'"
 msgstr "make_builtin: đối số dành cho số đếm bị âm cho hàm “%s”"
 
-#: ext.c:278
+#: ext.c:276
 msgid "extension: missing function name"
 msgstr "extension: (phần mở rộng) tên hàm còn thiếu"
 
-#: ext.c:283
+#: ext.c:279 ext.c:283
 #, c-format
 msgid "extension: illegal character `%c' in function name `%s'"
 msgstr "extension: (phần mở rộng) gặp ký tự cấm “%c” nằm trong tên hàm “%s”"
@@ -2043,17 +2064,17 @@ msgstr "extension: (phần mở rộng) gặp ký tự cấm “%c” nằm tron
 #: ext.c:291
 #, c-format
 msgid "extension: can't redefine function `%s'"
-msgstr "extension: (phần mở rộng) không thể xác định lại hàm “%s”"
+msgstr "extension: (phần mở rộng) không thể định nghĩa lại hàm “%s”"
 
 #: ext.c:295
 #, c-format
 msgid "extension: function `%s' already defined"
-msgstr "extension: (phần mở rộng) hàm “%s” đã được xác định"
+msgstr "extension: (phần mở rộng) hàm “%s” đã được định nghĩa"
 
 #: ext.c:299
 #, c-format
 msgid "extension: function name `%s' previously defined"
-msgstr "tên hàm “%s” đã được xác định trước"
+msgstr "tên hàm “%s” đã được định nghĩa trước đó"
 
 #: ext.c:301
 #, c-format
@@ -2062,139 +2083,143 @@ msgstr ""
 "extension: (phần mở rộng) không thể dùng điều có sẵn của gawk “%s” như là "
 "tên hàm"
 
-#: ext.c:374
+#: ext.c:375
 #, c-format
 msgid "function `%s' defined to take no more than %d argument(s)"
-msgstr "hàm “%s” được xác định để chấp nhấn %d đối số tối đa"
+msgstr "hàm “%s” được định nghĩa để chấp nhấn %d đối số tối đa"
 
-#: ext.c:377
+#: ext.c:378
 #, c-format
 msgid "function `%s': missing argument #%d"
 msgstr "hàm “%s”: thiếu đối số #%d"
 
-#: ext.c:394
+#: ext.c:395
 #, c-format
 msgid "function `%s': argument #%d: attempt to use scalar as an array"
 msgstr "hàm “%s”: đối số thứ %d: cố gắng dùng kiểu vô hướng như là mảng"
 
-#: ext.c:398
+#: ext.c:399
 #, c-format
 msgid "function `%s': argument #%d: attempt to use array as a scalar"
 msgstr "hàm “%s”: đối số thứ %d: cố gắng dùng mảng như là kiểu vô hướng"
 
-#: ext.c:412
+#: ext.c:413
 msgid "dynamic loading of library not supported"
 msgstr "tải động của thư viện không được hỗ trợ"
 
-#: extension/filefuncs.c:97
+#: extension/filefuncs.c:159
 msgid "chdir: called with incorrect number of arguments, expecting 1"
 msgstr "chdir: được gọi với số lượng đối số không đúng, cần 1"
 
-#: extension/filefuncs.c:343
+#: extension/filefuncs.c:439
 #, c-format
 msgid "stat: unable to read symbolic link `%s'"
 msgstr "stat: không thể đọc liên kết mềm “%s”"
 
-#: extension/filefuncs.c:376
+#: extension/filefuncs.c:472
 msgid "stat: called with wrong number of arguments"
 msgstr "stat: được gọi với số lượng đối số không đúng"
 
-#: extension/filefuncs.c:383
+#: extension/filefuncs.c:479
 msgid "stat: bad parameters"
 msgstr "stat: các đối số sai"
 
-#: extension/filefuncs.c:437
+#: extension/filefuncs.c:533
 #, c-format
 msgid "fts init: could not create variable %s"
 msgstr "khởi tạo fts: không thể tạo biến %s"
 
-#: extension/filefuncs.c:460
+#: extension/filefuncs.c:554
+msgid "fts is not supported on this system"
+msgstr "fts không được hỗ trợ trên hệ thống này"
+
+#: extension/filefuncs.c:573
 msgid "fill_stat_element: could not create array"
 msgstr "fill_stat_element: không thể tạo mảng"
 
-#: extension/filefuncs.c:469
+#: extension/filefuncs.c:582
 msgid "fill_stat_element: could not set element"
 msgstr "fill_stat_element: không thể đặt phần tử"
 
-#: extension/filefuncs.c:484
+#: extension/filefuncs.c:597
 msgid "fill_path_element: could not set element"
 msgstr "fill_path_element: không thể đặt phần tử"
 
-#: extension/filefuncs.c:500
+#: extension/filefuncs.c:613
 msgid "fill_error_element: could not set element"
 msgstr "fill_error_element: không thể đặt phần tử"
 
-#: extension/filefuncs.c:547 extension/filefuncs.c:594
+#: extension/filefuncs.c:660 extension/filefuncs.c:707
 msgid "fts-process: could not create array"
 msgstr "fts-process: không thể tạo mảng"
 
-#: extension/filefuncs.c:557 extension/filefuncs.c:604
-#: extension/filefuncs.c:622
+#: extension/filefuncs.c:670 extension/filefuncs.c:717
+#: extension/filefuncs.c:735
 msgid "fts-process: could not set element"
 msgstr "fts-process: không thể đặt phần tử"
 
-#: extension/filefuncs.c:671
+#: extension/filefuncs.c:784
 msgid "fts: called with incorrect number of arguments, expecting 3"
 msgstr "fts: được gọi với số lượng đối số không đúng, cần 3"
 
-#: extension/filefuncs.c:674
+#: extension/filefuncs.c:787
 msgid "fts: bad first parameter"
 msgstr "fts: đối số đầu tiên sai"
 
-#: extension/filefuncs.c:680
+#: extension/filefuncs.c:793
 msgid "fts: bad second parameter"
 msgstr "fts: đối số thứ hai sai"
 
-#: extension/filefuncs.c:686
+#: extension/filefuncs.c:799
 msgid "fts: bad third parameter"
 msgstr "fts: đối số thứ ba sai"
 
-#: extension/filefuncs.c:693
+#: extension/filefuncs.c:806
 msgid "fts: could not flatten array\n"
 msgstr "fts: không thể làm phẳng mảng\n"
 
-#: extension/filefuncs.c:711
+#: extension/filefuncs.c:824
 msgid "fts: ignoring sneaky FTS_NOSTAT flag. nyah, nyah, nyah."
 msgstr "fts: bỏ qua cờ FTS_NOSTAT vụng trộm. nyah, nyah, nyah."
 
-#: extension/filefuncs.c:728
+#: extension/filefuncs.c:841
 msgid "fts: clear_array() failed\n"
 msgstr "fts: clear_array() gặp lỗi\n"
 
-#: extension/fnmatch.c:98
+#: extension/fnmatch.c:112
 msgid "fnmatch: called with less than three arguments"
 msgstr "fnmatch: được gọi với ít hơn ba đối số"
 
-#: extension/fnmatch.c:101
+#: extension/fnmatch.c:115
 msgid "fnmatch: called with more than three arguments"
 msgstr "fnmatch: được gọi với nhiều hơn ba đối số"
 
-#: extension/fnmatch.c:104
+#: extension/fnmatch.c:118
 msgid "fnmatch: could not get first argument"
 msgstr "fnmatch: không lấy được đối số đầu tiên"
 
-#: extension/fnmatch.c:109
+#: extension/fnmatch.c:123
 msgid "fnmatch: could not get second argument"
 msgstr "fnmatch: không lấy được đối số thứ hai"
 
-#: extension/fnmatch.c:114
+#: extension/fnmatch.c:128
 msgid "fnmatch: could not get third argument"
 msgstr "fnmatch: không thể lấy tham số thứ ba"
 
-#: extension/fnmatch.c:127
+#: extension/fnmatch.c:141
 msgid "fnmatch is not implemented on this system\n"
 msgstr "fnmatch không được hỗ trợ trên hệ thống này\n"
 
-#: extension/fnmatch.c:159
+#: extension/fnmatch.c:173
 msgid "fnmatch init: could not add FNM_NOMATCH variable"
 msgstr "khởi tạo fnmatch: không thể thêm biến FNM_NOMATCH"
 
-#: extension/fnmatch.c:169
+#: extension/fnmatch.c:183
 #, c-format
 msgid "fnmatch init: could not set array element %s"
 msgstr "fnmatch init: không thể đặt phần tử mảng %s"
 
-#: extension/fnmatch.c:179
+#: extension/fnmatch.c:193
 msgid "fnmatch init: could not install FNM array"
 msgstr "khởi tạo fnmatch: không thể cài đặt mảng FNM"
 
@@ -2218,88 +2243,88 @@ msgstr "wait: được gọi mà không truyền đối số"
 msgid "wait: called with too many arguments"
 msgstr "wait: được gọi với quá nhiều đối số"
 
-#: extension/inplace.c:110
+#: extension/inplace.c:130
 msgid "inplace_begin: in-place editing already active"
 msgstr "inplace_begin: sửa in-place đã sẵn được kích hoạt rồi"
 
-#: extension/inplace.c:113 extension/inplace.c:187
+#: extension/inplace.c:133 extension/inplace.c:207
 #, c-format
 msgid "inplace_begin: expects 2 arguments but called with %d"
 msgstr "inplace_begin: cần 2 đối số như lại được gọi với %d"
 
-#: extension/inplace.c:116
+#: extension/inplace.c:136
 msgid "inplace_begin: cannot retrieve 1st argument as a string filename"
 msgstr "inplace_begin: không thể lấy đối số thứ nhất như là tên tập tin"
 
-#: extension/inplace.c:124
+#: extension/inplace.c:144
 #, c-format
 msgid "inplace_begin: disabling in-place editing for invalid FILENAME `%s'"
-msgstr "inplace_begin: tắt sửa chữa in-place cho TÊN-TẬP-TIN không hợp lệ “%s”"
+msgstr "inplace_begin: tắt sửa chữa in-place cho TÊN_TẬP_TIN không hợp lệ “%s”"
 
-#: extension/inplace.c:131
+#: extension/inplace.c:151
 #, c-format
 msgid "inplace_begin: Cannot stat `%s' (%s)"
-msgstr "inplace_begin: Không thể lấy trạng thái của “%s” (%s)"
+msgstr "inplace_begin: Không thể lấy thông tin thống kê của “%s” (%s)"
 
-#: extension/inplace.c:138
+#: extension/inplace.c:158
 #, c-format
 msgid "inplace_begin: `%s' is not a regular file"
 msgstr "inplace_begin: “%s” không phải là tập tin thường"
 
-#: extension/inplace.c:149
+#: extension/inplace.c:169
 #, c-format
 msgid "inplace_begin: mkstemp(`%s') failed (%s)"
 msgstr "inplace_begin: mkstemp(“%s”) gặp lỗi (%s)"
 
-#: extension/inplace.c:158
+#: extension/inplace.c:178
 #, c-format
 msgid "inplace_begin: chmod failed (%s)"
 msgstr "inplace_begin: chmod gặp lỗi (%s)"
 
-#: extension/inplace.c:165
+#: extension/inplace.c:185
 #, c-format
 msgid "inplace_begin: dup(stdout) failed (%s)"
 msgstr "inplace_begin: dup(stdout) gặp lỗi (%s)"
 
-#: extension/inplace.c:168
+#: extension/inplace.c:188
 #, c-format
 msgid "inplace_begin: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_begin: dup2(%d, stdout) gặp lỗi (%s)"
 
-#: extension/inplace.c:171
+#: extension/inplace.c:191
 #, c-format
 msgid "inplace_begin: close(%d) failed (%s)"
 msgstr "inplace_begin: close(%d) gặp lỗi (%s)"
 
-#: extension/inplace.c:190
+#: extension/inplace.c:210
 msgid "inplace_end: cannot retrieve 1st argument as a string filename"
 msgstr "inplace_end: không thể lấy lại đối số thứ nhất như là một tên tập tin"
 
-#: extension/inplace.c:197
+#: extension/inplace.c:217
 msgid "inplace_end: in-place editing not active"
 msgstr "inplace_end: việc sửa in-place không được kích hoạt"
 
-#: extension/inplace.c:203
+#: extension/inplace.c:223
 #, c-format
 msgid "inplace_end: dup2(%d, stdout) failed (%s)"
 msgstr "inplace_end: dup2(%d, stdout) gặp lỗi (%s)"
 
-#: extension/inplace.c:206
+#: extension/inplace.c:226
 #, c-format
 msgid "inplace_end: close(%d) failed (%s)"
 msgstr "inplace_end: close(%d) gặp lỗi (%s)"
 
-#: extension/inplace.c:210
+#: extension/inplace.c:230
 #, c-format
 msgid "inplace_end: fsetpos(stdout) failed (%s)"
 msgstr "inplace_end: fsetpos(stdout) gặp lỗi (%s)"
 
-#: extension/inplace.c:223
+#: extension/inplace.c:243
 #, c-format
 msgid "inplace_end: link(`%s', `%s') failed (%s)"
 msgstr "inplace_end: link(“%s”, “%s”) gặp lỗi (%s)"
 
-#: extension/inplace.c:229
+#: extension/inplace.c:253
 #, c-format
 msgid "inplace_end: rename(`%s', `%s') failed (%s)"
 msgstr "inplace_end: rename(“%s”, “%s”) gặp lỗi (%s)"
@@ -2328,178 +2353,178 @@ msgstr "chr: được gọi mà không có đối số"
 msgid "chr: called with inappropriate argument(s)"
 msgstr "chr: được gọi với đối số không thích hợp"
 
-#: extension/readdir.c:203
+#: extension/readdir.c:281
 #, c-format
 msgid "dir_take_control_of: opendir/fdopendir failed: %s"
 msgstr "dir_take_control_of: opendir/fdopendir gặp lỗi: %s"
 
-#: extension/readfile.c:84
+#: extension/readfile.c:113
 msgid "readfile: called with too many arguments"
 msgstr "readfile: được gọi với quá nhiều đối số"
 
-#: extension/readfile.c:118
+#: extension/readfile.c:137
 msgid "readfile: called with no arguments"
 msgstr "readfile: được gọi mà không có đối số"
 
-#: extension/rwarray.c:120
+#: extension/rwarray.c:124
 msgid "writea: called with too many arguments"
 msgstr "writea: được gọi với quá nhiều đối số"
 
-#: extension/rwarray.c:127
+#: extension/rwarray.c:131
 #, c-format
 msgid "do_writea: argument 0 is not a string\n"
 msgstr "do_writea: đối số 0 không phải là một chuỗi\n"
 
-#: extension/rwarray.c:133
+#: extension/rwarray.c:137
 #, c-format
 msgid "do_writea: argument 1 is not an array\n"
 msgstr "do_writea: đối số 1 không phải là một mảng\n"
 
-#: extension/rwarray.c:180
+#: extension/rwarray.c:184
 #, c-format
 msgid "write_array: could not flatten array\n"
 msgstr "write_array: không thể làm phẳng mảng\n"
 
-#: extension/rwarray.c:194
+#: extension/rwarray.c:198
 #, c-format
 msgid "write_array: could not release flattened array\n"
 msgstr "write_array: không thể giải phóng mảng được làm phẳng\n"
 
-#: extension/rwarray.c:276
+#: extension/rwarray.c:280
 msgid "reada: called with too many arguments"
 msgstr "reada: được gọi với quá nhiều đối số"
 
-#: extension/rwarray.c:283
+#: extension/rwarray.c:287
 #, c-format
 msgid "do_reada: argument 0 is not a string\n"
 msgstr "do_reada: đối số 0 không phải là một chuỗi\n"
 
-#: extension/rwarray.c:289
+#: extension/rwarray.c:293
 #, c-format
 msgid "do_reada: argument 1 is not an array\n"
 msgstr "do_reada: đối số 1 không phải là một mảng\n"
 
-#: extension/rwarray.c:333
+#: extension/rwarray.c:337
 #, c-format
 msgid "do_reada: clear_array failed\n"
 msgstr "do_reada: clear_array gặp lỗi\n"
 
-#: extension/rwarray.c:370
+#: extension/rwarray.c:374
 #, c-format
 msgid "read_array: set_array_element failed\n"
 msgstr "read_array: set_array_element gặp lỗi\n"
 
-#: extension/time.c:81
+#: extension/time.c:113
 msgid "gettimeofday: ignoring arguments"
 msgstr "gettimeofday: đang lờ đi các đối số"
 
-#: extension/time.c:112
+#: extension/time.c:144
 msgid "gettimeofday: not supported on this platform"
 msgstr "gettimeofday: không được hỗ trợ trên nền tảng này"
 
-#: extension/time.c:133
+#: extension/time.c:165
 msgid "sleep: called with too many arguments"
 msgstr "sleep: được gọi với quá nhiều đối số"
 
-#: extension/time.c:136
+#: extension/time.c:168
 msgid "sleep: missing required numeric argument"
 msgstr "sleep: thiếu đối số dạng số cần thiết"
 
-#: extension/time.c:142
+#: extension/time.c:174
 msgid "sleep: argument is negative"
 msgstr "sleep: đối số âm"
 
-#: extension/time.c:176
+#: extension/time.c:208
 msgid "sleep: not supported on this platform"
 msgstr "sleep: không được hỗ trợ trên nền tảng này"
 
-#: field.c:339
+#: field.c:345
 msgid "NF set to negative value"
 msgstr "“NF” được đặt thành giá trị âm"
 
-#: field.c:964 field.c:971 field.c:975
+#: field.c:971 field.c:978 field.c:982
 msgid "split: fourth argument is a gawk extension"
 msgstr "split (chia tách): đối số thứ tư là phần mở rộng gawk"
 
-#: field.c:968
+#: field.c:975
 msgid "split: fourth argument is not an array"
 msgstr "split (chia tách): đối số thứ tư không phải là mảng"
 
-#: field.c:982
+#: field.c:989
 msgid "split: second argument is not an array"
 msgstr "split: (chia tách) đối số thứ hai không phải là mảng"
 
-#: field.c:986
+#: field.c:993
 msgid "split: cannot use the same array for second and fourth args"
 msgstr ""
 "split (chia tách): không thể sử dụng cùng một mảng có cả đối số thứ hai và "
 "thứ tư"
 
-#: field.c:991
+#: field.c:998
 msgid "split: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "split (phân tách): không thể sử dụng mảng con của tham số thứ hai cho tham "
 "số thứ tư"
 
-#: field.c:994
+#: field.c:1001
 msgid "split: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "split (phân tách): không thể sử dụng mảng con của tham số thứ tư cho tham số "
 "thứ hai"
 
-#: field.c:1023
+#: field.c:1032
 msgid "split: null string for third arg is a gawk extension"
 msgstr ""
 "split: (chia tách) chuỗi vô giá trị cho đối số thứ ba là phần mở rộng gawk"
 
-#: field.c:1063
+#: field.c:1072
 msgid "patsplit: fourth argument is not an array"
 msgstr "patsplit: đối số thứ tư không phải là mảng"
 
-#: field.c:1068
+#: field.c:1077
 msgid "patsplit: second argument is not an array"
 msgstr "patsplit: đối số thứ hai không phải là mảng"
 
-#: field.c:1074
+#: field.c:1083
 msgid "patsplit: third argument must be non-null"
 msgstr "patsplit: đối số thứ ba không phải không rỗng"
 
-#: field.c:1078
+#: field.c:1087
 msgid "patsplit: cannot use the same array for second and fourth args"
 msgstr ""
 "patsplit (chương trình chia tách): không thể sử dụng cùng một mảng cho cả "
 "hai đối số thứ hai và thứ tư"
 
-#: field.c:1083
+#: field.c:1092
 msgid "patsplit: cannot use a subarray of second arg for fourth arg"
 msgstr ""
 "patsplit (chương trình phân tách): không thể sử dụng mảng con của tham số "
 "thứ hai cho tham số thứ tư"
 
-#: field.c:1086
+#: field.c:1095
 msgid "patsplit: cannot use a subarray of fourth arg for second arg"
 msgstr ""
 "patsplit (chương trình phân tách): không thể sử dụng mảng con của tham số "
 "thứ tư cho tham số thứ hai"
 
-#: field.c:1124
+#: field.c:1133
 msgid "`FIELDWIDTHS' is a gawk extension"
 msgstr "“FIELDWIDTHS” (độ rộng trường) là phần mở rộng gawk"
 
-#: field.c:1188
+#: field.c:1197
 #, c-format
 msgid "invalid FIELDWIDTHS value, near `%s'"
 msgstr "giá trị FIELDWIDTHS (độ rộng trường) không hợp lệ, gần “%s”"
 
-#: field.c:1261
+#: field.c:1270
 msgid "null string for `FS' is a gawk extension"
 msgstr "chuỗi vô giá trị cho “FS” là phần mở rộng gawk"
 
-#: field.c:1265
+#: field.c:1274
 msgid "old awk does not support regexps as value of `FS'"
 msgstr "awk cũ không hỗ trợ biểu thức chính quy làm giá trị của “FS”"
 
-#: field.c:1384
+#: field.c:1393
 msgid "`FPAT' is a gawk extension"
 msgstr "“FPAT” là phần mở rộng của gawk"
 
@@ -2515,386 +2540,386 @@ msgstr "node_to_awk_value: nút nhận được là null"
 msgid "node_to_awk_value: received null val"
 msgstr "node_to_awk_value: biến nhận được là null"
 
-#: gawkapi.c:808
+#: gawkapi.c:807
 msgid "remove_element: received null array"
 msgstr "remove_element: mảng nhận được là null"
 
-#: gawkapi.c:811
+#: gawkapi.c:810
 msgid "remove_element: received null subscript"
 msgstr "remove_element: nhận được là null"
 
-#: gawkapi.c:943
+#: gawkapi.c:947
 #, c-format
 msgid "api_flatten_array: could not convert index %d\n"
 msgstr "api_flatten_array: không thể chuyển đổi chỉ số %d\n"
 
-#: gawkapi.c:948
+#: gawkapi.c:952
 #, c-format
 msgid "api_flatten_array: could not convert value %d\n"
 msgstr "api_flatten_array: không thể chuyển đổi giá trị %d\n"
 
-#: getopt.c:603 getopt.c:632
+#: getopt.c:604 getopt.c:633
 #, c-format
 msgid "%s: option '%s' is ambiguous; possibilities:"
 msgstr "%s: tùy chọn “%s” chưa rõ ràng; khả năng là:"
 
-#: getopt.c:678 getopt.c:682
+#: getopt.c:679 getopt.c:683
 #, c-format
 msgid "%s: option '--%s' doesn't allow an argument\n"
 msgstr "%s: tùy chọn “--%s” không cho phép đối số\n"
 
-#: getopt.c:691 getopt.c:696
+#: getopt.c:692 getopt.c:697
 #, c-format
 msgid "%s: option '%c%s' doesn't allow an argument\n"
 msgstr "%s: tùy chọn “%c%s” không cho phép đối số\n"
 
-#: getopt.c:739 getopt.c:758
+#: getopt.c:740 getopt.c:759
 #, c-format
 msgid "%s: option '--%s' requires an argument\n"
 msgstr "%s: tùy chọn “--%s” yêu cầu một đối số\n"
 
-#: getopt.c:796 getopt.c:799
+#: getopt.c:797 getopt.c:800
 #, c-format
 msgid "%s: unrecognized option '--%s'\n"
 msgstr "%s: không nhận ra tùy chọn “--%s”\n"
 
-#: getopt.c:807 getopt.c:810
+#: getopt.c:808 getopt.c:811
 #, c-format
 msgid "%s: unrecognized option '%c%s'\n"
 msgstr "%s: không nhận ra tùy chọn “%c%s”\n"
 
-#: getopt.c:859 getopt.c:862
+#: getopt.c:860 getopt.c:863
 #, c-format
 msgid "%s: invalid option -- '%c'\n"
 msgstr "%s: tùy chọn không hợp lệ -- “%c”\n"
 
-#: getopt.c:915 getopt.c:932 getopt.c:1142 getopt.c:1160
+#: getopt.c:916 getopt.c:933 getopt.c:1143 getopt.c:1161
 #, c-format
 msgid "%s: option requires an argument -- '%c'\n"
 msgstr "%s: tùy chọn yêu cầu một đối số -- “%c”\n"
 
-#: getopt.c:988 getopt.c:1004
+#: getopt.c:989 getopt.c:1005
 #, c-format
 msgid "%s: option '-W %s' is ambiguous\n"
 msgstr "%s: tùy chọn “-W %s” vẫn mơ hồ\n"
 
-#: getopt.c:1028 getopt.c:1046
+#: getopt.c:1029 getopt.c:1047
 #, c-format
 msgid "%s: option '-W %s' doesn't allow an argument\n"
 msgstr "%s: tùy chọn “-W %s” không cho phép đối số\n"
 
-#: getopt.c:1067 getopt.c:1085
+#: getopt.c:1068 getopt.c:1086
 #, c-format
 msgid "%s: option '-W %s' requires an argument\n"
 msgstr "%s: tùy chọn “-W %s” yêu cầu một đối số\n"
 
-#: io.c:347
+#: io.c:392
 #, c-format
 msgid "command line argument `%s' is a directory: skipped"
 msgstr "tham số dòng lệnh “%s” là một thư mục: đã bị bỏ qua"
 
-#: io.c:350 io.c:463
+#: io.c:395 io.c:513
 #, c-format
 msgid "cannot open file `%s' for reading (%s)"
 msgstr "không mở được tập tin “%s” để đọc (%s)"
 
-#: io.c:590
+#: io.c:640
 #, c-format
 msgid "close of fd %d (`%s') failed (%s)"
 msgstr "lỗi đóng fd %d (“%s”) (%s)"
 
-#: io.c:666
+#: io.c:716
 msgid "redirection not allowed in sandbox mode"
 msgstr "chuyển hướng không cho phép ở chế độ khuôn đúc"
 
-#: io.c:700
+#: io.c:750
 #, c-format
 msgid "expression in `%s' redirection only has numeric value"
 msgstr "biểu thức trong điều chuyển hướng “%s” chỉ có giá trị thuộc số"
 
-#: io.c:706
+#: io.c:756
 #, c-format
 msgid "expression for `%s' redirection has null string value"
 msgstr "biểu thức cho điều chuyển hướng “%s” có giá trị chuỗi vô giá trị"
 
-#: io.c:711
+#: io.c:761
 #, c-format
 msgid "filename `%s' for `%s' redirection may be result of logical expression"
 msgstr ""
 "tên tập tin “%s” cho điều chuyển hướng “%s” có lẽ là kết quả của biểu thức "
 "luận lý"
 
-#: io.c:754
+#: io.c:809
 #, c-format
 msgid "unnecessary mixing of `>' and `>>' for file `%.*s'"
 msgstr "không cần hợp “>” và “>>” cho tập tin “%.*s”"
 
-#: io.c:808
+#: io.c:863
 #, c-format
 msgid "can't open pipe `%s' for output (%s)"
 msgstr "không thể mở ống dẫn “%s” để xuất (%s)"
 
-#: io.c:818
+#: io.c:873
 #, c-format
 msgid "can't open pipe `%s' for input (%s)"
 msgstr "không thể mở ống dẫn “%s” để nhập (%s)"
 
-#: io.c:849
+#: io.c:904
 #, c-format
 msgid "can't open two way pipe `%s' for input/output (%s)"
 msgstr "không thể mở ống dẫn hai chiều “%s” để nhập/xuất (%s)"
 
-#: io.c:928
+#: io.c:986
 #, c-format
 msgid "can't redirect from `%s' (%s)"
 msgstr "không thể chuyển hướng từ “%s” (%s)"
 
-#: io.c:931
+#: io.c:989
 #, c-format
 msgid "can't redirect to `%s' (%s)"
 msgstr "không thể chuyển hướng đến “%s” (%s)"
 
-#: io.c:982
+#: io.c:1040
 msgid ""
 "reached system limit for open files: starting to multiplex file descriptors"
 msgstr ""
 "đã tới giới hạn hệ thống về tập tin được mở nên bắt đầu phối hợp nhiều dòng "
 "điều mô tả tập tin"
 
-#: io.c:998
+#: io.c:1056
 #, c-format
 msgid "close of `%s' failed (%s)."
 msgstr "lỗi đóng “%s” (%s)"
 
-#: io.c:1006
+#: io.c:1064
 msgid "too many pipes or input files open"
 msgstr "quá nhiều ống dẫn hay tập tin nhập được mở"
 
-#: io.c:1028
+#: io.c:1086
 msgid "close: second argument must be `to' or `from'"
 msgstr "close: (đóng) đối số thứ hai phải là “to” (đến) hay “from” (từ)"
 
-#: io.c:1045
+#: io.c:1103
 #, c-format
 msgid "close: `%.*s' is not an open file, pipe or co-process"
 msgstr ""
 "close: (đóng) “%.*s” không phải là tập tin, ống dẫn hay đồng tiến trình đã "
 "được mở"
 
-#: io.c:1050
+#: io.c:1108
 msgid "close of redirection that was never opened"
 msgstr "đóng một chuyển hướng mà nó chưa từng được mở"
 
-#: io.c:1147
+#: io.c:1205
 #, c-format
 msgid "close: redirection `%s' not opened with `|&', second argument ignored"
 msgstr ""
 "close: chuyển hướng “%s” không được mở bởi “|&” nên đối số thứ hai bị bỏ qua"
 
-#: io.c:1164
+#: io.c:1222
 #, c-format
 msgid "failure status (%d) on pipe close of `%s' (%s)"
 msgstr "trạng thái thất bại (%d) khi đóng ống dẫn “%s” (%s)"
 
-#: io.c:1167
+#: io.c:1225
 #, c-format
 msgid "failure status (%d) on file close of `%s' (%s)"
 msgstr "trạng thái thất bại (%d) khi đóng tập tin “%s” (%s)"
 
-#: io.c:1187
+#: io.c:1245
 #, c-format
 msgid "no explicit close of socket `%s' provided"
 msgstr "không cung cấp lệnh đóng ổ cắm “%s” rõ ràng"
 
-#: io.c:1190
+#: io.c:1248
 #, c-format
 msgid "no explicit close of co-process `%s' provided"
 msgstr "không cung cấp lệnh đóng đồng tiến trình “%s” rõ ràng"
 
-#: io.c:1193
+#: io.c:1251
 #, c-format
 msgid "no explicit close of pipe `%s' provided"
 msgstr "không cung cấp lệnh đóng đường ống dẫn lệnh “%s” rõ ràng"
 
-#: io.c:1196
+#: io.c:1254
 #, c-format
 msgid "no explicit close of file `%s' provided"
 msgstr "không cung cấp lệnh đóng tập tin “%s” rõ ràng"
 
-#: io.c:1224 io.c:1279 main.c:842 main.c:879
+#: io.c:1284 io.c:1342 main.c:864 main.c:906
 #, c-format
 msgid "error writing standard output (%s)"
 msgstr "gặp lỗi khi ghi đầu ra tiêu chuẩn (%s)"
 
-#: io.c:1228 io.c:1284
+#: io.c:1289 io.c:1348 main.c:866
 #, c-format
 msgid "error writing standard error (%s)"
 msgstr "gặp lỗi khi ghi thiết bị lỗi chuẩn (%s)"
 
-#: io.c:1236
+#: io.c:1297
 #, c-format
 msgid "pipe flush of `%s' failed (%s)."
 msgstr "lỗi xoá sạch ống dẫn “%s” (%s)"
 
-#: io.c:1239
+#: io.c:1300
 #, c-format
 msgid "co-process flush of pipe to `%s' failed (%s)."
 msgstr "lỗi xoá sạch ống dẫn đồng tiến trình đến “%s” (%s)"
 
-#: io.c:1242
+#: io.c:1303
 #, c-format
 msgid "file flush of `%s' failed (%s)."
 msgstr "lỗi xoá sạch tập tin “%s” (%s)"
 
-#: io.c:1356
+#: io.c:1420
 #, c-format
 msgid "local port %s invalid in `/inet'"
 msgstr "cổng cục bộ %s không hợp lệ trong “/inet”"
 
-#: io.c:1374
+#: io.c:1438
 #, c-format
 msgid "remote host and port information (%s, %s) invalid"
 msgstr "thông tin về máy/cổng ở xa (%s, %s) không phải hợp lệ"
 
-#: io.c:1526
+#: io.c:1590
 #, c-format
 msgid "no (known) protocol supplied in special filename `%s'"
 msgstr "trong tên tập tin đặc biệt “%s” không cung cấp giao thức (đã biết) nào"
 
-#: io.c:1540
+#: io.c:1604
 #, c-format
 msgid "special file name `%s' is incomplete"
 msgstr "tên tập tin đặc biệt “%s” chưa xong"
 
-#: io.c:1557
+#: io.c:1621
 msgid "must supply a remote hostname to `/inet'"
 msgstr "phải cung cấp một tên máy chủ cho </inet>"
 
-#: io.c:1575
+#: io.c:1639
 msgid "must supply a remote port to `/inet'"
 msgstr "phải cung cấp một cổng máy chủ cho </inet>"
 
-#: io.c:1621
+#: io.c:1685
 msgid "TCP/IP communications are not supported"
 msgstr "truyền thông TCP/IP không được hỗ trợ"
 
-#: io.c:1796
+#: io.c:1867
 #, c-format
 msgid "could not open `%s', mode `%s'"
 msgstr "không mở được “%s”, chế độ “%s”"
 
-#: io.c:1846
+#: io.c:1917
 #, c-format
 msgid "close of master pty failed (%s)"
-msgstr "lỗi đóng pty (tài sản?) chính (%s)"
+msgstr "gặp lỗi khi đóng thiết bị cuối giả (%s)"
 
-#: io.c:1848 io.c:2024 io.c:2194
+#: io.c:1919 io.c:2105 io.c:2305
 #, c-format
 msgid "close of stdout in child failed (%s)"
-msgstr "lỗi đóng thiết bị xuất chuẩn trong tiến trình con (%s)"
+msgstr "lỗi đóng đầu ra tiêu chuẩn trong tiến trình con (%s)"
 
-#: io.c:1851
+#: io.c:1922
 #, c-format
 msgid "moving slave pty to stdout in child failed (dup: %s)"
 msgstr ""
-"gặp lỗi khi di chuyển pty phụ thuộc đến thiết bị xuất chuẩn trong con "
-"(trùng: %s)"
+"gặp lỗi khi di chuyển pty (thiết bị cuối giả) phụ thuộc đến thiết bị đầu ra "
+"tiêu chuẩn trong con (trùng: %s)"
 
-#: io.c:1853 io.c:2029
+#: io.c:1924 io.c:2110
 #, c-format
 msgid "close of stdin in child failed (%s)"
 msgstr "lỗi đóng thiết bị nhập chuẩn trong tiến trình con (%s)"
 
-#: io.c:1856
+#: io.c:1927
 #, c-format
 msgid "moving slave pty to stdin in child failed (dup: %s)"
 msgstr ""
-"lỗi di chuyển pty (tài sản?) phụ tới thiết bị nhập chuẩn trong điều con "
-"(nhân đôi: %s)"
+"lỗi di chuyển pty (thiết bị cuối giả) phụ tới thiết bị nhập chuẩn trong điều "
+"con (nhân đôi: %s)"
 
-#: io.c:1858 io.c:1879
+#: io.c:1929 io.c:1951
 #, c-format
 msgid "close of slave pty failed (%s)"
-msgstr "đóng pty phụ thuộc gặp lỗi (%s)"
+msgstr "đóng pty (thiết bị cuối giả) phụ thuộc gặp lỗi (%s)"
 
-#: io.c:1965 io.c:2027 io.c:2171 io.c:2197
+#: io.c:2040 io.c:2108 io.c:2276 io.c:2308
 #, c-format
 msgid "moving pipe to stdout in child failed (dup: %s)"
 msgstr ""
-"lỗi di chuyển ống dẫn đến thiết bị xuất chuẩn trong tiến trình con (dup "
-"(nhân đôi): %s)"
+"lỗi di chuyển ống dẫn đến thiết bị xuất chuẩn trong tiến trình con (trùng: "
+"%s)"
 
-#: io.c:1972 io.c:2032
+#: io.c:2047 io.c:2113
 #, c-format
 msgid "moving pipe to stdin in child failed (dup: %s)"
 msgstr ""
-"lỗi di chuyển ống dẫn đến thiết bị nhập chuẩn trong tiến trình con (dup "
-"(nhân đôi): %s)"
+"lỗi di chuyển ống dẫn đến thiết bị nhập chuẩn trong tiến trình con (trùng: "
+"%s)"
 
-#: io.c:1992 io.c:2187
+#: io.c:2073 io.c:2298
 msgid "restoring stdout in parent process failed\n"
 msgstr "phục hồi đầu ra tiêu chuẩn trong tiến trình mẹ gặp lỗi\n"
 
-#: io.c:2000
+#: io.c:2081
 msgid "restoring stdin in parent process failed\n"
 msgstr "phục hồi đầu vào tiêu chuẩn trong tiến trình mẹ gặp lỗi\n"
 
-#: io.c:2035 io.c:2199 io.c:2213
+#: io.c:2116 io.c:2310 io.c:2324
 #, c-format
 msgid "close of pipe failed (%s)"
 msgstr "đóng ống dẫn gặp lỗi (%s)"
 
-#: io.c:2089
+#: io.c:2174
 msgid "`|&' not supported"
 msgstr "“|&” không được hỗ trợ"
 
-#: io.c:2156
+#: io.c:2261
 #, c-format
 msgid "cannot open pipe `%s' (%s)"
 msgstr "không thể mở ống dẫn “%s” (%s)"
 
-#: io.c:2207
+#: io.c:2318
 #, c-format
 msgid "cannot create child process for `%s' (fork: %s)"
 msgstr "không thể tạo tiến trình con cho “%s” (fork: %s)"
 
-#: io.c:2667
+#: io.c:2790
 msgid "register_input_parser: received NULL pointer"
 msgstr "register_input_parser: nhận được con trỏ NULL"
 
-#: io.c:2695
+#: io.c:2818
 #, c-format
 msgid "input parser `%s' conflicts with previously installed input parser `%s'"
 msgstr ""
 "bộ phân tích đầu vào “%s” xung đột với bộ phân tích đầu vào được cài đặt "
 "trước đó “%s”"
 
-#: io.c:2702
+#: io.c:2825
 #, c-format
 msgid "input parser `%s' failed to open `%s'"
 msgstr "bộ phân tích đầu vào “%s” gặp lỗi khi mở “%s”"
 
-#: io.c:2722
+#: io.c:2845
 msgid "register_output_wrapper: received NULL pointer"
 msgstr "register_output_wrapper: nhận được con trỏ NULL"
 
-#: io.c:2750
+#: io.c:2873
 #, c-format
 msgid ""
 "output wrapper `%s' conflicts with previously installed output wrapper `%s'"
 msgstr ""
 "bộ bao kết xuất “%s” xung đột với bộ bao kết xuất được cài đặt trước đó “%s”"
 
-#: io.c:2757
+#: io.c:2880
 #, c-format
 msgid "output wrapper `%s' failed to open `%s'"
 msgstr "bộ bao kết xuất “%s” gặp lỗi khi mở “%s”"
 
-#: io.c:2778
+#: io.c:2901
 msgid "register_output_processor: received NULL pointer"
 msgstr "register_output_processor: nhận được con trỏ NULL"
 
-#: io.c:2807
+#: io.c:2930
 #, c-format
 msgid ""
 "two-way processor `%s' conflicts with previously installed two-way processor "
@@ -2903,221 +2928,221 @@ msgstr ""
 "bộ xử lý hai hướng “%s” xung đột với bộ xử lý hai hướng đã được cài đặt "
 "trước đó “%s”"
 
-#: io.c:2816
+#: io.c:2939
 #, c-format
 msgid "two way processor `%s' failed to open `%s'"
 msgstr "bộ xử lý hai hướng “%s” gặp lỗi khi mở “%s”"
 
-#: io.c:2923
+#: io.c:3064
 #, c-format
 msgid "data file `%s' is empty"
 msgstr "tập tin dữ liệu “%s” là rỗng"
 
-#: io.c:2965 io.c:2973
+#: io.c:3106 io.c:3114
 msgid "could not allocate more input memory"
 msgstr "không thể cấp phát bộ nhớ nhập thêm nữa"
 
-#: io.c:3539
+#: io.c:3682
 msgid "multicharacter value of `RS' is a gawk extension"
 msgstr "giá trị đa ký tự của “RS” là phần mở rộng gawk"
 
-#: io.c:3628
+#: io.c:3771
 msgid "IPv6 communication is not supported"
 msgstr "Truyền thông trên IPv6 không được hỗ trợ"
 
-#: main.c:388
+#: main.c:405
 msgid "empty argument to `-e/--source' ignored"
 msgstr "đối số rỗng cho tuỳ chọn “-e/--source” bị bỏ qua"
 
-#: main.c:478
+#: main.c:495
 #, c-format
 msgid "%s: option `-W %s' unrecognized, ignored\n"
 msgstr "%s: tùy chọn “-W %s” không được nhận diện nên bị bỏ qua\n"
 
-#: main.c:524
+#: main.c:541
 #, c-format
 msgid "%s: option requires an argument -- %c\n"
 msgstr "%s: tùy chọn cần đến đối số “-- %c”\n"
 
-#: main.c:545
+#: main.c:562
 msgid "environment variable `POSIXLY_CORRECT' set: turning on `--posix'"
 msgstr ""
 "biến môi trường “POSIXLY_CORRECT” (đúng kiểu POSIX) đã được đặt; đang bật "
 "tùy chọn “--posix”"
 
-#: main.c:551
+#: main.c:568
 msgid "`--posix' overrides `--traditional'"
 msgstr "tùy chọn “--posix” có quyền cao hơn “--traditional” (truyền thống)"
 
-#: main.c:562
+#: main.c:579
 msgid "`--posix'/`--traditional' overrides `--non-decimal-data'"
 msgstr ""
-"“--posix”/“--traditional” (truyền thống) có quyền cao hơn “--non-decimal-"
+"“--posix”/“--traditional” (cổ điển) có quyền cao hơn “--non-decimal-"
 "data” (dữ liệu khác thập phân)"
 
-#: main.c:566
+#: main.c:583
 #, c-format
 msgid "running %s setuid root may be a security problem"
 msgstr "việc chạy %s với tư cách “setuid root” có thể rủi rỏ bảo mật"
 
-#: main.c:571
+#: main.c:588
 msgid "`--posix' overrides `--characters-as-bytes'"
 msgstr "“--posix” đè lên “--characters-as-bytes”"
 
-#: main.c:630
+#: main.c:647
 #, c-format
 msgid "can't set binary mode on stdin (%s)"
-msgstr "không thể đặt chế độ nhị phân trên thiết bị nhập chuẩn (%s)"
+msgstr "không thể đặt chế độ nhị phân trên đầu vào tiêu chuẩn (%s)"
 
-#: main.c:633
+#: main.c:650
 #, c-format
 msgid "can't set binary mode on stdout (%s)"
-msgstr "không thể đặt chế độ nhị phân trên thiết bị xuất chuẩn (%s)"
+msgstr "không thể đặt chế độ nhị phân trên đầu ra tiêu chuẩn (%s)"
 
-#: main.c:635
+#: main.c:652
 #, c-format
 msgid "can't set binary mode on stderr (%s)"
-msgstr "không thể đặt chế độ nhị phân trên thiết bị lỗi chuẩn (%s)"
+msgstr "không thể đặt chế độ nhị phân trên đầu ra lỗi tiêu chuẩn (%s)"
 
-#: main.c:693
+#: main.c:710
 msgid "no program text at all!"
-msgstr "không có đoạn chữ chương trình nào cả !"
+msgstr "không có đoạn chữ chương trình nào cả!"
 
-#: main.c:779
+#: main.c:799
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] -f progfile [--] file ...\n"
 msgstr ""
 "Cách dùng: %s [tùy chọn kiểu POSIX hay GNU] -f tập_tin_chương_trình [--] "
 "tập_tin ...\n"
 
-#: main.c:781
+#: main.c:801
 #, c-format
 msgid "Usage: %s [POSIX or GNU style options] [--] %cprogram%c file ...\n"
 msgstr ""
 "Cách dùng: %s [tùy chọn kiểu POSIX hay GNU] [--] %cchương_trình%c "
 "tập_tin ...\n"
 
-#: main.c:786
+#: main.c:806
 msgid "POSIX options:\t\tGNU long options: (standard)\n"
-msgstr "Tùy chọn POSIX:\t\tTùy chọn dài GNU: (tiêu chuẩn)\n"
+msgstr "Tùy chọn POSIX:\t\t\tTùy chọn dài GNU: (tiêu chuẩn)\n"
 
-#: main.c:787
+#: main.c:807
 msgid "\t-f progfile\t\t--file=progfile\n"
-msgstr "\t-f tập_tin_chương_trình\t\t--file=tập_tin_chương_trình\n"
+msgstr "\t-f tập_tin_chương_trình\t--file=tập_tin_chương_trình\n"
 
-#: main.c:788
+#: main.c:808
 msgid "\t-F fs\t\t\t--field-separator=fs\n"
-msgstr "\t-F fs\t\t\t--field-separator=ký hiệu phân cách trường\n"
+msgstr "\t-F fs\t\t\t--field-separator=ký_hiệu_phân_cách_trường\n"
 
-#: main.c:789
+#: main.c:809
 msgid "\t-v var=val\t\t--assign=var=val\n"
 msgstr ""
-"\t-v var=giá trị\t\t--assign=biến=giá_trị\n"
+"\t-v var=giá_trị\t\t--assign=biến=giá_trị\n"
 "(assign: gán)\n"
 
-#: main.c:790
+#: main.c:810
 msgid "Short options:\t\tGNU long options: (extensions)\n"
-msgstr "Tuỳ chọn ngắn:\t\tTuỳ chọn GNU dạng dài: (mở rộng)\n"
+msgstr "Tuỳ chọn ngắn:\t\t\tTuỳ chọn GNU dạng dài: (mở rộng)\n"
 
-#: main.c:791
+#: main.c:811
 msgid "\t-b\t\t\t--characters-as-bytes\n"
 msgstr "\t-b\t\t\t--characters-as-bytes\n"
 
-#: main.c:792
+#: main.c:812
 msgid "\t-c\t\t\t--traditional\n"
 msgstr "\t-c\t\t\t--traditional\n"
 
-#: main.c:793
+#: main.c:813
 msgid "\t-C\t\t\t--copyright\n"
 msgstr "\t-C\t\t\t--copyright\n"
 
-#: main.c:794
+#: main.c:814
 msgid "\t-d[file]\t\t--dump-variables[=file]\n"
-msgstr "\t-d[tệp_tin]\t\t--dump-variables[=tệp_tin]\n"
+msgstr "\t-d[tập_tin]\t\t--dump-variables[=tập_tin]\n"
 
-#: main.c:795
+#: main.c:815
 msgid "\t-D[file]\t\t--debug[=file]\n"
 msgstr "\t-D[tập_tin]\t\t--debug[=tập_tin]\n"
 
-#: main.c:796
+#: main.c:816
 msgid "\t-e 'program-text'\t--source='program-text'\n"
-msgstr "\t-e “program-text”\t--source=”program-text”\n"
+msgstr "\t-e “program-text”\t--source=“program-text”\n"
 
-#: main.c:797
+#: main.c:817
 msgid "\t-E file\t\t\t--exec=file\n"
-msgstr "\t-E file\t\t\t--exec=tệp_tin\n"
+msgstr "\t-E file\t\t\t--exec=tập_tin\n"
 
-#: main.c:798
+#: main.c:818
 msgid "\t-g\t\t\t--gen-pot\n"
 msgstr "\t-g\t\t\t--gen-pot\n"
 
-#: main.c:799
+#: main.c:819
 msgid "\t-h\t\t\t--help\n"
 msgstr "\t-h\t\t\t--help\n"
 
-#: main.c:800
+#: main.c:820
 msgid "\t-i includefile\t\t--include=includefile\n"
 msgstr "\t-i includefile\t\t--include=tập-tin-bao-gồm\n"
 
-#: main.c:801
+#: main.c:821
 msgid "\t-l library\t\t--load=library\n"
 msgstr "\t-l library\t\t--load=thư-viện\n"
 
-#: main.c:802
+#: main.c:822
 msgid "\t-L [fatal]\t\t--lint[=fatal]\n"
 msgstr "\t-L [fatal]\t\t--lint[=fatal]\n"
 
-#: main.c:803
+#: main.c:823
 msgid "\t-n\t\t\t--non-decimal-data\n"
 msgstr "\t-n\t\t\t--non-decimal-data\n"
 
-#: main.c:804
+#: main.c:824
 msgid "\t-M\t\t\t--bignum\n"
 msgstr "\t-M\t\t\t--bignum\n"
 
-#: main.c:805
+#: main.c:825
 msgid "\t-N\t\t\t--use-lc-numeric\n"
 msgstr "\t-N\t\t\t--use-lc-numeric\n"
 
-#: main.c:806
+#: main.c:826
 msgid "\t-o[file]\t\t--pretty-print[=file]\n"
 msgstr "\t-o[tập_tin]\t\t--pretty-print[=tập_tin]\n"
 
-#: main.c:807
+#: main.c:827
 msgid "\t-O\t\t\t--optimize\n"
-msgstr "\t-O\t\t\t--optimize\ttối ưu hoá\n"
+msgstr "\t-O\t\t\t--optimize  (tạm dịch: tối_ưu_hoá)\n"
 
-#: main.c:808
+#: main.c:828
 msgid "\t-p[file]\t\t--profile[=file]\n"
-msgstr "\t-p[file]\t\t--profile[=file]\n"
+msgstr "\t-p[tập_tin]\t\t--profile[=tập_tin]\n"
 
-#: main.c:809
+#: main.c:829
 msgid "\t-P\t\t\t--posix\n"
 msgstr "\t-P\t\t\t--posix\n"
 
-#: main.c:810
+#: main.c:830
 msgid "\t-r\t\t\t--re-interval\n"
 msgstr "\t-r\t\t\t--re-interval\n"
 
-#: main.c:811
+#: main.c:831
 msgid "\t-S\t\t\t--sandbox\n"
 msgstr "\t-S\t\t\t--sandbox\n"
 
-#: main.c:812
+#: main.c:832
 msgid "\t-t\t\t\t--lint-old\n"
 msgstr "\t-t\t\t\t--lint-old\n"
 
-#: main.c:813
+#: main.c:833
 msgid "\t-V\t\t\t--version\n"
 msgstr "\t-V\t\t\t--version\n"
 
-#: main.c:815
+#: main.c:835
 msgid "\t-W nostalgia\t\t--nostalgia\n"
 msgstr ""
 "\t-W nostalgia\t\t--nostalgia\n"
 "(nỗi luyến tiếc quá khứ)\n"
 
-#: main.c:818
+#: main.c:838
 msgid "\t-Y\t\t--parsedebug\n"
 msgstr "\t-Y\t\t--parsedebug\n"
 
@@ -3126,7 +3151,7 @@ msgstr "\t-Y\t\t--parsedebug\n"
 #. for this application.  Please add _another line_ with the
 #. address for translation bugs.
 #. no-wrap
-#: main.c:827
+#: main.c:847
 msgid ""
 "\n"
 "To report bugs, see node `Bugs' in `gawk.info', which is\n"
@@ -3135,32 +3160,33 @@ msgid ""
 msgstr ""
 "\n"
 "Để thông báo lỗi, xem nút “Bugs” (lỗi) trong tập tin\n"
-"thông tin “gawk.info” mà nằm trong phần\n"
-"“Reporting Problems and Bugs” (thông báo vấn đề và lỗi)\n"
+"thông tin “gawk.info”, cái mà nằm trong phần\n"
+"“Reporting Problems and Bugs” (thông báo trục trặc và lỗi)\n"
 "trong bản in.\n"
+"Thông báo lỗi dịch cho: <http://translationproject.org/team/vi.html>.\n"
 "\n"
 
-#: main.c:831
+#: main.c:851
 msgid ""
 "gawk is a pattern scanning and processing language.\n"
 "By default it reads standard input and writes standard output.\n"
 "\n"
 msgstr ""
 "gawk là ngôn ngữ quét và xử lý mẫu.\n"
-"Mặc định là nó đọc thiết bị nhập chuẩn và ghi ra thiết bị xuất chuẩn.\n"
+"Mặc định, nó đọc từ đầu vào tiêu chuẩn và ghi ra đầu ra tiêu chuẩn.\n"
 "\n"
 
-#: main.c:835
+#: main.c:855
 msgid ""
 "Examples:\n"
 "\tgawk '{ sum += $1 }; END { print sum }' file\n"
 "\tgawk -F: '{ print $1 }' /etc/passwd\n"
 msgstr ""
-"Ví dụ :\n"
-"\tgawk “{ sum += $1 }; END { print sum }” file\n"
-"\tgawk -F: “{ print $1 }” /etc/passwd\n"
+"Ví dụ:\n"
+"\tgawk \"{ sum += $1 }; END { print sum }\" file\n"
+"\tgawk -F: \"{ print $1 }\" /etc/passwd\n"
 
-#: main.c:855
+#: main.c:880
 #, c-format
 msgid ""
 "Copyright (C) 1989, 1991-%d Free Software Foundation.\n"
@@ -3173,13 +3199,13 @@ msgid ""
 msgstr ""
 "Tác quyền © năm 1989, 1991-%d của Tổ chức Phần mềm Tự do.\n"
 "\n"
-"Chương trình này là phần mềm tự do; bạn có thể phát hành lại nó và/hoặc sửa "
-"đổi nó với điều kiện của Giấy Phép Công Cộng GNU như được xuất bản bởi Tổ "
-"Chức Phần Mềm Tự Do; hoặc phiên bản 3 của Giấy Phép này, hoặc (tùy chọn) bất "
-"kỳ phiên bản sau nào.\n"
+"Chương trình này là phần mềm tự do; bạn có thể phát hành lại nó\n"
+"và/hoặc sửa đổi nó với các điều điều khoản của Giấy Phép Công Cộng GNU\n"
+"được xuất bản bởi Tổ Chức Phần Mềm Tự Do; hoặc là phiên bản 3\n"
+"của Giấy Phép này, hoặc là (tùy chọn) bất kỳ phiên bản mới hơn.\n"
 "\n"
 
-#: main.c:863
+#: main.c:888
 msgid ""
 "This program is distributed in the hope that it will be useful,\n"
 "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
@@ -3188,79 +3214,79 @@ msgid ""
 "\n"
 msgstr ""
 "Chúng tôi phân phối chương trình này vì mong muốn nó hữu ích,\n"
-"nhưng mà KHÔNG BẢO ĐẢM GÌ CẢ, không ngay cả ngụ ý bảo đảm\n"
-"KHẢ NĂNG BÁN hoặc KHẢ NĂNG LÀM VIỆC DỨT KHOÁT.\n"
-"Hãy xem Bản Quyền Công Chung GNU (GPL) để tìm chi tiết.\n"
+"nhưng mà KHÔNG BẢO ĐẢM GÌ CẢ, không ngay cả khi nó ĐƯỢC BÁN\n"
+"hoặc PHÙ HỢP VỚI CÁC MỤC ĐÍCH ĐẶC THÙ.\n"
+"Hãy xem Giấy phép Công Chung GNU (GPL) để biết chi tiết.\n"
 "\n"
 
-#: main.c:869
+#: main.c:894
 msgid ""
 "You should have received a copy of the GNU General Public License\n"
 "along with this program. If not, see http://www.gnu.org/licenses/.\n"
 msgstr ""
 "Bạn nên nhận một bản sao của Giấy Phép Công Cộng GNU cùng với chương\n"
-"trình này. Nếu chưa có, bạn lấy về từ “http://www.gnu.org/licenses/”.\n"
+"trình này. Nếu chưa có, bạn xem tại <http://www.gnu.org/licenses/>.\n"
 
-#: main.c:904
+#: main.c:931
 msgid "-Ft does not set FS to tab in POSIX awk"
 msgstr "-Ft không đặt FS (hệ thống tập tin?) vào tab trong awk POSIX"
 
-#: main.c:1181
+#: main.c:1208
 #, c-format
 msgid "unknown value for field spec: %d\n"
-msgstr "không hiểu giá trị dành cho đặc tính trường: %d\n"
+msgstr "không hiểu giá trị dành cho đặc tả trường: %d\n"
 
-#: main.c:1279
+#: main.c:1306
 #, c-format
 msgid ""
 "%s: `%s' argument to `-v' not in `var=value' form\n"
 "\n"
 msgstr ""
-"%s: đối số “%s” đối với “-v” không có dạng “biến=giá_trị”\n"
+"%s: đối số “%s” cho “-v” không có dạng “biến=giá_trị”\n"
 "\n"
 
-#: main.c:1305
+#: main.c:1332
 #, c-format
 msgid "`%s' is not a legal variable name"
 msgstr "“%s” không phải là tên biến hợp lệ"
 
-#: main.c:1308
+#: main.c:1335
 #, c-format
 msgid "`%s' is not a variable name, looking for file `%s=%s'"
 msgstr "“%s” không phải là tên biến; đang tìm tập tin “%s=%s”"
 
-#: main.c:1312
+#: main.c:1339
 #, c-format
 msgid "cannot use gawk builtin `%s' as variable name"
 msgstr "không thể dùng builtin (dựng sẵn) của gawk “%s” như là tên biến"
 
-#: main.c:1317
+#: main.c:1344
 #, c-format
 msgid "cannot use function `%s' as variable name"
 msgstr "không thể dùng hàm “%s” như là tên biến"
 
-#: main.c:1370
+#: main.c:1397
 msgid "floating point exception"
-msgstr "ngoại lệ điểm phù động"
+msgstr "ngoại lệ số thực dấu chấm động"
 
-#: main.c:1377
+#: main.c:1404
 msgid "fatal error: internal error"
 msgstr "lỗi nghiêm trọng: lỗi nội bộ"
 
-#: main.c:1392
+#: main.c:1419
 msgid "fatal error: internal error: segfault"
-msgstr "lỗi nghiêm trọng: lỗi nội bộ : lỗi chia ra từng đoạn"
+msgstr "lỗi nghiêm trọng: lỗi nội bộ: lỗi phân đoạn"
 
-#: main.c:1404
+#: main.c:1431
 msgid "fatal error: internal error: stack overflow"
-msgstr "lỗi nghiêm trọng: lỗi nội bộ : tràn đống"
+msgstr "lỗi nghiêm trọng: lỗi nội bộ: tràn ngăn xếp"
 
-#: main.c:1463
+#: main.c:1490
 #, c-format
 msgid "no pre-opened fd %d"
 msgstr "không có fd (bộ mô tả tập tin) %d đã mở trước"
 
-#: main.c:1470
+#: main.c:1497
 #, c-format
 msgid "could not pre-open /dev/null for fd %d"
 msgstr "không thể mở trước “/dev/null” cho fd %d"
@@ -3315,19 +3341,19 @@ msgstr "%s: đối số #%d giá trị phần phân số %Rg sẽ bị cắt c�
 msgid "%s: argument #%d negative value %Zd will give strange results"
 msgstr "%s: đối số #%d có giá trị âm %Zd sẽ đưa ra kết quả không như mong muốn"
 
-#: msg.c:61
+#: msg.c:68
 #, c-format
 msgid "cmd. line:"
 msgstr "dòng lệnh:"
 
 #: node.c:421
 msgid "backslash at end of string"
-msgstr "gặp xuyệc ngoặc tại kết thúc của chuỗi"
+msgstr "gặp dấu gạch ngược tại kết thúc của chuỗi"
 
 #: node.c:500
 #, c-format
 msgid "old awk does not support the `\\%c' escape sequence"
-msgstr "awk cũ không hỗ trợ dãy thoát “\\%c”"
+msgstr "awk cũ không hỗ trợ thoát chuỗi  “\\%c”"
 
 #: node.c:551
 msgid "POSIX does not allow `\\x' escapes"
@@ -3335,7 +3361,7 @@ msgstr "POSIX không cho phép thoát chuỗi “\\x”"
 
 #: node.c:557
 msgid "no hex digits in `\\x' escape sequence"
-msgstr "không có số thập lúc nằm trong dây thoát “\\x”"
+msgstr "không có số thập lúc nằm trong thoát chuỗi “\\x”"
 
 #: node.c:579
 #, c-format
@@ -3343,13 +3369,13 @@ msgid ""
 "hex escape \\x%.*s of %d characters probably not interpreted the way you "
 "expect"
 msgstr ""
-"dây thoát thập lục \\x%.*s chứa %d ký tự mà rất có thể không phải được đọc "
+"thoát chuỗi thập lục \\x%.*s chứa %d ký tự mà rất có thể không phải được đọc "
 "bằng cách dự định"
 
 #: node.c:594
 #, c-format
 msgid "escape sequence `\\%c' treated as plain `%c'"
-msgstr "dây thoát “\\%c” được xử lý như là “%c” chuẩn"
+msgstr "thoát chuỗi “\\%c” được xử lý như là “%c” chuẩn"
 
 #: node.c:739
 msgid ""
@@ -3371,16 +3397,16 @@ msgstr ""
 "%s %s “%s”: không thể đặt “close-on-exec” (đóng một khi thực hiện): (fcntl "
 "F_SETFD: %s)"
 
-#: profile.c:70
+#: profile.c:71
 #, c-format
 msgid "could not open `%s' for writing: %s"
 msgstr "không thể mở “%s” để ghi: %s"
 
-#: profile.c:72
+#: profile.c:73
 msgid "sending profile to standard error"
 msgstr "đang gởi hồ sơ cho thiết bị lỗi chuẩn"
 
-#: profile.c:188
+#: profile.c:193
 #, c-format
 msgid ""
 "\t# %s block(s)\n"
@@ -3389,7 +3415,7 @@ msgstr ""
 "\t# %s khối\n"
 "\n"
 
-#: profile.c:193
+#: profile.c:198
 #, c-format
 msgid ""
 "\t# Rule(s)\n"
@@ -3398,16 +3424,16 @@ msgstr ""
 "\t# Quy tắc\n"
 "\n"
 
-#: profile.c:267
+#: profile.c:272
 #, c-format
 msgid "internal error: %s with null vname"
 msgstr "lỗi nội bộ: %s với vname (tên biến?) vô giá trị"
 
-#: profile.c:530
+#: profile.c:537
 msgid "internal error: builtin with null fname"
 msgstr "lỗi nội bộ: phần dựng sẵn với fname là null"
 
-#: profile.c:942
+#: profile.c:949
 #, c-format
 msgid ""
 "\t# Loaded extensions (-l and/or @load)\n"
@@ -3416,12 +3442,12 @@ msgstr ""
 "\t# Các phần mở rộng được tải (-l và/hoặc @load)\n"
 "\n"
 
-#: profile.c:965
+#: profile.c:972
 #, c-format
 msgid "\t# gawk profile, created %s\n"
 msgstr "\t# hồ sơ gawk, được tạo %s\n"
 
-#: profile.c:1351
+#: profile.c:1475
 #, c-format
 msgid ""
 "\n"
@@ -3430,21 +3456,16 @@ msgstr ""
 "\n"
 "\t# Danh sách các hàm theo thứ tự abc\n"
 
-#: profile.c:1389
+#: profile.c:1513
 #, c-format
 msgid "redir2str: unknown redirection type %d"
 msgstr "redir2str: không hiểu kiểu chuyển hướng %d"
 
-#: re.c:583
-#, c-format
-msgid "range of the form `[%c-%c]' is locale dependent"
-msgstr "vùng của dạng thức “[%c-%c]” phụ thuộc vào vị trí"
-
-#: re.c:610
+#: re.c:607
 #, c-format
 msgid "regexp component `%.*s' should probably be `[%.*s]'"
 msgstr ""
-"thành phần của biểu thức chính qui (regexp) “%.*s” hầu như chắc chắn nên là "
+"thành phần của biểu thức chính qui (regexp) “%.*s” gần như chắc chắn nên là "
 "“[%.*s]”"
 
 #: regcomp.c:131
@@ -3469,11 +3490,11 @@ msgstr "Tên hạng ký tự không hợp lệ"
 
 #: regcomp.c:146
 msgid "Trailing backslash"
-msgstr "Gặp xuyệc ngược nằm theo"
+msgstr "Gặp dấu gạch ngược thừa"
 
 #: regcomp.c:149
 msgid "Invalid back reference"
-msgstr "Tham chiếu trở lại không hợp lệ"
+msgstr "Tham chiếu ngược không hợp lệ"
 
 #: regcomp.c:152
 msgid "Unmatched [ or [^"
@@ -3493,7 +3514,7 @@ msgstr "Kết thúc phạm vi không hợp lệ"
 
 #: regcomp.c:167
 msgid "Memory exhausted"
-msgstr "Hết bộ nhớ rồi"
+msgstr "Hết bộ nhớ"
 
 #: regcomp.c:170
 msgid "Invalid preceding regular expression"
@@ -3505,21 +3526,24 @@ msgstr "Kết thúc quá sớm của biểu thức chính quy"
 
 #: regcomp.c:179
 msgid "Unmatched ) or \\)"
-msgstr "Chưa khớp “)” hay “\\)”"
+msgstr "Chưa khớp “)” hoặc “\\)”"
 
 #: regcomp.c:704
 msgid "No previous regular expression"
 msgstr "Không có biểu thức chính quy nằm trước"
 
-#: symbol.c:740
+#: symbol.c:741
 msgid "can not pop main context"
-msgstr "không thể pop ngữ cảnh chính"
+msgstr "không thể pop (lấy ra) ngữ cảnh chính"
+
+#~ msgid "range of the form `[%c-%c]' is locale dependent"
+#~ msgstr "vùng của dạng thức “[%c-%c]” phụ thuộc vào vị trí"
 
 #~ msgid "attempt to use function `%s' as an array"
 #~ msgstr "cố gắng dùng hàm “%s” như mảng"
 
 #~ msgid "reference to uninitialized element `%s[\"%.*s\"]'"
-#~ msgstr "tham chiếu đến phần tử chưa sở khởi “%s[”%.*s”]”"
+#~ msgstr "tham chiếu đến phần tử chưa khởi tạo “%s[”%.*s”]”"
 
 #~ msgid "subscript of array `%s' is null string"
 #~ msgstr "chữ in dưới mảng “%s” là chuỗi rỗng"
@@ -3594,4 +3618,4 @@ msgstr "không thể pop ngữ cảnh chính"
 #~ msgstr "hàm được gọi gián tiếp thông qua “%s” không tồn tại"
 
 #~ msgid "function `%s' not defined"
-#~ msgstr "chưa xác định hàm “%s”"
+#~ msgstr "chưa định nghĩa hàm “%s”"
diff --git a/posix/ChangeLog b/posix/ChangeLog
index 9eb72ff4..b93b891f 100644
--- a/posix/ChangeLog
+++ b/posix/ChangeLog
@@ -1,3 +1,7 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
 2013-06-03         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* gawkmisc.c (init_sockets): Remove ifdefs.
diff --git a/regcomp.c b/regcomp.c
index f3c4587d..a62364c9 100644
--- a/regcomp.c
+++ b/regcomp.c
@@ -2476,14 +2476,22 @@ parse_expression (re_string_t *regexp, regex_t *preg, re_token_t *token,
   while (token->type == OP_DUP_ASTERISK || token->type == OP_DUP_PLUS
 	 || token->type == OP_DUP_QUESTION || token->type == OP_OPEN_DUP_NUM)
     {
-      tree = parse_dup_op (tree, regexp, dfa, token, syntax, err);
-      if (BE (*err != REG_NOERROR && tree == NULL, 0))
-	return NULL;
+      bin_tree_t *dup_tree = parse_dup_op (tree, regexp, dfa, token,
+					   syntax, err);
+      if (BE (*err != REG_NOERROR && dup_tree == NULL, 0))
+	{
+	  if (tree != NULL)
+	    postorder (tree, free_tree, NULL);
+	  return NULL;
+	}
+      tree = dup_tree;
       /* In BRE consecutive duplications are not allowed.  */
       if ((syntax & RE_CONTEXT_INVALID_DUP)
 	  && (token->type == OP_DUP_ASTERISK
 	      || token->type == OP_OPEN_DUP_NUM))
 	{
+	  if (tree != NULL)
+	    postorder (tree, free_tree, NULL);
 	  *err = REG_BADRPT;
 	  return NULL;
 	}
@@ -3128,8 +3136,8 @@ parse_bracket_exp (re_string_t *regexp, re_dfa_t *dfa, re_token_t *token,
   if (BE (sbcset == NULL, 0))
 #endif /* RE_ENABLE_I18N */
     {
-      re_free (sbcset);
 #ifdef RE_ENABLE_I18N
+      re_free (sbcset);
       re_free (mbcset);
 #endif
       *err = REG_ESPACE;
diff --git a/regex.c b/regex.c
index 167d35b2..f56e8692 100644
--- a/regex.c
+++ b/regex.c
@@ -1,5 +1,5 @@
 /* Extended regular expression matching and search library.
-   Copyright (C) 2002-2013 Free Software Foundation, Inc.
+   Copyright (C) 2002-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
    Contributed by Isamu Hasegawa <isamu@yamato.ibm.com>.
 
diff --git a/regex.h b/regex.h
index c72079b2..56602961 100644
--- a/regex.h
+++ b/regex.h
@@ -1,6 +1,6 @@
 /* Definitions for data structures and routines for the regular
    expression library.
-   Copyright (C) 1985, 1989-2013 Free Software Foundation, Inc.
+   Copyright (C) 1985, 1989-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
 
    The GNU C Library is free software; you can redistribute it and/or
@@ -539,7 +539,7 @@ extern void re_set_registers (struct re_pattern_buffer *__buffer,
 			      regoff_t *__starts, regoff_t *__ends);
 #endif	/* Use GNU */
 
-#if defined _REGEX_RE_COMP || (defined _LIBC && defined __USE_BSD)
+#if defined _REGEX_RE_COMP || (defined _LIBC && defined __USE_MISC)
 # ifndef _CRAY
 /* 4.2 bsd compatibility.  */
 extern char *re_comp (const char *);
diff --git a/regex_internal.c b/regex_internal.c
index c7de18b6..056cff3d 100644
--- a/regex_internal.c
+++ b/regex_internal.c
@@ -1,5 +1,5 @@
 /* Extended regular expression matching and search library.
-   Copyright (C) 2002-2013 Free Software Foundation, Inc.
+   Copyright (C) 2002-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
    Contributed by Isamu Hasegawa <isamu@yamato.ibm.com>.
 
@@ -320,12 +320,11 @@ build_wcs_upper_buffer (re_string_t *pstr)
 			       + byte_idx), remain_len, &pstr->cur_state);
 	  if (BE (mbclen + 2 > 2, 1))
 	    {
-	      wchar_t wcu = wc;
-	      if (iswlower (wc))
+	      wchar_t wcu = towupper (wc);
+	      if (wcu != wc)
 		{
 		  size_t mbcdlen;
 
-		  wcu = towupper (wc);
 		  mbcdlen = wcrtomb (buf, wcu, &prev_st);
 		  if (BE (mbclen == mbcdlen, 1))
 		    memcpy (pstr->mbs + byte_idx, buf, mbclen);
@@ -390,12 +389,11 @@ build_wcs_upper_buffer (re_string_t *pstr)
 	mbclen = __mbrtowc (&wc, p, remain_len, &pstr->cur_state);
 	if (BE (mbclen + 2 > 2, 1))
 	  {
-	    wchar_t wcu = wc;
-	    if (iswlower (wc))
+	    wchar_t wcu = towupper (wc);
+	    if (wcu != wc)
 	      {
 		size_t mbcdlen;
 
-		wcu = towupper (wc);
 		mbcdlen = wcrtomb ((char *) buf, wcu, &prev_st);
 		if (BE (mbclen == mbcdlen, 1))
 		  memcpy (pstr->mbs + byte_idx, buf, mbclen);
@@ -547,10 +545,7 @@ build_upper_buffer (re_string_t *pstr)
       int ch = pstr->raw_mbs[pstr->raw_mbs_idx + char_idx];
       if (BE (pstr->trans != NULL, 0))
 	ch = pstr->trans[ch];
-      if (islower (ch))
-	pstr->mbs[char_idx] = toupper (ch);
-      else
-	pstr->mbs[char_idx] = ch;
+      pstr->mbs[char_idx] = toupper (ch);
     }
   pstr->valid_len = char_idx;
   pstr->valid_raw_len = char_idx;
diff --git a/regex_internal.h b/regex_internal.h
index 448e32ea..c8981a08 100644
--- a/regex_internal.h
+++ b/regex_internal.h
@@ -1,5 +1,5 @@
 /* Extended regular expression matching and search library.
-   Copyright (C) 2002-2013 Free Software Foundation, Inc.
+   Copyright (C) 2002-2014 Free Software Foundation, Inc.
    This file is part of the GNU C Library.
    Contributed by Isamu Hasegawa <isamu@yamato.ibm.com>.
 
diff --git a/symbol.c b/symbol.c
index fe297d22..7ecdfe85 100644
--- a/symbol.c
+++ b/symbol.c
@@ -508,7 +508,7 @@ append_symbol(NODE *r)
 	symbol_list->rnode = p;
 }
 
-/* release_symbol --- free symbol list and optionally remove symbol from symbol table */
+/* release_symbols --- free symbol list and optionally remove symbol from symbol table */
 
 void
 release_symbols(NODE *symlist, int keep_globals)
diff --git a/test/ChangeLog b/test/ChangeLog
index 33c5ca05..a337603b 100644
--- a/test/ChangeLog
+++ b/test/ChangeLog
@@ -1,3 +1,122 @@
+2014-06-19         Michael Forney       <forney@google.com>
+
+	* Makefile.am (poundbang): Fix relative path of AWKPROG.
+
+2014-06-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (dbugeval): Add leading @ to recipe. Ooops.
+
+2014-05-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (regnul1, regnul2): New tests.
+	* regnul1.awk, regnul1.ok, regnul1.awk, regnul2.ok: New files.
+
+2014-05-22         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* lintwarn.ok: Updated.
+
+2014-05-13         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (EXTRA_DIST): Forgot dbugeval.ok. Ooops.
+
+2014-05-11         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (dbugeval): New test.
+	* dbugeval.in, dbugeval.ok: New files.
+
+2014-05-10         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* Makefile.am (rsglstdin): New test.
+	* rsglstdin.ok: New file.
+
+2014-05-09         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* Makefile.am (rebuf): Force buffer size to 4096 via AWKBUFSIZE
+	environment variable.
+	(rsgetline): New test.
+	* rsgetline.awk, rsgetline.in, rsgetline.ok: New files.
+
+2014-04-11         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (charset-msg-start): Add a warning message that tests
+	may fail without adequate locale support, per request from
+	Nelson H.F. Beebe.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-04-04         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am: Prettify list of tests a little bit.
+
+2014-04-03         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (EXTRA_DIST): Add readfile2.ok. Oops.
+
+2014-03-27         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (readfile2): New test.
+	* readfile2.awk, readfile2.ok: New files.
+
+2014-02-28         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* regrange.ok: Update after code improvements.
+
+2014-02-03         Stepan Kasal         <kasal@ucw.cz>
+
+	* strftime.awk: the default format uses %e, not %d (Introduced on
+	2014-01-16; the previous code mangled the output of command "date"
+	to match %d.) Remove the "mucking" for cygwin, it's obsolete and
+	incompatible with %e.
+
+2014-01-28         Eli Zaretskii        <eliz@gnu.org>
+
+	* strftime.awk: If DATECMD variable is non-empty, use it instead
+	of the literal "date" as the 'date'-like command.
+
+2014-01-19         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (mpfrnegzero): New test.
+	* mpfrnegzero.awk, mpfrnegzero.ok: New files.
+
+2014-01-17         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (readdir): Run ls commands outside the awk script.
+	* readdir0.awk: Read ls results from files. Helps with MinGW.
+	Thanks to Eli Zaretskii for the problem report.
+
+2014-01-17         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am: Quote instances of $(top_srcdir) also.
+
+2014-01-16         Andrew J. Schorr     <aschorr@telemetry-investments.com>
+
+	* Makefile.am (strftime): Remove comment about the race condition, since
+	this should be fixed.  And gawk now calls date inside the script.
+	* strftime.awk: Based on an idea from Pat Rankin, fix the race
+	condition by looping repeatedly over strftime/date/strftime until
+	the before and after strftime results match.  That should fix
+	the race condition where the seconds field might increment between
+	invocations.
+
+2014-01-14         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (split_after_fpat): New test.
+	* split_after_fpat.awk, split_after_fpat.ok,
+	split_after_fpat.in: New files.
+
+2013-12-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* Makefile.am (ignrcas2): Change to use en_US.UTF-8; it
+	seems that plain en_US doesn't exist anymore. Thanks to
+	Richard Palo.
+
+2013-12-29         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* fts.awk: Adjust for VMS.
+	* rwarray.awk: Adjust for VMS.
+
 2013-12-10         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* Makefile.am: Remove instances of "" that were incorrect.
diff --git a/test/Makefile.am b/test/Makefile.am
index 13c9b977..13069084 100644
--- a/test/Makefile.am
+++ b/test/Makefile.am
@@ -1,7 +1,7 @@
 #
 # test/Makefile.am --- automake input file for gawk
 #
-# Copyright (C) 1988-2012 the Free Software Foundation, Inc.
+# Copyright (C) 1988-2014 the Free Software Foundation, Inc.
 #
 # This file is part of GAWK, the GNU implementation of the
 # AWK Programming Language.
@@ -167,6 +167,8 @@ EXTRA_DIST = \
 	datanonl.awk \
 	datanonl.in \
 	datanonl.ok \
+	dbugeval.in \
+	dbugeval.ok \
 	defref.awk \
 	defref.ok \
 	delargv.awk \
@@ -522,6 +524,8 @@ EXTRA_DIST = \
 	mpfrexprange.ok \
 	mpfrieee.awk \
 	mpfrieee.ok \
+	mpfrnegzero.awk \
+	mpfrnegzero.ok \
 	mpfrnr.awk \
 	mpfrnr.in \
 	mpfrnr.ok \
@@ -708,6 +712,8 @@ EXTRA_DIST = \
 	range1.ok \
 	readdir.awk \
 	readdir0.awk \
+	readfile2.awk \
+	readfile2.ok \
 	rebt8b1.awk \
 	rebt8b1.ok \
 	rebt8b2.awk \
@@ -725,6 +731,10 @@ EXTRA_DIST = \
 	regexprange.ok \
 	reginttrad.awk \
 	reginttrad.ok \
+	regnul1.awk \
+	regnul1.ok \
+	regnul2.awk \
+	regnul2.ok \
 	regrange.awk \
 	regrange.ok \
 	regtest.sh \
@@ -755,6 +765,10 @@ EXTRA_DIST = \
 	rs.awk \
 	rs.in \
 	rs.ok \
+	rsgetline.awk \
+	rsgetline.in \
+	rsgetline.ok \
+	rsglstdin.ok \
 	rsnul1nl.awk \
 	rsnul1nl.in \
 	rsnul1nl.ok \
@@ -808,6 +822,9 @@ EXTRA_DIST = \
 	sortu.awk \
 	sortu.ok \
 	space.ok \
+	split_after_fpat.awk \
+	split_after_fpat.in \
+	split_after_fpat.ok \
 	splitarg4.awk \
 	splitarg4.in \
 	splitarg4.ok \
@@ -942,8 +959,7 @@ BASIC_TESTS = \
 	arrayref arrymem1 arryref2 arryref3 arryref4 arryref5 arynasty \
 	arynocls aryprm1 aryprm2 aryprm3 aryprm4 aryprm5 aryprm6 aryprm7 \
 	aryprm8 arysubnm asgext awkpath \
-	back89 backgsub \
-	badassign1 \
+	back89 backgsub badassign1 \
 	childin clobber closebad clsflnam compare compare2 concat1 concat2 \
 	concat3 concat4 convfmt \
 	datanonl defref delargv delarpm2 delarprm delfunc dfamb1 dfastress dynlj \
@@ -982,7 +998,7 @@ UNIX_TESTS = \
 GAWK_EXT_TESTS = \
 	aadelete1 aadelete2 aarray1 aasort aasorti argtest arraysort \
 	backw badargs beginfile1 beginfile2 binmode1 charasbytes \
-	colonwarn clos1way delsub devfd devfd1 devfd2 dumpvars exit \
+	colonwarn clos1way dbugeval delsub devfd devfd1 devfd2 dumpvars exit \
 	fieldwdth fpat1 fpat2 fpat3  fpatnull fsfwfs funlen \
 	functab1 functab2 functab3 fwtest fwtest2 fwtest3 \
 	gensub gensub2 getlndir gnuops2 gnuops3 gnureops \
@@ -994,8 +1010,9 @@ GAWK_EXT_TESTS = \
 	nastyparm next nondec nondec2 \
 	patsplit posix printfbad1 printfbad2 printfbad3 procinfs \
 	profile1 profile2 profile3 profile4 profile5 pty1 \
-	rebuf regx8bit reginttrad reint reint2 rsstart1 \
-	rsstart2 rsstart3 rstest6 shadow sortfor sortu splitarg4 strftime \
+	rebuf regnul1 regnul2 regx8bit reginttrad reint reint2 rsgetline rsglstdin rsstart1 \
+	rsstart2 rsstart3 rstest6 shadow sortfor sortu split_after_fpat \
+	splitarg4 strftime \
 	strtonum switch2 symtab1 symtab2 symtab3 symtab4 symtab5 symtab6 \
 	symtab7 symtab8 symtab9
 
@@ -1005,7 +1022,8 @@ INET_TESTS = inetdayu inetdayt inetechu inetecht
 
 MACHINE_TESTS = double1 double2 fmtspcl intformat
 
-MPFR_TESTS = mpfrnr mpfrrnd mpfrieee mpfrexprange mpfrsort mpfrbigint
+MPFR_TESTS = mpfrnr mpfrnegzero mpfrrnd mpfrieee mpfrexprange \
+	mpfrsort mpfrbigint
 
 LOCALE_CHARSET_TESTS = \
 	asort asorti backbigs1 backsmalls1 backsmalls2 \
@@ -1014,7 +1032,7 @@ LOCALE_CHARSET_TESTS = \
 
 SHLIB_TESTS = \
 	fnmatch filefuncs fork fork2 fts functab4 inplace1 inplace2 inplace3 \
-	ordchr ordchr2 readdir readfile revout revtwoway rwarray testext time
+	ordchr ordchr2 readdir readfile readfile2 revout revtwoway rwarray testext time
 
 # List of the tests which should be run with --lint option:
 NEED_LINT = \
@@ -1137,6 +1155,10 @@ machine-msg-end:
 
 charset-msg-start:
 	@echo "======== Starting tests that can vary based on character set or locale support ========"
+	@echo "************************************************"
+	@echo "** Some or all of these tests may fail if you **"
+	@echo "** have inadequate or missing locale support  **"
+	@echo "************************************************"
 
 charset-msg-end:
 	@echo "======== Done with tests that can vary based on character set or locale support ========"
@@ -1173,7 +1195,7 @@ poundbang::
 	@if ./_pbd.awk "$(srcdir)"/poundbang.awk > _`basename $@` ; \
 	then : ; \
 	else \
-		sed "s;/tmp/gawk;../$(AWKPROG);" < "$(srcdir)"/poundbang.awk > ./_pbd.awk ; \
+		sed "s;/tmp/gawk;$(AWKPROG);" < "$(srcdir)"/poundbang.awk > ./_pbd.awk ; \
 		chmod +x ./_pbd.awk ; \
 		LC_ALL=$${GAWKLOCALE:-C} LANG=$${GAWKLOCALE:-C} ./_pbd.awk "$(srcdir)"/poundbang.awk > _`basename $@`;  \
 	fi
@@ -1250,12 +1272,10 @@ nonl::
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 strftime::
-	@echo This test could fail on slow machines or on a minute boundary,
-	@echo so if it does, double check the actual results:
 	@echo $@
 	@GAWKLOCALE=C; export GAWKLOCALE; \
 	TZ=GMT0; export TZ; \
-	(LC_ALL=C date) | $(AWK) -v OUTPUT=_$@ -f "$(srcdir)"/strftime.awk
+	$(AWK) -v OUTPUT=_$@ -f "$(srcdir)"/strftime.awk
 	@-$(CMP) strftime.ok _$@ && rm -f _$@ strftime.ok || exit 0
 
 litoct::
@@ -1319,6 +1339,16 @@ fmtspcl: fmtspcl.ok
 	$(CMP) "$(srcdir)"/$@-mpfr.ok _$@ && rm -f _$@ ; \
 	fi
 
+rebuf::
+	@echo $@
+	@AWKBUFSIZE=4096 AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
+rsglstdin:: 
+	@echo $@
+	@cat  "$(srcdir)"/rsgetline.in | AWKPATH="$(srcdir)" $(AWK) -f rsgetline.awk >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 reint::
 	@echo $@
 	@$(AWK) --re-interval -f "$(srcdir)"/reint.awk "$(srcdir)"/reint.in >_$@
@@ -1454,7 +1484,7 @@ widesub4::
 
 ignrcas2::
 	@echo $@
-	@GAWKLOCALE=en_US ; export GAWKLOCALE ; \
+	@GAWKLOCALE=en_US.UTF-8 ; export GAWKLOCALE ; \
 	$(AWK) -f "$(srcdir)"/$@.awk >_$@ 2>&1 || echo EXIT CODE: $$? >> _$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
@@ -1695,6 +1725,11 @@ mpfrrnd:
 	@$(AWK) -M -vPREC=53 -f "$(srcdir)"/$@.awk > _$@ 2>&1
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+mpfrnegzero:
+	@echo $@
+	@$(AWK) -M -f "$(srcdir)"/$@.awk > _$@ 2>&1
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 mpfrnr:
 	@echo $@
 	@$(AWK) -M -vPREC=113 -f "$(srcdir)"/$@.awk "$(srcdir)"/$@.in > _$@
@@ -1726,6 +1761,11 @@ readfile::
 	@$(AWK) -l readfile 'BEGIN {printf "%s", readfile("Makefile")}' >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) Makefile _$@ && rm -f _$@ || cp -p Makefile $@.ok
 
+readfile2::
+	@echo $@
+	@$(AWK) -f "$(srcdir)"/$@.awk "$(srcdir)"/$@.awk "$(srcdir)"/readdir.awk > _$@ || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 include2::
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) --include inclib 'BEGIN {print sandwich("a", "b", "c")}' >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
@@ -1800,7 +1840,7 @@ inplace3::
 
 testext::
 	@echo $@
-	@$(AWK) '/^(@load|BEGIN)/,/^}/' $(top_srcdir)/extension/testext.c > testext.awk
+	@$(AWK) '/^(@load|BEGIN)/,/^}/' "$(top_srcdir)"/extension/testext.c > testext.awk
 	@$(AWK) -f testext.awk >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@ testext.awk
 
@@ -1810,9 +1850,12 @@ readdir:
 	echo If it does, try rerunning on an ext'[234]' filesystem. ; \
 	fi
 	@echo $@
-	@$(AWK) -f "$(srcdir)"/readdir.awk $(top_srcdir) > _$@
-	@ls -afli $(top_srcdir) | sed 1d | $(AWK) -f "$(srcdir)"/readdir0.awk -v extout=_$@ $(top_srcdir) > $@.ok
-	@-$(CMP) $@.ok _$@ && rm -f $@.ok _$@
+	@$(AWK) -f "$(srcdir)"/readdir.awk "$(top_srcdir)" > _$@
+	@ls -afi "$(top_srcdir)" > _dirlist
+	@ls -lna "$(top_srcdir)" | sed 1d > _longlist
+	@$(AWK) -f "$(srcdir)"/readdir0.awk -v extout=_$@  \
+		-v dirlist=_dirlist -v longlist=_longlist > $@.ok
+	@-$(CMP) $@.ok _$@ && rm -f $@.ok _$@ _dirlist _longlist
 
 fts:
 	@case `uname` in \
@@ -1899,6 +1942,11 @@ backsmalls2:
 	AWKPATH="$(srcdir)" $(AWK) -f $@.awk "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+dbugeval::
+	@echo $@
+	@$(AWK) --debug -f /dev/null < "$(srcdir)"/$@.in > _$@  2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 # Targets generated for other tests:
 include Maketests
 
diff --git a/test/Makefile.in b/test/Makefile.in
index 17249a14..2632334b 100644
--- a/test/Makefile.in
+++ b/test/Makefile.in
@@ -17,7 +17,7 @@
 #
 # test/Makefile.am --- automake input file for gawk
 #
-# Copyright (C) 1988-2012 the Free Software Foundation, Inc.
+# Copyright (C) 1988-2014 the Free Software Foundation, Inc.
 #
 # This file is part of GAWK, the GNU implementation of the
 # AWK Programming Language.
@@ -413,6 +413,8 @@ EXTRA_DIST = \
 	datanonl.awk \
 	datanonl.in \
 	datanonl.ok \
+	dbugeval.in \
+	dbugeval.ok \
 	defref.awk \
 	defref.ok \
 	delargv.awk \
@@ -768,6 +770,8 @@ EXTRA_DIST = \
 	mpfrexprange.ok \
 	mpfrieee.awk \
 	mpfrieee.ok \
+	mpfrnegzero.awk \
+	mpfrnegzero.ok \
 	mpfrnr.awk \
 	mpfrnr.in \
 	mpfrnr.ok \
@@ -954,6 +958,8 @@ EXTRA_DIST = \
 	range1.ok \
 	readdir.awk \
 	readdir0.awk \
+	readfile2.awk \
+	readfile2.ok \
 	rebt8b1.awk \
 	rebt8b1.ok \
 	rebt8b2.awk \
@@ -971,6 +977,10 @@ EXTRA_DIST = \
 	regexprange.ok \
 	reginttrad.awk \
 	reginttrad.ok \
+	regnul1.awk \
+	regnul1.ok \
+	regnul2.awk \
+	regnul2.ok \
 	regrange.awk \
 	regrange.ok \
 	regtest.sh \
@@ -1001,6 +1011,10 @@ EXTRA_DIST = \
 	rs.awk \
 	rs.in \
 	rs.ok \
+	rsgetline.awk \
+	rsgetline.in \
+	rsgetline.ok \
+	rsglstdin.ok \
 	rsnul1nl.awk \
 	rsnul1nl.in \
 	rsnul1nl.ok \
@@ -1054,6 +1068,9 @@ EXTRA_DIST = \
 	sortu.awk \
 	sortu.ok \
 	space.ok \
+	split_after_fpat.awk \
+	split_after_fpat.in \
+	split_after_fpat.ok \
 	splitarg4.awk \
 	splitarg4.in \
 	splitarg4.ok \
@@ -1187,8 +1204,7 @@ BASIC_TESTS = \
 	arrayref arrymem1 arryref2 arryref3 arryref4 arryref5 arynasty \
 	arynocls aryprm1 aryprm2 aryprm3 aryprm4 aryprm5 aryprm6 aryprm7 \
 	aryprm8 arysubnm asgext awkpath \
-	back89 backgsub \
-	badassign1 \
+	back89 backgsub badassign1 \
 	childin clobber closebad clsflnam compare compare2 concat1 concat2 \
 	concat3 concat4 convfmt \
 	datanonl defref delargv delarpm2 delarprm delfunc dfamb1 dfastress dynlj \
@@ -1227,7 +1243,7 @@ UNIX_TESTS = \
 GAWK_EXT_TESTS = \
 	aadelete1 aadelete2 aarray1 aasort aasorti argtest arraysort \
 	backw badargs beginfile1 beginfile2 binmode1 charasbytes \
-	colonwarn clos1way delsub devfd devfd1 devfd2 dumpvars exit \
+	colonwarn clos1way dbugeval delsub devfd devfd1 devfd2 dumpvars exit \
 	fieldwdth fpat1 fpat2 fpat3  fpatnull fsfwfs funlen \
 	functab1 functab2 functab3 fwtest fwtest2 fwtest3 \
 	gensub gensub2 getlndir gnuops2 gnuops3 gnureops \
@@ -1239,15 +1255,18 @@ GAWK_EXT_TESTS = \
 	nastyparm next nondec nondec2 \
 	patsplit posix printfbad1 printfbad2 printfbad3 procinfs \
 	profile1 profile2 profile3 profile4 profile5 pty1 \
-	rebuf regx8bit reginttrad reint reint2 rsstart1 \
-	rsstart2 rsstart3 rstest6 shadow sortfor sortu splitarg4 strftime \
+	rebuf regnul1 regnul2 regx8bit reginttrad reint reint2 rsgetline rsglstdin rsstart1 \
+	rsstart2 rsstart3 rstest6 shadow sortfor sortu split_after_fpat \
+	splitarg4 strftime \
 	strtonum switch2 symtab1 symtab2 symtab3 symtab4 symtab5 symtab6 \
 	symtab7 symtab8 symtab9
 
 EXTRA_TESTS = inftest regtest
 INET_TESTS = inetdayu inetdayt inetechu inetecht
 MACHINE_TESTS = double1 double2 fmtspcl intformat
-MPFR_TESTS = mpfrnr mpfrrnd mpfrieee mpfrexprange mpfrsort mpfrbigint
+MPFR_TESTS = mpfrnr mpfrnegzero mpfrrnd mpfrieee mpfrexprange \
+	mpfrsort mpfrbigint
+
 LOCALE_CHARSET_TESTS = \
 	asort asorti backbigs1 backsmalls1 backsmalls2 \
 	fmttest fnarydel fnparydl jarebug lc_num1 mbfw1 \
@@ -1255,7 +1274,7 @@ LOCALE_CHARSET_TESTS = \
 
 SHLIB_TESTS = \
 	fnmatch filefuncs fork fork2 fts functab4 inplace1 inplace2 inplace3 \
-	ordchr ordchr2 readdir readfile revout revtwoway rwarray testext time
+	ordchr ordchr2 readdir readfile readfile2 revout revtwoway rwarray testext time
 
 
 # List of the tests which should be run with --lint option:
@@ -1563,6 +1582,10 @@ machine-msg-end:
 
 charset-msg-start:
 	@echo "======== Starting tests that can vary based on character set or locale support ========"
+	@echo "************************************************"
+	@echo "** Some or all of these tests may fail if you **"
+	@echo "** have inadequate or missing locale support  **"
+	@echo "************************************************"
 
 charset-msg-end:
 	@echo "======== Done with tests that can vary based on character set or locale support ========"
@@ -1597,7 +1620,7 @@ poundbang::
 	@if ./_pbd.awk "$(srcdir)"/poundbang.awk > _`basename $@` ; \
 	then : ; \
 	else \
-		sed "s;/tmp/gawk;../$(AWKPROG);" < "$(srcdir)"/poundbang.awk > ./_pbd.awk ; \
+		sed "s;/tmp/gawk;$(AWKPROG);" < "$(srcdir)"/poundbang.awk > ./_pbd.awk ; \
 		chmod +x ./_pbd.awk ; \
 		LC_ALL=$${GAWKLOCALE:-C} LANG=$${GAWKLOCALE:-C} ./_pbd.awk "$(srcdir)"/poundbang.awk > _`basename $@`;  \
 	fi
@@ -1674,12 +1697,10 @@ nonl::
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 strftime::
-	@echo This test could fail on slow machines or on a minute boundary,
-	@echo so if it does, double check the actual results:
 	@echo $@
 	@GAWKLOCALE=C; export GAWKLOCALE; \
 	TZ=GMT0; export TZ; \
-	(LC_ALL=C date) | $(AWK) -v OUTPUT=_$@ -f "$(srcdir)"/strftime.awk
+	$(AWK) -v OUTPUT=_$@ -f "$(srcdir)"/strftime.awk
 	@-$(CMP) strftime.ok _$@ && rm -f _$@ strftime.ok || exit 0
 
 litoct::
@@ -1743,6 +1764,16 @@ fmtspcl: fmtspcl.ok
 	$(CMP) "$(srcdir)"/$@-mpfr.ok _$@ && rm -f _$@ ; \
 	fi
 
+rebuf::
+	@echo $@
+	@AWKBUFSIZE=4096 AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
+rsglstdin:: 
+	@echo $@
+	@cat  "$(srcdir)"/rsgetline.in | AWKPATH="$(srcdir)" $(AWK) -f rsgetline.awk >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 reint::
 	@echo $@
 	@$(AWK) --re-interval -f "$(srcdir)"/reint.awk "$(srcdir)"/reint.in >_$@
@@ -1878,7 +1909,7 @@ widesub4::
 
 ignrcas2::
 	@echo $@
-	@GAWKLOCALE=en_US ; export GAWKLOCALE ; \
+	@GAWKLOCALE=en_US.UTF-8 ; export GAWKLOCALE ; \
 	$(AWK) -f "$(srcdir)"/$@.awk >_$@ 2>&1 || echo EXIT CODE: $$? >> _$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
@@ -2118,6 +2149,11 @@ mpfrrnd:
 	@$(AWK) -M -vPREC=53 -f "$(srcdir)"/$@.awk > _$@ 2>&1
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+mpfrnegzero:
+	@echo $@
+	@$(AWK) -M -f "$(srcdir)"/$@.awk > _$@ 2>&1
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 mpfrnr:
 	@echo $@
 	@$(AWK) -M -vPREC=113 -f "$(srcdir)"/$@.awk "$(srcdir)"/$@.in > _$@
@@ -2149,6 +2185,11 @@ readfile::
 	@$(AWK) -l readfile 'BEGIN {printf "%s", readfile("Makefile")}' >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) Makefile _$@ && rm -f _$@ || cp -p Makefile $@.ok
 
+readfile2::
+	@echo $@
+	@$(AWK) -f "$(srcdir)"/$@.awk "$(srcdir)"/$@.awk "$(srcdir)"/readdir.awk > _$@ || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 include2::
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) --include inclib 'BEGIN {print sandwich("a", "b", "c")}' >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
@@ -2223,7 +2264,7 @@ inplace3::
 
 testext::
 	@echo $@
-	@$(AWK) '/^(@load|BEGIN)/,/^}/' $(top_srcdir)/extension/testext.c > testext.awk
+	@$(AWK) '/^(@load|BEGIN)/,/^}/' "$(top_srcdir)"/extension/testext.c > testext.awk
 	@$(AWK) -f testext.awk >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@ testext.awk
 
@@ -2233,9 +2274,12 @@ readdir:
 	echo If it does, try rerunning on an ext'[234]' filesystem. ; \
 	fi
 	@echo $@
-	@$(AWK) -f "$(srcdir)"/readdir.awk $(top_srcdir) > _$@
-	@ls -afli $(top_srcdir) | sed 1d | $(AWK) -f "$(srcdir)"/readdir0.awk -v extout=_$@ $(top_srcdir) > $@.ok
-	@-$(CMP) $@.ok _$@ && rm -f $@.ok _$@
+	@$(AWK) -f "$(srcdir)"/readdir.awk "$(top_srcdir)" > _$@
+	@ls -afi "$(top_srcdir)" > _dirlist
+	@ls -lna "$(top_srcdir)" | sed 1d > _longlist
+	@$(AWK) -f "$(srcdir)"/readdir0.awk -v extout=_$@  \
+		-v dirlist=_dirlist -v longlist=_longlist > $@.ok
+	@-$(CMP) $@.ok _$@ && rm -f $@.ok _$@ _dirlist _longlist
 
 fts:
 	@case `uname` in \
@@ -2320,6 +2364,11 @@ backsmalls2:
 	@[ -z "$$GAWKLOCALE" ] && GAWKLOCALE=en_US.UTF-8; \
 	AWKPATH="$(srcdir)" $(AWK) -f $@.awk "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
+dbugeval::
+	@echo $@
+	@$(AWK) --debug -f /dev/null < "$(srcdir)"/$@.in > _$@  2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 Gt-dummy:
 # file Maketests, generated from Makefile.am by the Gentests program
 addcomma:
@@ -3474,9 +3523,14 @@ pty1:
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
-rebuf:
+regnul1:
 	@echo $@
-	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
+regnul2:
+	@echo $@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 regx8bit:
@@ -3484,6 +3538,11 @@ regx8bit:
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+rsgetline:
+	@echo $@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 rstest6:
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
@@ -3504,6 +3563,11 @@ sortu:
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+split_after_fpat:
+	@echo $@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 splitarg4:
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
diff --git a/test/Maketests b/test/Maketests
index df272ce8..0841ae77 100644
--- a/test/Maketests
+++ b/test/Maketests
@@ -1152,9 +1152,14 @@ pty1:
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
-rebuf:
+regnul1:
 	@echo $@
-	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
+regnul2:
+	@echo $@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
 regx8bit:
@@ -1162,6 +1167,11 @@ regx8bit:
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+rsgetline:
+	@echo $@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 rstest6:
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
@@ -1182,6 +1192,11 @@ sortu:
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
 	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
 
+split_after_fpat:
+	@echo $@
+	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
+	@-$(CMP) "$(srcdir)"/$@.ok _$@ && rm -f _$@
+
 splitarg4:
 	@echo $@
 	@AWKPATH="$(srcdir)" $(AWK) -f $@.awk  < "$(srcdir)"/$@.in >_$@ 2>&1 || echo EXIT CODE: $$? >>_$@
diff --git a/test/dbugeval.in b/test/dbugeval.in
new file mode 100644
index 00000000..6a3c2459
--- /dev/null
+++ b/test/dbugeval.in
@@ -0,0 +1,2 @@
+eval ""
+eval ""
diff --git a/test/dbugeval.ok b/test/dbugeval.ok
new file mode 100644
index 00000000..284f2abb
--- /dev/null
+++ b/test/dbugeval.ok
@@ -0,0 +1 @@
+EXIT CODE: 2
diff --git a/test/fts.awk b/test/fts.awk
index a1b49cbd..70af560f 100644
--- a/test/fts.awk
+++ b/test/fts.awk
@@ -3,8 +3,19 @@
 BEGIN {
 	Level = 0
 
-	system("rm -fr d1 d2")
-	system("mkdir d1 d2 ; touch d1/f1 d1/f2 d2/f1 d2/f2")
+	os = ""
+	if (ENVIRON["AWKLIBPATH"] == "sys$disk:[-]") {
+		os = "VMS"
+		system("create/dir/prot=o:rwed [.d1]")
+		system("create/dir/prot=o:rwed [.d2]")
+		system("copy fts.awk [.d1]f1")
+		system("copy fts.awk [.d1]f2")
+		system("copy fts.awk [.d2]f1")
+		system("copy fts.awk [.d2]f2")
+	} else {
+		system("rm -fr d1 d2")
+		system("mkdir d1 d2 ; touch d1/f1 d1/f2 d2/f1 d2/f2")
+	}
 	pathlist[1] = "d1"
 	pathlist[2] = "d2"
 	flags = FTS_PHYSICAL
@@ -19,7 +30,14 @@ BEGIN {
 	traverse(data2)
 	close(output)
 
-	system("rm -fr d1 d2")
+	if (os == "VMS") {
+		system("delete [.d1]*.*;*")
+		system("delete [.d2]*.*;*")
+		system("delete d1.dir;*")
+		system("delete d2.dir;*")
+	} else {
+		system("rm -fr d1 d2")
+	}
 }
 
 function indent(        i)
@@ -96,6 +114,13 @@ function process(pathname, data_array,
 	for (i in stat_data)
 		data_array[pathname]["."]["stat"][i] = stat_data[i]
 
+	os = ""
+	if (ENVIRON["AWKLIBPATH"] == "sys$disk:[-]") {
+		os = "VMS"
+		# Command in next section not valid on VMS.
+		return
+	}
+
 	command = ("ls -f " pathname)
 	while ((command | getline direntry) > 0) {
 		if (direntry == "." || direntry == "..")
diff --git a/test/lintwarn.ok b/test/lintwarn.ok
index ec87612f..bc5226e6 100644
--- a/test/lintwarn.ok
+++ b/test/lintwarn.ok
@@ -1,6 +1,6 @@
 gawk: lintwarn.awk:2: warning: `BEGINFILE' is a gawk extension
-gawk: lintwarn.awk:3: error: `getline var' invalid inside `BEGINFILE' rule
-gawk: lintwarn.awk:4: error: `getline' invalid inside `BEGINFILE' rule
+gawk: lintwarn.awk:3: error: non-redirected `getline' invalid inside `BEGINFILE' rule
+gawk: lintwarn.awk:4: error: non-redirected `getline' invalid inside `BEGINFILE' rule
 gawk: lintwarn.awk:8: warning: statement may have no effect
 gawk: lintwarn.awk:9: warning: plain `print' in BEGIN or END rule should probably be `print ""'
 gawk: lintwarn.awk:10: error: `nextfile' used in BEGIN action
diff --git a/test/mpfrnegzero.awk b/test/mpfrnegzero.awk
new file mode 100644
index 00000000..cc6bf65b
--- /dev/null
+++ b/test/mpfrnegzero.awk
@@ -0,0 +1,15 @@
+BEGIN {
+	printf("-0 -> %f, -0.0 -> %f\n", -0, -0.0)
+
+	printf("atan2(+0, -0) = %f\n", atan2(+0, -0))
+	printf("atan2(+0.0, -0.0) = %f\n", atan2(+0.0, -0.0))
+
+	printf("atan2(-0, -0) = %f\n", atan2(-0, -0))
+	printf("atan2(-0.0, -0.0) = %f\n", atan2(-0.0, -0.0))
+
+	printf("atan2(+0, +0) = %f\n", atan2(+0, +0))
+	printf("atan2(+0.0, +0.0) = %f\n", atan2(+0.0, +0.0))
+
+	printf("atan2(-0, +0) = %f\n", atan2(-0, +0))
+	printf("atan2(-0.0, +0.0) = %f\n", atan2(-0.0, +0.0))
+}
diff --git a/test/mpfrnegzero.ok b/test/mpfrnegzero.ok
new file mode 100644
index 00000000..7af16292
--- /dev/null
+++ b/test/mpfrnegzero.ok
@@ -0,0 +1,9 @@
+-0 -> -0.000000, -0.0 -> -0.000000
+atan2(+0, -0) = 3.141593
+atan2(+0.0, -0.0) = 3.141593
+atan2(-0, -0) = -3.141593
+atan2(-0.0, -0.0) = -3.141593
+atan2(+0, +0) = 0.000000
+atan2(+0.0, +0.0) = 0.000000
+atan2(-0, +0) = -0.000000
+atan2(-0.0, +0.0) = -0.000000
diff --git a/test/readdir0.awk b/test/readdir0.awk
index 296c03c7..2b7674a4 100644
--- a/test/readdir0.awk
+++ b/test/readdir0.awk
@@ -1,4 +1,9 @@
+# NOTE: This program is not a generalized parser for the output of 'ls'.
+# It's job is to read the output of ls from the gawk source code directory,
+# where we know there are no symbolic links, nor are there files with
+# spaces in their file names, etc.
 BEGIN {
+	# analyze results from readdir extension
 	while ((getline x < extout) > 0) {
 		numrec++
 		if ((split(x, f, "/") == 3) && (f[3] == "u"))
@@ -12,12 +17,7 @@ BEGIN {
 }
 
 BEGIN {
-	dir = ARGV[1]
-	delete ARGV[1]
-	ls_afi = "ls -afi " dir
-	ls_al = ("ls -lna " dir " | sed 1d")
-
-	for (i = 1; (ls_afi | getline) > 0; i++) {
+	for (i = 1; (getline < dirlist) > 0; i++) {
 		# inode number is $1, filename is read of record
 		inode = $1
 		$1 = ""
@@ -26,21 +26,18 @@ BEGIN {
 		names[i] = $0
 		ino[names[i]] = inode
 	}
-	close(ls_afi)
+	close(dirlist)
 
-	for (j = 1; (ls_al | getline) > 0; j++) {
+	for (j = 1; (getline < longlist) > 0; j++) {
 		type_let = substr($0, 1, 1)
 		if (type_let == "-")
 			type_let = "f"
-		$1 = $2 = $3 = $4 = $5 = $6 = $7 = $8 = ""
-		$0 = $0
-		sub(/^ */, "")
-		type[$0] = type_let
+		type[$NF] = type_let
 	}
-	close(ls_al)
+	close(longlist)
 
 	if (i != j)
-		printf("mismatch: %d from `ls -afi' and %d from `ls -l'\n", i, j) > "/dev/stderr"
+		printf("mismatch: %d from `ls -afi' and %d from `ls -lna'\n", i, j) > "/dev/stderr"
 	
 	for (i = 1; i in names; i++)
 		printf("%s/%s/%s\n", ino[names[i]], names[i], (ftype_unknown ? "u" : type[names[i]]))
diff --git a/test/readfile2.awk b/test/readfile2.awk
new file mode 100644
index 00000000..c21483fc
--- /dev/null
+++ b/test/readfile2.awk
@@ -0,0 +1,12 @@
+@load "readfile"
+BEGIN { PROCINFO["readfile"] = 1 }
+BEGINFILE { print "Start of", basename(FILENAME) }
+{ printf ("%d: <%s>\n", FNR, $0 ) }
+ENDFILE { print "End of", basename(FILENAME) }
+
+function basename(file,		result)
+{
+	result = file
+	gsub(".*/", "", result)
+	return result
+}
diff --git a/test/readfile2.ok b/test/readfile2.ok
new file mode 100644
index 00000000..be1ded6c
--- /dev/null
+++ b/test/readfile2.ok
@@ -0,0 +1,21 @@
+Start of readfile2.awk
+1: <@load "readfile"
+BEGIN { PROCINFO["readfile"] = 1 }
+BEGINFILE { print "Start of", basename(FILENAME) }
+{ printf ("%d: <%s>\n", FNR, $0 ) }
+ENDFILE { print "End of", basename(FILENAME) }
+
+function basename(file,		result)
+{
+	result = file
+	gsub(".*/", "", result)
+	return result
+}
+>
+End of readfile2.awk
+Start of readdir.awk
+1: <@load "readdir"
+
+{ print }
+>
+End of readdir.awk
diff --git a/test/regnul1.awk b/test/regnul1.awk
new file mode 100644
index 00000000..2a35d176
--- /dev/null
+++ b/test/regnul1.awk
@@ -0,0 +1,84 @@
+# From denis@gissoft.eu Thu May 29 09:07:56 IDT 2014
+# Article: 8400 of comp.lang.awk
+# X-Received: by 10.236.81.99 with SMTP id l63mr3912466yhe.3.1401224812642;
+#         Tue, 27 May 2014 14:06:52 -0700 (PDT)
+# X-Received: by 10.140.37.148 with SMTP id r20mr578874qgr.0.1401224812310; Tue,
+#  27 May 2014 14:06:52 -0700 (PDT)
+# Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!hl10no6493021igb.0!news-out.google.com!gi6ni15574igc.0!nntp.google.com!hl10no6493018igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
+# Newsgroups: comp.lang.awk
+# Date: Tue, 27 May 2014 14:06:52 -0700 (PDT)
+# Complaints-To: groups-abuse@google.com
+# Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.253.50.165;
+#  posting-account=zNhVLgoAAACsg-WfVe_or2VV7loUhx8H
+# NNTP-Posting-Host: 85.253.50.165
+# User-Agent: G2/1.0
+# MIME-Version: 1.0
+# Message-ID: <3112e356-d2e1-45cd-ba55-2f939ee50105@googlegroups.com>
+# Subject: \0 character can't be implement inside regexp in some cases?
+# From: denis@gissoft.eu
+# Injection-Date: Tue, 27 May 2014 21:06:52 +0000
+# Content-Type: text/plain; charset=ISO-8859-1
+# Xref: news.eternal-september.org comp.lang.awk:8400
+# 
+# Hello,
+# 
+# while doing some experiments with the gawk(4.1.1) i was found problem in implementing character \x00 inside regexp for two cases:
+# 
+# str~/\0/
+# 
+# and
+# 
+# switch ( str ) { case /\0/: ... }
+# 
+# the following code try to match given string(=="\x00") with the regexp /^\0$/ using different ways provided by gawk:
+# 
+func	_chm(t) {
+	_ch("match()",match(t,/^\0$/))
+	_ch("split()",split(t,A,/^\0$/)>1)
+	_ch("patsplit()",patsplit(t,A,/^\0$/))
+	_ch("gsub()",gsub(/^\0$/,"&",t))
+	_ch("sub()",sub(/^\0$/,"&",t))
+	_ch("gensub()",!gensub(/^\0$/,"","G",t))
+	_ch("str~/rexp/",t~/^\0$/)
+	a=0; switch ( t ) { case /^\0$/: a=1 }; _ch("switch-case //",a) }
+
+func	_ch(fn,bool) {
+	print substr(fn ":                ",1,16) (bool ? "+" : "-") }
+
+BEGIN{ _chm("\000") }
+# 
+# output:
+# 
+# > gawk -f _null.gwk
+# match():        +
+# split():        +
+# patsplit():     +
+# gsub():         +
+# sub():          +
+# gensub():       +
+# str~/rexp/:     -
+# switch-case //: -
+# 
+# can someone explain me:
+# 
+# why in case using match(), split(), patsplit(), gsub(), sub() and gensub() the given string "\x00" matches with the /^\0$/
+# 
+# but in cases:
+# 
+# "\x00"~/^\0$/
+# 
+# and
+# 
+# switch ( "\x00" ) { case /^\0$/: doesn't match? }
+# 
+# 
+# thank You
+# 
+# 
+# GNU Awk 4.1.1, API: 1.1 (GNU MPFR 3.1.0-p8, GNU MP 5.0.2)
+# Copyright (C) 1989, 1991-2014 Free Software Foundation.
+# downloaded from ezwinports
+# 
+# windows 7x64; cmd
+# 
+# 
diff --git a/test/regnul1.ok b/test/regnul1.ok
new file mode 100644
index 00000000..2ba0e1da
--- /dev/null
+++ b/test/regnul1.ok
@@ -0,0 +1,8 @@
+match():        +
+split():        +
+patsplit():     +
+gsub():         +
+sub():          +
+gensub():       +
+str~/rexp/:     +
+switch-case //: +
diff --git a/test/regnul2.awk b/test/regnul2.awk
new file mode 100644
index 00000000..3d93df41
--- /dev/null
+++ b/test/regnul2.awk
@@ -0,0 +1,112 @@
+# From denis@gissoft.eu Thu May 29 09:10:18 IDT 2014
+# Article: 8408 of comp.lang.awk
+# X-Received: by 10.182.128.166 with SMTP id np6mr93689obb.16.1401289466734;
+#         Wed, 28 May 2014 08:04:26 -0700 (PDT)
+# X-Received: by 10.140.36.6 with SMTP id o6mr4939qgo.26.1401289466607; Wed, 28
+#  May 2014 08:04:26 -0700 (PDT)
+# Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!c1no19185457igq.0!news-out.google.com!qf4ni13600igc.0!nntp.google.com!c1no19185454igq.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
+# Newsgroups: comp.lang.awk
+# Date: Wed, 28 May 2014 08:04:26 -0700 (PDT)
+# In-Reply-To: <lm4rra$4u9$1@dont-email.me>
+# Complaints-To: groups-abuse@google.com
+# Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=82.131.35.51; posting-account=zNhVLgoAAACsg-WfVe_or2VV7loUhx8H
+# NNTP-Posting-Host: 82.131.35.51
+# References: <3112e356-d2e1-45cd-ba55-2f939ee50105@googlegroups.com>
+#  <lm34d7$tb4$1@news.m-online.net> <f666871f-a94c-4505-9677-8711d656433c@googlegroups.com>
+#  <lm4rra$4u9$1@dont-email.me>
+# User-Agent: G2/1.0
+# MIME-Version: 1.0
+# Message-ID: <79828a24-d265-4e88-8de1-e61ecbaa6701@googlegroups.com>
+# Subject: Re: \0 character can't be implement inside regexp in some cases?
+# From: Denis Shirokov <denis@gissoft.eu>
+# Injection-Date: Wed, 28 May 2014 15:04:26 +0000
+# Content-Type: text/plain; charset=ISO-8859-1
+# Xref: news.eternal-september.org comp.lang.awk:8408
+# 
+# 
+#  All of the other use-cases just cluttered up your posting. 
+# 
+# oh, really?
+# 
+# 1. where in the Janis code the case with the `switch-case'?
+# 2. how do you know about that there is only two cases? may be you know it because my code contains the other test cases?
+# 3. fine. do you know what situation with the dynamic regexps? no?
+# 4. do you know what situation with RS,FS and /.../ in the middle-area? how you can say that there is only two cases if you absolutely do not know it?
+# 
+# i'm asking: WHO will perform testing other cases? You? gawk-team? the God?
+# what is that point of view: that it will be enough to say:
+# Oh! my match(t,/^\0$/) is matching "\x00" but t~/^\0$/ is not. why oh why?
+# 
+# where is the test cover? or you think that other peoples will doing its instead of You? instead of Me?
+# 
+# and the second point: guys you are screaming about two levels of stack. really,  you kidding? =)
+# 
+# however, i'm attaching some additional information about dynrexp:
+# 
+func	_chmd(t,r) {
+	_ch("match()",match(t,r))
+	_ch("split()",split(t,A,r)>1)
+	_ch("patsplit()",patsplit(t,A,r))
+	_ch("gsub()",gsub(r,"&",t))
+	t2=t; _ch("sub()",sub(r,"&",t2))
+	_ch("gensub()",!gensub(r,"","G",t))
+	_ch("str~/rexp/",t~r)
+	# switch-case is not applicable with dynrxp
+	_conline() }
+
+func	_ch(fn,bool) {
+	print substr(fn ":                ",1,16) (bool ? "+" : "-") }
+
+func	_conline() {
+	print "__________________________"; print }
+
+BEGIN{ _chmd("\x01","^\1$")     #testing that all doings right; all match
+	_chmd("\x00","^\1$")      #testing that all doings right; all not match
+	_chmd("\x00","^\0$")      #tesing dynrexp
+}
+# 
+# output:
+# 
+# match():        +
+# split():        +
+# patsplit():     +
+# gsub():         +
+# sub():          +
+# gensub():       +
+# str~/rexp/:     +
+# __________________________
+# 
+# match():        -
+# split():        -
+# patsplit():     -
+# gsub():         -
+# sub():          -
+# gensub():       -
+# str~/rexp/:     -
+# __________________________
+# 
+# match():        +
+# split():        +
+# patsplit():     +
+# gsub():         +
+# sub():          +
+# gensub():       +
+# str~/rexp/:     -
+# 
+# it's looks like with the dynamic regexp the same story.
+# 
+# i found another one moment that is possible near with the reason of this issue:
+# 
+# i was testing what characters can be present in doublestring and regexp "directly" (just as the character) and what characters must be present as escape sequence (\qqq)
+# 
+# so, i found the following:
+# 
+# t="abc"
+# if ( match(t,/^abc[NUL]def/) ) ... - where [NUL] is the character \x00 
+# 
+# it's seems that in that case the regular expression is processed until [NUL]character and the other part is ignored because the example above gives TRUE
+# 
+# friendship
+# Denis Shirokov
+# 
+# 
diff --git a/test/regnul2.ok b/test/regnul2.ok
new file mode 100644
index 00000000..6b3cecab
--- /dev/null
+++ b/test/regnul2.ok
@@ -0,0 +1,27 @@
+match():        +
+split():        +
+patsplit():     +
+gsub():         +
+sub():          +
+gensub():       +
+str~/rexp/:     +
+__________________________
+
+match():        -
+split():        -
+patsplit():     -
+gsub():         -
+sub():          -
+gensub():       -
+str~/rexp/:     -
+__________________________
+
+match():        +
+split():        +
+patsplit():     +
+gsub():         +
+sub():          +
+gensub():       +
+str~/rexp/:     +
+__________________________
+
diff --git a/test/regrange.ok b/test/regrange.ok
index 1fa00c70..ae8c6499 100644
--- a/test/regrange.ok
+++ b/test/regrange.ok
@@ -3,4 +3,4 @@
 "c" ~ /[[a-d]/ --> 1
 "\" ~ /[\[-\]]/ --> 1
 "[.c.]" ~ /[a-[.e.]]/ --> 1
-"[.d.]" ~ /[[.c.]-[.z.]]/ --> 0
+"[.d.]" ~ /[[.c.]-[.z.]]/ --> 1
diff --git a/test/rsgetline.awk b/test/rsgetline.awk
new file mode 100644
index 00000000..fa327fcf
--- /dev/null
+++ b/test/rsgetline.awk
@@ -0,0 +1,23 @@
+# Date: Sun, 4 May 2014 18:09:01 +0200
+# From: Davide Brini <dave_br@gmx.com>
+# To: bug-gawk@gnu.org
+# Subject: Re: [bug-gawk] Computed regex and getline bug / issue
+# 
+# I have been able to reduce the behavior to these simple test cases, which
+# (unless I'm missing something obvious) should behave identically but don't:
+# 
+# $ printf '1,2,' | gawk 'BEGIN{RS="[,]+"}{print; a = getline; print "-"a"-"; print}'
+# 1
+# -0-
+# 1
+
+BEGIN {
+	RS = "[,]+"
+}
+
+{
+	printf "[%s] [%s]\n", $0, RT
+	a = getline
+	print "-"a"-"
+	printf "[%s] [%s]\n", $0, RT
+}
diff --git a/test/rsgetline.in b/test/rsgetline.in
new file mode 100644
index 00000000..f1782346
--- /dev/null
+++ b/test/rsgetline.in
@@ -0,0 +1 @@
+1,2,
+\ No newline at end of file
diff --git a/test/rsgetline.ok b/test/rsgetline.ok
new file mode 100644
index 00000000..1388369a
--- /dev/null
+++ b/test/rsgetline.ok
@@ -0,0 +1,3 @@
+[1] [,]
+-1-
+[2] [,]
diff --git a/test/rsglstdin.ok b/test/rsglstdin.ok
new file mode 100644
index 00000000..1388369a
--- /dev/null
+++ b/test/rsglstdin.ok
@@ -0,0 +1,3 @@
+[1] [,]
+-1-
+[2] [,]
diff --git a/test/rwarray.awk b/test/rwarray.awk
index 5d1b7e9d..0cb214ee 100644
--- a/test/rwarray.awk
+++ b/test/rwarray.awk
@@ -21,13 +21,20 @@ BEGIN {
 		printf("dict[%s] = %s\n", dictindices[i], dict[dictindices[i]]) > "new.out"
 	close("new.out");
 
-	ret = system("cmp orig.out new.out")
-
-	if (ret == 0)
-		print "old and new are equal - GOOD"
-	else
-		print "old and new are not equal - BAD"
-
-	if (ret == 0 && !("KEEPIT" in ENVIRON))
-		system("rm -f orig.bin orig.out new.out")
+	os = ""
+	if (ENVIRON["AWKLIBPATH"] == "sys$disk:[-]") {
+		os = "VMS"
+		# return status from system() on VMS can not be used here
+	}
+	if (os != "VMS") {
+		ret = system("cmp orig.out new.out")
+
+		if (ret == 0)
+			print "old and new are equal - GOOD"
+		else
+			print "old and new are not equal - BAD"
+
+		if (ret == 0 && !("KEEPIT" in ENVIRON))
+			system("rm -f orig.bin orig.out new.out")
+	}
 }
diff --git a/test/split_after_fpat.awk b/test/split_after_fpat.awk
new file mode 100644
index 00000000..7e7cfd99
--- /dev/null
+++ b/test/split_after_fpat.awk
@@ -0,0 +1,11 @@
+BEGIN { FPAT = "\"[^\"]*\"" }
+
+{ print $1 }
+
+END { f("hi there") }
+
+function f (p,   a, n, i)
+{
+        n = split(p,a)
+        print n ; for (i=1; i<=n; i++) print a[i]
+}
diff --git a/test/split_after_fpat.in b/test/split_after_fpat.in
new file mode 100644
index 00000000..1aeefd59
--- /dev/null
+++ b/test/split_after_fpat.in
@@ -0,0 +1 @@
+a"stuff"b
diff --git a/test/split_after_fpat.ok b/test/split_after_fpat.ok
new file mode 100644
index 00000000..5c284490
--- /dev/null
+++ b/test/split_after_fpat.ok
@@ -0,0 +1,4 @@
+"stuff"
+2
+hi
+there
diff --git a/test/strftime.awk b/test/strftime.awk
index 775cd4e5..f1276c15 100644
--- a/test/strftime.awk
+++ b/test/strftime.awk
@@ -1,19 +1,35 @@
 # strftime.awk ; test the strftime code
 #
 # input is the output of `date', see Makefile.in
-#
-# The mucking about with $0 and $N is to avoid problems
-# on cygwin, where the timezone field is empty and there
-# are two consecutive blanks.
 
-# Additional mucking about to lop off the seconds field;
-# helps decrease chance of difference due to a second boundary
+BEGIN {
+	maxtries = 10
+	# On DOS/Windows, DATECMD is set by the Makefile to point to
+	# Unix-like 'date' command.
+	datecmd = DATECMD
+	if (datecmd == "")
+	    datecmd = "date"
+	fmt = "%a %b %e %H:%M:%S %Z %Y"
 
-{
-	$3 = sprintf("%02d", $3 + 0)
-	$4 = substr($4, 1, 5)
-	print > "strftime.ok"
-	$0 = strftime("%a %b %d %H:%M %Z %Y")
-	$NF = $NF
-	print > OUTPUT
+	# loop until before equals after, thereby protecting
+	# against a race condition where the seconds field might have
+	# incremented between running date and strftime
+	i = 0
+	while (1) {
+		if (++i > maxtries) {
+			printf "Warning: this system is so slow that after %d attempts, we could never get two sequential invocations of strftime to give the same result!\n", maxtries > "/dev/stderr"
+			break
+		}
+		before = strftime(fmt)
+		datecmd | getline sd
+		after = strftime(fmt)
+		close(datecmd)
+		if (before == after) {
+			if (i > 1)
+				printf "Notice: it took %d loops to get the before and after strftime values to match\n", i > "/dev/stderr"
+			break
+		}
+	}
+	print sd > "strftime.ok"
+	print after > OUTPUT
 }
diff --git a/vms/ChangeLog b/vms/ChangeLog
index f8344654..9e055cf4 100644
--- a/vms/ChangeLog
+++ b/vms/ChangeLog
@@ -1,3 +1,130 @@
+2014-04-18         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawk_alias_setup.com: Fix problem with file links on Vax/VMS.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* descrip.mms, vmsbuild.com: Update patchlevel.
+
+2014-02-12         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* vmstest.com: (strftime) requires GNV Coreutils date command to run
+	  (readdir) fix file cleanup to not generate warnings.
+
+2014-01-21         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* generate_config_vms_h_gawk.com: upate copyright and fix exit status.
+
+2014-01-17         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* vmstest.com (split_after_fpat): Added this test.
+
+2014-01-03         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* config_h.com, generate_config_vms_h_gawk.com,
+	  vms_args.c, vms_cli.c, vms_fwrite.c, vms_gawk.c, vms_misc.c,
+	  vms_popen.c: Update copyright to 2014.
+	* descrip.mms: Improve spotless cleanup.
+	* vmstest.com: Improve test cleanup.
+	* backup_gawk_src.com: New file. Create backup savesets for gawk source.
+	* build_gawk_pcsi_desc.com: New file. Create a pcsi$desc manifest
+	  file for building a gawk package.
+	* build_gawk_pcsi_text.com: New file. Create a pcsi$text file for
+	  building a gawk package.
+	* build_gawk_release_notes.com: New file. Create a VMS release notes
+	  file based on the gawk README and COPYING files and the release note
+	  start and build instruction files.
+	* compare_gawk_source.com: New file. Helper file to compare and
+	  optionally update two gawk source directories.  Used to copy
+	  source from an NFS volume to a VMS native volume for backup.
+	* gawk_alias_setup.com: New file. Used at installation time to
+	  create hard links for for some files instead of copies.
+	* gawk_build_steps.txt: New file.  Document how to build a PCSI kit.
+	* gawk_release_note_start.txt: New file.  Start of release notes.
+	* gawk_verb.com: New file. Converts the gawk.cld file into a
+	  gawk_verb.cld file for setting up GAWK as a DCL command.
+	* gnv_gawk_startup.com: New file.  Makes sure that the GNV$GNU logical
+	  name need to easily find the gawk image is defined.
+	* make_pcsi_gawk_kit_name.com: New File. Create the PCSI kit name
+	  based on the GAWK version.
+	* pcsi_gawk_file_list.txt: New File.  Input file for creating the
+	  pcsi$desc manifest file.
+	* pcsi_product_gawk.com: New file.  File to create the PCSI kit.
+	* remove_old_gawk.com: New file.  File to remove obsolete GNV gawk
+	  files replaced by the new PCSI kit.
+	* stage_gawk_install.com: New file.  Stages an install for the
+	  pcsi kit building.
+
+2013-12-29         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawk_plugin.opt: New file. Needed to build plugins on IA64
+	and ALPHA.
+	* generate_config_vms_h_gawk.com: Document which version
+	of VMS the mkstemp issue was seen.
+	* vms_popen: (pclose): Tolerate invalid file pointer.
+	* vmstest.com: Add tests for extensions ported to VMS.
+
+2013-12-23         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawkmisc.vms: Fix program name calculation on VAX.
+	* vms_cli.c: Fix case of public symbol.
+	* vms.hlp: Fix typo, add cautions on rounding and timezones.
+	* vmstest.com: Dcl symbol tz causing conflict with test.
+
+2013-12-20         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* descrip.mms: Set CC exact symbol names, cleanup repository.
+	* generate_config_vms_h_gawk.com: Use correct VMS exit codes.
+	* vmsbuild.com: Set CC exact symbol names.
+	* vmstest.com: Extract correct Unix status for failed tests.
+	* vms.h, vms_args.c, vms_cli.c, vms_fwrite.c, vms_gawk.c,
+	  vms_misc.c, vms_popen.c: Correct case of function names.
+	* vms.hlp: Updated with new information about exit codes.
+
+2013-12-10         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* gawkmisc.vms: Add lots of includes.
+	(sys_trnlnm): New function.
+	(gawk_name): Improved.
+	(os_arg_fixup): Fix up time zone.
+
+2013-12-08         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* descrip.mms: Add IEEE float for non-vax.
+	  Add vms_crtl_init.c.
+	  Remove code to generate version.c
+	* generate_config_vms_h_gawk.com (__attribute__): Removed
+	  definition from here.
+	* version_c.com: removed no longer used.
+	* vmsbuild.com: Add IEEE float for non-vax.
+	  Add vms_crtl_init.c
+	  Remove code to generate version.c
+	  Changes that should have been in the previous commit.
+	* vms_misc.c (vms_open): VMS CRTL for 8.3 Alpha is setting
+	  errno to ENOENT instead of EISDIR for ".".
+
+2013-12-05         John E. Malmberg      <wb8tyw@qsl.net>
+
+	* New config_h.com to generate config.h
+	* New gawk_ident.com generates ident line for link option file.
+	* Add version_c.com to create version.c from version.in.
+	* Remove fcntl.h covering up real fcntl.h.  If an older version
+	  of VMS needs this file, the build procedure should be updated
+	  to generate it from a template.
+	* descrip.mms: Use command files to generate files based
+	  on same input files as a Linux build.
+	* gawkmisc.vms (files_are_same): support _USE_STD_STAT for VMS 8.x.
+	* generate_config_vms_h_gawk.com: Generates a helper file
+	  config_vms.h to cover issues config_h.com can not handle.
+	* vmsbuild.com: Use command files to generate files based
+	  on the same input files as a Linux build.
+	* vms_misc.c (vms_open): VMS CRTL setting errno to ENOENT where
+	  it should be set to EMFILE.
+
 2013-12-06         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* vms-conf.h (__attribute__): Removed definition from here; fixed
diff --git a/vms/backup_gawk_src.com b/vms/backup_gawk_src.com
new file mode 100644
index 00000000..d1e47fbe
--- /dev/null
+++ b/vms/backup_gawk_src.com
@@ -0,0 +1,113 @@
+$! File: Backup_gawk_src.com
+$!
+$! Procedure to create backup save sets for installing in a PCSI kit.
+$!
+$! To comply with most Open Source licenses, the source used for building
+$! a kit will be packaged with the distribution kit for the binary.
+$!
+$! Backup save sets are the only storage format that I can expect a
+$! VMS system to be able to extract ODS-5 filenames and directories.
+$!
+$! The make_pcsi_kit_name.com needs to be run before this procedure to
+$! properly name the files that will be created.
+$!
+$! This file is created from a template file for the purpose of making it
+$! easier to port Unix code, particularly open source code to VMS.
+$! Therefore permission is freely granted for any use.
+$!
+$! 13-Jun-2009 J. Malmberg
+$!
+$!===========================================================================
+$!
+$! Save default
+$ default_dir = f$environment("DEFAULT")
+$!
+$ arch_type = f$getsyi("ARCH_NAME")
+$ arch_code = f$extract(0, 1, arch_type)
+$!
+$ if arch_code .nes. "V"
+$ then
+$   set proc/parse=extended
+$ endif
+$!
+$ ss_abort = 44
+$ status = ss_abort
+$!
+$ kit_name = f$trnlnm("GNV_PCSI_KITNAME")
+$ if kit_name .eqs. ""
+$ then
+$   write sys$output "@MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$ producer = f$trnlnm("GNV_PCSI_PRODUCER")
+$ if producer .eqs. ""
+$ then
+$   write sys$output "@MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$ filename_base = f$trnlnm("GNV_PCSI_FILENAME_BASE")
+$ if filename_base .eqs. ""
+$ then
+$   write sys$output "@MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$!
+$ node_swvers = f$getsyi("NODE_SWVERS")
+$ node_swvers_type = f$extract(0, 1, node_swvers)
+$ node_swvers_vers = f$extract(1, f$length(node_swvers), node_swvers)
+$ swvers_maj = f$element(0, ".", node_swvers_vers)
+$ node_swvers_min_update = f$element(1, ".", node_swvers_vers)
+$ swvers_min = f$element(0, "-", node_swvers_min_update)
+$ swvers_update = f$element(1, "-", node_swvers_min_update)
+$!
+$ if swvers_update .eqs. "-" then swvers_update = ""
+$!
+$ vms_vers = f$fao("!2ZB!2ZB!AS", 'swvers_maj', 'swvers_min', swvers_update)
+$!
+$!
+$!
+$! If available make an interchange save set
+$!-------------------------------------------
+$ interchange = ""
+$ if arch_code .eqs. "V"
+$ then
+$   interchange = "/interchange"
+$ endif
+$ if (swvers_maj .ges. "8") .and. (swvers_min .ges. 4)
+$ then
+$   interchange = "/interchange/noconvert"
+$ endif
+$!
+$!
+$! Put things back on error.
+$ on warning then goto all_exit
+$!
+$ current_default = f$environment("DEFAULT")
+$ my_dir = f$parse(current_default,,,"DIRECTORY") - "[" - "<" - ">" - "]"
+$!
+$ src_root = "src_root:"
+$ if f$trnlnm("src_root1") .nes. "" then src_root = "src_root1:"
+$ backup'interchange' 'src_root'[gawk...]*.*;0 -
+           'filename_base'_original_src.bck/sav
+$ status = $status
+$!
+$! There may be a VMS specific source kit
+$!-----------------------------------------
+$ vms_root = "vms_root:"
+$ if f$trnlnm("vms_root1") .nes. "" then vms_root = "vms_root1:"
+$ files_found = 0
+$ define/user sys$error nl:
+$ define/user sys$output nl:
+$ directory 'vms_root'[...]*.*;*/exc=*.dir
+$ if '$severity' .eq. 1 then files_found = 1
+$!
+$ if files_found .eq. 1
+$ then
+$   backup'interchange' 'vms_root'[gawk...]*.*;0 -
+            'filename_base'_vms_src.bck/sav
+$   status = $status
+$ endif
+$!
+$all_exit:
+$ set def 'default_dir'
+$ exit
diff --git a/vms/build_gawk_pcsi_desc.com b/vms/build_gawk_pcsi_desc.com
new file mode 100644
index 00000000..63d149e6
--- /dev/null
+++ b/vms/build_gawk_pcsi_desc.com
@@ -0,0 +1,428 @@
+$! File: Build_GAWK_PCSI_DESC.COM
+$!
+$! Build the *.pcsi$text file in the following sections:
+$!   Required software dependencies.
+$!   install/upgrade/postinstall steps.
+$!      1. Duplicate filenames need an alias procedure.
+$!      2. ODS-5 filenames need an alias procedure.
+$!      3. Special alias links for executables (cp. -> gnv$cp.exe)
+$!         if a lot, then an alias procedure is needed.
+$!      4. Rename the files to lowercase.
+$!   Move Release Notes to destination
+$!   Source kit option
+$!   Create directory lines
+$!   Add file lines for gawk.
+$!   Add Link alias procedure file (used for gawk)
+$!   Add [.SYS$STARTUP]gawk_startup file
+$!   Add Release notes file.
+$!
+$! The file PCSI_GAWK_FILE_LIST.TXT is read in to get the files other
+$! than the release notes file and the source backup file.
+$!
+$! The PCSI system can really only handle ODS-2 format filenames and
+$! assumes that there is only one source directory.  It also assumes that
+$! all destination files with the same name come from the same source file.
+$! Fortunately GAWK does not trip most of these issues, so those steps
+$! above are marked N/A.
+$!
+$! A rename action section is needed to make sure that the files are
+$! created in the GNV$GNU: in the correct case, and to create the alias
+$! link [usr.bin]gawk. for [usr.bin]gawk.exe.
+$!
+$! 02-Jan-2014  J. Malmberg - Gawk version
+$!
+$!===========================================================================
+$!
+$ kit_name = f$trnlnm("GNV_PCSI_KITNAME")
+$ if kit_name .eqs. ""
+$ then
+$   write sys$output "@[.vms]MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$ producer = f$trnlnm("GNV_PCSI_PRODUCER")
+$ if producer .eqs. ""
+$ then
+$   write sys$output "@[.vms]MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$ filename_base = f$trnlnm("GNV_PCSI_FILENAME_BASE")
+$ if filename_base .eqs. ""
+$ then
+$   write sys$output "@[.vms]MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$!
+$!
+$! Parse the kit name into components.
+$!---------------------------------------
+$ producer = f$element(0, "-", kit_name)
+$ base = f$element(1, "-", kit_name)
+$ product = f$element(2, "-", kit_name)
+$ mmversion = f$element(3, "-", kit_name)
+$ majorver = f$extract(0, 3, mmversion)
+$ minorver = f$extract(3, 2, mmversion)
+$ updatepatch = f$element(4, "-", kit_name)
+$ if updatepatch .eqs. "-" then updatepatch = ""
+$!
+$! kit type of "D" means a daily build
+$ kit_type = f$edit(f$extract(0, 1, majorver), "upcase")
+$!
+$!
+$ product_line = "product ''producer' ''base' ''product'"
+$ if updatepatch .eqs. ""
+$ then
+$     product_name = " ''majorver'.''minorver'"
+$ else
+$     product_name = " ''majorver'.''minorver'-''updatepatch'"
+$ endif
+$ product_line = product_line + " ''product_name' full;"
+$!write sys$output product_line
+$!
+$!
+$!
+$! Create the file as a VMS text file.
+$!----------------------------------------
+$ base_file = kit_name
+$ create 'base_file'.pcsi$desc
+$!
+$!
+$! Start building file.
+$!----------------------
+$ open/append pdsc 'base_file'.pcsi$desc
+$!
+$ write pdsc product_line
+$!
+$! Required product dependencies.
+$!----------------------------------
+$ vmsprd = "DEC"
+$ if base .eqs. "I64VMS" then vmsprd = "HP"
+$!
+$ write pdsc "   software ''vmsprd' ''base' VMS ;"
+$ arch_type = f$getsyi("ARCH_NAME")
+$ node_swvers = f$getsyi("node_swvers")
+$ vernum = f$extract(1, f$length(node_swvers), node_swvers)
+$ majver = f$element(0, ".", vernum)
+$ minverdash = f$element(1, ".", vernum)
+$ minver = f$element(0, "-", minverdash)
+$ dashver = f$element(1, "-", minverdash)
+$ if dashver .eqs. "-" then dashver = ""
+$ vmstag = majver + minver + dashver
+$ code = f$extract(0, 1, arch_type)
+$ arch_code = f$extract(0, 1, arch_type)
+$ write pdsc -
+ "   if (not <software ''vmsprd' ''base' VMS version minimum ''node_swvers'>) ;"
+$ write pdsc "      error NEED_VMS''vmstag';"
+$ write pdsc "   end if;"
+$!
+$!
+$!
+$! install/upgrade/postinstall steps.
+$!-----------------------------------
+$!      1. Duplicate filenames need an alias procedure.
+$!      2. ODS-5 filenames need an alias procedure.
+$!      3. Special alias links for executables (gawk. -> gnv$gawk.exe)
+$!         if a lot, then an alias procedure is needed.
+$!      4. Rename the files to lowercase.
+$!
+$!
+$!   Alias links needed.
+$!-------------------------
+$ add_alias_lines = ""
+$ rem_alias_lines = ""
+$ line_out = ""
+$!
+$!   Read through the file list to set up aliases and rename commands.
+$!---------------------------------------------------------------------
+$ open/read flst [.vms]pcsi_gawk_file_list.txt
+$!
+$inst_alias_loop:
+$   read/end=inst_alias_loop_end flst line_in
+$   line_in = f$edit(line_in,"compress,trim,uncomment")
+$   if line_in .eqs. "" then goto inst_alias_loop
+$   pathname = f$element(0, " ", line_in)
+$   linkflag = f$element(1, " ", line_in)
+
+$   if linkflag .nes. "->" then goto inst_alias_write
+$!
+$   linktarget = f$element(2, " ", line_in)
+$   nlink = "pcsi$destination:" + pathname
+$   ntarg = "pcsi$destination:" + linktarget
+$   new_add_alias_line = -
+  """if f$search(""""''nlink'"""") .eqs. """""""" then" + -
+  " set file/enter=''nlink' ''ntarg'"""
+$   if add_alias_lines .nes. ""
+$   then
+$       add_alias_lines = add_alias_lines + "," + new_add_alias_line
+$   else
+$       add_alias_lines = new_add_alias_line
+$   endif
+$!
+$   new_rem_alias_line = -
+  """if f$search(""""''nlink'"""") .nes. """""""" then" + -
+  " set file/remove ''nlink';"""
+$   if rem_alias_lines .nes. ""
+$   then
+$      rem_alias_lines = rem_alias_lines + "," + new_rem_alias_line
+$   else
+$      rem_alias_lines = new_rem_alias_line
+$   endif
+$!
+$   goto inst_alias_loop
+$!
+$inst_alias_write:
+$!
+$!  execute install / remove
+$   write pdsc "   execute install ("
+$! add aliases
+$   i = 0
+$ex_ins_loop:
+$       line = f$element(i, ",", add_alias_lines)
+$       i = i + 1
+$       if line .eqs. "" then goto ex_ins_loop
+$       if line .eqs. "," then goto ex_ins_loop_end
+$       if line_out .nes. "" then write pdsc line_out,","
+$       line_out = line
+$       goto ex_ins_loop
+$ex_ins_loop_end:
+$   if line_out .eqs. "" then line_out = "   ""continue"""
+$   write pdsc line_out
+$   line_out = ""
+$   write pdsc "      )"
+$   write pdsc "   remove ("
+$! remove aliases
+$   line_out = -
+       "  ""@pcsi$destination:[gnv.vms_bin]gawk_alias_setup.com remove"""
+$   i = 0
+$ex_rem_loop:
+$       line = f$element(i, ",", rem_alias_lines)
+$       i = i + 1
+$       if line .eqs. "" then goto ex_rem_loop
+$       if line .eqs. "," then goto ex_rem_loop_end
+$       if line_out .nes. "" then write pdsc line_out,","
+$       line_out = line
+$       goto ex_rem_loop
+$ex_rem_loop_end:
+$   if line_out .eqs. "" then line_out = "   ""continue"""
+$   write pdsc line_out
+$   line_out = ""
+$   write pdsc "      ) ;"
+$!
+$!  execute upgrade
+$   write pdsc "   execute upgrade ("
+$   line_out = -
+       "  ""@pcsi$destination:[gnv.vms_bin]gawk_alias_setup.com remove"""
+$   i = 0
+$ex_upg_loop:
+$       line = f$element(i, ",", rem_alias_lines)
+$       i = i + 1
+$       if line .eqs. "" then goto ex_upg_loop
+$       if line .eqs. "," then goto ex_upg_loop_end
+$       if line_out .nes. "" then write pdsc line_out,","
+$       line_out = line
+$       goto ex_upg_loop
+$ex_upg_loop_end:
+$   if line_out .eqs. "" then line_out = "   ""continue"""
+$   write pdsc line_out
+$   line_out = ""
+$! remove aliases
+$   write pdsc "      ) ;"
+$!
+$!  execute postinstall
+$   write pdsc "   execute postinstall ("
+$   if arch_code .nes. "V"
+$   then
+$       line_out = "   ""set process/parse=extended"","
+$       write pdsc line_out
+$   endif
+$   line_out = "  ""@pcsi$destination:[gnv.vms_bin]remove_old_gawk.com"","
+$   write pdsc line_out
+$   line_out = "  ""@pcsi$destination:[gnv.vms_bin]gawk_alias_setup.com"""
+$   i = 0
+$ex_pins_loop:
+$       line = f$element(i, ",", add_alias_lines)
+$       i = i + 1
+$       if line .eqs. "" then goto ex_pins_loop
+$       if line .eqs. "," then goto ex_pins_loop_end
+$       if line_out .nes. "" then write pdsc line_out,","
+$       line_out = line
+$       goto ex_pins_loop
+$ex_pins_loop_end:
+$   if line_out .eqs. "" then line_out = "   ""continue"""
+$!   write pdsc line_out
+$!   line_out = ""
+$! add aliases and follow with renames.
+$!
+$goto inst_dir
+$!
+$inst_dir_loop:
+$   read/end=inst_alias_loop_end flst line_in
+$   line_in = f$edit(line_in,"compress,trim,uncomment")
+$   if line_in .eqs. "" then goto inst_dir_loop
+$inst_dir:
+$   pathname = f$element(0, " ", line_in)
+$!
+$!  Ignore the directory entries for now.
+$!-----------------------------------------
+$   filedir = f$parse(pathname,,,"DIRECTORY")
+$   if pathname .eqs. filedir then goto inst_dir_loop
+$!
+$!  process .dir extensions for rename
+$!  If this is not a directory then start processing files.
+$!-------------------------
+$   filetype = f$parse(pathname,,,"TYPE")
+$   filetype_u = f$edit(filetype, "upcase")
+$   filename = f$parse(pathname,,,"NAME")
+$   if filetype_u .nes. ".DIR" then goto inst_file
+$!
+$!  process directory lines for rename.
+$!--------------------------------------
+$   if line_out .nes. ""
+$   then
+$       write pdsc line_out,","
+$       line_out = ""
+$   endif
+$   if arch_code .nes. "V"
+$   then
+$       if line_out .nes. "" then write pdsc line_out,","
+$       line_out = "   ""rename pcsi$destination:''pathname' ''filename'.DIR"""
+$   else
+$       if line_out .nes. "" then write pdsc line_out
+$       line_out = ""
+$   endif
+$   goto inst_dir_loop
+$!
+$!
+$!   process file lines for rename
+$!---------------------------------
+$inst_file_loop:
+$   read/end=inst_alias_loop_end flst line_in
+$   line_in = f$edit(line_in,"compress,trim,uncomment")
+$   if line_in .eqs. "" then goto inst_dir_loop
+$   pathname = f$element(0, " ", line_in)
+$!
+$!  Filenames with $ in them are VMS special and do not need to be lowercased.
+$!  --------------------------------------------------------------------------
+$   if f$locate("$", pathname) .lt. f$length(pathname) then goto inst_file_loop
+$!
+$   filetype = f$parse(pathname,,,"TYPE")
+$   filename = f$parse(pathname,,,"NAME") + filetype
+$inst_file:
+$   if arch_code .nes. "V"
+$   then
+$       if line_out .nes. "" then write pdsc line_out,","
+$       filetype = f$parse(pathname,,,"TYPE")
+$       filename = f$parse(pathname,,,"NAME") + filetype
+$       line_out = "   ""rename pcsi$destination:''pathname' ''filename'"""
+$   else
+$       if line_out .nes. "" then write pdsc line_out
+$       line_out = ""
+$   endif
+$   goto inst_file_loop
+$!
+$inst_alias_loop_end:
+$!
+$write pdsc line_out
+$write pdsc "        ) ;"
+$close flst
+$!
+$!   Move Release Notes to destination
+$!-------------------------------------
+$write pdsc "   information RELEASE_NOTES phase after ;"
+$!
+$!   Source kit option
+$!---------------------
+$write pdsc "   option SOURCE default 0;"
+$write pdsc "   directory ""[gnv.common_src]"" PROTECTION PUBLIC ;"
+$write pdsc -
+    "        file ""[gnv.common_src]''filename_base'_original_src.bck"""
+$write pdsc -
+    "          source [common_src]''filename_base'_original_src.bck ;"
+$if f$search("sys$disk:''filename_base'_vms_src.bck") .nes. ""
+$then
+$    write pdsc "   directory ""[gnv.vms_src]"" PROTECTION PUBLIC ;"
+$    write pdsc "        file ""[gnv.vms_src]''filename_base'_vms_src.bck"""
+$    write pdsc "          source [vms_src]''filename_base'_vms_src.bck ;"
+$endif
+$write pdsc "   end option;"
+$!
+$!
+$! Read through the file list again.
+$!----------------------------------
+$open/read flst [.vms]pcsi_gawk_file_list.txt
+$!
+$!
+$!   Create directory lines
+$!-------------------------
+$flst_dir_loop:
+$   read/end=flst_loop_end flst line_in
+$   line_in = f$edit(line_in,"compress,trim,uncomment")
+$   if line_in .eqs. "" then goto flst_dir_loop
+$!
+$   filename = f$element(0, " ", line_in)
+$   linkflag = f$element(1, " ", line_in)
+$   if linkflag .eqs. "->" then goto flst_dir_loop
+$!
+$!  Ignore .dir extensions
+$!-------------------------
+$   filetype = f$edit(f$parse(filename,,,"TYPE"), "upcase")
+$   if filetype .eqs. ".DIR" then goto flst_dir_loop
+$!
+$   destname = filename
+$!
+$!  It should be just a directory then.
+$!-------------------------------------
+$   filedir = f$edit(f$parse(filename,,,"DIRECTORY"), "lowercase")
+$!  If this is not a directory then start processing files.
+$!---------------------------------------------------------
+$   if filename .nes. filedir then goto flst_file
+$!
+$   write pdsc "   directory ""''destname'"" PROTECTION PUBLIC ;"
+$   goto flst_dir_loop
+$!
+$!
+$!   Add file lines for gawk.
+$!---------------------------
+$flst_file_loop:
+$   read/end=flst_loop_end flst line_in
+$   line_in = f$edit(line_in,"compress,trim,uncomment")
+$   if line_in .eqs. "" then goto flst_file_loop
+$   filename = f$element(0, " ", line_in)
+$   destname = filename
+$flst_file:
+$   if arch_code .eqs. "V"
+$   then
+$!      ! These files not available on VAX.
+$       src_dir = f$parse(destname,,,"DIRECTORY")
+$       if src_dir .eqs. "[GNV.USR.LIB.GAWK]" then goto flst_file_loop
+$   endif
+$   srcfile = filename - "gnv."
+$   write pdsc "   file ""''destname'"" "
+$   write pdsc "     source ""''srcfile'"" ;"
+$   goto flst_file_loop
+$!
+$flst_loop_end:
+$ close flst
+$!
+$!   Add Link alias procedure file (N/A for gawk)
+$!-----------------------------------------------------
+$ write pdsc "   file ""[vms_bin]gawk_alias_setup.com"""
+$ write pdsc "     source [vms_bin]gawk_alias_setup.com ;"
+$!
+$!   Add [.SYS$STARTUP]gawk_startup file
+$!---------------------------------------
+$ write pdsc "   file ""[sys$startup]gnv$gawk_startup.com"""
+$ write pdsc "     source [vms_bin]gnv$gawk_startup.com ;"
+$!
+$!   Add Release notes file.
+$!------------------------------
+$ write pdsc -
+    "   file ""[SYSHLP]''filename_base'.release_notes"" release notes ;"
+$!
+$! Close the product file
+$!------------------------
+$ write pdsc "end product;"
+$!
+$close pdsc
+$!
+$all_exit:
+$ exit
diff --git a/vms/build_gawk_pcsi_text.com b/vms/build_gawk_pcsi_text.com
new file mode 100644
index 00000000..a1053cf6
--- /dev/null
+++ b/vms/build_gawk_pcsi_text.com
@@ -0,0 +1,179 @@
+$! File: build_gawk_pcsi_text.com
+$!
+$! Build the *.pcsi$text file from the four components:
+$!    1. Generated =product header section
+$!    2. readme. file from the Gawk distribution, modified to fit
+$!       a pcsi$text file format.
+$!    3. copying file from the Gawk distribution, modified to fit
+$!       a pcsi$text file format.
+$!    4. Generated Producer section.
+$!
+$! Set the name of the release notes from the GNV_PCSI_FILENAME_BASE
+$!
+$!
+$! 02-Jan-2014  J. Malmberg - Gawk version
+$!
+$!===========================================================================
+$!
+$ kit_name = f$trnlnm("GNV_PCSI_KITNAME")
+$ if kit_name .eqs. ""
+$ then
+$   write sys$output "@MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$ producer = f$trnlnm("GNV_PCSI_PRODUCER")
+$ if producer .eqs. ""
+$ then
+$   write sys$output "@MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$ producer_full_name = f$trnlnm("GNV_PCSI_PRODUCER_FULL_NAME")
+$ if producer_full_name .eqs. ""
+$ then
+$   write sys$output "@MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$!
+$!
+$! Parse the kit name into components.
+$!---------------------------------------
+$ producer = f$element(0, "-", kit_name)
+$ base = f$element(1, "-", kit_name)
+$ product = f$element(2, "-", kit_name)
+$ mmversion = f$element(3, "-", kit_name)
+$ majorver = f$extract(0, 3, mmversion)
+$ minorver = f$extract(3, 2, mmversion)
+$ updatepatch = f$element(4, "-", kit_name)
+$ if updatepatch .eqs. "-" then updatepatch = ""
+$!
+$!
+$ product_line = "=product ''producer' ''base' ''product'"
+$ if updatepatch .eqs. ""
+$ then
+$     product_name = " ''majorver'.''minorver'"
+$ else
+$     product_name = " ''majorver'.''minorver'-''updatepatch'"
+$ endif
+$ product_line = product_line + " ''product_name' full"
+$!
+$!
+$! If this is VAX and the file is on NFS, the names may be mangled.
+$!-----------------------------------------------------------------
+$ readme_file = ""
+$ if f$search("readme.") .nes. ""
+$ then
+$   readme_file = "readme."
+$ else
+$   if f$search("$README.") .nes. ""
+$   then
+$       readme_file = "$README."
+$   else
+$       write sys$output "Can not find readme file."
+$       goto all_exit
+$   endif
+$ endif
+$ copying_file = ""
+$ if f$search("copying.") .nes. ""
+$ then
+$   copying_file = "copying."
+$ else
+$   if f$search("$COPYING.") .nes. ""
+$   then
+$       copying_file = "$COPYING."
+$   else
+$       write sys$output "Can not find copying file."
+$       goto all_exit
+$   endif
+$ endif
+$!
+$! Create the file as a VMS text file.
+$!----------------------------------------
+$ base_file = kit_name
+$ create 'base_file'.pcsi$text
+$!
+$!
+$! Start building file.
+$!----------------------
+$ open/append ptxt 'base_file'.pcsi$text
+$ write ptxt product_line
+$!
+$!
+$! First insert the Readme file.
+$!
+$ open/read rf 'readme_file'
+$!
+$ write ptxt "1 'PRODUCT"
+$ write ptxt "=prompt ''producter' ''product' for OpenVMS"
+$!
+$rf_loop:
+$   read/end=rf_loop_end rf line_in
+$   if line_in .nes. ""
+$   then
+$!    PCSI files use the first character in for their purposes.
+$!--------------------------------------------------------------
+$     first_char = f$extract(0, 1, line_in)
+$     if first_char .nes. " " then line_in = " " + line_in
+$   endif
+$   write ptxt line_in
+$   goto rf_loop
+$rf_loop_end:
+$ close rf
+$!
+$!
+$! Now add in the copying file
+$!--------------------------------
+$ write ptxt ""
+$ write ptxt "1 'NOTICE"
+$ write ptxt ""
+$!
+$ open/read cf 'copying_file'
+$!
+$cf_loop:
+$   read/end=cf_loop_end cf line_in
+$   if line_in .nes. ""
+$   then
+$!    PCSI files use the first character in for their purposes.
+$!--------------------------------------------------------------
+$     first_char = f$extract(0, 1, line_in)
+$     if first_char .nes. " " then line_in = " " + line_in
+$   endif
+$   write ptxt line_in
+$   goto cf_loop
+$cf_loop_end:
+$ close cf
+$!
+$! Now we need the rest of the boiler plate.
+$!--------------------------------------------
+$ write ptxt ""
+$ write ptxt "1 'PRODUCER"
+$ write ptxt "=prompt ''producer_full_name'"
+$ write ptxt -
+ "This software product is provided by ''producer_full_name' with no warranty."
+$!
+$ arch_type = f$getsyi("ARCH_NAME")
+$ node_swvers = f$getsyi("node_swvers")
+$ vernum = f$extract(1, f$length(node_swvers), node_swvers)
+$ majver = f$element(0, ".", vernum)
+$ minverdash = f$element(1, ".", vernum)
+$ minver = f$element(0, "-", minverdash)
+$ dashver = f$element(1, "-", minverdash)
+$ if dashver .eqs. "-" then dashver = ""
+$ vmstag = majver + minver + dashver
+$ code = f$extract(0, 1, arch_type)
+$!
+$ write ptxt "1 NEED_VMS''vmstag'"
+$ write ptxt -
+   "=prompt OpenVMS ''vernum' or later is not installed on your system."
+$ write ptxt "This product requires OpenVMS ''vernum' or later to function."
+$ write ptxt "1 SOURCE"
+$ write ptxt "=prompt Source modules for ''product'"
+$ write ptxt "The Source modules for ''product' will be installed."
+$ write ptxt "1 RELEASE_NOTES"
+$ write ptxt "=prompt Release notes are available in the [SYSHLP] directory."
+$!
+$ close ptxt
+$!
+$!
+$!
+$all_exit:
+$ exit
diff --git a/vms/build_gawk_release_notes.com b/vms/build_gawk_release_notes.com
new file mode 100644
index 00000000..c088ff8c
--- /dev/null
+++ b/vms/build_gawk_release_notes.com
@@ -0,0 +1,67 @@
+$! File: Build_gawk_release_notes.com
+$!
+$! Build the release note file from the three components:
+$!    1. The gawk_release_note_start.txt
+$!    2. readme. file from the Gawk distribution.
+$!    3. The gawk_build_steps.txt.
+$!
+$! Set the name of the release notes from the GNV_PCSI_FILENAME_BASE
+$! logical name.
+$!
+$!
+$! 31-Dec-2013  J. Malmberg
+$!
+$!===========================================================================
+$!
+$ base_file = f$trnlnm("GNV_PCSI_FILENAME_BASE")
+$ if base_file .eqs. ""
+$ then
+$   write sys$output "@MAKE_PCSI_GAWK_KIT_NAME.COM has not been run."
+$   goto all_exit
+$ endif
+$!
+$ gawk_vms_readme = f$search("sys$disk:[.readme_d]readme.vms")
+$ if gawk_vms_readme .eqs. ""
+$ then
+$   gawk_vms_readme = f$search("sys$disk:[.$README_$D]$README.VMS")
+$ endif
+$ if gawk_vms_readme .eqs. ""
+$ then
+$   write sys$output "Can not find gawk README.VMS file."
+$   goto all_exit
+$ endif
+$!
+$ gawk_readme = f$search("sys$disk:[]readme.")
+$ if gawk_readme .eqs. ""
+$ then
+$   gawk_readme = f$search("sys$disk:[]$README.")
+$ endif
+$ if gawk_readme .eqs. ""
+$ then
+$   write sys$output "Can not find gawk readme file."
+$   goto all_exit
+$ endif
+$!
+$ gawk_copying = f$search("sys$disk:[]copying.")
+$ if gawk_copying .eqs. ""
+$ then
+$   gawk_copying = f$search("sys$disk:[]$COPYING.")
+$ endif
+$ if gawk_copying .eqs. ""
+$ then
+$   write sys$output "Can not find gawk copying file."
+$   goto all_exit
+$ endif
+$!
+$ type/noheader sys$disk:[.vms]gawk_release_note_start.txt,-
+        'gawk_readme',-
+        'gawk_vms_readme',-
+        'gawk_copying', -
+        sys$disk:[.vms]gawk_build_steps.txt -
+        /out='base_file'.release_notes
+$!
+$ purge 'base_file'.release_notes
+$ rename 'base_file.release_notes ;1
+$!
+$all_exit:
+$   exit
diff --git a/vms/compare_gawk_source.com b/vms/compare_gawk_source.com
new file mode 100644
index 00000000..260ec4eb
--- /dev/null
+++ b/vms/compare_gawk_source.com
@@ -0,0 +1,367 @@
+$! Compare_gawk_source.com
+$!
+$! This procedure compares the files in two directories and reports the
+$! differences.
+$!
+$! It needs to be customized to the local site directories.
+$!
+$! This is used by me for these purposes:
+$!     1. Compare the original source of a project with an existing
+$!        VMS port.
+$!     2. Compare the checked out repository of a project with the
+$!        the local working copy to make sure they are in sync.
+$!     3. Keep a copy directory up to date.  The third is needed by
+$!        me because VMS Backup can create a saveset of files from a
+$!        NFS mounted volume.
+$!
+$! First the files in the original source directory which is assumed to be
+$! under source codde control are compared with the copy directory.
+$!
+$! Then the files are are only in the copy directory are listed.
+$!
+$! The result will five diagnostics about of files:
+$!    1. Files that are not generation 1.
+$!    2. Files missing in the copy directory.
+$!    3. Files in the copy directory not in the source directory.
+$!    4. Files different from the source directory.
+$!    5. Files that VMS DIFF can not process.
+$!
+$! This needs to be run on an ODS-5 volume.
+$!
+$! If UPDATE is given as a second parameter, files missing or different in the
+$! copy directory will be updated.
+$!
+$! By default:
+$!    The source directory is source_root:[gawk.reference.gawk],
+$!    the logical used on my system for the GNV Mecurial repository checkout.
+$!    If source_root: is not defined, then src_root:[gawk] will be
+$!    translated to something like DISK:[dir.gawk.reference.gawk]
+$!    and then DISK:[dir.gawk.vms_source.gawk] will be used.
+$!
+$!    The copy directory is vms_root:[gawk]
+$!    The UPDATE parameter is ignored.
+$!
+$!    This setting is used to make sure that the working vms directory
+$!    and the VMS specific repository checkout directory have the same
+$!    contents if they are different.
+$!
+$! If P1 is "SRCBCK" then this
+$!     The source directory tree is: src_root:[gawk]
+$!     The copy directory is src_root1:[gawk]
+$!
+$!   src_root1:[gawk] is used by me to work around that VMS backup will
+$!   not use NFS as a source directory so I need to make a copy.
+$!
+$!   This is to make sure that the backup save set for the unmodified
+$!   source is up to date.
+$!
+$!   If your repository checkout is not on an NFS mounted volume, you do not
+$!   need to use this option or have the logical name src_root1 defined.
+$!
+$! If P1 is "VMSBCK" then this changes the two directories:
+$!    The source directory is vms_root:[gawk]
+$!    The copy directory is vms_root1:[gawk]
+$!
+$!   vms_root:
+$!   src_root1:[gawk] is used by me to work around that VMS backup will
+$!   not use NFS as a source directory so I need to make a copy.
+$!
+$!   This is to make sure that the backup save set for the unmodified
+$!   source is up to date.
+$!
+$!   If your repository checkout is not on an NFS mounted volume, you do not
+$!   need to use this option or have the logical name src_root1 defined.
+$!
+$! 02-Jan-2014   J. Malmberg
+$!==========================================================================
+$!
+$! Update missing/changed files.
+$update_file = 0
+$if (p2 .eqs. "UPDATE")
+$then
+$   update_file = 1
+$endif
+$!
+$myproc = f$environment("PROCEDURE")
+$myprocdir = f$parse(myproc,,,"DIRECTORY") - "[" - "]" - "<" - ">"
+$myprocdir = f$edit(myprocdir, "LOWERCASE")
+$mydefault = f$environment("DEFAULT")
+$mydir = f$parse(mydefault,,,"DIRECTORY")
+$mydir = f$edit(mydir, "LOWERCASE")
+$odelim = f$extract(0, 1, mydir)
+$mydir = mydir - "[" - "]" - "<" - ">"
+$mydev = f$parse(mydefault,,,"DEVICE")
+$!
+$ref = ""
+$if P1 .eqs. ""
+$then
+$   ref_base_dir = myprocdir - ".vms"
+$   wrk_base_dir = mydir
+$   update_file = 0
+$   resultd = f$parse("src_root:",,,,"NO_CONCEAL")
+$   resultd = f$edit(resultd, "LOWERCASE")
+$   resultd = resultd - "][" - "><" - ".;" - ".."
+$   resultd_len = f$length(resultd) - 1
+$   delim = f$extract(resultd_len, 1, resultd)
+$   ref_root_base = mydir + delim
+$   if f$locate(".reference.", resultd) .lt. resultd_len
+$   then
+$      resultd = resultd - ref_root_base - "reference." + "vms_source."
+$   else
+$      resultd = resultd - ref_root_base - "gnu." + "gnu_vms."
+$   endif
+$   ref = resultd + ref_base_dir
+$   wrk = "VMS_ROOT:" + odelim + wrk_base_dir
+$   resultd_len = f$length(resultd) - 1
+$   resultd = f$extract(0, resultd_len, resultd) + delim
+$   ref_root_dir = f$parse(resultd,,,"DIRECTORY")
+$   ref_root_dir = f$edit(ref_root_dir, "LOWERCASE")
+$   ref_root_dir = ref_root_dir - "[" - "]"
+$   ref_base_dir = ref_root_dir + "." + ref_base_dir
+$endif
+$!
+$if p1 .eqs. "SRCBCK"
+$then
+$   ref_base_dir = "gawk"
+$   wrk_base_dir = "gawk"
+$   ref = "src_root:[" + ref_base_dir
+$   wrk = "src_root1:[" + wrk_base_dir
+$   if update_file
+$   then
+$       if f$search("src_root1:[000000]gawk.dir") .eqs. ""
+$       then
+$           create/dir/prot=o:rwed src_root1:[gawk]
+$       endif
+$   endif
+$endif
+$!
+$!
+$if p1 .eqs. "VMSBCK"
+$then
+$   ref_base_dir = "gawk"
+$   wrk_base_dir = "gawk"
+$   ref = "vms_root:[" + ref_base_dir
+$   wrk = "vms_root1:[" + wrk_base_dir
+$   if update_file
+$   then
+$       if f$search("vms_root1:[000000]gawk.dir") .eqs. ""
+$       then
+$           create/dir/prot=o:rwed vms_root1:[gawk]
+$       endif
+$   endif
+$endif
+$!
+$!
+$if ref .eqs. ""
+$then
+$   write sys$output "Unknown compare type specified!"
+$   exit 44
+$endif
+$!
+$!
+$!
+$! Future - check the device types involved for the
+$! the syntax to check.
+$ODS2_SYNTAX = 0
+$NFS_MANGLE = 0
+$PWRK_MANGLE = 0
+$!
+$vax = f$getsyi("HW_MODEL") .lt. 1024
+$if vax
+$then
+$   ODS2_SYNTAX = 1
+$endif
+$!
+$report_missing = 1
+$!
+$if .not. ODS2_SYNTAX
+$then
+$   set proc/parse=extended
+$endif
+$!
+$loop:
+$  ref_spec = f$search("''ref'...]*.*;",1)
+$  if ref_spec .eqs. "" then goto loop_end
+$!
+$  ref_dev = f$parse(ref_spec,,,"DEVICE")
+$  ref_dir = f$parse(ref_spec,,,"DIRECTORY")
+$  ref_dir = f$edit(ref_dir, "LOWERCASE")
+$  ref_name = f$parse(ref_spec,,,"NAME")
+$  ref_type = f$parse(ref_spec,,,"TYPE")
+$!
+$!
+$  if f$locate(".CVS]", ref_dir) .lt. f$length(ref_dir) then goto loop
+$  if f$locate(".cvs]", ref_dir) .lt. f$length(ref_dir) then goto loop
+$  if f$locate(".$cvs]", ref_dir) .lt. f$length(ref_dir) then goto loop
+$  if f$locate(".^.git", ref_dir) .lt. f$length(ref_dir) then goto loop
+$  if f$locate(".$5ngit", ref_dir) .lt. f$length(ref_dir) then goto loop
+$!
+$  rel_path = ref_dir - "[" - ref_base_dir
+$!  rel_path_len = f$length(rel_path) - 1
+$!  delim = f$extract(rel_path_len, 1, rel_path)
+$!  rel_path = rel_path - ".]" - ".>" - "]" - ">"
+$!  rel_path = rel_path + delim
+$!
+$  if ODS2_SYNTAX
+$  then
+$  endif
+$!
+$  wrk_path = wrk + rel_path
+$!
+$  ref_name_type = ref_name + ref_type
+$!
+$  if ref_name_type .eqs. "CVS.DIR" then goto loop
+$  if ref_name_type .eqs. "cvs.dir" then goto loop
+$  if ref_name_type .eqs. "$CVS.DIR" then goto loop
+$  if ref_name_type .eqs. "^.git.DIR" then goto loop
+$  if ref_name_type .eqs. "$5ngit.DIR" then goto loop
+$  if ref_name_type .eqs. "$5NGIT.DIR" then goto loop
+$  if ODS2_SYNTAX
+$  then
+$!
+$  endif
+$!
+$  wrk_spec = wrk_path + ref_name_type
+$!
+$!
+$  wrk_chk = f$search(wrk_spec, 0)
+$  if wrk_chk .eqs. ""
+$  then
+$    if report_missing
+$    then
+$      write sys$output "''wrk_spec' is missing"
+$    endif
+$    if update_file
+$    then
+$      copy/log 'ref_spec' 'wrk_spec'
+$    endif
+$    goto loop
+$  endif
+$!
+$  wrk_name = f$parse(wrk_spec,,,"NAME")
+$  wrk_type = f$parse(wrk_spec,,,"TYPE")
+$  wrk_fname = wrk_name + wrk_type"
+$  ref_fname = ref_name + ref_type
+$!
+$  if ref_fname .nes. wrk_fname
+$  then
+$    write sys$output "''wrk_spc' wrong name, should be ""''ref_fname'"""
+$  endif
+$!
+$  ref_type = f$edit(ref_type, "UPCASE")
+$  if ref_type .eqs. ".DIR" then goto loop
+$!
+$  if ODS2_SYNTAX
+$  then
+$       ref_fname = f$edit(ref_fname, "LOWERCASE")
+$  endif
+$!
+$! These files have records to long to diff, and we don't change them anyway.
+$  ref_skip = 0
+$  if ref_type .eqs. ".GMO" then ref_skip = 1
+$  if ref_type .eqs. ".PDF" then ref_skip = 1
+$  if ref_type .eqs. ".PNG" then ref_skip = 1
+$  if ref_type .eqs. ".JPG" then ref_skip = 1
+$  if ref_fname .eqs. "inftest.ok" then ref_skip = 1
+$  if ref_fname .eqs. "longsub.in" then ref_skip = 1
+$  if ref_fname .eqs. "longsub.ok" then ref_skip = 1
+$  if ref_fname .eqs. "nasty2.ok" then ref_skip = 1
+$  if ref_fname .eqs. "profile5.awk" then ref_skip = 1
+$  if ref_fname .eqs. "profile5.ok" then ref_skip = 1
+$  if ref_fname .eqs. "po.m4" then ref_skip = 1
+$!
+$!
+$  if ref_skip .ne. 0
+$  then
+$    if report_missing
+$    then
+$        write sys$output "Skipping diff of ''ref_fname'"
+$    endif
+$    goto loop
+$  endif
+$!
+$!
+$  wrk_ver = f$parse(wrk_chk,,,"VERSION")
+$  if wrk_ver .nes. ";1"
+$  then
+$    write sys$output "Version for ''wrk_spec' is not 1"
+$  endif
+$  set noon
+$  diff/out=nl: 'wrk_spec' 'ref_spec'
+$  if $severity .nes. "1"
+$  then
+$    write sys$output "''wrk_spec' is different from ''ref_spec'"
+$    if update_file
+$    then
+$       delete 'wrk_spec';*
+$       copy/log 'ref_spec' 'wrk_spec'
+$    endif
+$  endif
+$  set on
+$
+$!
+$  goto loop
+$loop_end:
+$!
+$!
+$missing_loop:
+$! For missing loop, check the latest generation.
+$  ref_spec = f$search("''wrk'...]*.*;")
+$  if ref_spec .eqs. "" then goto missing_loop_end
+$!
+$  ref_dev = f$parse(ref_spec,,,"DEVICE")
+$  ref_dir = f$parse(ref_spec,,,"DIRECTORY")
+$  ref_dir = f$edit(ref_dir, "LOWERCASE")
+$  ref_name = f$parse(ref_spec,,,"NAME")
+$  ref_type = f$parse(ref_spec,,,"TYPE")
+$!
+$  rel_path = ref_dir - "[" - wrk_base_dir
+$!
+$!
+$  wrk_path = ref + rel_path
+$  wrk_spec = wrk_path + ref_name + ref_type
+$  wrk_name = f$parse(wrk_spec,,,"NAME")
+$  wrk_type = f$parse(wrk_spec,,,"TYPE")
+$!
+$  wrk_fname = wrk_name + wrk_type"
+$  ref_fname = ref_name + ref_type
+$!
+$  wrk_skip = 0
+$  ref_utype = f$edit(ref_type,"UPCASE")
+$  ref_ufname = f$edit(ref_fname,"UPCASE")
+$!
+$!
+$  if wrk_skip .eq. 0
+$  then
+$     wrk_chk = f$search(wrk_spec, 0)
+$     if wrk_chk .eqs. ""
+$     then
+$         if report_missing
+$         then
+$             write sys$output "''wrk_spec' is missing"
+$         endif
+$         goto missing_loop
+$     endif
+$  else
+$     goto missing_loop
+$  endif
+$!
+$  if ref_fname .nes. wrk_fname
+$  then
+$    write sys$output "''wrk_spc' wrong name, should be ""''ref_fname'"""
+$  endif
+$!
+$  if ref_utype .eqs. ".DIR" then goto missing_loop
+$!
+$  wrk_ver = f$parse(wrk_chk,,,"VERSION")
+$  if wrk_ver .nes. ";1"
+$  then
+$    write sys$output "Version for ''wrk_spec' is not 1"
+$  endif
+$!
+$  goto missing_loop
+$!
+$!
+$missing_loop_end:
+$!
+$exit
diff --git a/vms/config_h.com b/vms/config_h.com
new file mode 100644
index 00000000..c1d3becf
--- /dev/null
+++ b/vms/config_h.com
@@ -0,0 +1,1661 @@
+$! File: config_h.com
+$!
+$! $Id: config_h.com,v 1.1.1.1 2012/12/02 19:25:21 wb8tyw Exp $
+$!
+$! This procedure attempts to figure out how to build a config.h file
+$! for the current project.
+$!
+$! The P1 parameter of "NOBUILTINS" inhibits the default #include <builtins.h>
+$! that is normally added.  This include can cause side effects if
+$! special VMS compiler settings are used.
+$!
+$! The CONFIGURE shell script will be examined for hints and a few symbols
+$! but most of the tests will not produce valid results on OpenVMS.  Some
+$! will produce false positives and some will produce false negatives.
+$!
+$! It is easier to just read the config.h_in file and make up tests based
+$! on what is in it!
+$!
+$! This file will create an empty config_vms.h file if one does not exist.
+$! The config_vms.h is intended for manual edits to handle things that
+$! this procedure can not.
+$!
+$! The config_vms.h will be invoked by the resulting config.h file.
+$!
+$! This procedure knows about the DEC C RTL on the system it is on.
+$! Future versions may be handle the GNV, the OpenVMS porting library,
+$! and others.
+$!
+$! This procedure may not guess the options correctly for all architectures,
+$! and is a work in progress.
+$!
+$! Copyright (C) 2014 the Free Software Foundation, Inc.
+$!
+$! This file is part of GAWK, the GNU implementation of the
+$! AWK Progamming Language.
+$!
+$! GAWK is free software; you can redistribute it and/or modify
+$! it under the terms of the GNU General Public License as published by
+$! the Free Software Foundation; either version 3 of the License, or
+$! (at your option) any later version.
+$!
+$! GAWK is distributed in the hope that it will be useful,
+$! but WITHOUT ANY WARRANTY; without even the implied warranty of
+$! MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+$! GNU General Public License for more details.
+$!
+$! You should have received a copy of the GNU General Public License
+$! along with this program; if not, write to the Free Software
+$! Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301,
+$! USA
+$!
+$! Per assignment agreement with FSF, similar procedures may be present
+$! in other packages under other licensing agreements and copyrights
+$!
+$! 15-Jan-2001	J. Malmberg	Original
+$! 29-Apr-2001	J. Malmberg	Also look for config.*in* in a [.include]
+$!				subdirectory
+$! 30-Apr-2001	J. Malmberg	Update for SAMBA checks
+$! 09-Apr-2005	J. Malmberg	Update for RSYNC and large file.
+$! 29-Sep-2011	J. Malmberg	Update for Bash 4.2
+$! 01-Mar-2012	J. Malmberg	Warn about getcwd(0,0)
+$! 21-Dec-2012	J. Malmberg	Update for gawk
+$!============================================================================
+$!
+$ss_normal = 1
+$ss_abort = 44
+$ss_control_y = 1556
+$status = ss_normal
+$on control_y then goto control_y
+$on warning then goto general_error
+$!
+$! Some information for writing timestamps to created files
+$!----------------------------------------------------------
+$my_proc = f$environment("PROCEDURE")
+$my_proc_file = f$parse(my_proc,,,"NAME") + f$parse(my_proc,,,"TYPE")
+$tab[0,8] = 9
+$datetime = f$element(0,".",f$cvtime(,"ABSOLUTE","DATETIME"))
+$username = f$edit(f$getjpi("","USERNAME"),"TRIM")
+$!
+$pid = f$getjpi("","PID")
+$tfile1 = "SYS$SCRATCH:config_h_temp1_''pid'.TEMP"
+$dchfile = "SYS$SCRATCH:config_h_decc_''pid'.TEMP"
+$configure_script = "SYS$SCRATCH:configure_script_''pid'.TEMP"
+$!
+$!  Get the system type
+$!----------------------
+$arch_type = f$getsyi("arch_type")
+$!
+$! Does config_vms.h exist?
+$!-------------------------
+$update_config_vms = 0
+$file = f$search("sys$disk:[]config_vms.h")
+$if file .nes. ""
+$then
+$   write sys$output "Found existing custom file ''file'."
+$else
+$   update_config_vms = 1
+$   write sys$output "Creating new sys$disk:[]config_vms.h for you."
+$   gosub write_config_vms
+$endif
+$!
+$!
+$! On some platforms, DCL search has problems with searching a file
+$! on a NFS mounted volume.  So copy it to sys$scratch:
+$!
+$if f$search(configure_script) .nes. "" then delete 'configure_script';*
+$copy PRJ_ROOT:configure 'configure_script'
+$!
+$!
+$! Write out the header
+$!----------------------
+$gosub write_config_h_header
+$!
+$!
+$!
+$! config.h.in could have at least five different names depending
+$! on how it was transferred to OpenVMS
+$!------------------------------------------------------------------
+$cfile = f$search("sys$disk:[]config.h.in")
+$if cfile .eqs. ""
+$then
+$   cfile = f$search("sys$disk:[]config.h_in")
+$   if cfile .eqs. ""
+$   then
+$	cfile = f$search("sys$disk:[]configh.in")
+$	if cfile .eqs. ""
+$	then
+$	    cfile = f$search("sys$disk:[]config__2eh.in")
+$	    if cfile .eqs. ""
+$	    then
+$		cfile = f$search("sys$disk:[]config.h__2ein")
+$	    endif
+$	endif
+$   endif
+$endif
+$if f$trnlnm("PRJ_INCLUDE") .nes. ""
+$then
+$   cfile = f$search("PRJ_INCLUDE:config.h.in")
+$   if cfile .eqs. ""
+$   then
+$	cfile = f$search("PRJ_INCLUDE:config.h_in")
+$	if cfile .eqs. ""
+$	then
+$	    cfile = f$search("PRJ_INCLUDE:config__2eh.in")
+$	    if cfile .eqs. ""
+$	    then
+$		cfile = f$search("PRJ_INCLUDE:config__2eh.in")
+$		if cfile .eqs. ""
+$		then
+$		    cfile = f$search("PRJ_INCLUDE:config.h__2ein")
+$		endif
+$	    endif
+$	endif
+$    endif
+$endif
+$if cfile .eqs. ""
+$then
+$   write sys$output "Can not find sys$disk:config.h.in"
+$   line_out = "Looked for config.h.in, config.h_in, configh.in, "
+$   line_out = line_out + "config__2eh.in, "config.h__2ein"
+$   write/symbol sys$output line_out
+$   if f$trnlnm("PRJ_INCLUDE") .nes. ""
+$   then
+$	write sys$output "Also looked in PRJ_INCLUDE: for these files."
+$   endif
+$!
+$   write tf ""
+$   write tf -
+	"   /* Could not find sys$disk:config.h.in                           */"
+$   write tf -
+	"  /*  Looked also for config.h_in, configh.in, config__2eh.in,     */"
+$   write tf -
+	" /*   config.h__2ein						   */"
+$   if f$trnlnm("PRJ_INCLUDE") .nes. ""
+$   then
+$	write tf -
+	" /* Also looked in PRJ_INCLUDE: for these files.		  */"
+$   endif
+$   write tf -
+	"/*--------------------------------------------------------------*/
+$   write tf ""
+$   goto write_tail
+$endif
+$!
+$!
+$! Locate the DECC libraries in use
+$!-----------------------------------
+$decc_rtldef = f$parse("decc$rtldef","sys$library:.tlb;0")
+$decc_shr = f$parse("decc$shr","sys$share:.exe;0")
+$!
+$! Dump the DECC header names into a file
+$!----------------------------------------
+$if f$search(dchfile) .nes. "" then delete 'dchfile';*
+$if f$search(tfile1) .nes. "" then delete 'tfile1';*
+$define/user sys$output 'tfile1'
+$library/list 'decc_rtldef'
+$open/read/error=rtldef_loop1_end tf1 'tfile1'
+$open/write/error=rtldef_loop1_end tf2 'dchfile'
+$rtldef_loop1:
+$   read/end=rtldef_loop1_end tf1 line_in
+$   line_in = f$edit(line_in,"TRIM,COMPRESS")
+$   key1 = f$element(0," ",line_in)
+$   key2 = f$element(1," ",line_in)
+$   if key1 .eqs. " " .or. key1 .eqs. "" then goto rtldef_loop1
+$   if key2 .nes. " " .and. key2 .nes. "" then goto rtldef_loop1
+$   write tf2 "|",key1,"|"
+$   goto rtldef_loop1
+$rtldef_loop1_end:
+$if f$trnlnm("tf1","lnm$process",,"SUPERVISOR") .nes. "" then close tf1
+$if f$trnlnm("tf2","lnm$process",,"SUPERVISOR") .nes. "" then close tf2
+$if f$search(tfile1) .nes. "" then delete 'tfile1';*
+$!
+$!
+$! Now calculate what should be in the file from reading
+$! config.h.in and CONFIGURE.
+$!---------------------------------------------------------------
+$open/read inf 'cfile'
+$do_comment = 0
+$if_block = 0
+$cfgh_in_loop1:
+$!set nover
+$   read/end=cfgh_in_loop1_end inf line_in
+$   xline = f$edit(line_in,"TRIM,COMPRESS")
+$!
+$!  Blank line handling
+$!---------------------
+$   if xline .eqs. ""
+$   then
+$	write tf ""
+$	goto cfgh_in_loop1
+$   endif
+$   xlen = f$length(xline)
+$   key = f$extract(0,2,xline)
+$!
+$!  deal with comments by copying exactly
+$!-----------------------------------------
+$   if (do_comment .eq. 1) .or. (key .eqs. "/*")
+$   then
+$	do_comment = 1
+$	write tf line_in
+$	key = f$extract(xlen - 2, 2, xline)
+$	if key .eqs. "*/" then do_comment = 0
+$	goto cfgh_in_loop1
+$   endif
+$!
+$!  Some quick parsing
+$!----------------------
+$   keyif = f$extract(0,3,xline)
+$   key1 = f$element(0," ",xline)
+$   key2 = f$element(1," ",xline)
+$   key2a = f$element(0,"_",key2)
+$   key2b = f$element(1,"_",key2)
+$   key2_len = f$length(key2)
+$   key2_h = f$extract(key2_len - 2, 2, key2)
+$   key2_t = f$extract(key2_len - 5, 5, key2)
+$   if key2_t .eqs. "_TYPE" then key2_h = "_T"
+$   key64 = 0
+$   if f$locate("64", xline) .lt. xlen then key64 = 1
+$!
+$!write sys$output "xline = ''xline'"
+$!
+$!  Comment out this section of the ifblock
+$!-----------------------------------------
+$   if if_block .ge. 3
+$   then
+$	write tf "/* ", xline, " */"
+$	if keyif .eqs. "#en" then if_block = 0
+$	goto cfgh_in_loop1
+$   endif
+$!
+$!  Handle the end of an ifblock
+$!-------------------------------
+$   if keyif .eqs. "#en"
+$   then
+$	write tf xline
+$	if_block = 0
+$	goto cfgh_in_loop1
+$   endif
+$!
+$   if key1 .eqs. "#ifndef"
+$   then
+$!	Manual check for _ALL_SOURCE on AIX error
+$!-----------------------------------------------
+$	if key2 .eqs. "_ALL_SOURCE"
+$	then
+$	   write tf "/* ", xline, " */"
+$!
+$!	   Ignore the rest of the block
+$!--------------------------------------
+$	   if_block = 3
+$	   goto cfgh_in_loop1
+$	endif
+$   endif
+$!
+$!
+$!  Default action for an #if/#else/#endif
+$!------------------------------------------
+$   if keyif .eqs. "#if" .or. keyif .eqs. "#el"
+$   then
+$	if_block = 1
+$	write tf xline
+$	goto cfgh_in_loop1
+$   endif
+$!
+$!
+$!  Process "normal?" stuff
+$!---------------------------
+$   if key1 .eqs. "#undef"
+$   then
+$	key2c = f$element(2, "_", key2)
+$	if (key2c .eqs. "_") .or. (key2c .eqs. "H") then key2c = ""
+$	key2d = f$element(3, "_", key2)
+$	if (key2d .eqs. "_") .or. (key2d .eqs. "H") then key2d = ""
+$	key2e = f$element(4, "_", key2)
+$	if (key2e .eqs. "_") .or. (key2e .eqs. "H") then key2e = ""
+$	if key2d .eqs. "T"
+$	then
+$	    if key2e .eqs. "TYPE"
+$	    then
+$		key2_h = "_T"
+$		key2d = ""
+$	    endif
+$	endif
+$!
+$	double_under = 0
+$!
+$	if key2 .eqs. "bits16_t"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' short"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "u_bits16_t"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' unsigned short"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "bits32_t"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' int"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "u_bits32_t"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' unsigned int"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "intmax_t"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#ifdef __VAX"
+$	    write tf "#define ''key2' long"
+$	    write tf "#else"
+$	    write tf "#define ''key2' long long"
+$	    write tf "#endif"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "uintmax_t"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#ifdef __VAX"
+$	    write tf "#define ''key2' unsigned long"
+$	    write tf "#else"
+$	    write tf "#define ''key2' unsigned long long"
+$	    write tf "#endif"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "socklen_t"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' int"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "GETGROUPS_T"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' gid_t"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_SYS_SIGLIST"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 0"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_SYS_ERRLIST"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_STRUCT_DIRENT_D_INO"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	! The header files have this information, however
+$!      ! The ioctl() call only works on sockets.
+$!	if key2 .eqs. "FIONREAD_IN_SYS_IOCTL"
+$!	then
+$!	    write tf "#ifndef ''key2'"
+$!	    write tf "#define ''key2' 1"
+$!	    write tf "#endif"
+$!	    goto cfgh_in_loop1
+$!	endif
+$!
+$!	! The header files have this information, however
+$!      ! The ioctl() call only works on sockets.
+$!	if key2 .eqs. "GWINSZ_IN_SYS_IOCTL"
+$!	then
+$!	    write tf "#ifndef ''key2'"
+$!	    write tf "#define ''key2' 1"
+$!	    write tf "#endif"
+$!	    goto cfgh_in_loop1
+$!	endif
+$!
+$!	! The header files have this information, however
+$!      ! The ioctl() call only works on sockets.
+$!	if key2 .eqs. "STRUCT_WINSIZE_IN_SYS_IOCTL"
+$!	then
+$!	    write tf "#ifndef ''key2'"
+$!	    write tf "#define ''key2' 0"
+$!	    write tf "#endif"
+$!	    goto cfgh_in_loop1
+$!	endif
+$!
+$	if key2 .eqs. "HAVE_STRUCT_TM_TM_ZONE"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_TM_ZONE"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_TIMEVAL"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_TZNAME"
+$	then
+$	    write tf "#if __CRTL_VER >= 70000000"
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "WEXITSTATUS_OFFSET"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 2"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_GETPW_DECLS"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_CONFSTR"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_PRINTF"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_SBRK"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_STRSIGNAL"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 0"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2a .eqs. "HAVE_DECL_STRTOLD"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 0"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_STRTOIMAX"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 0"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_STRTOL"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_STRTOLL"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_STRTOUL"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_STRTOULL"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_STRTOUMAX"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 0"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "GETPGRP_VOID"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "NAMED_PIPES_MISSING"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "OPENDIR_NOT_ROBUST"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "PGRP_PIPE"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "CAN_REDEFINE_GETENV"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_PRINTF_A_FORMAT"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "CTYPE_NON_ASCII"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_LANGINFO_CODESET"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_LC_MESSAGES"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!      This wants execve() to do this automagically to pass.
+$!	if key2 .eqs. "HAVE_HASH_BANG_EXEC"
+$!	then
+$!	    write tf "#ifndef ''key2'"
+$!	    write tf "#define ''key2' 1"
+$!	    write tf "#endif"
+$!	    goto cfgh_in_loop1
+$!	endif
+$!
+$	if key2 .eqs. "ICONV_CONST"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2'"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "VOID_SIGHANDLER"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_POSIX_SIGNALS"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "UNUSABLE_RT_SIGNALS"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2a .eqs. "HAVE_DECL_FPURGE"
+$	then
+$	    write tf "#ifndef ''key2a'"
+$	    write tf "#define ''key2a' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_DECL_SETREGID"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_POSIX_SIGSETJMP"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "HAVE_LIBDL"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "STRCOLL_BROKEN"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2 .eqs. "DUP_BROKEN"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	This is for a test that getcwd(0,0) works.
+$!	It does not on VMS.
+$!--------------------------
+$	if key2 .eqs. "GETCWD_BROKEN"
+$	then
+$	    write sys$output ""
+$	    write sys$output -
+  "%CONFIG_H-I-NONPORT, ''key2' being tested for!"
+$		   write sys$output -
+ "-CONFIG_H-I-GETCWD, GETCWD(0,0) does not work on VMS."
+$		   write sys$output -
+ "-CONFIG_H-I-GETCWD2, Work around hack probably required."
+$		   write sys$output -
+ "-CONFIG_H-I-REVIEW, Manual Code review required!"
+$		    if update_config_vms
+$		    then
+$			open/append tfcv sys$disk:[]config_vms.h
+$			write tfcv ""
+$			write tfcv -
+		"/* Check config.h for use of ''key2' settings */"
+$			write tfcv ""
+$			close tfcv
+$		    endif
+$
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$	if key2a .eqs. "HAVE" .or. key2a .eqs. "STAT"
+$	then
+$!
+$!	    Process extra underscores
+$!------------------------------------
+$	    if f$locate("HAVE___", key2) .lt. key2_len
+$	    then
+$		key2b = "__" + key2d
+$		key2d = ""
+$		double_under = 1
+$	    else
+$		if f$locate("HAVE__", key2) .lt. key2_len
+$		then
+$		    key2b = "_" + key2c
+$		    key2c = ""
+$		    double_under = 1
+$		endif
+$	    endif
+$!
+$	    if key2_h .eqs. "_H"
+$	    then
+$!
+$!		Looking for a header file
+$!---------------------------------------
+$		headf = key2b
+$		if key2c .nes. "" then headf = headf + "_" + key2c
+$		if key2d .nes. "" then headf = headf + "_" + key2d
+$!
+$!		   (key2b .eqs. "READLINE")
+$!
+$!		Some special parsing
+$!------------------------------------------
+$		if (key2b .eqs. "SYS") .or. (key2b .eqs. "ARPA") .or. -
+		   (key2b .eqs. "NET") .or. (key2b .eqs. "NETINET")
+$		then
+$		    if key2c .nes. ""
+$		    then
+$			headf = key2c
+$			if key2d .nes. "" then headf = key2c + "_" + key2d
+$		    endif
+$		endif
+$!
+$!		And of course what's life with out some special cases
+$!--------------------------------------------------------------------
+$		if key2b .eqs. "FILE"
+$		then
+$		   write sys$output ""
+$		   write sys$output -
+  "%CONFIG_H-I-NONPORT, ''key2' being asked for!"
+$		   write sys$output -
+ "-CONFIG_H-I-FILE_OLD, file.h will not be configured as is obsolete!"
+$		   write sys$output -
+ "-CONFIG_H_I-FCNTL_NEW, "Expecting fcntl.h to be configured instead!"
+$		   write sys$output -
+ "-CONFIG_H_I-FCNTL_CHK, "Unable to verify at this time!"
+$		   write sys$output -
+ "-CONFIG_H-I-REVIEW, Manual Code review required!"
+$!
+$		    if update_config_vms
+$		    then
+$			open/append tfcv sys$disk:[]config_vms.h
+$			write tfcv ""
+$			write tfcv -
+		"/* Check config.h for use of fcntl.h instead of file.h */"
+$			write tfcv ""
+$			close tfcv
+$		    endif
+$		endif
+$!
+$!		Now look it up in the DEC C RTL
+$!---------------------------------------------
+$		define/user sys$output nl:
+$		define/user sys$error nl:
+$		search/output=nl: 'dchfile' |'headf'|/exact
+$		if '$severity' .eq. 1
+$		then
+$		    if key64 then write tf "#ifndef __VAX"
+$		    write tf "#ifndef ''key2'"
+$		    write tf "#define ''key2' 1"
+$if p2 .nes. "" then write sys$output "''dchfile' - #define ''key2' 1"
+$		    write tf "#endif"
+$		    if key64 then write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$	    else
+$!
+$!		Looking for a routine or a symbol
+$!------------------------------------------------
+$		if key2c .eqs. "MACRO"
+$		then
+$		    if (key2b .eqs. "FILE") .or. (key2b .eqs. "DATE") -
+			.or. (key2b .eqs. "LINE") .or. (key2b .eqs. "TIME")
+$		    then
+$			write tf "#ifndef HAVE_''key2b'"
+$			write tf "#define HAVE_''key2b' 1"
+$			write tf "#endif"
+$		    endif
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$!		Special false tests
+$!-------------------------------------
+$		if double_under
+$		then
+$		    if key2b .eqs. "_FCNTL" .or. key2b .eqs. "__FCNTL"
+$		    then
+$			write tf "/* #undef HAVE_''key2b' */"
+$			goto cfgh_in_loop1
+$		    endif
+$!
+$		    if key2b .eqs. "_STAT" .or. key2b .eqs. "__STAT"
+$		    then
+$			write tf "/* #undef HAVE_''key2b' */"
+$			goto cfgh_in_loop1
+$		    endif
+$!
+$		    if key2b .eqs. "_READ" .or. key2b .eqs. "__READ"
+$		    then
+$			write tf "/* #undef HAVE_''key2b' */"
+$			goto cfgh_in_loop1
+$		    endif
+$		endif
+$!
+$		keysym = key2b
+$		if key2c .nes. "" then keysym = keysym + "_" + key2c
+$		if key2d .nes. "" then keysym = keysym + "_" + key2d
+$		if key2e .nes. "" then keysym = keysym + "_" + key2e
+$!
+$!
+$!		Stat structure members
+$!-------------------------------------
+$		if key2b .eqs. "STRUCT"
+$		then
+$		    if key2c .eqs. "STAT" .and (key2d .nes. "")
+$		    then
+$			key2b = key2b + "_" + key2c + "_" + key2d
+$			key2c = key2e
+$			key2d = ""
+$			key2e = ""
+$		    endif
+$		endif
+$		if (key2b .eqs. "ST") .or. (key2b .eqs. "STRUCT_STAT_ST")
+$		then
+$		    keysym = "ST" + "_" + key2c
+$		    keysym = f$edit(keysym,"LOWERCASE")
+$		endif
+$		if key2a .eqs. "STAT"
+$		then
+$		    if (f$locate("STATVFS", key2b) .eq. 0) .and. key2c .eqs. ""
+$		    then
+$			keysym = f$edit(key2b, "LOWERCASE")
+$		    endif
+$!$		    if (key2b .eqs. "STATVFS" .or. key2b .eqs. "STATFS2" -
+$!			.or. key2b .eqs. "STATFS3") .and. key2c .nes. ""
+$!
+$		    if (key2b .eqs. "STATVFS") .and. key2c .nes. ""
+$		    then
+$!			Should really verify that the structure
+$!			named by key2b actually exists first.
+$!------------------------------------------------------------
+$!
+$!			Statvfs structure members
+$!-------------------------------------------------
+$			keysym = "f_" + f$edit(key2c,"LOWERCASE")
+$		    endif
+$		endif
+$!
+$!		UTMPX structure members
+$!--------------------------------------
+$		if key2b .eqs. "UT" .and. key2c .eqs. "UT"
+$		then
+$		    keysym = "ut_" + f$edit(key2d,"LOWERCASE")
+$		endif
+$!
+$		if f$locate("MMAP",key2) .lt. key2_len
+$		then
+$		   write sys$output ""
+$		   write sys$output -
+  "%CONFIG_H-I-NONPORT, ''key2' being asked for!"
+$		   write sys$output -
+ "-CONFIG_H-I-MMAP, MMAP operations only work on STREAM and BINARY files!"
+$		   write sys$output -
+ "-CONFIG_H-I-REVIEW, Manual Code review required!"
+$		    if update_config_vms
+$		    then
+$			open/append tfcv sys$disk:[]config_vms.h
+$			write tfcv ""
+$			write tfcv -
+		"/* Check config.h for use of ''key2' settings */"
+$			write tfcv ""
+$			close tfcv
+$		    endif
+$		endif
+$!
+$!
+$		if keysym .eqs. "CRYPT"
+$		then
+$		   write sys$output ""
+$		   write sys$output -
+  "%CONFIG_H-I-NONPORT, ''key2' being asked for!"
+$		   write sys$output -
+ "-CONFIG_H-I-CRYPT, CRYPT operations on the VMS SYSUAF may not work!"
+$		   write sys$output -
+ "-CONFIG_H-I-REVIEW, Manual Code review required!"
+$		    if update_config_vms
+$		    then
+$			open/append tfcv sys$disk:[]config_vms.h
+$			write tfcv ""
+$			write tfcv -
+		"/* Check config.h for use of ''keysym' */"
+$			write tfcv ""
+$			close tfcv
+$		    endif
+$		endif
+$!
+$!
+$		if keysym .eqs. "EXECL"
+$		then
+$		   write sys$output ""
+$		   write sys$output -
+  "%CONFIG_H-I-NONPORT, ''key2' being asked for!"
+$		   write sys$output -
+ "-CONFIG_H-I-EXCEL, EXECL configured, Will probably not work."
+$		   write sys$output -
+ "-CONFIG_H-I-REVIEW, Manual Code review required!"
+$		    if update_config_vms
+$		    then
+$			open/append tfcv sys$disk:[]config_vms.h
+$			write tfcv ""
+$			write tfcv -
+		"/* Check config.h for use of ''keysym' */"
+$			write tfcv ""
+$			close tfcv
+$		    endif
+$		endif
+$!
+$!
+$!		Process if cpp supports ANSI-C stringizing '#' operator
+$!-----------------------------------------------------------------------
+$		if keysym .eqs. "STRINGIZE"
+$		then
+$		    write tf "#ifndef HAVE_STRINGIZE"
+$		    write tf "#define HAVE_STRINGSIZE 1"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$		if keysym .eqs. "VOLATILE"
+$		then
+$		    write tf "#ifndef HAVE_VOLATILE"
+$		    write tf "#define HAVE_VOLATILE 1"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$		if keysym .eqs. "ALLOCA"
+$		then
+$		    write tf "#ifndef HAVE_ALLOCA"
+$		    write tf "#define HAVE_ALLOCA 1"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$		if keysym .eqs. "ERRNO_DECL"
+$		then
+$		    write tf "#ifndef HAVE_ERRNO_DECL"
+$		    write tf "#define HAVE_ERRNO_DECL 1"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$		if keysym .eqs. "LONGLONG"
+$		then
+$		    write tf "#ifndef __VAX"
+$		    write tf "#pragma message disable longlongtype"
+$		    write tf "#ifndef HAVE_LONGLONG"
+$		    write tf "#define HAVE_LONGLONG 1"
+$		    write tf "#endif"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$!		May need to test compiler version
+$!-----------------------------------------------
+$		if (keysym .eqs. "LONG_LONG") .or. -
+                   (keysym .eqs. "LONG_LONG_INT")
+$		then
+$		    write tf "#ifndef __VAX"
+$		    write tf "#pragma message disable longlongtype"
+$		    write tf "#ifndef HAVE_''keysym'"
+$		    write tf "#define HAVE_''keysym' 1"
+$		    write tf "#endif"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$!		May need to test compiler version
+$!-----------------------------------------------
+$		if keysym .eqs. "UNSIGNED_LONG_LONG"
+$		then
+$		    write tf "#ifndef __VAX"
+$		    write tf "#pragma message disable longlongtype"
+$		    write tf "#ifndef HAVE_UNSIGNED_LONG_LONG"
+$		    write tf "#define HAVE_UNSIGNED_LONG_LONG 1"
+$		    write tf "#endif"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$!		May need to test compiler version
+$!-----------------------------------------------
+$		if keysym .eqs. "UNSIGNED_LONG_LONG_INT"
+$		then
+$		    write tf "#ifndef __VAX"
+$		    write tf "#pragma message disable longlongtype"
+$		    write tf "#ifndef HAVE_UNSIGNED_LONG_LONG_INT"
+$		    write tf "#define HAVE_UNSIGNED_LONG_LONG_INT 1"
+$		    write tf "#endif"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$!		May need to test compiler version
+$!-----------------------------------------------
+$		if keysym .eqs. "LONG_DOUBLE"
+$		then
+$		    write tf "#ifndef __VAX"
+$		    write tf "#pragma message disable longlongtype"
+$		    write tf "#ifndef HAVE_LONG_DOUBLE"
+$		    write tf "#define HAVE_LONG_DOUBLE 1"
+$		    write tf "#endif"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$		if keysym .eqs. "FCNTL_LOCK"
+$		then
+$		    write sys$output -
+  "%CONFIG_H-I-NONPORT, ''key2' being asked for!
+$		   write sys$output -
+ "-CONFIG_H-I-REVIEW, Manual Code review required!"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$!
+$!		These libraries are provided by the DEC C RTL
+$!-------------------------------------------------------------
+$		if keysym .eqs. "LIBINET" .or. keysym .eqs. "LIBSOCKET"
+$		then
+$		    write tf "#ifndef HAVE_''keysym'"
+$		    write tf "#define HAVE_''keysym' 1"
+$if p2 .nes. "" then write sys$output "''decc_shr' #define ''keysym' 1"
+$		    write tf "#endif
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$!
+$		if keysym .eqs. "HERRNO" then keysym = "h_errno"
+$		if keysym .eqs. "UTIMBUF" then keysym = "utimbuf"
+$		if key2c .eqs. "STRUCT"
+$		then
+$		    keysym = f$edit(key2d,"LOWERCASE")
+$		else
+$		    if key2_h .eqs. "_T"
+$		    then
+$			if key2_t .eqs. "_TYPE"
+$			then
+$			    keysym = f$extract(0, key2_len - 5, key2) - "HAVE_"
+$			endif
+$			keysym = f$edit(keysym,"LOWERCASE")
+$		    endif
+$		endif
+$!
+$!		Check the DEC C RTL shared image first
+$!------------------------------------------------------
+$		if f$search(tfile1) .nes. "" then delete 'tfile1';*
+$		define/user sys$output nl:
+$		define/user sys$error nl:
+$		search/format=nonull/out='tfile1' 'decc_shr' 'keysym'
+$		if '$severity' .eq. 1
+$		then
+$!
+$!		    Not documented, but from observation
+$!------------------------------------------------------
+$		    define/user sys$output nl:
+$		    define/user sys$error nl:
+$		    if arch_type .eq. 3
+$		    then
+$			keyterm = "''keysym'<SOH>"
+$		    else
+$			if arch_type .eq. 2
+$			then
+$			    keyterm = "''keysym'<BS>"
+$			else
+$			    keyterm = "''keysym'<STX>"
+$			endif
+$		    endif
+$		    search/out=nl: 'tfile1' -
+   "$''keyterm'","$g''keyterm'","$__utc_''keyterm'",-
+   "$__utctz_''keyterm'","$__bsd44_''keyterm'","$bsd_''keyterm'",-
+   "$''keysym'decc$","$G''keysym'decc$","$GX''keyterm'"
+$		    severity = '$severity'
+$!
+$!
+$!		    Of course the 64 bit stuff is different
+$!---------------------------------------------------------
+$		    if severity .ne. 1 .and. key64
+$		    then
+$			define/user sys$output nl:
+$		        define/user sys$error nl:
+$			search/out=nl: 'tfile1' "$_''keyterm'"
+$!			search/out 'tfile1' "$_''keyterm'"
+$			severity = '$severity'
+$		    endif
+$!
+$!		    UNIX compatability routines
+$!---------------------------------------------
+$		    if severity .ne. 1
+$		    then
+$			define/user sys$output nl:
+$			define/user sys$error nl:
+$			search/out=nl: 'tfile1' -
+    "$__unix_''keyterm'","$__vms_''keyterm'","$_posix_''keyterm'"
+$			severity = '$severity'
+$		    endif
+$!
+$!		    VAX special handling routines
+$!---------------------------------------------
+$		    if (severity .ne. 1) .and. (arch_type .eq. 1)
+$		    then
+$			define/user sys$output nl:
+$			define/user sys$error nl:
+$			search/out=nl: 'tfile1' "DECC$''keysym'<SOH>"
+$			severity = '$severity'
+$		    endif
+$!
+$!		    Show the result of the search
+$!------------------------------------------------
+$		    if 'severity' .eq. 1
+$		    then
+$			if key64 then write tf "#ifndef __VAX"
+$			write tf "#ifndef ''key2'"
+$			write tf "#define ''key2' 1"
+$if p2 .nes. "" then write sys$output "''decc_shr' #define ''key2' 1"
+$			write tf "#endif"
+$			if key64 then write tf "#endif"
+$			goto cfgh_in_loop1
+$		    endif
+$		endif
+$		if f$search(tfile1) .nes. "" then delete 'tfile1';*
+$!
+$!		Check the DECC Header files next
+$!----------------------------------------------
+$		define/user sys$output nl:
+$		define/user sys$error nl:
+$		search/out=nl: 'decc_rtldef' -
+		    "''keysym';", "''keysym'[", "struct ''keysym'"/exact
+$		severity = '$severity'
+$		if severity .eq. 1
+$		then
+$		    if key64 then write tf "#ifndef __VAX"
+$		    write tf "#ifndef ''key2'"
+$		    write tf "#define ''key2' 1"
+$if p2 .nes. "" then write sys$output "''decc_rtldef' #define ''key2' 1"
+$		    write tf "#endif"
+$		    if key64 then write tf "#endif"
+$		    goto cfgh_in_loop1
+$		endif
+$!
+$	    endif
+$	    write tf "/* ", xline, " */"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!
+$!	Process SIZEOF directives found in SAMBA
+$!------------------------------------------------
+$	if key2a .eqs. "SIZEOF"
+$	then
+$	    if key2b .eqs. "INO" .and. key2_h .eqs. "_T"
+$	    then
+$		write tf "#ifndef SIZEOF_INO_T"
+$		write tf "#define SIZEOF_INO_T (6)"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    if key2b .eqs. "INTMAX" .and. key2_h .eqs. "_T"
+$	    then
+$		write tf "#ifndef SIZEOF_INTMAX_T"
+$		write tf "#ifdef __VAX"
+$		write tf "#define SIZEOF_INTMAX_T (4)"
+$		write tf "#else"
+$		write tf "#define SIZEOF_INTMAX_T (8)"
+$		write tf "#endif"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    if key2b .eqs. "OFF" .and. key2_h .eqs. "_T"
+$	    then
+$		write tf "#ifndef SIZEOF_OFF_T"
+$		write tf "#ifdef __VAX"
+$		write tf "#define SIZEOF_OFF_T (4)"
+$		write tf "#else"
+$		write tf "#define SIZEOF_OFF_T (8)"
+$		write tf "#endif"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    if key2b .eqs. "CHAR" .and. key2_h .eqs. "_P"
+$	    then
+$		write tf "#ifndef SIZEOF_CHAR_P"
+$		write tf "#define SIZEOF_CHAR_P (4)"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    if (key2b .eqs. "INT")
+$	    then
+$		write tf "#ifndef SIZEOF_''key2b'"
+$		write tf "#define SIZEOF_''key2b' (4)"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    if key2b .eqs. "UNSIGNED"
+$	    then
+$               if key2c .eqs. "INT" .or. key2c .eqs. "LONG"
+$               then
+$		    write tf "#ifndef SIZEOF_''key2b'_''key2c'"
+$		    write tf "#define SIZEOF_''key2b'_''key2c' (4)"
+$		    write tf "#endif"
+$		    goto cfgh_in_loop1
+$               endif
+$	    endif
+$	    if key2b .eqs. "DOUBLE"
+$	    then
+$		write tf "#ifndef SIZEOF_DOUBLE"
+$		write tf "#define SIZEOF_DOUBLE (8)"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    if key2b .eqs. "LONG"
+$	    then
+$		if key2c .eqs. ""
+$		then
+$		    write tf "#ifndef SIZEOF_LONG"
+$		    write tf "#define SIZEOF_LONG (4)"
+$		    write tf "#endif"
+$		else
+$		    write tf "#ifndef SIZEOF_LONG_LONG"
+$		    write tf "#ifndef __VAX"
+$		    write tf "#define SIZEOF_LONG_LONG (8)"
+$		    write tf "#endif"
+$		    write tf "#endif"
+$		endif
+$		goto cfgh_in_loop1
+$	    endif
+$	    if key2b .eqs. "SHORT"
+$	    then
+$		write tf "#ifndef SIZEOF_SHORT"
+$		write tf "#define SIZEOF_SHORT (2)"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    write tf "/* ", xline, " */"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	Process NEED directives
+$!-------------------------------
+$	if key2a .eqs. "NEED"
+$	then
+$	    if key2b .eqs. "STRINGS" .and. key2_h .eqs. "_H"
+$	    then
+$		write tf "#ifndef NEED_STRINGS_H"
+$		write tf "#define NEED_STRINGS_H 1"
+$		write tf "#endif"
+$		goto cfgh_in_loop1
+$	    endif
+$	    write tf "/* ", xline, " */"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!
+$!	Process STATFS directives
+$!-------------------------------
+$!	if key2a .eqs. "STATFS"
+$!	then
+$!	    write tf "/* ", xline, " */"
+$!	    goto cfgh_in_loop1
+$!	endif
+$!
+$!	Process inline directive
+$!------------------------------
+$	if key2 .eqs. "inline"
+$	then
+$	    write tf "#ifndef inline"
+$	    write tf "#define inline __inline"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	Process restrict directive
+$!--------------------------------
+$	if key2 .eqs. "restrict"
+$	then
+$	    write tf "#ifndef restrict"
+$	    write tf "#define restrict __restrict"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	Process RETSIGTYPE directive
+$!----------------------------------
+$	if key2 .eqs. "RETSIGTYPE"
+$	then
+$	    write tf "#ifndef RETSIGTYPE"
+$	    write tf "#define RETSIGTYPE void"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	Process STDC_HEADERS (SAMBA!)
+$!---------------------------
+$	if key2 .eqs. "STDC_HEADERS"
+$	then
+$	    write tf "#ifndef STDC_HEADERS"
+$	    write tf "#define STDC_HEADERS 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	Process PROTOTYPES directive
+$!-------------------------------------
+$	if key2 .eqs. "PROTOTYPES"
+$	then
+$	    write tf "#ifndef PROTOTYPES"
+$	    write tf "#define PROTOTYPES 1"
+$	    write tf "#endif"
+$	    goto cfgh_in_loop1
+$	endif
+$!
+$!	Special for SEEKDIR_RETURNS_VOID
+$!---------------------------------------
+$	if key2 .eqs. "SEEKDIR_RETURNS_VOID"
+$	then
+$	    write tf "#ifndef SEEKDIR_RETURNS_VOID"
+$	    write tf "#define SEEKDIR_RETURNS_VOID 1"
+$	    write tf "#endif"
+$	endif
+$!
+$!      TIME_WITH_SYS_TIME note:  On VMS time.h and sys/time.h are same module.
+$!
+$!      TIME_T_IN_SYS_TYPES_H
+$!------------------------------
+$	if key2 .eqs. "TIME_T_IN_TYPES_H"
+$	then
+$	    write tf "#ifndef ''key2'"
+$	    write tf "#define ''key2' 1"
+$	    write tf "#endif"
+$	endif
+$!
+$!	Unknown - See if CONFIGURE can give a clue for this
+$!----------------------------------------------------------
+$	pflag = 0
+$	set_flag = 0
+$!	gproj_name = proj_name - "_VMS" - "-VMS"
+$	if f$search(tfile1) .nes. "" then delete 'tfile1';*
+$	define/user sys$output nl:
+$	define/user sys$error nl:
+$!	if f$locate("FILE", key2) .lt. key2_len then pflag = 1
+$!	if f$locate("DIR", key2) .eq. key2_len - 3 then pflag = 1
+$!	if f$locate("PATH", key2) .eq. key2_len - 4 then pflag = 1
+$!
+$	search/out='tfile1' 'configure_script' "''key2'="/exact
+$	search_sev = '$severity'
+$	if 'search_sev' .eq. 1
+$	then
+$	    open/read/err=unknown_cf_rd_error sf 'tfile1'
+$search_file_rd_loop:
+$	    read/end=unknown_cf_rd_err sf line_in
+$	    line_in = f$edit(line_in, "TRIM")
+$	    skey1 = f$element(0,"=",line_in)
+$	    if skey1 .eqs. key2
+$	    then
+$		skey2 = f$element(1,"=",line_in)
+$		skey2a = f$extract(0,2,skey2)
+$!
+$!		Keep these two cases separate to make it easier to add
+$!		more future intelligence to this routine
+$!----------------------------------------------------------------------
+$		if skey2a .eqs. """`"
+$		then
+$!		    if pflag .eq. 1
+$!		    then
+$!			write tf "#ifndef ''key2'"
+$!			write tf "#define ",key2," """,gproj_name,"_",key2,""""
+$!			write tf "#endif"
+$!		    else
+$!			Ignore this for now
+$!------------------------------------------
+$			write tf "/* ", xline, " */"
+$!		    endif
+$		    set_flag = 1
+$		    goto found_in_configure
+$		endif
+$		if skey2a .eqs. """$"
+$		then
+$!		    if pflag .eq. 1
+$!		    then
+$!			write tf "#ifndef ''key2'"
+$!			write tf "#define ",key2," """,gproj_name,"_",key2,""""
+$!			write tf "#endif"
+$!		    else
+$!			Ignore this for now
+$!-------------------------------------------
+$			write tf "/* ", xline, " */"
+$!		    endif
+$		    set_flag = 1
+$		    goto found_in_configure
+$		endif
+$		if f$extract(0, 1, skey2) .eqs. "'"
+$		then
+$		    skey2 = skey2 - "'" - "'"
+$		endif
+$		write tf "#ifndef ''key2'"
+$		write tf "#define ",key2," """,skey2,""""
+$		write tf "#endif"
+$		set_flag = 1
+$	    else
+$		goto search_file_rd_loop
+$!		if pflag .eq. 1
+$!		then
+$!		    write tf "#ifndef ''key2'"
+$!		    write tf "#define ",key2," """,gproj_name,"_",key2,""""
+$!		    write tf "#endif"
+$!		    set_flag = 1
+$!		endif
+$	    endif
+$found_in_configure:
+$unknown_cf_rd_err:
+$	    if f$trnlnm("sf","lnm$process",,"SUPERVISOR") .nes. ""
+$	    then
+$		close sf
+$	    endif
+$	    if f$search(tfile1) .nes. "" then delete 'tfile1';*
+$	    if set_flag .eq. 1 then goto cfgh_in_loop1
+$	endif
+$   endif
+$!
+$!
+$!
+$!  If it falls through everything else, comment it out
+$!-----------------------------------------------------
+$   write tf "/* ", xline, " */"
+$   goto cfgh_in_loop1
+$cfgh_in_loop1_end:
+$close inf
+$!
+$!
+$! Write out the tail
+$!--------------------
+$write_tail:
+$gosub write_config_h_tail
+$!
+$! Exit and clean up
+$!--------------------
+$general_error:
+$status = '$status'
+$all_exit:
+$set noon
+$if f$trnlnm("sf","lnm$process",,"SUPERVISOR") .nes. "" then close sf
+$if f$trnlnm("tf","lnm$process",,"SUPERVISOR") .nes. "" then close tf
+$if f$trnlnm("inf","lnm$process",,"SUPERVISOR") .nes. "" then close inf
+$if f$trnlnm("tf1","lnm$process",,"SUPERVISOR") .nes. "" then close tf1
+$if f$trnlnm("tf2","lnm$process",,"SUPERVISOR") .nes. "" then close tf2
+$if f$trnlnm("tfcv","lnm$process",,"SUPERVISOR") .nes. "" then close tfcv
+$if f$type(tfile1) .eqs. "STRING"
+$then
+$   if f$search(tfile1) .nes. "" then delete 'tfile1';*
+$endif
+$if f$type(dchfile) .eqs. "STRING"
+$then
+$   if f$search(dchfile) .nes. "" then delete 'dchfile';*
+$endif
+$if f$type(configure_script) .eqs. "STRING"
+$then
+$   if f$search(configure_script) .nes. "" then delete 'configure_script';*
+$endif
+$exit 'status'
+$!
+$!
+$control_y:
+$   status = ss_control_y
+$   goto all_exit
+$!
+$!
+$!
+$! Gosub to write a new config_vms.h
+$!-----------------------------------
+$write_config_vms:
+$outfile = "sys$disk:[]config_vms.h"
+$create 'outfile'
+$open/append tf 'outfile'
+$write tf "/* File: config_vms.h"
+$write tf "**"
+$write tf "** This file contains the manual edits needed for porting"
+$!write tf "** the ''proj_name' package to OpenVMS.
+$write tf "**"
+$write tf "** Edit this file as needed.  The procedure that automatically"
+$write tf "** generated this header stub will not overwrite or make any"
+$write tf "** changes to this file."
+$write tf "**"
+$write tf -
+ "** ", datetime, tab, username, tab, "Generated by ''my_proc_file'"
+$write tf "**"
+$write tf -
+ "**========================================================================*/"
+$write tf ""
+$close tf
+$return
+$!
+$! gosub to write out a documentation header for config.h
+$!----------------------------------------------------------------
+$write_config_h_header:
+$outfile = "sys$disk:[]config.h"
+$create 'outfile'
+$open/append tf 'outfile'
+$write tf "#ifndef CONFIG_H"
+$write tf "#define CONFIG_H"
+$write tf "/* File: config.h"
+$write tf "**"
+$write tf -
+  "** This file contains the options needed for porting "
+$write tf "** the project on a VMS system."
+$write tf "**"
+$write tf "** Try not to make any edits to this file, as it is"
+$write tf "** automagically generated."
+$write tf "**"
+$write tf "** Manual edits should be made to the config_vms.h file."
+$write tf "**"
+$write tf -
+ "** ", datetime, tab, username, tab, "Generated by ''my_proc_file'"
+$write tf "**"
+$write tf -
+ "**========================================================================*/"
+$write tf ""
+$write tf "#if (__CRTL_VER >= 70200000) && !defined (__VAX)"
+$write tf "#define _LARGEFILE 1"
+$write tf "#endif"
+$write tf ""
+$write tf "#ifndef __VAX"
+$write tf "#ifdef __CRTL_VER"
+$write tf "#if __CRTL_VER >= 80200000"
+$write tf "#define _USE_STD_STAT 1"
+$write tf "#endif"
+$write tf "#endif"
+$write tf "#endif"
+$write tf ""
+$!
+$if P1 .nes. "NOBUILTINS"
+$then
+$   write tf " /* Allow compiler builtins */"
+$   write tf "/*-------------------------*/"
+$   write tf "#ifdef __DECC_VER"
+$   write tf "#include <non_existant_dir:builtins.h>"
+$   write tf "#endif"
+$endif
+$!
+$write tf ""
+$return
+$!
+$! gosub to write out the tail for config.h and close it
+$!---------------------------------------------------------
+$write_config_h_tail:
+$write tf ""
+$write tf " /* Include the hand customized settings */"
+$write tf "/*--------------------------------------*/"
+$write tf "#include ""sys$disk:config_vms.h"""
+$write tf ""
+$write tf "#endif /* CONFIG_H */"
+$close tf
+$return
+$!
diff --git a/vms/descrip.mms b/vms/descrip.mms
index 77dad90a..a0b7bd6a 100644
--- a/vms/descrip.mms
+++ b/vms/descrip.mms
@@ -47,6 +47,7 @@ MAKEFILE = $(VMSDIR)Descrip.MMS
 #CCFLAGS = /noOpt/Debug
 
 # a comma separated list of macros to define
+# Do not specify _POSIX_EXIT here, other tricks are used for this.
 CDEFS	= "GAWK","HAVE_CONFIG_H"
 
 .ifdef GNUC
@@ -67,8 +68,15 @@ CFLAGS	= /Incl=[]/Obj=[]/Opt=noInline/Def=($(CDEFS)) $(CCFLAGS)
 LIBS	= sys$share:vaxcrtl.exe/Shareable
 .else	!!VAXC
 # neither GNUC nor VAXC, assume DECC (same for either VAX or Alpha)
-CC	= cc/DECC/Prefix=All
-CFLAGS	= /Incl=[]/Obj=[]/Def=($(CDEFS)) $(CCFLAGS)
+.ifdef __VAX__
+CFLOAT  =
+.else
+CFLOAT	= /float=ieee/ieee_mode=denorm_results
+.endif
+CNAME	= /NAME=(AS_IS,SHORT)
+CC	= cc/DECC/Prefix=All/NESTED_INCLUDE=NONE$(CFLOAT)
+CFLAGS	= /Incl=([],[.vms])/Obj=[]/Def=($(CDEFS))$(CNAME) $(CCFLAGS)
+CEFLAGS = /Incl=([],[.vms],[.missing_d],[.extension])$(CNAME) $(CCFLAGS)
 LIBS	=	# DECC$SHR instead of VAXCRTL, no special link option needed
 .endif	!VAXC
 .endif	!GNUC
@@ -106,7 +114,7 @@ AWKOBJS = $(AWKOBJ1),$(AWKOBJ2)
 # VMSOBJS
 #	VMS specific stuff
 VMSCODE = vms_misc.obj,vms_popen.obj,vms_fwrite.obj,vms_args.obj,\
-	vms_gawk.obj,vms_cli.obj
+	vms_gawk.obj,vms_cli.obj,vms_crtl_init.obj
 VMSCMD	= gawk_cmd.obj			# built from .cld file
 VMSOBJS = $(VMSCODE),$(VMSCMD)
 
@@ -114,7 +122,7 @@ DOCS= $(DOCDIR)gawk.1,$(DOCDIR)gawk.texi,$(DOCDIR)texinfo.tex
 
 # Release of gawk
 REL=4.1
-PATCHLVL=0
+PATCHLVL=1
 
 # generic target
 all : gawk
@@ -128,8 +136,8 @@ gawk : gawk.exe
 gawk.exe : $(GAWKOBJ) $(AWKOBJS) $(VMSOBJS) gawk.opt
 	$(LINK) $(LINKFLAGS) gawk.opt/options
 
-gawk.opt : $(MAKEFILE)			# create linker options file
-      @	open/write opt sys$disk:[]gawk.opt		! ~ 'cat <<close >gawk.opt'
+gawk.opt : $(MAKEFILE) config.h         # create linker options file
+      @	open/write opt sys$disk:[]gawk.opt	! ~ 'cat <<close >gawk.opt'
       @	write opt "! GAWK -- GNU awk"
       @ write opt "$(GAWKOBJ)"
       @ write opt "$(AWKOBJ1)"
@@ -139,17 +147,19 @@ gawk.opt : $(MAKEFILE)			# create linker options file
       @ write opt "stack=48	!preallocate more pages (default is 20)"
       @ write opt "iosegment=128	!ditto (default is 32)"
       @	write opt "$(LIBS)"
-      @	write opt "identification=""V$(REL).$(PATCHLVL)"""
-      @	close opt
+      @ close opt
+      $ @$(VMSDIR)gawk_ident.com
 
 $(VMSCODE)	: awk.h config.h $(VMSDIR)redirect.h $(VMSDIR)vms.h
-$(AWKOBJS)	: awk.h gettext.h mbsupport.h regex.h dfa.h config.h $(VMSDIR)redirect.h
+$(AWKOBJS)	: awk.h gettext.h mbsupport.h regex.h dfa.h config.h \
+		  $(VMSDIR)redirect.h
 $(GAWKOBJ)	: awk.h config.h $(VMSDIR)redirect.h
 
 #-----------------------------------------------------------------------------
 # Older versions of MMS have problems handling lower case file names typically
 # found on ODS-5 disks. Fix this by adding explicit dependencies.
 #_____________________________________________________________________________
+
 array.obj	: array.c
 awkgram.obj	: awkgram.c awk.h
 builtin.obj	: builtin.c floatmagic.h random.h
@@ -174,7 +184,8 @@ node.obj	: node.c
 profile.obj	: profile.c
 random.obj	: random.c random.h
 re.obj		: re.c
-regex.obj	: regex.c regcomp.c regex_internal.c regexec.c regex.h regex_internal.h
+regex.obj	: regex.c regcomp.c regex_internal.c regexec.c regex.h \
+		  regex_internal.h
 str_array.obj	: str_array.c
 symbol.obj	: symbol.c
 version.obj	: version.c
@@ -184,12 +195,14 @@ vms_fwrite.obj	: $(VMSDIR)vms_fwrite.c
 vms_args.obj	: $(VMSDIR)vms_args.c
 vms_gawk.obj	: $(VMSDIR)vms_gawk.c
 vms_cli.obj	: $(VMSDIR)vms_cli.c
+vms_crtl_init.obj : $(VMSDIR)vms_crtl_init.c
 replace.obj	: replace.c $(MISSNGD)system.c $(MISSNGD)memcmp.c \
 		  $(MISSNGD)memcpy.c $(MISSNGD)memset.c $(MISSNGD)memmove.c \
 		  $(MISSNGD)strncasecmp.c $(MISSNGD)strerror.c \
 		  $(MISSNGD)strftime.c $(MISSNGD)strchr.c $(MISSNGD)strtod.c \
 		  $(MISSNGD)strtoul.c $(MISSNGD)tzset.c $(MISSNGD)mktime.c \
-		  $(MISSNGD)snprintf.c $(MISSNGD)getaddrinfo.c $(MISSNGD)usleep.c \
+		  $(MISSNGD)snprintf.c $(MISSNGD)getaddrinfo.c \
+		  $(MISSNGD)usleep.c \
 		  $(MISSNGD)setenv.c $(MISSNGD)strcoll.c $(MISSNGD)wcmisc.c
 
 # bison or yacc required
@@ -201,7 +214,8 @@ awkgram.c	: awkgram.y	# foo.y :: yacc => y[_]tab.c, bison => foo_tab.c
 	$(PARSER) $(YFLAGS) $<
      @- if f$search("ytab.c")	.nes."" then  rename/new_vers ytab.c  $@
      @- if f$search("y_tab.c")	.nes."" then  rename/new_vers y_tab.c $@
-     @- if f$search("awkgram_tab.c").nes."" then  rename/new_vers awkgram_tab.c $@
+     @- if f$search("awkgram_tab.c").nes."" then \
+            rename/new_vers awkgram_tab.c $@
 
 command.c	: command.y
      @- if f$search("ytab.c")	.nes."" then  delete ytab.c;*
@@ -211,10 +225,14 @@ command.c	: command.y
 	$(PARSER) $(YFLAGS) $<
      @- if f$search("ytab.c")	.nes."" then  rename/new_vers ytab.c  $@
      @- if f$search("y_tab.c")	.nes."" then  rename/new_vers y_tab.c $@
-     @- if f$search("command_tab.c").nes."" then  rename/new_vers command_tab.c $@
+     @- if f$search("command_tab.c").nes."" then \
+            rename/new_vers command_tab.c $@
 
-config.h	: $(VMSDIR)vms-conf.h
-	copy $< sys$disk:[]$@
+config_vms.h : $(VMSDIR)generate_config_vms_h_gawk.com
+     $ @$(VMSDIR)generate_config_vms_h_gawk.com
+
+config.h	: configh.in config_vms.h $(VMSDIR)config_h.com
+     $ @$(VMSDIR)config_h.com
 
 $(VMSCMD)	: $(VMSDIR)gawk.cld
 	set command $(CLDFLAGS)/object=$@ $<
@@ -223,6 +241,96 @@ $(VMSCMD)	: $(VMSDIR)gawk.cld
 install.help	: $(VMSDIR)gawk.hlp
 	library/help $(HELPLIB) $< /log
 
+
+# Build dynamic extensions - Alpha/Itanium only.
+.ifdef __VAX__
+# VAX not complete yet.
+plug_opt = [.VMS.VAX]gawk_plugin_xfer.opt
+.else
+plug_opt = [.vms]gawk_plugin.opt
+.endif
+
+ext_gawkdirfd_h = [.extension]gawkdirfd.h config.h nonposix.h
+
+extensions : filefuncs.exe fnmatch.exe inplace.exe ordchr.exe readdir.exe \
+	revoutput.exe revtwoway.exe rwarray.exe testext.exe time.exe
+
+filefuncs.exe : filefuncs.obj stack.obj gawkfts.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), stack.obj, gawkfts.obj, \
+		$(plug_opt)/opt
+
+fnmatch.exe : fnmatch.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+inplace.exe : inplace.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+ordchr.exe : ordchr.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+readdir.exe : readdir.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+revoutput.exe : revoutput.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+revtwoway.exe : revtwoway.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+rwarray.exe : rwarray.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+testext.exe : testext.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+time.exe : time.obj $(plug_opt)
+	link/share=$(MMS$TARGET) $(MMS$SOURCE), $(plug_opt)/opt
+
+stack.obj : [.extension]stack.c config.h gawkapi.h \
+	[.extension]gawkfts.h, [.extension]stack.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+gawkfts.obj : [.extension]gawkfts.c config.h [.extension]gawkfts.h \
+	$(ext_gawkdirfd_h)
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H, ZOS_USS, "fchdir(x)=(-1)") \
+	/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+filefuncs.obj : [.extension]filefuncs.c config.h gawkapi.h \
+	[.extension]gawkfts.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+fnmatch.obj : [.extension]fnmatch.c config.h gawkapi.h \
+	[.missing_d]fnmatch.h [.missing_d]fnmatch.c
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+inplace.obj : [.extension]inplace.c config.h gawkapi.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+ordchr.obj : [.extension]ordchr.c config.h gawkapi.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+readdir.obj : [.extension]readdir.c config.h gawkapi.h \
+	$(ext_gawkdirfd_h)
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H, HAVE_DIRENT_H) \
+	/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+revoutput.obj : [.extension]revoutput.c config.h gawkapi.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+revtwoway.obj : [.extension]revtwoway.c config.h gawkapi.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H, HAVE_GETDTABLESIZE) \
+	/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+rwarray.obj : [.extension]rwarray.c config.h gawkapi.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+testext.obj : [.extension]testext.c config.h gawkapi.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+time.obj : [.extension]time.c config.h gawkapi.h
+    $(CC)$(CEFLAGS)/define=(HAVE_CONFIG_H)/object=$(MMS$TARGET) $(MMS$SOURCE)
+
+
 # miscellaneous other targets
 tidy :
       - if f$search("*.*;-1").nes."" then  purge
@@ -230,13 +338,35 @@ tidy :
 
 clean :
       - if f$search ("*.obj")    .nes. "" then delete *.obj;*
+      - if f$search ("*.lis")    .nes. "" then delete *.lis;*
       - if f$search ("gawk.opt") .nes. "" then delete gawk.opt;*
 
 spotless : clean tidy
-      - if f$search("config.h").nes."" then  rename config.h config.h-old/New
+      - if f$search("config.h").nes."" then delete config.h;*
+      - if f$search("config_vms.h").nes."" then delete config_vms.h;*
       - if f$search("gawk.exe").nes."" then  delete gawk.exe;*
+      - if f$search("*.dsf").nes."" then  delete *.dsf;*
+      - if f$search("*.map").nes."" then  delete *.map;*
+      - if f$search("*.pcsi$desc").nes."" then  delete *.pcsi$desc;*
+      - if f$search("*.pcsi$text").nes."" then  delete *.pcsi$text;*
+      - if f$search("gawk*_src.bck").nes."" then  delete gawk*_src.bck;*
+      - if f$search("*.release_notes").nes."" then  delete *.release_notes;*
+      - if f$search("filefuncs.exe").nes."" then  delete filefuncs.exe;*
+      - if f$search("fnmatch.exe").nes."" then  delete fnmatch.exe;*
+      - if f$search("inplace.exe").nes."" then  delete inplace.exe;*
+      - if f$search("ordchr.exe").nes."" then  delete ordchr.exe;*
+      - if f$search("readdir.exe").nes."" then  delete readdir.exe;*
+      - if f$search("revoutput.exe").nes."" then  delete revoutput.exe;*
+      - if f$search("revtwoway.exe").nes."" then  delete revtwoway.exe;*
+      - if f$search("rwarray.exe").nes."" then  delete rwarray.exe;*
+      - if f$search("testext.exe").nes."" then  delete testext.exe;*
+      - if f$search("time.exe").nes."" then  delete time.exe;*
+      - if f$search("gawk_verb.cld").nes."" then  delete gawk_verb.cld;*
       - if f$search("gawk.dvi").nes."" then  delete gawk.dvi;*
-      - if f$search("[.doc]texindex.exe").nes."" then  delete [.doc]texindex.exe;*
+      - if f$search("[.doc]texindex.exe").nes."" then \
+            delete [.doc]texindex.exe;*
+      - if f$search("[.cxx_repository]*.*;").nes."" then \
+            delete [.cxx_repository]*.*;*
 
 #
 # Note: this only works if you kept a copy of [.support]texindex.c
@@ -258,7 +388,8 @@ gawk.dvi : [.doc]texindex.exe [.doc]gawk.texi
       @ write sys$output " Third (final) pass"
 	TeX gawk.texi
      -@ purge
-     -@ delete gawk.lis;,.aux;,gawk.%%;,.cps;,.fns;,.kys;,.pgs;,.toc;,.tps;,.vrs;
+     -@ delete \
+         gawk.lis;,.aux;,gawk.%%;,.cps;,.fns;,.kys;,.pgs;,.toc;,.tps;,.vrs;
       @ rename/new_vers gawk.dvi [-]*.*
       @ set default [-]
 
diff --git a/vms/fcntl.h b/vms/fcntl.h
deleted file mode 100644
index d975db7a..00000000
--- a/vms/fcntl.h
+++ /dev/null
@@ -1,10 +0,0 @@
-/* "fcntl.h" -- constants for BSD-style I/O routines (ala VAX C's <file.h>) */
-#define O_RDONLY	0
-#define O_WRONLY	1
-#define O_RDWR		2
-#define O_NDELAY	4
-#define O_NOWAIT	4
-#define O_APPEND	8
-#define O_CREAT		0x0200
-#define O_TRUNC		0x0400
-#define O_EXCL		0x0800
diff --git a/vms/gawk.hlp b/vms/gawk.hlp
index 4b82e7e9..a14ad72b 100644
--- a/vms/gawk.hlp
+++ b/vms/gawk.hlp
@@ -1183,6 +1183,10 @@
                  the default is systime(); if u is present and non-zero
                  then t is treated as a UTC value, otherwise it is
                  considered to be local time
+
+5 time_logical_names
+ Gawk needs the SYS$TIMEZONE_RULE or TZ logical names defined or it will
+ output the time in the GMT timezone.
 5 time_formats
  Formatting directives similar to the 'printf' & 'sprintf' functions
  (each is introduced in the format string by preceding it with a
@@ -1557,9 +1561,28 @@
 4 exit
  The exit statement can optionally pass a final status value to the
  operating system.  GAWK expects a UN*X-style value instead of a
- VMS status value, so 0 indicates success and non-zero indicates
- failure.  The final exit status will be 1 (VMS success) if 0 is
- used, or even (VMS non-success) if non-zero is used.
+ VMS status value, so 0 indicates success.  A failure is indicated
+ by 1 and VMS will set the ERROR status.  A fatal error is indicated
+ by 2 and VMS will set the FATAL status.  All other values will will have
+ the SUCCESS status.  The exit value is encoded to comply with VMS
+ coding standards and will have the C_FACILITY_NO of 0x350000 with
+ the constant 0xA000 added to the number shifted over by 3 bits to
+ make room for the severity codes.
+
+ To extract the actual gawk exit code from the VMS status use:
+     unix_status = (vms_status .and. &x7f8) / 8
+
+ A C program that uses exec() to call gawk will get the original
+ UN*X-style exit value.
+
+ Older versions of Gawk treated Unix exit code 0 as 1, A failure as
+ 2, and a fatal error as 4, and passed all the other numbers through.
+ This violated the VMS exit status coding requirements.
+
+4 rounding
+ VAX/VMS floating point uses unbiased rounding.  This is different than
+ what portable gawk programs expect.
+
 3 changes
  Changes between version 4.0.0 and earlier versions
 
@@ -1569,6 +1592,7 @@
    General
      dgawk.exe does interactive debugging of awk programs
      pgawk.exe does comprehensive execution profiling of awk programs
+     pgawk.exe is not currently supplied for VMS.
      -d[file] and -p[file] options added
      -Wcompat and -Wusage options dropped; use -Wtraditional and -Whelp
      BEGINFILE and ENDFILE built-in rule patterns
@@ -1594,6 +1618,10 @@
        support for radix prefix '0' (octal) and '0x' (hexadecimal)
 
    VMS-specific
+     The VMS exit codes now correctly encode the gawk exit status and
+     the VMS severity bits are set.
+     Large file support is enabled on the platforms that support it.
+     Extended filename support is enabled on the platforms that support it.
      New command qualifiers: /EXTRA_COMMANDS, /PROFILE, /DUMP_VARIABLES,
        /OPTIMIZE, /TRADITIONAL, /SANDBOX, /NON_DECIMAL_DATA
      Revised qualifier: /LINT, takes optional argument list
diff --git a/vms/gawk_alias_setup.com b/vms/gawk_alias_setup.com
new file mode 100644
index 00000000..a7f13f4b
--- /dev/null
+++ b/vms/gawk_alias_setup.com
@@ -0,0 +1,139 @@
+$! File: gawk_alias_setup.com
+$!
+$! The PCSI procedure needs a helper script to set up and remove aliases.
+$!
+$! If p1 starts with "R" then remove instead of install.
+$!
+$!
+$! 02-Jan-2014  J. Malmberg - Gawk Version
+$!
+$!===========================================================================
+$!
+$ mode = "install"
+$ code = f$extract(0, 1, p1)
+$ if code .eqs. "R" .or. code .eqs. "r" then mode = "remove"
+$!
+$ arch_type = f$getsyi("ARCH_NAME")
+$ arch_code = f$extract(0, 1, arch_type)
+$!
+$ if arch_code .nes. "V"
+$ then
+$   set proc/parse=extended
+$ endif
+$!
+$!
+$ call do_alias "gawk" "[bin]"
+$ call do_alias "gawk" "[bin]" "awk"
+$ call do_alias "gawk" "[bin]" "gawk" "[usr.bin]"
+$ call do_alias "gawk" "[bin]" "awk" "[usr.bin]"
+$ call do_alias "gawk.1" "[usr.share.man.man1]" "awk.1"
+$!
+$ exit
+$!!
+$!
+$do_alias: subroutine
+$ if mode .eqs. "install"
+$ then
+$   call add_alias "''p1'" "''p2'" "''p3'" "''p4'"
+$ else
+$   call remove_alias "''p1'" "''p2'" "''p3'" "''p4'"
+$ endif
+$ exit
+$ENDSUBROUTINE ! do_alias
+$!
+$!
+$! P1 is the filename, p2 is the directory prefix,
+$! p3 is the alias name if different than p1
+$! p4 is the alias directory if different than p2
+$add_alias: subroutine
+$ if p3 .eqs. "" then p3 = p1
+$ if p4 .eqs. "" then p4 = p2
+$ ftype = f$element(1, ".", p1)
+$ if ftype .eqs. "."
+$ then
+$    file = "gnv$gnu:''p2'gnv$''p1'.EXE"
+$    alias = "gnv$gnu:''p4'''p3'."
+$ else
+$    file = "gnv$gnu:''p2'''p1'"
+$    alias = "gnv$gnu:''p4'''p3'"
+$ endif
+$ if f$search(file) .nes. ""
+$ then
+$   fid = ""
+$   mess = f$environment("message")
+$   if f$search(alias) .nes. ""
+$   then
+$      on warn then goto fix_link
+$      set message/nofac/nosev/noident/notext
+$      fid = f$file_attributes(alias, "FID")
+$   endif
+$   goto fix_link_end
+$fix_link:
+$    set file/remove 'alias';
+$fix_link_end:
+$   set message'mess'
+$   if f$search(alias) .eqs. ""
+$   then
+$       set file/enter='alias' 'file'
+$   endif
+$   alias1 = alias + "exe"
+$   if (ftype .eqs. ".")
+$   then
+$     fid = ""
+$     mess = f$environment("message")
+$     if f$search(alias1) .nes. ""
+$     then
+$       on warn then goto fix_link1
+$       set message/nofac/nosev/noident/notext
+$       fid = f$file_attributes(alias1, "FID")
+$     endif
+$     goto fix_link_end1
+$fix_link1:
+$    set file/remove 'alias1';
+$fix_link_end1:
+$   set message'mess'
+$     if (f$search(alias1) .eqs. "")
+$     then
+$       set file/enter='alias1' 'file'
+$     endif
+$   endif
+$ endif
+$ exit
+$ENDSUBROUTINE ! add_alias
+$!
+$remove_alias: subroutine
+$ if p3 .eqs. "" then p3 = p1
+$ if p4 .eqs. "" then p4 = p2
+$ ftype = f$element(1, ".", p1)
+$ if ftype .eqs. "."
+$ then
+$   file = "gnv$gnu:''p2'gnv$''p1'.EXE"
+$   alias = "gnv$gnu:''p4'''p3'."
+$ else
+$   file = "gnv$gnu:''p2'''p1'"
+$   alias = "gnv$gnu:''p4'''p3'"
+$ endif
+$ file_fid = "No_file_fid"
+$ if f$search(file) .nes. ""
+$ then
+$   fid = f$file_attributes(file, "FID")
+$   if f$search(alias) .nes. ""
+$   then
+$       afid = f$file_attributes(alias, "FID")
+$       if (afid .eqs. fid)
+$       then
+$           set file/remove 'alias';
+$       endif
+$   endif
+$   alias1 = alias + "exe"
+$   if (ftype .eqs. ".") .and. (f$search(alias1) .nes. "")
+$   then
+$       afid = f$file_attributes(alias1, "FID")
+$       if (afid .eqs. fid)
+$       then
+$           set file/remove 'alias1';
+$       endif
+$   endif
+$ endif
+$ exit
+$ENDSUBROUTINE ! remove_alias
diff --git a/vms/gawk_build_steps.txt b/vms/gawk_build_steps.txt
new file mode 100644
index 00000000..b3bb281b
--- /dev/null
+++ b/vms/gawk_build_steps.txt
@@ -0,0 +1,220 @@
+From File: gawk_build_steps.txt
+
+Building GAWK on OpenVMS for use with GNV requires a current HP C compiler
+and MMK.
+
+The HP C 7.x compilers were used for building on Alpha and Itanium.
+The Compaq C 6.4 compiler is being used on VAX.
+
+MMK was obtained from https://github.com/endlesssoftware/mmk
+
+Several special things were done in this port of Gawk to VMS to make it
+easier to keep it up to date with the Unix version.
+
+Note the GNV$ prefix is registered for the GNV project to prevent name
+collisions with other products and packages.  This is a VMS convention.
+
+The files are stored with GNV_ instead of GNV$ most open source source
+code maintainers do not want to files with $ in their source repositories.
+
+The build procedure will copy the files to have the GNV$ names as needed.
+
+1. The original GNU Gawk source files are in their own directory tree which
+is never written to by the build process.  This directory is kept up to date
+with the current official patches.  See below about the how this is done
+with logical names.
+
+2. A file vms_eco_level.h is used to set the ECO of the package.  The
+vms_eco_level.h needs to be set back to zero if the version or patch level
+of the GNU Unix source is changed.  This file is currently only used
+by the kit building procedure.
+
+The source kits are provided in backup savesets inside of the PCSI install kit.
+
+Backup save sets are currently the only distribution medium that I can be
+sure is installed on a target VMS system that will correctly unpack files
+with extended character sets in them.  You may need to adjust the ownership
+of the restored files for kits on Alpha/Itanium VMS versions 8.1 and earlier.
+
+On VAX, the filenames will be as seen on the VAX system, typically with non
+ODS-2 characters and case changes prefixed with $ characters.
+
+[gnv.common_src]gawk_*_original_src.bck is the original source of the
+gawk kit as provided by the GNV project.
+[gnv.vms_src]gawk-*_vms_src.bck, if present, has the changed files that
+are used for building that are not yet in the gawk source kits
+distributed by the GNU gawk project.
+
+These backup savesets should be restored to different directory trees on
+an ODS-5 volume(s) which are referenced by concealed rooted logical names,
+unless on VAX, where either an NFS or ODS-2 volume can be used.
+
+SRC_ROOT: is for the source files common to all platforms.  This can be a
+          read only copy of the files from a change control repository.
+
+          In my build environment, the TRUNK_ROOT:[gawk] is the
+          same directory as src_root:[gawk].  TRUNK_ROOT:[gawk] is a
+          checkout of the gawk repository used for the build.
+
+VMS_ROOT: is for the files that were changed from the repository copy of
+          SRC_ROOT:
+
+          Note, you should create the VMS_ROOT: directory tree even if it is
+          initially empty.  This is where you should put edits if you are
+          making changes.
+
+          In my build environment, the source_root:[gnu_vms.gawk] is a
+          directory with the checked out code and vms_root:[gawk] is
+          a copy with any local modifications.
+
+          The command procedure compare_gawk_source.com will report any
+          differences in the source_root:[gnu_vms.gawk] directory and the
+          vms_root:[gawk] directory.  If the source_root: logical is not
+          defined, it will translate the logical name src_root to do the
+          effective of src_root:[gawk.-.-.gnu_vms.gawk] to find the
+          VMS specific code CVS checkout based on where the checkout for
+          the GNU source is expected to be.
+
+LCL_ROOT: is manually created to have the same base and sub-directories as
+          SRC_ROOT: and VMS_ROOT:  This is for the architecture specific
+          binaries and other files created during the build.
+
+The logical name REF_ROOT: is optionally defined to be a logical name that
+is a search list for VMS_ROOT:,SRC_ROOT:
+
+The logical name PRJ_ROOT: is defined to be a logical name that is a search
+list for LCL_ROOT:,REF_ROOT:
+
+The VMS_ROOT and LCL_ROOT directory trees can be created with commands
+similar to:
+
+  $ create/dir lcl_root:[gawk]/prot=w:re
+  $ copy src_root:[gawk...]*.dir -
+    lcl_root:[gawk...]/prot=(o:rwed,w:re)
+  $ create/dir vms_root:[gawk]/prot=w:re
+  $ copy src_root:[gawk...]*.dir -
+    vms_root:[gawk...]/prot=(o:rwed,w:re)
+
+One of the ways with to protect the source from being modified is to have
+the directories under src_root: owned by a user or resource where the build
+username only has read access to it.
+
+Edit the file gawk_release_note_start.txt or other text files to reflect
+any changes.
+
+Edit the file PCSI_GAWK_FILE_LIST.TXT if there are new files added to the
+kit.  These files should all be ODS-2 legal filenames and directories.
+
+Note that if src_root: or vms_root: are NFS mounted disks, the
+step of backing up the source files will probably hang or fail.
+
+You need to copy the source files to VMS mounted disks and create
+logical names SRC_ROOT1 and VMS_ROOT1 to work around this to to
+reference local disks.  Make sure src_root1:[000000] and
+vms_root1:[000000] exist and can be written to.
+
+The command procedure compare_gawk_source can be used to check
+those directories and keep them up to date.
+
+    @[.vms]compare_gawk_source.com SRCBCK UPDATE
+
+    This compares the reference GNU source with the backup
+    staging directory for it and updates with any changes.
+
+    @[.vms]compare_gawk_source.com VMSBCK UPDATE
+
+    This compares the VMS specific source with the backup
+    staging directory for it and updates with any changes.
+
+    Leave off "UPDATE" to just check without doing any changes.
+
+    If you are not using NFS mounted disks and do not want to have a
+    separate directory for staging the sources for backup make sure
+    that src_root1: and vms_root1: do not exist.
+
+The kits will be built in the directory STAGE_ROOT:[KIT], which must be
+writable to the build procedure.
+
+Define the logical name GNV_PCSI_PRODUCER to indicate who is making the
+distribution.
+
+Define the logical name GNV_PCSI_PRODUCER_FULL_NAME to be your full name
+or full name of your company.
+
+These two GNV_PCSI_* logical names need to be manually defined to indicate
+the "branding" to differentiate the source of the kit.
+
+A limitation of the PCSI kitting procedure is that when selecting files, it
+tends to ignore the directory structure and assumes that all files with the
+same name are the same file, so every file placed in the kit must have a
+unique ODS-2 legal name.  Then a procedure needs to be added to the kit to
+create an alias link on install and remove the link on remove.
+
+While newer versions of PCSI can support ODS-5 filenames, not all verions
+of PCSI on systems that have ODS-5 filenames do.  So as a post install step,
+the PCSI kit built by these steps does a rename to the correct case.
+
+With these search lists set up and the logical names described, Gawk can
+be built and kitted by setting your default to PRJ_ROOT:[gawk]
+and then issuing the command:
+
+   $ @[.vms]pcsi_product_gawk.com
+
+First it will build the binaries by using  MMK utility.  The case of the
+parameter may be significant on ODS-5.
+
+   $ mmk/descrip=[.vms]descrip.mms gawk
+
+Then for Alpha and Itanium, it will build the dynamic extensions.
+
+   $ mmk/descrip=[.vms]descrip.mms extensions
+
+To clean up after a build to start over, run mmk with the target spotless.
+
+   $ mmk/descrip=[.vms]descrip.mms spotless
+
+The files are installed into a NEW_GNU directory for staging by running the
+procedure stage_gawk_install.com.  This copies the binaries and creates
+alias links to them.
+
+   $ @[.vms]stage_gawk_install.com remove
+   $ @[.vms]stage_gawk_install.com
+
+On the VAX platform, the staged files are needed for building the PCSI
+kit, as the VAX source was staged on an NFS volume, which encodes the
+filenames that have any upper case or special symbols in them.
+
+To remove the staged files, the procedure is run again with the parameter
+"REMOVE".  This makes sure that the alias links are removed.
+
+The names and contents of the PCSI files requires that the version of
+gawk be encoded in a special format.  This is done by:
+
+   @[.vms]make_pcsi_gawk_kit_name.com
+
+The release notes are built from the release note start, readme files and
+this file:
+
+   @[.release]build_gawk_release_notes.com
+
+Then the backup the source kits.
+
+Building a PCSI kit for an architecture takes the following steps after
+making sure that you have a working build environment.
+
+On VAX, the product command always prompts to the terminal for a confirmation.
+
+If there is another kit for this same version of gawk, but for a different
+base platform or operating system version, the product command will prompt
+to the terminal to select which one to compress.
+
+       The following message is normal:
+          %PCSI-I-CANNOTVAL, cannot validate
+            EAGLE$DQA0:[stage_root.][kit]GNV-AXPVMS-GAWK-V--1.PCSI;1
+          -PCSI-I-NOTSIGNED, product kit is not signed and therefore has
+          no manifest file
+
+This will result in both compressed and uncompressed kits for the target
+platform.
+
+Good Luck.
diff --git a/vms/gawk_ident.com b/vms/gawk_ident.com
new file mode 100644
index 00000000..5b3966f9
--- /dev/null
+++ b/vms/gawk_ident.com
@@ -0,0 +1,21 @@
+$! gawk_ident.com - Append ident with version to gawk.
+$!
+$!
+$ open/read cfgh config.h
+$cfgh_loop:
+$ read/end=cfgh_loop_end cfgh line_in
+$ key1 = f$element(0, " ", line_in)
+$ if key1 .nes. "#define" then goto cfgh_loop
+$ key2 = f$element(1, " ", line_in)
+$ if key2 .nes. "VERSION" then goto cfgh_loop
+$ version_string = f$element(2, " ", line_in) - """" - """"
+$ ver_major = f$element(0, ".", version_string)
+$ ver_minor = f$element(1, ".", version_string)
+$ REL = ver_major + "." + ver_minor
+$ PATCHLVL = f$element(2, ".", version_string)
+$cfgh_loop_end:
+$ close cfgh
+$!
+$ open/append Fopt gawk.opt
+$ write Fopt "identification=""V''REL'.''PATCHLVL'"""
+$ close Fopt
diff --git a/vms/gawk_plugin.opt b/vms/gawk_plugin.opt
new file mode 100644
index 00000000..b0523d08
--- /dev/null
+++ b/vms/gawk_plugin.opt
@@ -0,0 +1,5 @@
+CASE_SENSITIVE=YES
+SYMBOL_VECTOR=(plugin_is_GPL_compatible=DATA)
+SYMBOL_VECTOR=(PLUGIN_IS_GPL_COMPATIBLE/plugin_is_GPL_compatible=DATA)
+SYMBOL_VECTOR=(dl_load=PROCEDURE)
+SYMBOL_VECTOR=(DL_LOAD/dl_load=PROCEDURE)
diff --git a/vms/gawk_release_note_start.txt b/vms/gawk_release_note_start.txt
new file mode 100644
index 00000000..44fceaf5
--- /dev/null
+++ b/vms/gawk_release_note_start.txt
@@ -0,0 +1,189 @@
+From file: gawk_release_note_start.com
+
+This is GNU gawk packaged for VMS.
+
+The original readme files for GAWK for standalone building on VMS are
+supplied here along with a procedure for building GAWK for the making
+a PCSI kit.
+
+Note: I am a hobbyist and am not providing any support or any commitment
+to supply bug fixes or future releases.  This code is as-is with no
+warrantees.
+
+The testing of this port of Gawk involved running some self tests that
+were provided with the source.
+
+This version of gawk supports dynamically loaded extensions on Alpha and
+Itanium versions of VMS.  The pre-built dynamically loaded extensions
+are in gnv$gnu:[usr.lib.gawk].
+
+The linker option file used to build a dynamically loaded extension is
+located in gnv$gnu:[usr.src.gawk.extension.vms], and the gawkapi.h file
+is in gnv$gnu:[usr.include].
+
+Special installation notes:
+
+*  Please see https://sourceforge.net/p/gnv/wiki/InstallingGNVPackages/
+   for the latest information on installing GNV related PCSI kits.
+
+*  We are updating and replacing GNV one kit at a time and transitioning
+   GNV to be a set of kits that the GNV package will install.  During
+   this transition some extra issues will need to be handled during
+   installs and upgrades.
+
+*  Due to the way that PCSI identifies packages, if you install a package
+   from one producer and then want to upgrade it from another producer,
+   you will probably need to uninstall the previous package first.
+
+   Some of these packages were previously created with different producer
+   prefixes.  We are standardizing on VMSPORTS and GNV as the branding
+   prefixes.  GNV will be for packages that are part of the GNV product
+   suite, and VMSPORTS will be for most other packages.
+
+   This uninstall can cause warning messages about dependencies.  If you
+   are transitioning to an upwardly compatible package, you can ignore
+   those warnings.
+
+*  This package should be installed to the same volume as GNV is installed.
+
+   If you uninstall or upgrade GNV or install a GNV from before the
+   transition is complete, you will need to reinstall all other packages
+   that install to the same GNV directory tree.
+
+   This is because at least some of the existing GNV installation procedures
+   have bugs in them were instead of just deleting the files that were
+   installed, they delete all files in the GNV directory tree.
+
+*  Because this is a transition, this package is replacing files from the
+   old GNV packages.  This is a necessary issue to allow incremental
+   improvement as we can not replace the GNV package until we get all
+   the component packages done.
+
+*  The GNV 2.x through at least the 3.0.1 kits make an unusual change
+   to the disk directory structure where they are installed where
+   they use the [vms$common.gnv] as a mount point and mount the posix
+   root on it.  This is a bug because it causes many problems and does
+   not offer any advantages.  One of the problems is that it causes
+   problems with other PCSI installs and uninstalls to that directory.
+
+   This bug can be manually repaired such as has been done on
+   on encompasserve.org as documented in PORTING_TO_VMS notes conference.
+
+   At this time, we do not have a scripted repair to this bug, and it
+   may not be possible to fully script a repair because this bug can
+   cause the POSIX root and [vms$common.gnv] to have different contents
+   when they should be the same directory, and it will take a manual
+   inspection to select which files go where.
+
+*  Because of the directory change bug, the gnv$startup.com in the GNV
+   kit must be run when the system boots up or the [vms$common.gnv]
+   directory will appear to be empty.
+
+   If a PCSI kit like this one is installed when the GNV startup has not
+   been run, it will create a new directory tree under [vms$common.gnv]
+   that will not be visible to the posix root.  If you uninstall this
+   PCSI kit before running the gnv$startup.com procedure then you can
+   install it after running the gnv$startup.com procedure.  If you have
+   run the gnv$startup.com procedure after the install, then you have
+   a mess, and you will need to use the GNV umnt to un-mount the
+   [vms$common.gnv] directory before the uninstall of this kit will
+   work.
+
+An analyze/disk/repair step on the installation disk should be done after
+installation to collect files left over from incomplete deletions into the
+SYSLOST directory.  This step should be done on a "quiet" system per HP
+recomendations.
+
+Bugs can be logged at the tracker with https://sourceforge.net/projects/gnv/.
+There is no guarantee that bugs will be fixed for a hobbyist build.
+
+VMS specific port information:
+
+The logical name GNV$GNU is used to find the simulated posix root and defines
+the logical name SYS$POSIX_ROOT in the process table in user mode for child
+processes if needed.  This is to comply with VMS logical name conventions.
+The logical name BIN is also set in the process table in user mode to be
+GNV$GNU:[BIN] if it is not already set.
+
+The following DECC$Feature settings are in in effect for Gawk by default:
+
+DECC$ACL_ACCESS_CHECK enabled.
+DECC$ALLOW_REMOVE_OPEN_FILES enabled.
+DECC$ARGV_PARSE_STYLE enabled.
+DECC$EFS_CASE_PRESERVE enabled.
+DECC$EFS_CHARSET enabled.
+DECC$EFS_FILE_TIMESTAMPS enabled.
+DECC$ENABLE_GETENV_CACHE enabled.
+DECC$EXEC_FILEATTR_INHERITANCE set to 2.
+DECC$FILE_PERMISSION_UNIX enabled.
+DECC$FILE_SHARING enabled.
+DECC$FILE_OWNER_UNIX enabled.
+DECC$FILENAME_REPORT_UNIX enabled.
+DECC$FILENAME_UNIX_NO_VERSION enabled.
+DECC$GLOB_UNIX_STYLE enabled.
+DECC$POSIX_SEEK_STREAM_FILE enabled.
+DECC$READDIR_DROPDOTNOTYPE enabled.
+DECC$RENAME_NO_INHERIT enabled.
+DECC$STDIO_CTX_EOL enabled.
+DECC$STRTOL_ERANGE enabled.
+DECC$UNIX_PATH_BEFORE_LOGNAME enabled.
+
+While more strict UNIX compatibility feature settings can be applied by users
+by setting feature logical names, these settings are all the Bash and most
+ported programs need.
+
+This port of Gawk uses the VMS CRTL to handle the Unix format pathnames
+and as such is dependent on them.  It is a known issue that directories with
+a Unix name "file.dir/" and some symbolic links are not handled correctly.
+This is a combination of problems with RMS and CRTL.  The RMS portion is
+fixed with the VMS84?_RMS-V0300 ECO kit.  I am not aware of a CRTL kit that
+fixes the issues.
+
+This kit is designed to be used with the GNV Bash 4.2.45 or later kit.
+
+Fixes and enhancements:
+
+* No logical names required for proper Gawk operations other than GNV$GNU
+  for locating the simulated "/".
+
+* GNV$GNU is used to find the posix root and locally sets SYS$POSIX_ROOT
+  for child processes if needed.  This is to comply with VMS logical
+  name conventions.  The logical name BIN is also set locally to be
+  GNV$GNU:[BIN] if it is not already set.
+
+* config.h now generated at part of the build from a template.
+
+The supplied GNV$GAWK_STARTUP.COM procedure is provided in
+[VMS$COMMON.SYS$STARTUP] can be put in your VMS startup procedure to install
+selected images as known because they need privileges.  It is recommended
+that the GNV$STARTUP.COM procedure be run first, followed by the
+GNV$BASH_STARTUP.COM procedure before the GNV$GAWK_STARTUP.COM is
+executed.
+
+The names of the gawk image have been prefixed with GNV$ to prevent
+possible naming conflicts with other programs that are on the system.  The
+GNV$ prefix has been registered with HP for this purpose.
+
+OpenVMS specific building and kitting instructions are after the standard
+bash readme file below.
+
+The source kits contains files for building Gawk using MMK.
+MMK 4.0 was used for this build on Alpha and Itanium Itanium.
+
+Currently, the focus of the OpenVMS GNV porting team is to address bugs in
+the OpenVMS port of GNV components that pose immediate barriers to running
+configure and make scripts for Open Source Software packages targeting
+OpenVMS environments.
+
+The GNV development team is involved in an ongoing effort to identify and
+document the underlying technical causes for these current limitations and (if
+available) workarounds as well as developing code fixes to eliminate them. The
+VMS-Ports Source Forge project at https://sourceforge.net/p/vms-ports/tickets/
+currently documents OpenVMS CRTL bugs and limitations with respect to porting
+Open Source Software using OpenVMS. The VMS-Ports Source Forge Project also
+contains examples of ported packages provided by volunteer contributors as well
+as documentation with recommendations on how to setup, modify and use the
+OpenVMS GNV environment for the purpose of porting Open Source software
+packages to OpenVMS. Browse to https://sourceforge.net/p/vms-ports/wiki/Home/
+for more information.
+
diff --git a/vms/gawk_verb.com b/vms/gawk_verb.com
new file mode 100644
index 00000000..b74c49ed
--- /dev/null
+++ b/vms/gawk_verb.com
@@ -0,0 +1,26 @@
+$! gawk_verb.com - build the gawk_verb.cld from the gawk.cld.
+$!
+$! The CLD file needed to modify a DCL command table is different
+$! from the CLD file needed to build the product by specifying an image.
+$!
+$! So read in the [.vms]gawk.cld and generate a gawk_verb.cld.
+$!
+$! 23-Dec-2012 - J. Malmberg
+$!
+$outfile = "sys$disk:[]gawk_verb.cld"
+$infile = "[.vms]gawk.cld"
+$open/read cld 'infile'
+$create 'outfile'
+$open/append cldv 'outfile'
+$loop:
+$read cld/end=loop_end line_in
+$if f$locate("image gawk", line_in) .lt. f$length(line_in)
+$then
+$    write cldv "    image gnv$gnu:[bin]gnv$gawk"
+$    goto loop
+$endif
+$write cldv line_in
+$goto loop
+$loop_end:
+$close cldv
+$close cld
diff --git a/vms/gawkmisc.vms b/vms/gawkmisc.vms
index cbc59cd7..725cf669 100644
--- a/vms/gawkmisc.vms
+++ b/vms/gawkmisc.vms
@@ -3,7 +3,8 @@
  */
 
 /* 
- * Copyright (C) 1986, 1988, 1989, 1991-1996, 2003, 2011 the Free Software Foundation, Inc.
+ * Copyright (C) 1986, 1988, 1989, 1991-1996, 2003, 2011, 2014
+ * the Free Software Foundation, Inc.
  * 
  * This file is part of GAWK, the GNU implementation of the
  * AWK Progamming Language.
@@ -23,30 +24,441 @@
  * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
  */
 
+#include <stdio.h>
+#include <string.h>
+#include <ctype.h>
+#include <stdlib.h>
+
+#include <descrip.h>
+#include <dvidef.h>
+#include <efndef.h>
+#include <fscndef.h>
+#include <stsdef.h>
+#include <time.h>
+#include <lnmdef.h>
+
+
+#pragma member_alignment save
+#pragma nomember_alignment longword
+struct item_list_3 {
+	unsigned short len;
+	unsigned short code;
+	void * bufadr;
+	unsigned short * retlen;
+};
+
+struct filescan_itmlst_2 {
+    unsigned short length;
+    unsigned short itmcode;
+    char * component;
+};
+
+#pragma member_alignment
+
+int SYS$GETDVIW(
+        unsigned long efn,
+        unsigned short chan,
+        const struct dsc$descriptor_s * devnam,
+        const struct item_list_3 * itmlst,
+        void * iosb,
+        void (* astadr)(unsigned long),
+        unsigned long astprm,
+        void * nullarg);
+
+int SYS$FILESCAN(
+        const struct dsc$descriptor_s * srcstr,
+        struct filescan_itmlst_2 * valuelist,
+        unsigned long * fldflags,
+        struct dsc$descriptor_s *auxout,
+        unsigned short * retlen);
+
+int   SYS$TRNLNM(
+        const unsigned long * attr,
+        const struct dsc$descriptor_s * table_dsc,
+        struct dsc$descriptor_s * name_dsc,
+        const unsigned char * acmode,
+        const struct item_list_3 * item_list);
+
 char quote = '\'';
 char *defpath = DEFPATH;
 char *deflibpath = DEFLIBPATH;
 char envsep  = ',';
+#define VMS_NAME_LEN 255
+static char vms_name[VMS_NAME_LEN+1];
+
+/* Take all the fun out of simply looking up a logical name */
+static int sys_trnlnm
+   (const char * logname,
+    char * value,
+    int value_len)
+{
+	const $DESCRIPTOR(table_dsc, "LNM$FILE_DEV");
+	const unsigned long attr = LNM$M_CASE_BLIND;
+	struct dsc$descriptor_s name_dsc;
+	int status;
+	unsigned short result;
+	struct item_list_3 itlst[2];
+
+	itlst[0].len = value_len;
+	itlst[0].code = LNM$_STRING;
+	itlst[0].bufadr = value;
+	itlst[0].retlen = &result;
+
+	itlst[1].len = 0;
+	itlst[1].code = 0;
+
+	name_dsc.dsc$w_length = strlen(logname);
+	name_dsc.dsc$a_pointer = (char *)logname;
+	name_dsc.dsc$b_dtype = DSC$K_DTYPE_T;
+	name_dsc.dsc$b_class = DSC$K_CLASS_S;
+
+	status = SYS$TRNLNM(&attr, &table_dsc, &name_dsc, 0, itlst);
+
+	if ($VMS_STATUS_SUCCESS(status)) {
+
+		/* Null terminate and return the string */
+		value[result] = '\0';
+	}
+
+	return status;
+}
+
 
 /* gawk_name --- pull out the "gawk" part from how the OS called us */
 
+/* You would not think that this should be a such a problem, but
+ * VMS extended file specifications are tricky to parse, and we have
+ * to tell the difference between a CRTL generated argv[0] and a
+ * passed exec() argv[0] and handle both cases.
+ */
+
 char *
 gawk_name(filespec)
 const char *filespec;
 {
-	char *p, *q;
+	int status;
+	int result;
+	char * shell;
+	int lcname = 0;
+
+	/* If the path name starts with a /, then it is an absolute path
+	 * that may have been generated by the CRTL instead of the command
+	 * name.  If it is the device name between the slashes, then this
+	 * was likely from the run command and needs to be fixed up.
+	 * If the DECC$POSIX_COMPLIANT_PATHNAMES is set to 2, then it is
+	 * the DISK$VOLUME that will be present, and it will still need to
+	 * be fixed.
+	 */
+
+	result = 0;
+	if (filespec[0] == '/') {
+		char * nextslash;
+		int length;
+		struct item_list_3 itemlist[3];
+		unsigned short dvi_iosb[4];
+		char alldevnam[64];
+		unsigned short alldevnam_len;
+		struct dsc$descriptor_s devname_dsc;
+		char diskvolnam[256];
+		unsigned short diskvolnam_len;
+
+		 /* Get some information about the disk */
+		/*--------------------------------------*/
+		itemlist[0].len = (sizeof alldevnam) - 1;
+		itemlist[0].code = DVI$_ALLDEVNAM;
+		itemlist[0].bufadr = alldevnam;
+		itemlist[0].retlen = &alldevnam_len;
+		itemlist[1].len = (sizeof diskvolnam) - 1 - 5;
+		itemlist[1].code = DVI$_VOLNAM;
+		itemlist[1].bufadr = &diskvolnam[5];
+		itemlist[1].retlen = &diskvolnam_len;
+		itemlist[2].len = 0;
+		itemlist[2].code = 0;
+
+		/* Add the prefix for the volume name. */
+		/* SYS$GETDVI will append the volume name to this */
+		strcpy(diskvolnam,"DISK$");
+
+		nextslash = strchr(&filespec[1], '/');
+		if (nextslash != NULL) {
+			length = nextslash - filespec - 1;
+
+			/* DECC requires a cast here */
+			devname_dsc.dsc$a_pointer = (char *)&filespec[1];
+			devname_dsc.dsc$w_length = length;
+			devname_dsc.dsc$b_dtype = DSC$K_DTYPE_T;
+			devname_dsc.dsc$b_class = DSC$K_CLASS_S;
+
+			status = SYS$GETDVIW(
+				EFN$C_ENF,
+				0,
+				&devname_dsc,
+				itemlist,
+				dvi_iosb,
+				NULL, 0, 0);
+			if (!$VMS_STATUS_SUCCESS(status)) {
+				/* If the sys$getdviw fails, then this path
+				 * was passed by an exec() program and not
+				 * from DCL, so do nothing.
+				 * An example is "/tmp/program" where tmp:
+				 * does not exist
+				 */
+				result = 0;
+			} else if (!$VMS_STATUS_SUCCESS(dvi_iosb[0])) {
+				result = 0;
+			} else {
+				char * devnam;
+				int devnam_len;
+				char argv_dev[64];
+
+				/* Null terminate the returned alldevnam */
+				alldevnam[alldevnam_len] = 0;
+				devnam = alldevnam;
+				devnam_len = alldevnam_len;
+
+				/* Need to skip past any leading underscore */
+				if (devnam[0] == '_') {
+					devnam++;
+					devnam_len--;
+				}
+
+				/* And remove the trailing colon */
+				if (devnam[devnam_len - 1] == ':') {
+					devnam_len--;
+					devnam[devnam_len] = 0;
+				}
+
+				/* Null terminate the returned volnam */
+				diskvolnam_len += 5;
+				diskvolnam[diskvolnam_len] = 0;
+
+				/* Check first for normal CRTL behavior */
+				if (devnam_len == length) {
+					strncpy(vms_name, &filespec[1], length);
+				vms_name[length] = 0;
+				result = (strcasecmp(devnam, vms_name) == 0);
+				}
+
+				/* If we have not got a match check for
+				 * POSIX Compliant behavior.  To be more
+				 * accurate, we could also check to see
+				 * if that feature is active.
+				 */
+				if ((result == 0) &&
+				    (diskvolnam_len == length)) {
+					int cmp;
+					strncpy(vms_name, &filespec[1], length);
+					vms_name[length] = 0;
+					cmp = strcasecmp(diskvolnam, vms_name);
+					result = (cmp == 0);
+				}
+			}
+		}
+	} else {
+		/* The path did not start with a slash, so it could be VMS
+		 * format.  If it is vms format, it has a volume/device in
+		 * it as it must be an absolute path
+		 */
+		struct dsc$descriptor_s path_desc;
+		int status;
+		unsigned long field_flags;
+		struct filescan_itmlst_2 item_list[5];
+		char * volume;
+		char * name;
+		int name_len;
+		char * ext;
+
+		/* DECC requires a cast here */
+		path_desc.dsc$a_pointer = (char *)filespec;
+		path_desc.dsc$w_length = strlen(filespec);
+		path_desc.dsc$b_dtype = DSC$K_DTYPE_T;
+		path_desc.dsc$b_class = DSC$K_CLASS_S;
+
+		/* Don't actually need to initialize anything buf itmcode */
+		/* I just do not like uninitialized input values */
+
+		/* Sanity check, this must be the same length as input */
+		item_list[0].itmcode = FSCN$_FILESPEC;
+		item_list[0].length = 0;
+		item_list[0].component = NULL;
+
+		/* If the device is present, then it if a VMS spec */
+		item_list[1].itmcode = FSCN$_DEVICE;
+		item_list[1].length = 0;
+		item_list[1].component = NULL;
+
+		/* we need the program name and type */
+		item_list[2].itmcode = FSCN$_NAME;
+		item_list[2].length = 0;
+		item_list[2].component = NULL;
+
+		item_list[3].itmcode = FSCN$_TYPE;
+		item_list[3].length = 0;
+		item_list[3].component = NULL;
+
+		/* End the list */
+		item_list[4].itmcode = 0;
+		item_list[4].length = 0;
+		item_list[4].component = NULL;
+
+		status = SYS$FILESCAN(
+		    (const struct dsc$descriptor_s *)&path_desc,
+		     item_list, &field_flags, NULL, NULL);
+
+		if ($VMS_STATUS_SUCCESS(status) &&
+		   (item_list[0].length == path_desc.dsc$w_length) &&
+		   (item_list[1].length != 0)) {
+
+			char * dollar;
+			int keep_ext;
+			int i;
+
+			/* We need the filescan to be successful,
+			 * same length as input, and a volume to be present.
+			 *
+			 * We will assume that we only get to this path on
+			 * a version of VMS that does not support the EFS
+			 * character set.
+			 *
+			 * There may be a xxx$ prefix on the image name.
+			 * Linux  programs do not handle that well, so
+			 * strip the prefix.
+			 */
+			name = item_list[2].component;
+			name_len = item_list[2].length;
+			dollar = strrchr(name, '$');
+			if (dollar != NULL) {
+				dollar++;
+				name_len = name_len - (dollar - name);
+				name = dollar;
+			}
+
+			strncpy(vms_name, name, name_len);
+			vms_name[name_len] = 0;
+			result = 1;
+
+			/* We only keep the extension if it is not ".exe" */
+			keep_ext = 0;
+			ext = item_list[3].component;
+
+			if (item_list[3].length != 1) {
+				if (item_list[3].length != 4) {
+					keep_ext = 1;
+				} else {
+					int x;
+					x = strncmp(ext, ".exe", 4);
+					if (x != 0) {
+						keep_ext = 1;
+					}
+				}
+			}
+
+			if (keep_ext == 1) {
+				strncpy(&vms_name[name_len],
+					ext, item_list[3].length);
+			}
+		}
+	}
 
-	/* "device:[root.][directory.subdir]GAWK.EXE;n" -> "GAWK" */
-	p = strrchr(filespec, ']');  /* directory punctuation */
-	q = strrchr(filespec, '>');  /* alternate <international> punct */
+	if (result) {
+		char * lastslash;
+		char * dollar;
+		char * dotexe;
+		char * lastdot;
+		char * extension;
+
+		/* This means it is probably the name from a DCL command
+		 * Find the last slash which separates the file from the
+		 * path.
+		 */
+		lastslash = strrchr(filespec, '/');
+
+		if (lastslash != NULL) {
+			int i;
+
+			lastslash++;
+
+			/* There may be a xxx$ prefix on the image name. */
+			/* Linux programs do not handle that well, so    */
+			/* strip the prefix */
+			dollar = strrchr(lastslash, '$');
+
+			if (dollar != NULL) {
+				dollar++;
+				lastslash = dollar;
+			}
+
+			strcpy(vms_name, lastslash);
+
+			/* In UNIX mode + EFS character set, there should
+			 * not be a version present, as it is not possible
+			 * when parsing to tell if it is a version or part
+			 * of the UNIX filename as UNIX programs use numeric
+			 * extensions for many reasons.
+			 */
+
+			lastdot = strrchr(vms_name, '.');
+			if (lastdot != NULL) {
+				int i;
+
+				i = 1;
+				while (isdigit(lastdot[i])) {
+					i++;
+				}
+				if (lastdot[i] == 0) {
+					*lastdot = 0;
+				}
+			}
+
+			/* Find the .exe on the name (case insenstive)
+			 * and toss it
+			 */
+			dotexe = strrchr(vms_name, '.');
+			if (dotexe != NULL) {
+				if ((dotexe[1] == 'e' || dotexe[1] == 'E') &&
+				    (dotexe[2] == 'x' || dotexe[2] == 'X') &&
+				    (dotexe[3] == 'e' || dotexe[3] == 'E') &&
+				    (dotexe[4] == 0)) {
+
+					*dotexe = 0;
+				} else {
+					/* Also need to handle a null
+					 * extension because of a CRTL bug.
+					 */
+					if (dotexe[1] == 0) {
+						*dotexe = 0;
+					}
+				}
+			}
+		}
+	} else {
+		/* No changes needed */
+		strncpy(vms_name, filespec, VMS_NAME_LEN);
+		vms_name[VMS_NAME_LEN] = 0;
+	}
 
-	if (p == NULL || q > p)
-		p = q;
-	p = strdup(p == NULL ? filespec : (p + 1));
-	if ((q = strrchr(p, '.')) != NULL)
-		*q = '\0';  /* strip .typ;vers */
 
-	return p;
+	/*
+	 * The above fixes up the name, but for the DCL shell
+	 * may leave it in upper case, which messes up the self tests.
+	 * force it to lower case here.
+	 */
+	shell = getenv("SHELL");
+	if (shell != NULL) {
+		if (strcmp(shell, "DCL") == 0) {
+			lcname = 1;
+		}
+	} else {
+		lcname = 1;
+	}
+	if (lcname == 1) {
+		int i = 0;
+		while (vms_name[i] != 0) {
+			vms_name[i] = tolower(vms_name[i]);
+			i++;
+		}
+	}
+	return vms_name;
 }
 
 /* os_arg_fixup --- fixup the command line */
@@ -56,7 +468,24 @@ os_arg_fixup(argcp, argvp)
 int *argcp;
 char ***argvp;
 {
+	char *tz_rule;
+	int status;
+
 	(void) vms_arg_fixup(argcp, argvp);
+
+	/* Fix up the time zone */
+	/* For some reason it gets trashed */
+	tz_rule = malloc(1024);
+	status = sys_trnlnm("TZ", tz_rule, 1024);
+	if ($VMS_STATUS_SUCCESS(status)) {
+		setenv("TZ", tz_rule, 1);
+	} else {
+		status = sys_trnlnm("SYS$TIMEZONE_RULE", tz_rule, 1024);
+		if ($VMS_STATUS_SUCCESS(status)) {
+			setenv("TZ", tz_rule, 1);
+		}
+	}
+	free(tz_rule);
 }
 
 /* os_devopen --- open special per-OS devices */
@@ -208,11 +637,17 @@ files_are_same(char *newfile, SRCFILE *oldfile)
 
 	f2 = &oldfile->sbuf;
 		/* compare device string */
+#ifdef _USE_STD_STAT
+	return (f1->st_dev == f2->st_dev
+		/* and 48-bit file id cookie */
+		&& f1->st_ino == f2->st_ino);
+ #else
 	return (strcmp(f1->st_dev, f2->st_dev) == 0
 		/* and 48-bit file id cookie stored in 3 short ints */
 		&& f1->st_ino[0] == f2->st_ino[0]
 		&& f1->st_ino[1] == f2->st_ino[1]
 		&& f1->st_ino[2] == f2->st_ino[2]);
+#endif
 }
 
 int
diff --git a/vms/generate_config_vms_h_gawk.com b/vms/generate_config_vms_h_gawk.com
new file mode 100644
index 00000000..12d3d6cf
--- /dev/null
+++ b/vms/generate_config_vms_h_gawk.com
@@ -0,0 +1,298 @@
+$! File: GENERATE_CONFIG_H_VMS_GAWK.COM
+$!
+$! Gawk like most open source products uses a variant of a config.h file.
+$! Depending on the curl version, this could be config.h or curl_config.h.
+$!
+$! For GNV based builds, the configure script is run and that produces
+$! a [curl_]config.h file.  Configure scripts on VMS generally do not
+$! know how to do everything, so there is also a [-.lib]config-vms.h file
+$! that has VMS specific code that compensates for bugs in some of the
+$! VMS shared images.
+$!
+$! This generates a []config.h file and also a config_vms.h file,
+$! which is used to supplement that file.
+$!
+$!
+$! Copyright (C) 2014 the Free Software Foundation, Inc.
+$!
+$! This file is part of GAWK, the GNU implementation of the
+$! AWK Progamming Language.
+$!
+$! GAWK is free software; you can redistribute it and/or modify
+$! it under the terms of the GNU General Public License as published by
+$! the Free Software Foundation; either version 3 of the License, or
+$! (at your option) any later version.
+$!
+$! GAWK is distributed in the hope that it will be useful,
+$! but WITHOUT ANY WARRANTY; without even the implied warranty of
+$! MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+$! GNU General Public License for more details.
+$!
+$! You should have received a copy of the GNU General Public License
+$! along with this program; if not, write to the Free Software
+$! Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301,
+$! USA
+$!
+$! Per assignment agreement with FSF, similar procedures may be present
+$! in other packages under other licensing agreements and copyrights
+$!
+$!
+$! 21-Jan-2014	J. Malmberg
+$!
+$!=========================================================================
+$!
+$! Allow arguments to be grouped together with comma or separated by spaces
+$! Do no know if we will need more than 8.
+$ args = "," + p1 + "," + p2 + "," + p3 + "," + p4 + ","
+$ args = args + p5 + "," + p6 + "," + p7 + "," + p8 + ","
+$!
+$! Provide lower case version to simplify parsing.
+$ args_lower = f$edit(args, "LOWERCASE")
+$!
+$ args_len = f$length(args)
+$!
+$ if (f$getsyi("HW_MODEL") .lt. 1024)
+$ then
+$   arch_name = "VAX"
+$ else
+$   arch_name = ""
+$   arch_name = arch_name + f$edit(f$getsyi("ARCH_NAME"), "UPCASE")
+$   if (arch_name .eqs. "") then arch_name = "UNK"
+$ endif
+$!
+$!
+$! Start the configuration file.
+$! Need to do a create and then an append to make the file have the
+$! typical file attributes of a VMS text file.
+$ create sys$disk:[]config_vms.h
+$ open/append cvh sys$disk:[]config_vms.h
+$!
+$! Write the defines to prevent multiple includes.
+$! These are probably not needed in this case,
+$! but are best practice to put on all header files.
+$ write cvh "#ifndef __CONFIG_VMS_H__"
+$ write cvh "#define __CONFIG_VMS_H__"
+$ write cvh ""
+$!
+$ write cvh "#if __CRTL_VER >= 70000000"
+$ write cvh "#define VMS_V7"
+$ write cvh "#else"
+$ write cvh "#define HAVE_TZNAME 1 /* (faked in vms/vms_misc.c) */
+$ write cvh "#define HAVE_TZSET 1 /* (faked in vms/vms_misc.c) */
+$ write cvh "#endif"
+$ write cvh "#if __CRTL_VER >= 70200000"
+$ write cvh "#define DYNAMIC 1"
+$ write cvh "#endif"
+$ write cvh ""
+$ write cvh "#define PRINTF_HAS_F_FORMAT 1"
+$ write cvh ""
+$ write cvh "/* The _Noreturn keyword of C11.  */"
+$ write cvh "#ifndef _Noreturn"
+$ write cvh "# if (3 <= __GNUC__ || (__GNUC__ == 2 && 8 <= __GNUC_MINOR__) \"
+$ write cvh "      || 0x5110 <= __SUNPRO_C)"
+$ write cvh "#  define _Noreturn __attribute__ ((__noreturn__))"
+$ write cvh "# elif defined _MSC_VER && 1200 <= _MSC_VER"
+$ write cvh "#  define _Noreturn __declspec (noreturn)"
+$ write cvh "# else"
+$ write cvh "#  define _Noreturn"
+$ write cvh "# endif"
+$ write cvh "#endif"
+$ write cvh ""
+$ write cvh "/*"
+$ write cvh " * VAXCRTL is pre-ANSI and does some variations of numeric"
+$ write cvh " * formatting differently than gawk expects."
+$ write cvh " */"
+$ write cvh "#if defined(VAX) && !defined(__DECC)"
+$ write cvh -
+ "/* '0' format modifier for %e,%f,%g gives wrong results in many cases */"
+$ write cvh "#define VAXCRTL"
+$ write cvh "/* %g format chooses %e format when should use %f */"
+$ write cvh "#define GFMT_WORKAROUND	1"
+$ write cvh "#endif"
+$ write cvh ""
+$ write cvh "/*"
+$ write cvh " * VAX C"
+$ write cvh " *"
+$ write cvh -
+ " * As of V3.2, VAX C is not yet ANSI-compliant.  But it's close enough"
+$ write cvh -
+ " * for GAWK's purposes.  Comment this out for VAX C V2.4 and earlier."
+$ write cvh -
+ " * YYDEBUG definition is needed for combination of VAX C V2.x and Bison."
+$ write cvh " */"
+$ write cvh "#if defined(VAXC) && !defined(__STDC__)"
+$ write cvh "#define __STDC__	0"
+$ write cvh "#define NO_TOKEN_PASTING"
+$ write cvh "#define signed  /*empty*/"
+$ write cvh "#define inline	/*empty*/"
+$ write cvh "#ifndef __DECC	/* DEC C does not support #pragma builtins */"
+$ write cvh "#define VAXC_BUILTINS"
+$ write cvh "#endif"
+$ write cvh "/* #define YYDEBUG 0 */"
+$ write cvh -
+  "#define NO_MBSUPPORT  /* VAX C's preprocessor can't handle mbsupport.h */"
+$ write cvh "#endif"
+$ write cvh ""
+$ write cvh ""
+$ write cvh "#if __DECC_VER >= 60400000 && !defined(DEBUG)"
+$ write cvh "/* disable ""new feature in C99"" diagnostics (for regex code); "
+$ write cvh "   NEWC99 ought to suffice but doesn't (at least in V6.4) */"
+$ write cvh "#pragma message disable (NEWC99,DESIGNATORUSE)"
+$ write cvh "#ifdef __VAX
+$ write cvh "#endif
+$ write cvh "#pragma message disable (LONGDOUBLENYI)"
+$ write cvh "#endif"
+$!
+$! This stuff seems needed for VMS 7.3 and earlier, but not VMS 8.2+
+$! Need some more data as to which versions these issues are fixed in.
+$ write cvh "#if __VMS_VER <= 80200000"
+$! mkstemp goes into an infinte loop in gawk in VAX/VMS 7.3
+$ write cvh "#ifdef HAVE_MKSTEMP"
+$ write cvh "#undef HAVE_MKSTEMP"
+$ write cvh "#endif"
+$ write cvh "#endif"
+$ write cvh ""
+$!
+$! VMS not legal for ANSI compiler to pre-define
+$ write cvh "#ifndef VMS"
+$ write cvh "#define VMS 1"
+$ write cvh "#endif"
+$ write cvh ""
+$!
+$! Need to temp hide stuff that gawk is replacing or redefining before
+$! including the header.
+$ write cvh "/* Need to hide some stuff */"
+$ write cvh "#define getopt hide_getopt"
+$ write cvh "#define optopt hide_optopt"
+$ write cvh "#define optind hide_optind"
+$ write cvh "#define optarg hide_optarg"
+$ write cvh "#define opterr hide_opterr"
+$ write cvh "#define getpgrp hide_getpgrp"
+$ write cvh "#define unsetenv hide_unsetenv"
+$ write cvh "#define read hide_read"
+$ write cvh "#define delete hide_delete"
+$ write cvh "#define getcwd hide_getcwd"
+$ write cvh "#define getgid hide_getgid"
+$ write cvh "#define getegid hide_getegid"
+$ write cvh "#define setgid hide_setgid"
+$ write cvh "#define exit hide_exit"
+$ write cvh "#define _exit hide__exit"
+$ write cvh "#include <unistd.h>"
+$ write cvh "#include <stdlib.h>"
+$ write cvh "#include <stdio.h>"
+$ write cvh "#include <time.h>"
+$ write cvh "#include <stsdef.h>"
+$ write cvh "#include <string.h>"
+$ write cvh "#undef getopt"
+$ write cvh "#undef optopt"
+$ write cvh "#undef optind"
+$ write cvh "#undef optarg"
+$ write cvh "#undef opterr"
+$ write cvh "#undef getpgrp"
+$ write cvh "#undef getcwd"
+$ write cvh "#undef unsetenv"
+$ write cvh "#undef read"
+$ write cvh "#undef delete"
+$ write cvh "#undef getgid"
+$ write cvh "#undef getegid"
+$ write cvh "#undef setgid"
+$ write cvh "#undef exit"
+$ write cvh "#undef _exit"
+$!
+$write cvh "#ifdef HAVE_STRNCASECMP"
+$write cvh "#undef HAVE_STRNCASECMP"
+$write cvh "#endif"
+$!
+$ write cvh "#define IN_CONFIG_H"
+$ write cvh "#include ""redirect.h"""
+$ write cvh "#undef IN_CONFIG_H"
+$ write cvh "#define getpgrp gawk_vms_getpgrp"
+$ write cvh "#ifdef HAVE_SETENV"
+$ write cvh "#undef HAVE_SETENV"
+$ write cvh "#endif"
+$ write cvh "#ifdef HAVE_UNSETENV"
+$ write cvh "#undef HAVE_UNSETENV"
+$ write cvh "#endif"
+$ write cvh "#ifdef HAVE_STRFTIME"
+$ write cvh "#undef HAVE_STRFTIME"
+$ write cvh "#define USE_INCLUDED_STRFTIME"
+$ write cvh "#endif /* HAVE_STRFTIME */"
+$ write cvh ""
+$ write cvh "#include <bitypes.h>"
+$ write cvh "#define INT32_MAX __INT32_MAX"
+$ write cvh "#define INT32_MIN __INT32_MIN"
+$ write cvh ""
+$ write cvh "/*"
+$ write cvh " * DEFPATH"
+$ write cvh " *	VMS: ""/AWK_LIBRARY"" => ""AWK_LIBRARY:"""
+$ write cvh " * The default search path for the -f option of gawk.  It is"
+$ write cvh " * used if the AWKPATH environment variable is undefined."
+$ write cvh " *"
+$ write cvh " * Note: OK even if no AWK_LIBRARY logical name has been defined."
+$ write cvh " */"
+$ write cvh ""
+$ write cvh "#define DEFPATH	"".,/AWK_LIBRARY"""
+$ write cvh "#define DEFLIBPATH "".,/AWK_LIBRARY"""
+$ write cvh "#define ENVSEP	','"
+$ write cvh ""
+$ write cvh "/*"
+$ write cvh " * Extended source file access."
+$ write cvh " */"
+$ write cvh "#define DEFAULT_FILETYPE "".awk"""
+$ write cvh ""
+$ write cvh "/*"
+$ write cvh " * fork/Pipe handling."
+$ write cvh " */"
+$ write cvh "#define PIPES_SIMULATED	1"
+$ write cvh ""
+$ write cvh "/* Extension for shared libraries */"
+$ write cvh "#define SHLIBEXT	""exe"""
+$ write cvh ""
+$! GAWK does not want to use ALLOCA
+$ write cvh "#define NO_ALLOCA"
+$ write cvh "#define STACK_DIRECTION (-1)"
+$ write cvh ""
+$ write cvh "void decc$exit(int status);"
+$ write cvh "#define _exit(foo) vms_exit(foo)"
+$ write cvh "#define exit(foo) vms_exit(foo)"
+$ write cvh ""
+$ write cvh "/* Use POSIX exit codes here */"
+$ write cvh "#ifdef EXIT_FAILURE"
+$ write cvh "#undef EXIT_FAILURE"
+$ write cvh "#endif"
+$ write cvh "#define EXIT_FAILURE (1)"
+$ write cvh ""
+$ write cvh "#define EXIT_FATAL (2)"
+$ write cvh ""
+$ write cvh "#ifndef C_FACILITY_NO"
+$ write cvh "#define C_FACILITY_NO 0x350000"
+$ write cvh "#endif"
+$ write cvh ""
+$ write cvh "/* Build a Posix Exit with VMS severity */
+$ write cvh "static void vms_exit(int status) {"
+$ write cvh "    int vms_status;"
+$ write cvh "    /* Fake the __posix_exit with severity added */"
+$ write cvh "    /* Undocumented correct way to do this. */"
+$ write cvh "    vms_status = 0;"
+$ write cvh "    if (status != 0) {"
+$ write cvh "        vms_status = C_FACILITY_NO | 0xA000 | STS$M_INHIB_MSG;"
+$ write cvh "        vms_status |= (status << 3);"
+$ write cvh "    }"
+$ write cvh "    if (status == EXIT_FAILURE) {"
+$ write cvh "        vms_status |= STS$K_ERROR;"
+$ write cvh "    } else if (status == EXIT_FATAL) {"
+$ write cvh "        vms_status |= STS$K_SEVERE;"
+$ write cvh "    } else {"
+$ write cvh "        vms_status |= STS$K_SUCCESS;"
+$ write cvh "    }"
+$ write cvh "    decc$exit(vms_status);"
+$ write cvh "}"
+$!
+$! Close out the file
+$!
+$ write cvh ""
+$ write cvh "#endif /* __CONFIG_VMS_H__ */"
+$ close cvh
+$!
+$all_exit:
+$ exit
diff --git a/vms/gnv_gawk_startup.com b/vms/gnv_gawk_startup.com
new file mode 100644
index 00000000..e691965e
--- /dev/null
+++ b/vms/gnv_gawk_startup.com
@@ -0,0 +1,75 @@
+$! File: gnv$gawk_Startup.com / gnv_gawk_startup.com
+$!
+$! Procedure to setup the GAWK images for use by programs from the
+$! VMS SYSTARTUP*.COM procedure.
+$!
+$! 14-Mar-2011 J. Malmberg
+$! 04-May-2011 J. Malmberg      Use GNV_PCSI_DESTINATION to find the
+$!                              value to assing GNV$GNU per suggestion
+$!                              by Martin Vorlander.
+$! 02-Jan-2014 J. Malmberg	Gawk Version
+$!========================================================================
+$!
+$!
+$! GNV$GNU if needed.
+$ if f$trnlnm("GNV$GNU") .eqs. ""
+$ then
+$   x = f$trnlnm("GNU","LNM$SYSTEM_TABLE")
+$   if x .nes. ""
+$   then
+$       write sys$output -
+ "Notice: logical name GNU: was found in the system table instead of GNV$GNU:"
+$       write sys$output -
+ "This is a known bug in the GNV 2.1.3 and earlier kits."
+$       define/system/exec/trans=conc GNV$GNU 'x'
+$   else
+$!
+$!      File name per VMS standards
+$!      ---------------------------
+$       file1 = "sys$startup:gnv$destination_''f$getsyi("ARCH_NAME")'.com"
+$!
+$!      File name in GNV 2.1.3
+$!      ----------------------
+$       file2 = "sys$startup:gnv_destination_''f$getsyi("ARCH_NAME")'.com"
+$!
+$!      File name before GNV 2.1.3
+$!      ---------------------------
+$       file3 = "sys$startup:gnv_destination''f$getsyi("ARCH_NAME")'.com"
+$       arch_file = ""
+$       if f$search(file1) .nes. ""
+$       then
+$           arch_file = file1
+$       else
+$           if f$search(file2) .nes. ""
+$           then
+$               arch_file = file2
+$           else
+$               if f$search("file3") .nes. "" then arch_file = file3
+$           endif
+$       endif
+$       if (arch_file) .nes. "" then @'arch_file'
+$!
+$!      Logical name per VMS standards
+$!      -------------------------------
+$       destination = f$trnlnm("GNV$PCSI_DESTINATION")
+$!
+$!      Logical name in GNV 2.1.3
+$!      --------------------------
+$       if destination .eqs. ""
+$       then
+$           destination = f$trnlnm("GNV_PCSI_DESTINATION")
+$       endif
+$       if destination .eqs. ""
+$       then
+$           !Assume this procedure is on the same volume as the GNV install.
+$           my_proc = f$environment("PROCEDURE")
+$           my_dev = f$parse(my_proc,,,"DEVICE","NO_CONCEAL")
+$           destination = "''my_dev'[vms$common.gnv.]"
+$       endif
+$       define/system/exec/trans=conc gnv$gnu 'destination'
+$   endif
+$ endif
+$!
+$!
+$all_exit:
+$ exit
diff --git a/vms/make_pcsi_gawk_kit_name.com b/vms/make_pcsi_gawk_kit_name.com
new file mode 100644
index 00000000..daaa37a4
--- /dev/null
+++ b/vms/make_pcsi_gawk_kit_name.com
@@ -0,0 +1,189 @@
+$! File: MAKE_PCSI_GAWK_KIT_NAME.COM
+$!
+$! Calculates the PCSI kit name for use in building an installation kit.
+$! PCSI is HP's PolyCenter Software Installation Utility.
+$!
+$! The results are stored in as logical names so that other procedures
+$! can use them.
+$!
+$! 92-Jan-2014  J. Malmberg	Gawk version
+$!========================================================================
+$!
+$! Save default
+$default_dir = f$environment("DEFAULT")
+$!
+$! Put things back on error.
+$on warning then goto all_exit
+$!
+$! The producer is the name or common abbreviation for the entity that is
+$! making the kit.  It must be set as a logical name before running this
+$! procedure.
+$!
+$! HP documents the producer as the legal owner of the software, but for
+$! open source work, it should document who is creating the package for
+$! distribution.
+$!
+$producer = f$trnlnm("GNV_PCSI_PRODUCER")
+$if producer .eqs. ""
+$then
+$   write sys$output "The logical name GNV_PCSI_PRODUCER needs to be defined."
+$   write sys$output "This should be set to the common abbreviation or name of"
+$   write sys$output "the entity creating this kit.  If you are an individual"
+$   write sys$output "then use your initials as long as they do not match"
+$   write sys$output "a different well known producer prefix."
+$   goto all_exit
+$endif
+$producer_full_name = f$trnlnm("GNV_PCSI_PRODUCER_FULL_NAME")
+$if producer_full_name .eqs. ""
+$then
+$   write sys$output "The logical name GNV_PCSI_PRODUCER_FULL_NAME needs to"
+$   write sys$output "be defined.  This should be set to the full name of"
+$   write sys$output "the entity creating this kit.  If you are an individual"
+$   write sys$output "then use your name."
+$   write sys$output "EX: DEFINE GNV_PCSI_PRODUCER_FULL_NAME ""First M. Last"""
+$   goto all_exit
+$endif
+$!
+$write sys$output "*****"
+$write sys$output "***** Producer = ''producer'"
+$write sys$output "*****"
+$!
+$!
+$! Base is one of 'VMS', 'AXPVMS', 'I64VMS', 'VAXVMS' and indicates what
+$! binaries are in the kit.  A kit with just 'VMS' can be installed on all
+$! architectures.
+$!
+$base = "VMS"
+$arch_type = f$getsyi("ARCH_NAME")
+$code = f$extract(0, 1, arch_type)
+$if (code .eqs. "I") then base = "I64VMS"
+$if (code .eqs. "V") then base = "VAXVMS"
+$if (code .eqs. "A") then base = "AXPVMS"
+$!
+$!
+$product = "gawk"
+$!
+$!
+$! We need to get the version from config.h.  It will have a lines like
+$! #define PACKAGE_VERSION "4.1.0a"
+$!
+$!
+$open/read/error=version_loop_end verf config.h
+$version_loop:
+$   read/end=version_loop_end verf line_in
+$   if line_in .eqs. "" then goto version_loop
+$   if f$locate("#define PACKAGE_VERSION", line_in) .ne. 0
+$   then
+$       goto version_loop
+$   endif
+$   tag = f$element(1, " ", line_in)
+$   value = f$element(2, " ", line_in) - """" - """"
+$   if tag .eqs. "PACKAGE_VERSION"
+$   then
+$       distversion = value
+$       goto version_loop_end
+$   endif
+$   goto version_loop
+$version_loop_end:
+$close verf
+$!
+$!
+$! Optional ECO file.
+$ECO_LEVEL = ""
+$vms_eco_file = "[.vms]vms_eco_level.h"
+$if f$search(vms_eco_file) .nes. ""
+$then
+$   open/read ef 'vms_eco_file'
+$ecolevel_loop:
+$       read/end=ecolevel_loop_end ef line_in
+$       prefix = f$element(0, " ", line_in)
+$       if prefix .nes. "#define" then goto ecolevel_loop
+$       key = f$element(1, " ", line_in)
+$       value = f$element(2, " ", line_in) - """" - """"
+$       if key .eqs. "VMS_ECO_LEVEL"
+$       then
+$           ECO_LEVEL = value
+$           if ECO_LEVEL .eq. 0
+$           then
+$               ECO_LEVEL = ""
+$           else
+$               ECO_LEVEL = "E" + ECO_LEVEL
+$           endif
+$           goto ecolevel_loop_end
+$       endif
+$       goto ecolevel_loop
+$ecolevel_loop_end:
+$    close ef
+$endif
+$!
+$raw_version = distversion
+$!
+$!
+$! This translates to V0114-08 or D0115-01
+$! We can not encode the snapshot date into the version due to the way that
+$! the Polycenter Software Installation Utility evaluates the name.
+$!
+$! version_type = 'V' for a production release, and 'D' for a build from a
+$! daily repository snapshot, and a code for a build from a pre-release branch
+$majorver = f$element(0, ".", raw_version)
+$minorver = f$element(1, ".", raw_version)
+$update = f$element(2,".", raw_version)
+$if update .eqs. "." then update = ""
+$vtype = "V"
+$if update .nes. ""
+$then
+$   update_len = f$length(update)
+$   code = f$extract(update_len - 1, 1, update)
+$   code = f$edit(code, "UPCASE")
+$   if (code .ges. "A") .and. (code .les. "Z")
+$   then
+$       update = f$extract(0, update_len - 1, update)
+$       vtype = code
+$   endif
+$endif
+$if update .eqs. "0" then update = ""
+$!
+$!
+$version_fao = "!2ZB!2ZB"
+$mmversion = f$fao(version_fao, 'majorver', 'minorver')
+$version = vtype + "''mmversion'"
+$if update .nes. "" .or. ECO_LEVEL .nes. ""
+$then
+$!  The presence of an ECO implies an update
+$   if update .eqs. "" .and. ECO_LEVEL .nes. "" then update = "0"
+$   version = version + "-" + update + ECO_LEVEL
+$   fversion = version
+$else
+$   fversion = version
+$   version = version + "-"
+$endif
+$!
+$! Kit type 1 is complete kit, the only type that this procedure will make.
+$Kittype = 1
+$!
+$! Write out a logical name for the resulting base kit name.
+$name = "''producer'-''base'-''product'-''version'-''kittype'"
+$define GNV_PCSI_KITNAME "''name'"
+$fname = "''product'-''fversion'"
+$!
+$! No ECO or Patch level
+$fname_len = f$length(fname)
+$if f$extract(fname_len - 1, 1, fname) .eqs. "-"
+$then
+$    fname = f$extract(0, fname_len - 1, fname)
+$    fname_len = fname_len - 1
+$endif
+$if f$extract(fname_len - 1, 1, fname) .eqs. "-"
+$then
+$    fname = f$extract(0, fname_len - 1, fname)
+$    fname_len = fname_len - 1
+$endif
+$define GNV_PCSI_FILENAME_BASE 'fname'
+$write sys$output "*****"
+$write sys$output "***** GNV_PCSI_KITNAME = ''name'."
+$write sys$output "***** GNV_PCSI_FILENAME_BASE = ''fname'."
+$write sys$output "*****"
+$!
+$all_exit:
+$set def 'default_dir'
+$exit '$status'
diff --git a/vms/pcsi_gawk_file_list.txt b/vms/pcsi_gawk_file_list.txt
new file mode 100644
index 00000000..67d2d324
--- /dev/null
+++ b/vms/pcsi_gawk_file_list.txt
@@ -0,0 +1,120 @@
+! File: pcsi_gawk_file_list.txt
+!
+! File list for building a PCSI kit.
+! Very simple format so that the parsing logic can be simple.
+! links first, directory second, and files third.
+!
+! link -> file tells procedure to create/remove a link on install/uninstall
+! If more than one link, consider using an alias file.
+!
+! [xxx.yyy]foo.dir is a directory file for the rename phase.
+! [xxx.yyy.foo] is a directory file for the create phase.
+! Each subdirectory needs to be on its own pair of lines.
+!
+! [xxx.yyy]file.ext is a file for the rename and add phases.
+!
+! 14-Mar-2011  J. Malmberg
+! 08-Dec-2013  J. Malmberg      This list is based on what was found on
+!                               some Linux systems and what can be currently
+!                               built on VMS.
+!
+!============================================================================
+![gnv.bin]awk. -> [gnv.bin]gnv$gawk.exe
+![gnv.bin]awk.exe -> [gnv.bin]gnv$gawk.exe
+![gnv.bin]gawk. -> [gnv.bin]gnv$gawk.exe
+![gnv.bin]gawk.exe -> [gnv.bin]gnv$gawk.exe
+![gnv.usr.bin]awk. -> [gnv.bin]gnv$gawk.exe
+![gnv.usr.bin]awk.exe -> [gnv.bin]gnv$gawk.exe
+![gnv.usr.bin]gawk. -> [gnv.bin]gnv$gawk.exe
+![gnv.usr.bin]gawk.exe -> [gnv.bin]gnv$gawk.exe
+![gnv.usr.share.man.man1]awk.1 -> [gnv.usr.share.man.man1]gawk.1
+[gnv]
+[000000]gnv.dir
+[gnv.bin]
+[gnv]bin.dir
+[gnv.vms_bin]
+[gnv]vms_bin.dir
+[gnv.vms_help]
+[gnv]vms_help.dir
+[gnv.lib]
+[gnv]lib.dir
+[gnv.usr]
+[gnv]usr.dir
+[gnv.usr.bin]
+[gnv.usr]bin.dir
+[gnv.usr.include]
+[gnv.usr]include.dir
+[gnv.usr.lib]
+[gnv.usr]lib.dir
+[gnv.usr.lib.gawk]
+[gnv.usr.lib]gawk.dir
+[gnv.usr.share]
+[gnv.usr]share.dir
+[gnv.usr.share.awk]
+[gnv.usr.share]awk.dir
+[gnv.usr.share.doc]
+[gnv.usr.share]doc.dir
+[gnv.usr.share.doc.gawk]
+[gnv.usr.share.doc]gawk.dir
+[gnv.usr.share.info]
+[gnv.usr.share]info.dir
+[gnv.usr.share.man]
+[gnv.usr.share]man.dir
+[gnv.usr.share.man.man1]
+[gnv.usr.share.man]man1.dir
+![gnv.usr.share.man.man7]
+![gnv.usr.share.man]man7.dir
+[gnv.usr]src.dir
+[gnv.usr.src]
+[gnv.usr.src]gawk.dir
+[gnv.usr.src.gawk]extension.dir
+[gnv.usr.src.gawk.extension]
+[gnv.usr.src.gawk.extension]vms.dir
+[gnv.usr.src.gawk.extension.vms]
+[gnv.bin]gnv$gawk.exe
+[gnv.bin]igawk.
+[gnv.vms_bin]remove_old_gawk.com
+[gnv.vms_bin]gawk_alias_setup.com
+[gnv.vms_bin]gawk_verb.cld
+[gnv.vms_help]gawk.hlp
+[gnv.usr.include]gawkapi.h
+[gnv.usr.lib.gawk]filefuncs.exe
+[gnv.usr.lib.gawk]fnmatch.exe
+[gnv.usr.lib.gawk]inplace.exe
+[gnv.usr.lib.gawk]ordchr.exe
+[gnv.usr.lib.gawk]readdir.exe
+[gnv.usr.lib.gawk]revoutput.exe
+[gnv.usr.lib.gawk]revtwoway.exe
+[gnv.usr.lib.gawk]rwarray.exe
+[gnv.usr.lib.gawk]time.exe
+[gnv.usr.share.awk]assert.awk
+[gnv.usr.share.awk]bits2str.awk
+[gnv.usr.share.awk]cliff_rand.awk
+[gnv.usr.share.awk]ctime.awk
+[gnv.usr.share.awk]ftrans.awk
+[gnv.usr.share.awk]getopt.awk
+[gnv.usr.share.awk]gettime.awk
+[gnv.usr.share.awk]join.awk
+[gnv.usr.share.awk]libintl.awk
+[gnv.usr.share.awk]noassign.awk
+[gnv.usr.share.awk]ord.awk
+[gnv.usr.share.awk]readable.awk
+[gnv.usr.share.awk]readfile.awk
+[gnv.usr.share.awk]rewind.awk
+[gnv.usr.share.awk]round.awk
+[gnv.usr.share.awk]strtonum.awk
+[gnv.usr.share.awk]walkarray.awk
+[gnv.usr.share.awk]zerofile.awk
+[gnv.usr.share.doc.gawk]COPYING.
+[gnv.usr.share.doc.gawk]NEWS.
+[gnv.usr.share.doc.gawk]POSIX.STD
+[gnv.usr.share.doc.gawk]README.
+[gnv.usr.share.doc.gawk]README.vms
+[gnv.usr.share.doc.gawk]README.multibyte
+[gnv.usr.share.doc.gawk]README.tests
+[gnv.usr.share.info]gawk.info
+[gnv.usr.share.info]gawkinet.info
+[gnv.usr.share.man.man1]gawk.1
+[gnv.usr.share.man.man1]igawk.1
+![gnv.usr.share.man.man7]
+[gnv.usr.src.gawk.extension.vms]gawk_plugin.opt
diff --git a/vms/pcsi_product_gawk.com b/vms/pcsi_product_gawk.com
new file mode 100644
index 00000000..b0d9febd
--- /dev/null
+++ b/vms/pcsi_product_gawk.com
@@ -0,0 +1,187 @@
+$! File: pcsi_product_gawk.com
+$!
+$! This command file packages up the product GAWK into a sequential
+$! format kit
+$!
+$! 13-Dec-2013  J.Malmberg
+$!
+$!=========================================================================
+$!
+$! Save default
+$ default_dir = f$environment("DEFAULT")
+$!
+$! Put things back on error.
+$ on warning then goto all_exit
+$!
+$ arch_type = f$getsyi("ARCH_NAME")
+$ arch_code = f$extract(0, 1, arch_type)
+$!
+$ can_build = 1
+$ producer = f$trnlnm("GNV_PCSI_PRODUCER")
+$ if producer .eqs. ""
+$ then
+$   write sys$output "GNV_PCSI_PRODUCER logical name has not been set."
+$   can_build = 0
+$ endif
+$ producer_full_name = f$trnlnm("GNV_PCSI_PRODUCER_FULL_NAME")
+$ if producer_full_name .eqs. ""
+$ then
+$   write sys$output -
+        "GNV_PCSI_PRODUCER_FULL_NAME logical name has not been set."
+$   can_build = 0
+$ endif
+$ stage_root_name = f$trnlnm("STAGE_ROOT")
+$ if stage_root_name .eqs. ""
+$ then
+$   write sys$output "STAGE_ROOT logical name has not been set."
+$   can_build = 0
+$ endif
+$!
+$ if (can_build .eq. 0)
+$ then
+$   write sys$output "Not able to build a kit."
+$   goto all_exit
+$ endif
+$!
+$!
+$! Build the gawk image(s)
+$!-------------------------
+$ if f$search("gawk.exe") .eqs. ""
+$ then
+$   mmk/descrip=[.vms]descrip.mms gawk
+$ endif
+$ if arch_code .nes. "V"
+$ then
+$   if f$search("filefuncs.exe") .eqs. ""
+$   then
+$       mmk/descrip=[.vms]descrip.mms extensions
+$   endif
+$ endif
+$!
+$! Build the gawk_verb.cld
+$!-------------------------
+$ if f$search("gawk_verb.cld") .eqs. ""
+$ then
+$   @[.vms]gawk_verb.com
+$ endif
+$!
+$! Stage the images for building the kit
+$!--------------------------------------
+$ @[.vms]stage_gawk_install.com remove
+$ @[.vms]stage_gawk_install.com
+$!
+$!
+$!
+$! Make sure that the kit name is up to date for this build
+$!----------------------------------------------------------
+$ @[.vms]make_pcsi_gawk_kit_name.com
+$!
+$! Make sure that the release note file name is up to date
+$!---------------------------------------------------------
+$ @[.vms]build_gawk_release_notes.com
+$!
+$!
+$! Make sure that the source has been backed up.
+$!----------------------------------------------
+$ @[.vms]backup_gawk_src.com
+$!
+$! Regenerate the PCSI description file.
+$!--------------------------------------
+$ @[.vms]build_gawk_pcsi_desc.com
+$!
+$! Regenerate the PCSI Text file.
+$!---------------------------------
+$ @[.vms]build_gawk_pcsi_text.com
+$!
+$!
+$! Parse the kit name into components.
+$!---------------------------------------
+$ kit_name = f$trnlnm("GNV_PCSI_KITNAME")
+$ if kit_name .eqs. ""
+$ then
+$   write sys$output "@[.vms]make_pcsi_gawk_kit_name.com has not been run."
+$   goto all_exit
+$ endif
+$ producer = f$element(0, "-", kit_name)
+$ base = f$element(1, "-", kit_name)
+$ product_name = f$element(2, "-", kit_name)
+$ mmversion = f$element(3, "-", kit_name)
+$ majorver = f$extract(0, 3, mmversion)
+$ minorver = f$extract(3, 2, mmversion)
+$ updatepatch = f$element(4, "-", kit_name)
+$ if updatepatch .eqs. "" then updatepatch = ""
+$!
+$ version_fao = "!AS.!AS"
+$ mmversion = f$fao(version_fao, "''majorver'", "''minorver'")
+$ if updatepatch .nes. ""
+$ then
+$   version = "''mmversion'" + "-" + updatepatch
+$ else
+$   version = "''mmversion'"
+$ endif
+$!
+$!
+$! Move to the base directories
+$ current_default = f$environment("DEFAULT")
+$ my_dir = f$parse(current_default,,,"DIRECTORY") - "[" - "<" - ">" - "]"
+$!
+$!
+$ source = "''default_dir'"
+$ src1 = "new_gnu:[bin],"
+$ src2 = "new_gnu:[usr.bin],"
+$ src3 = "new_gnu:[vms_bin],"
+$ src4 = "new_gnu:[vms_help],"
+$ src5 = "new_gnu:[vms_src],"
+$ src6 = "new_gnu:[common_src],"
+$ src7 = "sys$disk:[''my_dir'],sys$disk:[''my_dir'.vms],"
+$ src8 = "new_gnu:[usr.share.awk],"
+$ src9 = "new_gnu:[usr.share.man.man1],"
+$ src10 = "new_gnu:[usr.share.doc.gawk],"
+$ src11 = "new_gnu:[usr.share.info],"
+$ src12 = "sys$disk:[''m_dir'.pc.awklib]"
+$ gnu_src = src1 + src2 + src3 + src4 + src5 + src6 + src7 + src8 + src9
+$ gnu_src = gnu_src + src10 + src11 + src12
+$!
+$!
+$ base = ""
+$ arch_name = f$edit(f$getsyi("arch_name"),"UPCASE")
+$ if arch_name .eqs. "ALPHA" then base = "AXPVMS"
+$ if arch_name .eqs. "IA64" then base = "I64VMS"
+$ if arch_name .eqs. "VAX" then base = "VAXVMS"
+$!
+$ if base .eqs. "" then exit 44
+$!
+$ pcsi_option = "/option=noconfirm"
+$ if arch_code .eqs. "V"
+$ then
+$   pcsi_option = ""
+$ endif
+$!
+$!
+$product package 'product_name' -
+ /base='base' -
+ /producer='producer' -
+ /source='source' -
+ /destination=STAGE_ROOT:[KIT] -
+ /material=('gnu_src','source') -
+ /format=sequential 'pcsi_option'
+$!
+$!
+$! VAX can not do a compressed kit.
+$! ZIP -9 "-V" does a better job, so no reason to normally build a compressed
+$! kit.
+$!----------------------------------
+$if p1 .eqs. "COMPRESSED"
+$then
+$   if arch_code .nes. "V"
+$   then
+$       product copy /options=(novalidate, noconfirm) /format=compressed -
+        'product_name' -
+        /source=stage_root:[kit]/dest=stage_root:[kit] -
+        /version='version'/base='base'
+$   endif
+$endif
+$!
+$all_exit:
+$ set def 'default_dir'
+$ exit
diff --git a/vms/remove_old_gawk.com b/vms/remove_old_gawk.com
new file mode 100644
index 00000000..ed68fc45
--- /dev/null
+++ b/vms/remove_old_gawk.com
@@ -0,0 +1,113 @@
+$! File: remove_old_gawk.com
+$!
+$! This is a procedure to remove the old gawk images that were installed
+$! by the GNV kits and replace them with links to the new image.
+$!
+$! 02-Jan-2014  J. Malmberg	Gawk version
+$!
+$!==========================================================================
+$!
+$vax = f$getsyi("HW_MODEL") .lt. 1024
+$old_parse = ""
+$if .not. VAX
+$then
+$   old_parse = f$getjpi("", "parse_style_perm")
+$   set process/parse=extended
+$endif
+$!
+$old_cutils = "gawk,awk,"
+$!
+$!
+$ i = 0
+$cutils_loop:
+$   file = f$element(i, ",", old_cutils)
+$   if file .eqs. "" then goto cutils_loop_end
+$   if file .eqs. "," then goto cutils_loop_end
+$   call update_old_image 'file'
+$   i = i + 1
+$   goto cutils_loop
+$cutils_loop_end:
+$!
+$!
+$if .not. VAX
+$then
+$   file = "gnv$gnu:[usr.share.man.cat1]awk^.1.gz"
+$   if f$search(file) .nes. "" then delete 'file';*
+$   file = "gnv$gnu:[usr.share.man.cat1]gawk^.1.gz"
+$   if f$search(file) .nes. "" then delete 'file';*
+$   file = "gnv$gnu:[usr.share.man.cat1]iawk^.1.gz"
+$   if f$search(file) .nes. "" then delete 'file';*
+$endif
+$!
+$!
+$if .not. VAX
+$then
+$   set process/parse='old_parse'
+$endif
+$!
+$all_exit:
+$  exit
+$!
+$! Remove old image or update it if needed.
+$!-------------------------------------------
+$update_old_image: subroutine
+$!
+$ file = p1
+$! First get the FID of the new gawk image.
+$! Don't remove anything that matches it.
+$ new_gawk = f$search("GNV$GNU:[BIN]GNV$''file'.EXE")
+$!
+$ new_gawk_fid = "No_new_gawk_fid"
+$ if new_gawk .nes. ""
+$ then
+$   new_gawk_fid = f$file_attributes(new_gawk, "FID")
+$ endif
+$!
+$!
+$!
+$! Now get check the "''file'." and "''file'.exe"
+$! May be links or copies.
+$! Ok to delete and replace.
+$!
+$!
+$ old_gawk_fid = "No_old_gawk_fid"
+$ old_gawk = f$search("gnv$gnu:[bin]''file'.")
+$ old_gawk_exe_fid = "No_old_gawk_fid"
+$ old_gawk_exe = f$search("gnv$gnu:[bin]''file'.exe")
+$ if old_gawk_exe .nes. ""
+$ then
+$   old_gawk_exe_fid = f$file_attributes(old_gawk_exe, "FID")
+$ endif
+$!
+$ if old_gawk .nes. ""
+$ then
+$   fid = f$file_attributes(old_gawk, "FID")
+$   if fid .nes. new_gawk_fid
+$   then
+$       if fid .eqs. old_gawk_exe_fid
+$       then
+$           set file/remove 'old_gawk'
+$       else
+$           delete 'old_gawk'
+$       endif
+$       if new_gawk .nes. ""
+$       then
+$           set file/enter='old_gawk' 'new_gawk'
+$       endif
+$   endif
+$ endif
+$!
+$ if old_gawk_exe .nes. ""
+$ then
+$   if old_gawk_fid .nes. new_gawk_fid
+$   then
+$       delete 'old_gawk_exe'
+$       if new_gawk .nes. ""
+$       then
+$           set file/enter='old_gawk_exe' 'new_gawk'
+$       endif
+$   endif
+$ endif
+$!
+$ exit
+$ENDSUBROUTINE ! Update old image
diff --git a/vms/stage_gawk_install.com b/vms/stage_gawk_install.com
new file mode 100644
index 00000000..22daf7f5
--- /dev/null
+++ b/vms/stage_gawk_install.com
@@ -0,0 +1,300 @@
+$! File: stage_gawk_install.com
+$!
+$! Stages the build products to new_gnu:[...] for testing and for building
+$! a kit.
+$!
+$! If p1 starts with "R" then remove instead of install.
+$!
+$! The file PCSI_GAWK_FILE_LIST.TXT is read in to get the files other
+$! than the release notes file and the source backup file.
+$!
+$! The PCSI system can really only handle ODS-2 format filenames and
+$! assumes that there is only one source directory.  It also assumes that
+$! all destination files with the same name come from the same source file.
+$!
+$!
+$! 29-Sep-2013  J. Malmberg
+$!
+$!===========================================================================
+$!
+$ arch_type = f$getsyi("ARCH_NAME")
+$ arch_code = f$extract(0, 1, arch_type)
+$!
+$ mode = "install"
+$ code = f$extract(0, 1, p1)
+$ if code .eqs. "R" .or. code .eqs. "r" then mode = "remove"
+$!
+$!  First create the directories
+$!--------------------------------
+$ if mode .eqs. "install"
+$ then
+$   create/dir new_gnu:[bin]/prot=o:rwed
+$   create/dir new_gnu:[vms_bin]/prot=o:rwed
+$   create/dir new_gnu:[vms_help]/prot=o:rwed
+$   create/dir new_gnu:[lib]/prot=o:rwed
+$   create/dir new_gnu:[usr.bin]/prot=o:rwed
+$   create/dir new_gnu:[usr.include]/prot=o:rwed
+$   create/dir new_gnu:[usr.lib.gawk]/prot=o:rwed
+$   create/dir new_gnu:[usr.share.awk]/prot=o:rwed
+$   create/dir new_gnu:[usr.share.doc.gawk]/prot=o:rwed
+$   create/dir new_gnu:[usr.share.info]/prot=o:rwed
+$   create/dir new_gnu:[usr.src.gawk.extension.vms]/prot=o:rwed
+$   create/dir new_gnu:[usr.share.doc.man.man1]/prot=o:rwed
+$ endif
+$!
+$ if mode .eqs. "install"
+$ then
+$    copy [.vms]gnv_gawk_startup.com -
+         new_gnu:[vms_bin]gnv$gawk_startup.com
+$ else
+$    file = "new_gnu:[vms_bin]gnv$gawk_startup.com"
+$    if f$search(file) .nes. "" then delete 'file';*
+$ endif
+$!
+$!
+$!   Read through the file list to set up aliases and rename commands.
+$!---------------------------------------------------------------------
+$ open/read flst [.vms]pcsi_gawk_file_list.txt
+$!
+$inst_alias_loop:
+$   ! Skip the aliases
+$   read/end=inst_file_loop_end flst line_in
+$   line_in = f$edit(line_in,"compress,trim,uncomment")
+$   if line_in .eqs. "" then goto inst_alias_loop
+$   pathname = f$element(0, " ", line_in)
+$   linkflag = f$element(1, " ", line_in)
+$   if linkflag .nes. "->" then goto inst_alias_done
+$   goto inst_alias_loop
+$!
+$inst_file_loop:
+$!
+$   read/end=inst_file_loop_end flst line_in
+$   line_in = f$edit(line_in,"compress,trim,uncomment")
+$   if line_in .eqs. "" then goto inst_file_loop
+$!
+$inst_alias_done:
+$!
+$!
+$!   Skip the directories as we did them above.
+$!   Just process the files.
+$   tdir = f$parse(line_in,,,"DIRECTORY")
+$   tdir_len = f$length(tdir)
+$   tname = f$parse(line_in,,,"NAME")
+$   lctname = f$edit(tname, "LOWERCASE")
+$   ttype = f$parse(line_in,,,"TYPE")
+$   if arch_code .eqs. "V"
+$   then
+$       tname = lctname
+$       ttype = f$edit(ttype, "LOWERCASE")
+$       tdir = f$edit(tdir, "LOWERCASE")
+$   endif
+$   if tname .eqs. "" then goto inst_file_loop
+$   if ttype .eqs. ".dir" then goto inst_file_loop
+$!
+$!   if p1 starts with "R" then remove instead of install.
+$!
+$!   If gnv$xxx.exe, then:
+$!       Source is []gnv$gawk.exe
+$!       Destination1 is new_gnu:[bin]gnv$gawk.exe
+$!       Destination2 is new_gnu:[bin]xxx.  (alias)
+$!       Destination2 is new_gnu:[bin]xxx.exe  (alias)
+$!       We put all in new_gnu:[bin] instead of some in [usr.bin] because
+$!       older GNV kits incorrectly put some images in [bin] and [bin]
+$!       comes first in the search list.
+$   if f$locate("gnv$", tname) .eq. 0
+$   then
+$       myfile_len = f$length(tname)
+$       myfile = f$extract(4, myfile_len, tname)
+$       source = "[]''myfile'''ttype'"
+$       dest1 = "new_gnu:[bin]''tname'''ttype'"
+$       dest2 = "new_gnu:[bin]''myfile'."
+$       dest3 = "new_gnu:[bin]''myfile'.exe"
+$       if mode .eqs. "install"
+$       then
+$           if f$search(dest1) .eqs. "" then copy 'source' 'dest1'
+$           if f$search(dest2) .eqs. "" then set file/enter='dest2' 'dest1'
+$           if f$search(dest3) .eqs. "" then set file/enter='dest3' 'dest1'
+$       else
+$           if f$search(dest2) .nes. "" then set file/remove 'dest2';*
+$           if f$search(dest3) .nes. "" then set file/remove 'dest3';*
+$           if f$search(dest1) .nes. "" then delete 'dest1';*
+$       endif
+$       goto inst_file_loop
+$   endif
+$!
+$!   If lib.gawk] then
+$!       source is sys$disk:[]
+$!       dest is new_gnu:[usr.lib.gawk]
+$    if f$locate("lib.gawk]", tdir) .lt. tdir_len
+$    then
+$!       ! Not yet available on VAX/VMS
+$        if arch_code .eqs. "V" then goto inst_file_loop
+$!
+$        source = "[]''tname'''ttype'"
+$        dest = "new_gnu:[usr.lib.gawk]''tname'''ttype'"
+$        if mode .eqs. "install"
+$        then
+$            if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$        else
+$            if f$search(dest) .nes. "" then delete 'dest';*
+$        endif
+$        goto inst_file_loop
+$    endif
+$!
+$!   If .vms_bin] then
+$!       source is sys$disk:[]
+$!       dest is [vms_bin]
+$   if (f$locate("vms_bin]", tdir) .lt. tdir_len)
+$   then
+$       if (ttype .eqs. ".cld")
+$       then
+$           source = "sys$disk:[]''tname'''ttype'"
+$       else
+$           source = "sys$disk:[.vms]''tname'''ttype'"
+$       endif
+$       dest = "new_gnu:[vms_bin]''tname'''ttype'"
+$       if mode .eqs. "install"
+$       then
+$           if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$       else
+$           if f$search(dest) .nes. "" then delete 'dest';*
+$       endif
+$       goto inst_file_loop
+$   endif
+$!
+$!   If .vms_hlp] then
+$!       source is sys$disk:[.vms]
+$!       dest is [vms_help]
+$   if (f$locate("vms_help]", tdir) .lt. tdir_len) .and. (ttype .eqs. ".hlp")
+$   then
+$       source = "sys$disk:[.vms]''tname'''ttype'"
+$       dest = "new_gnu:[vms_help]''tname'''ttype'"
+$       if mode .eqs. "install"
+$       then
+$           if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$       else
+$           if f$search(dest) .nes. "" then delete 'dest';*
+$       endif
+$       goto inst_file_loop
+$   endif
+$!
+$!   If doc.gawk] then
+$!       source is sys$disk:[] or [.readme_d]
+$!       dest is [usr.share.doc.gawk]
+$   if f$locate(".doc.gawk]", tdir) .lt. tdir_len
+$   then
+$       if lctname .eqs. "readme" .and. ttype .nes. "."
+$       then
+$           source = "sys$disk:[.README_D]''tname'''ttype'"
+$           if f$search(source) .eqs. ""
+$           then
+$!              ! This may be an NFS mangled name on VAX.
+$               stype = ttype - "."
+$               if stype .nes. "vms" then stype = "$" + stype
+$               source = "sys$disk:[.$README_$D]$README.''stype'"
+$           endif
+$       else
+$           source = "sys$disk:[]''tname'''ttype'"
+$           if f$search(source) .eqs. ""
+$           then
+$               source = "sys$disk:[]$''tname'''ttype'"
+$           endif
+$       endif
+$       dest = "new_gnu:[usr.share.doc.gawk]''tname'''ttype'"
+$       if mode .eqs. "install"
+$       then
+$           if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$       else
+$           if f$search(dest) .nes. "" then delete 'dest';*
+$       endif
+$       goto inst_file_loop
+$   endif
+$!
+$!   If .awk] then
+$!       source is sys$disk:[.awklib.eg.lib]
+$!       dest is new_gnu:[usr.share.awk]
+$    if f$locate(".awk]", tdir) .lt. tdir_len
+$    then
+$        source = "[.awklib.eg.lib]''tname'''ttype'"
+$        dest = "new_gnu:[usr.share.awk]''tname'''ttype'"
+$        if mode .eqs. "install"
+$        then
+$            if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$        else
+$            if f$search(dest) .nes. "" then delete 'dest';*
+$        endif
+$        goto inst_file_loop
+$    endif
+$!
+$!   If *.info then
+$!       source is [.doc]gawk.info
+$!       dest is [.usr.share.info]
+$    if ttype .eqs. ".info"
+$    then
+$        source = "[.doc]''tname'''ttype'"
+$        dest = "new_gnu:[usr.share.info]''tname'''ttype'"
+$        if mode .eqs. "install"
+$        then
+$            if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$        else
+$            if f$search(dest) .nes. "" then delete 'dest';*
+$        endif
+$        goto inst_file_loop
+$    endif
+$!
+$!   If *.h then
+$!       source is []*.h
+$!       dest is [.usr.include]
+$    if ttype .eqs. ".h"
+$    then
+$        source = "[]''tname'''ttype'"
+$        dest = "new_gnu:[usr.include]''tname'''ttype'"
+$        if mode .eqs. "install"
+$        then
+$            if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$        else
+$            if f$search(dest) .nes. "" then delete 'dest';*
+$        endif
+$        goto inst_file_loop
+$    endif
+$!
+$!   If *.opt then
+$!       source is [.vms]gawk_plugin.opt
+$!       dest is [.usr.src.gawk.extension.vms]
+$    if ttype .eqs. ".opt"
+$    then
+$        source = "[.vms]''tname'''ttype'"
+$        dest = "new_gnu:[usr.src.gawk.extension.vms]''tname'''ttype'"
+$        if mode .eqs. "install"
+$        then
+$            if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$        else
+$            if f$search(dest) .nes. "" then delete 'dest';*
+$        endif
+$        goto inst_file_loop
+$    endif
+$!
+$!   If xxx.1 then
+$!       source is [.doc]xxx.1
+$!       dest is [usr.share.man.man1]
+$    if ttype .eqs. ".1"
+$    then
+$        source = "[.doc]''tname'''ttype'"
+$        dest = "new_gnu:[usr.share.man.man1]''tname'''ttype'"
+$        if mode .eqs. "install"
+$        then
+$            if f$search(dest) .eqs. "" then copy 'source' 'dest'
+$        else
+$            if f$search(dest) .nes. "" then delete 'dest';*
+$        endif
+$        goto inst_file_loop
+$    endif
+$!
+$    goto inst_file_loop
+$!
+$inst_file_loop_end:
+$!
+$close flst
+$!
+$all_exit:
+$   exit
diff --git a/vms/vax/ChangeLog b/vms/vax/ChangeLog
new file mode 100644
index 00000000..7cf2c4fa
--- /dev/null
+++ b/vms/vax/ChangeLog
@@ -0,0 +1,11 @@
+2014-04-08         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* 4.1.1: Release tar ball made.
+
+2013-12-29         John Malmberg         <wb8tyw@qsl.net>
+
+	* ChangeLog: New directory.
+	* gawk_plugin_xfer.mar_exact, gawk_plugin_xfer.opt,
+	  macro32_exactcase.com, macro32_exactcase.patch:
+	  These are experimental files for future support of
+	  dynamic extensions on VAX/VMS.
diff --git a/vms/vax/gawk_plugin_xfer.mar_exact b/vms/vax/gawk_plugin_xfer.mar_exact
new file mode 100644
index 00000000..e90babbd
--- /dev/null
+++ b/vms/vax/gawk_plugin_xfer.mar_exact
@@ -0,0 +1,13 @@
+	.PSECT GAWK_PLUGIN_XFERVECTORS -
+			PIC,USR,CON,REL,GBL,SHR,EXE,RD,NOWRT,QUAD
+
+;	Exact case transfer vector and universal symbols
+;
+	.ALIGN QUAD
+	.EXTERNAL plugin_is_GPL_compatible
+
+	.TRANSFER dl_load
+	.MASK dl_load
+	JMP L^dl_load+2
+
+	.END
diff --git a/vms/vax/gawk_plugin_xfer.opt b/vms/vax/gawk_plugin_xfer.opt
new file mode 100644
index 00000000..75c134f7
--- /dev/null
+++ b/vms/vax/gawk_plugin_xfer.opt
@@ -0,0 +1,5 @@
+CASE_SENSITIVE=YES
+UNIVERSAL=plugin_is_GPL_compatible
+UNIVERSAL=dl_load
+!CLUSTER=GAWK_PLUGIN_XFER
+!COLLECT=GAWK_GLOBAL, GAWK_PLUGIN_XFERVECTORS
diff --git a/vms/vax/macro32_exactcase.com b/vms/vax/macro32_exactcase.com
new file mode 100644
index 00000000..79194e21
--- /dev/null
+++ b/vms/vax/macro32_exactcase.com
@@ -0,0 +1,16 @@
+$!
+$! Patch the Macro32 compiler and optional assemble
+$!-----------------------------------------------------
+$ patched_macro = "sys$disk:[]macro32_exactcase.exe"
+$ if f$search(patched_macro) .eqs. ""
+$ then
+$   copy sys$system:macro32.exe 'patched_macro'
+$   patch @[.vms]macro32_exactcase.patch
+$ endif
+$! Usage:
+$ xfer_file_source = p1
+$ if f$search(p1) .nes. ""
+$ then
+$    define/user macro32 'patched_macro'
+$    macro/lis 'p1'
+$ endif
diff --git a/vms/vax/macro32_exactcase.patch b/vms/vax/macro32_exactcase.patch
new file mode 100644
index 00000000..eda5cac7
--- /dev/null
+++ b/vms/vax/macro32_exactcase.patch
@@ -0,0 +1,11 @@
+macro32_exactcase.exe
+SE EC
+^X00000001
+RE /I
+^X00012B1D
+'BICB2 #^X00000020,R3'
+EXIT
+'BICB2 #^X00000000,R3'
+EXI
+U
+EXI
diff --git a/vms/vms-conf.h b/vms/vms-conf.h
deleted file mode 100644
index 575b5de6..00000000
--- a/vms/vms-conf.h
+++ /dev/null
@@ -1,678 +0,0 @@
-#ifndef CONFIG_H
-#define CONFIG_H
-/*
- * config.h -- configuration definitions for gawk.
- *
- * For VMS (assumes V4.6 or later; tested on V7.3-1, V8.3.
- */
-
-/* 
- * Copyright (C) 1991-1992, 1995-1996, 1999, 2001-2003, 2005, 2009, 2010, 2011,
- * 2012, the Free Software Foundation, Inc.
- * 
- * This file is part of GAWK, the GNU implementation of the
- * AWK Programming Language.
- * 
- * GAWK is free software; you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation; either version 3 of the License, or
- * (at your option) any later version.
- * 
- * GAWK is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- * GNU General Public License for more details.
- * 
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
- */
-
-#if 0		/* no longer used */
-/* Define to 1 if using alloca.c.  */
-#define C_ALLOCA 1
-#else
-#define NO_ALLOCA	/* vms/vms_fwrite.c needs this */
-/* If using the C implementation of alloca, define if you know the
-   direction of stack growth for your system; otherwise it will be
-   automatically deduced at run-time.
-	STACK_DIRECTION > 0 => grows toward higher addresses
-	STACK_DIRECTION < 0 => grows toward lower addresses
-	STACK_DIRECTION = 0 => direction of growth unknown */
-#define STACK_DIRECTION (-1)
-#endif /*0*/
-
-#include <bitypes.h>
-#define INT32_MAX __INT32_MAX
-#define INT32_MIN __INT32_MIN
-
-/* dynamic loading is possible */
-#undef DYNAMIC
-
-/* Define to 1 if translation of program messages to the user's native
-   language is requested. */
-#undef ENABLE_NLS
-
-/* Define to the type of elements in the array set by `getgroups'. Usually
-   this is either `int' or `gid_t'. */
-#define GETGROUPS_T int
-
-/* Define to 1 if the `getpgrp' function requires zero arguments. */
-#define GETPGRP_VOID	1
-
-/* Define to 1 if you have the `alarm' function. */
-#define HAVE_ALARM 1
-
-/* Define to 1 if you have the <arpa/inet.h> header file. */
-#undef HAVE_ARPA_INET_H
-
-/* Define to 1 if you have the `atexit' function. */
-#define HAVE_ATEXIT 1
-
-/* Define to 1 if you have the `btowc' function. */
-#undef HAVE_BTOWC
-
-/* Define to 1 if you have the MacOS X function CFLocaleCopyCurrent in the
-   CoreFoundation framework. */
-#undef HAVE_CFLOCALECOPYCURRENT
-
-/* Define to 1 if you have the MacOS X function CFPreferencesCopyAppValue in
-   the CoreFoundation framework. */
-#undef HAVE_CFPREFERENCESCOPYAPPVALUE
-
-/* Define if the GNU dcgettext() function is already present or preinstalled.
-   */
-#undef HAVE_DCGETTEXT
-
-/* Define to 1 if you have the declaration of `tzname', and to 0 if you don't.
-   */
-#undef HAVE_DECL_TZNAME
-
-/* Define to 1 if you don't have `vprintf' but do have `_doprnt.' */
-#undef HAVE_DOPRNT
-
-/* Define to 1 if you have the <fcntl.h> header file. */
-#undef HAVE_FCNTL_H
-
-/* Define to 1 if you have the `fmod' function. */
-#define HAVE_FMOD 1
-
-/* have getaddrinfo */
-#undef HAVE_GETADDRINFO
-
-/* Define to 1 if you have the `getgrent' function. */
-#undef HAVE_GETGRENT
-
-/* Define to 1 if you have the `getgroups' function. */
-#undef HAVE_GETGROUPS
-
-/* Define if the GNU gettext() function is already present or preinstalled. */
-#undef HAVE_GETTEXT
-
-/* Define to 1 if you have the `grantpt' function. */
-#undef HAVE_GRANTPT
-
-/* Define if you have the iconv() function. */
-#undef HAVE_ICONV
-
-/* Define if you have the 'intmax_t' type in <stdint.h> or <inttypes.h>. */
-#undef HAVE_INTMAX_T
-
-/* Define to 1 if you have the <inttypes.h> header file. */
-#undef HAVE_INTTYPES_H
-
-/* Define if <inttypes.h> exists, doesn't clash with <sys/types.h>, and
-   declares uintmax_t. */
-#undef HAVE_INTTYPES_H_WITH_UINTMAX
-
-/* Define to 1 if you have the `isascii' function. */
-#define HAVE_ISASCII 1
-
-/* Define to 1 if you have the `iswctype' function. */
-#define HAVE_ISWCTYPE 1
-
-/* Define to 1 if you have the `iswlower' function. */
-#define HAVE_ISWLOWER 1
-
-/* Define to 1 if you have the `iswupper' function. */
-#define HAVE_ISWUPPER 1
-
-/* Define if you have <langinfo.h> and nl_langinfo(CODESET). */
-#undef HAVE_LANGINFO_CODESET
-
-/* Define if your <locale.h> file defines LC_MESSAGES. */
-#undef HAVE_LC_MESSAGES
-
-/* Define to 1 if you have the <libintl.h> header file. */
-#undef HAVE_LIBINTL_H
-
-/* Define if you have the libsigsegv library. */
-#undef HAVE_LIBSIGSEGV
-
-/* Define to 1 if you have the `m' library (-lm). */
-#undef HAVE_LIBM
-
-/* Define to 1 if you have a fully functional readline library. */
-#undef HAVE_LIBREADLINE
-
-/* Define to 1 if you have the <limits.h> header file. */
-#define HAVE_LIMITS_H 1
-
-/* Define to 1 if you have the <locale.h> header file. */
-#undef HAVE_LOCALE_H
-
-/* Define if you have the 'long long' type. */
-#undef HAVE_LONG_LONG
-
-/* Define to 1 if the system has the type `long long int'. */
-#undef HAVE_LONG_LONG_INT
-
-/* Define to 1 if you have the `mbrlen' function. */
-#define HAVE_MBRLEN 1
-
-/* Define to 1 if mbrtowc and mbstate_t are properly declared. */
-#define HAVE_MBRTOWC 1
-
-/* Define to 1 if you have the <mcheck.h> header file. */
-#undef HAVE_MCHECK_H
-
-/* Define to 1 if you have the `memcmp' function. */
-#define HAVE_MEMCMP 1
-
-/* Define to 1 if you have the `memcpy' function. */
-#define HAVE_MEMCPY 1
-
-/* Define to 1 if you have the `memcpy_ulong' function. */
-#undef HAVE_MEMCPY_ULONG
-
-/* Define to 1 if you have the `memmove' function. */
-#define HAVE_MEMMOVE 1
-
-/* Define to 1 if you have the <memory.h> header file. */
-#undef HAVE_MEMORY_H
-
-/* Define to 1 if you have the `memset' function. */
-#define HAVE_MEMSET 1
-
-/* Define to 1 if you have the `memset_ulong' function. */
-#undef HAVE_MEMSET_ULONG
-
-/* Define to 1 if you have the `mkstemp' function. */
-#undef HAVE_MKSTEMP
-
-/* we have the mktime function */
-#define HAVE_MKTIME 1
-
-/* Define to 1 if you have the <netdb.h> header file. */
-#undef HAVE_NETDB_H
-
-/* Define to 1 if you have the <netinet/in.h> header file. */
-#undef HAVE_NETINET_IN_H
-
-/* we'll use the one in [.missing_d] */
-#undef HAVE_SETENV
-
-/* Define to 1 if you have the `setlocale' function. */
-#undef HAVE_SETLOCALE
-
-/* Define to 1 if you have the `setsid' function. */
-#undef HAVE_SETSID
-
-/* Define to 1 if you have the `snprintf' function. */
-#undef HAVE_SNPRINTF
-
-/* newer systems define this type here */
-#undef HAVE_SOCKADDR_STORAGE
-
-/* we have sockets on this system */
-#undef HAVE_SOCKETS
-
-/* Define to 1 if you have the <stdarg.h> header file. */
-#define HAVE_STDARG_H 1
-
-/* Define to 1 if you have the <stddef.h> header file. */
-#define HAVE_STDDEF_H 1
-
-/* Define to 1 if you have the <stdint.h> header file. */
-#undef HAVE_STDINT_H
-
-/* Define if <stdint.h> exists, doesn't clash with <sys/types.h>, and declares
-   uintmax_t. */
-#undef HAVE_STDINT_H_WITH_UINTMAX
-
-/* Define to 1 if you have the <stdlib.h> header file. */
-#define HAVE_STDLIB_H 1
-
-/* Define to 1 if you have the `strchr' function. */
-#define HAVE_STRCHR 1
-
-/* Define to 1 if you have the `strcoll' function. */
-#define HAVE_STRCOLL 1
-
-/* Define to 1 if you have the `strerror' function. */
-#define HAVE_STRERROR 1
-
-/* Define to 1 if you have the `strftime' function. */
-#undef HAVE_STRFTIME		/* use the missing_d/strfime.c version */
-
-/* Define to 1 if cpp supports the ANSI # stringizing operator. */
-#ifdef VAXC
-#undef HAVE_STRINGIZE
-#else
-#define HAVE_STRINGIZE 1
-#endif
-
-/* Define to 1 if you have the <strings.h> header file. */
-#undef HAVE_STRINGS_H
-
-/* Define to 1 if you have the <string.h> header file. */
-#define HAVE_STRING_H 1
-
-/* Define to 1 if you have the `strncasecmp' function. */
-#undef HAVE_STRNCASECMP
-
-/* Define to 1 if you have the <stropts.h> header file. */
-#undef HAVE_STROPTS_H
-
-/* Define to 1 if you have the `strtod' function. */
-#define HAVE_STRTOD 1
-
-/* Define to 1 if you have the `strtoul' function. */
-#define HAVE_STRTOUL 1
-
-/* Define to 1 if `st_blksize' is a member of `struct stat'. */
-#undef HAVE_STRUCT_STAT_ST_BLKSIZE
-
-/* Define to 1 if `tm_zone' is a member of `struct tm'. */
-#undef HAVE_STRUCT_TM_TM_ZONE
-
-/* Define to 1 if you have the `system' function. */
-#define HAVE_SYSTEM 1
-
-/* Define to 1 if you have the <sys/ioctl.h> header file. */
-#undef HAVE_SYS_IOCTL_H
-
-/* Define to 1 if you have the <sys/param.h> header file. */
-#undef HAVE_SYS_PARAM_H
-
-/* Define to 1 if you have the <sys/socket.h> header file. */
-#undef HAVE_SYS_SOCKET_H
-
-/* Define to 1 if you have the <sys/stat.h> header file. */
-#undef HAVE_SYS_STAT_H
-
-/* Define to 1 if you have the <sys/time.h> header file. */
-#undef HAVE_SYS_TIME_H
-
-/* Define to 1 if you have the <sys/types.h> header file. */
-#undef HAVE_SYS_TYPES_H
-
-/* Define to 1 if you have <sys/wait.h> that is POSIX.1 compatible. */
-#undef HAVE_SYS_WAIT_H
-
-/* Define to 1 if you have the <termios.h> header file. */
-#undef HAVE_TERMIOS_H
-
-/* Define to 1 if you have the `tmpfile' function. */
-#define HAVE_TMPFILE 1
-/* Force snprintf.c to use tmpfile() instead of mkstemp(). */
-#ifdef HAVE_MKSTEMP
-#undef HAVE_MKSTEMP
-#endif
-
-/* Define to 1 if your `struct tm' has `tm_zone'. Deprecated, use
-   `HAVE_STRUCT_TM_TM_ZONE' instead. */
-#undef HAVE_TM_ZONE
-
-/* Define to 1 if you have the `towlower' function. */
-#define HAVE_TOWLOWER 1
-
-/* Define to 1 if you have the `towupper' function. */
-#define HAVE_TOWUPPER 1
-
-/* Define to 1 if you don't have `tm_zone' but do have the external array
-   `tzname'. */
-#define HAVE_TZNAME 1		/* (faked in vms/vms_misc.c) */
-
-/* Define to 1 if you have the `tzset' function. */
-#define HAVE_TZSET 1		/* (faked in vms/vms_misc.c) */
-
-/* Define if you have the 'uintmax_t' type in <stdint.h> or <inttypes.h>. */
-#undef HAVE_UINTMAX_T
-
-/* Define to 1 if you have the <unistd.h> header file. */
-#ifdef __DECC
-#define HAVE_UNISTD_H 1
-#else
-#undef HAVE_UNISTD_H
-#endif
-
-/* Define if you have the 'unsigned long long' type. */
-#undef HAVE_UNSIGNED_LONG_LONG
-
-/* Define to 1 if the system has the type `unsigned long long int'. */
-#undef HAVE_UNSIGNED_LONG_LONG_INT
-
-/* Define to 1 if you have the `usleep' function. */
-#define HAVE_USLEEP 1
-
-/* Define to 1 if you have the `vprintf' function. */
-#define HAVE_VPRINTF 1
-
-/* Define to 1 if you have the <wchar.h> header file. */
-#define HAVE_WCHAR_H 1
-
-/* Define to 1 if you have the `wcrtomb' function. */
-#define HAVE_WCRTOMB 1
-
-/* Define to 1 if you have the `wcscoll' function. */
-#define HAVE_WCSCOLL 1
-
-/* Define to 1 if you have the `wctype' function. */
-#define HAVE_WCTYPE 1
-
-/* Define to 1 if you have the <wctype.h> header file. */
-#define HAVE_WCTYPE_H 1
-
-/* systems should define this type here */
-#define HAVE_WCTYPE_T 1
-
-/* systems should define this type here */
-#undef HAVE_WINT_T
-
-/* disable fatal errors on directories */
-#undef NO_DIRECTORY_FATAL
-
-/* disable lint checks */
-#undef NO_LINT
-
-/* Name of package */
-#define PACKAGE "gawk"
-
-/* Define to the address where bug reports for this package should be sent. */
-#define PACKAGE_BUGREPORT "bug-gawk@gnu.org"
-
-/* Define to the full name of this package. */
-#define PACKAGE_NAME "GNU Awk"
-
-/* Define to the full name and version of this package. */
-#define PACKAGE_STRING "GNU Awk 4.1.0"
-
-/* Define to the one symbol short name of this package. */
-#define PACKAGE_TARNAME "gawk"
-
-/* Define to the home page for this package. */
-#undef PACKAGE_URL
-
-/* Define to the version of this package. */
-#define PACKAGE_VERSION "4.1.0"
-
-/* Define to 1 if *printf supports %F format */
-#undef PRINTF_HAS_F_FORMAT
-
-/* Define as the return type of signal handlers (`int' or `void'). */
-#define RETSIGTYPE void
-
-/* The size of a `unsigned int', as computed by sizeof. */
-#define SIZEOF_UNSIGNED_INT 4
-
-/* The size of a `unsigned long', as computed by sizeof. */
-#define SIZEOF_UNSIGNED_LONG 4
-
-/* Define to 1 if you have the ANSI C header files. */
-#define STDC_HEADERS 1
-
-/* some systems define this type here */
-#undef TIME_T_IN_SYS_TYPES_H
-
-/* Define to 1 if you can safely include both <sys/time.h> and <time.h>. */
-#undef TIME_WITH_SYS_TIME
-
-/* Define to 1 if your <sys/time.h> declares `struct tm'. */
-#undef TM_IN_SYS_TIME
-
-/* force use of our version of strftime */
-#define USE_INCLUDED_STRFTIME 1
-
-/* Version number of package */
-#define VERSION "4.1.0"
-
-/* Define to 1 if on AIX 3.
-   System headers sometimes define this.
-   We just want to avoid a redefinition error message.  */
-#ifndef _ALL_SOURCE
-# undef _ALL_SOURCE
-#endif
-
-/* Number of bits in a file offset, on hosts where this is settable. */
-#undef _FILE_OFFSET_BITS
-
-/* Enable GNU extensions on systems that have them.  */
-#ifndef _GNU_SOURCE
-# undef _GNU_SOURCE
-#endif
-
-/* Define for large files, on AIX-style hosts. */
-#undef _LARGE_FILES
-
-/* Define to 1 if on MINIX. */
-#undef _MINIX
-
-/* The _Noreturn keyword of C11.  */
-#ifndef _Noreturn
-# if (3 <= __GNUC__ || (__GNUC__ == 2 && 8 <= __GNUC_MINOR__) \
-      || 0x5110 <= __SUNPRO_C)
-#  define _Noreturn __attribute__ ((__noreturn__))
-# elif defined _MSC_VER && 1200 <= _MSC_VER
-#  define _Noreturn __declspec (noreturn)
-# else
-#  define _Noreturn
-# endif
-#endif
-
-/* Define to 2 if the system does not provide POSIX.1 features except with
-   this defined. */
-#undef _POSIX_1_SOURCE
-
-/* Define to 1 if you need to in order for `stat' and other things to work. */
-#undef _POSIX_SOURCE
-
-/* Define to 1 if type `char' is unsigned and you are not using gcc.  */
-#ifndef __CHAR_UNSIGNED__
-# undef __CHAR_UNSIGNED__
-#endif
-
-/* Enable extensions on Solaris.  */
-#ifndef __EXTENSIONS__
-# undef __EXTENSIONS__
-#endif
-#ifndef _POSIX_PTHREAD_SEMANTICS
-# undef _POSIX_PTHREAD_SEMANTICS
-#endif
-#ifndef _TANDEM_SOURCE
-# undef _TANDEM_SOURCE
-#endif
-
-/* Define to empty if `const' does not conform to ANSI C. */
-#undef const
-
-/* Define to `int' if <sys/types.h> doesn't define. */
-#undef gid_t
-
-/* Define to `__inline__' or `__inline' if that's what the C compiler
-   calls it, or to nothing if 'inline' is not supported under any name.  */
-#ifndef __cplusplus
-#undef inline
-#endif
-
-/* Define to widest signed type if <inttypes.h> doesn't define. */
-#define intmax_t long int
-
-/* Define to `int' if <sys/types.h> doesn't define.  */
-#undef pid_t
-
-/* Define to the equivalent of the C99 'restrict' keyword, or to
-   nothing if this is not supported.  Do not define if restrict is
-   supported directly.  */
-#define restrict
-#if defined(__DECC) && (__DECC_VER >= 60400000)
-#undef restrict
-#endif
-
-/* Define to `unsigned' if <sys/types.h> doesn't define.  */
-#undef size_t
-
-/* type to use in place of socklen_t if not defined */
-#undef socklen_t
-
-/* Define to `int' if <sys/types.h> does not define. */
-#define ssize_t int
-
-/* Define to `int' if <sys/types.h> doesn't define.  */
-#undef uid_t
-
-/* Define to unsigned long or unsigned long long if <stdint.h> and
-   <inttypes.h> don't define. */
-#define uintmax_t unsigned long
-
-#if 0
-#include "custom.h"	/* overrides for stuff autoconf can't deal with */
-#else
-
-/* Whether `time_t' is an unsigned type. */
-#define TIME_T_UNSIGNED 1
-
-/* Extension for shared libraries */
-#define SHLIBEXT	"exe"
-
-
-/*******************************/
-/* Gawk configuration options. */
-/*******************************/
-
-/*
- * DEFPATH
- *	VMS: "/AWK_LIBRARY" => "AWK_LIBRARY:"
- * The default search path for the -f option of gawk.  It is used
- * if the AWKPATH environment variable is undefined.
- *
- * Note: OK even if no AWK_LIBRARY logical name has been defined.
- */
-
-#define DEFPATH	".,/AWK_LIBRARY"
-#define DEFLIBPATH ".,/AWK_LIBRARY"
-#define ENVSEP	','
-
-/*
- * Extended source file access.
- */
-#define DEFAULT_FILETYPE ".awk"
-
-/*
- * Pipe handling.
- */
-#define PIPES_SIMULATED	1
-
-/*
- * VAXCRTL is pre-ANSI and does some variations of numeric formatting
- * differently than gawk expects.
- */
-#if defined(VAX) && !defined(__DECC)
-/* '0' format modifier for %e,%f,%g gives wrong results in many cases */
-#define VAXCRTL
-/* %g format chooses %e format when should use %f */
-#define GFMT_WORKAROUND	1
-#endif
-
-/*
- * VAX C
- *
- * As of V3.2, VAX C is not yet ANSI-compliant.  But it's close enough
- * for GAWK's purposes.  Comment this out for VAX C V2.4 and earlier.
- * YYDEBUG definition is needed for combination of VAX C V2.x and Bison.
- */
-#if defined(VAXC) && !defined(__STDC__)
-#define __STDC__	0
-#define NO_TOKEN_PASTING
-#define signed  /*empty*/
-#define inline	/*empty*/
-#ifndef __DECC	/* DEC C does not support #pragma builtins even in VAXC mode */
-#define VAXC_BUILTINS
-#endif
-/* #define YYDEBUG 0 */
-#define NO_MBSUPPORT  /* VAX C's preprocessor can't handle mbsupport.h */
-#endif
-
-/*
- * DEC C
- *
- * Digital's ANSI complier.
- */
-#ifdef __DECC
- /* DEC C implies DECC$SHR, which doesn't have the %g problem of VAXCRTL */
-#undef GFMT_WORKAROUND
- /* DEC C V5.x introduces incompatibilities with prior porting efforts */
-#define _DECC_V4_SOURCE
-#define __SOCKET_TYPEDEFS
-#if __VMS_VER >= 60200000
-# undef __VMS_VER
-# define __VMS_VER 60100000
-#endif
-#if __CRTL_VER >= 60200000
-# if __CRTL_VER >= 70320000
-#  define CRTL_VER_V732
-#  define HAVE_SNPRINTF 1
-# endif
-# if __CRTL_VER >= 70301000
-#  define CRTL_VER_V731
-# endif
-# undef __CRTL_VER
-# define __CRTL_VER 60100000
-#endif
-#if __DECC_VER >= 60400000 && !defined(DEBUG)
-/* disable "new feature in C99" diagnostics (for regex code);
-   NEWC99 ought to suffice but doesn't (at least in V6.4) */
-#pragma message disable (NEWC99,DESIGNATORUSE)
-#endif
-#endif	/* __DECC */
-
-/*
- * GNU C
- *
- * Versions of GCC (actually GAS) earlier than 1.38 don't produce the
- * right code for ``extern const'' constructs, and other usages of
- * const might not be right either.  The old set of include files from
- * the gcc-vms distribution did not contain prototypes, and this could
- * provoke some const-related compiler warnings.  If you've got an old
- * version of gcc for VMS, define 'const' out of existance, and by all
- * means obtain the most recent version!
- *
- * Note: old versions of GCC should also avoid defining STDC_HEADERS,
- *       because most of the ANSI-C required header files are missing.
- */
-#ifdef __GNUC__
-/* #define const */
-/* #undef STDC_HEADERS */
-/* #undef HAVE_STDDEF_H */
-#ifndef STDC_HEADERS
-#define alloca __builtin_alloca
-#define environ $$PsectAttributes_NOSHR$$environ	/* awful GAS kludge */
-#endif
-#undef  REGEX_MALLOC	/* use true alloca() in regex.c */
-#endif
-
-/* EXIT_SUCCESS and EXIT_FAILURE normally come from <stdlib.h> */
-#ifndef HAVE_STDLIB_H
-# define EXIT_SUCCESS	1		/* SYS$_NORMAL */
-# define EXIT_FAILURE	0x10000002	/* STS$M_INHIB_MSG|STS$K_ERROR */
-#endif
-/* EXIT_FATAL is specific to gawk, not part of Standard C */
-#define EXIT_FATAL	0x10000004	/* STS$M_INHIB_MSG|STS$K_SEVERE */
-
-#define IN_CONFIG_H
-#include "vms/redirect.h"
-#undef  IN_CONFIG_H
-
-#endif	/*"custom.h"*/
-
-#endif	/*CONFIG_H*/
diff --git a/vms/vms-notes b/vms/vms-notes
deleted file mode 100644
index 23943bb9..00000000
--- a/vms/vms-notes
+++ /dev/null
@@ -1,8 +0,0 @@
-Thu Nov 22 18:18:47 IST 2012
-============================
-
-Per Anders Wallin, the HP VMS porting guide is available at
-
-	http://h71000.www7.hp.com/portability/portingguidelines.html
-
-This file documents this fact, and anything else of interest.
diff --git a/vms/vms.h b/vms/vms.h
index 0fb73d5b..3991d39b 100644
--- a/vms/vms.h
+++ b/vms/vms.h
@@ -54,26 +54,26 @@ typedef struct _itm { U_Short len, code; void *buffer; U_Short *retlen; } Itm;
 #define Descrip(strdsc,strbuf) Dsc strdsc = {sizeof strbuf - 1, (char *)strbuf}
 
 extern int    shell$is_shell(void);
-extern U_Long lib$find_file(const Dsc *, Dsc *, void *, ...);
-extern U_Long lib$find_file_end(void *);
+extern U_Long LIB$FIND_FILE(const Dsc *, Dsc *, void *, ...);
+extern U_Long LIB$FIND_FILE_END(void *);
 #ifndef NO_TTY_FWRITE
-extern U_Long lib$get_ef(long *);
-extern U_Long sys$assign(const Dsc *, short *, long, const Dsc *);
-extern U_Long sys$dassgn(short);
-extern U_Long sys$qio(U_Long, U_Long, U_Long, void *,
+extern U_Long LIB$GET_EF(long *);
+extern U_Long SYS$ASSIGN(const Dsc *, short *, long, const Dsc *);
+extern U_Long SYS$DASSGN(short);
+extern U_Long SYS$QIO(U_Long, U_Long, U_Long, void *,
 			 void (*)(U_Long), U_Long,
 			 const char *, int, int, U_Long, int, int);
-extern U_Long sys$synch(long, void *);
+extern U_Long SYS$SYNCH(long, void *);
 #endif	/*!NO_TTY_FWRITE*/
-extern U_Long lib$spawn(const Dsc *,const Dsc *,const Dsc *,
+extern U_Long LIB$SPAWN(const Dsc *,const Dsc *,const Dsc *,
 			   const U_Long *,const Dsc *,U_Long *,U_Long *,...);
  /* system services for logical name manipulation */
-extern U_Long sys$trnlnm(const U_Long *,const Dsc *,const Dsc *,
+extern U_Long SYS$TRNLNM(const U_Long *,const Dsc *,const Dsc *,
 			    const unsigned char *,Itm *);
-extern U_Long sys$crelnm(const U_Long *,const Dsc *,const Dsc *,
+extern U_Long SYS$CRELNM(const U_Long *,const Dsc *,const Dsc *,
 			    const unsigned char *,const Itm *);
-extern U_Long sys$crelog(int,const Dsc *,const Dsc *,unsigned char);
-extern U_Long sys$dellnm(const Dsc *,const Dsc *,const unsigned char *);
+extern U_Long SYS$CRELOG(int,const Dsc *,const Dsc *,unsigned char);
+extern U_Long SYS$DELLNM(const Dsc *,const Dsc *,const unsigned char *);
 
 extern void   v_add_arg(int, const char *);
 extern void   vms_exit(int);
diff --git a/vms/vms_args.c b/vms/vms_args.c
index 0a296105..12165131 100644
--- a/vms/vms_args.c
+++ b/vms/vms_args.c
@@ -1,7 +1,7 @@
 /* vms_args.c -- command line parsing, to emulate shell i/o redirection.
   		[ Escape sequence parsing now suppressed. ]
 
-   Copyright (C) 1991-1996, 1997, 2011 the Free Software Foundation, Inc.
+   Copyright (C) 1991-1996, 1997, 2011, 2014 the Free Software Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -106,10 +106,26 @@ vms_arg_fixup( int *pargc, char ***pargv )
     char **argv = *pargv;
     int i, argc = *pargc;
     int err_to_out_redirect = 0, out_to_err_redirect = 0;
+    char * shell;
+    int using_shell;
 
     /* make sure AWK_LIBRARY has a value */
     if (!getenv("AWK_LIBRARY"))
 	vms_define("AWK_LIBRARY", "SYS$LIBRARY:");
+
+    /* Check if running under a shell instead of DCL */
+    using_shell = 1;
+    shell = getenv("SHELL");
+    if (shell != NULL) {
+	if (strcmp(shell, "DCL") == 0) {
+	    using_shell = 0;
+	}
+    } else {
+	using_shell = 0;
+    }
+    if (using_shell) {
+	return;
+    }
 #ifdef CHECK_DECSHELL	    /* don't define this if linking with DECC$SHR */
     if (shell$is_shell())
 	return;		    /* don't do anything if we're running DEC/Shell */
@@ -325,12 +341,12 @@ vms_expand_wildcards( const char *prospective_filespec )
      */
     len = -1;			/* overload 'len' with flag value */
     context = NULL;		/* init */
-    while (vmswork(lib$find_file(&spec, &result, &context))) {
+    while (vmswork(LIB$FIND_FILE(&spec, &result, &context))) {
 	for (len = sizeof(res_buf)-1; len > 0 && res_buf[len-1] == ' '; len--) ;
 	res_buf[len] = '\0';	/* terminate after discarding trailing blanks */
 	v_add_arg(v_argc++, strdup(res_buf));		/* store result */
     }
-    (void)lib$find_file_end(&context);
+    (void)LIB$FIND_FILE_END(&context);
     if (len >= 0)		/* (still -1 => never entered loop) */
 	--v_argc;		/* undo final post-increment */
     return;
@@ -395,7 +411,7 @@ vms_define( const char *log_name, const char *trans_val )
     log_dsc.len = len;
     itemlist[0].buffer = (char *)trans_val;
     itemlist[0].len = strlen(trans_val);
-    return sys$crelnm(&attr, &lnmtable, &log_dsc, &acmode, itemlist);
+    return SYS$CRELNM(&attr, &lnmtable, &log_dsc, &acmode, itemlist);
 }
 
 /* t_strstr -- strstr() substitute; search 'str' for 'sub' */
diff --git a/vms/vms_cli.c b/vms/vms_cli.c
index ac793c1a..08e2d142 100644
--- a/vms/vms_cli.c
+++ b/vms/vms_cli.c
@@ -1,6 +1,6 @@
 /* vms_cli.c -- interface to CLI$xxx routines for fetching command line components
 
-   Copyright (C) 1991-1993, 2003, 2011 the Free Software Foundation, Inc.
+   Copyright (C) 1991-1993, 2003, 2011, 2014 the Free Software Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -29,13 +29,13 @@
 #include <string.h>
 #endif
 
-extern U_Long cli$present(const Dsc *);
-extern U_Long cli$get_value(const Dsc *, Dsc *, short *);
-extern U_Long cli$dcl_parse(const Dsc *, const void *, ...);
-extern U_Long sys$cli(void *, ...);
-extern U_Long sys$filescan(const Dsc *, void *, long *);
-extern void  *lib$establish(U_Long (*handler)(void *, void *));
-extern U_Long lib$sig_to_ret(void *, void *);	/* condition handler */
+extern U_Long CLI$PRESENT(const Dsc *);
+extern U_Long CLI$GET_VALUE(const Dsc *, Dsc *, short *);
+extern U_Long CLI$DCL_PARSE(const Dsc *, const void *, ...);
+extern U_Long SYS$CLI(void *, ...);
+extern U_Long SYS$FILESCAN(const Dsc *, void *, long *);
+extern void  *LIB$ESTABLISH(U_Long (*handler)(void *, void *));
+extern U_Long LIB$SIG_TO_RET(void *, void *);	/* condition handler */
 
 /* Cli_Present() - call CLI$PRESENT to determine whether a parameter or     */
 /*		  qualifier is present on the [already parsed] command line */
@@ -43,10 +43,10 @@ U_Long
 Cli_Present( const char *item )
 {
     Dsc item_dsc;
-    (void)lib$establish(lib$sig_to_ret);
+    (void)LIB$ESTABLISH(LIB$SIG_TO_RET);
 
     item_dsc.len = strlen(item_dsc.adr = (char *)item);
-    return cli$present(&item_dsc);
+    return CLI$PRESENT(&item_dsc);
 }
 
 /* Cli_Get_Value() - call CLI$GET_VALUE to retreive the value of a */
@@ -57,11 +57,11 @@ Cli_Get_Value( const char *item, char *result, int size )
     Dsc item_dsc, res_dsc;
     U_Long sts;
     short len = 0;
-    (void)lib$establish(lib$sig_to_ret);
+    (void)LIB$ESTABLISH(LIB$SIG_TO_RET);
 
     item_dsc.len = strlen(item_dsc.adr = (char *)item);
     res_dsc.len = size,  res_dsc.adr = result;
-    sts = cli$get_value(&item_dsc, &res_dsc, &len);
+    sts = CLI$GET_VALUE(&item_dsc, &res_dsc, &len);
     result[len] = '\0';
     return sts;
 }
@@ -79,11 +79,11 @@ Cli_Parse_Command( const void *cmd_tables, const char *cmd_verb )
     U_Long sts;
     int    ltmp;
     char   longbuf[8200];
-    (void)lib$establish(lib$sig_to_ret);
+    (void)LIB$ESTABLISH(LIB$SIG_TO_RET);
 
     memset(&cmd, 0, sizeof cmd);
     cmd.rqtype = CLI$K_GETCMD;		/* command line minus the verb */
-    sts = sys$cli(&cmd, (void *)0, (void *)0);	/* get actual command line */
+    sts = SYS$CLI(&cmd, (void *)0, (void *)0);	/* get actual command line */
 
     if (vmswork(sts)) {		/* ok => cli available & verb wasn't "RUN" */
 	/* invoked via symbol => have command line (which might be empty) */
@@ -92,7 +92,7 @@ Cli_Parse_Command( const void *cmd_tables, const char *cmd_verb )
 	    /* need to strip image name from MCR invocation   */
 	    memset(fscn, 0, sizeof fscn);
 	    fscn[0].code = FSCN$_FILESPEC;	/* full file specification */
-	    (void)sys$filescan(&cmd.rdesc, fscn, (long *)0);
+	    (void)SYS$FILESCAN(&cmd.rdesc, fscn, (long *)0);
 	    cmd.rdesc.len -= fscn[0].len;	/* shrink size */
 	    cmd.rdesc.adr += fscn[0].len;	/* advance ptr */
 	}
@@ -102,7 +102,7 @@ Cli_Parse_Command( const void *cmd_tables, const char *cmd_verb )
 	    cmd.rdesc.len = sizeof longbuf - ltmp;
 	strncpy(&longbuf[ltmp], cmd.rdesc.adr, cmd.rdesc.len);
 	cmd.rdesc.len += ltmp,	cmd.rdesc.adr = longbuf;
-	sts = cli$dcl_parse(&cmd.rdesc, cmd_tables);
+	sts = CLI$DCL_PARSE(&cmd.rdesc, cmd_tables);
     }
 
     return sts;
diff --git a/vms/vms_crtl_init.c b/vms/vms_crtl_init.c
new file mode 100644
index 00000000..081ae2cc
--- /dev/null
+++ b/vms/vms_crtl_init.c
@@ -0,0 +1,470 @@
+/* File: VMS_CRTL_INIT.C
+
+ This file is common to a lot of projects.
+
+ $Id: vms_crtl_init.c,v 1.1.1.1 2012/12/02 19:25:22 wb8tyw Exp $
+
+ Module that provides a LIB$INITIALIZE routine for the GNV toolset that
+ will turn on some CRTL features that are not enabled by default.
+
+ The CRTL features can also be turned on via logical names, but that
+ impacts all programs and some aren't ready, willing, or able to handle
+ the settings that GNV needs.
+
+ The original module was found linked with GPL V2 modules, and thus must
+ be able to be distributed under the GPL V2 provisions.
+
+ As this module or similar is needed for virtually all programs built to run
+ under GNV or UNIX, it can be distributed with other licenses.
+
+ Edit History
+
+ 1-001	John Reagan	Initial version using the old style interface
+			but with the new version commented out.
+
+ 1-002	John Reagan	Switch to new API for setting features
+
+ 1-003	Steve Pitcher	Add DECC$RENAME_NO_INHERIT.
+
+ 1-004	Steve Pitcher	Quiet these, if the DECC feature doesn't exist.
+
+ 2-001	J. Malmberg	New GNV requirements:
+			    Three variations of object modules:
+				1. For use with shells, sets the logical
+				   name GNV$UNIX_SHELL.
+
+				2. For utilities, if the logical name
+				   GNV$UNIX_SHELL is set, it means that the
+				   settings should assume that they are
+				   running under a UNIX like shell.
+
+				3. A third setting is for utilities that
+				   always should behave as if they are
+				   running under a UNIX shell.
+
+			    If GNV$GNU is defined, then locally define
+			    SYS$POSIX_ROOT to it.  GNV$GNU can be set in
+			    the SYSTEM table by the GNV setup.
+			    SYS$POSIX_ROOT can not.
+
+			    The logical name BIN also needs to be defined
+			    here, otherwise the CRTL replaces it with
+			    SYS$SYSTEM:
+
+			    Never set the POSIX UID here, it will break
+			    every reference to a GID/UID on systems that
+			    do not have every VMS account mapped to a UID/GID
+			    by TCPIP services.
+
+			    Reformat text to fit 80 columns.
+
+			    Remove all VAX C specific code.
+
+			    Linker is probably using exact case, so public
+			    symbols for LIB$* and SYS$* must be in upper case.
+
+ 2-002	J. Malmberg	Support for VAX builds.  OpenVMS/VAX does not have the
+	17-Jun-2010	DECC$FEATURE routines.  At this time I will not
+			be concerned if a feature setting exists on VAX,
+			as all we are doing is setting a logical name.
+
+ 2-003	J. Malmberg	Add DECC$FILENAME_UNIX_NOVERSION as version numbers
+			will usually mess up ported programs.
+
+*/
+
+#include <stdio.h>
+#include <descrip.h>
+#include <lnmdef.h>
+#include <stsdef.h>
+#include <string.h>
+
+#pragma message disable pragma
+#pragma message disable dollarid
+#pragma message disable valuepres
+
+#pragma member_alignment save
+#pragma nomember_alignment longword
+#pragma message save
+#pragma message disable misalgndmem
+struct itmlst_3 {
+  unsigned short int buflen;
+  unsigned short int itmcode;
+  void *bufadr;
+  unsigned short int *retlen;
+};
+#pragma message restore
+#pragma member_alignment restore
+
+#ifdef __VAX
+#define ENABLE "ENABLE"
+#define DISABLE "DISABLE"
+#else
+
+#define ENABLE TRUE
+#define DISABLE 0
+int   decc$feature_get_index (const char *name);
+int   decc$feature_set_value (int index, int mode, int value);
+
+#endif
+
+int   SYS$TRNLNM(
+	const unsigned long * attr,
+	const struct dsc$descriptor_s * table_dsc,
+	struct dsc$descriptor_s * name_dsc,
+	const unsigned char * acmode,
+	const struct itmlst_3 * item_list);
+int   SYS$CRELNM(
+	const unsigned long * attr,
+	const struct dsc$descriptor_s * table_dsc,
+	const struct dsc$descriptor_s * name_dsc,
+	const unsigned char * acmode,
+	const struct itmlst_3 * item_list);
+int   LIB$SIGNAL(int);
+
+/* Take all the fun out of simply looking up a logical name */
+static int sys_trnlnm
+   (const char * logname,
+    char * value,
+    int value_len)
+{
+    const $DESCRIPTOR(table_dsc, "LNM$FILE_DEV");
+    const unsigned long attr = LNM$M_CASE_BLIND;
+    struct dsc$descriptor_s name_dsc;
+    int status;
+    unsigned short result;
+    struct itmlst_3 itlst[2];
+
+    itlst[0].buflen = value_len;
+    itlst[0].itmcode = LNM$_STRING;
+    itlst[0].bufadr = value;
+    itlst[0].retlen = &result;
+
+    itlst[1].buflen = 0;
+    itlst[1].itmcode = 0;
+
+    name_dsc.dsc$w_length = strlen(logname);
+    name_dsc.dsc$a_pointer = (char *)logname;
+    name_dsc.dsc$b_dtype = DSC$K_DTYPE_T;
+    name_dsc.dsc$b_class = DSC$K_CLASS_S;
+
+    status = SYS$TRNLNM(&attr, &table_dsc, &name_dsc, 0, itlst);
+
+    if ($VMS_STATUS_SUCCESS(status)) {
+
+	 /* Null terminate and return the string */
+	/*--------------------------------------*/
+	value[result] = '\0';
+    }
+
+    return status;
+}
+
+/* How to simply create a logical name */
+static int sys_crelnm
+   (const char * logname,
+    const char * value)
+{
+    int ret_val;
+    const char * proc_table = "LNM$PROCESS_TABLE";
+    struct dsc$descriptor_s proc_table_dsc;
+    struct dsc$descriptor_s logname_dsc;
+    struct itmlst_3 item_list[2];
+
+    proc_table_dsc.dsc$a_pointer = (char *) proc_table;
+    proc_table_dsc.dsc$w_length = strlen(proc_table);
+    proc_table_dsc.dsc$b_dtype = DSC$K_DTYPE_T;
+    proc_table_dsc.dsc$b_class = DSC$K_CLASS_S;
+
+    logname_dsc.dsc$a_pointer = (char *) logname;
+    logname_dsc.dsc$w_length = strlen(logname);
+    logname_dsc.dsc$b_dtype = DSC$K_DTYPE_T;
+    logname_dsc.dsc$b_class = DSC$K_CLASS_S;
+
+    item_list[0].buflen = strlen(value);
+    item_list[0].itmcode = LNM$_STRING;
+    item_list[0].bufadr = (char *)value;
+    item_list[0].retlen = NULL;
+
+    item_list[1].buflen = 0;
+    item_list[1].itmcode = 0;
+
+    ret_val = SYS$CRELNM(NULL, &proc_table_dsc, &logname_dsc, NULL, item_list);
+
+    return ret_val;
+}
+
+
+ /* Start of DECC RTL Feature handling */
+
+/*
+** Sets default value for a feature
+*/
+#ifdef __VAX
+static void set_feature_default(const char *name, const char *value)
+{
+    sys_crelnm(name, value);
+}
+#else
+static void set_feature_default(const char *name, int value)
+{
+     int index;
+
+     index = decc$feature_get_index(name);
+
+     if (index > 0)
+	decc$feature_set_value (index, 0, value);
+}
+#endif
+
+static void set_coe ( void )
+{
+
+    char gnv_posix_root[4096];
+    char unix_shell_name[255];
+    int use_unix_settings = 0;
+    int status;
+    int gnv_posix_root_found = 0;
+
+    /* If this is compiled for use with a UNIX shell, then the logical
+     * name GNV$UNIX_SHELL will be set to that shell name.
+     *
+     * Else, if the GNV$UNIX_SHELL logical name is set, then this application
+     * is running under some UNIX like shell, so it should modify it's
+     * behavior to be UNIX like.
+     *
+     * If the above logical name is not set, then the application should
+     * expect that it is running under DCL, and should expect VMS filenames
+     * on input, and may need to output filenames in VMS format.
+     *
+     * This can be overriden at compile time with GNV_UNIX_TOOL being
+     * defined.
+     *
+     * So this means that there will be multiple object modules from this
+     * source module.  One for each shell, one for programs that can function
+     * in both DCL and UNIX environments, and one for programs that require
+     * a UNIX environment.
+     */
+
+#ifdef GNV_UNIX_SHELL
+    use_unix_settings = 1;
+
+    status = sys_crelnm("GNV$UNIX_SHELL", GNV_UNIX_SHELL);
+    if (!$VMS_STATUS_SUCCESS(status)) {
+	/* We have a big problem */
+	LIB$SIGNAL(status);
+    }
+#else
+
+#ifdef GNV_UNIX_TOOL
+    use_unix_settings = 1;
+#else
+    status = sys_trnlnm("GNV$UNIX_SHELL",
+			unix_shell_name, sizeof
+			unix_shell_name -1);
+    if (!$VMS_STATUS_SUCCESS(status)) {
+	unix_shell_name[0] = 0;
+	use_unix_settings = 0;
+    }
+#endif /* GNV_UNIX_TOOL */
+
+#endif /* GNV_UNIX_SHELL */
+
+    /* New style interface that works only on very recent
+       (Apr 2001 and beyond) CRTLs */
+
+    /*
+     * Only setting defaults allows logical names to
+     * override these settings.
+     */
+
+    /* Always set */
+
+    /* ACCESS should check ACLs or it is lying. */
+    set_feature_default("DECC$ACL_ACCESS_CHECK"		, ENABLE);
+
+    /* We always want the new parse style */
+    set_feature_default ("DECC$ARGV_PARSE_STYLE"	, ENABLE);
+
+    /* Unless we are in POSIX compliant mode, we want the old POSIX root
+     * enabled.
+     */
+    set_feature_default("DECC$DISABLE_POSIX_ROOT", DISABLE);
+
+    /* EFS charset, means UTF-8 support */
+    /* VTF-7 support is controlled by a feature setting called UTF8 */
+    set_feature_default ("DECC$EFS_CHARSET" 		, ENABLE);
+    set_feature_default ("DECC$EFS_CASE_PRESERVE"	, ENABLE);
+
+
+    /* Support timestamps when available */
+    set_feature_default ("DECC$EFS_FILE_TIMESTAMPS"	, ENABLE);
+
+    /* Cache environment varibles - performance improvements */
+    set_feature_default ("DECC$ENABLE_GETENV_CACHE"	, ENABLE);
+
+    /* Start out with new file attribute inheritance */
+#ifdef __VAX
+    set_feature_default ("DECC$EXEC_FILEATTR_INHERITANCE", "2");
+#else
+    set_feature_default ("DECC$EXEC_FILEATTR_INHERITANCE", 2);
+#endif
+
+    /* Don't display trailing dot after files without type */
+    set_feature_default ("DECC$READDIR_DROPDOTNOTYPE"	, ENABLE);
+
+    /* For standard output channels buffer output until terminator */
+    /* Gets rid of output logs with single character lines in them. */
+    set_feature_default ("DECC$STDIO_CTX_EOL"		, ENABLE);
+
+    /* Fix mv aa.bb aa						*/
+    set_feature_default ("DECC$RENAME_NO_INHERIT"  	, ENABLE);
+
+    if (use_unix_settings) {
+
+	/* POSIX requires that open files be able to be removed */
+	set_feature_default ("DECC$ALLOW_REMOVE_OPEN_FILES", ENABLE);
+
+	set_feature_default ("DECC$FILENAME_UNIX_ONLY"	, ENABLE);
+		/* FILENAME_UNIX_ONLY Implicitly sets
+		  decc$disable_to_vms_logname_translation */
+
+	set_feature_default ("DECC$FILE_PERMISSION_UNIX", ENABLE);
+
+	/* For now this only with UNIX mode, applications can override
+	 * with out using a LIB$INITIALIZE setting.
+	 * This should be an application specific setting only enabled
+	 * if the application requires it.
+	 * Left here for now for backwards compatibility
+         */
+	set_feature_default ("DECC$FILE_SHARING"	, ENABLE);
+
+        set_feature_default ("DECC$FILE_OWNER_UNIX"  	, ENABLE);
+        set_feature_default ("DECC$POSIX_SEEK_STREAM_FILE", ENABLE);
+
+    } else {
+	 set_feature_default("DECC$FILENAME_UNIX_REPORT", ENABLE);
+    }
+
+    /* When reporting UNIX filenames, glob the same way */
+    set_feature_default ("DECC$GLOB_UNIX_STYLE"	, ENABLE);
+
+    /* The VMS version numbers on Unix filenames is incompatible with most */
+    /* ported packages. */
+    set_feature_default("DECC$FILENAME_UNIX_NO_VERSION", ENABLE);
+
+    /* The VMS version numbers on Unix filenames is incompatible with most */
+    /* ported packages. */
+    set_feature_default("DECC$UNIX_PATH_BEFORE_LOGNAME", ENABLE);
+
+    /* Set strtol to proper behavior */
+    set_feature_default("DECC$STRTOL_ERANGE", ENABLE);
+
+    /*  Pipe feature settings are longer needed with virtual memory pipe
+	code.  Programs that use  pipe need to be converted to use the
+	virtual memory pipe code, which effectively removes the hangs and
+	left over temporary files.
+
+        Comment left here to prevent regressions, as the larger pipe size
+        actually hurts memory usage with the new algorithm.
+     */
+    /* do_not_set_default ("DECC$PIPE_BUFFER_SIZE"	, 8192); */
+
+
+    /* Rather than remove this completely, a comment is left here to warn
+     * someone from putting this bug back in.
+     *
+     * POSIX style UIDs require that the system administrator have set the
+     * system up to use POSIX style UIDs and GIDs.  And if they have done
+     * so, then they should set the DECC$POSIX_STYLE_UID as a system wide
+     * logical name.
+     *
+     * Setting them in a program will break all routines that expect GID/UID
+     * stuff to work on systems set up by default with out mappings.
+     *
+     * Most utilities do not reference GID/UID values, so it took a while for
+     * this bug to surface.
+     */
+     /*  do_not_set_default ("DECC$POSIX_STYLE_UID"	, TRUE); */
+
+
+
+    /* GNV depends on SYS$POSIX_ROOT to be properly set.  Since SYS$POSIX_ROOT
+     * globally affects all C applications, SYS$POSIX_ROOT can not be set
+     * anywhere that can be seen by other applications.
+     *
+     * So GNV$GNU is used instead, and SYS$POSIX_ROOT will be set in
+     * in the process table in user mode to that value.
+     *
+     * Restriction: The system manager should not point GNV$GNU at
+     * SYS$POSIX_ROOT, or anything that resolves to SYS$POSIX_ROOT.
+     *
+     */
+
+    status = sys_trnlnm("GNV$GNU",
+			gnv_posix_root,
+			sizeof gnv_posix_root - 1);
+    if ($VMS_STATUS_SUCCESS(status)) {
+	status = sys_crelnm("SYS$POSIX_ROOT", "GNV$GNU:");
+	gnv_posix_root_found = 1;
+    }
+
+    /* GNV depends on BIN being set to GNV$GNU:[bin].  Since BIN
+     * is not prefixed, and it affects everything globally, it needs to
+     * be set here if it is not defined already.
+     * If it is set already, assume that it is correct, rather than
+     * trying to second guess the user.
+     * If GNV$GNU is not defined, then define bin to be SYS$POSIX_ROOT.
+     */
+
+    status = sys_trnlnm("BIN",
+			gnv_posix_root,
+			sizeof gnv_posix_root - 1);
+    if (!$VMS_STATUS_SUCCESS(status)) {
+	if (gnv_posix_root_found) {
+	    status = sys_crelnm("BIN", "GNV$GNU:[BIN]");
+	} else {
+	    status = sys_crelnm("BIN", "SYS$POSIX_ROOT:[BIN]");
+	}
+    }
+
+}
+
+#pragma nostandard
+#pragma extern_model save
+#ifdef __VAX
+#pragma extern_model strict_refdef "LIB$INITIALIZE" nowrt, long, nopic
+#else
+#pragma extern_model strict_refdef "LIB$INITIALIZE" nowrt, long
+#    if __INITIAL_POINTER_SIZE
+#        pragma __pointer_size __save
+#        pragma __pointer_size 32
+#    else
+#        pragma __required_pointer_size __save
+#        pragma __required_pointer_size 32
+#    endif
+#endif
+/* Set our contribution to the LIB$INITIALIZE array */
+void (* const iniarray[])(void) = {set_coe, } ;
+#ifndef __VAX
+#    if __INITIAL_POINTER_SIZE
+#        pragma __pointer_size __restore
+#    else
+#        pragma __required_pointer_size __restore
+#    endif
+#endif
+
+
+/*
+** Force a reference to LIB$INITIALIZE to ensure it
+** exists in the image.
+*/
+int LIB$INITIALIZE(void);
+#ifdef __DECC
+#pragma extern_model strict_refdef
+#endif
+    int lib_init_ref = (int) LIB$INITIALIZE;
+#ifdef __DECC
+#pragma extern_model restore
+#pragma standard
+#endif
diff --git a/vms/vms_fwrite.c b/vms/vms_fwrite.c
index 1a16f58c..f29ec832 100644
--- a/vms/vms_fwrite.c
+++ b/vms/vms_fwrite.c
@@ -1,6 +1,6 @@
 /* vms_fwrite.c - augmentation for the fwrite() function.
 
-   Copyright (C) 1991-1996, 2010, 2011 the Free Software Foundation, Inc.
+   Copyright (C) 1991-1996, 2010, 2011, 2014 the Free Software Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -83,9 +83,9 @@ tty_fwrite( const void *buf, size_t size, size_t number, FILE *file )
 
 	    fgetname(file, devnam);			/* get 'file's name */
 	    device.len = strlen(device.adr = devnam);	/* create descriptor */
-	    if (vmswork(sys$assign(&device, &chan, 0, (Dsc *)0))) {
+	    if (vmswork(SYS$ASSIGN(&device, &chan, 0, (Dsc *)0))) {
 		/* get an event flag; use #0 if problem */
-		if (evfn == -1 && vmsfail(lib$get_ef(&evfn)))  evfn = 0;
+		if (evfn == -1 && vmsfail(LIB$GET_EF(&evfn)))  evfn = 0;
 	    } else  chan = 0;	    /* $ASSIGN failed */
 	}
 	/* store channel for later use; -1 => don't repeat failed init attempt */
@@ -119,19 +119,19 @@ tty_fwrite( const void *buf, size_t size, size_t number, FILE *file )
 	    else if (pos < count)  pos++,  cc_fmt |= POSTFIX_CR,  extra++;
 	    /* wait for previous write, if any, to complete */
 	    if (pt > (char *)buf) {
-		sts = sys$synch(evfn, &iosb);
+		sts = SYS$SYNCH(evfn, &iosb);
 		if (vmswork(sts))  sts = iosb.status,  result += iosb.count;
 		if (vmsfail(sts))  break;
 	    }
 	    /* queue an asynchronous write */
-	    sts = sys$qio(evfn, chan, io_func, &iosb, (void (*)(U_Long))0, 0L,
+	    sts = SYS$QIO(evfn, chan, io_func, &iosb, (void (*)(U_Long))0, 0L,
 			  pt, pos, 0, cc_fmt, 0, 0);
 	    if (vmsfail(sts))  break;	/*(should never happen)*/
 	    pt += pos,	count -= pos;
 	}
 	/* wait for last write to complete */
 	if (pt > (char *)buf && vmswork(sts)) {
-	    sts = sys$synch(evfn, &iosb);
+	    sts = SYS$SYNCH(evfn, &iosb);
 	    if (vmswork(sts))  sts = iosb.status,  result += iosb.count;
 	}
 	if (vmsfail(sts))  errno = EVMSERR,  vaxc$errno = sts;
@@ -202,7 +202,7 @@ tty_fclose( FILE *file )
 	short chan = file_num < _NFILE ? channel[file_num] : -1;
 
 	if (chan > 0)
-	    (void)sys$dassgn(chan); /* deassign the channel (ie, close) */
+	    (void)SYS$DASSGN(chan); /* deassign the channel (ie, close) */
 	if (file_num < _NFILE)
 	    channel[file_num] = 0;  /* clear stale info */
     }
diff --git a/vms/vms_gawk.c b/vms/vms_gawk.c
index f22e2fa9..4080e1db 100644
--- a/vms/vms_gawk.c
+++ b/vms/vms_gawk.c
@@ -1,6 +1,7 @@
 /* vms_gawk.c -- parse GAWK command line using DCL syntax
 
-   Copyright (C) 1991-1993, 1996, 2003, 2005, 2011 the Free Software Foundation, Inc.
+   Copyright (C) 1991-1993, 1996, 2003, 2005, 2011, 2014
+   the Free Software Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -37,16 +38,16 @@
 #define Present(arg)		vmswork(Cli_Present(arg))
 #define Get_Value(arg,buf,siz)	vmswork(Cli_Get_Value(arg,buf,siz))
 
-#ifndef __ia64__
-extern void   gawk_cmd();	/* created with $ SET COMMAND/OBJECT */
-#define GAWK_CMD ((const void *)gawk_cmd)
-#else	/* linker on Itanium is much pickier about such things */
+#ifndef __DECC
+extern void   GAWK_CMD();	/* created with $ SET COMMAND/OBJECT */
+#define gawk_cmd ((const void *)GAWK_CMD) */
+#else	/* Use ANSI definitions for DEC C */
 #pragma extern_model save
 #pragma extern_model strict_refdef
 /* (could use globalvalue rather than _refdef if we omit GAWK_CMD's `&') */
-extern void  *gawk_cmd;
+extern void  *GAWK_CMD;
 #pragma extern_model restore
-#define GAWK_CMD ((const void *)&gawk_cmd)
+#define gawk_cmd ((const void *)&GAWK_CMD)
 #endif
 extern void   _exit(int);
 static int    vms_usage(int);
@@ -88,7 +89,7 @@ vms_gawk()
 	   command, so we'll now attempt to generate a command from the
 	   foreign command string and parse that.
 	*/
-	sts = Cli_Parse_Command(GAWK_CMD, "GAWK");	/* (*not* CmdName) */
+	sts = Cli_Parse_Command(gawk_cmd, "GAWK");	/* (*not* CmdName) */
 	if (vmswork(sts))
 	    sts = Cli_Present("GAWK_P1");
     }
diff --git a/vms/vms_misc.c b/vms/vms_misc.c
index cd92d7ef..82c2f8a8 100644
--- a/vms/vms_misc.c
+++ b/vms/vms_misc.c
@@ -1,6 +1,6 @@
 /* vms_misc.c -- sustitute code for missing/different run-time library routines.
 
-   Copyright (C) 1991-1993, 1996-1997, 2001, 2003, 2009, 2010, 2011
+   Copyright (C) 1991-1993, 1996-1997, 2001, 2003, 2009, 2010, 2011, 2014
    the Free Software Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
@@ -118,15 +118,24 @@ vms_open( const char *name, int mode, ... )
 	result = creat(name, 0, "rfm=stmlf", "rat=cr", "shr=nil", "mbc=32");
     } else {
 	struct stat stb;
+        int stat_result;
 	const char *mbc, *shr = "shr=get", *ctx = "ctx=stm";
-
-	if (stat((char *)name, &stb) < 0) {	/* assume DECnet */
+ 
+	stat_result = stat((char *)name, &stb);
+	if ( stat_result < 0) {	/* assume DECnet */
 	    mbc = "mbc=8";
 	} else {    /* ordinary file; allow full sharing iff record format */
 	    mbc = "mbc=32";
 	    if ((stb.st_fab_rfm & 0x0F) < FAB$C_STM) shr = "shr=get,put,upd";
 	}
 	result = open(name, mode, 0, shr, mbc, "mbf=2");
+	if ((stat_result >= 0) && (result < 0) && (errno == ENOENT)) {
+	    /* ENOENT not possible because stat succeeded */
+	    errno = EMFILE;
+	    if (S_ISDIR(stb.st_mode)) {
+		errno = EISDIR; /* Bug seen in VMS 8.3 */
+	    }
+        }
     }
 
     /* This is only approximate; the ACP -> RMS -> VAXCRTL interface
@@ -165,8 +174,8 @@ vms_devopen( const char *name, int mode )
 #define VMS_UNITS_PER_SECOND 10000000L	/* hundreds of nanoseconds, 1e-7 */
 #define UNIX_EPOCH "01-JAN-1970 00:00:00.00"
 
-extern U_Long sys$bintim(), sys$gettim();
-extern U_Long lib$subx(), lib$ediv();
+extern U_Long SYS$BINTIM(), SYS$GETTIM();
+extern U_Long LIB$SUBX(), LIB$EDIV();
 
     /*
      * Get current time in microsecond precision.
@@ -183,13 +192,13 @@ vms_gettimeofday(struct timeval *tv, void *timezone__not_used)
     const long  thunk = VMS_UNITS_PER_SECOND;
     long        now[2], quad[2];
 
-    if (!epoch[0])  sys$bintim(&epoch_dsc, epoch);	/* 1 Jan 0:0:0 1970 */
+    if (!epoch[0])  SYS$BINTIM(&epoch_dsc, epoch);	/* 1 Jan 0:0:0 1970 */
     /* get current time, as VMS quadword time */
-    sys$gettim(now);
+    SYS$GETTIM(now);
     /* convert the quadword time so that it's relative to Unix epoch */
-    lib$subx(now, epoch, quad); /* quad = now - epoch; */
+    LIB$SUBX(now, epoch, quad); /* quad = now - epoch; */
     /* convert 1e-7 units into seconds and fraction of seconds */
-    lib$ediv(&thunk, quad, &tv->tv_sec, &tv->tv_usec);
+    LIB$EDIV(&thunk, quad, &tv->tv_sec, &tv->tv_usec);
     /* convert fraction of seconds into microseconds */
     tv->tv_usec /= (VMS_UNITS_PER_SECOND / 1000000);
 
@@ -272,7 +281,7 @@ int fork( void ) {
 #include <fab.h>
 #include <nam.h>
 
-extern unsigned long sys$parse(), sys$search();
+extern unsigned long SYS$PARSE(), SYS$SEARCH();
 
 /* Work around a VAXCRTL bug.  If a file is located via a searchlist,
    and if the device it's on is not the same device as the one specified
diff --git a/vms/vms_popen.c b/vms/vms_popen.c
index 62f3f719..23482df1 100644
--- a/vms/vms_popen.c
+++ b/vms/vms_popen.c
@@ -1,6 +1,7 @@
 /* [.vms]vms_popen.c -- substitute routines for missing pipe calls.
 
-   Copyright (C) 1991-1993, 1996, 2010, 2011 the Free Software Foundation, Inc.
+   Copyright (C) 1991-1993, 1996, 2010, 2011, 2014
+   the Free Software Foundation, Inc.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -133,8 +134,8 @@ pclose( FILE *current )
     int rval, cur = fileno(current);
 
  /* assert( cur >= 0 && cur < pipes_lim ); */
-    if (pipes[cur].pmode == unopened)
-	return -1;	/* should never happen */
+    if ((cur < 0) || (pipes[cur].pmode == unopened))
+	return -1;	/* should never happen, but does with two-way */
 
     rval = fclose(current);	/* close temp file; if reading, we're done */
     if (pipes[cur].pmode == writing) {
@@ -172,7 +173,7 @@ vms_execute( const char *command, const char *input, const char *output )
 	out_p = 0;
 
     push_logicals();	/* guard against user-mode definitions of sys$Xput */
-    sts = lib$spawn(&cmd, in_p, out_p, (U_Long *)0,
+    sts = LIB$SPAWN(&cmd, in_p, out_p, (U_Long *)0,
 		    (Dsc *)0, (U_Long *)0, &cmpltn_sts);
     pop_logicals();	/* restore environment */
 
@@ -219,9 +220,9 @@ static const Descrip(sys_output,"SYS$OUTPUT");
 static const unsigned char acmode = PSL$C_USER; /* only care about user-mode */
 
  /* macros for simplfying the code a bunch */
-#define DelTrans(l)	sys$dellnm(&lnmtable, (l), &acmode)
-#define GetTrans(l,i)	sys$trnlnm((U_Long *)0, &lnmtable, (l), &acmode, (i))
-#define SetTrans(l,i)	sys$crelnm((U_Long *)0, &lnmtable, (l), &acmode, (i))
+#define DelTrans(l)	SYS$DELLNM(&lnmtable, (l), &acmode)
+#define GetTrans(l,i)	SYS$TRNLNM((U_Long *)0, &lnmtable, (l), &acmode, (i))
+#define SetTrans(l,i)	SYS$CRELNM((U_Long *)0, &lnmtable, (l), &acmode, (i))
  /* itemlist manipulation macros; separate versions for aggregate and scalar */
 #define SetItmA(i,c,p,r) ((i).code = (c), (i).len = sizeof (p),\
 			  (i).buffer = (p), (i).retlen = (U_Short *)(r))
@@ -333,7 +334,7 @@ restore_translation( const Dsc *logname, const Itm *itemlist )
      /* assert( itemlist[2].code == LNM$_STRING ); */
 	trans_val.adr = itemlist[2].buffer;
 	trans_val.len = itemlist[2].len;
-	(void) sys$crelog(LOG_PROCESS_TABLE, logname, &trans_val, LOG_USERMODE);
+	(void) SYS$CRELOG(LOG_PROCESS_TABLE, logname, &trans_val, LOG_USERMODE);
     } else {
 	/* $crelnm definition; itemlist could specify multiple translations,
 	    but has already been setup properly for use as-is.
diff --git a/vms/vmsbuild.com b/vms/vmsbuild.com
index 95c6aeb3..c13e4b57 100644
--- a/vms/vmsbuild.com
+++ b/vms/vmsbuild.com
@@ -10,14 +10,24 @@ $!						gawk 3.1.1 revised, Apr'02
 $!						gawk 3.1.6 revised, Mar'07
 $!						gawk-bytecode revd, Jan'10
 $!						gawk 4.0.0 revd, May'11
-$!						gawk 4.1.0 revd, Nov'12
+$!						gawk 4.1.0 revd, May'13
+$!						gawk 4.1.1 revd, Apr'14
 $!
 $ REL = "4.1"	!release version number
-$ PATCHLVL = "0"
+$ PATCHLVL = "1"
 $!
+$ if (f$getsyi("HW_MODEL") .lt. 1024)
+$ then
+$   arch_name = "VAX"
+$ else
+$   arch_name = f$edit(f$getsyi("ARCH_NAME"), "UPCASE")
+$ endif
 $!
 $ CCFLAGS = "/noList"	! "/noOpt/Debug"
+$! CCFLAGS = "/list/show=(expan,incl)
 $ CDEFS	  = "GAWK,HAVE_CONFIG_H"
+$! Do not specify _POSIX_EXIT here, we are using other tricks for that.
+$!
 $!
 $ if p1.eqs."" then  p1 = "DECC"	!default compiler
 $ if p1.eqs."GNUC"
@@ -38,8 +48,17 @@ $   CFLAGS = "/Incl=[]/Obj=[]/Opt=noInline/Def=(''CDEFS')''CCFLAGS'"
 $   LIBS = "sys$share:vaxcrtl.exe/Shareable"
 $  else  !!VAXC
 $!  neither GNUC nor VAXC, assume DECC (same for either VAX or Alpha)
+$ if arch_name .eqs. "vax"
+$ then
+$   CFLOAT = ""
+$ else
+$   CFLOAT = "/float=ieee/ieee_mode=denorm_results"
+$ endif
 $   CC = "cc/DECC/Prefix=All"
-$   CFLAGS = "/Incl=[]/Obj=[]/Def=(''CDEFS')''CCFLAGS'"
+$   CNAME = "/NAME=(AS_IS,SHORT)
+$   CINC = "/NESTED_INCLUDE=NONE"
+$   CFLAGS = "/Incl=([],[.vms])/Obj=[]/Def=(''CDEFS')''CINC'''CCFLAGS'"
+$   CFLAGS = CNAMES + CFLOAT + CFLAGS 
 $   LIBS = ""	! DECC$SHR instead of VAXCRTL, no special link option needed
 $  endif !VAXC
 $ endif !GNUC
@@ -47,12 +66,15 @@ $!
 $ cc = CC + CFLAGS
 $ show symbol cc
 $!
-$ if f$search("config.h").nes."" then -
-    if f$cvtime(f$file_attr("config.h","RDT")).ges.-
-       f$cvtime(f$file_attr("[.vms]vms-conf.h","RDT")) then  goto config_ok
-$ v = f$verify(1)
-$ copy [.vms]vms-conf.h []config.h
-$! 'f$verify(v)'
+$ if f$search("config.h") .nes. ""
+$ then
+$    if f$cvtime(f$file_attr("config.h", "RDT")) .ges. -
+        f$cvtime(f$file_attr("configh.in","RDT")) then  goto config_ok
+$ endif
+$ v = f$verify(0)
+$ @[.vms]generate_config_vms_h_gawk.com
+$ @[.vms]config_h.com NOBUILTINS
+$!
 $config_ok:
 $ if f$search("awkgram.c").nes."" then  goto awkgram_ok
 $	write sys$output " You must process `awkgram.y' with ""yacc"" or ""bison"""
@@ -70,7 +92,7 @@ $	if f$search("ytab.c").nes."" .or. f$search("y_tab.c").nes."" then - !yacc
 	  write sys$output " or else rename `ytab.c' or `y_tab.c' to `command.c'."
 $	exit
 $command_ok:
-$ v = f$verify(1)
+$ v1 = f$verify(1)
 $ cc array.c
 $ cc awkgram.c
 $ cc builtin.c
@@ -106,7 +128,8 @@ $ cc [.vms]vms_fwrite.c
 $ cc [.vms]vms_args.c
 $ cc [.vms]vms_gawk.c
 $ cc [.vms]vms_cli.c
-$ set command/Object=[]gawk_cmd.obj [.vms]gawk.cld
+$ cc [.vms]vms_crtl_init.c
+$ set command/Object=[]gawk_cmd.obj sys$disk:[.vms]gawk.cld
 $! 'f$verify(v)'
 $!
 $ close/noLog Fopt
@@ -116,18 +139,21 @@ array.obj,awkgram.obj,builtin.obj,dfa.obj,ext.obj,field.obj,floatcomp.obj
 gawkmisc.obj,getopt.obj,getopt1.obj,io.obj
 main.obj,msg.obj,node.obj
 random.obj,re.obj,regex.obj,replace.obj,version.obj,eval.obj,profile.obj
-command.obj,debug.obj,int_array.obj,cint_array.obj,gawkapi.obj,mpfr.obj,str_array.obj,symbol.obj
+command.obj,debug.obj,int_array.obj,cint_array.obj,gawkapi.obj,mpfr.obj
+str_array.obj,symbol.obj
 []vms_misc.obj,vms_popen.obj,vms_fwrite.obj,vms_args.obj
-[]vms_gawk.obj,vms_cli.obj,gawk_cmd.obj
+[]vms_gawk.obj,vms_cli.obj,gawk_cmd.obj,vms_crtl_init.obj
 psect_attr=environ,noshr	!extern [noshare] char **
 stack=48	!preallocate more pages (default is 20)
 iosegment=128	!ditto (default is 32)
+$!
+$ v1 = f$verify(1)
+$ @[.vms]gawk_ident.com
 $ open/append Fopt gawk.opt
 $ write Fopt libs
-$ write Fopt "identification=""V''REL'.''PATCHLVL'"""
 $ close Fopt
 $!
-$ v = f$verify(1)
+$ v1 = f$verify(1)
 $ link/exe=gawk.exe gawk.opt/options
 $! 'f$verify(v)'
 $ exit
diff --git a/vms/vmstest.com b/vms/vmstest.com
index 25404373..30bdbf22 100644
--- a/vms/vmstest.com
+++ b/vms/vmstest.com
@@ -25,6 +25,7 @@ $	rm	= "delete/noConfirm/noLog"
 $	mv	= "rename/New_Vers"
 $	gawk = "$sys$disk:[-]gawk"
 $	AWKPATH_srcdir = "define/User AWKPATH sys$disk:[]"
+$	AWKLIBPATH_dir = "define/User AWKLIBPATH sys$disk:[-]"
 $
 $	listdepth = 0
 $	pipeok = 0
@@ -119,8 +120,9 @@ $		list = "include2 indirectcall lint lintold lintwarn match1" -
 		  + " nondec2 patsplit posix profile1 procinfs printfbad1" -
 		  + " printfbad2 printfbad3 profile2 profile3 pty1" -
 		  + " regx8bit rebuf reginttrad reint reint2 rsstart1 rsstart2 rsstart3 rstest6" -
-		  + " shadow sortfor sortu splitarg4 strtonum strftime switch2" -
-		  + " symtab1 symtab2 symtab3 symtab4 symtab5 symtab6 symtab7 symtab8 symtab9"
+		  + " shadow sortfor sortu split_after_fpat splitarg4" -
+		  + " strtonum strftime switch2 symtab1 symtab2 symtab3" -
+		  + " symtab4 symtab5 symtab6 symtab7 symtab8 symtab9"
 $		gosub list_of_tests
 $		return
 $
@@ -159,6 +161,13 @@ $		type sys$input:
 $		list = "inetechu inetecht inetdayu inetdayt"
 $		gosub list_of_tests
 $		return
+$!
+$extension:	echo "extension...."
+$		list = "inplace1 filefuncs fnmatch fts functab4 ordchr" -
+		+ " readdir revout revtwoway rwarray time"
+		gosub list_of_tests
+		return
+
 $
 $! list_of_tests: process 'list', a space-separated list of tests.
 $! Some tests assign their own 'list' and call us recursively,
@@ -259,6 +268,7 @@ $rstest6:
 $rswhite:
 $sortempty:
 $sortfor:
+$split_after_fpat:
 $splitarg4:
 $splitargv:
 $splitarr:
@@ -578,7 +588,7 @@ $defref:	echo "defref"
 $	set noOn
 $	AWKPATH_srcdir
 $	gawk --lint -f defref.awk >_defref.tmp 2>&1
-$	if .not.$status then call exit_code 2 _defref.tmp
+$	if .not. $status then call exit_code '$status' _defref.tmp
 $	set On
 $	cmp defref.ok sys$disk:[]_defref.tmp
 $	if $status then  rm _defref.tmp;
@@ -594,6 +604,16 @@ $
 $strftime:	echo "strftime"
 $	! this test could fail on slow machines or on a second boundary,
 $	! so if it does, double check the actual results
+$	! This test needs SYS$TIMEZONE_NAME and SYS$TIMEZONE_RULE
+$	! to be properly defined.
+$	! This test now needs GNV Corutils to work
+$	date_bin = "gnv$gnu:[bin]gnv$date.exe"
+$	if f$search(date_bin) .eqs. ""
+$	then
+$		echo "''test' skipped"
+$		return
+$	endif
+$	date := $'date_bin'
 $!!	date | gawk -v "OUTPUT"=_strftime.tmp -f strftime.awk
 $	now = f$time()
 $	wkd = f$extract(0,3,f$cvtime(now,,"WEEKDAY"))
@@ -601,11 +621,12 @@ $	mon = f$cvtime(now,"ABSOLUTE","MONTH")
 $	mon = f$extract(0,1,mon) + f$edit(f$extract(1,2,mon),"LOWERCASE")
 $	day = f$cvtime(now,,"DAY")
 $	tim = f$extract(0,8,f$cvtime(now,,"TIME"))
-$	tz  = ""
+$!	Can not use tz as it shows up in the C environment.
+$	timezone = f$trnlnm("SYS$TIMEZONE_NAME")
 $	yr  = f$cvtime(now,,"YEAR")
 $	if f$trnlnm("FTMP").nes."" then  close/noLog ftmp
 $	open/Write ftmp strftime.in
-$	write ftmp wkd," ",mon," ",day," ",tim," ",tz," ",yr
+$	write ftmp wkd," ",mon," ",day," ",tim," ",timezone," ",yr
 $	close ftmp
 $	gawk -v "OUTPUT"=_strftime.tmp -f strftime.awk strftime.in
 $	set noOn
@@ -637,7 +658,7 @@ $
 $incdupe:   echo "''test'"
 $   set noOn
 $   gawk --lint -i inclib -i inclib.awk "BEGIN {print sandwich(""a"", ""b"", ""c"")}" > _'test'.tmp 2>&1
-$   if .not. $status then call exit_code 1 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -646,7 +667,7 @@ $
 $incdupe2:   echo "''test'"
 $   set noOn
 $   gawk --lint -f inclib -f inclib.awk >_'test'.tmp 2>&1
-$   if .not. $status then call exit_code 1 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -661,7 +682,7 @@ $
 $incdupe4:   echo "''test'"
 $   set NoOn
 $   gawk --lint -f hello -i hello.awk >_'test'.tmp 2>&1
-$   if .not. $status then call exit_code 2 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -670,7 +691,7 @@ $
 $incdupe5:   echo "''test'"
 $   set NoOn
 $   gawk --lint -i hello -f hello.awk >_'test'.tmp 2>&1
-$   if .not. $status then call exit_code 2 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -679,7 +700,7 @@ $
 $incdupe6:   echo "''test'"
 $   set NoOn
 $   gawk --lint -i inchello -f hello.awk >_'test'.tmp 2>&1
-$   if .not. $status then call exit_code 2 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -688,7 +709,7 @@ $
 $incdupe7:   echo "''test'"
 $   set NoOn
 $   gawk --lint -f hello -i inchello >_'test'.tmp 2>&1
-$   if .not. $status then call exit_code 2 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -706,7 +727,7 @@ $symtab2:
 $symtab3:   echo "''test'"
 $   set noOn
 $   gawk -f 'test'.awk  >_'test'.tmp 2>&1
-$   if .not. $status then call exit_code 2 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -717,7 +738,7 @@ $symtab5:
 $symtab7:   echo "''test'"
 $   set noOn
 $   gawk -f 'test'.awk <'test'.in >_'test'.tmp 2>&1
-$   if .not. $status then call exit_code 2 _'test'.tmp
+$   if .not. $status then call exit_code '$status' _'test'.tmp
 $   cmp 'test'.ok sys$disk:[]_'test'.tmp
 $   if $status then rm _'test'.tmp;*
 $   set On
@@ -897,7 +918,7 @@ $noparms:	echo "noparms"
 $	set noOn
 $	AWKPATH_srcdir
 $	gawk -f noparms.awk >_noparms.tmp 2>&1
-$	if .not.$status then call exit_code 1 _noparms.tmp
+$	if .not. $status then call exit_code '$status' _noparms.tmp
 $	set On
 $	cmp noparms.ok sys$disk:[]_noparms.tmp
 $	if $status then  rm _noparms.tmp;
@@ -938,7 +959,12 @@ $	gawk -f nasty.awk >_nasty.tmp
 $	call fixup_LRL nasty.ok
 $	call fixup_LRL _nasty.tmp "purge"
 $	cmp nasty.ok sys$disk:[]_nasty.tmp
-$	if $status then  rm _nasty.tmp;
+$	if $status
+$	then
+$	    rm _nasty.tmp;
+$	    file = "lcl_root:[]nasty.ok"
+$	    if f$search(file) .nes. "" then rm 'file';*
+$	endif
 $	set On
 $	return
 $
@@ -948,7 +974,12 @@ $	gawk -f nasty2.awk >_nasty2.tmp
 $	call fixup_LRL nasty2.ok
 $	call fixup_LRL _nasty2.tmp "purge"
 $	cmp nasty2.ok sys$disk:[]_nasty2.tmp
-$	if $status then  rm _nasty2.tmp;
+$	if $status
+$	then
+$	    rm _nasty2.tmp;
+$	    file = "lcl_root:[]nasty2.ok"
+$	    if f$search(file) .nes. "" then rm 'file';*
+$	endif
 $	set On
 $	return
 $
@@ -968,7 +999,7 @@ $subslash:
 $	echo "''test'"
 $	set noOn
 $	gawk -f 'test'.awk >_'test'.tmp 2>&1
-$	if .not.$status then call exit_code 2 _'test'.tmp
+$	if .not. $status then call exit_code '$status' _'test'.tmp
 $	set On
 $	cmp 'test'.ok sys$disk:[]_'test'.tmp
 $	if $status then  rm _'test'.tmp;
@@ -1077,7 +1108,7 @@ $lintwarn:	echo "lintwarn"
 $	set noOn
 $	AWKPATH_srcdir
 $	gawk --lint -f lintwarn.awk >_lintwarn.tmp 2>&1
-$	if .not.$status then call exit_code 1 _lintwarn.tmp
+$	if .not. $status then call exit_code '$status' _lintwarn.tmp
 $	set On
 $	cmp lintwarn.ok sys$disk:[]_lintwarn.tmp
 $	if $status then  rm _lintwarn.tmp;
@@ -1120,7 +1151,7 @@ $sclifin:
 $	echo "''test'"
 $	set noOn
 $	gawk -f 'test'.awk 'test'.in >_'test'.tmp 2>&1
-$	if .not.$status then call exit_code 2 _'test'.tmp
+$	if .not. $status then call exit_code '$status' _'test'.tmp
 $	set On
 $	cmp 'test'.ok sys$disk:[]_'test'.tmp
 $	if $status then  rm _'test'.tmp;
@@ -1132,7 +1163,7 @@ $   !
 $	echo "''test'"
 $	set noOn
 $	gawk -f 'test'.awk <'test'.in >_'test'.tmp 2>&1
-$	if .not.$status then call exit_code 2 _'test'.tmp
+$	if .not. $status then call exit_code '$status' _'test'.tmp
 $	set On
 $	cmp 'test'.ok sys$disk:[]_'test'.tmp
 $	if $status then  rm _'test'.tmp;
@@ -1157,7 +1188,7 @@ $unterm:
 $	echo "''test'"
 $	set noOn
 $	gawk -f 'test'.awk 'test'.in >_'test'.tmp 2>&1
-$	if .not.$status then call exit_code 1 _'test'.tmp
+$	if .not. $status then call exit_code '$status' _'test'.tmp
 $	set On
 $	cmp 'test'.ok sys$disk:[]_'test'.tmp
 $	if $status then  rm _'test'.tmp;
@@ -1217,7 +1248,7 @@ $synerr2:
 $	echo "''test'"
 $	set noOn
 $	gawk -f 'test'.awk >_'test'.tmp 2>&1
-$	if .not.$status then call exit_code 1 _'test'.tmp
+$	if .not. $status then call exit_code '$status' _'test'.tmp
 $	set On
 $	cmp 'test'.ok sys$disk:[]_'test'.tmp
 $	if $status then  rm _'test'.tmp;
@@ -1237,7 +1268,7 @@ $
 $space:		echo "space"
 $	set noOn
 $	gawk -f " " space.awk >_space.tmp 2>&1
-$	if .not.$status then call exit_code 2 _space.tmp
+$	if .not. $status then call exit_code '$status' _space.tmp
 $	set On
 $!	we get a different error from what space.ok expects
 $	gawk "{gsub(""file specification syntax error"", ""no such file or directory""); print}" -
@@ -1320,7 +1351,7 @@ $
 $! This test is somewhat suspect for vms due to exit code manipulation
 $exitval1:	echo "exitval1"
 $	gawk -f exitval1.awk >_exitval1.tmp 2>&1
-$	if $status then  call exit_code 0 _exitval1.tmp
+$	if $status then  call exit_code '$status' _exitval1.tmp
 $	cmp exitval1.ok sys$disk:[]_exitval1.tmp
 $	if $status then  rm _exitval1.tmp;
 $	return
@@ -1424,7 +1455,7 @@ $!	nofile.ok expects no/such/file, but using that name in the test would
 $!	yield "file specification syntax error" instead of "no such file..."
 $	set noOn
 $	gawk "{}" no-such-file >_nofile.tmp 2>&1
-$	if .not.$status then call exit_code 2 _nofile.tmp
+$	if .not. $status then call exit_code '$status' _nofile.tmp
 $	set On
 $!	restore altered file name
 $	gawk "{gsub(""no-such-file"", ""no/such/file""); print}" _nofile.tmp >_nofile.too
@@ -1496,7 +1527,7 @@ $
 $mixed1:	echo "mixed1"
 $	set noOn
 $	gawk -f /dev/null --source "BEGIN {return junk}" >_mixed1.tmp 2>&1
-$	if .not.$status then call exit_code 1 _mixed1.tmp
+$	if .not. $status then call exit_code '$status' _mixed1.tmp
 $	set On
 $	cmp mixed1.ok sys$disk:[]_mixed1.tmp
 $	if $status then  rm _mixed1.tmp;
@@ -1758,7 +1789,7 @@ World!
 $	endif
 $	gawk /Commands="BEGIN { print ""World!"" }" _NL: /Output=_vms_cmd.tmp
 $	cmp vms_cmd.ok sys$disk:[]_vms_cmd.tmp
-$	if $status then  rm _vms_cmd.tmp;
+$	if $status then  rm _vms_cmd.tmp;,vms_cmd.ok;*
 $	return
 $
 $vms_io1:	echo "vms_io1"
@@ -1771,7 +1802,7 @@ $	gawk -f - >_vms_io1.tmp
 # prior to 3.0.4, gawk crashed doing any redirection after closing stdin
 BEGIN { print "Hello" >"/dev/stdout" }
 $	cmp vms_io1.ok sys$disk:[]_vms_io1.tmp
-$	if $status then  rm _vms_io1.tmp;
+$	if $status then  rm _vms_io1.tmp;,vms_io1.ok;*
 $	return
 $
 $vms_io2:	echo "vms_io2"
@@ -1799,7 +1830,90 @@ $	set On
 $	cmp _NL: sys$disk:[]_vms_io2.tmp
 $	if $status then  rm _vms_io2.tmp;
 $	cmp vms_io2.ok sys$disk:[]_vms_io2.vfc
-$	if $status then  rm _vms_io2.vfc;*
+$	if $status then  rm _vms_io2.vfc;*,vms_io2.ok;*
+$	return
+$!
+$!
+$inplace1:
+$	set process/parse=extended ! ODS-5 only
+$	echo "''test'"
+$	filefunc_file = "[-]gawkapi.o"
+$	open/write awkfile _'test'.awk
+$	write awkfile "@load ""inplace"""
+$!	write awkfile "BEGIN {print ""before""}"
+$	write awkfile "   {gsub(/foo/, ""bar""); print}"
+$!	write awkfile "END {print ""after""}"
+$	close awkfile
+$	copy inplace^.1.in _'test'.1
+$	copy inplace^.2.in _'test'.2
+$	set noOn
+$	AWKLIBPATH_dir
+$	gawk -f _'test'.awk _'test'.1 <inplace.in >_'test'.1.tmp 2>&1
+$	if .not. $status then call exit_code '$status' _'test'.1.tmp
+$	AWKLIBPATH_dir
+$	gawk -f _'test'.awk _'test'.2 <inplace.in >_'test'.2.tmp 2>&1
+$	if .not. $status then call exit_code '$status' _'test'.2.tmp
+$	set On
+$	cmp 'test'.1.ok sys$disk:[]_'test'.1.tmp
+$	if $status then rm _'test'.1.tmp;,_'test'.1;
+$	cmp 'test'.2.ok sys$disk:[]_'test'.2.tmp
+$	if $status then rm _'test'.2.tmp;,_'test'.2;,_'test'.awk;
+$	return
+$!
+$filefuncs:
+$fnmatch:
+$functab4:
+$ordchr:
+$revout:
+$revtwoway:
+$time:
+$	echo "''test'"
+$	filefunc_file = "[-]gawkapi.o"
+$	open/write gapi 'filefunc_file'
+$	close gapi
+$	set noOn
+$	AWKLIBPATH_dir
+$	gawk -f 'test'.awk 'test'.in >_'test'.tmp 2>&1
+$	if .not. $status then call exit_code '$status' _'test'.tmp
+$	set On
+$	cmp 'test'.ok sys$disk:[]_'test'.tmp
+$	if $status then rm _'test'.tmp;
+$	if f$search(filefunc_file) .nes. "" then rm 'filefunc_file';*
+$	return
+$!
+$rwarray:
+$	echo "''test'"
+$	set noOn
+$	AWKLIBPATH_dir
+$	gawk -f 'test'.awk 'test'.in >_'test'.tmp 2>&1
+$	if .not. $status then call exit_code '$status' _'test'.tmp
+$	set On
+$	cmp orig.out new.out
+$	if $status
+$	then
+$	    open/append tout _'test'.tmp
+$	    write tout "old and new are equal - GOOD"
+$	    close tout
+$	endif
+$	cmp 'test'.ok sys$disk:[]_'test'.tmp
+$	if $status then rm _'test'.tmp;,orig.bin;,orig.out;,new.out;
+$	return
+$!
+$readdir:
+$fts:
+$	echo "''test'"
+$	set noOn
+$	AWKLIBPATH_dir
+$	gawk -f 'test'.awk >_'test'.tmp 2>&1
+$	if .not. $status
+$	then
+$	    call exit_code '$status' _'test'.tmp
+$	    write sys$output _'test'.tmp
+$	else
+$	    if f$search("_''test'.tmp") .nes. "" then rm _'test'.tmp;*
+$	    if f$search("_''test'.") .nes. "" then rm _'test'.;*
+$	endif
+$	set On
 $	return
 $
 $clean:
@@ -1869,10 +1983,12 @@ $ endsubroutine !fixup_LRL
 $
 $! add a fake "EXIT CODE" record to the end of the temporary output file
 $! to simulate the ``|| echo EXIT CODE $$? >>_$@'' shell script usage
+$! Unix code = vms_code & (255 * 2^3) >> 3
 $exit_code: subroutine
+$	unix_status = (p1 .and. %x7f8) / 8
 $	if f$trnlnm("FTMP").nes."" then  close/noLog ftmp
 $	open/Append ftmp 'p2'
-$	write ftmp "EXIT CODE: ",p1
+$	write ftmp "EXIT CODE: ",'unix_status'
 $	close ftmp
 $ endsubroutine !exit_code
 $
diff --git a/xalloc.h b/xalloc.h
index eb0ef1a0..0d169cf9 100644
--- a/xalloc.h
+++ b/xalloc.h
@@ -136,6 +136,8 @@ xnmalloc (size_t n, size_t s)
 
 #ifdef GAWK
 #include <errno.h>
+extern void r_fatal(const char *msg, ...) ATTRIBUTE_NORETURN ;
+
 /* Allocate an array of N objects, each with S bytes of memory,
    dynamically, with error checking.  S must be nonzero.
    Clear the contents afterwards.  */
@@ -165,8 +167,6 @@ xrealloc(void *p, size_t size)
 void
 xalloc_die (void)
 {
-	extern void r_fatal(const char *msg, ...) ATTRIBUTE_NORETURN ;
-
 	r_fatal(_("xalloc: malloc failed: %s"), strerror(errno));
 }
 
@@ -179,6 +179,22 @@ xmemdup (void const *p, size_t s)
 {
   return memcpy (xmalloc (s), p, s);
 }
+
+/* xstrdup --- strdup and die if fails */
+char *xstrdup(const char *s)
+{
+	char *p;
+	int l;
+
+	if (s == NULL)
+		r_fatal(_("xstrdup: null parameter"));
+
+	l = strlen(s);
+	p = xmemdup(s, l + 1);
+	p[l] = '\0';
+
+	return p;
+}
 #endif
 
 /* Change the size of an allocated block of memory P to an array of N
@@ -260,7 +276,7 @@ x2nrealloc (void *p, size_t *pn, size_t s)
              requests, when the invoking code specifies an old size of
              zero.  64 bytes is the largest "small" request for the
              GNU C library malloc.  */
-          enum { DEFAULT_MXFAST = 64 };
+          enum { DEFAULT_MXFAST = 64 * sizeof (size_t) / 4 };
 
           n = DEFAULT_MXFAST / s;
           n += !n;
@@ -274,7 +290,7 @@ x2nrealloc (void *p, size_t *pn, size_t s)
          worth the trouble.  */
       if ((size_t) -1 / 3 * 2 / s <= n)
         xalloc_die ();
-      n += (n + 1) / 2;
+      n += n / 2 + 1;
     }
 
   *pn = n;
author	Juergen Kahrs <Juergen.Kahrs@googlemail.com>	2014-06-24 13:18:33 +0200
committer	Juergen Kahrs <Juergen.Kahrs@googlemail.com>	2014-06-24 13:18:33 +0200
commit	f1245d04a9f076773c60499b468f44ed9c91b59b (patch)
tree	2b49234400150bfaac7ebf8c017562300edc7471
parent	ee9707cc44eea3ca64cb71666ac3e8ed26a3bb7f (diff)
parent	78ded8ee8f11a321c96417e7d02dac2f5723a221 (diff)
download	egawk-f1245d04a9f076773c60499b468f44ed9c91b59b.tar.gz egawk-f1245d04a9f076773c60499b468f44ed9c91b59b.tar.bz2 egawk-f1245d04a9f076773c60499b468f44ed9c91b59b.zip