diff options
| -rw-r--r-- | doc/ChangeLog | 2 | ||||
| -rw-r--r-- | doc/gawk.info | 6 | ||||
| -rw-r--r-- | doc/gawk.texi | 6 | ||||
| -rw-r--r-- | doc/gawktexi.in | 6 |
4 files changed, 11 insertions, 9 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index 96f09650..6017ee44 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -4,6 +4,8 @@ dlward134@gmail.com. Added an example of use of rewind(), also per suggestion from David Ward. * gawktexi.in: Update info about Texinfo versions. + * gawktexi.in (Limitations): Fix Heisenberg Physics example and + spelling of Heisenberg's name. Thanks to Hermann Peifer. 2016-02-14 Arnold D. Robbins <arnold@skeeve.com> diff --git a/doc/gawk.info b/doc/gawk.info index 6c35a5f1..35484814 100644 --- a/doc/gawk.info +++ b/doc/gawk.info @@ -21991,7 +21991,7 @@ debug (the "debuggee", if you will). The 'gawk' debugger is different; it is an integrated part of 'gawk' itself. This makes it possible, in rare cases, for 'gawk' to become an -excellent demonstrator of Heisenburg Uncertainty physics, where the mere +excellent demonstrator of Heisenberg Uncertainty physics, where the mere act of observing something can change it. Consider the following:(1) $ cat test.awk @@ -22025,13 +22025,13 @@ under the debugger: -| main() at `test.awk':1 -| 1 { print typeof($1), typeof($2) } gawk> n Get result from typeof() - -| strnum string Result for $2 isn't right + -| strnum number Result for $2 isn't right -| Program exited normally with exit value: 0 gawk> quit In this case, the act of comparing the new value of '$2' with the old one caused 'gawk' to evaluate it and determine that it is indeed a -string, and this is reflected in the result of 'typeof()'. +number, and this is reflected in the result of 'typeof()'. Cases like this where the debugger is not transparent to the program's execution should be rare. If you encounter one, please report diff --git a/doc/gawk.texi b/doc/gawk.texi index 91d3d167..33a823bc 100644 --- a/doc/gawk.texi +++ b/doc/gawk.texi @@ -30526,7 +30526,7 @@ debug (the @dfn{debuggee}, if you will). The @command{gawk} debugger is different; it is an integrated part of @command{gawk} itself. This makes it possible, in rare cases, -for @command{gawk} to become an excellent demonstrator of Heisenburg +for @command{gawk} to become an excellent demonstrator of Heisenberg Uncertainty physics, where the mere act of observing something can change it. Consider the following:@footnote{Thanks to Hermann Peifer for this example.} @@ -30565,14 +30565,14 @@ gawk> @kbd{n} @ii{Keep going @dots{}} @print{} main() at `test.awk':1 @print{} 1 @{ print typeof($1), typeof($2) @} gawk> @kbd{n} @ii{Get result from} typeof() -@print{} strnum string @ii{Result for} $2 @ii{isn't right} +@print{} strnum number @ii{Result for} $2 @ii{isn't right} @print{} Program exited normally with exit value: 0 gawk> @kbd{quit} @end example In this case, the act of comparing the new value of @code{$2} with the old one caused @command{gawk} to evaluate it and determine that it -is indeed a string, and this is reflected in the result of +is indeed a number, and this is reflected in the result of @code{typeof()}. Cases like this where the debugger is not transparent to the program's diff --git a/doc/gawktexi.in b/doc/gawktexi.in index 19c1217e..7c9d473e 100644 --- a/doc/gawktexi.in +++ b/doc/gawktexi.in @@ -29617,7 +29617,7 @@ debug (the @dfn{debuggee}, if you will). The @command{gawk} debugger is different; it is an integrated part of @command{gawk} itself. This makes it possible, in rare cases, -for @command{gawk} to become an excellent demonstrator of Heisenburg +for @command{gawk} to become an excellent demonstrator of Heisenberg Uncertainty physics, where the mere act of observing something can change it. Consider the following:@footnote{Thanks to Hermann Peifer for this example.} @@ -29656,14 +29656,14 @@ gawk> @kbd{n} @ii{Keep going @dots{}} @print{} main() at `test.awk':1 @print{} 1 @{ print typeof($1), typeof($2) @} gawk> @kbd{n} @ii{Get result from} typeof() -@print{} strnum string @ii{Result for} $2 @ii{isn't right} +@print{} strnum number @ii{Result for} $2 @ii{isn't right} @print{} Program exited normally with exit value: 0 gawk> @kbd{quit} @end example In this case, the act of comparing the new value of @code{$2} with the old one caused @command{gawk} to evaluate it and determine that it -is indeed a string, and this is reflected in the result of +is indeed a number, and this is reflected in the result of @code{typeof()}. Cases like this where the debugger is not transparent to the program's |