diff options
Diffstat (limited to 'doc/gawktexi.in')
| -rw-r--r-- | doc/gawktexi.in | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/gawktexi.in b/doc/gawktexi.in index dddcf673..51d9afeb 100644 --- a/doc/gawktexi.in +++ b/doc/gawktexi.in @@ -7704,7 +7704,6 @@ FPAT = "([^,]*)|(\"[^\"]+\")" Finally, the @code{patsplit()} function makes the same functionality available for splitting regular strings (@pxref{String Functions}). - @node Testing field creation @section Checking How @command{gawk} Is Splitting Records @@ -17678,8 +17677,8 @@ whitespace goes into @code{@var{seps}[@var{n}]}, where @var{n} is the return value of @code{split()} (i.e., the number of elements in @var{array}). -The @code{split()} function splits strings into pieces in a -manner similar to the way input lines are split into fields. For example: +The @code{split()} function splits strings into pieces in the same way +that input lines are split into fields. For example: @example split("cul-de-sac", a, "-", seps) @@ -17715,6 +17714,8 @@ are separated by runs of whitespace. Also, as with input field splitting, if @var{fieldsep} is the null string, each individual character in the string is split into its own array element. @value{COMMONEXT} +Additionally, if @var{fieldsep} is a single-character string, that string acts +as the separator, even if its value is a regular expression metacharacter. Note, however, that @code{RS} has no effect on the way @code{split()} works. Even though @samp{RS = ""} causes the newline character to also be an input |