aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gawktexi.in
diff options
context:
space:
mode:
authorArnold D. Robbins <arnold@skeeve.com>2018-06-11 20:37:01 +0300
committerArnold D. Robbins <arnold@skeeve.com>2018-06-11 20:37:01 +0300
commit002c1fea9a83ec2d4abca4a84c7eeeee41bc219c (patch)
tree766a5e266915d2f0b05a966158c0ebb60bd7b7a3 /doc/gawktexi.in
parent6d352b599c28cb165f14ccf71a06cdaa016646b6 (diff)
parent210ab15f91e781c7c9e660c5f897cb0918b70db0 (diff)
downloadegawk-002c1fea9a83ec2d4abca4a84c7eeeee41bc219c.tar.gz
egawk-002c1fea9a83ec2d4abca4a84c7eeeee41bc219c.tar.bz2
egawk-002c1fea9a83ec2d4abca4a84c7eeeee41bc219c.zip
Merge branch 'master' into feature/fix-comments
Diffstat (limited to 'doc/gawktexi.in')
-rw-r--r--doc/gawktexi.in7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index 268ada1a..e6a44248 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -6371,6 +6371,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}).