summaryrefslogtreecommitdiff
path: root/tests/sort/Test.pm
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>1996-08-24 17:57:14 +0000
committerJim Meyering <jim@meyering.net>1996-08-24 17:57:14 +0000
commitd57a5cc166392cc66a8908c1bf140e161e0609e8 (patch)
tree05ad3bc5fce92d8a137db60e3d3a8039327d3476 /tests/sort/Test.pm
parent7216f62cada6182120748ef17589355afc496a36 (diff)
downloadcoreutils-d57a5cc166392cc66a8908c1bf140e161e0609e8.tar.xz
Reverse 10f and 10g so sort passes these tests.
Diffstat (limited to 'tests/sort/Test.pm')
-rwxr-xr-xtests/sort/Test.pm7
1 files changed, 5 insertions, 2 deletions
diff --git a/tests/sort/Test.pm b/tests/sort/Test.pm
index 6ed764202..bde59268d 100755
--- a/tests/sort/Test.pm
+++ b/tests/sort/Test.pm
@@ -87,8 +87,11 @@ use strict;
# An even simpler example demonstrating the bug.
["10e", '-k 1.2,1.2', "ab\nba\n", "ba\nab\n", 0],
#
-["10f", '-t : -k 1.3,1.3', ":ab\n:ba\n", ":ab\n:ba\n", 0],
-["10g", '-k 1.4,1.4', "a ab\nb ba\n", "a ab\nb ba\n", 0],
+# The way sort works on these inputs (10f and 10g) seems wrong to me.
+# See May 30 ChangeLog entry. POSIX doesn't seem to say one way or
+# the other, but that's the way all other sort implementations work.
+["10f", '-t : -k 1.3,1.3', ":ab\n:ba\n", ":ba\n:ab\n", 0],
+["10g", '-k 1.4,1.4', "a ab\nb ba\n", "b ba\na ab\n", 0],
#
# Exercise bug re using -b to skip trailing blanks.
["11a", '-t: -k1,1b -k2,2', "a\t:a\na :b\n", "a\t:a\na :b\n", 0],