diff options
| author | Arnold D. Robbins <arnold@skeeve.com> | 2014-02-27 05:57:47 +0200 |
|---|---|---|
| committer | Arnold D. Robbins <arnold@skeeve.com> | 2014-02-27 05:57:47 +0200 |
| commit | c40640f98379cbe112277033e3a8ab4caaa35ab8 (patch) | |
| tree | e1886493ece3f63646b47571eccd8698f651dbd9 | |
| parent | dad57e4fdd815c9038267ec0fc7aa593f20b0a05 (diff) | |
| download | gawk-c40640f98379cbe112277033e3a8ab4caaa35ab8.tar.gz | |
Start on doc fixes.
| -rw-r--r-- | doc/ChangeLog | 5 | ||||
| -rw-r--r-- | doc/gawk.info | 923 | ||||
| -rw-r--r-- | doc/gawk.texi | 166 | ||||
| -rw-r--r-- | doc/gawktexi.in | 166 |
4 files changed, 658 insertions, 602 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index dfebc27e..89164b93 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2014-02-27 Arnold D. Robbins <arnold@skeeve.com> + + * gawktexi.in: Lots of small fixes throughout, update of + profiling output. + 2014-02-20 Arnold D. Robbins <arnold@skeeve.com> * gawktexi.in: Add a quote to the alarm clock program. diff --git a/doc/gawk.info b/doc/gawk.info index a3ab750c..eb7c52fb 100644 --- a/doc/gawk.info +++ b/doc/gawk.info @@ -9116,9 +9116,11 @@ 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. + + 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 @@ -11969,10 +11971,10 @@ 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 - standard. See the Austin Group website + `fflush()' was added to Brian Kernighan's version of `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). POSIX standardizes `fflush()' as follows: If there is no argument, @@ -12689,7 +12691,7 @@ 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. +restriction.) The BODY-OF-FUNCTION consists of `awk' statements. It is the most important part of the definition, because it says what the function @@ -12732,8 +12734,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 @@ -12803,7 +12805,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. @@ -12843,13 +12846,19 @@ an `awk' version of `ctime()': 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: @@ -12863,16 +12872,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) @@ -13267,7 +13272,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. @@ -13418,8 +13423,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 @@ -13619,7 +13624,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 @@ -13870,9 +13875,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 @@ -13906,7 +13911,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 @@ -13982,8 +13987,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 @@ -14033,7 +14038,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 @@ -14474,7 +14479,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 @@ -14970,7 +14975,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 @@ -14990,9 +14995,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) { @@ -15339,8 +15344,8 @@ 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 and index and a value, -and then processes the element. +user-defined function that expects to receive an index and a value, and +then processes the element. File: gawk.info, Node: Sample Programs, Next: Advanced Features, Prev: Library Functions, Up: Top @@ -15601,7 +15606,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 @@ -18527,7 +18532,8 @@ 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 @@ -18665,56 +18671,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() + } + } - # 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!" + } 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 @@ -18765,8 +18779,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/ @@ -18825,6 +18838,9 @@ 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: Internationalization, Next: Debugger, Prev: Advanced Features, Up: Top @@ -25672,7 +25688,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 @@ -29975,7 +29991,7 @@ Index * ' (single quote): One-shot. (line 15) * ' (single quote), vs. apostrophe: Comments. (line 27) * ' (single quote), with double quotes: Quoting. (line 53) -* () (parentheses) <1>: Profiling. (line 138) +* () (parentheses) <1>: Profiling. (line 146) * () (parentheses): Regexp Operators. (line 79) * * (asterisk), * operator, as multiplication operator: Precedence. (line 55) @@ -30481,7 +30497,7 @@ Index * Boolean expressions, as patterns: Expression Patterns. (line 41) * 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) @@ -30688,7 +30704,7 @@ Index * csh utility: Statements/Lines. (line 44) * csh utility, POSIXLY_CORRECT environment variable: Options. (line 348) * csh utility, |& operator, comparison with: Two-way I/O. (line 44) -* ctime() user-defined function: Function Example. (line 72) +* ctime() user-defined function: Function Example. (line 73) * currency symbols, localization: Explaining gettext. (line 103) * custom.h file: Configuration Philosophy. (line 30) @@ -31288,8 +31304,8 @@ Index * 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: Profiling. (line 137) * functions, user-defined, library of: Library Functions. (line 6) * functions, user-defined, next/nextfile statements and <1>: Nextfile Statement. (line 47) @@ -31297,7 +31313,7 @@ Index (line 45) * G-d: Acknowledgments. (line 78) * Garfinkle, Scott: Contributors. (line 34) -* gawk program, dynamic profiling: Profiling. (line 172) +* gawk program, dynamic profiling: Profiling. (line 179) * gawk, ARGIND variable in: Other Arguments. (line 12) * gawk, awk and <1>: This Manual. (line 14) * gawk, awk and: Preface. (line 23) @@ -31480,7 +31496,7 @@ Index * hexadecimal values, enabling interpretation of: Options. (line 207) * histsort.awk program: History Sorting. (line 25) * Hughes, Phil: Acknowledgments. (line 43) -* HUP signal: Profiling. (line 204) +* HUP signal: Profiling. (line 211) * hyphen (-), - operator: Precedence. (line 52) * hyphen (-), -- operator <1>: Precedence. (line 46) * hyphen (-), -- operator: Increment Ops. (line 48) @@ -31556,7 +31572,7 @@ Index * 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 signal (MS-Windows): Profiling. (line 214) * int() function: Numeric Functions. (line 23) * integer, arbitrary precision: Arbitrary Precision Integers. (line 6) @@ -31603,11 +31619,12 @@ Index * 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 <5>: Library Functions. (line 12) +* Kernighan, Brian <6>: Concatenation. (line 6) +* Kernighan, Brian <7>: Acknowledgments. (line 72) +* Kernighan, Brian <8>: 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) @@ -31704,7 +31721,7 @@ Index * long options: Command Line. (line 13) * loops: While Statement. (line 6) * loops, continue statements and: For Statement. (line 64) -* loops, count for header: Profiling. (line 123) +* loops, count for header: Profiling. (line 131) * loops, exiting: Break Statement. (line 6) * loops, See Also while statement: While Statement. (line 6) * ls utility: More Complex. (line 15) @@ -31912,14 +31929,14 @@ Index * 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 () <1>: Profiling. (line 146) * parentheses (): Regexp Operators. (line 79) * password file: Passwd Functions. (line 16) * patsplit() function (gawk): String Functions. (line 290) * patterns: Patterns and Actions. (line 6) * patterns, comparison expressions as: Expression Patterns. (line 14) -* patterns, counts: Profiling. (line 110) +* patterns, counts: Profiling. (line 118) * patterns, default: Very Simple. (line 34) * patterns, empty: Empty. (line 6) * patterns, expressions as: Regexp Patterns. (line 6) @@ -31944,6 +31961,7 @@ Index * pipes, output: Redirection. (line 57) * Pitts, Dave <1>: Bugs. (line 73) * Pitts, Dave: Acknowledgments. (line 60) +* Plauger, P.J.: Library Functions. (line 12) * plus sign (+): Regexp Operators. (line 102) * plus sign (+), + operator: Precedence. (line 52) * plus sign (+), ++ operator <1>: Precedence. (line 46) @@ -32080,7 +32098,7 @@ Index * PROCINFO array <6>: Auto-set. (line 133) * PROCINFO array: Obsolete. (line 11) * profiling awk programs: Profiling. (line 6) -* profiling awk programs, dynamically: Profiling. (line 172) +* profiling awk programs, dynamically: Profiling. (line 179) * program, definition of: Getting Started. (line 21) * programmers, attractiveness of: Two-way I/O. (line 6) * programming conventions, --non-decimal-data option: Nondecimal Data. @@ -32116,7 +32134,7 @@ Index * QuikTrim Awk: Other Versions. (line 134) * quit debugger command: Miscellaneous Debugger Commands. (line 99) -* QUIT signal (MS-Windows): Profiling. (line 207) +* QUIT signal (MS-Windows): Profiling. (line 214) * quoting <1>: Comments. (line 27) * quoting <2>: Long. (line 26) * quoting: Read Terminal. (line 25) @@ -32215,7 +32233,7 @@ Index * 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) +* rev() user-defined function: Function Example. (line 53) * revoutput extension: Extension Sample Revout. (line 11) * revtwoway extension: Extension Sample Rev2way. @@ -32368,14 +32386,14 @@ Index (line 56) * 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) +* SIGHUP signal: Profiling. (line 211) +* SIGINT signal (MS-Windows): Profiling. (line 214) +* signals, HUP/SIGHUP: Profiling. (line 211) +* signals, INT/SIGINT (MS-Windows): Profiling. (line 214) +* signals, QUIT/SIGQUIT (MS-Windows): Profiling. (line 214) +* signals, USR1/SIGUSR1: Profiling. (line 188) +* SIGQUIT signal (MS-Windows): Profiling. (line 214) +* SIGUSR1 signal: Profiling. (line 188) * silent debugger command: Debugger Execution Control. (line 10) * sin() function: Numeric Functions. (line 75) @@ -32616,12 +32634,12 @@ Index * up debugger command: Execution Stack. (line 33) * user database, reading: Passwd Functions. (line 6) * user-defined, functions: User-defined. (line 6) -* user-defined, functions, counts: Profiling. (line 129) +* user-defined, functions, counts: 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: Profiling. (line 188) * values, numeric: Basic Data Typing. (line 13) * values, string: Basic Data Typing. (line 13) * variable typing: Typing and Comparison. @@ -32713,7 +32731,7 @@ Index * 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) @@ -32919,347 +32937,348 @@ Node: While Statement384453 Node: Do Statement386497 Node: For Statement387653 Node: Switch Statement390805 -Node: Break Statement392902 -Node: Continue Statement394892 -Node: Next Statement396685 -Node: Nextfile Statement399075 -Node: Exit Statement401718 -Node: Built-in Variables404134 -Node: User-modified405229 -Ref: User-modified-Footnote-1413587 -Node: Auto-set413649 -Ref: Auto-set-Footnote-1426727 -Ref: Auto-set-Footnote-2426932 -Node: ARGC and ARGV426988 -Node: Arrays430839 -Node: Array Basics432344 -Node: Array Intro433170 -Node: Reference to Elements437487 -Node: Assigning Elements439757 -Node: Array Example440248 -Node: Scanning an Array441980 -Node: Controlling Scanning444294 -Ref: Controlling Scanning-Footnote-1449381 -Node: Delete449697 -Ref: Delete-Footnote-1452462 -Node: Numeric Array Subscripts452519 -Node: Uninitialized Subscripts454702 -Node: Multidimensional456329 -Node: Multiscanning459422 -Node: Arrays of Arrays461011 -Node: Functions465651 -Node: Built-in466470 -Node: Calling Built-in467548 -Node: Numeric Functions469536 -Ref: Numeric Functions-Footnote-1473368 -Ref: Numeric Functions-Footnote-2473725 -Ref: Numeric Functions-Footnote-3473773 -Node: String Functions474042 -Ref: String Functions-Footnote-1496962 -Ref: String Functions-Footnote-2497091 -Ref: String Functions-Footnote-3497339 -Node: Gory Details497426 -Ref: table-sub-escapes499105 -Ref: table-sub-posix-92500459 -Ref: table-sub-proposed501810 -Ref: table-posix-sub503164 -Ref: table-gensub-escapes504709 -Ref: Gory Details-Footnote-1505885 -Ref: Gory Details-Footnote-2505936 -Node: I/O Functions506087 -Ref: I/O Functions-Footnote-1513072 -Node: Time Functions513219 -Ref: Time Functions-Footnote-1524152 -Ref: Time Functions-Footnote-2524220 -Ref: Time Functions-Footnote-3524378 -Ref: Time Functions-Footnote-4524489 -Ref: Time Functions-Footnote-5524601 -Ref: Time Functions-Footnote-6524828 -Node: Bitwise Functions525094 -Ref: table-bitwise-ops525656 -Ref: Bitwise Functions-Footnote-1529877 -Node: Type Functions530061 -Node: I18N Functions531212 -Node: User-defined532839 -Node: Definition Syntax533643 -Ref: Definition Syntax-Footnote-1538553 -Node: Function Example538622 -Node: Function Caveats541216 -Node: Calling A Function541637 -Node: Variable Scope542752 -Node: Pass By Value/Reference545715 -Node: Return Statement549223 -Node: Dynamic Typing552204 -Node: Indirect Calls553135 -Node: Library Functions562820 -Ref: Library Functions-Footnote-1566333 -Ref: Library Functions-Footnote-2566476 -Node: Library Names566647 -Ref: Library Names-Footnote-1570118 -Ref: Library Names-Footnote-2570338 -Node: General Functions570424 -Node: Strtonum Function571452 -Node: Assert Function574382 -Node: Round Function577708 -Node: Cliff Random Function579251 -Node: Ordinal Functions580267 -Ref: Ordinal Functions-Footnote-1583339 -Ref: Ordinal Functions-Footnote-2583591 -Node: Join Function583800 -Ref: Join Function-Footnote-1585571 -Node: Getlocaltime Function585771 -Node: Readfile Function589512 -Node: Data File Management591351 -Node: Filetrans Function591983 -Node: Rewind Function596052 -Node: File Checking597439 -Node: Empty Files598533 -Node: Ignoring Assigns600763 -Node: Getopt Function602316 -Ref: Getopt Function-Footnote-1613619 -Node: Passwd Functions613822 -Ref: Passwd Functions-Footnote-1622797 -Node: Group Functions622885 -Node: Walking Arrays630969 -Node: Sample Programs633106 -Node: Running Examples633780 -Node: Clones634508 -Node: Cut Program635732 -Node: Egrep Program645577 -Ref: Egrep Program-Footnote-1653350 -Node: Id Program653460 -Node: Split Program657076 -Ref: Split Program-Footnote-1660595 -Node: Tee Program660723 -Node: Uniq Program663526 -Node: Wc Program670955 -Ref: Wc Program-Footnote-1675221 -Ref: Wc Program-Footnote-2675421 -Node: Miscellaneous Programs675513 -Node: Dupword Program676701 -Node: Alarm Program678732 -Node: Translate Program683539 -Ref: Translate Program-Footnote-1687926 -Ref: Translate Program-Footnote-2688174 -Node: Labels Program688308 -Ref: Labels Program-Footnote-1691679 -Node: Word Sorting691763 -Node: History Sorting695647 -Node: Extract Program697486 -Ref: Extract Program-Footnote-1704989 -Node: Simple Sed705117 -Node: Igawk Program708179 -Ref: Igawk Program-Footnote-1723336 -Ref: Igawk Program-Footnote-2723537 -Node: Anagram Program723675 -Node: Signature Program726743 -Node: Advanced Features727843 -Node: Nondecimal Data729729 -Node: Array Sorting731312 -Node: Controlling Array Traversal732009 -Node: Array Sorting Functions740293 -Ref: Array Sorting Functions-Footnote-1744162 -Node: Two-way I/O744356 -Ref: Two-way I/O-Footnote-1749788 -Node: TCP/IP Networking749858 -Node: Profiling752702 -Node: Internationalization760199 -Node: I18N and L10N761624 -Node: Explaining gettext762310 -Ref: Explaining gettext-Footnote-1767378 -Ref: Explaining gettext-Footnote-2767562 -Node: Programmer i18n767727 -Node: Translator i18n771929 -Node: String Extraction772722 -Ref: String Extraction-Footnote-1773683 -Node: Printf Ordering773769 -Ref: Printf Ordering-Footnote-1776553 -Node: I18N Portability776617 -Ref: I18N Portability-Footnote-1779066 -Node: I18N Example779129 -Ref: I18N Example-Footnote-1781767 -Node: Gawk I18N781839 -Node: Debugger782460 -Node: Debugging783431 -Node: Debugging Concepts783864 -Node: Debugging Terms785720 -Node: Awk Debugging788317 -Node: Sample Debugging Session789209 -Node: Debugger Invocation789729 -Node: Finding The Bug791061 -Node: List of Debugger Commands797549 -Node: Breakpoint Control798883 -Node: Debugger Execution Control802547 -Node: Viewing And Changing Data805907 -Node: Execution Stack809263 -Node: Debugger Info810730 -Node: Miscellaneous Debugger Commands814712 -Node: Readline Support819888 -Node: Limitations820719 -Node: Arbitrary Precision Arithmetic822971 -Ref: Arbitrary Precision Arithmetic-Footnote-1824620 -Node: General Arithmetic824768 -Node: Floating Point Issues826488 -Node: String Conversion Precision827369 -Ref: String Conversion Precision-Footnote-1829074 -Node: Unexpected Results829183 -Node: POSIX Floating Point Problems831336 -Ref: POSIX Floating Point Problems-Footnote-1835161 -Node: Integer Programming835199 -Node: Floating-point Programming836938 -Ref: Floating-point Programming-Footnote-1843269 -Ref: Floating-point Programming-Footnote-2843539 -Node: Floating-point Representation843803 -Node: Floating-point Context844968 -Ref: table-ieee-formats845807 -Node: Rounding Mode847191 -Ref: table-rounding-modes847670 -Ref: Rounding Mode-Footnote-1850685 -Node: Gawk and MPFR850864 -Node: Arbitrary Precision Floats852119 -Ref: Arbitrary Precision Floats-Footnote-1854562 -Node: Setting Precision854878 -Ref: table-predefined-precision-strings855564 -Node: Setting Rounding Mode857709 -Ref: table-gawk-rounding-modes858113 -Node: Floating-point Constants859300 -Node: Changing Precision860729 -Ref: Changing Precision-Footnote-1862126 -Node: Exact Arithmetic862300 -Node: Arbitrary Precision Integers865438 -Ref: Arbitrary Precision Integers-Footnote-1868456 -Node: Dynamic Extensions868603 -Node: Extension Intro870061 -Node: Plugin License871326 -Node: Extension Mechanism Outline872011 -Ref: load-extension872428 -Ref: load-new-function873906 -Ref: call-new-function874901 -Node: Extension API Description876916 -Node: Extension API Functions Introduction878129 -Node: General Data Types882995 -Ref: General Data Types-Footnote-1888597 -Node: Requesting Values888896 -Ref: table-value-types-returned889627 -Node: Constructor Functions890581 -Node: Registration Functions893601 -Node: Extension Functions894286 -Node: Exit Callback Functions896511 -Node: Extension Version String897760 -Node: Input Parsers898410 -Node: Output Wrappers908167 -Node: Two-way processors912677 -Node: Printing Messages914885 -Ref: Printing Messages-Footnote-1915962 -Node: Updating `ERRNO'916114 -Node: Accessing Parameters916853 -Node: Symbol Table Access918083 -Node: Symbol table by name918595 -Node: Symbol table by cookie920342 -Ref: Symbol table by cookie-Footnote-1924472 -Node: Cached values924535 -Ref: Cached values-Footnote-1927984 -Node: Array Manipulation928075 -Ref: Array Manipulation-Footnote-1929173 -Node: Array Data Types929212 -Ref: Array Data Types-Footnote-1931915 -Node: Array Functions932007 -Node: Flattening Arrays935773 -Node: Creating Arrays942625 -Node: Extension API Variables947350 -Node: Extension Versioning947986 -Node: Extension API Informational Variables949887 -Node: Extension API Boilerplate950973 -Node: Finding Extensions954777 -Node: Extension Example955337 -Node: Internal File Description956067 -Node: Internal File Ops960158 -Ref: Internal File Ops-Footnote-1971666 -Node: Using Internal File Ops971806 -Ref: Using Internal File Ops-Footnote-1974159 -Node: Extension Samples974425 -Node: Extension Sample File Functions975949 -Node: Extension Sample Fnmatch984434 -Node: Extension Sample Fork986160 -Node: Extension Sample Inplace987378 -Node: Extension Sample Ord989156 -Node: Extension Sample Readdir989992 -Node: Extension Sample Revout991524 -Node: Extension Sample Rev2way992117 -Node: Extension Sample Read write array992807 -Node: Extension Sample Readfile994690 -Node: Extension Sample API Tests995508 -Node: Extension Sample Time996033 -Node: gawkextlib997397 -Node: Language History1000178 -Node: V7/SVR3.11001771 -Node: SVR41004091 -Node: POSIX1005533 -Node: BTL1006919 -Node: POSIX/GNU1007653 -Node: Feature History1013252 -Node: Common Extensions1026216 -Node: Ranges and Locales1027528 -Ref: Ranges and Locales-Footnote-11032146 -Ref: Ranges and Locales-Footnote-21032173 -Ref: Ranges and Locales-Footnote-31032433 -Node: Contributors1032654 -Node: Installation1037799 -Node: Gawk Distribution1038693 -Node: Getting1039177 -Node: Extracting1040003 -Node: Distribution contents1041695 -Node: Unix Installation1047400 -Node: Quick Installation1048017 -Node: Additional Configuration Options1050461 -Node: Configuration Philosophy1052197 -Node: Non-Unix Installation1054551 -Node: PC Installation1055009 -Node: PC Binary Installation1056308 -Node: PC Compiling1058156 -Node: PC Testing1061100 -Node: PC Using1062276 -Node: Cygwin1066461 -Node: MSYS1067461 -Node: VMS Installation1067975 -Node: VMS Compilation1068739 -Ref: VMS Compilation-Footnote-11070354 -Node: VMS Dynamic Extensions1070412 -Node: VMS Installation Details1071785 -Node: VMS Running1074032 -Node: VMS GNV1076866 -Node: VMS Old Gawk1077589 -Node: Bugs1078059 -Node: Other Versions1081977 -Node: Notes1088061 -Node: Compatibility Mode1088861 -Node: Additions1089644 -Node: Accessing The Source1090571 -Node: Adding Code1092011 -Node: New Ports1098056 -Node: Derived Files1102191 -Ref: Derived Files-Footnote-11107512 -Ref: Derived Files-Footnote-21107546 -Ref: Derived Files-Footnote-31108146 -Node: Future Extensions1108244 -Node: Implementation Limitations1108827 -Node: Extension Design1110079 -Node: Old Extension Problems1111233 -Ref: Old Extension Problems-Footnote-11112741 -Node: Extension New Mechanism Goals1112798 -Ref: Extension New Mechanism Goals-Footnote-11116163 -Node: Extension Other Design Decisions1116349 -Node: Extension Future Growth1118455 -Node: Old Extension Mechanism1119291 -Node: Basic Concepts1121031 -Node: Basic High Level1121712 -Ref: figure-general-flow1121983 -Ref: figure-process-flow1122582 -Ref: Basic High Level-Footnote-11125811 -Node: Basic Data Typing1125996 -Node: Glossary1129351 -Node: Copying1154813 -Node: GNU Free Documentation License1192370 -Node: Index1217507 +Node: Break Statement392959 +Node: Continue Statement394949 +Node: Next Statement396742 +Node: Nextfile Statement399132 +Node: Exit Statement401775 +Node: Built-in Variables404191 +Node: User-modified405286 +Ref: User-modified-Footnote-1413644 +Node: Auto-set413706 +Ref: Auto-set-Footnote-1426784 +Ref: Auto-set-Footnote-2426989 +Node: ARGC and ARGV427045 +Node: Arrays430896 +Node: Array Basics432401 +Node: Array Intro433227 +Node: Reference to Elements437544 +Node: Assigning Elements439814 +Node: Array Example440305 +Node: Scanning an Array442037 +Node: Controlling Scanning444351 +Ref: Controlling Scanning-Footnote-1449438 +Node: Delete449754 +Ref: Delete-Footnote-1452519 +Node: Numeric Array Subscripts452576 +Node: Uninitialized Subscripts454759 +Node: Multidimensional456386 +Node: Multiscanning459479 +Node: Arrays of Arrays461068 +Node: Functions465708 +Node: Built-in466527 +Node: Calling Built-in467605 +Node: Numeric Functions469593 +Ref: Numeric Functions-Footnote-1473425 +Ref: Numeric Functions-Footnote-2473782 +Ref: Numeric Functions-Footnote-3473830 +Node: String Functions474099 +Ref: String Functions-Footnote-1497019 +Ref: String Functions-Footnote-2497148 +Ref: String Functions-Footnote-3497396 +Node: Gory Details497483 +Ref: table-sub-escapes499162 +Ref: table-sub-posix-92500516 +Ref: table-sub-proposed501867 +Ref: table-posix-sub503221 +Ref: table-gensub-escapes504766 +Ref: Gory Details-Footnote-1505942 +Ref: Gory Details-Footnote-2505993 +Node: I/O Functions506144 +Ref: I/O Functions-Footnote-1513134 +Node: Time Functions513281 +Ref: Time Functions-Footnote-1524214 +Ref: Time Functions-Footnote-2524282 +Ref: Time Functions-Footnote-3524440 +Ref: Time Functions-Footnote-4524551 +Ref: Time Functions-Footnote-5524663 +Ref: Time Functions-Footnote-6524890 +Node: Bitwise Functions525156 +Ref: table-bitwise-ops525718 +Ref: Bitwise Functions-Footnote-1529939 +Node: Type Functions530123 +Node: I18N Functions531274 +Node: User-defined532901 +Node: Definition Syntax533705 +Ref: Definition Syntax-Footnote-1538619 +Node: Function Example538688 +Ref: Function Example-Footnote-1541337 +Node: Function Caveats541359 +Node: Calling A Function541877 +Node: Variable Scope542832 +Node: Pass By Value/Reference545795 +Node: Return Statement549303 +Node: Dynamic Typing552284 +Node: Indirect Calls553215 +Node: Library Functions562902 +Ref: Library Functions-Footnote-1566415 +Ref: Library Functions-Footnote-2566558 +Node: Library Names566729 +Ref: Library Names-Footnote-1570202 +Ref: Library Names-Footnote-2570422 +Node: General Functions570508 +Node: Strtonum Function571536 +Node: Assert Function574466 +Node: Round Function577792 +Node: Cliff Random Function579333 +Node: Ordinal Functions580349 +Ref: Ordinal Functions-Footnote-1583426 +Ref: Ordinal Functions-Footnote-2583678 +Node: Join Function583889 +Ref: Join Function-Footnote-1585660 +Node: Getlocaltime Function585860 +Node: Readfile Function589601 +Node: Data File Management591440 +Node: Filetrans Function592072 +Node: Rewind Function596141 +Node: File Checking597528 +Node: Empty Files598622 +Node: Ignoring Assigns600852 +Node: Getopt Function602406 +Ref: Getopt Function-Footnote-1613709 +Node: Passwd Functions613912 +Ref: Passwd Functions-Footnote-1622890 +Node: Group Functions622978 +Node: Walking Arrays631062 +Node: Sample Programs633198 +Node: Running Examples633872 +Node: Clones634600 +Node: Cut Program635824 +Node: Egrep Program645675 +Ref: Egrep Program-Footnote-1653448 +Node: Id Program653558 +Node: Split Program657174 +Ref: Split Program-Footnote-1660693 +Node: Tee Program660821 +Node: Uniq Program663624 +Node: Wc Program671053 +Ref: Wc Program-Footnote-1675319 +Ref: Wc Program-Footnote-2675519 +Node: Miscellaneous Programs675611 +Node: Dupword Program676799 +Node: Alarm Program678830 +Node: Translate Program683637 +Ref: Translate Program-Footnote-1688024 +Ref: Translate Program-Footnote-2688272 +Node: Labels Program688406 +Ref: Labels Program-Footnote-1691777 +Node: Word Sorting691861 +Node: History Sorting695745 +Node: Extract Program697584 +Ref: Extract Program-Footnote-1705087 +Node: Simple Sed705215 +Node: Igawk Program708277 +Ref: Igawk Program-Footnote-1723434 +Ref: Igawk Program-Footnote-2723635 +Node: Anagram Program723773 +Node: Signature Program726841 +Node: Advanced Features727941 +Node: Nondecimal Data729827 +Node: Array Sorting731410 +Node: Controlling Array Traversal732107 +Node: Array Sorting Functions740391 +Ref: Array Sorting Functions-Footnote-1744260 +Node: Two-way I/O744454 +Ref: Two-way I/O-Footnote-1749886 +Node: TCP/IP Networking749968 +Node: Profiling752812 +Node: Internationalization760315 +Node: I18N and L10N761740 +Node: Explaining gettext762426 +Ref: Explaining gettext-Footnote-1767494 +Ref: Explaining gettext-Footnote-2767678 +Node: Programmer i18n767843 +Node: Translator i18n772045 +Node: String Extraction772838 +Ref: String Extraction-Footnote-1773799 +Node: Printf Ordering773885 +Ref: Printf Ordering-Footnote-1776669 +Node: I18N Portability776733 +Ref: I18N Portability-Footnote-1779182 +Node: I18N Example779245 +Ref: I18N Example-Footnote-1781883 +Node: Gawk I18N781955 +Node: Debugger782576 +Node: Debugging783547 +Node: Debugging Concepts783980 +Node: Debugging Terms785836 +Node: Awk Debugging788433 +Node: Sample Debugging Session789325 +Node: Debugger Invocation789845 +Node: Finding The Bug791177 +Node: List of Debugger Commands797665 +Node: Breakpoint Control798999 +Node: Debugger Execution Control802663 +Node: Viewing And Changing Data806023 +Node: Execution Stack809379 +Node: Debugger Info810846 +Node: Miscellaneous Debugger Commands814828 +Node: Readline Support820004 +Node: Limitations820835 +Node: Arbitrary Precision Arithmetic823087 +Ref: Arbitrary Precision Arithmetic-Footnote-1824736 +Node: General Arithmetic824884 +Node: Floating Point Issues826604 +Node: String Conversion Precision827485 +Ref: String Conversion Precision-Footnote-1829190 +Node: Unexpected Results829299 +Node: POSIX Floating Point Problems831452 +Ref: POSIX Floating Point Problems-Footnote-1835277 +Node: Integer Programming835315 +Node: Floating-point Programming837054 +Ref: Floating-point Programming-Footnote-1843385 +Ref: Floating-point Programming-Footnote-2843655 +Node: Floating-point Representation843919 +Node: Floating-point Context845084 +Ref: table-ieee-formats845923 +Node: Rounding Mode847307 +Ref: table-rounding-modes847786 +Ref: Rounding Mode-Footnote-1850801 +Node: Gawk and MPFR850980 +Node: Arbitrary Precision Floats852235 +Ref: Arbitrary Precision Floats-Footnote-1854678 +Node: Setting Precision854994 +Ref: table-predefined-precision-strings855680 +Node: Setting Rounding Mode857825 +Ref: table-gawk-rounding-modes858229 +Node: Floating-point Constants859416 +Node: Changing Precision860845 +Ref: Changing Precision-Footnote-1862242 +Node: Exact Arithmetic862416 +Node: Arbitrary Precision Integers865554 +Ref: Arbitrary Precision Integers-Footnote-1868572 +Node: Dynamic Extensions868719 +Node: Extension Intro870177 +Node: Plugin License871442 +Node: Extension Mechanism Outline872127 +Ref: load-extension872544 +Ref: load-new-function874022 +Ref: call-new-function875017 +Node: Extension API Description877032 +Node: Extension API Functions Introduction878245 +Node: General Data Types883111 +Ref: General Data Types-Footnote-1888713 +Node: Requesting Values889012 +Ref: table-value-types-returned889743 +Node: Constructor Functions890697 +Node: Registration Functions893717 +Node: Extension Functions894402 +Node: Exit Callback Functions896627 +Node: Extension Version String897876 +Node: Input Parsers898526 +Node: Output Wrappers908283 +Node: Two-way processors912793 +Node: Printing Messages915001 +Ref: Printing Messages-Footnote-1916078 +Node: Updating `ERRNO'916230 +Node: Accessing Parameters916969 +Node: Symbol Table Access918199 +Node: Symbol table by name918711 +Node: Symbol table by cookie920458 +Ref: Symbol table by cookie-Footnote-1924588 +Node: Cached values924651 +Ref: Cached values-Footnote-1928100 +Node: Array Manipulation928191 +Ref: Array Manipulation-Footnote-1929289 +Node: Array Data Types929328 +Ref: Array Data Types-Footnote-1932031 +Node: Array Functions932123 +Node: Flattening Arrays935889 +Node: Creating Arrays942741 +Node: Extension API Variables947466 +Node: Extension Versioning948102 +Node: Extension API Informational Variables950003 +Node: Extension API Boilerplate951089 +Node: Finding Extensions954893 +Node: Extension Example955453 +Node: Internal File Description956183 +Node: Internal File Ops960274 +Ref: Internal File Ops-Footnote-1971782 +Node: Using Internal File Ops971922 +Ref: Using Internal File Ops-Footnote-1974275 +Node: Extension Samples974541 +Node: Extension Sample File Functions976065 +Node: Extension Sample Fnmatch984550 +Node: Extension Sample Fork986276 +Node: Extension Sample Inplace987494 +Node: Extension Sample Ord989272 +Node: Extension Sample Readdir990108 +Node: Extension Sample Revout991640 +Node: Extension Sample Rev2way992233 +Node: Extension Sample Read write array992923 +Node: Extension Sample Readfile994806 +Node: Extension Sample API Tests995624 +Node: Extension Sample Time996149 +Node: gawkextlib997513 +Node: Language History1000294 +Node: V7/SVR3.11001887 +Node: SVR41004207 +Node: POSIX1005649 +Node: BTL1007035 +Node: POSIX/GNU1007769 +Node: Feature History1013368 +Node: Common Extensions1026332 +Node: Ranges and Locales1027644 +Ref: Ranges and Locales-Footnote-11032262 +Ref: Ranges and Locales-Footnote-21032289 +Ref: Ranges and Locales-Footnote-31032549 +Node: Contributors1032770 +Node: Installation1037915 +Node: Gawk Distribution1038809 +Node: Getting1039293 +Node: Extracting1040119 +Node: Distribution contents1041811 +Node: Unix Installation1047516 +Node: Quick Installation1048133 +Node: Additional Configuration Options1050577 +Node: Configuration Philosophy1052313 +Node: Non-Unix Installation1054667 +Node: PC Installation1055125 +Node: PC Binary Installation1056424 +Node: PC Compiling1058272 +Node: PC Testing1061216 +Node: PC Using1062392 +Node: Cygwin1066577 +Node: MSYS1067577 +Node: VMS Installation1068091 +Node: VMS Compilation1068855 +Ref: VMS Compilation-Footnote-11070470 +Node: VMS Dynamic Extensions1070528 +Node: VMS Installation Details1071901 +Node: VMS Running1074148 +Node: VMS GNV1076982 +Node: VMS Old Gawk1077705 +Node: Bugs1078175 +Node: Other Versions1082093 +Node: Notes1088177 +Node: Compatibility Mode1088977 +Node: Additions1089760 +Node: Accessing The Source1090687 +Node: Adding Code1092127 +Node: New Ports1098172 +Node: Derived Files1102307 +Ref: Derived Files-Footnote-11107628 +Ref: Derived Files-Footnote-21107662 +Ref: Derived Files-Footnote-31108262 +Node: Future Extensions1108360 +Node: Implementation Limitations1108943 +Node: Extension Design1110195 +Node: Old Extension Problems1111349 +Ref: Old Extension Problems-Footnote-11112857 +Node: Extension New Mechanism Goals1112914 +Ref: Extension New Mechanism Goals-Footnote-11116279 +Node: Extension Other Design Decisions1116465 +Node: Extension Future Growth1118571 +Node: Old Extension Mechanism1119407 +Node: Basic Concepts1121147 +Node: Basic High Level1121828 +Ref: figure-general-flow1122099 +Ref: figure-process-flow1122698 +Ref: Basic High Level-Footnote-11125927 +Node: Basic Data Typing1126112 +Node: Glossary1129467 +Node: Copying1154929 +Node: GNU Free Documentation License1192486 +Node: Index1217623 End Tag Table diff --git a/doc/gawk.texi b/doc/gawk.texi index 75c7b758..50496c26 100644 --- a/doc/gawk.texi +++ b/doc/gawk.texi @@ -12893,6 +12893,8 @@ 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. + 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 @@ -16745,11 +16747,10 @@ 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. +@code{fflush()} was added to Brian Kernighan's version of @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 @@ -17881,7 +17882,7 @@ 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. +enforce this restriction.) 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 @@ -17928,7 +17929,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. @@ -18020,7 +18021,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. @@ -18076,7 +18078,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. @@ -18087,11 +18092,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 @@ -18561,7 +18561,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, @@ -18682,8 +18682,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 @@ -18756,7 +18757,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 @@ -18894,6 +18895,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 @@ -19023,7 +19026,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 @@ -19337,9 +19340,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 @@ -19388,7 +19391,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 @@ -19502,7 +19505,7 @@ function _ord_init( low, high, i, t) @cindex ASCII @cindex EBCDIC @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, @@ -19513,7 +19516,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 @@ -20187,7 +20190,7 @@ END @{ 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, +In particular, if you have a file name that contains an @samp{=} character, @command{awk} treats the file name as an assignment, and does not process it. Some users have suggested an additional command-line option for @command{gawk} @@ -20866,7 +20869,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. @@ -20896,10 +20899,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 @@ -21403,7 +21405,7 @@ index and value, use the indirect function call syntax 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 +function that expects to receive an index and a value, and then processes the element. @@ -21757,7 +21759,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 @@ -24485,7 +24487,7 @@ 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 @samp{/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}. @@ -25527,7 +25529,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 @{ @@ -25815,52 +25817,60 @@ 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 @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. @@ -25868,13 +25878,14 @@ They are as follows: @itemize @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 @item @@ -25955,8 +25966,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/ @@ -26046,6 +26057,11 @@ 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. + +@quotation NOTE +The @option{--pretty-print} option still runs your program. +This will change in the next major release. +@end quotation @c ENDOFRANGE advgaw @c ENDOFRANGE gawadv @c ENDOFRANGE awkp @@ -34284,7 +34300,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 diff --git a/doc/gawktexi.in b/doc/gawktexi.in index cd9c775e..48c09f31 100644 --- a/doc/gawktexi.in +++ b/doc/gawktexi.in @@ -12272,6 +12272,8 @@ 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. + 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 @@ -16045,11 +16047,10 @@ 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. +@code{fflush()} was added to Brian Kernighan's version of @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 @@ -17053,7 +17054,7 @@ 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. +enforce this restriction.) 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 @@ -17100,7 +17101,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. @@ -17192,7 +17193,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. @@ -17248,7 +17250,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. @@ -17259,11 +17264,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 @@ -17733,7 +17733,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, @@ -17854,8 +17854,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 @@ -17928,7 +17929,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 @@ -18066,6 +18067,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 @@ -18195,7 +18198,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 @@ -18509,9 +18512,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 @@ -18560,7 +18563,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 @@ -18674,7 +18677,7 @@ function _ord_init( low, high, i, t) @cindex ASCII @cindex EBCDIC @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, @@ -18685,7 +18688,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 @@ -19330,7 +19333,7 @@ END @{ 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, +In particular, if you have a file name that contains an @samp{=} character, @command{awk} treats the file name as an assignment, and does not process it. Some users have suggested an additional command-line option for @command{gawk} @@ -20009,7 +20012,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. @@ -20039,10 +20042,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 @@ -20546,7 +20548,7 @@ index and value, use the indirect function call syntax 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 +function that expects to receive an index and a value, and then processes the element. @@ -20900,7 +20902,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 @@ -23628,7 +23630,7 @@ 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 @samp{/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}. @@ -24670,7 +24672,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 @{ @@ -24958,52 +24960,60 @@ 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 @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. @@ -25011,13 +25021,14 @@ They are as follows: @itemize @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 @item @@ -25098,8 +25109,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/ @@ -25189,6 +25200,11 @@ 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. + +@quotation NOTE +The @option{--pretty-print} option still runs your program. +This will change in the next major release. +@end quotation @c ENDOFRANGE advgaw @c ENDOFRANGE gawadv @c ENDOFRANGE awkp @@ -33427,7 +33443,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 |