1
0
mirror of git://git.sv.gnu.org/coreutils.git synced 2026-08-07 09:11:11 +02:00

Fix typo in env_default comment.

(18c, 18d): Reverse the order of output lines, so that the
test cases conform to POSIX.
This commit is contained in:
Jim Meyering
2004-04-26 15:43:37 +00:00
parent 9a3fee94a0
commit b88eb38b98
+9 -8
View File
@@ -3,7 +3,7 @@ package Test;
require 5.002;
use strict;
# Tell head to accept old-style options like `-1'.
# Tell sort to accept old-style options like `-1'.
$Test::env_default = ['_POSIX2_VERSION=199209'];
my @tv = (
@@ -162,15 +162,16 @@ my @tv = (
# key specifier when a key-specific option (`n' in this case) is used.
["18b", '-b -k1.1,1.2n', " 901\n100\n", " 901\n100\n", 0],
# No change from above because the `b' on the key-end part of the
# key specifier makes sort ignore only trailing blanks
["18c", '-k1.1,1.2nb', " 901\n100\n", " 901\n100\n", 0],
# Here we're comparing ` 90' and `10', because the `b' on the key-end specifier
# makes sort ignore leading blanks when determining that key's *end*.
["18c", '-k1.1,1.2nb', " 901\n100\n", "100\n 901\n", 0],
# Here we're comparing `90' and `10', because the `b' on the key-start
# specifier makes sort ignore *leading* blanks on that key.
["18d", '-k1.1b,1.2n', " 901\n100\n", "100\n 901\n", 0],
# Here we're comparing `9' and `10', because the `b' on the key-start specifier
# makes sort ignore leading blanks when determining that key's *start*.
["18d", '-k1.1b,1.2n', " 901\n100\n", " 901\n100\n", 0],
# Equivalent to above, except it ignores both leading and trailing blanks.
# This compares `90' and `10', as it ignores leading blanks for both
# key start and key end.
["18e", '-nb -k1.1,1.2', " 901\n100\n", "100\n 901\n", 0],
# This looks odd, but works properly -- 2nd keyspec is never