aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gawk.texi
diff options
context:
space:
mode:
authorArnold D. Robbins <arnold@skeeve.com>2018-06-11 20:36:19 +0300
committerArnold D. Robbins <arnold@skeeve.com>2018-06-11 20:36:19 +0300
commit210ab15f91e781c7c9e660c5f897cb0918b70db0 (patch)
tree62e898a55a61dc8895959624476497a38370e9c2 /doc/gawk.texi
parente45f49c2abf38683327dff05da247ea5f3d401ac (diff)
parentc02d836a8cdfd0c26d56b4547dfef69a762a3576 (diff)
downloadegawk-210ab15f91e781c7c9e660c5f897cb0918b70db0.tar.gz
egawk-210ab15f91e781c7c9e660c5f897cb0918b70db0.tar.bz2
egawk-210ab15f91e781c7c9e660c5f897cb0918b70db0.zip
Merge branch 'gawk-4.2-stable'
Diffstat (limited to 'doc/gawk.texi')
-rw-r--r--doc/gawk.texi7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/gawk.texi b/doc/gawk.texi
index adc1395c..70e5d18d 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -6588,6 +6588,13 @@ 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.
+@command{gawk} allows @code{RS} to be a full regular expression
+(discussed shortly; @pxref{gawk split records}). Even so, using
+a regular expression metacharacter, such as @samp{.} as the single
+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}).