awk: CRLF handling

Previous efforts at handling DOS-style line endings in awk have
included commits ee7e00dc5 and 1a3717342.

The use of remove_cr() is unwise:

- It's overzealous, removing all CRs, not just those in CRLF pairs.

- Even if that were fixed awk reads input in chunks. There's a
  remote chance a CRLF might appear at a chunk boundary and be
  missed.

remove_cr() will be fixed separately.  In awk treat all data input
as being in text mode.

Skipping CRs in skip_spaces() is also flawed.  Instead read scripts
in text mode.

Add a couple of test cases.  One of these (awk backslash+CRLF eaten
with no trace) fails without this patch.

1 files changed, 14 insertions, 0 deletions

diff --git a/testsuite/awk.tests b/testsuite/awk.tests
index bbf0fbff1..11beb1b10 100755
--- a/testsuite/awk.tests
+++ b/testsuite/awk.tests
@@ -485,4 +485,18 @@ testing 'awk assign while test' \
         "" \
         "foo"
 
+optional PLATFORM_MINGW32
+testing 'awk match line ending' \
+        "awk '/world$/'" \
+        "world\n" \
+        "" \
+        "hello\r\nworld\r\n"
+
+testing 'awk backslash+CRLF eaten with no trace' \
+        "awk -f -" \
+        "Hello world\n" \
+        '' \
+        'BEGIN { printf "Hello\\\r\n world\\n" }\n'
+SKIP=
+
 exit $FAILCOUNT