aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gawktexi.in
diff options
context:
space:
mode:
authorArnold D. Robbins <arnold@skeeve.com>2020-12-07 14:28:30 +0200
committerArnold D. Robbins <arnold@skeeve.com>2020-12-07 14:28:30 +0200
commit8224cc546f7cfb0922fb69f3ad3f91313cf80e37 (patch)
tree369201efec078e37da78f3797e72f3e244f8adf6 /doc/gawktexi.in
parent0dfeaff26d60ebf6e175a781fe47f4e48a0ee210 (diff)
downloadegawk-8224cc546f7cfb0922fb69f3ad3f91313cf80e37.tar.gz
egawk-8224cc546f7cfb0922fb69f3ad3f91313cf80e37.tar.bz2
egawk-8224cc546f7cfb0922fb69f3ad3f91313cf80e37.zip
Remove some incorrect stuff from gawktexi.in.
Diffstat (limited to 'doc/gawktexi.in')
-rw-r--r--doc/gawktexi.in16
1 files changed, 0 insertions, 16 deletions
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index ceacad6b..78a28be1 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -6641,22 +6641,6 @@ character in the value of @code{RS} has no special effect: it is
treated literally. This is required for backwards compatibility with
both Unix @command{awk} and with POSIX.
-When using regular characters as the record separator,
-there is one unusual case that occurs when @command{gawk} is
-being fully POSIX-compliant (@pxref{Options}).
-Then, the following (extreme) pipeline prints a surprising @samp{1}:
-
-@example
-$ @kbd{echo | gawk --posix 'BEGIN @{ RS = "a" @} ; @{ print NF @}'}
-@print{} 1
-@end example
-
-There is one field, consisting of a newline. The value of the built-in
-variable @code{NF} is the number of fields in the current record.
-(In the normal case, @command{gawk} treats the newline as whitespace,
-printing @samp{0} as the result. Most other versions of @command{awk}
-also act this way.)
-
@cindex dark corner @subentry input files
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}.